Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Troubleshooting Common Upgrade Issues

LabVIEW 2013 Help

Edition Date: June 2013

Part Number: 371361K-01

»View Product Info

Locating Missing Module or Toolkit Functionality

To use a module or toolkit with LabVIEW 2013, you must install a version of the module or toolkit that is compatible with LabVIEW 2013. Otherwise, the VIs, project items, dialog boxes, and other features associated with the module or toolkit do not appear in LabVIEW.

Complete the following steps to locate and install missing modules and toolkits:

(Windows)

  1. Locate and install the module or toolkit.
    • Modules and toolkits that ship on the LabVIEW Platform DVDs—Insert the LabVIEW Platform DVD 1 and enter the serial number of the module or toolkit. To determine if a module or toolkit ships on the LabVIEW Platform DVDs, refer to the LabVIEW Platform Readme.
    • All other LabVIEW modules and toolkits—Insert the installation media for the module or toolkit and follow the onscreen instructions.
    • Third-party add-ons—From the Getting Started window of LabVIEW, select Find Drivers and Add-ons»Find LabVIEW Add-ons to access the latest versions of third-party add-ons.
  2. Repair the device drivers. If you install LabVIEW or an add-on after installing device drivers, LabVIEW cannot recognize the device drivers.

(OS X and Linux)

Install a version of the module or toolkit that is compatible with LabVIEW 2013. You can obtain a compatible version of the module or toolkit from the following locations:

  • For NI add-ons—Download the latest version of the add-on from ni.com/downloads.
  • For third-party add-ons—Download the latest version of the add-on from the LabVIEW Tools Network at ni.com.

For installation instructions, refer to the readme file on the installation media of the module or toolkit.

Locating Missing SubVIs, Palettes, and Property Nodes

LabVIEW may not be able to locate certain subVIs, palettes, or Property Nodes for the following reasons:

  • You did not install the LabVIEW 2013 versions of the drivers used by your VIs. To communicate with hardware devices, LabVIEW 2013 requires that the LabVIEW 2013 versions of the related device drivers be installed. If you do not update your drivers to run with LabVIEW 2013, the associated driver VIs, palettes, and Property Nodes are not available, making it impossible for LabVIEW to communicate with the device. To correct this problem, reinstall the related drivers from one of the following sources:
    • (Windows)
      • For most NI devices—Use the NI Device Drivers DVD packaged with the LabVIEW Platform DVDs.
      • For NI devices not included on the NI Device Drivers DVD—Use the driver media packaged with the device or download the latest version of the driver from ni.com/drivers.
      • For third-party devices—Search for and download drivers for third-party instruments on the Instrument Driver Network at ni.com.
    • (OS X)
      • For NI-VISA and GPIB devices—The default LabVIEW installation includes drivers for NI-VISA and GPIB, or NI-488.2, interfaces. If you previously customized the installation process to avoid installing these drivers, insert the LabVIEW DVD, click Customize on the Installation Type page, and select the drivers that are missing from LabVIEW.
      • For the latest version of the driver for any NI device—Download the latest version of the driver from ni.com/drivers.
      • For NI-DAQmx Base—Download the NI-DAQmx Base Software at ni.com.
      • For third-party devices—Search for and download drivers for third-party instruments on the Instrument Driver Network at ni.com.
    • (Linux)
      • For NI-VISA drivers—The INSTALL script for LabVIEW prompts you to install these drivers. If you chose not to install the drivers when you installed LabVIEW, you must run the INSTALL script again.
      • For other NI devices—Use the driver media packaged with the device or download the latest version of the driver from ni.com/drivers.
      • For NI-DAQmx Base—Download the NI-DAQmx Base Software at ni.com.
      • For third-party devices—Search for and download drivers for third-party instruments on the Instrument Driver Network at ni.com.
  • You installed a module or toolkit after you installed the drivers used by your VIs. If you install an add-on, such as LabVIEW FPGA or the LabVIEW Real-Time Module, after installing device drivers, you must repair the device drivers in order for the module to recognize them and their associated VIs. Complete the following steps to repair device drivers:
    1. Navigate to the Programs applet in the Control Panel.
    2. Select National Instruments Software from the list of programs.
    3. Select each device driver and click Repair.
  • Your VIs require files from the user.lib directory of a previous version of LabVIEW. If you created custom VIs in a previous version of LabVIEW, you must copy those VIs to the user.lib directory of LabVIEW 2013 to continue using them as subVIs.

Determining Why LabVIEW Cannot Open VIs from a Previous Version

If you are upgrading a VI from LabVIEW 5.1 or earlier, you cannot open the VI in LabVIEW 2013. To upgrade a VI from one of these versions of LabVIEW, you must first upgrade to an intermediate version of LabVIEW or use the LabVIEW Conversion Package. Refer to the NI Developer Zone at ni.com for more information about upgrading from your specific legacy version of LabVIEW.

Determining Which Versions of NI Software Are Installed

Use the Measurement & Automation Explorer or the system tools available on your machine to determine which versions of NI software you have installed, including modules, toolkits, and drivers.

Restoring VIs to a Previous Version of LabVIEW

After you save a VI in a new version of LabVIEW, you cannot automatically load it in an earlier version of LabVIEW. To allow the VI to run in the previous version, open the VI and select File»Save for Previous Version. Refer to the Developer Zone at ni.com for more information about loading VIs in a previous version of LabVIEW.

If your computer does not have enough memory to convert all the VIs at once, convert the VIs in stages. Examine the hierarchy of VIs you want to convert and begin by loading and saving subVIs in the lower levels of the hierarchy. Then progress gradually to the higher levels of the hierarchy. Open and convert the top-level VI last. You also can select Tools»Advanced»Mass Compile to convert a directory of VIs. However, mass compiling converts VIs in a directory or LLB in a set order. Refer to the Fundamentals»Creating VIs and SubVIs»How-To»Saving VIs»Mass Compiling VIs topic on the Contents tab of the LabVIEW Help for a description of the order in which LabVIEW processes files when you mass compile. If the conversion process encounters a high-level VI first, mass compiling requires approximately the same amount of memory as if you opened the high-level VI first.


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit