PrefBlog

I will never whine about debugging problems again:

On March 3, the team noticed that activity from one part of the flight data system stood out from the rest of the garbled data. While the signal wasn’t in the format the Voyager team is used to seeing when the flight data system is functioning as expected, an engineer with NASA’s Deep Space Network was able to decode it.
…
The decoded signal included a readout of the entire flight data system’s memory.

By investigating the readout, the team determined the cause of the issue: 3% of the flight data system’s memory is corrupted. A single chip responsible for storing part of the system’s memory, including some of the computer’s software code, isn’t working properly. While the cause of the chip’s failure is unknown, it could be worn out or may have been hit by an energetic particle from space, the team said.

The loss of the code on the chip caused Voyager 1’s science and engineering data to be unusable.

Since there was no way to repair the chip, the team opted to store the affected code from the chip elsewhere in the system’s memory. While they couldn’t pinpoint a location large enough to hold all of the code, they were able to divide the code into sections and store it in different spots within the flight data system.

“To make this plan work, they also needed to adjust those code sections to ensure, for example, that they all still function as a whole,” according to an update from NASA. “Any references to the location of that code in other parts of the (flight data system) memory needed to be updated as well.”

This entry was posted on Monday, April 22nd, 2024 at 8:44 pm and is filed under Market Action. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.