All through the 5 months of troubleshooting, Voyager’s floor workforce continued to obtain indicators indicating the spacecraft was nonetheless alive. However till Saturday, they lacked perception into particular particulars concerning the standing of Voyager 1.

“It’s just about simply the way in which we left it,” Spilker mentioned. “We’re nonetheless within the preliminary phases of analyzing all the channels and taking a look at their tendencies. A few of the temperatures went down a bit bit with this time period that is gone on, however we’re just about seeing the whole lot we had hoped for. And that is at all times excellent news.”

Relocating Code

Via their investigation, Voyager’s floor workforce found {that a} single chip accountable for storing a portion of the FDS reminiscence had stopped working, most likely attributable to both a cosmic ray hit or a failure of ageing {hardware}. This affected a number of the laptop’s software program code.

“That took out a bit of reminiscence,” Spilker mentioned. “What they must do is relocate that code into a unique portion of the reminiscence, after which make it possible for something that makes use of these codes, these subroutines, know to go to the brand new location of reminiscence, for entry and to run it.”

Solely about three p.c of the FDS reminiscence was corrupted by the dangerous chip, so engineers wanted to transplant that code into one other a part of the reminiscence financial institution. However no single location is giant sufficient to carry the part of code in its entirety, NASA mentioned.

So the Voyager workforce divided the code into sections for storage elsewhere within the FDS. This wasn’t only a copy-and-paste job. Engineers wanted to switch a number of the code to ensure it can all work collectively. “Any references to the situation of that code in different components of the FDS reminiscence wanted to be up to date as effectively,” NASA mentioned in an announcement.

Newer NASA missions have {hardware} and software program simulators on the bottom, the place engineers can take a look at new procedures to ensure they do no hurt after they uplink instructions to the actual spacecraft. As a result of its age, Voyager does not have any floor simulators, and far of the mission’s authentic design documentation stays in paper kind and hasn’t been digitized.

“It was actually eyes-only to take a look at the code,” Spilker mentioned. “So we needed to triple verify. Everyone was wanting by means of and ensuring we had all the hyperlinks coming collectively.”

This was simply step one in restoring Voyager 1 to full performance. “We have been fairly positive it could work, however till it really occurred, we did not know 100 p.c for positive,” Spilker mentioned.

“The explanation we didn’t do the whole lot in a single step is that there was a really restricted quantity of reminiscence we may discover rapidly, so we prioritized one information mode (the engineering information mode), and relocated solely the code to revive that mode,” mentioned Jeff Mellstrom, a JPL engineer who leads the Voyager 1 “tiger workforce” tasked with overcoming this drawback.

“The following step, to relocate the remaining three actively used science information modes, is basically the identical,” Mellstrom mentioned in a written response to Ars. “The principle distinction is the out there reminiscence constraint is now even tighter. Now we have concepts the place we may relocate the code, however we haven’t but totally assessed the choices or decided. These are the primary steps we are going to begin this week.”