Transcript CFS HSF JSC Status

Spacecraft Software Engineering Branch/ER6
Current Status of cFE/CFS use at JSC
Steve Duran
Spacecraft Software Engineering Branch
Software, Robotics and Simulation Division
NASA Johnson Space Center
10/17/12
Spacecraft Software Engineering Branch/ER6
Agenda
•
•
•
•
JSC’s Spacecraft Software Engineering Branch
GSFC’s cFE/CFS use at JSC
Current projects
Current plans
8/4/2016
2
Spacecraft Software Engineering Branch/ER6
JSC’s Spacecraft Software Engineering
Branch
• Flight GFE software development as well as ground support
software
• Technology development
• Oversight/System’s Management
– Orion/MPCV
• CMMI Level 3 Organization
8/4/2016
3
Spacecraft Software Engineering Branch/ER6
GSFC’s cFE/CFS use at JSC
• cFE/CFS use assessed and selected for the Project M (later
changed to Morpheus) lander
– Very aggressive schedule
• We quickly appreciated the many benefits through high application
development productivity rates and fully functioning code
• Successfully used and demonstrated on the Morpheus Vertical Test
bed
• This experience lead to use on other projects and the desire to
make CFS human rate-able for future projects
8/4/2016
4
Spacecraft Software Engineering Branch/ER6
CFS Evolution Vision for Human Rating
Core Flight Software
•
Evolve toward “human rating” – current human systems
–
Phase 1 – Analyze & Prototype
•
•
•
–
Phase 2 – Productize
•
•
•
Investigate additional services/abstractions, if any, to support redundancy/fault tolerance by adapting to platforms
designed for human spaceflight
– Time-space partitioned architectures (inter-machine fault tolerance)
» Greenhills ARINC OS (DO178B) , vxWorks ARINC OS (Triplex PPC)
– Lock-step redundant architectures (inter-machine fault tolerance)
» Hardware voting (X-38)
» Software voting
– “certifiable” architectures – DO178B
– Time-triggered architectures
– Integrate with Displays & Control System for proof of concept
Integrate with ECLSS “bubble” for proof of concept
Integrate with simulation environment (Trick)
Develop flight-qualified code resulting from Phase 1 (Planned AES)
Document and merge product with Goddard for distribution
Ensure state-of-the art by evolving toward future human platforms – future systems
–
Investigate additional services, if any, needed to support different topologies
•
•
•
Distributed systems
Multi-core processor systems
Build/Maintain New/Existing CFS-based Systems and simulation architectures
–
–
–
Maximize commonality/synergy between projects by minimizing custom software & unique hardware
Build library of reuse “bubbles”
Extend Development Environment
•
5
Evolve Eclipse and Develop Matlab/Simulink Models for integration with CFS services and API
Core Flight Executive / Core Flight Software
PPC750
Adding support for
- ARINC VxWorks OS
- Software Voting
Fault Containment between
processors
6
cFE/CFS
Reuse
Components
Mission
Specific
Components
Partitioning Layer
Greenhills ARINC OS
Adding Voting / Replication
Reuse
Components
Adding support for
- ARINC Greenhills OS
- DO178B
cFE/CFS
Mission
Specific
Components
cFE/CFS
Reuse
Components
Processor
Mission
Specific
Components
Non-Partitioned
OS
Fault containment
within Processor
Adding Partitioning
Reuse
Components
cFE/CFS
• Reusable Spacecraft Component Library &
Architecture
• Operating System / Hardware Abstraction Layer
(OSAL)
Mission
Specific
Components
Reuse
Components
Original CFS
Mission
Specific
Components
Spacecraft Software Engineering Branch/ER6
Layered Components Added
for Fault Isolation
cFE/CFS
Partitioning Layer
VxWorks ARINC OS
Fault Tolerant Software Voting
PowerPC 750GX
Spacecraft Software Engineering Branch/ER6
Current Projects
•
•
•
•
•
•
Morpheus Lander/Vertical Test bed
ISS Microcapsule
MMSEV (Multi-Mission Space Exploration Vehicle)
AEMU (Advanced Extravehicular Mobility Unit)
DSH (Deep Space Habitat) (FY13)
AES CFS (FY13, focus on Human rating, time/space partitioned
environments, redundant hardware)
8/4/2016
7
Spacecraft Software Engineering Branch/ER6
Current Plans
• Continue current CFS-based projects
• Through the AES CFS project, the primary task in FY13 is to make
CFS Human rate-able so that future use on a Human spacecraft
might be possible
– Productized versions of CFS applicable to architectures most
relevant to human spaceflight
– Integrate Trick simulation environment with CFS for packaged
use
• Another top priority task is to enhance CFS to be usable with fault
tolerant architectures
– Time/space partitioned (ARINC653)
– Voting architectures
8/4/2016
8
Spacecraft Software Engineering Branch/ER6
Current Plans
• Analysis tasks will additionally be performed in support of additional
advanced architectures needed by other NASA spaceflight projects
– AES Deep Space Habitation (distributed platform)
– AEMU (static/small footprint CFS version)
– MMSEV (redundant architecture)
– Morpheus (multi-core)
– Common Avionics Architecture (in definition)
8/4/2016
9
AES CFS FY13 Schedule
Spacecraft Software Engineering Branch/ER6
FY 2013
Oct
Nov
Jan
Feb
Dev complete
Major Milestones
Project Deliverables
Dec
1/29
PMP
SDP
Mar
Apr
Integrated test
Voting arch
3/29
May
Infrastructure/artifact collection
Jul
5/15
Sep
9/30
Code
Inspections
complete
SRS Design
Aug
Products complete,
demos
Trick product demo
Inspections
Product Line Repository
Jun
Tests
Complete
Integration
VDD, Guide
deployment
DO-178B cFE
Development/inspections
testing
documentation
ARINC 653 OSAL
Development/inspections
testing
documentation
Development/inspections
CFS/Trick
doc
testing
test & doc
Design & development
Advanced Arch. Analysis
Time-space partitioning
Vxworks-software voting
Distributed architectures
Static/small footprint CFS
10
Multicore architectures
prototyping
eval
prototyping
eval
prototyping
eval