How We Diagnosed and Fixed the 2023 Voyager 1 Anomaly from 15 Billion Miles Away
Flight Software Workshop2 HN recommenders · recommended in 2 months, 2026-2026
17K views · 1 year ago · talk · evergreen
JPL's David Cummings presents at the 2025 Flight Software Workshop how the team diagnosed and fixed the 2023 Voyager 1 anomaly from billions of miles away. It walks through the flight computer and the memory fix.
Commenters recommend it for the remarkable remote reverse engineering done on decades-old hardware with no simulator.
35:25Saving Voyager 1! - Bruce Waggoner at !!Con 2024
!!Con
8K views • 2 years ago
1:10:43The Remote Agent Experiment: Debugging Code from 60 Million Miles Away
Google TechTalks
23K views • 14 years ago
40:05"Uptime 15,364 days - The Computers of Voyager" by Aaron Cummings
Strange Loop Conference
349K views • 7 years ago
16:04Jonathan Diegelman - Modeling Spacecraft Separation Dynamics in Julia
The Julia Programming Language
12K views • 5 years ago
13:01Pinging The Voyager 2 Probe (PART 2)
EEVdiscover
75K views • 9 years ago
1:18:03Dtrace Review
GoogleTalksArchive
19K views • 14 years ago
20:16How To Contact The Voyager 2 Probe (PART 1)
EEVdiscover
93K views • 9 years ago
52:59David Kriesel: Lies, damned lies and scans
Free and Open Source Software Conference (FrOSCon) e.V.
58K views • 11 years ago
19:59EEVblog 1547 (Part 1) - Contacting the Voyager 2 Space Probe
EEVblog
71K views • 3 years ago
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
619K views • 8 years ago
31:12The Insane Engineering of James Webb Telescope
Real Engineering
8.8M views • 4 years ago
1:03:40David Kriesel: Traue keinem Scan, den du nicht selbst gefälscht hast
media.ccc.de
7M views • 11 years ago
14:06Tomorrow Corporation Tech Demo
retrogameinternals
107K views • 3 years ago
0:17Mercury-Redstone 1 Launch failure (MR-1)
vogonford
305K views • 15 years ago
43:04"Stop Writing Dead Programs" by Jack Rusher (Strange Loop 2022)
Strange Loop Conference
468K views • 4 years ago
49:09Debugging with the Scientific Method - Stuart Halloway
ClojureTV
25K views • 10 years ago
49:03Apollo Core Rope Memory (Apollo Guidance Computer Part 30)
CuriousMarc
759K views • 3 years ago
28:11Why Everyone Is Talking About Data Centers In Space
Scott Manley
408K views • 10 months ago
42:15"Performance Matters" by Emery Berger
Strange Loop Conference
502K views • 7 years ago
30:41Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015
ReactEurope
472K views • 11 years ago
3 comments from Hacker News
A slight tangent here is a technical deep dive on Voyager 1 fixing a memory corruption error in 2023 by hand 15 billion miles away. Blows my mind of the reverse engineering done to achieve this ▶ this video
Here's a talk about how the Voyager team fixed the flight data computer on Voyager 1 when a memory chip went bad on it a few years ago. It goes over how the flight computer works and he walks through a few assembly routines. ▶ this video Some of the challenges they had to deal with while developing the fix: - The only source code they had for the flight data software was an OCR'd Microsoft Word document (with typos) that was likely scanned from a hard copy assembler listing printout. - The processor runs a custom instruction set developed by JPL for the Voyager mission. The documentation they had on the processor was incomplete. - Everybody who had designed the flight software was dead. - They had no assembler, no debugger, and no processor simulator. They had no testbed, the only two FDS processors were in space.
Based on the communication fix, they also didn't have a simulator, or tests, or complete source code, on a custom instruction set that wasn't well documented, so they had to reverse engineer how it worked. ▶ this video