Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 1,477 records · Page 82

Thermal Interface Comparisons Under Flight Like Conditions

Thermal interface materials are used in bolted interfaces to promote good thermal conduction between the two. The mounting surface can include panels, heat pipes, electronics boxes, etc.. . On Lunar Reconnaissance Orbiter (LRO) project the results are directly applicable: a) Several high power avionics boxes b) Several interfaces from RWA to radiator through heat pipe network

Rodriquez-Ruiz, Juan↗

Thermal Model Development for Ares I-X

Thermal analysis for the Ares I-X vehicle has involved extensive thermal model integration, since thermal models of vehicle elements came from several different NASA and industry organizations. Many valuable lessons were learned in terms of model integration and validation. Modeling practices such as submodel, analysis group and symbol naming were standardized to facilitate the later model integration. Upfront coordination of coordinate systems, timelines, units, symbols and case scenarios was very helpful in minimizing integration rework. A process for model integration was developed that included pre-integration runs and basic checks of both models, and a step-by-step process to efficiently integrate one model into another. Extensive use of model logic was used to create scenarios and timelines for avionics and air flow activation. Efficient methods of model restart between case scenarios were developed. Standardization of software version and even compiler version between organizations was found to be essential. An automated method for applying aeroheating to the full integrated vehicle model, including submodels developed by other organizations, was developed.

Amundsen, Ruth M.↗

Pilot In-Trail Procedure Validation Simulation Study

A Human-In-The-Loop experiment was conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) to investigate the viability of the In-Trail Procedure (ITP) concept from a flight crew perspective, by placing participating airline pilots in a simulated oceanic flight environment. The test subject pilots used new onboard avionics equipment that provided improved information about nearby traffic and enabled them, when specific criteria were met, to request an ITP flight level change referencing one or two nearby aircraft that might otherwise block the flight level change. The subject pilots subjective assessments of ITP validity and acceptability were measured via questionnaires and discussions, and their objective performance in appropriately selecting, requesting, and performing ITP flight level changes was evaluated for each simulated flight scenario. Objective performance and subjective workload assessment data from the experiment s test conditions were analyzed for statistical and operational significance and are reported in the paper. Based on these results, suggestions are made to further improve the ITP.

Bussink, Frank J. L.↗

Design Study of 8 Meter Monolithic Mirror UV/Optical Space Telescope

The planned Ares V launch vehicle with its 10 meter fairing shroud and 55,000 kg capacity to the Sun Earth L2 point enables entirely new classes of space telescopes. NASA MSFC has conducted a preliminary study that demonstrates the feasibility of launching a 6 to 8 meter class monolithic primary mirror telescope to Sun-Earth L2 using an Ares V. Specific technical areas studied included optical design; structural design/analysis including primary mirror support structure, sun shade and secondary mirror support structure; thermal analysis; launch vehicle performance and trajectory; spacecraft including structure, propulsion, GN&C, avionics, power systems and reaction wheels; operations and servicing; mass and power budgets; and system cost.

Stahl, H. Philip↗

A GPS Receiver for Lunar Missions

Beginning with the launch of the Lunar Reconnaissance Orbiter (LRO) in October of 2008, NASA will once again begin its quest to land humans on the Moon. This effort will require the development of new spacecraft which will safely transport people from the Earth to the Moon and back again, as well as robotic probes tagged with science, re-supply, and communication duties. In addition to the next-generation spacecraft currently under construction, including the Orion capsule, NASA is also investigating and developing cutting edge navigation sensors which will allow for autonomous state estimation in low Earth orbit (LEO) and cislunar space. Such instruments could provide an extra layer of redundancy in avionics systems and reduce the reliance on support and on the Deep Space Network (DSN). One such sensor is the weak-signal Global Positioning System (GPS) receiver "Navigator" being developed at NASA's Goddard Space Flight Center (GSFC). At the heart of the Navigator is a Field Programmable Gate Array (FPGA) based acquisition engine. This engine allows for the rapid acquisition/reacquisition of strong GPS signals, enabling the receiver to quickly recover from outages due to blocked satellites or atmospheric entry. Additionally, the acquisition algorithm provides significantly lower sensitivities than a conventional space-based GPS receiver, permitting it to acquire satellites well above the GPS constellation. This paper assesses the performance of the Navigator receiver based upon three of the major flight regimes of a manned lunar mission: Earth ascent, cislunar navigation, and entry. Representative trajectories for each of these segments were provided by NASA. The Navigator receiver was connected to a Spirent GPS signal generator, to allow for the collection of real-time, hardware-in-the-loop results for each phase of the flight. For each of the flight segments, the Navigator was tested on its ability to acquire and track GPS satellites under the dynamical environment unique to that trajectory.

