In March, NASA’s Voyager 1 operating team sent a digital “poke” to the spacecraft, prompting its flight data subsystem (FDS) to send a full memory readout back home.
This memory dump revealed to scientists and engineers that the “glitch” is the result of a corrupted code contained on a single chip representing around 3% of the FDS memory. The loss of this code rendered Voyager 1’s science and engineering data unusable.

The NASA team can’t physically repair or replace this chip, of course, but what they can do is remotely place the affected code elsewhere in the FDS memory. Though no single section of the memory is large enough to hold this code entirely, the team can slice it into sections and store these chunks separately. To do this, they will also have to adjust the relevant storage sections to ensure the addition of this corrupted code won’t cause those areas to stop operating individually, or working together as a whole. In addition to this, NASA staff will also have to ensure any references to the corrupted code’s location are updated.
On April 18, 2024, the team began sending the code to its new location in the FDS memory. This was a painstaking process, as a radio signal takes 22.5 hours to traverse the distance between Earth and Voyager 1, and it then takes another 22.5 hours to get a signal back from the craft.
By Saturday (April 20), however, the team confirmed their modification had worked. For the first time in five months, the scientists were able to communicate with Voyager 1 and check its health. Over the next few weeks, the team will work on adjusting the rest of the FDS software and aim to recover the regions of the system that are responsible for packaging and returning vital science data from beyond the limits of the solar system.




