Patent Application
20180149092
The present disclosure relates generally to gas turbine engines, and more specifically to technology for controlling gas turbine engines.
Gas turbine engines are used to power aircraft, watercraft, power generators, and the like. Gas turbine engines typically include a compressor, a combustor, and a turbine. The compressor compresses air drawn into the engine and delivers high-pressure air to the combustor. In the combustor, fuel is mixed with the high-pressure air and is ignited. Products of the combustion reaction in the combustor are directed into the turbine where work is extracted to drive the compressor and, sometimes, an output shaft. Left-over products of the combustion are exhausted out of the turbine and may provide thrust in some applications.
Typical platforms (e.g., aircraft such as helicopters) may include a gas turbine engine and other components such as an inlet particle separator (IPS) and/or an infrared suppression system (IRS). The gas turbine engine and the IPS and/or the IRS are typically procured by the platform supplier from separate sources. Additionally, the IPS and/or the IRS may be added to the engine and/or the platform before or after delivery of the platform. Accordingly, in typical platforms the IPS and the IRS are not controlled by the engine controller of the gas turbine engine.
The present disclosure may comprise one or more of the following features and combinations thereof.
A propulsion system for a vehicle may include an inlet particle separator, a gas turbine engine, and an engine controller. The inlet particle separator is variably activated. The engine controller may include particle separator control logic configured to determine a first activation state of the inlet particle separator, adjust a first engine operating parameter based on the first activation state, and control the gas turbine engine based on the first engine operating parameter in response to adjustment of the first engine operating parameter. In some embodiments, to determine the first activation state may include to determine whether the inlet particle separator is activated or deactivated. In some embodiments, the first activation state may include a modulated activation state. In some embodiments, to adjust the first engine operating parameter may include to determine an inlet flow value based on the first activation state and to adjust the first engine operating parameter based on the inlet flow value.
In some embodiments, the propulsion system may further include an infrared suppression system that is variably activated. The engine controller may further include infrared suppression system control logic configured to determine a second activation state of the infrared suppression system and to adjust a second engine operating parameter based on the second activation state. To control the gas turbine engine may further include to control the gas turbine engine based on the second engine operating parameter in response to adjustment of the second engine operating parameter. In some embodiments, to determine the second activation state may include to determine whether the infrared suppression system is activated or deactivated. In some embodiments, the second activation state may include a modulated activation state. In some embodiments, to adjust the second engine operating parameter may include to determine a backpressure value based on the second activation state and to adjust the second engine operating parameter based on the backpressure value.
According to another aspect of the present disclosure, a method for propulsion system control includes determining, by an engine controller of a propulsion system, a first activation state of an inlet particle separator of the propulsion system, wherein the inlet particle separator is variably activated; adjusting, by the engine controller, a first engine operating parameter based on the first activation state; and controlling, by the engine controller, a gas turbine engine of the propulsion system based on the first engine operating parameter in response to adjusting the first engine operating parameter. In some embodiments, determining the first activation state may include determining whether the inlet particle separator is activated or deactivated. In some embodiments, determining the first activation state may include determining a modulated activation state. In some embodiments, adjusting the first engine operating parameter may include determining an inlet flow value based on the first activation state and adjusting the first engine operating parameter based on the inlet flow value.
In some embodiments, the method may further include determining, by the engine controller, a second activation state of an infrared suppression system of the propulsion system, wherein the infrared suppression system is variably activated; and adjusting, by the engine controller, a second engine operating parameter based on the second activation state. Controlling the gas turbine engine may further include controlling the gas turbine engine based on the second engine operating parameter in response to adjusting the second engine operating parameter. In some embodiments, determining the second activation state may include determining whether the infrared suppression system is activated or deactivated. In some embodiments, determining the second activation state comprises determining a modulated activation state. In some embodiments, adjusting the second engine operating parameter may include determining a backpressure value based on the second activation state and adjusting the second engine operating parameter based on the backpressure value.
According to another aspect of the present disclosure, one or more computer-readable storage media may include a plurality of instructions that in response to being executed cause an engine controller of a propulsion system to determine a first activation state of an inlet particle separator of the propulsion system, wherein the inlet particle separator is variably activated; adjust a first engine operating parameter based on the first activation state; and control a gas turbine engine of the propulsion system based on the first engine operating parameter in response to adjusting the first engine operating parameter. In some embodiments, to determine the first activation state may include to determine whether the inlet particle separator is activated or deactivated. In some embodiments, to determine the first activation state may include to determine a modulated activation state. In some embodiments, to adjust the first engine operating parameter may include to determine an inlet flow value based on the first activation state and adjust the first engine operating parameter based on the inlet flow value.
In some embodiments, the one or more computer-readable storage media may further include a plurality of instructions that in response to being executed cause the engine controller to determine a second activation state of an infrared suppression system of the propulsion system, wherein the infrared suppression system is variably activated; and adjust a second engine operating parameter based on the second activation state. To control the gas turbine engine may further include to control the gas turbine engine based on the second engine operating parameter in response to adjusting the second engine operating parameter. In some embodiments, to determine the second activation state may include to determine whether the infrared suppression system is activated or deactivated. In some embodiments, to determine the second activation state may include to determine a modulated activation state. In some embodiments, to adjust the second engine operating parameter may include to determine a backpressure value based on the second activation state and adjust the second engine operating parameter based on the backpressure value.
These and other features of the present disclosure will become more apparent from the following description of the illustrative embodiments.
For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to a number of illustrative embodiments illustrated in the drawings and specific language will be used to describe the same.
Referring now to
The illustrative turbine engine 14 is a multi-shaft turbofan gas turbine engine configured for aerospace applications; however, aspects of the present disclosure are applicable to other types of turbine engines, including various types of turbofan and turboshaft systems, as well as turbine engines that are configured for other, non-aerospace types of applications. A fan 16 (e.g., a fan, variable pitch propeller, compressor, etc.) draws air into the turbine engine 14. In some embodiments, some of the air drawn into the turbine engine 14 by the fan 16 may bypass other engine components via a bypass region 30 (e.g., a bypass duct). The remaining air flows to one or more compressors 20. For instance, in some embodiments, a low-pressure compressor may increase the pressure of air received from the fan 16, and a high-pressure compressor may further increase the pressure of air received from the low-pressure compressor. In any event, the compressor(s) 20 increase the pressure of the drawn-in air and forward the higher-pressure air to a combustor 22.
In the combustor 22, the pressurized air is mixed with fuel (e.g., gas), which is supplied to the combustor 22 by a fuel supply, for example a fuel pump. Typically, a flow meter, flow control valve, fuel flow sensor, or similar device monitors and/or regulates the flow of fuel into the combustor 22. An igniter (not shown) is typically used to cause the mixture of air and fuel to combust. The high-energy combusted air is directed to one or more turbines 26, 28. In the illustrative embodiment, a high-pressure turbine 26 is disposed in axial flow series with a low-pressure turbine 28. The combusted air expands through the turbines 26, 28, causing the turbines 26, 28 to rotate. The combusted air is then exhausted through, for example, a propulsion nozzle (not shown), which may generate additional propulsion thrust.
The rotation of the turbines 26, 28 causes the engine shafts 18, 24 to rotate. More specifically, rotation of the low-pressure turbine 28 drives a low-pressure shaft 18, which drives the fan 16. Rotation of the high-pressure turbine 26 drives the high-pressure shaft 24, which drives the compressor(s) 20. In the illustrative embodiments, the shafts 18, 24 are concentrically disposed and independently rotatable. In other embodiments, the shafts 18, 24 may be parallel but not concentric.
The IPS 12 is configured to receive atmospheric air that may include dust, sand, water, ice, or other debris particles. The IPS 12 separates the atmospheric air into a stream of relatively clean air, including fewer particles, that is provided to the turbine engine 14 (e.g., to the fan 16) and a stream of relatively dirty air, including more particles, that may be ejected from the propulsion system 10. For example, the IPS 12 may be embodied as an inertial particle separator including various surfaces (e.g., inlet splitters, ramps, and/or vanes) shaped to cause the inlet air to swirl, forcing heavier debris particles away from the center of the air stream and out of the propulsion system 10 (e.g., toward a scavenge passageway, blower motor, bleed valves, or other air ejection system). The IPS 12 is actuated or otherwise controllable by the engine controller 34 using the IPS control signals 40. The IPS 12 may be operable in at least two modes (e.g., on and off) or positions (e.g., open or closed), and in some embodiments may be continuously variable. For example, in some embodiments, the IPS 12 may be selectively enabled or disabled (i.e. turned on or turned off) by the engine controller 34. Additionally or alternatively, in some embodiments the operation of the IPS 12 may be modulated or otherwise varied between being completely disabled and completely enabled. For example, the IPS 12 may be controlled by opening or closing various aerodynamic surfaces, configuring valves, or otherwise controlling the flow of inlet air through or around the IPS 12.
The IRS 32 is configured to reduce the infrared signature of the propulsion system 10. For example, the IRS 32 may mix hot exhaust gases emitted by the turbine engine 14 with cool, ambient air to reduce the temperature of gases emitted by the propulsion system 10. As another example, the IRS 32 may include ducting, shrouds, or other systems that prevent a line-of-sight view from outside of the propulsion system 10 to the hot components of the turbine engine 14. Similar to the IPS 12, the IRS 32 is actuated or otherwise controllable by the engine controller 34 using the IRS control signals 44. The IRS 32 may be operable in at least two modes (e.g., on and off) or positions (e.g., open or closed), and in some embodiments may be continuously variable. For example, in some embodiments, the IRS 32 may be selectively enabled or disabled (i.e. turned on or turned off) by the engine controller 34. Additionally or alternatively, in some embodiments the operation of the IRS 32 may be modulated or otherwise varied between being completely disabled and completely enabled. For example, the IRS 32 may be controlled by moving various surfaces or other features to control mixing of ambient air with hot exhaust gases and/or to shield hot internal components from line-of-sight view.
The engine controller 34 controls the overall operation of the turbine engine 14 or various components of the propulsion system 10 and may be embodied as any microcontroller, microprocessor, embedded system, or other computing device capable of performing the functions described herein. For example, the engine controller 34 may be embodied as a full-authority digital engine controller (FADEC). In addition to various other control operations, the engine controller 34 includes IPS control logic 36 and IRS control logic 38. Each of the IPS control logic 36 and the IRS control logic 38 may be embodied as hardware, firmware, software, or a combination thereof. For example, the IPS control logic 36 and/or the IRS control logic 38 may form a portion of, or otherwise be established by, a processor or other hardware components of the engine controller 34. As such, in some embodiments, the IPS control logic 36 and/or the IRS control logic 38 may be embodied as a circuit or collection of electrical devices (e.g., an IPS control logic circuit and/or an IRS control logic circuit). Additionally, in although illustrated as being included in the engine controller 34, it should be understood that in some embodiments the IPS control logic 36 and/or the IRS control logic 38 may be included in a separate controller, control unit, or other component of the propulsion system 10, such as an IPS controller or an IRS controller. As shown, the engine controller 34 may communicate with IPS 12, the turbine engine 14, and the IRS 32 using one or more IPS control signals 40, engine control signals 42, and IRS control signals 44, respectively.
As described further below, the IPS control logic 36 is configured to determine an activation state of the IPS 12, adjust one or more engine operating parameters based on that activation state, and control the gas turbine engine 14 based on the adjusted engine operating parameters. Similarly, the IRS control logic 38 is configured to determine an activation state of the IRS 32, adjust one or more engine operating parameters based on that activation state, and control the gas turbine engine 14 based on the adjusted engine operating parameters. Additionally, although illustrated as including both IPS control logic 36 and IRS control logic 38, it should understood that the engine controller 34 may include the IPS control logic 36 but not the IRS control logic 38, or vice versa.
Referring now to
The method 100 begins in block 102, in which the engine controller 34 determines the activation state of the IPS 12. The activation state may be embodied as any indication of whether the IPS 12 is activated, enabled, or otherwise operational. The IPS 12 may be activated or deactivated in response to a user command (e.g., a pilot command) or, in some embodiments, may be activated or deactivated automatically by the engine controller 34. For example, as described below, in some embodiments the engine controller 34 may control the IPS 12 to improve engine performance. In some embodiments, in block 104 the engine controller 34 may determine whether the IPS 12 is activated or deactivated (i.e., on or off). In some embodiments, in block 106 the engine controller 34 may determine a modulated activation state of the IPS 12. For example, the engine controller 34 may determine that the IPS 12 has been activated at a particular percentage of full capacity or otherwise determine a variable degree of activation.
In block 108, the engine controller 34 adjusts one or more engine operating parameters based on the activation state of the IPS 12. When the IPS 12 is activated, operating conditions of the turbine engine 14 may be affected, and thus performance, efficiency, and other characteristics of the turbine engine 14 may be affected. The engine controller 34 may adjust one or more operating parameters to optimize performance of the turbine engine 14 for maximum efficiency, power, or other optimization objective, based on the activation state of the IPS 12. For example, the engine controller 34 may adjust operating parameters such as fuel flow rate, engine speed, engine air flow, or other operating parameters. The engine controller 34 may adjust the operating parameters using any appropriate control algorithm, such as a model-based control algorithm. In some embodiments, in block 110 the engine controller 34 may adjust the operating parameters based on an inlet flow that is determined based on the activation state of the IPS 12. For example, activating the IPS 12 may reduce the inlet air flow to the turbine engine 14. The engine controller 34 may determine the inlet air flow based on the activation state of the IPS 12 and then adjust one or more operating parameters to adapt to or otherwise compensate for the reduced inlet air flow. By adapting to the reduced inlet air flow, the engine controller 34 may improve engine performance.
In block 112, the engine controller 34 determines the activation state of the IRS 32. The activation state may be embodied as any indication of whether the IRS 32 is activated, enabled, or otherwise operational. The IRS 32 may be activated or deactivated in response to a user command (e.g., a pilot command) or, in some embodiments, may be activated or deactivated automatically by the engine controller 34. For example, as described below, in some embodiments the engine controller 34 may control the IRS 32 to improve engine performance. In some embodiments, in block 114 the engine controller 34 may determine whether the IRS 32 is activated or deactivated (i.e., on or off). In some embodiments, in block 116 the engine controller 34 may determine a modulated activation state of the IRS 32. For example, the engine controller 34 may determine that the IRS 32 has been activated at a particular percentage of full capacity or otherwise determine a variable degree of activation.
In block 118, the engine controller 34 adjusts one or more engine operating parameters based on the activation state of the IRS 32. When the IRS 32 is activated, operating conditions of the turbine engine 14 may be affected, and thus performance, efficiency, and other characteristics of the turbine engine 14 may be affected. The engine controller 34 may adjust one or more operating parameters to optimize performance of the turbine engine 14 for maximum efficiency, power, or other optimization objective, based on the activation state of the IRS 32. For example, the engine controller 34 may adjust operating parameters such as fuel flow rate, engine speed, engine air flow, or other operating parameters. As described above, the engine controller 34 may adjust the operating parameters using any appropriate control algorithm, such as a model-based control algorithm. In some embodiments, in block 120 the engine controller 34 may adjust the operating parameters based on backpressure that is determined based on the activation state of the IRS 32. For example, activating the IRS 32 may increase backpressure to the turbine engine 14. Increasing the backpressure may affect engine performance and reduce the surge margin of the turbine engine 14. The engine controller 34 may determine the backpressure based on the activation state of the IRS 32 and then adjust one or more operating parameters to adapt to or otherwise compensate for the increased backpressure. By adapting to the increased backpressure, the engine controller 34 may improve engine performance and/or increase surge margin.
In block 122, the engine controller 34 controls the turbine engine 14 using the engine operating parameters determined as described above in connection with blocks 108, 118. The engine controller 34 may control the turbine engine 14 by updating, adjusting, or otherwise generating one or more engine control signals 42 based on the engine operating parameters. For example, the engine controller 34 may send engine control signals 42 to realize the fuel flow rate, engine speed, air flow, or other operating parameters determined as described above.
In some embodiments, in block 124 the engine controller 34 may control the IPS 12 based on the adjusted operating parameters. The engine controller 34, for example, may send one or more IPS control signals 40 to the IPS 12 to control the activation state of the IPS 12. In some embodiments, the engine controller 34 may control the IPS 12 to improve engine efficiency, power delivery, or to achieve other optimization objectives. For example, the engine controller 34 may control the IPS 12 to achieve a desired inlet air flow, which may improve efficiency and/or performance in some embodiments. In some embodiments, the engine controller 34 may control the IPS 12 only when the user (e.g., the pilot) has deactivated the IPS 12. Similarly, in some embodiments, in block 126 the engine controller 34 may control the IRS 32 based on the adjusted operating parameters. The engine controller 34, for example, may send one or more IRS control signals 44 to the IRS 32 to control the activation state of the IRS 32. In some embodiments, the engine controller 34 may control the IRS 32 to improve engine efficiency, power delivery, or to achieve other optimization objectives. For example, the engine controller 34 may control the IRS 32 to achieve a desired engine backpressure, which may improve efficiency and/or performance in some embodiments. In some embodiments, the engine controller 34 may control the IRS 32 only when the user (e.g., the pilot) has deactivated the IRS 32. After controlling the turbine engine 14, the method 100 loops back to block 102 to continue controlling the propulsion system 10.
Referring now to
The illustrative engine controller 34 includes at least one processor 200, an input/output (I/O) subsystem 202, and a memory 204. The I/O subsystem 202 typically includes, among other things, an I/O controller, a memory controller, and one or more I/O ports, although not specifically shown. The processor 200 and the I/O subsystem 202 are communicatively coupled to the memory 204. The memory 204 may be embodied as any type of suitable computer memory device (e.g., volatile memory such as various forms of random access memory). The I/O subsystem 202 is communicatively coupled to a number of hardware and/or software components, including a data storage device 206 and communication circuitry 208.
The data storage device 206 may include one or more hard drives or other suitable persistent data storage devices (e.g., flash memory, memory cards, memory sticks, read-only memory devices, and/or others). Various data needed by the propulsion system 10 (e.g., the IPS control logic 36 and/or the IRS control logic 38) may be stored by the data storage device 206. Portions of the IPS control logic 36 and/or the IRS control logic 38 may be copied to the memory 204 during operation of the propulsion system 10, for faster processing or other reasons. The IPS control logic 36 and/or the IRS control logic 38 may be embodied as one or more computer-executable components and/or data structures (e.g., computer hardware, firmware, software, or a combination thereof). Particular aspects of the methods that may be performed by the IPS control logic 36 and/or the IRS control logic 38 may vary depending on the requirements of a particular design of the propulsion system 10. Accordingly, the examples described herein are illustrative and intended to be non-limiting.
The communication circuitry 208 may communicatively couple the engine controller 34 to one or more other devices, systems, or communication networks, e.g., a vehicle area network, controller area network, local area network, and/or wide area network, for example. Accordingly, the communication circuitry 208 may include one or more wired or wireless network interface software, firmware, or hardware, for example, as may be needed pursuant to the specifications and/or design of the particular propulsion system 10. Further, the engine controller 34 may include other components, sub-components, and devices not illustrated herein for clarity of the description. In general, the components of the engine controller 34 are communicatively coupled as shown in
In the foregoing description, numerous specific details, examples, and scenarios are set forth in order to provide a more thorough understanding of the present disclosure. It will be appreciated, however, that embodiments of the disclosure may be practiced without such specific details. Further, such examples and scenarios are provided for illustration, and are not intended to limit the disclosure in any way. Those of ordinary skill in the art, with the included descriptions, should be able to implement appropriate functionality without undue experimentation.
References in the specification to “an embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly indicated.
Embodiments in accordance with the disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored using one or more machine-readable media, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine. For example, a machine-readable medium may include any suitable form of volatile or non-volatile memory.
Modules, data structures, and the like defined herein are defined as such for ease of discussion, and are not intended to imply that any specific implementation details are required. For example, any of the described modules and/or data structures may be combined or divided into sub-modules, sub-processes or other units of computer code or data as may be required by a particular design or implementation.
In the drawings, specific arrangements or orderings of schematic elements may be shown for ease of description. However, the specific ordering or arrangement of such elements is not meant to imply that a particular order or sequence of processing, or separation of processes, is required in all embodiments. In general, schematic elements used to represent instruction blocks or modules may be implemented using any suitable form of machine-readable instruction, and each such instruction may be implemented using any suitable programming language, library, application programming interface (API), and/or other software development tools or frameworks. Similarly, schematic elements used to represent data or information may be implemented using any suitable electronic arrangement or data structure. Further, some connections, relationships, or associations between elements may be simplified or not shown in the drawings so as not to obscure the disclosure.
While the disclosure has been illustrated and described in detail in the foregoing drawings and description, the same is to be considered as exemplary and not restrictive in character, it being understood that only illustrative embodiments thereof have been shown and described and that all changes and modifications that come within the spirit of the disclosure are desired to be protected.
This invention was made in part with government support under contract number W911W6-14-2-0006 awarded by the United States Army. The United States Government has certain rights in this invention.
