Re:Diskee: Apollo's Most Important Crewmember
by joezydeco on Tuesday January 22, 2019 @09:04PM
(#18975015)
The DSKY was a demo.
“The DSKY and PINBALL (something flashy with buttons) was a demo.
And that demo got us to the moon.
"Apparently, nobody had yet arrived at any kind of software requirements for the AGC's user interface when the desire arose within the Instrumentation Laboratory to set up a demo guidance-computer unit with which to impress visitors to the lab. Of course, this demo would have to do something, if it was going to be at all impressive, and to do something it would need some software. In short order, some of the coders threw together a demo program, inventing and using the verb/noun user-interface concept, but without any idea that the verb/noun concept would somehow survive into the flight software. As time passed, and more and more people became familiar with the demo, nobody got around to inventing an improvement for the user interface, so the coders simply built it into the flight software without any specific requirements to do so."
Re:Diskee: Apollo's Most Important Crewmember
by btown on Tuesday January 22, 2019 @05:58PM
(#18973516)
It's funny that the personified user interface is used as the title, because the star of the show is something much more hidden - one of the first multitasking "operating systems" correctly handling, and limiting the impact of, an unforeseen CPU-hungry process in the midst of the first moon landing! The OP's a fascinating read and more technical than the title might imply.
For anyone interested in the process of compiling and loading the code for these systems (available at https://github.com/chrislgarry/Apollo-11/ ) into the "core rope memory" used for program storage in the capsules, here's one of the original spec documents, as well as an image from that document showing what I'd call a "compilation-bureaucracy-pipeline" that's a fascinating glimpse into software deployment practices.
Re:Diskee: Apollo's Most Important Crewmember
by lcuff on Tuesday January 22, 2019 @05:46PM
(#18973421)
This article makes it seem more dramatic and spur-of-the-moment than other writings on the same topic I've read. The Wikipedia article on Jack Garman asserts (unsourced) that they'd generated a 1202 alarm in simulations and Bales had (incorrectly) called for an abort there. So it was actually a rehearsed scenario, with an analyzed "should go anyway" decision.
Re:Diskee: Apollo's Most Important Crewmember
by troutwine on Tuesday January 22, 2019 @05:08PM
(#18973084)
If you're interested in the Apollo Guidance Computer there's some really excellent material out there in the world to learn more. My two favorite books are:
* The Apollo Guidance Computer: Architecture and Operation - Frank O'Brien
* Digital Apollo: Human and Machine in Spaceflight - David A. Mindell
Re:Diskee: Apollo's Most Important Crewmember
by RachelF on Tuesday January 22, 2019 @06:27PM
(#18973885)
For those interested in the engineering details behind the whole flight, from engines, to power systems, guidance, navigation and computers, I would say my favourite book is
Re:Diskee: Apollo's Most Important Crewmember
by kens on Tuesday January 22, 2019 @05:35PM
(#18973321)
I recommend Journey to the Moon by Eldon Hall, designer of the AGC. The O'Brien book has a lot of good information but also a lot of problems. Sunburst and Luminary is also interesting, written by Don Eyles who wrote much of the lunar landing code. He goes into a detailed explanation of the 1202 program alarms.
Re:Diskee: Apollo's Most Important Crewmember
by 1201alarm on Wednesday January 23, 2019 @11:25AM
(#18979618)
Eyles came to the Vintage Computer Festival-East in Wall, NJ last year, and was introduced by Frank O'Brien who's a regular there. He actually did a code walkthrough of the Apollo 14 flaky-switch hack - coolest talk I've ever attended. Scott Manley did a pretty good Youtube episode on the Apollo 14 hack last year also; the two of them complement each other nicely.
It describes that not just DELTAH was killed due to overload, but that whole system restarted (and reloaded critical landing tasks that were restart-protected)
“The DSKY and PINBALL (something flashy with buttons) was a demo. And that demo got us to the moon. "Apparently, nobody had yet arrived at any kind of software requirements for the AGC's user interface when the desire arose within the Instrumentation Laboratory to set up a demo guidance-computer unit with which to impress visitors to the lab. Of course, this demo would have to do something, if it was going to be at all impressive, and to do something it would need some software. In short order, some of the coders threw together a demo program, inventing and using the verb/noun user-interface concept, but without any idea that the verb/noun concept would somehow survive into the flight software. As time passed, and more and more people became familiar with the demo, nobody got around to inventing an improvement for the user interface, so the coders simply built it into the flight software without any specific requirements to do so."
http://www.ibiblio.org/apollo/ForDummies.html
For anyone interested in the process of compiling and loading the code for these systems (available at https://github.com/chrislgarry/Apollo-11/ ) into the "core rope memory" used for program storage in the capsules, here's one of the original spec documents, as well as an image from that document showing what I'd call a "compilation-bureaucracy-pipeline" that's a fascinating glimpse into software deployment practices.
https://www.ibiblio.org/apollo/Documents/HSI-208496.pdf
https://imgur.com/a/wBYt1o6
Wikipedia says there were visible-light LEDs in 1962 (https://en.wikipedia.org/wiki/Light-emitting_diode#Discoveri...), but even ignoring they emitted red light, which the photos do not show, I think it’s unlikely they used them in this device.
https://en.wikipedia.org/wiki/Apollo_Guidance_Computer#DSKY_... claims it used ”green high-voltage electroluminescent seven-segment displays”. That seems more likely to me.
Fran Blanche attempted a GoFundMe project to recreate these displays. Unfortunately the project stalled.
https://www.gofundme.com/apollo-dsky-display-project
https://hackaday.com/2017/05/29/re-creating-the-apollo-dskys...
* The Apollo Guidance Computer: Architecture and Operation - Frank O'Brien
* Digital Apollo: Human and Machine in Spaceflight - David A. Mindell
Fascinating machine.
"How Apollo Flew to the Moon" by W David Woods https://www.amazon.com/Apollo-Flew-Springer-Praxis-Books/dp/...
https://www.youtube.com/watch?v=F6S-mmunKuo
First episode: https://www.youtube.com/watch?v=2KSahAoOLdU
It describes that not just DELTAH was killed due to overload, but that whole system restarted (and reloaded critical landing tasks that were restart-protected)
https://www.pbs.org/wgbh/nova/video/apollos-daring-mission/