Note:  Telemetry documentation for this specific Lunar Module software version is not (yet) available, most likely due to an unavailable Guidance System Operations Plan (GSOP) for it.  The documentation herein is based on assumptions about the contents of the unavailable GSOP documents, so do not assume that it is perfectly reliable.  Careful examination of the source code for the AGC software version, if available, may provide additional detail in resolving questions; refer particularly to source-code files with names such as: Go directly to word: 10 20 30 40 50 60 70 80 90

1a

I.D. word for this list.  Will contain 777778.

1b

Sync bits.  Will contain 773408.

2,3,4,5,6,7,8

CSM STATE VECTOR and TIME.  The LGC's latest calculated state vector for the CSM in reference coordinates.  The coordinates may be either earth-centered or moon-centered; a zero in bit 12 of flagword 8 (CMOONFLG) indicates earth-centered, a one indicates moon-centered.  Words 2-4 contain the position components X, Y, Z scaled meters/229.  Words 5-7 contain the velocity components X, Y, Z scaled (meters/centisecond)/27.  Word 8 contains the time associated with the state vector scaled centimeters/228, referenced to the computer clock.  The scaling for position, velocity and time is the same whether earth-centered or moon-centered.

9

K-FACTOR.  The ground elapsed time of the zero reference time of the Abort Guidance System (AGS).  It is set only by the AGS Initialization Routine (R47).  Calculated on the first use of R47 and on subsequent calls to R47 if requested by the astronaut.  Scaled centiseconds/228.

10

TALIGN.  Time to which a landing site or LM state vector is referenced for the landing site and nominal IMU alignment orientations during P52 and P57.  Scaled centiseconds/228, referenced to computer clock.

11a

POSTORKU.  Running sum of positive torque commands about control axis U (RCS on-time multiplied by the number of jets used).  POSTORKU will, in time, overflow and subsequently increase once more from zero (overflow does not go into sign bit).  The scaling is such as to preclude more than one overflow per downlink cycle (2 sec) thus making the change from one reading to the next unambiguous.   Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32 (1 jetsecond is defined as 1 jet firing for 1 second).

11b

NEGTORKU.  Running sum (always positive) of negative torque about control axis U.  Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32.

12a

POSTORKV.  Running sum of positive torque about control axis V.  Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32.

12b

NEGTORKV.  Running sum (always positive) of negative torque about control axis V.  Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32.

13a

RR RANGE (Raw Data).  Treated as a 15-bit integer which is multiplied by either 9.38 for the low scale or by 75.04 for the high scale to convert to units of feet.  a 1 in bit 3 of RADMODES indicates high scale.  See page 2-98 for more complete description.

13b

RR RANGE RATE (Raw Data).  Treated as a 15-bit integer.  To convert to units of feet per second the following computation is done:

(15-bit integer - 17000) × (-0.6278)
A negative quantity indicates closing.

14

TIME OF EVENT.  Contains the image of TIME2, TIME1 at the time of the last significant event.  Loaded in burn programs with time of ignition and time of engine cutoff as they occur.  Loaded with abort initiation time in P70 and P71.  Scaled centiseconds/228.

15-20

REFSMMAT.  Six elements of REFSMMAT, in the order R1C1, R1C2, R1C3, R2C1, R2C2, R2C3.  REFSMMAT is the 3 × 3 matrix used to convert from reference to stable member coordinates.  The remaining three components of REFSMMAT may be computed as follows:

R3C1 = (R1C2) (R2C3) - (R1C3) (R2C2)

R3C2 = (R1C3) (R2C1) - (R1C1) (R2C3)

R3C3 = (R1C1) (R2C2) - (R1C2) (R2C1)

where R = Row and C = Column.

Calculated at the end of P51, prior to IMU coarse align in P52 for alignment options 1, 2 and 4, and in P57 for alignment techniques 1 and 4.  Each row is a half-unit vector.

21a

AOT CODE.  Bits 6-1 contain the octal identification number of the celestial body being sighted.

Bits 9-7 contain the Detent Code as follows:

0   
Optical System Calibration Code    
Valid only in R52
1
is AOT Position 1 (left forward)
AZ = -60° EL = 45°
2
is AOT Position 2 (forward)
AZ = 0° EL = 45°
3
is AOT Position 3 (right forward)
AZ = 60° EL = 45°
4
is AOT Position 4 (right rear)
AZ = 120° EL = 45°
5
is AOT Position 5 (rear)
AZ = 180° EL = 45°
6
is AOT Position 6 (left rear)
AZ = -120° EL = 45°
7
Crew Optical Alignment Sight


AOT CODE is the erasable storage for Display Nouns 70 and 71 in the routines AOTMARK (R53), Auto Optics Positioning (R52), and Star Acquisition (R59).  AOTCODE is always equal to the data keyed in by the astronaut under Nouns 70 and 71 except during R59 where the detent code in bits 9-7 is computed to reflect the azimuth position code in R3 under the display V06 N79.

21b

Garbage.

22,23,24

These words are known to vary by Luminary software version

Version
Description
Luminary 1
VGTIGs (X, Y, Z).  Velocity-to-be-gained at ignition.  For external-ΔV type burns this is the input ΔV rotated through half the calculated central angle expected to be covered by the burn.  Calculated once a the beginning of each of P40, P41, and P42.  In reference coordinates, scaled (meters/centisecond)/27.  VGPREV (X, Y, Z) appears in the same location once Average G has been turned on (TIG - 30 seconds).  This is the velocity-to-be-gained used by steering in P40 and P42, and for display in P41.  VGPREV is updated every 2 seconds during the burn.  In reference coordinates.  Scaled (meters/centisecond)/27.
Luminary 1A, 1B, 1C, 1D

LANDING SITE VECTOR (X, Y, Z).  Landing site in moon-fixed coordinates.  "LAND" is initialized from this vector (RLS) at the start of P63.  RLS is recomputed after landing by P68 and is computed by P57 if the landing site determination option is selected.  Otherwise except perhaps by uplink, it does not change.  Scaled meters/227.

25a,25b,26a

LR VELOCITIES (Raw Data).  Landing radar beam velocities (X, Y, Z).  The data readout from the Landing Radar High Speed Counter into LGC input counter 468.  Always contain the last values which were read, i.e., these registers are never initialized.  Each component read once per second during R77.  Each component read once per four seconds during LR option of R04.  Scaled (15-bit integer - 12288.2) × K ft/sec where K = -0.6440 for Vx, K = 1.212 for Vy, and K = -0.8668 for Vz.

26b

LR RANGE (Raw Data).  Landing radar slant range.  The data readout from the LR High Speed Counter into LGC input counter 468.  Always contains the last value read, i.e., this register is never initialized.  Read once per second in R77.  Read once every 4 sec during LR option of R04.  A 15-bit integer which is multiplied by either 5.395 on the high scale or 1.079 on the low scale to convert to units of feet.  A 1 in bit 9 of RADMODES indicates high scale.

27-29

These words are known to vary by Luminary software version.

Version
Description
Luminary 1, 1A
27-28
X789,X789+2. RR SHAFT and TRUNNION BIASES.  The estimate of the RR angle biases; 27 is shaft, 28 is trunnion.  Computed by the Rendezvous Navigation Program.  Initially pad-loaded to 0.  They can oscillate in sign and magnitude.  Calculated during state vector correction in P20 four times per mark (Range, Range-Rate, Trunnion and Shaft incorporations).  Marks are taken about once a minute in P20, so four calculations are made about once a minute when UPDATFLG is set.  They are not calculated if the No Update Flag is set.  Scaled radians/25 if in earth sphere of influence.  Scaled radians/23 if in lunar sphere of influence.  A 0 in bit 11 of flagword 8 (LMOONFLG) indicates earth sphere, a 1 indicates lunar sphere.  These words are updated only in P20, hence they are useful only on the Rendezvous and Prethrust List.
29a,29b
LASTYCMD,LASTXCMD.  RR TRUNNION and SHAFT ERROR COUNTERS.  Rendezvous Radar error counter commands; 79a is trunnion, 79b is shaft.  They are placed in the RR error counters and specify the rate at which the RR antenna is driven.  Values range from +384 to -384 and vary according to the angular error between the present and desired RR positions.  Calculated every 0.5 second in the Radar Designate Routine (DODES) whenever the the LGC is driving the RR antenna which occurs when:

  1. The RR monitor (R25) detects the antenna out of mode limits.
  2. V41 N72 (RR Coarse Align) is operated.
  3. R21 (RR designate) is operated in P20/P22.
  4. R24 (RR Automatic Search) is operated in P20/P22.

A magnitude of 384 corresponds to a rate command of about 10 degrees/second.  The exact rate depends on the characteristics of the motors in the RR gyros.  79a and 79b are each scaled 2-14.
Luminary 1B, 1C, 1D, 1E
VGTIGs (X, Y, Z).  Velocity-to-be-gained at ignition.  For external-ΔV type burns this is the input ΔV rotated through half the calculated central angle expected to be covered by the burn.  Calculated once a the beginning of each of P40, P41, and P42.  In reference coordinates, scaled (meters/centisecond)/27.  VGPREV (X, Y, Z) appears in the same location once Average G has been turned on (TIG - 30 seconds).  This is the velocity-to-be-gained used by steering in P40 and P42, and for display in P41.  VGPREV is updated every 2 seconds during the burn.  In reference coordinates.  Scaled (meters/centisecond)/27.



30a

REDO COUNTER.  Counter for hardware restarts.  Set to zero by keyboard freshstart (Verb 36).  Incremented once per hardware restart by restart program (GO PROG).  Scaled 2-14.

30b,31a,31b

FINAL DESIRED CDUs (X, Y, Z).  The target attitude (desired outer, inner and middle gimbal angles) for all coasting flight automatic maneuvers and for the ISS coarse align loop.  Also, used in the FDAI attitude error display checkout routine (V43).  Computed as inputs to the coasting flight automatic attitude maneuver routine (KALCMANU) and prior to or during R60.  Also computed whenever a coarse alignment is to be made.  The astronaut can load these quantities directly via N22.  The extended verbs V41N20, V43, V49, will request a load of these angles.  These registers are unsigned 15-bit fractions.  The quantities are scaled degrees/360

32a

RSBBQ.  Loaded with the setting of the BBANK and Superbank when a hardware restart occurs.

32b

RSBBQ + 1.  Loaded with the setting of the Q-register when a hardware restart occurs.

33a,33b,34a

CURRENT BODY RATES (X, Y, Z).  Estimated current rates about body axis.  Calculated at the beginning of every DAP cycle every 0.1 sec.  Zeroed at DAP start-up.  Scaled (degrees/sec)/45.  Expected range of ±10 degrees/sec but ±45 degrees/sec possible.

34b

Garbage.

35a,35b,36a

DAP INTERNAL DESIRED CDUs (X, Y, Z).  Outer, inner and middle intermediate desired gimbal angles.  Steering commands to DAP.  Generated during a burn by guidance equations or during an automatic maneuver.  Calculated every 2 secs during a PGNCS controlled burn (i.e., P40, P42).  Updated every 0.1 sec by the DAP (using DELCDUs) during an automatic maneuver (KALCMANU) and also during powered flight.  These registers are unsigned 15-bit fractions.  Scaled degrees/360.

36b

Garbage.

37a,37b,38a

ACTUAL CDUs (X, Y, Z).  The current outer, inner and middle IMU gimbal angles.  Automatically updated by the hardware when the IMU is on.  These registers are unsigned 15-bit fractions.  Scaled degrees/360.

38b

ACTUAL RR TRUNNION CDU.  RR trunnion angle CDU counter.  Defines the RR antenna position (along with shaft angle).  Updated from RR CDUs as trunnion angle changes.  This register is an unsigned 15-bit fraction.  Scaled degrees/360.

39a

FLAGWORD 0.  Bit assignments are as follows:

Bit
Meaning
15
NEED2FLG.  A 1 means display DAP rates on FDAI needles.  A 0 means needles will have either mode 1 or mode 2 attitude error displays.  Set 1 by V60.  Set 0 when V61 or V62 selected.  Also set 0 when R60 selected.
14
JSWITCH.  Bit set 1 to indicate that extrapolation of W-matrix is being carried out in orbital integration routine.  Bit set to 0 to indicate that the state vector extrapolation is being carried out in orbital integration routine.  Bit would remain 0 until bit 1 of flagword 3 becomes 1.
13
MIDFLAG.  Set to 1 in orbital integration when magnitude of conic position vector is greater than the constant RME when earth is primary body and RMM when moon is primary body and set to 0 when magnitude is less than these constants.  In LUMINARY, these constants are set to POSMAX; therefore MIDFLAG should never be set to 1.  If MIDFLAG were set to 1, integration would attempt to include secondary body and solar perturbations in the orbit.  Since position vectors of the moon and sun are needed, and these are not available in LUMINARY, integration would be invalid and possibly disastrous.
12
MOONFLAG.  Set as follows in orbital integration when integrating the stored CSM and LM state vectors:  1 indicates lunar orbit, 0 indicates earth orbit.  Also set to 0 or 1 in integration when switching coordinate centers but this can't be done in LUMINARY because logic is engaged by MIDFLAG = 1.  Also set to 0 (earth-orbit) or 1 (lunar-orbit) in P21, R31, INITVEL, P32 thru P35, P72 thru P75 when specifying a state vector to integrate and in P27, P76 when using integration subroutines to store modified state vectors for systems use.
11
P21FLAG.  Bit set to 1 when base vectors have been saved and indicates that integration is to be performed from base vectors which were computed during previous integration.  Bit set to 0 when P21 is established and on restarts.  Setting the bit to 0 means that the base vectors have not been computed; integration must operate to compute base vectors for use in subsequent passes.  Cleared in all software and hardware restarts.
10
FSPASFLG.  Bit is set to 1 during P22 at the point in the designate routine (R21) when the line of sight is not in mode 2 coverage (the Predesignate routine is necessary).  A 1 indicates the first pass through the Predesignate routine.  Bit is reset to 0 when the line of sight is inside mode 2 coverage; another line of sight computation is done before continuous designation starts.  A 0 indicates that it is not the first pass through the Predesignate routine.
9
P25FLAG.  A 1 means P25 is operating.  A 0 means P25 is not operating.  Set to 1 at the beginning of P25.  Set to 0 by P63, V56, Terminate Tracking, or by selection of P00.
8
IMUSE.  Set to 1 by P51 and R02.  Reset to 0 by P00, P06, IMU performance tests, Extended Verb 56 (if tracking is operating), and all new program selections unless either RNDVZFLG or P25FLAG is 1. Bit is examined by R47 and by the T4RUPT turn-on sequence to determine whether to do IMU CDU Zero.  If the bit is 1, CDU Zero is bypassed.  The effect of this is that CDU Zero is not done in AGS Initialization or after a restart if IMUSE is 1.
7
RNDVZFLG.  A 1 means P20 or P22 is operating.  A 0 means P20 or P22 is not operating.  Set to 1 at the beginning of P20 or P22.  Set to 0 by V56, Terminate Tracking, or by selection of P00.  Set to 0 by the ISS Service Routines in T4RUPT if a change in the ISS operate discrete is detected.  Set to 0 by P06-Standby Program, P12, and P63.
6
RRNBSW.  A 1 means RR target is in nav-base coordinates.  A 0 means RR target is in stable-member coordinates.  Set to 1 by V41 RR Coarse Align.  Set to 0 by LPS20.1 (subroutine of P20/P22).  Set to 0 by Stable Member Designate Subroutine (used by R21 and R24 in P20/P22).
5
LOKONSW.  A 1 means radar lock-on is desired in RR Designate.  A 0 means radar lock-on is not desired in RR Designate.  Set to 1 by R21 RR Designate Routine of P20/P22.  Set to 1 by V41 RR Coarse Align if the Lockon Option is selected.  Set 0 by R26.  Set 0 by V41 RR Coarse Align if the Continuous Designate Option is selected.
4
NEEDLFLG.  Set to 1 by Verb 62 or R60 and reset to 0 by Verb 61 (or a fresh start).  Used to control the information presented on the FDAI attitude error needles by the LM DAP.  If bit is 1, the "total attitude error" is displayed, defined as THETAD-CDU (THETAD is the Noun 22 cells) rotated into pilot axes (P, Q, R).  The crew may use this display as a "fly to" indicator when performing manual maneuvers to the attitude specified by the gimbal angles in Noun 22.  If the bit is 0, the "autopilot following error" is displayed.  This is the same error which is used in controlling the firing of the RCS jets and is provided as a monitor of the LM DAP.
3
FREEFLAG.  Used as a temporary flag to control the internal logic of the following subroutines:  R51, R54, P51, P57, and LSPOS.
2
R10FLAG.  Bit is set to 1 during ascent (in P12, P70, and P71) to indicate that R10 only outputs data to altitude and altitude rate meters.  Bit reset to 0 (initially and during descent) to indicate that R10 outputs data to the Forward and Lateral velocity cross-pointers, in addition to the altitude and altitude rate meters.  Bit is checked in R10 (Landing Analog Displays) in order to determine the type of output to display.
1
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
OLDESFLG.  Set to 1 when R29 gyro command loop requested, and set to 0 when not requested.
Luminary 1D, 1E
P66PROFL.  Set to 1 when P66 is entered for the first time (in R13) as a directive to continue P66 horizontal nulling.  It is reset to 0 when the astronaut proceeds on a flashing V06 N60 after touchdown, the 0 specifying a stop to P66 horizontal nulling.  It is tested in P66 after horizontal commands have been calculated, but before commands are issued.

