Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Flight Software”

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,099 records · Page 61
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Flight test of a propulsion controlled aircraft system on the NASA F-15 airplane

Flight tests of the propulsion controlled aircraft (PCA) system on the NASA F-15 airplane evolved as a result of a long series of simulation and flight tests. Initially, the simulation results were very optimistic. Early flight tests showed that manual throttles-only control was much more difficult than the simulation, and a flight investigation was flown to acquire data to resolve this discrepancy. The PCA system designed and developed by MDA evolved as these discrepancies were found and resolved, requiring redesign of the PCA software and modification of the flight test plan. Small throttle step inputs were flown to provide data for analysis, simulation update, and control logic modification. The PCA flight tests quickly revealed less than desired performance, but the extensive flexibility built into the flight PCA software allowed rapid evaluation of alternate gains, filters, and control logic, and within 2 weeks, the PCA system was functioning well. The initial objective of achieving adequate control for up-and-away flying and approaches was satisfied, and the option to continue to actual landings was achieved. After the PCA landings were accomplished, other PCA features were added, and additional maneuvers beyond those originally planned were flown. The PCA system was used to recover from extreme upset conditions, descend, and make approaches to landing. A heading mode was added, and a single engine plus rudder PCA mode was also added and flown. The PCA flight envelope was expanded far beyond that originally designed for. Guest pilots from the USAF, USN, NASA, and the contractor also flew the PCA system and were favorably impressed.

Burcham, Frank W., Jr.↗
NASA NTRS1987

Traditional versus rule-based programming techniques: Application to the control of optional flight information

To the software design community, the concern over the costs associated with a program's execution time and implementation is great. It is always desirable, and sometimes imperative, that the proper programming technique is chosen which minimizes all costs for a given application or type of application. A study is described that compared cost-related factors associated with traditional programming techniques to rule-based programming techniques for a specific application. The results of this study favored the traditional approach regarding execution efficiency, but favored the rule-based approach regarding programmer productivity (implementation ease). Although this study examined a specific application, the results should be widely applicable.

Ricks, Wendell R.↗
NASA NTRSDate not supplied

Flight Test Design and Implementation for Airspace Independent Surveillance Through a Distributed Ground Based Sensor Network

The paper presents a system architecture for distributed sensing, networking and computing, its hardware implementation, and execution of initial flight experiments to validate theoretical findings. It induces development of distributed sensing requirements, framework, and architecture, development of distributed ground node hardware prototypes, integration of all nodes and testing of baseline functionalities, integration of in-house developed perception, migration and tracking software packages, establishing flight scenario and flyable path for a selected UAS, flying the air vehicle along the path, recording sensors measurements, pre-processing them and transferring the resulting data to an optimal computing center. It also addresses the challenges related to pre-flight hardware calibration, clock synchronization, sensor registration and establishing a communication network. Sensors data processing results demonstrate the functionality of the presented distributed architecture and satisfactory performance of the applied technologies.

Target tracking↗
NASA NTRSDate not supplied

Flight Test Design and Implementation for Independent Surveillance of an Airspace Through a Distributed Ground Sensing Network

The paper presents a system architecture for distributed sensing, networking and computing, its hardware implementation, and execution of initial flight experiments to validate theoretical findings. It induces development of distributed sensing requirements, framework, and architecture, development of distributed ground node hardware prototypes, integration of all nodes and testing of baseline functionalities, integration of in-house developed perception, migration and tracking software packages, establishing flight scenario and flyable path for a selected UAS, flying the air vehicle along the path, recording sensors measurements, pre-processing them and transferring the resulting data to an optimal computing center. It also addresses the challenges related to pre-flight hardware calibration, clock synchronization, sensor registration and establishing a communication network. Sensors data processing results demonstrate the functionality of the presented distributed architecture and satisfactory performance of the applied technologies.

Distributed sensing↗
NASA NTRS1995

Concept Designed and Developed for Distortion- Tolerant, High-Stability Engine Control

