1 / 50

Bringing the Vision of Plug-and-play to High- Performance Computing on Orbit

Bringing the Vision of Plug-and-play to High- Performance Computing on Orbit. Presentation to HPEC 2009 22 Sept 2009. Outline. Introduction Space Plug-and-Play Avionics (SPA) Extending SPA to HPEC Conclusions. Space PnP Avionics (SPA). Introduction Key Features Status. “platform”.

kennemer
Download Presentation

Bringing the Vision of Plug-and-play to High- Performance Computing on Orbit

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bringing the Vision of Plug-and-play to High-Performance Computing on Orbit Presentation to HPEC 2009 22 Sept 2009

  2. Outline • Introduction • Space Plug-and-Play Avionics (SPA) • Extending SPA to HPEC • Conclusions

  3. Space PnP Avionics (SPA) • Introduction • Key Features • Status

  4. “platform” plug-and-play component driver USB interface chip Analogy of Consumer PnP with SPA “platform” plug-and-play component electronic datasheet interface module

  5. Space Plug-and-play AvionicsKey Features • Single-point interfaces (e.g. SPA-S) and protocols • Appliqué Sensor Interface Module (ASIM) • Electronic datasheets (XTEDS) • Software -- Satellite data model (SDM) • Test bypass • Pushbutton toolflow

  6. Interfaces • SPA-U (Data transport = USB 1.1, limited to 12 Mbps for entire bus) • SPA-S (Data transport = Spacewire, limited to 600 Mbps per direction per link) Devices with basic interfaces Data transport (commands, config, data) SPA-device n primary interface Power (two pins) ( 4.5A(L) or 30A(U) ) 2 Sync (two pins) (RS-422, 5V )* test bypass interface (TBI) 2

  7. Distribution of bandwidth in systems Very high data rate “SPA-Optical” high data rate (< 620 Mbit/sec) SPA-S Performance of components low data rate (< 1 Mbit/sec) SPA-U Very low data rate (< 10 kilobit/sec) “SPA-1” (future) Number of components

  8. Heterogeneity – Mixture of SPA networks SPA-y Network Bridge Node SPA-x Network

  9. Applique Sensor Interface Module (ASIM) – Simplifying SPA Engineering and SPA Compliance

  10. eXtended Transducer Electronic Datasheet (xTEDS) XTEDS • Primary mechanism for self-description • Embedded in hardware and software applications • Describes “knobs” and “measurands” • Conveys “semantic precision” through a common data dictionary (CDD) • Enforces order in the “LEGO universe” of SPA (features only exist if known through XTEDS) • Recently released to public domain • Studied as possible AIAA and ISO standard (facet) Interface (facet) Interface Message Message Variable Variable CDD

  11. The Satellite Data Model (SDM) – Building Awareness into Plug-and-play

  12. Test Bypass – Automating Support for Hardware-in-the-Loop

  13. 2. 4. COMPARE SIM VS. THE ORIGINAL MISSION SPACE- CRAFT PROFILER 3. 1. AUTO- GENERATE “EVERYTHING” MISSION CAPTURE Push-button Tool Flow(aka Satellite Design Automation) Mission Goals and Requirements Component Capabilities Drag & Drop Design Automatic Verification Iterate ************************************************************************* * CATEGORY RULES * ************************************************************************* predCategory( catidReferenceFrame ). predElementOf( catidReferenceFrame, catidReferenceFrame ). predCategory( catidCoordinateSystem ). predElementOf( catidCoordinateSystem, catidCoordinateSystem ). ************************************************************************* * INTERFACE RULES * ************************************************************************* predInterface( iidIEnvironmentObject ). predElementOf( iidIEnvironmentObject, catidEnvironment ). predInterface( iidIMomentumStorage ). predElementOf( iidIMomentumStorage, catidActuator ). ************************************************************************* * COMPONENT RULES * ************************************************************************* predComponent( clsidCEarth ). predElementOf( clsidCEarth, catidReferenceFrame ). predElementOf( clsidCEarth, catidEnvironment ). fncIn( iidIEnvironmentObject, clsidCEarth ). Performance Modeling Design Verification Rules Engine

  14. Other Tenets of SPA • Seek OS independence • Seek decentralization • Seek to conceal (unnecessary) complexity through encapsulation

  15. SPA Status • SPA Workshops (eight from 2004-2006) • Creation of Responsive Space Testbed(Kirtland AFB) • Flight developments • RESE (SPA-U, 4-port) – Launched and operated September 2007 • TacSat 3 (SPA-U, 4-port) – Integration into TacSat 3 (Launched in 2009) • Adoption of SPA as central interface approach for TacSat 5 • Creation of outreach concepts for SPA-based CubeSats • International agreement (with Sweden) and pursuit of national/international standards for SPA

  16. Plug-and-play Satellite (PnPSat) • First spacecraft ever built entirely on PnP principles • Decentralized, scalable computation • Use of satellite data model • All components (even panels) are SPA devices • up to 48 mounting sites • Ambitious development schedule • Targeting flight in 2009

  17. Component and Experiment Accommodations Battery Assembly (2) Magnetometer Primary Experiment (Example Only) Coarse Sun Sensor Module (2) Transceiver and Comsec Solar Array HPCOO (2) Torque Rod (3) Charge Control Electronics Reaction Wheel and Electronics (3) • A full complement of PnPSat components shown • By recessing electrical infrastructure and harnessing, we significantly increase flexibility for component and experiment mounting • Initial version of PnPSat may have fewer spacecraft components than the version shown

  18. Encapsulation (complexity hiding)

  19. Encapsulation (complexity hiding)

  20. Miniaturization CubeFlow = SPA+CubeSat • Targeting PnP platforms as small as cubesats (100mm) • Supports increased payload mass fraction and creation of PnP nanosatellites • Compact nanosat modular form factor (NMF)standard (70mm x 70mmx12.5mm)

  21. CubeFlow Training • “Eli Whitney meets spacecraft” • Short course based on the principles of SPA embedded in take-apart Cubesats • Entire system (with laptop console) fits in briefcase • Fifteen+ kits distributed so far (May 2009 course) • More CubeFlow courses planned

  22. SPA for high-performance embedded systems? • Scaling of SPA interfaces currently limited • Complex processing architectures far from plug-and-play

  23. Example Processing Chain Framework for high-performance (surveillance) sensor Digital Processing Analog processing / conversion Front-end processing Back-end processing TDP ODP MDP Processes that are done on every single object. Much reduced data rate compared to raw data. Generates enhance objects Sensor – Pixels, # rows, # cols, # frames/sec, modes (windowing) Processes that are done on every single pixel, intensive processing, but usually relatively simple. generates objects Processes that are done on enhanced objects. Much reduced data rates, but much greater # ops / enh.object

  24. Generic Processing System TDP ODP ASIC ASIC MDP ODP DSP Sensor data ASIC ODP DSP ODP DSP ODP DSP ODP DSP ASIC

  25. Example 1: TacSat2 Processing System TDP ODP FPGA FPGA FPGA ASIC ODP VLIW MDP RAD750 Sensor data FPGA FPGA Mem

  26. Example 2: Sensor And Fusion Engine (SAFE) Processing System TDP FPGA FPGA Link Sensor data ODP MDP MDP ODP VLIW ODP VLIW ODP VLIW ODP VLIW ODP VLIW TDP MDP FPGA FPGA Link ODP 1-12 (WSSP) MDP

  27. Problems With Ad Hoc HPEC Frameworks • Constant reinvention of reconfigurable computation architectures • Fragile, proprietary link structures • Difficult migration across heterogenous partitions How could SPA concepts be applied?

  28. Avoiding the “yet another reconfigurable computer” syndrome • Nodes based on single computation device • Ok to have heterogeneous node composition • Regular socket and messaging infrastructure • Not ok to have disparate socket/interface/messaging infrastructure • Pray for the existence of adequate tools to handle amortizing code (circuitize-able) into the fabric of distributed nodes • Use SPA-like ideas to manage the whole thing

  29. MPP Platform to study high-bisection bandwidth reconfigurable computing architectures (a) (b) (c)

  30. Conceptual “HPEC SPA” network without optical (multiple ports/device) SPA Device SPA Device SPA Router SPA Device SPA Router SPA Device SPA Device Hardware in loop interface HWILS

  31. Conceptual HPEC-SPA network based on optical transport Idealized optical backplane SPA Device SPA Device SPA Router SPA Device SPA Router SPA Device SPA Device Hardware in loop interface HWILS

  32. SPA-Optical “exec summary” • Also referred to as SPA-10 (original Gbps target, just a label now) • Expect to have properties similar to (nonscalable) SPA-S, but higher link speed • Use of embedded clock recovery • Desire to support optical physical layer for data, command, synchronization • Allows >Tbps scaling through WDM • Allows flexibility in “provisioning” (i.e. assigning particular wavelengths, protocols, to particular SPA-10 ports) • Allows greater flexibility in managing topology, routing policies, faults

  33. SPA-10 Device concepts RAW Device Types Interface schemes Fixed wavelength Sensor (camera, radar, comm, etc.) Tuned wavelength Mass storage SPA-10 Device WDM within single device Processing node

  34. XTEDS SPA-10 Possible Interface DetailsHybrid E/O SPA-10 Device Optically Enhanced ASIM (OASIM) Ser Des Hi BW out Hi BW in RAW DEVICE RAW DEVICE config OASIM Breakout I/O sync uP power

  35. SPA Computation • Addressing interconnection bottleneck leaves the problem of efficiently mapping computation problems to resources

  36. Complex (multi-FPGA board) Circuit Representation

  37. Partition into Unit-sized Portions D A C B

  38. Insertion of Socketing Infrastructure D A C B

  39. Wavelength Assignments to Sockets D A C B

  40. Transferral to Idealized Backplane D A Idealized Optical Backplane C B

  41. SPA-10 Modules C C A B Idealized Optical Backplane (Wavelength multiplexing drawn as spatial multiplexing for illustrative purposes)

  42. SPA-10 SPA-10 SPA-10 SPA-10 Colorless optical transport Idealized Optical Backplane

  43. Idealized (vs. practical) optical backplanes • Idealized: as described in Gilder’s Telecosm • Infinite resource, every actor has own wavelength • Practical: limited by finite resources and protocol barriers • Limited number of physical channels (fibers) • Limited number of wavelengths (CWDM,DWDM) • Differing channel characteristics (transceiver data rates, single-vs-multi-mode, transceiver spectral characteristics) • Time-slotting (time-division multiple access) • Protocol assignment (matching disparate OSI stacks) • Limitations of optical resources (e.g., outages due to time necessary to implement switch re-assignments)

  44. Practical implementation SPA-10 SPA-10 SPA-10 SPA-10

  45. How to “LEGO-ize” Anything(generalization of plug-and-play) Transport portal Payload Transport portal ASIM xTEDS Config. Control portal Core XTEDS extension extension

  46. Challenges in “plug-and-play” provisioning • Mapping algorithms into a variety of node types • FPGA-based • Single/multicore processors • Coordinating socketing • Messaging protocol • Establishing finite fabric resource allocation effectively with tolerable gaps in time due to transitions in provisioned configurations Source: http://www.kasahara.elec.waseda.ac.jp/schedule/

  47. Advent of Megacompilers? Problem represented in neutral format Number and type of target objects Awareness of network topology constraints Bitstreams for each target object Mega-compiler Topology for connecting objects Provisioning constraints Awareness of target architecture constraints

  48. In-house SPA-O R&D Testbed (plan) 1st High Data Rate Sensor High Speed Scope External PRBS Data In Router control Optical TX/RX SPA S Connector Optical Signal Electrical Signal Optical Switch/Router SDM/xTEDS/Apps Large Memory Storage 2nd High Data Rate Sensor On Board Processor

  49. Summary • Space plug-and-play (SPA) continues to gain momentum (completion of PnPSat 1, start of PnPSat 2, TacSat 5, ORS Chileworks, CubeFlow, standardization) • SPA-Optical / SPA-10 represents a collection of concepts to extend SPA to high-performance embedded computation • Early work on SPA-Optical testbed underway at AFRL (Kirtland AFB)

More Related