When debugging ADC measurements, it is natural to focus on the input pin: sensor output, divider ratio, front-end filtering.
But the ADC result is not determined by input voltage alone. Reference voltage participates in every conversion.
A more accurate first model is:
ADC code ≈ Vin / Vref * full scale
The ADC reads the ratio between input voltage Vin and reference voltage Vref. If Vin changes, the result changes. If Vref changes, the result also changes.
That is why a sensor may stay still and the input circuit may look unchanged, while ADC codes still move with supply, load, temperature, or board layout.
ADC Does Not Measure Absolute Voltage
For a 12-bit ADC with a 3.3 V reference, full scale is about 4095. With 1.65 V at the input, the ideal result is about half scale:
1.65 V / 3.3 V * 4095 ≈ 2048
If the input is still 1.65 V, but the reference becomes 3.0 V:
1.65 V / 3.0 V * 4095 ≈ 2252
The input did not change, but the code changed significantly.
If the reference voltage rises, the ADC code falls. If firmware treats ADC code only as “the input changed,” it can misread the physical quantity.
Reference Voltage Sets The Code Size
ADC resolution is often described by bit depth, but the voltage represented by one code depends on the reference voltage.
A 12-bit ADC with a 3.3 V reference has:
1 code ≈ 3.3 V / 4096 ≈ 0.8 mV
With a 2.5 V reference:
1 code ≈ 2.5 V / 4096 ≈ 0.61 mV
A lower reference gives smaller voltage per code for the same bit depth. That may look like finer resolution, but it is not free accuracy.
The reference must be stable, low-noise, low-drift, and high enough for the input range. If the input exceeds the reference range, the ADC saturates. If the reference jitters, the lower bits jitter too.
Using Supply As Reference Is Convenient And Risky
Many MCU projects use VDDA, VCC, or system supply directly as the ADC reference.
That is simple, low cost, and often good enough. If the measured signal is generated proportionally from the same supply, the ratio can even cancel some supply movement.
For example, if a potentiometer is connected across VCC, its wiper goes to ADC, and the ADC reference is also VCC:
Vout = VCC * position
ADC code ≈ Vout / VCC
VCC appears in both numerator and denominator, so slow supply movement may not change the position code.
But if the sensor output is an absolute voltage, or the front-end reference comes from another source, using system supply as ADC reference brings supply movement directly into the result.
Typical cases include:
- Battery voltage changes affect sensor readings
- ADC values jump during Wi-Fi transmission
- Motor PWM adds periodic ripple to samples
- USB power and battery power produce different readings
- All analog channels shift in the same direction when a load turns on
In these cases, the problem is not the input pin. The reference voltage itself is moving with the system supply.
Ratiometric And Absolute Measurements Are Different
ADC reference choice depends on where the measured signal comes from.
Some measurements are ratiometric. The sensor, divider, or bridge is excited by the same supply, and its output changes proportionally with that supply. If the ADC reference uses the same supply, slow supply movement can cancel out.
Common examples include:
- Potentiometer position
- Resistor-divider buttons or position sensing
- Some bridge sensors where excitation and ADC reference are shared
- Ratiometric sensors powered by the same supply
The key is ratio consistency.
Other measurements are absolute. The measured voltage itself represents the physical quantity and should not move with ADC reference.
Common examples include:
- Battery voltage measurement
- External analog sensor output
- Absolute voltage after current-sense amplification
- Signals generated from an external reference
- Calibration quantities that must match across devices
Absolute measurements depend more directly on a stable reference. Reference error becomes measurement error.
Internal Reference Is Not Always Better Than External
Many MCUs have internal reference voltage. It is convenient, requires no external part, and may be more stable than system supply.
But internal references have limits:
- Initial accuracy may be loose
- Temperature drift must be checked
- Startup may need settling time
- Noise and load capability are limited
- Device-to-device variation may be large
- Some internal references are intended mainly for self-calibration, not as high-accuracy external references
An external reference can provide better accuracy, drift, and noise, but it is not solved by placing the part. Layout, decoupling, load, startup time, and noise around the reference pin still matter.
So “internal or external” is not a question of advanced versus basic. It is a tradeoff among accuracy, cost, board area, power, and system noise.
Reference Noise Becomes ADC Noise
Noise on reference voltage directly enters ADC results.
If Vref has high-frequency ripple, ADC code jitters too. It can look like input noise, but the source is different.
Common causes include:
- Digital supply noise coupling into analog reference
- Weak reference decoupling
- Reference routing near high-speed digital lines or switching nodes
- Reference load changes
- ADC sampling draws dynamic current from the reference pin
- Reference does not recover between channels or fast samples
This is why some ADC problems look like input jitter but end up being Vref pin noise.
A useful experiment is to connect the ADC input to a stable voltage, or even to half of the reference. If the result still moves with load activity, radio transmission, or digital switching, suspect reference, power, or ground.
Reference Pins Need Layout And Decoupling
Reference voltage is not an abstract number. It reaches the ADC through a chip pin and PCB traces.
The layout around the reference pin affects the conversion result.
Common rules include:
- Place the reference source close to the ADC or MCU reference pin
- Put suitable decoupling near the reference pin
- Keep the decoupling loop short and return it to quiet analog ground
- Route reference traces away from switching nodes, fast digital lines, and high-current paths
- Do not hang unrelated loads on the reference line
- If several ADCs or peripherals share a reference, check load and dynamic current
A high-spec reference source can still perform poorly if the PCB routes it through a noisy region.
Calibration Fixes Bias, Not A Moving Reference
Firmware can calibrate ADC readings.
It can measure a known voltage and correct gain error. It can read an internal reference to estimate current VDDA. It can store factory gain and offset data.
These methods are useful for stable errors.
But calibration does not solve every reference problem:
- Reference voltage ripples with motor PWM
- Radio transmission causes brief reference dips
- Temperature changes create fast reference drift
- Layout noise makes lower bits jump randomly
- Sampling time is not synchronized with load activity
If the reference keeps changing during measurement, a one-time calibration only corrects one moment. It cannot make every later conversion correct.
The fix must go back to reference source, power, decoupling, sampling time, and hardware layout.
Debug Vin And Vref Separately
When ADC readings look wrong, do not check only the input.
A better checklist is:
- Where does the ADC reference come from: supply, internal reference, or external reference?
- Is the measured signal ratiometric or absolute?
- Do
VinandVrefcome from the same supply relationship? - Does
Vrefmove when loads switch? - Is reference startup and settling time sufficient?
- Is reference decoupling and routing clean?
- Is calibration correcting stable error, or hiding dynamic noise?
Useful logs include:
raw ADC code
converted voltage
reference source or estimated Vref
power state and load activity
ADC reference voltage is not a background parameter. It is the denominator of every conversion.
If input voltage stays still but reference voltage changes, the measurement result still changes. Only by looking at Vin and Vref together can ADC readings be interpreted correctly.