Skip to content

FT8

FT8 is a weak-signal, UTC-slotted 8-FSK mode used primarily by Amateur Radio. RF Sentry decodes it from the lane's demodulated linear-audio domain, not directly from wideband receiver IQ.

Signal and input geometry

Property RF Sentry value
Input 12 kS/s mono linear audio, USB
Search region 100–3,000 Hz
Preferred input bandwidth 2.9 kHz
Slot 15.0 s
Symbol duration 160 ms
Tone spacing 6.25 Hz
Modulation 8-GFSK/8-FSK symbol decisions
Symbols 79 total: 58 data + three 7-symbol Costas groups
Payload/FEC 77 payload bits + CRC-14; LDPC(174,91)
Time requirement UTC, at most 100 ms manifest uncertainty

IQ/audio pipeline

flowchart TB
    IQ[Receiver CU8 IQ] --> INGRESS[Independent ingress decoder sink]
    INGRESS --> INPUT[decoder.input.worker<br/>Residual DC + VFO translation]
    INPUT --> DSP[Decoder-only WASM channelizer<br/>USB + anti-aliased rational resampling]
    DSP --> AUDIO[12 kHz linear audio]
    AUDIO --> SLOT[Sample-counter slot assembler]
    SLOT --> FFT[Time/frequency candidate search]
    FFT --> MF[WebFT8/mfsk WASM]
    MF --> SYNC[Costas correlation]
    SYNC --> LDPC[Deep LDPC / OSD passes]
    LDPC --> CRC[CRC-14 validation]
    CRC --> PARSE[TypeScript message interpretation]
    PARSE --> STATION[Station intelligence and decoder UI]

The slot assembler derives boundaries from the decoder sample counter and the gateway's UTC anchor. It quarantines incomplete slots and does not concatenate across discontinuities. Browser wall-clock callbacks are not used as the sample clock.

The gateway's per-frame monotonic timestamp is callback timing. UTC is bound once per capture epoch and advanced from source sample counters; the FT slot bias is likewise bound once and advanced from decoderSampleCounter. Independent per-frame rebinding would mistake transport jitter for slot loss. FIR delay and resampler phase remain in the exact source-position mapping. See timing contracts.

This is decoder-only linear audio, not a tap after speaker volume/mute, squelch, browser AGC or de-emphasis. Changes to the audible filter do not replace the manifested search window.

Decoder implementation

The production FT8 path uses the vendored WebFT8/mfsk WASM core at revision b5ec75f59ac3d0aee82b87219b7fcfa5c262fa59. It performs multi-candidate deep decoding, ordered-statistics/AP-capable passes, and successive interference cancellation. Message output is accepted only when the payload and CRC/FEC checks succeed.

Typed interpretation exposes callsigns, grid/report or other supported FT8 fields, signal/frequency timing evidence, decode pass, and hash-resolution state. Unresolved hashed callsigns remain explicitly unresolved rather than being guessed.

Detection and tuning

The manifest contains common FT8 service-frequency hints (for example the 14.074 MHz USB allocation) as priors. Frequency is not proof. Candidate analysis can recognize narrow multi-tone digital behavior, while the decoder's CRC-valid messages provide protocol evidence.

Persistent measured digital evidence or a manifest-declared bounded customary-frequency trial may support opt-in Auto Start, but a usable UTC anchor and allowlisted compatible manifest remain prerequisites. A prior must not move detector bounds, replace the tuning/search reference or become a protocol claim. Validated output renews a minutes-scale hold through fades. Instantaneous detector bounds, published clickable bounds, held control envelope, audible passband and decoder search window remain distinct; rectangle-edge breathing must not steer the VFO. Signal Follow defaults off. Each mode's activation contract covers carrier/reference, passband geometry, containment, tracking, loss, pins and manual takeover.

Replay and limits

Replay preserves the original UTC/sample pairing. Accelerated processing must not change slot assignment or label replay throughput as live reception rate. The module has a 256 MiB manifest memory budget and bounded input/event queues.

Coverage and limitations

FT8 slot timing, gaps, duplicate handling, worker reset, message normalization, and decoder lifecycle are covered by ftxDecoder.test.ts, common decoder tests, and built-artifact validation. RF Sentry is a receive/analysis path; it does not transmit. Decoding performance is implementation-specific and should not be assumed identical to every WSJT-X release.

Ledger and remaining proof

docs/roadmap/decoders.md 6B.1A, 6B.1B, and 6B.1C record accepted timing, FT8/FT4 decoder and tracking slices. The extended multi-rate, dual-lane, live-FT4 and long-history workspace matrix remains a separate gate in the reconciled Phase 6 ledger. Dated live result/test counts describe that checkpoint, not a new validation performed by this documentation change.