LabWindows/CVI Adapter Configuration Dialog Box
Select Configure»Adapters, select the LabWindows Adapter in the list control, and click Configure to launch the LabWindows/CVI Adapter Configuration dialog box.
The LabWindows/CVI Adapter Configuration dialog box contains the following options:
- Show Function Arguments in Step Description—When enabled, the description for a step displays the function and its parameters. When you disable the option, the description displays the function and module name.
- Default Struct Packing—Specifies how the LabWindows/CVI Adapter packs structure parameters it passes. Set the packing options to match the default for structure packing in the application development environment. The following options are available: 1-, 2-, 4-, 8-, and 16-byte boundaries.
Note The development environment you use to create DLLs determines the choice for the structure value packing value, as follows: - For LabWindows/CVI, the default packing can be either 1- or 8-byte, depending on the compatibility mode. For example, in Visual C++ compatibility mode, LabWindows/CVI has a default of 8-byte packing.
- Visual C++ and Symantec C++ have a default of 8-byte packing.
- LabVIEW, Borland C++, and Watcom C++ have a default of 1-byte packing.
The Step Execution section allows you to specify in-process or out-of process for the LabWindows/CVI Adapter. When the adapter runs steps in-process, it executes in the same process as the sequence editor or user interface you are running. When the LabWindows/CVI Adapter runs steps out-of-process, it executes them in an external instance of the LabWindows/CVI development environment.
The LabWindows/CVI Adapter uses two different copies of the LabWindows/CVI development environment. The adapter uses one copy to execute code modules for out-of-process step execution. By default, the adapter opens <TestStand>\AdapterSupport\CVI\tscvirun.prj in this copy of LabWindows/CVI. Use this copy of LabWindows/CVI to edit the projects you use to create DLLs, static libraries, and object files.
This section contains the following options:
- Execute Steps in an External Instance of CVI—Specifies which project the LabWindows/CVI Adapter uses to run code modules.
- Pathname of the CVI Project Containing the Execution Server—The pathname of the LabWindows/CVI project file the LabWindows/CVI Adapter uses to run steps out-of-process.
- Execute Step In-Process (CVI is NOT Required for This Mode)—This is the fastest mode for running steps. However, you cannot debug .c files in this mode. For a .c file, TestStand locates the corresponding .obj file and uses it in the place of the .c file.
You can debug DLLs in this mode if you launch this application from the DLL development environment. Refer to the NI LabWindows/CVI Help for more information.
- Configure Auto-Loading of Support Libraries Needed for Linking .objs and .libs—Configures a list of support libraries for the LabWindows/CVI Adapter to load when executing object and library code modules. Clicking this button launches the Auto-Load Library Configuration dialog box.
- Code Template Policy—The templates to use during code creation. The following options are available:
- Allow Only New Templates—Only searches for new code templates.
- Allow Only Legacy Templates—Only searches for legacy code templates.
- Allow New and Legacy Templates—Searches for both new and legacy templates.
See Also
Auto-Load Library Configuration Dialog Box