Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight control computer”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1983

Analytical redundancy management mechanization and flight data analysis for the F-8 digital fly-by-wire aircraft flight control sensors

The details are presented of an onboard digital computer algorithm designed to reliably detect and isolate the first failure in a duplex set of flight control sensors aboard the NASA F-8 digital fly-by-wire aircraft. The algorithm's successful flight test program is summarized, and specific examples are presented of algorithm behavior in response to software-induced signal faults, both with and without aircraft parameter modeling errors.

Deckert, J. C.↗
NASA NTRS2011

Autorotation flight control system

The present invention provides computer implemented methodology that permits the safe landing and recovery of rotorcraft following engine failure. With this invention successful autorotations may be performed from well within the unsafe operating area of the height-velocity profile of a helicopter by employing the fast and robust real-time trajectory optimization algorithm that commands control motion through an intuitive pilot display, or directly in the case of autonomous rotorcraft. The algorithm generates optimal trajectories and control commands via the direct-collocation optimization method, solved using a nonlinear programming problem solver. The control inputs computed are collective pitch and aircraft pitch, which are easily tracked and manipulated by the pilot or converted to control actuator commands for automated operation during autorotation in the case of an autonomous rotorcraft. The formulation of the optimal control problem has been carefully tailored so the solutions resemble those of an expert pilot, accounting for the performance limitations of the rotorcraft and safety concerns.

Bachelder, Edward N.↗
NASA NTRS2007

Remote Controlled Orbiter Capability

The Remote Control Orbiter (RCO) capability allows a Space Shuttle Orbiter to perform an unmanned re-entry and landing. This low-cost capability employs existing and newly added functions to perform key activities typically performed by flight crews and controllers during manned re-entries. During an RCO landing attempt, these functions are triggered by automation resident in the on-board computers or uplinked commands from flight controllers on the ground. In order to properly route certain commands to the appropriate hardware, an In-Flight Maintenance (IFM) cable was developed. Currently, the RCO capability is reserved for the scenario where a safe return of the crew from orbit may not be possible. The flight crew would remain in orbit and await a rescue mission. After the crew is rescued, the RCO capability would be used on the unmanned Orbiter in an attempt to salvage this national asset.

Garske, Michael↗
NASA NTRS1990

Potential for integrated optical circuits in advanced aircraft with fiber optic control and monitoring systems

