FLIGHT MANUAL / 07 · SYSTEMS
GNSS & survey navigation
GNSS accuracy comes from visible, valid transmitters and their geometry—not from a receiver merely being powered.
Valid solution
A receiver needs sufficient visible transmitting satellites, usable line of sight, compatible constellation state, and acceptable geometry. Four transmitters are the normal minimum for a 3D fix and clock solution; more can improve resilience and dilution of precision.
Read the status panels
Visible Satellites is the receiver's current observation set. Accuracy is the computed solution uncertainty. No Signal means the solver has no valid set; it must not coexist with a fabricated accuracy value. RemoteTech control state and GNSS validity are displayed separately.
Constellation design
- Choose orbital altitude and plane count for the target body.
- Distribute satellites so multiple planes remain visible from the service region.
- Equip every navigation satellite with a transmitter, power, control path, and time reference.
- Use SCANsat coverage overlays to compare mapping gaps with navigation geometry.
- Test failure of one plane and one gateway before calling the system operational.
SCANsat integration
Survey coverage and navigation service share body, biome, geometry, mission-readiness, and telemetry context. Mission Control can correlate map gaps with available GNSS geometry; neither system silently completes the other's science or contract objectives.
Solution quality terms
Satellite count tells how many transmitters passed visibility and validity checks. GDOP describes geometry across position and time; PDOP focuses on three-dimensional position. Estimated accuracy combines geometry with the configured ranging error model.
A numeric accuracy is shown only for a valid solution. The UI reports why candidates were excluded: occluded, unpowered, incompatible, stale, or outside service range.
Commission a constellation
- Launch one plane and verify transmitter identity, power margin, clock state, and RemoteTech control.
- Populate remaining planes and confirm the receiver sees unique satellites rather than duplicate vessel modules.
- Sample coverage at multiple latitudes, altitudes, and body rotations.
- Compare the GNSS overlay against SCANsat coverage gaps.
- Disable one satellite and one gateway, then verify graceful loss and recovery.
No fix checklist
- Confirm the receiver is on and not reporting local-only test data.
- Confirm each constellation craft has the transmitter module rather than another receiver.
- Check line of sight and body occlusion.
- Check RemoteTech routes and electrical power on the constellation craft.
- Inspect visible IDs and geometry rather than trusting vessel count alone.