Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

NI USB-6210 - Error -200020 occurred at Self Test

I am running NI USB-6210 to measure voltage samples.  My system is Windows XP. 
 
My application was written in C#.  I was running test for a few hours and the card gave me the following error.
 
NationalInstruments.DAQmx.DaqException: No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified.
Task Name: _unnamedTask<0>
Status Code: -50405
So, I stopped my application and then opened Test Panel from Measurement and Automation.  I pressed Self-Test button and I got a dialog box with the following error message.
 

The device self test has failed. The error report from the device driver is as follows:

Error -200020 occurred at Self Test

Possible Reason(s):

Measurements: Self-test of the device has failed.

 
I unplugged the USB DAQ card and plugged it back in and then ran self-test and everything worked fine.  This is a very scary situation for me since my system will be used in production environment and I need to figure out what went wrong.
 
0 Kudos
Message 1 of 2
(3,802 Views)
Hello slim1976,

It sounds to me that your device ended up in a bad state somehow.  This can be caused by a large number of situations varying from your USB lost power for a second to not handling tasks properly (closing resources for example).  It sounds like resetting your device fixed the issue, whatever it was.  Instead of unplugging it, you can reset the device from Measurement and Automation Explorer directly or even programatically in your code.

If this is the first time you have seen this,  I would not be too worried.  If you can reproduce the behaivior, then the first thing I would suggest is to try and run an example program.  If this does not cause the problem,  then most likely it is something in the code.  If it does occur in the example program, then that leads us to a driver/hardware issue.  After that,  we would go down the route of trying different computers/etc to try and isolate the issue.

Again, there are many causes for this, so I cannot tell you exactly what happened.  Please post back if you have any questions or further concerns.
Neal M.
Applications Engineering       National Instruments        www.ni.com/support
0 Kudos
Message 2 of 2
(3,768 Views)