In This Episode: I’m recording this episode the evening of July 20th: the 50th anniversary of the first humans landing on the moon. If you think it maybe took Uncommon Sense to get there, you’re right: it took an extraordinary amount, and this episode talks about some of the details that you may not have heard about before.
- NASA budget information (historical through 2017) is here. The military budget info is from here and here.
- The several photos noted are interspersed in the transcript.
- Errata Note: I said at the time of Kennedy’s go-to-the-moon challenge, humanity had less than 2 hours of experience in space. It’s actually barely over 2 hours. (The most important number in this context remains the same: the U.S. was publicly making this challenge to itself after it had a single manned space flight that lasted a mere 15 minutes!
Welcome to Uncommon Sense. I’m Randy Cassingham.
When President John F. Kennedy announced the goal, “before this decade is out, of landing a man on the Moon and returning him safely to the Earth,” there certainly wasn’t a universal feeling of that being a great goal, even from Americans. The war in Vietnam was raging, and so were civil rights protests. And NASA wasn’t even sure it could be done.
When Kennedy gave that proposal as a speech to Congress on May 25, 1961, humankind — and I mean the Russians and Americans combined — had a total experience of less than two hours of human flight in space: 108 minutes by the USSR’s Yuri Gagarin, and a mere 15 minutes by American Alan Shepard, who had flown just 20 days prior to that speech. Russia was certainly not going to give us any lessons learned from their efforts: the whole thing was known as a “space race” — and landing humans on the moon was the biggest possible goal available at the time …and Russia was in the lead.
Flying to the moon and back wasn’t an order of magnitude more complex than Freedom 7’s suborbital flight: it was multiple orders of magnitude more complex, especially with JFK’s added difficulty factor: we have to return those guys to Earth “safely”!
So how did we do it? First, NASA was given enough money to do it. You often hear about the huge cost of the Apollo program, but NASA’s budget peaked out at just 4.4 percent of the federal budget, in 1966. By comparison, today NASA’s budget is less than one-half of one percent of the federal budget. By the way, in 2015 — the most recent figures I could find — our military spending was just shy of 16 percent of the entire budget, and is more than the next seven countries combined.
Still, that meant NASA was able to hire lots of engineers: they could hire Uncommon Sense, and the project was interesting enough that those engineers were willing to take government salaries.
But what was it they had to invent? It wasn’t just rockets, even though that technology was complex enough all by itself.
They knew they’d need computers, and they certainly had them. But they also desperately needed something that hadn’t been invented at that time: software engineering. You may have heard of Margaret Hamilton: she’s had some great press over the past few years, mostly centered around a photograph of her standing next to a printout of the software for Apollo, most of which she wrote. She was the director of what became the Software Engineering Division of the MIT Instrumentation Laboratory, leading the team that developed the on-board flight software for NASA’s Apollo space program. When she started on the project in 1963, Hamilton was 26 years old.
And she’s the one who is credited with popularizing the term “software engineering.” “Software during the early days of [Apollo] was treated like a stepchild and not taken as seriously as other engineering disciplines, such as hardware engineering,” Hamilton said later, even though, or perhaps because, MIT was such an established engineering center. “It was regarded as an art and as magic, not a science,” she continued. “I began to use the term ‘software engineering’ to distinguish it from hardware and other kinds of engineering.” It took years for the term to take hold.
And what sort of computer might that engineered software run on? At the time, computers were giant things that filled rooms. Even a “small” computer was the size of a household refrigerator. They needed something small and light to go onto the tiny and primitive spacecraft. MIT was developing the software, but they also developed the hardware in parallel. The result was the Apollo Guidance Computer, or AGC. The interface was called the DSKY, short for display and keyboard, and it was a marvel in itself. The Show Page has a photo.
The AGC had to juggle 200 different inputs and outputs, taking in data from sensors, radar, and uploaded information from Mission Control in Houston. It could control the spacecraft engines and attitude thrusters, and had to keep track of exactly where the ship was in relation to Earth and the moon, all the while displaying what was up to the astronauts via the DSKY. If it failed, there would be no way to recover the astronauts: they would die in space. It had to figure out what tasks were the most important and do those first — which wasn’t something computers ever had to do before.
Oh, and on top of all of that: it couldn’t really be fully tested until it was on a spacecraft, flying in space. It had to be operated not by computer scientists in white coats, but by test pilots-turned-astronauts wearing bulky spacesuits with clumsy gloves punching information onto the DSKY. The AGC also had to be able to recover by itself in case of any failure: rebooting and picking up where it left off, and do it quickly. That was in the 1960s: can your computer do that now, in the 20-teens?! And by the way: it did it all with just 73 kilobytes of memory — memory that was hand-made.
And that fault tolerance proved to be necessary. Remember that while Apollo 11’s Eagle was landing, the computer was throwing errors? 1201 and 1202 alarms: overloaded, in part because the command module rendezvous radar was still on, which wasn’t needed during the landing phase, but was supposed to be kept on standby in case of an abort, which meant they’d have to go back and rendezvous with the command module. But here’s the thing: the computer was working exactly as designed: when Buzz Aldrin commanded the computer to calculate the “Delta-H” — the difference between the computer’s calculated altitude and the landing radar’s measured altitude — that was enough to cause the overflow with all that going on.
So the computer displayed the error as it threw out the lower priority Delta-H calculation so it could do the higher-priority approach calculations and engine thrust control.
And here’s how well that computer software and hardware worked: over 11 Apollo missions, including the nine that flew to the moon and back, 2,504 hours of space flight, there was not one documented software or hardware fault. The perfect performance of the computer engineering absolutely made Apollo possible.
The second big piece of the puzzle I’ll talk about today is something else we take for granted today. So we have humans out in space in a specific direction and we not only need to talk to them at all times, but they’re sending back video streams so that hundreds of millions of people all around the world can watch, live.
Yet Earth is spinning on its axis: the moon certainly isn’t visible from Houston, Texas, 24 hours a day, so how could Mission Control talk to them after the moon sets, until it rises again later? You might think “satellites,” but they were pretty primitive in the 1960s too.
Enter the Manned Space Flight Network. Because everything in NASA has to have an acronym, they called it MSFN. NASA already had the Deep Space Network, operated by the Jet Propulsion Laboratory for unmanned spacecraft, and that was used also, but MSFN antennas were located in several spots around the world, including on ships in the ocean, so that at any particular time during the Earth’s 24-hour rotation, at least one would have a clear view toward the moon. JPL had a big part of this since they already had a fair amount of experience communicating with spacecraft beyond Earth orbit with the DSN.
There was also the Spacecraft Tracking and Data Network, though STDN wasn’t anywhere near as pronounceable as MSFN. STDN was mostly used for spacecraft in Earth orbit, but expanded greatly to support the Apollo missions that went beyond low Earth orbit.
But just having the antennas — the radio communication system — wasn’t enough: they had to be connected to each other, and to Mission Control in Houston, and also be able to feed signals to television networks all around the world. They needed data transmission. A perfect use of the Internet …but that didn’t exist yet either.
Even though the system was heavily computerized, thanks to 39 Univac mainframes installed around the world, the system required 2,700 people to keep it all going. They used two million miles of leased communication lines and two satellites to connect it all together, and this was in the era of multi-dollar 3-minute long-distance phone calls; the phone bill for it all was $70 million per year.
The data rate of the voice, video, and telemetry coming down from the spacecraft was around 51,000 bits per second. As per usual, upload wasn’t as fast: about 2,000 bits per second, but mostly they just needed to send voice, though they could upload some data to the Apollo computer, too.
It was all designed and operated by NASA’s Goddard Spaceflight Center in Greenbelt, Maryland, just outside Washington, D.C., and then piped to Mission Control in Houston via a dedicated circuit running at 40,800 bits per second. Remember, this is the 1960s, but it still took nearly 30 years for home-based computer modems to beat that rate!
Once on the moon, the astronauts were scheduled to sleep for five hours before going out for their walk, moon rock collection, and setting up several scientific instruments. But hey: if you were the first man on the moon, the culmination of work by 300,000 people working full time for years to get you there, would you be able to sleep? So they decided to do it all early.
Apollo 11’s Eagle lunar module had landed on July 20 at 20:17 Coordinated Universal Time, or UTC, which was the new name for what many still called Greenwich Mean Time. They had plenty to do before their scheduled rest period. They didn’t use all five rest hours after their work was done, so Neil Armstrong stepped onto the moon’s surface six hours and 39 minutes later, at 02:56 UTC, which was 9:56 P.M. in Houston. A lot of kids were awakened by their parents to come watch. I was still up: I lived in California, and even though I was pretty young, we had been watching it all on TV all evening, and it was not quite 8:00 P.M.
And the video of that moment and the radio transmissions from the moon were received at the Honeysuckle Creek Tracking Station near Canberra, Australia. As the Earth rotated, communications were switched to the larger Parkes radio telescope in New South Wales, Australia. And thanks to the first worldwide data network built for $370 million, everyone in the world in range of a TV set could watch live, and hear those words capping America’s victory in the space race: “That’s one small step for man, one giant leap for mankind.”
Meanwhile, during the missions, most of the time the tracking systems on Earth could pinpoint each spacecraft’s position during flight to within 30 feet, and measure their velocity to within 1 mile per hour, and report it on a console at Mission Control on command.
Now that’s a data network. And just a couple of examples why I say that when you really, really need Uncommon Sense, if you have enough money, you can rent it and make truly incredible things happen.
The Show Page for this episode with several photos and links are at thisistrue.com/podcast38, and you’re also welcome to comment there. That’s possible because some of the technology of the Internet has the Spacecraft Tracking and Data Network as an ancestor. A lot of things were invented to make Apollo happen. All the money spent on Apollo was spent right here on Earth, and we’re still benefiting from thousands of spinoffs that make life on Earth better. That’s Uncommon Sense in action.
I’m Randy Cassingham … and I’ll talk at you later.
Note: Part One to this story is the previous blog entry: One Small Step for [a] Man
Also related: Dinner with Neil Armstrong
- - -
This page is an example of Randy Cassingham’s style of “Thought-Provoking Entertainment”. His This is True is an email newsletter that uses “weird news” as a vehicle to explore the human condition in an entertaining way. If that sounds good, click here to open a subscribe form.
To really support This is True, you’re invited to sign up for a subscription to the much-expanded “Premium” edition:
Q: Why would I want to pay more than the regular rate?
A: To support the publication to help it thrive and stay online: this kind of support means less future need for price increases (and smaller increases when they do happen), which enables more people to upgrade. This option was requested by existing Premium subscribers.