FYI, you might be able to tweak your vi for ever-so-slightly better sync. Because Ctr7 is being triggered by Ctr6,
you'd usually want to start Ctr7's task before Ctr6's. You've got it the other way. At your pulse rates, Ctr6 will
probably generate a few pulses before Ctr7 is ready to be triggered off one of those falling edges. Your app may
not be sensitive to syncing the 1st pulses but if you *do* need to start them together, start Ctr7 task before
Ctr6.
I also noted that the pulse timing you set up is more like 43% duty cycle. It then seems that your Ctr7 initial
delay should be 350 nsec rather than 380.
Finally, FWIW, the vi I posted would probably work with your existing PCB. Unless you're already using the
board's DIO, there are many pairs of DIO lines and PFI signals that share a pin. DIO port 0 line 0 and PFI0
is one such pair that lets you generate your own hardware PFI0 trigger by toggling the state of DIO 0.0
Another note on the vi I posted is that the "arm start trigger" stuff could probably be replaced by the regular
Start Trigger vi's you used. I'm used to needing to use the "arm start trigger" for counter input tasks and
just tend to use it all the time. Also the stuff in the loop isn't important - it's just meant to provide a gui
display of something that indicates that the pulses are being generated in case it isn't convenient to tap
into the actual 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.
