Voyager 1 - eviltoast
  • merc@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    246
    ·
    6 months ago

    To me, the physics of the situation makes this all the more impressive.

    Voyager has a 23 watt radio. That’s about 10x as much power as a cell phone’s radio, but it’s still small. Voyager is so far away it takes 22.5 hours for the signal to get to earth traveling at light speed. This is a radio beam, not a laser, but it’s extraordinarily tight beam for a radio, with the focus only 0.5 degrees wide, but that means it’s still 1000x wider than the earth when it arrives. It’s being received by some of the biggest antennas ever made, but they’re still only 70m wide, so each one only receives a tiny fraction of the power the power transmitted. So, they’re decoding a signal that’s 10^-18 watts.

    So, not only are you debugging a system created half a century ago without being able to see or touch it, you’re doing it with a 2-day delay to see what your changes do, and using the most absurdly powerful radios just to send signals.

    The computer side of things is also even more impressive than this makes it sound. A memory chip failed. On Earth, you’d probably try to figure that out by physically looking at the hardware, and then probing it with a multimeter or an oscilloscope or something. They couldn’t do that. They had to debug it by watching the program as it ran and as it tried to use this faulty memory chip and failed in interesting ways. They could interact with it, but only on a 2 day delay. They also had to know that any wrong move and the little control they had over it could fail and it would be fully dead.

    So, a malfunctioning computer that you can only interact with at 40 bits per second, that takes 2 full days between every send and receive, that has flaky hardware and was designed more than 50 years ago.

    • flerp@lemm.ee
      link
      fedilink
      English
      arrow-up
      91
      arrow-down
      7
      ·
      6 months ago

      And you explained all of that WITHOUT THE OBNOXIOUS GODDAMNS and FUCKIN SCIENCE AMIRITEs

      • KubeRoot@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        20
        arrow-down
        1
        ·
        6 months ago

        Oh screw that, that’s an emotional post from somebody sharing their reaction, and I’m fucking STOKED to hear about it, can’t believe I missed the news!

    • chimasterflex@lemmy.world
      link
      fedilink
      English
      arrow-up
      66
      ·
      6 months ago

      Finally I can put some take into this. I’ve worked in memory testing for years and I’ll tell you that it’s actually pretty expected for a memory cell to fail after some time. So much so that what we typically do is build in redundancy into the memory cells. We add more memory cells than we might activate at any given time. When shit goes awry, we can reprogram the memory controller to remap the used memory cells so that the bad cells are mapped out and unused ones are mapped in. We don’t probe memory cells typically unless we’re doing some type of in depth failure analysis. usually we just run a series of algorithms that test each cell and identify which ones aren’t responding correctly, then map those out.

      None of this is to diminish the engineering challenges that they faced, just to help give an appreciation for the technical mechanisms we’ve improved over the last few decades

      • trolololol@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        6 months ago

        pretty expected for a memory cell to fail after some time

        50 years is plenty of time for the first memory chip to fail most systems would face total failure by multiple defects in half the time WITH physical maintenance.

        Also remember it was built with tools from the 70s. Which is probably an advantage, given everything else is still going

        • orangeboats@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          6 months ago

          Also remember it was built with tools from the 70s. Which is probably an advantage

          Definitely an advantage. Even without planned obsolescence the olden electronics are pretty tolerant of any outside interference compared to the modern ones.

      • merc@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        what we typically do is build in redundancy into the memory cells

        Do you know how long that has been going on? Because Voyager is pretty old hardware.

    • graymess@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      ·
      6 months ago

      Is there a Voyager 1, uh…emulator or something? Like something NASA would use to test the new programming on before hitting send?

      • Landless2029@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        6 months ago

        Today you would have a physical duplicate of something in orbit to test code changes on before you push code to something in orbit.

    • uis@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      6 months ago

      They have spare Voyager on Earth for debugging

      EDIT: or not