Next Generation Space Interconnect Standard

(NGSIS) SpaceVPX and SpaceVPXLite Tutorial

VITA 78 AND VITA 78.1 WORKING GROUPS
Bottom Line Up Front
What is wrong with just using Legacy Space Systems?

• Legacy space systems are often point solutions

• Re-use is not a priority
• Don’t have the full range of redundancy options (dual-string, M-of-N, etc.) built-in given the
particular application and its needs.
• Internal interfaces are often proprietary and application specific
• Modules are not designed to inter-operate at either hardware or software level
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
What is NGSIS? (Original)

SpaceVPX
SpaceVPXLite

RapidIO
Space
Device
Class

The Next Generation Space

Interconnect Standard
Constituent Parts
High
High
Reliability
Reliability
Systems
Systems

SpaceVPX
SpaceVPX SpaceVNX
SpaceVNX

SpaceVPXLIte
SpaceVPXLIte

RIO
RIO Space
Space
Device SpaceFibre
SpaceFibre
Device Class
Class

SpaceWire
SpaceWire
Targets or Marketplace
Targets are typically SpaceVPX
Large, Medium, and
Small High Performance
Computing Systems that
are Sensor Driven
New Market Focus on
Cube Sats and Non- Large Systems
Space High Reliability Medium
Small
Cube
High Reliability Systems
Systems
Sat – Non-Space
Systems SpaceVPXLite
Systems SpaceVNX

SpaceVNX

SpaceVPX/SpaceVPXLite
Who is Involved in SpaceVPX?
Who is Involved in the RIO Space
Device Class?
What are SpaceVPX’s Goals?
Created to bridge the VPX standards to the space market.
• SpaceVPX addresses both interoperability (as OpenVPX does) and space application
needs (not in OpenVPX).
• SpaceVPX defines Payload, Switch, Controller, and Backplane module profiles to meet
needs of space applications
• SpaceVPX adds features to the Utility Plane for fault tolerance
• Point-to-point not bussed to tolerate faults: failure on module does not affect entire system.

• Space Utility Module added to provide dual-redundant source for Utility Plane implementations.

• SpaceVPX defines use of SpaceWire for Control Plane over Ethernet (OpenVPX
preferred solution).
Goals for SpaceVPX and
SpaceVPXLite?
Develop
• Enhanced set of backplane specifications that are based upon existing commercial
standards with added features required for space applications.
Increase
• Interoperability and compatibility between manufacturers and integrators, while
simultaneously increasing affordability through the use of standard sets of hardware.
Scale
• Performance and Capability based upon user’s needs and requirements
What is in SpaceVPX and
SpaceVPXLite?
VITA 65
SpaceFibre/SpaceWire
VITA 46.0
VITA 46.3
SRIO on VPX VITA 46.9
PMC/XMC
VITA 46.11
Sys. Management VITA 48.2
Conduction
Direct Access Protocol

SpaceVPX & SpaceVPXLite

Modular Building Blocks

Processing card

Processing card
Payload input

Payload input

Payload input

Memory card

Output card
Switch card
Processing card

Processing card

Power card
Payload input

Payload input
Payload input

Memory card

Output card
Switch card

Power card
Processing card

Processing card
Payload input

Payload input

Payload input

Memory card

Output card
Switch card

Power card
SATCOM System

Slot Payload slots Payload slots

numbers
are logical,
physical UM VPX VPX VPX VPX
VPX VPX VPX VPX
slot
numbers 1 2 3 4 5 6 7 8 9
Expan Expan Expan Expan Expan Expan
may be Plane Plane Plane Plane Plane Plane
different

Data Plane
(DFP)

Data Data Data Data Data Data Data Data

Plane Plane Plane Plane Plane Plane Plane Plane

TP

Control Plane Contrl Contrl Contrl Contrl Contrl Contrl Contrl Contrl
(TP) Plane Plane Plane Switch Switch Plane Plane Plane

TP

Switched
Management
Plane (IPMB) IPMC IPMC IPMC ChMC ChMC IPMC IPMC IPMC

Switched
Utility Plane SW
Includes power
Controller
Selection
A and B (HLD)
Power A and B
Simplified SpaceVPX Development
Flow
Determine application requirements
• Size, weight and power
• Processing, fabric and I/O requirements

Select overall system parameters

• 3U or 6U?
• Switching topology?
• Number and type of slots?

Assemble development vehicle

• COTS development chassis
• COTS boards
• COTS or custom RTMs

Design deployment system

• Typically custom backplane
• Typically route I/O signals to custom
I/O slot or bulkhead connector
 SpaceVPX and SpaceVPXLite adapts
OpenVPX MOSA for Space
SpaceVPX allows flexibility in radial utility distribution and control
The Space Utility Module (SpaceUM) distributes and switches the OpenVPX reset, clocks and power to remove the vulnerability to single point failures.

VPX OpenVPX SpaceVPX SpaceVPXLite

VPX has progressed from Avionics to Space Modular Open Systems
 Updates as Part of the VITA 78 Revision
Large number of editorial fixes missed in original and not qualified as errata

Reorganized protocol sections to include utility plane protocols and register structure

Added SpaceFibre as an alternate control and data plane on all modules

Enhanced Direct Access Protocol (DAP) for lightweight operation

Allows Control Plane to access DAP registers in addition to Utility Plane

Added redundant Geographical Address for fault tolerance

Restricted slot locations for certain module types

Reorganized SpaceUM sections making it follow document’s profile structure

 Updates as Part of the VITA 78 Revision
Added smaller overhead 3U SpaceUM Modules that serve 5 logic slots

