Advanced GNC: estimation, autonomous navigation and control
Move from the idea of “knowing where you are” to an architecture that estimates state, carries uncertainty, commands actuators and remains safe when sensors disagree.
Mastery objectives
- explain quantities, units, assumptions and uncertainty
- repeat simple calculations without a black box
- identify interfaces, limits and degraded modes
- turn the result into an operational or architecture decision
1. State, measurement and model are three different things
A spacecraft never knows its perfect position, velocity and attitude directly. It carries an estimated state. Engineers often gather unknowns in a state vector x: position, velocity, attitude, sensor biases and sometimes environmental parameters. The symbol x therefore denotes a coherent set of variables rather than one sensor reading.
A measurement z comes from a sensor: a star observed by a star tracker, acceleration from an inertial unit, radio range, terrain imagery or lidar altitude. A model predicts how the state should evolve. Estimation compares model and measurements and must also preserve uncertainty. A number without uncertainty can be dangerous because the controller may act as if the information were exact.
2. Navigation: where are we, and how sure are we?
A Mars mission uses different navigation regimes. During cruise, the Deep Space Network helps determine trajectory. Near Mars, images, inertial sensors and altimetry can become more important. During EDL—entry, descent and landing—the available time is too short to wait for ground correction.
The useful question is not only “where am I?” but “what region of states remains plausible?” Error covariance represents that confidence. If lateral uncertainty becomes larger than the safe landing zone, the response must be operational: change trajectory, change target or enter a more conservative mode.
3. Kalman filtering: correct a prediction with an imperfect measurement
The Kalman filter is a family of estimation methods that combines a model prediction with a noisy measurement. Intuitively, if the model is uncertain and the sensor precise, the update follows the sensor more strongly. If the sensor becomes unreliable, the estimator should rely more on prediction. The gain is not a magic constant; it comes from assumed uncertainties.
Real spacecraft use nonlinear models and may rely on extended, unscented or other filters. The engineering loop remains recognizable: predict, measure, compare the innovation, update the state and check whether residuals are consistent with the assumed noise model.
4. Attitude, quaternions and reference frames
Pointing a vehicle requires clear reference frames: inertial, body, local-level, sensor and actuator frames. A frame error can create a numerically correct command along the wrong axis. Quaternions represent attitude without some singularities of Euler angles and make rotation composition convenient.
The operational lesson is more important than memorizing every quaternion identity: every transform must state from which frame to which frame it maps a vector, and the software must normalize and cross-check attitude estimates.
5. Guidance, navigation and control are separate responsibilities
Guidance computes what the vehicle should do to reach an objective. Navigation estimates the real state. Control converts the error between objective and state into actuator commands. A mission succeeds only if those interfaces are sound: brilliant guidance fed by a false state commands the wrong maneuver, and perfect control cannot execute a physically impossible trajectory.
For Mars, degraded modes should preserve this separation. Losing one sensor does not automatically mean losing all guidance. The system can reduce performance, switch sensors, increase margins or stop a critical sequence.
6. Actuators, saturation and control authority
Reaction wheels, thrusters, aerodynamic effectors and descent engines have limits. A wheel can saturate in stored momentum; a thruster has minimum and maximum thrust; an engine does not respond instantaneously. The controller must know the authority that actually exists.
A computed +120% command has no physical meaning. If software asks for more than the actuator can deliver, error can integrate and destabilize the loop. Verification must therefore include saturation, delay, biased sensors and failed actuators.
7. Autonomous surface navigation and rendezvous
On Mars, a rover or crewed vehicle may have to localize without immediate Earth assistance. Cameras, lidar, inertial sensing and maps can be fused to estimate motion. Rendezvous adds relative range, angle and closing-rate measurements.
Autonomy is not the absence of rules. It needs explicit limits: maximum speed when localization quality falls, safe-return distance, stop conditions and thresholds that request help.
8. Worked example: combine two simple estimates
Assume two independent estimates of one distance: 100.0 m with a standard uncertainty of 4.0 m and 106.0 m with a standard uncertainty of 2.0 m. In inverse-variance weighting, the weights are 1/4² = 1/16 and 1/2² = 1/4. The second measurement therefore receives four times the weight.
The weighted mean is (100×1/16 + 106×1/4) / (1/16 + 1/4) = 104.8 m. This is not a full Kalman filter, but it shows the principle: confidence changes the update. If uncertainty assumptions are wrong, the final estimate is wrong too.
Progressive exercise
A rover estimates lateral position at 12 m ± 6 m from odometry and 20 m ± 3 m from vision. Compute the inverse-variance weighted mean. Then explain what happens if dust partially obscures the camera but the software fails to increase its uncertainty.
Mini-project
Define the GNC architecture of a pressurized vehicle travelling 40 km from a Mars base: sensors, estimated state, update rates, actuators, degradation thresholds, return procedure and the data that must be recorded to reconstruct an anomaly.