So much for my prior understanding...
If it supports the DAQmx API for controlling the relays in question, I'll *now* guess that you would still have the option to choose either a counter pulse task or a more manually controlled DO task.
Timing for a counter pulse will be *autonomous*, which is often great, but maybe not so much for your particular app. You have to set up pulse timing parameters in advance, and then once you start the task the hardware takes over and controls timing. If you want to choose when to start *AND* stop this digital output, you'd have to do something hacky like define the pulse to be way longer than you'll ever want, and then stop the task when you want to stop the pulse. Yuck!
I agree with others' suggestion that it'd probably be more straightforward to use a regular DO task where you manually decide when to set it High (True) or Low (False) in your app.
The posted code doesn't explicitly set pulse timing parameters so it'll just use defaults. Seems you'd want to define the timing. It also looks *probably* wrong that you repeatedly start the task inside your loop. There's also no indication that you're choosing where to direct the counter pulse output. So again, it'll direct the pulse to the default pin which may or may not be the one you have hardwired. Under DAQmx, one can use a channel property to redirect the output to a desired PFI pin.
-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.
