Among other things, the FDS is designed to collect data from the science instruments as well as engineering data about the health and status of the spacecraft. It then combines that information into a single data "package" to be sent back to Earth by the TMU. The data is in the form of ones and zeros, or binary code. Varying combinations of the two numbers are the basis of all computer language.
Recently, the TMU began transmitting a repeating pattern of ones and zeros as if it were "stuck." After ruling out other possibilities, the Voyager team determined that the source of the issue is the FDS. This past weekend the team tried to restart the FDS and return it to the state it was in before the issue began, but the spacecraft still isn't returning useable data.
It could take several weeks for engineers to develop a new plan to remedy the issue. Launched in 1977, the spacecraft and its twin, Voyager 2, are the two longest-operating spacecraft in history. Finding solutions to challenges the probes encounter often entails consulting original, decades-old documents written by engineers who didn't anticipate the issues that are arising today. As a result, it takes time for the team to understand how a new command will affect the spacecraft's operations in order to avoid unintended consequences.
In addition, commands from mission controllers on Earth take 22.5 hours to reach Voyager 1, which is exploring the outer regions of our solar system more than 15 billion miles (24 billion kilometers) from Earth. That means the engineering team has to wait 45 hours to get a response from Voyager 1 and determine whether a command had the intended outcome.
Related Links
Voyager at JPL
Space Tourism, Space Transport and Space Exploration News
| Subscribe Free To Our Daily Newsletters |
| Subscribe Free To Our Daily Newsletters |
