04-28-2010 12:50 PM
04-28-2010 04:31 PM
Hi HeaveHo,
the DAQmxStartTask does actually start the task on the hardware. The read simply reads the value from the buffer on the DAQ board. You will not have the width of your pulse until the DAQmxReadCounterScalarF64() is called. If you have both of your counter tasks started before your pulse arrives and an appropriate timeout is given, you will be able to capture the width of two different pulses on seperate lines. I hope this helps clear things up!
Regards,
03-18-2011 12:22 PM
I am experiencing the same problem. Did you manage to resolve it ?
03-18-2011 04:07 PM
Hi nap3n,
What Dustin said is true of buffered tasks, but it sounds like the original poster is using an on-demand counter task, which is where the device starts counting when you call DAQmx Read. I think your best bet might be to use buffered tasks by calling DAQmx Timing (Implicit) like in the Meas Pulse Width-Buffered-Cont example. It may also be helpful to synchronize their arm start triggers, though implicit timing will still cause them to drift apart depending on the input signals.
Brad