A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
This is a science community. We use the Dawkins definition of meme.
I still cannot believe NASA managed to re-establish a connection with Voyager 1.
That scene from The Martian where JPL had a hardware copy of Pathfinder on Earth? That’s not apocryphal. NASA keeps a lot of engineering models around for a variety of purposes including this sort of hardware troubleshooting.
It’s a practice they started after Voyager. They shot that patch off into space based off of old documentation, blueprints, and internal memos.
Imagine scrolling back in the Slack chat 50 years to find that one thing someone said about how the chip bypass worked.
Imagine any internet company lasting 50 years.
This is why slack is bullshit. And discord. We should all go back to email. It can be stored and archived and organized and get off my lawn.
To add to the metal, the blueprints include the blueprints for the processor.
https://hackaday.com/2024/05/06/the-computers-of-voyager/
They don't use a microprocessor like anything today would, but a pile of chips that provide things like logic gates and counters. A grown up version of https://gigatron.io/
That means "written in assembly" means "written in a bespoke assembly dialect that we maybe didn't document very well, or the hardware it ran on, which was also bespoke".
I realize the Voyager project may not be super well funded today (how is it funded, just general NASA funds now?), just wondering what they have hardware-wise (or ever had). Certainly the Voyager system had to have precursors (versions)?
Or do they have a simulator of it today - we're talking about early 70's hardware, should be fairly straightforward to replicate in software? Perhaps some independent geeks have done this for fun? (I've read of some old hardware such as 8088 being replicated in software because some geeks just like doing things like that).
I have no idea how NASA functions with old projects like this, and I'm surely not saying I have better ideas - they've probably thought of a million more ways to validate what they're doing.
Probably brought in some of the original guys for one last job.
takes long drag off cigarette "I'm too old for this shit"
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.
And you explained all of that WITHOUT THE OBNOXIOUS GODDAMNS and FUCKIN SCIENCE AMIRITEs
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
Still faster than the average Windows update.
More stable, too.
Absolutely. The computers on Voyager hold the record for being the longest continuously running computer of all time.
Microsoft can't even release a fix for Window's recovery partition being too small to stage updates. I had to do it myself, fucking amateurs.
NASA should be in charge of Windows updates!
If they were it wouldn't be Windows
Windows 13 update log:
Change kernel to Linux.
Build custom OS for astrophysics and space science applications.
happy rocket engineer noises
It's hard to explain how significant the Voyager 1 probe is in terms of human history. Scientists knew as they were building it that they were making something that would have a significant impact on humanity. It's the first man made object to leave the heliosphere and properly enter the interstellar medium, and this was always just a secondary goal of the probe. It was primarily intended to explore the gas giants, especially the Jovian lunar system. It did its job perfectly and gave us so many scientific discoveries just within our solar system.
And I think there's something sobering about the image of it going on a long, endless road trip into the galactic ether with no destination. It's a pretty amazing way to retire. The fact that even today we get scientific data from Voyager, that so far away we can still communicate with it and control it, is an unbelievable achievement of human ingenuity and scientific progress. If you've never seen the image the Pale Blue Dot you should see it. That linked picture is a revised version of the image made by Nasa and released in 2020. It's part of a group of the last pictures ever taken by Voyager 1 on February 14th 1990, a picture of Earth from 6 billion kilometers away. It's one of my favorite pictures, and it kinda blows my mind every time I see it.
The pale blue dot photo always makes me tear up. We're so small and insignificant in such a grand universe and I'm crushed that I can't explore it.
There will always be a "step further we'd love to see but won't". Let's be glad we're in that step which included this photo and the inherent magnificence in it.
It totally beats being one of the earlier humans who just wondered what the lights in the sky might be. Probably gods or something.
I think the term "metal" is overused, but this is probably the most metal thing a programmer could possibly do besides join a metal band.
I was already impressed when they managed to diagnose a single bit flip a few years ago.
Keep in mind too these guys are writing and reading in like assembly or some precursor to it.
I can only imagine the number of checks and rechecks they probably go through before they press the "send" button. Especially now.
This is nothing like my loosey goosey programming where I just hit compile or download and just wait to see if my change works the way I expect...
they almost certainly have a hardware spare, or at the very least, an accurately simulated version of it, because again, this is 50 year old hardware. So it's pretty easy to just simulate it.
But yeah they are almost certainly pulling some really fucked QA on this shit.
Man I can’t even get my stupid Azure deployment to work and that’s only in Germany.
As someone who recently switched from AWS to Azure I feel your pain.
Best part is when you finally have a working solution, Microsoft sends you an email that it's being deprecated.
I wont even upgrade the BIOS on my motherboard because im afraid of bricking it.
As a teenager I experienced a power outage while I was updating my bios.
Guess what happened?
I’m still bitter about it.
Rejected : please comment your changes
My understanding is that they sent V'Ger a command to do "something," and then the gibberish it was sending changed, and that was the "here's everything" signal.
And yeah, I'm calling it V'Ger from now on.
They specifically sent it a command to send a full memory dump after it went haywire. It wasn't a fluke.
Why do Tumblr users approach every topic like a manic street preacher?
When I hear what they did, I was blown away. A 50 year old computer (that was probably designed a decade before launching) and the geniuses that built that put in the facility to completely reprogram it a light-day away.
People always underestimate the high level NASA works at. Everyone bitches and moans, especially Musk simps, about how long SLS took to make and its expense, but it worked right the first time. In the case of the Voyager spacecraft, they are working with tech so old, all the original engineers are retired or dead. NASA rocks.
I wonder how it is secured, or could anyone with a big enough transmitter reprogram it at will...
Modern satellites are protected by various means of encryption, but there’s an enthusiast community that tracks down and communicates with very old unencrypted zombie satellites. There’s even been an NGO which managed to fire rockets on an abandoned NASA/ESA probe (with their approval.)
The Voyagers benefits primarily from the lack of groups with an adequate deep space network to communicate with it. Their communication standards are otherwise completely open and well documented.
"Yeah, I always leave my car unlocked with the keys inside. I also always park it in the center of a lake."
I think the security is adequately managed by the need for a massive transmitter as well as the question "what is there to gain via a hostile takeover and re-programming the probe?"
I bet there's actual security of some kind going on, but those two points seem like a massive hurdle to clear just to mess with a deep space probe.
what is there to gain via a hostile takeover and re-programming the probe
"We did it for the lulz".
I just have to imagine how interesting of a challenege that is. Kinda like when old games only had 300kb to store all their data on so you had to program cool tricks to get it all to work.
Fuck it, we'll fix it live
It reminds me that there are still very intelligent and talented people within our ranks. A nice breath of fresh air.
