Method and apparatus for detecting airflow separation of engine

Abstract

Methods, apparatus, systems, and articles of manufacture are disclosed to detect airflow separation of an engine. An example apparatus includes hardware and memory including instructions that, when executed, cause the hardware to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determining a severity rating parameter based on the inlet flow separation parameter, the severity rating parameter based on a difference between the first pressure value and the second pressure value; and adjusting a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

Description

[0001] This application is a divisional application of the invention patent application with application number 202110461753.2 filed on April 27, 2021 and invention name “Method and device for detecting airflow separation of an engine”. Technical Field

[0002] The present disclosure relates generally to gas turbine engines and, more particularly, to methods and apparatus for detecting airflow separation of an engine. Background Art

[0003] A gas turbine engine typically includes an inlet section, a compressor section, a combustion section, a turbine section, and an exhaust section in a serial flow order. In operation, air enters the inlet section and flows to the compressor section, where one or more axial compressors gradually compress the air until it reaches the combustion section. Fuel mixes with the compressed air and burns in the combustion section, thereby producing combustion gases. The combustion gases flow from the combustion section through a hot gas path defined in the turbine section and then exit the turbine section via the exhaust section.

[0004] In a particular configuration, the compressor section includes a low pressure compressor ("LP compressor") and a high pressure compressor ("HP compressor") in a serial flow order. The LP compressor and the HP compressor may include one or more axially spaced stages. Each stage may include a row of circumferentially spaced stator blades and a row of circumferentially spaced rotor blades positioned downstream of the row of stator blades. The stator blades direct air flowing through the compressor section onto the rotor blades, which transfer kinetic energy to the air to increase its pressure.

[0005] The air intake of a gas turbine engine is subject to cross winds and high-incidence crossflows during takeoff, flight, etc., which can affect the aerostability of the rotor blades. During such flight conditions, the airflow at the inlet of the gas turbine engine can separate, resulting in inlet flow separation and reduced performance of the gas turbine engine. Summary of the invention

[0006] Methods and apparatus for controlling airflow separation in an engine are disclosed herein.

[0007] An example device disclosed herein includes hardware and a memory, the memory including instructions that, when executed, cause the hardware to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjust a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0008] Another example apparatus disclosed herein includes: an inlet flow separation parameter determiner that determines an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; an inlet flow separation severity level parameter determiner that determines a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and a command generator that adjusts a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0009] An example non-transitory computer-readable storage medium disclosed herein includes instructions that, when executed, cause at least one processor to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjust a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0010] An example method disclosed herein includes determining an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determining a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjusting a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0011] Yet another example apparatus disclosed herein includes hardware and a memory, the memory including instructions that, when executed, cause the hardware to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; and determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a schematic cross-sectional view of a first example high bypass turbofan type gas turbine engine.

[0013] Figure 2 is during an inlet flow separation event Figure 1 A schematic cross-sectional view of a first example high bypass turbofan type gas turbine engine.

[0014] Figure 3 is a schematic cross-sectional view of a second example high bypass turbofan gas turbine engine including an example controller monitoring inlet flow separation using an example pressure sensor.

[0015] Figure 4A is a schematic cross-sectional view of a third example high bypass turbofan type gas turbine engine including Figure 3 An example controller and an example actuator are provided to adjust a contribution of airflow to an inlet section of a third high bypass turbofan type gas turbine engine.

[0016] Figure 4B is a schematic cross-sectional view of a fourth example high bypass turbofan gas turbine engine comprising Figure 3 An example controller and an example pressure sensor and an example actuator are provided to regulate a contribution of airflow to an inlet section of a fourth high bypass turbofan type gas turbine engine.

[0017] Figure 5 is during an inlet flow separation event Figure 4B A schematic cross-sectional view of a fourth example high bypass turbofan type gas turbine engine.

[0018] Figure 6 is used with Figure 3-5 A block diagram of an example controller implementation for use with a high bypass turbofan type gas turbine engine.

[0019] Figure 7 It is used to detect Figure 3-5 Table of example determinations of inlet flow separation for a high bypass turbofan type gas turbine engine.

[0020] Figure 8 is a flowchart representing example machine readable instructions that may be executed to implement Figure 3-6 An example controller to adjust the Figure 4A-5 Airflow contribution to the inlet of a high bypass turbofan type gas turbine engine.

[0021] Fig. 9 is a flowchart representing example machine readable instructions that may be executed to implement Figure 3-6 The controller is based on Figure 3-5 Sensor data associated with a high bypass turbofan type gas turbine engine is used to determine inlet flow separation parameters.

[0022] Fig.10 is a flowchart representing example machine readable instructions that may be executed to implement Figure 3-6A controller is provided to detect inlet flow separation based on an example inlet flow separation parameter.

[0023] Fig.11 is a flowchart representing example machine readable instructions that may be executed to implement Figure 3-6 A controller is provided to identify an example inlet flow separation control measure based on an example inlet flow separation severity level parameter.

[0024] Fig.12 is a flowchart representing example machine readable instructions that may be executed to implement Figure 3-6 controller to adjust the Figure 4A , 4B and / or 5 are airflow contributions to the inlet of a high bypass turbofan type gas turbine engine.

[0025] Fig.13 is a block diagram of an example processing platform configured to perform Figure 8-12 Machine readable instructions to implement Figure 3-6 Controller.

[0026] The drawings are not drawn to scale. Generally, the same reference numbers will be used throughout the drawings and accompanying written description to refer to the same or like parts. DETAILED DESCRIPTION

[0027] Descriptors "first," "second," "third," etc., are used herein when identifying multiple elements or components that can be referenced separately. Unless otherwise specified or understood based on the context of their use, such descriptors are not intended to confer any meaning of priority, physical order or arrangement in a list, or chronological order, but are merely used as labels to refer to multiple elements or components separately for ease of understanding of the disclosed examples. In some examples, the descriptor "first" may be used to refer to an element in the detailed description, while a different descriptor such as "second" or "third" may be used in the claims to refer to the same element. In such cases, it should be understood that such descriptors are used only for ease of reference to multiple elements or components.

[0028] As used herein, the terms "upstream" and "downstream" refer to the relative direction of fluid flow in a fluid path. For example, "upstream" refers to the direction from which the fluid flows, while "downstream" refers to the direction to which the fluid flows.

[0029] The performance of a gas turbine engine used on an aircraft (e.g., a commercial aircraft) varies during different flight conditions experienced by the aircraft. In some cases, adverse flight conditions can reduce the performance of the gas turbine engine. Such adverse flight conditions can include takeoff of an aircraft or crosswind conditions of an aircraft in flight. The inlet lip section located at the front end of the engine nacelle is typically designed to enable the engine to operate to prevent separation of the airflow from the inlet lip section of the nacelle during adverse flight conditions. As used herein, the separation of the airflow from the inlet lip section of the nacelle is referred to as "inlet flow separation" or "inlet airflow separation" and is used interchangeably. For example, the inlet lip section may require a "thick" inlet lip section design to support the operation of the engine during specific flight conditions (e.g., crosswind conditions, takeoff, etc.).

[0030] In some cases, inlet flow separation can cause a significant asymmetry in the total pressure within the engine air intake. In this case, the asymmetric total pressure can cause asymmetric loading of the fan blades of the engine fan, which can increase the stress of the fan blades. In some such cases, the stress of the fan blades can cause the reliability and / or operating life of the fan blades and / or the engine more generally to be reduced. Some severe cases of inlet flow separation can cause compressor or engine surge, which is an increase in the revolutions per minute (rpm) of the engine compressor. For example, severe inlet flow separation can cause the compressor and / or the engine more generally to stall.

[0031] Reference will now be made in detail to embodiments of the present disclosure, one or more examples of which are shown in the accompanying drawings. Each example is provided by way of explanation of the present disclosure rather than limitation thereof. In fact, it will be apparent to those skilled in the art that various modifications and variations may be made to the present disclosure without departing from the scope or spirit of the present disclosure. For example, a feature shown or described as part of one example may be used together with another example to produce yet another example. Therefore, the present disclosure is intended to cover such modifications and variations that fall within the scope of the appended claims and their equivalents.

[0032] Examples disclosed herein detect and control airflow separation of an engine, such as a gas turbine engine. In some disclosed examples, an inlet flow separation (IFS) controller determines one or more severity level parameters or IFS severity level parameters that can be used to detect IFS. For example, the IFS controller can determine a first IFS severity level parameter based on the direction of the airflow, a second IFS severity level parameter based on the pressure difference across the inlet section of the engine nacelle, and / or a third IFS severity level parameter based on the engine vibration response. In such examples, the IFS controller can determine the first IFS severity level parameter and / or the second IFS severity level parameter based on air pressure data from an air pressure sensor included in an inlet lip section of the nacelle, an outlet lip section of the nacelle, etc. In some such examples, the IFS controller can determine the third IFS severity level parameter based on acceleration data obtained from one or more acceleration sensors monitoring one or more bearings (e.g., ball bearings, roller bearings, etc.) of the engine.

[0033] In some disclosed examples, the IFS controller may determine an IFS severity level or degree or quantification of IFS (if any) at the engine inlet based on the IFS severity level parameter. For example, the IFS controller may determine a probability density function based on the IFS severity level parameter. In such an example, the IFS controller may detect the IFS at the engine inlet by comparing the probability density function with one or more stored probability density functions, which may correspond to characterizations or representations of the engine under a variety of flight conditions.

[0034] In some disclosed examples, in response to detecting an IFS, an IFS controller may control one or more actuators included in the engine nacelle to reduce and / or otherwise eliminate the detected IFS. For example, the IFS controller may control the actuators to adjust a first airflow contribution (1) from a first region behind an engine fan to (2) a third region in front of the fan, and / or adjust a second airflow contribution (1) from a second region of the engine core to (2) a third region in front of the fan. In such examples, the IFS controller may reduce and / or otherwise eliminate the IFS by adjusting the airflow contribution of at least one of the first region or the second region. Advantageously, the examples disclosed herein may reduce and / or otherwise eliminate the IFS by adjusting the airflow contribution from at least one of the first region or the second region to the third region, thereby improving the reliability and operating life of the engine.

[0035] As used herein, "include" and "comprising" (and all forms and tenses thereof) are open-ended terms. Thus, whenever a claim employs any form of "include" or "comprising" (e.g., includes, includes, having, etc.) as a preamble or in any kind of claim recitation, it should be understood that other elements, terms, etc. may be present without exceeding the scope of the corresponding claim or recitation. As used herein, when the phrase "at least" is used as a transitional term, such as in the preamble of a claim, it is open-ended in the same manner as the terms "include" and "comprising" are open-ended. When used, for example, in a form such as A, B, and / or C, the term "and / or" refers to any combination or subset of A, B, and C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, and (7) A and B and C. As used herein in the context of describing structures, components, articles, objects, and / or things, the phrase “at least one of A and B” is intended to refer to embodiments that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, articles, objects, and / or things, the phrase “at least one of A or B” is intended to refer to embodiments that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. As used herein in the context of describing the performance or execution of processes, instructions, actions, activities, and / or steps, the phrase “at least one of A and B” is intended to refer to embodiments that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing the performance or execution of a process, instruction, action, activity, and / or step, the phrase "at least one of A or B" is intended to refer to embodiments that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.

[0036] As used herein, singular references (e.g., "a", "an", "first", "second", etc.) do not exclude a plurality. As used herein, the term "a" or "an" entity refers to one or more of that entity. The terms "a" (or "an"), "one or more" and "at least one" may be used interchangeably herein. Furthermore, although listed separately, multiple devices, elements or method actions may be implemented by, for example, a single unit or processor. In addition, although individual features may be included in different examples or claims, these features may be combined, and inclusion in different examples or claims does not mean that a combination of features is not feasible and / or disadvantageous.

[0037] Referring now to the drawings, wherein like reference numerals refer to like elements throughout the several views, Figure 1 is a schematic cross-sectional view of a first example high bypass turbofan gas turbine engine 100 (“turbofan engine 100”) that may be incorporated with various examples disclosed herein. Figure 1 As shown, first turbofan engine 100 defines a longitudinal or axial centerline axis 102 extending therethrough for reference. In general, first turbofan engine 100 may include a core turbine or gas turbine engine 104 disposed downstream of a fan section 106 .

[0038] The core turbine engine 104 may generally include a substantially tubular casing 108 defining an annular inlet 110. The casing 108 may be formed of a single shell or multiple shells. The casing 108 encloses, in serial flow relationship: a compressor section having a supercharger or low-pressure compressor 112 ("LP compressor 112") and a high-pressure compressor 114 ("HP compressor 114"); a combustion section 116; a turbine section having a high-pressure turbine 118 ("HP turbine 118") and a low-pressure turbine 120 ("LP turbine 120"); and an exhaust section 122. A high-pressure shaft or spool 124 ("HP shaft 124") drivingly couples the HP turbine 118 and the HP compressor 114. A low-pressure shaft or spool 126 ("LP shaft 126") drivingly couples the LP turbine 120 and the LP compressor 112. The LP shaft 126 may also be coupled to a fan shaft or spool 128 of the fan section 106. In some examples, LP shaft 126 may be directly coupled to fan shaft 128 (ie, a direct drive configuration). In an alternative configuration, LP shaft 126 may be coupled to fan shaft 128 via reduction gear 130 (ie, an indirect drive or gear drive configuration).