39b

FLAGWORD 1.  Bit assignments are as follows:

Bit
Meaning
15
NJETSFLG.  Used for thrust determination in P41.  Set in R03 (entered via V48) as follows:  set to 1 if bit 11 of DAPDATR1 is 0, indicating that 2-jet X translation is specified; set to 0 if bit 11 of DAPDATR1 is 1, indicating 4-jet X translation.
14
DIDFLAG.  Bit is set to 1 in R10 to indicate that R10 has performed initialization sequence on the first pass, and inertial data is available for displays on subsequent passes thru R10.  Bit is reset to 0 in R10, FRESH START, and RESTART to force R10 to perform initialization sequence if the mode select switch is set at PGNCS.  Bit will remain at 0 when inertial data displays are not desired.  Bit is examined when the mode select switch is set at PGNCS, indicating that the astronaut requests inertial data displays.
13
ERADFLAG.  Used in lat-long subroutine.  For the earth, a 1 means compute Fischer ellipsoid radius; a 0 means use fixed radius.  For the moon, a 1 means use fixed radius; a 0 means use RLS (lunar land site radius) for lunar radius.  Set to 0 or 1 by routines that use lat-long subroutine.
12
RODFLAG.  Bit is set to 1 on the first pass thru P66 to designate continuation of algorithm without reinitialization.  A 1 indicates that the rate-of-descent mode is in progress.  If in P66, a 0 indicates that there has been a restart.  Bit is set to 1 to check for restarts and fresh start.  Bit is set to 1 only when the vertical guidance (landing phase) is in effect, the SCSMODE is in attitude hold, and the ROD switch has been activated.
11
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
Garbage or Spare.
Luminary 1D, 1E
NOTERFLG.  Set 1 by V68 and also entrance to P66 (in R13) in order to bypass the terrain model computations.  It is reset to 0 in P63 and by V36 meaning that terrain model computations are to be performed.  The bit is checked each guidance pass (every 2 sec.) in Servicer.
10
R61FLAG.  Bit is set to 1 by UPFLAG at the start of R61, to indicate that R61 is in operation.  Bit is reset to 0 by DOWNFLAG at the start of R65, to indicate that R65 is in operation.  Bit is tested during R61, R65 to determine exit from these routines.
9
Not used.
8
VEHUPFLG.  A 1 means CSM state vector to be corrected by Navigation.  A 0 means LM state vector to be corrected by Navigation.  Set to 0 at the beginning of P20.  Set to 0 by V80 Update LM.  Set to 1 by V81 Update CSM.  Set to 1 at the beginning of P22.
7
UPDATFLG.  A 1 means updating of the state vector by Navigation is allowed.  A 0 means updating of the state vector by Navigation is not allowed.  Set to 1 at the beginning of P20 or P22.  Set to 0 by V37 selection of a program other than P20 or P22.  Set to 1 by V37 selection of P20 or P22 if either is already operating.  Set to 0 by V56 Terminate Tracking.  Also set 0 by V34E response to a P20 display (except V06N49).  Set to 1 by Rendezvous Targeting Programs (P32, P33, P34, P35 and P72 thru P75) during the loading of input data and set to 0 by these programs when starting the targeting computations.
6
NOUPFLAG.  A 1 means neither the CM nor the LM state vector may be updated by Navigation.  A 0 means either state vector may be updated (see bit 8 of this flagword).  Set to 1 by V95 Inhibit State Vector Updating.  Set to 0 by V80 Update LM V81 Update CSM.
5
TRACKFLG.  A 1 means tracking of CSM allowed.  A 0 means tracking of CSM not allowed.  Set to 1 at the beginning of P20 or P22.  Set to 0 by V37 selection of a program other than P20 or P22.  Set to 0 (if 1) by V56 Terminate Tracking.  Also set 0 by V34E response to a P20 display (except V06N49).  Set to 1 by V37 selection of P20, P22, or P25, unless one of these is already running.  Set to 1 by all of the rendezvous targeting programs (P32, P33, P34, P35, and P72 thru P76) at the beginning of the targeting program.  Set to 0 by the IMU mode switching routines when the IMU is put in the coarse align mode.
4
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Garbage or Spare.
Luminary 1E
FRSTIME.  Bit is set to 1 during P22 when the line of sight is not in Rendezvous Radar Mode 2 coverage (the Predesignate Routine, R26, is necessary).  A 1 indicates that LOS has not yet been found inside Mode 2 coverage.  Bit is reset to 0 by R26 when line of sight is inside Mode 2 coverage; another line of sight computation is done before continuous designation starts.  A 0 indicates that the LOS has been found to be inside Mode 2 coverage by R26.  Tested by R26.
3
SLOPESW.  Set to 1 at the start of the LAMBERT routine, and reset to 0 at the end of the first pass through the internal LAMBERT iteration process (specifically, inside the ITERATOR subroutine, which calculates the increment to be added to the independent variable for use on the next pass).  The bit controls the type of computation performed in the ITERATOR subroutine.  This bit is equivalent to the switch f3 of Section 5.5 of the GSOP.
2
GUESSW.  Set to 1 to indicate to the LAMBERT routine than an initial guess of the independent variable used in the internal LAMBERT iteration process is not available, thus forcing LAMBERT to start iterating from the mid-point of the range of the independent variable.  The bit is set to  0 to indicate to LAMBERT than an initial guess is available; this will in general greatly reduce the number of iterations and the computation time inside LAMBERT.  The Initial Velocity Subroutine INITVEL always sets the bit to 0 internally immediately after it calls LAMBERT.  The bit is also set to 1 by INITVEL, but only when INITVEL is entered via a special entrance.  This special entrance is used only by the Pre-TPI Maneuver Program P-34 or P74, the Pre-TPM Maneuver Program P-35 or P75, and the Lambert Aim-Point Maneuver Pre-Thrust Computation Routine.  This bit is equivalent to the switch f1 of Section 5.5 of the GSOP.
1
Not used.

40a

FLAGWORD 2.  Bit assignments are as follows:

Bit
Meaning
15
DRIFTFLG.  Set to 1 to enable free-flight gyro drift compensation and set to 0 to disable compensation.  Set to 0 if IMU caged and prior to the IMU being coarse aligned and when Average-G program is started.  Set 0 for pulse torquing option of P52.  Set to 1 after IMU coarse alignment and upon termination of Average-G.
14
SRCHOPTN.  A 1 means R24 RR Automatic Search Routine used to lock on to CSM.  A 0 means R24 not used to lock on.  Set to 0 at beginning of P20 or P22.  Set to 1 at beginning of R24.  Set to 0 (if 1) in P20 or P22 before going to R22 RR Data Read Routine.
13
ACMODFLG.  A 1 means Manual Radar Acquisition Mode (R23) used to lock-on.  A 0 means Manual Radar Acquisition Mode (R23) not used to lock-on.  Set to 0 at beginning of P20 or P22.  Set to 1 upon return from R23 to P20 or P22 before going to R22 RR Data Read Routine.
12
LOSCMFLG.  A 1 means line-of-sight being computed during Radar Designate.  A 0 means line-of-sight not being computed.  Set to 0 when RR data good discrete (indicating lock-on) is received by the Radar Designate Routine.  Set to 1 at the start of R21 RR Designate Routine.  Set to 0 at the end of R21 when lock-on has been achieved.  Set to 0 by V41N72 Designate, R24 Search Routine, and at the beginning of P20 or P22.  Set to 1 by R29 when a new line-of-sight is being computed.
11
STEERSW.  Bit is set to 1 in SERVICER (P40 or P42) to indicate that cross-product steering computations are to be performed and the result loaded into communication cells with the DAP (if the MODE SELECT SWITCH is in AUTO).  Bit is set to 0 when time-to-go (for a closed-loop guided burn, including predicted thrust decay) first drops below 4 seconds, or if bit 7 of FLAGWRD7 = 0 and the output of the accelerometers is below about 0.12 m/sec (CSM-docked), 0.36 m/sec (DPS), or 3.08 m/sec (APS) (for the 2-second interval).  Bit is set to 1 if the accelerometer output goes above these thresholds (if bit 7 FLAGWRD7 = 0).  *If bit is 0, only the required velocity is updated (no derivation of time-to-go or steering commands are performed).  Bit is set to 1 in SERVICER (P12, P63 thru P66) but it is not looked at in P12, P66, and P70/P71.  Set 0 in SERVICER in P12 and descent programs.
10
Not used.
9
IMPULSW.  Bit set to 1 when a countdown to initiate engine (DPS or APS) cutoff is required (i.e. the value of time-to-go is known and is not to be updated further).  The bit is set to 0 unconditionally at the start of S40.13 (entered about 5 seconds before nominal ignition, and comprising the "short burn test and time-to-go predictor" routine), and is then set to 1 if it is concluded that the predicted burn duration is to be less than 6 seconds.  (For DPS burns, a thrust level of approximately 10% is used.)  The bit is set to 1 when time-to-go (for "long" burns) is less than 4 seconds; it is reset to 0 after being sensed (when the action to perform the engine cutoff has been initiated, so as to avoid double initiation).
8
XDELVFLG.  Set to 1 if an External Delta V burn is to be performed.  Set to 0 if a Lambert burn is required.  Set to 1 in P30 before N42 display.  Set 1 by P72 and P73.  For P34, P35, P74, and P75 — set to 0 in subroutine S34/35.2.  For P32/P72 and P33/P73 set to 1 in subroutine ADVANCE.
7
ETPIFLAG.  A 1 means elevation angle supplied for P34, P74-compute TPI.  A 0 means no elevation angle supplied for P34, P74-compute ELEV.  Set to 0 initially in P34, P74.  After ELEV has been input (V06N55), the bit is set to 1 if the ELEV input is non-zero.
6
FINALFLG.  A 1 means last pass through rendezvous program computation.  A 0 means interim pass through rendezvous program computation.  Set to 0 by subroutine SELECTMU which is called at the start of P32 thru P35, and P72 thru P75 to perform initialization.  Bit is set to 1 by P30.  Set to 1 by subroutine VN1645 (which is called to perform calculations and display Noun 45 data) upon receipt of proceed to Noun 45 if FINALFLG not already set.
5
AVFLAG.  Set to 1 if LM is active vehicle, set to 0 if CSM is active vehicle.  Set to 1 in subroutine AVFLAGA which is called at the start of P32, P33, P34 and P35 to indicate that the LM is the active vehicle.  Set to 1 in subroutine S40.9 and program P42.  Set to 0 in subroutine AVFLAGP which is called at the start of P72, P73, P74 and P75.
4
PFRATFLG.  Set to 1 if an IMU orientation matrix has been stored for the preferred IMU alignment option.  Set to 1 in P40, P41, and P42 after computation of the "preferred IMU orientation" for engine ignition.  Bit is reset to 0 in P52 after completion of coarse align and gyro torque coarse align, and at the end of re-align routine R51.
3
CALCMAN3.  Set to 1 by the attitude maneuver routine (KALCMANU) to indicate that no gimbal lock avoidance (in going from the initial to final spacecraft attitude) is required.  Since the checks for intermediate gimbal lock as well as the gimbal lock avoidance feature have been removed, the bit should be 1 after the first maneuver computation and remain so (the final middle gimbal angle, THETAD+2 is checked and must be less than about 70° for the maneuver to be carried out).
2
CALCMAN2.  A 1 means perform maneuver starting procedure (in KALCMANU).  A 0 means bypass starting procedure.  Set to 1 at the end of a large attitude calculation of maneuver parameters and reset after some computations concerning initial conditions for generation of the commands have been completed.  Bit signifies that first iteration through the command generation equations is being performed; depending on phasing of the telemetry output with respect to the guidance computations, the 1 setting may or may not be observed on the downlink.
1
NODOFLAG.  Set to 1 by R47, P76, P06, and P00 integration to inhibit selection of any new program except P00.  Attempted selection of a new program other than P00 when the bit is 1 results in a program alarm (code 1520).  Reset to 0 by P00, P76 and R47 when they are completed and by P06 when recovering from standby.  Reset 0 by POODOO routine.

40b

FLAGWORD 3.  Bit assignments are as follows:

Bit
Meaning
15
POOHFLAG.  Set to 1 in STATINIT 1 as P00 integration is started to  bypass backwards integration and perform check for 4 time-step criterion while P00 integration loop is going.  Set to 0 in V37 logic.
14
GLOKFAIL.  Set to 1 when CALCGA detects gimbal lock (alarm 401 occurs at the same time bit is set).  Tested in IMU performance tests; if 1, PIPA test is done and GLOKFAIL is reset to 0.  Also reset in R00.
13
REFSMFLG.  Set to 1 if a meaningful REFSMMAT, reference to stable member matrix, is available, i.e. the alignment of the IMU is known in inertial (reference coordinate) space.  Set to 1 after computation of REFSMMAT in the IMU orientation determination routine P51.  Reset to 0 in the coarse align routine R50 and set to 1 on completion of R50 and on completion of gyro torque coarse align, after desired orientation is stored in REFSMMAT.  Reset to 0 in gravity vector determination routine in P57.  Reset to 0 in coarse align routine IMUCOARS.  Set to 1 after desired orientation is stored in REFSMMAT after alignment is completed in P57.
12
LUNAFLAG.  Used in lat-long subroutine.  A 1 means lunar lat-long.  A 0 means earth lat-long.  Set to 0 or 1 by routines that call lat-long subroutine.
11
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
NOR29FLG.  Bit is set by FRESH START, and when the Servicer routine terminates.  A 1 indicates that R29 is not allowed.  Bit is reset to 0 by P12 Ascent Guidance.  A 0 indicates that R29 is allowed.  Bit is tested during the RR read cycle of R29 and during software restart (V37).  Bit is tested by R04 and R77 to determine if another program/routine is using the radar.
Luminary 1D, 1E
NODOP07.  Bit can be set to 1 by ground uplink prior to liftoff.  It is also set to 1 by V37.  Tested by V92 which gives the operator error if the bit is set.  Tested in UPRUPT which maintains erasable sum of key codes if the bit is 0.  (NOTE:  this bit is not cleared by FRESH START).
10
VFLAG.  Used in automatic star selection routine (R56) during IMU alignment program (P52).  Set to 1 to indicate that a pair of stars are not in the AOT field-of-view.  Set to 0 if pair of stars found.  Initially set to 1 at beginning of R56 and is used temporarily for program control purposes.
9
In all Luminary software versions, this bit has the following interpretation:  R04FLAG.  Set to 1 by Verb 63 entry to indicate R04 is running and set to 0 at the end of R04.  Set to 0 by P20 or P22 selection.  Set to 0 in R00 (V37).