Added a small number of new slot / module profiles

Added new power supply, power switch and utility signal switch slots / modules

Lowered power on 3U modules to match SpaceVPXLite’s 187.5 mW/mm

Added additional module pitches for daughter cards and 3D constructs

Added missing 3U mechanical drawings

Adjusted mechanical keep-out areas

3U wedge-locks set to 250 and VITA 48.2 interoperable module handling described

Added Coax and Fiber connector options on slot and module profiles

Most changes in current draft - completion / ratification targeted for 2H18

SpaceVPX Document Structure
Description
SpaceVPX Document Structure
Description
SpaceVPX Document Structure
Description
SpaceVPX Document Structure
Description
SpaceVPX Document Structure
Description
Outline
• What is SpaceVPX?
• SpaceVPX Base Use Case and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
Basic SpaceVPX Payload Use Case
 Backplane Physical Topologies
SpaceVPX backplane profiles include Data Plane configurations using both Star and Mesh topologies. Other Data Plane
topologies are possible.
•A Star topology connects Payload Slots through centralized Switch Slots. The SpaceVPX Control Plane always uses the Star topology
while the SpaceVPX Data Plane can be either a Star topology or a Mesh topology.
•Note that when the Control and Data planes are both Star topology, the Control and Data plane switches can be combined on a
single module. In Star topologies with dual redundant fault tolerance, each switch topology has two switch slots and all
Payload slots are connected to each switch slot.
•A Mesh topology connects each of the Payload Slots directly to other Payload slots, without the use of a centralized Switch Slot.
•The SpaceVPX Data Plane is implemented as a full mesh where each Payload Slot data plane interface is connected to each of the
other Payload Slots.
•In a full-mesh, failure of one module does not adversely affect the ability of any working module to communicate with any other
working module in the mesh.
•Also, modules in the mesh can be in a standby redundant off-state without adversely affecting communication between modules
turned on.
•Any mesh configuration requiring one or more modules to be alive and working for other modules in the mesh to communicate
with other are not conducive to space applications.
Physical Topologies

Dual-Star Topology

Dual-Star Topology with

PCI Expansion
Full Mesh Topology
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
 Slot Profiles
Color
•Power related signals are reds Signals
(Microsoft Definition)
Example

and oranges Power Feeds Red PF

VS1, VS2, VS3 rose VS1

•Signals are greens, yellows and VBAT, auxilary power, sense lines light orange VBAT

UD (abbreviated UD) tan UD

blues Control plane light green CPtp02

Data plane pale blue DP01

•Unused pins are grey Expansion plane light turquoise EP02

PCI signals aqua PCI

•Miscellaneous utility signals are control/data/Expansion plane, contrast light yellow DP02

purple Grounds none GND

Reserved Pins (abbreviated RSVD) grey 25% RSVD

No pad grey 50% No Pad*

Global Address, System Controller light blue GA

Reference Clock, Auxiliary Clock yellow REF_CLK

System Management, JTAG sea green SM

SYSRESET, NVMRO, Maskable Reset lavender SYSRESET*

Power select dark red Power SEL

 What is in SpaceVPX (Profiles)
Slot Profile A physical mapping of ports onto a slot’s backplane connectors

Extends a slot profile by mapping protocols to a module’s ports

Module Profile
Profile Expansio User
Backplane Profile
Data Plane Control
Name n Plane

t
Slo

Slo
Plane 2 Defined

ts M
4 FP P2/J2

Slo cU
ol

ol
TP

ntr

ntr
ae
Co

Co
Sp
DP01 to CPtp01 P3/J3, Slot Payload slots Payload slots
numbers
DP04 to P5/J5 are logical,
physical
VPX VPX VPX VPX UM VPX VPX VPX VPX
CPtp02 slot
numbers 1 2 3 4 5 6 7 8 9
Expan Expan Expan Expan Expan Expan
may be Plane Plane Plane Plane Plane Plane

MOD6-PAY- sRIO 2.2 at sRIO 2.1 SpaceW User different

4F1Q2T- 3.125 at 3.125 ire per Defined

Data Plane
12.2.1-1-cc Gbaud per Gbaud Section DIFF (DFP)

Section 5.2 per 5.2.1 pins

Section Data Data Data Data Data Data Data Data

5.2 Plane Plane Plane Plane Plane Plane Plane Plane

TP

Control Plane Contrl Contrl Contrl Contrl Contrl Contrl Contrl Contrl
(TP) Plane Plane Plane Switch Switch Plane Plane Plane

TP

Switched
Management

A physical specification of a backplane Plane (IPMB) IPMC IPMC IPMC ChMC ChMC IPMC IPMC IPMC

Switched
Utility Plane SW

Also: Power Keying and Chassis profiles Includes power

Controller
Selection
A and B (HLD)
Power A and B
 What is in SpaceVPXLite (Profiles)
Slot Profile A physical mapping of ports onto a slot’s backplane connectors

Extends a slot profile by mapping protocols to a module’s ports

Module Profile Backplane Profile

Controller
Control/Switch/
Control Plane Radial Management Plane Payload Management Payload

Profile Name TP01 – TP08 RAD(3:0)_1 – RAD(3:0)_8 Slots Power Switch Slots
Power Supply
MOD3SL-CON-8T- IPMB-A & IPMB-B
16.10.1‑1 1000BASE-T per Section 5 VPX VPX VPX VPX VPX VPX VPX VPX VPX VPX VPX VPX VPX
1 2 3 4 5 6 7 8 9 10 11 12 13
MOD3SL-SWH-8F- Direct Access Protocol
Management
1000BASE-T per Section 5 Plane (IPMB)
16.10.1‑2 ChMC IPMC IPMC IPMC ChMC

