Exemplar CFS Architecture

Slides:



Advertisements
Similar presentations
CESG, Fall 2011, 5 th November 2011 Stuart Fowell, SciSys Device Virtualisation and Electronic Data Sheets.
Advertisements

Folie 1 Service Oriented Architecture - Prototyping study - DLR/GSOC Author: S.Gully.
Exemplar CFS Architecture
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
NASA’s Goddard Space Flight Center Flight Software Charlie Wildermann Mike Blau Code Code 582 August 16-17, 2005.
Add intro to concept of electronic data sheets PnP based on use of this Can describe s/w as well as h/w.
12006 MAPLD International ConferenceSpaceWire 101 Seminar CCSDS Standard On-Board InterfaceS (SOIS) Rick Schnurr NASA – Goddard Space Flight Center CCSDS.
1 Lunar Reconnaissance Orbiter (LRO) CRaTER Technical Interchange Meeting C&DH Flight Software April 14, 2005.
SXC Software interfaces1 SXC: SW interfaces Ground segment SpacecraftDetectorTelescope TelecommandsTelemetry Cmd & hk parameters- conversion SpacecraftTelecommandsTelemetryProtocolBandwidthcoverage.
SOIS at Design Net Approaching Reusability in Flight Software.
ONE Concept. ONE Work area & lab setup ONE Goals Provide single network interface regardless of physical link Provide reliable, isochronous message transport.
ESA UNCLASSIFIED – For Official Use SOIS architecture to handle RIUs F. Torelli (ESA) & G. Rakow (NASA) 15/04/2013.
ESA UNCLASSIFIED – For Official Use SOIS Evaluation by the Primes F. Torelli (ESA) Software Reference Architecture - Focus on the Execution Platform ADCSS.
SOIS APP Working Group Overview. Presentation Overview Application Support Services Electronic Datasheets ESA Project History and Plans Standards Documentation.
ESA UNCLASSIFIED – For Official Use Recap of SOIS Evaluation by the Primes F. Torelli (ESA) CCSDS Spring Meeting, 23/03/2015.
Real-Time Systems Presented by: Stuart D Fowell CCSDS Time Critical Onboard Application Services Stuart D. Fowell, Keith L. Scott, Chris.
RIU as related to SOIS EDS Glenn Rakow CCSDS SOIS Spring Meeting 2013.
Overview of SOIS Electronic Data Sheets (EDS) & Dictionary of Terms (DoT) SOIS APP WG Fall 2012.
Control & Data Handling, Operator Control, Aircraft Interface to C&DH Steve Musko Space Physics Research Laboratory University of Michigan Ann Arbor, MI.
Flight Software Overview
SOIS EDS and Onboard Architectures. ESA ‘de-facto’ Architecture PUS Services Mission Applications Data Handling PUS TM/TC Internal Datapool API System.
Design and Implementation of Spacecraft Avionics Software Architecture based on Spacecraft Onboard Interface Services and Packet Utilization Standard Beijing.
1 © 2015 Fraunhofer USA, Inc. Center for Experimental Software Engineering Requirement-driven Model-based Testing of the cFS’ Software Bus Service Dharma.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
07-Apr-2014-cesg-1 Jonathan Wilmot (WG Chair) Ramon Krosley (DWG Chair) SPACECRAFT ONBOARD INTERFACES SERVICES (SOIS) AREA APP WG.
SOIS Services Version 3, with post 19 Jan 2016 Telecon mods.
Discovery Systems Where Standards are Needed. Agenda Self-Organization Efficient Discovery Discovering Data Semantics Self-organizing Network Topology.
1 1 National Aeronautics and Space Administration Future Products & Technology The Johns Hopkins University Applied Physics Laboratory Core Flight Software.
NASA’s Goddard Space Flight Center Flight Software Charlie Wildermann Mike Blau Code Code 582 August 16-17, 2005.
SOIS Services. Layered View This is the traditional diagram that summarizes SOIS services in layers of a protocol stack.
Identify internal hardware devices (e. g
SOIS and Software Reference Architecture
cFS Platforms OSAL and PSP
850x0g2 Green Book Integrating the New SOIS Summary Diagram
Space Plug-and-Play Architecture (SPA) and SSM
The CCSDS Spacecraft Onboard Interface Services (SOIS) Standards An Introduction Stuart Fowell 6th October 2009.
Deterministic Communication with SpaceWire
Generic Remote Interface Unit (RIU) Interface Control Document (ICD)
Simulink Interface Layer (SIL)
SOIS APP Working Group Overview
Subnet plus Composable Applications
SCALE: The Safe Community Awareness and Alerting Network
Code Generation from SEDS
cFE FSW at APL & FSW Reusability
Overview of SOIS Electronic Data Sheets (EDS) & Dictionary of Terms (DoT) SOIS APP WG Fall 2012.
Version 4, 2016 March 1 Teleconference
SOIS Plug-and-Play Architecture and Proposed Mapping onto SpaceWire
From Bespoke to Standard Solid State Mass Memories
SOIS architecture to handle RIUs
Network Architecture Layered system with alternative abstractions available at a given layer.
Add intro to concept of electronic data sheets
Version 3, with post 19 Jan 2016 Telecon mods
TECH SESSION #1 STANDARDS AND BUILD TOOLS
SOIS-APP Working Group Report Jonathan Wilmot (WG Chair)
Where Standards are Needed
Recap of SOIS Evaluation by the Primes
TECH SESSION #1 ELECTRONIC DATA SHEETS
Design and Implementation of Spacecraft Avionics Software Architecture based on Spacecraft Onboard Interface Services and Packet Utilization Standard Beijing.
SPACECRAFT ONBOARD INTERFACES SERVICES
SPACECRAFT ONBOARD INTERFACES SERVICES
CFS Community Day Core Flight System Command and Data Dictionary Utility December 4, 2017 NASA JSC/Kevin McCluney December 4, 2017.
See embedded notes post 21 Sept telecon
Core Flight System Software Bus Networking Application Design As Built
Integrating CCSDS Electronic Data Sheets into Flight Software
cFS Systems Technology Roadmap
Multiple Processor Systems
and Device Interfaces from CCSDS Electronic Data Sheets
Advanced Exploration Systems (AES) Core Flight Software (CFS) Project
NASA/ Johnson Space Center
GSFC cFS Product Status
Presentation transcript:

Use of EDS for S/W Bus Adaptor CCSDS SOIS 2013 Spring Meeting Jonathan Wilmot NASA GSFC

Exemplar CFS Architecture Spacecraft Data Recorder Checksum Limit Checker CFDP File Transfer File Manager Stored Commanding Data Storage Instrument 1 Manager Instrument 2 Manager Scheduler Recorder Manager GNC Sensors Onboard Models 5 Hz GPS 232 GPS IO House keeping Software Bus Time Services Table Services Executive Event Health & Safety Control Law Altimeter 232 5 Hz Services Services Alt IO 422 50 Hz State Determination IMU LN200 IO Inter-task Message Router (SW Bus) Cnd Ingest EDAC Memory Scrubber Time Manager Space Wire Power Housekeeping Recorder 1553 Bus Controller Telemetry Output C&DH App GN&C App S/C Data CFS App RAM & EEPROM SBC 1553 Time HW SpaceWire Power hw S-Comm cFE App

CFS Software Bus (SB) CFS components publish/subscribe to CCSDS packets Packets are either telecommand or telemetry Publishers have no knowledge of subscribers One publisher to many subscribers is typical Control log, Fault management, data storage, telemetry output Send and forget Subscribers can request packet meta data (Publisher appid, system, subsystem) Subscriptions are based on packet app id (2^11) Common CFS applications use a consistent set of app ids, but missions can redefine them C structures are used in the software to extract packet data CCSDS headers are not part of the C structures but via abstractions Ad-hoc tools are used to convert between C structures and ground systems and tool databases Common definition parsed to generate packet definitions for other systems NASA working to establish CFS governance model and community Architecture, software, and tools commonality across many NASA missions Potential support for SOIS MTS compliance (Likely in the long term)

CFS Software Bus (SB) SB implements QOS only at the network interfaces SB API accepts QOS parameters and passes them down There is a Software Bus Network (SBN) component that plugs in for each network type (Ethernet, TTEthernet,1553, SpaceWire...) SBN is also used for interpartition (ARINC 653, PikeOS...), inter-core messaging (Multi-core), and intra-processor SB is not aware that SBN(s) exists SBN will pass network to network through traffic SBN implements a peer to peer network No protocol master, connection mappings are kept local Peers can come and go at runtime All subscription requests are replicated (This can have scaling issues) Ground interfaces are through Command Ingest and Telemetry Output plugins Not all components look at packet contents Data storage, telemetry output, both just filter and forward

Formats CFS may move toward the DEM format which moves beyond the 2^11 appid (topic) limitation Support for audio and video encapsulation CCSDS format Data Exchange message (DEM) format

EDS gets used in many places EDS(s) Subnetwork services Channelizations and service type (packet…) defined here Data Consumers I/O Schedule Device SpaceWire I/O Device Device specific driver(s) Device I/O Schedule device Raw Sensor processing device RIU Partition, core, network… device 1553 I/O Device Device Device I/O & Driver Software Bus Network (SBN) Software Bus Network (SBN) 422 Device

Use of EDS in the System Stack Layered Approach: Use of EDS in the System Stack HW and/or software logic SpaceWire 1553 Subnetwork I/O Sensor Processing Telemetry Output EDSes are incorporated into other EDSes up the stack. All of the spacecraft EDS eventually provide input into the ground systems and operational databases.

Meta data for file contents? End to End EDS EDS XTCE database EDS comm Telemetry monitors Control Center EDS Software Bus SOIS MTS EDS Star Tracker EDS Reaction Wheel EDS RTU driver EDS EDS File Manager EDS Command EDS Telemetry comm CFDP File Transfer EDS EDS EDS SOIS Stack HW RTU Mass Storage Meta data for file contents? XTEDS HW thermistor thermistor EDS 1451 HW 1451