1 / 19

EUSO-SODC status report

EUSO-SODC status report. M.C. Espírito Santo Huntsville, May 2003. Contents. Mid-Term Review “EUSO operations: flight & ground” document The comments Replies & evolution Towards the end of Phase A Specific documents Contribution to end of phase A report.

syshe
Download Presentation

EUSO-SODC status report

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. EUSO-SODC status report M.C. Espírito Santo Huntsville, May 2003

  2. Contents • Mid-Term Review • “EUSO operations: flight & ground” document • The comments • Replies & evolution • Towards the end of Phase A • Specific documents • Contribution to end of phase A report

  3. “EUSO operations: flight and ground” document A description of EUSO operations concept, covering flight and ground segments. • One of the documents requested for MTR package • Prepared by SODC team, with collaboration of TEO, • on IM request

  4. “EUSO Operations: flight and Ground” 2EUSO system description 2.1The flight segment 2.2The ground segment 2.3End-to-end communications scheme • 3EUSO operations concept • 3.1Basic operational requirements and constraints • 3.1.1Telemetry and telecommand budget • 3.2Operations overview • 3.3Calibration • 4Flight operations • 4.1System functionalities • 4.2System elements • 4.3System interfaces • 5Ground operations • 5.1System functionalities • 5.2System elements • 5.3System interfaces

  5. EUSO COL-APM TDRS MCC-H COL-CC WSGT COL-APM: Columbus Attached Pressurized module TDRS: Track and Data Relay Satellite system WSGT: White Sands Ground Terminal MCC-H: Mission Control Center – Houston Col-CC: Columbus Control Center SODC: Science Operations and Data Center (EUSO) SODC End-to-end communications scheme Ku-band S-band

  6. TVF TC ICR M A D B TCG C I Subsystems TMH DPM ICF TM AS UIF EDBIF TCG: TC Generation TMH: TM Handling MADB: Mission Archive and DB TVF: Test and Validation Facility SWM: SW Maintenance MAP: Mission Activity Planning DPM: Data Processing and Monitoring UIF: User I/F EDBIF: External DB I/F ICR: Instrument Control and Readout ICF: Instrument Configuration Files CI: Communications Interface AS: Atmospheric Sounding system Operations concept Ground Segment Flight Segment MAP

  7. Power off Initialisation HK1 Diagnostic HK1,HK2,SC5 Standby HK1,HK2 Technical calibration HK1,HK2,SC4 Engineering mode HK1,HK2 Observation HK1,HK2 EECR SC1 SC2 SC3 Slow GLS calib Flight operations • The on-board operations system has different Operational States • In each mode given TM packets are • generated and given TC are accepted • Collection and pre-processing of the scientific data • Collection and verification of HK data • Preparation of TM packets • TC handling • Management of the trigger configuration • Management of the different subsystems • Management of emergency situations • Interface to the atmospheric sounding system

  8. The MTR comments • On-board operations: • Level of autonomy defined as high but no precise info given • Definition of on-board operations system unsatisfactory: processing power cannot be deduced • Calibration of the instrument undefined • Telemetry & telecommandbudgets largely unspecified On MTR preliminary report:

  9. On-board autonomy 1 Definition of level of autonomy of on-board operations crucial for the dimensioning of EUSO flight and ground systems • No permanent contact is provided • Limited uplink capability • More on-board processing capability and redundancy required • Particular care with test and validation facilities • Clearly define operations concept • Be more concrete on definition of autonomy • Refer to appropriate (electronics) document for details on on-board system

  10. On-board autonomy 1 Current concept: • Transitions between states controled by on-board system and triggered by • Time-tagged commands uplinked from ground • Reception of ISS ephemeris parameters • Exceptional events • Within each operational state the on-board system is totally autonomous • Most “routine” transitions can be performed autnomously (see next slide) • Ground commands organised in schedule files containing only specific actions: calibration, system configuration setting Example: Shutter closing triggered by ISS ephemeris (position or time) and commanded autonomously by on-board system. Also: autonomous contingency procedure

  11. Power off Power_On/Off Initialisation HK1 Ground TC Non-observation Standby HK1,HK2 Contigency HK1,HK2 Setting mode HK1,HK2,SC5 Ground TC Engineering mode HK1,HK2,HK3 Technical Calibration HK1,HK2,HK3,SC4 HK1,HK2,HK3 Observation modes Slow SC2 EECR SC1 Science Calib SC3 On-board autonomy 1 Discussions with P. Tua and A. De Masi

  12. Calibration 2 • Autonomy / ground command • Procedures • TM volume? • Calibration issues are a more general question • Only operations point of view to be discussed in this document Technical Scientific e.g. GLS e.g. diode system • Paragraph on calibration operations, vague at this stage • Calibration working group !

  13. Telemetry/Telecommands budget 3 Current assumptions for available resources: Telemetry Assuming 300 Kbit/s for 10 min. => 180 Mbit/orbit Telecommands EUSO: similar reasoning => 360 Kbit/orbit (TBC)

  14. Telemetry Type Telemetry volume/Orbit Scientific - EECR 0.7 Mbit HK 30 Mbit Atmopheric 0.75 + 14.5 Mbit Calibration 1 Mbit (GLS) + TBD EUSO TM needs (TBC) 3 • Science - EECR data: • GTU 1 ms, 300 GTU, 1 event/orbit assumed, • Baseline (X,Y, ph_cnt, 9 macrocells) (Pixel info: 12 Mbit ?) • Slow events: ~EECR, rate TBD • HK: FS + TCU + LIDAR (see P. Tua estimation) • Atmospheric data: AS document: • 25 Kb/s for 30 s on EECR • 2.5 Kb/s continuous • Calibration: • GLS: assumptions of OM doc (30 Hz, 2 ms, 30 s, once per 24 hours) • Technical:can be critical • Telemetry peaks in certain orbits

  15. Telecommands 3 In large autonomy scenario, uplink is: • Time-tagged commands for “non-routine” operations (expected to be low) • Updates of configuration parameters • Dominated by FS parameters • Of the order of 10 K parameters (TBC) • One configuration file per operation mode x several operation conditions ~ 200 Kbytes of configuration files (TBC) • Update rate: 10% in orbit (TBC) • SW patches/upgrades: TBD • Still many open questions: • Sizes and rates • Bandwidth during commissioning phase • Possibility of larger bandwidth for SW upgrades

  16. EUSO operations: flight & ground • EUSO system description • EUSO operations concept • Observing plan • Basic requirements & constraints • Operations overview • Instrument calibration • Flight operations • System functionalities • System modes of operation • Operation modes diagram • On-board autonomy • Configuration parameters • HK parameters • System elements & interfaces • Ground operation • Telemetry & Telecommand budget

  17. Towards the end of Phase A Two specific documents • EUSO operations: flight and ground • Phase A specification and design document for the EUSO SODC ... And contribution to Final Phase A report

  18. Unit 1 TCG Telecommand generation MAP Mission Activity Planning TVF/SWM Test & validation Facility / SW Maintenance Unit 2 TMH Telemetry reception & handling MON Data Monitoring PROC Data Processing Unit 3 ADB Archive & database maintenance UIF User Interface & Support EDB External databases interface SODC document • Introduction • SODC objectives & lifecycle • SODC components and functionalities • SODC budget and timeline “Phase A specification and design document for the EUSO-SODC”

  19. Concluding ... • Section 7: Operations (C. Espirito Santo) Data products: C. Maccarone Closely connected to: • Section 6: Mission overview (A. De Masi) • Readout & control electronics (O. Catalano / P.Tua) • Updated version of MTR Operations doc under way • SODC specifications and design doc for end of Phase A 3. Final Phase A report

More Related