Debugging and Tracing of VIs Executed Using the LabVIEW Runtime

NI TestStand 2014 SP1 Help

Edition Date: August 2015

Part Number: 370052P-01

»View Product Info
Download Help (Windows Only)

Using the LabVIEW Development System, you can debug VIs that execute using the LabVIEW Runtime in the TestStand Sequence Editor. Using the LabVIEW Desktop Execution Trace Toolkit (DETT), you can trace and capture events for VIs executed using the LabVIEW Runtime in the TestStand Sequence Editor and the TestStand User Interfaces on the local machine.

The LabVIEW Development System that debugs a VI code module must match the version and bitness of the LabVIEW Runtime that executed the VI code module. In LabVIEW, you can configure breakpoints and probes on diagrams to debug VIs that TestStand executes using the LabVIEW Runtime.

Using the DETT, you can capture and trace events, such as the order of VI execution, thread IDs, reference leaks, timing details, and user-defined trace information. Trace and event information can be helpful when diagnosing complex threading issues, identifying performance bottlenecks, and debugging other complex problems.

To enable debugging and tracing in TestStand, use the Enable Debugging and Tracing option in the LabVIEW Adapter Configuration dialog box.

Notes Notes
  • Changes to the Enable Debugging and Tracing setting will not take effect until you restart a TestStand application.
  • LabVIEW 2015 or later is required to debug and trace VIs executed in the LabVIEW Runtime.
  • DETT 2015 or later is required to trace VIs executed in the LabVIEW Runtime.

WAS THIS ARTICLE HELPFUL?

Not Helpful