LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

pulse width timing /demodulation

Hello,

I'm trying to use labview 7.1 to simulate the behaviour and acquisition of a counter timer board.

I've created a VI which generates a frequency modulated pulse train using the signal generator VI's
and used the timing and transition measurement VI to get the pulse period. Unfortunately, the timing/transition
VI only seems to give a measurement every time the while loop iterates (about once a second), rather than measuring the period of every pulse.

Is it possible to measure the period of every single pulse (with a carrier frequency of around 1000-2000Hz)
to obtain the demodulated signal in Labview?

I've only been using the Labview demo version for a few days so I'm no expert...

thanks!

Tim
0 Kudos
Message 1 of 2
(2,634 Views)
Tim,

If you're going to be working with a TTL-compatible pulse train, the most straightforward solution is to use the hw counter/timers available on the multifunction boards. I've done some apps with a similar carrier freq and the good news is that you can get a reasonable quantization error on your measurements -- 1 part in 10k-20k, which is better than the 1 part in 4k you'd get from a 12 bit analog measurement.

The data acquisition should be done with a counter timer programmed for buffered period or frequency measurement. Under DAQmx, you'd use a DAQmx Timing vi set for "Implicit" to let the pulse train edges act as a variable-frequency sampling clock. You may also need to use a DAQmx property node to specify the appropriate timebase -- on E series you'd want the 20 MHz rather than the 100 kHz. Then the intervals you measure will count ~10k - 20k timebase cycles per cycle of your external pulse train, leading to a fairly low quantization error.

Post back if you need more info on using counter/timers. In the future, you might want to put signal and hw related questions in one of the hw boards. It's probably more likely to get answered sooner.

-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.
0 Kudos
Message 2 of 2
(2,608 Views)