Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -200279

I get this error in the code and I don't actually know why, it happens
usually after the code ran at least 200 iterations.

The error comes up after the second CountDown.vi (from left to right).
I attached a link to the pic with the part of the code that shows the
error, any ideas would be greatly appreciated.

Our system
Laptop P4 2.6GHz, 512 RAM, NI DAQ6024E, LabVIEW 8.2

http://plaza.ufl.edu/xchus/Work/Complete%20VI.jpg

Thanks in advance.
0 Kudos
Message 1 of 7
(4,701 Views)
Hi Xchus,

have you looked at my answer at LAVA

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 7
(4,670 Views)

Hello Xchus,

The two errors you are getting are due to a buffer overflow (-200279) and a timeout (-200284). I expect that the error is being returned by the DAQmx Read call that you are making after the second Countdown.vi.

A buffer overflow will occur if you do not read in samples fast enough for the rate at which you are acquiring.  It looks like you have set your application to acquire 1200 samples at a time at a rate of 10 Hz. I'm not entirely sure what your Countdown.vi is doing, but it looks like you are roughly calculating a delay before calling the DAQmx Read case structure.  If you are slightly off in this calculation, it is possible that you are waiting slightly too long in each iteration of the application and an excess amount of data is slowly building until you get an overflow after ~200 iterations. Two options to prevent this include:

1) Not wiring the 'Samples to Read' input on the DAQmx read so that all available data is read and
2) Use a property node to determine when to read the samples out of the buffer as explained in this Knowledge Base.

A timeout (-200284) will occur if you call the DAQmx read and there are not enough samples available after waiting the designated time ('Timeout' input to DAQmx Read.vi).  Following the same above suggestions you can avoid getting a timeout error.  The default timeout is 10 seconds.  You could also increase this number.  Given your sampling rate and number of samples, your application could take up to 120 seconds or 2 minutes to acquire enough data. For more information on resolving the timeout, please read Why Do I Get Error -200284 When I Set a Small Sampling Rate in DAQmx?

Hope this helps,

Jennifer O.
Applications Engineer
National Instruments

 

0 Kudos
Message 3 of 7
(4,670 Views)
I followed step number 2 mentioned by Jennifer and I also increased the samples to 3000 and the indicator increases and decreases (it shows 2 then 8 then 16 and then it drops to either 0 or 2 and it increases again).

I couldn't do step number 1 because it kept giving me errors, I'll let the program run like this for now and I'll try again option number 1 tomorrow. It seems like is working for now. Thanks again for the help.
0 Kudos
Message 4 of 7
(4,659 Views)
Update

Following both Ton and Jennifers suggestions I apparently fixed it. I got both computers running for about 12 hours one taking 1200 samples and the other 3000 samples, however I only added the timeout to DAQmx read and the Available Samples per Channel read node. I will continue testing. Again thanks for your help.
0 Kudos
Message 5 of 7
(4,644 Views)
The error showed up again after the 710th file (~ 24h of data), but the indicator doesn't show any remaining samples in the buffer, now I'm clueless.
I got to take at least 72h of data. I made some changes to the code, but if anyone have any other suggestions feel free to post them. Thanks!
0 Kudos
Message 6 of 7
(4,624 Views)
Hello Xchus,

could you show your current code?

Thanks,

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 7 of 7
(4,614 Views)