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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

An avionics scenario and command model description for Space Generic Open Avionics Architecture (SGOAA)

This paper presents a description of a model for a space vehicle operational scenario and the commands for avionics. This model will be used in developing a dynamic architecture simulation model using the Statemate CASE tool for validation of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA has been proposed as an avionics architecture standard to NASA through its Strategic Avionics Technology Working Group (SATWG) and has been accepted by the Society of Automotive Engineers (SAE) for conversion into an SAE Avionics Standard. This architecture was developed for the Flight Data Systems Division (FDSD) of the NASA Johnson Space Center (JSC) by the Lockheed Engineering and Sciences Company (LESC), Houston, Texas. This SGOAA includes a generic system architecture for the entities in spacecraft avionics, a generic processing external and internal hardware architecture, and a nine class model of interfaces. The SGOAA is both scalable and recursive and can be applied to any hierarchical level of hardware/software processing systems.

Stovall, John R.↗
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 NTRS2015

NASA Affordable Vehicle Avionics (AVA): Common Modular Avionics System for Nano-Launchers 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 only be launched affordably as secondary payloads. This makes it difficult for the small satellite mission to launch when needed, to the desired orbit, and with acceptable risk. NASA Ames Research Center has developed and tested a prototype low-cost avionics package for space launch vehicles that provides complete GNC functionality in a package smaller than a tissue box with a mass less than 0.84 kg. AVA takes advantage of commercially available, low-cost, mass-produced, miniaturized sensors, filtering their more noisy inertial data with realtime GPS data. The goal of the Advanced Vehicle Avionics project is to produce and flight-verify a common suite of avionics and software that deliver affordable, capable GNC and telemetry avionics with application to multiple nano-launch vehicles at 1 the cost of current state-of-the-art avionics.

Guidance Navigation and Control↗
NASA NTRS2001

Micro-Avionics Node for Distributed Avionics System

An avionics system is a platform residing on a flight vehicle that provides the resources (hardware and software) needed to manage the flight mission. Distributing the avionics system components, both functionally and spatially, can provide characteristics that benefit the overall system robustness, reliability, testability, and maintainability. This abstract discusses the concept of a distributed avionics system consisting of a network of micro-avionics nodes. Additional information is contained in the original extended abstract.

Blaes, B. R.↗
NASA NTRS2014

Avionics Architectures for Exploration: Building a Better Approach for (Human) Spaceflight Avionics

The field of Avionics is advancing far more rapidly in terrestrial applications than in space flight applications. Spaceflight Avionics are not keeping pace with expectations set by terrestrial experience, nor are they keeping pace with the need for increasingly complex automation and crew interfaces as we move beyond Low Earth Orbit. NASA must take advantage of the strides being made by both space-related and terrestrial industries to drive our development and sustaining costs down. This paper describes ongoing efforts by the Avionics Architectures for Exploration (AAE) project chartered by NASA's Advanced Exploration Systems (AES) Program to evaluate new avionic architectures and technologies, provide objective comparisons of them, and mature selected technologies for flight and for use by other AES projects. Results from the AAE project's FY13 efforts are discussed, along with the status of FY14 efforts and future plans.

Goforth, Montgomery B.↗
NASA NTRS2006

Micro-Inspector Avionics Module (MAM): A Self-Contained Low Power, Reconfigurable Avionics Platform for Small Spacecrafts and Instruments

This paper describes development of a radiation tolerant, low power, reconfigurable avionics module aimed at meeting the avionics needs of the JPL Micro-Inspector spacecraft. This module represents a complete avionics system, consisting of two PowerPC 405 CPUs embedded within a reconfigurable FPGA fabric of over 8 Million logic gates, 64MB of EDAC protected Flash storage and 128MB of EDAC protected DDR SDRAM or SDRAM memories, along with FPGA SEU mitigation logic, and all necessary power conversion. Processor SEU mitigation is achieved by running the two processors in a lock-step and compare configuration. All of these building blocks are integrated into a double sided circuit board that takes as little as 6 square inches of board space. This module can be embedded into a user system as part of a bigger circuit assembly or as a self contained module. This module is being developed as part of a JPL led Micro-Inspector Program, funded by NASA ESMD aimed at producing a 10Kg micro spacecraft.

configurable↗
NASA NTRS1975

Space Tug avionics definition study. Volume 2: Avionics functional requirements