[0039] like Figure 1 As shown, fan section 106 includes a plurality of fan blades 132 ("fan" 132) coupled to and extending radially outward from fan shaft 128. A first annular fan casing or first nacelle 134 circumferentially surrounds fan section 106 and / or at least a portion of core turbine 104. First turbofan engine 100 includes a second nacelle 135 opposite first nacelle 134. Nacelles 134, 135 may be supported relative to core turbine 104 by a plurality of circumferentially spaced outlet guide vanes 136. In addition, a downstream section 138 of nacelles 134, 135 may surround an outer portion of core turbine 104 to define a bypass airflow passage 140 therebetween.

[0040] like Figure 1As shown, air 142 enters an air intake or inlet portion 144 of the first turbofan engine 100 during operation of the first turbofan engine 100. A first portion 146 of the air 142 flows into the bypass airflow passage 140, while a second portion 148 of the air 142 flows into the inlet 110 of the LP compressor 112. One or more sequential stages of LP compressor stator vanes 150 and LP compressor rotor blades 152 coupled to the LP shaft 126 progressively compress the second portion 148 of the air 142 flowing through the LP compressor 112 directed to the HP compressor 114. Next, one or more sequential stages of HP compressor stator vanes 154 and HP compressor rotor blades 156 coupled to the HP shaft 124 further compress the second portion 148 of the air 142 flowing through the HP compressor 114. This provides the compressed air 158 to the combustion section 116, where the compressed air 158 is mixed with fuel and combusted to provide combustion gases 160.

[0041] The combustion gases 160 flow through the HP turbine 118, where one or more sequential stages of HP turbine stator blades 162 and HP turbine rotor blades 164 coupled to the HP shaft 124 extract a first portion of the kinetic and / or thermal energy from the combustion gases 160. This energy extraction supports the operation of the HP compressor 114. The combustion gases 160 then flow through the LP turbine 120, where one or more sequential stages of LP turbine stator blades 166 and LP turbine rotor blades 168 coupled to the LP shaft 126 extract a second portion of the thermal and / or kinetic energy from the combustion gases 160. This energy extraction rotates the LP shaft 126, thereby supporting the operation of the LP compressor 112 and / or the rotation of the fan shaft 128. The combustion gases 160 then exit the core turbine 104 through the exhaust section 122 of the core turbine 104.

[0042] Together with the first turbofan engine 100, the core turbine 104 functions similarly and is similar to the environment seen in a land-based gas turbine engine, a turbojet engine in which the ratio of the first portion 146 of air 142 to the second portion 148 of air 142 is less than that of a turbofan engine, and a non-ducted fan engine in which the fan section 106 does not have a nacelle 134, 135. In each of the turbofan engine, the turbojet engine, and the non-ducted engine, a speed reduction device (e.g., a speed reduction gearbox 130) may be included between any shaft and the spool. For example, the speed reduction gearbox 130 may be provided between the LP shaft 126 and the fan shaft 128 of the fan section 106.

[0043] As depicted therein, the first turbofan engine 100 defines an axial direction A, a radial direction R, and a circumferential direction C. Generally, the axial direction A extends generally parallel to the axial centerline axis 102 , the radial direction R extends orthogonally outward from the axial centerline axis 102 , and the circumferential direction C extends concentrically about the axial centerline axis 102 .

[0044] Figure 2 During an Inlet Flow Separation (IFS) event Figure 1 A schematic cross-sectional view of a first high bypass turbofan gas turbine engine 100 is shown. Figure 2 In FIG. 1 , an IFS event is represented by an example arrow 202, which points toward Figure 1 The fan section 106 is moved toward the middle or middle section, and / or more generally toward Figure 1 The axial centerline axis 102 moves. For example, arrow 202 can represent Figure 1 The air 142 separated at the inlet section (eg, the nacelle inlet section) 204, 206 of the nacelles 134, 135. In such an example, an IFS event may cause Figure 1 The pressure (eg, air pressure) experienced by fan blades 132 and / or a portion of fan section 106 is asymmetric.

[0045] exist Figure 2 In the example, the IFS event may be caused by an adverse flight condition. For example, the first turbofan engine 100 may be coupled to the aircraft and may cause an IFS event in response to takeoff of the aircraft. In other examples, the first turbofan engine 100 may be coupled to the aircraft and may cause an IFD event in response to a crosswind (e.g., a crosswind condition, a crosswind event, etc.) while the aircraft is in flight.

[0046] exist Figure 2 In FIG. 1 , the cabin entrance sections 204 and 206 include a first cabin entrance section 204 and a second cabin entrance section 206. Figure 2 In FIG. 1 , the first nacelle inlet section 204 has a first outer lip (eg, a first outer lip surface, a first outer lip section, etc.) 208 and a first inner lip (eg, a first inner lip surface, a first inner lip section, etc.) 210. Figure 2 , the second nacelle inlet section 206 has a second outer lip (eg, a second outer lip surface, a second outer lip section, etc.) 212 and a second inner lip (eg, a second inner lip surface, a second inner lip section, etc.) 214 .

[0047] In some examples, fan blades 132 are subjected to stresses (e.g., mechanical stresses, vibration stresses, etc.) in response to an IFS event. In response to the stresses, one or more fan blades 132 may structurally degrade, deteriorate, weaken, etc. over time and may result in reduced reliability and / or operational life of fan blades 132. For example, in response to an IFS event, one or more fan blades 132 may be damaged.

[0048] In some examples, an IFS event may cause Figure 1 The pressure at the inlet portion 144 of the compressor 112 may be significantly asymmetric, which may cause compressor or engine surge. For example, in response to an IFS event, at least one of the LP compressor 112 or the HP compressor 114 may experience compressor surge. In such an example, compressor surge may cause at least one of the LP compressor 112 or the HP compressor 114 to stall, and / or more generally may cause Figure 1-2 The core turbine 104 stalls.

[0049] Figure 3 is a schematic cross-sectional view of a second example high bypass turbofan gas turbine engine 300 including an example controller (eg, an IFS controller) that monitors inlet flow separation using example pressure sensors 304, 306, 308, 310. The second turbofan engine 300 may be Figure 1-2 For example, the second turbofan engine 300 may include Figure 1 All components of the first turbofan engine 100, such as Figure 1-2 The gas turbine engine 104, the tubular casing 108, the LP compressor 112, the HP compressor 114, etc. In such an example, the combination Figure 1-2 The description of the first turbofan engine 100 may be applicable to Figure 3 The second turbofan engine 300.

[0050] exist Figure 3 In the embodiment, the IFS controller 302 is a full authority digital engine control (FADEC) unit. Alternatively, the IFS controller 302 may be an engine control unit (ECU), an electronic engine control (EEC) unit, etc., or any other type of data acquisition and / or control computing device, processor platform (e.g., a processor-based computing platform), etc. Figure 3 In the embodiment of the present invention, IFS controller 302 is included in second nacelle 135. Alternatively, IFS controller 302 may be included at any other location of second turbofan engine 300 (eg, first nacelle 134).

