This is a question about the big picture of a frequency to voltage converter. For example when I use this Phoenix Contact MINI MCR-2-F-UI(-PT) f/V converter module with the settings to map a input frequency range 1Hz to 1kHz or 10Hz to 1kHz or 10Hz to 250Hz to 0-10V voltage output I observe better response at output when the input freq. range is smaller. It means better resolution I guess.

Since I dont know the inner mechanisms of the converter Im wondering why it is like that. Is there a way to grasp the idea how this converter works and why it has a better resolution when the input freq. range range is lowered?

Finally can we say the same behaviour for an IC like LM2907?

Im wondering the general working principle so this make one understand why input range and output resolution is related.

  • \$\begingroup\$ I would say it has some MCU counting the frequency and a DAC to output the voltage. \$\endgroup\$ – Eugene Sh. Sep 12 '18 at 17:44
  • \$\begingroup\$ It "could be" analog tach for F/V or PWM/V conversion with DAC setpoints for gain, offset on inputs and outputs, but better with uC with timer counters. What do you mean by better response? ripple? overshoot? \$\endgroup\$ – Tony Stewart Sunnyskyguy EE75 Sep 12 '18 at 18:15
  • \$\begingroup\$ @TonyEErocketscientist For example if I set the input freq. range 10Hz to 250Hz and the output 0-10V; then increasing even 1Hz I observe a change in output voltage. But if I set the input freq. range 1Hz to 1kHz and the output again 0-10V; then the output does not change with 1Hz at some intervals, it needs more freq. increase for output to increase. Im talking about resolution I guess. \$\endgroup\$ – cm64 Sep 12 '18 at 18:18

There are several possible sources of uncertainly and noise in any type of conversion. For this case, there will be error in converting the frequency to a digital value, and additional error in converting the digital value to a voltage.

Frequency to digital

I'm not exactly sure how the device you are using works, but there are a few different ways to make a frequency measurement. Which one is used depends on the application:

  1. Count the number of edges of the input signal occurring during a certain measurement window (gate time).

  2. Using a higher speed clock, count the number of cycles between edges of the input signal. The resolution of this measurement is based on the least significant bit/step size, which is the fast clock period. This could be combined with more specialized analog delay measurements to achieve better resolution. Another way is to calculate the average of multiple such measurements.

  3. Record the voltage vs. time with a relatively high speed ADC, then take an FFT of this data and report the frequency bin with the most power. This is useful if the input either has multiple frequencies combined, or if the input is so noisy that it makes it difficult for the input circuitry to determine the number of edges.

One source of error common to all 3 types is the internal clock (e.g., a crystal). This type of error will probably show up as a temperature-dependent offset below 50 ppm (0.005%). It's probably not the dominant error source in your situation.

The measurement resolution for all 3 types is generally better (smaller) for longer measurement times. Frequency counters sometimes allow you to directly specify the measurement time, but sometimes they calculate the measurement time automatically if you specify the expected measurement range and/or resolution.

Digital to analog

The digital measurement needs to be converted to an analog voltage. It will first be transformed digitally based on the input/output ranges, then sent to a DAC (digital-to-analog converter).

The digital transformation is often a simple linear scaling, but for measurements spanning a large range like this one, logarithmic scaling should be used. For example, using a simple linear scaling from [1 Hz, 1 kHz] to [0 V, 10 V], 10 Hz would only show up as a 0.009 V output, which is too small to generate or measure easily. Instead, a logarithmic scaling would equally space the values 1 Hz, 10 Hz, 100 Hz, 1 kHz within the 10 V range, so 10 Hz would be 2.5 V.

The resolution when using a logarithmic scale will not be a constant. The gain to convert from frequency to voltage will vary with the frequency. Using the example from 1 - 1000 Hz to 0 - 10 V again, the gain at different frequencies is:

  • Near 1 Hz: 1.4 V / Hz
  • Near 10 Hz: 0.14 V / Hz
  • Near 100 Hz: 0.014 V / Hz
  • Near 1 kHz: 0.0014 V / Hz

The DAC itself will add some voltage inaccuracy/noise to the output. Also, if you are converting it back to a digital value (using a DMM or another microcontroller) that will also have some error.


I don't know exactly how the device you are using works (I didn't read the document), but it's possible that if it simply has a set of input frequency ranges to choose from, these automatically affect both the frequency measurement time and the endpoints of the digital-to-analog scaling function.

  • \$\begingroup\$ This answer ignores the linear F/V gain sensitivity which is the problem, and which is the answer, but good info otherwise. \$\endgroup\$ – Tony Stewart Sunnyskyguy EE75 Sep 12 '18 at 19:05
  • \$\begingroup\$ @TonyEErocketscientist - did you see my edited version with the V / Hz values? Is that what you mean? \$\endgroup\$ – Justin Sep 12 '18 at 19:10
  • \$\begingroup\$ sure looks the same in values \$\endgroup\$ – Tony Stewart Sunnyskyguy EE75 Sep 12 '18 at 20:38

This is the F/V gain 100Hz/V for (1-1k)/10V.
and 24Hz/V for 10 to 250 Hz / 10V.

Implementation would be done uC with counter timers for integration of. f or duty cycle and DAC signal conditioner gain, offset for Vout range.

The LM2907 shares the linear Tach function except it is analog with a linear scale. It also has a comparator for output logic level above a certain frequency.
Vout = Vcc × fin × C1 × R1
So it starts from f=0 so you would subtract a small offset for 10 to 240 Hz input to get 0 to 10V out. Tach Error is < 1%.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.