Bamford, William A.↗

Safer Systems: A NextGen Aviation Safety Strategic Goal

The Joint Planning and Development Office (JPDO), is charged by Congress with developing the concepts and plans for the Next Generation Air Transportation System (NextGen). The National Aviation Safety Strategic Plan (NASSP), developed by the Safety Working Group of the JPDO, focuses on establishing the goals, objectives, and strategies needed to realize the safety objectives of the NextGen Integrated Plan. The three goal areas of the NASSP are Safer Practices, Safer Systems, and Safer Worldwide. Safer Practices emphasizes an integrated, systematic approach to safety risk management through implementation of formalized Safety Management Systems (SMS) that incorporate safety data analysis processes, and the enhancement of methods for ensuring safety is an inherent characteristic of NextGen. Safer Systems emphasizes implementation of safety-enhancing technologies, which will improve safety for human-centered interfaces and enhance the safety of airborne and ground-based systems. Safer Worldwide encourages coordinating the adoption of the safer practices and safer systems technologies, policies and procedures worldwide, such that the maximum level of safety is achieved across air transportation system boundaries. This paper introduces the NASSP and its development, and focuses on the Safer Systems elements of the NASSP, which incorporates three objectives for NextGen systems: 1) provide risk reducing system interfaces, 2) provide safety enhancements for airborne systems, and 3) provide safety enhancements for ground-based systems. The goal of this paper is to expose avionics and air traffic management system developers to NASSP objectives and Safer Systems strategies.

Darr, Stephen T.↗

Using Pipelined XNOR Logic to Reduce SEU Risks in State Machines

Single-event upsets (SEUs) pose great threats to avionic systems state machine control logic, which are frequently used to control sequence of events and to qualify protocols. The risks of SEUs manifest in two ways: (a) the state machine s state information is changed, causing the state machine to unexpectedly transition to another state; (b) due to the asynchronous nature of SEU, the state machine's state registers become metastable, consequently causing any combinational logic associated with the metastable registers to malfunction temporarily. Effect (a) can be mitigated with methods such as triplemodular redundancy (TMR). However, effect (b) cannot be eliminated and can degrade the effectiveness of any mitigation method of effect (a). Although there is no way to completely eliminate the risk of SEU-induced errors, the risk can be made very small by use of a combination of very fast state-machine logic and error-detection logic. Therefore, one goal of two main elements of the present method is to design the fastest state-machine logic circuitry by basing it on the fastest generic state-machine design, which is that of a one-hot state machine. The other of the two main design elements is to design fast error-detection logic circuitry and to optimize it for implementation in a field-programmable gate array (FPGA) architecture: In the resulting design, the one-hot state machine is fitted with a multiple-input XNOR gate for detection of illegal states. The XNOR gate is implemented with lookup tables and with pipelines for high speed. In this method, the task of designing all the logic must be performed manually because no currently available logic synthesis software tool can produce optimal solutions of design problems of this type. However, some assistance is provided by a script, written for this purpose in the Python language (an object-oriented interpretive computer language) to automatically generate hardware description language (HDL) code from state-transition rules.

Le, Martin↗

Ikhana: A NASA UAS Supporting Long Duration Earth Science Missions

The NASA Ikhana unmanned aerial vehicle (UAV) is a General Atomics Aeronautical Systems Inc. (San Diego, California) MQ-9 Predator-B modified to support the conduct of Earth science missions for the NASA Science Mission Directorate and, through partnerships, other government agencies and universities. It can carry over 2000 lb of experiment payloads in the avionics bay and external pods and is capable of mission durations in excess of 24 hours at altitudes above 40,000 ft. The aircraft is remotely piloted from a mobile ground control station (GCS) that is designed to be deployable by air, land, or sea. On-board support capabilities include an instrumentation system and an Airborne Research Test System (ARTS). The Ikhana project will complete GCS development, science support systems integration, external pod integration and flight clearance, and operations crew training in early 2007. A large-area remote sensing mission is currently scheduled for Summer 2007.

Cobleigh, Brent R.↗

Replication of Space-Shuttle Computers in FPGAs and ASICs