MOD3SL-SWH-8F- CANBUS
Data Plane Data Data Data Data Data Data

1000BASE-T per Section 5 (FP)

Plane Plane Plane Plane Plane Plane

16.10.1‑3
MOD3SL-SWH-8F- IPMB-A & IPMB-B Control Plane Contrl Contrl

16.10.1‑4 SpaceWire per Section 5 (TP)

Contrl
Plane
Contrl
Plane
Contrl
Plane Switch Switch
Contrl
Plane
Contrl
Plane
Contrl
Plane

MOD3SL-SWH-8F- Direct Access Protocol

SpaceWire per Section 5 Radial
16.10.1‑5 Management
IPMC IPMC IPMC
ChMC
IPMC IPMC
ChMC
IPMC IPMC IPMC
Plane (IPMB) (Rad) (Rad)

MOD3SL-SWH-8F- CANBUS
SpaceWire per Section 5 Utility Plane
16.10.1‑6 Reference
Section 3

A physical specification of a backplane

Also: Power Keying and Chassis profiles
Module Profiles
Profile Data Plane 4 FP Expansion Control Plane 2 User
Name Plane P2/J2 TP Defined
DP01 to DP04 CPtp01 to P3/J3, P5/J5
CPtp02
MOD6-PAY- sRIO 2.1 at 3.125
4F1Q2T- 1 sRIO 2.2 at 3.125 Gbaud per SpaceWire per User Defined DIFF
Gbaud Section
2.2.1-1-cc per Section 5.2 5.2 Section 5.2.1 pins

• Module Profiles specify a particular Slot Profile

and the protocols that go on groups of pins
– The section number and sequence number at the
end of the name make sure it is unique
– Module Profile sections, in ANSI/VITA 65, use the
sequence number, to specify a particular
combination of protocols out of the multiple options
Example Set of 6U Module Profiles
Profile Name Expansion Plane P2/J2 Control Plane 2 User
Data Plane 4 FP TP Defined
DP01 to DP04 CPtp01 to P3/J3, P5/J5
CPtp02
MOD6-PAY-4F1Q2T- sRIO 2.2 at 3.125 Gbaud per sRIO 2.1 at 3.125 Gbaud SpaceWire per User Defined
12.2.1-1-cc Section 5.2 per Section 5.2 Section 5.2.1 DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 at 5.0 Gbaud per sRIO 2.1 at 5.0 Gbaud per SpaceWire per User Defined
12.2.1-2-cc Section 5.2 Section 5.2 Section 5.2.1 DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 at 6.25 Gbaud per sRIO 2.1 at 6.25 Gbaud SpaceWire per User Defined
12.2.1-3-cc Section 5.2 per Section 5.2 Section 5.2.1 DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 at 3.125/5/6.25 User Defined – DIFF Pins SpaceWire per User Defined
12.2.1-4 to 6-cc Gbaud per Section 5.2 Section 5.2.1 DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 at 3.125/5/6.25 User Defined – SE Pins SpaceWire per User Defined
12.2.1-7 to 9-cc Gbaud per Section 5.2 Section 5.2.1 DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 per Section 5.2 SpaceWire per User Defined
12.2.1-1n-cc defined by “n” above defined by “n” above Section 5.2.1 J3=SE pins
J5=DIFF pins
MOD6-PAY-4F1Q2T- sRIO 2.2 per Section 5.2 SpaceWire per User Defined
12.2.1-2n-cc defined by “n” above defined by “n” above Section 5.2.1 J3=DIFF pins
J5=SE pins
MOD6-PAY-4F1Q2T- sRIO 2.2 per Section 5.2 SpaceWire per User Defined SE
12.2.1-3n-cc defined by “n” above defined by “n” above Section 5.2.1 pins
 Slot Profiles – Example
• Slot Profiles Define Pin Assignments for Both Plug-In Modules
and Backplanes, independent of protocol
– With 6U P0 thru P6 are Plug-In Module connectors
– J0 thru J6 are backplane connectors

• With most SpaceVPX Profiles P1/J1 thru P6/J6 are mostly

differential pairs
– 32 differential pairs / connector – 16 lanes
SpaceVPX 6U Slot Profile:
– 8 single-ended pins / connector
SLT6-PAY-4F1Q2T-10.2.1
– 6 connectors give a total of 192 pairs and 48 single-ended

Single-
Differential
Ended
pins
pins
Mapping Interfaces to SpaceVPX Slot
Profiles
Utility plane provides power, Key
SE
configuration, timing and Utility Plane
P0/J0

management input signals using S Expansion Plane for additional

E Diff Data Plane
I2C, CMOS and LVDS levels P1/J1 4 FP Data FPs, Heritage I/Fs or
Utility Plane Expansion
Utility Plane User Defined Signals
Serial RapidIO (sRIO) is used for the data User Defined
S Diff
E P2/J2 User Defined
plane
x1 interface = 1 Ultra thin pipe (UTP) Key

x2 interface = 1 Thin Pipe (TP) S Diff SpaceWire is used for the control
Diff
x4 interface = 1 Fat Pipe (FP) E P3/J3
P1/J1 plane
Control Plane
16 TP 1 interface = 1 Thin Pipe (TP)
S Diff
E P4/J4
User Defined

Expansion Plane for additional

Data FPs, Heritage I/Fs or S Diff
E P5/J5 User Defined
User Defined Signals
Signals to and from the
S Diff SpaceUM
16 Pairs
To SpaceUM E P6/J6
8 Pairs
Key
 Mapping Interfaces to SpaceVPXLite Slot Profiles
