News: 1707406213

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Work to resolve binary babble from Voyager 1 is ongoing

(2024/02/08)


NASA's Jet Propulsion Laboratory (JPL) has [1]confirmed that work to resolve a data issue aboard Voyager 1 continues, almost two months since the spacecraft began spouting gibberish.

The good news is that engineers can send commands to the spacecraft and have confirmed that those commands are being received. However, the distances involved mean that the process is hugely time consuming. According to JPL, it takes 22.5 hours for a message to reach the spacecraft and another 22.5 hours for the response to be received.

Thus, engineers must wait 45 hours to see if a command has the expected outcome.

[2]

The Register understands that "all available talents" are being used to resolve the problem. Considering the age of the probe and the fact that it is running on so many backup systems, such issues are inevitable.

[3]

[4]

Dr Garry Hunt, a member of the original Voyager team, told us: "This certainly shows the value of having backup systems and duplications."

According to Hunt, it is also a reminder that "commercial space organizations will not be able to afford to work in this way so we can expect more failures in the new space age."

[5]Space exploitation vs space exploration: Humanity has much to learn from the Voyager probes

[6]NASA engineers scratch heads as Voyager 1 starts spouting cosmic gibberish

[7]Half a century ago, NASA's Pioneer 10 visited Jupiter, then just kept going

[8]NASA just patched Voyager 2's software but spared Voyager 1 the risky rewrite

That said, Voyager 1's mission is not over by any stretch of the imagination, and Voyager 2 continues its journey unaffected by the travails of its sibling.

The [9]problem is an issue with one of Voyager 1's three onboard computers, called the Flight Data System (FDS). At the end of last year, the FDS started having issues communicating with Voyager's subsystems, which resulted in the Telemetry Modulation Unit (TMU) sending a repeating pattern of ones and zeroes back to Earth rather than the expected engineering and science data.

[10]

The Voyager team reckoned the issue was with the FDS and tried to restart it but to no avail.

The fact that the Voyager probes continue to function decades after their launch remains an impressive achievement, both on the part of the original engineers and designers and the teams that currently operate the spacecraft.

While JPL is suffering from some [11]severe budget constraints in the short term, the Voyager mission remains a reminder that when considering space exploration, long-term thinking is for the best. ®

Get our [12]Tech Resources



[1] https://twitter.com/NASAJPL/status/1754978848176029866

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

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

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

[5] https://www.theregister.com/2024/02/01/lessons_from_the_voyager_probes/

[6] https://www.theregister.com/2023/12/14/engineers_work_to_fix_voyager/

[7] https://www.theregister.com/2023/12/05/50_years_pioneer_10/

[8] https://www.theregister.com/2023/10/23/nasa_voyager_upgrades/

[9] https://www.theregister.com/2023/12/14/engineers_work_to_fix_voyager/

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

[11] https://www.theregister.com/2024/02/07/nasa_jpl_layoffs/

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



I am David Jones

All comments are pre-moderated.

You can expect your post to appear in the next 22.5 hours.

Bill Gray

No; you can expect your post to be approved in 22.5 hours. It'll be an additional 22.5 hours before it actually appears.

Little Mouse

22.5 light hours distance is seriously impressive.

There's got to be some kudos in Voyager passing the 1 light-day boundary. Is anyone here willing to do the necessary sums to calculate exactly when that will be?

I really hope it will still be sending/receiving when it does so.

Anonymous Coward

Given that it's got to 22.5 light-hours in ~46 years, that's pretty much 0.5light-hours/year. So I reckon that boundary will be about 3 years away.

(Assuming by 'day' you mean 24 hours, as opposed to a Martian sol or other equivalent definitions)

Lon24

Yep,the latency might be pretty poor but it is almost light years ahead of my bank's communication response. They are only two hundred earth miles distant.

NullDev

Is an "Earth mile" different than a "Mars mile"??

GregC

Based on available information (wiki and online distance converters!)

24 light-hours, 1 light-day, is 25902068371.2 (~26bn) km

22.5 light-hours is 24283189098 (~24bn) km

So Voyager has another 1618879273.2 (1.6bn-ish) km to go. Using a current speed of 17km/s (wiki says!), my maths says it will take 95228192 s, or just over 3 years, to reach the 1 light-day point.

Edit - or, what AC above said!

Reunite Gondwondaland!