Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space Avionics”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Space Generic Open Avionics Architecture (SGOAA) reference model technical guide

This report presents a full description of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA consists of a generic system architecture for the entities in spacecraft avionics, a generic processing architecture, and a six class model of interfaces in a hardware/software system. The purpose of the SGOAA is to provide an umbrella set of requirements for applying the generic architecture interface model to the design of specific avionics hardware/software systems. The SGOAA defines a generic set of system interface points to facilitate identification of critical interfaces and establishes the requirements for applying appropriate low level detailed implementation standards to those interface points. The generic core avionics system and processing architecture models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

Wray, Richard B.↗
NASA NTRS2008

Assessing Requirements Quality through Requirements Coverage

In model-based development, the development effort is centered around a formal description of the proposed software system the model. This model is derived from some high-level requirements describing the expected behavior of the software. For validation and verification purposes, this model can then be subjected to various types of analysis, for example, completeness and consistency analysis [6], model checking [3], theorem proving [1], and test-case generation [4, 7]. This development paradigm is making rapid inroads in certain industries, e.g., automotive, avionics, space applications, and medical technology. This shift towards model-based development naturally leads to changes in the verification and validation (V&V) process. The model validation problem determining that the model accurately captures the customer's high-level requirements has received little attention and the sufficiency of the validation activities has been largely determined through ad-hoc methods. Since the model serves as the central artifact, its correctness with respect to the users needs is absolutely crucial. In our investigation, we attempt to answer the following two questions with respect to validation (1) Are the requirements sufficiently defined for the system? and (2) How well does the model implement the behaviors specified by the requirements? The second question can be addressed using formal verification. Nevertheless, the size and complexity of many industrial systems make formal verification infeasible even if we have a formal model and formalized requirements. Thus, presently, there is no objective way of answering these two questions. To this end, we propose an approach based on testing that, when given a set of formal requirements, explores the relationship between requirements-based structural test-adequacy coverage and model-based structural test-adequacy coverage. The proposed technique uses requirements coverage metrics defined in [9] on formal high-level software requirements and existing model coverage metrics such as the Modified Condition and Decision Coverage (MC/DC) used when testing highly critical software in the avionics industry [8]. Our work is related to Chockler et al. [2], but we base our work on traditional testing techniques as opposed to verification techniques.

Rajan, Ajitha↗
NASA NTRS1990

IEEE/AIAA/NASA Digital Avionics Systems Conference, 9th, Virginia Beach, VA, Oct. 15-18, 1990, Proceedings

The present conference on digital avionics discusses vehicle-management systems, spacecraft avionics, special vehicle avionics, communication/navigation/identification systems, software qualification and quality assurance, launch-vehicle avionics, Ada applications, sensor and signal processing, general aviation avionics, automated software development, design-for-testability techniques, and avionics-software engineering. Also discussed are optical technology and systems, modular avionics, fault-tolerant avionics, commercial avionics, space systems, data buses, crew-station technology, embedded processors and operating systems, AI and expert systems, data links, and pilot/vehicle interfaces.

Source record↗
NASA NTRS1991

Architecture for Survivable System Processing (ASSP)

The Architecture for Survivable System Processing (ASSP) Program is a multi-phase effort to implement Department of Defense (DOD) and commercially developed high-tech hardware, software, and architectures for reliable space avionics and ground based systems. System configuration options provide processing capabilities to address Time Dependent Processing (TDP), Object Dependent Processing (ODP), and Mission Dependent Processing (MDP) requirements through Open System Architecture (OSA) alternatives that allow for the enhancement, incorporation, and capitalization of a broad range of development assets. High technology developments in hardware, software, and networking models, address technology challenges of long processor life times, fault tolerance, reliability, throughput, memories, radiation hardening, size, weight, power (SWAP) and security. Hardware and software design, development, and implementation focus on the interconnectivity/interoperability of an open system architecture and is being developed to apply new technology into practical OSA components. To insure for widely acceptable architecture capable of interfacing with various commercial and military components, this program provides for regular interactions with standardization working groups (e.g.) the International Standards Organization (ISO), American National Standards Institute (ANSI), Society of Automotive Engineers (SAE), and Institute of Electrical and Electronic Engineers (IEEE). Selection of a viable open architecture is based on the widely accepted standards that implement the ISO/OSI Reference Model.

Wood, Richard J.↗
NASA NTRS1994

