06-19-2006 05:35 AM
06-23-2006 03:23 AM
Hi Nazri,
Thanks for your post, sorry I'm still a bit unclear what you're trying to do.
Are you generating separate pulse trains on two outputs, then trying to measure them on one input? Are you trying to use digital output lines or counter outputs? Which lines are you using to measure the pulses, and how are you setting up the Data Acquisition?
Could you possibly post what code you are currently using to try this measurement, and exactly how your signals are connected?
Many thanks!
Mark
06-23-2006 03:59 AM
06-29-2006 05:38 AM
Hi Nazri,
Thanks for posting your counter code.
The minimum pulse width you can count using the counters is based upon what source clock you feed the counter, there is a KnowledgeBase about this calculation here:
http://zone.ni.com/devzone/conceptd.nsf/webmain/7C77FB9EDC17C3C386256802007B8AB3
Basically the closer your pulse width gets to the period of the source clock, the less accuracy you can give to the measurment.
The way I see it, if you had 2 separate pulse trains coming into LabVIEW, you could count the pulse widths on both, and then try and do some processing to write them into the same file. The other way you were suggesting is to combine both signals onto the same counter input line, and then just count the pulses in sequence. This sounds like a better way to do the count, but what happens if 2 pulses impinge on each other (happen at the same time)?
What are you currently getting in your text file?
There's a simpler example of reading pulse widths using Traditional DAQ here (which you could use for testing)
Or you could consider upgrading to our newer DAQmx drivers, which simplify most Data Acquisition operations.
Best wishes,
Mark