此內容不適用於您所偏好的語言。

此內容已顯示為其他適用語言。 您的瀏覽器可能含有可協助翻譯的套件。

Enabling Desktop Execution Trace Toolkit to Remotely Debug a LabVIEW Executable

Updated Mar 21, 2024

Environment

Software

  • LabVIEW Desktop Execution Trace Toolkit
  • LabVIEW

The present article will guide you through the process of configuring the LabVIEW Development Environment and a Build Executable so the LabVIEW Desktop Execution Trace Toolkit (DETT) can connect to the executable for further debugging and code analysis. 

This article assumes that you have knowledge regarding the usage of the LabVIEW Desktop Execution Trace Toolkit (DETT), if you are not familiar with the tool visit the following link:

The procedure for connecting the LabVIEW Desktop Execution Trace Toolkit (DETT) to an executable for debugging consists of 3 subprocedures: 
  • Enable VI server on LabVIEW Development Environment
  • Enable Debugging in your LabVIEW project's Build Specification.
  • Enable VI server access for your LabVIEW project.

Enable VI server on LabVIEW Development Environment

The process of enabling the VI Server on the LabVIEW Development Environment is detailed in the following article Enable VI server on LabVIEW Development Environment, this procedure is required not only when debugging executables but also when connecting the DETT to LabVIEW applications running in the development environment. 
 

Enable Debugging in your LabVIEW project's Build Specification.

To enable debugging in your executable follow the procedure of the following article: Remotely Debugging Executables in LabVIEW. You will notice the article also explains the debugging process once the executable is moved to the target machine. This procedure is not required for the DETT integration.

Enable VI server access for your LabVIEW project.

To enable VI server access follow these steps:
  1. Open your LabVIEW project.
  2. In LabVIEW's Project Explorer, perform a right-click on My Computer and open Properties.
  1. Go to the VI Server tab, enable TCP/IP and define a Port number (in this example 3364):
  1. Scroll down and add the IP address of the PC you want to execute DETT on to the Machine Access list. This can be the same PC as your application will be execute on, or a remote PC.
  1. Build your application.
  2. Completely close the LabVIEW Development Environment. If you leave LabVIEW open, it keeps the TCP/IP port you specified for your project in step 3 reserved, not allowing your compiled application to use it.
  3. Launch your application.
Once you have completed these required procedures, test the connection, Open Desktop Execution Trace Toolkit, and connect to your compiled application by following the next steps:
1. Enter the IP address of the machine that the executable is running on in the Machine field
2. Enter the port number you specified earlier in the Port field,
3. Click the Refresh icon,
4. After selecting the executable's name from the Application Instance drop-down menu.
 
​​​


Additional Considerations

  • In the steps above, changing the VI server settings was achieved by right-clicking My Computer. A similar setting for applications executed inside the LabVIEW Development Environment can be changed in menu Tools » Options » VI Server. DETT needs to use the port set in the above described steps in order to connect to the executable.
  • The VI Server settings are stored in the configuration file that gets created along with the executable. Make sure you add the corresponding settings if you are using a custom configuration file included in the Advanced category of your application build specifications.