Method and apparatus for wireless blasting

Information

  • Patent Grant
  • 11009331
  • Patent Number
    11,009,331
  • Date Filed
    Friday, August 16, 2019
    4 years ago
  • Date Issued
    Tuesday, May 18, 2021
    3 years ago
Abstract
Systems, methods, blasting machines and wireless bridge units are presented for wireless blasting for safe firing of detonators under control of a remote wireless master controller in which the blasting machine is connected by cabling to the wireless bridge unit and power to a firing circuit of the blasting machine is remotely controlled via the bridge unit. The bridge unit selectively provides first and second firing messages to the blasting machine contingent upon acknowledgment of safe receipt of the first firing message by the blasting machine, and the blasting machine fires the connected detonators only if the first and second firing messages are correctly received from the bridge unit. A wireless slave blasting machine is disclosed, including a wireless transceiver for communicating with a remote wireless master controller, which fires the connected detonators only if first and second firing messages are wirelessly received from the master controller.
Description
TECHNICAL FIELD

The present disclosure relates generally to the field of blasting technology, and particularly involves methods and apparatus for wireless remote blasting.


BACKGROUND

In blasting operations, detonators and explosives are buried in the ground, for example, in holes (e.g., bore holes) drilled into rock formations, etc., and the detonators are wired for external access to blasting machines that provide electrical firing signaling to initiate detonation of explosives. Wireless blasting involves use of a remotely located master controller and a local slave wireless device connected to a blasting machine at the blast site, with the blasting machine being wired to an array of detonators. In wireless blasting systems, no wiring or lead lines are connected between the detonator array and the master controller, and the master controller can be positioned a significant distance from the blast site, such as 1-5 miles in one example. The blasting machine is normally turned on together with the slave controller as the operator walks from the blast area to the master controller site some distance away, where the blast sequence includes power up, verification and/or programming of delay times, arming and finally issuance of a “fire” command. The blasting machine provides sufficient energy and voltage to charge the firing capacitors in the detonators, and initiates the actual detonator firing in response to the fire command. During the firing phase, upon operator input at the master controller, a fire command is transferred from the master to the slave which then issues the final command to the blasting machine in order to fire the detonator array. Accordingly, improved techniques, systems and apparatus are desirable for improved safety in wireless remote blasting.


SUMMARY

Various aspects of the present disclosure are now summarized to facilitate a basic understanding of the disclosure, wherein this summary is not an extensive overview of the disclosure, and is intended neither to identify certain elements of the disclosure, nor to delineate the scope thereof. Instead, the primary purpose of this summary is to present some concepts of the disclosure in a simplified form prior to the more detailed description that is presented hereinafter.


The disclosure relates to systems, methods and apparatus for electronic blasting, and provides improved blasting machine and slave bridge unit operation to facilitate improved safety and controllability compared with conventional wireless blasting. The disclosed apparatus provides remote blasting machine turn on and/or turnoff as well as reliable fire command issuance procedures using multiple fire command messages to facilitate improved safety and immunity from spurious noise. In certain implementations, the firing circuitry of the blasting machine is not powered up even though the branch lines or a lead line may be connected with the array of detonators, with the local slave bridge unit controlling the firing circuit power condition to apply power only if the bridge unit/master control unit wireless link is established. The fire command initiation process provides two or more fire commands issued by the slave bridge unit and properly received by the blasting machine in order to actually fire the control detonators. These devices and techniques thus advantageously facilitate safe blasting using remote wireless master control.


One or more aspects of the present disclosure relate to methods for wireless detonator blasting, including wirelessly receiving a wireless fire command message from a master controller at a wireless enabled bridge unit coupled with a blasting machine, and sending a first command message from the bridge unit to the blasting machine. The methods further include selectively sending a second fire command message from the bridge unit to the blasting machine in response to receipt of a fire command acknowledgment message from the blasting machine or after a predetermined period of time has elapsed since the first fire command message was sent. In certain embodiments, the second fire command message is sent to the blasting machine only if the fire command acknowledgment message is received within a predetermined time after the first fire command message was sent. In this manner, the method advantageously mitigates or avoids the possibility of a blasting machine inadvertently firing detonators based on receipt of noise or other spurious signaling, thereby facilitating safe, predictable remote wireless blasting. In addition, certain embodiments facilitate safe controlled operation during detonator verification and/or arming using multiple messages from the bridge unit and corresponding acknowledgment from the blasting machine. In various embodiments, moreover, the bridge unit is used to selectively enable or disable the firing circuit of the blasting machine. This, in turn, facilitates manual connection of the blasting machine to the detonator array and connection of the slave bridge unit while ensuring that the firing circuit of the blasting machine is unpowered. Moreover, the ability to thereafter turn off power to the blasting machine firing circuit via the RF-enabled bridge unit advantageously allows blasting personnel to visit the blasting site for troubleshooting while ensuring that the blasting machine is incapable of firing any detonators.


Further aspects of the disclosure provide a bridge unit for remote wireless operation of a blasting machine. The bridge unit includes a communications interface for connection to a blasting machine, as well as a wireless transceiver for interfacing with a master control unit, and at least one processor. The processor is programmed to receive a wireless fire command message from the master controller, to send a first fire command message to the blasting machine, and to selectively send a second fire command message to the blasting machine responsive to receipt of a fire command acknowledgment message from the blasting machine. In certain implementations, the bridge unit sends the second fire command message only if the acknowledgment of the first message is received from the blasting machine within a predetermined time. The bridge unit may be configured in certain embodiments to issue multiple command messages to the blasting machine for verification and/or arming operations, with the second or subsequent messages being sent only if proper acknowledgment is received from the blasting machine to ensure that these commands are initiated only when needed. Moreover, certain embodiments of the bridge unit involve the processor being programmed to selectively enable or disable the blasting machine firing circuit.


Still other aspects of the present disclosure involve a blasting machine with a communications interface for communicating with a connected bridge unit, as well as a firing circuit and at least one processor programmed to receive and acknowledge a first fire command from the bridge unit, and to selectively fire one or more connected detonators in response to receiving a second fire command message. In certain implementations, the detonators are fired only if the second fire command message is received from the bridge unit within a predetermined time period. The blasting machine processor in certain embodiments is programmed to verify the fire command messages and issue acknowledgment of the first message only if verified as correct and/or fire the detonators only if the second fire command is verified as correct. In certain embodiments, moreover, the blasting machine firing circuit can be selectively enabled or disabled by a connected bridge unit.


Further aspects of the disclosure provide an integrated wireless slave blasting machine having a wireless communications interface for communicating with a wireless master controller, as well as at least one processor and a firing circuit. The wireless slave blasting machine processor is programmed to fire connected detonators only if first and second firing messages are wirelessly received from the master controller. In addition, the wireless blasting machine is operative in certain embodiments to send a fire command acknowledgment message to the master controller via the wireless transceiver in response to receiving the first fire command message, and/or to selectively enable or disable the firing circuit in response to wirelessly receiving a remote turn on or remote turn off command from the master controller.


In accordance with further aspects of the disclosure, blasting machines, remote master controllers and methods are provided for preventing remote out of sync conditions in a wireless detonator blasting operation, in which the blasting machine sends the master controller a data packet with a data designation number and refrains from processing a received message command until the master controller sends back the data designation number.





BRIEF DESCRIPTION OF THE DRAWINGS

The following description and drawings set forth certain illustrative implementations of the disclosure in detail, which are indicative of several exemplary ways in which the various principles of the disclosure may be carried out. The illustrated examples, however, are not exhaustive of the many possible embodiments of the disclosure. Other objects, advantages and novel features of the disclosure will be set forth in the following detailed description of the disclosure when considered in conjunction with the drawings, in which:



FIG. 1 is a simplified system diagram illustrating a wireless blasting system for remotely firing an array of detonators connected to a blasting machine at a blast site, including a remotely located wireless master controller and a wireless slave bridge unit connected to the blasting machine in accordance with one or more aspects of the present disclosure;



FIGS. 2 and 3 are schematic diagrams illustrating first and second embodiments of the remote turn on and remote turn off features of the blasting machine and slave bridge unit;



FIGS. 4A-4C provide a flow diagram illustrating an exemplary process for operating the slave bridge unit;



FIG. 5 is a signal flow diagram illustrating operation of the master controller, slave bridge unit and blasting machine in the system of FIG. 1;



FIGS. 6A-6B provide a flow diagram illustrating an exemplary process for operating the blasting machine;



