Search NASA⌕ Search

SEARCH · Search NASA

Results for “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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS1998

Design of a Low Cost Avionics System for Launch Vehicles

Marshall Space Flight Center has long been one of the leaders in development of propulsion systems. Due to current launch vehicle costs, Marshall Space Flight Centers (MSFC) Advanced Space Transportation Program (ASTP) office has emphasized the development of low cost launch vehicles. The Bantam launch vehicle is one of the primary programs that has low cost as a requirement. One of the driving factors for a low cost launch vehicle is a low cost avionics system. This paper will summarize MSFC's Astrionics Laboratories efforts in designing a low cost avionics system. MSFC has done Phase A avionics system design and has been working with various contractors on a Phase B preliminary avionics design. Deriving the major requirements, trade studies and cost drivers are some of the topics to be discussed.

Crawford, Kevin↗
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 NTRS2000

On-Board Fiber-Optic Network Architectures for Radar and Avionics Signal Distribution

Continued progress in both civil and military avionics applications is overstressing the capabilities of existing radio-frequency (RF) communication networks based on coaxial cables on board modem aircrafts. Future avionics systems will require high-bandwidth on- board communication links that are lightweight, immune to electromagnetic interference, and highly reliable. Fiber optic communication technology can meet all these challenges in a cost-effective manner. Recently, digital fiber-optic communication systems, where a fiber-optic network acts like a local area network (LAN) for digital data communications, have become a topic of extensive research and development. Although a fiber-optic system can be designed to transport radio-frequency (RF) signals, the digital fiber-optic systems under development today are not capable of transporting microwave and millimeter-wave RF signals used in radar and avionics systems on board an aircraft. Recent advances in fiber optic technology, especially wavelength division multiplexing (WDM), has opened a number of possibilities for designing on-board fiber optic networks, including all-optical networks for radar and avionics RF signal distribution. In this paper, we investigate a number of different novel approaches for fiber-optic transmission of on-board VHF and UHF RF signals using commercial off-the-shelf (COTS) components. The relative merits and demerits of each architecture are discussed, and the suitability of each architecture for particular applications is pointed out. All-optical approaches show better performance than other traditional approaches in terms of signal-to-noise ratio, power consumption, and weight requirements.

Alam, Mohammad F.↗
NASA NTRS2008

Simulating Avionics Upgrades to the Space Shuttles

Cockpit Avionics Prototyping Environment (CAPE) is a computer program that simulates the functions of proposed upgraded avionics for a space shuttle. In CAPE, pre-existing space-shuttle-simulation programs are merged with a commercial-off-the-shelf (COTS) display-development program, yielding a package of software that enables high-fi46 NASA Tech Briefs, September 2008 delity simulation while making it possible to rapidly change avionic displays and the underlying model algorithms. The pre-existing simulation programs are Shuttle Engineering Simulation, Shuttle Engineering Simulation II, Interactive Control and Docking Simulation, and Shuttle Mission Simulator playback. The COTS program Virtual Application Prototyping System (VAPS) not only enables the development of displays but also makes it possible to move data about, capture and process events, and connect to a simulation. VAPS also enables the user to write code in the C or C++ programming language and compile that code into the end-product simulation software. As many as ten different avionic-upgrade ideas can be incorporated in a single compilation and, thus, tested in a single simulation run. CAPE can be run in conjunction with any or all of four simulations, each representing a different phase of a space-shuttle flight.

Deger, Daniel↗
NASA NTRS2009

Crew Exploration Vehicle (CEV) Avionics Integration Laboratory (CAIL) Independent Analysis

Two approaches were compared to the Crew Exploration Vehicle (CEV) Avionics Integration Laboratory (CAIL) approach: the Flat-Sat and Shuttle Avionics Integration Laboratory (SAIL). The Flat-Sat and CAIL/SAIL approaches are two different tools designed to mitigate different risks. Flat-Sat approach is designed to develop a mission concept into a flight avionics system and associated ground controller. The SAIL approach is designed to aid in the flight readiness verification of the flight avionics system. The approaches are complimentary in addressing both the system development risks and mission verification risks. The following NESC team findings were identified: The CAIL assumption is that the flight subsystems will be matured for the system level verification; The Flat-Sat and SAIL approaches are two different tools designed to mitigate different risks. The following NESC team recommendation was provided: Define, document, and manage a detailed interface between the design and development (EDL and other integration labs) to the verification laboratory (CAIL).

Davis, Mitchell L.↗
NASA NTRS2009

Ares I Avionics Introduction

