Star trackers — arcseconds from a camera and a catalogue

A star tracker is the only sensor that gives absolute, drift-free attitude anywhere in the solar system. It photographs a patch of sky, centroids the stars, matches the pattern against an onboard catalogue, and solves for orientation. What separates a $10 k CubeSat unit from a $1 M flagship instrument is accuracy, robustness to stray light, and how quickly it recovers when lost.

Symbols used on this page are defined in the Nomenclature → attitude & rotations.

The specs that matter

SpecMeaningWhy it bites
Cross-boresight accuracyerror about the two axes perpendicular to the boresightthe headline number; typically 1–10″
Roll (about-boresight) accuracyerror about the viewing direction5–10× worse than cross-boresight — the reason to fly two heads
NEA (noise-equivalent angle)random, per-measurement noiseaverages down with $1/\sqrt N$ frames — the benign part
Low-frequency / thermal errorslowly-varying biasdoes not average down; usually the real budget driver
Update ratesolutions per secondsets how far the gyro must coast between fixes
Exclusion angleskeep-out cones for Sun / Earth / Moondrives head placement and mission geometry
Max slew raterate at which it still tracksif exceeded, stars streak and you lose lock during a manoeuvre
Lost-in-space timefull-sky acquisition with no priorthe recovery path after a safe-mode event
The roll-axis trap. Buying a tracker with 2″ cross-boresight accuracy does not give you 2″ three-axis knowledge — roll may be 10–20″. Either fly two heads at ~90° so each covers the other's weak axis, or budget for the poor axis explicitly.

Why geometry beats averaging

Star-direction measurements only constrain rotations perpendicular to the measured vector. Adding more stars in the same small patch averages the noise but does almost nothing for the rotation about that patch. This is exactly the conditioning story behind Wahba's problem — and the same effect as GDOP in GNSS:

Representative units

UnitClassCross-boresightNotes
Blue Canyon Standard NSTCubeSat / smallsat~6–8″very widely flown, compact, low power
Sodern Auriga / Hydrasmallsat → flagship~1–5″Hydra uses multiple heads into one processor
Ball CT-2020 / CT-6xxlarge spacecraft~1–3″long heritage on science missions
Terma HE-5ASmedium/large~2″robust radiation performance
Berlin Space Tech ST200/400CubeSat~10–30″very small and inexpensive
Jena-Optronik ASTRO APSflagship / GEO~1″APS detector, high radiation tolerance

Integration notes

  • Baffle design dominates real performance. The stray-light rejection of the baffle, not the detector, usually decides whether you keep lock near the Sun-exclusion limit.
  • Thermo-elastic alignment between the tracker and the payload boresight is often the largest term in the whole pointing budget — see the ADCS jitter budget, where it beats every electronic error.
  • Time-tagging. The solution is valid at the middle of the exposure, not at packet arrival; getting this wrong injects a rate-dependent bias straight into the filter.
  • Pair with the gyro, don't choose between them. The tracker bounds drift; the gyro bridges the gaps and rejects tracker outliers. That is exactly the MEKF.

Related: star-tracker theory · attitude & the MEKF · back to Hardware.