04-04-2016 07:36 PM
I'm experiencing an issue where a system that runs fine for a while, with good margin (1 kHz loop rate, 300uS PCL loop duration), suddenly throws error -200714 and shuts down. I have filter DAQ errors on, and this is performance related, so why does this shut down the system instead of incrementing HP count?
Thanks,
The error explanation is "Acquisition has stopped because the driver could not transfer the data from the device to the computer memory fast enough. This was caused by computer system limitations.
Reduce your sample clock rate, the number of channels in the task, or the number of programs your computer is executing concurrently."
Solved! Go to Solution.
04-05-2016 06:54 PM
Hi Stephen,
What version of VeriStand are you seeing this on?
Also, does the error call out a source or specific DAQ channel? Any information about the DAQ configuration on this system may be helpful. Are you using Slow Background Conversion Mode?
Thanks,
Trent
04-05-2016 07:11 PM
So yeah, it would be nice to know
I can tolerate the error if it is not fatal
04-05-2016 07:16 PM
04-11-2016 02:26 PM
Any word from DAQ?
04-12-2016 05:46 PM
Hi Stephen,
The reason you're getting this error is because the program isn't keeping up with the sample clock.
I recreated this (external to VeriStand) by running the HW-Timed Single Point LabVIEW shipping example and increasing the rate until I got this error. I actually got Error -209802 a few times before getting -200714. The first error is recoverable and I was able to ignore it and continue, the second stops execution when it's thrown.
Error -209802:
"DAQmx Wait for Next Sample Clock detected one or more missed sample clocks since the last call to Wait for Next Sample Clock which indicates that your program is not keeping up with the sample clock.
To remove this error, slow down the sample clock, or else change your application so that it can keep up with the sample clock. Alternatively, consider setting the Convert Errors to Warnings property to true and then handling the warning case appropriately."
Error -200714:
"Acquisition has stopped because the driver could not transfer the data from the device to the computer memory fast enough. This was caused by computer system limitations.
Reduce your sample clock rate, the number of channels in the task, or the number of programs your computer is executing concurrently."
Based off what Jarrod mentioned above, the initial error would be filtered out by VeriStand judging by the blue highlighted portion of the first error. I suspect that error -200714 is fatal because of the red highlighted portion above; the acquisition has stopped.
If you monitor the DAQ Error System Channel, do you see Error -209802 as well? Does slowing down the PCL rate resolve these errors?
Hope this helps!
Trent
08-11-2016 12:09 PM - edited 08-11-2016 12:26 PM
I don't mean to dig up this old thread, but I remember reading somewhere a while ago that one of the newer DAQmx drivers can now successfully recover from this error (and subsequently the "filter DAQ errors" option in VeriStand becomes truly useful). Is there a version of DAQmx out there that can continue with acquisition after error -200714 is converted to a warning, and actually recover from running late?