Organization of LabVIEW

Organization of the LabVIEW Directory Structure

Learn about the LabVIEW file system on Windows, macOS, and Linux. LabVIEW installs driver software for GPIB, DAQ, VISA, IVI, Motion Control, and IMAQ hardware depending on platform availability.

The LabVIEW directory installs in the following location depending on your operating system:

Windows (32-bit)—C:\Program Files (x86)\National Instruments\LabVIEW <VERSION>

Windows (64-bit)—C:\Program Files\National Instruments\LabVIEW <VERSION>

Linux—/usr/local/natinst/LabVIEW-<VERSION>-64

macOS—/Applications/National Instruments/LabVIEW <VERSION> 64-bit

After you complete installation, the LabVIEW directory contains the following groupings.

Libraries

user.lib—Directory in which you can save controls and VIs you create. LabVIEW displays controls on User Controls palettes and VIs on User Libraries palettes. This directory does not change if you upgrade or uninstall LabVIEW.

vi.lib—Contains libraries of built-in VIs, which LabVIEW displays in related groups on the Functions palette. Do not save files in the vi.lib directory because LabVIEW overwrites these files when you upgrade or reinstall.

instr.lib—Contains instrument drivers used to control PXI, VXI, GPIB, serial, and computer-based instruments. When you install NI instrument drivers and place them in this directory, LabVIEW adds them to the Instrument Drivers palette.

Structure and Support

menus—Contains files LabVIEW uses to configure the structure of the Controls and Functions palettes.

resource—Contains additional support files for the LabVIEW application. Do not save files into this directory because LabVIEW overwrites these files when you upgrade or reinstall.

project—Contains files that become items on the LabVIEW Tools menu.

ProjectTemplates—Contains starting points for common LabVIEW design patterns that you customize with the Create Project dialog box.

templates—Contains templates for common VIs.

wizard—Contains files that become items on the LabVIEW File menu.

www—Location of HTML files you can access through the Web Server.

Learning and Instruction

• examples —Contains example VIs. Select Help » Find Examples to browse or search the examples.
• help —contains files that become items on the LabVIEW Help menu.

Suggested Location for Saving Files

LabVIEW installs the vi.lib and the resource directories for LabVIEW system purposes only. Do not save your files in these directories.

You can save your files in the following directories:

user.lib—Any controls or VIs you want to display on the User Controls or User Libraries palettes.

Note Save subVIs in the user.lib directory only if they are usable, without modification, across projects. Paths to VIs in user.lib are relative to the labview directory. Paths to subVIs you save elsewhere are relative to the parent VI. Therefore, copying a VI from user.lib to modify it for a special case does not change the path to its subVIs located in user.lib.

If you want to copy a VI and its subVIs to another directory or computer, do not save the VIs in user.lib because when you run the top-level VI from the new location LabVIEW references the original subVIs in user.lib.

instr.lib—Any instrument driver VI you want to display on the Instrument Drivers palette.

project—VIs you use to extend LabVIEW capabilities. VIs you store in this directory appear on the Tools menu.

wizard—VIs you store in this directory appear on the File menu.

www—Location of HTML files you can access through the Web Server.

help—Any VIs, .hlp, and .chm files that you want to make available on the Help menu.

LabVIEW Data—Any data files LabVIEW generates, such as .lvm or .txt files.

You also can create a directory anywhere on your hard drive to store LabVIEW files that you create.

When you open a VI you place in the labview\help, labview\project, and labview\wizard directories from the Help, Tools, or File menu, LabVIEW opens the VI in a private application instance (NI.LV.Dialog).