ssboisen
2007-02-20 10:40:11 UTC
Hello,
I have a VI where I'm using two DAQ, one for input and one for output. Following some calculations (detecting a trigger) on the input I need to stop the output VI without stopping the loop they are both in.
I tried using the stop (T) input but with no luck, when I link the result of the trigger to the stop(T) input I get an error after running the VI for a few seconds.
Error -200279 occurred at DAQmx Read (Analog 1D Wfm NChan NSamp).vi:2
Possible reason(s):
Attempted to read samples that are no longer available. The requested sample was previously available, but has since been overwritten.
Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem.
Property: RelativeToCorresponding Value: Current Read Position
Property: OffsetCorresponding Value:
Task Name: _unnamedTask<14>
If I link the result of the trigger to the stop-loop (Loop Condition) input it stops when the trigger is found, but I would rather have it just stop the output DAQ and not the main loop.
Gemme5_test.vi:
http://forums.ni.com/attachments/ni/170/230960/1/Gemme5_test.vi
I have a VI where I'm using two DAQ, one for input and one for output. Following some calculations (detecting a trigger) on the input I need to stop the output VI without stopping the loop they are both in.
I tried using the stop (T) input but with no luck, when I link the result of the trigger to the stop(T) input I get an error after running the VI for a few seconds.
Error -200279 occurred at DAQmx Read (Analog 1D Wfm NChan NSamp).vi:2
Possible reason(s):
Attempted to read samples that are no longer available. The requested sample was previously available, but has since been overwritten.
Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem.
Property: RelativeToCorresponding Value: Current Read Position
Property: OffsetCorresponding Value:
Task Name: _unnamedTask<14>
If I link the result of the trigger to the stop-loop (Loop Condition) input it stops when the trigger is found, but I would rather have it just stop the output DAQ and not the main loop.
Gemme5_test.vi:
http://forums.ni.com/attachments/ni/170/230960/1/Gemme5_test.vi