Engine Control Future aircraft turbine engines, both commercial and military, must be able to successfully accommodate expected increased levels of steady-state and dynamic engine-face distortion. Advanced tactical aircraft are likely to use thrust vectoring to enhance their maneuverability. As a result, the engines will see more extreme aircraft angles-of-attack and sideslip levels than are currently encountered with present-day aircraft. Also, the mixed-compression inlets needed for the High Speed Civil Transport will likely encounter disturbances similar to those seen by tactical aircraft, in addition to planar pulse, inlet buzz, and high distortion levels at low flight speed and off-design operation. The current approach of incorporating a sufficient component design stall margin to tolerate these increased levels of distortion would significantly reduce performance. The objective of the High Stability Engine Control (HISTEC) program is to design, develop, and flight demonstrate an advanced, high-stability, integrated engine-control system that uses measurement-based, real-time estimates of distortion to enhance engine stability. The resulting distortion-tolerant control reduces the required design stall margin, with a corresponding increase in performance and decrease in fuel burn. The HISTEC concept has been designed and developed, and the software implementing the concept has successfully accommodated time-varying distortion. The NASA Lewis Research Center is currently overseeing the development and validation of the hardware and software necessary to flight test the HISTEC concept. HISTEC is a contracted effort with Pratt & Whitney of West Palm Beach, Florida. The HISTEC approach includes two major systems: A Distortion Estimation System (DES) and Stability Management Control (SMC). DES is an aircraft-mounted, high-speed processor that estimates the amount and type of distortion present and its effect on the engine. It uses high-response pressure measurements at the engine face to calculate indicators of the type and extent of distortion in real time. From these indicators, DES determines the effects of distortion on the propulsion systems and the corresponding engine match point necessary to accommodate it. DES output consists of fan and compressor pressure ratio trim commands that are passed to the SMC. In addition, DES uses maneuver information, consisting of angle-of-attack and sideslip from the flight control, to anticipate high inlet distortion conditions. The SMC, which is contained in the engine-mounted, Improved Digital Electronic Engine Control (IDEEC), includes advanced control laws to directly control the fan and compressor transient operating line (pressure ratio). These advanced control laws, with a multivariable design, have the potential for higher bandwidth and the resulting more precise control of engine match. The ability to measure and assess the distortion effects in real time coupled with a high-response controller improves engine stability at high levels of distortion. The software algorithms implementing DES have been designed, developed, and demonstrated, and integration testing of the DES and SMC software has been completed. The results show that the HISTEC system will be able to sense inlet distortion, determine the effect on engine stability, and accommodate distortion by maintaining an adequate margin for engine surge. The Pratt &Whitney Comprehensive Engine Diagnostic Unit was chosen as the DES processor. An instrumented inlet case for sensing distortion was designed and fabricated. HISTEC is scheduled for flight test on the ACTIVE F-15 aircraft at the NASA Dryden Flight Research Center in Edwards, California, in late 1996.

Source record↗
NASA NTRS1978

Propulsion/flight control integration technology (PROFIT) software system definition

The Propulsion Flight Control Integration Technology (PROFIT) program is designed to develop a flying testbed dedicated to controls research. The control software for PROFIT is defined. Maximum flexibility, needed for long term use of the flight facility, is achieved through a modular design. The Host program, processes inputs from the telemetry uplink, aircraft central computer, cockpit computer control and plant sensors to form an input data base for use by the control algorithms. The control algorithms, programmed as application modules, process the input data to generate an output data base. The Host program formats the data for output to the telemetry downlink, the cockpit computer control, and the control effectors. Two applications modules are defined - the bill of materials F-100 engine control and the bill of materials F-15 inlet control.

Carlin, C. M.↗
NASA NTRS2013

Towards Real-time, On-board, Hardware-Supported Sensor and Software Health Management for Unmanned Aerial Systems

Unmanned aerial systems (UASs) can only be deployed if they can effectively complete their missions and respond to failures and uncertain environmental conditions while maintaining safety with respect to other aircraft as well as humans and property on the ground. In this paper, we design a real-time, on-board system health management (SHM) capability to continuously monitor sensors, software, and hardware components for detection and diagnosis of failures and violations of safety or performance rules during the flight of a UAS. Our approach to SHM is three-pronged, providing: (1) real-time monitoring of sensor and/or software signals; (2) signal analysis, preprocessing, and advanced on the- fly temporal and Bayesian probabilistic fault diagnosis; (3) an unobtrusive, lightweight, read-only, low-power realization using Field Programmable Gate Arrays (FPGAs) that avoids overburdening limited computing resources or costly re-certification of flight software due to instrumentation. Our implementation provides a novel approach of combining modular building blocks, integrating responsive runtime monitoring of temporal logic system safety requirements with model-based diagnosis and Bayesian network-based probabilistic analysis. We demonstrate this approach using actual data from the NASA Swift UAS, an experimental all-electric aircraft.

