Avionics and Software Project

Metadata Updated: February 28, 2019

The goal of the AES Avionics and Software (A[HTML_REMOVED]S) project is to develop a reference avionics and software architecture that is based on standards and that can be scaled and customized. The architecture will contain basic core elements and functionality needed for any spacecraft. The goal for specific mission implementation is that the avionics will be 80% core Avionics and Software elements and 20% unique.This project incorporates and builds on the results from the AES Avionics Architecture for Exploration and the Core Flight Software projects.The A[HTML_REMOVED]S project will also focus on the affordability and maintainability of avionics systems. The project will take into account design, development, test, and evaluation (DDT[HTML_REMOVED]E) costs, maintenance costs, upgrade flexibility, size, weight, and power (SWaP).The following architecture guidelines will be followed:Minimize SWaP for Avionics in Flight VehicleUse wireless where possibleMinimize wire weightUse low/no power sensorsPick a topology that keeps the processors close to what they controlMinimize CostUse existing capabilities to avoid near-term DDT[HTML_REMOVED]EAllow for growth using new technology to avoid future DDT[HTML_REMOVED]EAllow for infusion of new technology to reduce sustainingLeverage commercial technology development efforts as applicableMinimize Risk (multi-faceted)Use proven technology for critical functionsUse existing capabilities to minimize schedule riskNASA should develop and own the Reference ArchitectureDevelop a reference implementation, utilizing existing standards when possible, of the architecture that can be provided to industry as a basis for standards[HTML_REMOVED]The A[HTML_REMOVED]S project will build on the progress made by two previous AES projects: the Avionics Architectures for Exploration project and the Core Flight Software (CFS) project. The work accomplished under these previous AES Projects has resulted in a core avionics architecture for future exploration vehicles.[HTML_REMOVED] Key elements of this architecture, shown in the Figure: Baseline Avionics Architecture, are:The use of Ethernet as a backbone data bus. Time Triggered Ethernet (TTE) is included in order to accommodate any deterministic data requirements.[HTML_REMOVED] It has been shown that standard Ethernet and TTE can co-exist on the same data busUse of existing IEEE 802.11 communications standards for proximity communicationsUse of ISA100.11a communications standards for wireless instrumentation systems, which will serve to reduce the weight and complexity of point-to-point wiring.The use of Core Flight Software, certified for human spacecraft applications in FY14, which will support reusability and commonality of software applications.Development of a catalog of processors that can be used for Low-Earth orbit (LEO), Cis-Lunar, and deep-space applicationsDevelopment of a bus translator (Common Avionics Enabler) to convert different network standards to Ethernet.Advances in Human Interface systems to enable improved Astronaut interactions with future space vehicles[HTML_REMOVED]The Avionics and Software Project team will develop a system level environment and architecture that will accommodate equipment from multiple vendors in order to benchmark performance for missions beyond low Earth orbit (LEO). This will allow NASA to take advantage of strides being made by industry to drive our development and reduce sustaining costs. The project team will also evaluate emerging technologies in industry and academia to ensure that other potentially beneficial concepts are not overlooked.The reference architecture will be developed by dividing it into four core areas: Command and Data Handling (C[HTML_REMOVED]DH), Wireless and Communications, Human Interfaces, and Software. The hardware selected for these core areas will typically be mid/high TRL and currently available. The hardware must also have lineage that gives the team confidence that a radiation tolerant version that can survive the environment beyond Earth orbit and will be available within a reasonable time.[HTML_REMOVED]The C[HTML_REMOVED]DH Team will focus on the areas of processors and single board computers, network architecture and hardware, instrumentation systems, and hardware/network standards. They will demonstrate the use of multiple operating systems such as VxWorks, Integrity, Xenomai, and RTEMS, all utilizing Core Flight Software on the host processor. Also, they will address radiation tolerance issues with higher performance processors which are required to support the demands of human exploration. Various network technologies will be investigated for critical and non-critical applications.The Wireless and Communications Team will focus on developing a communications architecture that will operate over multiple mission phases and across various users, including international and commercial partners. They will take into account communications amongst several vehicles, EVA, and the ground while incorporating Delay/Disruption Tolerant Networking (DTN) technology to enable internetworking in the presence of long delays and frequent disruptions. The team will consider systems that support multiple formats, reconfigurability, adaptive power control, and other cognitive capabilities. The system will also have to address the high data rate demands of human exploration. The communications team will evaluate existing communications hardware from industry, including existing commercial and international standards.[HTML_REMOVED] The team will also support ongoing standardization efforts for new technology as applicable, to help address the needs for space applications.The Human Interfaces Team will address the great challenge of providing displays, audio systems, video systems, and controls which will reliably function in the environment beyond low Earth orbit, where new operational concepts will be needed due to communication delays. They will evaluate new display technologies (such as OLEDs) and Graphics Processing Unit options (including a software GPU). Off the shelf video and audio systems will be evaluated for performance, integration within the architecture, and environmental concerns.The Software team will continue the development of CFS with a specific focus in human-rated systems. A Johnson Space Center Engineering Directorate Internal Research and Development (IR[HTML_REMOVED]D) project initially seeded analysis and prototyping into the applicability of CFS toward human rated systems. This effort was augmented in June 2012 under AES funding specifically targeted to utilize the Orion platform as a target architecture supporting a concept mission to the Earth-Moon L2 point. The work in FY12 resulted in a key conclusion confirming viability of the CFS architecture to adapt to both inter-machine and intra-machine fault tolerance. The work prototyped and demonstrated the CFS system running both within the ARINC-653 standard allowing intra-machine software partitioning as well as on a software-voting triplex platform allowing inter-machine redundancy. Reusability of applications on these differing architectures was confirmed by running identical cFE applications and GNC applications on both platforms, for only a relatively small development effort for specific platform adaptation.

Access & Use Information

Public: This dataset is intended for public access and use. License: U.S. Government Work

Downloads & Resources


Metadata Created Date August 1, 2018
Metadata Updated Date February 28, 2019

Metadata Source

Harvested from NASA Data.json

Additional Metadata

Resource Type Dataset
Metadata Created Date August 1, 2018
Metadata Updated Date February 28, 2019
Publisher Space Technology Mission Directorate
Unique Identifier TECHPORT_32947
Maintainer Email
Public Access Level public
Bureau Code 026:00
Metadata Context https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld
Metadata Catalog ID https://data.nasa.gov/data.json
Schema Version https://project-open-data.cio.gov/v1.1/schema
Catalog Describedby https://project-open-data.cio.gov/v1.1/schema/catalog.json
Harvest Object Id c87c9733-c40d-493f-b364-7efae2757dc0
Harvest Source Id 39e4ad2a-47ca-4507-8258-852babd0fd99
Harvest Source Title NASA Data.json
Data First Published 2017-09-01
Homepage URL https://techport.nasa.gov/view/32947
License http://www.usa.gov/publicdomain/label/1.0/
Data Last Modified 2018-07-19
Program Code 026:027
Source Datajson Identifier True
Source Hash 40e4d9bf5634a2e3a6947d92a6ed5cef8f6e2940
Source Schema Version 1.1

Didn't find what you're looking for? Suggest a dataset here.