This application claims priority to and the benefit of U.S. Provisional patent application Ser. No. 14/995,781, filed 14 Jan. 2016, the disclosure of which is now expressly incorporated herein by reference.
The present disclosure relates generally to the use of optical scanning in the prediction of effective flow areas. Additionally, the present disclosure relates to the use of optical scanning of vanes to determine effective flow areas for turbine engines.
Gas turbine engines are used to power aircraft, watercraft, power generators, and the like. Gas turbine engines typically include a compressor, a combustor, and a turbine. The compressor compresses air drawn into the engine and delivers high pressure air to the combustor. In the combustor, fuel is mixed with the high pressure air and is ignited. Products of the combustion reaction in the combustor are directed into the turbine where work is extracted to drive the compressor and, sometimes, an output shaft. Left-over products of the combustion are exhausted out of the turbine and may provide thrust in some applications.
Compressors and turbines typically include alternating stages of static vane assemblies and rotating wheel assemblies. The rotating wheel assemblies include disks carrying blades around their outer edges. When the rotating wheel assemblies turn, tips of the blades move along blade tracks included in static shrouds that are arranged around the rotating wheel assemblies. Such static shrouds may be coupled to an engine case that surrounds the compressor, the combustor, and the turbine.
The vane assemblies may have a total effective flow area that can be determined by adding individual effective flow areas from individual vane segments. The individual vane segments may each have different effective flow areas based on, for example, different manufacturing tolerances or exposure to stress or temperature during operation. For example, a vane's effective flow area may be lessened due to its exposure to the temperature and products of the combustion reaction in the combustor.
The present disclosure may comprise one or more of the following features and combinations thereof.
A computing device for determining an effective flow area of a first vane for a turbine or a turbine engine may include at least one computing device and instructions embodied in one or more non-transitory machine accessible storage media, the instructions executable by the at least one computing device to cause the computing device to determine an effective flow area of the first vane for the turbine by optically scanning the first vane, creating a virtual vane based on the scan, determining at least one chokepoint of the virtual vane, and calculating a virtual vane effective flow area based at least in part on the at least one chokepoint.
In some embodiments, a computing device for determining an effective flow area of a vane ring for a turbine engine may include at least one computing device and instructions embodied in one or more non-transitory machine accessible storage media, the instructions executable by the at least one computing device to cause the computing device to determine an effective flow area of a vane ring for a turbine engine by: scanning a vane ring that includes a plurality of vanes; based on the scan, creating a virtual vane ring comprising a plurality of virtual vanes corresponding to each of the plurality of vanes; determining at least one chokepoint for each of the plurality of virtual vanes; calculating an individual effective flow area of each of the plurality of virtual vanes based at least in part on the at least one chokepoint; and calculating a vane ring effective flow area by calculating a sum of the individual effective flow areas.
These and other features of the present disclosure will become more apparent from the following description of the illustrative embodiments.
This disclosure is illustrated by way of example and not by way of limitation in the accompanying figures. The figures may, alone or in combination, illustrate one or more embodiments of the disclosure. Elements illustrated in the figures are not necessarily drawn to scale. Reference labels may be repeated among the figures to indicate corresponding or analogous elements.
For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to a number of illustrative embodiments illustrated in the drawings and specific language will be used to describe the same.
Referring now to
The computing device 100 may include hardware, firmware, and/or software components that are configured to perform the functions disclosed herein, including the functions of the scanning and modeling subsystem 132 and the effective flow area determination system 136. While not specifically shown, the computing device 100 may include other computing devices (e.g., servers, mobile computing devices, etc.) which may be in communication with each other and/or the computing device 100 via one or more communication networks to perform one or more of the disclosed functions.
The illustrative computing device 100 may include at least one processer 112 (e.g., a controller, microprocessor, microcontroller, digital signal processor, etc.), memory 114, and an input/output (I/O) subsystem 116. The computing device 100 may be embodied as any type of computing device (e.g., a tablet computer, smart phone, body-mounted device or wearable device, etc.), a server, an enterprise computer system, a network of computers, a combination of computers and other electronic devices, or other electronic devices.
Although not specifically shown, it should be understood that the I/O subsystem 116 typically includes, among other things, an I/O controller, a memory controller, and one or more I/O ports. The processor 112 and the I/O subsystem 116 are communicatively coupled to the memory 114. The memory 114 may be embodied as any type of suitable computer memory device (e.g., volatile memory such as various forms of random access memory.
The I/O subsystem 116 is communicatively coupled to a number of hardware, firmware, and/or software components, including a data storage device 118, a display 126, a communication subsystem 128, a user interface (UI) subsystem 130, the scanning and modeling subsystem 132, and the effective flow area determination system 136. The data storage device 118 may include one or more hard drives or other suitable persistent storage devices (e.g., flash memory, memory cards, memory sticks, and/or others). The virtual vane(s) 120, chokepoint(s) 122, and library 124 reside at least temporarily in the data storage device 118 and/or other data storage devices of the computing device 100 (e.g., data storage devices that are “in the cloud” or otherwise connected to the computing device 100 by a network). Portions of the scanning and modeling subsystem 132 and the effective flow area determination system 136 may be copied to the memory 114 during operation of the computing device 100, for faster processing or for other reasons. The display 126 may be embodied as any type of digital display device, such as a liquid crystal display (LCD), and may include a touchscreen. The illustrative display 126 is configured or selected to be capable of displaying two- and/or three-dimensional graphics.
The communication subsystem 128 may communicatively couple the computing device 100 to other computing devices and/or systems by, for example, one or more network(s) 150. The network(s) 150 may be embodied as, for example, a cellular network, a local area network, a wide area network (e.g., Wi-Fi), a personal cloud, a virtual personal network (e.g., VPN), an enterprise could, a public could, an Ethernet network, and/or a public network such as the Internet. The communication subsystem 128 may, alternatively or additionally, enable shorter-range wireless communications between the computing device 100 and other computing devices, using, for example, BLUETOOTH and/or Near Field Communication (NFC) technology. Accordingly, the communication subsystem 128 may include one or more optical, wired, and/or wireless network interface subsystems, cards, adapters, or other devices, as may be needed pursuant to the specifications and/or design of the particular computing device 100. The user interface subsystem 130 may include one or more user input devices (e.g., the display 126, a microphone, a touchscreen, keyboard, virtual keypad, etc.) and one or more output devices (e.g., audio speakers, LEDs, additional displays, etc.).
The communication subsystem 128 may communicate output of one or more of the scanning and modeling subsystem 132 and the effective flow area determination system 136. For example, portions of virtual vanes 120, chokepoint(s), 122, or libraries 124 may be supplied to other computing devices via network(s) 150.
The scanning and modeling subsystem 132 may be embodied as one or more computer-executable components and data structures for performing optical scanning and finite element modeling of a manufactured component, such as vanes of a turbine or turbine engine. The illustrative scanning and modeling subsystem 132 may create a virtual and mathematical model of structural characteristics of the component. For example, the scanning and modeling subsystem 132 may receive an optical scan of a vane component. The optical scan may be performed using various methods, such as laser scanning and/or precision structure light scanning with blue and/or white lights. By using a high resolution optical scanning process, the scanning and modeling subsystem 132 can produce a more precise virtual model of the component with better definition of subtle edge features. This is beneficial because the vanes may be deformed or disfigured during manufacturing, during transit, or during operation such that the effective flow area of individual vanes, a vane segment, or a vane ring is negatively impacted. Once a component is identified as having a negatively impacted effective flow area, that component can be monitored, repaired, or replaced to mitigate turbine issues during operation (e.g., vibration) or to improve turbine characteristics (e.g., fuel efficiency).
In some embodiments, the scanning and modeling subsystem 132 may scan the individual vanes of the turbine or turbine engine using a structured blue light scan. In some embodiments, the scan may include a scan of substantially the entire flow area surface of the vanes; for example, by performing both a full part scan of the vane. The full part scan may include performing both a front scan of the vane and a back scan of the vane. The full part scan of the vane ensures the scan captures a better definition of the subtle edge features of the vanes, as well as any datum surfaces that may be used to fit the scanned vanes into a simulated or virtual ring.
In some embodiments, the scanning and modeling subsystem 132 may identify chokepoint(s) 122 of the vane. Chokepoint(s) 122 may be areas or points of a vane that may restrict the effective flow area between vanes. The chokepoint(s) 122 may be stored as part of the virtual vane(s) 120 in library 124 of data storage 118 of the computing device 100. In some embodiments, identification of chokepoint(s) 122 may be performed via other parts of the computing device 100, such as the effective flow area determination system 136.
The effective flow area determination system 136 may be embodied as one or more computer-executable components and data structures for determining effective flow areas between one or more components, including a vane effective flow area generator 138, a virtual vane ring generator 140, and a vane ring effective flow area generator 142. The illustrative effective flow area determination system 136 may use the virtual and mathematical model of structural characteristics of the components from the scanning and modeling subsystem 132 to determine one or more effective flow areas between those components.
In some embodiments, a vane effective flow area generator 138 may generate a vane segment, based on two virtual vanes 120 scanned and modeled by the computing device 100. The vane segment may include chokepoint(s) 122. Based at least in part on the chokepoint(s) 122, the vane effective flow area generator 138 may calculate a vane effective flow area. In some embodiments, the vane effective flow area of the vane segment may be calculated mathematically by determining the area between two virtual vanes 120. This calculation may take into account the chokepoint(s) 122 in determining the vane effective flow area. The vane effective flow area generator 138 may determine the effective flow area for each area in between the virtual vane(s) 120.
In some embodiments, a virtual vane ring generator 140 may generate a virtual vane ring that includes each of the virtual vanes 120. The illustrative virtual vane ring generator 140 may use the virtual and mathematical model of structural characteristics of the vane components from the scanning and modeling subsystem 132 to assemble the virtual vane ring. Once the virtual vane ring is assembled, the vane ring effective flow area generator 142 may calculate a vane ring effective flow area for the entire turbine or turbine engine. In some embodiments, the vane ring effective flow area generator 142 may calculate the vane ring effective flow area by adding the determined vane effective flow areas.
The computing device 100 and instructions embodied thereon for determining effective flow areas of components of a turbine and/or of the entire vane ring assembly of a turbine or turbine engine may be used both in initial manufacturing and repair and reassembly. In some embodiments, the systems and methods described herein may be used during initial production to verify effective flow areas of a turbine or turbine engine. In other embodiments, the systems and methods described herein may be used during repair or reassembly to verify, modify, or repair components of a turbine or turbine engine based on one or more of the determined effective flow areas.
Particular aspects of the systems, devices, methods, and analyses that may be performed by the various modules of the computing device 100 may vary depending on one or more of the characteristics of the component being analyzed or its prescribed mission criteria. Accordingly, the examples described herein are illustrative and intended to be non-limiting. Further, the computing device 100 may include other components, sub-components, and devices not illustrated in
Referring now to
For ease of illustration and clarity, three sections were used to create the chokepoint 322 to determine the effective flow area 339 in
In some embodiments, a turbine or turbine engine may have reference specifications that indicate acceptable ranges for various components or characteristics. For example, a reference turbine or turbine engine may have an acceptable range for the total effective flow area and/or individual effective flow areas for that particular turbine or turbine engine make or model.
Referring back to
In some embodiments, if the computing device 100 detects a component or aspect of the turbine or turbine that is out of specification, it may take one or more actions. For example, the computing device 100 may use one or more of its I/O subsystem 116, display 126, communication subsystem 128, UI subsystem 130, or other components or processes to alert a user that the computing device 100 has detected a component or aspect that is out of specification. In some embodiments, the alert may be a visual alert on the display 126 or the I/O subsystem 116 (e.g., blinking LED lights), an audio alert from a speaker that is part of the I/O subsystem 116, and/or the alert may be an email, text message, or other communication sent via the communication system 128 or network(s) 150.
Referring now to
At 520, and as previously described herein, the computing device may determine effective flow areas between individual virtual vanes and may determine the total effective flow area of the entire vane ring assembly. At 522, the computing device may determine individual effective flow areas between each of the vanes. At 524, the computing device may generate a virtual vane ring assembly by piecing together each of the virtual vanes into a comprehensive ring assembly. At 526, the computing device may determine a vane ring effective flow area, for example, by adding up the individual vane effective flow areas. At 528, the computing device may compare components or aspects of the virtual turbine to a reference turbine.
In the foregoing description, numerous specific details, examples, and scenarios are set forth in order to provide a more thorough understanding of the present disclosure. It will be appreciated, however, that embodiments of the disclosure may be practiced without such specific details. Further, such examples and scenarios are provided for illustration only, and are not intended to limit the disclosure in any way. Those of ordinary skill in the art, with the included descriptions, should be able to implement appropriate functionality without undue experimentation.
References in the specification to “an embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic. Such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly indicated.
Embodiments in accordance with the disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored using one or more machine-readable media which may be read and executed by one or more processors. A machine-readable medium may include any suitable form of volatile or non-volatile memory.
Modules, data structures, and the like defined herein are defined as such for ease of discussion, and are not intended to imply that any specific implementation details are required. For example, any of the described modules and/or data structures may be combined or divided in sub-modules, sub-processes or other units of computer code or data as may be required by a particular design or implementation of the computing device.
In the drawings, specific arrangements or orderings of elements may be shown for ease of description. However, the specific ordering or arrangement of such elements is not meant to imply that a particular order or sequence of processing, or separation of processes, is required in all embodiments. In general, schematic elements used to represent instruction blocks or modules may be implemented using any suitable form of machine-readable instruction, and each such instruction may be implemented using any suitable programming language, library, application programming interface (API), and/or other software development tools or frameworks. Similarly, schematic elements used to represent data or information may be implemented using any suitable electronic arrangement or data structure. Further, some connections, relationships, or associations between elements may be simplified or not shown in the drawings so as not to obscure the disclosure.
This disclosure is considered to be exemplary and not restrictive. In character, and all changes and modifications that come within the spirit of the disclosure are desired to be protected.
Number | Name | Date | Kind |
---|---|---|---|
3732031 | Bowling et al. | May 1973 | A |
3957104 | Terpay | May 1976 | A |
4222172 | Mason | Sep 1980 | A |
4374459 | Burton | Feb 1983 | A |
4555798 | Bradbent, Jr. et al. | Nov 1985 | A |
4896430 | Burton | Jan 1990 | A |
4908782 | Pekarek et al. | Mar 1990 | A |
5291654 | Judd et al. | Mar 1994 | A |
5545003 | O'Connor et al. | Aug 1996 | A |
6148677 | Evangelista | Nov 2000 | A |
6582194 | Birkner et al. | Jun 2003 | B1 |
6654710 | Keller | Nov 2003 | B1 |
6923051 | Fleming | Aug 2005 | B2 |
6945124 | Leboeuf et al. | Sep 2005 | B1 |
6992315 | Twerdochlib | Jan 2006 | B2 |
7116839 | Leboeuf et al. | Oct 2006 | B2 |
7305118 | Leboeuf et al. | Dec 2007 | B2 |
7441331 | Hudson et al. | Oct 2008 | B2 |
7640793 | McCall et al. | Jan 2010 | B2 |
7656445 | Heyworth | Feb 2010 | B2 |
7668704 | Perchanok et al. | Feb 2010 | B2 |
7774171 | Chou et al. | Aug 2010 | B2 |
7784183 | Rockstroh et al. | Aug 2010 | B2 |
7791025 | Key | Sep 2010 | B2 |
8602722 | George et al. | Dec 2013 | B2 |
8937628 | Hatcher et al. | Jan 2015 | B2 |
9030667 | Tanriverdi | May 2015 | B2 |
9116071 | Hatcher et al. | Aug 2015 | B2 |
20030216856 | Jacobson | Nov 2003 | A1 |
20030228069 | Leboeuf | Dec 2003 | A1 |
20060087662 | Lefoeuf et al. | Apr 2006 | A1 |
20070050156 | Vaidyanathan | Mar 2007 | A1 |
20090164185 | Menuey | Jun 2009 | A1 |
20100300642 | Didion | Dec 2010 | A1 |
20110052370 | Karpman | Mar 2011 | A1 |
20110139915 | Didion | Jun 2011 | A1 |
20110229307 | Lemieux et al. | Sep 2011 | A1 |
20120087803 | Bulter et al. | Apr 2012 | A1 |
20140142889 | Chuong | May 2014 | A1 |
20140376589 | Karp et al. | Dec 2014 | A1 |
20150308337 | Marasco et al. | Oct 2015 | A1 |
Number | Date | Country |
---|---|---|
2002221006 | Aug 2002 | JP |
2003097217 | Apr 2003 | JP |
2005534002 | Nov 2005 | JP |
2007024597 | Feb 2007 | JP |
2007064218 | Mar 2007 | JP |
2008517282 | May 2008 | JP |
2011179493 | Sep 2011 | JP |
2015007425 | Jan 2015 | JP |
2006042397 | Apr 2006 | WO |
Entry |
---|
Extended European Search Report, European Application No. 17151332.8, dated Jul. 12, 2017, 6 pages. |
European Office Action, dated Jul. 30, 2019 in connection with European Application No. 17151332.8, 4 pages. |
Japanese Office Action for Application No. 2017-003411, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20200026821 A1 | Jan 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14995781 | Jan 2016 | US |
Child | 16417038 | US |