FIG. 7 is a simplified system diagram illustrating an alternate wireless blasting system with a wireless slave blasting machine in accordance with further aspects of the present disclosure; and



FIG. 8 is a flow diagram illustrating a data designation process to prevent remote out-of-sync conditions between the blasting machine and the remote master controller.





DETAILED DESCRIPTION

Referring now to the figures, several embodiments or implementations of the present disclosure are hereinafter described in conjunction with the drawings, wherein like reference numerals are used to refer to like elements throughout, and wherein the various features are not necessarily drawn to scale.



FIG. 1 shows a wireless blasting system with a blasting machine 2 is one a wireless-enabled slave bridge unit 20 located at or near a blast site B that includes a detonator array A with a number of electronic detonators D connected by wires to a single pair of lead lines LL. As shown in FIG. 1, the lead lines LL are connected to a firing circuit 4 of the blasting machine 2, although various operational aspects of the disclosed methods and systems contemplate that the lead lines LL may be connected to the firing circuit 4 only at certain points in a blasting process. A key 3 may be associated with the blasting machine 2 for security purposes, for example, to ensure that the blasting machine 2 operates only once a proper key 3 is installed. In other embodiments, password protection may be provided in the blasting machine 2, requiring an operator to enter a proper password to enable blasting machine operation, and the key 3 may be omitted. The blasting machine 2 further includes a microprocessor and associated electronic memory 6 operatively connected to the firing circuit 4 and to a communications interface 8. As is known, the blasting machine 2 may be housed in a suitable environmental enclosure capable of withstanding the rigors and environmental conditions of blasting sites, and the blasting machine 2 in certain implementations includes an internal battery 10 for operation without requiring connection of external power lines. Other embodiments are possible in which the blasting machine 2 does not include an internal power source, and operates exclusively using power supplied from a connected slave bridge unit 20.


The slave bridge unit 20 is really housed in a suitable enclosure and operated by a battery 30, and may have an associated key 23 for operating the unit 20. The slave bridge unit 20 may alternatively or in combination be password-protected, requiring user entry of a password to enable bridge unit operation, and the key 23 may be omitted. One or both of the blasting machine 2 and the slave bridge unit 20 may also include various user interface features (not shown) allowing an operator to perform various operations by pressing buttons, and may provide a display screen or other output means by which an operator can receive data or messages. The slave bridge unit 20 includes a communications interface 28 allowing communication between the slave bridge unit 20 and the blasting machine 2 connected by a communications cable 12. In addition, the slave bridge unit 20 includes a microprocessor and associated electronic memory 26 that is operatively connected to the communications interface 28 as well as to a wireless transceiver 22 having an associated RF antenna 32. Moreover, the illustrated bridge unit 20 includes a power control circuit 24 operative to selectively enable or disable the firing circuit 4 of the blasting machine 2 by any suitable means, including without limitation provision of firing circuit power 14 and/or by providing a power gating control signal 14, 14a in order to control the provision of power to the firing circuit 4, examples of which are further illustrated in FIGS. 2 and 3. Also, the slave bridge unit 20 includes an internal battery 30 allowing field operation.


The processors 6, 26 may be any suitable electronic processing device including without limitation a microprocessor, microcontroller, DSP, programmable logic, etc. and/or combinations thereof, which performs various operations by executing program code such as software, firmware, microcode, etc. The devices 2, 20 each include an electronic memory operatively associated with the corresponding processors 6, 26 to store program code and/or data, including computer executable instructions and data to perform the various functionality associated with blasting machine operation as is known as well as communications tasks and the various function set forth herein. The memory of the devices 2, 20 may be any suitable form of electronic memory, including without limitation RAM, EEPROM, flash, SD, a multimedia card, etc.


As further shown in FIG. 1, a master controller apparatus 40 includes a microprocessor and electronic memory 46 operatively coupled with a user interface 44 and a wireless transceiver 42 with an associated RF antenna 48. In operation, the master controller 40 and the slave bridge unit 20 establish a radio-frequency (RF) or other wireless communications link 34 via the transceivers 42, 22 and the corresponding antennas 48, 32, thus allowing the master controller 40 to 42 operate the slave bridge unit 20 and hence the blasting machine 2 at a significant distance away from the blast site 8, such as several miles in certain implementations. In this manner, the remote positioning of the master controller 40 facilitates operator safety during blasting operations, with the various concepts of the present disclosure further facilitating operator safety as detailed further below.



Fig. 2 illustrates one possible implementation of the blasting machine 2 and the slave bridge unit 20 facilitating control of the application of electrical power to the blasting machine firing circuit 4 by the slave bridge unit 20. In various situations, the disclosed blasting machine 2 and bridge apparatus 20 advantageously allow remote turn on and/or remote turn off of the firing circuit power, thereby enhancing personal safety for blasting sites. In this implementation, a relay 16 is provided in the blasting machine 2 for selectively connecting power from the blasting machine battery 10 to the firing circuit 4 according to a switching control signal 14 provided by the power control circuit 24 of the slave bridge unit 20. The control signal 14 can be provided from the bridge unit 20 to the blasting machine 2 by a variety of means, including a dedicated control line in a communications cable 12, 14 connecting the units 20 and 2. In another possible embodiment, the power control circuit 24 is implemented in programming of the processor 26, with the processor 26 providing a command message via the communications interfaces 28, 8, with the blasting machine processor 6 controlling operation of the relay 16 accordingly, wherein the switching control signaling 14 is provided via such messaging between the units 20, 2. Other possible implementations may be used by which the slave bridge unit 20 selectively controls the application of power to, or removal of power from, the firing circuit 4 to selectively enable or disable the firing circuit 4 of the blasting machine 2. In this manner, the power control circuit 24 operates under control of the slave bridge unit processor 26 to selectively provide the control signal 14 to either apply power to the blasting machine firing circuit 4 or to ensure that the firing circuit 4 is unpowered.



FIG. 3 illustrates another non-limiting embodiment in which a dedicated power line is provided in cabling connecting the blasting machine 2 with the bridge unit 20, including a single wire or pair of wires 14, where a single cable may also include the communications line or lines 12, or separate cabling can be provided. The slave bridge unit 20 in FIG. 3 includes an on-board relay 18 operative to selectively apply power from the bridge unit battery 30 to the firing circuit 4 of the blasting machine 2 according to a switching control signal 14a from the power control circuit 24. As in the implementation of FIG. 2, the power control circuit 24 may be a separate circuit operated under control of the bridge unit processor 26, or may be implemented via programming of the processor 26 to selectively provide the switching control signal 14a to operate the relay 18 to thereby selectively apply power from the battery 30 to the firing circuit 4, or to ensure that the firing circuit 4 is unpowered according to the state of the switching control signal 14a.


In the illustrated implementations, a single contact relay 16, 18 may be used, for example, to connect a positive DC power line to the firing circuit 4, or a relay 16, 18 may be used having multiple contacts, for instance, to selectively connect or disconnect multiple power lines to or from the firing circuit 4. In one possible implementation, the bridge unit processor 26 performs remote turn on of the firing circuit power by asserting the control signal 14 after connection of the bridge unit 20 to the blasting machine 2 only after a verified communications link 34 is established between the master control unit 40 and the slave bridge unit 20. In another possible implementation, the processor 26 of the bridge unit 20 is programmed to enable the firing circuit 4 via the power control circuit 24 and the signaling 14, 14a only upon receipt of a command message from the master controller 40 instructing the bridge unit 20 to apply power to the firing circuit 4. This operation advantageously allows blasting operators to leave the blasting site B before any powered circuit is connected to the detonators D. In addition, the provision of the power control circuitry 24 and selective enabling/disabling of the firing circuit 4 by the slave bridge unit 20 also facilitates remote turn off, whereby the slave bridge unit processor 26 is programmed in certain embodiments to remove power from the firing circuit 4 via the control signaling or messaging 14, 14a if the wireless link 34 between the slave bridge unit 20 and the master controller 40 is lost or if the master controller 40 sends a message via the wireless link 34 to the bridge unit 20 with a command to turn off power to the firing circuit 4.


