! File: 4032C.PROP ! Database: PEPDB ! Date: 20-FEB-1994:04:36:47 coverpage: title_1: DF-224 VERSION 8.0 FS INSTALLATION proposal_for: ENG/SC cont_id: 4032 pi_fname: LESLYE pi_lname: BOYCE pi_inst: CODE 441 pi_country: USA num_pri: 1 ! end of coverpage abstract: line_1: DF-224 Version 8.0 will implement the final phase of the 3 line_2: Logical Memory Unit Contingency Plan described in LMSC,EM line_3: SPS640. It focuses on new capabilities, implementing a spin line_4: stabilized safemode, correcting the integral calculation in line_5: Momentum Management Law and other miscellaneous command line_6: changes geared at enhancing acquistions and science. line_7: Due to the complexity of the installation, dedicated space- line_8: craft time is required to minimize risk. In summary, this line_9: proposal requests 7 orbits of dedicated spacecraft time for line_10: installation, regression testing and contingency back-out time line_11: for DF-224 Flight Software (FS) Version 8.0 for the week of line_12: April 27,(SMS118). No dedicated time is requested for the pre- line_13: load of the FS. ! ! end of abstract general_form_proposers: lname: BOYCE fname: LESLYE inst: GFSC/CODE 441 country: USA esa: X ! lname: LEIBOWITZ fname: ARIEL inst: GFSC/CODE 512 country: USA esa: X ! lname: ROY fname: NORM inst: LMSC/CODE 440.8 country: USA esa: X ! lname: MESNARD fname: GEOFF inst: LMSC/CODE 440.8 esa: X ! ! end of general_form_proposers block general_form_text: question: 2 section: 1 line_1: The time allocated will provide the specific vehicle line_2: configuration and dedicated spacecraft time for in- line_3: stallation and regression testing of ver. 8.0 FS mod. line_4: The new flight code once installed and validated via line_5: on-orbit regression testing, will provide new capabilities; line_6: implementing a spin stabilize safemode, correcting the line_7: Integral calculation in Momentum Management Law and other line_8: miscellaneous command changes geared at enhancing acquistions line_9: and science. The specific HST configuration for installation line_10: of this flight code is needed to configure the vehicle to line_11: reduce the CPU processing during installation, perform line_12: regression testing and provide contingency time for removal line_13: of the code in the event anomalies are detected. ! question: 3 section: 1 line_1: The described sequence of events must occur in the specified line_2: order and are requested for inclusion in the 118 SMS. line_4: 1. Installation line_5: Install flight code changes, installation of Acquistion Logic, line_6: reloading of Safemode macros and recovery load. line_7: VEHICLE CONFIGURATION: The HST in normal mode using the gyros line_8: for attitude reference. The vehicle attitude is to be V1:RA= line_9: 215.0, DEC=-14.0, ROLL= 78.8 (-V1 sunpoint, 180 deg roll). line_10: 4 Kbps programmable "AN" format should be active with the line_11: engineering recorder activities performed by generic sched- line_12: uling by PASS. The following FSW processing MUST be disabled line_13: or inactive prior to installation: line_14: 1.) FGS acq. ATTITUDE update, Command packets #33-47 DISABLED line_15: 2.) Conditional Processor DISABLED line_16: 3.) FHST processing be INACTIVE, Command packets #31,32 line_17: Additinal SSAF COMCON request should be included in the SMS line_18: of 15-20 minutes duration each for a total of 2 per orbit. line_19: A full DF-224 memory dump will follow installation. All line_20: engineering data will be recovered either in RT or via line_21: the Engineering Tape Recorder (ETR). line_22: TIME REQUIREMENT: 3 orbits dedicated. ! question: 3 section: 2 line_1: REGRESSION TEST: The regression test activities are defined line_2: to be the minimum activities which are pertinent to vehicle line_3: health and safety or continued normal vehicle operations. The line_4: majority of the regression test items are autonomously line_5: performed by the DF-224 FS as a result of vehicle config- line_6: uration. The activities have been defined and success/fail line_7: criteria established. Specific activities that are to be line_8: scheduled by the StSCI SMS are a large vehicle slew to the line_9: specified attitude with attendant Solar Array slew. The slew line_10: should be a type 2 and should use the PQVEHSLW PLCP group. line_11: Following this slew is an unspecified Fine Lock (P format), line_12: Coarse Track Acq. (A format), Coarse Re-acq. (A format). line_13: Guide Stars have been checked and are available for Fine Lock line_14: and Coarse Track. line_15: VEHICLE CONFIG: V1:RA=90.0, DEC=-67.0, ROLL=52.4 (SEP,+V3 line_16: sunpoint). 4Kbps programmable "AN" format should be active line_17: w/ ETR activities performed by generic scheduling by PASS. line_18: During this period Operations will be switching to 4Kbps line_19: "AN" format and "PN" format to validate formats. The FSW line_20: processing previosly disabled will be enabled via real-time line_21: activation of the SPC. line_22: TIME REQUIRED: 2 orbits dedicated. ! question: 3 section: 3 line_1: CONTINGENCY REMOVAL: The contingency removal time is the time line_2: required to remove the DF-224 code modifications and reload line_3: previous version of the Acquisition logic. The vehicle line_4: configuration will be managed by Operations in the event line_5: removal of the code is necessary. line_6: Additional SSAF COMCON request should be included in the SMS line_7: of 15-20 minutes duration each for a total of 2 per orbit. line_8: A full DF-224 memory dump will follow installation. All line_9: engineering data will be recovered either in RT or via line_10: the Engineering Tape Recorder (ETR). line_11: TIME REQUIREMENT: 2 orbits dedicated. ! question: 4 section: 1 line_1: Due to the complexity of this DF-224 installation, dedicated line_2: spacecraft time is needed to reduce the CPU processing and line_3: prevent unknown anomalous FSW operation, possibly causing line_4: entry into safemode. Previously, serendipitous installations line_5: of FSW code have proved to be difficult when specific vehicle line_6: configurations are desired. Project Office, code 440 has line_7: therefore directed that all future FSW installations line_8: requiring specific vehicle configurations be submitted line_9: through the proposal system. ! question: 5 section: 1 line_1: 7 orbits line_2: sms orbit activity line_4: 118 1 install flight code changes, reload acq. line_5: logic line_6: 2 reload safemode macros and safemode line_7: recovery load line_8: 3 contingency time line_10: Flight Software Regression Test Begins line_11: 4 Vehicle Slew type 2, use PQVEHSLW PLCP line_12: Fine Lock Acq. (P format), RT analysis line_13: 5 Course Track (CT) acq. (A format), line_14: CT Re-acq. (F format), RT analysis line_16: Back-out Contingency time begins line_17: 6 Remove FS code line_18: 7 Reload old Acq. Logic line_19: The 7 orbits should be continuous in time, with no other line_20: science activites scheduled between. As specified in orbit line_21: 4, the vehicle slew should use the PLCP group PQVEHSLW; this line_22: is to verify the velocity aberration correction in the #57 line_23: command. ! question: 7 section: 1 line_1: Normal vehicle telemetry will be used for evaluation of line_2: flight code installation and vehicle configuration. Two line_3: full DF-224 memory dumps will be needed to evaluate contents line_4: of memory and operating conditions. The first will be line_5: performed prior to load of flight code and the second line_6: performed after installation has been completed. In line_7: addittion, regression activities have been defined as line_8: presented in paragraph 3a. ! !end of general form text general_form_address: lname: BOYCE fname: LESLYE category: PI inst: GFSC/CODE 441 phone: 301 286-8219 ! ! end of general_form_address records fixed_targets: targnum: 1 name_1: SEP descr_1: S.ECLIPTIC POLE (NOMINAL) pos_1: RA = 90.0D +/- .1", pos_2: DEC = -67.000D +/- .01" equinox: 1991 comment_1: +V3 TO SUN ! targnum: 2 name_1: V1SUNPOINT descr_1: ANTISUN POINTING pos_1: RA = 215.00 D +/- .1", pos_2: DEC = -14.000D +/- .01" equinox: 1991 comment_1: -V1 SUNPOINT ! ! end of fixed targets ! No solar system records found ! No generic target records found exposure_logsheet: linenum: 2.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO req_1: RT ANALYSIS; req_2: REQ UPLINK; req_3: CYCLE 1 / 2-15; req_4: SEQ 2-15 NO GAP; req_5: ORIENT 78.8D+/-1D / 2-7; comment_1: FGS ACQ, FHST PROCESSING, ATTITUDE comment_2: UPDATE, CONDITIONAL PROCESSOR comment_3: AND COMMAND PACKETS 31,32,33-47 comment_4: MUST BE INACTIVE VIA SPC. BEGIN comment_5: INSTALLATION OF FLIGHT CODE; RELOAD comment_6: ACQUISITION LOGIC (ORBIT 1),AN FORMAT ! linenum: 3.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: SAME COMMENT AS LINE 2 ! linenum: 4.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: RELOAD SAFEMODE MACROS AND SAFEMODE comment_2: RECOVERY LOAD (ORBIT 2) ! linenum: 5.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: SAME COMMENT AS LINE 4 ! linenum: 6.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: CONTINGENCY TIME (ORBIT 3) ! linenum: 7.000 targname: V1SUNPOINT config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: SAME COMMENT AS LINE 6 ! linenum: 8.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=FGS, req_1: RT ANALYSIS; req_2: REQ UPLINK; req_3: GUID TOL 0.007"; req_4: ORIENT 52.4D+/-1D; comment_1: SLEW TO SEP RA=90.0 DEG, DEC=-67.0 DEG comment_2: ROLL=52.4 DEG (+V3 SUNPOINT) FINE LOCK comment_3: ACQ. VIA SPC: LOAD "P" FORMAT VIA MOC comment_4: MERGE SMS (ORBIT 4) comment_5: PLCP=PQVEHSLW comment_6: FINE LOCK ACQ. ! linenum: 9.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=FGS, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: TIME ALLOCATED FOR RT ANALYSIS comment_2: OF FINE LOCK ACQ. (ORBIT 4) ! linenum: 10.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=FGS, req_1: RT ANALYSIS; req_2: REQ UPLINK; req_3: GUID TOL 0.020" comment_1: COURSE TRACK ACQ. VIA SPC comment_2: LOAD "A" FORMAT VIA MOC MERGE comment_3: SMS (ORBIT 5) ! linenum: 11.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=FGS, req_1: RT ANALYSIS; req_2: REQ UPLINK; req_4: GUID TOL 0.20"; comment_1: COURSE TRACK RE-ACQ. VIA SPC comment_2: LOAD "F" FORMAT VIA MOC MERGE comment_3: SMS (ORBIT 5) ! linenum: 12.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: CONTINGENCY REMOVAL comment_2: OF FS CODE (ORBIT 6) ! linenum: 13.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: SAME COMMENT AS LINE 12 ! linenum: 14.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: RELOAD OLD ACQ LOGIC (ORBIT 7) ! linenum: 15.000 targname: SEP config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 20M fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO, req_1: RT ANALYSIS; req_2: REQ UPLINK; comment_1: SAME COMMENT AS LINE 14 ! ! end of exposure logsheet ! No scan data records found