The Ares I is the next generation human-rated launcher for the United States Constellation program. This system is required to provide single fault tolerance within defined crew safety and mission reliability limits. As part of the effort to achieve those safety goals, Ares I includes an avionics subsystem built as a multistring, voting architecture. The avionics design draws upon experience gained from building fly-by-wire systems for Shuttle, X- 38, and Seawolf. Architectural drivers for the avionics design include using proven technologies with existing suppliers of space rated parts for critical functions (to reduce overall development risk), easing the software development effort by using an off-theshelf, DO-178B certifiable, ARINC-653 operating system in the main flight computers, minimizing mutual data and power connections that might lead to a common-mode hardware failure of the redundant avionics strings, and centralizing overall Ares I command & control within the Upper Stage.

Marchant, Christopher C.↗
NASA NTRS2010

Advanced Avionics and Processor Systems for a Flexible Space Exploration Architecture

The Advanced Avionics and Processor Systems (AAPS) project, formerly known as the Radiation Hardened Electronics for Space Environments (RHESE) project, endeavors to develop advanced avionic and processor technologies anticipated to be used by NASA s currently evolving space exploration architectures. The AAPS project is a part of the Exploration Technology Development Program, which funds an entire suite of technologies that are aimed at enabling NASA s ability to explore beyond low earth orbit. NASA s Marshall Space Flight Center (MSFC) manages the AAPS project. AAPS uses a broad-scoped approach to developing avionic and processor systems. Investment areas include advanced electronic designs and technologies capable of providing environmental hardness, reconfigurable computing techniques, software tools for radiation effects assessment, and radiation environment modeling tools. Near-term emphasis within the multiple AAPS tasks focuses on developing prototype components using semiconductor processes and materials (such as Silicon-Germanium (SiGe)) to enhance a device s tolerance to radiation events and low temperature environments. As the SiGe technology will culminate in a delivered prototype this fiscal year, the project emphasis shifts its focus to developing low-power, high efficiency total processor hardening techniques. In addition to processor development, the project endeavors to demonstrate techniques applicable to reconfigurable computing and partially reconfigurable Field Programmable Gate Arrays (FPGAs). This capability enables avionic architectures the ability to develop FPGA-based, radiation tolerant processor boards that can serve in multiple physical locations throughout the spacecraft and perform multiple functions during the course of the mission. The individual tasks that comprise AAPS are diverse, yet united in the common endeavor to develop electronics capable of operating within the harsh environment of space. Specifically, the AAPS tasks for the Federal fiscal year of 2010 are: Silicon-Germanium (SiGe) Integrated Electronics for Extreme Environments, Modeling of Radiation Effects on Electronics, Radiation Hardened High Performance Processors (HPP), and and Reconfigurable Computing.

Keys, Andrew S.↗
NASA NTRS2010

Reference Avionics Architecture for Lunar Surface Systems

Developing and delivering infrastructure capable of supporting long-term manned operations to the lunar surface has been a primary objective of the Constellation Program in the Exploration Systems Mission Directorate. Several concepts have been developed related to development and deployment lunar exploration vehicles and assets that provide critical functionality such as transportation, habitation, and communication, to name a few. Together, these systems perform complex safety-critical functions, largely dependent on avionics for control and behavior of system functions. These functions are implemented using interchangeable, modular avionics designed for lunar transit and lunar surface deployment. Systems are optimized towards reuse and commonality of form and interface and can be configured via software or component integration for special purpose applications. There are two core concepts in the reference avionics architecture described in this report. The first concept uses distributed, smart systems to manage complexity, simplify integration, and facilitate commonality. The second core concept is to employ extensive commonality between elements and subsystems. These two concepts are used in the context of developing reference designs for many lunar surface exploration vehicles and elements. These concepts are repeated constantly as architectural patterns in a conceptual architectural framework. This report describes the use of these architectural patterns in a reference avionics architecture for Lunar surface systems elements.

Somervill, Kevin M.↗
NASA NTRS2006

Multi-Platform Avionics Simulator

Multi-Platform Avionics Simulator (MPAvSim) is a software library for development of simulations of avionic hardware. MPAvSim facilitates simulation of interactions between flight software and such avionic peripheral equipment as telecommunication devices, thrusters, pyrotechnic devices, motor controllers, and scientific instruments. MPAvSim focuses on the behavior of avionics as seen by flight software, rather than on performing high-fidelity simulations of dynamics. However, MPAvSim is easily integrable with other programs that do perform such simulations. MPAvSim makes it possible to do real-time partial hardware- in-the-loop simulations. An MPAvSim simulation consists of execution chains (see figure) represented by flow graphs of models, defined here as stateless procedures that do some work. During a simulation, MPAvSim walks the execution chain, running each model in turn. Using MPAvSim, flight software can be run against a spacecraft that is all simulation, all hardware, or part hardware and part simulation. With respect to a specific piece of hardware, either the hardware itself or its simulation can be plugged in without affecting the rest of the system. Thus, flight software can be tested before hardware is available, and as items of hardware become available, they can be substituted for their simulations, with minimal disruption.

