SPEEDBIRD

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}.

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:

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.

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.

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#

Source: speedbird-linux/speedbird-quickstart.md