Skip to main content

Voyager 1 Has Another Problem With its Computer System

For more than 46 years, the Voyager 1 probe has been traveling through space. On August 25th, 2012, it became the first spacecraft to cross the heliopause and enter interstellar space. Since then, mission controllers have maintained contact with the probe as part of an extended mission, which will last until the probe’s radioisotopic thermoelectric generators (RTGs) finally run out. Unfortunately, the Voyager 1 probe has been showing its age and signs of wear and tear, which is unavoidable when you’re the farthest spacecraft from Earth.

This includes issues with some of the probe’s subsystems, which have been a bit buggy lately. For instance, engineers at NASA recently announced that they were working to resolve an error with the probe’s flight data system (FDS). This system consists of three onboard computers responsible for communicating with another of Voyager 1’s subsystems, known as the telemetry modulation unit (TMU). As a result, while the spacecraft can receive and execute commands sent from Earth, it cannot send any science or engineering data back.

The main purpose of the FDS is to collect data from the probe’s science instruments and engineering data from the spacecraft itself. This data is then combined into a single package and sent to the TMU, which transmits in binary code back to Earth. Recently, mission controllers noticed that the TMU was transmitting a repeating pattern of ones and zeroes, which raised some eyebrows. After reviewing and ruling out all other potential causes, the Voyager team determined that the FDS was the source of the problem.

Artist’s impression of the Voyager mission looking back at the Solar System. Credit: NASA

Over the weekend, the mission team attempted to restart the FDS in the hopes that this would restore it to a working state. They did not succeed, and now the team anticipates that it could take several more weeks to develop a new plan to address the problem. This was not unexpected since both Voyager and its twin (Voyager 2) are the longest-serving spacecraft in history. When they launched in 1977, both probes represented cutting-edge astronautics, navigation, and communication technology.

However, both are now over forty years out of date, so finding solutions to problems often requires engineers and technical experts to consult the original documents. These decades-old documents were created by engineers who didn’t anticipate of problems the probes are countering today. As a result, it takes the mission team time to determine how a new command will affect the spacecraft’s operations and how to avoid unintended consequences. What’s more, commands from mission controllers take 22.5 hours to reach Voyager 1, which means that two-way communications take 45 hours.

This means that Voyager 1’s controllers have to wait almost two full days before they will learn if the solution they implemented worked. In the meantime, all NASA can do is troubleshoot the problem and wait for a solution that works to take effect. As for the Voyager 1 probe, it continues to explore the outermost regions of the Solar System and the is farthest artificial objects from Earth – 24 billion km (15 billion mi) and counting!

Further Reading: NASA

The post Voyager 1 Has Another Problem With its Computer System appeared first on Universe Today.



from Universe Today https://ift.tt/DK1VPwi
via IFTTT

Comments

Popular posts from this blog

Researchers Match Up 12 Meteorites with the Near-Earth Asteroids They Came From

Every day meteoroids blast through our planet’s atmosphere to hit the ground as meteorites. A team of researchers in Italy traced twelve of them to progenitor asteroids that orbit in near-Earth space. Scientists treasure meteorites because they reveal information about their parent bodies. In an arXiv paper, two Italian researchers—Albino Carbognani and Marco Fenucci—analyze the characteristics of the parent bodies of 20 selected meteorites. They were able to track all but eight back to their parent asteroids. Based on their work, the pair says at least a quarter of meteorites come from collisions that happened in near-Earth space and not in the Main Belt. Meteorites from Near-Earth Asteroids: How They Got Here Many meteorites are chondritic, similar to asteroids in the Main Belt (or came from it). In their paper, the authors point out that progenitor meteoroids (including many that fall to Earth and become meteorites) formed millions of years ago following collisions between main-...

JWST Takes a Detailed Look at Jupiter’s Moon Ganymede

Nature doesn’t conform to our ideas of neatly-contained categories. Many things in nature blur the lines we try to draw around them. That’s true of Jupiter’s moon Ganymede, the largest moon in the Solar System. The JWST took a closer look at Ganymede, the moon that’s kind of like a planet, to understand its surface better. Ganymede is basically a planet, except it doesn’t orbit the Sun. If it did orbit the Sun instead of Jupiter, it would be indistinguishable from a planet. It has a differentiated internal structure with a molten core that produces a magnetic field. It has a silicon mantle much like Earth’s, and has a complex icy crust with a deep ocean submerged beneath it. It has an atmosphere, though it’s thin. It’s also larger than Mercury, and almost as large as Mars. According to the authors of a new study, it’s an archetype of a water world. But even with all this knowledge of the huge moon, there are details yet to be revealed. This is especially true of its complex surface...

What Blew Up the Local Bubble?

In our neighborhood of the Milky Way, we see a region surrounding the solar system that is far less dense than average. But that space, that cavity, is a very irregular, elongated shape. What little material is left inside of this cavity is insanely hot, as it has a temperature of around a million Kelvin. from Universe Today https://ift.tt/KvVDeiC via IFTTT