A method to compute SEU fault probabilities in memory arrays with error correction

With the increasing packing densities in VLSI technology, Single Event Upsets (SEU) due to cosmic radiations are becoming more of a critical issue in the design of space avionics systems. In this paper, a method is introduced to compute the fault (mishap) probability for a computer memory of size M words. It is assumed that a Hamming code is used for each word to provide single error correction. It is also assumed that every time a memory location is read, single errors are corrected. Memory is read randomly whose distribution is assumed to be known. In such a scenario, a mishap is defined as two SEU's corrupting the same memory location prior to a read. The paper introduces a method to compute the overall mishap probability for the entire memory for a mission duration of T hours.

Gercek, Gokhan↗
NASA NTRS2001

Micro Navigator

Miniature high-performance low-mass space avionics systems are desired for planned future outer planetary exploration missions (i.e. Europa Orbiter/Lander, Pluto-Kuiper Express). The spacecraft fuel and mass requirements enabling orbit insertion is the driving requirement. The Micro Navigator is an integrated autonomous Guidance, Navigation & Control (GN&C)micro-system that would provide the critical avionics function for navigation, pointing, and precision landing. The Micro Navigator hardware and software allow fusion of data from multiple sensors to provide a single integrated vehicle state vector necessary for six degrees of freedom GN&C. The benefits of this MicroNavigator include: 1) The Micro Navigator employs MEMS devices that promise orders of magnitude reductions in mass power and volume of inertial sensors (accelerometers and gyroscopes), celestial sensing devices (startracker, sun sensor), and computing element; 2) The highly integrated nature of the unit will reduce the cost of flight missions. a) The advanced miniaturization technologies employed by the Micro Navigator lend themselves to mass production, and therefore will reduce production cost of spacecraft. b) The integral approach simplifies interface issues associated with discrete components and reduces cost associated with integration and test of multiple components; and 3) The integration of sensors and processing elements into a single unit will allow the Micro Navigator to encapsulate attitude information and determination functions into a single object. This is particularly beneficial for object-oriented software architectures that are used in advanced spacecraft. Additional information is contained in the original extended abstract.

Blaes, B. R.↗
NASA NTRSDate not supplied

Launch Vehicle and Spacecraft Transmitter Electromagnetic Compatibility

The Launch Services Program at NASA’s Kennedy Space Center (KSC) is the primary gate for acquiring commercial vehicles to provide a cost effective ride to space for NASA spacecraft. With the lunar Gateway, more human tended elements are planned for launch. One challenge facing the space industry is the proliferation of communication and science transmitters at frequencies beyond the qualification of space avionics and instruments. Studies have ensued to examine the intricacies of performing radiated susceptibility testing and analysis above 18 GHz. Changes in the launch vehicle communications interface to the range have also lead to new launch vehicle antenna systems and more reliance on GPS and telemetry systems. Finally, research initiated at KSC in the area of predicted electric field distributions in launch vehicle payload fairings have spawned Small Business Technology Transfer initiatives for industry to investigate statistical algorithm and computational improvements in large payload fairing modeling of transmitters at frequencies in the GHz range. These topics, along with electromagnetic compatibility testing for launch vehicles will be discussed.

Electromagnetic Testing Cavity Statistics↗
NASA NTRS2004

Space Application Requirements for Organic Avionics

The NASA Marshall Space Flight Center is currently evaluating polymer based components for application in launch vehicle and propulsion system avionics systems. Organic polymers offer great advantages over inorganic corollaries. Unlike inorganics with crystalline structures defining their sensing characteristics, organic polymers can be engineered to provide varying degrees of sensitivity for various parameters including electro-optic response, second harmonic generation, and piezoelectric response. While great advantages in performance can be achieved with organic polymers, survivability in the operational environment is a key aspect for their practical application. The space environment in particular offers challenges that must be considered in the application of polymer based devices. These challenges include: long term thermal stability for long duration missions, extreme thermal cycling, space radiation tolerance, vacuum operation, low power operation, high operational reliability. Requirements for application of polymer based devices in space avionics systems will be presented and discussed in light of current polymer materials.

Watson, Michael D.↗
NASA NTRS2011

Evolution of the Space Shuttle Primary Avionics Software and Avionics for Shuttle Derived Launch Vehicles