[0051] exist Figure 3In FIG. 1 , the pressure sensors 304 , 306 , 308 , and 310 include a first example pressure sensor 304 , a second example pressure sensor 306 , a third example pressure sensor 308 , and a fourth example pressure sensor 310 . Figure 3 In FIG. 1 , the first pressure sensor 304 is coupled to the first outer lip 208 of the first nacelle 134 . Figure 3 In the embodiment of the present invention, the second pressure sensor 306 is coupled to the first inner lip 210 of the first nacelle 134. The first pressure sensor 304 is configured to measure the first air pressure at the first outer lip 208. In the event of an IFS (e.g., Figure 2-3 During an IFS event as depicted in FIG. 1 , the first air pressure may approximate a stagnation pressure. The second pressure sensor 306 is configured to measure a second air pressure at the first inner lip 210. Figure 3 In the embodiment, the second air pressure can be approximated to the static pressure.

[0052] exist Figure 3 In FIG. 1 , the third pressure sensor 308 is coupled to the second outer lip 212 of the second nacelle 135 . Figure 3 In the embodiment of the present invention, the fourth pressure sensor 310 is coupled to the second inner lip 214 of the second nacelle 135. The third pressure sensor 308 is configured to measure the third air pressure at the second outer lip 212. In the event of an IFS (e.g. Figure 2-3 During an IFS event as depicted in FIG. 2 ), the third air pressure may approximate the stagnation pressure. The fourth pressure sensor 310 is configured to measure the fourth air pressure at the second inner lip 214. Figure 3 In the equation, the fourth gas pressure can be approximated to the static pressure.

[0053] exist Figure 3 In the embodiment, the first pressure sensor 304, the second pressure sensor 306, the third pressure sensor 308 and the fourth pressure sensor 310 are wireless sensors (e.g., wireless pressure sensors, wireless piezoelectric pressure sensors, wireless passive piezoelectric pressure sensors, etc.). For example, the first pressure sensor 304, the second pressure sensor 306, the third pressure sensor 308 and the fourth pressure sensor 310 may be wireless passive piezoelectric pressure sensors. Alternatively, one or more of the first pressure sensor 304, the second pressure sensor 306, the third pressure sensor 308 and / or the fourth pressure sensor 310 may be wired pressure sensors (e.g., wired pressure sensors, wired piezoelectric pressure sensors, wired passive piezoelectric pressure sensors, etc.). Alternatively, one or more of the first pressure sensor 304, the second pressure sensor 306, the third pressure sensor 308 and / or the fourth pressure sensor 310 may be different types of sensors, such as diaphragm pressure sensors, pitot tubes, etc.

[0054] exist Figure 3In FIG. 1 , the first pressure sensor 304 and the second pressure sensor 306 are communicatively coupled to a first example antenna (eg, antenna module) 312. Figure 3 In FIG. 1 , the third pressure sensor 308 and the fourth pressure sensor 310 are communicatively coupled to the second example antenna 314. Figure 3 In the embodiment, the first antenna 312 is included in the first nacelle 134 and the second antenna 314 is included in the second nacelle 135. Alternatively, both antennas 312, 314 may be included in the first nacelle 134, while in other examples, both antennas 312, 314 may be included in the second nacelle 135.

[0055] exist Figure 3 In an exemplary embodiment, the first antenna 312 and the second antenna 314 are coupled (e.g., communicatively coupled, electrically coupled, etc.) to the IFS controller 302 via a wired connection (not shown). Alternatively, one or both of the antennas 312, 314 may be coupled to the IFS controller 302 via a wireless connection. In an exemplary operation, the first pressure sensor 304 and the second pressure sensor 306 may transmit pressure data (e.g., air pressure data, air pressure measurements, etc.) to the IFS controller 302 via the first antenna 312. In an exemplary operation, the third pressure sensor 308 and the fourth pressure sensor 310 may transmit pressure data (e.g., air pressure data, air pressure measurements, etc.) to the IFS controller 302 via the second antenna 314.

[0056] exist Figure 3 In FIG. 1 , turbofan engine 300 includes example acceleration sensors 316 , 318 in example bearing section 320 . Figure 3 , bearing section 320 includes, corresponds to and / or otherwise represents example bearings 317, 319 (eg, ball bearings, roller bearings, etc.) to support fan shaft 128. Figure 3 In the embodiment, acceleration sensors 316, 318 are coupled to the bearing segment 320 (eg, coupled to one or more bearings 317, 319 included in the bearing segment 320) to monitor and / or otherwise measure forces experienced by the bearing (eg, acceleration forces, vibration forces, etc.).

[0057] exist Figure 3 In FIG. 1 , the acceleration sensors 316 and 318 include a first example acceleration sensor 316 and a second example acceleration sensor 318. Figure 3 In the embodiment, the acceleration sensors 316, 318 are accelerometers. For example, one or more of the acceleration sensors 316, 318 may be a vibration sensor (e.g., a vibration sensor including a piezoelectric crystal element), a gyroscope sensor, or a velocity sensor. Figure 3 In FIG. 1 , the first acceleration sensor 316 is coupled to a first side of the fan shaft 128 . Figure 3In FIG. 3 , a first acceleration sensor 316 is coupled to a first example bearing 317 of bearings 317, 319 included in a bearing section 320. Figure 3 In FIG. 1 , the second acceleration sensor 318 is coupled to a second side of the fan shaft 128 , wherein the second side is on an opposite side of the axial centerline axis 102 . Figure 3 , a second acceleration sensor 318 is coupled to a second example bearing 319 of the bearings 317 , 319 included in the bearing section 320 .

[0058] Figure 4A is a schematic cross-sectional view of a third example high bypass turbofan gas turbine engine 400, which includes Figure 3 The third turbofan engine 400 may include an IFS controller 302 and antennas 312, 314. Alternatively, the third turbofan engine 400 may not include one or both of the antennas 312, 314. The third turbofan engine 400 may be Figure 1-2 The first turbofan engine 100 or a portion thereof, and / or Figure 3 Example implementation of the second turbofan engine 300 or a portion thereof. For example, the third turbofan engine 400 may include Figure 1-2 The first turbofan engine 100 and / or Figure 3 One or more components of the second turbofan engine 300, such as Figure 1-3 The gas turbine engine 104, the tubular casing 108, the LP compressor 112, the HP compressor 114, etc., Figure 3 IFS controller 302, antennas 312, 314, etc., and / or combinations thereof. In such an example, in combination Figure 1-2 Description and / or incorporation of the first turbofan engine 100 Figure 3 The description of the second turbofan engine 300 may be applicable to Figure 4A of the third turbofan engine 400.

[0059] exist Figure 4A In the third turbofan engine 400, the example actuators 402, 404 are used to adjust the contribution of airflow from at least one of the first example section (e.g., first airflow section, first airflow contribution section, first airflow portion, first airflow area, first airflow zone, etc.) 406 or the second example section (e.g., second airflow section, second airflow contribution section, second airflow portion, second airflow area, second airflow zone, etc.) 408 to the third example section (e.g., third airflow section, third airflow contribution section, third airflow portion, third airflow area, third airflow zone, etc.) 410. Figure 4AIn FIG. 1 , the actuators 402 , 404 include: a first example actuator 402 included in the first nacelle 134 ; and a second example actuator 404 included in the second nacelle 135 .

[0060] exist Figure 4A , the first section 406 corresponds to the gas flow section between the LP compressor 112 and the HP compressor 114 and may generally be referred to herein as the “core”. Figure 4A , second section 408 may correspond to a section of the airflow behind fan blades 132 and in front of exit guide vanes 136. Figure 4A 1 , third segment 410 may correspond to an airflow segment in front of fan blades 132. For example, third segment 410 may include, correspond to, and / or otherwise represent fan segment 106.

[0061] exist Figure 4A In the embodiment, the airflow segments 406, 408, 410 are fluidly coupled and / or otherwise connected via example conduits (e.g., airflow conduits, exhaust passages, exhaust pathways, etc.) 412, 414. For example, airflow from the first segment 406 and / or the second airflow segment 408 can be directed via conduits 412, 414 to the third airflow segment 410. The conduits 412, 414 include: a first example conduit 412, which is included in the first nacelle 134; and a second example conduit 414, which is included in the second nacelle 135. In Figure 4A In the embodiment, the ducts 412, 414 are made of the same material and / or are otherwise constructed as the nacelles 134, 135. For example, the ducts 412, 414 may be constructed of one or more composite materials, one or more metallic materials, etc. and / or combinations thereof.

[0062] exist Figure 4A In the embodiment, the first conduit 412 has a first opening (e.g., a first conduit opening) 416, a second opening 418 (e.g., a second conduit opening) and a third opening (e.g., a third conduit opening) 420. The first opening 416 of the first conduit 412 is a first inlet (e.g., a first conduit inlet) coupled to the first section 406. The first opening 416 of the first conduit 412 is configured to obtain airflow (e.g., pressurized airflow) from the first section 406. The second opening 418 of the first conduit 412 is a second inlet (e.g., a second conduit inlet) coupled to the second section 408. The second opening 418 of the first conduit 412 is configured to obtain airflow (e.g., ambient airflow, non-pressurized airflow, incoming airflow, etc.) from the second section 408. The third opening 420 of the first conduit 412 is an outlet (e.g., a conduit outlet) coupled to the third section 410. The third opening 420 of the first conduit 412 is configured to discharge and / or otherwise output the airflow to the third section 410.

[0063] exist Figure 4A In the embodiment, the second conduit 414 has a first opening (e.g., a first conduit opening) 422, a second opening 424 (e.g., a second conduit opening) and a third opening (e.g., a third conduit opening) 426. The first opening 422 of the second conduit 414 is a first inlet (e.g., a first conduit inlet) coupled to the first section 406. The first opening 422 of the second conduit 414 is configured to obtain airflow from the first section 406. The second opening 424 of the second conduit 414 is a second inlet (e.g., a second conduit inlet) coupled to the second section 408. The second opening 424 of the second conduit 414 is configured to obtain airflow from the second section 408. The third opening 426 of the second conduit 414 is an outlet (e.g., a conduit outlet) coupled to the third section 410. The third opening 420 of the second conduit 414 is configured to discharge and / or otherwise output the airflow to the third section 410.

[0064] exist Figure 4A , airflow (e.g., exhaust airflow) from ducts 412, 414 is discharged in a direction opposite to the direction of air 142 (e.g., oncoming air 142 at inlet portion 144) and introduced into third section 410. Exhaust airflow introduced into third section 410 from ducts 412, 414 forces air 142 to flow around the exhaust airflow. Advantageously, the exhaust airflow introduced into third section 410 simulates and / or otherwise acts as a "thick" nacelle lip to reduce and / or otherwise eliminate IFS at inlet portion 144.

[0065] exist Figure 4A 4, airflow from ducts 412, 414 may be obtained from first section 406 and / or second section 408 and may therefore be delivered to third section 410 at a relatively high pressure. Airflow from ducts 412, 414 is introduced to third section 410 at an angle relative to air 142. Alternatively, airflow from ducts 412, 414 may be introduced to third section 410 at any angle based on the design of nacelles 134, 135 and / or more generally third turbofan engine 400.

[0066] exist Figure 4A, the actuators 402, 404 are valves actuated by solenoids and / or otherwise controlled. Alternatively, the actuators 402, 404 may be any other type of actuator. The actuators 402, 404 are operable in at least three positions including a first position, a second position, and a third position. The first position, the second position, and the third position may correspond to the amount of opening of the actuators 402, 404 to different sections 406, 408, 410. For example, the actuators 402, 404 in the first position may direct a large amount of air from the first section 406 to the third section 410, and a small amount of air from the second section 408 to the third section 410. In such an example, the first position may correspond to the actuators 402, 404 opening 70%, 80%, 90%, etc. to the first section 406, and opening 30%, 20%, 10%, etc. to the second section 408.

[0067] In other examples, the actuators 402, 404 in the second position may direct an intermediate amount of air from the first section 406 to the third section 410, and direct an intermediate amount of air from the second section 408 to the third section 410. In such examples, the second position may correspond to the actuators 402, 404 being 45%, 50%, 55%, etc. open to the first section 406, and 55%, 50%, 45%, etc. open to the second section 408.

[0068] In still other examples, the actuators 402, 404 in the third position may direct a small amount of air from the first section 406 to the third section 410, and direct a large amount of air from the second section 408 to the third section 410. In such examples, the third position may correspond to the actuators 402, 404 being open 10%, 20%, 30%, etc. to the first section 406, and 90%, 80%, 70%, etc. to the second section 408. For example, the small amount of air is less than the medium amount of air, and the medium amount of air is less than the large amount of air.

[0069] exist Figure 4A , the first antenna 312 is coupled to the first actuator 402 via a wired connection, and the second antenna 314 is coupled to the second actuator 404 via a wired connection. Alternatively, the first antenna 312 may be coupled to the first actuator 402 via a first wireless connection and / or the second antenna 314 may be coupled to the second actuator 404 via a second wireless connection. For example, Figure 3The IFS controller 302 can transmit wireless commands, directions, instructions, etc. to one or more of the antennas 312, 314 to control one or more of the actuators 402, 404 to change position. By calling the actuators 402, 404 to change position, the airflow contribution from at least one of the first section 406 or the second section 408 to the third section 410 can be adjusted. Advantageously, by adjusting the airflow contribution to the first section 406, the IFS controller 302 can reduce and / or otherwise eliminate the IFS in response to an adverse flight condition of the third turbofan engine 400.

[0070] Advantageously, the IFS controller 302 can reduce and / or otherwise eliminate the IFS by routing pressurized airflow (e.g., airflow from the first segment 406), ambient airflow (e.g., airflow from the second segment 408), etc., and / or combinations thereof to the third segment 410. For example, in response to a detected first severity level of IFS, the IFS controller 302 can route a first portion of ambient air from the second segment 408 to the third segment 410. In such examples, in response to a detected second severity level of IFS being greater than a detected first severity level of IFS (e.g., the second severity level represents a greater or more severe IFS than the first severity level), the IFS controller 302 can (1) route a second portion of ambient air from the second segment 408 to the third segment 408 and / or (2) route a third portion of pressurized air from the first segment 406 to the third segment 408. In some such examples, the second portion of ambient air can be less than and / or otherwise different than the first portion of ambient air.

[0071] Figure 4B is a schematic cross-sectional view of a fourth example high bypass turbofan gas turbine engine 430, which includes Figure 3-4A IFS Controller 302, Figure 3 pressure sensors 304, 306, 308, 310, and Figure 3-4A The fourth turbofan engine 430 may be Figure 1-2 The first turbofan engine 100 or a portion thereof, Figure 3 a second turbofan engine 300 or a portion thereof, and / or Figure 4A Example implementation of the third turbofan engine 400 or a portion thereof. For example, the fourth turbofan engine 430 may include Figure 1-2 The first turbofan engine 100, Figure 3 The second turbofan engine 300 and / or Figure 4A One or more components of the third turbofan engine 400, such as Figure 1-3The gas turbine engine 104, the tubular casing 108, the LP compressor 112, the HP compressor 114, etc., Figure 3 IFS controller 302, pressure sensors 304, 306, 308, 310, antennas 312, 314, etc., and / or combinations thereof. In such an example, in combination Figure 1-2 Description of the first turbofan engine 100, incorporating Figure 3 Description of the second turbofan engine 300, and / or in combination Figure 4A The description of the third turbofan engine 400 may be applicable to Figure 4B of the fourth turbofan engine 430 .

[0072] exist Figure 4B In the IFS controller 302, the first pressure sensor 304 and the second pressure sensor 306 communicate with the first antenna 312 via a wireless connection and / or are otherwise communicatively coupled to the first antenna 312. Figure 4B In the embodiment, the first actuator 402 communicates with the first antenna 312 via a wired connection and / or is otherwise communicatively coupled to the first antenna 312. Alternatively, the first actuator 402 may communicate with the first antenna 312 via a wireless connection and / or is otherwise communicatively coupled to the first antenna 312.

[0073] exist Figure 4B In the embodiment of the present invention, the IFS controller 302, the third pressure sensor 308, and the fourth pressure sensor 310 are in communication with the second antenna 314 via a wireless connection and / or are otherwise communicatively coupled to the second antenna 314. Figure 4B In the embodiment, the second actuator 404 communicates with the second antenna 314 via a wired connection and / or is otherwise communicatively coupled to the second antenna 314. Alternatively, the second actuator 404 may communicate with the second antenna 314 via a wireless connection and / or is otherwise communicatively coupled to the second antenna 314.

[0074] exist Figure 4B In FIG. 4 , the fourth turbofan engine 430 includes an IFS controller 302 to detect an IFS at the inlet portion 144 based on a pressure measurement from at least one of the first pressure sensor 304 , the second pressure sensor 306 , the third pressure sensor 308 , or the fourth pressure sensor 310 . Figure 4B In FIG. 1 , the IFS controller 302 may obtain pressure measurements from one or more of the pressure sensors 304 , 306 , 308 , 310 via corresponding one or more of the antennas 312 , 314 . Figure 4BIn some examples, the IFS controller 302 can control one or more of the actuators 402, 404 based on the IFS detection. For example, the IFS controller 302 can generate a command and transmit the command to the first actuator 402 and / or the second actuator 404. In such examples, in response to obtaining the command, the first actuator 402 can move from a first position to a second position, the second actuator 404 can move from a third position to a fourth position, and so on. In some such examples, the movement of the first actuator 402 and / or the second actuator 404 can adjust the airflow contribution from at least one of the first segment 406 or the second segment 408 to the third segment 410.

[0075] Figure 5 is during an inlet flow separation event Figure 4B A schematic cross-sectional view of a fourth high bypass turbofan gas turbine engine 430. Figure 5 , two different airflows 502, 504 are depicted, including a first airflow 502 and a second airflow 504. The first airflow 502 corresponds to a separation of the air 142 incident upon the nacelle inlet sections 204, 206, which causes the air 142 to move toward the axial centerline axis 102. The first airflow 502 may cause compressor or engine surge, increased engine vibration response, etc., and / or combinations thereof, which may result in reduced reliability and / or operational life of the fan blades 132 or any other component of the third turbofan engine 400.

[0076] exist Figure 5 , the second airflow 504 corresponds to an example in which separation of the air 142 incident on the cabin inlet sections 204, 206 does not occur and / or is otherwise minimized. For example, the second airflow 504 may correspond to an example in which the second airflow 504 is incident on the cabin inlet sections 204, 206. Figure 2 The arrow 202 represents an IFS event. Figure 5 , the second airflow 504 flows along the inner lips 210, 214 of the third turbofan engine 400. For example, in response to the IFS controller 302 detecting the first airflow 502 (eg, detecting an IFS event), the IFS controller 302 may control Figure 4A and / or one or more of the actuators 402, 404 of 4B to discharge the airflow from at least one of the first section 406 or the second section 408 to the third section 410. Advantageously, the IFS controller 302 can adjust the first airflow 502 to the second airflow 504 in response to adjusting the airflow contribution from at least one of the first section 406 or the second section 408 to the third section 410.

[0077] Figure 6 yes Figure 3-5 The IFS controller 302 is configured to detect and / or control Figure 3-5 The IFS at the inlet 144 of the turbofan engine 300, 400, 430 of the embodiment of the present invention is configured to control the IFS at the inlet 144 of the turbofan engine 300, 400, 430. In response to the detection of the IFS, the IFS controller 302 is configured to control one or more of the actuators 402, 404 of Figures 4-5 to control the contribution of the airflow from at least one of the core (e.g., the first section 406 of Figures 4-5) or the rear of the fan 132 (e.g., the second section 408 of Figures 4-5) to the front of the fan 132 to reduce and / or otherwise eliminate the IFS.

[0078] exist Figure 6 In the example, an embodiment of the IFS controller 302 includes an example communication interface 610, an example inlet flow separation parameter determiner 620, an example inlet flow separation severity level parameter determiner 630, an example inlet flow separation detector 640, an example command generator 650, an example alarm generator 660, and an example database 670. Figure 6 , database 670 includes example flight data 672 , example sensor data 674 , example IFS parameters 676 , example IFS severity level parameters 678 , example IFS detection model 680 , and example IFS control measures 682 .

[0079] exist Figure 6 In the example of FIG. 6 , the IFS controller 302 includes a communication interface 610 to communicate with a sensor (e.g., Figure 3-5 The first pressure sensor 304, the second pressure sensor 306, the third pressure sensor 308, the fourth pressure sensor 310, the first acceleration sensor 316 and / or the second acceleration sensor 318), an antenna (e.g., Figure 3-5 The communication interface 610 communicates with the first antenna 312 and / or the second antenna 314 of FIG. 4-5 ), an actuator (e.g., the first actuator 402 and / or the second actuator 404 of FIG. 4-5 ), and / or an example computing system 612. For example, the computing system 612 can correspond to one or more processor-based platforms associated with an aircraft, one or more processor-based platforms associated with an aircraft or turbofan engine manufacturer, etc. In some examples, the communication interface 610 obtains data or information from one or more of the sensors 304, 306, 308, 310, the antennas 312, 314, the actuators 402, 404, and / or the computing system 612 via a wired connection, a wireless connection, etc., and / or a combination thereof.

[0080] In some examples, communication interface 610 obtains flight data 672 from a computing system on board the aircraft (eg, computing system 612). For example, communication interface 610 may obtain information related to Figure 3-5The communication interface 610 may store the altitude data, speed data (e.g., airspeed data), etc. associated with the turbofan engine 300, 400, 430 and / or more generally the aircraft to which the turbofan engine 300, 400, 430 is coupled. In such an example, the communication interface 610 may store the altitude data, speed data, etc. as flight data 672 in the database 670.

[0081] In some examples, communication interface 610 obtains IFS commands from computing system 612. For example, communication interface 610 may obtain IFS commands from a computer system 612 connected to Figure 4A The aircraft with the third turbofan engine 400 configured to operate at a predetermined speed may receive an IFS command from a pilot controlling the aircraft from a cockpit of the aircraft, etc. In such an example, the IFS command may increase the airflow contribution from the first section 406 or the second section 408 to the third section 410. In other examples, the IFS command may decrease the airflow contribution from the first section 406 or the second section 408 to the third section 410.

[0082] In some examples, communication interface 610 transmits alerts, data, information, etc. to a computing system on the aircraft. For example, communication interface 610 can transmit the alert to the aircraft control system to display the alert on a user interface of a display in the cockpit for presentation to the pilot. In such an example, the alert can include data, information, etc. as described below in conjunction with alert generator 660.

[0083] In some examples, communication interface 610 receives Figure 3-5 The communication interface 610 may obtain sensor data from one or more of the sensors 304, 306, 308, 310. For example, the communication interface 610 may obtain pressure data (e.g., air pressure data) from the first pressure sensor 304 and the second pressure sensor 306 via the first antenna 312. In other examples, the communication interface 610 may obtain pressure data (e.g., air pressure data) from the third pressure sensor 308 and the fourth pressure sensor 310 via the second antenna 314.

[0084] In some examples, the communication interface 610 transmits commands, directions, instructions, etc. to one or more of the actuators 402, 404. For example, the communication interface 610 can transmit a command to the actuators 402, 404 via a wired connection to adjust from a first position to a second position. In other examples, the communication interface 610 can transmit a command to the first actuator 402 via the first antenna 312 to adjust from the first position to the second position. In still other examples, the communication interface 610 can transmit a command to the second actuator 404 via the second antenna 314 to adjust from the first position to the second position.

[0085] exist Figure 6In the embodiment of the present invention, the IFS controller 302 includes an IFS parameter determiner 620 to determine IFS parameters 676 based on sensor data associated with the turbofan engine and store the IFS parameters 676 in the database 670. The IFS parameters 676 may correspond to processed data values ​​used by the IFS controller 302 to detect an IFS event and / or determine a quantification or severity of an IFS event. For example, the IFS parameter determiner 620 may determine the value of the IFS parameter 676 associated with the turbofan engine. Figure 3-5 One or more IFS parameters 676 associated with the turbofan engine 300, 400, 430 include a first air pressure value at the first outer lip 208, a second air pressure value at the first inner lip 210, a third air pressure value at the second outer lip 212, a fourth air pressure value at the second inner lip 214, air density, Mach number and / or bearing load.

[0086] In some examples, the IFS parameter determiner 620 is based on Figure 3-5 The IFS parameter determiner 620 may determine the first air pressure value based on the first air pressure data from the first pressure sensor 304. Figure 3-5 The IFS parameter determiner 620 may determine the second air pressure value based on the second air pressure data from the second pressure sensor 306. Figure 3-5 The IFS parameter determiner 620 may determine the third air pressure value based on the third air pressure data from the third pressure sensor 308. Figure 3-5 The fourth air pressure value is determined based on the fourth air pressure data of the fourth pressure sensor 310.

[0087] In some examples, IFS parameter determiner 620 determines air density based on altitude data. For example, IFS parameter determiner 620 may determine air density by mapping the altitude of a turbofan engine 300, 400, 430, an aircraft coupled to a turbofan engine 300, 400, 430, etc. stored in flight data 672 to air density. Figure 1-5 The air density of the air 142 is determined by the altitude. In such an example, the altitude-air density mapping can be stored in a lookup table (e.g., a lookup table in the database 670).

[0088] In some examples, the IFS parameter determiner 620 determines the Mach number based on the speed data. For example, the IFS parameter determiner 620 may obtain the speed data from the flight data 672 and determine the Mach number based on the obtained speed data.

[0089] In some examples, the IFS parameter determiner 620 determines the bearing load, force value, vibration response, etc. and / or a combination thereof based on the acceleration data. For example, the communication interface 610 may be coupled to Figure 3-5One or more of the acceleration sensors 316, 318 of one or more of the bearings 317, 319 of the bearing section 320 of the engine 104 obtain acceleration data. The IFS parameter determiner 620 can determine a first bearing load, a first force value, a first vibration response, etc. associated with the first bearing 317 based on the first acceleration data obtained from the first acceleration sensor 316. The IFS parameter determiner 620 can determine a second bearing load, a second force value, a second vibration response, etc. associated with the second bearing 319 based on the second acceleration data obtained from the second acceleration sensor 318.

[0090] exist Figure 6 6, the IFS controller 302 includes an IFS severity level parameter determiner 630 to determine a severity level parameter, such as an IFS severity level parameter 678, based on the IFS parameter 676. The IFS severity level parameter determiner 630 can store the IFS severity level parameter 678 in the database 670. The IFS severity level parameter 678 can correspond to a processed data value used by the IFS controller 302 to determine a quantification or severity of an IFS event. For example, the IFS severity level parameter determiner 630 can determine a value corresponding to the severity of the IFS event. Figure 3-5 One or more IFS severity level parameters 678 associated with the turbofan engine 300, 400, 430 of the embodiment of the present invention include a first example severity level parameter 702 ( Figure 7 ), a second example severity level parameter 704 based on a pressure difference between the external cabin pressure and the internal cabin pressure ( Figure 7 ), and / or a third example severity level parameter 706 based on engine vibration response ( Figure 7 ).

[0091] Go to Figure 7 , the example IFS severity level table 700 depicts the severity levels of Figure 3-6 The IFS controller 302 is used to detect Figure 3-5 700. The IFS severity level table 700 represents example logic that the IFS controller 302 may use to determine a first IFS severity level parameter 702, a second IFS severity level parameter 704, and a third IFS severity level parameter 706. Alternatively, the IFS controller 302 may determine a first IFS severity level parameter 702, a second IFS severity level parameter 704, and a third IFS severity level parameter 706. Figure 7 Fewer or more severity level parameters as depicted in .

[0092] exist Figure 7 , the first IFS severity level parameter 702 indicates a flow direction (eg, an unfavorable flow direction, an unfavorable airflow direction, etc.). Figure 6The IFS severity level parameter determiner 630 may determine the flow direction based on a difference between Ps (e.g., a first pressure value from the first pressure sensor 304, a second pressure value from the third pressure sensor 308, etc.) and Pt (e.g., a pressure threshold), where Pt may be a predefined or predetermined pressure value. In such an example, Ps corresponds to a pressure value at the nacelle outer lip, such as a pressure value at the first outer lip 208 (e.g., a pressure value or measurement from the first pressure sensor 304), a pressure value at the second outer lip 212 (e.g., a pressure value or measurement from the third pressure sensor 308), etc. In response to determining that the difference satisfies the threshold (such as the difference is less than 0 (e.g., Ps<Pt) or a different value), the IFS severity level parameter determiner 630 may determine that the flow direction is substantially parallel (e.g., parallel in a range of -5 to 5 degrees, -2 to 2 degrees, etc.) to the nacelle outer lip.

[0093] In some examples, the IFS severity level parameter determiner 630 may determine that the turbofan engine 300, 400, 430 is experiencing a crosswind based on the flow direction. For example, the IFS severity level parameter determiner 630 may detect a crosswind based on a difference of approximately 0 (e.g., Ps=Pt, Ps is approximately equal to Pt, etc.), which may indicate that the flow direction is vertical (e.g., 90 degrees relative to the nacelle outer lip, vertical in a range of 85 to 95 degrees relative to the nacelle outer lip, etc.) and / or otherwise incident on the nacelle outer lip. In such an example, the IFS severity level parameter determiner 630 may determine that the airflow is stagnant based on the difference being approximately 0, which may indicate a crosswind.

[0094] In some examples, the second IFS severity level parameter 704 indicates a cabin inlet pressure difference based on a difference between a first pressure value (Psouter) at a cabin outer lip and a second pressure value (Psinner) at a cabin inner lip. For example, the IFS severity level parameter determiner 630 may determine the second IFS severity level parameter 704 by determining a difference between a first pressure value at the first outer lip 208 of the first nacelle 134 and a second pressure value at the first inner lip 210 of the first nacelle 134. In such an example, the IFS severity level parameter determiner 630 may determine the second IFS severity level parameter 704 by normalizing the difference to the Mach number (υ) and air density (ρ) of the ambient air, as described in the following formula (1):

[0095]

[0096] In some examples, the third IFS severity level parameter 706 is based on the accelerometer data from the bearing (e.g., Figure 3-5The acceleration data of the acceleration sensors 316, 318) coupled to the bearings 317, 319 indicates the engine vibration response. For example, the IFS severity level parameter determiner 630 can generate a parameter including the following: Figure 3-5 The third IFS severity level parameter 706 is determined based on an acoustic or vibration response of a load at a bearing (eg, the first bearing 317 , the second bearing 319 , etc.) in the bearing section 320 of the engine 104 .

[0097] exist Figure 7 , the IFS severity level parameter determiner 630 may determine the first IFS severity level parameter 702, the second IFS severity level parameter 704, and the third IFS severity level parameter 706 based on example weighting factors (e.g., scaling factors) 708, 710, 712. The weighting factors 708 include: a first example weighting factor (wtFD) 708, which corresponds to a flow direction weighting factor; a second example weighting factor (wtDP) 710, which corresponds to a pressure difference weighting factor; and a third example weighting factor (wtEVR), which corresponds to an engine vibration response weighting factor. The IFS severity level parameter determiner 630 may use the weighting factors to increase or decrease the contribution, impact, and / or influence of each of the IFS severity level parameters 702, 704, 706 on the detection of an IFS event and / or the quantification of the severity of the detected IFS event.

[0098] exist Figure 7 In the example, the IFS severity level parameter determiner 630 may determine the first IFS severity level parameter 702 based on the product of the output of the flow direction definition / determination logic and the first weighting factor 708 and / or other mathematical operations. Figure 7 In the example, the IFS severity level parameter determiner 630 may determine the second IFS severity level parameter 704 based on the product of the output of the cabin inlet pressure difference definition / determination logic and the second weighting factor 710 and / or other mathematical operations. Figure 7 , the IFS severity level parameter determiner 630 may determine the third IFS severity level parameter 706 based on a product of an output of the engine vibration response definition / determination logic and a third weighting factor 712 and / or other mathematical operations.

[0099] Return to Figure 6 The IFS controller 302 includes an IFS detector 640 to detect based on the IFS parameter 676 Figure 3-5The IFS detector 640 may be used to detect an IFS condition, event, etc. of a turbofan engine 300, 400, 430. In some examples, the IFS detector 640 detects IFS based on a comparison of an IFS detection model with one or more of an IFS detection model 680 stored in a database 670. For example, the IFS detector 640 may generate an IFS detection model based on a probability density function (PDF). The IFS detector 640 may generate and / or otherwise determine a PDF based on at least one of a first IFS severity level parameter 702, a second IFS severity level parameter 704, or a third IFS severity level parameter 706. Alternatively, the IFS detection model may be a machine learning model, such as a neural network (e.g., a convolutional neural network, a deep neural network, etc.).

[0100] Back to Figure 7 , the IFS detector 640 may generate an IFS detection model including a PDF based on the first IFS severity level parameter 702, the second IFS severity level parameter 704, or the third IFS severity level parameter 706. The IFS detector 640 may compare the PDF with the first example PDF 714, the second example PDF 716, and the third example PDF 718. The PDFs 714, 716, and 718 may be stored in the database 670 as an IFS detection model 680. Figure 7 , the first PDF 714 may correspond to Figure 1-5 A no IFS condition or a clean airflow condition at the inlet 144 of FIG.

[0101] exist Figure 7 , the second PDF 716 may correspond to a PDF generated based on the unfavorable inlet flow direction and the impact on the oncoming inlet airflow of the fan 132. The IFS detector 640 may determine the unfavorable inlet flow direction based on the first IFS severity level parameter 702. The IFS detector 640 may determine the impact on the oncoming inlet airflow of the fan 132 based on the second IFS severity level parameter 704. Figure 7 , the unfavorable inlet flow direction and the impact on the oncoming inlet airflow of the fan 132 may result in an average shift of the first PDF 714 to generate a second PDF 716 .

[0102] exist Figure 7 , the third PDF 718 may correspond to a PDF generated based on the unfavorable inlet flow direction, the effect on the oncoming inlet airflow of the fan 132, and the unfavorable engine vibration response. The IFS detector 640 may determine the unfavorable engine vibration response based on the third IFS severity level parameter 706. Figure 7In some examples, the unfavorable inlet flow direction, the impact on the oncoming inlet airflow of the fan 132, and the unfavorable engine vibration response may cause the mean shift and standard deviation (STD DEV) of the first PDF 714 to change, thereby generating a third PDF 718. In some examples, the IFS detector 640 generates a third PDF 718 based on the PDFs and the IFS severity level parameters 702, 704, 706. Figure 7 The IFS at the inlet 144 of the turbofan engine 300 , 400 , 430 is detected by comparing the PDFs 714 , 716 , 718 .

[0103] Return to Figure 6 , the IFS controller 302 includes a command generator 650 to generate commands, directions, instructions, etc. to control and / or otherwise invoke one or more of the actuators 402, 404 of FIGS. 4-5. In some examples, the command generator 650 invokes the communication interface 610 to transmit a command to the first antenna 312 to relay the command to the first actuator 402 to move the first actuator 402 from a first position to a second position, wherein the first position is different from the second position. In some such examples, the command generator 650 may invoke the first actuator 402 to promote a high airflow contribution from the first segment 406 to the third segment 410 and a low airflow contribution from the second segment 408 to the third segment 410.

[0104] In some examples, the command generator 650 calls the communication interface 610 to transmit a command to the second actuator 404 via a wired connection (e.g., without transmitting a command to the second antenna 314). In such examples, the command generator 650 can call the second actuator 404 to adjust the position based on the command. In some such examples, the command generator 650 can call the second actuator 404 to promote a low airflow contribution from the first section 406 to the third section 410 and a high airflow contribution from the second section 408 to the third section 410. In other examples, the command generator 650 can call the second actuator 404 to promote a medium airflow contribution from the first section 406 to the third section 410 and a medium airflow contribution from the second section 408 to the third section 410.

[0105] In some examples, command generator 650 determines one or more of IFS control measures 682 based on IFS severity level parameter 678. Figure 6 In the embodiment of the present invention, the IFS control measures 682 are commands, instructions, command or instruction sequences, etc., and / or combinations thereof that can be used by the command generator 650 to reduce and / or otherwise eliminate IFS. For example, when the first IFS severity level parameter 702 indicates no IFS, the command generator 650 can determine not to deploy one of the IFS control measures 682.

[0106] In some examples, the command generator 650 deploys a first of the IFS control measures 682 based on the IFS severity level parameter 678. For example, when the first IFS severity level parameter 702 and / or the second IFS severity level parameter 704 indicate that substantially high IFS exists at the inlet 144, the command generator 650 may perform the first of the IFS control measures 682 by controlling the actuators 402, 404 to promote a high core airflow contribution (e.g., a high contribution of airflow from the first section 406) and a low fan airflow contribution (e.g., a low contribution of airflow from the second section 408). In such an example, the first of the IFS control measures 682 may include a command sequence in which the command generator 650 transmits a first command to the first actuator 402, transmits a second command to the second actuator 404, transmits the second command after the first command, and the like.

[0107] In some examples, the command generator 650 deploys a second one of the IFS control measures 682 based on the IFS severity level parameter 678. For example, when the first IFS severity level parameter 702 and / or the second IFS severity level parameter 704 indicate that a medium quantification of IFS is present at the inlet 144, the command generator 650 may perform the second one of the IFS control measures 682 by controlling the actuators 402, 404 to promote a medium core airflow contribution (e.g., a medium contribution of airflow from the first section 406) and a medium fan airflow contribution (e.g., a medium contribution of airflow from the second section 408). In such an example, the second one of the IFS control measures 682 may include a command sequence of the command generator 650 transmitting a first command to the first actuator 402, transmitting a second command to the second actuator 404, transmitting the second command after the first command, and the like.

[0108] In some examples, the command generator 650 deploys a third of the IFS control measures 682 based on the IFS severity level parameter 678. For example, when the first IFS severity level parameter 702 and / or the second IFS severity level parameter 704 indicate that substantially low IFS exists at the inlet 144, the command generator 650 may execute the third of the IFS control measures 682 by controlling the actuators 402, 404 to promote a low core airflow contribution (e.g., a low contribution of airflow from the first section 406) and a high fan airflow contribution (e.g., a high contribution of airflow from the second section 408). In such an example, the third of the IFS control measures 682 may include a command sequence in which the command generator 650 transmits a first command to the first actuator 402, transmits a second command to the second actuator 404, transmits the second command after the first command, and the like.

[0109] exist Figure 6In the example, the IFS controller 302 includes an alarm generator 660, in response to detecting Figure 3-5 The alarm generator 660 generates an alarm, alert, warning, etc. in response to an IFS at the inlet 144 of the turbofan engine 300, 400, 430. In some examples, the alarm generator 660 generates the alarm by generating a log and / or report, transmitting the alarm to be presented on one or more displays (e.g., one or more displays in the aircraft cockpit, or a smart phone, tablet or laptop display, etc.), transmitting the alarm to a network (e.g., an aircraft control network), etc. and / or a combination thereof.

[0110] In some examples, alert generator 660 stores information (e.g., generated alerts, logs, reports, etc.) in database 670 and / or retrieves information to be included in an alert (e.g., IFS parameters 676, IFS severity level parameters 678, etc.) from database 670. For example, alert generator 660 may store a report in database 670 including a maintenance alert for fan blades 132 based on the engine vibration response stored in IFS severity level parameters 678.

[0111] In some examples, the alert generator 660 associates the flight data 672 ( ) with the time before, during, and / or after the actuation of the first actuator 402 and / or the second actuator 404. Figure 6 ) and / or sensor data 674 ( Figure 6 ) and / or otherwise stored in the database 670. In such an example, the alert generator 660 may record which of the actuators 402, 404 were called in response to the IFS command, the position of one or more of the actuators 402, 404, etc., and / or combinations thereof.

