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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS1981

A new method for hardware/software integration of strategic systems Case study for the Space Shuttle

A new method for ground testing a complex avionics system in an integrated manner has been developed. A case study for the Space Shuttle, on which the concept has been successfully implemented, is described here. This approach utilizes the actual hardware and software of the vehicle to perform a realistic simulation of its mission, verifying in the process all the critical interfaces and interactions of the software with the hardware. The advantages over current testing techniques are discussed, as well as the extension of the concept to other strategic systems.

Ionescu, T. V.↗
NASA NTRS1990

Advanced avionics concepts: Autonomous spacecraft control

A large increase in space operations activities is expected because of Space Station Freedom (SSF) and long range Lunar base missions and Mars exploration. Space operations will also increase as a result of space commercialization (especially the increase in satellite networks). It is anticipated that the level of satellite servicing operations will grow tenfold from the current level within the next 20 years. This growth can be sustained only if the cost effectiveness of space operations is improved. Cost effectiveness is operational efficiency with proper effectiveness. A concept is presented of advanced avionics, autonomous spacecraft control, that will enable the desired growth, as well as maintain the cost effectiveness (operational efficiency) in satellite servicing operations. The concept of advanced avionics that allows autonomous spacecraft control is described along with a brief description of each component. Some of the benefits of autonomous operations are also described. A technology utilization breakdown is provided in terms of applications.

Source record↗
NASA NTRS2000

The Deep Space 4/Champollion Comet Rendezvous and Lander Technology Demonstration Mission

The Deep Space 4/Champollion mission is designed to test and validate technologies for landing on and anchoring to small bodies, and sample collection and transfer, in preparation for future sample return missions from comets, asteroids, and satellites. in addition, DS-4 will test technologies for advanced, multi-engine solar electric propulsion (SEP) systems, inflatable-rigidizable solar arrays, autonomous navigation and precision guidance for landing, autonomous hazard detection and avoidance, and advanced integrated avionics and packaging concepts. Deep Space-4/Champollion consists of two spacecraft: an orbiter/carrier vehicle which includes the multi-engine SEP stage, and a lander, called Champollion, which will descend to the surface of the 46P/Tempel 1 cometary nucleus. The spacecraft will launch in April, 2003 and land on the comet in September, 2006 Deep Space 4/Champollion is a joint project between NASA and CNES, the French space agency.

Smythe, William D.↗
NASA NTRS2017

Flight Test Evaluation of the ATD-1 Interval Management Application

Interval Management (IM) is a concept designed to be used by air traffic controllers and flight crews to more efficiently and precisely manage inter-aircraft spacing. Both government and industry have been working together to develop the IM concept and standards for both ground automation and supporting avionics. NASA contracted with Boeing, Honeywell, and United Airlines to build and flight test an avionics prototype based on NASA's spacing algorithm and conduct a flight test. The flight test investigated four different types of IM operations over the course of nineteen days, and included en route, arrival, and final approach phases of flight. This paper examines the spacing accuracy achieved during the flight test and the rate of speed commands provided to the flight crew. Many of the time-based IM operations met or exceeded the operational design goals set out in the standards for the maintain operations and a subset of the achieve operations. Those operations which did not meet the goals were due to issues that are identified and will be further analyzed.

Swieringa, Kurt A.↗
NASA NTRS2010

Ares I-X: First Step in a New Era of Exploration

