ECParts Toolkit LogoECParts Toolkit

Oscillators Guide

Measuring Oscillator Frequency: Counter Timebase, Loading, Drift, and PPM

An oscillator can meet its ideal design equation and still appear out of tolerance on the bench. Separate the device behavior from counter reference error, gate resolution, probe loading, and test conditions before adjusting components.

10 min · Intermediate · Updated October 18, 2026

Start with the Frequency Acceptance Condition

The Oscillator Design Fundamentals Guide covers networks, startup, and tolerance budgeting. This guide is a measurement protocol. State nominal frequency, permitted offset at each temperature and age, supply and load, warm-up interval, expected output amplitude, and measurement averaging time. A 1-second counter result, a 10-second average, and a production temperature sweep answer different questions. Distinguish initial accuracy from frequency change with temperature, long-term aging, short-term stability, jitter, and phase noise.

Formula reference

Signed error and a simple counter limit

error_ppm = 10^6 (fmeas - fnom)/fnomDelta f = fnom error_ppm 10^-6fcount ≈ N/Tgatedirect-count quantization ≈ ±1/Tgate Hz (one-count estimate)

Variable definitions

fmeas and fnom must use the same frequency unit
N is integer cycles counted in gate duration Tgate
The one-count term is not the entire counter uncertainty
Use instrument-specific specifications for reciprocal counters and calibrated timebases

Do Not Confuse Resolution with Accuracy

A direct counter opens a gate controlled by its reference and counts input edges. An asynchronous gate boundary may contribute about one count of uncertainty. At a 1-second gate that is about ±1 Hz; at 10 MHz it corresponds to about ±0.1 ppm for this ideal quantization term. A 10-second gate reduces that term to about ±0.1 Hz, but does not remove a 2 ppm timebase offset or a drifting oscillator. Some instruments use reciprocal methods with different resolution behavior; follow the instrument manual, not the direct-count formula, when reporting a traceable result. Verify reference calibration and external-reference lock where used, and record the instrument serial number and reference state.

Worked comparison: nominal 10,000,000 Hz and a stabilized reading of 10,000,250 Hz imply +25 ppm. If the counter reference has a bounded ±2 ppm accuracy at the test conditions, claiming exactly +25.0 ppm for the device is unjustified without accounting for that reference contribution. The Oscillator Frequency Tolerance & PPM Calculator converts the measured offset and builds a stated budget; it does not certify the counter.

Avoid Measuring the Wrong Oscillator

Probe the buffered output or a specified test node where possible. A passive scope probe adds capacitance, and a frequency-counter input has finite impedance; either can alter a crystal load network, high-Q LC tank, or RC timing node. Measure input loading or estimate its size before connecting. Use an appropriate active probe or buffer if the node is high impedance, and compare readings with and without the probe when practical. Keep the output termination consistent. At low amplitude or slow edges, trigger threshold and noise can produce missed or extra counts. Check waveform shape and threshold with a scope before trusting the numeric readout. Oscillation that stops when probed is a loading problem, not evidence of a zero-frequency design.

MethodMeasured quantityPrimary caution
Direct frequency countCount input cycles during a known gateTimebase and ±1 count are separate limits
Reciprocal or period countMeasure time over one or many input periodsCheck trigger noise and timebase resolution
Scope period estimateRead repeated edge intervals on a calibrated scopeTimebase, trigger, and sampled waveform matter
VCO sweepFrequency versus controlled tuning voltageRecord load, temperature, hysteresis, and local slope
Temperature/aging runFrequency against temperature or elapsed timeKeep warm-up and reference stability distinct

Sweep Temperature, Supply, Load, and Tuning Deliberately

Hold the device at each temperature until its relevant internal or board temperature has stabilized. Record frequency, supply, output load, control voltage, warm-up time, and reference-clock status together. A temperature chamber air setpoint is not necessarily the crystal or board temperature. Separate reversible temperature behavior from aging by repeating a reference condition after a sweep. If testing a VCO, measure several tuning points in both upward and downward directions, then use local differences to estimate gain. For example, 100 MHz at 1.0 V and 110 MHz at 1.5 V give an average 20 MHz/V over that interval; this is not proof that the slope remains 20 MHz/V over the full tuning range. Use the VCO Frequency & Gain Calculator to document the selected points and expected local span, then inspect actual curvature and hysteresis.

