Saturn V Flight Manual (1969) [pdf]
history.nasa.gov
history.nasa.gov
http://www.apolloguidancecomputer.com/index.html
http://www.amazon.com/The-Apollo-Guidance-Computer-Architect...
(regarding the flight computers)
The powered flight major loop contains guidance and navigation calculations,
timekeeping, and all repetitive functions which do not occur on an interrupt
basis.
The minor loop contains the platform gimbal angle and accelerometer sampling
routines and control system computations. Since the minor loop is involved
with vehicle control, minor loop computations are executed at the rate of 25
times per second during the powered phase of flight. However, in earth
orbit, a rate of only ten executions per second is required for satisfactory
vehicle control.
The execution time for any given major loop, complete with minor loop
computations and interrupts, is not fixed.
(regarding the Vehicle Assembly Building) The high bay area which is located in the northern section of the building,
is approximately 525 feet high, 518 feet wide, and 442 feet long. It
contains four checkout bays, each capable of accommodating a fully
assembled, Saturn V space vehicle.
[it's not a rocket, it's a space vehicle. Kind of like boats aren't vessels] Each pair of opposite checkout bays is served by a 250-ton bridge crane with
a hook height of 462 feet.https://drive.google.com/file/d/0B8iAUeIURaT8ZS1PbTlMTjlCams...
Fun explanation. "he did the math"
Most engineering work was done in FORTRAN, and it ran very efficiently on the hardware. There were (usually) no CPU cycle sucking GUIs to slow down the computers.
As a high school student in the early 1970s I was privileged to take a summer course at the Goddard Institute for Space Studies [2] where they had an IBM 360/95 mainframe [3] for the scientists to take turns using (job entry by punched cards, job output by paper printout).
It's been so many years, and it was only casually explained to me, but I think NASA used three other 360/95 mainframes (the IBM top of the line at the time) located at the Goddard Space Flight Center [4] in Greenbelt MD to track the Apollo missions. I think these ran the same program more-or-less in triplicate (but there was no hardware for syncing). I think NASA also had an IBM 7094 [5] running an independently written program as a backup in case something went wrong with the S/360 computers.
Trust me, these computers were very very capable for the time. It's not like the primitive computer onboard the Apollo LEM. Mainframes were quite up to the task.
[1] http://en.wikipedia.org/wiki/Mainframe_computer#History [2] bonus points for whoever looks up that institution in Wikipedia and checks the picture to see what's located on the ground floor [3] http://en.wikipedia.org/wiki/IBM_System/360#Table_of_System.... [4] http://en.wikipedia.org/wiki/Goddard_Space_Flight_Center [5] http://en.wikipedia.org/wiki/IBM_7090#Notable_applications
But color TV had been widely available for about a decade. In fact, I watched the 1969 moon landings on my parents 1961 color Zenith. (They had rotary phone well into the 80s, however.)
That pilot had started his career on biplanes and ended it (in a crash, unfortunately) flying F-4 Phantom Jets (Commonly called Third generation Jets).
In my mind these eras of flight have been so ... seperated that I could not really imagine one man flying basically such a wide range of technology (and of course, he saw the moon landings).
My Dad told me that his first airplane ride was as a kid when a barnstormer put on a show at his town in Utah. The pilot/showman took him up in his Jenny:
http://en.wikipedia.org/wiki/Curtiss_JN-4
The kicker is that Dad told me this when he, Mom, and I were at flight level 350 about halfway to Hawaii for their 61st wedding anniversary, flying in a Boeing 757.
From an iffy ragwing biplane to a routine miracle world-spanning machine in his lifetime. Wonder if I'll get to see the equivalent of 757 service to Mars before I shuffle off...
Reading through the descriptions of some of the flight and launch control systems gives me a high level of respect for the software folk responsible. Sure, the systems were simple compared to today, but there was no room for any of the sloppiness we see passed off as "software engineering" in the interim years. "Mmm, I'm not entirely sure about that launch abort method, but we'll check it in, see if test finds anything."
Apollo Lunar Module documentation: https://www.hq.nasa.gov/alsj/alsj-LMdocs.html
I guess someone lost the PDF for it.
It seems to me the chances of reaching the rubber vestibule or the coil-spring-cushioned blast room are fairly slim.
Also, command module and spacesuit demo: http://www.youtube.com/watch?v=re0F-DgNQTA
You don't have permission to access /ap12fj/pdf/a12_sa507-flightmanual.pdf on this server.