Apollo PGNCS

The Apollo primary guidance, navigation, and control system (PGNCS) (pronounced pings) was a self-contained inertial guidance system that allowed Apollo spacecraft to carry out their missions when communications with Earth were interrupted, either as expected, when the spacecraft were behind the Moon, or in case of a communications failure. The Apollo command module (CM) and lunar module (LM), were each equipped with a version of PGNCS. PGNCS, and specifically its computer, were also the command center for all system inputs from the LM, including the alignment optical telescope, the radar system, the manual translation and rotation device inputs by the astronauts as well as other inputs from the LM systems.

Apollo Command Module primary guidance system components
Apollo Lunar Module primary guidance system components
Apollo Inertial Measurement Unit

PGNCS was developed by the MIT Instrumentation Laboratory under the direction of Charles Stark Draper (the Instrumentation Laboratory was later named after him). The prime contractor for PGNCS and manufacturer of the inertial measurement unit (IMU) was the Delco Division of General Motors. PGNCS consisted of the following components:

  • an inertial measurement unit (IMU)
  • the Apollo Guidance Computer (AGC)
  • resolvers to convert inertial platform angles to signals usable for servo control
  • optical units, one for the CM and a different one for the LM
  • a mechanical frame, called the navigation base (or navbase), to rigidly connect the optical devices and, in the LM, the rendezvous radar to the IMU
  • the AGC software

Versions

Apollo gyroscope (IRIG)
Apollo accelerometer (PIPA)

The CM and LM used the same computer, inertial platform and resolvers. The main difference was the optical unit. The navbase was different for each spacecraft as well, reflecting the differing mounting geometries. The LM's rendezvous radar was also connected to its navbase.

There were two versions of PGNCS—Block I and Block II—corresponding to the two generations of the CM. After the Apollo I fire, which occurred in a Block I CM, NASA decided that no further crewed missions would use Block I, though uncrewed missions did. Major differences between Block I and Block II PGNCS included replacing electromechanical resolvers with an all electronic design and replacing the Block I navbase, which was machined from beryllium, with a frame built out of aluminum tubing filled with polyurethane foam. The Block II navbases were lighter, cheaper, and just as rigid.

Another major difference between Block I and Block II was repairability. An original goal for the Apollo program was for the astronauts to be able to make repairs to the electronics. Accordingly, the Block 1 PNGCS was designed with many identical modules that could be replaced with spares, if necessary, in flight. However high humidity conditions inside the crew compartments and accidents in handling body fluids during the Gemini 7 mission made having unsealed electrical connections undesirable. The repairability goal was eliminated in Block II and all units and electrical connections were sealed.[1] The fatal Apollo 1 fire reenforced this concern.

Components from PGNCS were used by Draper for the U.S. Navy's deep-submergence rescue vehicle (DSRV).[2]

Inertial measurement unit

Apollo IMU

The IMU was gimbaled on three axes. The innermost part, the stable member (SM), was a 6-inch beryllium cube, with three gyroscopes and three accelerometers mounted in it. Feedback loops used signals from the gyroscopes by way of the resolvers to control motors at each axis. This servo system kept the stable member fixed with respect to inertial space. Signals from the accelerometers were then integrated to keep track of the spacecraft's velocity and position. The IMU was derived from the guidance system developed by Draper for the Polaris missile.

Inertial guidance systems are not perfect and Apollo system drifted about one milliradian per hour. Thus it was necessary to realign the inertial platform periodically by sighting on stars.

Optical units

CM space sextant
Apollo CM optical unit

The CM optical unit had a precision sextant (SXT) fixed to the IMU frame that could measure angles between stars and Earth or Moon landmarks or the horizon. It had two lines of sight, 28X magnification and a 1.8º field of view. The optical unit also included a low-magnification wide field of view (60º) scanning telescope (SCT) for star sightings. The optical unit could be used to determine CM position and orientation in space.

Apollo Lunar Module Alinement Optical Telescope (AOT)

