The present disclosure relates generally to electric detonators, particularly to digitally secured electric detonators, and more particularly to the communication and control of digitally secured electric detonators.
Detonator systems have applications in the mining, quarry, construction, pipeline and geophysical exploration industries, where many detonators may be connected and controlled by a single blasting machine. In view of the hazards inherent in such explosive systems, there is a need in the art for improved control and communication between a blasting machine and its associated detonators.
An embodiment of the invention includes a blasting control system for use with a blasting machine. The control system includes a detonator module, and a blasting machine interface configured for serial communication between the blasting machine interface and the detonator module. The detonator module includes a detonator, non volatile memory in which to store a unique electronic identification (ID) number, a switching device configured to enable or disable functioning of the detonator in response to the user's input, a communication device configured for communication with the blasting machine interface, and a processor responsive to instructions from the communication device. The blasting machine interface includes an input/output (I/O) device, a communication device, and a processor responsive to the I/O device and the communication device. Upon verification of the unique electronic ID of the detonator module via communication from a user via the blasting machine interface, a state of the switch associated with the detonator is placed in an unlocked mode so as to enable activation of the associated detonator upon a fire signal from the blasting machine via the blasting machine interface.
Another embodiment of the invention includes a method for controlling a blasting system. A detonator module is provided with a detonator in a locked state. A unique identification is provided or stored at and associated with the detonator, verification of the unique identification being operational for unlocking the detonator for controlled detonation. A password is entered into a blasting machine interface for providing operational control of the blasting machine interface. An enable signal is sent from the blasting machine interface to the detonator module, the enable signal containing verification information relating to the unique identification, and the detonator is unlocked at the detonator module upon receipt of the enable signal. A fire signal is sent from a blasting machine to the detonator module via the blasting machine interface, and the detonator is fired upon receipt of the firing signal.
Another embodiment of the invention includes a blasting control system as set forth above having a first processor at the blasting machine interface and a second processor at the detonator. Each of the first and second processors are separately responsive to computer-executable code which when executed on the respective processor facilitates the method as set forth above.
Another embodiment of the invention includes a product having any feature described herein, explicitly or equivalently, either individually or in combination with any other feature, in any configuration.
Another embodiment of the invention includes a method having any limitation described herein, explicitly or equivalently, either individually or in combination with any other limitation, in any order.
Referring now to the drawings, which are meant to be exemplary and not limiting, and wherein like elements are numbered alike in the accompanying Figures:
An embodiment of the invention, as shown and described by the various figures and accompanying text, provides a blasting machine interface (BMI) serially disposed between a blasting machine (BM), which may be a commercially available apparatus, and a detonator module (DM) for controlling the communication between the BM and the DM. The DM includes a digitally lockable control circuit and a firing circuit (detonator) where the detonator can only be fired via a firing signal from the BM when the detonator is unlocked. That is, the BMI would allow or pass a firing current from the BM to the detonator only when the detonator is unlocked via a verification signal from the BMI that serves to verify a proper identification (ID) of the associated detonator. In an embodiment, the detonator is a diode protected seismic electric detonator (DiPED). It should be understood that there is no communication between the BM and the DM. The BM sends the firing pulse (required energy/voltage) to the DM via the BMI. There is no “communication” between the BMI or DM and the BM. Communications are between the BMI, or alternatively a logger, and DM only. Existing seismic practice calls for remote control of the blasting event where the command to initiate the firing pulse is sent wirelessly (from the dog house) to the BM.
In an embodiment, the control circuit is an ASIC (Application Specific Integrated Circuit), which is incorporated into the design of the DM, and which may also include a MOSFET (Metal Oxide Semiconductor Field Effect Transistor) or other similar circuitry capable of electronically switching the flow path of current to the detonator bridge wire after having been “unlocked” by use of the BMI, and a means of communicating, in both directions, between the detonator and the BMI.
In an embodiment, RS-485 communication protocols are used for sensing and controlling the “digitally locked” detonator, where the communication hardware path is polarity insensitive and capable of withstanding up to a maximum twenty milliamps (20 mA) current leakage between detonator leg/lead wires. Leakage current preventing digital communication between a typical programming system and a detonator is a common problem in electric and electronic detonator systems, which has been overcome with the development of the RS-485 serial communication protocol. As such, an embodiment using RS-485 communication protocols allows digital communication over relatively large distances and is tolerant of noise, leakage currents, and magnetic field interference. In an embodiment, the RS-485 communications protocol is used at the physical hardware level along with a communications encoding technique, such as Manchester Differential Encoding for example, used as the communication software layer.
Communication via RS-485 would be used to “lock” and “unlock” the detonator bridge wire firing circuit and allow the firing pulse (required voltage and current) to be passed from industry standard fire sets to the detonator via the BMI.
In an embodiment, the detonator would be “digitally locked” at the manufacturing facility such that the current flow path to the firing circuit, or bridge wire, would be interrupted until the detonator is unlocked. As used herein, reference to a digitally locked detonator means a digitally locked DM where the control circuit of the DM has been modified (locked) in such a manner as to prevent a firing signal from reaching the detonator (firing circuit) of the DM.
Embodiments of the invention include without limitation at least the following three configurations.
Configuration-1:
In an embodiment consistent with configuration-1, the DM has an electronic identification (ID) or is able to store data or be programmed in any way for purposes of identification, and would be responsive to a proprietary digital signal for activation and/or unlocking. On receipt of this digital signal the DMs would unlock, thereby enabling them to be fired upon receipt of a high voltage Capacitor Discharge (CD) pulse blasting signal being applied to the input pins of the DMs. If the enabling signal were removed, the DMs would return to a disabled state. In this configuration, security is achieved by two methods. First, only a proprietary BMI is capable of providing the enable signal. And second, the BMI requires a user-established password to turn on the DM and use it. A data logger would typically not be used with this configuration, but a test unit could be employed that would verify that the detonator of the DM was in good working order when a blast hole is loaded. If a test unit were to be employed, it could be made to perform as a data logger and enter a variety of data relative to a shot point for later retrieval by a computer, but there would not be a true tie back to the specific DM.
Configuration-2:
In an embodiment consistent with configuration-2, the DM is equipped with a unique ID. When connected to a logger or BMI, the ID is displayed on the respective machine, which enables the BM to verify from loading data that it is connected to the correct DM in the correct blast hole. As with configuration-1, a CD pulse fires the detonator of the DM once the BMI provides an enable signal that unlocks the DM. In this configuration, a logger/tester is used to obtain the ID when the blast hole is loaded. This configuration also provides for entry of data, such as date, time, operator, grid location, depth, GPS, for example, at the logger/tester that can be correlated with the DM in the associated blast hole. While security of configuration-2 is achieved in the same way as in configuration-1, a BM capable of arming the overall system including the BMI is needed, which itself is password protected. By displaying the ID, an operator has some assurance that the correct BM is connected to the correct DMs. The unique ID need not be preprogrammed into the DM, but instead may be generated when the detonator is connected to the “Logger” in the field. A unique detonator ID could be generated and stored in either or both the DM and BMI using the detonator's GPS location or shot point lat/long as an input to a random number generator algorithm.
Configuration-3:
In an embodiment consistent with configuration-3, the DM is also equipped with a unique ID, similar to configuration-2, but is also be capable of receiving and storing a user-supplied code. In an embodiment, this code is a 9-digit grid location, but it could also be a GPS location or any user-supplied code suitable for the purposes disclosed herein up to the design limitation of the particular DM. As in configuration-2, a logger for use with configuration-3 is configured to accept any desired correlating data, as discussed above, but would also be used to enter the user-supplied code into a memory of the DM. On connection of the DMs to the BMI, the ID would be displayed, but the operator is required to enter the user-supplied code previously set by the logger to enable/unlock the DM, which is then fired by a CD pulse. If all of the data entered into the logger is lost, a BMI can be connected to the logger and a new user-supplied code entered, which would then allow reconnection to a BM for firing. In this configuration, security is achieved by requiring a proprietary BMI, password protection on the BM, and a requirement that a user enter a user-supplied code for the specific blast hole defined by the logger.
In view of the foregoing, it will be appreciated that the DM and BMI in combination consists of hardware and software to permit a digital command to be sent from the BMI to the DM that will unlock the detonator causing completion of a conductive electrical path from the BM to the DM, thereby providing the BM with the ability to fire the detonator charge. In addition, the BMI is capable of querying the detonator for its unique serial ID number, and for a positive readout of an internal bridge wire continuity test, which can then be displayed on the BMI, thereby permitting operator verification of the wiring and charge before firing. In an embodiment, the detonator has separate internal hardware that requires an elevated minimum voltage level of approximately 200 VDC, for example, thus eliminating the need to maintain ELV (Extra Low Voltage) or intrinsic safety designs. In an embodiment, a passive sense resistor is used across the input of the detonator, such that an industry standard blasting ohm meter or blasting galvanometer can be used to verify the integrity of the wiring to the detonator. The physical communication hardware path between the BM and DM via the BMI is configured to support polarity insensitivity as well as dependable communication, at a reasonable communication rate when exposed to voltage leakage of 20 mAh (0.020 ampere-hours) between the lead wires.
Example specifications for a DM control circuit and a BMI, where the control circuit is configured to interface with an industrial BM (minimum of 2 joules of energy) through a BMI, are provided in Table-1 below. While embodiments of the invention are described in connection with specifications presented in Table-1, it will be appreciated that these specifications are for example purposes only, and are not restrictive or limiting in any way. That is, other specifications may be employed that are not presented in or are different from those presented in Table-1.
Reference is now briefly made to
Reference is now briefly made to
In an embodiment, and with reference now to both
In an embodiment, the control circuit 120 depicted in
In an alternative embodiment, as discussed above in connection with configurations-2 and 3, a data logger 130 having an input/output (I/O) device 215 is employed and connected to either or both of the BMI 110 and/or the DM 115. When connected to BMI 110, the I/O device 215 of logger 130 is used to obtain the ID from DM 115 when the blast hole is loaded, as discussed above in connection with configuration-2. Data entry (correlating data), such as date, time, operator, grid location, depth, GPS, for example, input into logger 130 can be correlated with the DM 115 in the associated blast hole. When used with the system consistent with configuration-3, logger 130 may not only be configured to accept any desired correlating data, as discussed above in connection with configuration-2, but would also be used to enter, via I/O device 215, a user-supplied code into a memory of the DM 115. On connection of the DMs (generally referred to by reference numeral 115, but recognized that a plurality of DMs would be employed in a plurality of blast holes) to the BMI 110, the ID of the associated DM 115 would be displayed at the BMI 110, however, the operator of the system would be required to enter the user-supplied code previously set by the logger to enable/unlock the associated DM 115, which could then be fired by a CD pulse, as discussed above. If all of the data entered into the logger 130 were to be lost, a BMI 110 could be connected to the logger 130 and a new user-supplied code entered, which would then allow reconnection of the DMs 115 to a BM 105 for firing.
Operation of the blasting control system 100 is as discussed above and as generally outlined in the flowcharts of
Method 400 includes method blocks 405 (Lock DM), 410 (Store ID in DM for unlocking locked DM), 415 (Enter password into BMI, send enable signal from BMI to DM, and unlock DM upon receipt of enable signal from BMI), 420 (Send blasting signal from BM) and 425 (Fire DM upon receipt of blasting signal from BM via BMI) as illustrated in
Method 500 includes method blocks 505 (Lock DM), 510 (Store ID in DM for unlocking locked DM), 515 (Enter password into BMI, verify that BM is connected to correct DM by displaying ID on BMI), 520 (Send enable signal from BMI to DM, and unlock DM upon receipt of enable signal from BMI), 525 (Send blasting signal from BM) and 530 (Fire DM upon receipt of blasting signal from BM via BMI) as illustrated in
Method 600 includes method blocks 605 (Lock DM), 610 (Store ID in DM for unlocking locked DM), 615 (Store user-code in DM via logger for unlocking DM), 620 (Enter user-code into DM via logger to unlock DM, enter password into BMI, verify that BM is connected to correct DM by displaying ID on BMI), 625 (Send enable signal from BMI to DM, and unlock DM upon receipt of enable signal from BMI), 630 (Send blasting signal from BM) and 635 (Fire DM upon receipt of blasting signal from BM via BMI) as illustrated in
To perform the desired communication and control operations, processors 210, 315 are configured to be responsive to computer-executable code which when executed on the respective processor facilitates the desired communication and control operations as described and illustrated herein.
The hardware of the DM electronics (control circuit 120) includes a memory for storage of a unique, non-repeatable serial number, bi-directional communication from the BMI, enable/disable state of the detonator as directed by input to the BMI, igniter polarity insensitivity, secondary elevated threshold voltage circuitry.
Software design and coding for the DM includes a robust communication protocol, a configuration and control data set to include: igniter enable/disable, query the serial number, master igniter reset.
Hardware design of the BMI can either be embedded in an industry available BM or located externally between the BM and the igniter/detonator. The BMI will provide an industry standard asynchronous serial, SPI (synchronous serial), or USB communication connector for connection to the command/control equipment with an embedded visual alphanumeric display (that is, LCD, LED for example) to support operation at extended temperature range (such as to −20 C for example). Visual indicators include status LEDs supporting igniter lock/unlock and switches that include enable or disable control of the detonator.
Software design and coding of the BMI includes support of the detonator communication and control protocol, and support of the user interface (such as LED and switches to enable or disable the detonator for example).
In an embodiment, the igniter PCB (control circuit 120 of DM 115) is so dimensioned and configured as to fit into an industry standard encapsulation housing available from Dyno Nobel, which in an embodiment has a nominal inside diameter of 0.25 inches, that is, an inside diameter of 0.256 inches, and an outside diameter of 0.295 inches. However, it will be appreciated that the scope of the invention is not limited to a nominal inside diameter of 0.25, but is instead commensurate with the disclosure and purpose presented herein. In an embodiment, the blasting machine interface is configured for internal integration into an industry standard blasting machine, and in another embodiment is configured to operate as a “stand alone” device. The PCB configurations are made for high volume SMT (Surface Mount Technology) construction and automated final assembly.
An embodiment of the invention may be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. Embodiments of the invention may also be embodied in the form of a computer program product having computer program code containing computer executable instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, USB (universal serial bus) drives, or any other computer readable storage medium, such as read-only memory (ROM), random access memory (RAM), erasable-programmable read only memory (EPROM), and electronically erasable programmable read only memory (EEPROM), for example, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing embodiments of the invention. Embodiments of the invention may also be embodied in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing embodiments of the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits. A technical effect of the executable instructions is to control the unlocking of a detonator for controlled detonation thereof.
As disclosed, some embodiments of the invention may include some of the following advantages: the reduction or elimination of unauthorized use of commercial electric detonators; and, a blasting system that overcomes present limitations on the number of detonators in a blast site as well as limits on communication distances between the BM and DMs.
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best or only mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Also, in the drawings and the description, there have been disclosed exemplary embodiments of the invention and, although specific terms may have been employed, they are unless otherwise stated used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention therefore not being so limited. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2009/058778 | 9/29/2009 | WO | 00 | 6/10/2011 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2010/039704 | 4/8/2010 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4674047 | Tyler et al. | Jun 1987 | A |
5214236 | Murphy et al. | May 1993 | A |
7958824 | Stewart | Jun 2011 | B2 |
20030159609 | Rauscher, Jr. | Aug 2003 | A1 |
20060086277 | Bossarte et al. | Apr 2006 | A1 |
20100275799 | Hummel et al. | Nov 2010 | A1 |
Number | Date | Country |
---|---|---|
2005071348 | Aug 2005 | WO |
2007143759 | Dec 2007 | WO |
2008094060 | Aug 2008 | WO |
Entry |
---|
PCT International Search Report and Written Opinion for International Application No. PCT/2009/058778; International Filing Date: Sep. 29, 2009; 16 pgs. |
Chile Office Action for Chilean Patent Application No. 1909-2009; Dated: Sep. 28, 2009; with English Examination Report from Foreign Agent; 10 pgs. |
Number | Date | Country | |
---|---|---|---|
20110247517 A1 | Oct 2011 | US |
Number | Date | Country | |
---|---|---|---|
61101429 | Sep 2008 | US |