The LabVIEW 2017 runtime does not allow the loading of VIs, PPLs, or DLLs saved in LabVIEW 2016 or earlier, even if Version Independent Runtime Engine support is enabled.When Version Independent Runtime Engine support is enabled, and you are using LabVIEW 2018 or later runtimes and loading files saved in LabVIEW 2017 or later, this restriction no longer applies. When Version Independent Runtime Engine support is disabled, the version of the VI called in TestStand, and all its dependencies, must match the version of the runtime being used to load or run the VI.
TestStand can load and execute LabVIEW files saved in LabVIEW 2017 or later in a later version of the LabVIEW runtime.įor example, if a TestStand sequence calls LabVIEW code modules saved in LabVIEW 2017 and Version Independent Runtime Engine support is enabled, then these LabVIEW files will be loaded and executed in the LabVIEW 2018 Runtime Engine. When you enable this adapter option, Version Independent Runtime Engine support is enabled for all instances of LabVIEW runtimes, version 2017 or later, that are used by the TestStand application. Note Changes to this option do not take effect until you restart the TestStand application. TestStand allows users to enable or disable this feature in LabVIEW using the Enable Version Independent Runtime Engine LabVIEW Adapter option. LabVIEW enables these options by default for PPL build specifications you create in LabVIEW 2017 and later.ĭisabling the option binds a PPL build specification to a specific version of LabVIEW, prevents any changes to the performance profiles, and helps you avoid unexpected problems resulting from compiler upgrades.įor more information about this feature in LabVIEW, refer to the LabVIEW Help. PPL build specifications in LabVIEW also have an option to specify whether the build output subscribes to this feature. Enabling this feature in TestStand reduces the number of LabVIEW runtime engines that would have to be loaded into the TestStand process to execute LabVIEW code modules. TestStand 2016 SP1 supports this feature in the LabVIEW Adapter. Version Independent Runtime Engine support was introduced in LabVIEW 2017 and allows the LabVIEW runtime to load source files, such as VIs and projects, and build outputs, such as packed project libraries (PPLs), DLLs, and executables that were saved or built in an older version of LabVIEW.įor example, a PPL built in LabVIEW 2017 can now be loaded and executed by the LabVIEW 2018 runtime.