• IHeartBadCode@kbin.social
    link
    fedilink
    arrow-up
    141
    ·
    1 year ago

    Next hardware reset and automatic reorientation for Voyager 2 is October 15th. Yes the device automatically resets itself about four to five times a year. Communications are expected to be reestablished then.

    • Psythik@lemm.ee
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      Unrelated but I’ve been wondering this for years: What’s your avatar from and why do so many people across the web have that exact same one?

      • borlax@lemmy.borlax.com
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        No idea, I found it somewhere a decade ago and have been using it. I think I’ve only seen someone with it like one other time. 🤷🏻‍♂️

      • radau@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I remember it used to be popular in gaming groups and some music around 2008-2012 and a lot of variations of the same gas mask character were made

  • MJBrune@beehaw.org
    link
    fedilink
    English
    arrow-up
    34
    ·
    1 year ago

    Wikipedia states: “In July 2023, communication with Voyager 2 was lost when flight control pointed its antenna away from Earth, moving it by 2 degrees away from Earth. The NASA dish antenna in Canberra is being used to search for the space probe and will be used to saturate its location with commands to re-align the probe’s antenna in an attempt to re-establish the radio link. If NASA fails to contact the probe, it is expected that an automatic system on Voyager 2 will direct its dish toward Earth in October 2023.”

    • MJBrune@beehaw.org
      link
      fedilink
      English
      arrow-up
      34
      ·
      1 year ago

      So essentially someone probably wanted to move it one way and it moved the other. It should automatically reposition itself in contact with NASA in 2 months. It’s amazing the foresight we had in 1977 to write in all sorts of catch-alls… In 2 months we’ll get back in contact with the probe and it will have its own place, hanging out with aliens.

    • Sibbo@sopuli.xyz
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Great that they included these automatic hardware resets. Way to go if your computer will never see a human or human-made thing ever again

  • palordrolap@kbin.social
    link
    fedilink
    arrow-up
    33
    arrow-down
    1
    ·
    1 year ago

    V2 be like: “WHAT did you say about my mother? F… you, Earth man.”

    Mission control: “Dude you don’t have a mother it was a typo. Dude. Talk to me.”

    seen

    Mission control: “Dude.”

    seen

    Mission control: “C’mon man.”

    This message could not be sent. V2 may have blocked your number

    • kono_throwaway_da@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      I have done something similar. Disabled password authentication on SSH, forced public-key auth, restarted sshd.

      Guess who forgot to add their public key to their list of authorized keys.

  • YⓄ乙 @aussie.zone
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    1 year ago

    Wow! Wondering how the guy is being treated who sent the wrong command. I did it once at my work and people were acting really Weird. In my defense, I never really liked the job.

    • 𝘋𝘪𝘳𝘬@lemmy.ml
      link
      fedilink
      arrow-up
      27
      ·
      1 year ago

      I bet you don’t simply send random commands to the probe. There are likely a dozen of people who need to approve literally every keystroke.

      • Gecko@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        ·
        1 year ago

        This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.

        It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.

        • InputZero@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          This. This. I used to work on safety control systems for heavy industrial applications and it’s this. Once the system is running any changes at all went through a whole chain of people. When the change was being implemented I had my supervisor and their manager checking every line over my shoulder before we wrote it. Then test. Then lock it down with a digital signature.

          It’s not at all like in college/university where you’re making changes to your code over and over. Well it is in simulations but that’s long before you deploy it. By the end everyone involved should be able to say exactly what every line of code is going to do. This isn’t an intern fucking up, the whole team did, and whomever the buck stops with at the top is responsible.

            • InputZero@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              If you’re talking about Voyager, I’d assume so, but I don’t have any source to back that up. If you’re talking about my previous work, the test environment was exact enough… Cough not-even-close cough.

        • 𝘋𝘪𝘳𝘬@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I’m gonna click approve without looking

          … and at this moment it is no longer my problem. I have written evidence that I forwarded my command for approval.