! File: 3386C.PROP ! Database: PEPDB ! Date: 19-FEB-1994:05:56:49 coverpage: title_1: FHST ERROR BOX FSW UPDATE proposal_for: ENG/AST pi_fname: A pi_lname: LEIBOWITZ pi_inst: CODE 512 pi_country: USA num_pri: 1 ! end of coverpage abstract: line_1: DF-224 FSW modifications for FHST processing have resulted line_2: in the developement of a new code "FHST ERROR BOX". This line_3: code modification via implementation of CCR 2856 will line_4: result in an onboard quality check which permits the FSW line_5: to search for a an FHST reference star after detection of line_6: a spolier star, rather than failing the update. line_7: The time allocated will allow scheduling of the S/C to a line_8: specific configuration needed to uplink the FSW updates line_9: and allow for subsequent on-orbit testing of the new code. line_10: Once validated, this new code will reduce the FHST update line_11: failures and increase the pointing accuracy of HST line_12: w/a corresponding reduction of Guide Star ACQ failures ! ! end of abstract general_form_proposers: lname: LEIBOWITZ fname: A. inst: GFSC country: USA esa: X ! ! end of general_form_proposers block general_form_text: question: 2 section: 1 line_1: The installation of the FSW code will be conducted w/ line_2: the HST in normal mode using the gyros for attitude line_3: reference. THe attitude at anytime can be at any line_4: desired pointing. The Velocity Aberration and Parallax line_5: (VAP) must not be active to reduce the CPU processing line_6: of the DF-224 during installation. line_7: In addition Df-224 processing must also be inactive line_8: (ie no FHST maps or updates). 4Kbps "AN" format line_9: should be active with the engineering recorder activities line_10: performed by generic PASS scheduling. The time frame line_11: for installation is defined during normal working hours line_12: between 120000z and 210000z. 3 orbits are required to line_13: install and validate the code. 3 additional SSAF line_14: COMCON requests should be included in the SMS of 15-20M line_15: durations (ie 1 per orbit). ! question: 3 section: 1 line_1: The specific HST configuration for installation is needed line_2: to reduce the CPU processing and prevent unknown line_3: anomalous FSW operation, possibly causing entry into line_4: safemode. Previously, serendipitous installations of FSW line_5: have proved to be difficult when specific S/C config's. line_6: are desired. Project has therefore directed that all line_7: future FSW installations requiring specific S/C config's. line_8: be submitted thru the proposal system. ! question: 5 section: 1 line_1: 3 orbits under gyro control (~300mins) line_3: - 1 orbit to perform full DF-224 memory dump and line_4: evaluate content. Telemetry checks and TMDIAGS in line_5: RT for verifying DF-224 FSW config., FHST processing line_6: inactive and specific FSW code addresses prior to line_7: actual installation will be performed line_9: - 1 orbit needed to perform FSW installation, line_10: execution of the TMDIAGS to verify uplink, execution line_11: of the Special Processor to perform branch statment line_12: and patches to the code, followed by TMDIAGS to line_13: verify proper branch installation. line_15: - 1 orbit to perform full DF-224 dump and evaluate line_16: contents before enabling FHST ERROR BOX code. ! question: 6 section: 1 line_1: 2 additional SSAF COMCONS scheduled by SMS (1 per orbit) line_2: of 15-20min duration each, to perform installation. line_4: Generic scheduling by PASS of SSAF will be used for line_5: both Normal Ops activities and FSW installation. line_7: Normal S/C telemtry will be used for evaluation of line_8: FSW installation and S/C config. line_10: 2 full DF-224 dumps will be used to evaluate contents line_11: of memory and operating conditions. The 1st prior to line_12: installation and the 2nd after installation completed. ! !end of general form text general_form_address: lname: LEIBOWITZ fname: A category: PI inst: CODE 512 ! lname: LEIBOWITZ fname: A. category: PI inst: GFSC ! ! end of general_form_address records ! No fixed target records found ! No solar system records found ! No generic target records found exposure_logsheet: linenum: 1.000 targname: ANTI-SUN config: S/C opmode: POINTING aperture: V1 num_exp: 1 time_per_exp: 1S fluxnum_1: 1 priority: 1 param_1: CONTROL=GYRO req_1: SEQ 1-4 NO GAP; req_2: CYCLE 0 / 1-4; ! linenum: 2.000 targname: ANTI-SUN 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: NO FHST UPDATE AND NO comment_2: HFST MAPPING FOR NEXT 3 comment_3: ORBITS. VELOCITY comment_4: ABBERATION AND PARALLAX comment_5: (VAP) OFF. TELEMETRY comment_6: FORMAT= AN. ! linenum: 3.000 targname: ANTI-SUN 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: AFTER 2 BY 100M+/-10M; comment_1: NO FHST UPDATE AND NO comment_2: HFST MAPPING FOR NEXT 3 comment_3: ORBITS. VELOCITY comment_4: ABBERATION AND PARALLAX comment_5: (VAP) OFF. TELEMETRY comment_6: FORMAT= AN. ! linenum: 4.000 targname: ANTI-SUN 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: AFTER 3 BY 100M+/-10M; req_2: RT ANALYSIS; req_3: REQ UPLINK; comment_1: NO FHST UPDATE AND NO comment_2: HFST MAPPING FOR NEXT 3 comment_3: ORBITS. VELOCITY comment_4: ABBERATION AND PARALLAX comment_5: (VAP) OFF. TELEMETRY comment_6: FORMAT= AN. ! ! end of exposure logsheet ! No scan data records found