Saving Voyager 1!
summary
Voyager 1 loses all downlink telemetry in late 2023 while 15 billion miles away and a tiny Flight Data System failure stops frame markers; the team diagnoses 256 contiguous words corrupted by a single RAM chip flipping the fifth bit, crafts 20 hardware pokes and uploads staged binary patches (March 1, April 20, May 18) to relocate 14 code fragments and restore frame generation, recovering engineering telemetry and science at ~1.2 kilobits per second from a 47‑year‑old spacecraft with 22.5 hour one‑way latency.
AI-written summary · about
chapters (11)
- 0:00Mission overview
- 1:08Science and instrumentation
- 5:03Spacecraft status and health
- 8:38Onboard flight computers
- 9:50Anomaly detection
- 13:22Diagnosis strategy
- 19:20Identifying the root cause
- 24:22Executing the repair
- 28:21Restoring science data
- 30:35Final restoration and lessons
- 33:32Future goals and legacy
related talks
01h 01mFly the Enterprise: Applying Aviation Lessons to DevOps Teams
26mThe software bug all stars - and what we can learn from them
01h 08mSmall Steps, Giant Leaps: Engineering Lessons from Apollo
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
57mClosing Keynote
31mOver Nine Billion Dollars of SRE Lessons - the James Webb...
40mAn Average Working Day on Visionary NASA Projects
30mSoftware Development Lessons from the Apollo Program