Organizing Test Program Files with LabVIEW Project Libraries

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

LabVIEW project libraries (.lvlib) are collections of VIs, type definitions, shared variables, palette menu files, and other files, including other project libraries.

In TestStand, you can call public VIs in a project library, but you cannot call private VIs. To call a VI in a project library, you must specify the path to the VI file. TestStand does not use qualified paths that include the project file name and VI name.

Using project libraries in TestStand includes the following advantages:

  • You can avoid potential VI name collisions when you deploy multiple test systems to the same test station computer. Project libraries change the filenames of VIs they reference to a compound, qualified name that includes the project library filename so you can reference VIs with the same filename from different project libraries.

    For example, the Library.lvlib project library changes the filename of the test.vi it references to Library.lvlib:test.vi, and the LibraryTwo.lvlib project library changes the filename of the test.vi it references to LibraryTwo.lvlib:test.vi. When you reference a project library that another project library contains, the qualified name concatenates the parent project library name with the name of the project library it contains, such as ParentLibrary.lvlib:ReferencedLibrary.lvlib.
  • You can enforce security settings, such as limiting public access to certain files or limiting editing permission for a collection of files to prevent calling support VIs the project library references or calling VIs the project library does not reference.
  • You can organize files into a single hierarchy of items. When you reference a VI a project library references, LabVIEW also automatically references all the VIs in the project library. Similarly, when you load a VI a project library references, LabVIEW automatically loads the project library as well.

The project library must exist on the computer for TestStand or LabVIEW to execute a VI the project library references. If the project library is not available, LabVIEW breaks the VI to prevent it from running.

Refer to the LabVIEW Help for more information about project libraries.


See Also

Deploying Multiple Test Systems to the Same Test Station

Deploying TestStand Systems

LabVIEW Adapter

LabVIEW Help

WAS THIS ARTICLE HELPFUL?

Not Helpful