Since 2005, NASA's Constellation Program has been designing, building, and testing the next generation of launch and space vehicles to carry humans beyond low-Earth orbit (LEO). On October 28, 2009, the Ares Projects successfully launched the first suborbital development flight test of the Ares I crew launch vehicle, Ares I-X, from Kennedy Space Center (KSC). Although the final Constellation Program architecture is under review, data and lessons obtained from Ares I-X can be applied to any launch vehicle. This presentation will discuss the mission background and future impacts of the flight. Ares I is designed to carry up to four astronauts to the International Space Station (ISS). It also can be used with the Ares V cargo launch vehicle for a variety of missions beyond LEO. The Ares I-X development flight test was conceived in 2006 to acquire early engineering, operations, and environment data during liftoff, ascent, and first stage recovery. Engineers are using the test flight data to improve the Ares I design before its critical design review the final review before manufacturing of the flight vehicle begins. The Ares I-X flight test vehicle incorporated a mix of flight and mockup hardware, reflecting a similar length and mass to the operational vehicle. It was powered by a four-segment SRB from the Space Shuttle inventory, and was modified to include a fifth, spacer segment that made the booster approximately the same size as the five-segment SRB. The Ares I-X flight closely approximated flight conditions the Ares I will experience through Mach 4.5, performing a first stage separation at an altitude of 125,000 feet and reaching a maximum dynamic pressure ("Max Q") of approximately 850 pounds per square foot. The Ares I-X Mission Management Office (MMO) was organized functionally to address all the major test elements, including: first stage, avionics, and roll control (Marshall Space Flight Center); upper stage simulator (Glenn Research Center); crew module/launch abort system simulator (Langley Research Center); and ground systems and operations (KSC). Interfaces between vehicle elements and vehicle-ground elements, as well as environment analyses were performed by a systems engineering and integration team at Langley. Experience and lessons learned from these integrated product teams area are already being integrated into the Ares Projects to support the next generation of exploration launch vehicles.

Davis, Stephan R.↗
NASA NTRS2006

Time Triggered Protocol (TTP) for Integration Modular Avionics (IMA)

This viewgraph presentation is a review of the Time Triggered Protocol, designed to work with NASA's Integrated Safety-Critical Advanced Avionics Communication and Control (ISAACC) system. ISAACC is the product of the Propulsion High-Impact Avionics Technologies (PHIAT) project at NASA Marshall Space Flight Center (MSFC) during FY03 to the end of FY05. The goal is an avionics architecture suitable for control and monitoring of safety critical systems of manned spacecraft. It must be scalable to allow its use in robotic vehicles or launch pad and propulsion test stand monitoring and control systems. The developed IMA should have: a common power supply and rugged chassis for a set of modules, many upgradeable software functions on one module (i.e. processing unit Reduced weight, straightforward update and system integration. It is also important that it have Partitioning and a Memory Management Unit (MMU)

Gwaltney, David A.↗
NASA NTRS2000

The Design of a Fault-Tolerant COTS-Based Bus Architecture for Space Applications

The high-performance, scalability and miniaturization requirements together with the power, mass and cost constraints mandate the use of commercial-off-the-shelf (COTS) components and standards in the X2000 avionics system architecture for deep-space missions. In this paper, we report our experiences and findings on the design of an IEEE 1394 compliant fault-tolerant COTS-based bus architecture. While the COTS standard IEEE 1394 adequately supports power management, high performance and scalability, its topological criteria impose restrictions on fault tolerance realization. To circumvent the difficulties, we derive a "stack-tree" topology that not only complies with the IEEE 1394 standard but also facilitates fault tolerance realization in a spaceborne system with limited dedicated resource redundancies. Moreover, by exploiting pertinent standard features of the 1394 interface which are not purposely designed for fault tolerance, we devise a comprehensive set of fault detection mechanisms to support the fault-tolerant bus architecture.

Chau, Savio N.↗
NASA NTRS1976

Space shuttle engineering and operations support. Orbiter to spacelab electrical power interface. Avionics system engineering

The results are presented of an investigation of the factors which affect the determination of Spacelab (S/L) minimum interface main dc voltage and available power from the orbiter. The dedicated fuel cell mode of powering the S/L is examined along with the minimum S/L interface voltage and available power using the predicted fuel cell power plant performance curves. The values obtained are slightly lower than current estimates and represent a more marginal operating condition than previously estimated.

Emmons, T. E.↗
NASA NTRS1998

NASA Center for Integrated Space Microsystems

Develop and maintain a world class, leading edge capability in Advanced Avionic Systems and Advanced Microelectronics Technologies for future highly integrated, miniaturized, autonomous spacecraft systems for deep-space and Earth orbiting missions.

