Yeah, the method for reversing polarity was one of the quirks of moving from Trad. NI-DAQ to DAQmx. Under the traditional drivers, you defined a pulse as a delay interval followed by a pulse interval. You didn't explicitly set a high time and a low time. The counter would be in its idle state during the delay and in active state during the pulse. To define polarity, you would set a single parameter (I don't remember the syntax anymore...), and then the driver would figure out how to map from delay/pulse to low/high.
I think the high time / low time terminology of DAQmx is more universally understandable, but there are occasions where it slightly complicates the configuration of output pulses. A couple careers ago, I was putting together apps for automatic motor testing that often used a PWM-based speed control. Some motors had active high PWM and others were active low. In traditional NI-DAQ, this was actually a little simpler to accomodate than if I were doing it now with DAQmx. Not that I want to go back or anything -- DAQmx's advatages far outweigh the relatively few inconveniences.
Sorry for the ramble, we now return you to our regularly scheduled inquiries...
-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.