LabVIEW Executable Gives Unexpected Data on Deployment Machine

Updated Apr 24, 2018

Reported In

Software

  • LabVIEW
  • LabVIEW Application Builder Module

Issue Details

I developed a VI in LabVIEW, which works correctly on the development environment.

I then built the executable and installed it on a target/deployment PC (together with the proper version of LabVIEW Run-Time Engine).

However, when I run the executable on the target PC it doesn't work as expected: no error is returned, some data are correctly updated but other indicators are not updated.

How can I fix this problem?
 

Solution

In order to understand the origin of the malfunction of the executable on the target PC, you can enable debugging  for you executable: in this way, you will be able to remotely debug the executable from the development PC and use standard LabVIEW debugging techniques (such as probes, execution highlighting etc) to find if output data are correctly updated and connected to the not-working indicators.

To enable debugging in your application, you should:
  1. right-click the Application Build Specification in the LabVIEW project and select Properties
  2. select Advanced category
  3. check Enable debugging option
  4. build the application again
  5. run the application on the target PC
If debugging allows you to find the origin of the problem, you can edit the source code of the VI on the development PC and build the updated executable.


 

Additional Information

When you fix the problem in the application and test it intensively on the target PC, you should disable Enable debugging option and build the executable again: since enabling debugging retains the block diagrams of the VIs in the build, the executable size tends to be higher if debugging is enabled. Also, disabling debugging improves execution speed by ensuring that LabVIEW uses full compiler optimizations.
 

WAS THIS ARTICLE HELPFUL?

Not Helpful