Utility plane provides power,
Serial RapidIO (sRIO) configuration, timing and management
x1 interface = 1 Ultra thin pipe (UTP) input signals using I2C, CMOS and
x2 interface = 1 Thin Pipe (TP) LVDS levels
x4 interface = 1 Fat Pipe (FP) Key SpaceWire is used
Key
SE SE for the control plane
P0/J0 P0/J0
1 interface = 1 Thin Pipe (TP)
Utility Plane Data Plane - 2 Fat Pipes Utility Plane Diff
Diff S
S P1/ Control Plane — 8 Thin Pipes
P1/ User Defined E
E J1
J1
Control Plane – 2 Thin Pipes (Can
be used as four Ultra Thin Pipes)
Diff Diff Could also use SpaceFibre is used
S S Utility Control
User Defined P2/ User Defined P2/
E E
J2
32 DIFF, 8 SE signals in the control plane as a data signal
J2
1 interface = 1 Thin Pipe (TP)
Key Key
SpaceWire is used
for the control plane
1 interface = 1 Thin Pipe (TP)

Signals to and from the Utility

Module
SpaceVPX 6U Slot Families
Payload Family: Switch Family:
Payload, Controller, Peripheral, Control Switch Data Switch, Switch & Controller, Control Switch

Pinouts are consistent throughout slot profile families enabling single

design providing multiple slot types
 6U Slot Profiles
Payload Payload Peripheral Peripheral Switch and Controller Data and Control Switch

Data Switch Controller Controller

3U Slot Profiles
Payload Payload Peripheral Switch or Mesh Slot

Switch and Controller Controller Controller

 SpaceVPXLite Slot Profiles (Subset)
Key Key Key
Key
SE SE SE
SE
P0/J0 P0/J0 P0/J0
P0/J0
Utility Plane Diff Data Plane - 2 Fat Pipes Data Plane - 1 Fat Pipe Utility Plane Diff Primary Utility Plane
S Utility Plane S User Defined Diff
P1/ P1/ S
E User Defined S Diff P1/
J1 Expansion Plane – 2 Fat Pipes E E
E P1/J1 J1 J1
Control Plane – 2 Thin Pipes (Can Control Plane – 2 Thin Pipes (Can
Control Plane – 2 Thin Pipes
be used as four Ultra Thin Pipes) be used as four Ultra Thin Pipes) Data Plane — 8 Fat Pipes
(Can be used as four Ultra Thin
Diff Pipes) Diff Diff
User Defined
S
P2/ User Defined 66.4, S 66.4, S
E S Diff User Defined P2/
67.1, or User Defined User Defined P2/
J2 User Defined 67.1, or User Defined E 67.3A E
E 67.3A
P2/J2 J2 J2
Key Key
Key Key

Key Key Key

SE Key
SE SE
P0/J0 P0/J0 SE
P0/J0 P0/J0
Primary Utility Plane Diff Reserved unless ... Utility Plane
S Diff
P1/ Utility Plane S Utility Plane Data Plane - 2 Fat Pipes
E Diff E
P1/ Control Plane — 8 Thin Pipes S Diff
J1 Data Plane — 6 Fat Pipes S 2 Ultra Thin Pipes J1
P1/ E P1/J1 Expansion Plane – 8 pairs
E (Storage Interface)
J1 User Defined
Diff
66.4,
Control Plane – 2 Ultra-Thin Pipes
S P2/ Diff
User Defined
E J2 Data Plane — 4 Ultra Thin Pipes
Reserved unless S
P2/
Utility Control P2A/J2A 67.1, or
combined with E 32 DIFF, 8 SE signals 67.3A VITA 65 Aperture Pattern E
Control Plane — 2 Thin Pipes Diff J2
Reserved S 66.4, for optical/coax
Key P2/ another Profile
P2B/J2B 67.1, or
unless ... E Key
J2 67.3A
Key
Key

Note: This is not the complete set of profiles.

 6U Connector Guidelines
All: J0 & J1 Row G: Utility Plane
Data Switch:
– J1AB: Up to 4 TP Control
– J2, J3, J4, J5, J6, J1CD: Up to 22 FP Data
Integrated Switches: Data, Management and Control:
– J1, J2: up to 16 TP Control
– J4, J3, J5, J2: up to 16 FP Data
– J6: up to 4 SpaceUM Utility Plane Feeds
Payloads:
– J1, J3, J6: Up to 12 Data FP
– J2: Expansion - Daisy Chained Up to 32 Pairs of Heritage or Data
– J4D: Control 2 TP
– J5: Expansion – Heritage (PCI 32 bit)
– J6, J5: Optical or RF
Controllers (Payload Compatible)
– J1: Up to 4 Data FP
– J2: Expansion - Daisy Chained Up to 32 Pairs of Heritage or Data
– J4, J3: Up to 16 TP Control
– J5: Expansion – Heritage (PCI 32 bit) Non-assigned pins may be user defined
– J6: up to 4 SpaceUM Utility Plane Feeds
Payload Slot Profile (Switched)
Data-In Module

Utilize User Defined Pins and Top of Card

Possibility I

Connectors for Additional Capability

Data-Out Module

Data-In Module

Possibility II Processing Module

Data-Out Module

Data-In Module

Possibility III Processing Module

Storage Module

Any Combination of Payload Functions is Possible

Payload Slot Profile (Mesh)
Data-In Module

Utilize User Defined Pins and Top of Card

Possibility I

Connectors for Additional Capability

