SEARCH · Search NASA

Results for “ENGINES - SPEED”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 469 records · Page 26

All sources NASA NTRS DOE OSTI

NASA NTRS1996

Wave Engine Topping Cycle Assessment

The performance benefits derived by topping a gas turbine engine with a wave engine are assessed. The wave engine is a wave rotor that produces shaft power by exploiting gas dynamic energy exchange and flow turning. The wave engine is added to the baseline turboshaft engine while keeping high-pressure-turbine inlet conditions, compressor pressure ratio, engine mass flow rate, and cooling flow fractions fixed. Related work has focused on topping with pressure-exchangers (i.e., wave rotors that provide pressure gain with zero net shaft power output); however, more energy can be added to a wave-engine-topped cycle leading to greater engine specific-power-enhancement The energy addition occurs at a lower pressure in the wave-engine-topped cycle; thus the specific-fuel-consumption-enhancement effected by ideal wave engine topping is slightly lower than that effected by ideal pressure-exchanger topping. At a component level, however, flow turning affords the wave engine a degree-of-freedom relative to the pressure-exchanger that enables a more efficient match with the baseline engine. In some cases, therefore, the SFC-enhancement by wave engine topping is greater than that by pressure-exchanger topping. An ideal wave-rotor-characteristic is used to identify key wave engine design parameters and to contrast the wave engine and pressure-exchanger topping approaches. An aerodynamic design procedure is described in which wave engine design-point performance levels are computed using a one-dimensional wave rotor model. Wave engines using various wave cycles are considered including two-port cycles with on-rotor combustion (valved-combustors) and reverse-flow and through-flow four-port cycles with heat addition in conventional burners. A through-flow wave cycle design with symmetric blading is used to assess engine performance benefits. The wave-engine-topped turboshaft engine produces 16% more power than does a pressure-exchanger-topped engine under the specified topping constraints. Positive and negative aspects of wave engine topping in gas turbine engines are identified.

Welch, Gerard E.↗

NASA NTRS2001

Solar-Thermal Engine Testing

A solar-thermal engine serves as a high-temperature solar-radiation absorber, heat exchanger, and rocket nozzle. collecting concentrated solar radiation into an absorber cavity and transferring this energy to a propellant as heat. Propellant gas can be heated to temperatures approaching 4,500 F and expanded in a rocket nozzle, creating low thrust with a high specific impulse (I(sub sp)). The Shooting Star Experiment (SSE) solar-thermal engine is made of 100 percent chemical vapor deposited (CVD) rhenium. The engine 'module' consists of an engine assembly, propellant feedline, engine support structure, thermal insulation, and instrumentation. Engine thermal performance tests consist of a series of high-temperature thermal cycles intended to characterize the propulsive performance of the engines and the thermal effectiveness of the engine support structure and insulation system. A silicone-carbide electrical resistance heater, placed inside the inner shell, substitutes for solar radiation and heats the engine. Although the preferred propellant is hydrogen, the propellant used in these tests is gaseous nitrogen. Because rhenium oxidizes at elevated temperatures, the tests are performed in a vacuum chamber. Test data will include transient and steady state temperatures on selected engine surfaces, propellant pressures and flow rates, and engine thrust levels. The engine propellant-feed system is designed to Supply GN2 to the engine at a constant inlet pressure of 60 psia, producing a near-constant thrust of 1.0 lb. Gaseous hydrogen will be used in subsequent tests. The propellant flow rate decreases with increasing propellant temperature, while maintaining constant thrust, increasing engine I(sub sp). In conjunction with analytical models of the heat exchanger, the temperature data will provide insight into the effectiveness of the insulation system, the structural support system, and the overall engine performance. These tests also provide experience on operational aspects of the engine and associated subsystems, and will include independent variation of both steady slate heat-exchanger temperature prior to thrust operation and nitrogen inlet pressure (flow rate) during thrust operation. Although the Shooting Star engines were designed as thermal-storage engines to accommodate mission parameters, they are fully capable of operating as scalable, direct-gain engines. Tests are conducted in both operational modes. Engine thrust and propellant flow rate will be measured and thereby I(sub sp). The objective of these tests is to investigate the effectiveness of the solar engine as a heat exchanger and a rocket. Of particular interest is the effectiveness of the support structure as a thermal insulator, the integrity of both the insulation system and the insulation containment system, the overall temperature distribution throughout the engine module, and the thermal power required to sustain steady state fluid temperatures at various flow rates.

