R
Member
A probe is part of the circuit the moment it touches the board, and on fast edges it lies to you in ways that look like real signal problems. I have chased "ringing" that turned out to be my probe, and missed real ringing because the probe filtered it out. Here is how I choose and how I sanity-check what I see.
First, know what a passive probe does to the signal. A typical 10x passive probe presents about 10 MΩ at DC but only a few pF of capacitance, and that capacitance is what matters: at 500 MHz, 10 pF is roughly 30 Ω to ground. On a high-impedance node that is a heavy load. It rounds off edges, kills overshoot, and can make a marginal driver look clean. If the edge looks suspiciously perfect on a fast node, suspect the probe before you trust the waveform.
Second, active probes solve the loading problem but bring their own traps. Input capacitance drops below 1 pF, which is why they are the right tool above a few hundred MHz. The catch is dynamic range: most active probes clip at a few volts, and the clipping is not always obvious on screen — it can look like a flat top on a signal that is actually still rising. Check the probe's linear range against your signal amplitude before you believe the top of the pulse.
Third, the ground lead is usually the biggest error source. A 6-inch ground clip adds roughly 100 nH, which resonates with the probe capacitance right in the 100–300 MHz band — exactly where probe-induced ringing lives. When I see ringing in that band, my first move is to shorten the ground to a spring tip or a soldered ground and re-measure. If the ringing moves or disappears, it was the probe.
Fourth, compare two probes on the same node. If a passive probe and an active probe disagree on rise time or overshoot, the truth is usually closer to the active probe — but only after you have checked the active probe's own bandwidth and calibration. A quick sanity check: measure a known-good fast edge, like the scope's own calibration output or a reference pulser, with each probe and confirm the numbers make sense.
Fifth, remember the scope itself. Probe bandwidth, scope bandwidth, and the channel's own front end all stack. A 1 GHz probe on a 500 MHz scope gives you a 500 MHz system, not a 1 GHz one. Match the chain to the signal: for edges faster than about 1 ns, I want the whole chain at 1 GHz or better, and I verify it with a reference edge rather than trusting datasheet numbers.
My rule of thumb now: passive probes for power rails and slow control signals, active probes for anything with edges under a few nanoseconds, and a short ground always. What is your go-to probe check when a waveform looks too good — or too bad — to be true?
First, know what a passive probe does to the signal. A typical 10x passive probe presents about 10 MΩ at DC but only a few pF of capacitance, and that capacitance is what matters: at 500 MHz, 10 pF is roughly 30 Ω to ground. On a high-impedance node that is a heavy load. It rounds off edges, kills overshoot, and can make a marginal driver look clean. If the edge looks suspiciously perfect on a fast node, suspect the probe before you trust the waveform.
Second, active probes solve the loading problem but bring their own traps. Input capacitance drops below 1 pF, which is why they are the right tool above a few hundred MHz. The catch is dynamic range: most active probes clip at a few volts, and the clipping is not always obvious on screen — it can look like a flat top on a signal that is actually still rising. Check the probe's linear range against your signal amplitude before you believe the top of the pulse.
Third, the ground lead is usually the biggest error source. A 6-inch ground clip adds roughly 100 nH, which resonates with the probe capacitance right in the 100–300 MHz band — exactly where probe-induced ringing lives. When I see ringing in that band, my first move is to shorten the ground to a spring tip or a soldered ground and re-measure. If the ringing moves or disappears, it was the probe.
Fourth, compare two probes on the same node. If a passive probe and an active probe disagree on rise time or overshoot, the truth is usually closer to the active probe — but only after you have checked the active probe's own bandwidth and calibration. A quick sanity check: measure a known-good fast edge, like the scope's own calibration output or a reference pulser, with each probe and confirm the numbers make sense.
Fifth, remember the scope itself. Probe bandwidth, scope bandwidth, and the channel's own front end all stack. A 1 GHz probe on a 500 MHz scope gives you a 500 MHz system, not a 1 GHz one. Match the chain to the signal: for edges faster than about 1 ns, I want the whole chain at 1 GHz or better, and I verify it with a reference edge rather than trusting datasheet numbers.
My rule of thumb now: passive probes for power rails and slow control signals, active probes for anything with edges under a few nanoseconds, and a short ground always. What is your go-to probe check when a waveform looks too good — or too bad — to be true?
