TestStand Sequence File Breaks LabVIEW VI Link When Used on a Different PC

Issue Details

When using a TestStand sequence file created on one PC in another PC environment (both running LabVIEW 2019 and TestStand 2019 with Debug Deployment Environment License), the LabVIEW VI links in the sequence file are broken. How can I ensure that VI paths are preserved across different development and deployment environments?

Solution

To ensure that LabVIEW VI references in TestStand sequence files remain valid across different PCs, you should configure the VI calls using relative paths and adjust the search directory settings in TestStand. This helps maintain portability and avoids broken links.

Recommended Steps:

1. Use Relative Paths for VI References:

   • In the LabVIEW step configuration within TestStand, when selecting a VI, choose the option: “Use a relative path for the file you selected”
      
   • This stores the VI path relative to the sequence file location, making it portable across systems.

2. Enable Subdirectory Search:

   • Navigate to Configure > Search Directories in TestStand.
   • In the Current Sequence File Directory entry, enable: “Search Subdirectories”
      
     
   • This allows TestStand to locate VIs even if they are stored in subfolders under the sequence file directory.