Tucker, Stephen↗

NASA NTRS2005

Key Reliability Drivers of Liquid Propulsion Engines and A Reliability Model for Sensitivity Analysis

This paper is to address the in-flight reliability of a liquid propulsion engine system for a launch vehicle. We first establish a comprehensive list of system and sub-system reliability drivers for any liquid propulsion engine system. We then build a reliability model to parametrically analyze the impact of some reliability parameters. We present sensitivity analysis results for a selected subset of the key reliability drivers using the model. Reliability drivers identified include: number of engines for the liquid propulsion stage, single engine total reliability, engine operation duration, engine thrust size, reusability, engine de-rating or up-rating, engine-out design (including engine-out switching reliability, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction), propellant specific hazards, engine start and cutoff transient hazards, engine combustion cycles, vehicle and engine interface and interaction hazards, engine health management system, engine modification, engine ground start hold down with launch commit criteria, engine altitude start (1 in. start), Multiple altitude restart (less than 1 restart), component, subsystem and system design, manufacturing/ground operation support/pre and post flight check outs and inspection, extensiveness of the development program. We present some sensitivity analysis results for the following subset of the drivers: number of engines for the propulsion stage, single engine total reliability, engine operation duration, engine de-rating or up-rating requirements, engine-out design, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction, and engine health management system implementation (basic redlines and more advanced health management systems).

Huang, Zhao-Feng↗

NASA NTRS1995

Research project for increasing pool of minority engineers

The Tennessee State University (TSU) Research Project for Increasing the Pool of Minority Engineers is designed to develop engineers who have academic and research experiences in technical areas of interest to NASA. These engineers will also have some degree of familiarity with NASA Lewis Research Center as a result of interaction with Lewis engineers, field trips and internships at Lewis. The Research Project has four components, which are: (1) Minority Introduction to Engineering (MITE), a high school precollege program, (2) engineering and technology previews, (3) the NASA LeRC Scholars program which includes scholarships and summer internships, and (4) undergraduate research experiences on NASA sponsored research. MITE is a two-week summer engineering camp designed to introduce minority high school students to engineering by exposing them to: (1) engineering role models (engineering students and NASA engineer), (2) field trips to engineering firms, (3) in addition to introducing youth to the language of the engineer (i.e., science, mathematics, technical writing, computers, and the engineering laboratory). Three MITE camps are held on the campus of TSU with an average of 40 participants. MITE has grown from 25 participants at its inception in 1990 to 118 participants in 1994 with participants from 17 states, including the District of Columbia, and 51 percent of the participants were female. Over the four-year period, 77 percent of the seniors who participated in MITE have gone to college, while 53 percent of those seniors in college are majoring in science, engineering or mathematics (SEM). This first Engineering and Technology Previews held in 1993 brought 23 youths from Cleveland, Ohio to TSU for a two-day preview of engineering and college life. Two previews are scheduled for 1994-1995. The NASA LeRC Scholars program provides scholarships and summer internships for minority engineering students majoring in electrical or mechanical engineering. Presently six (6) engineering students are in the Scholars program. The average GPA for the scholars is 3.239. Each scholar must maintain a minimum GPA of 3.000/4.000. NASA LeRC Fred Higgs has been awarded a GEM Fellowship. In addition, he will be presenting a paper entitled 'Design of Helical Spring Using Probabilistic Design Methodology' at the Middle Tennessee Section ASME Student Design Presentations in Nashville on March 23rd and at the National Conference on Undergraduate Research to be held at Union College, Schenectady, New York on April 20-22, 1995. Each of the scholars is working on one of the three NASA sponsored research projects in the college.

Rogers, Decatur B.↗

NASA NTRS2017

A Dynamic Model for the Evaluation of Aircraft Engine Icing Detection and Control-Based Mitigation Strategies