A document discusses the replication of the functionality of the onboard space-shuttle general-purpose computers (GPCs) in field-programmable gate arrays (FPGAs) and application-specific integrated circuits (ASICs). The purpose of the replication effort is to enable utilization of proven space-shuttle flight software and software-development facilities to the extent possible during development of software for flight computers for a new generation of launch vehicles derived from the space shuttles. The replication involves specifying the instruction set of the central processing unit and the input/output processor (IOP) of the space-shuttle GPC in a hardware description language (HDL). The HDL is synthesized to form a "core" processor in an FPGA or, less preferably, in an ASIC. The core processor can be used to create a flight-control card to be inserted into a new avionics computer. The IOP of the GPC as implemented in the core processor could be designed to support data-bus protocols other than that of a multiplexer interface adapter (MIA) used in the space shuttle. Hence, a computer containing the core processor could be tailored to communicate via the space-shuttle GPC bus and/or one or more other buses.

Ferguson, Roscoe C.↗

Space Shuttle Usage of z/OS

This viewgraph presentation gives a detailed description of the avionics associated with the Space Shuttle's data processing system and its usage of z/OS. The contents include: 1) Mission, Products, and Customers; 2) Facility Overview; 3) Shuttle Data Processing System; 4) Languages and Compilers; 5) Application Tools; 6) Shuttle Flight Software Simulator; 7) Software Development and Build Tools; and 8) Fun Facts and Acronyms.

Green, Jan↗

Guidance and Control Software Project Data - Volume 2: Development Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the development documents from the GCS project. Volume 2 contains three appendices: A. Guidance and Control Software Development Specification; B. Design Description for the Pluto Implementation of the Guidance and Control Software; and C. Source Code for the Pluto Implementation of the Guidance and Control Software

Hayhurst, Kelly J.↗

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.↗

Guidance and Control Software Project Data - Volume 3: Verification Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.

Hayhurst, Kelly J.↗

Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

Hayhurst, Kelly J.↗

Ikhana: A NASA UAS Supporting Long Duration Earth Science Missions

NASA's Ikhana unmanned aerial vehicle (UAV) is a General Atomics MQ-9 Predator-B modified to support the conduct of Earth science missions for the NASA Science Mission Directorate through partnerships, other government agencies and universities. Ikhana, a Native American word meaning 'intelligence', can carry over 2000 lbs of atmospheric and remote sensing instruments in the payload bay and external pods. The aircraft is capable of mission durations in excess of 24 hours at altitudes above 40,000 ft. Redundant flight control, avionics, power, and network systems increase the system reliability and allow easier access to public airspace. The aircraft is remotely piloted from a mobile ground control station (GCS) using both C-band line-of-sight and Ku-band over-the-horizon satellite datalinks. NASA's GCS has been modified to support on-site science monitoring, or the downlink data can be networked to remote sites. All ground support systems are designed to be deployable to support global Eart science investigations. On-board support capabilities include an instrumentation system and an Airborne Research Test System (ARTS). The ARTS can host research algorithms that will autonomously command and control on-board sensors, perform sensor health monitoring, conduct data analysis, and request changes to the flight plan to maximize data collection. The ARTS also has the ability to host algorithms that will autonomously control the aircraft trajectory based on sensor needs, (e.g. precision trajectory for repeat pass interferometry) or to optimize mission objectives (e.g. search for specific atmospheric conditions). Standard on-board networks will collect science data for recording and for inclusion in the aircraft's high bandwidth downlink. The Ikhana project will complete GCS development, science support systems integration, external pod integration and flight clearance, and operations crew training in early 2007. A large-area remote sensing mission is currently scheduled for the Summer 2007.

Cobleigh, Brent R.↗

Rendezvous Integration Complexities of NASA Human Flight Vehicles

Propellant-optimal trajectories, relative sensors and navigation, and docking/capture mechanisms are rendezvous disciplines that receive much attention in the technical literature. However, other areas must be considered. These include absolute navigation, maneuver targeting, attitude control, power generation, software development and verification, redundancy management, thermal control, avionics integration, robotics, communications, lighting, human factors, crew timeline, procedure development, orbital debris risk mitigation, structures, plume impingement, logistics, and in some cases extravehicular activity. While current and future spaceflight programs will introduce new technologies and operations concepts, the complexity of integrating multiple systems on multiple spacecraft will remain. The systems integration task may become more difficult as increasingly complex software is used to meet current and future automation, autonomy, and robotic operation requirements.

Brazzel, Jack P.↗

Ares I and Ares V First Stage - Powering Exploration

