Not sure what you mean by "drift" exactly, but since both counters work off the same board and the same internal timebase, you're certainly in position to have consistent relative timing.
I only see two things to comment on, the former much more important than the latter.
- you have a curious combination of defining your gating pulse to be retriggerable, but also *not* to use a start trigger. I'm not sure what should happen there, but I'd be inclined to expect a single untriggered pulse to occur as soon as you run it.
- you never clear the task that generates the gating pulse. Auto-cleanup will take care of this when execution ends, but it'd be better to clear it explicitly. Not likely to be a contributor to your issue though.
-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.
