5.1 About this Volume

The spectrum analyzer is the mod that made the UV-K5 famous, and it is the feature most likely to be misunderstood. This volume takes it apart: the mechanism by which a narrowband voice radio draws a picture of a band, the on-screen experience, the receive unlocks that ride alongside it (AM, SSB, wide RX), and the frequency-counter and signal tools. Then it does the thing the hype usually skips — draws the honest line between this $30 triage instrument and a real software-defined radio, and points at the HackRF for the jobs the UV-K5 cannot do.

The reader should leave able to explain to someone else exactly why the analyzer is useful and exactly where it stops being useful, and to run a field workflow that uses the UV-K5 for what it is good at (fast, cheap triage) and hands off to the right tool when depth is needed. This is a capability analysis; the voice is impersonal because nothing here is owned, and the claims are grounded in the BK4819’s documented behaviour.

5.2 How the analyzer works — a stepped sweep, not a capture

The single most important sentence in this volume: the UV-K5 spectrum analyzer is a stepped RSSI sweep, not a wideband IQ capture. A real SDR captures a chunk of spectrum all at once and transforms it to a frequency display; the UV-K5 has no wideband path, so it cannot do that. What it does instead is tune its narrowband receiver to a frequency, read the signal-strength (RSSI) register, step to the next frequency, read again, and repeat — building a picture one point at a time.

   SDR (e.g. HackRF)                 UV-K5 "spectrum analyzer"
   ────────────────                  ─────────────────────────
   capture a wide span               tune narrow RX to f0, read RSSI
   all at once → FFT →               step to f1, read RSSI
   whole band appears                step to f2, read RSSI
   simultaneously, fast              ...  step across the span ...
                                     plot RSSI-vs-frequency
   ⇒ sees everything in the span     ⇒ sees only where the receiver
     at that instant                   is pointed right now; blind
                                       to anything between steps and
                                       to anything faster than the sweep

This mechanism has three consequences that define every strength and weakness in the rest of the volume. The sweep is sequential (so it is slow, and a brief signal can appear or vanish between steps). It is coarse (the step size — on the order of tens of kHz — sets the resolution, and the LCD has few pixels). And it is blind between steps (narrow signals that fall in the gaps can be missed). None of this is a flaw in the firmware; it is the inevitable result of building a spectrum display out of a narrowband receiver.

5.3 The sweep loop in detail

Reduced to pseudocode, the analyzer is a tight loop around two BK4819 operations — retune the PLL, read RSSI:

// Illustrative — the real code lives in the fagci/egzumer/F4HWN sources
for (f = f_start; f <= f_stop; f += step) {
    bk4819_set_frequency(f);     // program the PLL/VCO to f
    settle();                    // let the synthesizer/AGC settle
    rssi[i++] = bk4819_read_rssi();   // read the RSSI register
}
plot(rssi, f_start, f_stop);     // draw RSSI-vs-frequency on the LCD
// then scroll the trace into the waterfall history and repeat

Three parameters set the character of the sweep:

• Span (f_start … f_stop). How wide a slice the user asked for. A wider span at a fixed step count means coarser resolution; a narrower span means finer detail but a smaller view.
• Step size. The frequency increment between RSSI reads — on the order of tens of kHz in typical configurations. This is the resolution floor: signals closer together than a step cannot be distinguished, and signals narrower than a step can be straddled and missed.
• Settle time. The synthesizer and AGC need a moment to settle after each retune before the RSSI read is valid. Shorter settle = faster sweep but noisier/less accurate readings; longer settle = cleaner readings but a slower, more laggy display. The forks make tradeoffs here, and it is why the “refresh rate” feels sluggish compared to an SDR waterfall.

Tip. The sweep is a classic time-versus-fidelity tradeoff done on a shoestring. Widening the span, shrinking the step, and lengthening the settle all improve what you see at the cost of how fast you see it. For field triage the right instinct is a wide-ish span at coarse resolution to spot activity fast, then narrow in once something shows up — the same discipline one uses on a bench analyzer, just much slower.

5.4 The waterfall and the on-screen UX