CISM Avionics Microelectronics Miniaturization Aut↗
NASA NTRS2016

System Performance of an Integrated Airborne Spacing Algorithm with Ground Automation

The National Aeronautics and Space Administration's (NASA's) first Air Traffic Management (ATM) Technology Demonstration (ATD-1) was created to facilitate the transition of mature ATM technologies from the laboratory to operational use. The technologies selected for demonstration are the Traffic Management Advisor with Terminal Metering (TMA-TM), which provides precise time-based scheduling in the Terminal airspace; Controller Managed Spacing (CMS), which provides controllers with decision support tools to enable precise schedule conformance; and Interval Management (IM), which consists of flight deck automation that enables aircraft to achieve or maintain precise spacing behind another aircraft. Recent simulations and IM algorithm development at NASA have focused on trajectory-based IM operations where aircraft equipped with IM avionics are expected to achieve a spacing goal, assigned by air traffic controllers, at the final approach fix. The recently published IM Minimum Operational Performance Standards describe five types of IM operations. This paper discusses the results and conclusions of a human-in-the-loop simulation that investigated three of those IM operations. The results presented in this paper focus on system performance and integration metrics. Overall, the IM operations conducted in this simulation integrated well with ground-based decisions support tools and certain types of IM operational were able to provide improved spacing precision at the final approach fix; however, some issues were identified that should be addressed prior to implementing IM procedures into real-world operations.

Swieringa, Kurt A.↗
NASA NTRS2009

Avionics System Architecture for the NASA Orion Vehicle

It has been 30 years since the National Aeronautics and Space Administration (NASA) last developed a crewed spacecraft capable of launch, on-orbit operations, and landing. During that time, aerospace avionics technologies have greatly advanced in capability, and these technologies have enabled integrated avionics architectures for aerospace applications. The inception of NASA s Orion Crew Exploration Vehicle (CEV) spacecraft offers the opportunity to leverage the latest integrated avionics technologies into crewed space vehicle architecture. The outstanding question is to what extent to implement these advances in avionics while still meeting the unique crewed spaceflight requirements for safety, reliability and maintainability. Historically, aircraft and spacecraft have very similar avionics requirements. Both aircraft and spacecraft must have high reliability. They also must have as much computing power as possible and provide low latency between user control and effecter response while minimizing weight, volume, and power. However, there are several key differences between aircraft and spacecraft avionics. Typically, the overall spacecraft operational time is much shorter than aircraft operation time, but the typical mission time (and hence, the time between preventive maintenance) is longer for a spacecraft than an aircraft. Also, the radiation environment is typically more severe for spacecraft than aircraft. A "loss of mission" scenario (i.e. - the mission is not a success, but there are no casualties) arguably has a greater impact on a multi-million dollar spaceflight mission than a typical commercial flight. Such differences need to be weighted when determining if an aircraft-like integrated modular avionics (IMA) system is suitable for a crewed spacecraft. This paper will explore the preliminary design process of the Orion vehicle avionics system by first identifying the Orion driving requirements and the difference between Orion requirements and those of other previous crewed spacecraft avionics systems. Common systems engineering methods will be used to evaluate the value propositions, or the factors that weight most heavily in design consideration, of Orion and other aerospace systems. Then, the current Orion avionics architecture will be presented and evaluated.

Baggerman, Clint↗
NASA NTRS1993

Spacelab J air filter debris analysis

Filter debris from the Spacelab module SLJ of STS-49 was analyzed for microbial contamination. Debris for cabin and avionics filters was collected by Kennedy Space Center personnel on 1 Oct. 1992, approximately 5 days postflight. The concentration of microorganisms found was similar to previous Spacelab missions averaging 7.4E+4 CFU/mL for avionics filter debris and 4.5E+6 CFU/mL for the cabin filter debris. A similar diversity of bacterial types was found in the two filters. Of the 13 different bacterial types identified from the cabin and avionics samples, 6 were common to both filters. The overall analysis of these samples as compared to those of previous missions shows no significant differences.

