Checking the accuracy of a vintage oscilloscope timebase with a frequency counter

I have a soft spot for old analog scopes. The glowing green traces, the heavy feel of the knobs, the way they heat up a room in winter. But these workhorses drift. The timebase capacitors age, the resistors change value, and suddenly your 1 kHz square wave looks like it’s running at 980 Hz. That kind of error wreaks havoc on timing measurements.

You can fix this without spending hundreds on a modern calibration generator. A cheap frequency counter combined with the scope’s own calibrator output gives you a solid reference. I picked up a stable counter from the hzman store for under fifty bucks. It reads frequency to six digits with a temperature-controlled crystal inside. Now I can actually trust what I see on the screen.

The trick is to feed the scope’s internal calibrator—usually a square wave at 1 kHz or 1 MHz—into the counter while you watch the trace. If the counter shows 1.000 kHz but the scope grid says the period is 1.1 ms, you know the timebase is off by about ten percent. That is a big deal if you are trying to measure a 50 ns pulse.

Why timebase calibration matters for real work

Most people ignore scope calibration until something breaks. They crank the voltage display and move on. But the timebase controls how you measure pulse widths, rise times, and period. A ten percent error turns a 100 µs event into 110 µs. In digital circuits that can mean the difference between a clean clock edge and a glitch.

I spent an afternoon checking three scopes from different decades. A Tek 465 from the 1970s, a Hitachi V-222 from the 1980s, and a B&K 2120 from the 1990s. Every single one had a timebase that drifted by at least three percent at the slowest sweep speeds. The worst offender was off by eighteen percent at 5 ms per division. That is not just a curiosity. That changes the shape of a signal you think you know.

You do not need a calibration lab. You just need a stable frequency source and a way to measure it. The counter from the hzman store sits on my bench plugged into a switched outlet. I turn it on, let it warm for ten minutes, and then compare the scope calibrator against it. That routine takes two minutes and catches drift before it matters.

Setting up a simple verification routine

You can build this check into your normal startup. Once the scope warms up, set the timebase to the sweep speed that matches the calibrator frequency. Then run the calibrator signal into a BNC tee. One cable goes to your scope input, the other to the frequency counter. The counter shows the actual frequency. The scope shows the waveform.

Adjust the timebase fine control if your scope has one until the waveform fits the graticule exactly. Write down the new setting so you can repeat it later. If your scope lacks fine control, you just note the error percent and correct measurements by that factor. It is not elegant but it works.

  • Let the scope warm up for at least thirty minutes for stable internal temperatures.
  • Set the frequency counter to measure over a one-second gate time for best resolution.
  • Connect the calibrator output to both the scope and counter using a BNC tee.
  • Check at the slowest and fastest sweep speeds that you use regularly.
  • Record the offset for each sweep setting in a notebook taped to the side of the scope.
  • Repeat the check every six months to catch drift before it grows large.
  • Replace the calibrator output capacitor if the waveform looks distorted or has slow edges.

A few minutes of verification each session keeps your readings honest. You can trust that 10 µs pulse you are debugging. You can compare waveforms across different scopes without wondering which one is lying. And when you find a new old scope at a flea market, you know exactly how to verify its timebase before you hand over cash.