NASA Pulls Off Delicate Thruster Swap, Keeping Voyager 1 Mission Alive
gizmodo.com
gizmodo.com
1. Are able to diagnose the problems remotely at such distances and on such old hardware. How can they even measure the thruster tube apertures here?
2. Decide what actions to take. It's not like they have a local test device to experiment on is it? (Even if they did I can't imagine how they'd reproduce the conditions of the real thing.) And if they choose poorly, I'd assume the mission's over. There's no replacing Voyager 1 if they brick it.
3. Have such fine control over the hardware. For something built in the 70's when RAM was largely measured in kB, they seem to have an insane amount of flexibility to remotely reconfigure the equipment. Whatever they did, there must have been some real foresight.
JPL has (or had?) a "retiree badge" program that permitted retired staff to continue to access their office. Many programs benefited from highly knowledgeable personnel essentially continuing to report to the office every day without pay (not being paid comes with the luxury of not having to worry about being laid off if your charge accounts don’t have enough funds!) It was an absolute privilege to learn from these people.
For example JPL used to have beauty pageants ("Miss Guided Missile"). More recently, management appears to be trying to adopt policies and procedures from some venture funded commercial space companies. It is not clear how helpful these efforts will be given that these organizations are in fundamentally different businesses.
https://www.jpl.nasa.gov/images/slice-of-history-70th-annive...
All the web apps, that run of the mill devs are implementing are nowhere near as important as voyager.
I think we are fine ;)
It means that they are the most valuable employees, because their productivity per dollar is infinite.
It also means that when you sort all the (non-executive, of course!) employees by total comp in preparation for layoffs to make the budget look better, they are at the bottom of the list.
Great forward thinking
One saving grace was the fact that the architecture and the code space was simple enough so that they could reason through the symptoms and actions to take, something that would have been much harder with modern spacecraft.
Check out this amazing talk: https://youtu.be/dF_9YcehCZo?si=W_b3NJ7vgxaYS1__
Voyager: "Do you remember when our parents inserted this quirky module that has since left the solar system? We can use that to turn it off and on again. That was a mission critical decision!"
I would bet they have one or more simulators (“digital twin” in the parlance of our times). I’d want one simulator to always reflect the current state of the probe (with state data assimilated periodically from the real probe). Then other simulators can be used to test management changes to see how the system might respond.
Sadly they do not, but they are starting to write one.
https://science.nasa.gov/mission/voyager/spacecraft/
The data playbacks were initially transmitted at 7200 bps, but this was dropped to 1400 bps in 2007 (https://voyager.gsfc.nasa.gov/Library/DeepCommo_Chapter3--14... - page 72).
RTT ~46 hours (one-way light time 22:49:59, per https://science.nasa.gov/mission/voyager/where-are-they-now/)
Where the heck do you get SiO2 from on a spacecraft? Some kind of silicone?
edit: "clogged with silicon dioxide, a byproduct that appears with age from a rubber diaphragm in the spacecraft’s fuel tank"[0] —I'm guessing that is a silicone rubber. I didn't know that rubber can decompose into sand.
[0] https://science.nasa.gov/missions/voyager-program/voyager-1/...
1: https://ntrs.nasa.gov/api/citations/19810001583/downloads/19...
It’s basically blind debugging with a latency of 45 hours.
The talk is amazing and goes through the computer architecture of the spacecraft as well as the challenges of dealing with something that is so old, with so documentation that has conflicting information or unreadable etc.
I watched this excellent Voyager documentary recently:
While it was not a design requirement, the option for an extended mission past Saturn was always protected, unless it meant compromising a major mission objective at Jupiter or Saturn.
Even though the probability of Voyager 2 lasting another five years was calculated to be in the range of 60 to 70 percent -- well below NASA's usual acceptable probability-of-success threshold -- the decision was made to send Voyager on to Uranus.
After its Uranus encounter, Voyager 2 still carried 48% of the hydrazine initially loaded into its tanks, eight-and-a-half years before.
[1]: doi:10.1016/0094-5765(87)90096-8 (can be found on the hub of science)
Edit: There's more about that in the NASA link in a sibling comment.
Light sails. Laser propulsion. Photon rockets. None of which apply to Voyager. But none of which are laughably dismissible.
It's sad how much documentation is honestly unreachable now.