ESA UNCLASSIFIED – For Official Use SOIS architecture to handle RIUs F. Torelli (ESA) & G. Rakow (NASA) 15/04/2013

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 2 ESA UNCLASSIFIED – For Official Use Outline Remote Interface Unit (RIU) definition Tunnelling RIU and SOIS Smart RIU and SOIS RIUs and SOIS EDS Summary The presentation summarises the tech note “Aggregated devices in SOIS and SOIS EDS” distributed to the SOIS WG mailing list on 28/11/2012

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 3 ESA UNCLASSIFIED – For Official Use Remote Interface Unit (RIU) definition

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 4 ESA UNCLASSIFIED – For Official Use Remote Interface Unit 1/2 Also known as Remote Terminal Unit Connects devices to the Processor Module (PM) where flight SW (FSW) runs Data concentrator Physical aggregation Interfaces to very simple sensors/actuators Interfaces to smart devices Handles point-to-point links Handles sensor buses Processor Module RIU FSW DEV1 DEV2 DEVA DEVB DEVC I/F Logic System bus/subnetwork Sensor bus Point-to-point link

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 5 ESA UNCLASSIFIED – For Official Use Remote Interface Unit 2/2 Tunnelling RIU: PM manages each device separately PM is aware of the access protocol and data formats of each device RIU is just a multiplexer/demultiplexer RIU DEV1 DEV2 DEVA DEVB DEVC Mux/Demux Smart RIU: RIU autonomously access the devices RIU is aware of access protocol and data formats of each device PM is only aware of the access protocol and data formats of the RIU RIU DEV1 DEV2 DEVA DEVB DEVC Cmd & Acq Logic RIU complexity

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 6 ESA UNCLASSIFIED – For Official Use Tunnelling RIU and SOIS

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 7 ESA UNCLASSIFIED – For Official Use Tunnelling RIU in SOIS 1/2 Device access protocol is managed at DAS level in the PM The “simple” RIU Mux/Demux protocol is managed at DAS level in the PM System bus communication between PM and RIU is managed at subnetwork level

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 8 ESA UNCLASSIFIED – For Official Use Tunnelling RIU in SOIS 2/2 Possible mux/demux mechanisms: Commands/data encapsulation via Packet Service Time separated commands via Packet or Memory Access Service RIU Channel X SelectorDev X HeaderDev X Command/Data Packet exchanged at the subnetwork service interface Packet exchanged betwen RIU and Dev X Cmd/Data consumed/produced by Dev X RIU Channel X SelectionDev X Command/DataRIU Channel Y SelectionDev Y Command/Data Command to RIU Cmd/Data to/from Dev X Cmd/Data to/from Dev Y

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 9 ESA UNCLASSIFIED – For Official Use Smart RIU and SOIS

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 10 ESA UNCLASSIFIED – For Official Use Smart RIU in SOIS 1/2 Device access protocol is managed at RIU level Device data are accessed via RIU DAS using specific Value Ids RIU access protocol is managed at DAS level in the PM System bus communication between PM and RIU is managed at subnetwork level

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 11 ESA UNCLASSIFIED – For Official Use Smart RIU in SOIS 2/2 Possible RIU/device access mechanisms: Devices Cmd/Data mixed inside RIU Cmd/Data (Packet Service) Devices Cmd/Data allocated in RIU memory space (Memory Access Service) RIU HeaderDev X Cmd/Data 1Dev Y Cmd/Data 1Dev X Cmd/Data 2 Packet passed to the subnetwork service Dev X Cmd/Data 1 at 0x10 Value Id X1  MAS rd/wr.req to RIU at addr 0x10 Dev X Cmd/Data for Value Id X1 Dev X Cmd/Data for Value Id X2 Dev Y Cmd/Data for Value Id Y1 Dev X Cmd/Data 2 at 0x20 Dev Y Cmd/Data 1 at 0x28 Dev X Cmd/Data 3 at 0x30 Dev Z Cmd/Data 1 at 0x34 Dev Z Cmd/Data 2 at 0x3C Value Id X2  MAS rd/wr.req to RIU at addr 0x20 Value Id Y1  MAS rd/wr.req to RIU at addr 0x28 Value Id X3  MAS rd/wr.req to RIU at addr 0x30 Value Id Z1  MAS rd/wr.req to RIU at addr 0x34 Value Id Z2  MAS read.req to RIU at addr 0x3C

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 12 ESA UNCLASSIFIED – For Official Use RIUs and SOIS EDS

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 13 ESA UNCLASSIFIED – For Official Use Tunnelling RIU and SOIS EDS RIU + Devices can be described by separate EDS The DAS of each Device is built from RIU and device specific EDS Adding a new device to the RIU implies introducing the new Device EDS and a new DAS instance and updating the Device Layout in the RIU EDS RIU EDS Service I/F Mux/Demux Prot. Devices Layout Dev2 EDS Service I/F Dev2 Access Prot. Dev1 EDS Service I/F Dev1 Access Prot.

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 14 ESA UNCLASSIFIED – For Official Use Smart RIU and SOIS EDS One EDS describes RIU + Devices as a single equipment The DAS of the RIU is built from RIU EDS only Adding a new device to the RIU implies updating the RIU EDS and regenerating the MIB of the RIU DAS to access the new valid Value Ids RIU EDS Service I/F RIU Access Prot. Devices Layout RIU EDS is built using devices EDS as input (for data formats) Credit for the onion diagram: S. Fowell

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 15 ESA UNCLASSIFIED – For Official Use Summary

SOIS & RIUs | F. Torelli (ESA) & G. Rakow (NASA) | 15/04/2013 | Slide 16 ESA UNCLASSIFIED – For Official Use Summary Tunnelling RIU 1 DAS for every device Each Access Protocol composed by device + RIU access protocol 1 EDS for each device 1 EDS for the RIU RIU as equipment is described by the collection of the device and RIU EDS Smart RIU 1 DAS for the RIU as equipment RIU Access Protocol in charge to extract the device specific data from the RIU data 1 EDS for the RIU as equipment EDS is built with inputs from device EDS