LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Truncated response of the received signal

Solved!
Go to solution

Hi,

I am generating a signal with 15k samples at the sampling rate of 1.5M through a transducer in the water tank , but while receiving the signal through the channel with the same number of samples and at the same sampling rate the signal is getting truncated(The received signal should be of 0.1 milliseconds but I am receiving the signal of 0.975 milliseconds) Can anyone explain why is it so?

Please find the attached Received signal and block diagram image.

Download All
0 Kudos
Message 1 of 4
(2,281 Views)

Acquiring 15k samples at 1.5 MHz requires (15 e 3) / (1.5 e 6) = 10 e -3 = 10 ms, not 0.1 ms.  Your figure shows a signal that could be 9.75 ms, not 0.975 ms.  What effect does the filter have on your signal?  Have you examined the size of the waveform going into the filter?

 

Note that posting a picture doesn't allow us to examine your code for certain errors -- we need to be able to examine the VI, as well.  

 

Bob Schor

0 Kudos
Message 2 of 4
(2,247 Views)
Solution
Accepted by topic author rashp8

I share Bob's questions about the filter -- many of us long-time LabVIEW'ers tend to avoid express vi's because they're more *opaque*.  That is, their behavior isn't fully specified by the inputs visible on the diagram, there are also other "hidden" settings that are changed with a gui interface when you double-click them.

 

I'll add another guess.  You didn't identify your DAQ device, but it may not support an exact 1.5 MHz sample rate.  You may actually be getting a different sample rate that's as close as device can manage.   What's the "dt" value on the direct waveform output from DAQmx Read?  It will indicate the actual sample rate, which is sometimes different than what you asked for.

 

For example, consider an old E-series device with a max timebase of 20 MHz.  When you ask for 1.5 MHz sampling, the device needs to try to achieve that using an integer divisor of 20 MHz.  The *accurate* divisor is 13.3333333.  However, the device will *need* to use a neighboring integer, either 13 or 14.  A divisor of 13 would yield the slightly higher sample rate 1.538 MHz.  (I don't know the algorithm for how DAQmx chooses whether to round up or down, but it *will* behave consistently for a given requested freq).

 

It turns out that 15000 samples at 1.538 MHz takes -- TA DA! -- 0.975 seconds.

 

 

-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.
Message 3 of 4
(2,238 Views)

Thanks 

The DAQ device was not supporting exact 1.5MHz sample rate

0 Kudos
Message 4 of 4
(2,225 Views)