• Ashyr@sh.itjust.works
    link
    fedilink
    arrow-up
    49
    ·
    7 months ago

    Incredible! So the memory chip holding a lot of core programming was damaged or failed, so they figured out which chip it was, but then there was no single place large enough to store this vital code, so they divided it up and distributed it throughout the remaining memory and now it works.

    These people are brilliant.

    • thebestaquaman@lemmy.world
      link
      fedilink
      arrow-up
      20
      ·
      7 months ago

      I really struggle to comprehend how you can debug hardware that is several light-hours away, let alone how you would proceed to split an OS (or whatever Voyager is running) into separate parts and then upload those parts to separate hunks of memory to make a functioning machine…

      Also: What would they do if the code they uploaded was corrupted “in transmission”?

      • lemmy_in@lemm.ee
        link
        fedilink
        arrow-up
        9
        arrow-down
        1
        ·
        7 months ago

        For most transmissions of digital information (even those here on earth) there’s a concept of a “checksum”. Basically at the end of every message, there’s a special number, and you can do some math on the rest of the message to get that same number. If anything happened to change or damage the message in transit, the math doesn’t work out and so the checksum fails.

        I would assume Voyager works in a similar way so every time it receives a message it will compute the checksum and see whether it matches