The Longest Tech Support Call: Apollo 14 Computer Hack

Deep-voiced and aptly named [Scott Manley] posted a video about the computer hack that saved Apollo 14. Unlike some articles about the incident, [Scott] gets into the technical details in an entertaining way. If you don’t remember, Apollo 14 had an issue where the abort command button would occasionally signal when it shouldn’t.

The common story is that a NASA engineer found a way to reprogram the Apollo guidance computer. However, [Scott] points out that the rope memory in the computer wasn’t reprogrammable and there was no remote way to send commands to the computer anyway.

The initial patch had the astronauts use the DSKY to clear a bit that would prevent an abort from occurring. However, there was a chance that some other code would set that bit again as part of normal operations. If the bit was set and the switch malfunctioned, you could get a spurious abort. Engineers sent them another procedure to fool the computer into thinking it was already executing an abort which solved that problem.

However, this required a lot of effort during operations to make everything work. [Scott] shows you the nouns and verbs used and explains them in detail. It is rare to find such a technical treatment of this story and the NASA engineers were certainly doing a hack in the truest sense of the word.

The DSKY is no stranger to the pages of Hackaday. We’ve even talked about the odd rope memory before. While Apollo 13 got the big budget movie, the Apollo 14 hack is a great story, too. And without it, we’d have never had a golf shot on the moon.

12 thoughts on “The Longest Tech Support Call: Apollo 14 Computer Hack

      1. Today I spent 55 minutes on the phone walking someone through a wifi issue because the laptop didn’t have an airplane mode switch. At least, it didn’t until I showed up in person and flipped it.

  1. There was yet another “Hack” on that flight. When Alan Shepard was descending on his flight path toward the moon landing, the landing radar was reading “gibberish”. NASA flight parameters say that if there is no landing radar by a certain altitude then the landing must be aborted and Shepard would have to fire the accent rockets. He was very close to this go/no go altitude when a brilliant young engineer noticed something about the “gibberish” and had them tell Alan to turn off his radar, and turn it back on. (re-boot) He did and, he received good radar info numbers right away. What happened was that while the craft was turning into its landing attitude the radar was turned on and since it was pointed out into space at that moment, it received no bounce back signal and was reading “infinity”. Alan was asked many times if he was going to go ahead and abort, or just fly it down if the radar did not come up and he always said…”You’ll never know.” A simple hack maybe, but brilliant and timely. It saved that mission.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s