However, in Luminary 1, 1A, 1B, and 1C, it also has an additional secondary interpretation:  READRFLG. Bit is set to 1 by R29 when RR lock-on has been achieved and the RR read cycle is starting.  A 1 indicates that R29 is reading RR data.  Bit is reset to 0 by R29 when exiting the RR read cycle because of a bad reading or the RR not in LGC mode.  Bit is reset to 0 by software restart (V37), FRESH START, and hardware restart.  A 0 indicates that R29 is not reading RR data.  Bit is tested by the RR read cycle of R29 to determine if radar read is allowed.
8
PRECIFLG.  Set to 1 in the integration routine on calls to CSMPREC, LEMPREC, INTEGRVS, and in P00 when integrating LM.  Set to 0 when completing integration and in P00 when integrating CSM.  PRECIFLG = 0 engages integral time step logic in integration when major mode is 00.
7
CULTFLAG.  A 1 means star occulted.  A 0 means star not occulted.  Used in automatic star selection routine (R56) during the IMU alignment program (P52).  Set to 1 to indicate that the particular star being checked lies too close to the computed position of the Sun, Earth, or Moon.
6
ORBWFLAG.  Not used.  Bit is not set to 1 in LUMINARY.
5
STATEFLG.  Set to 1 if the permanent state vector is to be updated by orbital integration.  Bit is checked after completion of integration (either CSM or LM) and, if it is 1, it is reset to 0 and the appropriate loading of permanent and downlink state vectors (either CSM or LM) is accomplished.  Also set to 0 after V96 if QUITFLAG is 1.  Set 0 by POODOO routine.  Set to 1 if W-matrix integration overflows.  Set to 1 for periodic integration in P00 (LM and CSM) and to 0 if P00 integration not to be done (QUITFLAG = 1).  Set to 1 in P22 and P20 for integration to mark time and to cause permanent integration on initial operation of P20 and P22.
4
INTYPFLG.  Set to 1 if conic extrapolation to be done in orbital integration, set to 0 for precision extrapolation.
3
VINTFLAG.  Set to 1 if CSM state vector to be integrated; set to 0 if LM state vector to be integrated.  Set internally in integration on calls via CSMPREC (conic), LEMPREC (conic) and by callers of INTEGRV and INTEGRVS.
2
D6OR9FLG.  Used by orbital integration for W-Matrix integration: if bit is 1, 9 × 9 matrix is integrated; if bit is 0, 6 × 6 matrix is integrated.  Set to 0 or 1 by P00 periodic integration, P20, P22 and Average-G to coasting flight.
1
DIMOFLAG.  Used by orbital integration for W-Matrix integration:  if bit is 1, W-Matrix is to be integrated; if bit is 0, no W-Matrix integration is to be done.  Set to 0 or 1 by P00 periodic integration, P20, P22 and Average-G to coasting flight.

41a

FLAGWORD 4.  Bit assignments are as follows:

Bit
Meaning
15
MRKIDFLG. Set to 1 if a mark/extended verb display is waiting for a response: it signifies that a display of this type is in the "ENDIDLE" routine of the DSKY package ("pinball").
14
PRIODFLG. Set to 1 if a priority display is waiting for a response.  It signifies that a display of this type is in the "ENDIDLE" routine of the DSKY package.
13
NRMIDFLG.  Set to 1 if a normal display (most of the displays in the program are in this category) is waiting for a response: it signifies that a display of this type is in the "ENDIDLE" routine of the DSKY package.
12
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
PDSPFLAG.  Set to 1 to indicate that a priority display status exists.  This will lock out mark displays and normal displays.
Luminary 1E
Checked by the display routines, but remains 0 throughout the mission.
11
MWAITFLG.  Bit included in logic assignments to permit function similar to bit 10 to be applied to mark/extended verb displays.  Bit is set to 1 if a mark/extended verb display is waiting to be initiated.  Set to 1 if a priority display is presently on the DSKY.  Bit is used in case a priority display has been generated after an extended verb has passed the lockout check, but before corresponding verb display.
10
NWAITFLG.  Set to 1 if a normal display is waiting to be initiated (e.g. program attempts to initiate a normal display when an extended verb or mark display is occupying the DSKY).  Helps give DSKY sequence of crew-initiated display, crew-initiated monitor display, priority display, interrupted mark/extended verb display, interrupted normal display, and waiting normal display.
9
MRKNVFLG.  Set to 1 if a mark/extended verb display attempt found the display system busy (due to crew or uplink use for a display, including an externally initiated monitor display).  Bit reset after appropriate display initiated (following key release response).
8
NRMNVFLG. Set to 1 if a normal display attempt found the display system busy (cf. bit 9).
7
PRONVFLG.  Set to 1 if a priority display attempt found the display system busy (cf. bit 9).
6
PINBRFLG.  Set to 1 if it is concluded that "interference" with the internally generated display has taken place (e.g. an enter verb was used but the associated noun was not that requested by the program when the internally generated display was produced), or if a termination for an extended verb/mark routine is performed with bit 14 or bit 13 of this word = 1.  Bit reset to 0 upon successful conclusion of a priority or normal display after having been used to bypass internal checks that otherwise would cause a program abort.
5
MRUPTFLG.  Set to 1 if a mark/extended verb display or display attempt has been interrupted by a priority display.
4
NRUPTFLG.  Set to 1 if a normal display or display attempt has been interrupted by a priority display or by a mark/extended verb display.
3
MKOVFLAG.  Set to 1 briefly if a mark/extended verb display is to interrupt a normal display (used to control internal program branching, whereupon it is reset to 0).
2
Not used.
1
XDSPFLAG.  Set to 1 to indicate that a mark display status exists.  This will lock out normal displays.

41b

FLAGWORD 5.  Bit assignments are as follows:

Bit
Meaning
15
DSKYFLAG.  A 1 means displays sent to DSKY.  A 0 means no displays sent to DSKY.  Set to 1 (if 0) by subroutine of the Keyrupt routine.  Subroutine of T4RUPT program branches according to DSKYFLAG setting.
14
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
PDSPFLAG.  Set to 1 by R61 and R65, tested by R60 so that V50N18 display will be a priority display, if called by P20 or P25.  Set to 0 by R61 and R65.
13
SNUFFER.  Bit is set to 1 to inhibit RCS control about the U and V axes during unstaged powered flight.  Set to 0 by Verb 75.  Set to 1 by Verb 65.
12
NOTHROTL.  Bit set to 0 in P40 to indicate that the burn will last longer than 95 seconds at approximately 10% thrust and that the engine should be throttled to maximum in the number of centiseconds after ignition indicated by the contents of ZOOMTIME.  Bit set to 1 unconditionally in S40.13 (time-to-go predictor) and then reset to 0 if the predicted burn duration at 10% thrust is greater than 95 seconds.  Bit set to 0 in P63.
11
R77FLAG.  Bit is set to 1 at the start of R77 (in response to V78), if R77 operation is permissible.  Bit is reset to 0 at the end of R77 (in response to V79), and by FRESH START (V36).  Also set 0 by V37/software restarts or hardware restart.  Bit is checked in the RADAREAD routine: if bit is a 1 (R77 in operation), no checks are made for data fails.  Bit is checked in RADSAMP (Radar Sampling Loop); if bit is a 1, the portion of coding particular to R04 is bypassed.  Bit is checked at entry to both R04 and R77: if either is selected while the bit is set to 1, an operator error will be indicated.  Bit is checked at entry to V40N72, V41N72, and V59: if any one of these extended verbs is called while the bit is set to 1, an operator error will be indicated.
10
RNGSCFLG.  A 1 means a change has occurred in the RR range scale discrete while reading the range.  A 0 means no change has occurred.  Set to 0 at the beginning of each RR Read sequence in R22 RR Data Read Routine.  Set to 1 by the Radar Interrupt Processor if the range scale discrete changes while reading the range.
9
DMENFLG.  Set to 1 if the dimension of the W-Matrix is 9 for measurement incorporation.  Set to 0 if the dimension of the W-Matrix is 6 for measurement incorporation.  Set to 1 by the Rendezvous Navigation Routine.
8
ZOOMFLAG.  Set 1 at throttle up to indicate throttle up and to start guidance.  Reset 0 at TIG-5 to prepare for throttle up.  Tested at start of landing guidance equations: if 0 do N63 display only; if 1 do landing guidance.
7
ENGONFLG.  Bit set to 1 just after the DPS or APS engine is turned on (bit 13 of channel 11 set to 1 and bit 14 of channel set to 0), and reset to 0 when the engine is turned off (bit 14 set 1 and bit 13 set to 0 in channel 11).  This happens in P12, P40, P42, P70, and P71.  Bit is set to 1 in P63 and reset to 0 in P68.  Bit is used when a restart occurs to determine the proper setting for the channel bits.  Engine is turned off following ENTER response to V97.
6
3AXISFLG.  A 1 means maneuver specified by three gimbal angles (Noun 22).  A 0 means maneuver specified by two vectors.  Set to 1 prior to entering R60 if the attitude maneuver to be made is specified by three angles (Noun 22).  If it is 0, the attitude is specified by two vectors, the body fix vector (SCAXIS) and the direction in which this is to be pointed (POINTVSM).  Another routine, VECPOINT, is used to compute the corresponding desired gimbal angles (Noun 22).  Reset to 0 before exit from R60.  Most calls to R60 require a VECPOINT solution (bit = 0).  V49 (R62) uses the three gimbal angle option (bit = 1).
5
AORBSFLG.  A 1 means P-Axis couples 7, 15 and 8, 16 used.  A 0 means P-Axis couples 4, 12 and 3, 11 used.
4
NORRMON.  Set to 1 if the gimbal monitor function of the RR Monitor Routine, R25, is disabled; set to 0 if enabled.  Set to 0 at the beginning of P20/P22.  Set to 1 at the beginning of RR Manual Acquisition Routine (R23); set to 0 when exiting R23.  Set 1 by R26.  Set to 1 by V41 RR Coarse Align if the No Lockon Option is chosen.  Set to 0 by V44 Terminate Coarse Align Continuous Designate.  Set 0 by hardware/software restart or V37.
3
SOLNSW.  Set to 1 by the LAMBERT routine if the routine could not accurately solve the problem with which it was called (i.e., if sufficient convergence was not achieved to the specified transfer time, or if the subtended true anomaly difference between the two input position vectors was less than about 1/2 minute of arc).  Reset to 0 by LAMBERT if a successful LAMBERT solution was obtained.  Set to 1 by the TIME-RADIUS Routine if this routine was called with an orbit having an eccentricity less than about 0.000004, and reset to 0 if the eccentricity was greater than this value (regardless of what the specified terminal radius is, and regardless of whether this radius could be reached conically from the input state vector).  Thus, for TIME-RADIUS Routine, the resetting of this bit to 0 does not necessarily imply a successful TIME-RADIUS solution.  This bit is never tested by any of the mission programs.  This bit is equivalent to the switches f5 and f9 of Section 5.5 of the GSOP.  These two switches are represented by the same bit in the AGC.
2
MGLVFLAG.  A 1 means local vertical coordinates computed.  A 0 means middle gimbal angle computed.  Set to 0 by subroutine SETMGA after computation of the middle gimbal angle.  Set to 1 by subroutine GET.LVC after computation of local vertical coordinates.
1
RENDWFLG.  Set to 1 to indicate that the W-Matrix is valid and should not be re-diagonalized in navigation (P20 or P22), set to 0 to indicate W-Matrix is invalid.  Set to 1 in P20 or P22, after initializing the W-Matrix when state vector correction is being done and RENDWFLG is initially set to 0.  Set to 0 when integration of the W-Matrix overflows.  Set to  0 by V93.  Bit is reset to 0 by V67 if new W-Matrix initialization values have been loaded by V67.  Set to 0 when state vectors are uplinked by P27.  Set 0 in P12.  Used in P00 periodic state vector update, powered flight to coasting flight transition routine (AVETOMID) and P20 or P22 to determine if W-Matrix should be integrated to maintain synchronization of state vectors and W-Matrix.

42a

FLAGWORD 6.  Bit assignments are as follows:

Bit
Meaning
15
S32.1F1.  Used in P32, P72 to terminate iteration if ΔVCSI exceeds 1000 ft/sec twice during the iteration.  Set to 0 at start of each iteration loop.  Set to 1 if |ΔVCSI|>1000 ft/sec and subsequent test of bit in case |ΔVCSI|>1000 ft/sec will terminate iterative loop.
14
S32.1F2.  Controls first step size of iterative loop to establish two points for Newton-Raphson iteration in P32, P72.  Set to 1 at start of each iterative loop.  Set to 0 after first step.
13-12
S32.1F3A and S32.1F3B.  Control setting of alarm codes during first iterative loop and control the 50 ft/sec steps utilized to establish the starting point of the second iterative loop in P32, P72.  Bits set (0, 1) at start of first iterative loop to allow setting of the alarm codes.  Set (0, 0) at start of second iterative loop until after first 50 ft/sec step is taken, when set (1, 1).  Set (1, 0) after the angular error undergoes a sign change.
11
Not used.
10
GMBDRVSW.  Bit used in "TRIMGIMB", a subroutine called by R03 (entered via Verb 48) to indicate that the trim gimbal has been driven to the correct position in either pitch or roll (depending on which gets finished first).  Bit is unconditionally set to 0 at start of "TRIMGIMB" and is checked at the conclusion of the roll drive task and the pitch drive task; if the bit is 0 (indicating that the other task has not been completed yet) it is set to 1 and the current task ended; if it is already 1 (indicating that the other task has already finished) a return to routine 03 is initiated (via a NOVAC job call) and the task ended.
9
Not used.
8
MUNFLAG.  Bit is set to 1 at entry to P12 and P63.  Bit is reset to 0 at the termination of SERVICER.  Bit is checked by R25: if both AVEGFLAG and MUNFLAG are set to 1, R25 exists without checking RR gimbal angles.  Bit is checked by SERVIDLE (the routine executed if a POODOO abort occurs while SERVICER is running): if bit is set to 1, restart group 2 is left alone; otherwise it is inactivated.  Bit is checked by READACCS: if bit is set to 1, R09 is initiated; otherwise it is bypassed.  Bit is checked by NORMLIZE (which is called by PREREAD to initialize state vectors for SERVICER): if bit is set to 1, MUNRVG is initialized; otherwise CALCRVG is initialized.  *Bit is checked by SERVICER: if bit is set to 1 (either P12, P63, P64, P66, P70 or P71 running), the average-g routine MUNRVG is called; otherwise (either P40, P41, P42 or P47 running) the average-g routine CALCRVG is called.  Bit is checked by BURNBABY (Master Ignition routine): if bit is set to 1, CSMPREC is called prior to calling R41; otherwise it is omitted.  Bit is reset to 0 by V37.
7
Not used.
6
REDFLAG.  Bit is set to 1 by "proceed" response to V06N64 in P64 to enable landing site redesignation capability.  Bit is reset to 0 at the start of P63, P64 as initialization.  Set 0 in P64 if TREDES = 0.  Bit is tested by P64 display routine to determine whether to flash V06N64, and by redesignation logic to determine whether to allow redesignations.
5
Not used.
4
Not used.
3
NTARGFLG.  A 1 means astronaut did overwrite delta velocity.  A 0 means astronaut did not overwrite delta velocity.  Set to 0 in subroutine S34/35.5 (used by P34, P35, P74, and P75) initially before displaying Noun 81.  If the values for Noun 81 are changed by the astronaut, NTARGFLG is set 1 after a PROCEED response, and the new target vector is computed based on the loaded Delta V (LV).
2
AUXFLAG.  Bit is set to 1 by SERVICER whenever the delta-V monitor is bypassed.  When the delta-V monitor detects that the bit is a 1, the monitor knows that it must be on the first pass; the monitor then bypasses further activity and resets the bit to 0.  A 0 indicates that the delta-V monitor is on the second or later pass and can perform its normal functions.  The bit is used only by the delta-V monitor as a one-pass delay mechanism.
1
ATTFLAG.  Bit is set to 1 by REFMF routine during the Lunar Surface Alignment Program P57 if the REFSMMAT flag is set 1 and the Post Lunar Landing Program P68, after LM Y and Z axis vectors are calculated in moon-fixed coordinates and stored in YNBSAV and ZNBSAV.  Bit is reset to 0 by a FRESH START.  If align technique 0 or 1 is selected, alarm 701 will be displayed if bit is zero and REFSMMAT is not available.  If align technique 2 or 3 is selected, the INITALGN flag is clear and the alignment continues.  Bit is tested with each P57 alignment.

