Exercise set
Spacecraft ADCS Pointing and Actuator Budget Exercises
Solved spacecraft ADCS exercises for pointing loss, gyro drift, slew torque, reaction-wheel momentum, desaturation, actuator margin and release gates.
These exercises focus on spacecraft attitude determination and control. They connect pointing error, sensor drift, slew kinematics, moment of inertia, actuator torque, reaction-wheel momentum, desaturation, mode timing and release evidence.
Use the calculations as screening checks. Flight release still needs sensor calibration, actuator qualification, flexible-body analysis, disturbance modeling, closed-loop simulation, fault detection, operations constraints and telemetry evidence from the same mission mode.
How to use these exercises
Use the set as an ADCS mode release review. Exercises 1 to 3 establish pointing allocation and attitude knowledge risk. Exercises 4 to 8 turn the required maneuver into rates, acceleration, torque and actuator margin. Exercises 9 to 13 check reaction-wheel momentum accumulation and desaturation authority. Exercises 14 to 18 add rate limits, control timing, sensor fusion, safe-mode pointing and the final release gate.
Before calculating, name the attitude mode, payload or link that depends on pointing, the inertia configuration, sensor availability, disturbance environment and operations timeline. A torque margin during a short slew does not prove a long imaging pass will avoid wheel saturation. A pointing error budget does not prove safe mode unless star-tracker outage, gyro drift, actuator limits and sun-pointing recovery rules are included.
Release Evidence Notes
ADCS release evidence should state pointing requirement, attitude mode, inertia basis, actuator set, wheel capacity, desaturation method, sensor availability, control law, rate limit, fault response and communications or payload mode that depends on pointing. A pointing margin is weak evidence if it is not tied to the actual attitude timeline.
The evidence package should keep estimation, control and actuation evidence separate. Sensor calibration, star-tracker outage behavior, gyro bias, residual gates and Kalman-filter tuning describe attitude knowledge. Slew profiles, torque limits, wheel momentum, magnetorquer authority and rate limits describe control authority. Flight rules, safe-mode entry, fault detection and telemetry thresholds describe operational survivability.
The release basis must also identify whether the value comes from analysis, hardware-in-the-loop testing, actuator qualification, flight-software simulation, operations rehearsal or prior flight heritage. ADCS is often limited by interactions among small effects, so source traceability matters as much as the arithmetic.
Engineering Boundary Notes
The exercises use rigid-body, first-order disturbance and margin estimates. They do not replace high-fidelity attitude simulation, flexible-mode review, actuator saturation analysis, sensor fusion validation, magnetic-field environment modeling, hardware-in-the-loop tests or flight rules. Treat pass results as evidence that a case deserves deeper simulation, not as standalone flight approval.
The main boundary is time. Pointing loss, gyro drift, wheel momentum, desaturation and safe-mode recovery all depend on duration and sequence. The second boundary is geometry: torque axes, magnetic-field direction, sensor field of view, antenna boresight and payload pointing frame must match the mode under review. A scalar margin can hide an axis-specific failure.
Common Release Mistakes
- checking slew torque without wheel momentum accumulation;
- approving link margin while pointing loss exceeds RF allocation;
- using gyro drift without outage duration and star-tracker reacquisition rules;
- ignoring actuator rate limits and software command latency;
- assuming desaturation is always available during payload or downlink modes;
- recording wheel capacity without telemetry thresholds and safe-mode action.
Another common mistake is treating desaturation as an independent maintenance activity. Momentum unloading can conflict with imaging, downlink pointing, power-positive sun pointing and thermal constraints. If the desaturation window is not available in the mission timeline, the wheel capacity margin is optimistic.
Do not validate ADCS only with nominal sensors. Star-tracker blinding, gyro bias growth, magnetometer disturbance, actuator saturation and residual outlier handling define how the spacecraft behaves when the perfect sensor set is not available. Safe-mode pointing and recovery evidence should be reviewed with the same seriousness as payload-pointing performance.
Scenario Map
The exercises move from pointing and sensor errors to slew torque, wheel momentum, desaturation, actuator limits, control timing and integrated release gates.
Exercise 1: Pointing Loss Margin
An RF link can tolerate 2.5\ \text{dB} pointing loss. Predicted worst-case pointing loss is 1.7\ \text{dB}. Compute remaining pointing-loss margin.
Solution
Engineering Comment
This margin belongs jointly to ADCS and communications. It should be reviewed against attitude uncertainty and antenna pattern data.
Plausibility Check
Predicted loss is below allocation, so the margin is positive.
Exercise 2: Pointing Error RSS
Star tracker error is 0.035^\circ, alignment error is 0.050^\circ and control jitter is 0.040^\circ. Estimate RSS pointing error.
Solution
Engineering Comment
RSS combination assumes independent contributors. Bias-like errors should be treated conservatively.
Plausibility Check
The result is larger than each contributor but smaller than their linear sum.
Exercise 3: Gyro Drift during Star-Tracker Outage
Gyro bias is 0.015^\circ/\text{s}. Star tracker is unavailable for 18 s. Estimate uncompensated drift.
Solution
Engineering Comment
Outage duration and bias estimation determine whether inertial propagation can protect pointing.
Plausibility Check
Hundredths of a degree per second over tens of seconds gives tenths of a degree.
Exercise 4: Slew Angle
A spacecraft must slew from nadir pointing to a target 22^\circ off-nadir. Convert the angle to radians.
Solution
Engineering Comment
Torque and momentum calculations should use radians even when operations constraints are stated in degrees.
Plausibility Check
Twenty-two degrees is a little less than 0.4 radians.
Exercise 5: Triangular Slew Rate
A triangular slew profile covers 0.384\ \text{rad} in 120 s. Estimate peak rate.
Solution
For a symmetric triangular profile,
Engineering Comment
Peak rate should be compared with actuator, sensor and payload smear limits.
Plausibility Check
A slow spacecraft slew should have milliradian-per-second rates.
Exercise 6: Slew Acceleration
The peak rate from Exercise 5 is reached in 60 s. Estimate angular acceleration.
Solution
Engineering Comment
Acceleration drives torque demand through inertia and can excite flexible appendages.
Plausibility Check
Slow slews have very small angular acceleration.
Exercise 7: Required Slew Torque
Moment of inertia about the slew axis is 42\ \text{kg m}^2 and acceleration is 1.07\times10^{-4}\ \text{rad/s}^2. Estimate torque.
Solution
Engineering Comment
This is ideal rigid-body torque. Disturbances, friction, wheel limits and margin should be added for release.
Plausibility Check
Small spacecraft slews can require millinewton-metre torques.
Exercise 8: Actuator Torque Margin
Available wheel torque is 0.012\ \text{N m} and required torque with margin is 0.0065\ \text{N m}. Compute margin.
Solution
The margin is 84.6 percent relative to requirement.
Engineering Comment
Check whether torque is available at the current wheel speed and bus voltage.
Plausibility Check
The available torque is almost twice the requirement, so a large positive margin is expected.
Exercise 9: Reaction-Wheel Momentum Accumulation
Disturbance torque is 2.0\times10^{-5}\ \text{N m} during a 2400 s imaging pass. Estimate accumulated wheel momentum.
Solution
Engineering Comment
Long mode durations can saturate wheels even when instantaneous torque is small.
Plausibility Check
Small torque over thousands of seconds gives hundredths of N m s.
Exercise 10: Wheel Capacity Margin
Wheel momentum capacity is 0.18\ \text{N m s} and predicted accumulated momentum is 0.048\ \text{N m s}. Compute capacity fraction used.
Solution
Engineering Comment
Capacity looks acceptable, but initial wheel bias and missed desaturation opportunities must also be included.
Plausibility Check
The predicted accumulation is about one quarter of the capacity.
Exercise 11: Saturation Time
Wheel capacity remaining is 0.12\ \text{N m s} and constant disturbance torque is 2.0\times10^{-5}\ \text{N m}. Estimate time to saturation.
Solution
Engineering Comment
Time to saturation should be compared with pass duration, safe-mode thresholds and planned desaturation windows.
Plausibility Check
Hundredths of N m s divided by tens of micronewton-metre gives thousands of seconds.
Exercise 12: Magnetic Desaturation Authority
Magnetorquer dipole is 0.18\ \text{A m}^2 and local magnetic field is 30\ \mu\text{T}. Estimate maximum magnetic torque.
Solution
Engineering Comment
Magnetic torque direction depends on field geometry, so maximum torque is not always available along the desired axis.
Plausibility Check
Magnetorquer torques are often in the micronewton-metre range for small spacecraft.
Exercise 13: Desaturation Time
Momentum to dump is 0.030\ \text{N m s} and usable magnetic torque is 4.0\times10^{-6}\ \text{N m}. Estimate ideal dump time.
Solution
Engineering Comment
Desaturation can take longer than payload passes, so operations planning matters.
Plausibility Check
Small torque dumping hundredths of N m s should take hours.
Exercise 14: Actuator Rate Limit
A gimbal can move at 0.8^\circ/\text{s}. A target transition requires 24^\circ. Estimate minimum motion time.
Solution
Engineering Comment
Rate limits can dominate mode transition time even if control torque is adequate.
Plausibility Check
Moving 24 degrees at almost one degree per second takes about half a minute.
Exercise 15: Control Sampling Margin
Closed-loop bandwidth is 0.08\ \text{Hz} and controller update rate is 2.0\ \text{Hz}. Compute update-to-bandwidth ratio.
Solution
Engineering Comment
This is a coarse sampling screen. Stability margins still require the implemented control law and delays.
Plausibility Check
The controller updates many times within one control-bandwidth period.
Exercise 16: Sensor Fusion Outlier Gate
Predicted attitude uncertainty is 0.08^\circ one sigma. A sensor residual is 0.31^\circ. How many sigma is the residual?
Solution
Engineering Comment
A nearly four-sigma residual should trigger outlier handling or sensor-health review.
Plausibility Check
The residual is about four times the expected uncertainty.
Exercise 17: Safe-Mode Sun Pointing Margin
Safe-mode requirement allows 12^\circ sun-pointing error. Worst-case predicted error is 7.5^\circ and sensor uncertainty is 1.2^\circ. Compute guarded margin.
Solution
Engineering Comment
Safe-mode pointing protects power and thermal survival, so the guard should include sensor and actuator faults.
Plausibility Check
The guarded error is below the limit, leaving a few degrees of margin.
Exercise 18: ADCS Release Gate
An ADCS release package has 18 required items. Sixteen are complete, but wheel desaturation simulation and star-tracker outage test are missing. Should the pointing mode be released?
Solution
The package is 88.9 percent complete, but release should fail because the missing items directly affect pointing continuity.
Engineering Comment
ADCS release is about timeline survivability: sensors, control law, actuators and operations must stay valid through the full mode.
Plausibility Check
Two missing core validation items are enough to block an attitude mode.
Validation Package Checklist
Before accepting a spacecraft ADCS mode, collect:
- pointing requirement, attitude mode and error budget;
- inertia basis, slew profile, torque demand and rate limits;
- wheel momentum capacity, initial bias and desaturation plan;
- sensor calibration, outage behavior, fusion residual gates and fault handling;
- control-law timing, actuator authority and safe-mode transition evidence;
- flexible-body, jitter, latency and disturbance assumptions explicitly bounded;
- hardware-in-the-loop, flight-software simulation or operations rehearsal evidence;
- telemetry thresholds for pointing error, wheel speed, residuals, rate limits and safe-mode entry;
- release decision tied to the same payload, communications or power mode that depends on pointing.
A complete validation package should make the attitude timeline reproducible. Another engineer should be able to trace when the spacecraft slews, how long it holds pointing, how momentum is removed, what happens when a sensor is unavailable and which telemetry condition forces a mode change before the margin is lost.