I just learned the voyager probes are expected to go silent by the early 2030's. Kinda wish we had other long running deep-space exploration experiments to take their place!
I'd be fascinated to know the exact nature of the failure. What analog processes cause a CMOS memory IC that we like to think of as being discrete to be consistently wrong at reading its stored values? I'd like to know all the way down to the interaction between the gates and traces. Did some pathway erode due to constant interchange of charge carriers? Did thermal cycles or stress cause one of the mechanical interconnects on the package to fracture and no longer conduct? If so, which one?
According to AI, one type of failure mode in those early aerospace CMOS chips was sudden parasitic current in the PNPN junction being caused by a high energy particle, shorting paths to ground melting metal. Though that sounds rare. Another option is a total ionizing dose of radiation over time, which creates electron-hole pairs in the gate oxide, leading to trapped positive charge. That makes NMOS get closer and closer to turning on when they shouldn't, and PMOS requiring more voltage to turn on. It's fascinating to me that there came a specific moment in time when the chip managed to work, and the next clock cycle it didn't. I'd love to see the I_D vs. V_GS charts showing a before and after. So I had Claude make a plausible approximation. You can too by asking your AI agent of choice by basically just pasting in my comment!
Nice! This appears to be vibecoded, but what was the process? Was there any original research or AI did most/all of it? Was this double checked against any authoritarive source?
Thanks! Yes, Claude did a lot of the heavy lifting. For research, I mainly used NASA's archives on these probes, and in total I gathered about 3 GB of files.
With reportedly over 90% of code at even Anthropic written and tested by AI, what is not vibe coded in 2026? The term has lost all meaning when most applications are mainly AI generated code. Are people still writing While loops by hand?
Execution is becoming all that matters. This is a great project and congrats to the creator on putting it together, whether he did by punchcard coding or prompting.
Inside a nuclear battery: https://rshekhar.com/voyager/v1/rtg-1
The data computer's memory chips: https://rshekhar.com/voyager/v1/bay-4/memories
One bit of the command computer's memory: https://rshekhar.com/voyager/v1/bay-3/memory-1/plane-1/bit
The Golden Record's cover: https://rshekhar.com/voyager/v1/apart/golden-record
How Voyager 1 was fixed by radio: https://rshekhar.com/voyager/story/the-fix
The journey past the planets: https://rshekhar.com/voyager/story/the-voyagers
According to AI, one type of failure mode in those early aerospace CMOS chips was sudden parasitic current in the PNPN junction being caused by a high energy particle, shorting paths to ground melting metal. Though that sounds rare. Another option is a total ionizing dose of radiation over time, which creates electron-hole pairs in the gate oxide, leading to trapped positive charge. That makes NMOS get closer and closer to turning on when they shouldn't, and PMOS requiring more voltage to turn on. It's fascinating to me that there came a specific moment in time when the chip managed to work, and the next clock cycle it didn't. I'd love to see the I_D vs. V_GS charts showing a before and after. So I had Claude make a plausible approximation. You can too by asking your AI agent of choice by basically just pasting in my comment!
These were the main sources:
JPL's Voyager requirements book: https://spdf.gsfc.nasa.gov/pub/data/voyager/vgrmag-data/raw/...
JPL's report on the electronic parts and radiation: https://ntrs.nasa.gov/api/citations/19780007219/downloads/19...
Positions (JPL Horizons): https://ssd.jpl.nasa.gov/horizons/
The dishes (NASA's DSN Now): https://eyes.nasa.gov/dsn/dsn.html
Where the sources don't say, like which memory chip failed, I've taken the liberty of choosing one, with a disclaimer.
Execution is becoming all that matters. This is a great project and congrats to the creator on putting it together, whether he did by punchcard coding or prompting.