[0112] exist Figure 6In the embodiment of the present invention, the IFS controller 302 includes a database 670 to record and / or otherwise store data, such as flight data 672, sensor data 674, IFS parameters 676, IFS severity level parameters 678, IFS detection models 680, and IFS control measures 682. The database 670 can be implemented by volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or non-volatile memory (e.g., flash memory). The database 670 can be additionally or alternatively implemented by one or more double data rate (DDR) memories (e.g., DDR, DDR2, DDR3, DDR4, mobile DDR (mDDR), etc.). The database 670 can be additionally or alternatively implemented by one or more mass storage devices (e.g., hard disk drives, optical disk drives, digital versatile disk drives, solid state disk drives, etc.). Although the database 670 is shown as a single database in the illustrated example, the database 670 may be implemented by any number and / or type of databases. In addition, the data stored in the database 670 may be in any data format, such as binary, comma-delimited, hexadecimal, JavaScript Object Notation (JSON), tab-delimited, Structured Query Language (SQL), XML, etc.

[0113] Despite Figure 6 It is shown in Figure 3-5 The IFS controller 302 is an example embodiment of the present invention, but may be combined, divided, rearranged, omitted, eliminated and / or implemented in any other manner. Figure 6 In addition, the example communication interface 610, the example IFS parameter determiner 620, the example IFS severity level parameter determiner 630, the example IFS detector 640, the example command generator 650, the example alarm generator 660, the example database 670 and / or more generally, Figure 3-5The example IFS controller 302 may be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, any of the example communication interface 610, the example IFS parameter determiner 620, the example IFS severity level parameter determiner 630, the example IFS detector 640, the example command generator 650, the example alarm generator 660, the example database 670, and / or more generally the example IFS controller 302 may be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, graphics processing units (GPUs), digital signal processors (DSPs), application specific integrated circuits (ASICs), programmable logic devices (PLDs), and / or field programmable logic devices (FPLDs). When any apparatus or system claims of this patent are read to cover pure software and / or firmware implementations, at least one of the example communication interface 610, the example IFS parameter determiner 620, the example IFS severity level parameter determiner 630, the example IFS detector 640, the example command generator 650, the example alarm generator 660, and / or the example database 670 is expressly defined herein as including a non-transitory computer-readable storage device or storage disk, such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc., containing the software and / or firmware. Further, except Figure 6 In addition to or in lieu of those shown in Figure 6 Those shown in Figure 3-5 The example IFS controller 302 may include one or more elements, processes and / or devices, and / or may include any one or more or all of the elements, processes and devices shown. As used herein, the phrase "communication" includes variations thereof, encompassing direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but additionally includes selective communication at periodic intervals, scheduled intervals, non-periodic intervals and / or one-time events.

