Deploying exe into compact rio

Dear Labview Users,
We are using compact rio 9002 and labview 8 version. We made a program to acquire the data through 9215 module, doing some calculations and transmitting to radio through serial port. My problem is, I want to deploy this program permanently into the compact rio, because when power goes and comes the program must start automatically without human intervention.
For this I tried the procedures given in our NI site, but the problem we facing is when we switch OFF and ON the program doesn't start automatically. When we rebooted it by software and reset manually then only its working. But I want this is to rectified, Can anybody help me by providing solution to the same.
Labview Lovers

Shivkumar,
1st: Include the bitfile as supported file to the application (the step before is to add the bitfile to the project)
2nd: If you have finished the configuration make a right click on the application and choose "Set as Startup"
3rd: Afterwards make a right click one more time and click Build and then Download
BR,
ThSa
http://www.newgistics.com

Similar Messages

Compact RIO EtherNet/IP Industrial Communication Data Packaging

Hello,
I’m new to the Industrial Communications for EtherNet/IP module and quite a few questions. I am using a Compact RIO 9074 I first configured the Compact RIO’s Ethernet Adapter eth1 port to TCP/IP Network and entered the static IP address to the same subnet as the Fanuc LR. This was then saved and deployed to the Compact RIO. I then implemented the VI for the Access Assembly Instance Data through Explicit Messages, built the application and deployed it to the Compact Rio. This VI was run and the system shows that its making a connection, however, it’s still not able to communicate.
In the example, there are two arrays, the Data Received, and Data to Set. I want to know if there’s a certain way of configuring the Data to Set to a scanner.
Thank you.
Thomas

Hi Jesse
Thanks for your information it was very helpful.
I thought that the IP address of the Compact RIO’s Ethernet terminal needed to be within the same subnet but not the exact same.
I agree with the Ethernet/IP having an address scheme laid out. Having a look at the example project, it claims I need to create the assembly instance. This can be done using the create assembly instance example VI.
Does the create assembly instance VI need to be running with the Assembly Instance Data (using Explicit Messaging)? If so I’m having difficulty understanding how to apply this. Under the create assembly VI, it uses I/O Data function, while using an array of Data to Set and Data Received. Will the assembly address need to be set up in this array?
I’m having a look through the manual for the Robot and the information I provided before is the configuration for the scanner.
Thanks
Thomas
Attachments:
Assembly Acess Panel.PNG ‏70 KB
Create Assembly Instruction Panal.PNG ‏71 KB
Create Assembly Block.PNG ‏35 KB

R series intelligent DAQ, NI-Compact RIO , NI single board RIO

Hi,
I'm in the phase of choosing an FPGA to use in programming some DSP modules. The thing is that while I'm reading about the different technologies to be used, I find it difficult to know how will these devices be connected to my PC and programmed. For example, when using R series intelligent DAQs, do I have to get a compact RIO as well , or can I get a PCI-bus R - DAQ and connect it to the PC.
Some clarification of how to use each of these devices will be appreciated.
Thanks,
Walid

Just to elaborate on what Venkatesh said
With a compact RIO you will connect your PC to the RIO using Ethernet, direct through a cross over or through a network hub.
This introductory video will teach you how to install, configure, and program the latest NI CompactR...
A PCI R series card, just plugs straight into your Windows computer PCI slot.
A PXI card will plug into a PXI chassis and will give you one of 2 programming options
1. If you have a PXI system controller running Windows XP with the appropriate drivers and version of LV you can program the FPGA directly in the PXI chassis
2. You can connect to the PXI chassis through Ethernet and program the FPGA from there.
Compiling and deploying your program will work the same no matter what connection you use.
-Hunter

Compact RIO Standalone RT Application with Internet access

Hi,
I am currently working on a Compact RIO and would like to deploy the VI as a standalone application to run independantly on the Compact RIO without the need for a host computer. Apart from that, the Compact RIO also has to have internet access. I have a CRIO 9022 and am unsure how to set up internet access for it as well. Should the Ethernet cable be plugged into Socket 1 or Socket 2? The other end of the ethernet cable is connected to a switch with internet access enabled.
Please Help
Thanks

