Show HN: Take Voyager 1 apart, down to a single memory chip

(rshekhar.com)

179 points | by raj-shekhar 14 hours ago ago

45 comments

  • raj-shekhar 13 hours ago

    A few things are hard to find, so here are direct links:

    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

    • vusbtrm 6 hours ago

      Not to be overly dismissive, but there are so many factual inaccuracies with both the modeling and information I'm honestly not sure this is useful. From the Antenna feeds, lack of sun detector, incorrect modeling of the bus, internals of the RTG being hallucinated, mislabeling of computers and components. There are a plethora of really high quality drawings and diagrams from the original design phases that could have been used here.

      • raj-shekhar 2 hours ago

        Hi! Everything is based on NASA and JPL documents. I've linked my primary references in another reply here.

        > Antenna feeds, incorrect modeling of the bus

        Which parts do you think are wrong, and which drawings would you use?

        > internals of the RTG being hallucinated

        It follows NASA's 1980 cutaway: https://ntrs.nasa.gov/api/citations/19810001583/downloads/19.... One thing you are right about: the fuel spheres should be stacked in pairs. I'll fix that.

        > lack of sun detector

        fair, it's not named on the site. I'll add it.

        > mislabeling of computers and components

        The layout and names come from JPL's own packaging drawing: https://spdf.gsfc.nasa.gov/pub/data/voyager/vgrmag-data/raw/...

      • noir_lord 5 hours ago

        > Not to be overly dismissive.

        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.

    • bigwheels 11 hours ago

      I just learned the voyager probes are expected to go silent by the early 2030's.

      I wish we had other long running deep-space exploration experiments to take their place!

      • raj-shekhar 11 hours ago

        Me too! The only other probe heading out now is New Horizons. It should still be working when it reaches interstellar space in the early 2040s, if NASA keeps funding it.

  • gourneau 9 hours ago

    This is awesome I love it!

    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/

    • raj-shekhar 2 hours ago

      Oh wow, very nice! Really liked the decoder. Mind if I link it from the Golden Record part of my site?

  • IAmNotACellist 12 hours ago

    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!

    • raj-shekhar 11 hours ago

      I tried to find the exact root cause. NASA said they could not determine the cause of the chip failure with certainty, so we can only speculate.

      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...

    • alhadrad 12 hours ago

      It is most certainty cumulative radiation effects degrading the gates as you have eluded. This problem still exists for on orbit power electronics.

  • carter-qadenza 6 hours ago

    This is neat, even if it's missing some things. I actually really like how Voyager is displayed. Thinking about putting something like together in the late 70's is pretty wild.

    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!

    • raj-shekhar 2 hours ago

      It really is fascinating. Originally I just wanted to understand the computers on board Voyager, and I fell for more and more of it.

  • glimshe 12 hours ago

    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?

    • raj-shekhar 12 hours ago

      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.

      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.

      • mek6800d2 7 hours ago

        Very nice and impressive work - well done!

        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...

        • raj-shekhar 2 hours ago

          Thanks for the link! I couldn't find which chip failed when I built this, so the site shows a stand-in. I'll update it to the real one.

      • altcognito 5 hours ago

        I didn't really think about how it has to adjust for earth's travel around the sun to point the dish, it's crazy that it is constantly gently adjusting every so very, very carefully. What a great tiny detail

    • hodder 12 hours ago

      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.

      • lukeify 10 hours ago

        It’s possible to use LLMs as part of your process while still having editorial or design control over the output. I usually take “vibecoded” as a pejorative to mean you’ve let LLMs handle almost all elements of a project. Using LLMs themselves does not make something vibecoded.

      • glimshe 10 hours ago

        My projects aren't. "Execution" is what my question is about. This is a great project, but we need more information to have confidence on the output. I'm just struggling with AI right now in getting a makefile right. So AI output, no matter how good, can be wrong - sometimes very wrong.

      • schmookeeg 11 hours ago

        I normally see it as pejorative or condescending these days, although I don't think that's what the commenter intended.

        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.

  • djeastm 8 hours ago

    Really, really cool. I have to admit that the Pale Blue dot image, as it always does, caused me to tear up a little.

  • dongjoo 5 hours ago

    This is cool! I like the neat design.

  • ajju 7 hours ago

    Super cool! I also like your titan visual - very calming.

  • blinding-streak 12 hours ago

    I really enjoyed the timeline of the Voyager journeys from launch until today. Thank you for making this.

    • raj-shekhar 11 hours ago

      Thank you, glad you enjoyed it!

  • nephihaha 7 hours ago

    Other missions have probably returned much more data but I will always have a soft spot for Voyager 1 & 2. Their pictures from the gas giants and their moons were so fresh and inspiring back in the day.

    Together with the longer lasting Mars rovers I think they have offered some of the best returns on space "investments" we've ever seen.

  • thelbartworks 13 hours ago

    maybe when you show the journey you can adapt the zoom

    • raj-shekhar 13 hours ago

      Hi! Could you elaborate? Do you want to zoom out more to see where it's heading, or zoom in closer on the planets?

  • engineer_22 10 hours ago

    https://rshekhar.com/voyager/v1/apart

    this should be the link if you want to take apart the craft

    • raj-shekhar 2 hours ago

      Thanks, you're right. That's the best place to start. I should have put it in my list.

  • ForHackernews 12 hours ago

    If you haven't seen it, this is a great documentary: https://www.youtube.com/watch?v=8vJT8AW0wYw

  • skullone 10 hours ago

    Very neat!

  • cdelsolar 12 hours ago

    i dont know if it got hugged to death but i can't get anything to work, latest chrome on linux (btw i use arch)

    • raj-shekhar 2 hours ago

      Sorry for the late reply. It's not the traffic. The site needs WebGL, and Chrome on Linux often has it turned off. The site now shows a message when that happens.

      To turn it on, paste chrome://settings/system in the address bar, turn on "Use graphics acceleration when available" and restart Chrome. Or try another browser.

  • iJohnDoe 10 hours ago

    Really amazing! This is cool and learned some new things.

    • raj-shekhar 2 hours ago

      Thank You!

    • elbistec24 10 hours ago

      How confident are you those those things you learned were true if the author themselves said they had Claude do a lot of it?

      • raj-shekhar 2 hours ago

        Hi! I've linked my primary sources and the original JPL and NASA drawings in my other replies, so you can check for yourself.