Data-Out Module

Data-In Module

Possibility II Processing Module

Data-Out Module

Data-In Module

Possibility III Processing Module

Storage Module

Any Combination of Payload Functions is Possible

 SpaceVPX System Controller
• Optional data plane connections
Key element of SpaceVPX fault tolerance
• Power channeled to System Controller SpaceWire to other boxes
Power A and B
which then directs powering of other
modules
• Uses System Management Interface (SMI) System SpaceUM SMI & Clocks

Router
SpaceWire A SMI & Clocks To 1-8 Modules
for chassis management then SpaceWire to all Modules Controller A
for Control Plane operations A Power
• SpaceWire router defined with System
Controller may be separated with cross- Power & Sys Controller Selects
SpaceWire (fault tolerant)
strapping

System SpaceUM SMI & Clocks

Router
SpaceWire B SMI & Clocks To 1-8 Modules
to all Modules Controller B
B Power
Power A and B
SpaceWire to other boxes
SpaceWire may be used as C&DH or medium
Optional data plane connections speed data path within SpaceVPX box
Controller Slot (without Data Plane
Connection)

Utilize User Defined Pins and Top of Card

Connectors for Additional Capability
Processing Module

Possibility I Controller Module

Control Switch Module
or

Storage Module
Controller Module
Possibility II
Control Switch Module

Processing Module

Any Combination of Payloads with Controller

or Control Switch is Possible
Data Switch and Controller Slot Profile
Controller Module

Utilize User Defined Pins and Top of Card

Connectors for Additional Capability
Possibility I
Data Switch Module
or

Control Switch Module

Possibility II
Data Switch Module
or

Controller Module

Possibility III Control Switch Module

Data Switch Module

Any Combination of Data Switch with Controller

or Control Switch is Possible
Controller Slot (with Data Plane
Connection)

Utilize User Defined Pins and Top of Card

Connectors for Additional Capability
Data-In Module

Possibility I Control Switch Module

Controller Module
or
Data-In Module
Processing Module
Possibility II
Control Switch Module
Controller Module

Any Combination of Payloads with Controller

or Control Switch is Possible
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
 I/O Planes in SpaceVPX

n tr h &
er

n tr h &
ts M

er
oll
Slo eU

oll
Co w i tc
Slot

Co wi t c
Payload Payload

ac
numbers
slots slots

S
are logical,

Sp

S
physical
slot
numbers
may be VPX VPX VPX VPX VPX VPX VPX UM VPX VPX VPX VPX VPX VPX VPX
different 1 2 3 4 5 6 7 8-9 10 11 12 13 14 15 16

Expansion Plane Expansion

Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
Expan
Plane
(DFP)

Data Plane Data Plane

(FP)
Data
Plane
Data
Plane
Data
Plane
Data
Plane
Data
Plane
Data
Plane
Data
Switch
Data
Switch
Data
Plane
Data
Plane
Data
Plane
Data
Plane
Data
Plane
Data
Plane

TP

Control Plane
Control Plane (TP)
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Switch
Contrl
Switch
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane
Contrl
Plane

TP

Switched
Utility Plane Utility Plane
(includes system IPMC IPMC IPMC IPMC IPMC IPMC ChMC ChMC IPMC IPMC IPMC IPMC IPMC IPMC

management,
reference clocks,
reset and power) SW

Power Plane Controller

Selection
A and B
Power A and B
Data Plane Switch Topology
Data Plane Mesh Topology
Control Plane Switch Topology
Example of 6U SpaceVPX Backplane
Profile
  Mechanical Slot Profiles and Section Channel Gbaud Rate
 
          Control Data Exp.
Pitch RTM   Switch & Plane Plane Plane
Profile name (in) Conn Payload Controller

        SLT6-      
BKP6-CEN9-   SLT6-PAY- SWC-  0.4  3.125  3.125
1.2 [VITA 4F1Q2T-
11.2.5-1 12F16T-
46.10] 10.2.1 10.4.1

        SLT6-      
BKP6-CEN9-   SLT6-PAY- SWC-  0.4  5.0  5.0
1.2 [VITA 4F1Q2T-
11.2.5-2 12F16T-
46.10] 10.2.1 10.4.1
        SLT6-      
BKP6-CEN9-   SLT6-PAY- SWC-  0.4  6.25  6.25
1.2 [VITA 4F1Q2T-
11.2.5-3 12F16T-
46.10] 10.2.1 10.4.1
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
SpaceVPX Concept Development
Three concepts developed
• Concept 1 – Redefine an existing OpenVPX connector block as a second Utility/Management plane block (similar to P0/P1)
• Incompatible with existing OpenVPX modules

• Concept 2 – Extend the existing Open VPX connector by adding a second Utility/Management plane block (P7/P8 similar to
P0/P1)
• Extends module height from 6U to 6U+TBD
• Partially compatible with existing OpenVPX modules

