Deploy an application in real time

Similar Questions

• cRIO: error when compiling an application in real time

  My code can be executed when the cRIO is connected to the PC with Ethernet cable.

  But when I want to compile my code (Release), I get the following massage.

  Also the image of the massage is shown below.

  ////////////////////////////////////

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use the following as a reference:

  Error 6 took place to copy in AB_Targetfile.lvclassostBuild.vi-> AB_Application.lvclassostBuild.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File generic i/o error.

  E:\2013_05_23a_research\2013_05_27a_Richard's\exercise\2013_07_07_exampleFinder_1DMAFIFO\examples\CompactRIO\Module Specific\NI 9234\builds\NI 9234 is Started\NI-cRIO9024-UConn\My in time real Application\c

  ////////////////////////////////////

  

  Hi Cashany,

  What version of LabVIEW Real-time work? What cRIO you deploy? What version of the Drivers OR-RIO do you use?

  Behind your error dialog box you have a save warning dialog box. What is the full path of ANTICIPATED LabVIEW expects to find this VI to? Have you tried to correct this conflict by moving the file to the intended path or change your project for what he expect from this new path?

  I also note that the listed pathnames are rather long. It is possible that your problem is related to this knowledge base, error 6 occurs to create folder when I build my executable in real time?

• Quit the Application in real time

  Is it possible to leave a real-time application of in the software (the exit() function reboots the system according to the documentation) without the system rebooting?

  Thank you

  Martin

  The only safe way to complete a CVI RT application is to return from the function RTMain. If you are very deeply nested under RTMain when you want to complete the application, and it is not practical to place battery completely upward, then an option you have is to use setjmp/longjmp functions to jump up to RTMain.

  If you do not skip a bunch of code of long jump, you must always be very careful in making sure you release/close all handles or other memory resources that your application may have acquired, before leaving. Unlike Windows, the RT process unique operating system and the process will continue to run after your application exits, so whatever you do in an invocation will persist.

  Luis