[0114] exist Figure 8-12 The following table shows a representative method for implementing Figure 3-6 The IFS controller 302 is provided with a flowchart of example hardware logic, machine readable instructions, hardware implemented state machines and / or any combination thereof. The machine readable instructions may be one or more executable programs or portions of executable programs for use in conjunction with, for example, the following: Fig.13The program may be executed by a computer processor of the processor 1312 shown in the example processor platform 1300 discussed above. The program may be embodied in software stored on a non-transitory computer-readable storage medium (e.g., a CD-ROM, floppy disk, hard drive, DVD, Blu-ray disk, or memory associated with the processor 1312), however, the entire program and / or portions thereof may alternatively be executed by a device other than the processor 1312 and / or embodied in firmware or dedicated hardware. In addition, although reference is made to Figure 8-12 The flowchart shown in describes an example procedure, but many other methods of implementing the example IFS controller 302 may alternatively be used. For example, the order of execution of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuits, etc.) configured to perform the corresponding operations without executing software or firmware.

[0115] The machine-readable instructions described herein may be stored in one or more of a compressed format, an encrypted format, a segmented format, a compiled format, an executable format, a packaged format, and the like. The machine-readable instructions described herein may be stored as data (e.g., portions of instructions, code, representations of code, and the like) that can be used to create, manufacture, and / or generate machine-executable instructions. For example, the machine-readable instructions may be segmented and stored on one or more storage devices and / or computing devices (e.g., servers). The machine-readable instructions may require one or more of installation, modification, adaptation, updating, merging, supplementation, construction, decryption, decompression, unpacking, distribution, redistribution, compilation, and the like in order to make them directly readable, interpretable, and / or executable by a computing device and / or other machine. For example, the machine-readable instructions may be stored in multiple parts that are separately compressed, encrypted, and stored on separate computing devices, where the parts, when decrypted, decompressed, and combined, form a set of executable instructions that implement a program such as described herein.

[0116] In another example, the machine-readable instructions may be stored in a state in which they can be read by a computer, but require the addition of a library (e.g., a dynamic link library (DLL)), a software development kit (SDK), an application programming interface (API), etc., in order to execute the instructions on a particular computing device or other device. In another example, the machine-readable instructions and / or corresponding programs may need to be constructed (e.g., set up storage, data entry, network address recording, etc.) before the machine-readable instructions and / or corresponding programs can be executed in whole or in part. Therefore, the disclosed machine-readable instructions and / or corresponding programs are intended to cover such machine-readable instructions and / or programs, regardless of the specific format or state of the machine-readable instructions and / or programs when stored or otherwise at rest or transmitted.

[0117] The machine-readable instructions described herein may be represented by any past, present or future instruction language, scripting language, programming language, etc. For example, any of the following languages ​​may be used to represent machine-readable instructions: C, C++, Java, C#, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.

[0118] As described above, the present invention may be implemented using executable instructions (e.g., computer and / or machine readable instructions) stored on a non-transitory computer and / or machine readable medium (e.g., a hard drive, flash memory, read-only memory, compact disk, digital versatile disk, cache, random access memory and / or any other storage device or storage disk in which information is stored for any duration (e.g., for an extended period of time, permanently, transiently, temporarily buffered and / or cached information)). Figure 8-12 As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable storage device and / or storage disk and to exclude propagating signals and to exclude transmission media.

[0119] Figure 8 is a flow chart representing example machine readable instructions 800 that may be executed to implement Figure 3-6 The IFS controller 302 of FIGS. 4-5 regulates the airflow contribution to the inlet 144 of the third turbofan engine 400 . Figure 8 The machine readable instructions 800 of FIG. 8 begin at block 802 where the IFS controller 302 determines an inlet flow separation (IFS) parameter based on sensor data associated with the turbofan engine. For example, the IFS parameter determiner 620 ( Figure 6 ) can be based on the turbofan engine 300, 400, 430 ( Figure 3-5 ) in one or more associated sensor data 674 ( Figure 6) to determine the IFS parameter 676 ( Figure 6 ) in one or more. Fig. 9 Example instructions that may be executed to implement block 802 are described.

[0120] At block 804, the IFS controller 302 detects the IFS based on the IFS parameters. For example, the IFS detector 640 ( Figure 6 ) can be based on IFS parameter 676, IFS severity level parameter 678 ( Figure 6 ), etc., and / or a combination thereof to detect Figure 5 The second airflow 504 is composed of Figure 2 The arrow 202 indicates the IFS event, etc. Fig.10 Example instructions that may be executed to implement block 804 are described.

[0121] At block 806, the IFS controller 302 determines whether IFS is detected based on the IFS parameters. For example, the IFS detector 640 may not detect IFS based on the IFS parameters 676, the IFS severity level parameters 678, etc., and / or a combination thereof. In other examples, the IFS detector 640 may detect IFS based on the IFS parameters 676, the IFS severity level parameters 678, etc., and / or a combination thereof.