Aircraft flying in regions of high ice crystal concentrations are susceptible to the buildup of ice within the compression system of their gas turbine engines. This ice buildup can restrict engine airflow and cause an uncommanded loss of thrust, also known as engine rollback, which poses a potential safety hazard. The aviation community is conducting research to understand this phenomena, and to identify avoidance and mitigation strategies to address the concern. To support this research, a dynamic turbofan engine model has been created to enable the development and evaluation of engine icing detection and control-based mitigation strategies. This model captures the dynamic engine response due to high ice water ingestion and the buildup of ice blockage in the engines low pressure compressor. It includes a fuel control system allowing engine closed-loop control effects during engine icing events to be emulated. The model also includes bleed air valve and horsepower extraction actuators that, when modulated, change overall engine operating performance. This system-level model has been developed and compared against test data acquired from an aircraft turbofan engine undergoing engine icing studies in an altitude test facility and also against outputs from the manufacturers customer deck. This paper will describe the model and show results of its dynamic response under open-loop and closed-loop control operating scenarios in the presence of ice blockage buildup compared against engine test cell data. Planned follow-on use of the model for the development and evaluation of icing detection and control-based mitigation strategies will also be discussed. The intent is to combine the model and control mitigation logic with an engine icing risk calculation tool capable of predicting the risk of engine icing based on current operating conditions. Upon detection of an operating region of risk for engine icing events, the control mitigation logic will seek to change the engines operating point to a region of lower risk through the modulation of available control actuators while maintaining the desired engine thrust output. Follow-on work will assess the feasibility and effectiveness of such control-based mitigation strategies.

engine control↗

NASA NTRS2017

A Dynamic Model for the Evaluation of Aircraft Engine Icing Detection and Control-Based Mitigation Strategies

engine control↗

NASA NTRS2001

Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.

Trevino, Luis↗

NASA NTRS2006

Engine Development Design Margins Briefing Charts

New engines experience durability problems after entering service. The most prevalent and costly is the hot section, particularly the high-pressure turbine. The origin of durability problems can be traced back to: 1) the basic aero-mechanical design systems, assumptions, and design margins used by the engine designers, 2) the available materials systems, and 3) to a large extent, aggressive marketing in a highly competitive environment that pushes engine components beyond the demonstrated capability of the basic technology available for the hardware designs. Unfortunately the user must operate the engine in the service environment in order to learn the actual thrust loading and the time at max effort take-off conditions used in service are needed to determine the hot section life. Several hundred thousand hours of operational service will be required before the demonstrated reliability of a fleet of engines or the design deficiencies of the engine hot section parts can be determined. Also, it may take three to four engine shop visits for heavy maintenance on the gas path hardware to establish cost effective build standards. Spare parts drive the oerator's engine maintenance costs but spare parts also makes lots of money for the engine manufacturer during the service life of an engine. Unless competition prevails for follow-on engine buys, there is really no motivation for an OEM to spend internal money to improve parts durability and reduce earnings derived from a lucrative spare parts business. If the hot section life is below design goals or promised values, the OEM migh argue that the engine is being operated beyond its basic design intent. On the other hand, the airframer and the operator will continue to remind the OEM that his engine was selected based on a lot of promises to deliver spec thrust with little impact on engine service life if higher thrust is used intermittently. In the end, a standoff prevails and nothing gets fixed. This briefing will propose ways to hold competing engine manufacturers more accountable for engine hot section design margins during the entire Engine Development process as well as provide tools to assess the design temperature margins in the hot section parts of Service Engines.

Bentz, Chuck↗

DOE OSTI2023

Cyber-Informed Engineering Implementation Guide

This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system’s lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.

42 ENGINEERING↗

DOE OSTI2023

Cyber-Informed Engineering Implementation Guide: Version 1.0 [Slides]

This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system's lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements - but does not replace - the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system's engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.

24 POWER TRANSMISSION AND DISTRIBUTION↗

NASA NTRS1988

Component improvement of free-piston Stirling engine key technology for space power

