Results for “engine” — Page 6

NASA NTRS1984

Data engineering systems: Computerized modeling and data bank capabilities for engineering analysis

The Data Engineering System (DES) is a computer-based system that organizes technical data and provides automated mechanisms for storage, retrieval, and engineering analysis. The DES combines the benefits of a structured data base system with automated links to large-scale analysis codes. While the DES provides the user with many of the capabilities of a computer-aided design (CAD) system, the systems are actually quite different in several respects. A typical CAD system emphasizes interactive graphics capabilities and organizes data in a manner that optimizes these graphics. On the other hand, the DES is a computer-aided engineering system intended for the engineer who must operationally understand an existing or planned design or who desires to carry out additional technical analysis based on a particular design. The DES emphasizes data retrieval in a form that not only provides the engineer access to search and display the data but also links the data automatically with the computer analysis codes.

Kopp, H.↗

NASA NTRS1989

LEADER - An integrated engine behavior and design analyses based real-time fault diagnostic expert system for Space Shuttle Main Engine (SSME)

The LEADER expert system has been developed for automatic learning tasks encompassing real-time detection, identification, verification, and correction of anomalous propulsion system operations, using a set of sensors to monitor engine component performance to ascertain anomalies in engine dynamics and behavior. Two diagnostic approaches are embodied in LEADER's architecture: (1) learning and identifying engine behavior patterns to generate novel hypotheses about possible abnormalities, and (2) the direction of engine sensor data processing to perform resoning based on engine design and functional knowledge, as well as the principles of the relevant mechanics and physics.

Gupta, U. K.↗

NASA NTRS1990

Status report on a real time Engine Diagnostics Console for rocket engine exhaust plume monitoring

This paper describes the work done on the Engine Diagnostics Console during the past year of development at Stennis Space Center. The Engine Diagnostics Console (EDC) is a hardware and software package which provides near real time monitoring of rocket engine exhaust plume emissions during ground testing. The long range goal of the EDC development program is to develop an instrument that can detect engine degradation leading to catastrophic failure, and respond by taking preventative measures. The immediate goal for the past year's effort is the ability to process spectral data, taken from a rocket engine's exhaust plume, and to identify in an automated and high speed manner, the elemental species and multielemental materials that are present in the exhaust plume.

Bircher, F. E.↗

NASA NTRS1928

Combustion time in the engine cylinder and its effect on engine performance

As part of a general program to study combustion in the engine cylinder and to correlate the phenomena of combustion with the observed performance of actual engines, this paper presents a sketchy outline of what may happen in the engine cylinder during the burning of a charge. It also suggests the type of information needed to supply the details of the picture and points out how combustion time and rate affect the performance of the engine. A theoretical concept of a flame front which is assumed to advance radially from the point of ignition is presented, and calculations based on the area and velocity of this flame and the density of the unburned gases are made to determine the mass rate of combustion. From this rate the mass which has been burned and the pressure at any instant during combustion are computed. This process is then reversed in an effort to determine actual rates of combustion and flame velocities from the pressures as recorded on indicator diagrams. The effects of different rates of combustion on engine performance are then discussed and the importance of proper spark advance is emphasized.

Marvin, Charles F , Jr↗

NASA NTRS1939

Correction of Temperatures of Air-Cooled Engine Cylinders for Variation in Engine and Cooling Conditions

Factors are obtained from semiempirical equations for correcting engine-cylinder temperatures for variation in important engine and cooling conditions. The variation of engine temperatures with atmospheric temperature is treated in detail, and correction factors are obtained for various flight and test conditions, such as climb at constant indicated air speed, level flight, ground running, take-off, constant speed of cooling air, and constant mass flow of cooling air. Seven conventional air-cooled engine cylinders enclosed in jackets and cooled by a blower were tested to determine the effect of cooling-air temperature and carburetor-air temperature on cylinder temperatures. The cooling air temperature was varied from approximately 80 degrees F. to 230 degrees F. and the carburetor-air temperature from approximately 40 degrees F. to 160 degrees F. Tests were made over a large range of engine speeds, brake mean effective pressures, and pressure drops across the cylinder. The correction factors obtained experimentally are compared with those obtained from the semiempirical equations and a fair agreement is noted.

Schey, Oscar W↗

NASA NTRS1988

Software engineering as an engineering discipline

The following topics are discussed in the context of software engineering: early use of the term; the 1968 NATO conference; Barry Boehm's definition; four requirements fo software engineering; and additional criteria for software engineering. Additionally, the four major requirements for software engineering--computer science, mathematics, engineering disciplines, and excellent communication skills--are discussed. The presentation is given in vugraph form.

