To get to the configuration dialog, select the TestStand menu options Configure ➔ Adapters...
The LabVIEW Runtime Engine behaves differently from the Development System on several occasions that apply to TestStand as well.One example is the Application Path-VI. When used in LabVIEW test step executed by the LabVIEW Development System, it will return the path to the folder containing the VI. When the LabVIEW Runtime Engine is used, it will return the path to the Caller Executable in the TestStand Application directory, i.e. C:\Program Files (x86)\National Instruments\TestStand 2019\Bin. Similar behavior applies when compiled LabVIEW code is called.This will lead to invalid paths when external resources are referenced.To amend the issue, please adapt your LabVIEW code to behave consistently. In the case of the Application Path, consider replacing the Application Path-VI with a String-Control that gets its path-string passed from TestStand. Alternatively, replace the Application Path-VI with the Path-Property of the calling This VI object.Observe the different paths returned when the VI is called using the LabVIEW Runtime or Development adapter. The example VI below and a TestStand sequence are included in the files section.
Please compare the results of the attached demo TestStand sequence TS_LV_Path_Demo_TS2019_32b.seq for further clarification.The Path_Demo.vi called by the TestStand sequence returns the currently used LabVIEW Adapter and paths generated by multiple methods:
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.