08-07-2005 06:25 PM
08-08-2005 08:04 AM
08-08-2005 01:53 PM
08-08-2005 06:09 PM
08-08-2005 11:58 PM
08-09-2005 02:04 PM
08-09-2005 03:59 PM
Nick,
I don't have LV on my network PC so I can't look at the code you posted now. Here's a couple thoughts anyhow:
Re: "flipping" between high pulse time and low pulse time. Are you sure you are reading ALL the buffered data, and always in chunks that are a multiple of 2? Exactly how are you "splitting the signal in two?". Once the task starts, the values should alternate properly until/unless you get an error.
Warning: back a few years ago, there wasn't any good way to specify whether to start measuring with the high time or the low time when doing buffered semi-period measurement on E-series boards. It was just random chance for whichever was present when the task was started. If you're still in LV 5, you must also be using the standard "traditional" NI-DAQ driver rather than the newer DAQmx, right? If so, I'm pretty sure you'll be stuck with this indeterminacy.
Note that this is a different effect than the "flipping" which sounded like it occurred part way through a continuous acquisition. This other indeterminacy will make it impossible to predict whether the very first value buffered represents a high time or low time -- unless you can figure it out using other knowledge about your signal's duty cycle.
-Kevin P.