1 / 21

Exchanging Databases with Dissimilar Systems Using CCSDS XTCE

Exchanging Databases with Dissimilar Systems Using CCSDS XTCE. CCSDS Spacecraft Monitoring & Control WG and OMG Space Domain Task Force Presented by Mario Merri, ESA. Outline. Where does XTCE come from? Its goals and benefits How does it work? Usage so far Conclusions. FUTURE. NOW.

bianca-carrillo
Télécharger la présentation

Exchanging Databases with Dissimilar Systems Using CCSDS XTCE

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. Exchanging Databases with Dissimilar Systems Using CCSDS XTCE CCSDS Spacecraft Monitoring & Control WG and OMG Space Domain Task Force Presented by Mario Merri, ESA

  2. Outline • Where does XTCE come from? • Its goals and benefits • How does it work? • Usage so far • Conclusions 28 March 2006, GSAW

  3. FUTURE NOW Editors1   MCS   Editors2   FDS       PGS2   ODB SDB MPS     EGSE PGS1   Proprietary Formats Standard Formats (XTCE) SIM AIV OPERATIONS XTCE Vision AIV: Assembly, Integration Verification DB: Database EGSE: Electrical Ground System Equipment FDS: Flight Dynamics System MCS: Mission Control System MPS: Mission Planning System ODB: Operational Database PGS: Procedure Generation System SDB: Source Database SIM: Spacecraft Simulator 28 March 2006, GSAW

  4. XTCE History • Object Management Group (OMG) standard originally developed by • European Space Agency • US Air force/Mission Operations (Lockheed Martin) • Boeing Communications & Satellites • NASA & JPL • Being adopted by CCSDS via Agency Review under responsibility of SM&C WG 28 March 2006, GSAW

  5. CCSDS SM&C and XTCE • ESA • M Merri (chairman), M Schmidt, A Ercolani, J Muller,I Dankiewicz, S Cooper • BNSC • R Thompson (deputy chairman), B Harnett • CNES • B Béhal, E Poupart, R Soumagne • CSA • P Melanson • DLR • H Hofmann • INPE • PG Milani, AM Ambrosio • JAXA • T Yamada • NASA/GSFC • DC Lokerson, F Johnson, JK Marquart, JS Gal-Edd, C Fatig,R Jones,K Rice • NASA/JPL • A Oyake, P Shames, J Moholt • ASI • C Labonia • OMG • G Simon (Lockheed Martin), B Kizzort (Harris Corp.) XTCE Splinter Group 28 March 2006, GSAW

  6. XTCE Goal • Non-proprietary standard format to exchange TM & TC data definitions that will reduce • human errors • ambiguities, confusion, and • lost time and money in difficult, sometimes lousy (painful) conversions between dissimilar systems 28 March 2006, GSAW

  7. Planning Scheduling XTCE Format Instrument Manufacturers Command Management Real time Spacecraft Manufacturers Simulators Trending Analysis Application Field • Exchange between • working teams • Systems • missions • agencies • Reuse legacy systems • Adapt only I/O • Reduce costs 28 March 2006, GSAW

  8. XTCE Benefits • Allows better interoperability • Across organisations (e.g. JWST) • Within a mission (e.g. S/C Prime -> operations) • Lets different philosophies collaborate in one data model • Separates “pure” telemetry and telecommand data from dedicated/proprietary processing data • Able to extend for data items not currently defined 28 March 2006, GSAW

  9. XTCE Scope • TM & TC definitions are very similar between space systems … • XTCE defines standard exchange formats for: • TM & TC parameter properties • Telemetry • Telecommand • Data transmission and packaging • Uses XML Schema technology • Covers only exchange of operational TM & TC information • e.g. no displays, no operational procedures 28 March 2006, GSAW

  10. XTCE Hierarchy • The “SpaceSystem” is the basic building block • “SpaceSystems” produce/consume TM/TC • “SpaceSystems” associate hierarchically one another • Their granularity is left to the user • The hierarchy allows integration of multiple data description into one overall data description • e.g. multi-satellite missions, multi-instrument satellite 28 March 2006, GSAW

  11. Example: XTCE for a single spacecraft Space System Spacecraft level Space System Space System One satellite DB Instrument level Space System Space System Device level 28 March 2006, GSAW

  12. Example: XTCE for a constellation Space System Constellation level Space System Space System Multi-satellite DB Satellite level Space System Space System Instrument level 28 March 2006, GSAW

  13. XTCE SpaceSystem Basics • A SpaceSystem describes: • Telemetry parameters, their packaging and dedicated processing • Telecommand arguments, their packaging and dedicated processing • Streams (up and down, with coding information) • Minimal configuration information • Conversion information • Limits and pre/post command checks 28 March 2006, GSAW

  14. Header for configuration data Telemetry for core data Telecommand for core data Services for packet identification XTCE SpaceSystem Decomposition Space System Header Telemetry Telecommand Services 28 March 2006, GSAW

  15. XTCE Telemetry Data • Telemetry data consists of: • Parameter types • Encoding • Limit checking information • Calibrations • Unit (mnemonic) • Parameters • Validity conditions • Containers • e.g. CCSDS frames or packets • Streams • Encoding, decoding of frames • e.g. sequences of frames on a VC • Algorithms • e.g. derived parameters Logical sequence of definition 28 March 2006, GSAW

  16. XTCE Container and Stream Ver # Type P.hdr f APID Gr. f SSC P.h.len Container: Packet header Container: Packet Packet header Packet data field Frame primary header Frame secondary header Frame data field Op.ctrl Err.ctrl Container: Frame Sequence of those frames Stream Parameter Container 28 March 2006, GSAW

  17. XTCE Telecommand Data • Telecommand data consists of: • Parameter types • Used if no parameters defined in the telemetry data • Parameters • Used if not parameters defined in telemetry data • Containers • Frames and packets, reused by command containers • Metacommands (i.e. command definitions) • Arguments • Command container (data field of a TC packet) • Transmission constraints • Interlock • Verifiers (execution, transmission, reception) • Streams • Telecommand link, sequences of frames • Algorithms • Additional processing tasks, external scripts Logical sequence of definition 28 March 2006, GSAW

  18. XTCE Applications so far • NASA: James Webb Space Telescope XML Schema converted: • Future work includes exchanging database with other archive systems and control centre real-time systems • ESA: two conversion tools created: • Rosetta database converted • Cryosat database converted • Industry: • EADS: scaleable monitoring & control system uses XTCE • Hardware vendors deliver the database information in XTCE format to the spacecraft integrator on some US programs 28 March 2006, GSAW

  19. CCSDS Documentation • Draft CCSDS Green book • Tutorial • Pending publication • CCSDS Magenta book • Best practices report, developer guide for CCSDS missions • Released for internal CCSDS review • Validation at ESA and NASA ongoing • CCSDS Red book released • Adopting OMG XTCE 1.1 • Under agency review until 20th March 2006 28 March 2006, GSAW

  20. Conclusions • XTCE powerful concepts are ideal for exchanging TM & TC data descriptions across: • planning systems • legacy tools can be (temporarily) maintained by the addition of I/O adaptors • real-time command and control systems • Easily translated between the project XML database format and XTCE, no longer just a concept but being used internationally • XML technologies usage: • XML self-describing nature reduces learning curve and errors • XML is easy to work with, due to the amount of libraries, tools, and broad industry acceptance 28 March 2006, GSAW

  21. Questions and Answers ? 28 March 2006, GSAW

More Related