Obenhuber, Donald C.↗
NASA NTRS2014

Investigation of HZETRN 2010 as a Tool for Single Event Effect Qualification of Avionics Systems

NASA's future missions are focused on long-duration deep space missions for human exploration which offers no options for a quick emergency return to Earth. The combination of long mission duration with no quick emergency return option leads to unprecedented spacecraft system safety and reliability requirements. It is important that spacecraft avionics systems for human deep space missions are not susceptible to Single Event Effect (SEE) failures caused by space radiation (primarily the continuous galactic cosmic ray background and the occasional solar particle event) interactions with electronic components and systems. SEE effects are typically managed during the design, development, and test (DD&T) phase of spacecraft development by using heritage hardware (if possible) and through extensive component level testing, followed by system level failure analysis tasks that are both time consuming and costly. The ultimate product of the SEE DD&T program is a prediction of spacecraft avionics reliability in the flight environment produced using various nuclear reaction and transport codes in combination with the component and subsystem level radiation test data. Previous work by Koontz, et al.1 utilized FLUKA, a Monte Carlo nuclear reaction and transport code, to calculate SEE and single event upset (SEU) rates. This code was then validated against in-flight data for a variety of spacecraft and space flight environments. However, FLUKA has a long run-time (on the order of days). CREME962, an easy to use deterministic code offering short run times, was also compared with FLUKA predictions and in-flight data. CREME96, though fast and easy to use, has not been updated in several years and underestimates secondary particle shower effects in spacecraft structural shielding mass. Thus, this paper will investigate the use of HZETRN 20103, a fast and easy to use deterministic transport code, similar to CREME96, that was developed at NASA Langley Research Center primarily for flight crew ionizing radiation dose assessments. HZETRN 2010 includes updates to address secondary particle shower effects more accurately, and might be used as another tool to verify spacecraft avionics system reliability in space flight SEE environments.

Rojdev, Kristina↗
NASA NTRS2003

Color and Luminance Analysis of the Space Shuttle Multifunction Display Units(MDUs)

The purpose of this evaluation is to measure and analyze the colors that can be shown on the Multifunction Display Units (MDUs) of the Space Shuttle cockpit. The evaluation was conducted in the JSC Avionics Engineering Laboratory (JAEL) in building 16A at NASA Johnson Space Center. The JAEL contains a suite of 11 MDUs, each of which can be configured to show colors based on input values of the MDU red, green and blue (RGB) channels. Each of the channels has a range of 0 to 15. For example, bright green is produced by setting RGB to 0,15,0, and orange is produced by setting RGB to 15,4,0. The Cockpit Avionics Upgrade (CAU) program has specified the RGB settings for 14 different colors in the Display Design document (Rev A, 29 June 2001). The analysis in this report may help the CAU program determine better RGB settings for the colors.

McCandless, Jeffrey W.↗
NASA NTRS2016

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Bolton, Albanie T.↗
NASA NTRS1976

Annual report to the NASA Administrator by the Aerospace Safety Advisory Panel on the space shuttle program. Part 2: Summary of information developed in the panel's fact-finding activities

Safety management areas of concern include the space shuttle main engine, shuttle avionics, orbiter thermal protection system, the external tank program, and the solid rocket booster program. The ground test program and ground support equipment system were reviewed. Systems integration and technical 'conscience' were of major priorities for the investigating teams.

Source record↗
NASA NTRS1985

Space shuttle main engine hardware simulation

The Huntsville Simulation Laboratory (HSL) provides a simulation facility to test and verify the space shuttle main engine (SSME) avionics and software system using a maximum complement of flight type hardware. The HSL permits evaluations and analyses of the SSME avionics hardware, software, control system, and mathematical models. The laboratory has performed a wide spectrum of tests and verified operational procedures to ensure system component compatibility under all operating conditions. It is a test bed for integration of hardware/software/hydraulics. The HSL is and has been an invaluable tool in the design and development of the SSME.

Vick, H. G.↗