Flight and ground operational phases of the tug/shuttle system are analyzed to determine the general avionics support functions that are needed during each of the mission phases and sub-phases. Each of these general support functions is then expanded into specific avionics system requirements, which are then allocated to the appropriate avionics subsystems. This process is then repeated at the next lower level of detail where these subsystem requirements are allocated to each of the major components that comprise a subsystem.

Source record↗
NASA NTRS1975

Space tug avionics definition study. Volume 3: Avionics baseline configuration definition

The baseline avionics systems for the space tug is comprised of a central digital computer that integrates the functions of all of the tug's subsystems by means of a redundant digital data bus. The major subsystems of the avionics system are: data management; communications; guidance, navigation, and control; rendezvous and docking; electrical power; and instrumentation. The baseline avionics system for the space tug resulting from system and subsystem trade studies is defined. Tug interfaces with the spacecraft, orbiter and the ground, and the baseline philosophy and configuration for onboard checkout of the tug are included. Baseline configurations, functional and operational features, component details and characteristics, and the supporting software are included in the subsystem descriptions.

Source record↗
NASA NTRS2015

Avionics Configuration Assessment for Flightdeck Interval Management: A Comparison of Avionics and Notification Methods

Flightdeck Interval Management is one of the NextGen operational concepts that FAA is sponsoring to realize requisite National Airspace System (NAS) efficiencies. Interval Management will reduce variability in temporal deviations at a position, and thereby reduce buffers typically applied by controllers - resulting in higher arrival rates, and more efficient operations. Ground software generates a strategic schedule of aircraft pairs. Air Traffic Control (ATC) provides an IM clearance with the IM spacing objective (i.e., the TTF, and at which point to achieve the appropriate spacing from this aircraft) to the IM aircraft. Pilots must dial FIM speeds into the speed window on the Mode Control Panel in a timely manner, and attend to deviations between actual speed and the instantaneous FIM profile speed. Here, the crew is assumed to be operating the aircraft with autothrottles on, with autopilot engaged, and the autoflight system in Vertical Navigation (VNAV) and Lateral Navigation (LNAV); and is responsible for safely flying the aircraft while maintaining situation awareness of their ability to follow FIM speed commands and to achieve the FIM spacing goal. The objective of this study is to examine whether three Notification Methods and four Avionics Conditions affect pilots' performance, ratings on constructs associated with performance (workload, situation awareness), or opinions on acceptability. Three Notification Methods (alternate visual and aural alerts that notified pilots to the onset of a speed target, conformance deviation from the required speed profile, and reminded them if they failed to enter the speed within 10 seconds) were examined. These Notification Methods were: VVV (visuals for all three events), VAV (visuals for all three events, plus an aural for speed conformance deviations), and AAA (visual indications and the same aural to indicate all three of these events). Avionics Conditions were defined by the instrumentation (and location) used to present IM information to crews: (1) Integrated (IM information is embedded in extant PFD (Primary Flight Display), ND (Navigation Display), EICAS (Engine Indicating and Crew Alerting System) displays); (2) EFB_Aft (IM information is only supplied in an EFB and mounted in location similar to that for MITRE's UPS work); (3) EFB_Fore (IM information is only supplied in an EFB which is mounted more forward, under the side window), and (4) EFB_Aft plus use of an AGD (the same IM information is supplied in an EFB and on an AGD, both mounted in locations similar to that in MITRE's UPS work ). Twelve commercial pilot crews flew descent scenarios (VNAV Speed with the mode control panel (MCP) speed window open until flaps extended, then VNAV Path) in a commercial transport flight simulator with realistic visual scene and communications. The results of this study serve three practical aims: (1) contribute to the down-select of avionics configuration for future assessment of the ASTAR spacing algorithm at NASA; (2) provide information useful to the FAA Human Factors Division (ANG-C1)'s mission to identify issues pertinent to flight certification of, and flight standards; (3) identify methodological considerations in support of future FIM human-in-the-loop (HITL) investigations.

Latorella, Kara A.↗
NASA NTRS2004

Advanced mobility avionics : a reconfigurable mirco-avionics platform for the future needs of small planetary rovers and micospacecraft

Future small and micro-missions, such as Mars Scouts and Deep Space probes, require a new look at highly integrated, re-configurable, low power avionics. This paper will present our plans for developing a scalable, configurable, and highly integrated 32-bit embedded platform capable of implementing computationally intensive signal processing and control algorithms in space flight instruments and systems. This platform is designed to service the need of both small and large spacecraft and planetary rovers that will operate within moderate radiation environments. Some of the key characteristics of this platform are its small size, low power, high performance, and flexibility. This estimated 10 fold reduction in both size and power over state-of-the-art processing platforms will enable this new product to act as the core of a low-cost mobility system for a wide range of missions.

reconfigurable↗
NASA NTRS2018

Customer Avionics Interface Development and Analysis (CAIDA): Software Developer for Avionics Systems

The Customer Avionics Interface Development and Analysis (CAIDA) supports the testing of the Launch Control System (LCS), NASA's command and control system for the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and ground support equipment. The objective of the semester-long internship was to support day-to-day operations of CAIDA and help prepare for verification and validation of CAIDA software.

Mitchell, Sherry L.↗
NASA NTRS2019

Implementing CubeSat Avionics Components to Full-Scale Capsule Return Missions

Returning samples from Low Earth Orbit (LEO) is no simple task. Whether the samples are scientific experiments or surveillance footage, engineers must overcome many challenges to achieve mission success. In August of 1960 the first payload recovered from LEO, the Corona capsule, carried “more photographic coverage of the Soviet Union than all previous U-2 missions”. The Corona program proved that re-turning surveillance footage from LEO is possible, the program is still referenced today when designing new sample return missions. Although there are many crucial subsystems that make up a sample return capsule, the avionics subsystem demands the most attention. This paper will discuss how current CubeSat avionics components can be applied to large sample return missions. One advantage of using CubeSat avionics components is that they can fit into a 1.5 U (10x10x15 cm) compartment, leaving more room for the payload. This paper is broken down as follows. First, the reader is introduced to the history of sample return projects. The major design strengths of previous projects are analyzed and applied to the current capsule design. Next, the typical trajectory of a capsule is presented along with mission requirements and operations. During the re-entry phase, the avionics subsystem is responsible for commanding the deployment of the parachute, back shell, and the heat shield. Next, the power subsystem is discussed in detail including a trade study on batteries and voltage regulators. Next, the interface between the Ground Support Equipment (GSE) and the avionics components is discussed. It is important that the capsule is able to provide avionics system state of health to ensure proper functionality before the capsule is launched. Next, an in-depth analysis of current TechEdSat avionics components, with proven flight history, are presented. The various avionics components including the radios, GPS, IMU, temperature sensors, altitude sensors, and ejectors are discussed. The application of cur-rent avionics components to a sample return projects are analyzed. After, the wiring diagram is presented along with a discussion of the design. Next, a summary of how the avionics components are tested and validated is pro-vided. Finally, this article will present current sample return missions TechEdSat avionics components are being applied to. CubeSat Avionics can be applied to almost all sample return missions due to their compact configuration and proven space flight heritage. The TechEdSat team is currently making great progress in returning samples from the International Space Station (ISS) and is excited to present how their avionics components can be applied to a full-scale sample return mission.

Hughes, Z. M.↗
NASA NTRS2022

X-57 Mod II Avionics Power Analysis

The X-57 Mod II Avionics Power Analysis was developed to provide the design requirements for the X-57 Avionics Power System. In the Mod II configuration, the two stock Tecnam P2006T Rotax engines are replaced with two electric motors. A high voltage traction battery (460 VDC nominal) supplies power for the motors. The Mod II avionics power design uses the stock Tecnam avionics power architecture as a baseline. The stock Tecnam power system utilizes three 12 VDC power sources, a battery and two alternators, to provided redundant avionics power. This redundancy was preserved in the X-57 avionics power architecture. A block diagram of the X-57 avionics system can be found in the “Mod II Architecture” worksheet of this documents. Since the X-57 electric motors do not have alternators or generators, two 13.8V DC Converters were added to replace the stock Tecnam alternators. Input power to these DC Converters is provide by the high voltage traction battery. The Tecnam stock lead acid battery was replaced with a Lithium Iron Phosphate (LiFePO4) battery. The Mod II Avionics Power Analysis provided the power requirements for the two 13.8V DC converters and the Lithium Iron Phosphate battery. Power requirement estimates for each subsystem used in this analysis were provided by manufacturer specifications, measured in the laboratory or provided by the subsystem design engineer. Typical power requirements and maximum power requirements were provided for each subsystem. The Mod II Avionics Power Systems consists of seven 13.8 VDC buses, two 28 VDC Buses and two 23 VDC buses. The avionics power requirements for Mod III configuration are the same as Mod II. The Mod III configuration replaces the stock Tecnam wing with a carbon fiber wing that is optimized for cruise conditions. The motors are located on the wingtips. The Mod IV Avionics Power Analysis is a separate analysis and is document number ANLYS-CEPT-032.

Keith Harris↗