Since you show both AO tasks and your AI tasks having the same sample rate, you could get rid of all the unnecessary trigger stuff and simply share the AI sample clock.
Your call to DAQmx Timing.vi for the AO tasks would specify "/PXI1Slot2/ai/SampleClock" as the clock source. You've already got the necessary sequencing in place to make sure the AI task starts last.
Another method I tend to prefer is to make a counter pulse train output task that my other tasks use as their sample clock. This lets me do things like generate AO on the *leading* edge of the clock while capturing AI on the *trailing* edge. This gives the system a little time to respond to the new AO value before capturing the AI response. With a counter pulse train, I can control the duty cycle to maximize the amount of time available for system response while still getting all my AI done before the next AO update.
-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).
