Where DL4ZAO’s “Balun” PDF Derails

A reader asked us to review this, so we did, based on the RF.Guru articles and lab notes we’ve published over the past 4 years.

The source document is DL4ZAO’s “Balun-Workshop” workshop handout, available here. (We’re not reproducing slides, drawings, or chunks of text. This is a practical technical review of definition and measurement traps that mislead people in real stations.)

The thesis

DL4ZAO’s PDF is clearly meant as an educational workshop handout. Much of it is useful as an introduction, but it goes off the rails when it mixes definitions and measurements across different “scopes” and then treats the result as portable truth for real stations.

The most common failure mode in older balun/choke writeups is not “wrong math.” It’s category errors:

• Mixing differential antenna current (the wanted radiator current) with feedline common-mode current (the unwanted outside-of-coax current).
• Using a tidy 50 Ω lab fixture and then making claims about a non-50 Ω common-mode ecosystem.
• Measuring differential insertion loss and calling it common-mode suppression.

What the PDF gets right (and why it feels convincing)

To be fair: the PDF lands several fundamentals that many operators never get taught properly:

• The “inner shield vs outer shield” idea (skin effect) as a useful mental model for how common-mode can exist on coax.
• The practical symptom list: TVI/EMI, noise pickup, “hot shack,” and why a current choke matters.
• The split between current balun (choke behavior) and voltage balun (transformer behavior), including the key point that a voltage balun does not inherently stop common-mode.

Where we differ at RF.Guru is not the basics... it’s discipline. We keep the definitions and the measurement scope consistent all the way through, because that’s what makes results transfer to real stations.

Myth vs reality

Where the PDF goes off the rails

Mode confusion that breaks the troubleshooting map

The most damaging idea a reader can leave with is that “dipole radiation is common-mode.” A dipole’s wanted radiator current is differential: equal magnitude, opposite direction on the two legs. The common-mode current we fight is the unwanted current on the outside of the coax shield and everything it couples into.

Once you blur those two, troubleshooting becomes impossible, because you’re no longer distinguishing: wanted antenna current versus unwanted feedline/system current. That’s why we keep the functional split sharp: a transformer solves impedance transformation, a choke solves feedline current and symmetry enforcement. See Baluns in a Nutshell.

“Coax has three conductors” is useful… until it becomes a fake constant

Yes, coax can support a differential mode (inner conductor with return on the inside of the shield) and a common mode (current on the outside surface of the shield). The derailment happens when common-mode behavior is treated like a neat single-wire transmission line with a stable velocity factor.

In reality, common-mode propagation is environment-defined: mast, soil, gutters, tower, house wiring, parallel runs, cable routing, even “what it’s near.” Common-mode is not a datasheet parameter. It’s a system behavior.

“Earth return” is an incomplete default story in modern stations

Some models lean heavily on “return through earth.” Sometimes that is part of the return path, but in many home stations the dominant return is: shack bonding, PE wiring, other coax runs, rotator/control cables, mast/tower, and capacitively coupled nearby structures.

That’s why we frame it as “unbalanced to ground/structure” rather than “earth return,” because it names the actual return candidates that exist in real installs. See Unbalanced to Ground.

The Strombauch (current belly) placement advice sounds advanced, but becomes unusable without measurement

“Place the choke at the common-mode current maximum” is theoretically correct and practically incomplete. The current maximum is not a fixed point; it shifts with routing and frequency. Add a choke, and the standing wave pattern changes again.

The station-grade version is: apply a sane default strategy, then measure the actual braid current and iterate. See Do I Have Enough Baluns?.

Transmission-line transformer rules leaking into choke rules

Another common derailment is when “TLT rules” (transmission-line transformer rules) get generalized into “choke rules.” For example, guidance like “the line must be 50 Ω for good SWR” may be relevant in a very specific transformer context, but it does not automatically apply to a choke used purely as a common-mode isolator.

In practical station terms, “balun” covers at least two different jobs:

• Transformation (impedance conversion): unun / autotransformer / voltage balun behavior.
• Isolation (blocking feedline common-mode): current choke / current balun behavior.

When you blur those jobs, you start applying “transformation constraints” to devices that are being used as isolators, and you end up with bad build choices and bad test expectations.

The biggest trap: converting choke impedance to dB in a 50 Ω fantasy world

dB claims are not portable unless you state the common-mode source resistance. Mapping “X ohms equals Y dB” as a universal rule is how people get misled into shopping for vanity numbers.

Measurement is the single biggest derailment: beautiful plots that test the wrong thing

A large fraction of ham “VNA choke tests” accidentally measure differential behavior, fixture behavior, or room coupling. That’s why you can generate a curve that looks engineering-grade while never actually exciting common-mode.

The common failure patterns look like this:

• S21-through by default excites differential mode unless the fixture deliberately forces common-mode excitation and controls the return path.
• Resistor fixtures and correction tables don’t fix the core problem if the mode you excite is still not controlled.
• One-port S11 with conductors strapped becomes extremely sensitive to a few pF of stray capacitance and lead inductance, which can create convincing-looking resonances that are mostly fixture artifacts.

“Just wind a wire on the core” only tests material trend, not choke performance

A single-wire-on-core test can be useful to compare core mixes or show general trends, but it does not capture the dominant shape-movers in real chokes: winding-to-winding capacitance, end-to-end capacitance, connector geometry, lead length, layering, and resonance shifts that can land right on an HF band.

