LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 200361 on some Machines

Hi,

we have a problem reading from a NI USB-6009 (its the same with a NI USB-6008). When reading data "Error -200361 occured at DAQmx Read" occurs - but not every time. Once the program runs it will keep running fine, then if I stop it and start it again a couple of times it will aquire no data and then evntually display the error code. Sometimes it can be run five times until the error occurs sometimes only twice. We figured it can't be our VI since the same thing happens in the Meas.&Aut. Expl. Testpanels (again after a couple of starts) , plus this only happens on two identical new computers yet it works fine on the other computers in the office. The culprits are two Acer AX 3900 with Win 7 64 installed. We've tried to update all relevant drivers but the problem persists. Now we worry that our program could face similar problems on our customer's computers. I've read a couple of related threads and they don't seem to help. I feel this could be a drive issue.

 

Any help would be appreciated

 

Thanks,

 

Florian

0 Kudos
Message 1 of 10
(5,383 Views)
0 Kudos
Message 2 of 10
(5,353 Views)

Thanks for the reply,

but the article does't help:

The error occurs even when I close all other windows. I also tried the other fix, but removing and reinstalling the device didn't help either.

Meanwhile I was able to reproduce this error an a notebook which also runs Win 7 64.

Using an NI USB-6216 prevents the error from happening - but I feel I'm not demanding anything extraordinary of the 6008/6009 especially since it seems to happen randomly and works more often than it crashes.

Afaik WIN7 had a change in USB software in order to increase throughput - can my issue be related to this changes?

0 Kudos
Message 3 of 10
(5,337 Views)

Hi again,

we have found a workaround for our problem. We installed a USB 2.0 PCIe Card and everything works fine. Afterwards I tried the USB-6009 on the computer's original USB ports again - this time unplugging everything else from USB but it still didn't work there. The cause obviously can't be traffic and overhead caused by other USB devices.

I'd like to know the cause because issues like that could affect any of our customers - can anyone contribute suggestions? Does anyone know a freeware/shareware programm to benchmark USB performance?

 

Regards,

 

Florian

0 Kudos
Message 4 of 10
(5,254 Views)

Hello,

 

we have the same problem by using the NI USB 6251 device on windows 7. 

 

We have two measurement cards installed, a pci express wich works fine and a usb device wich occurs the 200361 error. I think it can't be our vi. because we used the same configuration on an older pc with windows xp and we never got that error there. So it seems that the error is occured by the windows 7 usb support. Unfortunately we are not able to use an additional usb 2.0 card, because there is not enough space. 

 

Xeledon, wich mainboard do you have?  We are using the Gigabyte P55M UD2 with intel ci.

 

regards Christoph

Message Edited by Christoph O. on 05-31-2010 10:24 AM
0 Kudos
Message 5 of 10
(5,208 Views)

Hello,

 

the mainboard is Acer FIH57 with Intel H57 Revision 12.
Does the error occur in the Measurement & Automation Explorer Testpanel too? To reproduce our error there the mode has to be set to "continuous", then press "start" and then "stop". Repeat until the error message appears - usually that doesn't take long.

New info: I installed the 32 bit version of Win7 but that didn't help either.

 

regards

Florian

0 Kudos
Message 6 of 10
(5,153 Views)

Ok, i tried the Measurement and Automation Explorer. I got the error Message 200279.

 

"Measurements: Attempted to read samples that are no longer available. The requested sample was previously available, but has since been overwritten. "

 

In my experience this error occurs, when the calibration of the measurement programm(sample rate, buffer size, samples to grab) is wrong or the pc is just to busy. But i don't know the code behind the m&a - explorer.....

 

The last days (yes, i'm very frustated) i played arround with the error message 200361 and i found that it is independent from the sample rate, the buffer size or the cpu usage. 

We have the latest driver and tried different bios versions, but there is no solution yet. 

 

So if anyone has a solution, pleeeaaaase let us know.

 

thanks! and regards christoph

Message Edited by Christoph O. on 06-01-2010 04:14 AM
0 Kudos
Message 7 of 10
(5,140 Views)

Ok, i played around a bit and figured out, that the problem really depends on the used usb port. The front usb-connector definetely doesn't work, even if it is usb 2.0. The mainboard ports are working fine, but not all them. By using one of the good usb-ports the measurment card works fantastic. There is no error by reading 6 channels @ 10 khz and it doesn't matter if the system is used by other programms. great!

 

But i've no idea for the core problem yet.

0 Kudos
Message 8 of 10
(5,027 Views)

Hi Christoph,

 

I'm having exactly the same issues as you had (see my post here:http://forums.ni.com/t5/Multifunction-DAQ/USB-6009-overflow-error-on-continuous-mode-after-restart-o...) which I posted before I had come across your post.

 

Anyways, did you come across a satisfactory solution other than changing USB ports?  I'm trying to use the 6009 on a laptop so I would expect all the ports to be on the main board, I'm not sure I have any way to know which ones are or are not.

 

Thanks for any insight,

Dan

 

0 Kudos
Message 9 of 10
(4,674 Views)

Hi,

 

I ran into the same problem when trying to run my 6008 on a Dell laptop with Windows 7.  It was working fine on my HP desktop and now is randomly crashing with this error on the dell.  The symptoms are identical, in that it works at first, but then throws this error.  Also, the software reset in measurement and automation does not even reset the device.  I have to unplug and replug in the device.  This is very frustrating.  Has anyone at NI figured out the problem.  Unistalling and reinstalling doesn't seem to fix anything.  Any help would be appreciated.

 

Regards,

Brian

0 Kudos
Message 10 of 10
(4,582 Views)