Berard, Edward V.↗

NASA NTRS1994

Two Rotor Stratified Charge Rotary Engine (SCRE) Engine System Technology Evaluation

This report summarizes results of an evaluation of technology enablement component technologies as integrated into a two rotor Stratified Charge Rotary Engine (SCRE). The work constitutes a demonstration of two rotor engine system technology, utilizing upgraded and refined component technologies derived from prior NASA Contracts NAS3-25945, NAS3-24628 and NAS-23056. Technical objectives included definition of, procurement and assembly of an advanced two rotor core aircraft engine, operation with Jet-A fuel at Take-Off rating of 340 BHP (254kW) and operation at a maximum cruise condition of 255 BHP (190kW), 75% cruise. A fuel consumption objective of 0.435 LBS/BHP-Hr (265 GRS/kW-Hr) was identified for the maximum cruise condition. A critical technology component item, a high speed, unit injector fuel injection system with electronic control was defined, procured and tested in conjunction with this effort. The two rotor engine configuration established herein defines an affordable, advanced, Jet-A fuel capability core engine (not including reduction gear, propeller shaft and some aircraft accessories) for General Aviation of the mid-1990's and beyond.

Hoffman, T.↗

NASA NTRS1959

Engine Operating Conditions that Cause Thermal-Fatigue Cracks in Turbojet-Engine Buckets

Five engine tests were conducted to definitely establish the failure mechanism of leading-edge cracking and to determine which conditions of engine operation cause the failures. Five groups of S-616 and M-252 buckets from master lots were run consecutively in the same J47-25 engine. The tests included a steady-state run at full-power conditions, rapid cycling between idle and rated speed, and three different start-stop tests. The first start-stop test consisted of cycles of start and stop with 5 minutes of idle speed before each stop; the second included cycles of start and stop but with 15 minutes of rated speed before each stop; the third consisted of cycles of gradual starts and normal stops with 5 minutes at idle speed before each stop. The test results demonstrated that the primary cause of leading-edge cracking was thermal fatigue produced by repeated engine starts. The leading edge of the bucket experiences plastic flow in compression during starts and consequently is subjected to a tensile stress when the remainder of the bucket becomes heated and expands. Crack initiation was accelerated when rated-speed operation was added to each normal start-stop cycle. This acceleration of crack formation was attributed to localized creep damage and perhaps to embrittlement resulting from overaging. It was demonstrated that leading-edge cracking can be prevented simply by starting the engine gradually.

Johnston, James R.↗

NASA NTRS1999

High Reliability Engine Control Demonstrated for Aircraft Engines

For a dual redundant-control system, which is typical for short-haul aircraft, if a failure is detected in a control sensor, the engine control is transferred to a safety mode and an advisory is issued for immediate maintenance action to replace the failed sensor. The safety mode typically results in severely degraded engine performance. The goal of the High Reliability Engine Control (HREC) program was to demonstrate that the neural-network-based sensor validation technology can safely operate an engine by using the nominal closed-loop control during and after sensor failures. With this technology, engine performance could be maintained, and the sensor could be replaced as a conveniently scheduled maintenance action.

Guo, Ten-Huei↗

NASA NTRS2004

NASA Glenn's Engine Components Research Lab, Cell 2B, Reactivated to Support the U.S. Army Research Laboratory T700 Engine Test

The U.S. Army Vehicle Technology Directorate at the NASA Glenn Research Center has been directed by their parent command, the U.S. Army Research Laboratory (ARL), to demonstrate active stall technology in a turboshaft engine as the next step in transitioning this technology to the Army and aerospace industry. Therefore, the Vehicle Technology Directorate requested the reactivation of Glenn's Engine Components Research Lab, Cell 2B, (ECRL 2B). They wanted to test a T700 engine that had been used previously for turboshaft engine research as a partnership between the Army and NASA on small turbine engine research. ECRL 2B had been placed in standby mode in 1997. Glenn's Testing Division initiated reactivation in May 2002 to support the new research effort, and they completed reactivation and improvements in September 2003.

Beltran, Luis R.↗

NASA NTRS2010

History and Benefits of Engine Level Testing Throughout the Space Shuttle Main Engine Program