In other words: “core + turns” is not the full device. A publishable choke specification must reflect the real assembly geometry because parasitics often dominate the upper-HF behavior.

Ferrite guidance is often too categorical: design for minima and margin

“Best mix” statements tend to hide the realities that actually move a choke curve: A_L spread, permeability variation, loss-vs-frequency behavior, temperature dependence, winding capacitance, and measurement parasitics.

That’s why the station-safe approach is: design to conservative minima across your active bands (and publish those minima), instead of chasing the tallest best-case peak on a single sample.

Baluns behind a tuner: the direction is right, but the “why” matters

The tuner output impedance can be extreme and undefined. That’s exactly why fixed-ratio transformer baluns placed inside/after tuners are often a bad idea in practice. In a real station workflow: let the tuner handle transformation, and use a robust 1:1 current choke for isolation where you need it.

The VSWR-based “symmetry test” is clever... but it stays a proxy

Workshop demos that “flip one side to ground and watch SWR change” can be educational, but they’re still indirect proxies and can be very sensitive to the fixture’s grounding reference and stray coupling. For publishable choke performance, you still want Zcm (bench) and braid current (in the real install).

Why “aim for −20 dB” reinforces the wrong KPI

When a document frames success as “better than −20 dB,” it quietly teaches readers to optimize for a number that depends on Rcm and test setup assumptions. That’s how people end up with impressive-looking charts that don’t transfer.

If you must show dB, define the assumed Rcm. Otherwise, publish Zcm in ohms and let installers translate that into station behavior through measurement.

The 2026 RF.Guru workflow that actually transfers

Our position is consistent across the RF.Guru knowledge base: publish Zcm in ohms, measure it correctly on the bench, then verify it in the installation.

Start with the right question

• Need impedance transformation? Use a transformer (unun / voltage / autotransformer) and validate it in the impedance world it will actually see.
• Need feedline isolation and pattern stability? Use a current choke and target Zcm across your bands.

Set targets in ohms, not marketing dB

For common-mode control, Zcm is the portable metric. If you want to talk dB, you must state the assumed Rcm. Practical guidance and why it varies is covered in How Much Choking Do You Need for RX and TX?.

Measure correctly on the bench

• Calibrate at the fixture plane (SOLT).
• Keep the fixture symmetric and control unintended coupling.
• Extract Zcm using the Y21 method (not “S21-through”).

“Enough choking” in the real world

The practical version is intentionally unromantic: measure, don’t guess. Bench curves matter, but the installation decides the common-mode source impedance and the standing-wave pattern on the outside of the feedline.

Bench targets (starting point)

• ≥ 5 kΩ Zcm across your active bands is a practical baseline for meaningful common-mode control.
• ≥ 10 kΩ Zcm is excellent headroom, especially for QRO behavior and stubborn installations.

These are not magic constants. They’re practical minimum bars that survive real-world variation better than chasing a narrow resonance peak.

Installation verification (the part most people skip)

Use a clamp-on RF ammeter and map coax braid current at the feedpoint area, a short distance downline, and at the shack entry. Then add/move chokes and observe where current collapses. If your current distribution changes drastically when you move a choke, that’s normal: you’re changing the common-mode system, not “adding a simple part.”

Placement defaults that actually work

• Feedpoint choke: primary defense (keeps the antenna from recruiting the feedline as part of the radiator system).
• Station-entry choke: secondary defense (keeps the station wiring/chassis from becoming the return partner).
• Optional mid-line choke: only when measurements show a residual peak; practical distances often land somewhere around 0.05–0.25 λ downline (referenced to the lowest band of concern), but you verify with a clamp meter, not vibes.

This is the real-world replacement for “place it at Strombauch (current belly).” In a real station, Strombauch (current belly) is not a fixed point you can know in advance without measurement.

Why Strombauch (current belly) is theoretically cute and operationally fragile

The idea is correct in theory: a choke inserted at the common-mode current maximum should have maximum effect. But in practice, the CM peaks move with frequency, routing, and nearby metal, and adding a choke changes the standing-wave pattern you’re trying to “target.” So Strombauch (current belly) becomes an after-the-fact description, not an actionable instruction, unless you are actively measuring braid current while iterating placement.

One analogy that exposes the same category error

The “back-to-back transformer test” myth in EFHW land is the same failure pattern: a convenient 50 Ω fixture produces a neat curve, then people claim it proves real-world performance at a high-impedance, reactive feedpoint. See The Back-to-Back EFHW Measurement Myth.

If your fixture forces a world your antenna system never lives in, your “proof” is theater.

Conclusion

DL4ZAO’s “Balun-Workshop” is a decent workshop primer, but it becomes misleading when it blurs differential radiator current with feedline common-mode, treats CM behavior like a neat line with fixed parameters, converts 50 Ω dB bench numbers into universal targets, and promotes measurement approaches that commonly measure the wrong thing.

The 2026 reality check is simple and ruthless: publish Zcm in ohms, measure with Y21 (Zcm = −1/Y21), and verify in the real installation with clamp measurements and iterative choke placement.

Interested in more technical content? Subscribe to our updates for deep-dive RF articles and lab notes.

Questions or experiences to share? Feel free to contact RF.Guru for technical support and feedback.