ADC Averaging / Oversampling
Estimate noise reduction and effective resolution (ENOB gain) from averaging or oversampling + decimation.
How to Use
- Pick a mode: Averaging (noise reduction) or Oversampling (extra effective bits).
- Enter ADC parameters (bits + Vref) if you want LSB sizing, and enter noise in LSB or volts.
- Set Samples (N) or choose a target Extra bits and let the tool solve for required N.
- Use “Show Work” to see formulas and step-by-step math in base units.
Important: Oversampling improves effective resolution only when there is sufficient noise/dither and proper low-pass filtering before decimation.
Show Work (step-by-step)
Reference
These are common, practical relationships used for quick engineering estimates.
- LSB size (ideal):
LSB ≈ Vref / 2^bits - Averaging noise reduction:
σ_out ≈ σ_in / √N - Oversampling ENOB gain (rule of thumb):
Δbits ≈ 0.5 · log2(OSR) - Samples required for Δbits (rule of thumb):
OSR ≈ 4^(Δbits) - Decimated output rate (typical):
F_out ≈ Fs / N
FAQ
Does averaging always improve resolution?
It reduces random noise (roughly by √N). If your dominant error is DC offset, drift, or quantization with
insufficient dither/noise, the improvement may be limited.
Why does oversampling need noise?
Oversampling + decimation relies on noise/dither to spread quantization error so averaging can reduce it. With a perfectly static signal and too little noise, extra “bits” won’t appear.
What’s the quick rule for extra bits?
Roughly +1 bit → 4× samples, +2 bits → 16×, +3 bits → 64×.
That’s the OSR ≈ 4^(Δbits) relationship.
Is “Fs/N” always the output rate?
For a simple block average / decimation by N, yes. For more complex filters or overlapping windows, it depends. This page uses the common decimation estimate unless you implement something else in firmware.
Tool Info
Last updated:
Updates may include filter options, edge-case handling, and export formats.