The code I posted is only meant to *illustrate* some key points, not to be a complete end solution. I wasn't trying to think about your specific pin assignments, only trying to show how to export a counter output to one of the PFI pins that's allowed to be configured for output.
Note: a counter task is *not* a DO task. These counter pulsetrain tasks require the use of NO timing engines from the cDAQ chassis -- that's just one of the advantages of doing this with counter tasks.
In the code I posted, one counter pulsetrain is based on time, the other is based on an external signal (which can be an encoder) known as the 'source of ticks'. You can do things either way. (Actually, the time-based API is just a programming convenience. Internally, the counter always *really* works on Ticks. But when you don't specify an external 'source of ticks', it uses one of its own constant-rate internal timebases, and then it knows how to convert your timing specs into the Ticks it *really* uses.)
My advice:
- work on each element individually before trying to bring them all together. For example, configure just 1 counter pulsetrain that uses the encoder as its 'source of ticks' to generate pulses for your camera. Focus on just the camera until you're sure that the frames are synced to the correct CAD position.
- if the spark or injector pulses need to have pulse widths that are precise in time but with a start position that's sync'ed to CAD, you'll need a helper counter. (And if they're at different CAD positions, the earlier one may need to act as the helper for the later one.) The thread I linked in turn has a link to an earlier thread where I illustrated how to do this. You could extend the idea to make the 2nd counter act as a trigger for a 3rd.
-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.
