Real Time Commanding using Command Panels


Preface
This page is an edited version of the:

Universal CSM Console Handbook
S/C 106 and subsequent vehicles
Flight Control Division
Manned Spacecraft Center, Houston, May 1969

Section D "Communication and Command"
Subsection SCP No. CSM-D5 "Real-Time Commanding"
Revision A, 17 April 1969
By L.V. Howard

This page has been created based on the original document but with a different layout to improve readability and searchability.

The original text has been retained as much as possible; only some errors in spelling have been corrected, and missing words and some titles have been added. Further, the call name "RTC" has been changed into the call name "CCATS RTC" to make a clear distinction between a CCATS Real-Time Controller and a Real-Time Command.
Comments have been added in green to provide some background information, some clarification and some context.


Purpose of document
This document presents the operating procedures for the Universal Command Systems components on the EECOM systems engineer's console in the Mission Operations Control Room. These components are the interface between the flight controller and the computer systems through which all commands must pass for normal ground control of spacecraft equipment. The evident necessity for safeguards to ensure proper command transmission is reflected in hardware and software design. However, safe commanding ultimately becomes the responsibility of Flight Control personnel in correctly exercising operational procedures. Those procedures are described in the following sections of this report.
Content
  1. The Push Button Indicators (PBI's) of the Universal Command System

  2. The Command Control Module (CCM)

  3. The Digital Select Matrix Module (DSM)

  4. The RTC PBI Modules (RCM)

  5. RTC Commanding Procedures

  6. Command Sequence Completion

1.The Push Button Indicators (PBI's) of the Universal Command System
The command panels for the EECOM engineer's console incorporate components of the Universal Command System.
The panels include the ones shown below.
The functions associated with the PBIs on each module are described in this section.
The PBIs enable the EECOM Flight Controller to communicate with the Universal Command System to control spacecraft systems remotely and upload data and instructions to the onboard computer of the spacecraft.
Command Panels/Modules

Digital Readout Module (DRM)
Command Control Module (CCM)

Digital Select Matrix Module (DSM)
Real-Time Command (RTC)
Push Button Indicator (PBI) Module (RCM)

Data Entry Module (DEM)
No part of the EECOM systems engineer's console
The number of consoles equipped with command panels was reduced from 8 to 4.
The five Command Panels shown above were used by the following nine Flight Controllers (FCs) in the Mission Operations Control Room (MOCR) in the Apollo missions initially:
BOOSTER, RETRO, GUIDO, EECOM, GNC, TELMU, CONTROL and INCO.
However, if I am not mistaken, in the Apollo 13 mission and subsequent missions, only the consoles of four Flight Controllers were equipped with Command Panels:
BOOSTER, GUIDO, CONTROL and INCO.

One set of command panels for the Flight Dynamics Group
Initially the consoles of RETRO and GUIDO were equipped with command panels.
RETRO, FIDO and GUIDO constituted the Flight Dynamics Group in MOCR. A redistribution of tasks resulted in enabling GUIDO only to send commands to the launch vehicle and the spacecrafts.

RTC panels from EECOM to INCO console
The EECOM console was equipped with the command panels DRM, DSM, CCM and two RTCs.
These EECOM command panels were related to onboard systems for communications. It was decided that after the Apollo 12 mission the task related to communication would be transferred to FC INCO. The INCO console was already equipped with the command panels DRM, DSM, CCM and two RTCs. Since the DRM, DSM and CCM were general command panels, only the two EECOM-specific RTC panels had to be transferred.

Where did the GNC command panels go?
I don't know what happened with the GNC RTC panels.
The FC GNC should have been able to have active control over the guidance, navigation and control systems of the Apollo CSM remotely. Maybe this task was left to GUIDO.

TELMU (LM EECOM) command panels to INCO
It seems logical to me that, like in the case of EECOM, the command panels of TELMU (LM EECOM) were transferred to INCO. Maybe the RTC panels have been rearranged to facilitate real-time commanding to the EECOM CSM and the EECOM LM systems from the INCO console.

CONTROL (LM GNC) command panels
The CONTROL (LM GNC) console remained equipped with command panels. It would have been logical that, like in the case of GNC, commanding the LM GNC systems would have been left to GUIDO too. But it might have been decided to have some redundancy here. It is not unthinkable that there could have been scenarios in which the GNC systems of both the CSM and the LM needed to be commanded remotely simultaneously.

EECOM console
The document, discussed here, relates to command panels used by FC EECOM to control Apollo CSM spacecrafts with serial number 106 and subsequent numbers. The list of EECOM RTC commands in section 4 pertains to the Saturn IB - Apollo stack AS-205, which was used for the Apollo 7 mission and of which the Apollo CSM spacecraft had serial number 101. It might probably be fair to assert that the EECOM console was only equipped with command panels for Apollo missions 4, 6, 7, 8, 8 and 10, which corresponds to CSM serial numbers 017, 014, 101, 103, 104 and 106.

In the table below is shown with which Apollo missions the CSM serial numbers correspond.

Mission NameLaunch VehicleApollo CM/SM
Serial No.Serial No.
Apollo 1ASaturn IBAS-201009
Apollo 2Saturn IBAS-202011
Apollo 3Saturn IBAS-203----
Apollo 1Saturn IBAS-204012
Apollo 4Saturn VAS-501017
Apollo 5Saturn IBAS-204----
Apollo 6Saturn VAS-503014
Apollo 7Saturn IBAS-205101
Apollo 8Saturn VAS-503103
Mission NameLaunch VehicleApollo CM/SM
Serial No.Serial No.
Apollo 9Saturn VAS-504104
Apollo 10Saturn VAS-505106
Apollo 11Saturn VAS-506107
Apollo 12Saturn VAS-507108
Apollo 13Saturn VAS-508109
Apollo 14Saturn VAS-509110
Apollo 15Saturn VAS-510112
Apollo 16Saturn VAS-511113
Apollo 17Saturn VAS-512114

Configuration of the EECOM console for the Apollo missions 4, 6, 7, 8, 9 and 10
The five command panels are outlined in red:

  • the Digital Readout Module (DRM);
  • the Digital Select Matrix Module (DSM);
  • the Command Control Module (CCM) and;
  • two Push Button Indicator Modules (RCM).

Configuration of the EECOM console for the Apollo 11 mission
After the Apollo 10 mission the command panels have been moved to the INCO console.

Three types of Push Button Indicators

There are three types of PBI functions, which are described below:

  1. Execute PBIs
    Depression of an Execute PBI results in CCATS transmitting an Execute Command Request (ECR) to the MSFN, provided the console is site selected and an enabled vehicle is selected.
    Light logic for Execute PBIs:
    1. Console Disabled:
      Initial depression of an Execute PBI results in illumination of the upper half. A second depression extinguishes the upper half to verify the CCATS-PBI interface.
      It is necessary to extinguish the PBI upper half prior to enabling the console.
    2. Console Enabled:
      Upper halves of all enabled Execute PBIs illuminate. Depressing an Execute PBI causes CCATS to output the related Execute and the upper half remains illuminated.
    3. Receipt of Site Validation CAP Word:
      SITE VAL portion of SITE VAL/RSCC INVAL PBI illuminates.
    4. Receipt of S/C Verification CAP Word:
      CCATS illuminates lower half of Execute PBI and extinguishes SITE VAL.
    5. Reinitiation of Execute PBI:
      Upper Half Illuminates
      Lower Half Extinguishes
      Execute is Retransmitted
      SITE VAL, RSCC INVAL, S/C REJ or GND REJ PBIs are extinguished if previously illuminated.
    6. Console Disabled After S/C Verification but prior to depressing the VERIFY CLEAR PBI:
      Upper Half of Execute PBI extinguishes.
      Lower Half remains illuminated.
    7. Depression of an Execute PBI with lower half illuminated:
      Lower Half Extinguishes
      Upper Half illuminates
    8. Depression of VERIFY CLEAR in ENABLE or DISABLE MODE:
      Lower Halves of Execute PBIs will extinguish
    9. Console returned to ENABLE prior to depressing VERIFY CLEAR PBI:
      CCATS illuminates upper halves of all Execute PBIs
      Lower halves of verified Execute PBIs remain illuminated
      Lower halves of other Execute PBI's are extinguished.

  2. Program Request (PR) PBI's
    Depression of a PR PBI instructs either CCATS or the RSCC to perform certain functions.

  3. R/S or S/C Action Indicators
    Illumination of these PBIs indicates action or status of the spacecraft, the remote site, or the R/S-CCATS interface.

2.The Command Control Module (CCM)
The purpose of the CCM Push Button Indicators explained

  1. ENABLE/DISABLE PBI
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Alternate action PBI (enable or disable)
    2. In DISABLE mode (normal state):
      Uplink capability is deactivated, and upper halves of Execute PBIs are extinguished.
      Active functions:
      • Select RTC numbers on DSM PC/M&O
      • UHF/USB
      • VEHICLE SELECT PBI's
      • SITE SELECT/CARRIER ON indicator
      • DSM SELECT CLEAR
      • VERIFY CLEAR
      • LOAD MODE /RTC MODE
      • DSM NUMERICAL PBIS.
    3. In ENABLE Mode:
      Console is enabled for commanding.
      Upper halves of all enabled Execute PBIs are illuminated.
      Active functions:
      • Same as in Disable mode

  2. LOAD MODE / RTC MODE PBI
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Alternate Action PBI (Load or RTC Mode)
    2. Illuminated half indicates which uplink capability is available.
    3. In RTC Mode (normal state for EECOM console):
      CCATS evaluates RTC numbers selected on DSM.
      INVALID DSM inputs to CCATS:
      Depression of LOAD INITIATE or RTC INITIATE PBI with other than three digits selected on DSM or depression of the LOAD INITIATE PBI with three DSM digits selected.
    4. In LOAD Mode:
      CCATS evaluates load numbers selected on the DSM.
      Selection of more than four digits is not recognised by CCATS.
      Invalid DSM Inputs to CCATS:
      Depression of LOAD or RTC INITIATE PBI with less than four digits selected.
      Depression of RTC INITIATE PBI with four digits selected.
    5. For invalid inputs, the lower half of the DSM SELECT / CLEAR PBI will illuminate, any command outputs will be inhibited, and a printout will be provided at the CCATS Command Controller (CCC) position.

  3. UHF/USB PBI
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Alternate Action PBI (UHF or USB)
    2. CCATS retains the selected carrier to instruct the RSCC as to the carrier on which to uplink commands from the EECOM console.
    3. The CSM EECOM UHF/USB select PBI controls selection of carrier for the Flight Director and Flight Dynamics Officer for missions with a CSM involved.

  4. SITE SELECT/CARRIER ON PBI
    TYPE: Indicator

    STATEDESCRIPTION
    Illuminated Green Console selected to a site with carrier on which agrees with the state of UHF/USB PBI.
    Illuminated Amber Console selected to a site with no carrier on or carrier does not agree with UHF/USB PBI.
    Extinguished Console Deselected.

    With the exception of the Command Support Control Console, any number of the commanding consoles can be selected for a site at a given time. Any console can be selected for only one site at a time.

  5. FC/M&O PBI
    TYPE: Indicator

    STATEDESCRIPTION
    FC FC and M&O command panels enabled.
    Command processor output enabled.
    M&O data call up capability enabled.
    RTCC input enabled.
    FC light indications active.
    M&O FC and M&O command panels disabled except M&O MED capability to override inhibit functions for program checkout and troubleshooting.
    Output of command processor disabled except for load transfer.
    M&O data call up capability enabled.
    RTCC input controlled by M&O.
    FC light indications active only to show the state selected while in FC mode.

  6. MAP OVERRIDE
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Alternate action PBI (illuminated or extinguished)
    2. Normal state is extinguished.
    3. When illuminated, CCATS sets a bit in initiated executes, which results in the RSCC uplinking the commands without regard to MAP indication.

  7. DATA REJ / TM REJ
    TYPE: Indicator
    DESCRIPTION:
    1. This PBI activity is applicable only to the GUIDANCE console.
    2. Normal state is extinguished.
    3. Upper half illuminates when CAP words indicate "no compare" due to bad data.
    4. Lower half illuminates when CAP words indicate "no compare" due to TM downlink problems.
    5. Either half is extinguished when the PBI is depressed.

  8. VEHICLE SELECT PBI's
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Any command console can select any vehicle. The selection applies to RTC Executes only.
    2. Only one vehicle can be selected at any one time.
    3. Depression of a PBI deselects a previously selected vehicle, extinguishes that light, and illuminates the newly selected PBI.

  9. DSM SELECT/CLEAR
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Normal state is extinguished.
    2. Upper half illuminates when a valid RTC number is selected.
    3. Lower half illuminates when an invalid RTC number is selected.
    4. Depression of the PBI extinguishes either half of DSM SELECT/CLEAR on the CCM, extinguishes SC REJ / GND REJ PBI on the DSM, clears the DRM indicators, and clears logic on the DSM.

  10. VERIFY CLEAR
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Normal state is extinguished
    2. Depression results in CCATS extinguishing the lower half (S/C Verification Indication) of all execute PBIs which are illuminated.

3.The Digital Select Matrix Module (DSM)
The purpose of the DSM Push Button Indicators explained

  1. RTC INITIATE PBI
    TYPE: Execute
    DESCRIPTION:
    1. Normal state is extinguished.
    2. Depressing the PBI with the console enabled in RTC mode with the appropriate carrier selected causes CCATS to transmit a valid RTC selected on the DSM to the R/S.

  2. VERB INITIATE PBI
    TYPE: Execute
    DESCRIPTION
    1. Normal state is extinguished.
    2. Depression of the PBI with the console enabled causes CCATS to transmit the execute to the selected R/S to uplink the selected load preamble.

  3. LOAD INITIATE PBI
    TYPE: Execute
    DESCRIPTION
    1. Normal state is extinguished.
    2. Depressing the PBI with the console enabled causes CCATS to transmit the execute to the selected R/S to uplink the data portion of the selected load.

  4. LINE/LINE INITIATE PBI
    TYPE: Execute
    DESCRIPTION
    1. Normal state is extinguished
    2. Depression of the PBI with the console enabled causes CCATS to transmit the EXECUTE to the selected R/S to result in line-by-line correction of the data words found incorrect by the buffer compare.

  5. COMPARE INITIATE PBI
    TYPE: RSCC Program Request
    DESCRIPTION:
    1. Normal state is extinguished
    2. Depressing the PBI with the console enabled causes CCATS to transmit the EXECUTE to the selected WS to perform a buffer compare on the selected load.
    3. Upper Half of PBI is illuminated when console is enabled.

  6. COMMAND TERMINATE PBI
    TYPE: RSCC Program Request
    DESCRIPTION:
    1. Normal state is extinguished.
    2. With the console disabled:
      Execute initiate is prohibited.
      PBI depression causes CCATS to illuminate the upper half.
      Second depression causes CCATS to extinguish the PBI
      (Loop Check).
    3. With the console enabled:
      Upper half of the PBI illuminates. Depressing the PBI causes CCATS to transmit the Execute to the selected R/S to terminate any uplinking in process.
      Receipt of a CAP word acknowledging termination illuminates the lower half of the PBI.

  7. NUMERICAL PBIs
    TYPE: CCATS Program Request
    DESCRIPTION:
    1. Normal state is extinguished.
    2. Depression causes CATS to display the number in the right-land window of the readout module.
      As succeeding numbers are selected, the numbers in the readout window shift to the left.
      Each PBI can be depressed more than once.
      The final number displayed in the readout module is the selected load or RTC number.
      The readout module and the PBI logic are cleared by depressing the DSM SELECT CLEAR PBI.

  8. SITE VAL / INVALID REQUEST PBI
    TYPE: Indicator
    DESCRIPTION:
    1. Normal state is extinguished.
    2. Upper half (SITE VAL):
      Illuminates as result of R/S accepting an Execute or PR and returning the appropriate CAP word.
      Extinguishes upon receipt of an S/C verification, receipt of a GND REJ, receipt of an S/C REJ, initiation of an Execute, or by depression of the PBI.
    3. Lower half
      Illuminates upon receipt of a SITE VAL word indicating that an Execute was received by the R/S but was not processed due to some function in progress.
      Extinguishes upon initiation of an Execute or by depressing the PBI.

  9. S/C REJ / GND REJ PBI
    TYPE: Indicator
    DESCRIPTION:
    1. Normal state is extinguished.
    2. The lower half illuminates if a ground equipment problem at the R/S has prevented uplinking.
    3. The upper half is illumminated by CCATS for receipt of an R/S CAP word indicating an S/C rejection of a command.
    4. The lighting states can be extinguished by depressing the PBI, reinitiating any execute, or by depressing the DSM SELECT/CLEAR PBI.

4.The RTC PBI Modules (RCM)

Real-Time Command (RTC) Push Button Indicator (PBI) Module (RCM) No.1 of the EECOM console



Real-Time Command (RTC) Push Button Indicator (PBI) Module (RCM) No.2 of the EECOM console

The purpose of the RCM Push Button Indicators explained

  1. All RTC PBIs are Execute type.
  2. Normal state is extinguished.
  3. Depression of the enabled PBI with the console enabled, site selected, vehicle selected, and in FC mode will result in a single Execute being transmitted to the R/S. The single Execute will result in uplinking either single- or multiple-word regular RTCs or multiple-word special RTCs.
  4. RTCs assigned to individual PBIs are accessible via the DSM.
  5. The commands which can be transmitted using the RTC PBIs, the DSM, or either are listed in the following tables:

    AS-205 CSM COMMAND LIST

    1. COMMANDS NOT ON RTC PSI PANELS:
    RTC (OCTAL) DESCRIPTION DSM CODE
    104 & Subs
    ----CTE UPDATE601
    ----UDL TEST A602
    ----UDL TEST B603
    04CREW ALARM OFF604
    05CREW ALARM ON605

    2. COMMANDS ON CONSOLE 7 (EECOM) PBI PANELS
    RTC (OCTAL) COMMAND DESCRIPTION DSM CODE
    104 & Subs
    65BIT RATE LOW606
    64, 71BIT RATE HIGH607
    64, 70BIT RATE RESET608
    32, 37REAL TIME PCM ON609
    33, 37REAL TIME PCM OFF610
    32, 36REAL TIME PCM RESET 611
    41, 45FM ON (TAPE)612
    41, 44FM OFF (TAPE OFF)613
    40, 51BACK UP VOICE FM OFF614
    40, 50USB MODE RESET615
    72, 77DSE TAPE FORWARD616
    73, 76DSE TAPE STOP617
    73, 77DSE TAPE REWIND618
    72, 76TAPE CONTROL RESET619
    62, 67DSE ELECT RECORD620
    63, 66DSE ELECT OFF621
    63, 67DSE ELECT PLAYBACK622
    62, 66DSE ELECT RESET623
    52, 57SELECT CSM PLAYBACK DATA624
    53SELECT LM PLAYBACK DATA625
    52, 56PAYBACK MODE RESET626
    43, 46POWER AMPLIFIER OFF627
    43, 47POWER AMPLIFIER LOW628
    42, 47POWER AMPLIFIER HIGH629
    42, 46POWER AMPLIFIER RESET630
    23RANGING DISABLE631
    22, 27RANGING ENABLE632
    22, 26RANGING RESET633
    30, 32SALVO RESET 1634
    70, 72SALVO RESET 2635
    74ANTENNA RESET636
    75D OMNI ANTENNA SELECT637
    10ACE CMC "0" ENABLE638
    11ACE CMC "0" DISABLE639
    12ACE CMC "1" ENABLE640
    13ACE CMC "1" DISABLE641

    3. SALVO RESET 1 RESETS
    RTC (OCTAL) COMMAND DESCRIPTION
    00ABORT LIGHT A OFF
    04CREW ALARM OFF
    06ABORT LIGHT B OFF
    22, 26RANGING RESET
    32, 36REAL TIME PCM RESET

    A SALVO RESET 1 contains five RTCs which are submitted simultaneously.
    The last two RTCs mentioned in table 3 can also be submitted individually by depressing a PBI as listed in table 2.

    4. SALVO RESET 2 RESETS
    RTC (OCTAL) COMMAND DESCRIPTION
    40, 50USB MODE RESET
    42, 46POWER AMP RESET
    52, 56PLAYBACK MODE RESET
    62, 22DSE ELECT RESET
    72, 76TAPE CONTROL REST
    64, 70BIT RATE RESET
    74ANTENNA RESET

    A SALVO RESET 2 contains seven RTCs which are submitted simultaneously.
    Each of these seven RTCs can also be submitted individually by depressing a PBI as listed in table 2.


    The serial number of the CSM used with launch vehicle AS-205 was 101. The whole AS-205 stack was used for the Apollo 7 mission.
    However,, the document this page relates to presents the real-time commanding procedures for CSM spacecrafts with serial number 106 and beyond, which relates to the Apollo 10 mission and the subsequent Apollo missions.
    The question is whether the list of commands shown above is valid for all the Apollo missions after the Apollo 7 mission.


5.RTC Commanding Procedures
The RTC commanding procedures are described in terms of the coordination required with other positions during command activity. The PBI indications are presented in brief form, with detailed PBI functions available in the previous section if required.

1. At time: AOS-40 MIN
Note any S/C or R/S equipment problems not previously discussed, keyhole positions, and peculiar circuit margins.
Note commands which affect other flight controllers.
Resolve conflicts with command activity of other positions and note times during the pass when additional coordination may be required.

2. At time: AOS-5 MIN
  1. With control function DISABLE selected, set up the Command Control Module, the DSM and RTC PBI panels:

    PANEL PBI INDICATION
    Command Control Module (CCM) ENABLE/DISABLE
    LOAD MODE / RTC MODE
    UHF/USB
    SITE SELECT / CARRIER ON
    FC/M&O
    MAP OVRD
    DATA REJ / TM REJ
    VEHICLE SELECT PBIs
    DSM SELECT/CLEAR
    VERIFY CLEAR
    		 DISABLE
    RTC MODE
    AS REQUIRED
    ILLUMINATED AMBER
    FC
    MAP OVRD
    EXTINGUISHED
    AS REQUIRED
    EXTINGUISHED
    EXTINGUISHED
    Digital Select Matrix Module (DSM)ALL PBIsEXTINGUISHED
    RTC PBI PANELSPBIs OF RTCs TO BE TRANSMITTEDUPPER HALF ILLUMINATED

Digital Readout Module (DRM)
Command Control Module (CCM)

Digital Select Matrix Module (DSM)
Real-Time Command (RTC)
Push Button Indicator (PBI) Module (RCM)
  1. Select Console ENABLE.

    PANEL PBI INDICATION
    Command Control Module (CCM) ENABIE/DISABLE
    		 ENABLE
    Digital Select Matrix Module (DSM) RTC INITIATE
    VERB INITIATE
    LOAD INITIATE
    LINE/LINE INITIATE
    COMPARE INITIATE
    CMD TERMINATE
    		 RTC INITIATE
    VERB
    LOAD
    LINE/LINE
    COMPARE
    CMD
    RTC PBI PANELSENABLED RTC PBIsUPFER HALF ILLUMINATED

    NOTE: Only changes from previous indications are listed.

    I assume that the lower half of the RTC INITIATE PBI on the DSM should be illuminated as well to indicate that the command panels have been put in the RTC MODE.


Digital Readout Module (DRM)
Command Control Module (CCM)

Digital Select Matrix Module (DSM)
Real-Time Command (RTC)
Push Button Indicator (PBI) Module (RCM)
3. At time: AOS
  1. Verify SITE SELECT / CARRIER ON PBI is green and receives "GO" from CCATS RTC on the RTC loop. Any command consoles may be selected for a given site at one time except command support control console. Any one console may be selected for only one site.
  2. If the DSM is to be used:
    1. Select the DSM code of the command to be transmitted, using the numerical PBIs on the DSM.
    2. Verify that the DSM code in the readout window agrees with the required code.
    3. At the appropriate time to command, depress the RTC INITIATE PBI on the DSM.
      (The lower half of the PBI will extinguish on depression, if illuminated).
    4. Observe illumination of SITE VAL on the DSM.
      Validation check by Remote Site of RTC uplink request is OK.
    5. Observe that the lower half of the RTC INITIATE PBI illuminates and that the SITE VAL PBI extinguishes.
      Validation check by spacecraft of RTC is OK.
    6. If additional commands are to be transmitted, select the DSM code of the next command, repeating step. 1-5 above.
    7. When commands have been transmitted, depress the console DISABLE PBI.
    8. Observe that the upper half of the RTC INITIATE PBI extinguishes.
    9. If the record of EXECUTES as shown by lower half illumination is no longer required, depress VERIFY CLEAR.
    10. Observe that the lover half of the RTC INITIATE PBI extinguishes.
  3. If the RTC PBIs are to be used:
    1. At the appropriate time to command, depress the required RTC PBI.
      (The lower half of the PBI will extinguish on depression, if illuminated.)
    2. Observe illumination of SITE VAL on the DSM.
      Validation check by Remote Site of RTC uplink request is OK.
    3. Observe that the lower half of the RTC PBI illuminates and that the SITE VAL PBI extinguishes.
      Validation check by spacecraft of RTC is OK.
    4. If additional commands are to be transmitted, select the required PBI and repeat steps 1, 2, and 3.
    5. When commands have been transmitted, depress console DISABLE PBI.
    6. Observe that the upper halves of the RTC PBIs extinguish and that lower halves remain illuminated.
    7. If the record of executes as shown by lower half illumination is no longer required, depress VERIFY CLEAR.
    8. Observe that lower halves of RTC PBIs extinguish.
  4. If SITE VAL indication is not received:
    Determine from "CCATS RTC" on the RTC loop if the command was transmitted from MCC-H.
    • If it was transmitted:
      Attempt a retransmission.
      If no result, determine the extent of the problem as is possible from "CCATS RTC". Request selection to an alternate site if advisable.
    • If it was not transmitted:
      Determine the cause, if known. Attempt retransmission if the problem is unidentified. If no result, go to console disable and perform PBI-CCATS interface check:
      • If positive indications:
        Inform the Flight Director and request that the command be transmitted by R/S M&O.
      • If negative indications:
        Request "CCATS RTC" to transmit the command from the Command Support Control Console.
        Inform the Flight Director of the results.
  5. If S/C Verification is not received:
    1. If GND REJ PBI on the DSM is illuminated:
      Observe SITE VAL PBI illuminated then extinguished.
      Determine the extent of the problem from "CCATS RTC". Request selection to an alternate site if advisable.
      Retransmit the command:
      Depression of RTC INITIATE or RTC PBI will extinguish the GND REJ PBI.
      Monitor for SITE VIE and S/C verification.
      If GND REJ again occurs, inform the Flight Director of the problem, action, and status.
    2. If S/C REJ PBI on the DSM is illuminated:
      Observe SITE VAL PBI illuminated then extinguished.
      Determine from "COMM" if S/C equipment problem exists.
      If the problem is not evident, attempt a retransmission.
      If unsuccessful, inform the Flight Director.
      If the problem is evident, determine the effect on upcoming activity, the alternate methods available, and the current status. Inform Flight Director.

6.Command Sequence Completion
  1. Announce to "GUIDANCE" and "CCATS RTC" on the RTC loop or MOCR DYNAMICS loop that commanding is complete.
  2. Report any abnormal indications of equipment status, to the Flight Director.




Acronyms
ACE Audio Center Equipment
AOS Acquisition Of Signal
AVP Address Verification Pulse
CAP Command Analysis Pattern
CCATS Communication, Command and Telemetry System
CCATS RTC CCATS Real Time Controller
CCM Command Control Module
CM Command Module
CMC - - - - Command Module Computer ?
CRP Computer Reset Pulse
CSM Command & Service Module
DEM Data Entry Module
DRM Digital Readout Module
DSE Data Storage Equipment
DSM Digital Select Matrix Module
FC Flight Controller
GND Ground
INVAL Invalid
MAP Message Acceptance Pulse
MCC-H Mission Control Center Houston
MOCR Mission Operations Control Room
M&O Maintenance & Operations
OVRDOverride
PBI Push Button Indicator
PCM Pulse Code Modulation
PR Program Request
RCM RTC PBI Module
REJ Reject
RTC Real-Time Command
R/S Remote Site
R/T Real Time
SM Service Module
S/C Spacecraft
UHF Ultra High Frequency
USB Unified S-Band
The Maintenaonce & Control (M&O) team of a Remote Site can request an uplink of data or commands on directions from Flight Control in Houston,

References
  1. Universal CSM Console Handbook
    S/C 106 and subsequent vehicles
    Section D-5 Flight Control Division
    Manned Spacecraft Center, Houston, May 1969

  2. AS-508; MCC / MSFN; Mission Configuration / System Description
    March 1970
    by the Manned Spacecraft Center, Flight Support Division

  3. Ref




Site Map |  References |  Change History

Copyright 2025 by Sander Panhuyzen
Comments and questions welcome. All pictures and drawings contained on these pages are the author's, unless otherwise noted. No unauthorized reproduction without permission.