Conversation
Notices
-
Embed this notice
>Instead of beaming back binary code over billions of miles, Voyager 1 is sending 1s and 0s that just alternate. Efforts to reset the aging probe have failed so far — but that shouldn't come as a surprise, considering the technology dates back to the mid-1970s.
-
Embed this notice
What if that's literally what's out there? Unused storage space.
-
Embed this notice
@BowsacNoodle V'Ger?
-
Embed this notice
@DasSauerkraut @BowsacNoodle we still have voyager 2! :sadcat:
-
Embed this notice
@BowsacNoodle Will be sad to see it go, we won't have another technological achievement like it in our lifetimes. 50 years for it to get out of the solar system, it'd probably take us 50 years at this point to get another similar probe built and launched.
-
Embed this notice
@BowsacNoodle Considering the part of space it is in, really hard radiation has prolly put a toll on the vitals in unforeseen ways. Also, iirc it is currently outside the sun's wake where interstellar radiation is a weeeee bit more potent.
-
Embed this notice
@Professor_Groyper @BowsacNoodle there was a software patch they uploaded to V-1 some months ago which was very risky I can’t remember what for but the poor thing’s been having problems since 😭All the OG engineers and programmers are long gone so nobody to get tech help on the situation. I hate this, I‘m not ready to lose any of the voyagers.
-
Embed this notice
@ShemsBorealis @Professor_Groyper Shoot I remember that! How do you even patch something from the 70s? lol download more RAM
-
Embed this notice
>V'Ger?
-
Embed this notice
@adequate @Professor_Groyper @BowsacNoodle lmao! I don’t believe it was hiring practices or anything but they knew the software patch was an extremely risky decision - being an archaic computer that used tape decks & FORTRAN Operating System, and I think they found out its operations manual was missing after the previous OG operator retired. What the team did was practically a tech miracle, the patch worked for what it was intended but the way all patches go, fix one thing and something else nerfs up. They knew it could either make or break the craft.
-
Embed this notice
@ShemsBorealis @Professor_Groyper @BowsacNoodle Tell me that diversity hires killed Voyager 1 without telling me diversity hires killed Voyager 1.
-
Embed this notice
@BowsacNoodle @Professor_Groyper That was the incredible part on what they did! The team didn’t know if it would work but made the risky decision. I think it was something to do with preventing some type of accumulation of something from its fuel system. Imagine doing a remote software patch on a computer built with 68K tape decks for memory devices & runs FORTRAN. Add a 48 hour deep space data transmission speed. They were in a crisis not too long ago maybe 5 years? The guy that operated the Voyagers for years retired and was the ONLY one at NASA who knew how to run FORTRAN. They couldn’t even find Voyagers’ original manual.
-
Embed this notice
@DasSauerkraut @Vril_Oreilly @BowsacNoodle Is this Voyager the one that the woman from NASA lost control of. If so wouldn't be surprised if it fell into some kind of error loop due the lack of control signal?
-
Embed this notice
@Vril_Oreilly @BowsacNoodle
Voyager 2 is 3 billion miles behind Voyager 1 at this point, if I'm reading the table right. If it encounters the same conditions Voyager 1 is seeing further out, we may soon see the end of the mission :sadhug: