6009 USB DAQmx Read Error 50405

[Bulsan]

I have an 6009 USB that I'm using to monitor a square pulse generated by a relay closing. It uses the 6009's 5V supply through a 10K resistor tied to ground.  The pulse is produced by a wavelength counter on a spectrometer that is scanning wavelengths at a constant rate.  I use the rising edge of this pulse to trigger a wavelength calculation and also a lock-in amplifier measurement in Labview.  The routine runs for approximately a 30 minute period to complete a measurement.  When I wrote the code in Labview 8.5, about a year ago, it worked fine.  Over time, I started getting an intermittent 50405 error, "No transfer is in progress because the transfer was aborted by the client.  The operation could not be completed as specified."   The failure occurs with DAQmx Read (Analog 1D Wfm NChan NSamp) which is running in a continuous mode.  The led on the 6009 also turns off.  The frequency of this error has increased over time and is now to the point that I cannot complete a complete wavelength scan.  Unplugging the 6009 and plugging it back in restores 6009 operation operation, however, this solution is not practical because I am measuring parameters as a function of time and I lose data.  I recently updated NI-DAQ to version 8.9, but the problem persists.  The error also occurs when the 6009 is operated in MAX.  I've also unplugged all other USB devices from the back of the computer and the problem still occurs.  Any suggestions would be greatly appreciated.

I'm using a Dell Optiplex 775 system with Windows XP, Labview 8.5.1 and NI-DAQ 8.9.

[Frozen]

There goes my hopes of downgrading from Win7 to XP to solve a similar problem...

First, you should upgrade to the latest DAQmx version, which is 9.2.2.... (this will not fix your problem)

Next you should read this thread. Luckily for you, the RESET works in XP.

Then you should throw away the DELL computer. I have read lots of other posts about people having problems with DELL computers. Here is another interesting thread to read.

Lastly, go an purchase the highest quality, gold plated, ferrite beaded USB 2.0 cables that money can buy to replace every USB cable in your system.

Hopefully this helps you, because I will be doing the same very shortly.

Good luck.

[Bulsan]

Thanks for the response and the links.  They were very helpful.

I also upgraded to 9.2.2 and as you suspected the problem is still there.  I did have ordered some new USB 2.0 cables with Ferrite and will let you know if that helps the situation.

[Bulsan]

I've now upgraded to the USB 2.0 cables, but the problem didn't go away.  I did discover that the frequency of the error  was significantly reduced by inserting a wait(ms) call (set to 0 mS) in the while loop controlling the continuous data acquisition.  I'm not sure why this improved the situation, but it did. 

[TimmTheEnchanter]

Bulsan,

Have you tried the other suggestions for resolving this issue?  I don't know if USB 2.0 cables alone will be enough to fix the issue, as per what Frozen mentioned.

However, I would like to mention I've heard of some intermittent and non-consistent issues which arise out of the Windows XP driver interfacing with certain USB devices.  There is a hotfix which you can try implementing if the other solutions do not work for you.

Regards,

Andrew