[0122] If the IFS controller 302 determines at block 806 that the IFS is not detected, control proceeds to block 816 to determine whether to continue monitoring the turbofan engine. If the IFS controller 302 determines at block 806 that the IFS is detected, the IFS controller 302 identifies an IFS control measure based on the IFS severity level parameter at block 808. For example, the IFS severity level parameter determiner 630 ( Figure 6 ) can determine the IFS severity level parameter 678 ( Figure 6 ) in one or more. In such an example, the command generator 650 ( Figure 6 ) can identify IFS control measures 682 based on IFS severity level parameters 678 ( Figure 6 ) in one or more. Fig.11 Example instructions that may be executed to implement block 808 are described.

[0123] At block 810, the IFS controller 302 determines whether an IFS control measure has been identified. For example, in response to determining that the IFS severity level parameter 678 does not indicate IFS, the command generator 650 may determine that there are no IFS control measures to deploy. In other examples, the command generator 650 may determine to invoke the actuators 402, 404 (or the like) based on the IFS severity level parameter 678 indicating low, medium, or high IFS at the inlet portion 144. Figure 4Aand / or 4B) to adjust IFS.

[0124] If at block 810, the IFS controller 302 determines that there is no identified IFS control measure, control proceeds to block 816 to determine whether to continue monitoring the turbofan engine. If at block 810, the IFS controller 302 determines that there is an identified IFS control measure, at block 812 the IFS controller 302 controls the actuator to adjust the airflow contribution to the inlet 144 of the turbofan engine 300, 400, 430. For example, the command generator 650 may transmit a command to the actuator 402, 404 to adjust the position, thereby adjusting the airflow contribution from the first section 406 and / or the second section 408 of Figures 4-5 to the third section 410.

[0125] At block 814, the IFS controller 302 generates an alarm. For example, the alarm generator 660 ( Figure 6 ) may generate an alert that includes flight data 672 ( Figure 6 ), sensor data 674, one or more IFS parameters 676, one or more IFS severity level parameters 678, or at least one of deployed one or more IFS control measures 682. In such an example, alert generator 660 may transmit the alert to a display for presentation to a pilot in a cockpit of the aircraft, store the alert in database 670 ( Figure 6 ) for maintenance tasks or improvements to be performed on the turbofan engines 300, 400, 430, etc., and / or combinations thereof.

[0126] At block 816, the IFS controller 302 determines whether to continue monitoring the turbofan engine. For example, the communication interface 610 ( Figure 6 ) may determine that the turbofan engine 300, 400, 430 is not in flight (e.g., the aircraft has landed on the ground, taxied to the gate, parked at the gate, etc.), and therefore determine not to continue monitoring the turbofan engine 300, 400, 430. In other examples, the communication interface 610 may determine to continue monitoring the turbofan engine 300, 400, 430 to determine whether the IFS has been reduced and / or otherwise eliminated in response to the IFS control measures 682 deployed at block 810.

[0127] If the IFS controller 302 determines at block 816 to continue monitoring the turbofan engine, control returns to block 802 to determine the IFS parameters based on sensor data associated with the turbofan engine. If the IFS controller 302 determines at block 816 not to continue monitoring the turbofan engine, then Figure 8 The machine readable instructions 800 end.

[0128] Fig. 9 is a flow chart representing example machine readable instructions 900 that may be executed to implement Figure 3-6 The IFS controller 302 is based on Figure 3 The second turbofan engine 300 and / or the third turbofan engine 400 of FIGS. 4-5 are associated Figure 6 The sensor data 674 is used to determine Figure 6 The IFS parameter is 676. Fig. 9 The machine readable instructions 900 may be executed to implement Figure 8 Frame 802.

[0129] Fig. 9 The machine-readable instructions 900 of FIG. 1 begin at block 902, where the IFS controller 302 obtains first air pressure data from a first air pressure sensor at the outer lip of the cabin. For example, the communication interface 610 ( Figure 6 ) can obtain first air pressure data from the first pressure sensor 304 and second air pressure data from the third pressure sensor 308.

[0130] At block 904, the IFS controller 302 determines a first air pressure value at the nacelle outer lip based on the first air pressure data. For example, the IFS parameter determiner 620 ( Figure 6 ) can determine a first air pressure value at the first outer lip 208 based on the first air pressure data, and determine a second air pressure value at the second outer lip 212 based on the second air pressure data.

[0131] At block 906 , the IFS controller 302 obtains second air pressure data from a second air pressure sensor at the lip of the cabin. For example, the communication interface 610 may obtain third air pressure data from the second pressure sensor 306 and fourth air pressure data from the fourth pressure sensor 310 .

[0132] At block 908, the IFS controller 302 determines a second air pressure value at the cabin inner lip based on the second air pressure data. For example, the IFS parameter determiner 620 may determine a third air pressure value at the first inner lip 210 based on the third air pressure data, and determine a fourth air pressure value at the second inner lip 214 based on the fourth air pressure data.

[0133] At block 910, the IFS controller 302 obtains altitude data and speed data from a database. For example, the IFS parameter determiner 620 may obtain altitude data and speed data from a database stored in the database 670 ( Figure 6 ) in flight data 672( Figure 6 ) to obtain altitude and speed data.

[0134] At block 912, the IFS controller 302 determines air density based on the altitude data. For example, the IFS parameter determiner 620 may determine air density based on the altitude data.

[0135] At block 914 , the IFS controller 302 determines the Mach number based on the speed data. For example, the IFS parameter determiner 620 may determine the Mach number based on the speed data.

[0136] At block 916, the IFS controller 302 obtains acceleration data from the acceleration sensor. For example, the communication interface 610 may be coupled to Figure 3-5 One or more acceleration sensors 316 , 318 of one or more bearings 317 , 319 of a bearing section 320 of the engine 104 obtain acceleration data.

[0137] At block 918, the IFS controller 302 determines a bearing load based on the acceleration data. For example, the IFS parameter determiner 620 may determine a first load on the first bearing 317 of the engine 104, a second load on the second bearing 319, etc. based on the acceleration data. In response to determining the bearing load based on the acceleration data at block 918, control returns to Figure 8 Block 804 of the machine readable instructions 800 may be to detect the IFS based on the IFS parameter.

[0138] Fig.10 is a flow chart representing example machine readable instructions 1000 that may be executed to implement Figure 3-6 The IFS controller 302 can detect the IFS based on the IFS parameters. Fig.10 The machine readable instructions 1000 are used to implement Figure 8 Frame 804.

[0139] Fig.10 The machine readable instructions 1000 of FIG. 1004 begin at block 1002 where the IFS controller 302 determines the airflow direction based on a difference between the external cabin pressure and a pressure threshold. For example, the IFS severity level parameter determiner 630 ( Figure 6 ) may determine a first flow direction of the airflow at the first outer lip 208 based on a difference between a first pressure value from the first pressure sensor 304 and the pressure threshold. In such an example, the IFS severity level parameter determiner 630 may determine a second flow direction of the airflow at the second outer lip 212 based on a difference between a second pressure value from the third pressure sensor 308 and the pressure threshold.