Hi
Thanks for your reply. After we set up the Compact RIO to run st startup with a real time application, what other settings do we have to configure to allow it to have internet access? The IP address is static. Also, we would like to have a remote front panel service running in order to view the front panel from a remote browser to monitor our system. Would it be possible to provide me with some step by step instructions of setting this up? I tried the steps from the guides at National Instruments website but all of them require the presence of a host computer, whereas we are building a real time application.
Thanks

Error 1335 When Installing Compact RIO Module Software 2.1.4 From Hard Drive

I’m having issues with the installation of the CompactRIO Module Software 2.1.4.
Initially, problems were occurring when trying to communicate with the device, as it was denying access to it from the Development PC. Various things were tried such as adding a ‘*’ to the fields and making sure 'Allow' was selected in the communication properties on LabView RT. This didn't seem to work. A post relating to our problem is here: http://forums.ni.com/ni/board/message?board.id=170&message.id=269809&query.id=18752#M269809
As none of this was working, we decided to format the disk on the Compact RIO and reinstall the software to it. The software downloaded from Ni.com was the CompactRIO Module Software version 2.1.4 (dated May 2007). This file was unzipped using WinZIP 9.0 (on a PC running Windows XP Pro SP2 5.1.2600) and then transferred with a USB stick to the Development PC.
We attempted to install the file on the Development PC (running Windows 2000 SP3 5.00.2195) by running setup.exe. This started normally, but then proceeded to come up with an error message saying: ‘Error 1335. The cabinet file ‘Cabs.w1.cab’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.’
Attached are screen shots of the error message that appears.
As a result of this error, the installation could not be continued and the module software was not installed.
What is going wrong with the installation and how can I go about sorting it out?
Thanks very much,
Moses
RT target cRIO-9012, NI-RIO 2.1.3, LV 8.2, RT 8.2, FPGA 8.2, host ip 150.150.10.15, cRIO IP 150.150.10.4
Message Edited by Mohoyt on 09-10-2007 04:03 AM
Attachments:
Error Message CRIO Module 2.1.4.JPG ‏36 KB

Way,
Thanks for the help overall, I finally worked it out. The problem was initially present in the unzipping of the original archive that had been downloaded from the NI.com website. When I had previously unzipped it, I had done so to a network drive which for some reason stopped autorun.inf and autorun.exe from functioning properly and so when I tried to install it on the Dev PC I got the aforementioned error. To overcome this problem I unzipped it to a local drive and (surprise!) there were no faults, so when installing the actual software, no errors appeared and it was installed correctly.
This however was not the only problem, the version that had now been installed did not want to co-operate with the RIO at all, and came up with various software errors in addition to not having all of the available software modules for the RIO available to install. The solution was then to install the newest RIO software, which is very badly labelled on the NI.com website by the way (its packaged as RIO software, so if you're looking explicitly for CRIO software you've got no chance of finding it). The newest version, 2.3 (Aug 07) as opposed to the 2.1.4 (May 07) that I was previously trying, worked fine and I was able to get all the software modules installed. So for now the problem is solved!
Thanks again for all the help.
Cheers,
Moses

Build real-time application with Compact RIO

Good afternoon,
I am currently trying to run a VI on compact RIO and would like to control it through remote front panel. I followed steps on this link http://digital.ni.com/public.nsf/allkb/AB6C6841486E84EA862576C8005A0C26 and successfully done everything with a simple example.
However when I moved on and did the same thing to a more complicated VI (my purpose is to make this VI work), everything was fine until I reboot the compact RIO. After a few seconds connection lost between the host computer and cRIO, and I had to shut it down and delete the startup file (with extension .rtexe).
I am not sure what happened since everthing works fine with simple VI but not the complicated one. It could because the second VI has many sub VIs as well as objective functions loaded in it, it could also because the VI takes too much memories of the CRIO and stop it from connecting to the host computer.
If anyone have any ideas of how to make it work please let me know.
Thanks very much
Carl

