Hi Robert,
Thank you for the reply. I actually used that example
as a basis for my test code. The issue is with
similar code in a larger application, that I am using but did not write, which uses events
to "fake" multi-threading data acquisition; allowing the application to perform other actions while data is being acquired. This code is working fine for other NI DAQs, but
is having difficulty with my E series card.
I am discussing this problem with an NI engineer in tech support and it seems the problem is partially related to the DAQ_rate function having been written
before the E series line came out. It is returning an incorrect timebase.
There also seems to be a larger problem with the 6036E DAQCard that has not been confirmed by NI yet
.
The card is having a problem when scanning groups of
channels equal to the power of 2 at a power of 2 frequency, i.e. acquiring from 2, 4, 8, and 16 channels at 256Hz.
It is my feeling the card is rounding up a delay value to a power of two which normally takes care of the delay in multiplexing the channels to one A/D converter (the E series DAQs only have 1 A/D). However, in my situation, using a power of 2 number of channels with a power of 2 frequency, the delay is falling on a power of two so it is not rounding and thus not taking into account the delay. (Or maybe my card is broken).
I'll post back when this gets resolved.
Kind regards,
-Sam