Voyager 1 contact restored

    • lechatron@lemmy.today
      link
      fedilink
      English
      arrow-up
      104
      ·
      6 months ago

      The actual news release has a bit more information.

      The team discovered that a single chip responsible for storing a portion of the FDS memory — including some of the FDS computer’s software code — isn’t working. The loss of that code rendered the science and engineering data unusable. Unable to repair the chip, the team decided to place the affected code elsewhere in the FDS memory. But no single location is large enough to hold the section of code in its entirety.

      So they devised a plan to divide the affected code into sections and store those sections in different places in the FDS. To make this plan work, they also needed to adjust those code sections to ensure, for example, that they all still function as a whole. Any references to the location of that code in other parts of the FDS memory needed to be updated as well.

      Source: https://www.jpl.nasa.gov/news/nasas-voyager-1-resumes-sending-engineering-updates-to-earth

      • Infynis@midwest.social
        link
        fedilink
        English
        arrow-up
        23
        ·
        6 months ago

        That’s incredible. It also reminds me of the episode of Star Trek Deep Space 9 where they need to find space to store a bunch of people’s transporter patterns, so they just dump them into the stations computer, replacing everything that used to be there lol

        • nilloc@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          5
          ·
          6 months ago

          It interesting that the memory is so discrete that it can be reprogrammed when a single ROM fails. And it’s really neat that they made the whole thing accessible to a radio controlled boot loader. The planning that went into building and maintaining Voyager is really incredible.

          I wonder if we could still build one as robust these days?

        • Karyoplasma@discuss.tchncs.de
          link
          fedilink
          arrow-up
          34
          ·
          6 months ago

          The problem was that Voyager sent junk data back to us due to a memory fault. It was still responsive to receive updates from Earth and to pings.

          Pinging Voyager 1 takes about 2 days, so testing updates is naturally quite slow.

          • halcyoncmdr@lemmy.world
            link
            fedilink
            English
            arrow-up
            20
            ·
            6 months ago

            Not only round trip time, the hardware only supports bandwidth of 160bps at this range. Down from the 21.6kbps at launch.

        • histic@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          15
          ·
          edit-2
          6 months ago

          Im guessing it could still listen just not talk back

          Edit read the article

          Although the radio signal from the spacecraft had never ceased its connection to ground control operators on Earth during the computer problem, that signal had not carried any usable data since

        • lorkano@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          This Satelite must offer option to install software updates over the air, so they modified software and slowly uploaded it to the satelite.

        • Richard@lemmy.world
          link
          fedilink
          English
          arrow-up
          11
          ·
          6 months ago

          I know that this is supposed to be a joke, and I do find it funny, but I also find it sad that it carries a large dose of truth. C is such a “low-level” high-level language that it makes you deal directly with memory allocation and management as well as pointer arithmetic to advance addresses in the stack, which in my opinion is very important for programmers to gain an understanding of the actual hardware and architecture their programs are running on, because I feel that many don’t have that understanding. Should Rust replace C in many applications, especially low-level, I fear that we will ultimately end up with worse code because of that. (BTW I know that Voyager’s program is not written in C, this is just purely about your statement on Rust.)

          • Kualk@lemm.ee
            link
            fedilink
            arrow-up
            8
            ·
            6 months ago

            C will never fully go away.

            Constrained environments will always remain in C.

            But RUST offers the best trade off today. It is way better than C++.

            C IMO is not comparable to RUST.

      • lorkano@lemmy.world
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        6 months ago

        Can we appreciate how they can basically change software of this 45y/o satelite over the air? Original designers thought everything through

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

        It was much more complicated than that.

        They also had to wrap half a roll of tin foil around the antennas.

  • Richard@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    6 months ago

    Very cool, especially that the expertise still exists within NASA to understand and debug almost 50 year old code from a now ancient seeming architecture. They are probably training their people assigned to the Voyager mission in these things.

      • bitwaba@lemmy.world
        link
        fedilink
        arrow-up
        14
        ·
        6 months ago

        Radioactive materials have a half-life, which means every X number of days/months/years, the material will have decayed to half its initial size. This continually happens, so while something might start at say 100g and have a 10 day half life, 10 days later it is 50g, 10 days later 25g, 10 days later 12.5g, 10 days later 6.25g, etc. This will continue forever until there is literally one atom left, at which point it is random chance when the atom would decay.

        Voyager launched with 3 Radioisotope Thermoelectric Generators, each with 4.5kg of Pu238 which generated 157 watts of usable electric power at launch, for a total of 471 watts

        It will be half that in 87.7 years (235W) . And half that (117W) in another 87.7.

        The problem comes from the amount of power necessary to run the craft and it’s radio. While the generators might continue to run for practically forever, at some point they just don’t produce enough power to keep everything working. Its official mission is expected to end in 2025, but it’s generators are expected to be able to power it’s instruments for another ~10 years

        • Telodzrum@lemmy.world
          link
          fedilink
          arrow-up
          5
          arrow-down
          1
          ·
          6 months ago

          Just a reminder that half-life is a probabilistic measurement, not an exact one. Given adequate scale of material it’s accurate across the measured sample, but it is not precise at lower volumes of material or in narrower measurement periods.

      • geography082@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        6 months ago

        Estmate , around 2025. It depends on so many tings I guess , they are constantly doing enhancements to it since the beginning and that could make it last a little bit longer, but not much more I think.

  • Blackmist@feddit.uk
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    6 months ago

    Well alright, but if memory serves, it’s Voyager 6 we have to be worried about.