• Concept 3 – Add one or more Space Utility/Management (SpaceUM) modules with independent support for each
OpenVPX module
• The SpaceUM module receives redundant Utility and Management Plane signals through the backplane and selects
one set to be forwarded to the OpenVPX module Utility/Management plane signals
• Allows use of existing OpenVPX modules in appropriate flight applications
SpaceVPX Fault Tolerance
Goal - SpaceVPX is to achieve an acceptable level of fault tolerance, while maintaining reasonable
compatibility with OpenVPX components, including connector pin assignments. For the purposes of
fault tolerance, a module is considered the minimum redundancy element. The Utility Plane,
Management Plane, and Control Plane are all distributed redundantly and in star topologies to provide
fault tolerance.
For Space applications, the major fault tolerance requirements are listed below:
• Dual-redundant power distribution (bussed) where each distribution is supplied from an independent power source.
• Dual-redundant management distribution (point-to-point cross-strapped) where each distribution is supplied from an independent
management controller to a SpaceUM module that selects between the A and B management controllers for distribution to each of
the slots controlled by the SpaceUM module.
• Card-level serial management
• Card-level reset control
• Card-level power control
• Timing/synchronization/clocks, Matched length, low-skew differential
• Fault tolerant Utility Plane selection (bussed)
• Dual-redundant Data planes (point-to-point cross-strapped)
• Dual-Redundant Control planes (point-to-point cross-strapped)
• VITA 78 infrastructure allows for fully managed FRUs and for dumb FRUs (via VITA 46.11)
SpaceVPX Redundancy
• Each of the interconnect planes defined by OpenVPX are supported by
SpaceVPX as fully cross-strapped single-fault tolerant capable
• Control, Data and Expansion plane redundancy is provided using the existing OpenVPX
connectivity
• Ability to utilize M-of-N payload module redundancy to support either higher reliability or
degraded modes of operation
• The SpaceVPX Utility and Management plane redundancy is a major departure from
OpenVPX
• OpenVPX uses single-source, bused power distribution
• OpenVPX uses single-source, bused clock, reset and management distribution
• Each interconnect plane can be implemented with reduced fault tolerance when desired
SpaceVPX Redundancy
SpaceVPX Utility Management
• Architecture
• Provides single-fault-tolerance with limited increase in SWaP
• One SpaceUM module supports eight VPX slots
• Scalable to very large units
• Maximum of 31 VPX slots and 4 SpaceUM slots
• Dual-redundant power distribution
• Allows traditional space methods
• Dual-redundant management distribution
• Traditional capability using improved methods
• Accommodates supplier-preferred methods for implementing interoperable products

• Topology
• Traditional tree-topology is familiar to space suppliers
• Flexible command/status interface options allow tailoring to customer needs
SpaceVPX System (Chassis)
Management
• Leverages the VITA 46.11 industry standard
• Limited subset to minimize complexity

• Defines an alternative light-weight protocol for less complex systems

• Basic functions supported
• Individual module power on-off control
• Individual module reset control
• Individual module status monitoring
• Advanced capabilities
• Module-level telemetry acquisition
• Voltage, temperature, digital state, etc.
• Module-level functional control
• Sub-function power control, register access, memory access, etc.
Mandatory System Management
Controls
System Management Controls Description

System Management Reset Controls and monitors the state of the System Management Reset (SM_RESET*) signals for all
Control modules within the System Management domain.

System Management Health Monitors the state of the System Management Health Status (SM_STAT*) signals for all
Status modules within the System Management domain.

Module Primary Power Controls and monitors the state of the Module Primary Power Enable signals for all modules
Enable Control within the System Management domain.

Controls and monitors the state of the Module System Reset (SYSRESET*) signals for all
Module System Reset Control
modules within System Management domain.

The System Management infrastructure is responsible for the distribution of the System
Management IPMB and discrete signals, as well as primary power and reset, to the SpaceVPX
Modules. Four sets of controls are defined specifically for the management of these signals and
functions.
Optional System Management Discrete
Signals
System Management Description
Discrete Signals

System Management Controls and monitors the state of a set of 32 discrete output signals.
Discrete Output Signals

System Management
Discrete Input Signals
Monitors the state of up to 32 discrete input signals.

A SpaceVPX Module can optionally provide commanded discrete outputs and inputs. Two
optional sets of discrete signals, each containing 32 bits, are defined specifically to control and
monitor the state of discrete signals on a module. The IPMC on a module can support one or
more discrete outputs or inputs. The use of these discrete signals is implementation-specific.
System Controller/Utility Plane
Space Utility-Management (SpaceUM)
Module Architecture
•The SpaceVPX SpaceUM module provides selection functions for the dual-redundant Utility
Plane (power) distribution and for the dual-redundant Utility Plane system control distribution.
•By combining the Power Selection and Management Selection functions in the SpaceUM
module, SpaceVPX provides compatibility with existing OpenVPX capabilities and
implementations.
•Note that although the SpaceUM module is an integral part of the SpaceVPX power distribution
system, it is not a power supply and does not include transformer-coupled power isolation
capability.
•Note: Implementers that choose to provide power isolation in the SpaceUM module are
exceeding the scope of this specification.
 Select
Controller

System
System

Select
(discrete)

SYS_RST
SYS_RST

Management
Management
Topology

(ChMC)
(ChMC)

System
System

VPX Slot
VPX Slot

VPX Slot VPX Slot

Controller A

Controller B
(IPMC) (IPMC)

Select Select Select Select

Circuit Circuit Circuit Circuit
Management Select

Management Fanout B Management Fanout A

(IPMC) (IPMC)

Select Select Select Select Select

Circuit Circuit Circuit Circuit Circuit

VPX Slot VPX Slot VPX Slot VPX Slot VPX Slot
(IPMC) (IPMC) (IPMC) (IPMC) (IPMC)
SpaceVPX Management Distribution
SpaceVPX Management Distribution
Topology
SpaceVPX IPMB Topology
Power/Utility Plane
SpaceVPX Power Distribution Topology

VPX Slot

VPX Slot
Circuit

Circuit
Select

Select
System

VPX Slot
Circuit

Circuit
Select

Select
Controller A
VPX Slot
(ChMC)
Power A Power
Supply

VPX Slot
Select

