A one-day message delay changes everything
Operating Voyager 1 is a lesson in extreme latency. At roughly one light-day from Earth, a radio command travels for nearly 24 hours to reach the probe. Mission control then waits another full day for confirmation, creating a near-48-hour feedback loop for even the simplest instruction.
This vast distance means mission control cannot "steer" Voyager 1 like a drone. Instead, onboard systems must execute complex command sequences and protect the spacecraft autonomously. Engineers upload precise instructions, then patiently await telemetry confirming their execution, a process demanding meticulous planning and robust self-governance from the probe.
Launched in 1977 for a mission expected to last only a few years, Voyager 1 has defied all expectations. This scientific outpost, powered by decaying plutonium, continues to transmit data from beyond the planets, a testament to its original engineering and NASA’s sustained ingenuity. Its extraordinary lifespan necessitates ongoing, unprecedented remote maintenance.
Six computers, less memory than a photo
Voyager 1 operates with three primary computer subsystems, each with a redundant backup, totaling six onboard computers. The Computer Command Subsystem (CCS) processes mission sequences and manages fault protection. The Attitude and Articulation Control Subsystem (AACS) maintains the spacecraft’s orientation and antenna pointing toward Earth. The Flight Data Subsystem (FDS) collects, formats, and compresses scientific and engineering telemetry for transmission.
Combined, these six computers possess a mere 69 kilobytes of memory—less than a single high-resolution photograph on a modern smartphone. Engineers wrote the original software in assembly language, leaving minimal free space at launch. One programmer noted the pointing computer had only two words of memory left.
Crucially, Voyager’s memory was reprogrammable. Unlike the hardwired rope memory of the Apollo missions, which was immutable after launch, Voyager’s design allowed engineers to uplink software changes. This capability proved indispensable, enabling critical updates and repairs decades into its mission, including 18 software changes sent during the 1979 Jupiter flyby alone.
NASA moved code around a dead chip
November 2023 brought a new challenge: Voyager 1, still receiving commands, began transmitting only an unreadable, repeating pattern of ones and zeros. The Flight Data Subsystem (FDS), responsible for packaging science and engineering data, had malfunctioned, effectively blinding ground control.
Engineers initiated a remote diagnosis in March 2024, sending a targeted "poke" command to prompt a memory readout. This maneuver revealed the fault: a single failed memory chip had corrupted approximately 3% of the FDS memory. This small but critical failure rendered vast swathes of data unintelligible.
With no large, contiguous block of available memory, the team devised an audacious solution. They painstakingly split the affected code into smaller fragments and relocated these pieces into scattered, unused memory gaps. Critically, they then rewrote every reference point in the FDS software to reflect these new locations, translating changes into binary by hand without conventional software development tools or a physical test spacecraft.
This intricate repair unfolded in stages. Engineering data, detailing the spacecraft's health, returned in April 2024, marking the first readable telemetry in five months. By June, science data from all operating instruments resumed transmission, a testament to the team's ingenuity. For more details on the mission's history and ongoing operations, explore Voyager - NASA Science.
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
The next enemy is power, not distance
Voyager 1’s next great challenge is power. The spacecraft maintains its Earth-facing antenna alignment using thrusters, which fire intermittently to correct its orientation. However, aging fuel-system components, particularly a rubber part in the fuel tank, shed silicon dioxide, gradually narrowing the tiny fuel passages from 0.25 mm down to about 0.035 mm. This clogging threatens the thrusters’ reliability, making precise aiming increasingly difficult.
This engineering battle directly impacts the mission’s power budget. Voyager 1 runs on radioisotope thermoelectric generators (RTGs) that convert the heat from decaying plutonium into electricity. These generators lose approximately 4 watts of output each year. To compensate for the diminishing power, NASA engineers must selectively shut down heaters or science instruments, ensuring essential systems like communications and attitude control remain operational. Eight of Voyager 1’s ten instruments are now off.
The Deep Space Network must still capture an ever-fainter signal from a spacecraft that is nearly one light-day away. While NASA expects at least one instrument to continue operating into the 2030s, and communications to persist until approximately 2036, the remaining power and operational instruments will ultimately dictate how much longer Voyager 1 can transmit data from interstellar space. Each year brings the mission closer to its quiet conclusion.
Frequently Asked Questions
How much memory does Voyager 1 have?
Its six computers have about 69 kilobytes of memory combined, according to the source material.
How long does it take to communicate with Voyager 1?
A radio signal takes roughly a day to travel one way at light-day distances, so a command and reply can take about two days.
How did NASA fix Voyager 1’s 2023 data problem?
Engineers identified a failed memory chip, moved affected code into smaller free spaces and updated the program’s references remotely.
Can Voyager 1 still send science data?
It has returned science data after the 2024 software repair, though its instruments and power supply are being managed as the spacecraft ages.