• cRIO - creation and deployment of real-time independent startup application troubleshooting

  I use cRIO-9024 with a chassis 9112 for a control system. I use LV2011 SP1. When you run the system in development mode (by pressing the run button), everything seems to work properly. When the autonomous real-time construction and running in startup application, something stops working.

  In order to know if the application is running or not, I toggle the user LED on the cRIO using this code:

  

  When I turn off all the code in the main VI except this loop, the application deploys and runs at startup without problem (the LED flashes). I then add progressively more loops that I want to run (by disabling the code less and less), and the problem seems to be in the open FPGA VI reference block. If I disable this block, the slopes of autonomous real-time application (I guess the error 63195, handful of peripheral communication not valid, will spread along the line, but I know that the app works because the LED flashes).

  

  I tried several configurations for this block open FPGA VI and mixed results. For example, if I set it up this way:

  

  The application in real-time to start runs with the reference block opened VI FPGA active but work stoppages as soon as I turn on a code that makes use of this reference in the subVIs .

  Someone at - it an idea of what could go wrong? I have explored the messages thrown by cRIO at startup but can not see the error messages (in fact, the console output is the same when I managed to deploy an application that is running (by disabling the code). I also tried to explore the error logs (via right click on target Utilities > view error log) but cannot decrypt any useful info on their part.

  

  Any ideas will be greatly appreciated.

  Hi kkguner,

  My problem is that the code runs (apparently) ok in development mode, but it seems that, when it is deployed as a stand-alone application in real time, it does not at all. As I was not able to get messages through to watch the console output when restarting my cRIO or explore the Project Explorer error logs or error, I can only imagine what is happening.

  I feel that QFang suggestions go in the right direction, but I've yet to be able to determine the exact cause and the solution of the problem.

  The solution I set it with has been to deploy my application as a source with a start VI distribution instead of as a stand-alone application in real time. You can try this option.

  What I could try when I have some time is to clean my system from LV (whether in mass compilation or by reinstalling completely). I tried a massive compilation of vi.lib and I got a good amount of (UN) insanities, the wrong screws and several other unfortunate messages.

  kkguner, let us know what you discover in your inquiry, or if none of the suggestions solves your problem.

  Thank you QFang and xseadog for your help. Best regards!

  --

  Raúl

• Control software for real-time Applications

  Hi all

  We develop products based on the platform or sbRIO and deploy applications to the target in real time. We need to get these what UL listed products and part of the procedure test requires that the software be locked and not changed while the test is in progress. For this I need a way to get and display the checksum (or some other signature) of the currently deployed on the target real-time application.

  Is there a way to do this? Please let me know if you need more information.

  Thank you

  Hi LabVIEWingToday

  On the first link in the previous post, there is a section that explains what is the checksum and they recommend a community tool or a LabVIEW VI, you could use programmatically.

  To calculate a checksum on the key files, consider using the File.VI MD5Checksum, which is built...

  Concerning

  R. Esteban

• build a real-time application failed

  When I Isaiah to compile my application in real-time in order to deploy it in a device crio, it fails. I can run very well by opening it and clicking run. It can deploy and run all day in this way, but he needs the computer that much too. So I need to be able to build and deploy. When I do a preview of the generation, it complements very well with no error. I put the program I want to launch the start and my folder virtual subVIs always include. It is a typical procedure for deploying projects on the crio.

  When it crashes, I get an error:

  The build failed.

  Possible reasons

  An error occurred during the recording of the following file:

  C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\rvi\ClientSDK\Core\ModuleGeneration\CommunicationInterfaceUtility\niFpgaDmaChannelImplementation.ctl

  Invoke the node in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_RTEXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_RTEXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_CreateNewWizard_Invoke_CORE.vi-> RTBUIP_CreateNewWizard_Invoke.vi-> RTBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
  
  Method name: Save target: Instrument

  I put in a request for service (reference #7259553), but I'm just not getting help fast enough. I'm on a real deadline here and I expected just kind of request of manufacturer to work as she has always done. I have done this a million times with other applications and never had a problem like this.

  Thanks in advance for your help guys.

  With the great help of sales engineer Will Schoettler, we were able to solve the problem.

  1. first of all we tried to create a new project from scratch file, add all the files and the fpga of the compilation. Same mistake.

  2. then we made individual buildings deploy each Subvi individually to see if one of them was the cause of error. Each built without problem.

  3. I tried to create a new generation of program main crio and tweek the settings. Rather than manually adding the Subvi and variable to the section "always include" the compilation option library folder, I simply added the main VI to the list of startup programs and would make LabVIEW to understand what screws to add. For some reason, this gave me a more verbose error explanation and gave the following reason as the last sentence of the explanation of the error

  "Due to limitations of the operating system, LabVIEW cannot create the file because its pathname contains too many characters."

  I moved the project to the c: folder /, fixed broken in the project references, and he built the VI and deployed it is fine.

  The constructor creates a directory with a very long path name in your project file, so if you have your project folder deep in your directory tree, it will attempt to create files with paths for windows too big to manage.

  Mad Kudos to Will Schoettler engineering app for such a powerful and complete troubleshooting task list to try things which lead me straight to the solution. I'm glad it was something so simple and not a form of file corruption or something wrong with my code.

  Thanks for trying to help the guy.

• Deployment of local variables shared on a real-time target

  Hello everyone, once again

  I read more posts and knowledge base articles about this topic than I can count at this point, and I'm scared, I'm still not clear on exactly how it works, and I hope that someone can delete it for me, if it is to earn themselves some laurels more.

  I have a project with a real-time quote and the other Windows.  They shared communication via network-published variables.  The real-time part also uses shared single process variables to communicate between the loops.  I have the intention of all 3 libraries of shared variables (Windows-> RT, RT-> Windows and RT Local) to be hosted on RT target for reliability.  Real-time executable must start at startup and run even if side Windows is not started (on the side of Windows is optional).

  I realized that real-time executable will not start the variable engine shared and/or deploy itself shared variables.  I also read that I can't deploy the shared variables programmatically from the side of RT.  This leaves only two options that I know of:

  (1) their deployment programmatically in Windows-side program.

  (2) deploying the shared variables on the target RT manually via the project in the LabVIEW development environment, and

  About option 1, as I said running Windows is supposed to be optional, so you have to run a program on the Windows side before the side RT will work is highly undesirable.  Moreover, even if I do a little "Deploy shared variable" application that runs at Windows startup, I can't guarantee that it will work before start of the side RT executable will run.  In this case, the executable file RT will fail due to not having the variable engine shared running?  If so, and side Windows, and then starts the engine / deploys the shared variables, the side RT begins to work automatically?  If not, is it possible to trigger this restart of the Windows startup application side?

  Also, I just read everything and tried the option to build to deploy variables shared in the application of the side Windows.  Not only that my RT shared Local Library variables not listed as an option (given that the application of the side Windows does refer to it in all for obvious reasons), but when it deployed two other libraries at startup, the program side of RT (which was running in the development environment) stopped.  I'm not positive that would happen even if he was running like a real executable file, but it is certainly enough to make me nervous.  I assumed that the library is not listed may be resolved by including a variable network-a published in the local library of RT and including the app side Windows.

  About option 2, I don't understand how I'm supposed to deploy my libraries shared variables without stopping the execution of the startup on the target real-time application.  Once I did, the only way to restart the application of the RT is to restart the computer RT, correct?  In this case, I just undid all the interest to deploy the shared variable libraries?  Unless libraries remain deployed and variable motor shared running even after restarting the computer of RT, which would solve the problem I guess.  Certainly, I would like to know if this is the case.

  However, option 2 is complicated by the fact that when I manually right-click on any of my shared variables libraries and select "Deploy" or 'Deploy all', libraries still do not appear in the Manager of the distributed systems, even after clicking Refresh several times, on the local system or the target system.  The only thing that shows up, on both sides, is the Group of 'System', with FieldPoint, etc. in it.  The same is true when I run my application in real-time in the development environment, even if the shared variables are clearly working, as I mentioned earlier.

  So, if you have done so far through this mammoth post, thanks!  I have three main questions:

  (1) are that all my descriptions above correct in what concerns the variables how work sharing?

  (2) what is the best way to meet the requirements I have described above for my project?

  (3) why shared variables libraries not appearing in my manager of distributed systems?

  Thanks for any help you can give on any of these three questions!

  -Joe

  1. Yes, as soon as you deploy the project the NSV is tranactional.  EVS is loaded by MAX when you configure the RT target and begin to operate as part of the boot sequence.

  2. you can see anything on your target rt in the DSM?

  3. Yes, NSV and EVS are persistent resets.

• Application errors of the RT with the PXI-4461 with Labview real-time 9.0.1, DAQmx 9.0.2

  HI -.

  I recently converted a PXI time system real OS (PXI-1042 q chassis, controller PXI-8187, DAQ, PXI-4461, DAQ, PXI-6259). I can write and run DAQmx applications in real time with the 6259 very well. Whenever I try to write a labview RT app to use the 4461, however, it will fail. Note that I can use two cards through MAX I tried switching card slots, just in case it was a problem. Both cards worked with labview, the PXI chassis was before Windows.

  Attached are pictures of the screw base demo I built to show the problem. Since I was a mistake (-200758) if I started from the raw strings, I tried to create a MAX task and use it. The task, but he complained of a buffer is too small. I explicitly put the buffer to work around this problem and still get the same error (-200608). I've also attached a screenshot of the software currently on the Max MAX RT PXI system is version 4.6.2 btw. (I installed the most/all this from DS1 Dev Suite 2010 version).

  Please let me know if I hurt something installed, versions if 4461 just don't play nice with the new BT or RT software, or if something is wrong. Thank you.

  Kregg

  The first error you see is (details in the help-> error explain in LV)

• cRIO and 9234 modules do not work or communicate via fpga with accelerometers, fpga, connected to the real-time application is also related to shared variables related to modbus slave

  Hello

  I have a compact rio, which has a 4 way frame this chassis is the three modules of ni9234, they are related using FPGAs for application in real time, then using shared variables in the low-speed loop associated with a slave modbus to communicate with the domain controllers, the nor 9234 accelerometers linked to them with option ac coupled iepe on c modules , my problem is the real-time application seems to work well even when power loss occurs it restarts without problem and the fpga written hard disk portable bin files very well, but without an accelerometer connected I get readings of low noise as soon as I connect an accelerometer to one of the outputs 10 it just goes to a fixed number (0.03125) as soon as you unplug it again He returned to readout noise, I ran a scan on the modules and get only a spike when I connect or disconnect the accelerometer, I tested voltage at the pins on the module and I get 22 volts CC which makes it more likely that the material is not the problem, but software is perhaps the cause to hang up, I join the project and files for your perusal. I also realized a new project which, in mode directly linked scan has the module entry in the shared variable and the scenerio even once again. Help would be appretiated.

  Thank you very much

  Jason

  Whren using waveform with the 9234 acquisition, we recommend the following FPGA and RT model.

  http://sine.NI.com/NIPs/CDs/view/p/lang/en/NID/209114

  It can be extended as a datalogger with:

  http://zone.NI.com/DevZone/CDA/EPD/p/ID/6388

  or using shared variables combined with the analytical engine

  http://zone.NI.com/DevZone/CDA/tut/p/ID/9851

  The FPGA in all this, as well as the framework of RT have used successfully by 1000s of users.  I recommend giving these a try.

• Real-time Application Installer

  I built two requests in real time; one for a PXI Chassi and the other for a compact field point. I wish I could send the customer updated versions of applications in real time and ask them to install them to the respective chassi/fieldpoint in the field. The customer is not the development environment. I looked around MAX, but could not find a way to do this.

  Any ideas?

  Thank you

  Kevan-

  HI Kevan.  Take a look at replication system tools.  According to me, it appeared in 8.0 or more.

  We used the tools NOR as basis of our own tools of level end-user to exactly what you are

  describe (in addition to the upgrade of the OS, if necessary).

  Matt

• Real-time target - change IP and shared network varables

  Hello

  I create an application for the system in time real (Compact RIO).

  All data between the (current running on a windows PC-based) GUI and the real time system - is transferred via shared network variables.

  Shared variables are hosted on the target.

  I attributed the static IP address to the real-time target.

  Now for the question:

  After the deployment of the application in real time on the Rio target compact

  If I change the IP address of the target: how the shared variables 'know' to connect to the target?

  There is no place in the GUI (running on windows PC based) I set the IP address of the target.

  So I change the IP Address of the target (and for the sake of argument if I change the IP address of the PC, but they are always on the same subnet) - how to 'know' how to connect?

  Looks like a basic question I am absolutely certain I'm missing something to understand shared variable...

  Thnaks

  Hello Hazkel,

  The IP address of your shared time variable real target is located in the *.aliases file when you create an executable file, you will need to change there.  See the example below:

  

• Abnormal behavior observed in real-time executable.

  Hello

  I have an interesting problem. I have developed an embedded application of Real-time/FPGA for cRIO 9024 and come across a problem that I don't understand. I work FPGA and RT of top-level and subVIs, proven individually and together when it is run interactively. When I create and deploy an executable in real-time like start, however, the behavior changes. I posted the code below, which I'll explain briefly:

  I have a state machine with 5 States architecture. "Initialize" and "Shut Down" are exactly meet once whenever the device is reset, and the cycle between them is wait > pre-test > wait > run the Test and repeat as many times as desired. Measures are taken by FPGA and past in real-time by DMA FIFO and are then recorded to the TDMS file by the real time. Everything else is just interface.

  The problem comes from the first time, the program enters the Test case to run. The FPGA send measurements as usual, and they are stored in a growing table updated buffering in the fixed-point shift register shown below.

  

  Run interactively, this method successfully bed, buffers, sorts and writes all data in the file. However, in time real executable, only the data collected in the first round (147 items total, as it is initialized by the whole shift register) are saved, the rest seems remainsin a buffer? before calling the following function TDMS write, is that in the case before the next test.

  I'm unable to debug the executable file in real time, probably because of the FPGA reference or some other schema components. I tried to replace the pad with a FIFO in real-time, a variable shared with RT FIFO active and tried to write inside the loop. The FIFO are not improving the situation, and when writing inside the loop, the loop does not run quite fast to stand.

  The problem does not exist when I run the VI interactively from my computer, only when I try to deploy all of the embedded, any application that works (as far as I know) except this one place.

  Any ideas to solve, or workarounds?

  Ryan

  Technical support helped me to resolve the problem, the early termination of loop caused loop condition, although I still don't understand why the behavior was different as an executable file, because the condition of the loop has worked in interactive mode, so if someone has any ideas as to the why, I would still like to know.

• When I use the library function node call in real time, is loaded only once for all or load the DLL whenever it is called?

  When I use the library function node call in real time, is loaded only once for all or load the DLL every time when it is called?

  I have a critical application in real time, in which I use a piece of DLL function developed in C++.  It is ok?  Make sure any senior developer?

  Thank you in advance.

  The user interface thread is the thread that is used to update the user interface. It's slow. And it's supposed to be that way because humans are slow.

  The call library function node can be configured as this thread to use in the configuration for it dialog box. Please visit the LabVIEW documentation on how to do this.

• Shared on a real-time target Variables defined causes the command to remotely fail

  Here's a strange. We create a solution of customer using a CompactRIO, and they want remote panels can view and interact with the executable file. That's fine, we are able to create this, but we noticed a thing is:

  If we build and deploy our code in real-time for CompactRIO with all shared Variables associated with a type definition, the executable will not run. Indeed, it is reported by the browser as a broken VI remote Panel utility.

  Breaking the shared link Variable with the type-def and rebuild the executable file, solves the problem. Weird.

  Anyone else seen this before?

  Hello Thoric,

  I think I spotted a CAR already assigned to it:

  http://www.NI.com/white-paper/13235/en

  #292012

  Looking at our notes this should be fixed in the next version.

• a pc with a stand-alone module, real-time can display of its own data

  Hi all

  It is sort of a basic question, and it's probably why I can't find the answer explicitly in textbooks or the forum posts.

  If I want to use a PC as a unit in real time, and I install the LabView time real OS on it and make an Application of real-time on another machine and compile it in the PC target in time real LabView, can I attach a monitor or a kind of screen directly to the PC unit in real time to display some data I need?  Or do I still need a Labview PC to act as a host for display data and interface with a user?

  Thanks for the info!  I have some experience of labview, making some other applications but I have never used the RealTime module yet so I don't know much. So if there is a good place for more information in time real LabView for use a PC as a device target, which may also be of interest and would be appreciated!

  Thanks again.

  Steve

  Hi Steve,.

  Our objectives in real time are designed to work in headlessly, which means that they are independent and have no user interfaces.  It comes to screens.  For a display of information, you must use a host VI, on a host computer. There are several ways to move data between a target RT and a host PC including, but without limitation, TCP, UDP, network flow, published static Variables of network and Web Services.  These are all covered in documents on best practices.

  Here is a page real-time best practices:

  http://zone.NI.com/reference/en-XX/help/370622J-01/lvrtbestpractices/rt_portal/

  Here's a page on the conversion of a desktop computer to a target RT:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/2733

  Good luck with your project.