FT4¶
FT4 is a faster UTC-slotted 4-FSK weak-signal mode. It shares RF Sentry's FTx slot/timing infrastructure with FT8 but has different framing, synchronization, symbol timing, and decoder code.
Signal and input geometry¶
| Property | RF Sentry value |
|---|---|
| Input | 12 kS/s mono linear audio, USB |
| Search region | 200–3,000 Hz |
| Preferred input bandwidth | 2.8 kHz |
| Slot | 7.5 s |
| Symbol duration | 48 ms |
| Tone spacing | approximately 20.833 Hz |
| Modulation | 4-GFSK/4-FSK symbol decisions |
| Symbols | 105: 87 data, four 4-symbol sync groups, two ramps |
| Payload/FEC | 77 payload bits + CRC-14; LDPC(174,91) |
| Time requirement | UTC, at most 100 ms manifest uncertainty |
Pipeline¶
flowchart TB
IQ[Receiver CU8 IQ] --> INGRESS[Independent ingress decoder sink]
INGRESS --> INPUT[decoder.input.worker<br/>Residual DC + VFO translation]
INPUT --> USB[Decoder-only WASM channelizer<br/>USB + exact resampling]
USB --> A[12 kHz linear audio]
A --> SLOT[7.5 s sample-clock slot]
SLOT --> SPEC[Candidate spectrogram]
SPEC --> CORE[ft8_lib Emscripten module]
CORE --> SYNC[Four Costas/sync groups]
SYNC --> LDPC[Multi-candidate LDPC]
LDPC --> CRC[CRC-14]
CRC --> MSG[Typed FTx message]
MSG --> UI[Decoder and station intelligence]
The shipped module adapts kgoba/ft8_lib revision
9fec6ca39886edbf96f4f5e71edc76da5074e871, built through the audited wrapper
from Signal-Decoder revision eac2c950…. Its message unpacker supports the
implemented FTx message types; unsupported/unresolved forms remain explicit.
FT4 applies its protocol whitening/XOR sequence and Gray mapping before LDPC interpretation. A generic event or sync candidate is not presented as a valid message unless CRC/FEC succeeds.
The shared clock contract binds source UTC and decoder-slot bias once per continuity epoch, then advances by sample counters. Callback boundaries never establish new slots. Decoder-only audio remains independent of listening controls; FT4's 200–3,000 Hz search is not replaced by the audible passband. The FT8 start/tracking rules also apply: priors are not proof, usable UTC is required, pins/manual control win, and the held envelope is distinct from detector-edge motion.
Replay and tests¶
The shared slot assembler preserves source-time boundaries during replay and
rejects partial/gapped slots. ftxDecoder.test.ts exercises both FT8 and FT4
slot behavior and message mapping; artifact and lifecycle tests exercise the
WASM/worker boundary.
The module has a 128 MiB manifest budget. Unlike the FT8 deep decoder, the FT4
implementation uses the lighter ft8_lib path; decoder performance and
supported unpacking are therefore documented separately rather than implying
the two modules share an identical engine.
Accepted Phase 6B.1 slices do not close the broader live-FT4, multi-rate,
dual-lane and long-history matrix in docs/roadmap/decoders.md; see the
shared ledger note.