Formula reference

Local tuning slope

Kvco,local ≈ (f2 - f1)/(V2 - V1)ppm at a condition = 10^6 (fcondition - fnom)/fnomworst-case bound <= sum of bounded absolute error terms (when each can align)

Variable definitions

V2 and V1 are the actual measured control-node voltages
A local secant slope need not equal small-signal gain everywhere
Systematic offsets, drift, and random measurement uncertainty need separate accounting
Worst-case addition is conservative; RSS needs justified independent random terms

Keep an Uncertainty Ledger

List counter timebase accuracy and calibration age, gate/count resolution, trigger sensitivity, probe pulling, output termination, temperature sensor placement, warm-up stability, supply measurement, and repeatability. Classify each item as known offset, bounded systematic term, or random variation. A calibration can remove a measured offset at one condition but does not erase future drift. For a conservative pass/fail decision, compare the whole bounded range with the specification; if the range straddles the limit, improve the measurement or apply a documented guard band rather than calling the part good or bad from displayed digits alone. This Guide does not calculate phase noise or Allan deviation; use specialist methods when those are the actual requirements.

  • Check the counter timebase specification at the actual calibration, warm-up, and temperature conditions.
  • Capture the raw frequency series, not only its rounded average.
  • Record probe and termination settings and repeat the test after removing the probe where feasible.
  • Run supply and temperature corners after the nominal operating state is stable.
  • For VCOs, label each local gain interval and the tuning direction.
  • Do not add signed deterministic offsets as if they were independent random noise.

Common Mistakes

  • Trusting display digits without checking counter timebase accuracy.
  • Assuming a longer gate removes oscillator or reference drift.
  • Connecting a high-capacitance probe directly to a crystal or LC tank.
  • Using an unstable trigger threshold on a noisy low-amplitude output.
  • Comparing readings taken at different loads or supply voltages.
  • Comparing chamber air temperature with a datasheet crystal-temperature limit.
  • Calling one VCO endpoint slope the gain across the entire tuning range.
  • Reporting absolute ppm without preserving the sign of the measured error.
  • Combining systematic and random error terms without an uncertainty model.
  • Confusing mean frequency accuracy with jitter, phase noise, or short-term stability.

Measurement Sources

NIST Frequency Measurement addresses accuracy, stability, instrumentation, and reporting terminology. The NIST Time and Frequency Users Manual describes counter timebase and gate behavior. Instrument-specific specifications remain authoritative for an actual test setup.

Support reference

FAQ

Why does a frequency counter need an accurate timebase?

The counter measures the input against its own time reference. Its reference error contributes directly to the reported frequency even if the input counting resolution looks fine.

What does gate time change?

For a simple direct-counting counter, a longer gate reduces the approximate one-count quantization limit in hertz. It does not correct timebase inaccuracy or oscillator drift during the gate.

Is a displayed 10.000000 MHz reading necessarily accurate?

No. Display digits are resolution, not traceable accuracy. Check the timebase calibration, gate or reciprocal-counter method, trigger, loading, and uncertainty.

Why can an oscilloscope probe change oscillator frequency?

Probe capacitance or resistance can load a crystal, LC tank, or high-impedance RC node and pull its frequency or disrupt startup. Prefer an isolated buffered output where available.

How do I convert measured frequency error to ppm?

Use signed ppm = 1,000,000 times (measured frequency minus nominal frequency) divided by nominal frequency, with both frequencies in the same unit.

Can I add counter uncertainty to oscillator limits?

For a conservative bound, keep systematic offsets and individual bounded errors explicit. Do not use root-sum-square unless the terms are suitably independent random contributions and the result is labeled as a statistical estimate.

How should I measure VCO gain?

Record stabilized frequency at several control voltages under a fixed load and temperature, then calculate a local slope between adjacent points. A single endpoint slope can hide nonlinearity or tuning limits.

Is frequency accuracy the same as jitter or phase noise?

No. Average frequency offset describes mean rate over a measurement interval. Jitter and phase noise describe timing or spectral fluctuations and require appropriate measurement methods.

Summary

Measure a buffered oscillator output against a known reference, state the gate or reciprocal method, and control loading, trigger, warm-up, temperature, and supply. Convert offset to signed ppm only after instrument uncertainty is understood, and distinguish average frequency from stability and noise.