SPEEDBIRD

Time-sequenced beacons#

SPEEDBIRD can send short beacons in fixed UTC time slots, in the spirit of the NCDXF/IARU International Beacon Project. Every station knows when and where every other station will transmit, so anyone can listen and build a propagation map from what they hear. Code: src/speedbird/core/beacon.py. API: /api/beacon. UI: Control → Beacons.

The beacon is disabled by default. When you enable it, the station transmits automatically, without an operator, as your callsign.

Part 97 compliance (read this first)#

SPEEDBIRD does not decide whether your operation is legal. You do. Points to check (US rules; other countries differ):

The Beacons page lists every frequency the configuration will use. It flags each one that lies outside the §97.203(d) automatic-beacon segments and outside the band's automatic-control data sub-band.

Time slots#

Modes#

Mode What Airtime Decodes to (nominal) Slot rule
call SBP CALL burst ~1.5 s about −13 dB ≥ 10 s
ft8 SBP-FT8 ~12.6 s about −21 dB multiple of 15 s
fst4w120 SBP-FST4W-120 ~109 s about −32 dB 120 s slots on even UTC minutes
auto (default) chosen per band by SNR as for fst4w120

How auto chooses a mode for each band:

  1. It takes the median SNR over the last 24 h at which other stations heard us. Two sources feed this: - reception reports (R:CALL@SNR tokens in their beacons); - SBP mesh neighbours' reports.
  2. If there are no reports, it uses how well we hear them: heard beacons, plus SBP rows in NodeDB on that band.
  3. It maps that SNR to a mode: - ≥ −10 dB: call - −10 to −20 dB: ft8 - below −20 dB, or no data: fst4w120
  4. Hysteresis (hysteresis_db, 3 dB) applies. A faster mode is chosen only when SNR − h qualifies for it, and a slower mode only when SNR + h drops below the current one.
  5. The decision is made once per period and stored in <state>/beacon/state.json.

A band entry's mode overrides the global setting. Until the SBP code provides send_beacon, every beacon goes out as one ordinary SBP broadcast. The status and the schedule show this.

Airtime is capped per radio:

Both caps are measured over max(1 h, period_s). The default 2 h period leaves room for one 109 s FST4W beacon (about 1.5 %).

Band hopping#

With hop: true and a band sequence of N bands, a station whose slot is k uses bands[(p + k + r) % N] during period p. Here r is the index of our radio, so two radios cover different bands. At any moment different stations are on different bands, and a listener who stays on one band hears every station once every N periods.

The radio is retuned through the normal modem start (SbpService.start_link) at most once per period, and only when all of these hold:

It never retunes in the middle of a session. Without hopping, the beacon goes out on whatever frequency the radio is on.

Payload#

A beacon is one SBP data block:

SBB1 K4MFC-1 EM73tv 40m 7105.0 P10 S5/60 T1763380800 Mft8 R:W1AW@-14 :optional text

The fields are:

Field Example Meaning
callsign K4MFC-1
grid EM73tv
band, kHz 40m 7105.0
P P10 power %
S S5/60 slot / number of slots
T T1763380800 slot start (Unix seconds)
M Mft8 mode
R: R:W1AW@-14 up to 3 reception reports
:text :optional text up to 40 characters

What gets recorded#

Mesh HELLO alignment#

align_mesh_hello: true moves SBP mesh HELLOs from their free-running interval into our slot, sent after the longest beacon the configured modes can produce. The mesh keeps its own idle checks and airtime cap.

API#

Method Path Notes
GET / PUT /api/beacon/config
GET /api/beacon/status
GET /api/beacon/schedule?n=20
GET /api/beacon/heard?band=&since=&call=&limit=
POST /api/beacon/test body {radio, confirm: true, mode?}. Transmits one beacon now.