MineSpace SatComm — Receive Systems & Distributed Observation

Station controls

Orbital receive console

ModeReceive-only

TargetNone

Max El—

Doppler—

Field checklist

Station location confirmed Satellite status confirmed Receive chain armed / SDR recording ready Antenna path clear / az-el guide open Operating lane reviewed before any transmit-capable workflow

Target import

TLE manager

Feed URL Downlink MHz

Prediction layer

Next-pass candidates

Sat	AOS	LOS	Dur	Max El	Az Start/Peak/End	Doppler	Accuracy	Score

Azimuth / elevation

Pointing guide

Select a predicted pass to render the antenna track.

Receive lab

Signal Bench

Signal Bench is idle. Demo Signal runs without opening any browser prompt.

Use the demo beacon with no browser prompt, or connect receiver audio only after choosing the two-step audio flow. This bench records lock events and creates receipt data; it does not transmit.

Link model

Quick link budget

Range km Frequency MHz TX EIRP dBW RX gain dBi Loss margin dB Noise floor dBm Bandwidth Hz System temp K

Waiting for calculation.

Browser SDR engine

Signal Workbench

A receive-only browser signal workbench for spectrum review, waterfall history, field receipts, and receiver-chain demos. It does not transmit.

Compute pathCHECKChecking browser signal path

Display pathCHECKWebGL when available, Canvas fallback always

Signal quality—Run a signal test

Sample view—0 frames

Public Browser SDR receipt · receive-only benchmark000f8d40dc03e926

SNR66.31 dBsignal over noise

Peak437.801477 MHz+1,476.6 Hz offset

Noise floor-76.53 dBBlackman-Harris window

Bin width23.4375 HzFFT 2048 · 48 kHz

ComputeWebGPUbrowser signal path active

DisplayWebGLcapable display path

Center437.800000 MHz48 kHz span

Frame3,787receipt frame index

Safety boundaryReceive, display, estimate, and save receipts only. No transmit or spacecraft command path.

Input profile FFT size Window Mode Center MHz Span kHz Display gain dB Averaging

Public Browser SDR receipt loaded. Run Signal Test to create a fresh local receipt.

MineSpace Receive Engine

Develop the Receive Chain.

Receive-only architecture: observe, estimate, classify, timestamp, and preserve evidence. No transmit chain, no jamming, no spacecraft command path.

Reference public receipt66.31 dB SNR437.801477 MHz peak · 23.4375 Hz bins · hash 000f8d40dc03e926

Receiver development pathBrowser + hardware SDRWebGPU DSP, WebGL display, receipt ledger, hardware-agnostic capture, a planned MineSpace receive-board design target.

01Browser DSP Core

Windowing, FFT, averaging, peak tracking, SNR, waterfall history, anomaly flags, and reproducible local receipts.

02Receiver Hardware Layer

RF front end, stable clocking, calibrated gain stages, IQ capture, GPS/PPS timing option, and open station profiles.

03Signal Intelligence Layer

Beacon watch, Doppler-aware pass context, frequency drift traces, lock scoring, packet preview lanes, and field notes.

04Receipt Ledger

Hashable observations with settings, timestamp, path status, signal metrics, station data, and exportable MSRX evidence.

Architecture tier Input bandwidth kHz FFT size ADC / sample depth bits Clock stability ppm Noise figure dB Channels Evidence mode

Frequency bin23.4375 Hzsample rate / FFT size

Theoretical quantization span72.2 dBapprox. 6.02N + 1.76

Clock drift at center218.9 Hzppm × center frequency

Program postureReceive-onlyno transmit path

NowBrowser SDR Engine

Public receipt benchmark, WebGPU/WebGL path checks, waterfall, spectrum, and exportable records.

NextMineSpace Receiver Adapter

Hardware-agnostic IQ ingest, station profiles, calibrated noise/gain settings, and repeatable observation captures.

ThenMineSpace Receive Node

Dedicated receive-board requirements, time discipline, edge storage, antenna metadata, and passive multi-node comparison.

MSRXEvidence Publication

Turn verified signal observations into research receipts without exposing transmit or command capability.

Generate Receiver Plan to create a receive-only MineSpace SDR architecture receipt.

MineSpace SatComm · Deep Space Acquisition

Acquire the Carrier First.

