Fixing Voyager: How NASA Restored Communications with Voyager 1 from Across the Solar System

Main ideas, concepts, and lessons

• Purpose of the talk

  • Introduces the Voyager “Grand Tour” mission and explains how Voyager 1’s communications were restored after it unexpectedly stopped sending usable science data back to Earth (November 2023).
  • Emphasizes that even after decades, the Voyager spacecraft still perform “hard science” from interstellar space.

• Voyager mission background

  • Launched in 1977, with a rare alignment of the outer planets (Jupiter, Saturn, Uranus, Neptune) occurring only about every 175 years.
  • Voyager 2 is noted as the only spacecraft to have done close flybys of both Uranus and Neptune.
  • After planetary missions, both spacecraft traveled out of the ecliptic plane and into interstellar space:
    • Voyager 1 entered interstellar space in 2012
    • Voyager 2 crossed in 2018
  • Despite distance, the craft continue operating in their 47th year (as of the talk).

• What went wrong (the communications/data failure)

  • In November 2023, Voyager 1 stopped transmitting scientific data back to Earth.
  • The team uses a “mailbox/letter” analogy:
    • Earth still received “letters” from Voyager 1, but the “page” inside was blank (no usable data).
  • The root cause was traced to the Flight Data Subsystem (FDS):
    • It synchronizes instruments and other onboard computers and composes the telemetry “letters.”
    • A corrupted block of 256 words (instructions) stored in one integrated circuit caused the system to misbehave.
  • A key diagnostic clue:
    • Different telemetry “modes” changed behavior, indicating a software issue, not just a general hardware failure.
    • Hardware attempts (changing where possible) didn’t fix it, and telemetry analysis suggested corruption.

• How the team fixed it from extremely far away

  • This was described as a first-time event for that team approach:
    • Normally, software patches are tested in a testbed/simulator—but they lacked those tools for Voyager’s specific situation.
    • They performed the patch by hand analysis.
  • Steps/approach described (methodology):
    • Gather and review legacy documentation and prior knowledge (including handwritten notes from decades ago).
    • Use subject-matter experts and records from around JPL (including a retiree with pre-launch Voyager familiarity).
    • Create/obtain an FDS program (from an old document) to generate a memory readout.
    • Compare expected vs. actual memory contents to locate a corrupted block of 256 words.
    • Determine the needed update and implement a software patch by manually editing instructions (address/instruction pairs were shown as an example).
    • Validate the patch externally as much as possible by comparing results with what they expected the FDS to do.
    • Uplink the corrected code on April 20, 2024.
    • Confirm success by observing that the “blank letters” began to contain words/data again.

• Significance of the fix

  • The successful uplink was portrayed as extraordinarily satisfying:
    • It was observable in real time (data/words returned rather than blank transmissions).
    • The talk highlights team joy and achievement in the operations room.
  • It underscores Voyager as a continued, exceptional engineering platform—operating far beyond the solar system environment.

• Communications and signal-strength realities

  • Signal and transmission are described as extremely weak/low-power:
    • Earth receives something comparable to a refrigerator light bulb’s worth of energy spread over huge distance (15 billion miles).
    • Uplink power is much larger (figures discussed included 100 kW range, as stated).
  • Signals require:
    • Giant antennas
    • The Deep Space Network (DSN) using multiple stations/antennas to improve reception.

• What Voyager instruments still do in interstellar space

  • Voyager continues with five science instruments still operating, including:
    • Magnetometer (magnetic field intensity/direction)
    • Plasma Wave subsystem (radio waves from space events)
    • Low-energy charged particle instrument (low-energy cosmic rays in multiple directions)
    • Plasma spectrometer (composition/density/temperature of interstellar plasma)
    • Cosmic ray spectrometer (highest energy cosmic rays)
  • Additional instruments:
    • Camera/scanning instruments were turned off earlier (especially 1990 after the “family portrait”).
    • The scan platform instruments were shut down to conserve power as energy dwindles.