Clark, Micah↗
NASA NTRS2003

Developing Generic Software for Spacecraft Avionics

A proposed approach to the development of software for spacecraft avionics is based partly on a concept of generic software that could be tailored to satisfy requirements for specific missions. The proposed approach would stand in contrast to the conventional approach of first defining avionics requirements for a specific mission, then developing software specific to those requirements. The proposed approach might also be adaptable to programming computers that control and monitor other complex equipment systems that range in scale from automobiles to factories. The concept of a spacecraft avionics functional model (SAFM) is a major element of the proposed approach. An SAFM would be, essentially, a systematic and hierarchical description of the functionality required of the avionics software (and hardware) for a given mission. Although the initial input information used to start the construction of an SAFM would typically amount to a high-level description, the SAFM would thereafter be decomposed to a low level. The resulting low-level version of the model would be used to develop a set of generic requirements that could be expected to include a large fraction of all requirements for a large fraction of all missions. The generic requirements would be used to develop software modules that could be included in, or excluded from, the final flight software to satisfy the requirements of a specific mission.

Smith, Joseph↗
NASA NTRS2012

Orion MPCV Service Module Avionics Ring Pallet Testing, Correlation, and Analysis

The NASA Orion Multi-Purpose Crew Vehicle (MPCV) is being designed to replace the Space Shuttle as the main manned spacecraft for the agency. Based on the predicted environments in the Service Module avionics ring, an isolation system was deemed necessary to protect the avionics packages carried by the spacecraft. Impact, sinusoidal, and random vibration testing were conducted on a prototype Orion Service Module avionics pallet in March 2010 at the NASA Glenn Research Center Structural Dynamics Laboratory (SDL). The pallet design utilized wire rope isolators to reduce the vibration levels seen by the avionics packages. The current pallet design utilizes the same wire rope isolators (M6-120-10) that were tested in March 2010. In an effort to save cost and schedule, the Finite Element Models of the prototype pallet tested in March 2010 were correlated. Frequency Response Function (FRF) comparisons, mode shape and frequency were all part of the correlation process. The non-linear behavior and the modeling the wire rope isolators proved to be the most difficult part of the correlation process. The correlated models of the wire rope isolators were taken from the prototype design and integrated into the current design for future frequency response analysis and component environment specification.

Staab, Lucas↗
NASA NTRS2013

Estimation of Airline Benefits from Avionics Upgrade under Preferential Merge Re-sequence Scheduling

Modernization of the airline fleet avionics is essential to fully enable future technologies and procedures for increasing national airspace system capacity. However in the current national airspace system, system-wide benefits gained by avionics upgrade are not fully directed to aircraft/airlines that upgrade, resulting in slow fleet modernization rate. Preferential merge re-sequence scheduling is a best-equipped-best-served concept designed to incentivize avionics upgrade among airlines by allowing aircraft with new avionics (high-equipped) to be re-sequenced ahead of aircraft without the upgrades (low-equipped) at enroute merge waypoints. The goal of this study is to investigate the potential benefits gained or lost by airlines under a high or low-equipped fleet scenario if preferential merge resequence scheduling is implemented.

air traffic management↗
NASA NTRS2017

Flight Crew Survey Responses from the Interval Management (IM) Avionics Phase 2 Flight Test

The Interval Management (IM) Avionics Phase 2 flight test used three aircraft over a nineteen day period to operationally evaluate a prototype IM avionics. Quantitative data were collected on aircraft state data and IM spacing algorithm performance, and qualitative data were collected through end-of-scenario and end-of-day flight crew surveys. The majority of the IM operations met the performance goals established for spacing accuracy at the Achieve-by Point and the Planned Termination Point, however there were operations that did not meet goals for a variety of reasons. While the positive spacing accuracy results demonstrate the prototype IM avionics can contribute to the overall air traffic goal, critical issues were also identified that need to be addressed to enhance IM performance. The first category was those issues that impacted the conduct and results of the flight test, but are not part of the IM concept or procedures. These included the design of arrival and approach procedures was not ideal to support speed as the primary control mechanism, the ground-side of the Air Traffic Management Technology Demonstration (ATD-1) integrated concept of operations was not part of the flight test, and the high workload to manually enter the information required to conduct an IM operation. The second category was issues associated with the IM spacing algorithm or flight crew procedures. These issues include the high frequency of IM speed changes and reversals (accelerations), a mismatch between the deceleration rate used by the spacing algorithm and the actual aircraft performance, and some spacing error calculations were sensitive to normal operational variations in aircraft airspeed or altitude which triggered additional IM speed changes. Once the issues in these two categories are addressed, the future IM avionics should have considerable promise supporting the goals of improving system throughput and aircraft efficiency.

