|| 4.57 out of 5
Instrument Driver Troubleshooting Guide
Instrument Drivers/IVI>>LabVIEW Plug and Play Driver
Primary Software Version:
Primary Software Fixed Version:
Instrument Drivers/IVI>>LabWindows/CVI Plug and Play Driver
I have downloaded an Instrument Driver from IDNet and it is not behaving as expected. What steps should I take to troubleshoot the issue?
Here is a list of steps to take in order to troubleshoot instrument drivers:
Confirm that the instrument driver is installed correctly
- Check the instrument driver's readme or download page for required software and any other special instructions.
- Confirm that the proper supporting software is installed, and that your computer was restarted after the software was installed.
- Also, make sure that the software was installed in the correct order.
- Examples of necessary software
- IVI Compliance Package
- NI Modular Instrument Driver (NI-SCOPE, NI-DMM, etc)
- Confirm that you have the currently released instrument driver.
- Confirm successful communication through NI-VISA (or other supporting software)
If you will be using IVI-C Class Drivers, you will need to configure the IVI Logical Name and Driver session in MAX and then Save the settings.
Try communicating through a simple VISA example to confirm that VISA is working through the ADE (LabVIEW, LabWindows/CVI, Measurement Studio).
Open the ADE that you will be using and find an example for the instrument driver
- LabVIEW Plug and Play instrument drivers should be located under <LabVIEW>/instr.lib. (For example: C:\Program Files\National Instruments\LabVIEW 2009\instr.lib\Agilent 34401) Plug and Play instrument drivers do not have installers, they just need to be extracted into instr.lib. When extracting them, make sure that your extraction software does not create an additional folder layer (...\LabVIEW 2009\instr.lib\Agilent 34401\Agilent 34401).
- LabWindows/CVI Plug and Play instrument drivers just need to have the source code referenced properly in the project that you create. They do not have installers and just need to be extracted.
- IVI Instrument Specific instrument drivers should be installed in the IVIStandardRoot directory(s). (For example: C:\Program Files\IVI Foundation\IVI\Drivers) If the IVI Instrument Specific instrument driver is maintained by NI, it will also create IVI driver entries in MAX, as shown in the image below.
Confirm that you are using the correct VISA resource or IVI Logical Name and run the example
- For LabVIEW PnP (project-style), you will need to run the Example Finder (Help»Find Examples).
- For IVI-C Drivers, create a CVI project and add the driver files and example to the project. The files can be found at <IVIStandardRootDir>/Drivers.
- For CVI PnP, just open up the .prj file and run the example.
- For IVI-C Class Driver examples:
- In LabVIEW, use the example finder (Help»Find Examples then Hardware I/O»Instrument Drivers»IVI)
- In LabWindows/CVI, use the example finder (Help»Find Examples then Hardware I/O»Instrument Drivers»IVI)
If none of those steps were able to communicate through the instrument driver, then skip ahead to step 12
If you can communicate through the instrument driver, but see a problem, isolate the problem down to the minimum number of VIs or function calls that reproduce the error
- If the example runs correctly, skip ahead to step 11.
- If the example does not run correctly, try the following:
- Just running an Initialize and Close
- Disabling IDQuery
- Restarting the computer and re-confirming VISA communication
- Seeing if the problem reproduces on another computer or with an identical instrument
- If using IVI, try using the Specific Driver directly
Take an NI I/O Trace capture of the error occurring
If the Instrument Driver is NI-Supported, collect the following information:
- See if the problem persists in highlight execution mode (LabVIEW) or single-stepping
- Confirm that you are closing the instrument driver reference at the end of your application
- Look up any error codes on ni.com
Once you have all of the previous information, contact NI Support.
If the instrument driver is not NI-Supported, try posting your problem to the NI Discussion Forums or contacting the instrument driver vendor for support.
- Operation System version and bitness
- ADE version, type, and bitness
- Instrument Driver name, version, and bitness
- Exact instrument model, revision, and firmware version
- Is the instrument listed as being supported by the instrument driver?
- Was the instrument driver working well before? If yes, what has changed since then?
- When was successful VISA communication last confirmed?
- What error codes are being generated and what did you find when looking them up on ni.com?
- Does the problem reproduce on other computers?
- Does the problem reproduce with other identical instruments?
- Instrument control bus being used (USB, GPIB, Serial, etc.)
- Does the problem occur in all buses?
- Based on the error information and NI I/O Trace capture, look at the VI or function where the error is being reported from.
- Look at the commands being sent and compare them to the programming manual.
- If the commands being sent do not match those in the programming manual, try changing them and see if that resolves the issue.
- For debugging an IVI driver when using the LV wrappers, see this document.
- If available, try a different instrument driver.
- If using an IVI Driver, see if the problem occurs when simulating a device, or when range checking is turned off.
Possible Reasons for incorrect instrument driver behavior:
Related Links: Instrument Driver NetworkGetting Started with NI ProductsGetting Started with Instrument Control
- The commands are incomplete or incorrect.
- The instrument model/revision is not supported by the instrument driver.
- The communication settings are not correct in the instrument driver (most common in RS-232).
- The values being passed by the user application are out of range.
- The instrument driver is not installed or configured correctly.
- The particular instrument model that you are using is supported by the driver, but was not available for testing.
- The instrument control bus that you are using is not supported by the instrument driver (most common with RS-232).
- The IVI driver is in simulation mode, and you do not expect it to be.