System & Software Health Management↗
NASA NTRS2015

Towards Real-Time, On-Board, Hardware-Supported Sensor and Software Health Management for Unmanned Aerial Systems

For unmanned aerial systems (UAS) to be successfully deployed and integrated within the national airspace, it is imperative that they possess the capability to effectively complete their missions without compromising the safety of other aircraft, as well as persons and property on the ground. This necessity creates a natural requirement for UAS that can respond to uncertain environmental conditions and emergent failures in real-time, with robustness and resilience close enough to those of manned systems. We introduce a system that meets this requirement with the design of a real-time onboard system health management (SHM) capability to continuously monitor sensors, software, and hardware components. This system can detect and diagnose failures and violations of safety or performance rules during the flight of a UAS. Our approach to SHM is three-pronged, providing: (1) real-time monitoring of sensor and software signals; (2) signal analysis, preprocessing, and advanced on-the-fly temporal and Bayesian probabilistic fault diagnosis; and (3) an unobtrusive, lightweight, read-only, low-power realization using Field Programmable Gate Arrays (FPGAs) that avoids overburdening limited computing resources or costly re-certification of flight software. We call this approach rt-R2U2, a name derived from its requirements. Our implementation provides a novel approach of combining modular building blocks, integrating responsive runtime monitoring of temporal logic system safety requirements with model-based diagnosis and Bayesian network-based probabilistic analysis. We demonstrate this approach using actual flight data from the NASA Swift UAS.

Unmanned Aerial System↗
NASA NTRS1990

System testing of a production Ada (trademark) project: The GRODY study

The use of the Ada language and design methodologies that utilize its features has a strong impact on all phases of the software development project lifecycle. At the National Aeronautics and Space Administration/Goddard Space Flight Center (NASA/GSFC), the Software Engineering Laboratory (SEL) conducted an experiment in parallel development of two flight dynamics systems in FORTRAN and Ada. The teams found some qualitative differences between the system test phases of the two projects. Although planning for system testing and conducting of tests were not generally affected by the use of Ada, the solving of problems found in system testing was generally facilitated by Ada constructs and design methodology. Most problems found in system testing were not due to difficulty with the language or methodology but to lack of experience with the application.

Seigle, Jeffrey↗
NASA NTRS2019

NEXT Single String Integration Tests in Support of the Double Asteroid Redirection Test Mission

A system integration test has been performed utilizing a prototype model NEXT ion thruster, an engineering model power processing unit, and a laboratory model command and data handling system. The objectives of the test were to: a) verify that the integrated system meets performance requirements, b) demonstrate that the integrated system is functional across the anticipated thermal, power processor, and Xe propellant ranges for the DART mission, and to c) evaluate fault detection and operation of the command and data handling system. Measurements made during this test included: thruster performance, PPU input voltages, PPU electrical and thermal telemetry, software states, and fault flags. Additionally, a far-field electrostatic probe diagnostic was used to infer relative changes in the thrust vector across the various propellant flow splits. This manuscript presents the results of these tests, which include integrated ion propulsion system demonstrations of performance, details on the execution of DART flight algorithms, and software fault handling.

Thomas, Robert E.↗
NASA NTRS2019

NEXT Single String Integration Tests in Support of the Double Asteroid Redirection Test Mission

A system integration test has been performed utilizing a prototype model NEXT ion thruster, an engineering model power processing unit, and a laboratory model command and data handling system. The objectives of the test were to: a) verify that the integrated system meets performance requirements, b) demonstrate that the integrated system is functional across the anticipated thermal, power processor, and Xe propellant ranges for the DART mission, and to c) evaluate fault detection and operation of the command and data handling system. Measurements made during this test included: thruster performance, PPU input voltages, PPU electrical and thermal telemetry, software states, and fault flags. Additionally, a far-field electrostatic probe diagnostic was used to infer relative changes in the thrust vector across the various propellant flow splits. This manuscript presents the results of these tests, which include integrated ion propulsion system demonstrations of performance, details on the execution of DART flight algorithms, and software fault handling.

Thomas, Robert↗
NASA NTRS2006

