Turbine Performance Characteristics of a Python Turbine-propeller Engine Investigated in Altitude Wind Tunnel
Explore the source record for details and available documents.
SEARCH · Engineering Papers
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.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Cost and case analyzer components of the FUSED-Wind software. These are small pieces of code which define interfaces between software in order to do wind plant cost of energy on the one hand and analysis of load cases for an aeroelastic code on the other.
A wind tunnel investigation of the engine exhaust and windstream flow interaction on a gunship helicopter model was conducted in the Langley V/STOL tunnel. The investigation utilized a flow visualization technique employing neutrally buoyant helium filled bubbles to determine the cause of exhaust shield overheating during cruising flight and to evaluate means of eliminating the problem. The flow patterns were recorded with still cameras and on television magnetic tape. Exhaust flow impingement on the exhaust shield during cruise was found to cause the problem. Several flow altering devices were evaluated to find suitable ways to correct the problem. A flow deflector located on the model cowling upstream of the exhaust provides an effective solution.
This paper presents a parametric sensitivity analysis of the Space Shuttle Ascent flight to the wind profile. Engineering systems parameters are obtained by flight simulations using wind profile models and samples of detailed (Jimsphere) wind profile measurements. The wind models used are the synthetic vector wind model, with and without the design gust, and a model of the vector wind change with respect to time. From these comparison analyses an insight is gained on the contribution of winds to ascent subsystems flight parameters.
Motivated by the need to develop reference wind energy systems for optimisation and technology assessment studies, the International Energy Agency Wind Task 37 on Wind Energy Systems Engineering is developing a reference offshore wind power plant at the Dutch offshore wind energy areas Borssele III and IV. This work presents a comparison between two approaches for developing the preliminary design of an offshore wind plant turbine layout, electrical collection system, and support structures. The first is a sequential approach, where components of the wind farm are optimised sequentially, each with its own objective function, thus neglecting potential interactions between them. The second approach uses Multidisciplinary Design Analysis and Optimisation (MDAO), where all components are jointly optimised with the overall system levelised cost of energy (LCOE) as a global objective function. Studying the cases of regular and irregular layouts, the integrated approach always shows a greater improvement in the LCOE of the final design compared to the design resulting from the traditional sequential approach. The most significant trade-off exploited by the MDAO approach used in this study is between losses in energy production due to turbine wake effects and the costs of electrical cable infrastructure.
Wind tunnel investigations were performed to determine the performance properties of an axial-flow gas turbine-propeller engine II. Windmilling characteristics were determined for a range of altitudes from 5000 to 35,000 feet, true airspeeds from 100 to 273 miles per hour, and propeller blade angles from 4 degrees to 46 degrees.
The predictive simulation of the dynamics of modern wind turbines and wind farms is a high-performance-computing (HPC) grand challenge. Modern wind turbines are the largest rotating machines in the world, with rotor diameters exceeding 200 meters, and with heights well into the atmospheric boundary layer. To address this grand challenge, the U.S. Department of Energy (DOE) Wind Energy Technologies Office and the Exascale Computing Project have been supporting the creation of the ExaWind modeling and simulation environment since 2016. ExaWind is composed of the incompressible-flow computational-fluid-dynamics (CFD) solvers AMR-Wind and Nalu-Wind and the wind-turbine-dynamics solver OpenFAST. In our hybrid CFD approach, Nalu-Wind unstructured-grid models resolve the near-body flow around the turbine; those models are embedded in, and two-way coupled to, an AMR-Wind structured-grid mesh through overset meshes. In this talk I give an overview of ExaWind software stack and describe how it is being used to address important problems in wind energy.
An investigation has been conducted in the Cleveland altitude wind tunnel to determine the operational characteristics of the I-40 jet-propulsion engine over a range of pressure altitudes from 10,000 to 50,000 feet and ram-pressure ratios from 1.00 to 1.76. Engine operational data were obtained with the engine in the standard configuration and with various modifications of the fuel system, the electrical system, and the combustion chambers. The effects of altitude and airspeed on operating speed range, starting, windmilli.ng, acceleration, speed regulation, cooling, and vibration of the standard and modified engines were determined, and damage to parts was noted. Maximum engine speed was obtainable at all altitudes and airspeeds wi th each fuel-control system investigated. The minimum idling speed was raised by increases in altitude and airspeed. The lowest minimum stable speeds were obtained with the standard configuration using 40-gallon nozzles with individual metering plugs. The engine was started normally at altitudes as high as 20,000 feet with all of the fuel systems and ignition combinations except one. Ignition at 70,000 feet was difficult and, although successful ignition occurred, acceleration was slow and usually characterized by excessive tail-pipe temperature. During windmilling investigations of the engine equipped with the standard fuel system, the engine could not be started at ram-pressure ratios of 1.1 to 1.7 at altitudes of 10,000, 20,000 and 30,000 feet. When equipped with the production barometric and Monarch 40-gallon nozzles, the engine accelerated in 12 seconds from an engine speed of 6000 rpm to 11,000 rpm at 20,000 feet and an average tail-pipe temperature of 11000 F. At the same altitude and temperature, all the engine configurations had approximately the same rate of acceleration. The Woodward governor produced the safest accelerations, inasmuch as it could be adjusted to automatically prevent acceleration blow out. The engine speed was held constant by the Woodward governor and the Edwards regulator during simulated dives and climbs at constant throttle position. The bearing cooling system was satisfactory at all altitudes and airspeeds. The engines operated without serious failure, although the exhaust cone, the tail pipe, and the airplane fuselage were damaged during altitude starts.
During an aerospace engineer's undergraduate studies, he or she will attend classes in aerodynamics, thermodynamics, structures, stability and control, dynamics, design, propulsion, and computer science, along with the related courses in mathematics, physics, statistics, and chemistry required to understand the material. Upon graduation, the new engineer will have acquired a basic knowledge of how to build an aerospace vehicle. What only comes through experience, however, is the understanding of the inevitable imperfect process through which an aerospace vehicle is built. This is the adventure of turning a basic concept into functional hardware. Engineers working on a project must often deal with ambiguous situations. They are routinely asked by management to provide risk assessments of a project, yet even after careful analysis uncertainties remain. The project must be accomplished within finite limits of time and money. The question an engineer answers is whether the solution to potential problem is worth the cost and schedule delay, or if the solution might actually be worse than the problem it is meant to solve. Review protocols are established to ensure that an unknown has not been overlooked. But these cannot protect against an unknown unknown. Examples of these situations can be found in the history of the X-43A Hyper-X (Hypersonic Experiment) program. In this NASA project, a supersonic combustion ramjet (scramjet) engine was flight tested on a subscale vehicle. The X-43A Hyper-X Research Vehicle (HXRV) was launched from a B-52B mothership, then boosted to the test speed by a modified Pegasus rocket first stage, called the Hyper-X Launch Vehicle (HXLV). Once at the proper speed and altitude, the X-43A separated from the booster, stabilized itself, and then the engine test began. Although wind-tunnel scramjet engine tests had begun in the late 1950s, before the Hyper-X program there had never been an actual in-flight test of such an engine integrated with an appropriate airframe. Thus, while the scramjet had successfully operated in the artificial airflow of wind tunnels, the concept had yet to be proven in real air. These conditions meant changes in density and temperature, as well as changes in angle of attack and sideslip of a free-flying vehicle. A wind tunnel is limited in its ability to simulate these subtle factures, which have a major impact on almost any vehicle, but especially that of a scramjet's performance. The Hyper-X project was to provide a real-world benchmark of the ground test data. The full scale X-43A engine would be operated in the wind tunnel, and then flown, and the data from its operation would then be compared with projections. If these matched, the wind tunnel data would be considered a reliable design tool for future scramjet. If there were significant differences, the reasons for these would have to be identified. Until such information was available, scramjets would lack the technological maturity to be considered for future space launch or high-speed atmospheric flight vehicles.
FAST, developed by the National Renewable Energy Laboratory (NREL), is a computer-aided engineering (CAE) tool for aero-hydro-servo-elastic analysis of land-based and offshore wind turbines. This paper discusses recent upgrades made to FAST to enable loads simulations of offshore wind turbines with fixed-bottom, multimember support structures (e.g., jackets and tripods, which are commonly used in transitional-depth waters). The main theory and strategies for the implementation of the multimember substructure dynamics module (SubDyn) within the new FAST modularization framework are introduced. SubDyn relies on two main engineering schematizations: 1) a linear frame finite-element beam (LFEB) model and 2) a dynamics system reduction via Craig-Bampton's method. A jacket support structure and an offshore system consisting of a turbine atop a jacket substructure were simulated to test the SubDyn module and to preliminarily assess results against results from a commercial finite-element code.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
The performance of the 11-stage axial-flow compressor in the X24C-4B turbojet engine was analyzed on the basis of results obtained from an investigation of the complete engine in the NACA Cleveland altitude wind tunnel. The engine was operated with four, exhaust nozzles of different outlet area over a range of engine speeds from 6000 to 12,500 rpm, corrected engine speeds from approximately 6100 to 13,600 rpm, and compressor Mach numbers from 0.45 to 1.00. Data are presented for engine operation over a range of simulated altitudes from 15,000 to 45,000 feet and simulated flight Mach numbers from 0.24 to 1.08.
This presentation was given at the Wind Energy Systems Engineering Workshop.
Wind energy researchers typically share one key characteristic: a passion for increasing wind energy in the global energy mix. The U.S. Department of Energy (DOE) supports this mission in a number of ways including allocating funding directly to various aspects of wind energy research through the Office of Energy Efficiency and Renewable Energy (EERE) via the Wind Energy Technologies Office (WETO). While the traditional output of research is academic publication, software development efforts are increasingly a major focus. Software tools in the research environment allow researchers to describe an idea and quickly increase the scope and scale as they study it further. As a product of research, these tools represent a direct pipeline from researcher to industry practitioners since they are the implementation of ideas described in academic publications. Given this vital role in wind energy research and commercial development, the broad research software portfolio supported by WETO must maintain a minimum level of quality to support the wind energy field in the growing transition to renewable energy. This report outlines a series o f best practices to be adopted by all WETO-supported software projects, as well as expectations that the communities interacting with these projects should have of the developers and tools themselves. Wind energy research software has a unique standing in the field of scientific software. The stakeholders are varied with a subset being: (1) DOE EERE leadership, (2) DOE WETO leadership and program managers, (3) National lab leadership, (4) Associated project principle investigators, (5) Research software engineers, (6) Wind energy researchers in academia (including graduate students, post docs, and national lab staff), (7) Industry researchers and practitioners, (8) Commercial software developers, and (9) The general public interested in wind energy. These software are typically the end-user of other generic software libraries, so the funding cycles are often tied to applied research rather than the development of the software itself. Since the developers are also wind energy researchers, these tools are typically designed in a way that closely resembles the application in which they're used. Additionally, the expertise and incentives for the developers have a high variability, and often neither are aligned with software engineering or computer science. Given the unique environment in which wind energy research software is produced and consumed, it is critical for model owners to understand the context of their software. A framework for developing this understanding is to answer the following questions of a given software project: What is it's purpose? What is its role in the field of wind energy? What is the profile of the expected users? For how long will it be relevant? What is the expected impact? These questions allow model owners to identify the appropriate methods for the design, development, and long term maintenance of their software. Additionally, the answer provide context for future planners to understand why particular decisions were made and discern the consequences of changing course. The information is aggregated from experience within WETO-supported software development groups as well as external organizations and efforts to define the craft of research software engineering. These best practices aim to make the collaborative development process efficient and effective while improving the model understanding across stakeholders. Additionally, the general adoption of a common framework for software quality ensures that the end users of WETO software can trust these tools and accurately understand the risks to workflow integration.
This report gives an overview of a recent improvement project to reduce the background noise in the NASA Glenn Research Center 9-by 15-Foot Low Speed Wind Tunnel. Noise surveys of the original tunnel configuration indicated that flow surface noise in the test section and noise propagating from other tunnel regions were the primary background noise contributors. Several novel features were incorporated in the design of the upgraded tunnel, including a low noise flow surface and serpentine baffles for noise reduction, along with acoustically treated turning vanes and a new diffuser. Three companion papers present implementation details including the acoustic design and the aerodynamic quality/design CFD. The upgrades reduced background noise in the test section by about 10dBA over a wide range of flow speeds and frequencies. It is hoped this will be a useful summary to aid future users of the facility and wind tunnel engineers everywhere.
Abstract not provided