09-06-2006 03:32 PM
09-07-2006 08:11 AM
The problem is that when you configure a finite pulse train, the driver actually uses both counters to implement it. That's why it isn't available to count edges.
Try the "continuous pulse train" example instead -- then your other counter will be free to count its edges.
-Kevin P.
09-07-2006 09:48 AM
Hi Aida,
I agree with Kevin's analysis. If you look at your example documentation for the finite counter generation, you'll see that the hardware specifications require two counters for that example. Generally, the continuous counter examples only require one.
Great advice Kevin, and I hope that this sheds some more light on your situation.
Regards,
Daniel L.
Applications Engineer
National Instruments