! File: 2855C.PROP ! Database: PEPDB ! Date: 17-FEB-1994:18:40:20 coverpage: title_1: SAFEMODE RECOVERY OF THE HST SCIENCE INSTRUMENTS proposal_for: ENG pi_title: DR. pi_fname: RODGER pi_mi: E. pi_lname: DOXSEY pi_inst: ST SCI pi_country: USA pi_phone: (301) 338-4750 wf_pc: Y foc: Y fos: Y hrs: Y hsp: Y ! end of coverpage abstract: line_1: The HST science instruments can autonomously enter a SAFE line_2: configuration due to either SI unique or spacecraft problems. line_3: In order to carry on the science mission it is necessary to line_4: return these instruments from this safe configuration to the line_5: normal operational configuration. This proposal describes the line_6: procedure for this transition. ! ! end of abstract general_form_proposers: lname: DOXSEY fname: RODGER title: DR. mi: H. inst: ST SCI country: USA ! lname: SCHIFFER 3RD fname: FRANCIS title: DR. mi: H. inst: CSC/ST SCI country: USA ! ! end of general_form_proposers block general_form_text: question: 2 section: 1 line_1: The instruments are incapable of taking science data when line_2: in the safemode configuration which can be entered by a number line_3: of processes through autonomous actions by the HST flight line_4: software. In order to continue normal science operations it is line_5: required to return the science instruments to an operational line_6: configuration. These transition are defined by this proposal. line_8: change Feb 1990: add WFPC and delete FOC in hold. ! question: 3 section: 1 line_1: This proposal describes the actions necessary to reconfigure each line_2: SI into an operational configuration from a SAFEMODE configuration. line_3: Each SI uses the same basic structure to transition: line_4: 1. a line which requires a safemode configuration. This line line_5: - will cause the ground system to reconfigure its tracking line_6: - information to correspond to the spacecraft configuration line_7: - (assuming the spacecraft is really in safemode). No line_8: - commanding will be issued to force the safemode line_9: - configuration. Note the standard reconfiguration software line_10: - will be triggered by this line to cleanup all the RTCSs line_11: - and any other history keeping functions. Nominally this line_12: - line does not trigger any science activity commanding. line_13: - the single exception to this lack of commanding is the FOC line_14: - which uses the science activity to return the SI to a line_15: - thermally safe configuration. line_16: 2. a line or lines which configure the SI from the SAFE line_17: - hardware configuration back to a standard operating line_18: - configuration. This commanding is done as part of the line_19: - science activity associated with this line using the line_20: - specialized commanding specified in the exposure logsheet line_21: - comments. Once again the FOC is the exception to this line_22: - rule and uses the reconfiguration software due to the long line_23: - time delays needed between the recovery steps. ! question: 3 section: 2 line_1: 3. a line which configures the SI from the software safe line_2: - configuration to the lowest level of operational line_3: - configurations (ie, the one which corresponds to the line_4: - hardware configuration defined by the commanding from line_5: - step 2. Normally this activity will neither issue any line_6: - commanding as part of the science activity or require line_7: - any commanding from the reconfiguration software. line_8: - The activity implements a "bookkeeping" transition. line_10: This structure ensures that the normal software processing line_11: which schedules science observations will not schedule such line_13: an observation into the time span required by the safemode line_14: recovery even if the total duration of the recovery is quite line_15: extended due to the need to investigate a problem. line_16: Normally step 1 will be scheduled as soon as possible after line_17: the safemode entry in order to correct the ground system line_18: status. Additional tests may be scheduled or the SI returned line_19: to the operational hardware configuration by using step 2 and line_20: other specialized commanding. When the SI is deemed ready for line_21: general use step 3 will be scheduled. ! question: 3 section: 3 line_1: FOC recovery considerations - line_2: This instrument has unique requirements concerning safemode line_3: recovery due to the fact the safemode is not thermally safe. line_4: The instrument must be recovered to a thermally safe line_5: configuration prior to any attempt to recover back to any line_6: operational level. In addition the requirements state that this line_7: thermal reconfiguration must proceed the return to an line_8: operational state by at least 18 hours, although other steps in line_9: the recovery process may begin earlier. It appears that the best line_10: solution is to define the thermal requirements as states off the line_11: FOC instrument tree with the reconfiguration software and off line_12: the dectector tree for the configuration information. Due to line_13: the need to maintain a thermal history, it is impossible to line_15: implement the FOC safemode recovery in the simplistic manner line_16: envisioned for the other SIs. For this reason the actual line_17: recovery commanding will be issued by the reconfiguration line_18: software rather than the science activities except for the line_19: commanding to recover to the thermally safe configuration (ie, line_20: the first step of the recovery process). ! question: 3 section: 4 line_1: Questions which must be answered in order to schedule an FOC line_2: safemode recovery: line_3: 1. Is FOC High Voltage operation acceptable? line_4: 2. Was the FOC in Hold during the safing event? line_5: 3. Is the FOC mechanism tracking data correct? line_7: FOS recovery considerations - line_8: This instrument has only one method for recovering from a line_9: safemode incident. The scheduling of the instrument and line_10: detector states is independent for the normal operational modes. line_11: This independence requires that both the instrument and line_12: detectors be placed in the Offline state when safing occurs. line_13: With this one exception, the FOS fits the standard model for line_14: safemode recovery. ! question: 3 section: 5 line_1: GHRS recovery considerations - line_2: The GHRS has two safemode recovery procedures which differ only line_3: in the need to reload the thresholds if they were lost during line_4: the safemode. Unfortunately the SI must be brought up to a low line_5: voltage operate state in order to reload the thresholds. The line_6: reconfiguration tables need to add a single state to the SI tree line_7: to define the instrument safe condition and a single state to line_8: each of the detectors to reflect the need to reload the line_9: thresholds. line_11: In order to schedule the GHRS safemode recovery the following line_12: question must be answered: line_13: Do the GHRS thresholds need to be reloaded? ! question: 3 section: 6 line_1: HSP recovery considerations - line_2: The HSP has only one method for recovering from safemode, line_3: however, the standard approach leaves the SI in the Hold line_4: configuration which is not the standard configuration for the line_5: HSP. An additional transition to the Ready configuration may be line_6: needed to return the HSP to the standard configuration (ie, line_7: instrument team new-hold). Due to the requirements for SI line_8: configuration within the detector reconfiguration states, only line_9: one Offline configuration is needed: line_11: In order to schedule the HSP recovery, one question must be answered: line_12: Should the HSP be returned to New-Hold? ! question: 3 section: 7 line_1: WFPC recovery considerations - line_2: The WFPC recovery is significantly different from the other SIs. line_3: Instead of having 9 different scenarios to select between, there line_4: is one scenario of activities and the second step (line 501) is line_5: is modified by creating QESIPARMS which describe the state of the line_6: instrument during the safemode event: line_7: . The QESIPARM FLOOD must be defined if either the uvflood mirror line_8: . was in motion or in the UVFLOOD position during the safemode line_9: . event. If the mirror was in the FLOOD position or in motion line_10: . and nearest the flood position the qesiparm should have the line_11: . value of IN. If the mirror was in motion and nearest the line_12: . clear position, the parameter should have the value OUT. line_13: . The QESIPARM PYR must be defined if either the pyramid was in line_15: . motion or in the PC position. If the pyramid was in the PC line_16: . PC position or in motion and nearest the PC position the line_17: . qesiparm should have the value PC. If the pyramid was in line_18: . motion and nearest the WFC side, the the qesiparm should have line_19: . the value WFC. line_20: If the above conditions were not true the qesiparm should not be line_21: created. ! question: 4 section: 1 line_1: only HST has the appropriate science instruments to carryout line_2: these recoveries and without these recoveries normal science line_3: observations cannot be done after a safe mode entry. ! question: 5 section: 1 line_1: The questions defined in section 3 must be answered for each SI line_2: in safe mode and the appropriate sequence scheduled. Except where line_3: special timing requirements are indicated on the exposure logsheet line_4: arbitrary gaps between the various steps is acceptable. line_6: Only one occurrance of the safemode recovery sequence is included line_7: in the proposal, however, the lines must be scheduled for each line_8: safemode event. line_10: The planning structures should define each of the planning steps line_11: as a separate scheduling unit to facilitate creating recovery line_12: calendars. The general scheduling procedure would be to select line_13: the time at which normal mode operations would resume and schedule line_15: the safemode to an operating state transition at that time. line_16: Then the initial transition to Offline would be scheduled at the line_17: earliest time at which a recovery could be begun. This process line_18: will ensure that all the normal mode operations between those times line_19: have been deleted. Then the actual recovery steps or diagnostic line_20: activities could be scheduled betweent these activities. ! !end of general form text general_form_address: lname: DOXSEY fname: RODGER mi: E. title: DR. category: PI inst: ST SCI addr_1: ST SCI/SESD addr_2: 3700 SAN MARTIN DRIVE city: BALTIMORE state: MD zip: 21218 country: USA phone: (301) 338-4750 ! lname: SCHIFFER 3RD fname: FRANCIS mi: H. title: DR. category: CON inst: CSC/ST SCI addr_1: ST SCI/SESD addr_2: 3700 SAN MARTIN DRIVE city: BALTIMORE state: MD zip: 21218 country: USA phone: (301) 338-4789 ! ! end of general_form_address records ! No fixed target records found ! No solar system records found ! No generic target records found exposure_logsheet: linenum: 100.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 40S priority: 1 req_1: COND IF SAFED WHILE req_2: PRESSURE CONSTRAINT NOT MET; req_3: SELECT 1 OF 100 OR req_4: 120-122 OR 130-132; req_5: NON-INT; comment_1: SI = FOC:COLD, FOC:DET:OFFLINE; comment_2: INSTRUCTION = SXRECOVER1 ! linenum: 120.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 40S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS CORRECT; req_3: SEQ 120-122; NON-INT; comment_1: SI = FOC:COLD, FOC:DET:OFFLINE; comment_2: INSTRUCTION = SXRECOVER1 ! linenum: 121.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS CORRECT; comment_1: SI = FOC:DET:KNOWN; ! linenum: 122.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS CORRECT; comment_1: START SI = FOC:HOLD, FOC:DET:OFFLINE; comment_2: END SI = FOC:HOLD, FOC:DET:HOLD; ! linenum: 130.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 40S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS NOT CORRECT; req_3: SEQ 130-132; NON-INT; comment_1: SI = FOC:COLD, FOC:DET:OFFLINE; comment_2: INSTRUCTION = SXRECOVER1 ! linenum: 131.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS NOT CORRECT; comment_1: SI = FOC:DET:LOST; ! linenum: 132.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF MECHANISM TRACKING req_2: IS NOT CORRECT; comment_1: START SI = FOC:HOLD, FOC:DET:OFFLINE; comment_2: END SI = FOC:HOLD, FOC:DET:HOLD; ! linenum: 200.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: SEQ 200-202; comment_1: SI = FOS:OFFLINE, FOS:BLUE:OFFLINE, comment_2: FOS:RED:OFFLINE ! linenum: 201.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1900S priority: 1 req_1: NON-INT; comment_1: SI = FOS:OFFLINE, FOS:BLUE:OFFLINE, comment_2: FOS:RED:OFFLINE; comment_3: INSTRUCTION = SYRECOVER; ! linenum: 202.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 comment_1: SI START = FOS:OFFLINE, comment_2: FOS:BLUE:OFFLINE, FOS:RED:OFFLINE; comment_3: SI END = FOS:HOLD, FOS:BLUE:HOLD, comment_4: FOS:RED:HOLD; ! linenum: 300.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF THRESHOLDS OK; req_2: SEQ 300-302; comment_1: SI = HRS:OFFLINE, HRS:DET1:OFFLINE, comment_2: HRS:DET2:OFFLINE; ! linenum: 301.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 80S priority: 1 req_1: COND IF THRESHOLDS OK; req_2: NON-INT; comment_1: SI = HRS:OFFLINE, HRS:DET1:OFFLINE, comment_2: HRS:DET2:OFFLINE; comment_3: INSTRUCTION = SZRECOVER; ! linenum: 302.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF THRESHOLDS OK; comment_1: SI START = HRS:OFFLINE, comment_2: HRS:DET1:OFFLINE, HRS:DET2:OFFLINE; comment_3: SI END = HRS:HOLD, HRS:DET1:HOLD, comment_4: HRS:DET2:HOLD; ! linenum: 310.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF THRESHOLDS MUST BE LOADED; req_2: SEQ 310-311; comment_1: SI = HRS:OFFLINE, HRS:DET1:OFFLINE, comment_2: HRS:DET2:OFFLINE; ! linenum: 311.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 80S priority: 1 req_1: COND IF THRESHOLDS MUST BE LOADED; req_2: NON-INT; comment_1: SI = HRS:OFFLINE, HRS:DET1:OFFLINE, comment_2: HRS:DET2:OFFLINE; comment_3: INSTRUCTION = SZRECOVER; ! linenum: 312.000 sequence_1: USE sequence_2: LDTHRESH sp_element: SAFE1 time_per_exp: X14 param_1: FUNCTION=BOTH req_1: COND IF THRESHOLDS MUST BE LOADED; req_2: AFTER 311; BEFORE 314; ! linenum: 313.000 sequence_1: USE sequence_2: LDTHRESH sp_element: SAFE2 time_per_exp: X14 param_1: FUNCTION=BOTH req_1: COND IF THRESHOLDS MUST BE LOADED; req_2: AFTER 311; BEFORE 314; ! linenum: 314.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: COND IF THRESHOLDS MUST BE LOADED; comment_1: SI (START) = HRS:OFFLINE, comment_2: HRS:DET1:OFFLINE, HRS:DET2:OFFLINE; comment_3: SI (END) = HRS:HOLD, comment_4: HRS:DET1:HOLD, HRS:DET2:HOLD; ! linenum: 320.000 sequence_1: DEFINE sequence_2: LDTHRESH targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: SEQ 320-322 NON-INT; comment_1: SI (START) = HRS:OFFLINE, comment_2: HRS:DET1:OFFLINE, HRS:DET2:OFFLINE; comment_3: SI (END) = HRS:HOLD, comment_4: HRS:DET1:HOLD, HRS:DET2:HOLD; ! linenum: 321.000 sequence_1: DEFINE sequence_2: LDTHRESH targname: DARK config: HRS opmode: THRESHOLD sp_element: # num_exp: 1 time_per_exp: 1M priority: 1 param_1: # ! linenum: 322.000 sequence_1: DEFINE sequence_2: LDTHRESH targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 comment_1: SI = HRS:OFFLINE, HRS:DET1:OFFLINE, comment_2: HRS:DET2:OFFLINE; ! linenum: 400.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: SEQ 400-402; comment_1: SI = HSP:OFFLINE, comment_2: ALL HSP DETECTORS HOLD; ! linenum: 401.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 80S priority: 1 req_1: NON-INT; comment_1: SI = HSP:OFFLINE, comment_2: ALL HSP DETECTORS HOLD; comment_3: INSTRUCTION = SVRECOVER; ! linenum: 402.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 comment_1: SI START = HSP:OFFLINE; comment_2: SI END = HSP:HOLD; comment_3: ALL HSP DETECTORS IN HOLD; ! linenum: 403.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: AFTER 402 BY 1S; req_2: COND IF NEW-HOLD IS DESIRED; comment_1: SI = HSP:READY, comment_2: ALL HSP DETECTORS IN HOLD; comment_3: FORCE HSP TO NEW-HOLD; ! linenum: 500.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 req_1: SEQ 500-502; comment_1: SI = WFPC:OFFLINE, WFPC:PYR:HOLD; ! linenum: 501.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 25M priority: 1 req_1: NON-INT; comment_1: SI = WFPC:OFFLINE, WFPC:PYR:HOLD; comment_2: INSTRUCTION = SWRECOVER; comment_3: QESIPARMS: FLOOD AND PYR MUST BE SET comment_4: ACCORDING TO CONFIGURATION AT SAFING; comment_5: SEE SECTION 3 FOR DETAILS; ! linenum: 502.000 targname: DARK config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S priority: 1 comment_1: SI START=WFPC:OFFLINE,WFPC:PYR=HOLD; comment_2: SI END = WFPC:STDBY, WFPC:PYR=HOLD; ! ! end of exposure logsheet ! No scan data records found