On the monochrome top-mounted LCD, the analyzer presents a live RSSI-vs-frequency trace across the chosen span, typically with a moving marker and the frequency/strength of the current peak, and many forks scroll past traces downward into a waterfall history so a glance shows not just “what is on now” but “what has been on recently.” In egzumer the analyzer is reached with F then 5; other forks use their own key sequences, but the interaction model is the same: pick a center/span, watch the trace, tap to tune the main receiver to a bump to hear what it is.

The UX is constrained by the canvas. The LCD has few pixels, so the trace is coarse and the waterfall history is short. The display is monochrome, so signal strength is shown by trace height (and, in the waterfall, by dot density/pattern) rather than by a color heat-map. And because the whole thing is a sequential sweep, the display updates with visible lag. Within those constraints it is genuinely useful: the “tap a bump to listen” loop — see activity, tune to it, identify it by ear — is the analyzer’s killer interaction and the reason it earns a place in the field even though it is crude.

5.5 AM and SSB receive

Alongside the analyzer, the receive-mode unlocks are the other half of what the custom firmware adds, because the stock firmware demodulates only FM.

• AM receive. The BK4819 has an AM demodulation path; the custom firmware selects it and sets appropriate front-end gains. This is one of the genuinely good unlocks: it makes airband (civil aviation AM, ~108–137 MHz) and shortwave/broadcast AM listenable on the radio, which a stock UV-K5 cannot do at all. Quality is “narrowband-radio AM” — fine for voice, not hi-fi — but it is real and useful.
• SSB receive. Single-sideband is harder, because the BK4819 was never designed for it. The forks approximate SSB using the AM/IF path plus firmware DSP tricks. The honest characterization is crude but listenable: usable for copying an SSB voice contact or a utility station in a pinch, not a substitute for a proper SSB receiver. Exactly how well it works varies by fork and by band.

Note. AM airband is the unlock most owners actually use day to day — it turns the radio into a competent cheap airband scanner. SSB is the more impressive-sounding unlock but the more qualified one; set expectations accordingly. Neither changes the fundamental front-end limits covered next.

5.6 Wideband RX coverage and the front-end limits

The custom firmware lets the BK4819’s synthesizer tune across roughly 18 MHz to 1300 MHz — a startling range for a $30 radio and the basis of the “it does everything” excitement. The reality is more bounded, in two specific ways that no firmware can fix:

1. The 630–840 MHz baseband gap. Reception in roughly this region is simply unavailable — a limitation inside the BK4819’s baseband/IF, not a software choice. Any claim of continuous coverage to 1300 MHz is wrong here; plan around the gap.
2. Fixed, ham-band-optimized front-end filtering. The radio’s RX input filtering is designed for the VHF/UHF ham bands. The synthesizer will tune far outside them, but the signal must still pass through filtering not cut for those frequencies, so sensitivity falls off — sometimes sharply — away from the design bands. “Tunes to 900 MHz” is not “hears 900 MHz well.”

   Coverage reality (custom firmware)

   18 MHz ████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 1300 MHz
          │  usable, but      │XXXX│   degraded sensitivity
          │  off-band roll-off│630-│   away from the ham bands,
          │  worsens with     │840 │   worst far from VHF/UHF
          │  distance from    │gap │
          │  the ham bands    │(HW)│
   ───────┴───────────────────┴────┴───────────────────────
   best:  ~2 m (144) and 70 cm (430) ham bands + airband AM

The honest summary of coverage: wide where it counts for a scanner — the ham bands, airband AM, nearby VHF/UHF activity — and increasingly marginal at the extremes. A better antenna (Volume 2 §8) helps on bands it is cut for but cannot undo the fixed front-end or the baseband gap. For flat, sensitive, truly wideband coverage, the tool is an SDR (§8).

5.7 The frequency counter and signal tools

The same RSSI/measurement registers that power the analyzer also back a set of signal utilities, which together make the UV-K5 a surprisingly handy little field instrument:

• Frequency counter. Point the radio at a strong, nearby transmitter and the firmware uses the BK4819’s frequency-measurement capability to read its frequency. The classic use is identifying an unknown handheld or keyfob transmitting close by. It needs a strong local signal — it is not a sensitive, calibrated counter — but for “what frequency is that thing on?” at arm’s length it works.
• RSSI / S-meter. A readable, often graphable signal-strength display — useful for antenna comparisons, for walking toward a signal, and for judging whether a bump on the analyzer is worth tuning to.
• Tone / squelch tools. Driving the CTCSS/DCS and DTMF registers enables tone scanning (discovering the sub-audible tone a repeater or signal uses) and related scanning tricks.