42b

FLAGWORD 7.  Bit assignments are as follows:

Bit
Meaning
15
ITSWICH.  A 1 means a solution of TPI time has not yet been reached.  A 0 means a solution for TPI time has been reached.  Bit is reset to 0 in P34, P74 if the TPI time is given and the elevation angle is to be computed.  Bit is set to 1 in P33, P34, P73, and P74 when the elevation angle is given and TPI time is to be computed.  Bit is tested at SWCHCLR: if 1, it is immediately set to 0 and control is transferred to INTLOOP where the final solution for TPI time is reached; if 0, then either the TPI time or the elevation angle is displayed depending on the setting of ETPIFLAG.  ITSWICH also test at TESTY: if 1, the program looking for a solution for TPI time; if 0, the computed elevation angle is stored.
14
MANUFLAG.  Not used.  Bit is not set to 1 in LUMINARY.
13
IGNFLAG.  Set to 1 in P12, P40, P41, P42 and P63 when nominal ignition time has arrived.  If bit is 1 when a "proceed" response is received to the V99 display, engine ignition is performed immediately.  Set to 0 5 seconds before scheduled ignition time or 5 seconds before next attempt at engine ignition if the astronaut has keyed in "enter" to the V97 engine fail display.  In the latter case P70 and P71 treat IGNFLAG in the same manner as the above five programs.  Also set to 0 at time engine (DPS or APS) has been turned on.
12
ASTNFLAG.  Bit set to 1 in P12, P40, P42, and P63 when crew authorization for ignition (a "proceed" to the V99 display) is received.  If bit 13 of this word is 1, engine ignition is performed promptly.  Bit is set to 0 at the same time that bit 13 is set to 0.  The treatment of this bit for P70 and P71 following an "enter" to the V97 display, is the same as for P12.
11
SWANDISP.  Bit is set to 1 in the Master Ignition Routine at P63IGN and P12IGN portions of the program to enable Landing Analog Displays (R10).  The mode select switch must be set to the PGNCS position n order to display.  Bit is reset to 0 at the termination of SERVICER or on landing confirmation to suppress the Landing Analog Displays.  R10 can be executed at the rate of four times per second, but data will not be displayed while the bit is 0.  The bit is examined immediately upon entrance to the R10 routine.
10
NORMSW.  Set to 1 to specify to the LAMBERT routine that it is to use the unit normal vector (to the conic transfer plane) which is provided by the calling program; reset to 0 if LAMBERT is to calculate its own unit normal vector (by crossing the initial and final position vectors of the transfer).  Set to 1 by the Initial Velocity Routine, INITVEL (the only routine which calls LAMBERT) whenever INITVEL is called with a (true or offset) target vector which lies inside "the cone"; reset to 0 by INITVEL whenever INITVEL is called with a (true or offset) target vector which lies outside "the cone".  ("The cone" is a mathematically-defined cone whose vertex is the origin of coordinates, whose axis is the 180° transfer direction, and whose semi-cone angle is specified to INITVEL.)  The semi-cone angle is set to 15° by P34, P35, P74 and P75 because active vehicle transfer angles between 165° and 195° are normally avoided in the targeting procedure.  However, if a transfer angle falling within this 180° ± 15° sector is intentionally selected by one of the targeting programs (P34 or P74), or results from one of the maneuver programs (P35 or P75) during an intercept trajectory targeted for more than 180°, the Lambert Aim Point Maneuver Prethrust Routine increases the semi-cone angle to 45° so that active vehicle transfer angle will not change from inside to outside the cone angle during the powered maneuver.  Such a condition is undesirable since the intercept trajectory would be retargeted during the powered maneuver.  Likewise, if the initial transfer central angle falls outside the 15° semi-cone angle, the semi-cone angle is decreased to 10° to reduce the possibility of a transfer angle changing from outside to inside the cone during a powered maneuver.  NORMSW should generally remain 0, unless transfers between 165° and 195° are intended.  NORMSW is equivalent to the switch f2 of Section 5.5, and to the switch SR of Section 5.3.3. of the GSOP.
9
RVSW.  Set to 1 to indicate to the TIME-THETA and TIME-RADIUS Routines that the only desired output is the time required to transfer through the specified transfer angle or to the specified radius respectively, and set to 0 to indicate that the state vector at the terminal point is desired in addition to the transfer time.  Set to both 1 and to 0 during the course of the computations of each standard internal iteration in the Pre-CSI Maneuver Program P32 or P72.  Set to 0 by the Pre-CDH Maneuver Program P33 or P73.  Set to 1 by the Pre-TPI Maneuver Program P34 or P74.  The bit is equivalent to the inverse of the switch f6 of Section 5.5 of the GSOP.
8
V67FLAG.  Set to 0 whenever an extended verb V67 is taken.  The verb displays the RMS position, velocity, and bias errors from the W-Matrix using a V06N99.  If the astronaut then changes these values, the bit is set to 1.  The bit is tested in the V67CALL routine: a 1 means compute new initial W-Matrix values for either rendezvous or lunar surface navigation; a 0 means do not compute these values.
7
IDLEFLAG.  Bit set to 1 as part of a fresh start, and used if 0 to permit the Delta-V monitor computations to be performed by the Average-G loop.  Bit is always set to 0 when engine is turned on in P12 and P63 (or in P70 and P71 if the astronaut has attempted to relight the engine following an engine failure).  In P40 and P42 the bit is set to 0 at engine ignition if and only if bit 9 of flagword 2 is 0 (i.e., burn interval≥6 secs).  The bit is set to a 1 in the following instances:  1) Whenever V37 is used to select a new program.  2) In P12, P40, P42, P70, and P71 when TGO is less than 4 seconds (i.e., when a waitlist task is set up to turn off the engine), and 3) when engine fail has been determined (i.e. when V97 appears on the DSKY).  In addition the bit is set to 0 if an engine failure is detected and the astronaut keys in a "proceed" to the V97.  The bit is set to 1 also if a "POODOO" type of abort occurs while Average-G is running.
6
V37FLAG.  Set to 1 by PREREAD (Average-G initialization) to indicate that Average-G is running.  Bit is examined by R00 (Program Change Routine) to detect Average-G activity and to wait for Average-G termination if it is on.  Reset to 0 by AVGEND after termination of Average-G.
5
AVEGFLAG.  Set to 1 by PREREAD (Average-G initialization) to indicate that Average-G is desired.  Bit is examined by READACCS (PIPA Read Routine, cycling at 2-second intervals) to determine whether to continue Average-G cycle.  Reset to 0 by R00 (Program Change Routine) to indicate that Average-G should terminate.
4
UPLOCKFL.  Set to 1 if a failure of the CCC data check is detected in processing an input from the uplink receiver.  The bit can be reset by sending an error reset code via the uplink (the DSKY error reset key does not reset the bit).  While the bit is 1, all uplink information except an error reset code is rejected by the program.
3
VERIFLAG.  Bit whose value is complemented when the final proceed entry is received in P27, indicating that the uplink information is to be used.
2
V82EMFLG.  A 1 indicates moon vicinity.  A 0 indicates earth vicinity.  Set to 1 or 0 by R30 according to whether state vectors are moon-centered or earth-centered.  Bit tested by SR30.1 when called by R30 to compute PERIGEE, APOGEE radius and PERIGEE, APOGEE height above launch pad or lunar landing site.
1
TFFSW.  Set to 1 in CALCTPER, cleared in CALCTFF.  When 1, indicates that present or last computation was Time to Perigee for Noun 32.  When 0, indicates that present or last computation was Time to Free Fall for Noun 44.  In R30, Time to Perigee is computed if perigee altitude is at least 300,000 feet above the earth launch pad (Earth sphere) or at least 35,000 above the lunar landing site (Moon sphere).  Otherwise TFF is computed.

43a

FLAGWORD 8.  Bit assignments are as follows:

Bit
Meaning
15
RPQFLAG.  Internal flag in integration to indicate if primary body to secondary body position vector (RPQ) was computed; 1 indicates RPQ not computed.
14
Not used.
13
NEWIFLG.  Internal flag in integration.  Used to engage 4 time step only on the first step of P00 integration; 1 means first step, 0 means not first step.
12
CMOONFLG.  Indicates origin of "permanent" CSM State Vector; 1 means lunar-centered, 0 means earth-centered.  Always set to 0 or 1 depending on MOONFLAG when permanently updating the CSM state vector.
11
LMOONFLG.  Indicates origin of "permanent" LM State Vector; 1 means lunar-centered, 0 means earth-centered.  Always set to 0 or 1 depending on MOONFLAG when permanently updating the LM state vector.
10
FLUNDISP.  Bit is set to 1 by R40 (Engine-fail routine) to suppress guidance displays that P12, P63 thru P66 P65, P70, and P71 issue in order to avoid conflict with V97 or V99.  Bit is reset to 0 by TIG-0 to allow guidance displays to be presented by the guidance equations.  The bit is examined by P12, P63 thru P66 P65, P70, and P71 prior to issuing a display.
9
Not used.
8
SURFFLAG.  Bit is set to 1 by P68.  Bit is reset to 0 by P12 when engine thrust is detected.  Bit is not altered by FRESH START.  Bit is checked by LEMCONIC, LEMPREC, and INTEGRV (when integrating LM) integration routines; if set, these routines call the Planetary Inertial Orientation subroutine to obtain the LM state vector.  Bit is checked by R31; if bit is set to 1, R31 obtains LM state vectors by calling LEMPREC rather than by calling a conic integration routine.  Bit is checked by V67 to determine whether the W-matrix is being initialized for P20 or P22.  Bit is checked by P20 and P22 in common coding areas to determine  if P20 or P22 is running.  Bit is checked by the AOTMARK routine to determine whether the mark taken is an in-flight or a surface mark.  Bit is checked by the P00 integration routine; if the bit is set to 1, the LM state vectors are not updated.  Bit is checked by SERVICER; if the bit is set to 1, the LM mass is not altered by MASSMON.  Bit is checked by  the LASTBIAS and NBDONLY routines (IMU compensation routines for free-fall and lunar surface operation): if the bit is set to 1, these routines include acceleration-sensitive drift corrections; whereas, if the bit is reset to 0, only non-acceleration-sensitive drift corrections are made.  In addition, NBDONLY zeroes the pipas (after reading them) if the bit is set to 1.  P21 checks SURFFLAG to determine whether LM is on the surface.  Bit is checked in V66 to see if LM is on lunar surface.
7
INFINFLG.  Set to 1 in the conic TIME-THETA Routine to indicate that the routine was called with a hyperbolic initial state vector and a true anomaly transfer angle which was so large as to require a transfer past the hyperbolic asymptote of the conic, which is physically impossible.  Set to 0 in TIME-THETA if a valid physical solution is obtained.  Set to 1 in the conic TIME-RADIUS Routine to indicate that the routine was called with a hyperbolic initial state vector, a desired final radius, and a desired sign of the radial velocity of the final radius (to indicate whether trajectory is to be inbound or outbound here) which would require a transfer past the hyperbolic asymptote of the conic.  For example, a spacecraft which is inbound can never return inbound to a radius which is greater than its current radius, and likewise a spacecraft which is outbound can never return outbound to a radius which is less than its current radius.  Set to 0 in TIME-RADIUS if a valid physical solution is obtained.  Set to 1 during any one (or several) of the internal LAMBERT iterations if the intermediate solution arrived at on this particular internal iteration required a transfer past a hyperbolic asymptote.  The LAMBERT routine senses such a situation on the succeeding iteration and adjusts various parameters in an attempt to obtain a valid solution.  Set to 0 in LAMBERT if the preceding internal iteration yielded a physically realizable transfer.  The bit is never tested or set either way outside the conic subroutines.  The bit is equivalent to the switch f7 of Section 5.5 of the GSOP.
6
ORDERSW.  Never set to 1.  Set to 0 as part of a fresh start.  Used to control the type of computation performed in the ITERATOR routine (part of the conic subroutines).  This bit is equivalent to the switch f4 of Section 5.5 of the GSOP.
5
APSESW.  Set to 1 by the TIME-RADIUS routine to indicate that the routine solved for the time required to reach pericenter (or apocenter) rather than the desired radius, because the desired radius input to the routine was less than the pericenter radius (or was greater than the apocenter radius, respectively).  Set to 0 by the TIME-RADIUS routine to indicate that the routine attempted to solve for the time required to reach the desired radius, since the desired radius input was greater than pericenter radius and less than apocenter radius.  (Such a solution will be reached unless INFINFLG is set to 1.)  This bit is equivalent to the switch f8 in Section 5.5 of the GSOP.
4
COGAFLAG.  Set to 1 by the TIME-THETA routine and the TIME-RADIUS routine if either of these routines was called with an initial state vector having a flight-path-angle (measured from local vertical) less than 1° 47.5' or greater than 178° 12.5'.  Set to 0 in each of these routines if either was called with an initial state vector having a flight-path-angle between these two extremes.  The bit is never tested or set either way outside the conic routines.
3
Not used.
2
INITALGN.  Bit is set to 1 by P57 alignment to indicate than an initial alignment, technique 0, is being performed.  The program will then branch to the selected alignment technique, unless the selected technique is 0.  Bit is reset to 0 after completion of the initial alignment to indicate that the final, selected technique, alignment is to be performed.  Bit is reset to 0 if ATTFLAG is at 0.  Bit is tested after each initial alignment if the alignment technique is 1, 2, or 3.
1
360SW.  Used to indicate the type of computation to be performed by the Universal Variable Routine (a subroutine called by the LAMBERT, TIME-THETA, and TIME-RADIUS routines).  The bit is not of interest outside these three conic routines and in fact is neither tested nor set either way outside the Universal Variable Routine itself.  The bit is equivalent to the switch fW of Fig. 5.10-4 of Section 5.5 of the GSOP.

43b

FLAGWORD 9.  Bit assignments are as follows:

