Skip to content

Decoder roadmap and requested modes

This is the capability roadmap, not a list of installed or accepted decoders. It preserves the protocol/mode requests from the opening WEBSDR plan. Current support comes from the generated catalog, implementation chapters and their qualification limits; the original delivery checklists remain in docs/roadmap/decoders.md.

FT8 was the first timing-sensitive proof case, not the boundary of the system. A manifested module, an analog listening mode, a parser, a research candidate and an operator-accepted feature are different kinds of evidence. Proposed Pi workers/optional analysis hosts are not required for current browser modules. See execution tiers.

Each family's status below describes current source, not a new RF test. The lists remain requested scope even where a subset already exists. Nothing here closes the wider FT8/FT4, NRSC-5 AM, aviation or SATCOM acceptance gates.

Core Analog and Audio Modes

Current realtime DSP defines AM, USB, LSB, CW, NFM and WFM demodulators, with the controls documented in Browser DSP and receiver tuning. Synchronous AM, DSB and the wider audio-processing wishlist below must not be inferred from those six modes. Raw CU8 ingress/DVR is not automatically a selectable raw-IQ listening mode or durable SigMF recorder. Analog FM stereo/RDS is not established by the separate NRSC-5 stereo decoder.

  • AM.
  • Synchronous AM.
  • USB.
  • LSB.
  • DSB.
  • CW and CW reverse.
  • NFM.
  • WFM mono.
  • WFM stereo.
  • Raw I/Q.
  • Adjustable AGC, manual gain, squelch, de-emphasis, filtering, noise blanking, notch filtering, and audio noise reduction.

Amateur Weak-Signal Modes

FT8 and FT4 have shipped modules; the other listed modes remain requests. Their timing, parsing limits and qualification are separate: FT8, FT4.

  • FT8.
  • FT4.
  • WSPR.
  • WSPR-15.
  • FST4.
  • FST4W.
  • JT4.
  • JT9.
  • JT65.
  • Q65.
  • MSK144.
  • JS8Call normal, slow, fast, turbo, and ultra modes.

The initial shared ft8_lib proposal evolved: FT8 uses pinned WebFT8/mfsk; FT4 uses ft8_lib with the recorded wrapper. Exact revisions and dated WSJT-X comparison results remain in the source provenance and individual decoder chapters. Those comparisons are not universal weak-signal or message-family parity.

Amateur Text and Keyboard Modes

These text/keyboard decoders are not in the current catalog. Audible CW demodulation does not establish a Morse text decoder.

  • CW/Morse.
  • QRSS and slow CW visualization.
  • RTTY/Baudot with common shifts and baud rates.
  • BPSK and QPSK.
  • PSK31, PSK63, PSK125, PSK250, PSK500, and PSK1000.
  • Robust PSK variants where supported.
  • Olivia.
  • Contestia.
  • MFSK4, 8, 11, 16, 22, 31, 32, 64, and 128.
  • DominoEX.
  • THOR.
  • Throb and Throb-X.
  • MT63.
  • FSQ.
  • Hellschreiber.
  • IFKP.

Packet Radio

No current manifested AX.25/APRS/FX.25/IL2P module is shipped. The future packet/application scope is retained below.

  • AX.25 at 300 baud HF.
  • AX.25/APRS at 1200 baud AFSK.
  • 2400 and 4800 baud packet variants.
  • 9600 baud G3RUH/GMSK packet.
  • FX.25.
  • IL2P.
  • APRS messages, positions, objects, weather, and telemetry.
  • KISS and AGW-compatible read-only output for external applications later.

Dire Wolf remains an upstream candidate, not a bundled packet modem. Confirm exact coverage and integration before use.

HF Utility and Messaging

These utility/time-station decoder paths remain planned. The list is not permission to promise a proprietary decoder or to identify a protocol from frequency alone.

  • NAVTEX at 490 kHz, 518 kHz, and applicable HF channels.
  • SITOR-B.
  • AMTOR FEC.
  • SITOR-A where practical.
  • ALE 2G.
  • ALE 3G as a later extension.
  • Open ARDOP support.
  • PACTOR I where an open implementation is legally and technically suitable.
  • WEFAX.
  • WWV and WWVH timing information.
  • CHU and other applicable time-station formats.

Proprietary or closed protocols such as later PACTOR generations and VARA should be identified where possible but should not be promised as open decoders.

Aviation / Aeronautical RF Intelligence

Current modules are 1090ES and 978 UAT, feeding shared aviation intelligence. The 1090 module validates 112-bit DF17/DF18 extended squitter, not every Mode S format or Mode A/C. UAT broadcast/application support is limited to its documented parser subset. ACARS/VDL2/HFDL and specialized links below remain roadmap requests.

Aviation is one coherent intelligence domain, not a collection of unrelated decoder buttons. Phase 10 owns its protocol decoders, capture-time aircraft and message model, adaptive Aviation workspace, local-first metadata, map adapter, and detection/activation integration. It reuses the accepted Phase 6 decoder substrate, Phase 9 investigation/selection patterns, generic map, and IQ timeshift clock.