Referring again to FIG. 1, the master controller 40 and the slave bridge unit 20 implement two-way communications via the wireless link 34, by which the master controller 40 remotely controls the operation of the blasting machine 2 with all blasting machine functions and messages being displayed or echoed on the user interface 44 of the master controller 40. In this regard, the blasting machine 2 may have a local user interface (not shown), and may be operable in a local control mode according to a keypad and other means for receiving user inputs locally, with connection to the slave bridge unit 20 placing the blasting machine 2 into a remote control mode for operation according to the master controller 40 via the wireless link 34 and the connection to the slave bridge unit 20. In certain embodiments, echoing of the local blasting machine user interface prompts and displayed information via the bridge unit 20 to the master controller 40 enables the remote operator at the master controller 40 to safely see remotely whatever is on the blasting machine display from a distance. In addition, the system implemented by the interconnection and operation of the master controller 40, the bridge unit 20 and the blasting machine 2 performs various operations using multiple messages with acknowledgment and verification as detailed below in order to further facilitate safe and predictable operation of a remote wireless blasting system.


Referring now to FIGS. 4A-6B, exemplary methods 100, 200 are illustrated for implementing a remote wireless blasting operation, including a method 100 in FIGS. 4A-4C showing exemplary operation of the slave bridge unit 20, and a method 200 in FIGS. 6A and 6B for operating the blasting machine 2, along with a signal flow diagram 150 in FIG. 5 showing various interconnections and messaging between the master controller 40, slave bridge unit 20, blasting machine 2 and detonator array A. While the exemplary methods 100 and 200 are illustrated and described hereinafter in the form of a series of acts or events, it will be appreciated that the various methods of the disclosure are not limited by the illustrated ordering of such acts or events. In this regard, except as specifically provided hereinafter, some acts or events may occur in different order and/or concurrently with other acts or events apart from those illustrated and described herein in accordance with the disclosure. It is further noted that not all illustrated steps may be required to implement a process or method in accordance with the present disclosure, and one or more such acts may be combined. The illustrated methods 100, 200 and other methods of the disclosure may be implemented in hardware, processor-executed software, or combinations thereof, such as in the exemplary blasting machine 2 and slave bridge unit 20 described herein, and may be embodied in the form of computer executable instructions stored in a non-transitory computer readable medium such as the memories associated with the processors 6 and 26.


In one possible remote wireless blasting procedure, electronic detonators D are programmed and logged using one or more loggers (not shown), with detonator delay times being programmed during the logging process, or such delay times may have been previously programmed. Thereafter, the detonators D are connected to each of their individual branch wires, and a logger may be used to verify that each detonator D in a specific branch is properly electrically connected. Detonator data may then be transferred from the logger to the blasting machine 2, such as by electrical connection of the longer (not shown) to the communications interface 8 for transfer of the detonator data. Branch wires may then be connected to the lead line wiring LL, where the lead line wiring LL may extend some difference from the detonator array A to the position of the blasting machine 2.


The process 100 begins at 102 in FIG. 4A begins in one example with connection of the lead lines LL from the detonator array A to the blasting machine 2 while the blasting machine 2 and the firing circuit 4 thereof remain unpowered. On-site blasting personnel may then insert and turn the power keys 3 and 23 of the blasting machine 2 and the slave bridge unit 20, but the firing circuit 4 of the blasting machine 2 initially remains off. The slave bridge unit 20 is connected to the blasting machine 2 at 104, with the bridge unit 20 maintaining the unpowered condition of the blasting machine firing circuit 4. At 106 in FIG. 4A, the slave bridge unit 20 is powered up while still maintaining the blasting machine firing circuit 4 in the unpowered state. The blasting site B may then be cleared of personnel and/or extra equipment.


At 108, the bridge unit 20 and the master controller 40 establish a wireless communications link 34 with the blasting machine firing circuit 4 still unpowered under control of the power control circuit 24 implemented in the slave bridge unit 20. At 110 in FIG. 4A, the slave bridge unit enables the blasting machine firing circuit power after linking with the master controller 40. This is schematically illustrated in the signal flow diagram 150 of FIG. 5, in which the slave bridge unit 20 provides suitable signaling and/or messaging 14, 14A to the blasting machine 2 under control of the slave bridge unit processor 26 to initiate application of electrical power to the firing circuit 4, for example, using the relay circuit control techniques shown in FIG. 2 or 3 above. In one possible embodiment, the bridge unit 20 sends a command message “BM0” or “BM1” to the blasting machine 2, which may be acknowledged by the blasting machine 2 in certain implementations. The slave bridge unit processor 26 determines at 112 in FIG. 4A whether the wireless link 34 has been lost, or alternatively whether a message has been received from the master controller 40 including a command or instruction to turn off the blasting machine 2. If so (YES at 112), the method 100 continues to 114 where the slave bridge unit 20 disables the blasting machine firing circuit power via the power control circuit 24 and any associated signaling or messaging 14, 14a, and one or more remedial measures may be undertaken at 116. For instance, if the wireless link 34 was lost, blasting personnel may safely visit the blasting site B, if necessary, to service the slave bridge unit 20 or take other actions to reestablish the communications link 34. Alternatively, if the remote turn off feature was initiated by receipt of a message from the master controller 40, the blasting personnel can attend to other situations at the blast site B with the assurance that the firing circuit 4 of the blasting machine 2 has been disabled. Once the remedial measures have been undertaken at 116, blasting personnel can determine that it is now safe to again turn on the blasting machine at 118, with the process 100 returning to 110 for the slave bridge unit 20 to enable the blasting machine firing circuit power after again establishing the communications link with the master controller 40, and optionally after receiving a specific command from the master controller 40 to again power up the blasting machine firing circuit 4.


Once it is determined at 112 that the wireless link 34 is operational and no turn off messaging has been received from the master controller 40 (NO at 112 in FIG. 4A), the process 100 proceeds to 120 in FIG. 4B with the slave bridge unit 20 wirelessly receiving a verify command message from the master controller 40 (shown as a wireless verify command message 152 in FIG. 5) and sending a verify command message to the blasting machine 2 (message 154 in FIG. 5). In one possible embodiment, the blasting machine 2 receives the verify command 154 and performs one or more verification operations, while the operator at the master controller 40 may monitor the user interface 44 to verify proper interconnection of the various detonators D. In the illustrated implementation, moreover, the slave bridge unit 20 and the blasting machine 2 further ensure proper receipt of a verify command with the blasting machine 2 using two or more verify commands from the bridge unit 20 an acknowledgment by the blasting machine 2 as shown. In this case, the bridge unit 20 waits for an acknowledgment message from the blasting machine 2 at 122 in FIG. 4B. If no acknowledgment is received (NO at 122), the slave bridge unit 20 notifies the master controller 40 at 124, and the process 100 returns to await another verify command from the master controller 40 at 120. If the blasting machine 2 provides an acknowledgment (message 156 in FIG. 5) within a predetermined time (YES at 122 in FIG. 4B), the slave bridge unit 20 sends a second verify command (message 158 in FIG. 5) to the blasting machine 2 at 126 in FIG. 4B. The verify process, in this regard, may be individualized for specific detonators D, and the multiple command messaging with acknowledgment shown at 120-126 in FIG. 4B may be implemented at the beginning of a verification process, with further single messaging being used to verify individual detonators D. The slave bridge unit 20, moreover, may receive one or more notification messages at 128 in FIG. 4B from the blasting machine 2 indicating any missing detonators or other verify process status indicators, which can then be relayed via the wireless link 34 to the remote master controller 40 for display to an operator via the user interface 44.


At 130 in FIG. 4B, the slave bridge unit 20 wirelessly receives a charge or “ARM” command message (message 162 in FIG. 5) from the master controller 40, and sends an arm command to the blasting machine 2 (message 164 in FIG. 5). In certain embodiments, the blasting machine 2 responds to the first arm command and charges firing capacitors of connected detonators D, and may perform calibration processing as well, and reports any arming or calibration errors to the slave bridge unit 20, which are then forwarded to the master controller 40 for display to an operator via the user interface 44. In the illustrated implementation, the bridge unit 20 waits for an acknowledgment at 132 in FIG. 4B of the arm command from the blasting machine 2, and if no such acknowledgment is received within a predetermined time (NO at 132), notifies the master controller 40 and returns to 132 await receipt of another charge or arm command from the master controller 40. Otherwise (YES at 132), once the acknowledgment from the blasting machine 2 has been received within the predetermined time (acknowledgment message 166 in FIG. 5), the slave bridge unit 20 sends a second arm command (message 168 in FIG. 5) to the blasting machine 2 at 136 in FIG. 4B, and receives one or more notification messages at 138 from the blasting machine 2 indicating any arming our calibration errors, which are then forwarded via the wireless link 34 to the master controller 40.


