Guides Sdr

SDR first steps

A software-defined radio receiver turns the computer into a radio that can tune from shortwave to microwave and see a whole slice of spectrum at once. The cheapest way in is an RTL-SDR dongle, and nothing on this page needs a licence: it is all receiving.

This page gets a dongle from the bag to three things in one evening: broadcast FM, aircraft, and the 433 MHz sensors around your house.

Install

hammunition install sdr listening --dry-run
hammunition install sdr listening

sdr carries the receivers (Gqrx, SDR++, CubicSDR, SDRangel), GNU Radio and the device drivers. listening carries the decoders: aircraft, ships, pagers, sensors, weather. Some units are not in every distribution's archive; the plan names any it defers and why, and installs the rest.

1. Plug it in and check it

hammunition hardware list

This lists what is plugged in and whether the catalog recognises it, and whether its permissions are set up. Then ask the device itself:

rtl_test

It should find the dongle, name its tuner chip, and start reading samples. A few seconds without lost at least messages is a healthy device; stop it with Ctrl-C. Other devices have their own test tool, named on their hardware page.

If rtl_test says the device is busy

A message like usb_claim_interface error -6 means the Linux kernel's digital-TV driver took the dongle first. It was built for watching TV, and it holds the device so nothing else can.

echo 'blacklist dvb_usb_rtl28xxu' | sudo tee /etc/modprobe.d/blacklist-rtl-sdr.conf
sudo modprobe -r dvb_usb_rtl28xxu

Unplug the dongle and plug it back in. Undo: delete that file.

Whether your distribution already ships this file varies. Ubuntu 24.04's rtl-sdr 2.0.1 packages ship udev rules and no blacklist (read from the package archives, 2026-09-30), so there the command above may be needed.

If it says permission denied

The device's udev rule grants access to the plugdev group, and group membership starts at your next login. Log out and back in. hammunition hardware apply --dry-run shows the rules and groups the catalog would set up for every device it knows.

2. Broadcast FM with Gqrx

Gqrx is the catalog's general-purpose default receiver (why).

1. Start Gqrx. The first-run dialog lists detected devices: choose the RTL-SDR. Leave the sample rate at its default.
2. Press the power button (top left) to start.
3. Set the frequency to a local FM station, say 99.5 MHz, and the mode (right-hand panel) to WFM (stereo).
4. Raise the Gain in the Input Controls tab until the station is clear; too much gain makes ghosts of strong stations all over the band.

You are hearing the station, and the waterfall above shows every station around it at once.

The other receivers do the same job differently. SDR++ is fast and modern, SDRangel does almost everything including transmit on capable hardware, CubicSDR is simple. Try them; they coexist.

3. Aircraft

Aircraft broadcast their position, altitude and callsign on 1090 MHz (ADS-B). readsb decodes it, and serves a map and data feeds for other programs. It is not in every distribution's archive (Ubuntu 24.04 has none; checked 2026-09-30), and the install plan says where it is deferred. Its own documentation gives the command lines.

Close Gqrx first: one program at a time can hold the dongle.

The aircraft map in a browser

tar1090 is the page most ADS-B receivers are watched with: a table of aircraft, a track for each, altitude, speed and range rings, filters. It is in listening beside readsb and deferred by name wherever readsb is. Its own installer is not used (it is a root script piped from wget that opens a web server on port 80 on every address); instead hammunition reference serve serves the page on this machine only:

hammunition install tar1090          # or the whole listening profile
sudo systemctl start readsb           # Debian's service; it writes /run/readsb
hammunition reference serve

Open http://127.0.0.1:8480/aircraft/. It reads the JSON file readsb keeps up to date, read-only. If your readsb writes elsewhere (a hand-run readsb --write-json DIR), say so with --readsb-json DIR. dump978-fa's UAT aircraft appear on the same page when readsb takes them as an input (--net-connector 127.0.0.1,30978,uat_in, which is how the 978 sample was decoded with Debian's readsb).

What is behind the aircraft. If you installed osm-pmtiles with map regions (the navigation guide), the base map is your own regions, drawn from the same tiles as the page at /map/, only plainer. Without it there is no base map: aircraft on a plain background, and a line on the page saying why. The page never loads a map from the internet. Nor does it fetch aircraft photographs, flight routes, weather or airspace overlays, and the browser enforces that (a Content-Security-Policy that names no host). The links in an aircraft's detail panel to FlightAware and planespotters are still links: they open when you click them.

What is not there. The aircraft database (type, operator, registration lookups) is not carried: its upstream replaces its only commit regularly, so it cannot be pinned. The columns show only what readsb decoded. Tracks are what the page has seen since you opened it, because tar1090's history service is not run.

Measured and not. With synthetic aircraft and a synthetic map tile in headless Chromium, the aircraft table fills, a selected aircraft's panel opens, the map tile is decoded and no request leaves 127.0.0.1. Not yet seen with a live receiver, in Firefox, at street zoom over a real region, or on a phone.

For aircraft datalink text rather than positions, acarsdec (VHF ACARS), dumpvdl2 and dumphfdl (HF) are in listening.

4. Sensors on 433 MHz

Weather stations, tyre-pressure sensors, doorbells and utility meters transmit short bursts on 433.92 MHz (868 MHz in Europe for many). rtl_433 knows hundreds of them:

rtl_433

With no options it listens on 433.92 MHz and prints each decoded device as it hears it: model, ID, and whatever it reports. Give it a few minutes in a built-up area. rtl_433 -f 868M listens on 868 MHz.

5. Ships

On the coast, ships broadcast AIS on 162 MHz. AIS-catcher and rtl-ais decode it; their pages say how to feed a map.

What you may decode is your law to know

Receiving is unlicensed nearly everywhere. What you may decode, record or repeat is not the same everywhere: pager traffic, aircraft datalink and some utility transmissions are protected in some countries. Hammunition tells you what a tool can do and never judges what your law allows. That is yours to know before you listen.

When it does not work

• Nothing found by rtl_test → cable, USB port, then hammunition hardware list.
• Busy → the kernel driver, above.
• Everything is noise → the antenna. The telescopic antenna in the box is a compromise; for 1090 MHz a quarter-wave (about 6.9 cm) vertical helps enormously.
• The frequency is slightly off → cheap dongles' crystals drift. Newer ones with a TCXO barely do. rtl_test -p measures the error in ppm, and Gqrx's input settings take it as a Freq. correction.

What was measured

The rtl-sdr package contents, rtl_test's options and rtl_433's default frequency were read from Ubuntu 24.04's packages on 2026-09-30, and readsb's absence from its archive the same day. The receiver steps follow each program's own documentation. The field laptop's SDR bench is recorded in the bench record; this page's steps were not run end to end there.