Circuit
Select
Powe (discrete Utility Select
r )
Power
Selec Supply
t
Power B System

VPX Slot
Circuit

Circuit
Select

Select
Controller B
VPX Slot
(ChMC)

VPX Slot

VPX Slot
Circuit

Circuit
Select

Select
 Power Supply-Switch Module Profiles
•The SpaceVPX Power Supply-Switch module includes transformer-coupled power isolation capability between
the Front Panel main power input and the secondary power outputs.
•The secondary output power switching capability supports dual-redundant SpaceVPX Utility Plane power
distribution and allows the individual VPX slot power management needed for SpaceVPX redundancy
management.
•By incorporating these functions, the Power Supply-Switch module provides compatibility with existing
OpenVPX capabilities and implementations.
•SpaceVPX Power Supply-Switch modules are intended for use in redundant configurations where one module
of the redundant set is active and all others are inactive.
•The fault-tolerant POWER_SEL[5..0] signals are used to inform each Power Supply-Switch module of its current
state (active or inactive).
•System integrators are responsible for distributing the Power Select signals to the Power Supply-Switch
modules in a manner that provides the desired redundancy control and fault tolerance.
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
 Mechanical
• General Form Factor – VITA 46
• Conduction Cooled Modules – VITA 48.2
• Updated figures
• Screw and tab modules with addition of threaded holes
• Separate extraction tool for non-levered modules

• Pitch – 0.8”, 1.0”, 1.2” (default)

• Multiple pitch cards may be used Strongly leverages existing
OpenVPX mechanical
• 160 mm standard length
infrastructure and standards
• 220, 280 and 340 mm allowed

• Accommodates larger wedgelock

• Connections to PWB ground allowed
• Connector – VITA 46, VITA 60 or VITA 63 may be used
SpaceVPX Connector Pad and Wafers
Current Ratings
Power Wafer Current Rating for 30oC Temp. Rise
(at Wafer Pad and Backplane Connector Contact Interfaces)
Power plane thickness in 2 ounce copper 1 ounce copper
plug-in module and
backplane
Number of wafers across 3 adjacent 2 adjacent wafers 1 wafer 3 adjacent wafers 2 adjacent wafers 1 wafer 2 pairs of adjacent power
which power is dissipated wafers current carrying wafers
separated by 2 non power
current carrying wafers

Current allowed per pad (A) 6 8 11.5 5 7 11 4.5

Current allowed per wafer 12 16 23 10 14 22 9
(A)
These current ratings are dependent on several variables, such as:

 Heatsinking, e.g. copper plane thickness and size, connected to power pins. The above ratings are from test data for 1 and 2 ounce copper planes within test plug-in modules and
backplane.

 Thermal management, e.g. cooling method for a plug-in module. The above ratings are from test data where cooling was to still ambient air.

 Contact resistance degradation from environmental exposure. The above ratings assume approximately 20% increase in contact resistance from initial to end-of-life values. Larger
increases would result in proportionately lower current ratings

 All current ratings represent maximum current for each pin or set of pins called out.

 Because the separate current levels are expected to be unique per system for all three voltage types and the amount of current that can flow back through the wafer grounds is not
fully determined, we recommend consulting the table above which shows the expected current carrying capacity of different wafer combinations based on test data. Rather than
reducing current capacity, this approach gives the system designer guidelines to appropriately estimate current levels per wafer based on how current is uniquely distributed across
the three voltages, while maintaining the ability to maximize current for the system.
6U/3U SpaceUM Connector
•Currently two vendors are designing and
building SpaceUM connectors

•TE Connectivity
•Smith Connectors
6U and 3U Form Factor Plug-In Unit
Dimensions OpenVPX SpaceVPX
 VITA Connector Options
3 VITA standard connectors as candidates (TE Connectivity, Amphenol, and Smith Connectors).
The SpaceVPX (VITA 78) did not make a connector recommendation.
Insufficient information largely the reason for a “No Go” on a recommendation.

Amphenol now has a VITA 46 Connector that is intermateable with the version from TE Connectivity
 Blind-Mate Optical and Coax
Connectors
ANSI/VITA 66.1 in J5
connector location – 24 or 48
optical fibers depending on
MT selection
Pictures courtesy of Elma. Elma
Backplane and CSPI 6U TeraXP
Embedded Server shown. See
http://rtcmagazine.com/articles/view
/102730#
ANSI/VITA 67.2 in J6
connector location – 8
coax connections
ANSI/VITA 66.1 in P6 connector
location – 4 lanes of FDR InfiniBand
over Optical fiber (each lane at 14
Gbaud)
 Proposed Slot Profile Name
Construction
SLTU y – PAY- nXnXnX-1X.x.x-n
n = a line in the Slot Profile
Board Size spreadsheet identifying
U = 3 or 6
VITA 65 specific connector aperture
n = # pipes Sections
pattern (if any) and RF or
or connector 10 or 14
y = Clock variations optical module population (if
• p = parallel termination patterns
any)
• s = series termination
• x = radial - not defined X = Type of Pipes or Aperture
Pipes (number of diff. pairs Connector aperture name
• Omitted field = bussed
or discrete fibers) (Connector Module size)
Slot type • S= Single Pipe (1) • A= 66.1 (full)
• PAY = payload • U= Ultra-thin (2) • B= 66.2 (full)
• STO = storage • T= Thin (4) • C= 66.3 (full)
• PER = peripheral • F= Fat (8) • E= 66.4/ 67.1/ 67.3A (half)
• SWH = switch • M= Ten (10) • G= 67.2/ 67.3B (full)
• TIM = timing • W=Twelve (12) • H= 67.3C (full new)
• D= Double (16) • J= 67.3D (half new)
Note: That order of Pipes is from top to bottom in the physical slot • Q= Quad (32)
• K= 67.3E (full+half new)
• O= Octal (64)
Outline
• What is SpaceVPX?
• SpaceVPX Use Cases and Topologies
• SpaceVPX Slot Profiles
• SpaceVPX Backplane Profile
• SpaceUM - Provisions for Redundancy and Fault Tolerance
• SpaceVPX Mechanical General Specifications
• SpaceVPX Compliance
• Backup
 SpaceVPX Compliance
