Input to CCSDS P&P WG

1. Input to CCSDS P&P WG Chris Taylor CCSDS 2011 Berlin

2. Introduction • In reviewing the IEE1451 and CANOpen specs for the use of EDS, it is apparent that certain architectures are assumed by the standards • These architectures influence the point at which interfaces are exposed and the application of the EDS • In particular, both 1451 and CANopen assume an intelligent controller which insulate the host software from underlying details of the connected sensors and actuators • Such an architecture is similar to that being proposed by ESA for a standard building block Remote Terminal Unit (RTU) – essentially a data concentrator • We need to take account of these architectures both to ensure that SOIS is compatible but also to understand the use of EDS ESA UNCLASSIFIED – For Official Use

3. Cryosat ESA UNCLASSIFIED – For Official Use

4. RTU as element of P/F Avionics: P/L MMU P/L SpW, HSSL,SpF MIL-STD-1553B, CAN, SpW P/L Bus CDMU ECSS-E-ST-50-13C ECSS-E-ST-50-12C,… ECSS-E-ST-50-15dr MIL-STD-1553B CAN RS-422 SpW ECSS-E-ST-50-14C ECSS for digital sensor busses RTU P/F Bus RTU2015 PCU/PCDU Sensors & Actuators (T, AOCS, Propulsion, …) Power Bus Load ESA UNCLASSIFIED – For Official Use

5. Avionics 2015: RTU2015 Command and control Bus (Can, Milbus, SpaceWire) • Remote terminal unit acts as a data concentrator • Standard interface to OBC/CDMU with a standardized protocol • Standard Serial bus to devices • S/C may employ several miniaturised versions RTU Micro Controller/FPGA Standard Interface Memory Motor Drive Module Memory HK Module Digital Sensor bus Standard Digital Bus (SPI, I2C, …) M Sensors and Actuators Aeronautics/Embedded examples of RTUs ESA UNCLASSIFIED – For Official Use

6. RTU : possible configurations ESA UNCLASSIFIED – For Official Use

7. DAS DAS Device Access protocol Device Access protocol Data link any Data link any Serial I2C 1 Wire EDS EDS DVS Virtual EDS Functional contr Mem EDS EDS CDMU RTU ESA UNCLASSIFIED – For Official Use

8. DAS DAS Device Access protocol Device Access protocol Data link any Data link any Serial I2C 1 Wire EDS EDS DVS Virtual EDS EDS Functional contr Functional Mem EDS EDS CDMU RTU ESA UNCLASSIFIED – For Official Use

9. IEEE 1451 – “RTU Architecture” ESA UNCLASSIFIED – For Official Use

10. 1451 – use of TEDs ESA UNCLASSIFIED – For Official Use

11. SMU PM TC Management TM Management OBT Management FDIR Management MdM Management AOCS Management Power Management Thermal Management Payload management RM Alarms PDHT P/L C&C bus P/L BC CPDU P/F ON/OFF HLC TTC RF Sub-system Payload Instruments TC Decoder Security Module S band RX POWER S/S PCDU TM Encoder S band TX 1553 BC SADM MM Payload Instruments OBT PPS Thermal P/F Heaters Discrete I/Os Thermistors P/F Monitoring Payload Instruments SpaceWire Mil-1553 bus AOCS Sub-system Propulsion Sub-system P/L Essential Monitoring GPS STR CRS RW CSS MAG MTB Thrusters LV Tank Pt Payload Platform Traditional architecture ESA UNCLASSIFIED – For Official Use

12. IEEE 1451 standards ESA UNCLASSIFIED – For Official Use

13. Questions for SOIS WG • IEEE1451 use the same architecture as the proposed ESA RTU. 1451 uses XTEDS for devices but presents a standard API for access over the user network – How does this fit with the SOIS P&P architecture, in particular the DAS and DVS • ESA is also standardising the use of CANBus as a primary onboard bus. CANBus has its own (text based) EDS – how does this fit with the SOIS P&P architecture? (important as use of CAN will force equipment suppliers to provide EDS’s) • There are several “object dictionaries” (1451, CAN, XTEDS) available – how (should we) do we rationalise these into a single view and document? • Our diagrams to not yet reflect the use of a device specific protocol to support the device access service – propose this should be identified/specified as this will be needed e.g. for standard access to an RTU • The SPA guidebook contains a section on SOIS – is everybody happy that the text correctly reflects the comparison with SPA? • The Green book has been updated, are there still actions and updates and what are the plans for the review and release? • Although we made a great step forwards at the last meeting and reflected the results in the Green book, I’m concerned that the GB text is a little ‘academic’ and would benefit from a practical example to supplement the layered model – comments anyone? ESA UNCLASSIFIED – For Official Use

14. Reference architecture ESA UNCLASSIFIED – For Official Use

15. SMU PM TC Management TM Management OBT Management FDIR Management MdM Management AOCS Management Power Management Thermal Management Payload management RM Alarms PDHT P/L C&C bus P/L BC CPDU P/F ON/OFF HLC TTC RF Sub-system Payload Instruments TC Decoder Security Module S band RX POWER S/S PCDU TM Encoder S band TX 1553 BC SADM MM Payload Instruments OBT PPS Thermal P/F Heaters Discrete I/Os Thermistors P/F Monitoring Payload Instruments SpaceWire Mil-1553 bus AOCS Sub-system Propulsion Sub-system P/L Essential Monitoring GPS STR CRS RW CSS MAG MTB Thrusters LV Tank Pt Payload Platform Traditional architecture ESA UNCLASSIFIED – For Official Use

16. Avionics 2015: Platform S/s and I/Fs P/L Bus Sensors & Actuators (T, AOCS, Propulsion, …) OBC/CDMU/ SMU P/F Bus TX RTU RTU analog digital PCDU MIL-STD-1553B (CAN) Propulsion AOCS Sensors & actuators AOCS Sensors & actuators ESA UNCLASSIFIED – For Official Use