LabVIEW NXG Adapter Configuration Dialog Box

To launch the LabVIEW NXG Adapter Configuration dialog box, which contains Select Which LabVIEW NXG Server to Use and Adapter Settings sections, select Configure»Adapters , select the LabVIEW NXG Adapter in the list control, and click Configure .
Note If no LabVIEW NXG Runtime versions are installed, the LabVIEW NXG Adapter Configuration dialog box is disabled.

Selecting a LabVIEW NXG Server

The Select Which LabVIEW NXG Server to Use section contains the following options for specifying the server or engine the LabVIEW NXG Adapter uses:

  • LabVIEW NXG Run-time Engine —Selecting this option runs VIs in the same process as TestStand to provide optimal performance when calling VIs. To execute VIs in the LabVIEW NXG Runtime, the VIs should have been built into a GLL.
  • Active LabVIEW NXG Development System —To use LabVIEW NXG to create or edit VIs or to debug VIs TestStand calls, you must select this option so VIs execute in the supported LabVIEW NXG development environment. You must have the LabVIEW NXG development system installed on the same computer as TestStand to use this option.
Note TestStand supports calling VIs and GLLs created only in LabVIEW NXG 3.x.
Note If no LabVIEW NXG development system is present on the computer, but a compatible LabVIEW NXG Runtime Engine is installed, then the Runtime Engine option is automatically selected and all other options are disabled.

Adapter Settings

The Adapter Settings section contains the following options:

  • Automatically Build Missing or Outdated GLLs at Start of Execution —When enabled, TestStand validates that the GLL configured in a step matches the GLL path expected for the project and VI specified for the step. If the GLL path matches but it hasn't been built or the GLL present is stale (the binary doesn't match the code in the source files) at the time of execution, TestStand automatically triggers a build of the GLL before executing it. If the GLL doesn't match the expected GLL, TestStand returns an error.
    Note
    • TestStand must launch the LabVIEW NXG development system to perform the validations mentioned above and to build a GLL. By enabling this option, the LabVIEW NXG development system runs on the machine even though the LabVIEW NXG Adapter is set to use the LabVIEW NXG Run-time Engine.
    • To optimize the performance of deployed systems, NI recommends that GLLs are pre-built and this option is disabled. Building large components can take time and this slows down execution.
  • Validate GLL Path —When enabled, TestStand validates that the GLL path configured in the step matches the GLL path specified in the Build Output Directory of the specified component in LabVIEW NXG. The project, component, and target specified in the step are used to determine the expected GLL path. Enabling the Automatically Build Missing GLL option also enables the Validate the GLL Path option.
  • Disable Early Access Warning Dialog —Enable this option to prevent the Early Access Dialog from being displayed when using LabVIEW NXG steps.

See Also

Choose Code Template dialog box

LabVIEW NXG Module tab

Organizing LabVIEW NXG-Based TestStand Systems

Specify Module dialog box

TestStand Deployment Utility