Communication with the ni usb 6009 could not be established

[michael27]

I am trying to use the NI DAQmx with Labview, but every time I run my labview program to collect data, a screen pops up saying ...

"Communication with the NI USB 6009 could not be established. Please check the connections and look for a blinking green indicator light on the side of the device."

The light is blinking green. I reinstalled the NiDAQmx drivers but nothing changed.  Any suggestions?

[Jim_S]

Hello Michael,

I would try to see if the device is being recognize in Measurement and Automation explorer (MAX). MAX is located on your desktop or it can be found by navigating to Start » All Programs » National Instruments. Your device should be under Devices and Interfaces. If it is, I would try to access the device using Test panels. Here is a link to it.

If this is still producing the same error, please provide the Error number of it along with the version of your DAQmx driver. This information can be found in MAX by navigating in the Configuration window to My System » Software. The Software section states all the NI software on your machine.

If the USB-6009 isn't in MAX, I would check to see if this is in the Device Manager. If you are using Windows 7, go to this link. For Windows XP, go to this link. The USB-6009 should be under a section called Data Acquistion Devices. If it isn't there, then the USB-6009 wasn't recognized correctly by Windows.

[caprice24]

Hi Jim,

I can see that the USB-6009 is found in the Device Manager for XP as Data Acquisition Devices-USB-6009. But I cannot see it in the NI Device Monitor, nor can I see it in the Measurement and Automation Explorer. It looks like it is properly detected by Windows XP, and the USB light is blinking on the unit.

Any ideas?

Thanks,

Nick

[caprice24]

I should add that I'm using NI-DAQmx Device Driver 9.1.5 and Labview 2010.

[Jim_S]

Hello caprice24,

After looking into this issue, there was a problem with our DAQmx driver that caused some USB devices not to be recongized in MAX even though they are represented in Device Manager. I would suggest as a fix to this is to upgrade the driver to 9.2.2 or get the patch for it and this should fix the issue.