[0140] At block 1004, the IFS controller 302 determines a first IFS severity level parameter based on the airflow direction and the first weighting factor. For example, the IFS severity level parameter determiner 630 may determine the first IFS severity level parameter based on the airflow direction at the first outer lip 208 and the first weighting factor 708 ( Figure 7 ) to determine a first IFS severity level parameter 702 associated with the first nacelle 134 ( Figure 7 In such an example, the IFS severity level parameter determiner 630 may determine the first IFS severity level parameter 702 associated with the second nacelle 135 based on the airflow direction at the second outer lip 212 and the first weighting factor 708 .

[0141] At block 1006, the IFS controller 302 determines a pressure difference between the external cabin pressure and the internal cabin pressure. For example, the IFS severity level parameter determiner 630 may determine a first pressure difference across the surface of the first cabin 134 based on a first difference between a first pressure value from the first pressure sensor 304 and a second pressure value from the second pressure sensor 306. In such an example, the IFS severity level parameter determiner 630 may determine a second pressure difference across the surface of the second cabin 135 based on a second difference between a third pressure value from the third pressure sensor 308 and a fourth pressure value from the fourth pressure sensor 310.

[0142] At block 1008, the IFS controller 302 determines a second IFS severity level parameter based on the pressure difference and the second weighting factor. For example, the IFS severity level parameter determiner 630 may determine the second IFS severity level parameter based on the first pressure difference across the first outer lip 208 and the first inner lip 210 and the second weighting factor 710 ( Figure 7 ) to determine a second IFS severity level parameter 704 associated with the first nacelle 134 ( Figure 7 In such an example, the IFS severity level parameter determiner 630 may determine a second IFS severity level parameter 704 associated with the second nacelle 135 based on the second pressure differential across the second outer lip 212 and the second inner lip 214 and the second weighting factor 710 .

[0143] At block 1010, the IFS controller 302 determines the engine vibration response based on the bearing load. For example, the IFS severity level parameter determiner 630 may determine the third IFS severity level parameter 706 ( Figure 7 ).

[0144] At block 1012, the IFS controller 302 determines a third IFS severity level parameter based on the engine vibration response and the third weighting factor. For example, the IFS severity level parameter determiner 630 may determine the third IFS severity level parameter based on the engine vibration response associated with the engine 104 and the third weighting factor 712 ( Figure 7 ) to determine a third IFS severity level parameter 706 associated with the engine 104.

[0145] At block 1014, the IFS controller 302 determines a probability density function based on at least the first through third severity level parameters. For example, the IFS detector 640 ( Figure 6 ) may determine a probability density function based on one or more first IFS severity level parameters 702, one or more second IFS severity level parameters 704, one or more third IFS severity level parameters, and the like.

[0146] At block 1016, the IFS controller 302 compares the probability density function with the stored probability density function. For example, the IFS detector 640 may compare the probability density function with the first probability density function 714 ( Figure 7 ), the second probability density function 716 ( Figure 7 ) and / or the third probability density function 718 ( Figure 7 ) for comparison. In such an example, the first to third probability density functions 714, 716, 718 can be stored in the database 670 ( Figure 6 )middle.

[0147] At block 1018, the IFS controller 302 detects the IFS based on the comparison. For example, the IFS detector 640 may detect and / or otherwise determine based on the comparison performed at block 1016. Figure 1-5 In response to detecting the IFS based on the comparison at block 1018, control returns to Figure 8 Block 806 of the machine readable instructions 800 is to determine whether an IFS is detected.

[0148] Fig.11 is a flowchart representing example machine readable instructions 1100 that may be executed to implement Figure 3-6 The IFS controller 302 can be configured to detect the severity of the IFS based on the IFS severity level parameter 678 ( Figure 6 ) to identify IFS control measures 682 ( Figure 6 ). You can execute Fig.11 The machine readable instructions 1100 are used to implement Figure 8 Frame 808.

[0149] Fig.11 The machine readable instructions 1100 of the embodiment of the present invention begin at block 1102, where the IFS controller 302 determines whether the IFS severity level parameter indicates that there is no IFS. For example, the IFS detector 640 ( Figure 6 ) can determine that there is no IFS at the inlet 144 based on the IFS severity level parameter 678. In other examples, the IFS detector 640 can determine that there is an IFS at the inlet 144 based on the IFS severity level parameter 678.

[0150] If the IFS controller 302 determines at block 1102 that the IFS severity level parameter indicates no IFS, then the IFS controller 302 determines at block 1104 that there are no IFS control measures to deploy. For example, the command generator 650 ( Figure 6 ) may determine not to deploy the data stored in database 670 ( Figure 6 In response to determining at block 1104 that there are no IFS controls to deploy, control returns to Figure 8 Block 810 of the machine readable instructions 800 is to determine whether an IFS control measure has been identified.

[0151] If the IFS controller 302 determines at block 1102 that the IFS severity level parameter does not indicate no IFS, control passes to block 1106 to determine whether the IFS severity level parameter indicates high IFS. For example, the IFS detector 640 may determine that there is a substantially high IFS at the inlet 144. In such an example, the IFS detector 640 may determine that the IFS severity level parameter indicates no IFS. Figure 7 The probability density function determined by the IFS severity level parameters 702, 704, 706 closely matches (e.g., within a predefined tolerance) and / or otherwise corresponds to the third probability density function 718 ( Figure 7 ).

[0152] If the IFS controller 302 determines at block 1106 that the IFS severity level parameter indicates a high IFS, then at block 1108, the IFS controller 302 controls the actuators to promote a high core airflow contribution and a low fan airflow contribution. For example, the command generator 650 may map the detection of a high IFS to a first of the IFS control measures 682 to achieve a high airflow contribution to be delivered from the first segment 406 to the third segment 410 and a low airflow contribution to be delivered from the second segment 408 to the third segment 410. In such an example, the command generator 650 may cause the actuators 402, 404 to increase the airflow from the first segment 406 and decrease the airflow from the second segment 408. In response to controlling the actuators at block 1108 to promote a high core airflow contribution and a low fan airflow contribution, control returns to Figure 8 Block 810 of the machine readable instructions 800 is to determine whether an IFS control measure has been identified.

[0153] If the IFS controller 302 determines at block 1106 that the IFS severity level parameter does not indicate a high IFS, control passes to block 1110 to determine whether the IFS severity level parameter indicates a medium IFS. For example, the IFS detector 640 may determine that a medium level, amount, etc. of IFS exists at the inlet 144. In such an example, the IFS detector 640 may determine that the IFS severity level parameter indicates a medium IFS. Figure 7 The probability density function determined by the IFS severity level parameters 702, 704, 706 closely matches (e.g., within a predefined tolerance) and / or otherwise corresponds to the second probability density function 716 ( Figure 7 ).

[0154] If the IFS controller 302 determines at box 1110 that the IFS severity level parameter indicates a medium IFS, then at box 1112, the IFS controller 302 controls the actuators to promote a medium core airflow contribution and a medium fan airflow contribution. For example, the command generator 650 may map the detection of the medium IFS to a second one of the IFS control measures 682 to implement a medium airflow contribution to be introduced from the first section 406 to the third section 410 and a medium airflow contribution to be introduced from the second section 408 to the third section 410. In such an example, the command generator 650 may cause the actuators 402, 404 to adjust the airflow from the first section 406 (e.g., reduce from a high airflow to a medium airflow, increase from a low airflow to a medium airflow, etc.) and adjust the airflow from the second section 408 (e.g., increase from a low airflow to a medium airflow, reduce from a high airflow to a medium airflow, etc.). In response to controlling the actuators at box 1112 to promote a medium core airflow contribution and a medium fan airflow contribution, control returns to Figure 8 Block 810 of the machine readable instructions 800 is to determine whether an IFS control measure has been identified.

[0155] If the IFS controller 302 determines at block 1110 that the IFS severity level parameter does not indicate medium IFS, control passes to block 1114 to determine whether the IFS severity level parameter indicates low IFS. For example, the IFS detector 640 may determine that low IFS exists at the inlet 144. In such an example, the IFS detector 640 may determine that the IFS severity level parameter indicates low IFS. Figure 7 The probability density functions determined by the IFS severity level parameters 702, 704, 706 do not closely match (e.g., within a predefined tolerance) and / or otherwise correspond to the probability density functions 714, 716, 718 ( Figure 7), or closely matches the probability density function associated with a low IFS.

[0156] If the IFS controller 302 determines at block 1114 that the IFS severity level parameter does not indicate low IFS, control returns to Figure 8 The command generator 650 controls the actuators to promote a low core airflow contribution and a high fan airflow contribution. For example, the command generator 650 may map the detection of a low IFS to a third of the IFS control measures 682 to cause a low airflow contribution to be introduced from the first segment 406 to the third segment 410 and a high airflow contribution to be introduced from the second segment 408 to the third segment 410. In such an example, the command generator 650 may cause the actuators 402, 404 to reduce the airflow from the first segment 406 and increase the airflow from the second segment 408. In response to controlling the actuators to promote a low core airflow contribution and a high fan airflow contribution at block 1116, control returns to the control unit 650. Figure 8 Block 810 of the machine readable instructions 800 is to determine whether an IFS control measure has been identified.

[0157] Fig.12 is a flowchart representing example machine readable instructions 1200 that may be executed to implement Figure 3-6 The IFS controller 302 is used to adjust the Figure 4A The third turbofan engine 400 and / or Figure 4B and / or Figure 5 The airflow contribution to the inlet of the fourth turbofan engine 430 . Fig.12 The machine readable instructions 1200 of FIG. 1200 begin at block 1202 where the IFS controller 302 determines whether an inlet flow separation (IFS) command has been obtained. For example, the communication interface 610 ( Figure 6 ) can be connected from Figure 4A The aircraft with the third turbofan engine 400 configured to operate at a predetermined speed may receive an IFS command from a pilot controlling the aircraft from a cockpit of the aircraft, etc. In such an example, the IFS command may increase the airflow contribution from the first section 406 or the second section 408 to the third section 410. In other examples, the IFS command may decrease the airflow contribution from the first section 406 or the second section 408 to the third section 410.

[0158] If the IFS controller 302 determines at block 1202 that an IFS command has not been obtained, control waits for an IFS command at block 1202. If the IFS controller 302 determines at block 1202 that an IFS command has been obtained, control passes to block 1204 to identify an IFS control measure based on the IFS command. For example, the command generator 650 ( Figure 6 ) can map commands to IFS control 682 ( Figure 6 ) to determine one or more actions to be performed.

[0159] At block 1206, the IFS controller 302 determines whether the IFS control measure includes increasing the airflow contribution behind the fan. For example, the command generator 650 may determine that the IFS control measure 682 based on the IFS command includes controlling one or more of the actuators 402, 404 to increase the airflow contribution from the second section 408 to the third section 410.

[0160] If the IFS controller 302 determines at block 1206 that the IFS control measures do not include increasing the airflow contribution behind the fan, control passes to block 1210 to determine whether the IFS control measures include decreasing the airflow contribution behind the fan. If the IFS controller 302 determines at block 1206 that the IFS control measures include increasing the airflow contribution behind the fan, then at block 1208, the IFS controller 302 controls the actuator to increase the airflow contribution from behind the fan to the inlet of the turbofan engine. For example, the command generator 650 ( Figure 6 ) may transmit a command to the first actuator 402 and / or the second actuator 404 to facilitate an increase in airflow from the second section 408 to the third section 410.

[0161] At block 1210, the IFS controller 302 determines whether the IFS control measure includes reducing the airflow contribution behind the fan. For example, the command generator 650 may determine that the IFS control measure 682 based on the IFS command includes controlling one or more of the actuators 402, 404 to reduce the airflow contribution from the second section 408 to the third section 410.

[0162] If the IFS controller 302 determines at block 1210 that the IFS control measures do not include reducing the airflow contribution behind the fan, control proceeds to block 1214 to store data associated with the action in the database. If the IFS controller 302 determines at block 1210 that the IFS control measures include reducing the airflow contribution behind the fan, then at block 1212, the IFS controller 302 controls the actuator to reduce the airflow contribution from behind the fan to the inlet of the turbofan engine. For example, the command generator 650 may transmit a command to the first actuator 402 and / or the second actuator 404 to facilitate a reduction in airflow from the second section 408 to the third section 410.

[0163] At block 1214, the IFS controller 302 stores data associated with the action in a database. For example, the alert generator 660 ( Figure 6 ) may be associated with the flight data 672 ( Figure 6 ) and / or sensor data 674 ( Figure 6 ) recorded and / or otherwise stored in database 670 ( Figure 6 In such an example, the alert generator 660 may record which of the actuators 402, 404 are called in response to the IFS command, the position of one or more of the actuators 402, 404, etc., and / or combinations thereof.

[0164] At block 1216, the IFS controller 302 determines whether to continue monitoring the turbofan engine. If at block 1216 the IFS controller 302 determines to continue monitoring the turbofan engine, control returns to block 1202 to determine whether another IFS command has been obtained. If at block 1216 the IFS controller 302 determines not to continue monitoring the turbofan engine, then Fig.12 The machine readable instructions 1200 end.

[0165] Fig.13 is a block diagram of an example processor platform 1300 configured to perform Figure 8-12 Instructions to implement Figure 3-6 The IFS controller 302. The processor platform 1300 may be, for example, an electronic control unit (ECU), an electronic engine control (EEC) unit, a full authority digital engine control (FADEC) unit, a self-learning machine (e.g., a neural network), or any other type of computing device.

[0166] The processor platform 1300 of the illustrated example includes a processor 1312. The processor 1312 of the illustrated example is hardware. For example, the processor 1312 may be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor-based (e.g., silicon-based) device. In this example, the processor 1312 implements Figure 6 The IFS parameter determiner 620, the IFS severity level parameter determiner 630, the IFS detector 640, the command generator 650 and the alarm generator 660. Fig.13 , the IFS parameter determiner 620 is depicted as “IFSPARAM DETER”, the IFS severity level parameter determiner 630 is depicted as “IFS SL PARAM DETER”, and the command generator 650 is depicted as “CMD GENERATOR” 650 .

[0167] The processor 1312 of the illustrated example includes a local memory 1313 (e.g., a cache). The processor 1312 of the illustrated example communicates with a main memory including a volatile memory 1314 and a non-volatile memory 1316 via a bus 1318. The volatile memory 1314 may be comprised of synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), Dynamic Random Access Memory The non-volatile memory 1316 may be implemented by flash memory and / or any other desired type of memory device. Access to the main memory 1314, 1316 is controlled by a memory controller.

[0168] The processor platform 1300 of the illustrated example also includes an interface circuit 1320. The interface circuit 1320 may be implemented by any type of interface standard (e.g., Ethernet interface, Universal Serial Bus (USB), interface, near field communication (NFC) interface and / or PCI express interface). In this example, the interface circuit 1320 implements Figure 6 The communication interface 610 is provided.

[0169] In the example shown, one or more input devices 1322 are connected to the interface circuit 1320. The input devices 1322 allow a user to enter data and / or commands into the processor 1312. The input devices 1322 may be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, buttons, a mouse, a touch screen, a trackpad, a trackball, an isopoint device, and / or a speech recognition system.

[0170] One or more output devices 1324 are also connected to the interface circuit 1320 of the illustrated example. The output device 1324 may be implemented, for example, by a display device (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube (CRT) display, an in-place switching (IPS) display, a touch screen, etc.), a tactile output device, a printer, and / or a speaker. Therefore, the interface circuit 1320 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0171] The interface circuitry 1320 of the illustrated example also includes a communication device (e.g., a transmitter, a receiver, a transceiver, a modem, a residential gateway, a wireless access point, and / or a network interface) to facilitate the exchange of data with an external machine (e.g., any kind of computing device) via a network 1326. Communications may be via, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a field line wireless system, a cellular telephone system, etc.

[0172] The processor platform 1300 of the illustrated example also includes one or more mass storage devices 1328 for storing software and / or data. Examples of such mass storage devices 1328 include floppy disk drives, hard disk drives, optical disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives. In this example, the one or more mass storage devices 1328 implement Figure 6 database 670, flight data 672, sensor data 674, IFS parameters 676, IFS severity level parameters 678, IFS detection model 680, and IFS control measures 682. Fig.13 , the IFS severity level parameter 678 is depicted as "IFS SL PARAM", the IFS detection model 680 is depicted as "DETECT MODEL", and the IFS control measures 682 are depicted as "CNTL measures".

[0173] Figure 8-12 The machine executable instructions 1332 may be stored in the mass storage device 1328, in the volatile memory 1314, in the non-volatile memory 1316, and / or on a removable non-transitory computer readable storage medium (eg, a CD or DVD).

[0174] From the foregoing, it will be appreciated that example methods, apparatus, and articles of manufacture have been disclosed for detecting and / or controlling airflow separation of an engine. The example methods, apparatus, and articles of manufacture determine IFS parameters based on flight data, sensor data, and the like, and may determine an IFS severity level parameter based on the IFS parameters. The example methods, apparatus, and articles of manufacture may detect IFS and / or quantification and / or severity of IFS based on IFS parameters, IFS severity level parameters, and the like. The example methods, apparatus, and articles of manufacture may control one or more actuators to adjust airflow discharge to an inlet section of an engine based on IFS detection. Advantageously, the example methods, apparatus, and articles of manufacture may improve the reliability and / or operating life of engine components and / or, more generally, an engine by detecting IFS and reducing and / or otherwise eliminating IFS in response to detection.

[0175] The disclosed methods, apparatus, and articles of manufacture improve the efficiency of using a computing device (such as an ECU, FADEC, etc.) by preprocessing data (such as IFS parameters, IFS severity level parameters, etc.) before detecting IFS. Advantageously, by preprocessing the data, the disclosed methods, apparatus, and articles of manufacture can detect IFS using reduced computing resources compared to detecting IFS using unprocessed data. Thus, the disclosed methods, apparatus, and articles of manufacture are directed to one or more improvements in computer functionality.

[0176] Further aspects of the invention are provided by the subject matter of the following clauses:

[0177] 1. An apparatus comprising hardware and a memory, the memory comprising instructions that, when executed, cause the hardware to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjust a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0178] 2. An apparatus according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the severity level parameter is a first severity level parameter, and the hardware: determines an airflow direction at the outer lip based on a difference between the first pressure value and a threshold value; determines a second severity level parameter based on the difference and a weight value; and detects inlet flow separation at an inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0179] 3. An apparatus according to any of the preceding clauses, wherein the hardware: determines a first probability density function based on a first severity level parameter and a second severity level parameter; compares the first probability density function with a second probability density function stored in a database; and detects inlet flow separation at an inlet of a turbofan engine based on the comparison.

[0180] 4. The apparatus of any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, the severity level parameter corresponds to a cabin inlet pressure differential, and the hardware: determines the cabin inlet pressure differential based on a difference between the first pressure value and the second pressure value; determines the severity level parameter based on the cabin inlet pressure differential and a weight value; and detects an inlet flow separation at an inlet of the turbofan engine based on the severity level parameter.

[0181] 5. An apparatus as described in any preceding clause, wherein the severity level parameter is a first severity level parameter, and the hardware: obtains acceleration data from an accelerometer coupled to a bearing of a turbofan engine; determines a vibration response of the turbofan engine based on the acceleration data; determines a second severity level parameter based on the vibration response and a weight value; and detects inlet flow separation at an inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0182] 6. An apparatus as described in any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, and the hardware: obtains altitude data and speed data from an aircraft coupled to a turbofan engine; determines air density based on the altitude data; determines Mach number based on the speed data; and determines an inlet flow separation parameter based on at least one of the first pressure value, the second pressure value, the air density, or the Mach number.

[0183] 7. An apparatus as described in any preceding clause, wherein the hardware adjusts the contribution of airflow from behind the fan by controlling an actuator included in the nacelle based on a severity level parameter, the actuator moving from a first position to a second position to adjust the contribution of airflow from behind the fan to in front of the fan.

