It isn't clear what you mean by edges 0 and 1, but *whatever* you mean, a counter task on a USB-6001 isn't gonna be able to get you there.
Meaning 1: edge 0 = rising edge, edge 1 = next falling edge
Your counter cannot be sensitive to both rising and falling edges in the same task. You can count rising edges for a while to estimate average frequency or you can count falling edges for a while to estimate average frequency. But the counter can't tell you anything about the time between rising and falling edges. And that's exactly the info you'd need to determine a pulse width, which in turn you need to determine duty cycle.
Meaning 1: edge 0 = rising edge, edge 1 = next rising edge
This is what you were already doing. If you count for a known amount of time, you can get a decent estimate of average frequency. But since you're only looking at rising edges, you have no way to estimate pulse width.
A more capable device (such as an X-series) would let you do such measurements with extreme hardware-level precision. With the 6001, you can't do them at all with the limited counter. But again, you could possibly acquire the signal with an AI task on the 6001, and figure this stuff out with some fairly straightforward post-processing.
-Kevin P
ALERT! LabVIEW's subscription-only policy coming to an end (finally!). Permanent license pricing remains WIP. Tread carefully.
