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
talk · advanced · evergreen · 2026–2026 on HN
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.
Up next
2 mo on HNWhy Are Birthrates Plummeting Worldwide?
Patrick Boyle
2 HN recommender · 2025–2026
8 mo on HNCasey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025
Better Software Conference
11 HN recommender · 2025–2026
6 mo on HNI Tried To Make Something In America (The Smarter Scrubber Experiment) - Smarter Every Day 308
SmarterEveryDay
6 HN recommender · 2025–2026
11 mo on HNLight Years Ahead | The 1969 Apollo Guidance Computer
TNMoC
11 HN recommender · 2021–2026
9 mo on HNThe Solar Gravitational Lens will Map Exoplanets. Seriously.
Launch Pad Astronomy
10 HN recommender · 2020–2025
7 mo on HN34C3 - The Ultimate Apollo Guidance Computer Talk
media.ccc.de
9 HN recommender · 2018–2025
6 mo on HNFalcon Heavy Test Flight
SpaceX
4 HN recommender · 2018–2026
7 mo on HNI Was SCARED To Say This To NASA... (But I said it anyway) - Smarter Every Day 293
SmarterEveryDay
9 HN recommender · 2023–2025
8 mo on HNStarbase Tour with Elon Musk [PART 1 // Summer 2021]
Everyday Astronaut
11 HN recommender · 2021–2024
5 mo on HNCarl Sagan - Pale Blue Dot
carlsagandotcom
5 HN recommender · 2011–2026
6 mo on HNApollo Guidance Computer Part 1: Restoring the computer that put man on the Moon
CuriousMarc
8 HN recommender · 2019–2024
5 mo on HNDr. Robert Zubrin with a brilliant answer to "Why Should We Go To Mars?"
Jamin Gray
3 HN recommender · 2016–2021
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