Continuing in FIG. 4C, the slave bridge unit 20 wirelessly receives a fire command at 140 from the master controller 40 (message 172 in FIG. 5), and sends a fire command to the blasting machine 2 (command message 174 in FIG. 5). At 142, the bridge unit 20 waits for an acknowledgment of the fire command from the blasting machine 2, and if no acknowledgment is received within a predetermined time (NO at 142) the bridge unit 20 notifies the master controller 40 at 144, and the process returns for remedial measures at 116 in FIG. 4A. If the slave bridge unit 20 receives a proper acknowledgment of the fire command (YES at 142 in FIG. 4C, acknowledgment message 176 in FIG. 5), the slave bridge unit 20 sends a second fire command (message 178 in FIG. 5) at 146 to complete the blasting process 100. As seen in FIG. 5, moreover, this causes the blasting machine 2 in certain embodiments to fire the detonator array A at 179. In other embodiments, the slave bridge unit 20 need not implement a timeout function, and may instead continue to await receipt of a second or subsequent fire command at 142 in FIG. 4C. In certain embodiments, moreover, the blasting machine 2 may be configured to implement a predetermined timeout for receipt of the second command message 178, and if not received from the slave bridge unit 20 in the predetermined period of time, may issue a message to the slave bridge unit 20 indicating that the fire process, if intended, needs to be restarted. In addition, although illustrated and described above in the context of a dual message process with intervening acknowledgment, more than 2 fire command messages may be required, with intervening acknowledgments from the blasting machine 2, in order to fire the detonators D at 179 in FIG. 5.


In this manner, if the initial fire command message 174 was not properly received by the blasting machine 2, or if the communications interface 12 between the blasting machine 2 in the slave bridge unit 20 is inoperative or intermittent, the bridge unit 20 will not send a second or subsequent fire command to the blasting machine 2. Moreover, as discussed further below in connection with FIGS. 6A and 6B, the blasting machine 2 is adapted to await a second or subsequent fire command before actually firing the detonators D via the firing circuit 4. Consequently, the wireless blasting system of the present disclosure advantageously employs multiple fire command messaging between the blasting machine 2 and the slave bridge unit 20 in order to ensure that the blasting machine 2 only acts upon intended firing commands. In this regard, should the blasting machine 2 inadvertently receive a different command or spurious noise via of the communications interface 8 which is interpreted as being a single fire command, without the slave bridge unit 20 actually intending to cause the detonators D to be fired, no unintended firing will be initiated by the blasting machine 2. Consequently, this aspect of the present disclosure facilitates safe controlled detonation of the detonator array A and presents a significant robust system architecture providing an advance over conventional wireless blasting systems which could be susceptible to misinterpretation of single firing command messages or signals.


Referring also to FIGS. 6A and 6B, the process 200 illustrates exemplary operation of the blasting machine 2 in conjunction with the above-described bridge unit operation in FIGS. 4A-4C and 5. At 202 in FIG. 6A, the blasting machine firing circuit power is enabled by the slave bridge unit (signaling 14, 14a in FIG. 5). At 204, the blasting machine 2 receives a verify command message (message 154 in FIG. 5) and sends a verify command acknowledgment in certain embodiments to the slave bridge unit 20 (acknowledgment 156 in FIG. 5). As mentioned previously, certain embodiments of the blasting machine 2 and slave bridge unit 20 may provide for single messaging for verify operation, with or without acknowledgment. In the illustrated example, the blasting machine 2 waits at 206 in FIG. 6A for a second verify command to be received from the slave bridge unit 20, and if no second or subsequent verify command is received (NO at 206), the blasting machine 2 notifies the slave bridge unit 20 at 208, and returns to 204 as described above. If the second verify command (message 158 in FIG. 5) is received within a predetermined time (YES at 206), the blasting machine 2 performs one or more verification operations at 210 and may notify the slave bridge unit 20 of any missing (unverified) detonators D. In certain embodiments, moreover, the blasting machine 2 performs a remote out of sync prevention process 400 as further described below in connection with FIG. 8 to selectively perform the verification operation or operations at 210 after verifying synchronization with the master controller 40.


At 212 in FIG. 6A, the blasting machine 2 receives an arm command message (message 164 in FIG. 5) from the slave bridge unit 20, and sends an arm command acknowledgment (message 166 in FIG. 5) to the slave bridge unit 20. In certain embodiments, the blasting machine 2 may be programmed to initiate detonator arming in response to the first arm command message 164, with or without sending any acknowledgment message 176. In the illustrated implementation, moreover, the blasting machine 2 waits at 214 in FIG. 6A for receipt of a second arm command from the slave bridge unit 20 (arm command 168 in FIG. 5), and may implement a timeout period in certain embodiments. If a second arm command is not received within the optional predetermined time period (NO at 214), the blasting machine 2 notifies the slave bridge unit at 216 and returns to await a first verify command message at 212 as described above. Otherwise (YES at 214), the machine 2 charges the firing capacitors of the connected detonators D and performs calibration at 218, and may notify the slave bridge unit 20 of any arming or calibration errors. As discussed further below in connection with FIG. 8, certain embodiments of the blasting machine 2 implement a remote out of sync operation before charging the firing capacitors and performing other operations at 218.


The process 200 then continues at 220 in FIG. 6B, where the blasting machine 2 receives a fire command message (message 174 in FIG. 5) from the bridge unit 20, and performs a cyclical redundancy check (CRC) evaluation at 222 to determine whether the received fire command message 174 is correct. If there is a CRC error (YES at 222), the blasting machine 2 notifies the slave bridge unit 20 at 224 that an erroneous message has been received, and returns to await retransmission of any valid fire command message at 220. If there was no CRC error in the first fire command message (NO at 222), the blasting machine sends a fire command acknowledgment (message 176 and FIG. 5) to the slave bridge unit 20, and waits for receipt of a second or subsequent fire command message from the bridge unit 20 at 226. If a second or subsequent fire command message (e.g., second fire command message 178 in FIG. 5) is received at 228 from the slave bridge unit 20 (YES at 228), a CRC error check is performed at 230 by the blasting machine 2. If no CRC error occurs in the second received fire command message (NO at 230), the blasting machine fires the detonators D at 232 to complete the blasting process. In certain embodiments, moreover, even if the second fire command message is properly received without CRC errors, the blasting machine 2 verifies synchronization with the remote master controller 40 via a process 400 in FIG. 8 before firing the detonators at 232, as described further below.


The firing of the detonators at 232 can be by any suitable operation of the blasting machine using the firing circuit 4. For example, where electronic detonators D are used, the blasting machine 2 may issue a fire command at 232 in FIG. 6B along the lead lines LL to cause the detonators D to fire according to any programmed delay times in the detonators D (also shown at 179 in FIG. 5). As previously discussed, moreover, although the operation in FIG. 6B illustrates usage of first and second fire commands 174 and 178 with an intervening acknowledgment message 176 by the blasting machine 2, other implementations are possible in which more than two fire command messages must be received before the blasting machine 2 will fire the detonators at 232. Further, while the blasting machine 2 implements a timeout period in the determination at 228 in FIG. 6B, other implementations are possible in which no timeout period is used, and the blasting machine 2 will fire the detonators D in response to receipt of the second (or subsequent) fire command message 178. In cases where a CRC error occurs at 222 or 230, moreover, the blasting machine 2 will notify the slave bridge unit 20 at 224, and will itself treat the received fire command message(s) as invalid or as an automatic abort command, and thus the blasting machine 2 will not cause the detonators D to be fired.



FIG. 7 illustrates another wireless blasting system with a wireless slave blasting machine 300 according to further aspects of the present disclosure. In this case, the blasting machine 300 is equipped with a wireless transceiver 22 and associated wireless antenna 32 for wireless (e.g., RF) communications 34 with the master controller 40. In addition, the wireless slave blasting machine 300 in this example includes a firing circuit 4 for connection to the lead lines LL of the detonator array A, and may be selectively operable by way of a key 3, and/or the unit 300 may be password-protected in certain implementations. The wireless slave blasting machine 300 in general implements the functions and features of the slave bridge unit 20 and the blasting machine 2 of FIG. 1, and includes a power control circuit 24 operative to selectively enable or disable provision of power to a firing circuit 4 connected to one or more detonators D as shown, for example, using a power control circuit 24 and a relay 16 as described above. In addition, the blasting machine 300 includes one or more batteries 30 to power various internal circuitry and the firing circuit 4 by way of a power control relay 16 as described above.