SpaceVPX standards enable the creation of robust high performance space electronics systems. SpaceVPX
standardizes the interfaces necessary for developing and integrating interoperable standard electronics modules
leveraging the [VITA 65] family of standards. There are many levels of user definition while maintaining the base
capabilities needed for such systems. SpaceVPX provides for the following levels of compliance and compatibility.
•A SpaceVPX compliant module meets the module requirements of Section 8 and Section 12 (6U) or Section 16
(3U).
•A SpaceVPX compliant development chassis meets the development chassis requirements of Section 9 and
Section 13 (6U) or Section 17 (3U).
•A SpaceVPX compliant backplane meets the backplane requirements of Section 7 and Section 11 (6U) or Section
15 (3U).
•Permission 2-1: Compliant backplane implementations based on an included topology may be reduced by any
number of slot types and/or increased by any number of peripheral slots, as long as single-fault tolerance
requirements are maintained.
 SpaceVPX Compliance (2)
A SpaceVPX compatible backplane meets the backplane requirements of a SpaceVPX compliant backplane while
allowing the absence of spares (redundant modules) and/or SpaceUM modules.
A SpaceVPX compatible module is any module that operates without causing damage to itself or other SpaceVPX
elements when plugged into a SpaceVPX slot as defined in Section 6 and Section 10 (6U) or Section 14 (3U)
contained within a SpaceVPX backplane as defined in Section 7 and Section 11 (6U) or Section 15 (3U). Any
OpenVPX module not modified to be compliant with the SpaceVPX standard is SpaceVPX compatible if it meets the
requirements for a SpaceVPX compatible module.
A fully compliant fault tolerant SpaceVPX system provides at least single fault tolerant capabilities throughout.
• Permission 2 2: Based on the system reliability requirements, modules may be combined or attached.
• Rule 2-2: Single point fault tolerance shall be achieved between each redundancy grouping as well as on all
intergroup interfaces.
Such a system typically includes a SpaceVPX compliant chassis, a SpaceVPX compliant backplane, one to four
SpaceUM modules and two or more SpaceVPX compliant and/or compatible modules.
New Efforts
SpacVNX (VITA 74.4)
 The Story Behind VNX
VNX is a standards based, small form factor, ecosystem and infrastructure
◦ VITA-74 Committee est. by VITA Standards Organization(VSO) in early 2010
◦ The VITA-74 Committee has significant involvement from several merchant board manufacturers, system integrators, and defense primes
◦ The Standard’s status is “Released for Trial Use” and is gaining wide acceptance
◦ VNX Marketing Committee established by VSO in early 2014

VNX used existing standards to reduce technical risk and schedule

◦ VITA-46 VPX and VITA-65 Open VPX topology and pin assignments
◦ VITA-57 FMC connector
◦ PICMG COM Express Mini SBC

VNX committee provides reference chassis design in the spec.

◦ 12.5mm and 19mm Modules
◦ 4-Slot cubical chassis
 What is SpaceVNX?
VNX is a standard for plug-in modules
◦ Compute, Processing, Sensors, Memory and I/O
◦ 19mm and 12.5mm

VNX was designed from the ground up to be inherently rugged and conduction cooled

VNX was designed for the Small Form Factor marketplace

VNX is designed to be similarly architected to VPX systems, but at a smaller size, lower power, and
lower cost
 What is in SpaceVNX?

Payload input
Processing/Memory
card
Output card

Power card
 Value Proposition
Small satellite benefits
◦ Lower overall cost to an operational system.
◦ Disaggregation allows for greater system resiliency and redundancy
◦ System would become “single-point failure” tolerant through redundant power distribution and fault detection on critical
configuration signals

Small Satellite Standards Development

◦ Increased market potential and vendor competition for user needs

Adoption of VITA 74
◦ A marketed reduction in CSWaP of rugged embedded computer systems
◦ Concurrent increase in architectural modularity
◦ Provision of higher performance computing capability in a smaller form factor
◦ Optional implementation of PCIe Ring Topology
◦ Robust system diagnostics
 SpaceVNX Use Cases
I. Single small satellite high performance computing (data collection and data analytics) capability at a
lower cost.

II. Single small satellite networked high performance computing platform with a large data collection and
processing capability.

III. Disaggregated cluster of networked satellites designed for a variety of data collection and data analysis
applications with a single sensor.

IV. Disaggregated cluster of network satellites designed for variety of data collection and data analysis
applications with multiple sensors, where the networked cluster fuses the data from all active sensors.
 SpaceVNX Ring Topology Concepts
Redundant PCIe Network
High Bandwidth SBC Ring
Low Bandwidth I/O Ring
Any contiguous selection of components will always have 4x
fiber-optic connections
Applicable to other PCIe Architectures (VPX)
Compatible with PCIe Gen2 and ultimately Gen 3
CES has built boards and systems using similar 3U VPX PCIe
Linear Topology

It is feasible to consider a Ring Topology generated by a

cluster of small satellites.
Questions?
Backup