Space shuttle orbiter avionics software. Systems analysis flight software and SDL analysis reports
Results are presented of systems analyses of the avionics software of the space shuttle orbiter.
Source record↗
SEARCH · Engineering Papers
Results for “Flight Systems”
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.
The Development of an Airborne Instrumentation Computer System for Flight Test
Instrumentation interfacing frequently requires the linking of intelligent systems together, as well as requiring the link itself to be intelligent. The airborne instrumentation computer system (AICS) was developed to address this requirement. Its small size, approximately 254 by 133 by 140 mm (10 by 51/4 by 51/2 in), standard bus, and modular board configuration give it the ability to solve instrumentation interfacing and computation problems without forcing a redesign of the entire unit. This system has been used on the F-15 aircraft digital electronic engine control (DEEC) and its follow on engine model derivative (EMD) project and in an OV-1C Mohawk aircraft stall speed warning system. The AICS is presently undergoing configuration for use on an F-104 pace aircraft and on the advanced fighter technology integration (AFTI) F-111 aircraft.
Glenn A Bever↗
Analysis and Design of Launch Vehicle Flight Control Systems
This paper describes the fundamental principles of launch vehicle flight control analysis and design. In particular, the classical concept of "drift-minimum" and "load-minimum" control principles is re-examined and its performance and stability robustness with respect to modeling uncertainties and a gimbal angle constraint is discussed. It is shown that an additional feedback of angle-of-attack or lateral acceleration can significantly improve the overall performance and robustness, especially in the presence of unexpected large wind disturbance. Non-minimum-phase structural filtering of "unstably interacting" bending modes of large flexible launch vehicles is also shown to be effective and robust.
Wie, Bong↗
Plan Execution Interchange Language (PLEXIL) Software User's Manual
Plan Execution Interchange Language (PLEXIL) is a Core Flight System (or Core Flight Software) (cFS) based application, developed by the Autonomy Operating System project at NASA. cFS is open-source, reusable flight software, also developed by NASA and targeted to space missions. PLEXIL runs within the cFS framework, and is a wrapper integrating the open source PLEXIL Executive into the cFE (core Flight Executive) infrastructure. Software features include: Executes PLEXIL plans stored on local file system; Can be event-driven or clock-driven; and, Intended for "soft real time" discrete control.
Fry, Charles R.↗
TDRSS Onboard Navigation System (TONS) flight qualification experiment
The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) is currently developing an operational Tracking and Data Relay Satellite (TDRS) System (TDRSS) Onboard Navigation System (TONS) to provide realtime, autonomous, high-accuracy navigation products to users of TDRSS. A TONS experiment was implemented on the Explorer Platform/Extreme Ultraviolet Explorer (EP/EUVE) spacecraft, launched June 7, 1992, to flight qualify the TONS operational system using TDRSS forward-link communications services. This paper provides a detailed evaluation of the flight hardware, an ultrastable oscillator (USO) and Doppler extractor (DE) card in one of the TDRSS user transponders and the ground-based prototype flight software performance, based on the 1 year of TONS experiment operation. The TONS experiment results are used to project the expected performance of the TONS 1 operational system. TONS 1 processes Doppler data derived from scheduled forward-link S-band services using a sequential estimation algorithm enhanced by a sophisticated process noise model to provide onboard orbit and frequency determination and time maintenance. TONS 1 will be the prime navigation system on the Earth Observing System (EOS)-AM1 spacecraft, currently scheduled for launch in 1998. Inflight evaluation of the USO and DE short-term and long-term stability indicates that the performance is excellent. Analysis of the TONS prototype flight software performance indicates that realtime onboard position accuracies of better than 25 meters root-mean-square are achievable with one tracking contact every one to two orbits for the EP/EUVE 525-kilometer altitude, 28.5 degree inclination orbit. The success of the TONS experiment demonstrates the flight readiness of TONS to support the EOS-AM1 mission.
Gramling, C. J.↗
The development and testing of a lightweight flight prototype ion engine system.
Lightweight flight prototype mercury ion engine system development and testing
ION ENGINE↗
Development and testing of a lightweight flight prototype ion engine system.
Lightweight flight prototype mercury ion engine system development and testing
ION ENGINE↗
Some system considerations in configuring a digital flight control - navigation system
A trade study was conducted with the objective of providing a technical guideline for selection of the most appropriate computer technology for the automatic flight control system of a civil subsonic jet transport. The trade study considers aspects of using either an analog, incremental type special purpose computer or a general purpose computer to perform critical autopilot computation functions. It also considers aspects of integration of noncritical autopilot and autothrottle modes into the computer performing the critical autoland functions, as compared to the federation of the noncritical modes into either a separate computer or with a R-Nav computer. The study is accomplished by establishing the relative advantages and/or risks associated with each of the computer configurations.
Boone, J. H.↗
Entry, Descent, and Landing Communications for the 2011 Mars Science Laboratory
The Mars Science Laboratory (MSL), established as the most advanced rover to land on the surface of Mars to date, launched on November 26th, 2011 and arrived to the Martian Gale Crater during the night of August 5th, 2012 (PDT). MSL will investigate whether the landing region was ever suitable to support carbon-based life, and examine rocks, soil, and the atmosphere with a sophisticated suite of tools. This paper addresses the flight system requirement by which the vehicle transmitted indications of the following events using both X-band tones and UHF telemetry to allow identification of probable root causes should a mission anomaly have occurred: Heat-Rejection System (HRS) venting, completion of the cruise stage separation, turn to entry attitude, atmospheric deceleration, bank angle reversal commanded, parachute deployment, heatshield separation, radar ground acquisition, powered descent initiation, rover separation from the descent stage, and rover release. During Entry, Descent, and Landing (EDL), the flight system transmitted a UHF telemetry stream adequate to determine the state of the spacecraft (including the presence of faults) at 8 kbps initiating from cruise stage separation through at least one minute after positive indication of rover release on the surface of Mars. The flight system also transmitted X-band semaphore tones from Entry to Landing plus one minute although since MSL was occulted, as predicted, by Mars as seen from the Earth, Direct-To-Earth (DTE) communications were interrupted at approximately is approx. 5 min after Entry ( approximately 130 prior to Landing). The primary data return paths were through the Deep Space Network (DSN) for DTE and the existing Mars network of orbiting assets for UHF, which included the Mars Reconnaissance Orbiter (MRO), Mars Odyssey (ODY), and Mars Express (MEX) elements. These orbiters recorded the telemetry data stream and returned it back to Earth via the DSN. The paper also discusses the total power received during EDL and the robustness of the telecom design strategy used to ensure EDL communications coverage.
relay operations↗
Spacecraft Design Thermal Control Subsystem
This slide presentation reviews the functions of the thermal control subsystem engineers in the design of spacecraft. The goal of the thermal control subsystem that will be used in a spacecraft is to maintain the temperature of all spacecraft components, subsystems, and all the flight systems within specified limits for all flight modes from launch to the end of the mission. For most thermal control subsystems the mass, power and control and sensing systems must be kept below 10% of the total flight system resources. This means that the thermal control engineer is involved in all other flight systems designs. The two concepts of thermal control, passive and active are reviewed and the use of thermal modeling tools are explained. The testing of the thermal control is also reviewed.
thermal control↗
Advanced Transport Operating System (ATOPS) Flight Management/Flight Controls (FM/FC) software description
The flight software developed for the Flight Management/Flight Controls (FM/FC) MicroVAX computer used on the Transport Systems Research Vehicle for Advanced Transport Operating Systems (ATOPS) research is described. The FM/FC software computes navigation position estimates, guidance commands, and those commands issued to the control surfaces to direct the aircraft in flight. Various modes of flight are provided for, ranging from computer assisted manual modes to fully automatic modes including automatic landing. A high-level system overview as well as a description of each software module comprising the system is provided. Digital systems diagrams are included for each major flight control component and selected flight management functions.
Wolverton, David A.↗
The effects of lightning on digital flight control systems
Present practices in lightning protection of aircraft deal primarily with the direct effects of lightning, such as structural damage and ignition of fuel vapors. There is increasing evidence of troublesome electromagnetic effects, however, in aircraft employing solid-state microelectronics in critical navigation, instrumentation and control functions. The potential impact of these indirect effects on critical systems such as digital fly by wire (DFBW) flight controls was studied. The results indicate a need for positive steps to be taken during the design of future fly by wire systems to minimize the possibility of hazardous effects from lightning.
Plumer, J. A.↗
Flight design system level C requirements. Solid rocket booster and external tank impact prediction processors
The prediction of the SRB and ET impact areas requires six separate processors. The SRB impact prediction processor computes the impact areas and related trajectory data for each SRB element. Output from this processor is stored on a secure file accessible by the SRB impact plot processor which generates the required plots. Similarly the ET RTLS impact prediction processor and the ET RTLS impact plot processor generates the ET impact footprints for return-to-launch-site (RTLS) profiles. The ET nominal/AOA/ATO impact prediction processor and the ET nominal/AOA/ATO impact plot processor generate the ET impact footprints for non-RTLS profiles. The SRB and ET impact processors compute the size and shape of the impact footprints by tabular lookup in a stored footprint dispersion data base. The location of each footprint is determined by simulating a reference trajectory and computing the reference impact point location. To insure consistency among all flight design system (FDS) users, much input required by these processors will be obtained from the FDS master data base.
Seale, R. H.↗
Apollo 12 mission report. Supplement 4: Ascent propulsion system final flight evaluation
The results of the postflight analysis of the ascent propulsion system (APS) performance during the Apollo 12 Mission are presented. The steady-state performance analysis, and pressurization system are discussed along with the propellant loading and usage, APS overburn, and burn time. It is concluded that APS flight performance reconstructions for LM-3, LM-4, LM-5, and LM-6 indicate that engine performance prediction techniques are conservative.
Griffin, W. G.↗
Pi-Sat: A Low Cost Small Satellite and Distributed Spacecraft Mission System Test Platform
Current technology and budget trends indicate a shift in satellite architectures from large, expensive single satellite missions, to small, low cost distributed spacecraft missions. At the center of this shift is the SmallSatCubesat architecture. The primary goal of the Pi-Sat project is to create a low cost, and easy to use Distributed Spacecraft Mission (DSM) test bed to facilitate the research and development of next-generation DSM technologies and concepts. This test bed also serves as a realistic software development platform for Small Satellite and Cubesat architectures. The Pi-Sat is based on the popular $35 Raspberry Pi single board computer featuring a 700Mhz ARM processor, 512MB of RAM, a flash memory card, and a wealth of IO options. The Raspberry Pi runs the Linux operating system and can easily run Code 582s Core Flight System flight software architecture. The low cost and high availability of the Raspberry Pi make it an ideal platform for a Distributed Spacecraft Mission and Cubesat software development. The Pi-Sat models currently include a Pi-Sat 1U Cube, a Pi-Sat Wireless Node, and a Pi-Sat Cubesat processor card.The Pi-Sat project takes advantage of many popular trends in the Maker community including low cost electronics, 3d printing, and rapid prototyping in order to provide a realistic platform for flight software testing, training, and technology development. The Pi-Sat has also provided fantastic hands on training opportunities for NASA summer interns and Pathways students.
Software↗
Progress in Scheduling Algorithms for a Collaborative Distributed System for Flight Planning
This Technical Memorandum describes four contributions made by the authors to a larger team effort toward developing a distributed system for scheduling commercial flights at navigation fixes and/or airport runways. These contributions are as follows: (1) a proof of correctness for a scheduling algorithm published previously by Meyn, (2) an improvement of Meyn's algorithm from quadratic to linear time, (3) two independent implementations of the algorithm with test results identical to those published, and (4) an extension of Meyn's algorithm to support minimum usable time intervals.
arrival scheduling↗
Apollo 15 mission report. Supplement 3: Ascent propulsion system final flight evaluation
Results from the postflight analysis of the ascent propulsion system (APS) performance during the Apollo 15 mission are presented. The duty cycle for the LM-10 APS consisted of two firings, and ascent stage liftoff from the lunar surface and the terminal phase ignition (TPI) burn. An evaluation was made of APS performance for the first firing and found to be satisfactory. No propulsion data was received from the second APS burn; however, all indications were that the burn was nominal. All performance parameters were well within their LM-10 3-sigma limits. Calculated throat erosion at engine cutoff for the LM-10 APS was approximately 3 percent greater than predicted.
Griffin, W. G.↗
Drinking from the Fire Hose: Why the Flight Management System Can Be Hard to Train and Difficult to Use
The Flight Management Computer (FMC) and its interface, the Multi-function Control and Display Unit (MCDU) have been identified by researchers and airlines as difficult to train and use. Specifically, airline pilots have described the "drinking from the fire-hose" effect during training. Previous research has identified memorized action sequences as a major factor in a user s ability to learn and operate complex devices. This paper discusses the use of a method to examine the quantity of memorized action sequences required to perform a sample of 102 tasks, using features of the Boeing 777 Flight Management Computer Interface. The analysis identified a large number of memorized action sequences that must be learned during training and then recalled during line operations. Seventy-five percent of the tasks examined require recall of at least one memorized action sequence. Forty-five percent of the tasks require recall of a memorized action sequence and occur infrequently. The large number of memorized action sequences may provide an explanation for the difficulties in training and usage of the automation. Based on these findings, implications for training and the design of new user-interfaces are discussed.
Sherry, Lance↗