1
$\begingroup$

In this Question the excellent answer explains from the handbook that the cross pointer input can be either from landing radar or PGNS or AGS.

My question is which mode was choosen during the final phase of landing or which mode was supposed to be choosen by procedure and why so?

Also, was PGNS/AGS was corrected with LDG RADAR ? If so then directly PGNS/AGS mode would have sufficed?

$\endgroup$
3
$\begingroup$

According to the Apollo 14 LM Timeline Book, the MODE SEL switch that selects the source for the pointers is set at two different points.

At LANDING RADAR CHECKOUT, at mission time 106:30, the RATE ERR MON switch is set to LDG RDR/CMPTR and MODE SEL is set to LR, so the cross-pointers are controlled from the landing radar.

Between 108:00 and 108:20, we have UPDATE FROM MSFN -- a data uplink from the ground, presumably updating the spacecraft's computer with the latest and greatest position and velocity information. During this sequence, MODE SEL goes to PGNS; the pointers are controlled by the primary guidance computer.

Powered descent starts at 108:40 with the MODE SEL still in PGNS mode. I don't see any other mentions of MODE SEL in the timeline, but searching OCR'd PDFs can be error prone, so I can't rule out some other mode change in there, but I think nominal landings were done with the cross-pointers driven by PGNS.

In Digital Apollo, I noticed something rather interesting in the discussion of the 1201/1202 errors encountered during the Apollo 11 landing. The notes for those errors in the program alarm "cheat sheet" say:

Watch for other cues, PGNCS condition unknown, DSKY may be locked up, duty cycle may be up to point of missing some functions (nav. last to die) Switch to AGS (follow ERR needles) may help (reduces PGNCS duty cycle signif.)

In other words, when hitting the executive overflow errors that Apollo 11 encountered, it was suggested to switch the cross pointer needles to AGS-driven to lighten the load on the primary computer. No such suggestion was relayed to Armstrong and Aldrin at the time, however; Aldrin noticed the errors seemed to occur when a particular data display was up, so they simply monitored that datum from the ground instead for the remainder of the descent.

| improve this answer | |
$\endgroup$
  • $\begingroup$ so... in the end phase it was inertially propogated state vector for horizontal velocity used by pilot to steer ? $\endgroup$ – Prakhar Nov 17 '19 at 6:15
  • $\begingroup$ @Prakhar I'm guessing the computer continued to integrate data from the radar, but I'm not 100% sure. $\endgroup$ – Russell Borogove Nov 17 '19 at 6:20
  • 2
    $\begingroup$ @Prakhar The landing radar updates the state vector in the computer up until (almost) touchdown, the computer calculates horizontal velocity components from its current state vector and that data is used in the PGNS mode of the cross pointer. $\endgroup$ – indy91 Nov 17 '19 at 10:29
  • 1
    $\begingroup$ The radar experience report also says the computer overloads may have affected the incorporation of the landing radar data into the state vector: "The two questionable data points were probably caused by poor data processing during the LGC overload alarm." $\endgroup$ – Organic Marble Nov 17 '19 at 16:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.