12-13-2007 05:17 PM
12-14-2007
03:50 PM
- last edited on
04-29-2025
03:05 PM
by
Content Cleaner
Hello,
Are you specifying a fixed number of Samples to Read or using the read all available samples with the DAQmx Read.vi? You stated you played with the rate and the samples. Does this mean that you changing the Sample Rate and Samples per Channel on the DAQmx Timing.vi?
Since you stated that the samples available to read is always 10 on the development machine, I would assume this is reflective of your buffer size set by the Sample Rate and Samples per Channel on the DAQmx Timing.vi. It could be that you are pulling too slowly from your buffer with the Read function and the buffer is set to a size around 10. Thus, you don’t see the value increase over time past 10 but it’s still overwriting.
Another option to look into is if there is anything else in your program that is prolonging the time in-between the Start Task and Read functions. This could be solved by using the error outputs to control the flow of the program. To learn more about dataflow in LabVIEW, refer to the LabView Help. Try to make sure that the last function executed prior to entering the loop that contains the Read function is the Start Task function. You can run highlight execution also to help further troubleshoot.
12-14-2007 04:10 PM
Thanks for the info.
I actually got it to work today by playing with the sample rate and samples per channel settings. I increased the samples per channel to read by 2x, and it worked.
It was fustrating because it would work in the LV environment, but not on the target computer. That made it hard to debug. But I got it.
Thanks,
Vinny