I'm working with a counter sequence that acquires data from a photo-detector. Quite often, while running the program, this error code is displayed:
Error – 200278 ocurred at DAQmx Read (Counter 1D U32 1Chan NSamp).vi
Possible reason(s):
Attempted to read a sample beyond the final sample acquired. The acquisition has stopped, therefore the sample specified by the combination of position and offset will never be available.
Specify a position and offset which selects a sample up to, but not beyond, the final sample acquired. The final sample acquired can be determined by querying the total samples acquired after an acquisition has stopped.
Attempted to Read Sample: 0
Property: RelativeTo
Corresponding Value: Current Read
Position Property: Offset
Corresponding Value:
Task Name: _unnamedTask<240C>
I do believe it has to do with the timing from different sequences within the program. The clock for the counter is ruled by data-acquisition-card, while other sequences —such as writing (data)— are governed by the computer (not-a-reliable chronometer!). Thus, both processes may entangle when the program is running. Do you think that's the problem? Any idea to avoid this issue? About the frequency peaks: I'm calibrating the equipment right now —photo-detectors are turned off—, but sometimes, while running the program, there are some peaks displayed in the graph that I can't simply explain. I believe it's just noise, but I'm not quite sure. Is there any way to prevent these frequency peaks?
Message Edited by Liwk on 04-21-2009 12:02 AM