A receive-only planning and analysis laboratory using public deep-space mission parameters and custom carrier definitions. It combines ephemeris, Doppler, narrowband integration, clock discipline, and array-processing concepts in one testable acquisition chain.

Carrier firstDe-DopplerCoherent integrationArray phase closureNo transmit

Target model

Deep-space link definition

Mission preset Nominal carrier MHz Range AU Range rate km/s TX power W TX antenna gain dBi Telemetry rate bps Receiver dish diameter m Dish efficiency % System temperature K Front-end loss dB Atmosphere / weather dB Solar interference penalty dB Coherent array nodes Array phase efficiency % Coherent integration s Residual frequency error Hz Residual drift Hz/s Decode threshold Eb/N₀ dB Residual acceleration Hz/s² Observation duration min Frequency schedule step s

Receive-only boundaryThis module estimates, records, and analyzes public downlinks. It contains no uplink, command, jamming, interference, or access-control bypass path.

Reality gate

Carrier ≠ Telemetry.

The harmonic insight is useful after downconversion. Phase recurrence, symmetric sidebands, and cyclostationary structure can reject false peaks and improve lock confidence. They do not replace antenna area, low system temperature, or an accurate Doppler model.

Observed center—topocentric Doppler model

RX gain—beam and pointing

Received power—after modeled losses

Array gain—phase-efficient combining

Calculating carrier feasibility…

Run the model to classify the acquisition path.

Calculating telemetry feasibility…

Decode margin is evaluated independently from carrier visibility.

Equivalent dish for carrier——

Equivalent dish for telemetry——

Coherent block ceiling—from residual frequency/drift

Surface RMS target—approx. λ/16 reflector criterion

Acquisition chain

Deep-Space Acquisition Requirements

01 / EPHEMERISReplace TLE logic with deep-space state vectors.

Use observer geometry, light time, range rate, and solar elongation. Deep-space spacecraft cannot be tracked rigorously from Earth-orbit TLEs.

02 / CLOCKDiscipline every receiver and local oscillator.

GNSSDO or better reference, PPS timestamping, oscillator calibration, and explicit residual-frequency uncertainty before long integration.

03 / DE-DOPPLERSearch frequency, drift, and acceleration.

Mix the expected trajectory to baseband, integrate short coherent blocks, then noncoherently stack while the candidate track remains phase-consistent.

04 / ARRAYCorrelate stations instead of merely averaging spectra.

Calibrate delay, phase, gain, polarization, and clock offset per node; then combine voltages coherently or correlate post-capture.

05 / HARMONIC GATEUse recurrence to identify the spacecraft line.

Test carrier continuity, symmetric sidebands, symbol/subcarrier periodicity, and phase closure across independent stations.

06 / RECEIPTPreserve raw IQ and reproducible evidence.

Hash capture metadata, ephemeris, tracking polynomial, clock state, processing settings, and candidate score before making a claim.

07 / CARRIER FIRSTProve detection before attempting telemetry.

A stable narrow line after independent de-Doppler trials is the first milestone. Frame synchronization and coding come only after link margin exists.

08 / DECODEApply public modulation and CCSDS knowledge.

Symbol timing, residual carrier recovery, frame sync, convolutional/Reed-Solomon or mission-specific coding, and bit-level validation require much more C/N₀.

Ephemeris and frequency plan

Build the topocentric de-Doppler track

Paste JPL Horizons observer-table output, JSON, key/value data, or CSV. A multi-row ephemeris lets SatComm derive frequency rate and acceleration instead of trusting operator placeholders.

Ephemeris source Target command / ID Source generated UTC Source reference / query digest

Base Doppler—from range rate

Track rate—Hz/s polynomial term

Pointing—RA / Dec not loaded

Solar elongation—low angles can dominate noise

UTC offset	Predicted carrier MHz	Doppler Hz	Frequency rate Hz/s
Build a frequency schedule.

Coherent search simulator

Frequency × drift acquisition map

Search span Hz Drift span ±Hz/s Synthetic true offset Hz Synthetic true drift Hz/s

Search not run.

The simulator uses the current link budget to show how a phase-coherent carrier emerges only near the correct frequency and drift hypothesis.

Harmonic and recurrence discriminator

Confirm structure without inventing gain

