TestStand Deployment Utility supports deploying sequence files which call LabVIEW NXG code modules. LabVIEW NXG steps can be configured in the following ways:

  • Project and GLL are Both Specified— These steps can execute using the LabVIEW NXG development system to execute the VI directly, or using the LabVIEW NXG Run-Time Engine to execute the VI within the GLL. In this case, TestStand enforces that the specified GLL must match the GLL output configured in the project and component in LabVIEW NXG. When deploying these types of steps, TestStand Deployment Utility automatically regenerates the GLL from the project before deploying to ensure that the latest code is used.
  • GLL Specified, Project Not Specified— These steps must be executed using the LabVIEW NXG Run-Time Engine to execute the VIs built into the GLL. When deploying these types of steps, the GLL file is deployed as-is because no source files are present to rebuild it.
  • Project Specified, GLL Not Specified— These steps can execute using the LabVIEW NXG Development System to execute the VI directly. Deployment is not supported for these steps by TestStand Deployment Utility. An error is generated indicating that a GLL is required.
Note If a LabVIEW NXG file is included in a deployment but not referenced by the sequence file, TestStand Deployment Utility will not process the file and will include it as-is.

Configuring LabVIEW NXG Files

After analyzing a sequence with LabVIEW NXG code modules, the referenced GLLs are displayed in the distributed files tab. You can configure the destination for the GLL file. Like other code module types, TestStand Deployment Utility ensures that the sequence file is updated to reference the correct files if the files are deployed within the same base destination as the calling sequence file.

To include LabVIEW NXG source files in the deployment, click LabVIEW options, and select the LabVIEW NXG options tab. Enable the Include LabVIEW NXG Source Files option. With this option selected, LabVIEW NXG projects, components, and VIs will also be displayed in the distributed files tab. Only referenced files are displayed in the distributed files tab, but all files included in the project will be included in the deployment. You can configure the destination for the source project, but not for contained components and VIs; these files will be deployed to a location relative to the project.

Deploying the LabVIEW NXG Run-Time Engine in an MSI-based Installer

Because the LabVIEW NXG Run-Time Engine is a NI package it is not directly available as a dependency in an MSI-based installer. However, if you enable the Automatically Include Required Installers option in the Drivers and Components dialog, TestStand Deployment Utility will include the Run-Time Engine package within the installer folder. When the installer is executed, it will invoke NI Package Manager to install the Run-Time Engine package.