Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -200284 occurring intermittently towards end of testing.

Hi,

 

I am getting the following error when trying to aquire samples with my DAQ USB-6008:

Error -200284 occurred at Configure DAQ.vi:1

Possible reason(s):

Some or all of the samples requested have not yet been acquired.

To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock.

Property: RelativeTo
Corresponding Value: Current Read Position
Property: Offset
Corresponding Value: 0

Task Name: _unnamedTask<2DD0>

 

My sample rate is only 5kS/s, and my timeout is more than enough at 40seconds (I only take less than 10 s of samples at a time).  The external trigger is hardwired to the PFIO pin on the NI-USB6008.  I have determined the grounding is all okay and the problem is intermittent.  It seems to only give me this error towards the end of my test, where I have taken at least 150 trials.  If I stop the test early, and then restart for my last trials, then I don't get any errors.  It's like the DAQ is off sync and didn't catch when the trigger went  high at the beginning.  Could it be a resource problem?  If so, should I reset the DAQmx and how?  I'm running out of ideas.  Thanks in advance.

0 Kudos
Message 1 of 3
(4,003 Views)

kcarbon80,

 

Try the suggestions in this KnowledgeBase Article (http://digital.ni.com/public.nsf/allkb/FEF778AD990D5BD886256DD700770103?OpenDocument). If none of the suggestions work post up some screenshots of your program.

Thomas N.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(3,975 Views)

kcarbon,

 

the 6008 does not support retriggering, I would suspect that later on in your code you are missing triggers, which would then cause the read function to timeout.

 

The example here will give the quickest retriggering of the device. http://digital.ni.com/public.nsf/allkb/FF8D0302E200ADDE86256FB20077E88A

 

Also if you are doing any sort of processing I would recommend the producer consumer architecture so any additional delay in processing data is transferred to the consumer loop.  

 

https://decibel.ni.com/content/docs/DOC-2431

 

I hope that helps!

 

J Newk
Systems Engineer
National Instruments
0 Kudos
Message 3 of 3
(3,972 Views)