Statistical Detection of Atypical Aircraft Flights

A computational method and software to implement the method have been developed to sift through vast quantities of digital flight data to alert human analysts to aircraft flights that are statistically atypical in ways that signify that safety may be adversely affected. On a typical day, there are tens of thousands of flights in the United States and several times that number throughout the world. Depending on the specific aircraft design, the volume of data collected by sensors and flight recorders can range from a few dozen to several thousand parameters per second during a flight. Whereas these data have long been utilized in investigating crashes, the present method is oriented toward helping to prevent crashes by enabling routine monitoring of flight operations to identify portions of flights that may be of interest with respect to safety issues.

Statler, Irving↗
NASA NTRS2003

Development and Flight Testing of an Autonomous Landing Gear Health-Monitoring System

Development and testing of an adaptable vehicle health-monitoring architecture is presented. The architecture is being developed for a fleet of vehicles. It has three operational levels: one or more remote data acquisition units located throughout the vehicle; a command and control unit located within the vehicle; and, a terminal collection unit to collect analysis results from all vehicles. Each level is capable of performing autonomous analysis with a trained expert system. Communication between all levels is done with wireless radio frequency interfaces. The remote data acquisition unit has an eight channel programmable digital interface that allows the user discretion for choosing type of sensors; number of sensors, sensor sampling rate and sampling duration for each sensor. The architecture provides framework for a tributary analysis. All measurements at the lowest operational level are reduced to provide analysis results necessary to gauge changes from established baselines. These are then collected at the next level to identify any global trends or common features from the prior level. This process is repeated until the results are reduced at the highest operational level. In the framework, only analysis results are forwarded to the next level to reduce telemetry congestion. The system's remote data acquisition hardware and non-analysis software have been flight tested on the NASA Langley B757's main landing gear. The flight tests were performed to validate the following: the wireless radio frequency communication capabilities of the system, the hardware design, command and control; software operation; and, data acquisition, storage and retrieval.

Woodard, Stanley E.↗
NASA NTRSDate not supplied

Successful First Flight of NASA’s SLS (Space Launch System) Super Heavy-Lift Rocket Lays Groundwork for U. S.’s Most Ambitious Missions

In late 2022, NASA’s SLS (Space Launch System) super heavy-lift rocket launched for the first time. Artemis I sent an uncrewed Orion spacecraft on a 25.5-day round-trip mission to lunar orbit. The near-perfect performance laid the groundwork for the next flights and for NASA’s return of humans to the Moon. The SLS team is now preparing for the launch of Artemis II, which will be the first launch of astronauts to cislunar space since Apollo 17 in December 1972. In addition to preparations on the Artemis II launch vehicle, significant progress is being made on the hardware and software for future flights. Artemis II will include a test of a new military-grade GPS system, which will be fully utilized on Artemis III. Progress is also being made on the exploration upper stage (EUS) for the Block 1B SLS variant, which will debut on Artemis IV. New production RS-25 liquid-propellant engines will be used beginning with Artemis V. These new engines, which are in a final qualification test firing program at the time of writing, realize a cost savings of at least 30 percent and reduced production time due to streamlined manufacturing and advances in technology, including additive manufacturing. The evolved solid rocket boosters, which will debut on Artemis IX as part of the Block 2 variant, are in development now. In addition to propulsion updates, each variant of SLS maintains payload configuration flexibility and can fly crew-only, cargo-only, and crew-cargo combinations. This adaptability ensures that SLS, with its significant mass and volume capability – including the ability to launch large co-manifested payloads with Orion directly to trans-lunar injection (TLI) – can support the country’s most ambitious missions. Results from the Artemis I mission, as well as progress to the next flights and SLS variants, will be covered in the paper and presentation.

Bruce R. Askins↗
NASA NTRSDate not supplied

Successful First Flight of NASA’s SLS (Space Launch System) Super Heavy-Lift Rocket: Laying Groundwork for U. S.’s Most Ambitious Missions

