dhs architecures - CWE

advertisement
Input to CCSDS P&P WG
Chris Taylor
CCSDS 2011 Berlin
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
Cryosat
ESA UNCLASSIFIED – For Official Use
RTU as element of P/F Avionics:
SpW, HSSL,SpF
P/L
P/L
MMU
P/L Bus
CDMU
MIL-STD-1553B,
CAN, SpW
MIL-STD-1553B ECSS-E-ST-50-13C
ECSS-E-ST-50-12C,…
CAN
ECSS-E-ST-50-15dr
RS-422
SpW
P/F Bus
PCU/PCDU
Power Bus
RTU
RTU2015
ECSS-E-ST-5014C
ECSS for digital
sensor busses
Sensors &
Actuators
(T, AOCS,
Propulsion, …)
Load
ESA UNCLASSIFIED – For Official Use
Avionics 2015: RTU2015
Command and control Bus (Can, Milbus, SpaceWire)
1. Remote terminal unit
acts as a data
concentrator
2. Standard interface to
OBC/CDMU with a
standardized protocol
3. Standard Serial bus to
devices
4. S/C may employ several
miniaturised versions
Micro
Controller
/FPGA
Memory
RTU
Standard
Interface
Memory
Digital
Sensor bus
HK Module
Motor Drive
Module
Standard
Digital Bus
(SPI, I2C, …)
M
Sensors and Actuators
Aeronautics/Embedded
examples of RTUs
ESA UNCLASSIFIED – For Official Use
RTU : possible configurations
RTU2015 #1
CAN/1553B/RS422
FPGA
With
CCIP/1553/
RS422 I/F
D
C
/
D
C
uController
With CAN/
1553/RS422
I/F
Controller
H
K
S
L
A
V
E
M
O
D
S
A
D
M
C
T
R
L
M
O
D
Backplane
OBC/CDMU/SMU
SpW
RTU2015 #2
H
K
SpW
RTC
D
C
/
D
C
ESA UNCLASSIFIED – For Official Use
S
L
A
V
E
SpW
Router
Controller
M
O
D
Backplane
Dig
S
E
R
I
A
L
W
I
R
E
L
E
S
S
Bus
Data
Collec.
M
O
D
.
M
O
D
1 Wire
DVS
EDS
Virtual
EDS
Functional
DAS
Serial
I2C
EDS
Mem contr
EDS
Device
Access protocol
Device
Access protocol
Data link
any
Data link
any
CDMU
ESA UNCLASSIFIED – For Official Use
EDS
DAS
RTU
1 Wire
DVS
EDS
Virtual
EDS
Functional
DAS
Serial
I2C
EDS
EDS
Device
Access protocol
Data link
any
Data link
any
ESA UNCLASSIFIED – For Official Use
EDS
DAS
Device
Access protocol
CDMU
EDS
Functional
contr
Mem
RTU
IEEE 1451 – “RTU Architecture”
ESA UNCLASSIFIED – For Official Use
1451 – use of TEDs
ESA UNCLASSIFIED – For Official Use
Traditional architecture
SMU
P/L C&C bus
PDHT
P/L
BC
Payload
Instruments
PCDU
1553
BC
SADM
Payload
Instruments
PM
Alarms
RM
TC Management
TM Management
OBT Management
FDIR Management
MdM Management
AOCS Management
Power Management
Thermal
Management
Payload
management
P/F
ON/OFF
HLC
CPDU
TC
Decoder
TM
S band
RX
S band
TX
TTC RF Sub-system
Security
Module
Encoder
MM
POWER S/S
PPS
OBT
Heaters
Discrete I/Os
Thermistors
Payload
Instruments
P/F
Monitoring
Thermal P/F
SpaceWire
Mil-1553 bus
P/L
Essential
Monitoring
Payload
GPS
Platform
ESA UNCLASSIFIED – For Official Use
STR
CRS
RW
CSS
AOCS Sub-system
MAG
MTB
Thrusters
LV
Tank
Pt
Propulsion Sub-system
IEEE 1451 standards
ESA UNCLASSIFIED – For Official Use
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
Reference architecture
System Services
Application BB
OBCP
interpreter
PUS library/
TMTC
Plan/ Autonomy
Framework
AOCS
MTL services
Thermal
OBT Mgmt
Mission TL/
Mode mgmt
Equipment
Mgmt
Context
Mgmt
Power
Central FDIR
Libraries:
Math, Security,
Payload,…
SSMM Mgmt
P/L Manager
Sensors
(Star Trackers, Sun sensors, Gyros, Earth
sensors, magnetometers)
Software bus
Actuators
(Reaction wheels, magneto torquers,
thrusters, etc)
Execution framework
Middleware services
Application
Layer
SOIS Subnetwork
Layer
TM/TC
SSMM
ECSS Datalink
Protocols
SOIS
Communication
Services
RTOS
Standardized
devices
Legacy
devices
Standardized
devices
“minitor”
Essential
TM
Payloads &
Instruments
High Speed
Telemetry
Encryption
Storage
Compression
BSP
TC decoder
Essential
TM
Payload Data
Processing
DSP
OBC Hardware
TM
Encoder
Compress
Encrypt
Security
Unit
Filing
System
SOIS
Layers
SOIS
Layers
CPU/
Multicore
HW
watchdog
Safe Guard
Memory
CAN
RS422
RAM
OB Timer
Time synch
MIL-1553
SpW
EEPROM
Boot
PROM
Reconfig
Module
Onboard Communications H/W
(e.g. MIL-STD-1553B, SpaceWire, CAN RS422)
ESA UNCLASSIFIED – For Official Use
RTU
Micro
controller
SOIS
Layers
Payload Control
Computer
Digital
Sensorbus
ADCs / DACs
SOIS
Layers
SOIS
Layers
Payload
TM Link
Traditional architecture
SMU
P/L C&C bus
PDHT
P/L
BC
Payload
Instruments
PCDU
1553
BC
SADM
Payload
Instruments
PM
Alarms
RM
TC Management
TM Management
OBT Management
FDIR Management
MdM Management
AOCS Management
Power Management
Thermal
Management
Payload
management
P/F
ON/OFF
HLC
CPDU
TC
Decoder
TM
S band
RX
S band
TX
TTC RF Sub-system
Security
Module
Encoder
MM
POWER S/S
PPS
OBT
Heaters
Discrete I/Os
Thermistors
Payload
Instruments
P/F
Monitoring
Thermal P/F
SpaceWire
Mil-1553 bus
P/L
Essential
Monitoring
Payload
GPS
Platform
ESA UNCLASSIFIED – For Official Use
STR
CRS
RW
CSS
AOCS Sub-system
MAG
MTB
Thrusters
LV
Tank
Pt
Propulsion Sub-system
Avionics 2015: Platform S/s and I/Fs
P/L Bus
Sensors &
Actuators
(T, AOCS,
Propulsion, …)
P/F Bus
TX
OBC/CDMU/
SMU
analog
RTU
RTU
PCDU
Propulsion
ESA UNCLASSIFIED – For Official Use
MIL-STD-1553B
(CAN)
AOCS
Sensors & actuators
digital
Download