1 / 59

EO-1 Flight Dynamics Support System (FDSS) Operations Readiness Review

This document outlines the operations readiness review for the FDSS supporting the EO-1 mission, covering launch details, orbit characteristics, and mission operations plans.

amontagna
Download Presentation

EO-1 Flight Dynamics Support System (FDSS) Operations Readiness Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EARTH OBSERVING-1 (EO-1) FLIGHT DYNAMICS SUPPORT SYSTEM (FDSS)OPERATIONS READINESS REVIEWOCTOBER 11, 2000 Prepared by: Bob DeFazio / GSFC / 572 Rich Luquette / GSFC / 572 Chad Mendelsohn / GSFC / 572 Seth Shulman / EO1 FOT / CSC Jennifer Sager / EO1 FOT/ HTSI Skip Owens / AI-Solutions

  2. FLIGHT DYNAMICS TEAM FDAB (CODE 572) GN&CC MAB (CODE 583) ISC FOT RESPONSIBLE FOR DEFINING FUNCTIONAL REQUIREMENTS, TESTING, TRAINING AND OPERATIONS RESPONSIBLE FOR DEFINING FUNCTIONAL REQUIREMENTS, DEVELOPING, AND TESTING TOGETHER THE TEAM: COORDINATES WITH OUTSIDE INTERFACES, INTEGRATES SCHEDULE, BUILDS OPS CONCEPT FDF (CSOC) PROVIDES L & EO FLIGHT DYNAMICS INSTITUTIONAL SERVICES

  3. FDSS TEAM ROSTER Pre-Launch & L&EO

  4. FDSS TEAM ROSTER Normal Operations

  5. FDSS DOCUMENTATION LOCATIONS • MOST DOCUMENTATION IS ON THE FDSS SHARED DRIVE BETWEEN THE FDSS WORKSTATIONS & PCs: • FDSS Mission Procedures Handbook • ICD with Landsat-7 MOC • Software User’s Guides • Mission Timelines • SOME FDSS COTS DOCUMENTATION WILL BE AVAILABLE AS HARDCOPY IN THE MOC

  6. AGENDA • ORBIT • ATTITUDE • TEAM OPERATIONS READINESS • SYSTEM DESCRIPTION AND READINESS • ISSUES AND CONCERNS

  7. ORBIT AGENDA • MISSION ORBIT CHARACTERISTICS • LAUNCH AND INJECTION • BASELINE ASCENT PROFILE • ROUTINE MANEUVERS • ORBIT DETERMINATION

  8. MISSION ORBIT CHARACTERISTICS • FROZEN, SUN-SYNCHRONOUS • REPEAT CYCLE: 233 REVS/16 DAYS • 705 KM MEAN ALTITUDE OVER EQUATOR • 98.2 DEG INCLINATION • 10:03:38 AM (+/- 6 SEC) DESCENDING NODE MLT • +/- 5 KM GROUND TRACK CONTROL AT EQUATOR • +/- 10 TO 20 METERS RADIAL CONSTRAINT • MISSION DURATION: 1 YEAR

  9. FORMAT FLYING WITH LANDSAT-7 EO-1 Orbit Plane Landsat-7 Orbit Plane EO-1 Descending Node 1 Min. Behind Landsat-7 Descending Node 10:02 AM WRS Ground Track MLT Path 10:03AM MLT Equator Landsat-7 at Descending Node Mean Sun 12:00 MLT 1 min Earth Rotation

  10. LAUNCH • LAUNCH DATE: November 16, 2000 • LAUNCH VEHICLE: Delta II , 7920 • LAUNCH SITE: VANDENBERG AFB, CA • LAUNCH CO-MANIFEST: SAC-C • LAUNCH WINDOW: • 20 to 27 SECOND WINDOW EACH DAY IN NOV. AND DEC. 2000 • Window open: 18:24:16 UTC • Window close: Between 18:24:36 UTC • & • 18:24:43 UTC

  11. LAUNCH STATUS • AS OF 10/10/00, EO1/SAC-C ARE GO FOR LAUNCH ON 11/16/00 • EO-1 IS SEPARATED FIRST AT LAUNCH + 1 HOUR

  12. INJECTION • INJECTION TARGETS • MLT: 10:03:38 AM (+30 SECONDS, -18 SECONDS) • INCLINATION: 98.2 DEG. • ALTITUDE: • 705 KM. CIRCULAR, AT 1ST ASCENDING NODE • TARGET SPECIFICATION • PROVIDED TO BOEING 8/14/00 • VALID THROUGH 12/31/00 • WILL UPDATE BY 10/15/00 FOR LAUNCH LATER THAN 12/31/00

  13. EO-1 MLT 1 YEAR PREDICTION AT END OF ASCENT SEQUENCE

  14. EO-1 FORMATION FLYINGWITH LANDSAT-7 • AGREEMENT TO FLY SAME GROUND TRACK KEEPING EO-1 1 MINUTE (+ / - 6 SECONDS) BEHIND AND WITHIN +/- 3 KM CROSS TRACK OF LANDSAT-7 • SEPARATION WITHIN ORBIT TO FLY SAME GROUND TRACK IS DICTATED BY ORBIT PLANE MLT SEPARATION • MLT SEPARATION IS SET BY CHOOSING NEARLY INSTANTANEOUS LAUNCH WINDOW FOR EO-1. MLT DISPERSIONS WILL BE CORRECTED • ASCENT MANEUVERS WILL START 3 DAYS AFTER LAUNCH - ASCENT PHASE DURATION AND PROPELLANT USAGE WILL DEPEND ON THE INITIAL PHASING WITH LANDSAT-7 AT EO-1 INJECTION (MAY VARY BY A FACTOR OF 2) • FORMATION FLYING CONTROL WILL BE PERFORMED BY EO-1

  15. AM CONSTELLATION LANDSAT-7, EO-1, TERRA AND SAC-C ARE THE MEMBERS OF THE “AM CONSTELLATION” WHICH WILL PARTICIPATE IN IMAGING ACTIVITIES AND STUDIES The EO-1/SAC-C LAUNCH WILL DELIVER THE FINAL MEMBERS OF THE CONSTELLATION INTO ORBIT

  16. BASELINE ASCENT PLAN • 8 MANEUVERS SPACED EVERY 48 HOURS AFTER L+3 DAYS • START DATE NOMINALLY 3 DAYS AFTER INJECTION • GROUND STATION OR TDRS COVERAGE IS DESIRABLE FOR EACH ASCENT MANEUVERS • AFTER LAUNCH, FDSS WILL PREPARE AN UPDATED ASCENT PLAN AND BRIEF PROJECT MANAGEMENT ON AVAILABLE OPTIONS • MORE DETAILS REGARDING CONTINGENCY PLANS IN PROJECT DOCUMENT

  17. BASELINE ASCENT PLAN Assumes Propellant Load of 49.16 lbm (22.9 kg) Ascent Nominal Propellant Budget: 6.11 lbm (2.77 kg) Ascent Profile Duration: ~17 Days

  18. ROUTINE GTC MAINTENANCE MANEUVER PLAN • PLAN TO DO GROUND TRACK MAINTENANCE MANEUVERS TO MEET CO-FLY REQUIREMENTS WITH LANDSAT-7: • AS FREQUENTLY AS EVERY WEEK FOR HIGH SOLAR FLUX • AS INFREQUENTLY AS EVERY 3 WEEKS FOR LOW SOLAR FLUX • INCLINATION MAINTENANCE • FUEL BUDGET INCLUDES REMOVING ELV INCLINATION DISPERSIONS PLUS ONE MANEUVER ABOUT MID-OCTOBER 2001 FOLLOWING PLANNED LANDSAT-7 INCLINATION BURN • THE INITIAL INCLINATION WILL BE CHOSEN TO KEEP EO-1’s MLT AT THE DESCENDING NODE WITHIN 1 MINUTE OF LANDSAT-7’S MLT (+/- 6 SECONDS)

  19. ORBIT DETERMINATION • LAUNCH AND EARLY ORBIT • FDF PROVIDES EO-1 MOC - LAUNCH VEHICLE INSERTION VECTOR AND CODE 500 EPHEM FOR USE AS A PRIORI IN INITIAL OD SOLUTION AT EO-1 MOC - 46 CHARACTER C-BAND RADAR TRACKING DATA FILES - FDF’S INITIAL OD SOLUTION VECTOR AND EPHEM DURING FIRST FEW HOURS AFTER LAUNCH USING TDRS DOPPLER, GN S-BAND AND C-BAND RADAR TRACKING DATA • TDRS DOPPLER DATA WILL BE RECEIVED SOLELY AT FDF. WHILE EO-1 IS NON-COHERENT, DIFFERENCED 1-WAY DOPPLER FROM TWO TDRSs MAY BE RECEIVED. • EO-1 MOC WILL USE GN S-BAND AND C-BAND RADAR TRACKING DATA TO GET INITIAL OD SOLUTION

  20. ORBIT DETERMINATION • ON ORBIT • USING GPS ONBOARD NAVIGATION SYSTEM (PRIME); GN S-BAND DATA USED FOR GPS VALIDATION AND BACKUP OD • POSITION KNOWLEDGE REQUIREMENT IS BEST AVAILABLE, BUT EXPECTED TO BE 20-30 METERS, 3-SIGMA ON BOARD • GPS ORBIT SOLUTION COMES DOWN IN TELEMETRY IN SCIENCE AND HOUSEKEEPING PACKETS. • NO DEFINITIVE REQUIREMENT, BUT EPHEMERIS OVER DATA ARCS PROCESSED ON THE GROUND WILL BE ARCHIVED TO TAPE

  21. CSOC/FDF INTERFACE • FDF WILL PERFORM THE FOLLOWING FUNCTIONS: • LAUNCH VEHICLE SUPPORT • TRACKING DATA EVALUATION AND LOCAL OSCILLATOR FREQUENCY CALCULATIONS • DELIVERY OF ACQUISITION DATA TO C-BAND SITES • DELIVERY OF ACQUISITION DATA TO NCC FOR TDRS L&EO AND CONTINGENCY SUPPORT • SPACECRAFT ORBIT DETERMINATION (1ST 8 HOURS OF L&EO) • DELIVERY OF 46 CHARACTER C-BAND RADAR TRACKING DATA TO EO-1 MOC • DELIVERY OF LAUNCH VEHICLE INSERTION VECTOR AND EPHEM TO EO-1 MOC • DELIVERY OF INITIAL OD SOLUTION VECTOR AND EPHEM TO EO-1 MOC • LOF MAINTENANCE FOR LOCAL OSCILLATOR

  22. ATTITUDE AGENDA • ATTITUDE ORIENTATION AND SENSORS • ATTITUDE DETERMINATION SYSTEM • MOMENTUM MANAGEMENT • IRU & TAM SENSOR CALIBRATION • INSTRUMENT CALIBRATION MANEUVERS • AST FAILURE OPTIONS

  23. ATTITUDE ORIENTATION Expected ACS Performance < 60 arcsec per axis; Combined Knowledge & Control for Imaging

  24. SENSORS Litton SIRU (3 HRGs) Lockheed/Martin AST-201 Three-Axis Magnetometer (TAM) 4 Coarse Sun Sensors GPS ACTUATORS 3 Reaction Wheels 3 Magnetic Torquer Bars 4 Thrusters ATTITUDE CONTROL HARDWARE

  25. ATTITUDE DETERMINATION SYSTEM • PC based MATLAB/ADS with customized TP, RTADS interface to ASIST, and RTADS displays • TP is used processes GPS data into PCE tracking data format for use in PODS • Integrated with customized OBC Table Utilities to convert TAMCAL and IRUCAL results into ACS Flight Software Tables • MATLAB/ADS was tested using data generated using VSAT and ASIST

  26. MOMENTUM MANAGEMENT • Momentum Management and Attitude Planning (MMAP) is a MATLAB based utility that is integrated with the Mission Planning System (MOPSS) • Used to bias Reaction Wheels to avoid zero crossings during Imaging and also used to plan Pre-Image slews that include Yaw Steering and Instrument Offsets • MMAP was tested “End-to-End” using MOPSS and VSAT to verify proper Momentum and Attitude • Also runs in “Standalone” mode to plan Engineering Slews

  27. IRU SENSOR CALIBRATION • IRU calibration is performed during Spacecraft Checkout (and as needed thereafter) • IRU calibration slews are planned using MMAP and will consist of 3 pairs of “out and back” orbital referenced slews that occur on Mission Day 3 • IRU calibration sequence was tested “End-to-End” using VSAT for ACS simulation and error modeling, ADS for attitude determination, IRUCAL to solve for the G-Matrix (and biases), and the Flight S/W Lab to verify proper ACS Table phasing and magnitude

  28. TAM SENSOR CALIBRATION • TAM calibration is performed during the Spacecraft Checkout (and as needed thereafter) • TAM calibration will make use of the IRU calibration slews because of the high Torquer Bar activity • TAM calibration sequence was tested “End-to-End” using VSAT for ACS simulation and error modeling, ADS for attitude determination, TAMCAL to solve for the misalignment, scale factor, bias, and MTB coupling, and the Flight S/W Lab to verify proper ACS Table phasing and magnitude

  29. INSTRUMENT CALIBRATION MANEUVERS • Calibration Maneuver (CALMAN) is a MATLAB based utility that is used to plan all instrument calibration slews (Solar, Lunar, Deep Space) • CALMAN provides the capability to check the slews for AST and Instrument constraint violations • CALMAN was tested using VSAT to model slews and RTADS to verify proper attitude • Solar Calibrations involve a single slew to an inertial attitude to allow an individual instrument to view the Sun

  30. INSTRUMENT CALIBRATION MANEUVERS • Lunar Calibrations involve a series of slews to get the Moon to move through each instrument FOV at a specified rate:

  31. AST FAILURE OPTIONS • Short Term Option: Use RTADS to perform a TAM/IRU KF Solution and uplink a Delta-Quaternion near the end of a ground support. This solution is developed and tested using VSAT, ASIST, and RTADS. • Mid Term Option: Use ADS to perform a TAM/IRU Batch Solution and uplink a Delta-Quaternion on next available support. This solution would need minor modifications to the ADS. • Long Term Option: Modify ACS (TRMM Heritage) to use TAM (instead of AST) as input to the KF.

  32. FLIGHT DYNAMICS TEAMOPERATIONS READINESS • OPS CONCEPT • STAFFING • TRAINING • SIMULATIONS

  33. OPERATIONS CONCEPT • FDAB/FOT PERSONNEL OPERATE FDSS UNTIL EARLY MISSION CHECKOUT IS COMPLETE. ACTIVITIES SUPPORTED INCLUDE: • LAUNCH, INJECTION, AND ASCENT TO MISSION ORBIT • ATTITUDE SENSOR CALIBRATION MANEUVERS • FIRST TWO GROUND TRACK MAINTENANCE MANEUVERS (COMPLETED BY ~ L + 45 DAYS) • INITIAL INSTRUMENT CALIBRATION MANEUVERS • FDAB THEN HANDS OVER ALL RESPONSIBILITY FOR FUNCTIONS TO EO1 FOT FOR ROUTINE OPS.

  34. OPERATIONS CONCEPT • PRIOR TO HANDOVER: • FDAB WILL PROVIDE TRAINING TO FOT • FDAB WILL PROVIDE DOCUMENTATION OF PROCEDURES AND SYSTEM OPERATIONS • PARALLEL OPERATIONS WILL BE PERFORMED BY FOT AND FDSS TEAM • AFTER HANDOVER: • FOT PROVIDES ROUTINE OPERATIONS SUPPORT • FDAB ON CALL FOR CONTINGENCY, ANOMALY RESOLUTION NO HANDOVER UNTIL FDAB DETERMINES THAT FOT IS READY

  35. STAFFING PLAN - L&EO • TWO (2) TWELVE HOUR OPERATIONS SHIFTS (PLUS OVERLAP TIME FOR HANDOVER) • PRIME SHIFT, 9:00 AM TO 9:30 PM (CONTAINING ORBIT/ATTITUDE MANEUVERS) • -4 ENGINEERS COVERING THE FOLLOWING FUNCTIONS: • ATTITUDE SUPPORT, ORBIT DETERMINATION, ORBIT MANEUVERS AND PRODUCT GENERATION • OFF SHIFT, 9:00 PM TO 9:30 AM • - 2 ENGINEERS COVERING THE FOLLOWING FUNCTIONS: • ATTITUDE SUPPORT AND PRODUCT GENERATION • SOFTWARE SUPPORT PROVIDED ON CALL

  36. CALLUP PLAN • IF ADDITIONAL/ALTERNATIVE STAFFING IS NEEDED, THE OPS LEAD WILL: • CALL THE EMPLOYEE IDENTIFIED AS A SOLE SOURCE TO RESOLVE THE PROBLEM • CALL THE EMPLOYEE’S SUPERVISOR TO MAKE THEM AWARE OF THE PROBLEM AND THE STAFFING CHANGE

  37. MANAGEMENT NOTIFICATION • DURING NOMINAL OPERATIONS, FDAB MANAGEMENT WILL RECEIVE DAILY REPORTS OF ACTIVITES COMPLETED AND CURRENT STATUS. • IN THE EVENT OF A CONTINGENCY, FDAB MANAGEMENT WILL BE NOTIFIED AS SOON AS POSSIBLE BY THE FDE

  38. FDSS TEAM TRAINING Flight Dynamics Support System Team (FDSST) • TRAINING TRACKED BY AREAS OF SPECIALIZATION USING MATRIX • PROFICIENCY LEVELS DEFINED FOR EACH TEAM MEMBER, BASED ON SUPPORT ROLES Flight Operations Team (FOT) • CONTINUOUS TRAINING THROUGH HANDOVER • ALREADY PROVIDED SOME S/W TRAINING, MORE TO COME • OPS NOTEBOOK DESIGNED FOR EASY UPDATES

  39. FDSS TEAM TRAINING AREAS • ORBIT: Navigation and Maneuvers: • Pre-process Tracking Data, Orbit Determination, O. D. Quality Assurance, Tracking Data Archiving, EFF Orbit Maneuver Planning, Thruster Calibration, Est. of Propellant Remaining, EFF Table Generation • ATTITUDE : • Attitude Determination, IRU Calibration, TAM Calibration, Slew Planning, ADS Utilities • PRODUCTS: Generation and Delivery • DATABASE: Maintenance & Archiving

  40. FDSS TEAM TRAINING

  41. FDSS TEAM TRAINING STATUS • ALL TEAM MEMBERS HAVE ACHIEVED MINIMUM PROFICIENCY LEVELS SUFFICIENT TO SUPPORT LAUNCH • SUSTAINED TRAINING ACTIVITIES WILL ACHIEVE DESIRED GOALS PRIOR TO LAUNCH • IMPROVED TEAM PERFORMANCE • IMPROVED STAFF FLEXIBILITY

  42. COMPLETED: ATTITUDE CALIBRATION MANEUVER ASCENT MANEUVERS (IN & OUT OF PLANE) GROUND TRACK MAINTENANCE ATTITUDE TELEMETRY LAUNCH DAY & FDF INTERFACE NAVIGATION END-TO-END ACQ DATA TO WOTIS & NCC NON-NOMINAL MANEUVER LAUNCH VEHICLE OPM DELIVERY PRODUCT GENERATION ELECTRONIC INTERFACE TESTS AND BACKUPS WITH PIs, WOTIS, NCC, AND McMURDO INSTRUMENT CALIBRATION FUTURE: INCLINATION DELTA-V INTERNAL SIMULATIONS

  43. EXTERNAL SIMULATIONS • BETWEEN 10/99 AND 10/00, THE FDSS TEAM SUPPORTED THE EO-1 PROJECT DURING: • - MONTHLY LAUNCH & EARLY ORBIT SIMS • - MONTHLY SCIENCE DATA COLLECTION AND PROCESSING SIMS • - NETWORK SIMS WITH THE SN (4) AND THE WALLOPS GN (6)

  44. SYSTEM DESCRIPTIONAND READINESS • FACILITY CONFIGURATION • ARCHITECTURE OVERVIEW • SOFTWARE STATUS • TESTING STATUS • CERTIFICATION

  45. FDSS HARDWARE 2 Hewlett Packard workstations (1 prime; 1 backup) • software: Satellite Toolkit (STK), Ephemeris Utilities, Real Time Attitude Determination System (RTADS), MATLAB attitude tools, Precision Orbit Determination System (PODS), AutoProducts 4 Pentium Pro PCs (2 prime; 2 backup) • software: FreeFlyer, Microsoft Office, MATLAB attitude tools, NFS/MAESTRO; STK/PRO 4 Hewlett Packard workstations (2 prime; 2 backup) in FDF for initial EO-1 L & EO support ALL FDSS PLATFORMS CONNECTED TO SHARED DRIVES.

  46. FDSS INTERFACES MOPSS (P&S, CMS,DMS) Principal Investigators • • EPVs • Manv. Cmds. • Sci. Planning • & • Health & Safety • Products • FDSS Planning Products ASIST (Epoch 2000) • RT TLM Science Validation Facility • Mis-Align. Utility • RT TLM • Carry-Out Files Flight Operations Team • Pass Schedules FDF (bldg 28) • OPM (Post-Sep.) • C-Band Data • Ephemeris Files • Acquisition Data FDSS • UTC-UT1 • STK/PODS Files • JPL Files • FDF Files Internet • Acq Data NCC • • Acq Data • Tracking Data • Scheduling PSATs WOTIS

  47. FDSS MOC CONFIGURATION FOR L&EO

  48. L & EO PRODUCT GENERATION • ORBIT DETERMINATION (USING GPS) - DAILY; O.D. VERIFICATION (USING S-BAND) WEEKLY • 25 ORBIT & ATTITUDE PRODUCTS (IMAGE PLANNING & SCHEDULING, TABLE LOADS); • - FOLLOWING EVERY ASCENT MANEUVER PLAN - 8 DAY LENGTH • - FRIDAY: 35 DAY LENGTH • ORBIT MANEUVER COMMAND SHEETS - AS REQUIRED • RUN RTADS EVERY REALTIME PASS > 32 Kbps • INSTRUMENT CALIBRATION PLANS - AS REQUIRED

  49. NORMAL OPS PRODUCT GENERATION • ORBIT DETERMINATION (USING GPS) - M-W-F; O.D. VERIFICATION (USING S-BAND) WEEKLY • 25 ORBIT & ATTITUDE PRODUCTS (IMAGE PLANNING & SCHEDULING, TABLE LOADS); EVERY M-W-F • - MONDAY & WEDNESDAY: 8 DAY LENGTH • - FRIDAY: 35 DAY LENGTH • ORBIT MANEUVER COMMAND SHEETS - AS REQUIRED • RUN RTADS ON REQUEST • INSTRUMENT CALIBRATION PLANS - AS REQUIRED

  50. STK / PODS / executable: version 4.1.1, done - RFI sites may be added (not launch critical) AUTOCON-G / executable: version 4.3, done AutoProducts (STK/PODS), done AutoProducts (AUTOCON-G), final testing for retrofit to AUTOCON-G V4.3 (not launch critical) FreeFlyer/executable: version 4.8.0.6, done MATLAB ADS: version 2000.01, done MATLAB EO1MAN (MMAP & CALMAN): version 1.6, done MATLAB WRSSUN: version 1.0, done MATLAB ALI Mis-Alignment: version 1.2, done SOFTWARE STATUS

More Related