LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does my frequency measurement double

I have a Low-Frequency 1 Counter measurement in a VI that I wrote. There are two of them in the same program, and one of them reads accurately at ~118 Hz. The other one occasionally doubles the frequency. The true signal is ~30Hz, but the display reads 60Hz half the time. What am I doing wrong and how can I fix it?

 

 

0 Kudos
Message 1 of 6
(3,696 Views)

you may need to look for "aliasing"

0 Kudos
Message 2 of 6
(3,693 Views)

To my knowledge "aliasing" occurs to do undersampling a signal, and results in an apparently lower frequency. If the program has no problem distinguishing 118 Hz it is not undersampling 30 Hz. The frequencies stated have been measured by oscilloscope.

 

0 Kudos
Message 3 of 6
(3,690 Views)

Try tracking the delta time between your freq checks. I fmemory serves me that VI accepts a delta time input that if not provided by the caller will be calcualated by the driver based on when it THINKS it was last checked.

 

Trying to help,

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 6
(3,686 Views)

adding to the above...

 

a low pass filter (if availabel on borad for your widget) may help if the is a mismatch between the output/input impeadance resulting in reflection or "rining" which could give you multiple counts per unit time.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 5 of 6
(3,677 Views)

Ben wrote:

a low pass filter (if availabel on borad for your widget) may help if the is a mismatch between the output/input impeadance resulting in reflection or "rining" which could give you multiple counts per unit time.


That's exactly the issue I had about 15 years ago reading pulses from an instrument. A simple termination resistor at the input eliminated the problem.

0 Kudos
Message 6 of 6
(3,665 Views)