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.
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.
It reminds me that there are still very intelligent and talented people within our ranks. A nice breath of fresh air.
Why do Tumblr users approach every topic like a manic street preacher?
There’s a significant overlap between theatre kids and Tumblr users.
That ven diagram is maybe 3 degrees away from a circle.
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.
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
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.
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”.
Imagine scrolling back in the Slack chat 50 years to find that one thing someone said about how the chip bypass worked.
Still faster than the average Windows update.
Certainly better tested.
Well, they only had to test it for a single hardware deployment. Windows has to be tested for millions if not billions of deployments. Say what you want, but Microsoft testers are god like.
Windows? Hardware testing? Testing in general? LMAOOO
Yeah that’s what the updates are for haha
I wonder how it is secured, or could anyone with a big enough transmitter reprogram it at will…
Its partially because there is only one set of antennas large enough to communicate with it, and that’s only sometimes. Its called the Deep space network and it is very secure because it’s used for many things, not just communicating with the Voyager probes.
Second, you’d have to have very very intimate knowledge of the hardware, and programming language to even begin to hack it. And the people who do have that knowledge are very very passionate about their probes.
So I guess technically the answer is yes. But practically, no.
deleted by creator
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”.
They get doom to run on it.
Imagine playing with a 22 hour delay on frames.
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.”
Let’s hope the over-the-air update didn’t get Man-In-The-Middled…
Voyager is a boomer and could more easily be phished
Suspect #1:
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.
And yeah, I’m calling it V’Ger from now on
Have my upvote.
Why haven’t we been doing this already? I’m with you, let’s make this happen!
Stop trying to make V’ger happen! Its not going to happen!