As a result of recommendation from the Augustine Panel, the direction for Human Space Flight has been altered from the original plan referred to as Constellation. NASA s Human Exploration Framework Team (HEFT) proposes the use of a Shuttle Derived Heavy Lift Launch Vehicle (SDLV) and an Orion derived spacecraft (salvaged from Constellation) to support a new flexible direction for space exploration. The SDLV must be developed within an environment of a constrained budget and a preferred fast development schedule. Thus, it has been proposed to utilize existing assets from the Shuttle Program to speed development at a lower cost. These existing assets should not only include structures such as external tanks or solid rockets, but also the Flight Software which has traditionally been a "long pole" in new development efforts. The avionics and software for the Space Shuttle was primarily developed in the 70 s and considered state of the art for that time. As one may argue that the existing avionics and flight software may be too outdated to support the new SDLV effort, this is a fallacy if they can be evolved over time into a "modern avionics" platform. The technology may be outdated, but the avionics concepts and flight software algorithms are not. The reuse of existing avionics and software also allows for the reuse of development, verification, and operations facilities. The keyword is evolve in that these assets can support the fast development of such a vehicle, but then be gradually evolved over time towards more modern platforms as budget and schedule permits. The "gold" of the flight software is the "control loop" algorithms of the vehicle. This is the Guidance, Navigation, and Control (GNC) software algorithms. This software is typically the most expensive to develop, test, and verify. Thus, the approach is to preserve the GNC flight software, while first evolving the supporting software (such as Command and Data Handling, Caution and Warning, Telemetry, etc.). This can be accomplished by gradually removing the "support software" from the legacy flight software leaving only the GNC algorithms. The "support software" could be re-developed for modern platforms, while leaving the GNC algorithms to execute on technology compatible with the legacy system. It is also possible to package the GNC algorithms into an emulated version of the original computer (via Field Programmable Gate Arrays or FPGAs), thus becoming a "GNC on a Chip" solution where it could live forever to be embedded in modern avionics platforms.

Ferguson, Roscoe C.↗
NASA NTRS2011

NEXUS Scalable and Distributed Next-Generation Avionics Bus for Space Missions

A paper discusses NEXUS, a common, next-generation avionics interconnect that is transparently compatible with wired, fiber-optic, and RF physical layers; provides a flexible, scalable, packet switched topology; is fault-tolerant with sub-microsecond detection/recovery latency; has scalable bandwidth from 1 Kbps to 10 Gbps; has guaranteed real-time determinism with sub-microsecond latency/jitter; has built-in testability; features low power consumption (< 100 mW per Gbps); is lightweight with about a 5,000-logic-gate footprint; and is implemented in a small Bus Interface Unit (BIU) with reconfigurable back-end providing interface to legacy subsystems. NEXUS enhances a commercial interconnect standard, Serial RapidIO, to meet avionics interconnect requirements without breaking the standard. This unified interconnect technology can be used to meet performance, power, size, and reliability requirements of all ranges of equipment, sensors, and actuators at chip-to-chip, board-to-board, or box-to-box boundary. Early results from in-house modeling activity of Serial RapidIO using VisualSim indicate that the use of a switched, high-performance avionics network will provide a quantum leap in spacecraft onboard science and autonomy capability for science and exploration missions.

He, Yutao↗
NASA NTRS1999

System Engineering Issues for Avionics Survival in the Space Environment

This paper examines how the system engineering process influences the design of a spacecraft's avionics by considering the space environment. Avionics are susceptible to the thermal, radiation, plasma, and meteoroids/orbital debris environments. The environment definitions for various spacecraft mission orbits (LEO/low inclination, LEO/Polar, MEO, HEO, GTO, GEO and High ApogeeElliptical) are discussed. NASA models and commercial software used for environment analysis are reviewed. Applicability of technical references, such as NASA TM-4527 "Natural Orbital Environment Guidelines for Use in Aerospace Vehicle Development" is discussed. System engineering references, such as the MSFC System Engineering Handbook, are reviewed to determine how the environments are accounted for in the system engineering process. Tools and databases to assist the system engineer and avionics designer in addressing space environment effects on avionics are described and usefulness assessed.

Pavelitz, Steven↗
NASA NTRS2024

Failure-Tolerant Avionics for Crewed Space Systems Recommended Best Practices

