Patent Application
20210139167
The present invention relates to assessing system performance for revolving mechanical components of a kind employed in rotary systems, such as transport systems. More particularly, the present invention relates to monitoring vibrations in complex gear systems such as for example planetary gear systems, or rotating turbine blades.
Vehicular Sensors and Sensing Systems: Modern transport vehicles (hereinafter, “vehicles”) include helicopters, airplanes, cars, trucks, boats and trains. It is common for vehicles to include electronic sensors to monitor both the performance and the environment of a vehicle. In a vehicle, one or more accelerometer sensors may record data indicative of the performance or the behaviour of mechanical systems or electromechanical systems, such as engines or transmissions.
The data obtained via vehicle sensors may be used for multiple purposes. For example, a sensor may monitor real-time performance of a vehicle component to ensure a component is operating within safe or appropriate parameters (for example, for heat, pressure, electrical performance, and similar). Where variations from expected performance ranges are detected by a sensor, a hardware processor with suitable code may be used to adjust operations of the vehicle to correct for problems. Another use of collected sensor data is for after-the-fact analysis of vehicle performance. After-the-fact analysis may help with the development of vehicle prototypes during a vehicle design process. In other cases such data, when analyzed over time, may provide early-alert warnings to potential or pending problems for the vehicle already in field use.
Data Acquisition and Processing Units: A vehicle's sensing/monitoring system (VSMS) is formed of one or more unique maintenance and/or safety systems that are already fitted to many vehicles, including in particular but not limited to aircraft, such as airplanes and helicopters. These maintenance and/or safety systems will typically entail the use of multiple Data Acquisition and Processing Units (DAPUs), which each collect and process data from various sensors. Exemplary DAPUs may include, for example and without limitation: Crash-Survivable Cockpit Voice & Flight Data Recorders (CVFDR); On-board Maintenance Systems (OMS); Engine Monitoring Units (EMU); and Health & Usage Monitoring/Management Systems (HUMS).
For example, a health and usage monitoring system (HUMS) is fitted to machinery primarily in order to give advanced warning of impending failures. In helicopter applications of a HUMS, these systems perform data acquisition, processing, storage and transmission, drawing their data from dedicated sensors (such as accelerometers).
Vibration Monitoring and Gear Systems: Typical DAPU functions, such as HUMS functions, include vibration health monitoring (VHM) of portions of a helicopter. Vibration sensors may be employed to monitor the amount of vibration in gear systems throughout the vehicle. These vibration sensors, in conjunction with suitable DAPUs, can determine whether or not the vibration signature remains within designated limits, which may be determined by engineers during system design or which may be user configurable via software. The limits may be designated with respect to, or out of concern for, gear/drivetrain safety issues, performance assessment, indications of wear-and-tear, and many other factors.
Vibration signatures may include for example and without limitation: vibration amplitude, vibration frequency, time variations of frequency or amplitude, averages of amplitude or frequency, frequency bandwidth, and any number of other parameters of the raw sensor vibration signal, or characteristics derived from the raw signal.
Because gears turn, it is generally not practical or even possible to mount vibration sensors on the rotating gears themselves. Instead, vibration sensors are typically mounted on a housing which contains the gears. A vibration sensor can detect vibrations of fixed-location (fixed relative to the sensor), nearby gears within the housing. However, such monitoring yields only indirect recording of the vibrations of the actual gears themselves.
Epicyclic Gear Monitoring: Further, some gear systems, referred to equivalently in this document as “planetary gear systems” and “epicyclic gear systems”, involve multiple gears which are engaged in two movements: the first movement is a turning around its own center point by each gear of several planetary gears; the second movement is a spatial rotation/revolving of the several planetary gears around a common central axis.
Due to this revolving of the gears, individual gears move cyclically in- and out-of range of a fixed vibration sensor on the gear system housing. Planetary gear systems therefore pose additional challenges for accurately identifying/isolating the vibrations which may be due to a specific gear among the multiple gears. As opposed to other gears which may be fixed in place in a drivetrain, the position of the planetary gears relative to a fixed sensing location varies greatly during normal operation. Planet gears can only be monitored when they are known to be within range of the sensor.
In conventional sensing systems for planetary gear systems, then, a complete picture of gear health must be built-up by sensing gear vibrations over multiple revolutions over time. This generally results in a time-imprecise or “fuzzy” reconstruction of gear vibrations. Due to the number of samples required and the nature of the planetary gearbox, a time-averaged vibration signal can take tens-of-minutes to acquire. Further, to ensure that samples which are time-averaged are comparable samples, the samples are only acquired in the same or comparable “regimes” (for example, signals obtained during the same or similar flight conditions). This further limits the opportunity to collect averaged signals.
Given the aforementioned deficiencies, what is needed is an improved system and method for monitoring complex gear systems such as planetary gear systems where the positions of some gears are not fixed over time. An improved monitoring system for planetary gears also has applications for other types of rotary mechanical systems.
In an embodiment, the present system and method employs multiple vibration sensing points on the outside of the gearbox/housing. The method then aggregates the vibration signals relating to the same gear (or gear bearing) from the multiple sensors. In an epicyclic gearbox this allows the planet gears to be “tracked’ by the multiple vibration sensors through their rotation around the central shaft axis.
This present system and method provides benefits for the speed in which a complete scan of the gear can be completed. This system and method also increases the number of samples to reduce the influence of noise in the signal average, and provides a consistent load path for the transmission of planet bearing vibration. It will be noted that the sun gear is also monitored, if only indirectly, via monitoring of the planet gears and ring gears; the present system and method benefits from providing a consistent load path for the monitoring of the sun gear (since the sun gear is monitored via sensors at different angles in relation to the central axis of the sun gear).
Other specific implementation details and benefits of the present system and method, as well as other embodiments and additional applications, will be apparent to persons skilled in the art from the detailed description and drawings which follow, and also from the appended claims.
Advantageous designs of embodiment of the present invention result from independent and dependent claims, the description, and the drawing. In the following, preferred examples of embodiments of the invention are explained in detail with the aid of the attached drawings. The drawings, which are incorporated herein and form part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the relevant art(s) to make and use the invention.
While the present invention is described herein with illustrative embodiments for particular applications, it should be understood that the invention is not limited thereto.
The following detailed description is merely exemplary in nature and is not intended to limit the system and methods, the elements or steps of the system and method, its applications, and its uses disclosed herein. Further, there is no intention for the scope to be bound or limited to or by any theory presented in the preceding background or summary, nor in the following detailed description. Those skilled in the art with access to the teachings provided herein will recognize additional modifications, applications, and embodiments within the scope thereof and additional fields in which the invention would be of significant utility.
Throughout the application, description of various embodiments may use “comprising” language, indicating that the system and method may include certain elements or steps which are described; but that the system and method may also include other elements or steps which are not described, or which may be described in conjunction with other embodiments, or which may be shown in the figures only, or those which are well known in the art as necessary to the function of processing systems. However, it will be understood by one of skill in the art, that in some specific instances, an embodiment can alternatively be described using the language “consisting essentially of” or “consisting of.”
For purposes of better understanding the present teachings and in no way limiting the scope of the teachings, it will be clear to one of skill in the art that the use of the singular includes the plural unless specifically stated otherwise. Therefore, the terms “a,” “an” and “at least one” are used interchangeably in this application.
Headings used in this detailed description are present only to assist in making this document readable and easy to navigate, and should not be construed as defining or limiting.
The system and method is not limited to the embodiments described below, which are exemplary only. Rather, the full scope of the system and method is recited in the claims which follow. It will be further understood that the appended claims are themselves disclosure, and the full scope of the system and method may include elements which are recited in the claims only.
Vehicle and Sensors
The vehicle 100 may include a sensor or a multitude of sensors 105, typically of different types. The sensors 105 may have elements which are electrical, mechanical, optical, and/or chemical, and may sense various environmental or vehicle phenomena or energies. The sensors 105 operate in real-time to provide a time-series view of the magnitude or intensity of the phenomena they sense, the real-time data being provided as output as either raw electrical signals with varying voltages and currents, or as digital/numeric sampled data.
Exemplary placements within or along the vehicle 100 of numerous exemplary sensors 105 are shown in the
Mechanical State/Property Sensors: Included among the sensors 105 may be mechanical state/property (MSP) sensors 110, such as vibration sensors 110 that are also referred to as accelerometers 110. (Persons skilled in the art will appreciate that, as used herein, the term “accelerometer” is employed equivalently to “vibration sensors”, as opposed to the types of acceleration detectors which may be employed to detect gross acceleration of the entire vehicle 100.) Vibration sensors 110 may detect vibration frequencies, vibration magnitudes, or waveforms which reflect vibration frequency and magnitude. In alternative embodiments of the present system and method, mechanical state sensors 110 may include other types of mechanical sensors as well, such a time-of-arrival sensors 1110 for engine blades 1115 (see
In one embodiment of the present system and method, traditional vibration sensors 110 (such as piezo-electric sensors) may be employed. In an alternative embodiment, MEMS (micro-electrical mechanical systems) vibration sensors 110 may be utilized. Other vibration sensors 110 may be employed as well.
The gear system 200 is internal to helicopter 100 (and so not shown in the view of
In the figure only a few vibration sensors 110 are illustrated. As will be understood by persons skilled in the relevant arts, placements of vibration sensors 110 may be made at any gearbox among multiple gearboxes 210 within the drive train or within/associated-with other mechanical elements (for example, along or within the engine).
Shown in the figure is one vibration sensor 110 only associated with each single gearbox 210. Embodiments of the present system and method employ multiple vibration sensors 110 associated with a single gear box 210.
Exemplary Vehicle Sensing/Monitoring System According to Present Art
(1) Multiple Data Acquisition and Processing Units (DAPU) 307, which may for include for example and without limitation: a Crash-Survivable Cockpit Voice & Flight Data Recorder (CVFDR) 307 an On-board Maintenance Systems (OMS) 307, Quick Access Recorders (QAR) 307, and a Health & Usage Monitoring/Management Systems (HUMS) 307. The DAPU(s) 307 support the recording of vehicular sensor data, the processing and analysis of that sensor data, storage of both raw and analyzed sensor data, and distribution of the raw/analyzed/stored data to aircraft display and control elements, and to off-vehicle computers. The DAPU(s) 307 function as the real-time processing and data storage cores of the VSMS 300; and
(2) One or more Vehicular Distributed VSMS Elements 350, which may include a variety of sensors 105/110 distributed throughout the vehicle 100, including mechanical state sensors (MSP) 110, as well as other elements 350.n.
Both of these are discussed further immediately below.
Data Acquisition and Processing Unit (DAPU)
As illustrated schematically in the callout in
(a) A circuit card assembly (CCA) 310, which may also be known in the art as a motherboard 310, which typically holds and interconnects various microchips, including for example microchips 315/320/325 discussed immediately below (paragraphs (b), (c), (d), and (e)), and also bus 303 (paragraph (f)). In some embodiments, the CCA 310 may also hold or mount either or both of power supply 318 (paragraph (h)) and/or data storage 320.3 (paragraph (g)).
(b) One or more hardware processor 315(s), also known as a central processing unit (CPU) 315 or microcontroller unit (MCU) 315, which provides for overall operational control of the DAPU 307. This includes but is not limited to receiving data from sensors 105, and possibly modifying some operations of sensors 105 via various application specific integrated circuits (ASICs) 325. The MCU 315 may also be programmable or hard-coded to support the processing and analysis functions of the present system and method.
(c) Volatile memory 320.2, such as dynamic RAM (DRAM), may be used to temporarily store data received from the sensors 105. Volatile memory 320.2 may also be used to temporarily store some or all of the code from static memory 320.1, and also for temporarily storing processed sensor data which is generated by the hardware processor 315 based on the data received from sensors 105.
(d) Static memory or firmware 320.1 for storing non-volatile operational code, including but not limited to operating system code, computer code for locally processing and analyzing data from sensors 105, and computer code which may be used specifically to enable the DAPU 307 to implement the methods described in this document and other methods within the scope of the appended claims. In particular the CPU 315 may employ the code stored in the static memory 320.1 to implement the methods described in this document and other methods within the scope of the appended claims.
(e) Interface circuits 325 may perform a variety of tasks, including data and control exchanges with sensors 105, as well as input/output (I/O) tasks, network connection operations, control of the bus 303, and other tasks generally known in the art of processing systems. Interface circuits 325 may also control or interface with non-volatile data storage 320.3.
Interface circuits 325 may also support such functions as external input/output (for example, via USB ports, an Ethernet port, or wireless communications, not illustrated in the figure); addressing and receiving data from various aircraft and engine data buses 350.1; and a cockpit interface panel 350.3 and/or a remote cockpit control unit (CCU) 350.2.
(f) A system bus 303 may serve to transfer data and messages between elements of motherboard 310, and between motherboard 310 and various other sensors, microchips, and controllers of DAPU 307.
(g) Non-volatile data storage 320.3 provides long-term storage for sensor data, which may include some raw sensor data recorded over time; but typically includes processed (and thereby condensed) sensor data. Non-volatile storage 320.3 may take the form of hard disk drives, solid state drives (including flash drives and memory cards), recording on magnetized tape, storage on DVD or similar optical disks, or other forms of non-volatile storage now known or to be developed.
(h) A power supply 318, which may be mounted on CCA 310 or may be a separate element within the DAPU 307.
Volatile and non-volatile memory or storage 320.2/320.3, along with CPU 315, enable at the hardware level the operations of the DAPU 307 and also enable the operations of the present system and method.
Above it is indicated that a DAPU 307 contains internal memory 320.1/320.2. In some embodiments, a DAPU may have or be connected to/coupled with one or more memory receptacles or storage receptacles (MCRs) (not shown) configured to contain the memory 320.1/320.2 or storage 320.3, or in some embodiments to contain supplementary, backup, or additional memory 320.1/320.2 or storage 320.3, which can be inserted and removed via an exterior access port of the MCR.
Ports and connectors: Not shown in
Vehicle Sensing/Monitoring System (VSMS) Elements
Monitoring of Mechanical Phenomena, Behaviors, Properties, or States
The system and methods disclosed in this document are mainly taught as entailing the sensing of (i) vibrations of a component or components of a mechanical system or (ii) a time of arrival of a component or component at a particular point along a traversal path within a mechanical system (such as a transport system). However, persons skilled in the relevant arts will appreciate that the present system and method, with suitable mechanical property sensors or mechanical state/property sensors (MSP sensors), may be employed to sense other time-varying mechanical states, properties, phenomena, or behaviors of one or more mechanical elements within a mechanical system. For example, multiple suitable optical sensors, brush sensors, magnetic sensors, capacitive sensors or other sensors, with suitable processing, may be employed to sense for emerging cracks or “pitting” in a mechanical element, where early detection of an emerging structural crack or flaw may help prevent a safety hazard for the mechanical system. For another example, multiple suitable MSP sensors, with suitable processing, may be employed to sense small variations in position of a mechanical component (for example, due to a gradual-but-progressive failure of a supporting structural element for the sensed component).
Planetary (Epicyclic) Gear System with Single Vibration Sensor
For convenience herein, a planetary gear system/epicyclic gear chain 405 may be referred to herein, below, simply as a “gear system 405” or “gear chain 405”.
A gear 403 (or cogwheel 403) is a rotating machine part having cut teeth (or in the case of a cogwheel, inserted teeth called cogs), which mesh with another toothed part to transmit torque (rotational force). A gear is typically flat and round, with teeth of equal sizes arranged adjacent to each other on the outer circumference. In some cases, a gear may have a hollow circular rim with the cogs arranged on the interior surface of the rim. The entire arrangement of gears 403 and planet carrier 440 is contained within a gearbox housing 210, which is generally maintained and secured within a fixed position within a vehicle 100.
Persons skilled in the relevant arts will appreciate that in
Planet gear systems 405 are well known in the art, and a detailed operational description is not provided here. But it will be observed that exemplary planetary gear system 405 has an inner sun gear 410 (with teeth on the outer circumference); four planet gears 415 (also with teeth on the outer circumference) arranged symmetrically and equidistantly around the sun gear 410; and an outer, hollow ring gear 420 (also known as an “annulus gear”) with interior teeth, arranged symmetrically around the inner sun gear 410, around the four conjoined planet gears 415, and around a central axis or gearshaft 435. The four planet gears are arranged to be conjoined via the four symmetric arms of the planet carrier 440, which is centrally mounted on the gearshaft 435.
Persons skilled in the art will appreciate that the use of four planet gears 415 is exemplary only, and fewer (three) or more (four or more) may be employed.
Persons skilled in the art will also appreciate that a planetary gear system, such as exemplary gear system 405, is employed to transfer torque and rotational speed between the sun gear 410 and the ring gear 420 via rotation of the planet gears 415. For the planetary gears 415 and planet carrier 440 as a unit, the common speed/direction of rotation 475 may be either clockwise (as shown in
Vibrations: The combination of both rotation 475 and gear turning 477 results in each planet gear 415 generating mechanical vibrations (537, see
Each planet gear 415.n passes within the effective sensor angle 450 just once per planet carrier rotation 475. Each time a planet gear 415.n passes this sensing point, a different part of the gear 415.n is visible (that is, is in closest contact with sensor 110), and so a signal average covering all gear teeth must be built up over a number of rotations (determined by gearbox geometry). Planet bearing monitoring is also challenging as a consistent load path to each bearing is not available.
Broadly speaking the epicyclic gear system 405 is a noisy monitoring environment, and so increasing the samples over which a signal average is created is desirable, but also increases the time to complete a vibration scan.
Consolidated Vibration Data from a Single Vibration Sensor
Vibration signatures: Because the rotation speed (via a tachometer) and the geometry (via transfer of information from the gearbox manufacturer) are known for gear system 400, it is possible to assign one or more vibration signatures 517 to a “gear data bin” 515.N representing each gear 415.g on the gear system 400. Vibration signatures 517 may also be referred to as vibration data samples 517 or vibration signal samples 517, and may be indicative of vibration intensity, vibration frequency, or both.
For any one planetary gear 415.g, multiple data bins 515.g.t with their vibration data samples 517 may be combined over time to obtain a consolidated vibration profiles 520.N indicative of the vibrations 537.g of each planetary gear 415 over time. The vibration profiles 520.N reflect the actual vibrations 537.g of each planet gear 415.
Method for Vibration Sensing With A Single Sensor
In general, however, it is desirable to obtain not only an approximate (e.g., time averaged or representative) vibration data for each planetary gear 415.g. Rather, it is desirable to obtain tooth-specific or tooth-localized vibration data 505 for each tooth (or a series of closely-spaced adjacent teeth) for each planetary gear 415.g. (As per above, gear teeth are not illustrated in
Again because there is a known rotation speed (via a tachometer) and the system geometry (via transfer of information from the gearbox manufacturer) for exemplary gear system (410) with single vibration sensor (110), it is possible to assign vibration signatures 517 to a “teeth bin” representing each tooth on each planet gear 415.g, based on a time-offset from the first acquisition.
On each pass a given planet gear 415.g presents a different set of gear teeth to the ring gear 420 over the effective angular range 450 at which vibrations are sensed by vibration sensor 110. Consequently, many revolutions 475 of the planet gears 415 are necessary before vibration signatures 517 are observed from each and every tooth on each planet gear 415.
Furthermore, throughout the vibration sensing process, signal averaging is typically employed to reduce the distortions from random noise. This means that when employing only one vibration sensor 110, multiple vibration signatures 517 from each tooth on each gear 415.g are required to build up a sample to average over, further increasing the number of planet gear revolutions 475 required.
Because the rotation speed (via a tachometer) and the geometry (via transfer of information from the gearbox manufacturer) are known, it is possible to assign vibration signatures 517 to a “tooth bin” representing teeth on the planet gear based on a time-offset from the first acquisition.
As is known in the art, typical planet gears 415 may have many teeth, numbering in the dozens or even hundreds. However, in an exemplary case, and for each planet gear 415.g, only a few gear teeth (for example, three (3) gear teeth or six (6) gear teeth) from among the total number of gear teeth may be visible for each interval of vibration sensor data acquisition.
As discussed in detail below a method may be employed for gear-and-teeth specific vibration sensing, such as exemplary method 600 below. In the exemplary instance with vibration data acquisition for six (6) gear teeth at a time, and during the first acquisition time window (for acquisition of vibration data for gear bins 515.A.1 through 515.E.1), the vibration samples for each gear tooth are assigned to tooth vibration bins one (1) through five (5). (For example, planet gear 415.A may have 70 teeth, so the vibration data for planet gear 415.A is divided into tooth bins which may be numbered 1 to 70.) The initial gear vibration readings may then be stored in tooth data bins 1 through 6 (for example, tooth data bins addressed as A.1.1 through A.1.6).
The second time the same planet gear (for example, 415.A) passes by sensor 110, it will be known that the teeth presented are offset by “x” from the first acquisition. For this acquisition the time windowed vibration samples are assigned to tooth data bins x+1 through x+6 (which may be identified as A.2.x+1 through A.2.x+6). This process continues until the averaged signal for each bin shows minimal difference from the previously calculated average, as determined by a signal convergence check.
Method for Tooth-Specific Vibration Sensing With A Single Sensor
The process for legacy systems with one single vibration sensor 110 can be summarised as follows, according to method 600 of
The method begins with step 605, which entails continuously acquiring vibration data 505 from single vibration sensor 110.
In step 610, time windows are applied to identify both the specific planetary gear 415.g, and to extract from the gear's data bin 515.g.t the vibration data 505 for each tooth.
The method continues with step 615, which resamples the data to reduce the number of points stored. (This step is a practical consideration. The vibration signatures 517 are typically acquired at a much higher frequency than is needed for planet gears 415, and the extraneous data would create an unnecessary processing overhead.)
The method continues with step 625, where the windowed and resampled data 517 is assigned to a gear-specific tooth bin representing the gear-tooth to which it pertains. [It is noted that a step numbering of “620” is deliberately not used for flowchart 600.]
The method continues with step 630. In step 630, a signal average is calculated from all vibration signal samples 517 assigned to each tooth bin.
The next step, step 635, applies to each tooth bin a convergence check. The convergence check is used to compare the signal average just calculated to the signal average from the previous iteration.
If the signal convergence is below a configured value (meaning the signal has not converged sufficiently to indicate a stable signal average), then more vibration acquisitions are required, entailing a return to step 605. If in step 635 the signal convergence is satisfactory (that is, above the configured signal convergence threshold), the averaged vibration data for the tooth bin is accepted.
When averages for all bins are accepted no further vibration acquisitions are required to establish a current level of vibration for the planetary gears 415. However, vibration monitoring may be continued, and the method 600 repeated, to determine any changes in the vibration levels 500 of gear system with single sensor (400).
As noted above, the epicyclic gearbox 405 is a noisy monitoring environment. Therefore, with a single sensor, lengthy scan times may be required and to provide adequate signal averaging and convergence. The present system and method addresses this deficiency, among others.
Exemplary Planetary Gear System With Multiple Vibration Sensors
(i) the exterior surface of ring gear 420 (that is, a surface which faces away from the sun gear 410 and the planet gears 415;
(ii) an interior surface of the ring gear 420 (the surface which faces the sun gear 410 and right gears 415), for example on a ring gear 420 which is wider than the planet gears 415, thereby having an interior surface which may not make contact with the planet gears and so provides a suitable interior surface for the vibration sensors 110.1; or
(iii) either of the two surfaces on the transverse plane of the ring gear 420.
Though not illustrated in
The exemplary planetary gear system 705 may be the same or substantially similar to the planetary gear system 405 of
Similarly, the rotation direction 475 illustrated in the figure is exemplary only, and a reverse rotation may be employed. The sun gear 410 may be fixed so that the angular output of the gear system 705 is transmitted via the ring gear 420; or the ring gear 420 may be fixed in position. Similarly, multiple sizes and configurations of gear teeth (not shown in the figure) may be employed, as is known in the art, consistent with the present system and method. The relative sizes of gears 403, such as sun gear 410, planet gears 415, and ring gear 420 are also exemplary and for purposes of illustration only, and should not be construed as limiting.
Persons skilled in the relevant arts will appreciate that in
Vibrations: As with legacy systems, the combination of both rotation 475 and gear turning 477 results in each planet gear 415 generating vibrations 537. For system health and operational safety, mechanical vibrations 537 are analyzed to determine consistency with system health and operation safety parameters/limits.
In exemplary embodiment of multi-sensor planetary gear system (MSPGS) 700, multiple vibration sensors 110.s are deployed on the exterior of gearbox 210 of planetary gear system 705. Each vibration sensor 110.s is situated at a fixed point on gearbox 210. In an alternative embodiment, and as discussed above, the multiple vibration sensors 110.2 are affixed to specified points directly on the ring gear 420. As the planet gears 415 undergo rotation 475, each planet gear 415.g successively passes near each of the fixed locations of multiple sensors 110.s. Each vibration sensor 110.s may, in turn, effectively detect vibrations from each of the planet gears 415.g when each respective planet gear 415.g is within an effective sensor angle 450 for the vibration sensor 110.s.
Number of Vibration Sensors: The number (s) of vibration sensors 110 illustrated in MSPGS 700 is eight (8), but this number of vibration sensors is exemplary only and not limiting. Fewer sensors (for example, just two (2)), or more than eight (for example, ten (10) or more vibration sensors) may be employed. In one embodiment of the present system and method, there may be one vibration sensor 110.s deployed on the gearbox 210 for each planetary gear 415.g. (That is “s” may equal “g.”) In an alternative embodiment, the number (s) of vibration sensors 110 may be twice the number (g) of planet gears 415, or three or four times the number (n) of planet gears 415.
In an alternative embodiment, the number (s) of vibration sensors 110 deployed may be system-specific, and is determined by for example a lowest number (L) of vibration sensors 110 required to ensure that each planet gear 415.g is always detected by at least one vibration sensor 110.g. In yet another alternative embodiment, the number of vibration sensors 110 deployed may be greater than L, providing for varying degrees of sensing redundancy, so that at any time the vibrations from at least some planetary gears 415 are detected by more than one vibration sensor 110. Such sensor redundancy may allow for more refined determinations of vibration data, or may help compensate for an exceptionally vibration-noisy planetary gear system 705, or for an exceptionally vibration-prone/noisy local internal environment of the vehicle 100.
Positioning/Spacing of Vibration Sensors: In some embodiments of the present system and method, the multiple vibration sensors 110 are spaced as shown in
In an alternative embodiment, some portions or arcs along the sensing path 780 may be more densely populated with vibration sensors 110 (meaning along the entire arc of the vibration sensors 110), with some pairs of adjacent sensors 110.s spaced more closely to each other than pairs of adjacent vibration sensors 110.s. For example, a particular arc portion of the sensing path 780 may receive additional, fixed-location vibration sensors 110 if it is known or anticipated that such portion of the arc will be oriented towards or otherwise coupled with other proximate vehicle systems which are anticipated to generate an exceptional amount of vibration noise or audio noises.
Operational Effect of Multiple Vibration Sensors: In various embodiments of a multi-sensor planetary gear system (MSPGS) 700, planet gear vibrations 537 are sampled across the multiple sensor locations as the planet gears 415 rotate in unison along the interior gear surface of ring gear 420. Synchronous time-windowing is then used to identify and separate respective time periods of interest with sensor data relating to a planet gear 415.g of interest. These time windows are then aggregated and averaged across multiple rotations, which is then used as an input to the DAPU/HUMS 307 condition indicator calculations. Details of this method are discussed further immediately below.
In some embodiments, the combined results of using multiple sensors 110 and the time-windowing methods of the present system and method have the constructive effect of making the planet gears 415.g appear “stationary” in relation to a single “virtual vibration sensor”; the vibration data for the single virtual sensor is constructed (as discussed below) as a composite based on data from what are actually multiple separate vibration sensors 110.s. As the relative position between each planet gears 415.g and the virtual vibration sensor remains substantially constant, all parts of the gearbox housing 210 can be monitored continuously for vibration data (rather than once per carrier rotation as with legacy systems with one sensor).
Consolidated Vibration Data from Multiple Vibration Sensors
The signal processing 800 illustrated in
Illustrated in
For each respective planet gear 415.g of the plurality, and for each vibration sensor 110.s of the plurality (or other periodically rotating element, as applicable), the present system and method determines an element-dependent and sensor-dependent time range (GDSD time range) when a given planet gear 415.g passes within a sensing range 450.s of a given sensor 110.s. Because the rotation speed (via a tachometer) and the geometry (via transfer of information from the gearbox manufacturer) are known for gear system 705, it is possible to assign vibration signatures 517 to “gear data bins” 815(s).g.t which each represent: (i) vibration data for each gear 815.g as (ii) detected by each sensor 110.s. For each planetary gear 415.A, 415.B, 415.C, 415.D, 415.E, multiple successive sensor data bins 815(s).g.t are then obtained from each vibration sensor 110.s over successive time periods (T).
For any one planetary gear 415.g, and based on vibration sensor data bins 815(s).g.t from multiple vibration sensors 110.s, their vibration data samples may be combined over time to obtain a consolidated vibration profiles 820.g indicative of the vibrations 537.g of each planetary gear 415.g or each tooth on each planetary gear over time.
Process for Vibration Sensing With Multiple Sensors
As discussed above, it is desirable to obtain not only an overall vibration data for each planetary gear 415.g. Rather, it is desirable to obtain tooth-specific or tooth-localized vibration data 505 for each tooth (or a series of closely-spaced adjacent teeth) for each planetary gear 415.g. (As per above, gear teeth are not illustrated in
Vibration signatures: As discussed above, and due to the known rotation speed 475 of shared planetary gears rotation (known via a tachometer), and due to the known system geometry (via transfer of information from the gearbox manufacturer) for exemplary gear system (700) with multiple vibration sensors (110.s), in an embodiment it is possible to detect vibrations 537 from individual gear teeth. In an alternative embodiment, vibrations 537 may be ascertained with respect to identifiable small subsets of teeth among the overall gear teeth.
It is then possible to assign sensor-specific tooth vibration signatures 817(g) to “teeth bin” representing each tooth on each planet gear 415.g, based on a time-offset from the first acquisition. As discussed above, and similar to vibration signatures 517 for a legacy single sensor system, in various embodiments a vibration signature 817(g) may be a single value indicating a level of vibration each time a gear tooth is sensed; or a time series of values over a short time interval over which a gear tooth is sensed; or some other digital characterization of vibration intensity when a gear tooth is sensed; in alternative embodiments, a vibration signature 817(g) may be understood as a series of vibration values, or a waveform representation of vibration values, over some more extended time over which a gear tooth is repeatedly sensed. The sensor-specific vibration signature 817(g) for a gear tooth may also be known in this document as a “tooth vibration signature” 817(g).
In an embodiment of the present system and method, a whole collection of vibration signatures 817 for all the teeth on a gear 415, and from all the sensors 415.1, may be viewed as a gear vibration profile 820.g for the entire gear. In an alternative embodiment, a gear vibration profile 820 may be determined by analysis or storage of a subset of tooth vibration signatures, or by a processed summary (such as an average, peak values, or minimum values) of multiple tooth vibration signatures 817 for a period of time.
Persons skilled in the relevant arts will appreciate that it is a purpose and effect of the present system and method to accurately and quickly identify, over time, variations in vibration signatures—either or both of tooth vibration signatures and/or gear vibration signatures—which may indicate stresses on, damage too, or problems with a planetary gear system 705.
Process: An exemplary process 800 of data acquisition for a planetary gear system 705 with multiple vibration sensors 110.g, according to the present system and method, may entail some elements which are illustrated in part in
Each of the multiple vibrations sensors 110.g has an effective sensor range 450.g, which may also be referred to as an “effective gear vibration detection range” 450.g, as illustrated in
In an embodiment of the present system and method, a single revolution 475 of the planet gears 415 (such as any one of time periods T1, T2, T3, or T4) may be sufficient to observe, via the multiple sensors 110.s, all of the vibration signatures 820 for each tooth on each planet gear 415.
In an embodiment of the present system and method, signal averaging is employed to reduce the distortions from random noise. This means that even when employing multiple vibration sensors 110.s, multiple vibration signatures collected over multiple revolution time periods T, from each tooth on each gear 415.g, may be required to build up a sample to average over. However, with multiple sensors 110.s employed, it is expected that a sufficiently reliable vibration profile 820 may be acquired with fewer planet gear revolutions 475 than the number of revolutions required under legacy systems.
The planet gear rotation speed (via a tachometer) and the geometry (via transfer of information from the gearbox manufacturer) are known. It is therefore possible to assign, for each vibration sensor 110.s, vibration signatures 817(g) to sensor-specific, gear-specific, and tooth-specific tooth bins which represent representing teeth on the planet gear as sensed by each sensor 110.s, all based on a time-offset from the first acquisition.
As discussed in detail below a method may be employed for sensor-specific, and gear-and-teeth specific vibration sensing, such as exemplary method 900 below. In the exemplary instance with vibration data acquisition for six (6) gear teeth at a time:
For a first vibration sensor 110.1, and during first time window (that is, a first portion of the first acquisition time period T1), the first vibration sensor may acquire vibration data for gear bin 815.A.1 representing vibration data from gear 415.A, with the vibration samples 817(1) for each gear tooth being assigned to tooth vibration bins one (1) through five (6) for the first vibration sensor 110.1.
For a second vibration sensor 110.2, and during the same first time window, (the same first portion of the first acquisition time period T1), the second vibration sensor may acquire of vibration data for gear bin 815.B.1 representing vibration data from gear 415.B, with the vibration samples 817(2) for each gear tooth of gear 415.B being assigned to tooth vibration bins seven (7) through twelve (12) for the second vibration sensor 110.1.
For an Jth vibration sensor 110.J, and during the same first time window (the same first portion of the first acquisition time period T1), the Jth vibration sensor may (i) first acquire vibration data first for gear bin 815.C.1 representing vibration data from gear 415.C, with the vibration samples 817(J) for each gear tooth of gear 415.0 being assigned to tooth vibration bins k through k+3 for the Jth vibration sensor 110.1, and (ii) then acquire vibration data first for gear bin 815.D.1 representing vibration data from gear 415.D, with the vibration samples 817(J) for each gear tooth of gear 415.J being assigned to tooth vibration bins k+4 to k+6 for the Jth vibration sensor 110.J.
Subsequently, for each vibration sensor 110.s, and during a second time window (a second portion of the first acquisition time period T1), each vibration sensor 110.s will acquire six (6) bins of tooth vibration data for a series of adjacent teeth for a successive gear.
Persons skilled in the relevant arts will appreciate that the values provided above are exemplary only. For each sensor 110.s, all of the following may vary during any given portion of a full rotation time period T, due to the number of planet gears 415, due to the rotation speed/direction 475, and due to the relative sizes of the planet gears 415, sun gear 410, and ring gear 420: the planet gear 415.g detected, and which teeth on the gear are detected. Further, it is possible that during some time periods T, one or more vibration sensors 110 may detect vibrations from no planet gear, or detect vibrations from teeth from two successive planet gears.
As shown in
Exemplary Method Elements
In method 900, vibrations 537 from an exemplary rotary mechanical system 700 is sampled across multiple locations by respective multiple sensors (s) to obtain multiple vibration data samples 805(s), for example at multiple different angular positions along a gearbox housing 210 or along the ring gear 420 of the rotary mechanical system 700. The data vibration data 805 is sampled at the multiple angular locations via fixed, distributed vibration sensors 110(s) (110(1) 110(2) . . . 110(M). Synchronous time windows 912.t are applied to separate periods of interest relating to a common mechanical component of interest, for example relating to a rotating planet gear 415.A.
Synchronous time windows 912.t are defined as time windows (brief time intervals) which may occur at different specific times (t) at each sensor (s), but each synchronous time window corresponds to capturing vibration data from a particular common mechanical component, for example to a common rotating planet gear 415.K (where K is any specific gear from gear 1 through gear G). The times (t) are calculated by the hardware processor 315 as a function of each sensor location, the rotation speed 475 of the planet gears 415, and the overall geometry and spatial arrangement of the planetary gear system 705.
In the exemplary case illustrated, this result is multiple bins 815(sensor).gear_A.time of gear data 805 for planet gear 415.A, each of the multiple bins 815(s).A.t indicative of data:
from a particular sensor (for example, s=sensor 1, 2, . . . M);
for the particular common gear (in the exemplary case, g=gear A); and
for successive time windows 912.t (in the exemplary case illustrated, time intervals t=1, or t=2, or t=m), so as to capture from each sensor (s)=1, 2, . . . M the vibration data for the common gear (g=gear A, in the exemplary case shown).
This results in the capture of exemplary data bins 815(s).g=A.t.
In a method step 950, these data bins 815 are both resampled over multiple rotations 475 of the planetary gear system; and then all the data bins are scaled by a configured sensor-specific factor, to ensure that data from each sensor 110(s) is of a similar amplitude. Scaling my be accomplished through various methods including, for example and without limitation: software data rescaling, adjusting signal gain, or other electronic means. Rescaling compensates for design and manufacturing variations between sensors 110, and for variations in sensor placement along the gearbox housing 210, and other factors which may make sensor data be different than nominal sensor data.
In a step 955, data bins are aggregated, for example associating all the data bins 805 from multiple sensors (s) from different time periods (t) which are associated with a given gear g (for example, g=A). In a step 960, these signals may be averaged.
Aggregated and averaging across multiple rotations the data from multiple sensors over multiple time periods results in a time averaged vibration profile 820.g for each gear 415 of the planetary system. These results are then used as an input to the HUMS 307 condition indicator calculations or as input to other DAPUs 307.
The effect of exemplary process 900 is to makes each planet gear 415.g appear “stationary”, as the relative position between each gear 415.g and an apparent single “virtual sensor” remains constant. As a further result, and all planet gears 415 of the planetary gear system 705 can be monitored continuously, rather than once per carrier rotation 475.
While elements of a method 800 and a method 900 have been described above with respect to acquiring per-gear sampling data, analogous methods with more refined or narrow time windows may also be applied to collect vibration data for specific gear teeth from multiple sensors 110.s.
Exemplary Method for Tooth-Specific Vibration Sensing With Multiple Sensors
Another exemplary method 1000 for vibration sensing with multiple vibration sensors 110.s is presented in
The method 1000 begins with step 1005, which entails continuously acquiring vibration data 805 from each and all of the multiple vibration sensors 110.s.
In step 1010, for each sensor (s), time windows are applied to identify both the specific planetary gear(s) 415.g being sensed, and to extract from the gear's data bins 815(s).g.t the vibration data 805 for each tooth.
The method continues with step 1015, which resamples the data to reduce the number of points stored. (This step is a practical consideration. The vibration signatures 817 are typically acquired at a much higher frequency than is needed for planet gears 415, and the extraneous data would create an unnecessary processing overhead.)
The method continues with step 1020. In step 1020, data from each vibration sensor 110.s is rescaled, by a configured sensor-specific factor, to ensure that data from each sensor 110.s is of a similar amplitude. Scaling my be accomplished through various methods including, for example and without limitation: software data rescaling, adjusting signal gain, or other electronic means. Rescaling compensates for design and manufacturing variations between sensors 100, and for variations in sensor placement along the gearbox housing 210, and other factors which may make sensor data be different than nominal sensor data. The rescaling factor for each sensor 110.s may be determined by a system operator, by manually examining vibration signatures from each sensing point as compared among different sensors for a common planet gear (or for each separate planet gear); or via algorithms designed to determine rescaling factors according to suitable criteria.
The method continues with step 1025, where the windowed and resampled data 817 for each sensor (s), that is a vibration signature 817(s), is assigned to a gear-specific tooth bin representing the gear-tooth to which it pertains.
The method continues with step 1030. In step 1030, a signal average is calculated from all vibration signatures 817(1), 817(2), . . . 817(s), and the calculated average is assigned to (that is, stored in) a common, master tooth bin for each tooth of each gear 415.g.
The next step, step 1035, applies to each tooth bin a convergence check. The convergence check is used to compare the signal average just calculated to the signal average from the previous iteration.
If the signal convergence is below a configured value (meaning the signal has not converged sufficiently to indicate a stable signal value), then more vibration acquisitions are required, entailing a return to step 1005. If in step 1035 the signal convergence is satisfactory (that is, above the configured signal convergence threshold), the averaged vibration data 817 for the tooth bin is accepted.
When averages for all tooth bins are accepted, then no further vibration acquisitions are required to establish a current level of vibration for the planetary gears 415. However, vibration monitoring may be continued, and the method 1000 repeated, to determine any changes in the vibration levels 500 of gear system with multiple sensors (700).
As noted above, with multiple sensors 110.1, convergence time decreases due to increased effective sampling rates for each tooth of each planet gear 415. Therefore, with multiple sensors, reduced scan times may provide adequate signal averaging and convergence, as compared to scan times for single sensor systems.
Exemplary Method for Vibration Sensing with Multiple Sensors
Consistent with methods 800, 900, and 1000 discussed above, another exemplary method for vibration sensing with multiple sensors 805(s) may entail:
(1) From the vibrations sensor 110.s, obtain at the hardware processor 315 of a DAPU 307 the time-continuous vibration sensor signals/data 805 indicative of the sensed vibrations from the planet gears 415.
(2) For the first vibration signal 805(1) of the first vibration sensor 110.1, determining via the hardware processor 315 a series of consecutive time windows when each planet gear 415.g passes within sensing range of the first vibration sensor 110.1; based on this first series of time windows, determining a first group of respective gear data bins 815(1).X.t which each includes vibration sensor data for only one specific planet gear 415.X.
(3) For the second vibration signal 805(2) from the second vibration sensor 110.2, determining via the hardware processor 315 a series of consecutive time windows when each planet gear 415.g passes within sensing range of the second vibration sensor 110.2; based on this second series of time windows, determining a second group of respective gear data bins 815(2).X.t which each includes vibration sensor data for only the one specific planet gear 415.X.
(4) Determine via the hardware processor 315 that a first data bin 815(1).X.1 occurs over during first time interval t; and that a second data bin 815(2).X.2 occurs over during second time interval t+1, where t+1 is immediately successive to t.
(5) Concatenate via the hardware processor the first data bin 815(1).X.1 and the second data bin 815(2).X.2, so that the hardware processor 315 establishes vibration profile 820.X for the planet gear 415.X.
Repeating steps (1) through (5) above for multiple time intervals, and for multiple planet gears 415.g, results in time-extended vibration profiles 820 for each of the planet gears 415.g.
Rotary Element Sensing/Monitoring for Other Mechanical Systems
Embodiments of the present system and method described above entail using multiple vibration sensors 110 to efficiently detect vibrations from multiple rotating components, such as multiple planet gears 115, which revolve within an enclosure 210 such as a gearbox. However, the multiple sensors 105 and the methods 800, 900, 1000 disclosed herein are also applicable, with suitable modifications to other rotary mechanical elements with multiple component, with each component part subject to a shared rotation about an axis, where each such component may benefit from or require real-time sensing or detection. Such mechanical parts may include for example and without limitation blades (in an engine, turbine, or compressor) or a chain around one or more gears or crank shafts.
While vibration sensors may be employed, additional or alternative embodiments of the present system and method may employ other kinds of sensors, such as multiple optical or video sensors, to monitor performance and operational aspects of such time-displaced components.
Legacy Engine or Turbine Blade Monitoring: By way of example,
In the legacy system 1100, each rotating blade 1115 passes a time-of-arrival sensor 1110 at a single sensing point once per rotation 475. The arrival time (t) of any one blade 1115.b is detected. Characteristics of the blade signal 1137 (for example, time changes in static deflection (As) or resonance modes) are calculated based on changes (Δt) in expected, synchronous blade arrival times over multiple blade passes 1150 (that is, multiple complete revolutions of the blades 1115).
Engine or Turbine Blade Monitoring According to the Present System and Method:
In the exemplary system and method 1200, blade passes are sensed at multiple locations around the arc of rotation by multiple, spaced time-of-arrival sensors 1110.r. Signals from each sensor are:
(1) Time-windowed 1212 to isolate each blade 1115 as it passes by each sensor 1110.r, the time windows being based on an approximate range for an expected time of arrival for each blade;
(2) Processed to identify a specific time of arrival of each blade on each rotation;
(3) Resampled and scaled 1215 to account for sensor differences;
(4) Aggregated 1220 to create a combined signal 1225 for each blade across one or more complete revolutions.
Characteristics of the combined blade signal 1125 are then calculated. For example, changes in time of arrival of a given blade over an extended period of time may indicate a potential warping or the blade or a pending failure of the blade attachment.
In a mechanical system with rotating mechanical components (such as planet gears 415, blades 1115, propellers, or chains) which repeatedly traverse a circular path (780), typically but not necessary within a housing (210, the present system and method aggregates the vibration signals relating to the same gear, blade, or chain 415/1115 from multiple sensors 110/1110 placed at distributed fixed sensing points along the arc of motion of the rotating mechanical components. In an epicyclic gearbox 705, for one example, this allows the planet gears 415 to be “tracked” through the rotation, providing benefits for the speed in which a complete scan of each gear 415.g can be completed; this also increases the number of vibration 815/817 samples to reduce the influence of noise in the signal average and providing a consistent load path for the transmission of planet bearing vibration.
Components with spatial translations other than rotation: While the present system and method has been described with respect to rotating elements, other mechanical systems with dynamic variations in the placement of vibration components along some path 475 may benefit from similar application of multiple sensors along a known, repeated path of motion (that is, dynamically, time-varying changes of location of the components relative to the mechanical system as a unit).
For example, a mechanical system may have vibrating components 415/1115 (which may vibrate for example due to a localized rotation or oscillation of the element itself), where the component spatially translates (that is, changes position) along a linear path within the structure of the mechanical system, or along only an arc (rather than a full circle), or along an elliptical path. Other dynamic paths 475 of spatial translation or component displacement within the mechanical system may be envisioned as well.
Suitably distributed placement of multiple sensors 110.s along the path 475 of the component's dynamic displacement may be supported by the methods 800/900/1000/1200 disclosed herein, and other methods disclosed herein, to enable more detailed, more efficient monitoring of vibrations, locations, or other selected, time-variable operational properties of the dynamically moving components. Such methods will typically include at least:
(i) data time-windowing to identify/select data for a common element from different sensors;
(ii) aggregation of data from different sensors for a particular common, dynamically moving element; and
(iii) time averaging of data from a same sensor and/or multiple sensors (as sensed during analogous time windows from different times) for the common, dynamically moving element. The methods may also include resampling of data to reduce data density, and rescaling of data from different sensors to normalize sensor data from different sensors. As above, normalization may be achieved by, for example and without limitation, software processing or adjusting gain on a signal.
Monitoring of continuous components: In an alternative embodiment, the present system and method, employing multiple sensors, may be used to provide improved health monitoring for a continuous component which is subject to spatial translation within a larger system. For example, multiple cameras or optical sensors may monitor the condition(s) of portions of a rapidly moving fan belt or chain (which may in turn move or be moved by multiple stationary gears). Real-time “snap shot” sensing of a fan belt or chain may be employed to maintain a continuous monitor of the entire condition of the fan belt or chain.
The methods disclosed herein thereby reduce the number of revolutions (or other path traversals) required to build up an accurate picture of component health for dynamically moving components. For example, in a planetary gear system 705, increasing the number of sensing locations at which planet gears 415 are tracked around the gearbox 210, fewer revolutions are required to obtain a complete vibration signal for each planet gear 415 (as opposed to systems with a single sensor).
Non-transportation systems: While the present system and method has been described herein with respect to vibration monitoring of rotary elements of a vehicle, many other mechanical and electron mechanical systems employ rotary gear systems and other rotary functional elements as well. For example, wind turbines and other automatic gearboxes have rotary mechanical components including planetary gear systems and blades. All such systems may also benefit from vibration monitoring via the present system and method.
Alternative embodiments, examples, and modifications which would still be encompassed by the disclosure may be made by those skilled in the art, particularly in light of the foregoing teachings. Further, it should be understood that the terminology used to describe the disclosure is intended to be in the nature of words of description rather than of limitation.
Those skilled in the art will also appreciate that various adaptations and modifications of the preferred and alternative embodiments described above can be configured without departing from the scope of the disclosure. Therefore, it is to be understood that, within the scope of the appended claims, the disclosure may be practiced other than as specifically described herein.
The present invention has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.
For example, various aspects of the present invention can be implemented by software, firmware, hardware (or hardware represented by software such, as for example, Verilog or hardware description language instructions), or a combination thereof. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the invention using other computer systems and/or computer architectures.
It should be noted that the simulation, synthesis and/or manufacture of the various embodiments of this invention can be accomplished, in part, through the use of computer readable code, including general programming languages (such as C or C++), hardware description languages (HDL) including Verilog HDL, VHDL, Altera HDL (AHDL) and so on, or other available programming and/or schematic capture tools (such as circuit capture tools).
This computer readable code can be disposed in any known computer usable medium including semiconductor, magnetic disk, optical disk (such as CD-ROM, DVD-ROM) and as a computer data signal embodied in a computer usable (e.g., readable) transmission medium (such as a carrier wave or any other medium including digital, optical, or analog-based medium). As such, the code can be transmitted over communication networks including the Internet and intranets. It is understood that the functions accomplished and/or structure provided by the systems and techniques described above can be represented in a core (such as a GPU core) that is embodied in program code and can be transformed to hardware as part of the production of integrated circuits.
It is to be appreciated that the Detailed Description section (and not the Summary and Abstract sections) is primarily intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the present invention as contemplated by the inventor(s), and thus, are not intended to limit the present invention and the appended claims in any way.