Bit
Meaning
15
Not used.
14
FLVR.  Bit is set to 1 in P70, P71 initialization before throttling up the engine, and in P12 during initialization.  A 1 indicates that the vertical rise command overrides the computed guidance command. Bit is reset to 0 when either the vertical rate is greater than 40 fps or the altitude is greater than 25 K ft.  A 0 indicates that computed guidance commands may be used.  Bit is tested in Ascent Guidance Equations to determine whether vertical rise is required.
13
P7071FLG.  Set 1 near the beginning of P70 and P71 to indicate that the ascent guidance equations are operating in abort mode (i.e. explicit targeting and no R29).  Pad-loaded 0.  Tested as follows: near the beginning of Ascent Guidance Equations, if 1 compute needed ZDOTD; in middle of Ascent Guidance Equations, if 1 compute estimated pericynthion radius (RP), in tipover segment of Ascent Guidance Equations, if 1 do not activate R29.
12
FLPC.  Bit is set to 1 in Ascent Guidance Equations when Time-to-go is less than 10 seconds.  A 1 indicates that the pitch rate parameter is nulled, thereby releasing altitude control.  Bit is assumed to be 0 in padload.  A 0 indicates that the pitch rate parameter is a function of altitude and altitude rate.  Bit is tested in guidance parameter computations.
11
FLPI.  Bit is set to 1 in P12 initialization (pre-launch computation) to use Ascent Guidance Equations as a subroutine.  A 1 indicates that program sequence will return to P12.  Bit is reset to 0 immediately upon return from Ascent Guidance Equations.  A 0 indicates that normal Ascent Guidance operation will be continued (call FINDCDUW).  Bit is tested in Ascent Guidance Equations before call to FINDCDUW.
10
FLRCS.  Bit is set to 1 when an engine cuts off while guidance is under control of Ascent Guidance Equations.  A 1 indicates that the thrust-magnitude filter will be bypassed, and that the Ascent Guidance Equations will only be used to generate VGB.  Bit is assumed to be 0 in padload.  Bit is reset to 0 in P70, P71 initialization.  A 0 indicates that the thrust-magnitude filter will be used (if ΔV is large enough), and that the normal mode of the guidance equations will be used.  Bit is tested at the beginning of thrust-magnitude filter, and early in Ascent Guidance Equations.
9
LETABORT.  Bit is set to 1 in P63 after ignition, permitting the calling of the abort programs P70 and P71.  Bit is rest to 0 during P68, prohibiting any subsequent call to P70 or P71.  Bit is also reset to 0 after a TERMINATE or PROCEED response to the V16N85 display following injection, and at the beginning of P71.  Bit is tested at the beginning of P70, P71.
8
FLAP.  This bit is examined by P71 in order to determine if it has been preceded by the P70 abort program.  If P71 finds it set the abort will proceed using target initialization set up by P70.  If P71 finds it reset then either P70 did not precede P71 or else the P70 target initialization had not been completed by the time P71 was selected.  In this case, P71 performs the target initialization itself.  P70 sets the bit to 1 when all target initialization is complete.  P71 also sets the bit to 1 if it is required to do its own initialization but this has no real function.
7
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B
Spare or garbage.
Luminary 1C, 1D, 1E
ABTTGFLG.  The bit is normally a 0 (reset 0 by V37).  In P70 and P71, if the J1,K1 parameters are being used for Abort Targeting, the bit will remain a 0.  If the J2,K2 parameters are to be used, the bit will be set to 1.  The bit will then be reset to 0 by the next V37.
6
ROTFLAG.  Bit is set to 1 by UPFLAG shortly after P70 or P71 is selected by pushbutton action or through DSKY entry.  A 1 indicates that P70, P71 will force vehicle rotation in the preferred direction ("over-the-top" automatic attitude maneuver).  If the LM altitude is less than 25K feet at the time of altitude check, the bit is reset to 0 when HDOT is greater than 40 fps (up).  If the LM altitude is more than 25K feet at the time of altitude check, the bit is reset to 0 when the LM x-axis is within 90° of the desired LM x-axis, or the present LM x-axis is within 30° of the local vertical (up).  A 0 indicates that P70, P71 will not force vehicle rotation in the preferred direction (vehicle rotation completed or the conditions stated above have been satisfied).  The bit is used for branching during ABORT and/or ABORT STAGE ascent guidance.
5
QUITFLAG.  Set to 1 by extended Verb 96 (which then exits to P00) to indicate that integration should be discontinued.  Bit is examined by integration routines which exit if the bit is 1.  P00 state vector integration is not performed if the bit is 1.  Reset to 0 in P00 if it was found to be 1.  Normal integration processes resume as soon as a new program is selected via V37.
4
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
FLT59FLG.  Used to select cursor-spiral mark procedure during inflight alignment.  Set by V32 response to V50N25 display (checklist code 15).  Reset prior to V50N25 display (checklist code 15) in R51.  Also reset by V36 and V37 and at the start of P57.
3
MID1FLAG.  Bit set 1 to indicate that MIDTOAV1 called integration.
2
MIDAVFLG.  Bit set 1 to indicate that integration was called by MIDTOAV1 or MIDTOAV2 (R41).  Bit set 1 engages R41 logic.
1
AVEMIDSW.  Set to 1 to indicate that synchronization of state vectors and W-Matrix is in progress in the transition from powered flight to coasting flight and that the powered flight state vector should not be overwritten until the synchronization is completed.

44a

FLAGWORD 10.  Bit assignments are as follows:

Bit
Meaning
15
Not used.
14
INTFLAG.   A 1 indicates that some program or routine has called INTSTALL and is presumably in the process of integrating.  Other programs calling INTSTALL will wait until this bit is reset to 0.  A 0 indicates that no program or routine is currently using integration.  Set 1 by INTSTALL.  Set 0 by INTWAKE.  A hardware or software restart sets this bit to 0.
13
APSFLAG.  Bit is set to 1 by the astronaut in R03 (V48).  Bit is set to 1 when entering P68 (touchdown) or P71 (APS abort).  Bit is also set 1 by P42.  A 1 indicates that LM has staged or that it is on the lunar surface.  Bit is reset to 0 before launch or by the astronaut in R03 (V48).  A 0 indicates that the descent stage is attached and that the LM is not on the lunar surface.  Bit is the only indicator of state and is not changed by FRESH START.  Bit is used in the autopilot and in burn programs.
12
Not used.
11
Not used.
10
Not used.
9
Not used.
8
Not used.
7
REINTFLG.  A 1 indicates that the routine currently using INTSTALL is to be restarted.  A 0 indicates that no restartable integration is in progress.  Programs which have restart points during integration set this bit to 1.  INTWAKE sets this bit to 0.  Bit is untouched by hardware restarts thus retaining INTSTALL for restartable programs.
6
Not used.
5
Not used.
4
Not used.
3
Not used.
2
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
CONTRLFL.  A 1 indicates that the DAP is controlling (or attempting to control) the vehicle; a 0 indicates that it is not.  A routine is executed every 480 msec under TIME4 control that forces the state of the No DAP Control DSKY light (DSPTAB + 11D/bit 2) to be the opposite of the state of this bit; it then initializes the bit to 1.  The bit is reset to 0 by the DAP if it executes its Idling routine or Minimum Impulse routine.  The bit is not set, reset or tested except in the routines mentions.
1
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
NPGNCSFL.  The bit is an image from the non-idling autopilot cycle of Channel 30/bit 10 (0 for PGNCS Guidance select indication; 1 for AGS).  At the beginning of any non-idling autopilot cycle, if the channel bit is 0 and NPGNCSFL is 1 the bit is reset, and then the DAP goes through an initialization pass.

44b

FLAGWORD 11.  Flagword 11 is used to control the operation of R12, the Descent State Vector Update routine.  Therefore, its contents are only used during the programs P63 thru P66.  During all other programs, bit 15 is set, bits 14 thru 1 are reset, and the contents of flagword 11 should be 400008.  The exception, bit 8, which can be set and reset by extended verb 57 and reset by extended verb 58, is normally switched during R12.

Flagword 11 is initialized to 400008 by R00, R11 (when an abort is requested), and by a fresh start.  Also set to 400008 whenever a POODOO abort occurs when Average-G is running.

Bit
Meaning
15
LRBYPASS.  Bit is reset to 0 by P63 to permit R12 operation.  R09, the "R10, R11, R12 service monitor", checks LRBYPASS and when it is 0, R12 is entered.  When the bit is set to 1, R09 bypasses R12.  This bit is set to 1 by R00 (V37) or by an abort (R11), insuring that R12 will be off when either P12, P70, or P71 is called.
14
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
Not used.
Luminary 1D, 1E
VFAILFLG.  Velocity fail test.  Set 1 when velocity radar reading has failed the LR data reasonability test.  Bit is reset 0 when the corresponding radar reading has passed the reasonability test.
13
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
Not used.
Luminary 1D, 1E
HFAILFLG.  Altitude fail test.  Set 1 when altitude radar reading has failed the LR data reasonability test.  Bit is reset 0 when the corresponding radar reading has passed the reasonability test.
12
VXINH.  If the Z velocity component fails to pass the data reasonability test, the bit is set to 1 and the X velocity component is not updated with landing radar data.  If the next velocity sample to pass the reasonability test is not an X component, the bit is reset to 0 and the data is accepted; X component data will be rejected, and then the bit will be reset to 0.  This process prevents updating with questionable data caused by cross lobe lock-up on the X component.
11
PSTHIGAT.  Bit is initially reset to 0.  Bit is set to 1 when the criteria for repositioning the landing radar antenna are first met, and indicates that the antenna should be either repositioning or in position 2. Bit remains set for the duration of the landing.
10
NOLRREAD.  Bit is set to 1 when PSTHIGAT is set to 1, to prevent reading the landing radar while the antenna is repositioning.  Bit is reset to 0 after the antenna achieves position 2 and allows further readings.  If the antenna does not achieve position 2, and the astronaut chooses to proceed without R12 (i.e. V34E response to flashing V05N09 alarm 00523), the bit will remain set to 1 and therefore inhibit landing radar reading.
9
XORFLG.  Bit is set to 1 when the LM estimated altitude first falls below 30K feet.  At this point, R12 inhibits X axis override in the digital autopilot.  Bit remains set to 1 for the duration of the landing.  Its purpose is to prevent R12 from inhibiting X axis override.
8
LRINH.  This bit is initially reset to 0 by R00 allowing the landing radar data to be read and tested but not incorporated into the state vector.  The bit may be set to 1 via extended verb 57, permitting landing radar data incorporation into the state vector.  It is reset to 0 via extended verb 58.  Bit may be reset to 0 after it has been set to 1 in V57.
7
VELDATA.  Bit is set to 1 by the landing radar velocity read routine after a valid reading has been made.  A 1 indicates that a landing radar velocity reading has been made and that the data is available.  Bit is reset to 0 by R12 after the data is used.  Bit has a limited value on the downlink because it is set and reset at least once during a two second interval; and, due to the fact that the downlink reads this bit at the same point during each pass, it may read exactly the same (either always set or always reset) on each pass.
6
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A
READLR.  Set 1 if OK to read LR range data, set to 0 if not OK.
Luminary 1B, 1C, 1D
LPOS2FLG.  Set 1 in SETPOS2 to inform that position 2 transformation is being used.  Reset 0 in fresh start and V37 logic.  Also set 0 for abort or abort stage.
Luminary 1D, 1E
Not used.
5
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
READVEL.  Bit is set to 1 when the LM inertial velocity estimate drops below 6K feet per second.  When the bit is set to 1, it permits R12 to read the landing radar velocity components, and process the data.  This bit remains set to 1 during the entire landing.
Luminary 1D, 1E
Not used.
4
RNGEDATA.  Bit is set to 1 by the landing radar altitude read routine after a valid reading has been made.  A 1 indicates that a landing radar altitude reading has been made and that data is available.  Bit is reset to 0 by R12 after the data is used.  Bit has a limited value on the downlink because it is set and reset at least once during a two second interval; and, due to the fact that the downlink reads this bit at the same point during each pass, it may read exactly the same (either always set or always reset) on each pass.
3
This bit is known to vary by Luminary software version.

Version
Description
Luminary 1, 1A
SCALBAD.  Set to 1 if LR low scale discrete not present when it should be, set to 0 if LR scale discrete appears OK.
Luminary 1B, 1C
NO511FLG.  A 1 means do not test LR antenna position in R12.  Set 1 by V33 response to a flashing V05N09, alarm code=523.  If bit is 1, R12 won't test for 511 alarm.
Luminary163
Spare or garbage.
Luminary 1D, 1E
R12RDFLG.  Bit is set to 1 as an indication to wait (R12) until all velocity readings are finished.  It is reset to 0 as an indication that all radar reads are completed.  The bit is set 1 when R12READ begins and is reset to 0 when R12READ is finished.  R12 (itself a part of SERVICER) waits until the bit is reset.  This flagbit is also reset by a Fresh Start or Restart.
2
VFLSHFLG.  Bit is set to 1 when two or more of the last four landing radar velocity readings (including the current reading) have failed the landing radar velocity data reasonability test.  When bit is set to 1, the landing radar velocity fail light will be flashed by R09.  Bit is reset to 0 when a velocity reading passes the reasonability test.
1
HFLSHFLG.  Bit is set to 1 when two or more of the last four landing radar altitude readings (including the current reading) have failed the landing radar altitude data reasonability test.  When bit is set to 1, the landing radar altitude fail light will be flashed by R09.  Bit is reset to 0 when an altitude reading passes the reasonability test.

45a,45b,46a,46b,47a,47b,48a,48b,49a,49b,50a

DSPTABs.  The eleven registers, DSPTAB through DSPTAB+10D, indicate the status of the DSKY displays.  If bit 15 through 12 are 0001, the next 11 bits will indicate the actual status of the DSKY displays; if bits 15 through 12 are 1110, the next 11 bits indicate the "ones" complement of the status to which the LGC will command the DSKY display.  Bits 11-1 of DSPTAB+0 through DSPTAB+10D are decoded as follows:





Bit Assignments
DSPTAB
Register
    
Downlink
Word No.
    
Bit 11
Bits 10-6
Bits 5-1
DSPTAB+0

45a

-R3S
R3D4
R3D5
DSPTAB+1
45b

+R3S
R3D2
R3D3
DSPTAB+2
46a


R2D5
R3D1
DSPTAB+3
46b

-R2S
R2D3
R2D4
DSPTAB+4
47a

+R2S
R2D1
R2D2
DSPTAB+5
47b

-R1S
R1D4
R1D5
DSPTAB+6
48a

+R1S
R1D2
R1D3
DSPTAB+7
48b



R1D1
DSPTAB+8D
49a


ND1
ND2
DSPTAB+9D
49b


VD1
VD2
DSPTAB+10D
50a


MD1
MD2

R3D1 stands for digit one of the third register and VD1 stand for the first digit of the verb display, etc.  For the right character of a pair, bit 5 is the MSB with bit 1 the LSB.  For the left character of a pair, the MSB is bit 10 with bit 6 the LSB.  Bit 11 of some of the DSPTABs contains discrete information, a one indicating that the discrete is on.  For example, a one in bit 11 of DSPTAB+1 indicates that R3 has a plus sign.  If the sign bits associated with a given register are both zeros, then the content of that particular register is octal; if either of the bits is set, the register content is decimal data.

The five bit codes associated with the digits are as follows:

                
MSB



LSB
0
1
0
1
0
1
1
0
0
0
1
1
2
1
1
0
0
1
3
1
1
0
1
1
4
0
1
1
1
1
5
1
1
1
1
0
6
1
1
1
0
0
7
1
0
0
1
1
8
1
1
1
0
1
9
1
1
1
1
1
Blank
0
0
0
0
0

The following is a diagram of the DSKY face showing positions of the different digits:

                             Program
┌───────┬───────┐ │ MD1 │ MD2 │ └───────┴───────┘
Verb Noun
┌───────┬───────┐ ┌───────┬───────┐ │ VD1 │ VD2 │ │ ND1 │ ND2 │ └───────┴───────┘ └───────┴───────┘
Register 1
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R1D1 │ R1D2 │ R1D3 │ R1D4 │ R1D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘
Register 2
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R2D1 │ R2D2 │ R2D3 │ R2D4 │ R2D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘

