Ideally, I would like a timed loop, or 1 sample on demand with a timer. I played with 10, 20 , 50, 100, and 200 samples to read, but they all come with a 2-12 sec lag between sample groups. at least the continuous samples have no data loss. all channels are sampling at 100/sec with only a few ms lag between DAQ units. I didn't try it earlier mainly b/c every sample code I see is with the task being passed into the loop. Maybe an on demand setup with an inline timer being passsed into the loop? For now, I am up and running, but as I add more features, the producer loop structure may become more critical. I think the way I pass the task into the loop is the issue. Going back to what you said earlier, it's almost as if the task is recreated after n samples are taken. more channels, more lag. For example, using my test setup of one channel, I monitored items in Queue in producer and consumer loop. producer set @ 100/sec and consumer on timed loop. when the consumer timing matched the data gaps (31ms), the enque and deque numbers match. that means to me that the que was only recieving data at 31ms increments, despite the higher rate of 100/sec. regardless of the final issue, I learned quite a bit and using continuous samples gets me running, giving me the time to tweak this, so thank you for the time you are investing into this discussion.
