What Errors are Common with USB Devices and NI-DAQmx Base?

Updated Nov 8, 2017

Reported In

Hardware

  • cDAQ-9132
  • cDAQ-9133
  • cDAQ-9138
  • cDAQ-9139
  • cDAQ-9135
  • USB-6210

Driver

  • NI-DAQmx Base 15.0

Issue Details

When running a program using NI-DAQmx Base with a USB device I get an error that I cannot resolve. What are some of the common errors that occur with USB devices in DAQmx Base, and how do I fix them?

Solution

Important Note: NI-DAQmx Base is different than NI-DAQmx. NI-DAQmx Base offers a subset of NI-DAQmx functionality on Windows, Linux, Mac OS X, Windows Mobile, and Windows CE OSs. 


Below are descriptions and potential solutions to some common errors seen when using a USB device with the NI-DAQmx Base driver. 

Error -6001 
This error indicates that a USB-600x or USB-6501 device in your system has out-of-date firmware. This error can occur with a "factory fresh" device or after upgrading your application from NI-DAQmx Base 2.x or earlier. To update the firmware, run the utility FWUpdate from any desktop PC, located here: <NI-DAQmx Base directory>/bin 

Note: If you plan to deploy your application to a target other than your desktop development PC, you must ensure that the deployed version of NI-DAQmx Base matches that which is installed on your development PC. 

Error -6003
This error may arise when an incompatible version of NI-DAQmx is installed on the same system. For example, DAQmx Base 3.1 for Windows is only compatible with NI-DAQmx 8.6 for Windows. You can find compatible versions of NI-DAQmx in the NI-DAQmx Base readme found in NI Downloads, using directions found here

In addition, this error may occur if NI-DAQmx was recently removed, or if NI-DAQmx Base was recently upgraded. Unplugging and re-plugging the device back into the USB port may fix this error in those situations. 

Error -6004
This error typically occurs because the driver associated with the device has recently changed, and the device firmware is incompatible with NI-DAQmx Base. Unplugging and re-plugging the device back into the USB port may fix this problem. 

Error -6005
This error typically occurs when an NI-DAQmx Base operation is closed unexpectedly (by aborting a running VI, etc.). Restarting LabVIEW or unplugging and re-plugging the device back into the USB port may fix this problem.

Error -6006
This NI-DAQmx Base error can occur when an incompatible version of NI-DAQmx is installed on the same system. For example, DAQmx Base 3.1 for Windows is only compatible with NI-DAQmx 8.6 for Windows. You can find compatible versions of NI-DAQmx in the NI-DAQmx Base readme found in NI Downloads, using directions found here

In addition, this error may occur if NI-DAQmx was recently removed, or if NI-DAQmx Base was recently upgraded. Unplugging and re-plugging the device back into the USB port may fix this error in those situations. 

Error -8002
This device initialization error can occur when USB power is temporarily lost from the host, possibly due to operating system hibernation or other power loss. This can also occur randomly as an internal software error. Unplugging and re-plugging the device back into the USB port may fix this problem. 

Error -8006
This device initialization error can occur when USB power is temporarily lost from the host, possibly due to operating system hibernation or other power loss. This can also occur randomly as an internal software error. Unplugging and re-plugging the device back into the USB port may fix this problem. 

Error -8007
This device initialization error can occur when USB power is temporarily lost from the host, possibly due to operating system hibernation or other power loss. This can also occur randomly as an internal software error. Unplugging and re-plugging the device back into the USB port may fix this problem. 

Error -200220
This "device identifier is invalid" error can occur if a USB task is aborted before DAQmx Base Stop Task.vi is called. If the LED is no longer blinking on the USB device, you will need to unplug and re-plug the device back into the USB port to reset the device. Additionally, you may need to run lsdaq and/or close and re-open LabVIEW to reset the software.

WAS THIS ARTICLE HELPFUL?

Not Helpful