SpaceWire Test and Demonstration using the Integrated Payload Processing Module

1
SpaceWire Test and Demonstration using the
Integrated Payload Processing Module

• J.Ilstad, D.Jameux
• European Space Research Technology Centre
• (ESTEC)
• SpaceWire Conference 2008
• Nara, Japan

2
Outline

• Motivation
• TDP Overview
• TDP Architecture
• Integrated Payload Processing Module
• RTEMS
• Packet Utilization Standard
• SpaceWire Demonstration Scenarios
• Future Outlook
• Conclusion

3
Motivation

• Establish and demonstrate best practices
  towards.
• Network Topologies with respect to reference
  architectures.
• Redundancy Schemes and FDIR
• SpW Networking Protocols together with use of
  SpW-enabled equipment
• General purpose processing nodes
• Dedicated processing modules
• Nodes with no processing capability

4
TDP overview

• Basic setup TTC, SMU, PDHU, 1 instrument, no
  redundancy
• A mix between RMAP and subset of PUS is used in
  TDP 1.0

5
TDP 1.0 Architecture
RTEMS

• SpaceWire Demonstration Activity with Aurelia
  Microelettronica (IT) T0 Q3 2008, end Q2 2009.
• 3 IPPM boards is used as basis for an onboard DHS

RMAP
PUS packets
6
Integrated Payload Processing Module
PCI connector
262 Mbyte memory
UARTs (GPIO)
AT697E CPU
DSU Connector
SpW Router 10X
GPIO pins
ICCU (control FPGA)
2 CAN links
MIL1553 Bus
7
IPPM Control and Communication Unit

• Remote Control
• SW Application upload
• Bridge traffic between other bus interfaces
• Direct memory access

RMAP CoDec

• Other Protocols will be processed by SW

8
RTEMS

• Primary Motivation
• Open Source
• Real Time multitasking kernel with modular
  architecture
• Availability of development and support tools
• E.g. Eclipse with plug-ins, RTEMS configuration
  tools
• Great potential for critical onboard SW
• Secondary Motivation
• Availability of support
• Gaisler Resarch, EDI soft (RTEMS Centre Europe)
• Mission heritage (e.g. Hercel Planck)
• In-house developments (e.g. RASTA)

9
RTEMS

• Objectives
• To utilize RTEMS with SpaceWire equipment and
  protocol related development activities
• Identify requirements and constraints at both SW
  and HW level
• Identify recommendations or best practices for
  implementation.

10
Packet Utilization Standard (ECSS-E-70-41a)

• Background
• The PUS complements the CCSDS packet TMTC
  standards by defining the application-level
  interface between ground and space
• It provides the operational concepts and a set of
  on-board Services meeting them.
• It defines TMTC packets and structures to
  exploit the onboard services.
• Motivation
• Study interaction between PUS and SpW protocols.

11
SpaceWire demonstration scenarios

• Test and validate SpW network topologies and
  SpW-enabled devices
• Investigate SpW-based time distribution as
  opposed to legacy time distribution (PPS)
• Prototyping and validating SpW-based protocols
  coupled with use of PUS
• Evaluate FDIR concepts in this context
• Introduce SOIS in future development steps of TDP

12
Future Outlook
Payload
RTU
Inst. 3
SpW-RT SpW PnP
Inst. 2
Inst. 1
PDHU
X-Band TM
P/L MIL 1553
MM
Discrete IO
P/L MIL 1553
P/F MIL 1553
AOCS Subsystem Mock-up
SpaceWire
Discrete I/O
Satellite Management Unit
S-Band TM/TC
CAN
ASSP w/ SpW IF
P/F MIL 1553
SpW-RT SpW PnP
IPPM Unit
Power Subsystem Mock-up
Platform
13
Conclusion

• SpaceWire Test Demonstration Platform
• view towards current and future SpaceWire related
  development activities.
• The features of the IPPM make it an ideal
  candidate for
• experimentation and validation of
  SpaceWire-enabled equipment
• SpaceWire network topology and protocols
• Hosting RTEMS based applications conforming to
  ECSS-E-70-41a (PUS) and SW based protocol
  handlers.
• Future development steps of the TDP will
  introduce
• SpaceWire equipment based on the next generation
  of ASSPs such as the SpW-RTC.
• CCSDS SOIS

14

• Thank You