SPEEDBIRD quick start#
This guide takes a station from install to its first SBP contact, using the standard SPEEDBIRD channel set. Frequencies are in MHz unless noted. The rules summaries are for US stations (Part 97) and are not legal advice; check the current rules and your local band plan.
1. Install and run#
sudo deploy/install.sh # venv, TLS cert, geodata, Pat; enables and starts speedbird.service
The web UI is then on https://<host>/ (port 443). Run the same script again to redeploy after an update.
For development without a radio: .venv/bin/speedbird serve --demo (synthetic source on port 8073).
Warning: the web UI has no authentication yet. Only expose it on a trusted network.
2. Add your radios#
Open Radios in the web UI and add each rig (Icom radios over LAN: host, port 50001, user, password). The SBP modem needs a radio with an RX audio stream, which in practice means a LAN-connected rig.
3. Start the SBP modem#
On each radio, start the modem with the station callsign plus a different SSID per radio, on the band's calling frequency, for example:
| Radio | Callsign | Calling frequency |
|---|---|---|
| IC-7610 | K4MFC-6 | 7.084 |
| IC-7300MK2 | K4MFC-7 | 7.084 |
| IC-705 | K4MFC-8 | 7.084 |
Or use the API: POST /api/sbp/links/<radio> with {"mycall": "K4MFC-6", "freq": 7084000, "profile": "hf", "monitor": true}.
- One SSID per radio. SPEEDBIRD refuses to start a second modem with a callsign that another radio is already using, because the mesh routes between radios and frequencies by callsign.
- Running modems survive restarts and reboots. They are saved in
/var/lib/speedbird/sbp/links.jsonand restored when the service starts. Stopping a modem yourself removes it from that file.
4. The SPEEDBIRD channel set#
Every band has one calling channel, where sessions start, and a set of data channels that a session
can move to. The plan lives in /var/lib/speedbird/channels.json and is managed on the Channels page or
through /api/channels/sbp/<band>.
| Band | Calling | Data channels | Mode / step |
|---|---|---|---|
| 80 m | 3.583 | 3.556, 3.559, 3.562, 3.565 | USB-D, 3 kHz |
| 40 m | 7.084 | 7.093, 7.096, 7.111, 7.117, 7.120 | USB-D, 3 kHz |
| 20 m | 14.084 | 14.117, 14.120, 14.123, 14.126, 14.129, 14.132 | USB-D, 3 kHz |
| 17 m | 18.096 | 18.087, 18.090, 18.093 | USB-D, 3 kHz |
| 15 m | 21.084 | 21.063, 21.066, 21.087, 21.093 | USB-D, 3 kHz |
| 10 m | 28.084 | 28.087, 28.090, 28.093, 28.096, 28.099, 28.108 | USB-D, 3 kHz |
| 6 m | 50.323 | 50.602, 50.605, 50.608, 50.611, 50.614, 50.617 | USB-D, 3 kHz |
| 2 m | 144.800 | 144.925, 144.9375 | FM-D, 12.5 kHz |
| 440 | 440.800 | 441.000, 441.025, 441.050, 441.075, 441.100, 441.125 | FM-D, 25 kHz |
| 900 (Meshtastic) | — | LongFast 906.875, MediumFast 913.125, ShortFast 918.875 | LoRa, 250 kHz |
On 80 m to 10 m and 6 m the calling channel is FT8 + 10 kHz (17 m: just below FT8), so a receiver slice of about 13 kHz covers SBP calling and FT8 together (see "SBP + FT8 channels" below). 7.088 is reserved for the planned K4MFC Winlink gateway.
HF frequencies are USB dial frequencies; the SBP signal occupies about 0.3–3.0 kHz above the dial.
How the set was chosen:
- Legal segment: every channel is inside the Part 97 data segment and outside the Extra-only segment.
- Clear of others: channels avoid the listed FT8/FT4/WSPR/JS8 dials, NCDXF beacons, Winlink gateways and VARA/ARDOP/PACTOR channels. A slot that would overlap one is skipped.
- Band-plan window: on 40, 20, 10 and 6 m the data channels stay inside the ARRL data window. On 80, 17 and 15 m the window is too crowded, so some channels sit just outside it, on frequencies that are still legal for data. 2 m only has room for two.
- 900 MHz is Meshtastic only. SBP has no 33 cm profile. These are the default US slots for each preset; your mesh may use another slot. The station's T-Beam runs LongFast (906.875). Meshtastic on 900 MHz is Part 15 unless the node is in licensed (ham) mode.
Automatic control (§97.221(b)). Unattended stations may only run in the automatic-control sub-bands. The calling channels on 80, 40, 20, 17, 15 and 10 m (next to FT8) are outside them, so run those bands attended. 6 m, 2 m and 440 allow automatic control on these frequencies. The Channels page marks every channel with whether automatic control is allowed there.
SBP + FT8 channels#
One SBP channel per band sits next to FT8, so that a single receiver slice can cover both FT8 and SBP. The rule is FT8 dial + 10 kHz, which makes the combined span about 13 kHz:
| Band | FT8 dial | SBP + FT8 channel |
|---|---|---|
| 80 m | 3.573 | 3.583 |
| 40 m | 7.074 | 7.084 |
| 20 m | 14.074 | 14.084 |
| 17 m | 18.100 | 18.096 (below FT8: +10 kHz would be past the data segment, on the 18.110 beacon) |
| 15 m | 21.074 | 21.084 |
| 10 m | 28.074 | 28.084 |
| 6 m | 50.313 | 50.323 |
| 2 m | 144.174 | 144.800 (FM-D, SBP VHF profile; not next to FT8. US repeater-input range, check local pairs) |
| 440 | 432.174 | 440.800 (FM-D, SBP UHF profile; not next to FT8. Local repeater area, check with your coordinator) |
80 m to 6 m are USB-D dials with the SBP HF profile. The 2 m and 440 entries are FM-D channels instead (SBP VHF and UHF profiles) and are not next to FT8. Several share frequency with other users (RTTY near 14.085, Winlink gateways and VARA channels on 80 m, old DIGIALL VARA slots near 21.085 and 28.085), so listen before transmitting. Covering FT8 and SBP from one receiver needs the radio's IF output: the normal AF output is only about 3 kHz wide. 40 m 7.084 is also SBP data channel 1, and 7.088 is reserved for the planned K4MFC Winlink gateway.
To change a band, for example to 8 data channels on 20 m:
curl -sk -X PUT -H 'content-type: application/json' \
-d '{"count": 8}' https://<host>/api/channels/sbp/20m
Other fields: calling_hz, spacing_hz, direction (auto, above, below, around), avoid (skip
colliding slots), spill (allow channels outside the band-plan window), and overrides (per-channel frequency
or name). A running modem picks up a changed set the next time it starts.
5. Nodes and per-node frequencies#
The Nodes page lists every station heard on every radio.
- ✎ Edit a node to set its name, notes and manual position, or to link a callsign with its Meshtastic node(s). Your edits win over what is heard on air.
- + Add node creates a station you have not heard yet.
- ⇄ Frequencies maps a callsign or pattern (
W1ABC,W1ABC-7,W1*) to the frequency that reaches it, for any radio or for a specific one. Sending or connecting to a mapped station first moves that radio's modem to its frequency (only while the modem is idle). The modem returns to its home frequency after 2 minutes idle.
6. Cross-frequency mesh#
With radios on different frequencies (for example one on 7.084 and one on 14.084), the SBP mesh relays between them: a message heard on 40 m can be passed on over 20 m. This is on by default. To keep each frequency separate:
curl -sk -X PUT -H 'content-type: application/json' \
-d '{"cross_freq": false}' https://<host>/api/sbpmesh/config
7. Meshtastic gateway#
Plug a Meshtastic node in over USB and add it on the Mesh page. Gateway rules connect it to an SBP radio.
- HF → mesh: SBP stations heard on HF appear on the Meshtastic map as waypoints.
- Mesh → HF: a rule can carry text messages, position reports, node info and telemetry. Each one goes over
HF as a short tagged line, for example
[MESH 9aec/!e0f79aec] POS 35.1235,-83.1235 820m EM85kc. Position, node info and telemetry are sent at most once per node and type per interval (default 15 minutes). Receiving SPEEDBIRD stations add those mesh nodes to their node list.
Third-party traffic (§97.115). Meshtastic users are usually not licensed amateurs, so anything relayed from the mesh over HF is third-party traffic. Mesh → HF stays off until you tick "Allow third-party traffic" on the rule. You are responsible for everything it relays.
More#
docs/winlink.md: Winlink over SBP (VARA-compatible TNC ports)docs/vara.md: using a real VARA modemdocs/beacons.md: SBP beaconsdocs/windows.md: running on Windowssrc/speedbird/sbp/SPEC.md: the SBP on-air specification
Source: speedbird-linux/speedbird-quickstart.md