In late 2022, NASA’s SLS (Space Launch System) super heavy-lift rocket launched for the first time. Artemis I sent an uncrewed Orion spacecraft on a 25.5-day round-trip mission to lunar orbit. The near-perfect performance laid the groundwork for the next flights and for NASA’s return of humans to the Moon. The SLS team is now preparing for the launch of Artemis II, which will be the first launch of astronauts to cislunar space since Apollo 17 in December 1972. In addition to preparations on the Artemis II launch vehicle, significant progress is being made on the hardware and software for future flights. Artemis II will include a test of a new military-grade GPS system, which will be fully utilized on Artemis III. Progress is also being made on the exploration upper stage (EUS) for the Block 1B SLS variant, which will debut on Artemis IV. New production RS-25 liquid-propellant engines will be used beginning with Artemis V. These new engines, which are in a final qualification test firing program at the time of writing, realize a cost savings of at least 30 percent and reduced production time due to streamlined manufacturing and advances in technology, including additive manufacturing. The evolved solid rocket boosters, which will debut on Artemis IX as part of the Block 2 variant, are in development now. In addition to propulsion updates, each variant of SLS maintains payload configuration flexibility and can fly crew-only, cargo-only, and crew-cargo combinations. This adaptability ensures that SLS, with its significant mass and volume capability – including the ability to launch large co-manifested payloads with Orion directly to trans-lunar injection (TLI) – can support the country’s most ambitious missions. Results from the Artemis I mission, as well as progress to the next flights and SLS variants, will be covered in the paper and presentation.

Bruce Askins↗
NASA NTRS2002

Development and Flight Testing of an Adaptive Vehicle Health-Monitoring Architecture

On going development and testing of an adaptable vehicle health-monitoring architecture is presented. The architecture is being developed for a fleet of vehicles. It has three operational levels: one or more remote data acquisition units located throughout the vehicle; a command and control unit located within the vehicle, and, a terminal collection unit to collect analysis results from all vehicles. Each level is capable of performing autonomous analysis with a trained expert system. The expert system is parameterized, which makes it adaptable to be trained to both a user's subject reasoning and existing quantitative analytic tools. Communication between all levels is done with wireless radio frequency interfaces. The remote data acquisition unit has an eight channel programmable digital interface that allows the user discretion for choosing type of sensors; number of sensors, sensor sampling rate and sampling duration for each sensor. The architecture provides framework for a tributary analysis. All measurements at the lowest operational level are reduced to provide analysis results necessary to gauge changes from established baselines. These are then collected at the next level to identify any global trends or common features from the prior level. This process is repeated until the results are reduced at the highest operational level. In the framework, only analysis results are forwarded to the next level to reduce telemetry congestion. The system's remote data acquisition hardware and non-analysis software have been flight tested on the NASA Langley B757's main landing gear. The flight tests were performed to validate the following: the wireless radio frequency communication capabilities of the system, the hardware design, command and control; software operation and, data acquisition, storage and retrieval.

Woodard, Stanley E.↗
NASA NTRS2021

System Validation on the Europa Clipper mission in Early Implementation Phase

NASA’s next flag-ship mission - Europa Clipper, will embark on a journey to Jupiter’s icy moon Europa in 2024 to assess its environment and habitability with a highly capable spacecraft. Post Jupiter-Orbit-Insertion, the spacecraft will be commanded to perform intricate, yet meticulously planned Europa flybys to perform science investigations using a suite of instruments, while withstanding Jupiter’s harsh radiation environment. The success of this mission is dependent on a well-coordinated project and its elements such as the flight hardware and software, the ground support and mission operations teams, procedures and other cross-cutting elements. The Europa Clipper project needs to ensure that these elements are realized at a reasonable confidence level prior to launch and other mission critical events. System Validation test and analysis activities exercise and confirm the integrity of the system of all project elements in the expected flight environment with reasonable stressing conditions. These activities go beyond system design requirements verification and are driven by validation objectives that describe the end-to-end functional and operational capabilities required during nominal and off-nominal flight-like scenarios and critical events. The challenges associated with validating that the Europa Clipper project as a whole can function and perform correctly to meet the intended mission objectives with the as-delivered capabilities of all of its elements are daunting. This paper discusses the systematic methodology established in the early implementation phase of the Europa Clipper project for developing System Validation activities and their validation objectives, and addressing any validation-related challenges on the project. Approaches include decomposition of mission objectives using activity timelines in the Mission Design plan for developing nominal scenarios, use of fault trees for exploring off-nominal cases and system boundaries, and use of Model-based Systems Engineering (MBSE) tools for planning and prioritizing these activities.

Wang, Xu↗