Recover satellite images and telemetry from existing IQ and audio recordings.
View comparisons
Selected recordings compared with gr-satellites and SatDump. Where outputs are combined, both decoders are named.
Modulation, channel coding and packet format are listed separately. Each mission needs a matching receiver profile.
Native features run in the Rust receiver. Recording tests cover the inputs listed below; component tests do not yet establish end-to-end performance.
| Layer and format | Implementation | Evidence | Scope and limits |
|---|
Not implemented as complete native receivers: 8PSK, QAM, DVB-S2, AR4JA telemetry LDPC, SAR processing and arbitrary mission payloads. SSTV uses the SatNOGS reference path; no native gain is claimed. Capability details and source checks.
Reprocess archived passes to recover additional image segments and onboard measurements.
Offline analysis of recorded passes from your own or authorised satellite systems.
Both decoders process the same recording. These selected cases show recovery gains, not average performance across all recordings.
Geoscan and GASPACS provide camera images. Meteor recordings add daytime and infrared channels from the MSU-MR radiometer. The current Meteor M2-2 case compares standalone Frame lift with SatDump; older exploratory Meteor cases explicitly label combined outputs. Counters cover entire recordings; sliders show selected crops.
CELESTA frames with valid received FCS supply temperature, voltage and current values. Across seven observations, gr-satellites recovered 18 frames and Frame lift recovered 123, a gain of 105. Each frame contains five fields and is counted once. Five dot plots show the real readings against IQ window start: blue rings for gr-satellites, orange dots for Frame lift. Use the arrows to inspect a frame; totals cover the whole recording.
Matched-input decoding, comparisons with gr-satellites and SatDump, common-packet checks, image reconstruction and interpretation of five telemetry fields. CRC where the protocol supplies it; Reed-Solomon checks for Meteor.
No real-time guarantee, universal mission coverage, guaranteed gain, SLA or safety-critical qualification. Both MSU-MR outputs use the same unchanged SatDump image renderer; our independent receiver recovers frames from IQ.
Conversions follow the CSUM documentation, pages 4, 5 and 7 and the SatNOGS parser. All 615 values were checked. Window times mark the start of IQ analysis windows, not exact measurement times. Missing readings are not zero, and values are not interpolated. A blue ring and orange dot at the same position indicate one frame recovered by both decoders. Unique PDUs are counted within each observation, not globally.
Packet sets were repeatable, but the original requirement for identical raw KISS files was not met. This is a sensitivity analysis, not a passed preregistered test. The gallery does not establish universal superiority. These examples were not compared with Dire Wolf.
The correct gr-satnogs PD120 path produced readable SSTV images; we did not demonstrate a native gain. SSTV results. On the current Meteor M2-2 recording, standalone Frame lift retains every SatDump CADU; on some older Meteor recordings it still misses frames recovered by SatDump. The gallery therefore does not establish a universal lossless replacement. Instrument recordings and detailed limitations.
In coverage comparisons, hatching marks an area outside the reference decoder's image extent. No received pixels were removed. Additional coverage can still contain gaps; no missing content is interpolated.