|NI TestStand 2014 Help|
|NI TestStand 2014 SP1 Help|
|TestStand 2016 Help|
|TestStand 2016 SP1 Help|
|TestStand 2017 Help|
LabVIEW steps that invoke Express VIs or property nodes embed the configured VI in step properties as files that include the front panel, block diagram, and compiled code.
You can use the 32-bit LabVIEW development system and the 64-bit LabVIEW development system to execute steps with embedded VIs without modifying the sequence file because LabVIEW recompiles the embedded VIs at execution. If you use the LabVIEW Run-Time Engine (RTE) to execute steps, the bitness of TestStand must match the bitness of the LabVIEW development system that last configured or saved the embedded VI. In TestStand, select Tools»Update VI Calls to update Express VIs and property node calls to use the appropriate version of LabVIEW.
When you use the LabVIEW RTE to call a LabVIEW step configured with Express VIs or property node calls, you must provide separate step types that correspond to each version and bitness of LabVIEW you support. This restriction does not apply when you use the LabVIEW development system to call step types configured with Express VIs or property node calls because LabVIEW recompiles the embedded VI. Selecting Tools»Update VI Calls does not update step types. You can allow users to manually update the prototype to specify the version and bitness of LabVIEW to use, but this action causes the step type to change.