Hi Will,
I'm at a network workstation w/o LabVIEW so I can't show an example right now. The earlier code picture I posted showed two alternate methods for sync'ing a counter pulsetrain with AI. The top section generates the pulsetrain, the middle section shows a method where one AI sample is taken for each pulse, and the lower section is the method where the first pulse triggers the AI to start sampling at the rate and duration you choose. The lower section sounds like what you'd need. You would just put those 2 lower vi's in place of the Sample Clock one in the middle.
There's a way to be able to stop and re-start a triggered AI under DAQmx without clearing and re-configuring the entire task. I *think* you have to use one of the more advanced DAQmx Task control vi's to either 'reserve' or 'commit' the task before you 'DAQmx Start' it. Then when you 'DAQmx Stop' the task, you can quickly 'DAQmx Start' it again without any further configuring. As I recall, only one of those options will actually work. Or maybe one was just a lot faster.
Anyway the point of all that is to alert you to methods that will get you ready for the next triggered AI acq as soon as possible after finishing the previous one. Even if you don't need to worry about it for this app, the day will come...
-Kevin P.
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).