NASA Finds Cause of Voyager 2 Glitch

astroengine writes "Earlier this month, engineers suspended Voyager 2's science measurements because of an unexpected problem in its communications stream. A glitch in the flight data system, which formats information for radioing to Earth, was believed to be the problem. Now NASA has found the cause of the issue: it was a single memory bit that had erroneously flipped from a 0 to a 1. The cause of the error is yet to be understood, but NASA plans to reset Voyager's memory tomorrow, clearing the error."

Comments

Re:Really?

[pclminion]

Let me guess: cosmic ray. Is it really that hard? What else causes a single bit-flip error in space?

When you have a probe billions of miles from Earth, with no hope of ever physically retrieving it, and something weird happens, I don't think the first thing you do is start making assumptions.

Re:So.... reboot?

[Brett Buck]

Why don't they just always try that first?

        Because sometimes it doesn't come back on again.

      Brett

33 years and still going strong - nuclear FTW

[blind biker]

This is why you DO WANT nuclear energy in space! OK, Voyager 1 and 2 have RTGs, but even those are considered politically incorrect these days, especially such massive ones as in the Voyagers.

More nuclear power in spacecraft, I say. To provide propulsion (ion drive, or even better, explosive drive) and energy when far from the Sun. Fuck PC.

Hero

[LoudMusic]

NASA is my hero. They do cool shit all the time. Even when their stuff breaks, it's cool. Then they fix it and it's even more cool.

Re:Really?

[BitZtream]

Its also extremely important to note that not a single item you own is made to the specifications that Voyagers were made, even though made over 30 years ago.

Its also rather important to note that as unstable as most OSes are, they are several million times more complex than the code Voyager 1 and 2 run.

Finally, joke about Windows all you want ... if you do a default installation of Windows and you don't install any additional drivers or software, it is extremely stable and will just sit there for ages happy to do nothing but tick away.

Its also entirely feasable to find 1 stuck or flipped bit even using Java and .NET, you just have to actually understand the inner workings of this code which is not something pretty much any developer working in these environments has time to do these days.

Both things may be computers that run code and use electricity to do so, but thats about where the shared bits end. These guys have been using the same code for 30+ years ... they kinda know how it works and all its quirks at this point.

With all that said ... you're still right, its freaky impressive.

Re:Just incredible!

[Hurricane78]

tubes had that nice desirable sweet distortion...

There, fixed that for ya...