Troubleshooting LabVIEW Stand-Alone Applications (Executables)

Updated Sep 19, 2019

Reported In

Hardware

  • Multifunction I/O Device
  • USB-6351

Software

  • LabVIEW
  • LabVIEW Application Builder Module

Driver

  • NI-DAQmx
  • NI-VISA
  • NI-488.2

Issue Details

  • I built a LabVIEW application and the behavior is not the same as in the development environment. The executbale does not show any error, but it does not work correctly.
  • I built an executable in LabVIEW and I have deployed it on multiple machines. The application is not working as expected.

Solution

When deploying a LabVIEW executable consider the following aspects:
  • You must install the same LabVIEW Run-Time Engine version used to develop the application on the deployment environment, as well as any driver such as NI-DAQmx, NI-VISA, NI-488.2, among others used by the application in the development environment. In the article Distributing Applications with the LabVIEW Application Builder, you will find information about deploying LabVIEW executables and the requirements for it to properly work.
  • If after verifying that the proper software is already installed in deployment environment the application does not work as expected, you can re-build the executable in the LabVIEW Application Builder and check the Enable debugging option in the Advanced menu. This option will allow you to remotely debug the application deployed on the target from the developer machine using the debugging tools. For information about how to configure the LabVIEW executable with debugging enabled and how to remotely access the application follow the steps in Remotely Debugging Executables in LabVIEW.
  • Ensure that you have proper error handling in your program- especially with DAQmx Tasks. Simple error handling implementations such as linking error wires during data flow, ending loops with error wires, and ending your VI with a SimpleErrorHandler.vi normally are all that are needed to determine troublesome VI's during deployment. Use Highlight Execution on the development computer to determine where the VI is failing.
  • If your device name comes from a string data type, use the Type Cast function to change the data type. Also make sure that the device name is correct as explained in this document: NI-DAQmx Syntax for Specifying Physical Channel Settings.

Additional Information

Some modules require a specific Run-Time Engine to be installed in the deployment machine to work as in the development environment, such as the Vision Deployment Module which requires the Vision Run-Time Engine to be installed and activated in the deployment machine.
 

WAS THIS ARTICLE HELPFUL?

Not Helpful