Fiber optic technology is expected to be used in future advanced weapons platforms as well as commercial aerospace applications. Fiber optic waveguides will be used to transmit noise free, high speed data between a multitude of computers as well as audio and video information to the flight crew. Passive optical sensors connected to control computers with optical fiber interconnects will serve both control and monitoring functions. Implementation of fiber optic technology has already begun. Both the military and NASA have several programs in place. A cooperative program, called FOCSI (Fiber Optic Control System Integration), between NASA Lewis and the NAVY to build, environmentally test and flight demonstrate sensor systems for propulsion and flight control systems is currently underway. Integrated Optical Circuits (IOC's) are also being given serious consideration for use in advanced aircraft systems. IOC's will result in miniaturization and localization of components to generate, detect optical signals and process them for use by the control computers. In some complex systems IOC's may be required to perform calculations optically if the technology is ready, replacing some of the electronic systems used today. IOC's are attractive because they will result in rugged components capable of withstanding severe environments in advanced aerospace vehicles. Manufacturing technology developed for microelectronic integrated circuits applied to IOC's will result in cost effective manufacturing. This paper reviews the current FOCSI program and describes the potential role of IOC's in FOCSI applications.

Robert Baumbick↗
NASA NTRS1998

Incorporating Manual and Autonomous Code Generation

Code can be generated manually or using code-generated software tools, but how do you interpret the two? This article looks at a design methodology that combines object-oriented design with autonomic code generation for attitude control flight software. Recent improvements in space flight computers are allowing software engineers to spend more time engineering the applications software. The application developed was the attitude control flight software for an astronomical satellite called the Microwave Anisotropy Probe (MAP). The MAP flight system is being designed, developed, and integrated at NASA's Goddard Space Flight Center. The MAP controls engineers are using Integrated Systems Inc.'s MATRIXx for their controls analysis. In addition to providing a graphical analysis for an environment, MATRIXx includes an autonomic code generation facility called AutoCode. This article examines the forces that shaped the final design and describes three highlights of the design process: (1) Defining the manual to autonomic code interface; (2) Applying object-oriented design to the manual flight code; (3) Implementing the object-oriented design in C.

McComas, David↗
NASA NTRS1998

Using Engine Thrust for Emergency Flight Control: MD-11 and B-747 Results

With modern digital control systems, using engine thrust for emergency flight control to supplement or replace failed aircraft normal flight controls has become a practical consideration. The NASA Dryden Flight Research Center has developed a propulsion-controlled aircraft (PCA) system in which computer-controlled engine thrust provides emergency flight control. An F-15 and an MD-11 airplane have been landed without using any flight control surfaces. Preliminary studies have also been conducted that show that engines on only one wing can provide some flight control capability if the lateral center of gravity can be shifted toward the side of the airplane that has the operating engine(s). Simulator tests of several airplanes with no flight control surfaces operating and all engines out on the left wing have all shown positive control capability within the available range of lateral center-of-gravity offset. Propulsion-controlled aircraft systems that can operate without modifications to engine control systems, thus allowing PCA technology to be installed on less capable airplanes or at low cost, are also desirable. Further studies have examined simplified 'PCA Lite' and 'PCA Ultralite' concepts in which thrust control is provided by existing systems such as auto-throttles or a combination of existing systems and manual pilot control.

Burcham, Frank W., Jr.↗
NASA NTRS1999

Simulator Evaluation of Simplified Propulsion-Only Emergency Flight Control Systems on Transport Aircraft

With the advent of digital engine control systems, considering the use of engine thrust for emergency flight control has become feasible. Many incidents have occurred in which engine thrust supplemented or replaced normal aircraft flight controls. In most of these cases, a crash has resulted, and more than 1100 lives have been lost. The NASA Dryden Flight Research Center has developed a propulsion-controlled aircraft (PCA) system in which computer-controlled engine thrust provides emergency flight control capability. Using this PCA system, an F-15 and an MD-11 airplane have been landed without using any flight controls. In simulations, C-17, B-757, and B-747 PCA systems have also been evaluated successfully. These tests used full-authority digital electronic control systems on the engines. Developing simpler PCA systems that can operate without full-authority engine control, thus allowing PCA technology to be installed on less capable airplanes or at lower cost, is also a desire. Studies have examined simplified ?PCA Ultralite? concepts in which thrust control is provided using an autothrottle system supplemented by manual differential throttle control. Some of these concepts have worked well. The PCA Ultralite study results are presented for simulation tests of MD-11, B-757, C-17, and B-747 aircraft.

Burcham, Frank W., Jr.↗
NASA NTRS1986

Anthropometric considerations for a 4-axis side-arm flight controller

A data base on multiaxis side-arm flight controls was generated. The rapid advances in fly-by-light technology, automatic stability systems, and onboard computers have combined to create flexible flight control systems which could reduce the workload imposed on the operator by complex new equipment. This side-arm flight controller combines four controls into one unit and should simplify the pilot's task. However, the use of a multiaxis side-arm flight controller without complete cockpit integration may tend to increase the pilot's workload.

Debellis, W. B.↗
NASA NTRS1984

Control system testing

A three stage process of ground testing of the Space Telescope Pointing Control System is used for verification prior to on-orbit operation. First, development tests are conducted in a laboratory environment using flight/engineering model control sensor and actuators configured with an engineering model of the flight computer and data management system breadboards. These development tests validate the results of computer simulations predicting control system performance. Integration tests bring together flight system elements and software interfaced to a software simulation of vehicle dynamics to confirm closed loop performance. The final ground test phase, flight systems testing, is conducted on the fully assembled Space Telescope, verifies interfaces with the Fine Guidance Sensors and includes a thermal vacuum testing period. During the final test phase, the Point Control System is exercised with the dynamics simulator running in real time.

Whittler, W. H.↗
NASA NTRS1986

Wright Brothers Lectureship in Aeronautics: Experience with HiMAT remotely piloted research vehicle - An alternate flight test approach

The highly maneuverable aircraft technology (HiMAT) program explored the various and complex interactions of advanced technologies, such as aeroelastic tailoring, close-coupled canard, and relaxed static stability. A 0.44-subscale remotely piloted research vehicle (RPRV) of a hypothetical fighter airplane was designed and flight-tested to determine the effects of these interactions and to define the design techniques appropriate for advanced fighter technologies. Flexibility and high maneuverability were provided by flight control laws implemented in ground-based computers and telemetered to the vehicle control system during flight tests. The high quality of the flight-measured data and their close correlation with the analytical design modeling proved that the RPRV is a viable and cost-effective tool for developing aerodynamic, structure, and control law requirements for highly maneuverable fighter airplanes of the future.

Deets, D. A.↗
NASA NTRS1985

Achieving reliability - The evolution of redundancy in American manned spacecraft computers

The Shuttle is the first launch system deployed by NASA with full redundancy in the on-board computer systems. Fault-tolerance, i.e., restoring to a backup with less capabilities, was the method selected for Apollo. The Gemini capsule was the first to carry a computer, which also served as backup for Titan launch vehicle guidance. Failure of the Gemini computer resulted in manual control of the spacecraft. The Apollo system served vehicle flight control and navigation functions. The redundant computer on Skylab provided attitude control only in support of solar telescope pointing. The STS digital, fly-by-wire avionics system requires 100 percent reliability. The Orbiter carries five general purpose computers, four being fully-redundant and the fifth being soley an ascent-descent tool. The computers are synchronized at input and output points at a rate of about six times a second. The system is projected to cause a loss of an Orbiter only four times in a billion flights.

Tomayko, J. E.↗
NASA NTRS1982

NASA Deep Space Network Operations Scheduling

The functioning of the Deep Space Network Operations Scheduling, Jet Propulsion Laboratory, CA is reviewed. The primary objectives of the Operations Scheduling are: to schedule the worldwide global allocation of ground communications, tracking facilities, and equipment; and to provide deep space telecommunications for command, tracking, telemetry, and control in support of flight mission operations and tests. Elements of the earth set are Deep Space Stations (DSS) which provide the telecommunications link between the earth and spacecraft; NASA Communications Network; Network Data Processing Area; Network Operations Control Area which provides operational direction to the DSS; Mission Control and Computing systems; and Mission Support areas which provide flight control of the spacecraft. Elements of the space set include mission priorities and requirements which determine the spacecraft queue for allocating network resources. Scheduling is discussed in terms of long-range (3 years), mid-range (8 weeks), and short-range (2 weeks).

Enari, D. M.↗
NASA NTRS1986

In-Flight Simulator for IFR Training

Computer-controlled unit feeds navigation signals to airplane instruments. Electronic training system allows students to learn to fly according to instrument flight rules (IFR) in uncrowded airspace. New system self-contained IFR simulator carried aboard training plane. Generates signals and commands for standard instruments on airplane, including navigational receiver, distance-measuring equipment, automatic direction finder, a marker-beacon receiver, altimeter, airspeed indicator, and heading indicator.

Parker, L. C.↗
NASA NTRS1977

The aircraft energy efficiency active controls technology program

Broad outlines of the NASA Aircraft Energy Efficiency Program for expediting the application of active controls technology to civil transport aircraft are presented. Advances in propulsion and airframe technology to cut down on fuel consumption and fuel costs, a program for an energy-efficient transport, and integrated analysis and design technology in aerodynamics, structures, and active controls are envisaged. Fault-tolerant computer systems and fault-tolerant flight control system architectures are under study. Contracts with leading manufacturers for research and development work on wing-tip extensions and winglets for the B-747, a wing load alleviation system, elastic mode suppression, maneuver-load control, and gust alleviation are mentioned.

Hood, R. V., Jr.↗
NASA NTRS1981

Hierarchical specification of the SIFT fault tolerant flight control system

The specification and mechanical verification of the Software Implemented Fault Tolerance (SIFT) flight control system is described. The methodology employed in the verification effort is discussed, and a description of the hierarchical models of the SIFT system is given. To meet the objective of NASA for the reliability of safety critical flight control systems, the SIFT computer must achieve a reliability well beyond the levels at which reliability can be actually measured. The methodology employed to demonstrate rigorously that the SIFT computer meets as reliability requirements is described. The hierarchy of design specifications from very abstract descriptions of system function down to the actual implementation is explained. The most abstract design specifications can be used to verify that the system functions correctly and with the desired reliability since almost all details of the realization were abstracted out. A succession of lower level models refine these specifications to the level of the actual implementation, and can be used to demonstrate that the implementation has the properties claimed of the abstract design specifications.

Melliar-Smith, P. M.↗