Sideband symmetry % Independent station confirmations Expected subcarrier / cycle Hz Harmonic orders tested

Carrier continuity—

Drift closure—

Sideband symmetry—

Station phase closure—

Harmonic gate not run.

This stage raises identification confidence only after the link model predicts a detectable line.

Real capture path

Analyze recorded baseband IQ

Use an external X/Ka downconverter and SDR to record baseband. Stereo WAV is interpreted as I/Q; mono WAV as a real-valued channel; CF32 is interleaved float32 I,Q. Processing is local in the browser.

Capture file Format

Raw sample rate Hz Predicted baseband offset Hz Predicted drift Hz/s RF tuner center MHz FFT size Off-target control shift Hz Time-shift control seconds

Persistent blocks—

Off-target control—

Time-shift control—

No capture analyzed.

Load a local IQ or WAV file; no data leaves the device.

Observation identity

Station, clock, and carrier provenance

Observation mode Capture start UTC Station name Latitude ° Longitude ° Altitude m Time reference Clock uncertainty µs Local oscillator reference LO uncertainty Hz

Active receive frequency independently verified.
The selected search center is tied to a dated public schedule, observatory report, or other reproducible source—not merely the preset.

Carrier verification referenceOperator note

Immutable promotion gate

Evidence classification

SIMULATION

No raw capture has crossed the evidence gate.

Candidate SNR threshold dB Control margin threshold dB Frequency residual tolerance Hz Drift residual tolerance Hz/s

Independent raw-IQ processing reproduced the track.

Independent analysis receipt SHA-256

A second calibrated station reproduced the predicted track.

Second-station receipt SHA-256

Deep-space receipt

Reproducible observation object

Run the model, acquisition search, or capture analyzer to create a deep-space receipt.

Audit an earlier receipt

The included v54 Parker receipt should classify as SIMULATION because it has synthetic truth fields and no capture analysis.

Engineering basis

Public mission facts used by the presets

JPL Horizons APIObserver geometry, topocentric range, range rate, pointing, and reproducible query parameters. NASA Voyager spacecraft23-watt class transmitter, 3.7 m high-gain antenna, 160 bps normal X-band telemetry. JPL Voyager TelecommunicationsCoherent and non-coherent X-band carrier assignments and telecommunications architecture. ATA Voyager detectionIndependent narrowband detection of Voyager 1 near 8420.43 MHz with sub-hertz spectral width. Parker mission reviewKa-band high-rate science downlink architecture and solar-geometry constraints. Amateur deep-space detectionPublished evidence that a 1.8 m amateur station detected Parker at 32 GHz. NASA Deep Space Network34 m and 70 m aperture context for the difference between carrier detection and telemetry recovery.

Operational frequencies and active downlink windows must be verified at observation time. The Parker Ka preset uses a nominal deep-space Ka search center, not a claim of its exact current channel. Voyager coherent channel values are public engineering assignments, but received frequency still moves with coherent uplink state and Doppler.

MineSpace SatComm · Distributed Receive Federation

Operate Within RF Capability.

Discover public receive infrastructure, enroll owner-approved nodes, match targets by documented RF capability, run baseband processing locally, and combine independent evidence without overstating array coherence.

Receive onlyOwner consentBand matchedLocal DSPHashed receiptsCoherent only when clocked

Mission target

Define the receive requirement

Target source Target name Center frequency MHz Required bandwidth kHz Capture duration s Minimum elevation ° Required product Combination goal Observation start UTC

Choose a target or load a verified active transmitter. Template frequencies are planning aids and must be verified at observation time.

Public discovery

Network and transmitter sources

SatNOGS Network stations API SatNOGS recent observations API SatNOGS DB transmitters API

Import registry / receipts

Public APIs are read-only discovery inputs here. Scheduling or controlling third-party stations requires their owner and the provider's authenticated workflow.

Capability map

Where the receive nodes are

Demo nodes are illustrative until replaced by imported or enrolled station metadata.

Station registry

Documented capability, not assumed coverage

Include clearly marked demo nodes in planning

Node	Coverage	Timing / IQ	Source	Status

Enroll a receive node

Owner-approved capability record

Node name Node ID Owner / operator Latitude ° Longitude ° Altitude m Minimum RF MHz Maximum RF MHz Instantaneous bandwidth kHz Antenna aperture m Timing source Clock uncertainty µs LO uncertainty Hz Raw IQ Pointing Connector