[0184] 8. An apparatus comprising: an inlet flow separation parameter determiner, the inlet flow separation parameter determiner determining an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; an inlet flow separation severity level parameter determiner, the inlet flow separation severity level parameter determiner determining a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and a command generator, the command generator adjusting a contribution of an airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0185] 9. An apparatus according to any preceding clause, wherein the first pressure sensor is connected to the outer lip of the nacelle, the severity level parameter is a first severity level parameter, an inlet flow separation severity level parameter determiner: determines the airflow direction at the outer lip based on the difference between the first pressure value and a threshold value; and determines a second severity level parameter based on the difference and a weight value; and further includes an inlet flow separation detector, which detects inlet flow separation at the inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0186] 10. An apparatus according to any preceding clause, wherein the inlet flow separation detector: determines a first probability density function based on a first severity level parameter and a second severity level parameter; compares the first probability density function with a second probability density function stored in a database; and detects inlet flow separation at the inlet of the turbofan engine based on the comparison.

[0187] 11. An apparatus according to any preceding clause, wherein a first pressure sensor is coupled to an outer lip of the cabin, a second pressure sensor is coupled to an inner lip of the cabin, a severity level parameter corresponds to a cabin inlet pressure difference, an inlet flow separation severity level parameter determiner: determines the cabin inlet pressure difference based on a difference between a first pressure value and a second pressure value; determines the severity level parameter based on the cabin inlet pressure difference and a weight value; and further comprises an inlet flow separation detector, which detects inlet flow separation at the inlet of the turbofan engine based on the severity level parameter.

[0188] 12. An apparatus according to any preceding clause, wherein the severity level parameter is a first severity level parameter, further comprising a collecting engine, the collecting engine obtaining acceleration data from an accelerometer connected to a bearing of a turbofan engine, an inlet flow separation severity level parameter determiner: determining a vibration response of the turbofan engine based on the acceleration data; determining a second severity level parameter based on the vibration response and a weight value; and further comprising an inlet flow separation detector, the inlet flow separation detector detecting inlet flow separation at the inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0189] 13. An apparatus according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, and further comprising a collection engine that obtains altitude data and speed data from an aircraft coupled to a turbofan engine, and an inlet flow separation parameter determiner: determines air density based on the altitude data; determines Mach number based on the speed data; and determines the inlet flow separation parameter based on at least one of the first pressure value, the second pressure value, air density, or the Mach number.

[0190] 14. An apparatus according to any preceding clause, wherein the command generator adjusts the contribution of the airflow from behind the fan by controlling an actuator included in the nacelle based on a severity level parameter, the command generator calling the actuator to move from a first position to a second position to adjust the contribution of the airflow from behind the fan to in front of the fan.

[0191] 15. A non-transitory computer-readable storage medium comprising instructions that, when executed, cause at least one processor to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjust a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0192] 16. A non-transitory computer-readable storage medium according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the severity level parameter is a first severity level parameter, and the instructions, when executed, cause at least one processor to: determine an airflow direction at the outer lip based on a difference between the first pressure value and a threshold value; determine a second severity level parameter based on the difference and a weight value; and detect an inlet flow separation at an inlet of a turbofan engine based on the first severity level parameter and the second severity level parameter.

[0193] 17. A non-transitory computer-readable storage medium according to any of the preceding clauses, wherein the instructions, when executed, cause at least one processor to: determine a first probability density function based on a first severity level parameter and a second severity level parameter; compare the first probability density function with a second probability density function stored in a database; and detect inlet flow separation at an inlet of a turbofan engine based on the comparison.

[0194] 18. The non-transitory computer-readable storage medium of any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, the severity level parameter corresponds to a cabin inlet pressure differential, and the instructions, when executed, cause at least one processor to: determine the cabin inlet pressure differential based on a difference between the first pressure value and the second pressure value; determine the severity level parameter based on the cabin inlet pressure differential and a weight value; and detect an inlet flow separation at an inlet of the turbofan engine based on the severity level parameter.

[0195] 19. A non-transitory computer-readable storage medium according to any preceding clause, wherein the severity level parameter is a first severity level parameter, and the instructions, when executed, cause at least one processor to: obtain acceleration data from an accelerometer coupled to a bearing of a turbofan engine; determine a vibration response of the turbofan engine based on the acceleration data; determine a second severity level parameter based on the vibration response and a weight value; and detect inlet flow separation at an inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0196] 20. A non-transitory computer-readable storage medium according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, and the instructions, when executed, cause at least one processor to: obtain altitude data and speed data from an aircraft coupled to a turbofan engine; determine air density based on the altitude data; determine Mach number based on the speed data; and determine an inlet flow separation parameter based on at least one of the first pressure value, the second pressure value, the air density, or the Mach number.

[0197] 21. A non-transitory computer-readable storage medium according to any preceding clause, wherein the instructions, when executed, cause at least one processor to adjust the contribution of airflow from behind the fan by controlling an actuator included in the nacelle based on a severity level parameter, the actuator moving from a first position to a second position to adjust the contribution of airflow from behind the fan to in front of the fan.

[0198] 22. A method comprising: determining an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; determining a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value; and adjusting a contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0199] 23. A method according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the severity level parameter is a first severity level parameter, and further comprising: determining an airflow direction at the outer lip based on a difference between the first pressure value and a threshold value; determining a second severity level parameter based on the difference and a weight value; and detecting an inlet flow separation at an inlet of a turbofan engine based on the first severity level parameter and the second severity level parameter.

[0200] 24. The method according to any of the preceding clauses further comprises: determining a first probability density function based on a first severity level parameter and a second severity level parameter; comparing the first probability density function with a second probability density function stored in a database; and detecting inlet flow separation at an inlet of a turbofan engine based on the comparison.

[0201] 25. A method according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, the severity level parameter corresponds to a cabin inlet pressure differential, and further comprising: determining the cabin inlet pressure differential based on a difference between the first pressure value and the second pressure value; determining the severity level parameter based on the cabin inlet pressure differential and a weight value; and determining an inlet flow separation at an inlet of the turbofan engine based on the severity level parameter.

[0202] 26. A method according to any preceding clause, wherein the severity level parameter is a first severity level parameter, and further comprising: obtaining acceleration data from an accelerometer coupled to a bearing of a turbofan engine; determining a vibration response of the turbofan engine based on the acceleration data; determining a second severity level parameter based on the vibration response and a weight value; and detecting inlet flow separation at an inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0203] 27. A method according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle and the second pressure sensor is coupled to an inner lip of the nacelle, and further comprising: obtaining altitude data and speed data from an aircraft coupled to a turbofan engine; determining air density based on the altitude data; determining Mach number based on the speed data; and determining an inlet flow separation parameter based on at least one of the first pressure value, the second pressure value, the air density, or the Mach number.

[0204] 28. A method according to any preceding clause, wherein adjusting the contribution of the airflow from behind the fan comprises controlling an actuator included in the nacelle based on a severity level parameter, the actuator moving from a first position to a second position to adjust the contribution of the airflow from behind the fan to in front of the fan.

[0205] 29. An apparatus comprising hardware and a memory, the memory comprising instructions that, when executed, cause the hardware to at least: determine an inlet flow separation parameter based on a first pressure value from a first pressure sensor included in a nacelle of a turbofan engine and a second pressure value from a second pressure sensor included in the nacelle; and determine a severity level parameter based on the inlet flow separation parameter, the severity level parameter being based on a difference between the first pressure value and the second pressure value.

[0206] 30. The apparatus of any preceding clause, wherein the hardware adjusts the contribution of airflow from behind a fan of the turbofan engine based on the severity level parameter.

[0207] 31. An apparatus as described in any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the severity level parameter is a first severity level parameter, and the hardware: determines an airflow direction at the outer lip based on a difference between the first pressure value and a threshold value; determines a second severity level parameter based on the difference and a weight value; and detects inlet flow separation at an inlet of a turbofan engine based on the first severity level parameter and the second severity level parameter.

[0208] 32. An apparatus according to any preceding clause, wherein the hardware: determines a first probability density function based on a first severity level parameter and a second severity level parameter; compares the first probability density function with a second probability density function stored in a database; and detects inlet flow separation at an inlet of a turbofan engine based on the comparison.

[0209] 33. An apparatus according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, the severity level parameter corresponds to a cabin inlet pressure differential, and the hardware: determines the cabin inlet pressure differential based on a difference between the first pressure value and the second pressure value; determines the severity level parameter based on the cabin inlet pressure differential and a weight value; and detects inlet flow separation at an inlet of the turbofan engine based on the severity level parameter.

[0210] 34. An apparatus as described in any preceding clause, wherein the severity level parameter is a first severity level parameter, and the hardware: obtains acceleration data from an accelerometer coupled to a bearing of a turbofan engine; determines a vibration response of the turbofan engine based on the acceleration data; determines a second severity level parameter based on the vibration response and a weight value; and detects inlet flow separation at an inlet of the turbofan engine based on the first severity level parameter and the second severity level parameter.

[0211] 35. An apparatus according to any preceding clause, wherein the first pressure sensor is coupled to an outer lip of the nacelle, the second pressure sensor is coupled to an inner lip of the nacelle, and the hardware: obtains altitude data and speed data from an aircraft coupled to a turbofan engine; determines air density based on the altitude data; determines Mach number based on the speed data; and determines an inlet flow separation parameter based on at least one of the first pressure value, the second pressure value, the air density, or the Mach number.

[0212] 36. An apparatus as described in any preceding clause, wherein the hardware adjusts the contribution of airflow from behind the fan by controlling an actuator included in the nacelle based on a severity level parameter, the actuator moving from a first position to a second position to adjust the contribution of airflow from behind the fan to in front of the fan.

[0213] Although certain example methods, apparatus, and articles of manufacture have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus, and articles of manufacture that fully fall within the scope of the claims of this patent.

[0214] The following claims are hereby incorporated into the Detailed Description by this reference, with each claim standing on its own as a separate embodiment of the disclosure.

Claims

1. A turbine engine, characterized in that: include: fan; a nacelle, the nacelle surrounding at least the fan; a compressor section located downstream of the fan; a duct at least partially defined by the nacelle, wherein the duct comprises: a first opening located in the compressor section; a second opening located downstream of the fan and upstream of the compressor section; and a third opening, the third opening being located upstream of the fan; a first pressure sensor located at an outer lip of the nacelle; a second pressure sensor coupled to the nacelle and spaced apart from the first pressure sensor; and and at least one actuator communicatively coupled to the first pressure sensor and the second pressure sensor, the at least one actuator being located in the conduit and configured to regulate airflow between the first opening and the third opening and between the second opening and the third opening, wherein the first pressure sensor and the second pressure sensor provide outputs to generate commands to control the at least one actuator.

2. The turbine engine according to claim 1, characterized in that Further included is a controller for generating the command, the controller being in communication with the first pressure sensor, the second pressure sensor, and the at least one actuator.

3. The turbine engine according to claim 2, characterized in that: Further comprising at least one antenna, wherein communication between the controller, the first pressure sensor, the second pressure sensor, and the at least one actuator is performed via the at least one antenna.

4. The turbine engine according to claim 1, characterized in that: Wherein the first opening in the nacelle is located between a low-pressure compressor and a high-pressure compressor of the compressor section.

5. The turbine engine according to claim 1, characterized in that The second pressure sensor is located at the inner lip of the nacelle.

6. The turbine engine according to claim 5, characterized in that Wherein the third opening in the nacelle is located downstream of the second pressure sensor.

7. The turbine engine according to claim 6, characterized in that Further included is a third pressure sensor coupled to the outer lip and circumferentially spaced apart from the first pressure sensor.

8. A turbine engine, characterized in that: include: fan; a nacelle, the nacelle surrounding at least the fan; a compressor section located downstream of the fan; at least two ducts, the at least two ducts being at least partially defined by at least two portions of the nacelle, wherein each of the at least two ducts comprises: a first opening located in the compressor section; a second opening located downstream of the fan and upstream of the compressor section; and a third opening, the third opening being located upstream of the fan; a first pressure sensor coupled to the nacelle; a second pressure sensor coupled to the nacelle and spaced apart from the first pressure sensor; and At least two actuators are communicatively coupled to the first pressure sensor and the second pressure sensor, wherein each of the at least two actuators is located in each of the at least two conduits and is configured to regulate airflow between the first opening and the third opening, and to regulate airflow between the second opening and the third opening, wherein the first pressure sensor and the second pressure sensor provide outputs to generate commands to control the at least two actuators.

9. A turbine engine, characterized in that: include: fan; a nacelle, the nacelle surrounding at least the fan; an accelerometer coupled to a bearing of the turbine engine; a first pressure sensor and a second pressure sensor, the first pressure sensor and the second pressure sensor being included in the nacelle; as well as a controller in communication with the first pressure sensor and the second pressure sensor, wherein the controller is configured to: determining a first pressure value from the first pressure sensor and a second pressure value from the second pressure sensor; determining a first severity level parameter based on a difference between the first pressure value and the second pressure value; determining a vibration response based on acceleration data from the accelerometer; determining a second severity level parameter based on the vibration response obtained from the acceleration data; detecting an inlet flow separation at an inlet of the turbine engine based on the first severity level parameter and the second severity level parameter; as well as Airflow behind the fan is adjusted based on the first severity level parameter and the second severity level parameter.

10. A device for detecting and controlling engine airflow separation, characterized in that: include: Hardware; and A memory comprising instructions that, when executed, cause the hardware to at least perform the following operations: determining a first pressure value from the first pressure sensor and a second pressure value from the second pressure sensor; determining a first severity level parameter based on a difference between the first pressure value and the second pressure value; determining a vibration response based on acceleration data from the accelerometer; determining a second severity level parameter based on the vibration response obtained from the acceleration data; detecting an inlet flow separation at an inlet of the turbine engine based on the first severity level parameter and the second severity level parameter; as well as Airflow behind the fan is adjusted based on the first severity level parameter and the second severity level parameter.

Images