The National Aeronautics and Space Administration (NASA) Ares Projects Office (APO) is continuing to make progress toward the final design of the first stage propulsion system for the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Ares I and Ares V will provide the space launch capabilities needed to fulfill NASA' s exploration strategy of sending human beings to the Moon, Mars, and beyond. As primary propulsion for the Ares launch vehicles, the Space Shuttle-derived Reusable Solid Rocket Motor (RSRM) is one of the first and most important components to be tested. The first flight of Ares I, called Ares I-X, will occur in April 2009, with booster integration to begin at Kennedy Space Center (KSC) by autumn 2008. The Ares I-X flight will use a combination of flight and simulation hardware to obtain data on controlling the long and narrow crew launch vehicle configuration. The test will use a four-segment RSRM from the Shuttle inventory and a fifth spacer segment to simulate the size and weight of the operational five-segment motor to be used on later flights. The upper stage, Orion crew exploration vehicle, and launch abort system will all be replaced with simulator hardware. Manufacturing work has begun on the spacer segment, as well as the new forward hardware for the booster. Atlas V avionics will be adapted to control Ares I-X' s first stage. That hardware is undergoing hardware-in-the-loop testing in a contractor-provided systems integration laboratory (SIL); a critical design review (CDR) was completed in December 2007. Drogue and main parachute drop tests have also been conducted successfully at Yuma Proving Grounds, allowing the First Stage team to begin fabricating parachutes for Ares I-X. The Ares I-X flight test will be the first flight test for the parachutes. A series of preliminary design technical interchange meetings is being conducted prior to the Ares I-X CDR in January 2007 to ensure readiness for the flight. Much of the First Stage activity in 2007 has focused on a series of preliminary design (PDR) activities associated with each booster subsystem. These events will culminate in a formal preliminary design review in 2008, where subsystems and component specifications will be developed and associated analyses and drawings will be evaluated for technical adequacy. The first stage also has been undergoing a series of trade studies to determine means for upgrading booster performance and reducing operational costs. Performance improvement studies have included changing from polybutadiene acrylonitrile (PBAN) propellant to hydroxyl-terminated polybutadiene (HTPB); replacing aluminum with composite motor casings; and optimizing or upgrading the propellant grain and nozzle structures. Some or all of these changes could result in a block upgrade to the Ares I first stage, after becoming the standard configuration for the Ares V. The cost reduction studies included a change from reusable or recoverable boosters to completely expendable boosters; changing from hydrazine-powered to more environmentally friendly electrohydrostatic actuators (EHAs) on the thrust vector control (TVC) system; and changing the location of the separation plane to reduce the likelihood of recontact upon booster separation. The expendability trade study resulted in a decision to keep the recoverable boosters, as the new hardware costs significantly outweighed the potential operational cost savings due to reduced ground operations. Likewise, due to cost considerations, the team continued using existing hydrazine-powered actuators for the TVC system. The separation plane location for Ares I is still being studied, with results to be announced in 2008. In short, the Ares launch vehicles' first stage is building upon NASA's close familiarity with this Shuttle-derived system, while continuing to seek out improvements for long-term exploration.

Priskos, Alex S.↗

Initial Assessment of the Ares I-X Launch Vehicle Upper Stage to Vibroacoustic Flight Environments

The Ares I launch vehicle will be NASA s first new launch vehicle since 1981. Currently in design, it will replace the Space Shuttle in taking astronauts to the International Space Station, and will eventually play a major role in humankind s return to the Moon and eventually to Mars. Prior to any manned flight of this vehicle, unmanned test readiness flights will be flown. The first of these readiness flights, named Ares I-X, is scheduled to be launched in April 2009. The NASA Glenn Research Center is responsible for the design, manufacture, test and analysis of the Ares I-X upper stage simulator (USS) element. As part of the design effort, the structural dynamic response of the Ares I-X launch vehicle to its vibroacoustic flight environments must be analyzed. The launch vehicle will be exposed to extremely high acoustic pressures during its lift-off and aerodynamic stages of flight. This in turn will cause high levels of random vibration on the vehicle's outer surface that will be transmitted to its interior. Critical flight equipment, such as its avionics and flight guidance components are susceptible to damage from this excitation. This study addresses the modelling, analysis and predictions from examining the structural dynamic response of the Ares I-X upper stage to its vibroacoustic excitations. A statistical energy analysis (SEA) model was used to predict the high frequency response of the vehicle at locations of interest. Key to this study was the definition of the excitation fields corresponding to lift off acoustics and the unsteady aerodynamic pressure fluctuations during flight. The predicted results will be used by the Ares I-X Project to verify the flight qualification status of the Ares I-X upper stage components.

Larko, Jeffrey M.↗