I own or operate this station, or I have explicit permission to enroll its receive capability and submit observation receipts.

No third-party station is enrolled automatically. Discovery records remain read-only until an owner-approved capability record exists.

Baseband edge engine

Capture and analyze IQ in the browser

Idle

Source Sample rate Hz RF center MHz Expected offset Hz Expected drift Hz/s Capture seconds Bridge URL Local IQ file

Peak offset—baseband estimate

Drift—block regression

SNR—peak over median

SHA-256—raw capture identity

The virtual receiver validates DSP only. A sky receipt requires actual antenna hardware, calibrated RF metadata, and a preserved raw capture.

Observation scheduler

Route a job to eligible nodes

Federation API URLNode write token

Jobs are receive-only requests. Public discovery nodes are never commanded; only enrolled nodes may explicitly accept work.

Match nodes, then create an observation job.

Distributed evidence

Combine receipts without overstating coherence

Fusion modeFrequency closure tolerance HzDrift closure tolerance Hz/sImport node receipts

No independent receipts loaded.

A coherent array requires a common reference, sample-level time alignment, phase calibration, and compatible raw IQ. Otherwise SatComm automatically uses noncoherent or evidence-only fusion.

Federation boundary

Distributed System Boundary

Discovery
Read public station, transmitter, and observation metadata. Unknown RF coverage is never treated as a match.

Execution
Owner-approved nodes receive opt-in observation jobs, process baseband locally, and publish small signed or hashed receipts rather than unrestricted raw streams.

Combination
Independent detections strengthen evidence. Coherent gain is credited only when clocks, sample timing, frequency reference, and phase are actually controlled.

Receive-only safety rule: this module cannot transmit, tune or command third-party equipment without its owner-controlled adapter, command spacecraft, bypass access controls, decrypt protected links, jam, interfere, or represent a synthetic or demo node as a real observation.

Field node

Station profile

Device location has not been requested.

Station name Call sign / ID Latitude Longitude Altitude m Station class

Device geolocation permissionNot requested

Fix stateManualStation coordinates are manually entered.

Accuracy—reported by device when available

Grid squareFM17gmderived locally from station coordinates

Last receipt—no location receipt yet

Tap Use Device Location only when you want this page to ask your browser or device for location permission. Coordinates stay in this browser until you export or clear them.

PrivacyLocal-first station profile

UsePass planning and receive receipts

BoundaryNo transmit or command path

Permission discipline

Device location is never requested automatically. The browser prompt appears only after the visitor chooses Use Device Location. The resulting station receipt stays local unless copied or exported.

Build sheet

Station kit ladder

Tier 0 / Receive Bench

Receiver, simple antenna, pass console, signal capture, and mission receipts.

Tier 1 / Portable Field Node

Handheld directional antenna, phone/compass guide, tripod, battery, and local web app.

Tier 2 / Autonomous Station

Mini PC, fixed or rotatable antennas, station health, auto-observation jobs.

Tier 3 / Experimental Lane

Lawful experimental/commercial expansion separate from amateur operations.

Evidence layer

Mission receipts

Receipt schema

Data object

{
  "system": "MineSpace SatComm Receive Systems",
  "station": "...",
  "grid": "...",
  "satellite": "...",
  "aos": "...",
  "los": "...",
  "maxElevation": 0,
  "dopplerHz": 0,
  "mode": "receive-only",
  "events": [],
  "predictionStatus": "high-accuracy planning model",
  "precision": {},
  "uncertainty": {},
  "hash": "..."
}

Scientific confidence

Accuracy Check

Not run in this session

StatusReady to checkhigh-accuracy pass math

Orbit equation—orbit equation check

Horizon crossing—rise / set timing check

Peak timing—best visibility time

Doppler estimate—frequency shift cross-check

Geometry closure—station-to-sky geometry check

Confidence gate

Planning model active. Operational use requires approved orbital data, calibrated hardware, applicable licensing or authorization, and approved procedures.

Run the accuracy check to verify the current pass model and export a clear report.

Confidence range

Pass confidence envelope

Run a pass prediction to generate the pass confidence range.

What the accuracy check verifies