Hello zzzfreedom,
There are a number of potential issues I can see with the VI you're trying to deploy as a startup executable. How do you intend to interact with this VI? Are you running the front panel as a remote panel or connecting to the VI using debug tools? A few points:
- Your VI will run immediately when the RIO boots unless you're using debugging tools to prevent this from happening, keep that in mind. It looks like you've accounted for this and required an initialize or network trigger of some sort for some of your loops, but the AI loop will start quickly and appears that it may require user input.
- You have several "user prompt" style express VIs. These will not work (or will not work as expected) on a standalone RT target. There is usually no front panel to interact with!
- Like dialogs, event structures watching for user interaction probably aren't going to do what you want.
- You are writing quite a bit of data to the VI's front panel, and there is at least one chart indicator. Again, how will the user interact with this VI? It looks like you need a host VI that will run on a machine the user will interact with.
- You're using quite a few local variables. It looks like you've taken a lot of care to protect against race conditions, but this causes a lot of data copies and tends to be error prone.
- I've not analyzed all cases, but it looks like you have a number of places where the execution of a timed loop may be blocked under certain conditions. This will likely rail the CPU due to the much higher priority of the timed loops.
- What will happen if you lose connection with the server in your TCP command loop? it doesn't look like there is any way for the user to reconnect without restarting the RIO.
If you do intend to run this as a remotely accessible VI on your RT target, another point to note is that when running from the development environment, the front panel of your VI executes on the host machine. Once you deploy it as a remote front panel or debuggable RTEXE, everything is hosted on the RIO, and this has the potential to bog things down quickly.
Here are a few references I think you might find helpful:
LabVIEW Help: Real-Time Operating Systems - see considerations for Express VIs and Front Panel interaction
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_osnotes/
LabVIEW Help: Real-Time Module on VxWorks Targets - see unsupported features
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_vxworks/
NI LabVIEW for CompactRIO Developer's Guide -lots of good general information on architecting RT applications, network communication and hosts, etc. It looks like you're using the RIO Scan Engine, so the FPGA portion might not be relevant at this time.
http://www.ni.com/compactriodevguide/
Best Regards,
Tom L.

IMAQ FFT multiplication and MATLAB Script Nodes/Compact Rio

I would like to automatically generate a frequency kernel to multiply with the FFT of my IMAQ image. I was wondering if there was a way for LabVIEW to automatically set up 2D arrays (with a lower bound, a step size and a higher bound) like what is done in MATLAB.
I was wondering also, if someone could give me some insight as to what restrictions I face, when uploading code from MATLAB script nodes into the Compact RiO (I have a cRiO-9025).

Hi Bilaln,
I think you confused about a MATLAB script node and a Mathscript node.
A MATLAB script nodes uses ActiveX to call into MATLAB, where as a Mathscript node runs in a NI built environment. The MATLAB script node requires both that MATLAB be installed and the host supports ActiveX. Since cRIO does not do either, you should use the MATHSCRIPT RT module.
Joe Daily
National Instruments
Applications Engineer
may the G be with you ....

Referenced Parameters in C library not working on Compact RIO

