Switching between VIs and Packed Project Libraries

The LabVIEW Adapter allows you to easily switch the configuration of a step between executing a VI and executing a VI in a packed project library without having to modify the step. You can also configure the LabVIEW Adapter to automatically build a missing or out-of-date packed project library at the start of execution.

In previous versions of TestStand, after you build the packed project library in LabVIEW, you would have to modify the step to point to the VI in the packed project library. Now, if the step is configured to call a VI in the context of a project and the project has a build specification configured to build a packed project library containing that VI, you can choose to execute the VI in the packed project library instead of the VI.
  1. Set the following settings in the Override Module Settings window for a step calling a VI:
    1. Select the build specification for the VI.
    2. Set the path of the VI in the packed project library.
    3. Optional: Set the path of the project to use when executing the VI in the packed project library.
  2. Enable the Always run VI in Packed Project Library option in the LabVIEW Adapter Configuration dialog box or step settings.
    Note Enabling Always run VI in Packed Project Library in the LabVIEW Adapter Configuration dialog box overrides the module settings for all LabVIEW steps and always run the VI in the packed project library. You must configure the VI settings in the Override Module Settings window to yse this option.
    Note
    The LabVIEW Adapter will automatically run the VI in the packed project library and project configured in the Override Module Settings window instead of the VI and project configured in the step.
  3. If LabVIEW Development System is installed, you can enable automatically building the packed project library at the start of execution by enabling the Automatically Build Packed Project Libraries at the Start of Execution option in the LabVIEW Adapter Configuration dialog box.