Home » today » Technology » NASA Engineers Identify Cause of Voyager 1 Anomaly, Provide Hope for Repair

NASA Engineers Identify Cause of Voyager 1 Anomaly, Provide Hope for Repair

After months of sending unusable data to mission control, there is finally hope for the Voyager 1 spacecraft. NASA engineers have identified the cause of a strange mission anomaly and believe they can help the interstellar probe transmit data in readable form again.

Engineers from NASA’s Jet Propulsion Laboratory considerthat the Voyager 1 spacecraft is sending meaningless data due to corrupted memory hardware in the spacecraft’s flight data system (FDS).

The team suspects that one chip responsible for storing the corrupted portion of FDS memory is malfunctioning.

FDS collects data from Voyager’s science instruments, as well as engineering data about the spacecraft’s health, and combines it into a single package that is transmitted to Earth through one of the probe’s subsystems, the Telemetry Modulation Unit (TMU), in binary code.

FDS and TMU have difficulty communicating with each other. As a result, the TMU sends data to mission control in a repeating pattern of ones and zeros. NASA engineers aren’t entirely sure what damaged the FDS memory hardware—they think either the chip was hit by a high-energy particle from space, or it was simply worn out after 46 years of operation.

Voyager 1 was launched in 1977, less than a month after its sister probe, Voyager 2, began its own journey into space. The probe entered interstellar space in August 2012, becoming the first spacecraft to leave the heliosphere.

The problem first arose in May 2022 when the probe suddenly began sending meaningless Attitude and Position Control (AACS) data. Engineers solved the problem by sending telemetry data through one of the spacecraft’s other computers. In December 2023, Voyager 1 spoke in gibberish again.

On March 1, the team sent a test request to the spacecraft’s data acquisition system, a command that gently nudges FDS to use different sequences in its software package to identify the damaged partition. Two days later, Voyager 1 sent a signal containing data from the entire FDS memory, which helped the team determine the source of the failure by comparing with the previous one to find inconsistencies in the code.

Using a readout, the team confirmed that about 3% of the FDS memory was corrupted, preventing the computer from performing normal operations.

Engineers hope to solve the problem by developing a way for FDS to function without a corrupted memory block, allowing Voyager 1 to continue transmitting useful data.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.