The processor 26 of the wireless slave blasting machine 300 in certain embodiments is programmed to receive a first wireless fire command message (e.g., like command 172 above) from the master controller 40 via the wireless transceiver 22 using the wireless connection 34, as well as to receive a second wireless fire command message from the master controller 40, and to selectively fire one or more connected detonators D via the firing circuit 4 only after receiving both the first and second fire command message from the master controller 40 via the wireless transceiver 22. In certain embodiments, the wireless blasting machine 300 will only fire the detonators D if the first and second fire command messages are received from the master controller 40 within a predetermined time period. In certain embodiments, moreover, the wireless blasting machine 300 will send a fire command acknowledgment message to the master controller 40 via the wireless transceiver 22 in response to receiving the first fire command message 172. Moreover, the wireless slave blasting machine 300 in certain embodiments implements remote turn on/off, with the processor 26 being programmed to selectively enable or disable the firing circuit 4 (e.g., via the power control circuit 24 providing a relay control signal 14 to the relay 16 in FIG. 7) in response to wirelessly receiving a remote turn on or remote turn off command from the master controller 40.


In certain related aspects, the master controller 40, and the processor 46 thereof, may be programmed to receive an input from an operator (e.g., via the user interface 44) for initiation of a firing operation, and to automatically wirelessly transmit first and second firing command messages via the wireless link 34 to the wireless slave blasting machine 300 of FIG. 7. In one implementation, the master controller 40 sends the second firing command message within a predetermined time following transmission of the first firing command message. In certain implementations, moreover, the master controller 40 will selectively transmit the second firing command message only in response to receipt of a firing command acknowledgment message received through the wireless link 34 from the wireless slave blasting machine 300.


In accordance with further aspects of the disclosure, the slave bridge unit 20 and blasting machine 2 (e.g., FIG. 1) and/or the wireless slave blasting machine (FIG. 7) implement remote turn on/turnoff operation according to commands from the master controller 40, independent of specific fire command operation of these devices. In this manner, the operator at the master controller 40 may selectively disable the firing circuit 4 through transmission of a disable message from the master controller 40 to either a wireless slave blasting machine 300 as set forth in FIG. 7 or to a wireless slave bridge unit 20 as seen in FIG. 1. Also, the operator may use the master controller 40 to wirelessly send an enable command or message via the wireless link 34 to either the wireless slave blasting machine 300 or to a slave bridge unit 20 in order to remotely enable (e.g., power) the corresponding firing circuit 4.


In accordance with further aspects of the present disclosure, the multiple fire command message concepts (and/or multiple verify and multiple arm message concepts), alone or in further combination with the associated predetermined times and/or acknowledgment message concepts, may be implemented in association with multiple slave bridge units 20 and/or multiple wireless enabled slave blasting machines 300 or combinations thereof. In this manner, a single master controller 40 can wirelessly control multiple bridge units 20 and/or multiple wireless blasting machines 300 with respect to detonator firing operations and other associated tasks such as verification and/or arming. Moreover, the remote turn on/turnoff features of the illustrated and described master controller 40, wireless slave blasting machine 300 and slave bridge units 20 can be implemented in systems having a single master controller 40 operatively coupled via corresponding wireless links 34 to multiple slave blasting machines 300, or multiple slave bridge units 20, or combinations thereof, by which the master controller 40 may selectively enable or disable multiple firing circuits 4. Referring now to FIG. 8, certain embodiments of the blasting machine 2, 300, any included slave bridge unit 20, and the master controller 40 are configured to implement a data designation process 400 to prevent one or more operations if remote out-of-sync conditions are detected between the blasting machine 2, 300 and the remote master controller 40. In particular, when the blasting machine 2, 300 receives a second verify, arm or fire command (e.g., at 206 or 214 in FIG. 6A or at 228, 230 in FIG. 6B) or any other event occurs at 402 in FIG. 8 for which the blasting machine 2, 300 updates its display, the blasting machine 2, 300 sends a wireless display data packet or other message to the master controller 40 at 404, either directly as per the blasting machine 300 in FIG. 7, or indirectly through an associated slave bridge unit 20 as shown in FIG. 1 above. This first out of sync prevention message at 404 includes the updated display data for updating the remote master controller 40, as well as a data designator command, such as a command bite, and a data designation number determined by the blasting machine 2, 300. In addition, the blasting machine 2, 300 starts a timer at 404 to establish a predetermined time following transmission of the first message.


If the blasting machine 2, 300 and the master controller 40 are synchronized properly with a functioning direct or indirect wireless communications link established, the master controller 40 receives the first message and processes the display data to update its own display, and sends a wireless “Data Designator” response message back to the blasting machine 2, 300 directly or through any associated slave bridge unit 20. The response message includes the data designation number originally transmitted from the blasting machine 2, 300 at 404 in FIG. 8. At 406, the blasting machine 2, 300 determines whether the data designator response message was received before expiration of the timer started at 404. If so (YES at 406), the blasting machine 2, 300 determines at 408 whether the response message includes the correct data designation number provided with the display data packet at 404. If so (YES at 408), the blasting machine 2, 300 processes the received verify, arm or fire command (e.g., at 210 or 218 in FIG. 6A, or at 232 in FIG. 6B above). Thereafter, the process 400 returns to 402 as described above. If the blasting machine 2, 300 does not receive any data designator response before the timer expires (NO at 406), the blasting machine at 416 refrains from processing the requested verify, arm or fire command, and may optionally shut down in a safe mode.


If, however, the blasting machine 2, 300 receives a data designator response before expiration of the timer (YES at 406) but the response does not include the correct data designation number (NO at 408), the blasting machine 2, 300 determines at 412 whether a predetermined maximum number of retransmissions of the display data packet has occurred. If not (NO at 412), the blasting machine 2, 300 sends another display data packet with the data designator command bite and a new data designation number at 414 to the master controller 40 (e.g., via a slave bridge unit 20 or directly), and returns to 406 to await a response from the master controller 40. If the blasting machine 2, 300 receives a response to the second message including the new data designator number (YES at 408), the requested verify, arm or fire command is processed at 410. In addition, this retransmission attempt processing at 406, 408, 412 and 414 can repeat until the predetermined maximum number of retries has occurred (YES at 412) or until the timer expires without receipt of a data designator response message including the most recent data designation number (NO at 416), in which case the blasting machine 2, 300 refrain from processing the verify, arm or fire command at 416, and may optionally shut down in the safe mode. In this manner, the master controller 40 and the blasting machine 2, 300 are ensured to be synchronized before performance of critical operations by the blasting machine 2, 300, and the display data presented to an operator at the remote master controller 40 correctly reflects the display data at the blasting machine 2, 300.