The successful performance of the 25 kW Space Power Demonstrator (SPD) engine during an extensive testing period has provided a baseline of free piston Stirling engine technology from which future space Stirling engines may evolve. Much of the success of the engine was due to the initial careful selection of engine materials, fabrication and joining processes, and inspection procedures. Resolution of the few SPD engine problem areas that did occur has resulted in the technological advancement of certain key free piston Stirling engine components. Derivation of two half-SPD, single piston engines from the axially opposed piston SPD engine, designated as Space Power Research (SPR) engines, has made possible the continued improvement of these engine components. The two SPR engines serve as test bed engines for testing of engine components. Some important fabrication and joining processes are reviewed. Also, some component deficiencies that were discovered during SPD engine testing are described and approaches that were taken to correct these deficiencies are discussed. Potential component design modifications, based upon the SPD and SPR engine testing, are also reported.

Alger, Donald L.↗

DOE OSTI2023

Cyber-Informed Engineering Principles: What’s in it for me?

CIE is an emerging method to integrate cybersecurity considerations into the conception, design, development, and operation of any physical system that has digital connectivity, monitoring, or control. CIE complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Rather, it expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve, and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences. Engineers and technicians that design critical energy infrastructure installations can integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. These principles are aimed at system or design engineers, operators, and technicians, rather than software engineers or operational cybersecurity practitioners, because the engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. This approach creates new opportunities for engineering teams—and not just cybersecurity teams—to secure the system using the physics and mechanics of engineering controls—not just digital monitoring and controls.

99 GENERAL AND MISCELLANEOUS↗

NASA NTRS2009

Rocketdyne - Lunar Ascent Engine

The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).

Harmon, Tim↗

NASA NTRSDate not supplied

Pilot Controls for a Hybrid Turbine-Electric 17 Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This paper details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

NASA NTRSDate not supplied

Pilot Controls for a Hybrid Turbine-Electric 17-Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This presentation details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

DOE OSTI2023

Engineering Computational Practices (Rev. 1)

This manual will attempt to motivate the use of an automated build system for the purposes of computational science and engineering. As part of this motivation, the surrounding computational practices of version control, documen tation, compute environment management, and regression testing will also be addressed as applied to the practice of computational engineering. Specifically, this manual intends to motivate the adoption of these traditional software engineering practices for use in research and production engineering simulation projects. This manual is not the first such effort in the greater scientific computing community. In fact, the authors relied heavily on the lesson plans of the Software Carpentry, established to teach computing skills to researchers in 1998. As the intention for this manual is to lay out fundamental practices of engineering computing, it will not attempt to fully teach the underlying concepts and will instead reference the well designed lesson plans of the Software Carpentry. Where possible, this manual will explain to general computing practices and concepts and limit discussion of specific software implementations to examples or vehicles for practice in concrete application. The specific software taught by the Software Carpentry curriculum is an excellent starting point to learn the core concepts of computational engi neering. However, the authors have found that applications to engineering simulation and analysis require translation of these software development concepts into the language and workflows of computational engineers. Adopting these computational tools may require engineers to re-imagine their workflows in some combination of traditional engineer ing and software concepts. It has also been necessary to extend existing software build systems for engineering practices beyond the simple wrap ping of engineering software execution. Where necessary, examples of specific software and their method of extension to engineering simulations will be given, with reference to the User Manual for recommended practical use. Where this manual relies on specific implementation examples, it should be understood that the practicing engineer may find that different software is more amenable to their specific work. It is always the overall collection of computational practices is more important than any specific software implementation. The ability to recognize which concepts are implemented by a software package will make a practicing engineer agile to changing project needs, computing resources, numeric solvers, programming languages, and even available funding.

42 ENGINEERING↗

DOE OSTI2020

Supercritical Reforming of Wet Ethanol for High Efficiency Direct-injection Heavy-duty Compression-ignition Engines

