Running a LabVIEW Application on a Windows cDAQ Controller

Issue Details

• How do I run a LabVIEW program on my cDAQ controller using Windows?
• How can I deploy code onto my cDAQ controller with an embedded operating system?

Solution

A cDAQ controller behaves like a normal computer. You can run a LabVIEW application on the cDAQ controller by either creating and deploying an executable, or by developing the LabVIEW code directly on the controller.

See below for further details on each method.

Creating an Executable:

Create an executable (if you have LabVIEW Professional or Application Builder) and run it on the cDAQ controller with the LabVIEW Run-Time Engine.

• You can do this by moving the executable onto the cDAQ controller.
• If the controller has the LabVIEW Run-Time Engine installed, you can open and run the executable.

Developing Code on the Controller:

 Install LabVIEW and NI-DAQmx on the cDAQ controller, and run your LabVIEW program on there.

• We do not recommend developing LabVIEW code on the controller itself due to memory limitations. However, this remains an available option.

Note: If installing the development system is necessary, consider that new versions of LabVIEW and DAQmx require more space than older versions. Therefore, if you are using a 16GB cDAQ cotroller, there is not enough space for newer versions of LabVIEW and DAQmx. These controllers can only install the Run-Time Engine, or older versions of LabVIEW and DAQmx, such as version 15.0.
 

Additional Information

• To create an NI-DAQmx application in LabVIEW, you can follow this tutorial: Creating an NI-DAQmx Application Installer with LabVIEW .
• If the application is not working as expected on the cDAQ controller, look at the following document: Troubleshooting LabVIEW Stand-Alone Applications (Executables) 
• If your cDAQ controller does not install the NI-DAQmx Run-Time Engine or application correctly, check that the development computer or the USB media you used to transfer the files does not have any encrypting protocol that affects the files.
  • For example, if you see a Command Prompt showing up and disappearing immediately when you run the application or the NI-DAQmx Run-Time Engine and nothing happens, this could be the cause.