The above examples are merely illustrative of several possible embodiments of various aspects of the present disclosure, wherein equivalent alterations and/or modifications will occur to others skilled in the art upon reading and understanding this specification and the annexed drawings. In particular regard to the various functions performed by the above described components (assemblies, devices, systems, circuits, and the like), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component, such as hardware, processor-executed software and/or firmware, or combinations thereof, which performs the specified function of the described component (i.e., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the illustrated implementations of the disclosure. In addition, although a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Also, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in the detailed description and/or in the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”

Claims
  • 1. A method for wireless detonator blasting, comprising: using a wireless enabled bridge unit coupled with a blasting machine via a communications cable, wirelessly receiving a wireless fire command message from a master controller;using the wireless enabled bridge unit, sending a first fire command message to the blasting machine via the communications cable;using the wireless enabled bridge unit, sending a second fire command message to the blasting machine via the communications cable within a predetermined time after sending the first fire command message to the blasting machine; andusing the blasting machine, selectively firing at least one connected detonator only if both the first and second fire command messages are received from the wireless enabled bridge unit within the predetermined time.
  • 2. The method of claim 1, further comprising: using the wireless enabled bridge unit, selectively enabling or disabling a firing circuit of the blasting machine in response to wirelessly receiving a remote turn on or remote turn off command from a master controller.
  • 3. The method of claim 1, further comprising: using the wireless enabled bridge unit, selectively enabling or disabling a firing circuit of the blasting machine in response to wirelessly receiving a remote turn on or remote turn off command from a master controller.
  • 4. A method for wireless detonator blasting, comprising: using a wireless blasting machine having a wireless transceiver operative to communicate with a remote master controller and a firing circuit operative when enabled and powered to fire at least one connected detonator, wirelessly receiving a wireless first fire command message from a master controller;using the wireless blasting machine, wirelessly receiving a wireless second fire command message from the master controller; andusing the wireless blasting machine, selectively firing the at least one connected detonator only if both the first and second fire command message are received from the master controller within a predetermined time.
  • 5. A method for wireless detonator blasting, comprising: using a blasting machine having a direct or indirect wireless communications link with a remote master controller and a firing circuit operative when enabled and powered to fire at least one connected detonator, directly or indirectly receiving a wireless verify, arm or fire command message from the remote master controller;using the blasting machine directly or indirectly sending a wireless first message to the remote master controller in response to receiving the wireless verify, arm or fire command message, the first message including display data, a data designator command, and a data designation number;using the blasting machine:selectively processing the verify, arm or fire command message if the blasting machine directly or indirectly receives, from the remote master controller, a wireless data designator response message including the data designation number sent in the first message within a predetermined time after sending the wireless first message, andselectively refraining from processing the verify, arm or fire command message if the blasting machine does not directly or indirectly receive, from the remote master controller, a wireless data designator response message including the data designation number sent in the first message within the predetermined time after sending the wireless first message.
  • 6. The method of claim 5, comprising: in response to receiving a wireless data designator response message that does not include the data designation number sent in the first message within the predetermined time after sending the wireless first message, using the blasting machine, directly or indirectly sending a wireless second message to the remote master controller, the second message including the display data, a data designator command, and a different second data designation number;selectively processing the verify, arm or fire command message if the blasting machine directly or indirectly receives, from the remote master controller, a second wireless data designator response message including the second data designation number sent in the second message within the predetermined time after sending the wireless first message, andselectively refraining from processing the verify, arm or fire command message if the blasting machine does not directly or indirectly receive, from the remote master controller, a wireless data designator response message including the first or second data designations within the predetermined time after sending the wireless first message. age.
REFERENCE TO RELATED APPLICATION

This application is a divisional of currently pending U.S. patent application Ser. No. 15/100,347, filed on May 31, 2016 which claims priority to, and the benefit of, U.S. Provisional Patent Application No. 61/910,654, filed on Dec. 2, 2013, entitled METHOD AND APPARATUS FOR WIRELESS BLASTING, which applications are hereby incorporated by reference.

US Referenced Citations (393)
Number Name Date Kind
3987729 Andrews et al. Oct 1976 A
4005631 Kaiser et al. Feb 1977 A
4037538 Andrews et al. Jul 1977 A
4320704 Gawlick et al. Mar 1982 A
4495851 Koerner et al. Jan 1985 A
4576093 Snyder Mar 1986 A
4777880 Beattie et al. Oct 1988 A
4884506 Guerreri Dec 1989 A
5038682 Marsden Aug 1991 A
5069131 Kennedy et al. Dec 1991 A
5159149 Marsden Oct 1992 A
5214236 Murphy et al. May 1993 A
5295438 Hill et al. Mar 1994 A
5431073 Gregory Jul 1995 A
5546862 Schabdach Aug 1996 A
5769034 Zilka et al. Jun 1998 A
6233430 Helferich May 2001 B1
6253061 Helferich Jun 2001 B1
6259892 Helferich Jul 2001 B1
6321690 Zilka et al. Nov 2001 B1
6422145 Gavrilovic et al. Jul 2002 B1
6459360 Helferich Oct 2002 B1
6462646 Helferich Oct 2002 B2
6533316 Breed et al. Mar 2003 B2
6557636 Cernocky et al. May 2003 B2
6564866 Clark et al. May 2003 B2
6565119 Fogle, Jr. May 2003 B2
6584907 Boucher et al. Jul 2003 B2
6604468 Zilka et al. Aug 2003 B2
6618237 Eddy et al. Sep 2003 B2
6644201 Zilka et al. Nov 2003 B2
6648097 Tite et al. Nov 2003 B2
6648367 Breed et al. Nov 2003 B2
6696291 Helferich Feb 2004 B2
6733036 Breed et al. May 2004 B2
6755156 Zilka et al. Jun 2004 B1
6837310 Martin Jan 2005 B2
6860206 Rudakevych et al. Mar 2005 B1
6889610 Boucher et al. May 2005 B2
6905135 Breed Jun 2005 B2
6928030 Chamberlain et al. Aug 2005 B2
6938689 Farrant et al. Sep 2005 B2
6941870 McClure et al. Sep 2005 B2
6955217 Clark et al. Oct 2005 B2
6962202 Hell et al. Nov 2005 B2
6988449 Teowee et al. Jan 2006 B2
7003304 Helferich Feb 2006 B1
7039428 Helferich May 2006 B1
7103510 Moolman et al. Sep 2006 B2
7143696 Rudakevych et al. Dec 2006 B2
7155241 Helferich Dec 2006 B2
7232001 Hakki et al. Jun 2007 B2
7242951 Helferich Jul 2007 B2
7273102 Sheffield Sep 2007 B2
7277715 Starr et al. Oct 2007 B2
7278658 Boucher et al. Oct 2007 B2
7280838 Helferich Oct 2007 B2
7284489 Bell et al. Oct 2007 B2
7284601 Bell et al. Oct 2007 B2
7322416 Burris, II et al. Jan 2008 B2
7327550 Meyer et al. Feb 2008 B2
7347144 Teowee et al. Mar 2008 B2
7347145 Teowee et al. Mar 2008 B2
7347278 Lerche et al. Mar 2008 B2
7350448 Bell et al. Apr 2008 B2
7363967 Burris, II et al. Apr 2008 B2
7370513 Meyer et al. May 2008 B2
7370583 Hallin et al. May 2008 B2
7376432 Helferich May 2008 B2
7383882 Lerche et al. Jun 2008 B2
7395760 Zilka et al. Jul 2008 B2
7403787 Helferich Jul 2008 B2
7436937 Clawson Oct 2008 B2
7437985 Gal Oct 2008 B2
7451700 Land Nov 2008 B1
7461580 Bell et al. Dec 2008 B2
7464647 Teowee et al. Dec 2008 B2
7478680 Sridharan et al. Jan 2009 B2
7479624 Morris Jan 2009 B2
7481453 Breed Jan 2009 B2
7493859 Russell Feb 2009 B2
7499716 Helferich Mar 2009 B2
7520323 Lerche et al. Apr 2009 B2
7568429 Hummel et al. Aug 2009 B2
7577756 Teowee et al. Aug 2009 B2
7581413 Block et al. Sep 2009 B2
7594471 Koekemoer et al. Sep 2009 B2
7597047 Doyle et al. Oct 2009 B2
7617775 Teowee Nov 2009 B2
7648164 Breed Jan 2010 B2
7650841 McClure et al. Jan 2010 B2
7661348 Murello Feb 2010 B2
7676973 Powers Mar 2010 B1
7681500 Teowee Mar 2010 B2
7710820 Clark May 2010 B2
7712405 Toycen et al. May 2010 B2
7740273 Breed Jun 2010 B2
7744122 Breed Jun 2010 B2
7762580 Breed Jul 2010 B2
7774115 Breed Aug 2010 B2
7778006 Stewart et al. Aug 2010 B2
7784389 Mardirossian Aug 2010 B2
7791858 Hummel et al. Sep 2010 B2
7802509 Wall Sep 2010 B2
7810421 Hiza et al. Oct 2010 B2
7810430 Chan et al. Oct 2010 B2
7814833 Land Oct 2010 B1
7814970 Strickland Oct 2010 B2
7823508 Anderson et al. Nov 2010 B2
7832762 Breed Nov 2010 B2
7835757 Helferich Nov 2010 B2
7843314 Helferich Nov 2010 B2
7848078 Hummel et al. Dec 2010 B2
7861924 Block et al. Jan 2011 B1
7866544 Block et al. Jan 2011 B1
7874250 Veneruso Jan 2011 B2
7882921 Hakki et al. Feb 2011 B2
7882926 Fullerton Feb 2011 B2
7883008 Miller et al. Feb 2011 B1
7886866 Fullerton Feb 2011 B2
7911760 Lownds Mar 2011 B2
7922491 Jones et al. Apr 2011 B2
7929270 Hummel et al. Apr 2011 B2
7930923 Patel et al. Apr 2011 B2
7934453 Moore May 2011 B2
7946209 Schneider et al. May 2011 B2
7946480 Miller et al. May 2011 B2
7954703 Miller et al. Jun 2011 B2
7958824 Stewart Jun 2011 B2
7975592 Bell et al. Jul 2011 B2
7975612 Teowee et al. Jul 2011 B2
7975613 Labuschagne et al. Jul 2011 B2
7975774 Akcasu Jul 2011 B2
7989742 Bredy Aug 2011 B2
7990286 Shankwitz et al. Aug 2011 B2
7992777 Block et al. Aug 2011 B1
8011928 Schaeffer et al. Sep 2011 B1
8020491 Simon Sep 2011 B2
8022839 Goodman Sep 2011 B2
8035255 Kurs et al. Oct 2011 B2
8069789 Hummel et al. Dec 2011 B2
8084725 Dryer Dec 2011 B1
8087956 Nakayama Jan 2012 B2
8106539 Schatz et al. Jan 2012 B2
8107601 Helferich Jan 2012 B2
8109191 Rudakevych et al. Feb 2012 B1
8116741 Helferich Feb 2012 B2
8122830 Moore Feb 2012 B2
8127983 Block et al. Mar 2012 B1
8134450 Helferich Mar 2012 B2
8134822 Ballantine et al. Mar 2012 B2
8136624 Fullerton Mar 2012 B2
8151882 Grigar et al. Apr 2012 B2
8152055 Miller et al. Apr 2012 B2
8172034 Fullerton May 2012 B2
8186578 Block et al. May 2012 B1
8220706 Miller et al. Jul 2012 B1
8224294 Helferich Jul 2012 B2
8250961 Mardirossian Aug 2012 B2
8261976 Block et al. Sep 2012 B1
8292022 Fullerton Oct 2012 B2
8295450 Helferich et al. Oct 2012 B2
8302730 Fullerton Nov 2012 B2
8304935 Karalis et al. Nov 2012 B2
8324759 Karalis Dec 2012 B2
8336766 Miller et al. Dec 2012 B1
8346438 Breed Jan 2013 B2
8347092 Wilson et al. Jan 2013 B2
8348151 Block et al. Jan 2013 B1
8353450 Miller et al. Jan 2013 B2
8355702 Helferich Jan 2013 B2
8368339 Jones et al. Feb 2013 B2
8369062 Fisher et al. Feb 2013 B2
8374585 Helferich Feb 2013 B2
8374721 Halloran et al. Feb 2013 B2
8375838 Rudakevych et al. Feb 2013 B2
8380350 Ozick et al. Feb 2013 B2
8385042 McCann et al. Feb 2013 B2
8387193 Ziegler et al. Mar 2013 B2
8390251 Cohen et al. Mar 2013 B2
8395878 Stewart et al. Mar 2013 B2
8400017 Kurs et al. Mar 2013 B2
8410636 Kurs et al. Apr 2013 B2
8421587 Link Apr 2013 B2
8438695 Gilbert, Jr. et al. May 2013 B2
8441154 Karalis et al. May 2013 B2
8441370 Bonavides et al. May 2013 B2
8451137 Bonavides et al. May 2013 B2
8459546 Block et al. Jun 2013 B1
8461719 Kesler et al. Jun 2013 B2
8461720 Kurs et al. Jun 2013 B2
8461721 Karalis et al. Jun 2013 B2
8461722 Kurs et al. Jun 2013 B2
8461803 Cohen et al. Jun 2013 B2
8466583 Karalis et al. Jun 2013 B2
8468244 Redlich et al. Jun 2013 B2
8468914 Givens et al. Jun 2013 B2
8468944 Givens et al. Jun 2013 B2
8471410 Karalis et al. Jun 2013 B2
8474379 Jacobson et al. Jul 2013 B2
8476788 Karalis et al. Jul 2013 B2
8479983 Block et al. Jul 2013 B1
8480397 Gerber et al. Jul 2013 B2
8482158 Kurs et al. Jul 2013 B2
8487480 Kesler et al. Jul 2013 B1
8487755 Gudgel et al. Jul 2013 B2
8496168 Miller et al. Jul 2013 B1
8497601 Hall et al. Jul 2013 B2
8497987 Miller et al. Jul 2013 B2
8498387 Helferich Jul 2013 B2
8516963 Bossarte et al. Aug 2013 B2
8528157 Schnittman et al. Sep 2013 B2
8552592 Schatz et al. Oct 2013 B2
8805814 Zijlstra et al. Aug 2014 B2
9450684 Roper et al. Sep 2016 B2
10267611 Lownds Apr 2019 B2
20010007247 Zilka et al. Jul 2001 A1
20010015548 Breed et al. Aug 2001 A1
20010020892 Helferich Sep 2001 A1
20010048215 Breed et al. Dec 2001 A1
20020027346 Breed et al. Mar 2002 A1
20020101067 Breed Aug 2002 A1
20020112638 Zilka et al. Aug 2002 A1
20020178955 Gavrilovic et al. Dec 2002 A1
20030010565 Brooks et al. Jan 2003 A1
20030052769 Helferich Mar 2003 A1
20030135327 Levine et al. Jul 2003 A1
20040107858 Zilka et al. Jun 2004 A1
20040206503 Bell et al. Oct 2004 A1
20040216698 Zilka et al. Nov 2004 A1
20050000382 Hummel et al. Jan 2005 A1
20050015473 Teowee et al. Jan 2005 A1
20050030695 Meyer et al. Feb 2005 A1
20050131655 Moolman et al. Jun 2005 A1
20050134432 Helferich Jun 2005 A1
20050164652 Helferich Jul 2005 A1
20050164653 Helferich Jul 2005 A1
20050164654 Helferich Jul 2005 A1
20050170792 Helferich Aug 2005 A1
20050215272 Helferich Sep 2005 A1
20050243499 Hallin et al. Nov 2005 A1
20050247109 Meyer et al. Nov 2005 A1
20060027121 Kockemoer et al. Feb 2006 A1
20060027191 Zilka et al. Feb 2006 A1
20060130693 Teowee Jun 2006 A1
20060183465 Helferich Aug 2006 A1
20060219122 Teowee et al. Oct 2006 A1
20060232052 Breed Oct 2006 A1
20060262480 Stewart Nov 2006 A1
20060268246 Jacobs et al. Nov 2006 A1
20070044673 Hummel et al. Mar 2007 A1
20070116189 Clawson May 2007 A1
20070155437 Helferich Jul 2007 A1
20070159766 Lownds Jul 2007 A1
20070207669 Hummel et al. Sep 2007 A1
20070228703 Breed Oct 2007 A1
20070228793 Breed Oct 2007 A1
20070272110 Brent et al. Nov 2007 A1
20080041261 Hummel et al. Feb 2008 A1
20080067792 Breed Mar 2008 A1
20080082237 Breed Apr 2008 A1
20080098921 Labuschagne et al. May 2008 A1
20080125940 Breed May 2008 A1
20080156217 Stewart et al. Jul 2008 A1
20080173204 Anderson et al. Jul 2008 A1
20080236377 Wall Oct 2008 A1
20080243342 Breed Oct 2008 A1
20080272580 Breed Nov 2008 A1
20080277911 Breed Nov 2008 A1
20080282925 Lownds et al. Nov 2008 A1
20080284145 Breed Nov 2008 A1
20080284156 Breed Nov 2008 A1
20080293385 Helferich Nov 2008 A1
20080302264 Hummel et al. Dec 2008 A1
20090019957 Eisenman et al. Jan 2009 A1
20090163190 Helferich Jun 2009 A1
20090188379 Hiza et al. Jul 2009 A1
20090191848 Helferich Jul 2009 A1
20090254572 Redlich et al. Oct 2009 A1
20090283005 Teowee Nov 2009 A1
20090283994 Teowee et al. Nov 2009 A1
20100005994 Jacobson et al. Jan 2010 A1
20100041331 Helferich Feb 2010 A1
20100066851 Pooley et al. Mar 2010 A1
20100107917 Moser May 2010 A1
20100109445 Kurs et al. May 2010 A1
20100141042 Kesler et al. Jul 2010 A1
20100164297 Kurs et al. Jul 2010 A1
20100164298 Karalis et al. Jul 2010 A1
20100171368 Schatz et al. Jul 2010 A1
20100180788 Hummel et al. Jul 2010 A1
20100181843 Schatz et al. Jul 2010 A1
20100181845 Fiorello et al. Jul 2010 A1
20100201203 Schatz et al. Aug 2010 A1
20100203872 Helferich Aug 2010 A1
20100212527 McCann et al. Aug 2010 A1
20100219694 Kurs et al. Sep 2010 A1
20100231340 Fiorello et al. Sep 2010 A1
20100237709 Hall et al. Sep 2010 A1
20100250497 Redlich et al. Sep 2010 A1
20100259108 Giler et al. Oct 2010 A1
20100259110 Kurs et al. Oct 2010 A1
20100264747 Hall et al. Oct 2010 A1
20100275799 Hummel et al. Nov 2010 A1
20100277121 Hall et al. Nov 2010 A1
20100286800 Lerche et al. Nov 2010 A1
20100308939 Kurs Dec 2010 A1
20100328838 Lownds Dec 2010 A1
20110043047 Karalis et al. Feb 2011 A1
20110043048 Karalis et al. Feb 2011 A1
20110043049 Karalis et al. Feb 2011 A1
20110072956 Wall Mar 2011 A1
20110090091 Lerche et al. Apr 2011 A1
20110095618 Schatz et al. Apr 2011 A1
20110000244 Labuschagne et al. May 2011 A1
20110174181 Plummer et al. Jul 2011 A1
20110217955 Helferich Sep 2011 A1
20110230270 Helferich Sep 2011 A1
20110244802 Kozlowski et al. Oct 2011 A1
20110247517 Hurley Oct 2011 A1
20110265677 Hummel et al. Nov 2011 A1
20110302615 Helferich Dec 2011 A1
20120042800 McCann et al. Feb 2012 A1
20120086284 Capanella et al. Apr 2012 A1
20120086867 Kesler et al. Apr 2012 A1
20120091794 Campalella et al. Apr 2012 A1
20120091795 Fiorello et al. Apr 2012 A1
20120091796 Kesler et al. Apr 2012 A1
20120091797 Kesler et al. Apr 2012 A1
20120091819 Kulikowski et al. Apr 2012 A1
20120091820 Campanella et al. Apr 2012 A1
20120091949 Campanella et al. Apr 2012 A1
20120091950 Campanella et al. Apr 2012 A1
20120112531 Kesler et al. May 2012 A1
20120112532 Kesler et al. May 2012 A1
20120112534 Kesler et al. May 2012 A1
20120112535 Karalis et al. May 2012 A1
20120112536 Karalis et al. May 2012 A1
20120112538 Kesler et al. May 2012 A1
20120112691 Kum et al. May 2012 A1
20120119569 Karalis et al. May 2012 A1
20120119576 Kesler et al. May 2012 A1
20120119675 Kurs et al. May 2012 A1
20120119698 Karalis et al. May 2012 A1
20120153732 Kurs et al. Jun 2012 A1
20120153733 Schatz et al. Jun 2012 A1
20120153734 Kurs et al. Jun 2012 A1
20120153735 Karalis et al. Jun 2012 A1
20120153736 Karalis et al. Jun 2012 A1
20120153737 Karalis et al. Jun 2012 A1
20120153738 Karalis et al. Jun 2012 A1
20120153893 Schatz et al. Jun 2012 A1
20120174809 Stewart et al. Jul 2012 A1
20120184338 Kesler et al. Jul 2012 A1
20120223573 Schatz et al. Sep 2012 A1
20120227608 Givens et al. Sep 2012 A1
20120228952 Hall et al. Sep 2012 A1
20120228953 Kesler et al. Sep 2012 A1
20120228954 Kesler et al. Sep 2012 A1
20120235501 Kesler et al. Sep 2012 A1
20120235502 Kesler et al. Sep 2012 A1
20120235503 Kesler et al. Sep 2012 A1
20120235504 Kesler et al. Sep 2012 A1
20120235505 Schatz et al. Sep 2012 A1
20120235567 Karalis et al. Sep 2012 A1
20120235568 Prodin et al. Sep 2012 A1
20120235633 Kesler et al. Sep 2012 A1
20120239117 Kesler et al. Sep 2012 A1
20120242135 Thomson et al. Sep 2012 A1
20120242159 Lou et al. Sep 2012 A1
20120242225 Karalis et al. Sep 2012 A1
20120248886 Kesler et al. Oct 2012 A1
20120248887 Kesler et al. Oct 2012 A1
20120248888 Kesler et al. Oct 2012 A1
20120248981 Karalis et al. Oct 2012 A1
20120256494 Kesler et al. Oct 2012 A1
20120274147 Stecher et al. Nov 2012 A1
20120280765 Kurs et al. Nov 2012 A1
20120299708 Guyon et al. Nov 2012 A1
20120313449 Kurs et al. Dec 2012 A1
20120313742 Kurs et al. Dec 2012 A1
20130057364 Kesler et al. Mar 2013 A1
20130063299 Proudkii Mar 2013 A1
20130098257 Goodridge et al. Apr 2013 A1
20130125772 Backhus et al. May 2013 A1
20130154389 Kurs et al. Jun 2013 A1
20130157625 Helferich Jun 2013 A1
20130175875 Kurs et al. Jul 2013 A1
20130200716 Kesler et al. Aug 2013 A1
20130206236 Hosseini et al. Aug 2013 A1
20140026775 Papillon Jan 2014 A1
20140084859 Hall et al. Mar 2014 A1
20210003377 Monroe Jan 2021 A1
Foreign Referenced Citations (59)
Number Date Country
201666766 Dec 2010 CN
0 897 098 Feb 1999 EP
0 974 035 Feb 2002 EP
1 027 574 Jan 2003 EP
1 067 349 Jan 2004 EP
1 216 391 Mar 2004 EP
1 426 719 Jun 2004 EP
1 432 959 Jun 2004 EP
1 452 813 Sep 2004 EP
1 021 868 Dec 2005 EP
1 692 822 May 2007 EP
1 782 019 Nov 2008 EP
2 357 442 Aug 2011 EP
1 848 960 Dec 2011 EP
2 082 184 Jun 2012 EP
2 069 710 Dec 2012 EP
1 859 223 Mar 2013 EP
1 687 584 Apr 2013 EP
WO 0159401 Aug 2001 WO
WO 0167031 Sep 2001 WO
WO 02099356 Dec 2002 WO
WO 03029748 Apr 2003 WO
WO 03076868 Sep 2003 WO
WO 03083406 Oct 2003 WO
WO 2005006689 Jan 2005 WO
WO 2005052498 Jun 2005 WO
WO 2005052499 Jun 2005 WO
WO 2005060173 Jun 2005 WO
WO 2005090595 Sep 2005 WO
WO 2005090895 Sep 2005 WO
WO 2006047823 May 2006 WO
WO 2006076777 Jul 2006 WO
WO 2006076778 Jul 2006 WO
WO 2007085916 Aug 2007 WO
WO 2007088404 Aug 2007 WO
WO 2007124538 Nov 2007 WO
WO 2008022399 Feb 2008 WO
WO 2008078288 Jul 2008 WO
WO 2008098302 Aug 2008 WO
WO 2008138070 Nov 2008 WO
WO 2009143585 Dec 2009 WO
WO 2010034442 Apr 2010 WO
WO 2010036980 Apr 2010 WO
WO 2010048587 Apr 2010 WO
WO 2010085837 Aug 2010 WO
WO 2010093997 Aug 2010 WO
WO 2010101597 Sep 2010 WO
WO 2011038449 Apr 2011 WO
WO 2011130099 Oct 2011 WO
WO 2011140549 Nov 2011 WO
WO 2011143679 Nov 2011 WO
WO 2012029877 Mar 2012 WO
WO 2012061850 May 2012 WO
WO 2012077082 Jun 2012 WO
WO 2012148450 Nov 2012 WO
WO 2012149277 Nov 2012 WO
WO 2012149584 Nov 2012 WO
WO 2013093300 Jun 2013 WO
WO 2013 116938 Aug 2013 WO
Non-Patent Literature Citations (3)
Entry
US 8,266,754 B2, 09/2012, Ziegler et al. (withdrawn)
US 8,271,129 B2, 09/2012, Halloran et al. (withdrawn)
US 8,359,703 B2, 01/2013, Svendsen et al. (withdrawn)
Related Publications (1)
Number Date Country
20200003535 A1 Jan 2020 US
Provisional Applications (1)
Number Date Country
61910654 Dec 2013 US
Divisions (1)
Number Date Country
Parent 15100347 US
Child 16542764 US