Baxley, Brian T.↗
NASA NTRS2017

Space Technology Game Changing Development: NASA Affordable Vehicle Avionics (AVA)

Common Modular Avionics System for Nanolaunchers Offering Affordable Access to Space Small satellites are becoming ever more capable of performing valuable missions for both government and commercial customers. However, currently these satellites can be launched affordably only as secondary payloads. This makes it difficult for the small satellite mission to launch when needed, to the desired orbit, and with acceptable risk. What is needed is a class of low-cost launchers, so that launch costs to low-Earth orbit (LEO) are commensurate with payload costs. Several private and government-sponsored launch vehicle developers are working toward just that—the ability to affordably insert small payloads into LEO. But until now, cost of the complex avionics remained disproportionately high. AVA solves this problem. Significant contributors to the cost of launching nanosatellites to orbit are the avionics and software systems that steer and control the launch vehicles, sequence stage separation, deploy payloads, and telemeter data. The high costs of these guidance, navigation and control (GNC) avionics systems are due in part to the current practice of developing unique, single use hardware and software for each launch. High-performance, high-reliability inertial sensors components with heritage from legacy launchers also contribute to costs—but can low-cost commercial inertial sensors work just as well?

Aquilina, Rudy↗
NASA NTRS1999

Future Avionics for X2K

The JPL X2000 program is for the delivery of advanced avionics systems, cutting edge technologies, and avionics components to spacecraft/orbiter, micro/nano-spacecraft, and in-situ missions. The objective is to develop and deliver avionics systems that will serve a multitude of future missions over the next 12 to 15 years.

DSST X2000 Micro/Nano Spacecraft Avionics distribu↗
NASA NTRS2018

NASA GSFC Avionics Architectures and Future Directions

NASA Goddard Spaceflight Center (GSFC) employs standard avionics hardware and software architectures. Hardware architectures include GMSA (Goddard Modular Smallsat Architecture), MUSTANG (Modular Unified Space Technology Avionics for Next Generation), SpaceCube. The spaceflight software architecture is based on cFS (Core Flight System). Future driving requirements for avionics architectures include increase sensor data rates, increased onboard processing, autonomous applications, and distributed space missions. Architectural concepts that can meet these requirements include the use of the High Performance Spaceflight Computing (HPSC) Chiplet, employing hybrid computing architectures, and increasing network bandwidths.

architectures↗
NASA NTRS1995

A Multi-Mission Space Avionics Architecture

As the budget for the space industry is dwindling, a reusable avionics architecture applicable across multiple missions is urgently needed to reduce the development and production costs of flight projects. This paper presents a multi-mission avionics architecture which employs interface standards extensively, sot hat avionics systems can be built rapidly by assembling subsystems and instruments in a plug-and-play manner. The key feature of this architecture is a "backbone" standard parallel bus which can accommodate various standard interfaces through a repertoire of I/O modules. Hence, specific ;mission requirements can be met by selecting and integrating the appropriate subsystems and instruments into the system. This architecture can also adopt different "backbone" buses, implement redundant processors, and support distributed processing. An example of the architecture using the MOPS6000 from the Southwest Research Institute is also described. Experiments will be done in the Flight System Testbed (FST) of the Jet Propulsion Laboratory to benchmark the MOPS6000 and to demonstrate its multi-mission capability.

Avionics↗
NASA NTRS1971

Alternate avionics system study and phase B extension

Results of alternate avionics system studies for the space shuttle are presented that reduce the cost of vehicle avionics without incurring major off-setting costs on the ground. A comprehensive summary is provided of all configurations defined since the completion of the basic Phase B contract and a complete description of the optimized avionics baseline is given. In the new baseline, inflight redundancy management is performed onboard without ground support; utilization of off-the-shelf hardware reduces the cost figure substantially less than for the Phase B baseline. The only functional capability sacrificed in the new approach is automatic landing.

Source record↗