Date: August 12, 1994 To: D. Muhonen From: C. Cazeau/ SOHO FOT Subject: GOLF - FOT Meeting Minutes Ref. #: SH-FOT-MN-940812-011 The first of the FOT - Experimenter Interface meetings was held at GSFC on August 5 and 8 with the GOLF experiment. The meetings are being conducted to identify how the FOT will determine health and safety of each experiment, and to identify experiment activities the FOT is responsible to perform. The meeting also identifies the activities the FOT will conduct for each experiment during a GSCT. The meeting minutes follow. Regards, Carline J. Cazeau SOHO Flight Operations Team #################################################### GOLF EXPERIMENT MEETING MINUTES Instrument: GOLF Attendees: J. Charra, N. Petrou,D. Muhonen, K. Walyus, A. Wiener, C.Cazeau, C. St.Cyr, S. Vaghi (telecon), P. Martens (telecon), M. Hill Date: 05 & 08 Aug 94 Location: SOHO EOF, GSFC ESA QUESTIONS asked by Sergio Vaghi: - Does any mode of this experiment produce "jitter" or other disturbances? -- GOLF does not produce jitter or other disturbances for the other experiments. - Does any mode have pointing accuracy requirements? -- It is in EID-B. GOLF has no requirements beyond the nominal accuracy requirements for the spacecraft. - Can the instrument accept thruster firings? What are the contamination constraints? -- GOLF does not believe this will be a problem. However, to be safe they will close the door during the Cruise Phase, but during nominal operations they will continue observing. At the worst, they may close the door, which takes 16 seconds. - Is ground support required during any operations -- in particular, critical support? -- None have been identified. - How does this instrument recover from safe mode? What is the duration of this operation? -- Two cases: (1) contamination: Just re-open door (2) Other contingencies -- Observation mode is safe mode. - What is the power dissipation in any mode of operation? -- This information was provided to the Project in preparation for TV. It will be included in the EOM. - What are the telemetry mode rate change requirements? -- Not applicable to GOLF. - What about the IIDE? -- Not applicable to GOLF. - Can this experiment provide Sun-pointing? -- Not applicable to GOLF. - What jitter disturbing operation can be used for commissioning the disturbance on other experiments? Does it require ground critical support? -- In the GOLF manual. (Not applicable?) - Commissioning/Cruise Phase Timeline? -- For GOLF it was sent to Piet Martens via email in the past week. It should be considered preliminary information, since there is no information exchanged between the instruments at this point. END OF ESA QUESTIONS #################################################### DISCUSSION OF FOT QUESTIONS Purpose--To define Flight Operations Team (FOT) activities for TESTING. Background There are two tests scheduled between the spacecraft and the NASA Ground System: -- Ground System Compatibility Test #2 in March 95 with SOHO at Matra Launch Site Test in July 95 with SOHO at Cape Canaveral. (Another test is being negotiated between ESA and NASA.) The ELISA Procedures for the instruments are scheduled for delivery to NASA in the December 1994 Spacecraft Users' Manual (SUM). Therefore, we must rely on the experimenters to provide input for any Ground System testing activities. We address these activities through this questionnaire. (1) Will this instrument participate in these tests? -- Yes. GOLF has now gone through IWS integration in the EOF. If test is in November, GOLF will be able to participate. (2) Telemetry Processing Activities (a) Define the telemetry page(s) layout you would like to see on the POCC system. -- GOLF does not have supercommutated and subcommutated data. -- Two pages of display on GOLF IWS -- one page defines the items to determine experiment safe operations (more critical), the other provides additional data on operations status. -- Layouts of the two GOLF page displays were discussed at length. Some modifications were analyzed. The FOT will develop these pages on the POCC system and discuss again with GOLF. -- GOLF has Two detectors working in parallels. Each detector has two counting chains. Spectra- threshold can be either fixed or scanned. Gives amplitude of detectors. Can switch spectrum detectors on- and off- Some details will be added to telemetry descriptions in EOM. For Command Reception (last 4). the scrolling - The last parameter (tc) is always contained in the last (#4) Refer to ÒMnemonic Elaboration Rules and Their UsageÓ for Naming convention for experiment mnemonics:. Look for this doc: ÒMnemonic Elaboration Rules and Their UsageÓ Internal data generation rate is 5 seconds. -- Mnemonic GSIT -- used by GOLF when daily pulse is received. Internal clock rate: When daily pulse is received this parameter goes to zero. This can be used to verify that daily pulse function was performed properly. -- GOLF needs to receive a Daily pulse only once, each time instrument is turned ON. This will be handled automatically by the experiment. After receiving one daily pulse, it will not accept any more. -- Each time the OBT is received, it will be accepted and the LOBT will be re-adjusted based on the OBT. -- GOLF has no requirement on how often to update the LOBT. Forward a time distribution at initial OBT setting, and each time experiment is switched ON (TBC). (2). Telemetry Processing Activities (b) Define the subset of telemetry points that the FOT will monitor for this instrument. What is the mnemonic? Are the limits that the POCC will receive in the SDB accurate for test? What action should be taken by the FOT in "out-of-limits" situation? -- The telemetry monitoring is divided in two categories: Critical items, that may endanger experiment safety, and Performance monitoring parameters. -- Critical items: -- Critical Mnemonics -- Spacecraft PDU at Instrument Input -- No POWER to Instrument (PDU - S/C TM) - (GIPWA and GIPWB in spacecraft telemetry). FOT must monitor Input Current (both Nominal and Redundant). If both nominal and redundant currents are zero this is a critical state. -- Response: Switch OFF GOLF, Switch ON non-op-heaters and notify experimenter immediately -- Filter temperature (GTFIFIN in GOLF VC0 - see page ÒHealth and Safety) measures radiator temperature. Response: If the temperature exceeds the normal range, POWER OFF GOLF, Power ON non-op heaters, and notify experimenter immediately. -- Use proc GLF_OFF to turn it off -- The responses defined above apply to the Yellow limits ****Limits are not included in Database at present**** There should be RED and YELLOW limits included in SDB. Routine Monitoring -- Nominal Operations Mnemonics for Routine Observations. Ten are outlined (they are identified by a box).sample page descriptions provided by GOLF. -- If a problem is detected at the S/C level use proc: GLF_EMRGNCY to turn off GOLF. If door was open when this proc is executed, another proc must be executed to recover and close the door (Execute GLF_SAFE, which contains the following steps: turn ON, Close door, and Power OFF) (3) Commanding Activities (a) Activity requests to the FOT will be via a SOHO Activity Request form (see example) (b) Define each TSTOL Procedure that the FOT will send for this instrument. (See Appendix to Flight Operations Plan "TSTOL Style Guide") Description of Approval Cycle and Configuration Management for Procedures Description of Procedure testing Proc will be syntax and logic-checked in POCC system. Proc will be run against Ground System Simulator to insure database. **Simulator does not provide any fidelity for instruments** Procedure name for Test will be X_TS_XXXXXXXX English language script (or clearly commented ELISA code) will be required. For each TSTOL Procedure: Are there system or instrument constraints to be monitored before sending this Procedure? What telemetry points can be monitored to verify the response of this Procedure? Does a representative from your instrument need to be present in order to send this Procedure? -- The procedures for the test are defined from the English language procedures provided by GOLF. Some real-time additions and changes were performed by J. Charra. These procedures can be used for the ground system test. With some modifications they will be usable for early orbit operations. -- The FOT will code the TSTOL procedures from these inputs. -- During nominal Halo orbit, commanding will be minimal. -- Any required modifications to experiment will be performed mostly during the momentum off loading phase, when perturbations already occur. -- GOLF would like the FOT to perform the bulk of the commanding operations. -- The same procedure validation process that was adopted for SVM will be followed with the Experimenters. The FOT will code the procedures, then submit them for review and approval by each Experiment team. -- It may take up to 45 seconds to receive verification of command acceptance for GOLF. This is because the GOLF H/K packet is acquired by the S/C every 15 s, but GOLF generates 2 packets during this time. The ground system must never send more than 4 OBDH blocks every 15 seconds in order to obtain TM reporting on TC acceptance. The GOLF H/K packet will only contain command acceptance reporting for the last 4 commands received. During GSCT sequence to follow: -- GLF_ON : Power On -- GLF_COM : Commissioning Sequence -- GLF_OBS : Set up in observation state -- GLF_OFF : Power Off -- GLF_Recovery : Recovery to Standby sequence -- GOLF will basically use similar procedures as are used in CCS for testing, with some changes to include TV. These will be performed by FOT. -- GOLF is a low maintenance experiment, so far as FOT is concerned. -- GOLF has both English-language version (used as input to CCS) and ELISA versions. The English-language versions are marked in BOLD where an operator on GOLF team takes action (log mnemonic value, print screen, etc). -- In the ELISA files there are long waits, since the telemetry verification can take up to 45 seconds for GOLF. -- Never send more than 4 commands each 15 seconds (in order to get report through telemetry). -- GLF_EMERGENCY pulls the plug, without closing the door. -- GLF_SAFE powers up the instrument, closes the door, and performs a graceful shutdown. -- GLF_OFF is a graceful shutdown. Specific TSTOL Procs for Test will be covered in separate meeting at 13:00 on 08Aug94. (c) Describe the instrument activities to be performed using the EOF near-realtime throughput (NRT) commanding channel. Will the Remote Procedure Request (RPR) be used? Will the Remote Command Request (RCR) be used? -- Already covered in (b) (d) Describe the instrument activities to be performed using Delayed Commanding. -- Already covered in (b) (e) Describe any use of the Background Queue (for large table loads). -- Already covered in (b) (4) Other Possible Test Activities (a) Describe any constraints of switching telemetry modes (Low, Medium, High). -- Not applicable. (b) Describe any constraints of switching between High rate telemetry modes. -- Not applicable. (c) Describe any constraints of switching telemetry sub- modes. -- Not applicable. (d) Describe any constraints associated with the OBT distribution and Daily Pulse. -- Described above. (e) Describe any constraints of the Inter-Instrument Data Exchange. -- Not Applicable (5) Future Activities for Flight See answers below to ESA/Matra questions. (a) Any necessary modifications to (1) through (4). (b) Describe the timeline for commissioning activities of this instrument. Timeline provided recently to P. Martens and to FOT (preliminary). (c) Describe any constraints associated with Thruster Operations. (d) Describe any known jitter created by this instrument. (e) Describe any special pointing accuracy requirements for this instrument. (f) Can this instrument provide relevant information to Flight Dynamics regarding absolute pitch, yaw, or roll? (g) Describe any anticipated power dissipation changes for this instrument. (h) Describe Daily Pulse usage. GOLF will use it only once after power-up. It will only be required again if GOLF is powered down. (i) Describe OBT Update usage. -- Discussed previously with ESA on-line. OTHER TOPICS - Flight S/W Uplinks Question: GOLF can only uplink its S/W by uplinking the entire S/W (Total size 17 KBytes) -- Answer: For initial uplink of S/W and anytime it is necessary to update it, GOLF should request a block of reserved time to perform the S/W uplink functions. These can be negotiated via the regular planning meetings with the Experimenters. ######################################################### CONSTRAINTS: RELAY commands should not be sent while the experiment is powered off -- FOT requests that all the relay commands for GOLF .be specified as critical commands in the SDB. These are S/C commands. ######################################################### UNANSWERED QUESTIONS 1. GOLF will accept the OBT update. The GOLF LOBT will be synchronized with OBT. GOLF only wants the OBT updates only at initial power-up. (TBC) 2. If a DHSS reconfiguration takes place, which sets OBT back to zero, once the clock is re-initialized should time be forwarded to experiment? (TBD). ########################################################## DOCUMENTS OBTAINED -- Page Descriptions -- Procedures (English description): ---- GLF_ON ---- GLF_COM ---- GLF_OBS ---- GLF_OFF ---- GLF_Recovery -- ELISA Control Files (provided as a reference only) ---- GLF_BLK_CHK ---- GLF_COM ---- GLF_COM_D ---- GLF_DOOR ---- GLF_EMC ---- GLF_EMRGNCY ---- GLF_OBS ---- GLF_OFF ---- GLF_ON ---- GLF_PARAM ---- GLF_PARAM_01 ---- GLF_RCOVERY ---- GLF_STATUS ---- GLF_TEST -- Listing of TC and TM