The Voyager 1 spacecraft, launched in 1977, is a testament to the ingenuity of its engineers and the resilience of its design. Despite operating with computer systems that have less memory than a typical phone photo, it has been successfully carrying out commands from Earth for nearly five decades. This remarkable feat challenges the common assumption that more computing power is always necessary to solve complex problems.
The spacecraft's three principal computer systems, designed in the 1970s, are each responsible for different aspects of the mission. The Computer Command Subsystem interprets instructions and manages spacecraft sequencing, the Flight Data Subsystem collects and packages science and engineering data, and the Attitude and Articulation Control Subsystem controls the spacecraft's orientation. Together, these systems run the mission with memory measured in kilobytes, not gigabytes.
One of the key factors in Voyager 1's longevity is its redundant hardware design. The spacecraft was built with nearly everything redundant, including duplicate major systems and critical components. This redundancy was deliberate, as Suzanne Dodd, the Voyager project manager, explained, "Having two spacecraft — right there is a redundancy." This design choice allowed the mission to continue even after a failure.
However, this redundancy has its limits. The Flight Data System computers, for example, were originally carried in pairs. Unfortunately, the backup FDS failed in 1981, leaving the spacecraft dependent on the remaining unit. This scenario is not unlike keeping an aging car running by working around failed parts.
In November 2023, Voyager 1 began sending back a pattern of meaningless ones and zeros, indicating a failure in its Flight Data System. Engineers identified the damaged area and determined that about 3% of the FDS memory had been corrupted, likely due to a single memory chip failure. The repair process was challenging due to the limited memory available.
The engineers had to divide the damaged software into smaller pieces and search for unused memory sections to store them. They also identified processes and data modes that were no longer needed, freeing up space. The first relocated section of code was transmitted in April 2024, and the spacecraft returned readable engineering data for the first time in over five months.
This repair demonstrated the flexibility and resilience of the Voyager 1 design. The engineers were able to work around a failure that none of them could have predicted, aboard a spacecraft that will never be physically examined or touched by humans. John Casani, the Voyager project manager, emphasized that the team "didn’t design them to last 30 years or 40 years, we designed them not to fail."
The repair also highlighted the increasing risk with each intervention as the spacecraft ages. Dodd noted that future decisions will require more analysis and caution. The Voyager 1's success challenges the notion that more computing power is always necessary, demonstrating that careful design and redundancy can enable remarkable feats of engineering and longevity.
