Related to "Error- 200279"

[Parny]

Dear all,

I am using DAQmxRead.vi of type set to analog1dwfm Nchan Nsam. My continuous aquisition(data is finally put into MS access database) runs successfully for the whole day and found that at the end of the day at a point of time, it populates the error - 200279, thus stopping the data acquisition. Could not catch yet any event that is influencing so at that point of time.

But I wonder lightly, if there is any issue, how come the vi runs fine the whole day?? Also I would not mind trying of overwriting the samples and neglect the old ones. Is there a way to do so?, hence forth I can neglect that error-200279.

My labview - ver8.5. I had seen the prev posts regarding error-200279, but unable to conclude myself

Also the vi and subvi are enclosed here.

Thanking you.

Message Edited by Parny on 02-11-2008 06:14 PM

[JoeFriedchicken]

Hi Parny,

It certainly is strange that the VI would run for a whole day before having this error. I looked at your VI and noticed that you're not handling errors. After the DAQmxStop, use a Simple Error Handler VI to show and explain any errors that may occur. Also, you didn't attach the configuration VI for your DAQmx task (it was called "Untitled 20.vi"), so I don't know exactly how you're setting up your task. If you still have problems, please add that VI later.

Since your VI can run for many hours without any problems, my guess is that another system process (like virus scanning or automatic updates) is dominating CPU usage and causing LabVIEW to execute at lower priority. When this happens, the while loop won't run as quickly and samples can be overwritten before DAQmxRead can pull them into LabVIEW memory. I saw that you read 100 samples at a time, so you may want to try increasing the number of samples to read or try reading all of the available samples (use '-1' as the number of samples to read in this case).

If you're still getting the error after trying these, you can ignore the overwritten samples. If you want to do that, you can set that with a DAQmx Channel Property Node (see my attached image). Please let me know how it works out.

[Parny]

Hello Joe,

Thanks for the tips and suggestions given. Sorry for forgetting the other vi(untitled20.vi), attached here. 

I changed the connections to overwrite the samples using DAQmx property node as you showed in your diagram, will monitor how it goes. Will know you the update. Not sure whether the simple error handler will make much difference?

Thanking you.

[JoeFriedchicken]

Great, thanks for adding the other VI. Please let me know what happens 🙂

The error handler won't fix the errors, but it will give a more detailed description of the error when it happens. This often helps you figure out what you can do to fix the problem, though.

[Parny]

Hi Joe,

Just giving you some update: As my vi was also assigned database(MS access/Oracle) tasks where the most of the time was comsumed by executing the SQL query. Sometimes this query time was long and may be resulting in overwriting of samples(got that error - 200279). It looks to be in control after adding that node before the task, but it failed(gave error-200279) once or twice before as well. Moreover I have been running 5 more vis parallelly which are also doing database tasks and so. These all vis are meant to run 24/7 without any interrupt to collect the data from the active production floor. At the moment, all vis are under overwritten(samples) mode.

Overall, there's some improvement.

Thanking you again.

[JoeFriedchicken]

Hi Parny,

I'm glad that your system is running better than before. It sounds like you have some high demand on it! You may need another computer soon 😉