Register 3
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R3D1 │ R3D2 │ R3D3 │ R3D4 │ R3D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘

50b

DSPTAB+11D.  This register drives relays for the display lights.  The bit assignments are:

Bit
Assignment
1
This bit differs by Lunar Module software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
Priority Display
2
This bit differs by Lunar Module software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D Not used.
Luminary 1E
No DAP Control
3
Landing Radar Velocity Fail
4
No Attitude
5
Landing Radar Altitude Fail
6
Gimbal Lock
7

8
Tracker
9
Program Caution

If bits 15 through 12 of DSPTAB+11D are 1000, the last 11 bits indicate the state to which the LGC will command the relays; if bits 15 through 12 are 0000, the last 11 bits indicate the actual state of the relays.  A one indicates that the discrete is on.

51

TIME2, TIME1.  Double precision word indicating ground elapsed time.  Used for all timing while LGC is on.  Zeroed at liftoff (by crew procedure), increment by one bit per centisecond.  May be updated by V55 (R33), V25N36, V70 (P27), or V73 (P27).  Scaled centiseconds/228.

52,53,54,55,56,57,58

LM STATE VECTOR and TIME.  The LGC's latest calculated state vector for the LM in reference coordinates.  The coordinates may be either earth-centered or moon-centered; a zero in bit 11 of flagword 8 (LMOONFLG) indicates earth-centered, a one indicates moon-centered.  Words 52-54 contain the position components X, Y, Z scaled meters/229.  Words 55-57 contain the velocity components X, Y, Z scaled (meters/centisecond)/27.  Word 58 contains the time associated with the state vector scaled centiseconds/228, referenced to the computer clock.  The scaling for position, velocity and time is the same whether earth-centered or moon-centered.  These parameters are calculated whenever the LM state vector is permanently extrapolated or changed as follows:

59a,59b,60a

DESIRED BODY RATES (X, Y, Z).  Desired automatic maneuver rates about body axes as given to the DAP.  Calculated at the beginning of an automatic coasting flight maneuver (KALCMANU) and zeroed at the end.  Recomputed every 2 seconds in powered flight when steering (FINDCDUW) is enabled.  Scaled (radians/sec)/(π/4).  Range is ±10 degrees/sec.

60b

Garbage.

61a,61b,62a

These downlink items are known to differ somewhat by Luminary software version.

 Version
Description
Luminary 1, 1A, 1B, and 1C
CADRFLSHs.  A set of three single-precision erasable memory cells used to retain return address information from the display interface routine.  CADRFLSH contains the FCADR of the last priority display request, CADRFLSH+1 the FCADR of the last mark/extended verb display, and CADRFLSH+2 contains the FCADR for the last normal display.  Octal quantities.
Luminary 1D
  • 61a: Garbage or Spare
  • 61b: CHAN77.
  • 62a: CADRFLSH +2 as above.

As for CHAN77 (Channel 77):  A computer output channel, the individual bits of which are used to indicate the source of a hardware restart.  The channel is initialized to 0 by a V36E (request fresh start).  The channel will be zeroed by the final V33E on a P27 state vector uplink and also by a crew or ground V21N10E77EE.  Should a hardware restart occur, one of the bits in the channel should be set to 1 indicating the source.  If multiple restarts occur, more than one bit could possibly be left set afterwards (i.e., if they were different types).  Many restarts of the same type would leave just one bit set with the software REDO COUNTER indicating the number.  The bit definitions are:

         
BIT
         
RESTART (and/or AGC
warning) CAUSE             

15-10

Spare

9

Scalar double freq.

8

Scalar fail

7

Counter fail

6

Voltage fail

5

Nightwatchman

4

Ruptlock

3

TC Trap

2

E-memory parity fail

1

E or F-memory parity fail

Note that a restart due to oscillator fail is not shown in this channel.
Luminary 1E
  • 61a: Garbage or Spare
  • 61b: CHAN77 as above
  • 62a: CHANBKUP

As for CHANBKUP:  A single-precision erasable memory cell used to bypass logic check of channel 30, bits 1, 4, and 5.  Displayed as R2 of NOUN 46 in R03.

         
Bit
         
Meaning (If set to 1)

4

Bypass logic for Auto Throttle (bit 5)
in P66 and pre-ignition powered-flight
programs if the APSFLAG is not set.
Assumes Auto Throttle.

1

Bypass logic for Abort (bit 1) and Abort
State (bit 4) in aborts monitor routine
(R10, R11).  Assumes no abort or abort
stage request; P70 or P71 must be
called if this bit is set.

62b,63a,63b

FAILREG's, a set of three single-precision cells used to retain alarm pattern code information.  They are all reset to 0 by a fresh start.  FAILREG and FAILREG+1 are also reset to 0 by use of the "ERROR RESET" keycode.  FAILREG contains the first alarm code received after the "ERROR RESET", FAILREG+1 contains the second, and FAILREG+2 will always contain the most recent alarm code.  Octal quantities.

64a

RADMODES.  A flagword associated with radar modes.  A fresh start sets bits 7 and 2 to 1, sets bit 6 to the value of bit 6 of channel 33, and sets all other bits to 0.

Bit
Meaning
15
CDESFLAG. Continuous Designate.  A 1 means that commands are issued by the LGC to the Rendezvous Radar without checking to see if lock-on is achieved.  A 0 indicates that the LGC checks for lock-on when designating the antenna.  Set to 1 by selection of the continuous designate option of Verb 41, RR Coarse Align, and RR Automatic Search Routine (R24).  Set 0 by Verb 56 (Terminate Tracking), Verb 37 selection of P00, Verb 44 (Terminate RR Coarse Align), by answering the display (V16 N80) of R24, and by RR Monitor Routine (R25) if the RR mode changes from LGC to manual or off, i.e., if the RR auto mode discrete (Bit 2 of channel 33) changes from 0 to 1.  Also set 0 at the start of P20, P22, and P12.
14
REMODFLG. Remode.  A 1 means that a change in the antenna mode has been requested or is in progress.  A 0 indicates that no remode is requested.  Set to 1 when the Radar Designate Routines (R21, R24, Verb 41) determine that a designate may be performed after a remode has been done, and by R21 when on the lunar surface (in P22).  Set to 0 by the remode subroutine at the end of remoding and by Verb 56 or a Verb 37 request for another program and by R25 when the RR auto-mode discrete changes from 0  to 1.  Set to 1 by R29 before it calls the remode routine.
13
RCDU0FLG. RR CDU Zero.  A 1 means that the RR CDUs are being zeroed.  A 0 means that they are not being zeroed.  A 1 inhibits an RR CDU fail from lighting the tracker fail light.  Set to 1 by R25 when the RR auto-mode discrete changes from off/manual to on, and by Verb 40 with Noun 72.  Set to 0 by the RR zero subroutine at the end of the CDU zero, by Verb 56 or a Verb 37 request for another program and by a change in the RR auto-mode discrete from 0 to 1.
12
ANTENFLG. RR antenna mode.  A zero means the antenna is in Mode I, a 1 indicates Mode II.  The bit is set to the appropriate value by the RR turn-on sequence in R25 after an RR CDU zero, by the remode subroutine at the conclusion of a remode, and by a Verb 37 request for a new program.
11
REPOSMON. Monitor Reposition.  A 1 means that an RR reposition is taking place.  A 0 means that no reposition is taking place.  A 1 inhibits further checking of the antenna gimbal limits by R25.  When a designate is possible and about to begin, a 1 in this bit delays the designate until the reposition is completed.  If this bit is set to 1 during a designate operation, the designate is terminated with an error return (503 alarm).  Set to 1 by the RR Monitor Routine (R25) when it detects the antenna gimbal angles outside the limits for the present mode.  Set to 0 by the Reposition Routine at the end of the reposition, by Verb 56 or a Verb 37 request for another program and by R25 when the RR auto-mode discrete changes from on to off/manual.  Set to 1 at the start of antenna prepositioning in R29, set to 0 at the end of antenna prepositioning in R29.
10
DESIGFLG. Designate.  A 1 means that an RR designate has been requested or is in progress.  A 0 indicates that a designate has not been requested nor is one in progress.  Set to 1 at the start of a designate by R21, R24 or verb 41.  Set to 0 by Verb 44, by R21 when the designate is completed, by R24 when the V16 N80 display is answered, and by Verb 56.  Set to 0 by SERVICER if R29 if not allowed.  Set to 0 by R29 when lock-on is achieved in R29.  Set to 0 by R29 before calling the remode routine.  Set to 1 at the beginning of R29 if previously 0.  Set to 0 by a Verb 37 request for a program if R29 had been requested.  Also set 0 at the start of P20, P22 and P12.
9
ALTSCALE. Landing Radar Altitude Scale.  A 1 means that the landing radar altitude reading is on the high scale.  A 0 means low scale.  Set to the value in channel 33 bit 9 by R04 and R77 and each time the LR altitude is read.
8
LRVELFLG. Landing Radar Velocity Data Fail.  A 1 means that landing radar velocity data could not be read successfully.  Set to the value in channel 33 bit 8 each time landing radar velocity data is read.  Set to 0 by pressing the error reset button on the DSKY and by a lamp test.
7
RCDUFAIL. No RR CDU Fail.  A 1 means that an RR CDU fail has not occurred.  A 0 means one has occurred.  Set to the value in channel 30 bit 7 whenever the RR CDU fail discrete changes.  Set to 1 by an IMU turn-on sequence.  Set to 1 by a fresh start or a hardware restart.
6
LRPOSFLG. Landing Radar Position.  A 1 indicates LR position 2.  A 0 indicates position 1.  Set to 1 by Verb 59.  Set to value of bit 6 of channel 33 at start of R04/R77.   Also set 1 by R12.
5
LRALTFLG. Landing Radar Altitude Data Fail.  A 1 means that LR altitude data could not be read successfully.  Set to the value in channel 33 bit 5 each time LR altitude data is read.  Set to 0 by pressing the error reset button on the DSKY and by a lamp test.
4
RRDATAFL. RR Data Fail.  A 1 means that RR data could not be read successfully.  Set to the value in channel 33 bit 4 each time RR data is read.  Set to 0 by pressing the error reset button on the DSKY, and by a lamp test.
3
RRRSFLAG. RR Range Scale.  A 1 indicates the RR range reading is on the high scale.  A 0 indicates low scale.  Set to the value in channel 33 bit 3 by R22 prior to reading RR range, and also set by R22 when a scale change is detected.  Set to value of bit 3 of channel 33 at start of R04/R77.
2
AUTOMODE. RR Auto Mode.  A 1 means that RR is not in the auto mode; i.e., the RR auto mode discrete is not present.  A 0 means the RR is in the auto mode.  Set to the appropriate value by R25 when a change occurs in the RR auto mode discrete (channel 33 bit 2).  Set to 1 by an IMU turn-on sequence.  Set to 1 by a fresh start or hardware restart.
1
TURNONFL. RR Turn-On.  A 1 indicates than an RR turn-on sequence (zero the RR CDUs and establish the antenna mode) is in progress.  A 0 means that no RR turn-on sequence is in progress.  Set to 1 by R25 when the RR auto mode discrete changes from off/manual to auto.  Set to 0 at the termination of the turn-on sequence.

64b

DAPBOOLS.  A flagword associated with the DAP.  A fresh start sets DAPBOOLS to 213228.

Bit
Name
1 Meaning
0 Meaning
15
PULSES, PULSEFLG
Minimum impulse command mode.
Not in minimum impulse command mode.
14
USEQRJTS, USEQRFLG
Gimbal unusable.  Use jets only.
Gimbal may be used.
13
CSMDOCKED, CSMDKFLG
CSM-DOCKED (Use backup DAP)
CSM not docked.
12
OURRCBIT, OURRCFLG
Still in rate command
Not in rate command.
11
ACC4OR2X, ACC4-2FL
4-Jet X-Axis translation requested
2-Jet X-Axis translation requested.
10
AORBTRAN, AORBTFLG
B-System for X-translation
A-System for X-translation.
9
LPDPHASE (XOVINHIB), XOVINFLG
In LPD Phase (X-Axis override locked out).
Not in LPD Phase.
8
DRIFTBIT, DRIFTDFL
Assume zero offset.  Drifting Flight.
Offset acceleration likely (DPS, APS).
7
RHCSCALE, RHCSCFLG
Normal RHC scaling requested.
Fine RHC scaling requested.
6
ULLAGER, ULLAGFLG
Internal Ullage request
No internal ullage request.
5-4
DBSL2FLG, DBSELECT, DBSELFLG
These bits are used together to indicate astronaut-chosen deadband (5°, 1° or 0.3°).
3
ACCSOKAY, ACCOKFLG
Computed accelerations probably correct.
Computed accelerations probably incorrect.
2-1
AUTORATE2, AUTORATE1 (AUTR2FLG, AUTR1FLG)
These bits are used together to indicate astronaut-chosen KALCMANU maneuver rates.

Bits 13, 11, 10, 7, 5, 4, 2, 1 are changed only in R03.  Bit 15 is set by V76, cleared by V77; also cleared by P63, P70 and P71.  Bit 12 is under internal DAP control.  Bit 3 is set by 1/ACCs, cleared by fresh start and restart.

65-67

OGC, IGC, MGC.  The X, Y, and Z gyro torquing angles computed in CALCGTA in P52, P57; counted down as gyros are torqued.  During coarse align in CALCGA in P52, P57 the desired gimbal angles.  Scaled degrees/360.

68a, 68b

STAR IDs.  68a contains the star I.D. for the sighting vector in words 69-71.  68b contains the star I.D. for the sighting vector in words 72-74.  Set during PICAPAR and after astronaut changes star number.  These I.D.s will be the LGC catalogue number (Refer to Control Data section of this GSOP) multiplied by six.  Scaled 2-14.

69-71

STAR SIGHTING VECTOR 1 (STARSAV1).  During P52, P51 and Technique 2 of P57 STARSAV1 contains the 1st optics sighting vector.  During Technique 0 of P57 it contains the Y spacecraft axis and the gravity vector during techniques 1 and 3.  In stable member coordinates.  Scaled 2-1.

72-74

STAR SIGHTING VECTOR 2 (STARSAV2).  During P52, P51 and Techniques 2  and 3 of P57 STARSAV2 contains the 2nd optics sighting vector and contains the 1st sighting vector temporarily during sighting on the 2nd body.  During P57 techniques 0 and 1, STARSAV2 contains the Z spacecraft axis.  In stable member coordinates.  Scaled 2-1.

75-76

These words are known to vary by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C
75a,75b,76a: 
LR VELOCITIES (Raw Data).  Landing radar beam velocities (X, Y, Z).  The data readout from the Landing Radar High Speed Counter into LGC input counter 468.  Always contain the last values which were read, i.e., these registers are never initialized.  Each component read once per second during R77.  Each component read once per four seconds during LR option of R04.  Scaled (15-bit integer - 12288.2) × K ft/sec where K = -0.6440 for Vx, K = 1.212 for Vy, and K = -0.8668 for Vz.
76b:
LR RANGE (Raw Data).  Landing radar slant range.  The data readout from the LR High Speed Counter into LGC input counter 468.  Always contains the last value read, i.e., this register is never initialized.  Read once per second in R77.  Read once every 4 sec during LR option of R04.  A 15-bit integer which is multiplied by either 5.395 on the high scale or 1.079 on the low scale to convert to units of feet.  A 1 in bit 9 of RADMODES indicates high scale.
Luminary 1D, 1E
75a:
SERVDURN.  The Average-G cycle duration which is computed as the difference between TIME1 and the least significant half of PIPTIME at exit from the Average-G in SERVICER.  It is a measure of TLOSS; the greater the TLOSS, the larger that time will be.  The quantity is scaled centiseconds/214, and is corrected for overflow (always > 0).
75b:
DUMLOOPS.  The number of passes through Dummy Job, scaled counts/214.  The register is incremented when there is less than 100% duty cycle to indicate relative amounts of DUMMYJOB activity at various times.  The rate at which it is incremented indicates the amount of available processing time.
76:
TET.  Time of state vector being integrated or time to which last state vector was integrated.  It is stepped by half-time-step increments, plus or minus, whenever integration is being done.  Scaled, centiseconds/228.

