Patent Application
20180058462
The present invention generally relates to gas turbine engines, and more particularly relates to systems and methods for avoiding compressor surge in gas turbine engines.
A gas turbine engine may be used to supply power to various types of vehicles and systems. For example, gas turbine engines may be used to supply propulsion power to an aircraft. Some gas turbine engines may also serve as auxiliary power units (APUs) to supplement main propulsion engines in providing electrical and/or pneumatic power, and/or to start the propulsion engines.
Regardless of its end-use, and as is generally known, gas turbine engines are designed so that the compressor operates with sufficient surge margin. If the surge margin is inadequate, a compressor surge can occur resulting, for example, in a stall or a compressor surge, in which an undesirable reversal of flow occurs. Most gas turbine engines control the positions of variable inlet and/or exit geometries or bleed valves to avoid compressor surge. Unfortunately, most gas turbine engines do not include systems to detect an impending surge or even if a compressor surge has occurred. Moreover, gas turbine engines do not include systems that can modify the areas of operation to be avoided in the event that the surge margin is reduced.
Hence, there is a need for a system and method for avoiding gas turbine compressor surge and/or modify areas of operation to be avoided in the event that the engine surge margin is reduced. The present invention addresses at least this need.
This summary is provided to describe select concepts in a simplified form that are further described in the Detailed Description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
In one embodiment, a compressor surge avoidance control method for a gas turbine engine includes sensing a plurality of engine inlet parameters, and receiving, in a processor, a fuel command value. The sensed parameters are processed in the processor to determine a surge fuel value that is representative of a fuel flow above which, for the sensed engine inlet parameters, a compressor surge will likely occur. The surge fuel value and the fuel command value are compared, in the processor, and a protective action signal is generated if the fuel command value exceeds the surge fuel value.
In another embodiment, a compressor surge avoidance control system for a gas turbine engine includes a plurality of engine inlet sensors and a processor. Each sensor is configured to sense an engine inlet parameter and supply an engine inlet parameter signal representative of the sensed engine inlet parameter. The processor is coupled to receive the engine inlet parameter signals and a fuel command value. The processor is configured, upon receipt of the engine inlet parameter signals and the fuel command, to: (i) determine a surge fuel value, the surge fuel value representative of a fuel flow above which, for the sensed engine inlet parameters, a compressor surge will likely occur, (ii) compare the surge fuel value and the fuel command, and (iii) generate a protective action signal if the fuel command value exceeds the surge fuel value.
In yet another embodiment, a compressor surge avoidance control system for a gas turbine engine includes an engine inlet air temperature sensor, an engine inlet air pressure sensor, and a processor. The engine inlet air temperature sensor is configured to sense engine inlet air temperature and supply an engine inlet air temperature signal representative thereof. The engine inlet air pressure sensor is configured to sense engine inlet air pressure and supply an engine inlet air pressure signal representative thereof. The processor is coupled to receive the engine inlet air temperature signal, the engine inlet air pressure signal, and a fuel command value, and is configured to: (i) determine a surge fuel value, the surge fuel value representative of a fuel flow above which, for the sensed engine inlet parameters, a compressor surge will likely occur, (ii) compare the surge fuel value and the fuel command, and (iii) generate one or both of an operator alert signal and a load adjustment signal that causes a load reduction on the gas turbine engine.
Furthermore, other desirable features and characteristics of the gas turbine engine compressor surge avoidance system and method will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the preceding background.
The present invention will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and wherein:
The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Thus, any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described herein are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary, or the following detailed description.
In view of the foregoing, although one embodiment described herein is directed toward a single-spool gas turbine engine for use in an aircraft, it will be appreciated that the described embodiments could be implemented in other types of gas turbine engines, including any one of numerous single-spool gas turbine engines and any one of numerous multi-spool gas turbine engines, and may also be used in various other vehicles and end-use environments.
Turning now to
The high-energy gas expands through the turbine 106, where it gives up much of its energy and causes the turbine 106 to rotate. The gas is then exhausted from the APU 100 via an exhaust gas outlet 114. As the turbine 106 rotates, it drives, via a turbine shaft 116, various types of equipment that may be mounted in, or coupled to, the APU 100. For example, in the depicted embodiment the turbine 106 drives the compressor 102. It will be appreciated that the turbine 106 may also be used to drive a generator and/or a load compressor and/or other rotational equipment, which are not shown in
The APU 100 is controlled via an electronic control unit 150, which is referred to herein as an APU controller. The APU controller 150, which may be implemented using one or more processors, implements various logic to control the operation of the APU 100. In particular, the APU controller 150, at least in the depicted embodiment, implements fuel control logic 200 and surge avoidance logic 300. In the depicted embodiment, the fuel control logic 200 controls fuel flow to the combustor fuel nozzles 112 by controlling the position of a fuel metering valve 118. It will be appreciated that the use of a single fuel metering valve 118 is merely exemplary of the depicted embodiment, and that the fuel control logic 200 could instead, or additionally, control fuel flow by controlling one or more additional valves or pumps. It will additionally be appreciated that the fuel control logic 200 may be implemented according to any one of numerous fuel control logic schemes, now known or developed in the future. A detailed description of the fuel control logic is not needed to enable or fully describe the instant invention, and will thus not be further described.
The surge avoidance logic 300 receives a plurality of engine inlet parameters 120 and a fuel command value 122. The engine inlet parameters 120 that are supplied to the surge avoidance logic 300 are each representative of a sensed APU operational parameter, and the fuel command value 122 is representative of the fuel flow being supplied to the combustor fuel nozzles 112, as commanded by the fuel control logic 200. It will be appreciated that the particular APU operational parameters that are used in the surge avoidance logic 300 may vary. In the depicted embodiment, however, the APU operational parameters include at least engine inlet air temperature and engine inlet air pressure. In other embodiments, the APU operational parameters may include additional parameters, if needed or desired.
The specific sources of each of the engine inlet parameters may vary. For example, one or more of the engine inlet parameters may be supplied to the surge avoidance logic 300 directly via sensors or indirectly via other aircraft systems or devices. In the depicted embodiment, however, the engine inlet parameters are supplied to the surge avoidance logic 300 directly via sensors. Thus, as
No matter the specific number and sources of engine inlet parameters, the surge avoidance logic 300 is configured, upon receipt of the engine inlet parameters 120 and the fuel command value 122, to determine if the engine compressor surge margin has, or is about to be, undesirably reduced and, if so, generates a protective action signal. The protective action signal may be an operator alert signal, a load adjustment signal that causes a load reduction on the gas turbine engine, or both. The particular logic implemented by the surge avoidance logic 300 to determine if the engine compressor surge margin has, or is about to be, undesirably reduced, and the types of protective action signals it generates may vary. One particular embodiment of the logic is depicted in
The depicted surge avoidance logic 300 uses the engine inlet parameters 120 to determine a surge fuel value 202. As used herein, the surge fuel value is a value that is representative of a fuel flow above which, for the sensed engine inlet parameters 120, a compressor surge will likely occur. Although various techniques may be used to determine the surge fuel value 202, in the depicted embodiment the surge avoidance logic 300 uses a look-up table 204. The look-up table 204, which may be stored, for example, in a memory 128 (see
Upon determining the surge fuel value 202, the surge avoidance logic 300, via a comparator function 206, compares the surge fuel value 202 and the fuel command value 122. If the fuel command value 122 is less than the surge fuel value 202, then no action is taken. If, however, the fuel command value 122 exceeds the surge fuel value 202, which can occur either through increased engine loading or changes in environmental conditions, then a protective action signal 208 is generated, indicating that engine load should be reduced to avoid a surge.
It will be appreciated that engine load reduction may be variously implemented. For example, if the engine 100 is supplying both bleed air and electrical power, bleed air load can be reduced by closing variable geometry devices, such as inlet guide vanes, and/or electrical load can be reduced via electrical load shedding. Regardless of the specific manner in which engine load reduction is achieved, as
If the protective action signal 208 results in automated protection 212, a load adjustment signal 216 is generated that causes the load reduction on the gas turbine engine 100. In the depicted embodiment, the load adjustment signal 216 adjusts the inlet guide vane position commands that are supplied from, for example, inlet guide vane control logic 218 in the APU controller 150 to a plurality of inlet guide vanes 222. As load reduction is achieved through inlet guide vane position adjustment, the speed governor of the APU controller 150 will automatically reduce the fuel command 122 in order to maintain a constant speed. If the fuel command value 122 still exceeds the surge fuel value 202, and the inlet guide vane position command is at the minimum bleed command 223, then electrical load on the engine is reduced by supplying a generator load reduction command 224. The generator load reduction command 224 may be supplied to, for example, a vehicle control 226 that implements generator control logic 228 to implement automatic generator load shedding.
If the protective action signal 208 also, or instead, results in manual protection 214, then an operator alert signal 232 is generated. The operator alert signal 232 may result in an alert 234, audible, visual, or both, to an operator, indicating that the operator should manually reduce engine load or that engine load is being reduced automatically. In the event the alert 234 indicates that the operator should manually reduce engine load, then the operator can manually command the inlet guide vanes 222 and/or the generator control logic 228 as needed or desired to reduce engine load. If, on the other hand, the alert 234 indicates that engine load is being reduced automatically, the operator may, if needed or desired, override the load adjustment signal 216.
During the operational lifetime of a gas turbine engine 100, deterioration or other changes to the engine characteristics may result in a decrease in surge margin. Thus, the surge avoidance logic 300 is additionally configured to detect when a compressor surge occurs in the gas turbine engine 100 and, in response, update the look-up table 204 so that the protective action signal 208 will be triggered at a lower fuel command 122 in order to avoid a similar surge from reoccurring. In the depicted embodiment, the surge avoidance logic 300 detects a compressor surge via surge detection logic 236. The surge detection logic 236 may detect a compressor surge from one or more operational characteristics. Some example characteristics include, but are not limited to, cycling speeds, high operating temperatures, and fluctuating fuel demand.
Regardless of how the surge detection logic 236 specifically detects a compressor surge, upon detecting a surge, surge calibration logic 238 stores the fuel flow, the engine inlet air temperature (T2), and the engine inlet air pressure (P2) when the surge occurred, and modifies the values in the look-up table 204 accordingly to lower the fuel flow values to new levels. The modification of values in the look-up table 204 may occur across all table values or only a portion of table values in the vicinity of the detected surge.
The system and method described herein provides a technique for avoiding gas turbine compressor surge and/or modifying areas of operation to be avoided in the event that the engine surge margin is reduced.
Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Some of the embodiments and implementations are described above in terms of functional and/or logical block components (or modules) and various processing steps. However, it should be appreciated that such block components (or modules) may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments described herein are merely exemplary implementations.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Numerical ordinals such as “first,” “second,” “third,” etc. simply denote different singles of a plurality and do not imply any order or sequence unless specifically defined by the claim language. The sequence of the text in any of the claims does not imply that process steps must be performed in a temporal or logical order according to such sequence unless it is specifically defined by the language of the claim. The process steps may be interchanged in any order without departing from the scope of the invention as long as such an interchange does not contradict the claim language and is not logically nonsensical.
Furthermore, depending on the context, words such as “connect” or “coupled to” used in describing a relationship between different elements do not imply that a direct physical connection must be made between these elements. For example, two elements may be connected to each other physically, electronically, logically, or in any other manner, through one or more additional elements.
While at least one exemplary embodiment has been presented in the foregoing detailed description of the invention, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an exemplary embodiment of the invention. It being understood that various changes may be made in the function and arrangement of elements described in an exemplary embodiment without departing from the scope of the invention as set forth in the appended claims.
