05-28-2020 06:02 AM
@NickUoA wrote:
It would be nice to have timestamps to the values. Not system time though, like the time it took to make that measurement. I suppose I could just make that myself by doing 1/Sampling rate. I suppose it's accurate enough?
It is more accurate than timestamps if you are sampling with DAQmx hardware, which are designed with crystal-controlled clocks to sample at precise time intervals. Timestamps are obtained from the Windows "clock", and can be affected by all of the things that Windows is trying to do at the same time.
Bob Schor
05-28-2020 08:42 AM
This topic is being briefly interrupted to plug my Idea Exchange suggestion that the status quo leaves a lot of users confused about the relationship between the "# samples" designated in the call to DAQmx Timing and the "# samples" designated in the call to DAQmx Read. (Not to mention the further relationship with sample rate and reading loop rate that Bob just discussed very cogently, *AND* the fact that things change fairly drastically between Continuous and Finite sampling).
We now return to your regularly scheduled topic.
-Kevin P
05-28-2020 05:07 PM
Hi Kevin,
Thanks for linking your post. I agree, the terminology can get really confusing between finite and continuous sampling, especially if you're relatively new to using the DAQmx. Perhaps NI staff will pick it up soon and perhaps update the terminology itself or maybe the help documentation.
Cheers,
Nick.