Just to add a few thoughts to Paul's earlier reply:
What he described will help you to generate single pulses from ctr1 and ctr2 with a precision time delay between them. With some care in setting all the pulse specs (high time & low time), you may be able to extend his method by generating a pulse train on ctr0 (rather than a single pulse) which can in turn cause ctr1 and ctr2 to generate pulse trains with that same precision time delay between them. In either case, ctr1 and ctr2 would need to be configured for re-triggerable (single) pulse generation. So long as ctr0 keeps re-triggering them at a constant rate, they will keep producing single pulses at a constant rate. To the rest of the outside world, ctr1 and ctr2 will look like they are generating continuous pulse trains.
Again, it takes some care to get all the pulse specs right -- if you can describe your specific timing needs, I could help you to get them defined properly.
Also just to let you know that your first post was correct as far as it went -- only 1 signal's active edge can be designated as a digital start trigger for continuous counter tasks. If you have multiple counters in multiple continuous tasks, they would need to share that one trigger signal's edge. However, because the counters are quite flexible, there are often ways to work around this limitation. Here ctr1 and ctr2 are used in a re-triggerable single pulse mode, so they can be re-triggered by different edges of a single signal from ctr0. It would also be possible to have them re-triggered by 2 independent signals.
-Kevin P.
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
