02-18-2006 02:44 PM
02-20-2006 04:39 AM
02-21-2006
12:16 AM
- last edited on
11-17-2025
10:09 AM
by
Content Cleaner
Hey there Starcha,
To clarify for you here is what each of those VIs is for:
DAQmx Timing: This sets of all of the timing parameters of your task (i.e. acquisition). Timing parameters such as if you are doing a finite acquisition, or a continuous one, what sample rate you are acquiring at if you are doing hardware timed, things of this nature. Basically everything involved how you are acquiring things in relation to time.
DAQmx Read: This actually reads the values of you acquisition into LabVIEW and gives them to you. So if you were doing a hardware timed, continuous acquisition and thus buffering all of you readings, this VI would go in and grab a specified number (Samples to Read) of samples out of the buffer and import them in to LabVIEW so that you can do with them what you want.
You can find out the specifics of what each input and output mean for these VIs by using the context help (Ctrl-H to enable) and over you mouse over the VI in question, then press "click here for more..."
Generally both these VIs are called when setting up a DAQ task. You will set up the timing VI first, then down the line when you are reading to read some values into LabVIEW then you will use the read VI.
What Kay said is correct if you are doing a finite acquisition, but not the case if you are doing a continuous acquisition. If you are doing continuous acquisition then Samples to Read sets the number of samples to grab out of the buffer every iteration of that DAQmx Read (which will be in a while loop).
I hope that this clears things up for you, and answers you questions. If any of that was unclear or I didn't answer your question feel free to post back here.
Best of luck,
-GDE