LabVIEW VI Options Dialog Box

TestStand 2017 Help

Edition Date: November 2017

Part Number: 370052W-01

»View Product Info

Download Help (Windows Only)
NI TestStand 2014 Help
NI TestStand 2014 SP1 Help
TestStand 2016 Help
TestStand 2016 SP1 Help
TestStand 2017 Help

Launch the TestStand Deployment Utility and select LabVIEW Options on the Distributed Files tab to launch the LabVIEW VI Options dialog box.

The LabVIEW VI Options dialog box contains the following options:

LabVIEW Options Tab

  • General LabVIEW VI Options
    • Remove Block Diagrams—When you enable this option, the deployment utility removes the block diagrams of VIs in the deployment to prevent users from viewing and editing the block diagrams. If you enable this option, you cannot also enable the Apply New Password option. You can remove block diagrams for VIs that are part of XControls.
    • Apply New Password—Enable this control to lock VIs to prevent editing. Applying a password is incompatible with removing VI diagrams. This option is disabled when you enable the Remove VI Diagrams option.
    • Password—Launches a dialog box in which you can set the password to apply. VIs that already have a password retain their original password. When you lock VIs with a password, you cannot edit them without entering the password.
    • Check for Broken VIs—When you enable this option, the deployment utility checks for broken VIs during analysis and after building the deployable image. This option is disabled by default to improve performance. Enable this option when you want to debug VI errors.
      Notes Notes
      • When you deselect a sequence file in the Distributed Files control of the Distributed Files tab to exclude the sequence file from the deployment, the VIs the sequence file calls remain in the deployment. The deployment utility does not confirm whether the VIs are broken during analysis. However, the deployment utility always checks all VIs in a TestStand project during an analysis to determine whether the VIs are broken after a build.
      • The deployment utility attempts to find all the dependencies of VIs before it checks for broken VIs. If the utility does not find one or more dependencies of the VIs, the utility reports those dependencies as missing and does not check for broken VIs, even when the Check for Broken VIs option is enabled. National Instruments recommends that before you attempt to deploy again after finding missing VIs, you mass compile the VIs or run the TestStand Sequence Analyzer to identify possible issues with the deployment.
    • SubVI Location (end path with .LLB to place files in a VI library)—The location to save subVIs. This location must be a relative path.

      If the specified path uses the .llb extension, the location is a LabVIEW VI library. Otherwise, the location is a directory.
  • Packed Project Library Options
    • Output VIs to Packed Project Library—When you enable this option, the deployment utility builds a LabVIEW packed project library for the VIs you deploy.
      • Enable Debugging—When you enable this option, the deployment utility builds a LabVIEW packed project library with debugging information.
    • Options—Launches the Packed Project Library Options dialog box, in which you can configure options for how the deployment utility builds LabVIEW packed project libraries, such as the base library name, versioning information, descriptive information about the build, and source file options.
    • Copy files from vi.lib before build—Ensures that a copy of all dependencies in vi.lib are copied into the source distribution, which TestStand Deployment Utility uses to build the Packed Library.
    • Copy files from user.lib before build—Ensures that a copy of all dependencies in user.lib are copied into the source distribution, which TestStand Deployment Utility uses to build the Packed Library.
    • Copy files from instr.lib before build—Ensures that a copy of all dependencies in instr.lib are copied into the source distribution, which TestStand Deployment Utility uses to build the Packed Library.
  • Exclusions—Contains the following options for excluding certain files from the deployment:
    • Exclude Files from VI lib—Excludes all files in the vi.lib directory from the deployment.
    • Exclude Files from User lib—Excludes all files in the user.lib directory from the deployment.
    • Exclude Files from Instr lib—Excludes all files in the instr.lib directory from the deployment.
    • Remove unused members of project libraries—Removes unused project library members during the build process. If you enable this option, LabVIEW includes only VIs from the library you call directly from the block diagram. Enabling this option reduces the application size, since LabVIEW does not include the other VIs referenced by the same project library unless the VIs are referenced by other VIs that are included in the deployment.
    • Modify project library file after removing unused members—If you remove unused members of the project library, enable this option to direct LabVIEW to modify the library so that the library file does not refer to the removed members. If you do not modify the project library, the deployment may take longer to build.
    • Exclude Dependent Shared Libraries (LabVIEW 2014 and Later)—Reduces the overall number of files in a deployment. Enabling this option limits the number of shared libraries that LabVIEW copies. When you create a deployment and then link to a file in that deployment from another deployment, LabVIEW traditionally copies the linked file. When this option is enabled, LabVIEW retains the links relative to the original files instead of copying the files during the build.
    • Exclude Dependent Packed Libraries (LabVIEW 2014 and Later)—When you enable this option, LabVIEW excludes copies of dependent packed project libraries to which you link from other deployments. To exclude dependent packed project library files, LabVIEW retains the links relative to the original dependent packed project libraries instead of copying those files during the build. For example, if you create a deployment and then a subsequent deployment, you can relatively link the subsequent deployment to a file in the first deployment. If you leave this option disabled, LabVIEW copies the dependent packed library file to which you linked instead of retaining the relative link to that file.
  • Optimizations—Contains the following options for optimizing files in the deployment:
    • Remove Unused VI Components—Removes unused polymorphic VI instances code modules reference. This option does not remove any files that are directly referenced in a sequence or workspace project.
      Note Note  Enabling the Remove Unused VI Components option disables certain editing and debugging options, such as wiring a new type to a polymorphic VI or making type changes across several VIs by editing a type definition.
    • Consolidate Files Shared By Projects—When you enable this option, the deployment utility consolidates all files in LabVIEW projects into a single, merged project. This consolidation increases build speed and decreases disk usage for multiple projects that share common subVIs by making a single source distribution for every project. This optimization is not always possible because two projects might compile the same source VI differently, which can result in slower build times.

      If the deployment utility cannot consolidate all projects, the utility returns a warning that explains why consolidation is not possible and builds the distribution without consolidating the projects.

      When you disable this option, the deployment utility builds one LabVIEW source distribution for each LabVIEW project. If multiple LabVIEW projects share files, the deployment utility includes multiple copies of the shared files.
    • Enable SSE2 Optimizations—When you enable this option, the deployment utility uses SSE2 optimizations to compile VIs, which can improve execution speed. This option is enabled by default. Do not enable this option if you are using processors that do not support the SSE2 instruction set. Refer to the LabVIEW Help for more information about which processors and National Instruments devices support SSE2.

LabVIEW NXG Options Tab

  • General LabVIEW NXG VI Options
    • Include LabVIEW NXG Source Files—When you enable this option, the LabVIEW NXG projects referenced by your sequence files are included in the deployment. All source files referenced by the projects are included. Enable this option if you want to view or edit LabVIEW NXG source code on a deployment target. If this option is disabled, only GLL files referenced by sequence files are included in the deployment. After changing this setting, click Ananlyze Source Files to update the included files.

See Also

Deploying TestStand Systems

Effectively Using LabVIEW with TestStand

TestStand Deployment Utility

WAS THIS ARTICLE HELPFUL?

Not Helpful