I'm pretty sure you're going to find that you need to do this indirectly. Although you *could* configure the finite AI task to be retriggerable, you'd also need to retrieve all your samples from the task buffer in the ~100 microsec after one finite acquisition completes and before the next triggering signal. I wouldn't count on that working out reliably.
A different approach is to configure a counter task to generate a retriggerable finite pulse train that acts as the sample clock for the AI task. The counter can be set to generate 100 pulses at 1 MHz in reaction to each trigger and the AI task can use counter output as its sample clock. (The AI task should be started *before* starting the counter task.)
You could then further declare the AI task to be continuous so you'll be free to retrieve the data at a more leisurely pace. Maybe retrieve 50k samples at a time so your Read loop can iterate 10 times a second? Then you can rearrange them into 500 separate subsets of 100 each if needed.
-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).