Orbit math, station geometry, horizon crossings, peak visibility, Doppler estimates, and receipt replay consistency for the current planning model.

Before operational use

Public pass planning is not flight authorization. Operational use requires approved orbital data and propagation methods, calibrated station hardware, applicable licensing or authorization, and approved procedures.

Next accuracy upgrade

Add certified orbital propagation, station survey calibration, clock discipline, antenna feedback, signal calibration, and richer capture metadata.

Planner without actuation

Hold / reposition / replay planner

ObjectiveNo plan

Δv Budget—

Risk—

Replay—

Select a pass, choose a mission objective, then build a safe planning scenario. This page does not send commands or signals.

Planning envelope

Field node constraints

Objective Field nodes Position uncertainty meters Clock uncertainty microseconds Network latency ms Hold corridor degrees Max Δv m/s Altitude offset km Phase offset degrees Plan steps

Safety boundary

This planner is for safe mission design only. Spacecraft maneuvering, Earth-station transmission, remote sensing tasking, and orbital operations require authorization, oversight, and mission-specific safety approval.

Scientific discipline

Every planning value is calculated consistently, recorded in the receipt, and replay-checked so the same inputs produce the same plan.

Human outside the fast loop, safely

The planner models automated field decisions while keeping policy, authorization, constraints, and stop conditions declared before execution. No spacecraft command path exists in this public build.

Deployment path

MineSpace SatComm deployment path

SatComm Receive Systems starts as a public web console, then grows into field receiver stations and authorized mission environments. The public flow stays simple: open the console, choose a station mode, load targets, predict passes, capture signals, and export evidence.

Mode 1Browser Console

Browser implementation supports public demonstrations, pass planning, link modeling, receipts, and mission-scenario analysis.

Mode 2Receive Station

Integrate receiver audio, antenna metadata, station profiles, local receipts, and optional owner-authorized network feeds.

Mode 3Edge Field Node

Integrate an edge computer, station-health records, scheduled receive captures, storage rules, and optional owner-authorized antenna-pointing interfaces.

Mode 4Authorized Operations

Keep transmission, protected communications, remote-sensing tasking, and commercial services separated behind their own authorization, licensing, security, and safety requirements.

Web AppStationOrbital DataPassesSignal BenchReceiptsReports

MineSpace SatComm Receive Systems is a receive-first technical console for satellite pass planning, RF capture analysis, link modeling, observation receipts, and mission planning. It can be hosted as a static HTTPS web application at MineSpace.us/SatComm/ and extended with owner-authorized local receive-node services.

Deployment checklist

Public deployment checks

Host over HTTPS or localhost so optional receiver audio can be connected when the visitor chooses it Upload the full SatComm Receive Systems package together Confirm the deployed version matches the current package before each public demonstration Verify the correct operating lane before any transmit-capable workflow Confirm orbital data can be fetched or pasted manually Run Accuracy Check and export the report before public demos Export a mission receipt after every field capture

Public promise

MineSpace SatComm Receive Systems supports repeatable receive-side observation workflows for satellite passes: predict, listen, model, capture, verify, and export.

Privacy promise

Receipts, station profiles, and mission scenarios stay on the user’s device until exported or connected to a chosen backend.

Infrastructure promise

The public console is designed as a receive-only interface. Production hosting still requires normal application, privacy, dependency, and security review. Field receiver bridges, antenna control, transmission, remote sensing, and commercial services remain separate authorized modules.

Lane A

Receive-only / education

Safe starting lane. Observe public signals, model passes, capture audio/IQ, build receipts, and avoid transmission until qualified.

Lane B

Licensed amateur operation

For licensed amateur operators. Contacts and experiments must remain noncommercial and compliant with amateur-service rules.

Lane C

Experimental / commercial

Separate design lane for licensed experimental or commercial operations, protected communications, and mission-specific authorization.

Platform roadmap

Console to Field Infrastructure

Public console: predict passes, understand visibility, and prepare a field station.
Signal capture: listen, record, and preserve mission receipts from real satellite passes.
Mission planning: test hold, reposition, and replay scenarios safely before any real-world operation.
Field stations: expand into receiver nodes with antennas, timing, local storage, and station health.
Authorized operations: keep transmission, protected links, remote sensing, and commercial services in their proper approval lanes.