The LabVIEW Desktop Execution Trace Toolkit (DETT) is a tool that collects various types of trace data from LabVIEW applications. Refer to the LabVIEW Desktop Execution Trace Toolkit Help and the Opening a Trace Connection topic in the LabVIEW Help for more information about using the DETT.

Note Tracing VI execution using the DETT can have a performance impact on the execution of code module VIs. To minimize the performance impact, connect the DETT as close as possible to the section of code you want to trace.

Configuring the DETT

When you enable debugging and tracing in TestStand, TestStand configures each LabVIEW Runtime loaded by TestStand to open a unique TCP port. Refer to the TCP Ports for the LabVIEW Runtimes topic for more information about TCP ports used.

Complete the following steps to trace and capture events for VIs executed using the LabVIEW Runtime in a TestStand application:

  1. Ensure that the Enable Debugging and Tracing option in the LabVIEW Adapter Configuration dialog box is enabled and restart the TestStand Sequence Editor or User Interface if required.
  2. Execute your test sequence to ensure all LabVIEW Runtimes and VI code modules are loaded.
    Note The DETT can only connect to the TestStand Sequence Editor or a User Interface after TestStand loads a supported LabVIEW Runtime. Determine the appropriate port for the runtime you want to trace. Refer to the TCP Ports for the LabVIEW Runtimes topic for more information.
  3. In the DETT:
    1. Set the Machine text box in the toolbar to localhost, then set the Port text box to the port number for the LabVIEW Runtime you want to trace.
    2. Refresh the Application Instance drop-down menu to see the context for the TestStand application.
    3. Click the Start button in the DETT to begin a trace session.
Note
  • You can only trace one LabVIEW execution/project context at a time.
  • The DETT can connect and generate trace and event information for the TestStand Sequence Editor and User Interfaces. The DETT cannot connect to a TestStand application until TestStand loads a supported LabVIEW Runtime.

Tracing VIs executing in different LabVIEW projects

If you have a sequence file that executes VIs in one or more project contexts, you must connect to the specific project context you want to trace from the Application Instance drop-down menu.