If you have a LabVIEW executable file, but do not have the LabVIEW Development Environment nor the
Real-Time and
FPGA modules, you can still deploy your startup executable to PharLap, VxWorks, and Linux targets through one of the available solutions below.
- Using identical hardware. It is possible to deploy the executable on a duplicate image via the Replication and Deployment (RAD) Utility. If you need to deploy to a Linux Real-Time target outside of the LabVIEW Development environment, this is the recommended method. Instructions for how to install and use RAD are included in the previous link.
- If the executable has been compiled for the correct target. You can FTP the file onto your real-time controller:
- Place the executable in the
c:\ni-rt\startup\ directory. - Set the following two settings in the
NI-RT.ini file or lvrt.conf file on the target. The NI-RT.ini file is located in the root directory of the target, at c:\ni-rt.ini for PharLap/VxWorks targets. For Linux targets, you will need to use the lvrt.conf file, which is located at etc/natinst/share/lvrt.conf.
RTTarget.ApplicationPath=c:\ni-rt\startup\startup.rtexeRTTarget.LaunchAppAtBoot=True where
startup.rtexe is the name of your executable file.
Additional Information
While this method works, the recommended method for deploying a LabVIEW Real-Time startup executable is to
do so through the LabVIEW Project .
The reason you have to modify the
NI-RT.ini or
lvrt.conf file settings is that when you deploy the executable to the real-time controller using the LabVIEW Project Explorer, LabVIEW sets the two flags automatically. Therefore, if you are transferring the start-up executable to the controller via FTP, then you need to set these two flags manually.