I was recently in a thread that may help get you started. Here's a link.
The basic concept is that counter A is configured to generate several identical pulses, but will only do it when the other counter, counter B, is in the high state. Counter B is also configured to generate pulses, and you carefully control the time it spends in the high state and in the low state. The net effect is that you get your burst of several short identical pulses from counter A, and they can be initiated at whatever interval you choose.
You can even choose to change that interval on the fly, though some care is needed. Specifically, once you change the pulse timing on counter B, you must let it generate a full pulse with those settings before you change the settings again. Attempts to change them too early will produce an error. I suspect, but cannot absolutely verify, that it won't be possible to make every single pulse cycle have different timing paramaters. At best (I suspect), you can change them on every 2nd cycle.
There is a DAQmx property node that will allow you to query Counter B's task to determine when it is ready to receive new pulse timing values. It's buried *very* deep in the property menu hierarchy. I'd look first under a DAQmx Channel property node, though it could possibly be under Timing or Write property nodes. Sorry, I'm not near an LV PC to check.
(Update: look at this posting for more info...)
-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.