77a

ACTUAL RR SHAFT CDU.  RR shaft angle CDU counter.  Defines RR antenna position (along with trunnion angle).  Updated from RR CDUs as shaft angle changes.  This register is an unsigned 15-bit fraction.  The quantity is scaled degrees/360.

77b,78a,78b

ACTUAL PIPAS (X, Y, Z).  Velocity increments along the IMU Stable Member X, Y, and Z axes.  Data is valid commencing at approximately 15 seconds after ISS Turn-on.  Automatic increments when ISS is on.  Zeroed every 2 seconds during powered flight.  Zeroed after coarse alignment in P51, P52, and P57.  Zeroed by NBDONLY (after reading) if SURFFLAG is set 1.  In stable member coordinates.  Scaled (centimeters/second)/214.

79

RR TRUNNION and SHAFT ERROR COUNTERS.  Rendezvous Radar error counter commands; 79a is trunnion, 79b is shaft.  They are placed in the RR error counters and specify the rate at which the RR antenna is driven.  Values range from +384 to -384 and vary according to the angular error between the present and desired RR positions.  Calculated every 0.5 second in the Radar Designate Routine (DODES) whenever the the LGC is driving the RR antenna which occurs when:
  1. The RR monitor (R25) detects the antenna out of mode limits.
  2. V41 N72 (RR Coarse Align) is operated.
  3. R21 (RR designate) is operated in P20/P22.
  4. R24 (RR Automatic Search) is operated in P20/P22.
A magnitude of 384 corresponds to a rate command of about 10 degrees/second.  The exact rate depends on the characteristics of the motors in the RR gyros.  79a and 79b are each scaled 2-14.

80a

LM MASS.  Current mass of the LM.  First part of Noun 47.  A buffered quantity that is determined by MASS (and CSMMASS when desired).  Pad-loaded.  Can also be loaded by crew via R03 (Verb 48 — DAP Data Load); R03 then determines MASS on the basis of LEMMASS (and CSMMASS when docked).  The 1/ACCS Routine, which is called every 2 seconds during powered flight, determines LEMMASS from MASS (MASS is decremented as a function of acceleration).  Scaled kilograms/216.

80b

CSM MASS.  Current mass of the CSM.  Used in the computation of the RCS and GTS control authorities when the LM is docked to the CSM.  Second half of Noun 47.  Pad-loaded.  Can also be loaded by crew via R03 (Verb 48 — DAP Data Load).  Scaled kilograms/216.

81a

IMODES30.  A flagword which monitors IMU conditions.  Set to 374118 by a fresh start.  A restart sets bits 14, 13, 12, 11, 10 to 1, sets bits 15, 8, 7, 6, 2 to 0 and preserves bits 9, 5, 4, 3, 1.  Updated every 0.48 second by T4RUPT program.

Bit
Meaning
15
Value of bit 15 of channel 30.  A 0 indicates stable member temperature within design limits.
14
Value of bit 14 of channel 30.  A 0 indicates ISS has been turned on or commanded to be turned on.  Bit is set 1 by a fresh start or a restart.
13
Value of bit 13 of channel 30.  A 0 indicates an IMU fail indication has been produced.  If this bit becomes 0 while bit 4 of this word is also 0, bit 1 of channel 11 (ISS warning) is set 1.
12
Value of bit 12 of channel 30.  A 0 indicates IMU CDU fail indication has been produced.  If this bit becomes 0 while bit 3 of this word is also 0, bit 1 of channel 11 (ISS warning) is set 1.
11
Value of bit 11 of channel 30.  A 0 indicates an IMU cage command has been generated by the crew.
10
Value of bit 13 of channel 33.  A 0 indicates a PIPA fail indication has been produced.  This bit has the same value as bit 13 of IMODES33.  Set 1 if an error reset key code is received (DSKY or uplink).  If this bit becomes 0 while bit 1 of this word is also 0, bit 1 of channel 11 (ISS warning) is set 1.
9
Value of bit 9 of channel 30.  A 0 indicates IMU turned on and operating with no malfunctions.  If bit becomes 1 while IMUSE (bit 8 of flagword 0) is 1, alarm 02148 will be generated.
8
Used to control sequencing of IMU turn-on.  Set 1 if bit 7 of this word is 1 and reset zero 0.48 second later, before the IMU turn-on sequencing is started.  Used to achieve a 0.48-second wait before acting on IMU turn-on information.
7
Used to control sequencing of IMU turn-on, set 1 based on values of bits 14, 9 and 2 of this word.  Reset zero 0.48 second later.  Can be set 1 if ISS initialization requested since last fresh start, IMU turn-off, or turn-on delay complete.
6
A 1 indicates that IMU initialization is being carried out.  Set 1 during turn-on sequence, if a cage command is received, or if IMU zeroing is done in T4RUPT.  Set 0 about 10.56 seconds after cage command removed, 10.56 seconds after start of zeroing in T4RUPT, or about 100 seconds after start of turn-on sequence.  If bit is 1, verb 37 input will not be processed (alarm 15208 will be generated).  If bit is 1, an error exit will be forced from the internal IMU routines.
5
Set to 1 to inhibit the generation of alarm 02128 if a PIPA fail signal occurs.  Not used unless bit 1 of this word is 1.  Set 1 during IMU turn-on sequence and reset 0 about 4 seconds after bit 6 is reset 0.  (If bit 10 of this word is 0, an alarm will be generated when Average-G is stopped regardless of the value of bit 5.)
4
Set to 1 to inhibit generation of an ISS warning based on receipt of an IMU fail signal.  Reset 0 when bit 6 is set 0.  Set 1 when IMU coarse align started and set 0 about 5.12 seconds after mode change to fine align.  Set 1 for 10.56 seconds when IMU CDU zero commanded.
3
Set to 1 to inhibit generation of an ISS warning based on receipt of an IMU fail signal.  Set 1 when bit 6 of this word is set 1 and set 0 when bit 6 is set 0.  Also set 1 for 10.56 seconds when IMU CDU zero is commanded separate from T4RUPT package (by V40N20 or prelaunch or IMU tests).
2
Set to 1 to indicate failure of the IMU turn-on delay sequence (alarm 02078 will also be generated).
1
Set to 1 to inhibit generation of an ISS warning based on receipt of a PIPA fail signal.  Bit set 1 when bit 6 of this word is set 1.  Bit set 0 when Average-G started and set 1 when Average-G ends.

81b

IMODES33.  A flagword which monitors various channel 32, channel 33, and IMU conditions.  Also monitors Verb 35 "lamp test".  Set to 160408 by a fresh start. Set to 160008 + the contents of bit 6 by a restart.  An error reset key code sets bits 13, 12, and 11 to 1 and does not affect other bits.  Updated every 0.48 second by T4RUPT program except for bit 14 which is updated every 0.12 second.

Bit
Meaning
15
Not used.
14
Value of bit 14 of channel 32.  A 0 indicates Proceed Key depressed.  A change from a 1 to a 0 will cause a job to be established that has the same program logic effect as Verb 33.  It should be noted that in the case of a response to a V21, V22 and V23, the logic for a Proceed is not the same as for a V33E.
13
Value of bit 13 of channel 33.  A 0 indicates a PIPA fail signal.  This bit has the same value as bit 10 of IMODES30.
12
Value of bit 12 of channel 33.  A 0 indicates downlink end pulse rate greater than 100 pps.  If this bit changes from 1 to 0, alarm 11058 is generated.
11
Value of bit 11 of channel 33.  A 0 indicates uplink rate greater than 6.4K pps.  If this bit changes from 1 to 0, alarm 11068 is generated.
10
Not used.
9
Not used.
8
Set to 1 when R10 routine is initialized during the powered descent trajectory.  A 1 in this bit causes the display inertial data discrete to be sent to the RR CDUs (bit 8 set in channel 12) and the RR error counter to be enabled (bit 2 set in channel 12).  A 0 in this bit causes the display inertial data discrete to be removed from the RR CDUs and the RR error counter to be disabled if R10 was terminated during the descent trajectory.  However, if R10 was terminated and/or restarted while in ascent bits 2 and 8 of channel 12 are left unchanged.
7
A switch employed in R10 for alternate computations of altitude rate and altitude (bit 2 of channel 14 tells which is which).  A 0 forces a program branch to compute and display altitude rate; bit is then set to 1 to compute and display altitude on next pass thru R10.  Bit then set 0, etc.
6
Set to 1 to indicate that IMU should not be used for vehicle attitude information.  Bit checked every 0.1 second by autopilot.  Bit set 1 the same time as bit 6 of IMODES30 and also when bit 4 of IMODES30 is set 1 (for IMU zeroing external to T4RUPT and for IMU coarse align).  Bit set 0 if IMU fine align routine is performed.  Bit set 1 if IMU turned off.
5
Set to 1 in IMU zeroing routine external to T4RUPT (by V40N20 or prelaunch or IMU tests).  Remains set to 1 for an interval of about 10.56 seconds while zeroing taking place.  Bit 6 of this word is set to 1 at the same time as bit 5.
4
Not used.
3
Not used.
2
Not used.
1
Set to 1 when Verb 35 "lamp test" is received.  Reset to 0 about 5 seconds later.  A 1 inhibits resetting of lights to 0 in T4RUPT during lamp test.

82


TIG.  Targeted time of ignition.  Calculated during pre-burn programs (P30s, P70s).  Updated in P12, P40, P41, P42, or P63 by MIDTOAVE routine if integration cannot be completed in time (1703 alarm).  After ignition TIG is set to time of engine cutoff (PIPTIME + TGO).  See also pg. 2-106 for use on Descent/Ascent List.  Scaled centiseconds / 228.

83a,83b,84a

CURRENT BODY RATES (X, Y, Z).  Estimated current rates about body axis.  Calculated at the beginning of every DAP cycle every 0.1 sec.  Zeroed at DAP start-up.  Scaled (degrees/sec)/45.  Expected range of ±10 degrees/sec but ±45 degrees/sec is possible.

84b

Garbage.

85a,85b,86a

DAP INTERNAL DESIRED CDUs (X, Y, Z).  Outer, inner and middle intermediate desired gimbal angles.  Steering commands to DAP.  Generated during a burn by guidance equations or during an automatic maneuver.  Calculated every 2 secs during a PGNCS controlled burn (i.e., P40, P42).  Updated every 0.1 sec by the DAP (using DELCDUs) during an automatic maneuver (KALCMANU) and also during powered flight.  These registers are unsigned 15-bit fractions.  Scaled degrees/360.

86b

Garbage.

87a,87b,88a

ACTUAL CDUs (X, Y, Z).  The current outer, inner and middle IMU gimbal angles.  Automatically updated by the hardware when the IMU is on.  These registers are unsigned 15-bit fractions.  Scaled degrees/360.

88b

ACTUAL RR TRUNNION CDU.  RR trunnion angle CDU counter.  Defines the RR antenna position (along with shaft angle).  Updated from RR CDUs as trunnion angle changes.  This register is an unsigned 15-bit fraction.  Scaled degrees/360.

89a,89b

These words are known to differ by Luminary software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Y, Z MOMENT OFFSETS.  Calculated angular acceleration about Y and Z body axes due to the fact that the main engine is not exactly aligned with the center of gravity.  During powered flight these are calculated every 0.1 second at the beginning of the DAP cycle; otherwise these are zeroed in every DAP cycle.  Also zeroed at discrete times, such as fresh start and engine off.  Scaled (degrees/second2)/90.  Expected range is ±35 degrees/second2.
Luminary 1E
CH5MASK, CH6MASK.  Flagwords whose bits correspond to the bits of channel 5 and channel 6 respectively.  Only bits 1-8 are used.  When a bit is set, the autopilot regards the corresponding jet as being disabled.  The bits are set and cleared either automatically in response to changes in the LGC Thruster Pair Command Switches (channel 32/bits 1-8), or manually via the DSKY.

90a

POSTORKP.  Running sum of positive torque about control axis P.  Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32.

90b

NEGTORKP.  Running sum (always positive) of negative torque about control axis P.  Calculated every 0.1 second when DAP is running.  Scaled jetseconds/32.

91a

CHANNEL 11.  Output channel.  Bits are used to control engine on/off and for display parameter quantities.  Set 0 by a fresh start.  A restart zeroes all output channels by hardware means.  The program associated with restart or processing of a V37 program change preserves the value of bits 14, 13, and 1 and sets remaining bits to 0.  A restart then sets bit 13 to 1 if ENGONFLG (bit 7 of flagword 5) is 1 and sets bit 14 to 1 if ENGONFLG is 0.

Bit
Meaning
15
Not used.
14-13
Engine on-off.  A 1 in bit 14 and a 0 in bit 13 turns off the descent (ascent) engine.  A 0 in bit 14 and a 1 in bit 13 turns on the descent (ascent) engine.  All other combinations are ignored.
12-11
Not used.
10
Caution Reset signal (for display system lights).  A 1 indicates an Error Reset Key code (uplink or DSKY) has been received.
9
Used in hybrid simulation only.
8
Not used
7
Operator Error Light.  Set to 0 when an Error Reset Key code (uplink or DSKY) is received.  Set to 1 if various procedures (mainly DSKY, such as illegal noun/verb combinations) are not performed properly.
6
Flash verb and noun lights.  Set 1 to indicate that an operator action is required.
5
Key Release light.  Set 1 if program desires to use display system but external (DSKY or uplink) use of it is being made.  Also would be set to 1 if an internal or externally initiated monitor display (e.g. verb 16) had been started and then some DSKY button (except error reset) was depressed.  (It is lit if a request for operator response has been initiated and crew does not respond directly to it, but instead displays something else.)  Set 0 by key release keyboard input, and upon other instances (such as processing of an extended verb, or at the end of a V37 request) when display system is released by the internal program.
4
Temperature Caution light.  A 0 indicates stable member temperature within design limits.
3
Uplink Activity light.  A 1 indicates an uplink interrupt has been received.  Reset 0 when an error reset key code is received, a key release key code is received, or at the end of P27 (based on receipt of a "proceed" or "terminate" response).
2
Computer Activity light.  A 0 indicates no active "jobs" are to be performed.  Normally 0 during P00 except during the periodic state vector update or gyro compensation.  Bit is not set 1 if a "task" is performed, but retains its previous value.
1
ISS Warning light.  A 1 indicates an IMU fail indication or an IMU CDU fail indication or a PIPA fail indication has been received.  Setting of this bit may be inhibited (see bits 4, 3, and 1 of IMODES30).

91b

CHANNEL 12.  Output channel.  Bits are used for control of the rendezvous radar and IMU CDUs.  Set 0 by a fresh start.  A restart preserves bits 14, 12, 11, 10, 9, 6, 5, 4 and sets remaining bits to 0.  Set 0 by a hardware restart.

Bit
Meaning
15
ISS turn-on delay complete.  Set 1 at end of 90 second ISS turn-on delay and rest 0 about 10.24 seconds later.
14
Rendezvous radar enable.  A 1 in this bit enables rendezvous radar range and angle trackers to acquire target (lock on).  Set 1 when rendezvous radar antenna is within 0.5° of target.
13
Landing radar position command.  If this bit is set 1 and the antenna position switch is in LGC position, the LR antenna will move to position 2 (Hover).  Removing the discrete will not return the antenna to position 1.
12* Minus roll gimbal trim.  A 1 in this bit will cause the descent engine to rotate positively about the +Z axis causing the vehicle to rotate negatively about the +Z axis if the engine is thrusting.