Rocket engine testing is important throughout a program s life and is essential to the overall success of the program. Space Shuttle Main Engine (SSME) testing can be divided into three phases: development, certification, and operational. Development tests are conducted on the basic design and are used to develop safe start and shutdown transients and to demonstrate mainstage operation. This phase helps form the foundation of the program, demands navigation of a very steep learning curve, and yields results that shape the final engine design. Certification testing involves multiple engine samples and more aggressive test profiles that explore the boundaries of the engine to vehicle interface requirements. The hardware being tested may have evolved slightly from that in the development phase. Operational testing is conducted with mature hardware and includes acceptance testing of flight assets, resolving anomalies that occur in flight, continuing to expand the performance envelope, and implementing design upgrades. This paper will examine these phases of testing and their importance to the SSME program. Examples of tests conducted in each phase will also be presented.

VanHooser, Katherine↗

NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

Iwata, Curtis↗

NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

MODEL↗

NASA NTRS2016

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

This document is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

Steven R Hirshorn↗

NASA NTRS2014

An Integrated Architecture for Aircraft Engine Performance Monitoring and Fault Diagnostics: Engine Test Results

This paper presents a model-based architecture for performance trend monitoring and gas path fault diagnostics designed for analyzing streaming transient aircraft engine measurement data. The technique analyzes residuals between sensed engine outputs and model predicted outputs for fault detection and isolation purposes. Diagnostic results from the application of the approach to test data acquired from an aircraft turbofan engine are presented. The approach is found to avoid false alarms when presented nominal fault-free data. Additionally, the approach is found to successfully detect and isolate gas path seeded-faults under steady-state operating scenarios although some fault misclassifications are noted during engine transients. Recommendations for follow-on maturation and evaluation of the technique are also presented.

propulsion system performance↗

NASA NTRS2014

An Integrated Architecture for Aircraft Engine Performance Monitoring and Fault Diagnostics: Engine Test Results

This paper presents a model-based architecture for performance trend monitoring and gas path fault diagnostics designed for analyzing streaming transient aircraft engine measurement data. The technique analyzes residuals between sensed engine outputs and model predicted outputs for fault detection and isolation purposes. Diagnostic results from the application of the approach to test data acquired from an aircraft turbofan engine are presented. The approach is found to avoid false alarms when presented nominal fault-free data. Additionally, the approach is found to successfully detect and isolate gas path seeded-faults under steady-state operating scenarios although some fault misclassifications are noted during engine transients. Recommendations for follow-on maturation and evaluation of the technique are also presented.

propulsion system performance↗

NASA NTRS2015

An Integrated Architecture for Aircraft Engine Performance Monitoring and Fault Diagnostics: Engine Test Results

This paper presents a model-based architecture for performance trend monitoring and gas path fault diagnostics designed for analyzing streaming transient aircraft engine measurement data. The technique analyzes residuals between sensed engine outputs and model predicted outputs for fault detection and isolation purposes. Diagnostic results from the application of the approach to test data acquired from an aircraft turbofan engine are presented. The approach is found to avoid false alarms when presented nominal fault-free data. Additionally, the approach is found to successfully detect and isolate gas path seeded-faults under steady-state operating scenarios although some fault misclassifications are noted during engine transients. Recommendations for follow-on maturation and evaluation of the technique are also presented.

systems health monitoring↗

DOE OSTI2026

Data for Metabolic Engineering of Nonmodel Yeast Issatchenkia orientalis SD108 for 5-Aminolevulinic Acid Production

Biological production of 5‐aminolevulinic acid (5‐ALA) has received growing attentionover theyears.However, thereis the tradeoff between 5‐ALA biosynthesis and cell growth because the fermentation broth will become acidic due to the production of 5‐ALA. To address this limitation, we engineered an acid‐tolerant yeast, Issatchenkia orientalis SD108, for 5‐ALA production. We first discovered that the cell growth rate of I. orientalis SD108 was boosted by 5‐ALA and its endogenous ALA synthetase (ALAS) showed higher activity than those homologs from other yeasts. The titer of 5‐ALA was improved from 28mg/L to 120‐, 150‐, and 300mg/L, by optimizing plasmid design, overexpressing a transporter, and increasing gene copy number, respectively. After redirecting the metabolic flux using the pyruvate decarboxylase (PDC) knockout strain (SD108ΔPDC) and culturing with urea, we increased the titer of 5‐ALA to 510mg/L, a 13‐fold enhancement, proving the importance of the newly identified IoALAS with higher activity and the strategic selection of nitrogen sources for knockout strains. This study demonstrates the acid‐tolerant I. orientalis SD108ΔPDC has a high potential for 5‐ALA production at a large scale in the future.

Bioproducts↗