These tools share the analyzer’s character: cheap, immediate, approximate. The frequency counter’s “needs a strong nearby signal” caveat is the one most likely to surprise a newcomer expecting a bench counter’s reach.

5.8 The honest comparison — this is not an SDR

The phrase “turns a $30 radio into an SDR” sells radios and sets up disappointment. The table makes the real relationship explicit.

Table 1 — 8. The honest comparison — this is not an SDR

	UV-K5 “analyzer” (custom FW)	A real SDR (HackRF One + PC/PortaPack)
Acquisition	Sequential stepped RSSI sweep	Simultaneous wideband IQ capture + FFT
Instantaneous bandwidth	Narrow (one voice channel at a time)	Wide (many MHz at once)
Resolution	Coarse (tens-of-kHz steps, few LCD pixels)	Fine (FFT bins, full-screen color waterfall)
Speed	Slow; blind between steps; misses brief signals	Fast; sees the whole span at once
Frequency range	~18–1300 MHz with a 630–840 MHz gap + roll-off	HackRF: 1 MHz – 6 GHz, flat front end
IQ / recording / decode	None	Full IQ capture, record, and decode in software
Display	Monochrome trace + short waterfall	Full color waterfall, demod, decoders
Cost	~$30	~$320+ (HackRF + PortaPack), or $30 dongle + a PC
Right job	Field triage: “is something on near here?”	Analysis: capture, measure, decode, transmit

The correct mental model is a division of labor, not a competition. The UV-K5 is the thing in a pocket that answers “is there activity around this frequency right now, and roughly where?” — fast, cheap, no laptop. When the answer is yes and the task becomes knowing what a signal is, recording it, measuring it, or transmitting, that is the HackRF One’s job, with its flat wideband front end, real FFT waterfall, IQ capture, and decode-in-software workflow. A bench that owns both uses the UV-K5 to notice and the HackRF to understand. Seen that way, the UV-K5 analyzer is not a disappointing SDR; it is an excellent $30 triage tool that knows when to hand off.

Warning — RF-legal (brief). Everything in this volume is receive-side and generally legal to listen with (local rules on what may be monitored vary by jurisdiction). The firmware’s separate TX unlock is a different matter and is license- and region-gated — see Volume 2 §9, the sibling Volume 10, and the hub’s legal/ethics note. Wide RX unlock does not imply any right to transmit.

5.9 A field workflow that plays to its strengths

Putting the pieces together, the workflow that gets the most out of a modded UV-K5 is a triage loop:

1. Sweep wide, coarse, fast. Open the analyzer on a broad span to spot where there is activity — accept that it is coarse and that brief signals may be missed.
2. Narrow in. Reduce the span around any bump for better resolution; read the approximate frequency off the display.
3. Listen. Tap-to-tune the main receiver to the signal and pick the demod mode (FM/AM/SSB) to hear what it is — this is where AM airband and the receive unlocks earn their keep.
4. Identify if close. If it is a strong nearby transmitter, use the frequency counter to pin the frequency; use the S-meter to walk toward it.
5. Hand off when it matters. If the signal needs recording, decoding, precise measurement, or a transmit response, switch to the HackRF/SDR (or the Flipper for sub-GHz capture/replay) — the UV-K5 has done its job by finding it.

That loop is the honest, useful core of the whole custom-firmware project: a cheap, instant, pocketable way to notice RF activity and listen to it, with a clear handoff to heavier tools for everything past noticing. The sibling Volume 9 develops the field workflow further and the pairing with the HackRF and Flipper; the sibling Volumes 6–8 cover getting the firmware onto the radio and programming it in the first place.

Capability claims in this volume are grounded in the BK4819’s documented behaviour and the fagci/egzumer/F4HWN analyzer implementations as of 2026-10-17. The 18–1300 MHz synthesizer range, the 630–840 MHz baseband gap, and the stepped-RSSI sweep mechanism are community-documented; sweep step sizes and settle times vary by fork and configuration. Transmit is out of scope here and is covered under the legal envelope in the sibling Volume 10.