Receive-only public modeNo transmit · No jamming · No spacecraft command path
Field communications for protected operations
Receive the field. Preserve the evidence.
A standalone SatComm workspace for orbital pass prediction, browser SDR analysis, optional device-station location, receiver architecture, confidence checks, and local receipts.
Pass PlanningStation ReadinessSignal ReviewLink BudgetField Records
ModeReceive-onlyNo transmit or command path
Signal66.31 dB SNRPublic SDR receipt loaded
StationOptional device fixPermission only after tap
No target loaded
Load TLEs or use demo orbit
SatComm command frame
One operating path from station to verified receipt.
Set the station, predict the pass, receive the signal, preserve the receipt, and verify the result. The interface is standalone, but the navigation is correctly integrated into MineSpace.us.
01 / 09Command Console
Swipe or use arrow keys to move through SatComm modules
SatComm module
Command Console
Use this as the operations overview before moving into pass, signal, or evidence work.
Orbit displayTarget controlsMission state
Track station, targets, receipts, accuracy, and receive posture from one surface.
Jump from high-level status directly into pass, receive, station, or receipt modules.
Orbit display stays decorative but connected to target and pass state.
StateConfirm system readiness
TargetLoad or select orbit
NextMove to pass windows
Field control
Live orbital console
ModeReceive-only
TargetNone
Max El—
Doppler—
Field checklist
Target import
TLE manager
SatComm module
Pass Windows
Review AOS/LOS timing, elevation windows, range, and Doppler estimates before receiving.
AOS / LOSElevationDoppler
Pass candidates are sorted for field review and export.
Antenna cues connect timing to azimuth/elevation decisions.
Frequency motion stays visible before signal capture.
PredictAOS/LOS candidates
PointAzimuth/elevation cue
NextReceive engine
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.
SatComm module
Receive Engine
Use the signal engine to evaluate receipt quality, SNR, bin width, noise floor, and hardware path.
FFTWaterfallReceipt hash
SNR, bin width, noise floor, and peak data stay visible and exportable.
WebGPU/WebGL path status is surfaced as an operating condition.
Hardware ladder moves from browser bench to field node.
BenchSpectrum and waterfall
MeasureSNR, bin, peak
ReceiptCopy/export evidence
Receive lab
Signal Bench
Receiver audio opens only when you choose it.
This page will not open a browser audio prompt on its own. Demo Signal works without any permission request. Open the browser prompt only when your receiver is connected and you choose it here.
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
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 benchmark
000f8d40dc03e926SNR66.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.
Public Browser SDR receipt loaded. Run Signal Test to create a fresh local receipt.
MineSpace Receive Engine
Build our own SDR beyond normal receivers.
Receive-only architecture: observe, estimate, classify, timestamp, and preserve evidence. No transmit chain, no jamming, no spacecraft command path.
Validated public receipt66.31 dB SNR437.801477 MHz peak · 23.4375 Hz bins · hash 000f8d40dc03e926
Target product jumpBrowser + hardware SDRWebGPU DSP, WebGL display, receipt ledger, hardware-agnostic capture, future MineSpace receiver board.
Windowing, FFT, averaging, peak tracking, SNR, waterfall history, anomaly flags, and reproducible local receipts.
RF front end, stable clocking, calibrated gain stages, IQ capture, GPS/PPS timing option, and open station profiles.
Beacon watch, Doppler-aware pass context, frequency drift traces, lock scoring, packet preview lanes, and field notes.
Hashable observations with settings, timestamp, path status, signal metrics, station data, and exportable MSRX evidence.
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 consistent field captures.
ThenMineSpace Receive Node
Dedicated receive board targets, 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.
SatComm module
Field Station
Set manual coordinates or ask the device only when the user taps the location button.
Manual modeDevice permissionGrid square
Device geolocation prompts only after the user taps the button.
Coordinates, accuracy, grid square, and hash remain local unless exported.
Receiver tiers are presented as practical field configurations.
LocateManual or device-approved
ClassifyStation tier
SaveLocal station profile
Field node
Station profile
Device location has not been requested.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.
SatComm module
Evidence Receipts
Record observations as local receipts until the user chooses to copy or export them.
Local-firstHashableExportable
Evidence objects stay readable, copyable, and exportable.
No background upload or hidden backend dependency.
Receipts can later be packaged for research review.
RecordManual or generated receipt
InspectReadable schema
ExportLocal JSON
Proof layer
Mission receipts
Receipt schema
Data object
{
"system": "MineSpace SatComm Field OS",
"station": "...",
"grid": "...",
"satellite": "...",
"aos": "...",
"los": "...",
"maxElevation": 0,
"dopplerHz": 0,
"mode": "receive-only",
"events": [],
"predictionStatus": "high-accuracy planning model",
"precision": {},
"uncertainty": {},
"hash": "..."
}
SatComm module
Accuracy Kernel
Run consistency checks before treating any pass plan or observation as reliable.
GeometryReplayConfidence
Geometry, Doppler, horizon, and replay checks are separated.
The UI distinguishes planning confidence from certified operations.
The operator sees the envelope, not just a single number.
ReplayGeometry consistency
CheckConfidence envelope
ExportVerification report
Scientific confidence
Accuracy Check
Not run in this sessionStatusReady 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. Certified mission operations require approved orbital data, calibrated hardware, and licensed operating authority.
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 real mission operations
Public pass planning is not a flight authority. Real mission operations require certified orbital propagation, calibrated station hardware, and approved operating procedures.
Next accuracy upgrade
Add certified orbital propagation, station survey calibration, clock discipline, antenna feedback, signal calibration, and richer capture metadata.
SatComm module
Mission Planner
Plan observation scenarios, not commands. The public route never transmits.
ScenarioConstraintReplay
Public mode builds safe receive-only plans.
Planner language avoids spacecraft control or transmit behavior.
Plans are exportable and replayable from the same inputs.
PlanReceive-only scenario
ReplayDeterministic plan
GateNo command path
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
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.
SatComm module
Deployment Path
Package the public console, receive node, receipts, launch checklist, and privacy boundary.
PWAField nodeReports
The public route is packaged for clean static deployment.
Receive nodes can be added without changing the public safety model.
Receipts remain on device until copied/exported.
PackagePWA and static route
FieldReceiver node path
ReportLaunch brief
Launch command
MineSpace Orbital launch path
Orbital Field OS 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 proof.
Mode 1Browser Console
Works in a browser for public demos, pass planning, link modeling, receipts, and mission scenarios.
Mode 2Receive Station
Add receiver audio, antenna details, station profile, local receipts, and optional network feeds.
Mode 3Edge Field Node
Add a field computer, station health, scheduled captures, storage rules, and future antenna control.
Mode 4Authorized Operations
Keep transmission, protected links, remote sensing, and commercial services separated until authorized.
Web AppStationOrbital DataPassesSignal BenchReceiptsReports
MineSpace SatComm Field OS is a receive-first orbital field console for satellite pass planning, RF capture, link modeling, mission receipts, and safe mission planning. It can be deployed as a static HTTPS Web App at MineSpace.us/SatComm/ and expanded into a local field node without changing the public operating model.
Launch checklist
Public launch checks
Public promise
MineSpace SatComm Field OS turns real satellite passes into repeatable field data: 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 safe to host today. Field receiver bridges, antenna control, transmission, remote sensing, and commercial services remain separate authorized modules.
SatComm module
Operating Rules
Keep education, amateur, experimental, and commercial lanes separate and explicit.
Receive-onlyLicensed lanesNo command path
Educational, amateur, experimental, and commercial lanes are distinct.
Mode selection updates the visible operating boundary.
The page communicates safe public operation without overclaiming authority.
Lane AReceive-only
Lane BLicensed
Lane CAuthorized only
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 future lawful experimental authority, commercial earth-station operations, protected links, and mission-specific licensing.
Platform roadmap
From public console to orbital 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.