Fire-fighting vehicles, for example Aircraft Rescue Fire-Fighting (ARFF) vehicles, are specialized vehicles that carry water and foam with them to the scene of an emergency. Most commonly, ARFF vehicles are commissioned for use at an airfield, where the location of an emergency (e.g., an airplane crash, etc.) can vary widely, thereby prompting the transport of fire-fighting materials and personnel to the emergency site. ARFF vehicles are heavy-duty vehicles in nature and are able to respond at high speeds to reach even remote areas of an airfield quickly.
Aircraft fuselages are often configured to partially or completely seal their interior from their surroundings (e.g., to facilitate pressurization of a passenger cabin). Accordingly, conventional fire suppression methods (e.g., spraying water from a distance) can be ineffective when combatting a fire located on the interior of such a fuselage. To facilitate suppression of such fires, some ARFF vehicles are equipped with a penetrating nozzle mounted near an end of a boom assembly. The penetrating nozzle is configured to penetrate the fuselage of an airplane and supply fire suppressant (e.g., foam, water, etc.) to the interior of the fuselage. Due to the round shape of a typical aircraft fuselage, the penetrating nozzle may fail to penetrate the fuselage if aligned at a shallow angle relative to the exterior surface of the fuselage. Conventionally, the boom assembly and the penetrating nozzle are aligned manually by an operator located a distance away from the penetrating nozzle (e.g., in a cabin of the ARFF vehicle). The alignment may occur at night or in rain or snow, obstructing the operator's view of the penetrating nozzle. Additionally, manual operation of such penetrating nozzle requires significant training. Accordingly, operators often experience difficulty properly aligning a penetrating nozzle, causing delays during time-sensitive emergency situations and potential damage to the penetrating nozzle.
One embodiment relates to a fire-fighting vehicle including a chassis, a boom assembly movably coupled to the chassis, a penetrating nozzle coupled to the boom assembly, an actuator configured to move the penetrating nozzle relative to the chassis, a sensor, and a controller configured to receive the sensor data. The penetrating nozzle includes a piercing tip extending along a longitudinal axis and an outlet configured to be selectively fluidly coupled to a supply of fire suppressant. The piercing tip is configured to be selectively repositioned between a first position that is spaced from a surface of an object having an interior cavity and a second position that is within the interior cavity of the object. The outlet is positioned to supply fire suppressant into the interior cavity when the piercing tip is in the second position. The sensor is configured to provide sensor data relating to at least one of a position and an orientation of the piercing tip relative to a surface. The controller is configured to determine an angular orientation of the piercing tip relative to the surface of the object based on the sensor data.
Another embodiment relates to a control system for a fire-fighting vehicle including a first actuator configured to selectively reposition a boom assembly of the vehicle relative to a chassis of the vehicle, a second actuator configured to move a penetrating nozzle relative to the chassis, a sensor configured to provide sensor data relating to at least one of a position and an orientation of the piercing tip relative to a surface of an object, and a controller configured to receive the sensor data. The penetrating nozzle includes a piercing tip extending along a longitudinal axis and an outlet configured to be selectively fluidly coupled to a supply of fire suppressant. The controller is configured to determine an angular orientation of the piercing tip relative to the surface of the object based on the sensor data.
Yet another embodiment relates to a method of facilitating penetration of a penetrating nozzle through a surface of an object, including rotating the penetrating nozzle such that the penetrating nozzle sweeps through an angular range, measuring range data relating to a distance between a piercing tip of the penetrating nozzle and the surface at multiple angular positions throughout the angular range, and determining an angular orientation between the penetrating nozzle and the surface based on the range data.
The invention will become more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, in which:
Before turning to the figures, which illustrate the exemplary embodiments in detail, it should be understood that the present application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.
According to an exemplary embodiment, a fire-fighting vehicle includes a chassis, a boom assembly movably coupled to the chassis, and a penetrating nozzle rotatably coupled to the boom assembly. The penetrating nozzle includes a piercing tip configured to penetrate a surface of an object (e.g., an aircraft fuselage, a building, etc.) and an outlet selectively fluidly coupled to a supply of fire suppressant. The fire-fighting vehicle is configured to penetrate the object with the penetrating nozzle and provide fire suppressant to an interior volume (e.g., a cabin, a room, etc.) of the object to suppress a fire within the interior volume. The fire-fighting vehicle further includes a nozzle alignment system that assists an operator in orienting the penetrating nozzle in an angular orientation relative to the surface where penetration of the surface is likely to succeed. The nozzle alignment system includes an actuator configured to rotate the penetrating nozzle relative to the boom assembly.
When aligning the penetrating nozzle, the actuator first sweeps the penetrating nozzle through a series of angular positions. As the penetrating nozzle rotates, a range sensor coupled to the penetrating nozzle is used to measure range data relating to a distance between the piercing tip and the surface in multiple different angular positions. Using the range data, the nozzle alignment system determines a target range of angular orientations relative to the surface for the penetrating nozzle. The target range includes the angular orientation where the distance between the piercing tip and the surface is smallest, as this is near or coincides with the point where the penetrating nozzle is perpendicular to the surface. Accordingly, with the penetrating nozzle in the target range, the penetrating nozzle is less likely to deflect off of the surface when attempting to penetrate the surface. The nozzle alignment system issues instructions (e.g., through a graphical display) to the operator to facilitate alignment of the penetrating nozzle within the target range (e.g., instructions to rotate the penetrating nozzle up or down using the actuator). After the penetrating nozzle is within the target range, the surface is penetrated, and fire suppressant is supplied to the interior volume.
According to the exemplary embodiment shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
Referring again to
As shown in
As shown in
Referring still to
According to the exemplary embodiment shown in
The controller 310 may be implemented as a general-purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital-signal-processor (DSP), circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. According to the exemplary embodiment shown in
As shown in
As shown in
The range data and angle data may be acquired at multiple different angular positions of the penetrating nozzle 210. The controller 310 may be configured to generate a profile or map of the surface 270 from this range data and angle data. By way of example, the nozzle actuator 218 may rotate the penetrating nozzle 210, and the range sensor 320 and the tip inclinometer 230 may provide range data and angle data corresponding to multiple different angular positions of the penetrating nozzle 210. Using the range data, the angle data, and the geometry of the nozzle assembly 200, the controller 310 may calculate a profile of the surface 270 relative to the location and the orientation of the penetrating nozzle 210 and/or the piercing tip 212. Accordingly, the range data and the angle data relate to a position and an orientation of the penetrating nozzle 210 and/or the piercing tip 212 relative to the surface 270.
As shown in
The systems and methods outlined herein facilitate aligning the penetrating nozzle 210 with the surface 270, despite depth perception challenges (e.g., due to the distance between the penetrating nozzle 210 and the front cabin 30), obstructed views, or environmental challenges (e.g., rain, snow, etc.) operators may face. As shown in
The nozzle alignment system 358 may be configured to interact with the range sensor 320 and/or the tip inclinometer 330 to facilitate aligning the longitudinal axis 276 of the penetrating nozzle 210 within the target range. In some embodiments, the operator controls the boom assembly 100 (e.g., using the turntable actuator 112, the base actuator 132, the upper actuator 152, and/or the telescoping actuator 172, etc.) to bring the penetrating nozzle 210 near the surface 270 prior to alignment. In some embodiments, the operator manually aligns the penetrating nozzle 210 within a target range about a first axis (e.g., a vertical axis). By way of example, the operator may align the penetrating nozzle 210 about a vertical axis by controlling the turntable actuator 112 and using the boom assembly 100 as a visual guide. In such embodiments, the nozzle alignment system 358 is used to align the piercing nozzle within a target range about a second axis (e.g., a horizontal axis). Alternatively, the nozzle alignment system 358 may be used to align the penetrating nozzle 210 about multiple axes. In such embodiments, the nozzle alignment system 358 may be used to align the penetrating nozzle 210 about a first axis (e.g., a vertical axis) prior to aligning the penetrating nozzle 210 about a second axis (e.g., a horizontal axis). Accordingly, in such embodiments, the controller 310 may determine two target ranges of angular orientations relative to the surface 270: one target range defined about the first axis and one target range defined about the second axis.
The controller 310 is configured to control the nozzle actuator 218 to sweep (e.g., rotate up and down, rotate left and right, etc.) the penetrating nozzle 210 over the surface 270 through an angular range (e.g., a range of angular positions). Alternatively, the controller 310 may be configured to control one of the actuators of the boom assembly 100 (e.g., the turntable actuator 112, the upper actuator 152, etc.) to sweep the penetrating nozzle 210. The angular range may be a predetermined range (e.g., from horizontal to 45 degrees above horizontal, etc.), may be set by an operator (e.g., the operator controls actuation of the nozzle actuator 218 using a joystick operatively coupled to the controller 310, etc.), may be based on the range data from the range sensor 320 (e.g., the penetrating nozzle 210 is moved until the range sensor 320 no longer detects the surface 270), or may otherwise be determined. The controller 310 may initiate the sweeping automatically (e.g., when the range sensor 320 detects the surface 270, etc.) and/or in response to a user request from an operator (e.g., when the operator issues a user request through the user interface 350, etc.). While the penetrating nozzle 210 is swept over the surface 270, the range sensor 320 provides range data relating to the distance between the piercing tip 212 and the surface 270 at various angular positions of the penetrating nozzle 210, and the controller 310 stores the range data. The angular positions may be measured relative to gravity, the ground, any component of the fire-fighting vehicle 10 other than the penetrating nozzle 210, or any other reference point. In some embodiments, the tip inclinometer 330 provides angle data relating to the angular position of the penetrating nozzle 210 (e.g., the angle 284, etc.) that corresponds to each range data point, and the controller 310 stores the angle data.
The controller 310 evaluates the range data to locate an angular position of the penetrating nozzle 210 that corresponds to the smallest distance between the piercing tip 212 and the surface 270. By way of example, the controller 310 may search the range data for the smallest distance and use the angle data to determine the corresponding angular position. In situations where the surface 270 is flat or convex, in this angular position the penetrating nozzle 210 is oriented approximately perpendicular to the surface 270. Accordingly, in this angular position, the penetrating nozzle 210 has a known angular orientation relative to the surface 270. After determining the angular orientation of the penetrating nozzle 210 and/or the piercing tip 212 relative to the surface 270 corresponding to one angular position, the controller may use the relative angular displacement of the penetrating nozzle 210 (e.g., as measured using the angle data from the tip inclinometer 330 and/or the boom inclinometer 340) to continuously determine (e.g., track) the angular orientation of the penetrating nozzle 210 and/or the piercing tip 212 relative to the surface 270.
The controller 310 is configured to determine a target range of angular orientations of the penetrating nozzle 210 relative to the surface 270 such that, when oriented within the target range, the penetrating nozzle 210 has an elevated likelihood of successfully penetrating the surface 270. The controller 310 is configured such that the target range includes the orientation in which the penetrating nozzle 210 is approximately perpendicular to the surface. The target range further includes orientations within a predefined range of this orientation (e.g., within two degrees, within 5 degrees, etc.). Accordingly, the controller 310 may correlate the target range of angular orientations of the penetrating nozzle 210 relative to the surface 270 to the angular position of the penetrating nozzle 210 (e.g., measured relative to gravity, the ground, any component of the fire-fighting vehicle 10 other than the penetrating nozzle 210, or any other reference point).
After determining the target range, the operator may provide an input to engage the nozzle actuator 218 and rotate the penetrating nozzle 210 into the target range in preparation for penetrating the surface 270. In some embodiments, the nozzle actuator 218 is controlled by the controller 310 using data from the tip inclinometer 330 to determine when the penetrating nozzle 210 is in the target range (e.g., the penetrating nozzle 210 is rotated until the angle 284 measured by the tip inclinometer 330 is determined by the controller 310 to correspond with an angular orientation within the target range, etc.). In other embodiments, the nozzle actuator 218 is controlled by the controller 310 using data from the range sensor 320 to determine when the penetrating nozzle 210 is in the target range (e.g., the penetrating nozzle 210 is rotated until the distance measured by the range sensor 320 is determined by the controller 310 to correspond with an angular orientation within the target range, etc.). By way of example, the controller 310 may determine that the penetrating nozzle 210 is in the target range when the distance measured by the range sensor 320 is within a predetermined range (e.g., within 5 inches, within 1 inch, within 0.5 inches, etc.) of the smallest distance measured by the range sensor 320 while sweeping the penetrating nozzle 210.
In some embodiments, the nozzle actuator 218 is controlled manually by the operator (e.g., through manual interaction with a valve of a hydraulic system, through interaction with a joystick operatively coupled to the controller 310, etc.). The user interface 350 may provide information to the operator regarding proposed or suggested movements (e.g., prompts the operator to sweep the penetrating nozzle 210, provides the operator with the current angular position relative to the target range, prompts the operator to rotate the penetrating nozzle 210 up or down, etc.). In other embodiments, the nozzle alignment system 358 is automated (e.g., controlled by the controller 310). By way of example, an operator may position the penetrating nozzle 210 along (e.g., nearby, adjacent, etc.) the surface 270, and the controller 310 may automatically (a) sweep the penetrating nozzle 210 (e.g., using the nozzle actuator 218 or the upper actuator 152) (b) determine the target range of angular orientations using range data and angle data and (c) engage various actuators to position the piercing tip 212 within the target range. In other embodiments, the range sensor 320 itself provides a signal that sweeps horizontally and/or vertically, the range sensor 320 itself includes an actuator that sweeps a sensor thereof horizontally and/or vertically, and/or the range sensor 320 otherwise maps the surface 270 so as to reduce or eliminate movement of the penetrating nozzle 210 prior to piercing.
The nozzle alignment system 358 may use angle data to determine an amount of force applied by the piercing tip 212 and whether the amount of force is greater than a minimum amount required to pierce the object. By way of example, a minimum force may be required to pierce the piercing tip 212 through a sheet of a certain material having a certain thickness. The controller 310 may determine the angle 290 using angle data from the tip inclinometer 330 and the boom inclinometer 340, respectively, or from another angle sensor. In some embodiments, the controller 310 is configured to calculate one or both of a piercing force gauge in the extension direction (e.g., parallel to the longitudinal axis 280) and a piercing force gauge in the raise/lower direction (e.g., perpendicular to the longitudinal axis 280) using the angle 290. The piercing force gauge in the extension direction represents the component of a force applied parallel to the longitudinal axis 280 (e.g., a force from the telescoping actuator 172) that acts along the longitudinal axis 276. The piercing force gauge in the extension direction may be determined using the cosine of the angle 290. By way of example, when the piercing force gauge in the extension direction is 0.8, 80 percent of a force applied parallel to the longitudinal axis 280 acts along the longitudinal axis 276. The piercing force gauge in the raise/lower direction represents the component of a force applied perpendicular to the longitudinal axis 280 (e.g., a resultant force from the moment applied to the telescoping boom section 170 by the base actuator 132 and/or the upper actuator 152) that acts along the longitudinal axis 276. The piercing force gauge in the raise/lower direction may be determined using the sine of the angle 290. By way of example, when the piercing force gauge in the raise/lower direction is 0.8, 80 percent of a force applied perpendicular to the longitudinal axis 280 acts along the longitudinal axis 276.
Accordingly, the piercing force gauge may be used to determine an amount of force that will be applied by the piercing tip 212 using a certain actuator based on the angle data from the angle sensor(s). If the force gauge in a certain direction is above or below a threshold value (e.g., a threshold value based on the material properties of the surface 270), the nozzle alignment system 358 may indicate to the operator that the boom assembly 100 should be repositioned before piercing can occur, or that a particular actuator should be used when piercing the surface 270. The force gauge may additionally be used to orient the penetrating nozzle 210 to maximize the force applied to the piercing tip 212 by a particular actuator.
Referring to
Referring again to
Referring again to
Referring to
The angle register 376 cooperates with the tip indicator 372 to indicate to the operator the orientation of the penetrating nozzle 210 and/or the piercing tip 212 relative to the target range of orientations. In some embodiments, the angle register 376 includes angle markings (e.g., at 0, 90, and −90 degrees from horizontal). As shown in
As shown in
Referring to
As utilized herein, the terms “approximately,” “about,” “substantially,” and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the invention as recited in the appended claims.
It should be noted that the terms “exemplary” and “example” as used herein to describe various embodiments is intended to indicate that such embodiments are possible examples, representations, and/or illustrations of possible embodiments (and such term is not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
For purposes of this disclosure, the term “coupled” means the joining of two members directly or indirectly to one another. Such joining may be stationary in nature (e.g., permanent, etc.) or moveable in nature (e.g., removable, releasable, etc.). Such joining may allow for the flow of electricity, electrical signals, or other types of signals or communication between the two members. Such joining may be achieved with the two members or the two members and any additional intermediate members being integrally formed as a single unitary body with one another or with the two members or the two members and any additional intermediate members being attached to one another. Such joining may be permanent in nature or alternatively may be removable or releasable in nature.
References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below,” “between,” etc.) are merely used to describe the orientation of various elements in the figures. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, Z, X and Y, X and Z, Y and Z, or X, Y, and Z (i.e., any combination of X, Y, and Z). Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y, and at least one of Z to each be present, unless otherwise indicated.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
The construction and arrangements of the systems and methods, as shown in the various exemplary embodiments, are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.) without materially departing from the novel teachings and advantages of the subject matter described herein. Some elements shown as integrally formed may be constructed of multiple parts or elements. The position of elements may be reversed or otherwise varied. The nature or number of discrete elements or positions may be altered or varied. Although the figures may show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. The order or sequence of any process, logical algorithm, or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes and omissions may also be made in the design, operating conditions and arrangement of the various exemplary embodiments without departing from the scope of the present invention. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps. It should be noted that the elements and/or assemblies of the components described herein may be constructed from any of a wide variety of materials that provide sufficient strength or durability, in any of a wide variety of colors, textures, and combinations. Accordingly, all such modifications are intended to be included within the scope of the present inventions. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the preferred and other exemplary embodiments without departing from scope of the present disclosure or from the spirit of the appended claim.
This application claims the benefit of U.S. Provisional Application No. 62/456,440, filed Feb. 8, 2017, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
1001863 | Kirkwood | Aug 1911 | A |
1376467 | Simmon | May 1921 | A |
1463569 | Bathrick | Jul 1923 | A |
1835132 | Anania | Dec 1931 | A |
2614743 | Arps | Oct 1952 | A |
2632577 | Sacco | Mar 1953 | A |
2916997 | Terrie | Dec 1959 | A |
2993650 | Badberg | Jul 1961 | A |
2997242 | Grosholz | Aug 1961 | A |
3010533 | Ross | Nov 1961 | A |
3083790 | McAfee et al. | Apr 1963 | A |
3188966 | Tetlow | Jun 1965 | A |
3346052 | Moore et al. | Oct 1967 | A |
3500961 | Eberhardt et al. | Mar 1970 | A |
3550146 | Eberle | Dec 1970 | A |
3590948 | Milner, Jr. | Jul 1971 | A |
3675721 | Davidson et al. | Jul 1972 | A |
3715001 | Wilson | Feb 1973 | A |
3726308 | Eberhardt | Apr 1973 | A |
3770062 | Riggs | Nov 1973 | A |
3789869 | Morris | Feb 1974 | A |
4037664 | Gibson | Jul 1977 | A |
4059170 | Young | Nov 1977 | A |
4084522 | Younger | Apr 1978 | A |
4094381 | Wilkerson | Jun 1978 | A |
4103757 | McVaugh | Aug 1978 | A |
4118151 | Murakami et al. | Oct 1978 | A |
4157733 | Ewers et al. | Jun 1979 | A |
4160492 | Johnston | Jul 1979 | A |
4185924 | Graham | Jan 1980 | A |
4212908 | Hendy et al. | Jul 1980 | A |
4317504 | Artaud et al. | Mar 1982 | A |
4337830 | Eberhardt | Jul 1982 | A |
4373600 | Buschbom et al. | Feb 1983 | A |
4410045 | Whitman | Oct 1983 | A |
4456093 | Finley et al. | Jun 1984 | A |
4556200 | Shoemaker | Dec 1985 | A |
4563124 | Eskew | Jan 1986 | A |
4570973 | Ewers et al. | Feb 1986 | A |
4586743 | Edwards et al. | May 1986 | A |
4587862 | Hoffman | May 1986 | A |
4811804 | Ewers et al. | Mar 1989 | A |
4852690 | Salmi | Aug 1989 | A |
4945780 | Bosma | Aug 1990 | A |
4998982 | Arnold et al. | Mar 1991 | A |
5004156 | Montanier | Apr 1991 | A |
5021917 | Pike et al. | Jun 1991 | A |
5113946 | Cooper | May 1992 | A |
5145014 | Eberhardt | Sep 1992 | A |
5158614 | Takeuchi | Oct 1992 | A |
5174383 | Haugen et al. | Dec 1992 | A |
5211245 | Relyea et al. | May 1993 | A |
5232052 | Arvidson et al. | Aug 1993 | A |
5301756 | Relyea et al. | Apr 1994 | A |
5313548 | Arvidson et al. | May 1994 | A |
5326232 | McDonnel et al. | Jul 1994 | A |
5346334 | Einaru et al. | Sep 1994 | A |
5368317 | McCombs et al. | Nov 1994 | A |
5389031 | Sharpe et al. | Feb 1995 | A |
5467827 | McLoughlin | Nov 1995 | A |
5494112 | Arvidson et al. | Feb 1996 | A |
5538185 | Rabitsch et al. | Jul 1996 | A |
5538274 | Schmitz et al. | Jul 1996 | A |
5553673 | Hackman | Sep 1996 | A |
5617696 | Young | Apr 1997 | A |
5746396 | Thorton-Trump | May 1998 | A |
5765644 | Arvidson et al. | Jun 1998 | A |
5785372 | Glatzmeier et al. | Jul 1998 | A |
5788158 | Relyea | Aug 1998 | A |
5820150 | Archer et al. | Oct 1998 | A |
5826663 | Sundholm | Oct 1998 | A |
5839664 | Relyea | Nov 1998 | A |
5881818 | Lee et al. | Mar 1999 | A |
RE36196 | Eberhardt | Apr 1999 | E |
5897123 | Cherney et al. | Apr 1999 | A |
5899276 | Relyea et al. | May 1999 | A |
5909780 | De Andrade | Jun 1999 | A |
6006841 | Hunke | Dec 1999 | A |
6009953 | Laskaris et al. | Jan 2000 | A |
6105984 | Schmitz et al. | Aug 2000 | A |
6155351 | Breedlove et al. | Dec 2000 | A |
6161643 | Bober et al. | Dec 2000 | A |
6193007 | Lie | Feb 2001 | B1 |
6220532 | Manon et al. | Apr 2001 | B1 |
6289995 | Fuller | Sep 2001 | B1 |
6394534 | Dean | May 2002 | B1 |
6421593 | Kempen et al. | Jul 2002 | B1 |
6516914 | Andersen et al. | Feb 2003 | B1 |
6520494 | Andersen et al. | Feb 2003 | B1 |
6553290 | Pillar | Apr 2003 | B1 |
6561718 | Archer et al. | May 2003 | B1 |
6588286 | Kudo et al. | Jul 2003 | B1 |
6598702 | McGillewie et al. | Jul 2003 | B1 |
6615675 | Kudo et al. | Sep 2003 | B1 |
6695328 | Cope | Feb 2004 | B2 |
6715373 | Kudo et al. | Apr 2004 | B2 |
6739174 | Kudo et al. | May 2004 | B2 |
6755258 | Hunke et al. | Jun 2004 | B1 |
6755259 | Peltola | Jun 2004 | B2 |
6757597 | Yakes et al. | Jun 2004 | B2 |
6764085 | Anderson | Jul 2004 | B1 |
6769733 | Seksaria et al. | Aug 2004 | B2 |
6782965 | Sztykiel et al. | Aug 2004 | B2 |
6811161 | Anderson | Nov 2004 | B1 |
6860332 | Archer et al. | Mar 2005 | B1 |
6882917 | Pillar et al. | Apr 2005 | B2 |
6883815 | Archer | Apr 2005 | B2 |
6885920 | Yakes et al. | Apr 2005 | B2 |
6909944 | Pillar et al. | Jun 2005 | B2 |
6922615 | Pillar et al. | Jul 2005 | B2 |
6973768 | Samejima et al. | Dec 2005 | B2 |
6976688 | Archer et al. | Dec 2005 | B2 |
6993421 | Pillar et al. | Jan 2006 | B2 |
7006902 | Archer et al. | Feb 2006 | B2 |
7024296 | Squires et al. | Apr 2006 | B2 |
7055613 | Bissen | Jun 2006 | B1 |
7055880 | Archer | Jun 2006 | B2 |
7072745 | Pillar et al. | Jul 2006 | B2 |
7080694 | Boyle | Jul 2006 | B2 |
7100741 | Wissler et al. | Sep 2006 | B2 |
7107129 | Rowe et al. | Sep 2006 | B2 |
7127331 | Pillar et al. | Oct 2006 | B2 |
7137456 | Moses | Nov 2006 | B2 |
7143641 | Palazzolo et al. | Dec 2006 | B2 |
7162332 | Pillar et al. | Jan 2007 | B2 |
7164977 | Yakes et al. | Jan 2007 | B2 |
7184862 | Pillar et al. | Feb 2007 | B2 |
7184866 | Squires et al. | Feb 2007 | B2 |
7201255 | Kreikemeier | Apr 2007 | B1 |
7213872 | Ronacher et al. | May 2007 | B2 |
7234534 | Froland et al. | Jun 2007 | B2 |
7254468 | Pillar et al. | Aug 2007 | B2 |
7274976 | Rowe et al. | Sep 2007 | B2 |
7277782 | Yakes et al. | Oct 2007 | B2 |
7290457 | Kudo et al. | Nov 2007 | B2 |
7293478 | Kudo et al. | Nov 2007 | B2 |
7302320 | Nasr et al. | Nov 2007 | B2 |
7308968 | Denison | Dec 2007 | B2 |
7331586 | Trinkner et al. | Feb 2008 | B2 |
7379797 | Nasr et al. | May 2008 | B2 |
7387348 | Archer et al. | Jun 2008 | B2 |
7389826 | Linsmeier et al. | Jun 2008 | B2 |
7392122 | Pillar et al. | Jun 2008 | B2 |
7412307 | Pillar et al. | Aug 2008 | B2 |
7439711 | Bolton | Oct 2008 | B2 |
7451028 | Pillar et al. | Nov 2008 | B2 |
7513315 | Boyle et al. | Apr 2009 | B2 |
7522979 | Pillar | Apr 2009 | B2 |
7530403 | Cano | May 2009 | B2 |
7555369 | Pillar et al. | Jun 2009 | B2 |
7611075 | Relyea et al. | Nov 2009 | B2 |
7689332 | Yakes et al. | Mar 2010 | B2 |
7703543 | Waters et al. | Apr 2010 | B2 |
7711460 | Yakes et al. | May 2010 | B2 |
7715962 | Rowe et al. | May 2010 | B2 |
7725225 | Pillar et al. | May 2010 | B2 |
7729831 | Pillar et al. | Jun 2010 | B2 |
7756621 | Pillar et al. | Jul 2010 | B2 |
7784554 | Grady et al. | Aug 2010 | B2 |
7792618 | Quigley et al. | Sep 2010 | B2 |
7792949 | Tewari et al. | Sep 2010 | B2 |
7835838 | Pillar et al. | Nov 2010 | B2 |
7848857 | Nasr et al. | Dec 2010 | B2 |
7874373 | Morrow et al. | Jan 2011 | B2 |
8000850 | Nasr et al. | Aug 2011 | B2 |
8095247 | Pillar et al. | Jan 2012 | B2 |
8103366 | Gamble et al. | Jan 2012 | B2 |
8201656 | Archer et al. | Jun 2012 | B2 |
8215241 | Garneau et al. | Jul 2012 | B2 |
8376719 | Grady et al. | Feb 2013 | B2 |
8413764 | Cohen et al. | Apr 2013 | B1 |
8555625 | Trinkner et al. | Oct 2013 | B2 |
8739892 | Moore et al. | Jun 2014 | B2 |
8789614 | Hosfield | Jul 2014 | B2 |
8801393 | Crabtree et al. | Aug 2014 | B2 |
8807233 | Peltola | Aug 2014 | B2 |
8839902 | Archer et al. | Sep 2014 | B1 |
9008913 | Sears et al. | Apr 2015 | B1 |
9061168 | Mikota | Jun 2015 | B2 |
9061169 | Linsmeier | Jun 2015 | B2 |
9315210 | Sears et al. | Apr 2016 | B2 |
9493921 | Amin et al. | Nov 2016 | B2 |
20020117345 | Sztykiel et al. | Aug 2002 | A1 |
20030158635 | Pillar et al. | Aug 2003 | A1 |
20030163228 | Pillar et al. | Aug 2003 | A1 |
20030195680 | Pillar | Oct 2003 | A1 |
20030230414 | Peltola et al. | Dec 2003 | A1 |
20040020262 | Kudo et al. | Feb 2004 | A1 |
20040133319 | Pillar et al. | Jul 2004 | A1 |
20040155426 | Wen et al. | Aug 2004 | A1 |
20050099885 | Tamminga | May 2005 | A1 |
20050196269 | Racer et al. | Sep 2005 | A1 |
20050234622 | Pillar et al. | Oct 2005 | A1 |
20050236226 | Salmi et al. | Oct 2005 | A1 |
20050247524 | Wissler et al. | Nov 2005 | A1 |
20060021764 | Archer et al. | Feb 2006 | A1 |
20060022001 | Linsmeier et al. | Feb 2006 | A1 |
20060032701 | Linsmeier et al. | Feb 2006 | A1 |
20060032702 | Linsmeier et al. | Feb 2006 | A1 |
20060070845 | Crookston | Apr 2006 | A1 |
20060086566 | Linsmeier et al. | Apr 2006 | A1 |
20060213672 | Mohr | Sep 2006 | A1 |
20060266532 | Moskun | Nov 2006 | A1 |
20070187434 | Schrafel | Aug 2007 | A1 |
20070205053 | Isham et al. | Sep 2007 | A1 |
20070246230 | Roberts | Oct 2007 | A1 |
20070256842 | Mohr | Nov 2007 | A1 |
20070284156 | Grady et al. | Dec 2007 | A1 |
20070286736 | Grady et al. | Dec 2007 | A1 |
20080035201 | Roberts | Feb 2008 | A1 |
20080059030 | Quigley et al. | Mar 2008 | A1 |
20080099212 | Do | May 2008 | A1 |
20080099213 | Morrow et al. | May 2008 | A1 |
20080103651 | Pillar et al. | May 2008 | A1 |
20080215700 | Pillar et al. | Sep 2008 | A1 |
20080236846 | Gamble et al. | Oct 2008 | A1 |
20080271901 | Decker | Nov 2008 | A1 |
20090101436 | Burman et al. | Apr 2009 | A1 |
20090218108 | Cano | Sep 2009 | A1 |
20100038098 | Groonwald et al. | Feb 2010 | A1 |
20100044059 | Mikota | Feb 2010 | A1 |
20100065286 | Hosfield | Mar 2010 | A1 |
20100200328 | Savard et al. | Aug 2010 | A1 |
20110064591 | McLoughlin et al. | Mar 2011 | A1 |
20120132445 | Mallon | May 2012 | A1 |
20120193109 | Moore et al. | Aug 2012 | A1 |
20140048353 | Ellis | Feb 2014 | A1 |
20140238704 | Moore et al. | Aug 2014 | A1 |
20140334169 | Ewert | Nov 2014 | A1 |
20150096835 | Hong et al. | Apr 2015 | A1 |
20150120152 | Lauterjung et al. | Apr 2015 | A1 |
20150246251 | Mikota et al. | Sep 2015 | A1 |
20150273252 | Lenz et al. | Oct 2015 | A1 |
20150273253 | Lenz et al. | Oct 2015 | A1 |
Number | Date | Country |
---|---|---|
2478228 | Feb 2006 | CA |
203050481 | Jul 2013 | CN |
11 86 334 | Jan 1965 | DE |
36 20 603 | Jan 1987 | DE |
36 40 944 | Jun 1988 | DE |
0 244 668 | Nov 1987 | EP |
0 685 382 | Dec 1995 | EP |
1 371 391 | Dec 2009 | EP |
1471914 | Mar 1967 | FR |
2380176 | Sep 1978 | FR |
2 168 015 | Jun 1986 | GB |
H11-239625 | Sep 1999 | JP |
2000-107313 | Apr 2000 | JP |
2008-297701 | Dec 2008 | JP |
20110040306 | Apr 2011 | KR |
101297477 | Aug 2013 | KR |
WO-0176912 | Oct 2001 | WO |
WO-03049987 | Jun 2003 | WO |
WO-2007140179 | Dec 2007 | WO |
Entry |
---|
International Search Report and Written Opinion regarding Application No. PCT/US2018/017216, dated Apr. 24, 2018, 15 pps. |
Number | Date | Country | |
---|---|---|---|
20180221694 A1 | Aug 2018 | US |
Number | Date | Country | |
---|---|---|---|
62456440 | Feb 2017 | US |