The LM instead had an alignment optical telescope (AOT), essentially a periscope. The outer element of the AOT was a sun-shielded prism that could be rotated to one of six fixed positions relative to the LM, in order to cover a large portion of the lunar sky. Each position had a 60º field of view. When rotated, the AOT's position was readable by the AGC; by pointing the reticule at two different stars, the computer could determine the craft's orientation.[3]

The sun shade was added late in the program, in 1967, after tests and modeling determined that the astronauts might not be able to see stars on the lunar surface due to direct sun light or light scattered by near-by parts of the LM impinging on the outside prism. Adding the sun shade also allowed increasing the number of view positions from three to six.[1]:p. 41 ff

AOT sun shade on Apollo 9 Lunar Module

Software

The onboard guidance software used a Kalman filter to merge new data with past position measurements to produce an optimal position estimate for the spacecraft. The key information was a coordinate transformation between the IMU stable member and the reference coordinate system. In the argot of the Apollo program this matrix was known as REFSMMAT (for "Reference to Stable Member Matrix"). There were two reference coordinate system used, depending on the phase of the mission, one centered on Earth and one centered on the Moon.

Despite the word "primary" in its name, PGNCS data was not the main source of navigation information. Tracking data from NASA's Deep Space Network was processed by computers at Mission Control, using least squares algorithms. The position and velocity estimates that resulted were more accurate than those produced by PGNCS. As a result, the astronauts were periodically given state vector updates to enter into the AGC, based on ground data. PGNCS was still essential to maintain spacecraft orientation, to control rockets during maneuvering burns, including lunar landing and take off, and as the prime source of navigation data during planned and unexpected communications outages. PGNCS also provided a check on ground data.

The lunar module had a third means of navigation, the abort guidance system (AGS), built by TRW. This was to be used in the event of failure of PGNCS. The AGS could be used to take off from the Moon, and to rendezvous with the Command Module, but not for landing. During Apollo 13, after the most critical burn near the Moon the AGS was used in place of PGNCS because it required less electrical power and cooling water.

Apollo 11

During the Apollo 11 mission, two PGNCS alarms (1201 "No VAC areas available" and 1202 "Executive alarm, no core sets") were relayed to mission control as the first lunar landing was being attempted on July 20, 1969. The computer system overload was caused by the simultaneous capture of landing radar data and rendezvous radar data. Support staff at Mission control concluded that the alarms could be safely ignored and the landing succeeded.[4][5]

gollark: As I said, if this is somehow a webserver issue, I'm hoping caddy 2 will fix it, so I'm reading the docs to prepare for an upgrade to that.
gollark: Its internal HTTP logs, which I figured out how to get it to dump, do appear to show it doing *something*, but I don't understand them enough to say what.
gollark: The really weird thing is that Firefox didn't actually seem to be *sending* any request or whatever for the websockets. Nothing appears in devtools, wireshark didn't show anything websocket-looking (although I am not very good at using it, I think it was working because it showed the regular HTTP requests), mitmproxy didn't say anything either, and the webserver logs don't show it.
gollark: I've decided to just update caddy and see if that helps, since I am a bit overdue for switching to v2.
gollark: I have some applications sending data over websocket to the browser - mostly JSON. They work in Chrome and Firefox on Android, but not on Firefox on my Linux systems - it just says "failed to establish connection". Specifically, they work if I run them directly on my local machine but not behind my server's reverse proxy.

See also

References

  1. Holley, M. D. (May 1976). "Apollo Experience Report--Guidance And Control Systems: Primary Guidance Navigation And Control System Development, NASA TN D-8287" (PDF). Lyndon B. Johnson Space Center, United States. National Aeronautics and Space Administration.
  2. The Silent War: The Cold War Battle Beneath the Sea, John Pina Craven, Simon and Schuster, 2002, p.120
  3. The Apollo Lunar Module Alignment Optical Telescope, Apollo Lunar Surface Journal
  4. Eyles, Don (2004-02-06), Tales from the Lunar Module Guidance Computer, retrieved 2017-10-01
  5. "Apollo 11 Lunar Surface Journal: Program Alarms". www.hq.nasa.gov. Retrieved 2017-04-16.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.