DASYLab

cancel
Showing results for 
Search instead for 
Did you mean: 

Sample Rate too fast

I've created a DasyLab program which needs to run for a period of about 24 hours.  The program works as it is meant to, however, when I try to let it run for the full duration, it encounters a problem, usually around about 4 hours in, with the error message:
"Sample rate too fast.  Measurement had to be stopped."
 
I'm working in DasyLAB 8, with a sample rate of 100Hz and block size 16 (small because I need it to respond relatively quickly).  Data is being written at a not-too-challenging 1Hz and is only 8 channels of ASCII data.
 
So, I've tried what i could think of: disabling my virus scan and trying to stop tasks running in the background which might magically be causing DasyLab to flip.  However, these don't work.
 
I write data to disk in the program, so I tried dropping the rate at which data is dropped, but this also makes no difference.  Also, I changed the buffer size downwards to see if that would make it stop faster, but it made no difference, which leads me to the conclusion that it is my computer doing something stupid, not DasyLab.
 
However, the question still stands on how to get around this problem....
 
I noticed this morning that when the error message comes up, the program is not physically stopped, merely paused.  Is there a way to get DasyLab to just not tell me that there is a problem, and to carry on as soon as it can?
0 Kudos
Message 1 of 3
(7,447 Views)
Are you using National Instruments hardware? If not, you would need to contact Adept Scientific who distribute DasyLAB.
 
Thanks,
 
KostasB
 
NIUK Applications Engineering
0 Kudos
Message 2 of 3
(7,433 Views)
The hardware driver is important.

DASYLab V10 has a new benchmark feature, which would enable you to see where the program is using its time.

100 Hz with a block size of 16 seems reasonable, but, I recall that some older drivers had a performance "knee" as the sample rate dropped... they would automatically change from the faster "scan" mode, to a more cpu intensive "read" mode. We could diagnose that by suggesting that you increase your sample rate, say, to 250, with a block size of 25 (or, if you need the power of two, 32).


Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.
0 Kudos
Message 3 of 3
(7,426 Views)