NASA patched its Voyager 2 spacecraft last week, to address a bug that last year saw its sibling [1]generate corrupted telemetry data , but won't know if its fix worked – or overwrote critical code – until some time after October 28.

Both Voyagers were launched in 1977. Voyager 1 is now more than 22 billion kilometers (15 billion miles) from Earth, and almost 22 and a half light hours away. Voyager 2 is over 20 billion kilometers from home (12.5 billion miles) and more than eighteen hours and forty minutes away at the speed of light. The two probes have left our solar system and communication is therefore very slow – 160 bits per second to Voyager 1 as of May 2022.

NASA already figured out that the cause of the garbled data on Voyager 1 was the attitude articulation and control system (AACS) – a tool that controls the crafts' orientation, including keeping their antennae pointed precisely at Earth.

[2]

In a Friday [3]post , NASA's Jet Propulsion Laboratory explained that the AACS was writing commands into memory instead of carrying them out. "One of those missed commands wound up garbling the AACS status report before it could reach engineers on the ground," the post states.

[4]

[5]

"The team determined the AACS had entered into an incorrect mode; however, they couldn't determine the cause and thus aren't sure if the issue could arise again. The software patch should prevent that," the document continues.

JPL's Voyager project manager Suzanne Dodd explained that months of effort went into creating a patch, which was sent to Voyager 2 last Friday.

[6]

"Because of the spacecraft's age and the communication lag time, there's some risk the patch could overwrite essential code or have other unintended effects on the spacecraft," she warned. Voyager 2 is therefore the first target for the patch, because it's closer to Earth – which matters for two reasons.

For starters, communication with Voyager 2 is quicker, making uploads and tests a little easier.

NASA also rates Voyager 1's data more valuable, as it is farther from home. Messing up Voyager 2, while undesirable, is more acceptable.

[7]

The patch was despatched to Voyager 2 on October 20 and NASA plans to test it on the 28th.

[8]NASA's New Horizons probe scores extended vacation in Kuiper Belt

[9]NASA mistakenly severs communication to Voyager 2

[10]NASA tweaks Voyager 2's power supply to avoid another sensor shutdown

[11]The years were worth the wait. JWST gives us an amazing view of Neptune's rings

Fuel problems

NASA also made a change to address problems with the Voyagers' thrusters, which aren't in peak condition as the propellant inlet tubes that bring them fuel have accumulated a "significant" buildup of residue.

The space agency has therefore begun letting the two spacecraft rotate slightly farther in each direction before firing the thrusters, as doing so will reduce the frequency of thruster firings.

"The adjustments to the thruster rotation range were made by commands sent in September and October, and they allow the spacecraft to move almost one degree farther in each direction than in the past," reads the October 20 post. "The mission is also performing fewer, longer firings, which will further reduce the total number of firings done on each spacecraft."

The post explains that NASA has had to make a trade-off, because rotating the spacecraft more means some data doesn't make it to Earth. But mission boffins "concluded the plan will enable the Voyagers to return more data over time."

"Engineers can't know for sure when the thruster propellant inlet tubes will become completely clogged, but they expect that with these precautions, that won't happen for at least five more years, possibly much longer," the post adds.

Given Voyager's engineers have kept the two probes going far, far, longer than expected, who would bet against them finding new ways to extend their lives? ®

Get our [12]Tech Resources



[1] https://www.theregister.com/2022/08/31/voyager_1_telemetry_data_corrupted/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/science&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZTZERdyWH7JeCQHDIu13LQAAAE8&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://www.nasa.gov/missions/voyager-program/nasas-voyager-team-focuses-on-software-patch-thrusters/

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/science&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZTZERdyWH7JeCQHDIu13LQAAAE8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/science&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZTZERdyWH7JeCQHDIu13LQAAAE8&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/science&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZTZERdyWH7JeCQHDIu13LQAAAE8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/science&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZTZERdyWH7JeCQHDIu13LQAAAE8&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[8] https://www.theregister.com/2023/10/02/new_horizons_mission_extension/

[9] https://www.theregister.com/2023/07/31/nasa_mistakenly_disconnects_voyager_2/

[10] https://www.theregister.com/2023/04/27/nasa_tweaks_voyager_2s_power/

[11] https://www.theregister.com/2022/09/22/jwst_neptune_images_faults/

[12] https://whitepapers.theregister.com/