rfSentry¶
Open the workstation in a browser on your LAN to tune an SDR connected to the Raspberry Pi. The Pi manages the receiver, antenna path and sample stream. Your browser turns those samples into audio, a waterfall, decoder results and an IQ history you can rewind.
Opening the web app leaves idle receivers asleep. For unattended GOES reception, enable a continuous HRIT job on the Pi. It can keep decoding while the browser is closed. The GOES workspace can read the Pi’s buffered records or connect directly to an optional Server for archived records and reconstructed products.
Start here¶
- Install the appliance or learn how to add a receiver.
- Follow basic operation for tuning, decoder selection, replay, and map use.
- Set up the optional workstation client or follow isolated browser support when operator-started diagnostics are needed.
- Use the interface guide for the workstation layout and the separate, deferred mobile roadmap.
- Read the end-to-end architecture before modifying acquisition, DSP, persistence, or temporal behavior.
- Use the decoder chapters for exact IQ geometry, synchronization, FEC, parsing, outputs, and tests.
- Consult the generated decoder catalog reference for manifest values taken from the shipped catalog.
- Check third-party provenance before changing vendored decoder or dataset sources.
- Consult validation and acceptance and the documentation map for evidence requirements, source ownership and historical checkpoints.
Design principles¶
Local first. Ordinary receiving, decoding, enrichment, mapping, search, and replay work without an Internet connection after local assets are built or hydrated. Received weather and satellite products are not replaced with Internet look-alikes.
Evidence before claims. A spectral shape is detector evidence, not a decoded protocol. Decoder output becomes validated only after the protocol's actual framing, parity, checksum, or FEC checks succeed. The UI distinguishes requested settings, confirmed state, estimates, and unavailable facts.
Capture time is authoritative. Raw observations retain capture-time provenance. Replay's contract is an as-of-reference-time view, not future RF evidence projected backward. Limits must remain explicit: for example, cached FAA metadata currently has no effective-date filter. See aviation replay guarantees, rather than treating the principle as blanket qualification of every enrichment path.
Work scales with change. Live aviation, map, decoder, and product views use keyed deltas, bounded presentation caches, and retained GPU resources. Archive size must not turn every live update into a full-history reconstruction.
Hardware identity is stable. USB serial numbers identify physical SDRs. Aliases identify operational roles. Transient device indices and USB bus paths are never authoritative identities.
Documentation scope
This site explains current implementation and explicit limits. The topic roadmaps own requirements and acceptance gates; current code does not close them. Selected verification records scoped results and limitations without a development diary.
Current capabilities¶
RF Sentry includes multi-lane acquisition, audio and spectrum DSP, a high-resolution detector/classifier, manifested decoder selection and Auto Start, IQ DVR/replay, station intelligence, aviation intelligence, globe and 2D mapping, local FCC and FAA enrichment, celestial globe rendering, and SATCOM HRIT/EMWIN acquisition and product handling.
Implemented decoder modules cover the IQ substrate monitor, FT8, FT4, NRSC-5 FM and AM, diagnostic NRSC-5 sanitizer variants, 1090ES/Mode S, 978 UAT, and GOES HRIT/EMWIN. Each has a dedicated technical chapter.
Module presence does not qualify an entire protocol family or complete an operator acceptance gate. Compare the shipped catalog with the requested decoder roadmap.