High level
I want to use Google Protobuf on my Compact RIO. I have it 90% of the way there and running into issues.
Details
I'm a long time C++ developer who's newish to LabVIEW. I'm using C to create a cross-compiled library to use on a Compact RIO (9025) with LabVIEW code. I'm using Linux (Ubuntu 14.04.1) with a VxWorks toolchain and CMake to create the library. I copy it over manually (looking for a better solution to that here), call it from LabVIEW via a Call Library Function, and assuming I'm doing simple things it works great! Here's a quick sample of what I have that works:
My C code
extern "C" double addNums(double in1, double in2)
return in1 + in2;
extern "C" double multNums(double in1, double in2)
return in1 * in2;
Which I cross compile to a VxWorks binary and copy over to the cRIO.
Then on the LabVIEW side, I have this.
I run it on the target cRIO and all works great.
I mentioned protobuf. Cross compiling the full blown protobuf library for VxWorks proved to be a near (if not 100%) impossible task. So I found and am using Nanopb. I'm able to cross compile and get the following code using Nanopb to actually run on the cRIO and spit out the expected response:
extern "C" double testPbuf()
uint8_t buffer[128];
size_t message_length;
bool status;
std::ofstream file;
file.open("testOutput.bin", std::ios::out | std::ios::binary);
//! Create a message
ExampleMsg message;
message.value = 13;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
status = pb_encode(&stream, ExampleMsg_fields, &message);
//! Decode the message
ExampleMsg message;
pb_istream_t stream = pb_istream_from_buffer(buffer, message_length);
status = pb_decode(&stream, ExampleMsg_fields, &message);
return message.value;
return 0;
Not terribly important, but if you know protobuf, here's the proto message I'm using
message ExampleMsg {
required int32 value = 1;
So then I call this function from LabVIEW very simply:
I run this and it works! I see my 13 as expected. Jump for joy, protobuf works on the Compact RIO! Ok no jumping yet...
Now what I want to do is get the C library to generate and output the actual serialized protobuf message because I need to send it over UDP from the Compact RIO. So here's my attempt so far:
extern "C" const void getPacket(uint8_t* packet)
uint8_t buffer[128];
uint16_t packetSize;
bool status;
ExampleMsg msg;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
msg.value = 14;
status = pb_encode(&stream, ExampleMsg_fields, &msg);
packetSize = stream.bytes_written;
//! If something failed we should see an 'X' in the first byte
if (!status)
buffer[0] = 'X';
memcpy(packet, buffer, packetSize);
And on the LabVIEW side, I'm initializing an array of unsigned int 8s to the proper size and feeding it into the function, and reading the packet parameter as output.
When I run this I never get any output on packet except whatever I set the initializer to. I have also changed the code to try to output a string as a parameter argument, with this declaration:
extern "C" const void getPacket(char* packet)
And memcpy() appropriately and can't seem to get the output properly in LabVIEW using strings in place of the U8s. I need to figure out how to get this serialized protobuf data into LabVIEW so I can send it over UDP as a message.
I have seen several examples in the LabVIEW installation directory, but they're referring to objects and libraries which are meant for Windows DLLs and not easily used in a cross compiled environment. I also have seen many threads on here relating to this but none have helped so far. Any help would be greatly appreciated!

I would hate to do a file write to solve this as it would add a whole new lag to the system. I did end up with a solution, which is essentially what I posted above. It seems like the real issue I was having was that the dll was not being reloaded on subsequent rebuilds/tests. So I would make changes to the DLL to test and they wouldn't be reflected even when I copied the DLL to the Compact RIO. Turns out I have to completely close the project and re-open it if I change the dll file. This is really strange behaviour. I could even *delete* the DLL from the Compact RIO and the VI would still run with the previous "copy" somehow.
Anyhow it looks like I have protobuf working from the Compact RIO, though still have a few issues with encoding certain data types. If anyone is interested in the full solution I may do a write up.

Visa Error in MAX for Compact RIO

Hi,
I have a compact rio I haven't used in a few months. In Labview 7.1 and since upgrading to 7.1.1, I can't
connect to the compact rio. In MAX, I can see the crio device. When I open up the device, I get a VISA error
under Devices and Interfaces . 0xBFFF00A7 (VI_ERROR_MACHINE_NAVAIL). I can't ftp or ping to the crio either.
I have NI-RIO 1.2.
I connected to the crio console ....
General Software STPC Embedded BIOS 2000 (tm) Revision 5.2
Copyright (C) 2003 General Software, Inc.
Copyright (C) 2004 National Instruments Corp.
NI cRIO-9002 Controller
00000589K Low Memory Passed
00064512K Ext Memory Passed
Wait.....
PCI Device Table.
Bus Dev Func VendID DevID Class Irq
00 0B 00 104A 0201 Host Bridge
00 0C 00 104A 0210 ISA Bridge
00 0D 00 104A 0229 IDE Controller 11
00 0E 00 104A 0230 Serial Bus 11
00 0F 00 104A 0238 Ethernet 11
00 18 00 1093 70F7 Unknown Device 11
00 1F 00 104A 0981 Ethernet 10
(C) 1996-2003 General Software, Inc.
STPC-5.2-01DE-EB2E
BIOS revision: 1.1.9 (08/10/04)
Firmware revision: 10.1.94
Booting LabVIEW RT from drive...
Fat16
Jumping to 07E0:0000
Checksum: 011BCEEB
LabVIEW RT Boot Loader
(C) Copyright 2002-2003 National Instruments Corporation
STE10/100A Ethernet found.
Initializing network... done. IP address is 152.50.232.157
--------------------- NI-Serial v2.5.4 for LabVIEW RT ---------------------
COM1 - | Built-In Serial Interface
Welcome to LabVIEW Real-Time 7.1
NI-VISA Server started successfully.

Hi, Raltieri,
I noticed from the text that you sent that your cRIO controller has LabVIEW RT 7.1. Since you upgraded your host computer to LabVIEW 7.1.1, you will also need to upgrade the LabVIEW image on your controller to the same version. Try reinstalling the LabVIEW RT component into the cRIO controller (in MAX, under Remote Systems, under your cRIO >> Software), and just make sure that you select 7.1.1 as the version to reinstall. Most likely that is the problem.
Please let me know if that doesn't help.
GValdes
National Instruments

Error 7 produced when saving to a spread sheet file using a compact rio

Hi
Im having a little difficultly saving to a spread sheet file using a compact rio. I bundled the data from a NI 9215 with a timer and stuck it into an x-y graph and that works fine as it goes round in shift registers. But then I passed the data out of my while loop unbundled it, turned it into a 2d array and tried to write it into a spread sheet file using the appropriate i/o vi provided by labview 8.2. I have hooked up all the requirements like format, and file path. But it keeps returning error 7 and says that my file path is incorrect. I’ve tried using a constant file path, ive tried creating the file before running the program, ive tried just writing the file straight to a disk in this case h:\test.asc but every time it comes back with error 7. I then went to a lab downstairs to see how they did it and the method I’m using it works down there but is exactly the same as mine upstairs. I’m a little confused by this one.
Any pointers would be much appreciated.
Dan

Hi
I apologise I didn’t specify I was only using a NI cRIO-9004 not realising you could get ones that had a USB port. I thought mine would behave in the same way as a DAQ device and write the file back onto the main computer hard drive. Is this not what happens if not how do you make it do that. The computer is a networked system with its own C:\ harddrive, but my personal space is on H:\ which must be like a pretend hard drive, or alternatively can you make the cRIO write it to a memory stick within a USB port of the programming PC itself. Or can you write onto memory of cRIO but then how do you download the data?
Also I apologise that I posted the message twice only did cos I thought it might be in the wrong forum.
Thanks
Dan

Compact RIo's programming mode

Hi,
I'm working on Compact RIO 9022 including two chassis NI9403(Digital CHassis) and NI92205(Analog Chasis), and I want to konw if it is possibly to program my controler using scan Interface instead of scan engine. Because I find out that Scan Interface is dedicated for specific Modules as NI 9014 and NI 9073.
Thank you in advance for your answers
Best Regards
Nadia
Solved!
Go to Solution.

Hello Nadia,
Thank you for posting to the National Instruments Forum.
Can you tell us briefly what is your application?
Do you have an error occuring when you try to develop in Scan Mode?
Here are some information which can help you;
- cRIO Scan Mode
- Your Spec
- Choose you mode (P7)
Here's is a short extract:
Scan Interface mode enables you to use C Series modules directly from LabVIEW Real-Time. Modules that you use in Scan Interface mode appear directly under the chassis item in the Project Explorer
window and I/O channels appear as I/O variables under the modules. To use I/O variables, you drag and drop them to LabVIEW Real-Time VIs. In Scan Interface mode, you do not need to do any LabVIEW FPGA development or program communication between FPGA and Host VIs. You also do not need to wait for VIs to be compiled to the FPGA before deploying and running them. In Scan Interface mode , LabVIEW programs the FPGA on the CompactRIO target to work with the variables."
Keep us notified,
Kind regards.
Pierre_D
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
LabVIEW Tour
Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014

Module RT compact RIO + bug compilation

Hi,
I got a problem with my Labview program.
When I compile it, I had some bugs :
"variable shared 'RT compact RIO Target\...[name Folder]......\[varible name]' not in the project"
in french : "variable partagé"RT compact RIO Target\......[nom du dossier].......\[,om de la variable]' pas dans le projet"
I though, it was the module "RT compact RIO", which was unstall, but, I have no problem with my others Labview program.
Do you have an idea?
Thanks

Hello simaoniko,
It sounds like there are one or more Network-Published Shared Variables used in your VIs that aren't included in the project you are trying to deploy. Are you using shared variables? Did you copy this code from another project? If there are shared variable libraries in the project you're using, are they deployed to the host and/or target?
Regards,
Tom L.

Compact rio wireless

Hi experts,
We are currently using a Compact RIO as a data logger and controller on a university formula student car. Currently we connect the RIO to the car using the normal method of a CAT5 cross over cable when it is in the pits. We are endeavouring to have wireless contact with the RIO by implementing two ethernet bridges to act as a transparent cable replacement so that we can take data from the RIO as the car is moving.
2 Linksys WET11 bridges are being used and their connection is fine but when the PCis plugged into one and the RIO into the other the connection light comes on on the RIO but the 10/100Mbps communication active green light is not coming on. Are there any specific codes that need to be implemented on the RIO to carry out this type of communication?? Our current coding fully works with the crossover cable connection so this is becoming abit of a headache as to why the PC and RIO will not communicate. Have you ever heard of anyone succesfully connecting to the RIO over wireless LAN?
Thank you in advance

I have looked at the page that you have cited and carried out the instructions to the letter but our RIO still wont connect. We have been using a LInksys WET-11 Ethernet Adaptor and a SWEEX router. When the RIO is plugged into the Wi-Fi router and the Laptop into the Adaptor the system works fine. Due to the fact that we are using the RIO on a race car as a data logger we would much prefer the much lighter Adaptor to be what the RIO is direct wired to and to have the Laptop in the pits. But, when we set this configuration up the RIO will not talk to the adaptor. The orange LAN light comes on but the green network connection light by the LAN port will not. The PC can see the RIO ie a connection is present but no communication will take place between them in any programme. I was hoping someone else may have experienced this problem?? Is maybe our ethernet adaptor to dated?? Is b-technology limiting the RIO??
Thank you

Install more than one exe into one folder or into some subfolders of the same folder

Hi!
I want to do at least one of the following:
1. I want to install several exes (built with LV app builder) into one directory because they belong together.
2. Make several subfolders under the same top level folder aand install exes into each of them.
The (top level) folder should be the "company" folder. The subfolders are for the applications.
For example:
c:\company\app1\app1.exe
c:\company\app1\app1setup.exe
c:\company\app2\app2.exe
etc.
This may also reside under the "program files" folder.
If i try to do so, i encounter some problems setting up the build specifications. If i have more than one build spec. for exes i cannot add them to the same folder. At least if they contain the same external files, e.g. dlls.
If i try to make one installer per exe, i get an error message telling me that the same folder (my "top level folder") already exists in the registry and cannot be added a second time. This is also true if i try to make a new project instead of having several installer build specs in one project.
I use Labview 2009 (engl.) under Windows Vista (german).
If anyone has some help for me or encounters similar problems please let me know.
Holger
Message Edited by HolgerD on 09-26-2009 10:13 AM
Solved!
Go to Solution.

Hi Holger,
the build directories should be different for each build, but you can copy the executables into one folder manually (tested successfully in WinXP). For multiple installers, put each installer build in a separate directory, and install all to the same program files subfolder. Works with XP (tested!), so this must be a Vista issue...
Please build the four specs in attached project and run both installers to the same directory - should be working...
Best regards,
Sebastian
Attachments:
calc.dll.zip ‏73 KB

Compact RIO and LabVIEW run time

Dear All,
Good Morning.
We are developing a new experimental setup which will have different components, such as mass spectrometer, pressure transducers, valves and thermocouples, RTDs. We are currently having LabVIEW 8.6 Run time. We would like to control different components and acquire data using CompactRIO. I am not clear if compact RIO works with 8.5 run time. In the developers guide NI, mention about the real-time LabVIEW.
Thank you very much for help,
Zach

You need the Real-Time Toolkit (and possibly the FPGA toolkit, depending on your needs) to work with the cRIO. The version of LabVIEW installed on the cRIO must match the version you're using for programming on the PC (so you can't have LabVIEW 8.5 on the cRIO and 8.6 on your computer). The LabVIEW Real-Time is not the same as the LabVIEW Run-Time engine. The Run-Time engine lets you run compiled applications on your computer. The Real-Time toolkit lets you program real-time targets such as the CompactRIO.

Deploying exe into compact rio

Similar Messages

Maybe you are looking for