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
Based on what you listed been accurate (I don't know enough about Voyager to know one way or the other), I think it's perfectly reasonable to be dismissive in this instance.
I wish we had other long running deep-space exploration experiments to take their place!
Here is my little tribute to the Golden Record on both Voyagers https://goldenrecord.voyage/
Also a decoder to turn their raw audio into the images https://gourneau.github.io/golden-record-images/
Seeing the spectrometers reminded me that nearly my entire physics degree only covered what was known up until the 50's. I always underestimate how much we understood even 75 years ago!
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!
This is what I found as part of my research:
NASA: "Engineers can't determine with certainty what caused the issue. Two possibilities are that the chip could have been hit by an energetic particle from space or that it simply may have worn out after 46 years." https://science.nasa.gov/blogs/voyager/2024/04/04/engineers-...
IEEE Spectrum, citing project scientist Linda Spilker, reported that the memory readout showed "a stuck bit, fixed at the same binary value" in that 256-bit chunk: https://spectrum.ieee.org/voyager-1
EE Journal reported JPL's chief engineer naming the part as an RCA CD4061A, a 256 x 1-bit CMOS SRAM. Losing it took out 256 of the data computer's 8,192 words, which matches NASA's 'about 3%': https://www.eejournal.com/article/jpl-software-update-rescue...
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.
The failed bit is the fifth bit (bit 4 in 0..15 numbering) at addresses 0x1400-0x14FF (module 3). See Voyager Spacecraft and Fortran 5 - FDS Memory Problems: http://www.geonius.com/writing/other/voyager.html#FDSMemoryP...
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.
I read "was that vibe-coded?" in the voice one might speak to an infant in. "did you codey-wodey that all with your friend clooooood?". And it's super cringe. As you noted, nobody cares if you hand-coded things anymore. Execution counts, and this was well done.
Together with the longer lasting Mars rovers I think they have offered some of the best returns on space "investments" we've ever seen.
this should be the link if you want to take apart the craft