Executing Source-Only VIs in LabVIEW Runtime Engine
- Updated2025-07-23
- 2 minute(s) read
Executing Source-Only VIs in LabVIEW Runtime Engine
Use the Version Independent Runtime Engine Support feature in the LabVIEW Adapter as an option to avoid potential issues when executing source-only VIs using the LabVIEW Runtime Engine through the LabVIEW adapter. These issues can occur if the LabVIEW version the source-only VI was saved or mass-compiled in does not match the LabVIEW Runtime engine version, as VI version no longer gets updated during a save or mass-compile.
-
Option 1: Disable the Save version
feature in LabVIEW, and re-save your VIs.
- Close TestStand.
- Open LabVIEW, navigate to , and disable the Maintain the Save Version of Loaded Projects by Default feature.
-
Clear the compiled object cache in LabVIEW by navigating to .
Note If you have files copied to user.lib or instr.lib, delete the .vidb cache file located at <LabVIEW Install Directory>\VIObjCache\<version>\objFileDB.vidb.
- Set the save version of your LabVIEW projects to Editor Version in the project properties.
- Delete any .lvversion files you created in your project folders.
- Mass-compile your LabVIEW files.
-
Option 2: Use the Version Independent Runtime Engine
Support feature in TestStand.
- In TestStand, Enable the Enable Version Independent Runtime Engine option in the LabVIEW Adapter Configuration dialog box.
- Set the LabVIEW Runtime Version control to match the version of LabVIEW that you used to save or mass-compile your VIs.
- Restart TestStand.
- Option 3: If your files do not need to be source-only, disable the Separate compiled code from source file setting for your VI, project, library, or entire environment in LabVIEW.
Related Information
- Saving for a Previous Version
- Build Source Files and Execute
The Build Source Files and Execute feature supports executing source-only VIs in TestStand using the LabVIEW adapter when it is configured to use the LabVIEW runtime engine.
- Version Independent Run-Time Engine Support
- Separating Compiled Code From VIs and Other File Types