The purpose of the research was to investigate the potential of using a mature bio-fuel in heavy-duty compression ignition engines. By co-optimizing both the fuel characteristics and engine system the potential for a superior outcome was demonstrated. The use of wet bio-ethanol eliminates the majority of the energy intensive distilling and dehydrating fuel production processes, which moves the fuel towards carbon neutral and also lowers the fuel costs. The relatively high water content of the resulting fuel is leveraged in the proposed novel combustion system by incorporating an integrated high efficiency exhaust waste heat recovery system. This results in significantly higher thermal efficiency. In addition the combustion system features low criteria pollutant emissions and the potential to reduce the initial cost of the engine system hardware. Substantial societal benefits are demonstrated through the co-optimization of the fuel and engine system. A computational proof-of-concept study has been performed to demonstrate the potential benefits of a novel wet ethanol heavy-duty compression ignition combustion system featuring integrated exhaust waste heat recovery. A combined in-cylinder closed cycle 3D computational fluid dynamics (CFD) - 1D engine system simulation approach was used. The models were validated to baseline engine data using diesel fuel and then applied to the wet ethanol study. The original concept was to maximize exhaust waste heat recovery through supercritical reforming of the wet ethanol fuel. Phase I simulation results indicated that the optimal solution for maximum engine efficiency gains were realized through maximizing thermo-mechanical recuperation with negligible fuel reformation. The results show the potential to achieve impressive gains in brake thermal efficiency (BTE) over the base diesel engine. The potential to increase BTE up to 20.9% over the base diesel engine was demonstrated, with even larger gains possible through reduced in-cylinder heat transfer losses. The majority of the efficiency gains were realized through integrated high efficiency exhaust waste heat recovery. The concept also has the potential to achieve future ultra-low NO x emissions standards and negligible engine-out soot emissions. The mixing controlled combustion of high temperature wet ethanol features relatively low engine-out NO x emissions without the need for exhaust gas recirculation (EGR). The soot free combustion enabled by the relatively high oxygen content of ethanol also allows for the use of stoichiometric mixing controlled combustion, which is not practical with diesel fuel. When stoichiometric combustion is used a simple passive 3-way catalyst can be used for exhaust emissions after-treatment and near zero tailpipe emissions. The Phase I simulations results have defined the system layout and requirements in preparation for the Phase II experimental proof-of-concept study. The potential applications of the research include most current applications of diesel engines. The Phase I study focused on heavy-duty on-highway class 8 trucks. However, virtually any application that requires highly efficient clean power generation would benefit from the novel engine system proposed. The results indicate substantial fuel cost savings and reduced greenhouse gas emissions with similar or reduced initial system hardware costs compared to modern diesel engine systems.

09 BIOMASS FUELS↗

DOE OSTI2022

Coupling a Lagrangian–Eulerian Spark-Ignition (LESI) model with LES combustion models for engine simulations

In the United States transportation sector, Light-Duty Vehicles (LDVs) are the largest energy consumers and CO 2 emitters. Electrification of LDVs is posed as a potential solution, but SI engines can still contribute to decarbonization. Car manufacturers have turned to unconventional engine operation to increase the efficiency of Spark-Ignition (SI) engines and reduce the carbon emissions of their fleets. Dilute, lean, and stratified-charge engine operation has the potential for engine efficiency improvements at the expense of increased cyclic variability and combustion instability. At such demanding engine conditions, the spark ignition event is key for flame initiation and propagation and for enhanced combustion stability. Reliable and accurate spark ignition models can help design ignition systems that reduce cyclic variability. Multiple computational spark-ignition models exist that perform well under conventional conditions, but the underlying physics needs to be expanded, for unconventional engine operation. In this paper, a hybrid Lagrangian–Eulerian Spark-Ignition (LESI) model is coupled with different turbulent flame propagation models for engine simulations. LESI relies on Lagrangian arc tracking and Eulerian energy deposition. The LESI model is coupled with the Well-Stirred Reactor (WSR), Thickened Flame Model (TFM), and g-equation model and used to simulate several cycles of a Direct-Injection Spark-Ignition (DISI) engine using a commercial Computational Fluid Dynamics (CFD) engine solver. The results showcase the successful coupling of LESI with the combustion models. Global engine metrics, such as pressure and Apparent Heat Release Rate (AHRR), for each simulation setup are compared to experimental engine results, for validation. In addition, results highlight the successful prediction of spark channel movement by comparing simulation images to experimental optical engine images. Finally, the successful coupling of LESI to combustion models, making it a usable model in the engine modeling community, is emphasized and future development details are discussed.

33 ADVANCED PROPULSION SYSTEMS↗