*This bit will issue commands of opposite polarity to the names.  (Missile vs gimbal polarity problem).
11*
Plus roll gimbal trim.  A 1 in this bit will cause the descent engine to rotate negatively about the +Z axis causing the vehicle to rotate positively about the +Z axis if the engine is thrusting.

*This bit will issue commands of opposite polarity to the names.  (Missile vs gimbal polarity problem).
10*
Minus pitch gimbal trim.  A 1 in this bit will cause the descent engine to rotate positively about the +Y axis causing the vehicle to rotate negatively about the +Y axis if the engine is thrusting.

*This bit will issue commands of opposite polarity to the names.  (Missile vs gimbal polarity problem).
9
Plus pitch gimbal trim.  A 1 in this bit will cause the descent engine to rotate negatively about the +Y axis causing the vehicle to rotate positively about the +Y axis if the engine is thrusting.

*This bit will issue commands of opposite polarity to the names.  (Missile vs gimbal polarity problem).
8
Display inertial data.  A 1 in this bit commands the rendezvous radar CDU DACs to switch to the forward and lateral velocity meters during landing.
7
Not used.
6
Enable IMU CDU error counters.  Set to 1 during coarse align of IMU, and in order to permit output of error information to the FDAI attitude error needles (bit is set to 0 on initialization pass, then set to 1; the third pass is the first one with output to needles).
5
Zero IMU CDUs.  A 1 in this bit permits the IMU CDUs to be zeroed.  Bit set 1 at the same time as bit 4 of this channel when bit 6 of IMODES30 is set to 1 (IMU initialization) and reset 0 about 10.24 seconds before bit 6 of IMODES30 is reset 0.
4
Enable IMU coarse align.  Set 1 to specify IMU coarse align.  Also set 1 if middle gimbal angle exceeds 85°.
3
Not used.
2
Enable rendezvous radar error counter.  A 1 in this bit during designate causes error counter to be loaded with appropriate rate commands to drive antenna.  If display inertial data bit (bit 8 of this channel) is 1, a 1 enables error counter for driving inertial velocity display meter.
1
Zero rendezvous radar CDUs.  A 1 in this bit zeroes the CDUs.

92a

CHANNEL 13. Output channel.  Bits are used for various purposes.  Set 0 by a fresh start.  A restart or V37 sets bit 12 to 1, preserves bits 15-13 and 7-5 and sets remaining bits to 0.  Set 0 by a hardware restart.

Bit
Meaning
15
When this bit is set 1, an internal computer clock (TIME6) may be counted down at a 1600 pps rate.  This clock is used to control jet on-times.  Bit is reset to 0 by auto-pilot when no timed firings are being commanded.
14
Used in association with program interrupt #10.  Should always appear as 0.
13
Used in association with program interrupt #10.  Should always appear as 0.
12
Used in association with program interrupt #10.  Should always appear as 0.
11
Enable standby.  Set 1 at end of P06 to enable the "PRO" button to put the computer into a period of low power operation.
10
Test DSKY lights.  Set 0 if an error reset keycode is received.  Set 1 (for about 5 seconds) if a V35 input received.
9
Start "read" of rotational hand controller.  A 1 in this bit (together with a 1 in bit 8) starts a sequence which allows all the hand controller angles to be read into the counters.  Bit reset 0 when hand controllers are read.   Should not be set more than 30 times/sec.
8
Rotational hand controller counter enable.  A 1 in this bit allows the hand controller counters to receive inputs.
7
Telemetry word order code bit.  Will have a value of 1 (0 for words 1 and 51 only) when channel is telemetered.
6
Block inputs to uplink register.  Not set by program.
5
Not used.
4
Radar activity.  A 1 in this bit starts a sequence which reads the rendezvous radar or landing radar parameter selected by bits 3-1.  Bit set 0 when sequence is finished, and a radar rupt is generated by the hardware.
3-1
These three bits select the radar parameter to be read as follows:

Bit
   
3
2
1
   



0
0
0

-


0
0
1

RR range


0
1
0

RR range rate


0
1
1

-


1
0
0

LR X velocity


1
0
1

LR Y velocity


1
1
0

LR Z velocity


1
1
1

LR range

92b

CHANNEL 14.  Output channel. Bits are used for control of computer counter registers.  Set 0 by fresh start.  A restart or V37 preserves bit 6 and sets remaining bits to 0.  Caging command zeroes bits 15-6.  Set 0 by a hardware reset.

Bit
Meaning
15
A 1 in this bit causes output pulses from register used to drive X-axis IMU CDU error counter.  (IMU X-axis coarse align mode or error needles for yaw axis in FDAI mode).
14
A 1 in this bit causes output pulses from register used to drive Y-axis IMU CDU error counter.  (IMU Y-axis coarse align mode or error needles for pitch axis in FDAI mode).
13
A 1 in this bit causes output pulses from register used to drive Z-axis IMU CDU error counter.  (IMU Z-axis coarse align mode or error needles for roll axis in FDAI mode).
12
A 1 in this bit causes output pulses from the register used to drive rendezvous radar trunnion or lateral horizontal velocity meter depending on the mode of operation.  Reset 0 after counter register reduced to 0 (3200 pps).
11
A 1 in this bit causes output pulses from the register used to drive radar shaft or forward velocity meter depending on the mode of operation.  Reset 0 after counter register reduced to 0 (3200 pps).
10
A 1 in this bit generates gyro torquing pulses.  Set 1 when pulse torquing of gyros performed (for IMU compensation or for pulse torquing in P52 or P57 following acceptance of V06N93 display and for ENTR to 000138 checklist).  Also set 1 in P57 following coarse alignment after the N22 display.  Reset 0 when required number of pulses have been produced. 
9
A 1 in this bit indicates negative gyro torquing required (otherwise, torquing is positive).  Reset 0 after completion of routine.
8-7
These bits indicate the axis for gyro compensation (in the sequence Y, Z, X for inner, middle, outer).  Program resets to 002 when finished.

          
002
   
No axis

012

X-axis

102

Y-axis

112

Z-axis

6
A 1 in this bit enables gyro torquing power supply.  Set 1 at beginning of routine to generate gyro torquing pulses; remains 1 unless a fresh start done or a caging command.
5
Not used.
4
Thrust drive activity.  A 1 in this bit causes output engine pulses from the register used to throttle the engine.  Bit reset 0 after counter register reduced to 0 (3200 pps).
3
Altitude meter activity.  A 1 in this bit causes the contents of the altitude counter to be shifted out serially to either the altitude rate meter or the altitude meter depending on the setting of bit 2.  Bit reset 0 after shifting is completed.
2
Altitude rate select.  A 1 in this bit causes the contents of the altitude counter register to be shifted out to the altitude rate meter.  If this bit is 0 the contents will be shifted out to the altitude meter when bit 3 is set 1.  This bit should alternatively be set 1 and 0 for smooth meter driving.
1
Not used.

93a

NOTE:
For channel 30, the logic is inverted, i.e., 0 is considered "set" and 1 is considered "cleared."

CHANNEL 30.  Input channel.  Bits are used for various purposes.

Bit
Meaning
15
A 0 indicates stable member temperature within design limits.
14
A 0 indicates ISS has been turned on or commanded to be turned on.
13
A 0 indicates an IMU fail indication has been produced.
12
A 0 indicates an IMU CDU fail indication has been produced.
11
A 0 indicates an IMU cage command has been generated by the crew.
10
A 0 indicates G&N system is in control of S/C.
9
A 0 indicates IMU turned on and operating with no malfunctions.
8
Not used.
7
A 0 indicates a rendezvous radar CDU fail indication has been produced.
6
A 0 indicates a display of inertial data signal has been produced.
5
A 0 indicates an auto throttle control signal has been produced.
4
A 0 indicates an abort stage signal has been produced (abort with ascent stage).
3
A 0 indicates an engine armed signal has been produced.
2
A 0 indicates a stage verify signal has been produced (descent stage attached).
1
A 0 indicates an abort signal has been produced (abort with descent stage).

93b

NOTE:
For channel 30, the logic is inverted, i.e., 0 is considered "set" and 1 is considered "cleared."

CHANNEL 31.  Inputs from crew control devices, used by DAP.

Bit
Meaning
15
A 0 indicates an attitude control out detent signal has been produced (from attitude control assembly).
14
A 0 indicates auto stabilization mode has been selected.
13
A 0 indicates attitude hold mode has been selected.
12
A 0 indicates translation in -Z direction has been commanded.
11
A 0 indicates translation in +Z direction has been commanded.
10
A 0 indicates translation in -Y direction has been commanded.
9
A 0 indicates translation in +Y direction has been commanded.
8
A 0 indicates translation in -X direction has been commanded.
7
A 0 indicates translation in +X direction has been commanded.
6
A 0 indicates rotation in negative roll direction (minimum impulse), or a negative azimuth direction has been commanded.
5
A 0 indicates rotation in positive roll direction (minimum impulse), or a positive azimuth direction has been commanded.
4
A 0 indicates rotation in negative yaw direction (minimum impulse) has been commanded.
3
A 0 indicates rotation in positive yaw direction (minimum impulse) has been commanded.
2
A 0 indicates rotation in negative pitch direction (minimum impulse) has been commanded, or a negative elevation direction has been commanded.
1
A 0 indicates rotation in positive pitch direction (minimum impulse) has been commanded, or a positive elevation direction has been commanded.

94a

NOTE:
For channel 30, the logic is inverted, i.e., 0 is considered "set" and 1 is considered "cleared."

CHANNEL 32.  Input channel.  Additional crew input to DAP, etc.

Bit
Meaning
15
Not used.
14
A 0 indicates "proceed key" is depressed.
13
Not used.
12
Not used.
11
Not used.
10
A 0 indicates an apparent gimbal fail signal has been produced.
9
A 0 indicates a gimbal off signal has been produced.
8
A 0 indicates a thruster 10&11 fail signal has been produced.
7
A 0 indicates a thruster 9&12 fail signal has been produced.
6
A 0 indicates a thruster 13&15 fail signal has been produced.
5
A 0 indicates a thruster 14&16 fail signal has been produced.
4
A 0 indicates a thruster 6&7 fail signal has been produced.
3
A 0 indicates a thruster 1&3 fail signal has been produced.
2
A 0 indicates a thruster 5&8 fail signal has been produced.
1
A 0 indicates a thruster 2&4 fail signal has been produced.

94b

NOTE:
For channel 30, the logic is inverted, i.e., 0 is considered "set" and 1 is considered "cleared."

CHANNEL 33.  Input channel.  Bits are used for hardware status and command information.  Bits 15-11 are "flip-flop" bits (reset by a channel "write" command).  They are reset in the T4RUPT loop every 0.48 second.  They are also reset by a restart.

Bit
Meaning
15
A 0 indicates the LGC oscillator has stopped.
14
A 0 indicates repeated presence of the following alarms:  restart, counter fail, voltage fail (standby mode), and scaler double alarm.  An alarm test will also turn it on.
13
A 0 indicates one of the following:  no pulses have arrived from a PIPA during a 312.5 μsec. period; both a + and a - pulse occurred simultaneously; only + (-) pulses occurred for a period greater than 1.28 seconds.
12
A 0 indicates downlink end pulses occurred at a rate greater than 100 pps.
11
A 0 indicates uplink rate is greater than 6.4K pps.
10
This bit is always 1 since the block uplink signal is wired in accept position.
9
A 0 indicates a landing radar range low scale signal has been produced.
8
A 0 indicates a landing velocity good signal has been produced.
7
A 0 indicates a landing radar position #2 signal has been produced.
6
A 0 indicates a landing radar position #1 signal has been produced.
5
A 0 indicates a landing radar range data good signal has been produced.
4
A 0 indicates a rendezvous radar data good signal has been produced.
3
A 0 indicates a rendezvous radar range low scale signal has been produced.
2
A 0 indicates a rendezvous radar power on auto signal has been produced.
1
Not used.

95a,95b,96a,96b,97a,97b,98a,98b,99a,99b,100a

DSPTABs.  The eleven registers, DSPTAB through DSPTAB+10D, indicate the status of the DSKY displays.  If bit 15 through 12 are 0001, the next 11 bits will indicate the actual status of the DSKY displays; if bits 15 through 12 are 1110, the next 11 bits indicate the "ones" complement of the status to which the LGC will command the DSKY display.  Bits 11-1 of DSPTAB+0 through DSPTAB+10D are decoded as follows:





Bit Assignments
DSPTAB
Register
    
Downlink
Word No.
    
Bit 11
Bits 10-6
Bits 5-1
DSPTAB+0

45a

-R3S
R3D4
R3D5
DSPTAB+1
45b

+R3S
R3D2
R3D3
DSPTAB+2
46a


R2D5
R3D1
DSPTAB+3
46b

-R2S
R2D3
R2D4
DSPTAB+4
47a

+R2S
R2D1
R2D2
DSPTAB+5
47b

-R1S
R1D4
R1D5
DSPTAB+6
48a

+R1S
R1D2
R1D3
DSPTAB+7
48b



R1D1
DSPTAB+8D
49a


ND1
ND2
DSPTAB+9D
49b


VD1
VD2
DSPTAB+10D
50a


MD1
MD2

R3D1 stands for digit one of the third register and VD1 stand for the first digit of the verb display, etc.  For the right character of a pair, bit 5 is the MSB with bit 1 the LSB.  For the left character of a pair, the MSB is bit 10 with bit 6 the LSB.  Bit 11 of some of the DSPTABs contains discrete information, a one indicating that the discrete is on.  For example, a one in bit 11 of DSPTAB+1 indicates that R3 has a plus sign.  If the sign bits associated with a given register are both zeros, then the content of that particular register is octal; if either of the bits is set, the register content is decimal data.

The five bit codes associated with the digits are as follows:

                
MSB



LSB
0
1
0
1
0
1
1
0
0
0
1
1
2
1
1
0
0
1
3
1
1
0
1
1
4
0
1
1
1
1
5
1
1
1
1
0
6
1
1
1
0
0
7
1
0
0
1
1
8
1
1
1
0
1
9
1
1
1
1
1
Blank
0
0
0
0
0

The following is a diagram of the DSKY face showing positions of the different digits:

                             Program
┌───────┬───────┐ │ MD1 │ MD2 │ └───────┴───────┘
Verb Noun
┌───────┬───────┐ ┌───────┬───────┐ │ VD1 │ VD2 │ │ ND1 │ ND2 │ └───────┴───────┘ └───────┴───────┘
Register 1
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R1D1 │ R1D2 │ R1D3 │ R1D4 │ R1D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘
Register 2
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R2D1 │ R2D2 │ R2D3 │ R2D4 │ R2D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘

Register 3
┌───────┬───────┬───────┬───────┬───────┬───────┐ │ ± │ R3D1 │ R3D2 │ R3D3 │ R3D4 │ R3D5 │ └───────┴───────┴───────┴───────┴───────┴───────┘

100b

DSPTAB+11D.  This register drives relays for the display lights.  The bit assignments are:

Bit
Assignment
1
This bit differs by Lunar Module software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D
Not used.
Luminary 1E
Priority Display
2
This bit differs by Lunar Module software version.

Version
Description
Luminary 1, 1A, 1B, 1C, 1D Not used.
Luminary 1E
No DAP Control
3
Landing Radar Velocity Fail
4
No Attitude
5
Landing Radar Altitude Fail
6
Gimbal Lock
7

8
Tracker
9
Program Caution

If bits 15 through 12 of DSPTAB+11D are 1000, the last 11 bits indicate the state to which the LGC will command the relays; if bits 15 through 12 are 0000, the last 11 bits indicate the actual state of the relays.  A one indicates that the discrete is on.



Proofed.  Last edited by RSB, 2025-04-06