The aviation roadmap prioritizes the following sequence. It is site-specific planning, not a universal hardware policy or a statement that every item below is implemented. Verify the installed RF path before applying its HF/L-band assumptions:

  1. 1090ES ADS-B, Mode S, and Mode A/C awareness. This has the broadest immediate local yield, mature open implementations, aircraft position and state, and a direct fit with the existing map. A 2.4 MS/s RTL-SDR capture is sufficient for established 1090 MHz decoders.
  2. 978 MHz UAT. Treat the U.S. general-aviation link as a first-class peer, not an optional ADS-B footnote. In addition to aircraft reports, retain TIS-B, ADS-R, and FIS-B weather/aeronautical products with source, product time, and experimental/non-safety-certified presentation.
  3. VHF data link: VDL Mode 2 and ACARS. Commercial airport traffic can make both valuable. VDL2 is the richer modern traffic source; conventional VHF ACARS is the lower-complexity demodulation proof and both should share libacars application decoding and one message-oriented workspace.
  4. HFDL. The installed HF antenna/upconverter path makes long-range HFDL a practical next step after the local VHF links. It should reuse the same ACARS/CPDLC/ADS-C/MIAM application model rather than fork the UI.
  5. Specialized and hardware-gated sources. Add SELCAL as an audio adjunct; evaluate FLARM/FAMP for North American 915 MHz operation; and defer Inmarsat AERO/STD-C, 1030 MHz interrogation analysis, and navigation-aid intelligence until their antenna, bandwidth, licensing, and operator-value gates are met.

Protocol groupings are therefore:

  • Cooperative surveillance: 1090ES ADS-B, Mode S elementary/enhanced surveillance, bounded Mode A/C awareness, 978 UAT ADS-B, TIS-B, and ADS-R.
  • Weather and aeronautical broadcast: UAT FIS-B products including METAR, TAF, NOTAM, PIREP, AIRMET/SIGMET, winds, and graphical weather where decoded.
  • Aircraft/ground messaging: VHF ACARS, VDL2, HFDL, CPDLC, ADS-C, MIAM, and other payloads explicitly supported by the shared application library.
  • Specialized cooperative systems: FLARM/FAMP/OGN-compatible receive-only operation where lawful and technically compatible, plus SELCAL correlation.
  • Hardware-gated future links: Inmarsat AERO Classic and STD-C with a suitable L-band antenna/filter/LNA path; 1030 MHz SSR/TCAS interrogation and DME/TACAN or VOR/ILS signal intelligence as later research, never as certified navigation or collision-avoidance equipment.

Selected readsb and dump978-fa source portions are already adapted into the browser modules, not entire native receiver programs. libacars, dumpvdl2 and dumphfdl remain messaging candidates. Every new import still requires exact provenance, transitive-license review, browser-WASM suitability, malformed-input and recorded-IQ qualification.

Marine and Distress

No current manifested marine/distress decoder is shipped. Keep lawful-reception and experimental/non-safety-certified restrictions explicit.

  • AIS channels A and B.
  • Marine DSC.
  • NAVTEX.
  • COSPAS-SARSAT 406 MHz beacon messages.
  • EPIRB, ELT, and PLB payload presentation where legally receivable.

Decoded safety information must be labelled as experimental and must not be presented as safety-certified.

Paging, Selcall, and Signalling

These are requested families, not local multimon-ng integrations or shipped browser modules.

  • POCSAG 512.
  • POCSAG 1200.
  • POCSAG 2400.
  • FLEX.
  • FLEX_NEXT.
  • AFSK1200 and AFSK2400 variants.
  • FSK9600.
  • UFSK1200.
  • HAPN4800.
  • DTMF.
  • MDC1200.
  • FleetSync.
  • EAS/SAME.
  • ZVEI1, ZVEI2, ZVEI3, DZVEI, and PZVEI.
  • CCIR.
  • EEA.
  • EIA.
  • FMSFSK.
  • GSC/Golay sequential code.
  • X10.

multimon-ng is a paging/signalling research candidate; its upstream coverage is not RF Sentry's decoder inventory.

Digital Voice

No current manifested digital-voice decoder is shipped. Codec/hardware and license review remain prerequisites, not implied support.

  • FreeDV 700C, 700D, 700E, 1600, and 2020 where supported.
  • M17 voice and packet data.
  • DMR conventional Tier II.
  • Both DMR TDMA slots where practical.
  • D-STAR.
  • Yaesu System Fusion/C4FM.
  • P25 Phase 1.
  • P25 Phase 2.
  • NXDN48.
  • NXDN96.
  • dPMR.
  • TETRA unencrypted traffic where an appropriate decoder is available.
  • EDACS.
  • ProVoice.

DSD-FME remains a digital-voice/trunking candidate. Some requested modes need AMBE-family codecs or external vocoder hardware; record and review those dependencies before promising a decoder.

Encrypted calls should be identified as encrypted and left undecoded. The platform should never imply that encrypted audio can be recovered.

Broadcast