• Key science highlights and open mysteries

  • Heliosphere shielding: Cosmic ray instrument suggests the heliopause shields Earth from ~75–80% of high-energy cosmic radiation.
  • Magnetic field direction puzzle: Expectation that magnetic field direction would shift from solar to interstellar orientation—but it hasn’t yet.
  • Persistent plasma/magnetic jump: Voyager 1 observed a jump in plasma/magnetic intensity that persisted for ~five years (unresolved whether solar or interstellar cause).
  • “Interstellar eyes” analogy:
    • Voyager provides a view of currents, shocks/waves, and particle populations that humans can’t perceive directly.

• Future of Voyager

  • Power constraints will eventually force:
    • Turning off more science instruments and possibly
    • No longer pointing the high-gain antenna to Earth.
  • When communications can no longer be maintained:
    • Voyager craft become silent ambassadors orbiting the Milky Way for immense timescales.
  • Each spacecraft carries a Golden Record:
    • Encodes sights/sounds of Earth.
    • Intended for discovery by future beings, with long expected durability times.

• Q&A themes emphasized

  • No new photos: cameras were turned off long ago (no current power to reactivate).
  • Clarification: Voyager is in interstellar space but not gravitationally out of the solar system’s region where objects like Oort Cloud remain bound—hence ambiguity people discuss.
  • Communication duration depends on data rate and DSN capabilities; power may run out before full communication strategies fail.
  • Programming language challenge:
    • Voyager computers use custom designs and include Assembly Language; the specific flight hardware/software environment doesn’t exist on Earth in the same way.
  • Hardware failure cause:
    • Electronic part failure; cosmic radiation is mentioned as a plausible contributor but not confirmed.
  • “Coffee consumed” and dedication:
    • Humor about late nights and problem-solving intensity; some staff sleep in offices during data events.
  • Communication protocol basics:
    • Radio signals include framing/headers and identifiers so Earth/spacecraft can target the correct spacecraft (“like addresses”) and handle telemetry formatting.

---

Methodology / list of instructions (detailed bullet format)

Restoring Voyager 1 communications (as described in the talk)

• Confirm the symptoms

  • Detect that Voyager 1 transmissions arrived but contained no usable science data (“blank letter”).

• Identify likely subsystem

  • Infer the issue is tied to the Flight Data Subsystem (FDS) because it:
    • Synchronizes onboard components
    • Formats instruments’ outputs into telemetry sent to Earth

• Diagnose using telemetry and operational evidence

  • Attempt hardware-level changes where possible in the FDS path and configuration.
  • Test different telemetry modes and observe behavior changes:
    • Mode-dependent changes suggested a software/corruption event.

• Reconstruct the needed diagnostic capability

  • Locate an FDS program from old documentation (minimum FDS program).
  • Use the program to generate a memory readout of what the onboard computer stored.

• Perform expected-vs-actual comparison

  • Determine what memory contents should be.
  • Compare against what the spacecraft actually reported in memory readout.
  • Find a corrupted block of 256 words in a specific integrated circuit that held required instructions.

• Create a patch without a normal test environment

  • Because a simulator/testbed wasn’t available, perform manual software patch analysis:
    • Edit the instruction at specific memory addresses (address/instruction pairs were shown as an example).
    • Apply “multiple pairs of eyes” review/verification to reduce error risk.

• Uplink the corrected instructions

  • Send the updated code to Voyager from Earth (the talk indicates uplink occurred on April 20, 2024).

• Validate success through real observable results

  • Wait for the next “letter” telemetry:
    • Confirm that the previously blank data now returned correctly populated content (“blank page becomes words”).

• Continue awaiting/monitoring the final fix results

  • The talk notes “awaiting the results of that Final Fix” even after restoration.

---

Speakers / sources featured (identified)

• Gregory Smith — Host; Communications and Education Directorate, JPL
• Calla Coffield — Co-host; Media Relations Specialist, JPL (also mentions being in DSN “Crows Nest” operations)
• Kareem Badine — Voyager Mission Manager, JPL
• Dr. Linda Spilker — Voyager Project Scientist, JPL
• Dave Cummings — Mentioned as the engineer who wrote the code for the patch (named during discussion of the April 20, 2024 response photo)
• NASA / JPL Jet Propulsion Laboratory (JPL) — Organizational source of the talk and mission teams
• Deep Space Network (DSN) — Operational system discussed (not a person, but a featured source/tool)