Ripple complaints: finding the noise before your customer does
Of all the ways a charger can disappoint, ripple is the sneakiest. Voltage wrong? The device complains immediately. Protocol missing? It charges slowly. But ripple is quieter than that: the charger works, the phone charges, everything on the bench looks fine — and somewhere in the field a customer's speaker hums or a screen stutters while plugged in.
What ripple actually is
A charger's job is to deliver smooth DC. No switching circuit does that perfectly — a small AC residue always rides on top of the DC output. That residue is ripple. In small amounts it is normal and harmless; every real charger has some. In excess it leaks into the device being charged, and that is where the complaints come from: audio circuits pick it up as hum, displays pick it up as visible jitter or flicker, sensitive electronics misbehave in ways that look like software bugs.
The trap for QC is that ripple is load-dependent. A unit can look clean at low load and misbehave near its ceiling. Spot-checking one point tells you almost nothing about the curve.
Why the customer finds it first
Three reasons, in practice:
- Sampling misses it. If ripple is not on the mandatory test list, it is only discovered when someone happens to look — usually after a complaint.
- The symptom is ambiguous. A humming speaker or a jittery screen reads as a device problem. Nobody connects it to the charger until the charger is swapped and the noise follows it.
- Locating the source without a waveform is guessing. Swap the adapter, swap the cable, swap the port — each swap is an hour, and none of them shows you the actual noise.
What real-time capture changes
A bench with ripple measurement shows you the output waveform at each load point, live, while the unit is still on your line. Instead of a number after the fact, you see the curve: clean at mid load, spiking near the ceiling — and now you know exactly which operating point to fix. What used to be a week of internal back-and-forth becomes one look.
Models in this series carry ripple measurement built in — the GTI6028H/A on a 60V/10A/150W range, with OCP over-current protection alongside, and the GTI6030H and GTI6031H above it. Combined with external trigger, ripple checks can run as part of the automated sequence rather than a separate manual step.
Ripple belongs next to OCP and protection validation, not after them as an optional extra. A charger can pass voltage, current and protocol checks and still be the noisiest unit in the batch. If your destination market includes audio equipment or display devices, treat ripple as a mandatory pass/fail line — and record it per unit, so a field complaint has a curve to compare against.
The customer's half of the story
When the complaint does arrive, a recorded ripple history is the difference between debugging and answering. You either have the curve for that batch and can compare it against the field unit — or you start swapping parts and hoping. The benches that record it per unit make the second option unnecessary.