AM and FM listening exist; NRSC-5 FM and AM have separate browser modules, plus operator-only sanitizer builds. The AM module's presence does not close its positive-acquisition gate. Analog synchronous-AM/FM-stereo/RDS, DAB/DAB+ and DRM remain requests unless separately qualified. Public-service/content restrictions apply to decoded radio objects.

  • AM broadcast audio.
  • Synchronous AM.
  • FM mono and stereo.
  • RDS and RBDS, including station identifiers, programme type, radio text, traffic flags, clock time, and RadioText+ where present.
  • HD Radio/NRSC-5 FM and AM, including selectable public main/supplemental programme audio, station and service information, programme-service data, title/artist/album/genre, broadcast images, quality/synchronization metrics, supported public data services, and emergency-alert presentation.
  • DAB and DAB+ ensembles, service labels, metadata, and audio.
  • DRM where a compatible open decoder and sufficient CPU are available.

redsea and welle.io remain RDS/DAB candidates. Selected nrsc5 sources are already vendored for the browser. Pinned nrsc5/FFTW/FAAD2-HDC provenance, restricted-service handling, hostile-object bounds and distribution/codec review remain explicit; an FM comparison or shared artifact does not qualify every AM/media path.

Weather, Images, and Satellites

GOES HRIT / EMWIN and SATCOM products are implemented but were absent from the original general wishlist. Shared CCSDS/file machinery does not qualify Meteor, HRPT, another HRIT/LRIT RF service, radiosondes or the amateur-satellite profiles below.

  • SSTV Martin, Scottie, Robot, and common related modes.
  • WEFAX IOC 576 and 288.
  • NOAA APT where transmitting satellites remain available.
  • Meteor LRPT.
  • HRPT only with hardware capable of its required bandwidth.
  • Radiosondes including RS41, DFM, M10, iMet, and LMS6 families.
  • Amateur satellite AX.25.
  • CCSDS framing and telemetry.
  • GOMspace NanoCom modem formats.
  • AO-40/FUNcube protocols.
  • Satellite image and file reassembly.
  • Doppler tracking and frequency correction later.

gr-satellites remains an upstream mission/protocol candidate, not a bundled RF Sentry satellite runtime.

Manifest preflight must block or explain modes exceeding the active hardware/ capture bandwidth. HRPT's 2.4 MS/s example in the original plan is a constraint example, not an application-wide maximum rate. Actual geometry and supported capture rates remain authoritative; do not infer compatibility from a name.

ISM, Sensors, and IoT

These RF decoder paths are not in the current catalog. Received GOES DCS measurement parsing is a different integration; it does not establish an rtl_433/LoRa/ISM decoder.

  • rtl_433 supported weather sensors.
  • TPMS.
  • Utility meters.
  • Thermometers and environmental sensors.
  • Door, alarm, and remote-control protocols.
  • OOK pulse analysis.
  • FSK timing and bitstream analysis.
  • X10.
  • LoRa physical-layer detection and decoding.
  • Compatible unencrypted LoRa payload formats.
  • Meshtastic metadata only where accessible and authorized.

rtl_433 remains a source/fixture research candidate, not an installed appliance daemon or bundled browser decoder.

Trunking and Scanning

These integrations remain planned. The automatic scanner is also deferred; route purpose tags do not implement it.

  • P25 control channels and voice following.
  • DMR trunking and Capacity Plus-style metadata where supported.
  • NXDN trunking.
  • LTR and LTR-Net.
  • MPT-1327.
  • EDACS.
  • Conventional-channel scanning.

Trunk following changes the hardware tuning frequency and therefore needs an explicit controller lease. A second physical receiver may later hold a control channel while another follows voice traffic, but this must preserve the serial-keyed, independent-receiver architecture.

Experimental Analysis Tools

Keep the requested tools below, while distinguishing them from currently exposed detector/candidate features. An available spectral view or feature value does not establish every requested constellation, eye, symbol-clock or occupancy-analysis workspace.

  • Audio and RF spectra.
  • Constellation plots.
  • Eye diagrams.
  • Instantaneous-frequency plots.
  • Autocorrelation and cepstrum.
  • Symbol-clock recovery view.
  • Estimated baud rate and tone spacing.
  • Spectral entropy and flatness.
  • Envelope statistics.
  • Higher-order cumulants.
  • Cyclostationary analysis.
  • Drift and Doppler tracking.
  • I/Q imbalance and DC-offset monitoring.
  • Unknown-signal capture and comparison.
  • A/B spectrum comparison.
  • Long-term signal occupancy plots.

For an unidentified digital signal, show only actually measured facts. Requested tone spacing, symbol-rate or constellation tools must remain unavailable until implemented; missing metrics are not permission to invent a protocol name.

Scope and source maintenance

Keep this requested-mode inventory separate from the generated manifest catalog. A new implementation needs a truthful manifest, exact input/timing and output contracts, source/license notices, malformed-input tests and independent RF qualification. Update the relevant decoder chapter and delivery ledger without silently treating the whole family as accepted. Research candidates are indexed in Sources / Third-party.