This paper provides an overview of some of the major steps needed to mature and justify the design of an avionics system for crewed spacecraft. It is organized as a collection of artifacts or pieces of evidence that NASA needs to assess the system at design reviews, including a functional failure modes and effects analysis (FFMEA), fault containment region (FCR) definitions, the failure hypothesis, and reliability analysis. This paper is intended as a reference for designers working on NASA crewed spaceflight projects, reliability engineers responsible for avionics system assessments, and program managers wanting to understand what evidence is required at design reviews to ensure crew safety and mission success.

Avionics↗
NASA NTRS2018

The International Space Station Space Radiation Environment: Avionics Systems Performance in Low-Earth Orbit Single Event Effects (SEE) Environments

Single event effects (SEE) are those errors, anomalies, or failures in microelectronic devices caused by the passage of a single energetic charged particle through the device. Spacecraft SEE environments consist primarily of energetic charged particles; both primary particles originating in the natural environment and secondary particles (including secondary neutrons) produced by nuclear reactions of primary particles with spacecraft materials. The energetic charged particle components (electrons, protons, and atomic nuclei) of the spacecraft SEE environment include galactic cosmic rays (GCR), and planetary radiation belt charged particles, as well as solar energetic particle event (SPE) charged particles. The International Space Station (ISS) orbital altitude and inclination (~350 km to ~420 km at 51.6o inclination) results in a spacecraft SEE environment that varies dramatically with the location in Earth?s geomagnetic field. Geomagnetic GCR shielding diminishes with distance from the geomagnetic equator. Near + 51.6o latitude the ISS GCR environment has a high degree of similarity to the interplanetary GCR environment in cis-Lunar space.SEE environments supporting ISS avionics systems design, development, test, and verification are documented in SSP-30512, Space Station Ionizing Radiation Design Environment. Comparisons of overall ISS avionics systems in-flight performance with pre-flight verification report predictions have been previously reported and meet or exceed expectations in all cases.In this paper we report the results of more detailed investigations of the effects of geographic location, altitude, solar cycle, and shielding mass effects on the in-flight SEE performance of the ISS command and data handling system during the past 17 years. In addition, we report on the preflight testing and in-flight performance of the commercial-off-the-shelf lap top computers used on ISS. Finally, we present an assessment of ISS as an avionics SEE test and flight demonstration platform for exploration hardware destined for the cis-lunar or other inner solar system environments.

International Space Station↗
NASA NTRSDate not supplied

MUSTANG: A Workhorse for NASA Spaceflight Avionics

The Modular Unified Space Technology Avionics for Next Generation (MUSTANG) is a small integrated Avionics system including Command and Data Handling (C&DH), Power System Electronics (PSE), Attitude Control System Interfaces (ACS), and Propulsion Electronics. The MUSTANG Avionics Architecture is built upon many years of knowledge capture and lessons learned at the Goddard Space Flight Center. With a motivation towards modularity and keeping board redesign costs to a minimum, MUSTANG offers flexibility in features with a backplane-less design and allows the user to choose the options (cards) needed for their system. It incorporates a distributed power system that provides secondary power to all its subcomponents reducing the number of primary services needed for an Avionics. MUSTANG can be integrated into one system or divided into several smaller components. MUSTANG supports redundancy and cross-strap ability for a more robust and reliable Avionics system. A variation of MUSTANG exists for Instrument Electronics called iMUSTANG and allows the user to select functionality applicable to the instrument electronics. MUSTANG is not meant to replace Avionics for all spacecraft. There are limitations due to its relatively compact size, but the MUSTANG design has proven broadly applicable on many spacecraft and instrument bus avionics architectures.

MUSTANG↗
NASA NTRSDate not supplied

Alternating Between Software Models and Real Hardware in the System Integration Lab for theIncremental Development of the Space Launch System Program Avionics

The MSFC System Integration Lab (SIL) supports avionics development of NASA’s Space Launch System—a new U.S. heavy-lift launch vehicle for NASA’s next generation of human space exploration beyond low-Earth orbit. The SIL facility allows for the incremental development of system components by either hosting real hardware in the loop and/or software models of those components. Through this functionality test teams are able to evaluate overall system performance as components are designed, built and modified. Early hardware/software integration and testing reduces risks and saves overall cost and schedule throughout a program/project life cycle. By performing early hardware/software integration, potential architecture and interface-related problems can be identified, and thus reduce associated risk as early in the design cycle as possible when problems are the least expensive to resolve while also improving the design and requirements. This presentation will illustrate the power of employing a hardware in the loop simulation system for the development of novel spacecraft avionics.

Space Launch System↗