Classifications

• • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
  • F42—AMMUNITION; BLASTING
  • F42D—BLASTING
  • F42D1/00—Blasting methods or apparatus, e.g. loading or tamping
  • F42D1/04—Arrangements for ignition
  • F42D1/045—Arrangements for electric ignition
  • F42D1/05—Electric circuits for blasting
• • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
  • F42—AMMUNITION; BLASTING
  • F42D—BLASTING
  • F42D1/00—Blasting methods or apparatus, e.g. loading or tamping
  • F42D1/04—Arrangements for ignition
  • F42D1/045—Arrangements for electric ignition
  • F42D1/05—Electric circuits for blasting
  • F42D1/055—Electric circuits for blasting specially adapted for firing multiple charges with a time delay

Definitions

• the present invention relates to a system for programming and firing a set of electronic detonators, and a corresponding programming method.
• WO 97/45696 discloses detonator programming steps consisting mainly of using one or more programming units or consoles to associate a delay time, in milliseconds, with each of the detonators.
• the corresponding association table forms a firing plan that is subsequently transferred to a firing unit or console having detonator firing capabilities and codes.
• an operator travels the work site back and forth to successively and individually connect each of the detonators to a firing line. Since the operator's programming unit is also connected to the firing line, it detects the connection of a new detonator and identifies the latter. The operator then enters, through an alphanumeric keypad of the programming console, a delay time to associate with each of the detonators successively identified on the firing line.
• the operator can specify, on his programming unit, information of firing type identifier of the hole drilled on the site in which the detonator detected is placed, the association with a delay time can be performed later on the firing console for example.
• a detonator identification step is performed.
• This identification consists for the programming unit to recover a detonator identification parameter connected by message exchange on the firing line, this parameter being for example stored in the ROM memory of the electronic detonator.
• the programming unit then stores, in the EEPROM memory, the association made between this identification parameter and the corresponding delay time or hole number entered.
• the resulting table constitutes the firing plan.
• the identification may consist, for the programming unit, in sending to the detonator an identification parameter which will be memorized by the detonator, for example in the EEPROM memory, the programming unit then memorizing the association of this identifier and firing time type information or hole number.
• this programming operation can quickly become laborious with regard mainly to the large number of detonators to connect and program. Thus, several hours of programming may sometimes be necessary.
• the programming operation can be performed by several operators, each being equipped with a programming console to program, with each of them, a part of the firing plan.
• the firing plan is divided into several zones, the detonators of each of them being connected on bus lines, all of these bus lines constituting a network connected to a main line called a firing line.
• each of them contains the identification parameters only of a part of the detonators present on the firing line, corresponding only to the detonators programmed by this console .
• Each console performs counting functions and then identification of connected detonators.
• detonators programmed by other consoles should not be considered intruders. This forces a mental intervention of operators to compare the number of detonators connected to the number of detonators programmed, without easily detect any intruders.
• a programming unit fails during these programming operations, for example because of a battery failure or a material destruction resulting from a construction accident.
• Such a situation requires complete reprogramming of the detonators initially stored in the (partial) firing plan of the defective console. A considerable loss of time can thus be generated.
• the operator can not complete his programming operations because the battery is flat and requires recharging.
• the invention aims to solve at least one disadvantage of the state of the art by proposing in particular to simplify the transfer of data, including programmed fire plans, between different consoles.
• the invention relates in particular to a system for programming and firing a plurality of electronic detonators, each of which is associated with a specific identification parameter, the system comprising:
• At least one programming unit comprising a memory and arranged to determine the detonator identification parameters and individually associate them, in memory, with firing information, so as to form a firing plan;
• a firing unit arranged to recover, from the memory of the at least one programming unit, said firing plan formed from associations between the identification parameters and the corresponding firing information, and to drive a sequence of firing detonators from the recovered firing plan;
• a radio frequency reader arranged to read and write passive tags, including said passive tag of the programming unit.
• the system according to the invention is based on RFID tags for storing firing plans during on-site or "on-site” programming.
• "On site” or “in front” means the operations carried out on the work site where the detonators are located. This denomination is opposed to the firing which is, she, carried out at a distance through the firing line by a firing console, also called firing console.
• a "master" firing console may possibly control several different shots by means of "slave” and local firing consoles each connected to a particular firing line.
• the invention By transferring a partial firing plan to a new programming console using RFID means, programming of the firing plan can be continued without losing what has been done until the first console fails.
• the invention also simplifies the transfer of programming on a single console. Tests conducted using this unique console allow easier identification of intruder detonators and reduce or eliminate the intervention of the operator.
• the passive tag according to the invention mainly functions as a de-correlated data memory of any identification of the programming console that contains it.
• the memorized firing plan is not intended to identify the programming console.
• this passive tag appears as a temporary memory of the firing plans before transfer either to another programming console, or generally to the firing console.
• a first programming unit comprises means for controlling said radio-frequency reader arranged to read the firing plan in memory of the passive label of a second programming unit and to copy said fired plan in the memory of the passive tag of the first programming unit.
• This arrangement makes it possible to ensure simple and effective recovery of firing plans partially programmed by a programming unit that has become defective.
• said passive tag comprises, associated with said firing plan, an identification datum of a geographical zone to which said detonators forming the firing plane belong.
• a programming console since a programming console is generally used on a single firing line or a bus line, it may be the identification of this line, for example via an identifier of a connected slave and local fire console. to this line.
• said firing unit comprises a radiofrequency reader arranged to read and write the passive label of the at least one programming unit so as to recover said firing plan.
• said programming unit comprises means for inhibiting its radio frequency reader when an external radiofrequency reader transfers the firing plane from the memory of this programming unit.
• said firing information comprises a firing time delay of the corresponding detonator.
• the firing plan thus obtained is directly operational for the firing consoles.
• said identification parameters are coded on 24 bits and said time delays are coded on 14 bits.
• This configuration makes it possible to store, in the form of a table, a firing plan composed of several thousand entries on conventional radio frequency tags, for example provided with 32 KB (kilobytes) of memory.
• the at least one programming unit comprises a plurality of radiofrequency tags for each storing a part of the firing plan.
• the radiofrequency tag is removable. It can thus be inserted into another programming unit to continue programming operations.
• the invention also relates to a programming method for firing a plurality of electronic detonators, each of which is associated with a specific identification parameter, the method comprising:
• association step comprises a radio frequency write of said association, in the memory of a radio frequency read / write passive tag.
• the method has advantages similar to those of the system set out above, in particular the easy provision of the firing plan for other consoles.
• the method may include steps relating to the features of the previously disclosed programming and firing system.
• the method also comprises a step of radiofrequency reading transfer of the firing plane from the passive tag of a first programming unit to the passive tag memory of a second programming unit.
• This transfer can in particular be made during the failure of said first programming unit or when it is desired to group, on site, the firing plans of several consoles. programming, for example to conduct tests on the entire detonators.
• said second programming unit continues the acquisition and association steps so as to complete the transferred firing plan.
• a second programming unit for example a backup unit, programming the detonators by completing the firing plan retrieved from the failed console.
• the plurality of electronic detonators is divided into several distinct geographical areas, and the method comprises a step of reading and associating an identifier of a said geographical area to said firing plan in memory.
• This step may include reading an RFID tag contained in a slave firing console connected to the firing line on which are connected the detonators of said geographical area.
• FIG. 1 represents the general organization of a firing assembly for the implementation of the invention
• FIGS. 2A, 2B and 2C are schematic representations of a firing assembly comprising detonators mounted in parallel, showing communication circuits established respectively during the programming of a detonator, the transfer of information from the programming unit to the firing control unit and during a firing sequence of a detonator volley;
• FIG. 3 diagrammatically represents a programming unit or console according to the invention.
• FIG. 4 shows schematically an example of firing unit according to the invention.
• a firing assembly can be constituted from detonators 1 similar to those presented in publication WO 97/45696.
• This firing assembly also visible in FIGS. 2B and 2C, comprises any number of electronic detonators 1 connected to bus lines 30, themselves connected to a firing line 40 which is in turn connected to a control unit distant fire 10, also called "firing console” or "firing console”.
• the detonators 1 can be used in large numbers in parallel assembly, up to more than 1000.
• the detonators 1 are provided with a ROM memory storing a unique identifier IDdét of the detonator on 24 bits for example. Any other combination of detonator identification parameters, such as that discussed in WO 97/45696, may be provided.
• the detonators are able to interact with the firing console 1 0 (or the slave consoles), which can transmit orders to them and receive information from them.
• the firing assembly also comprises one or more programming units 20, also called “programming consoles”. These are intended to identify each of the electronic detonators 1 before or after their introduction in a drilled hole on the site, and to progressively constitute information of firing sequences or "firing plan", during this identification. They are also used to transfer this shot plan information to the firing console 10.
• the programming console 20 is successively connected to each of the detonators 1.
• This first configuration corresponds to a first step, during which an on-site operator "programs" the firing plan by successively associating each connected detonator (and its identifier) with a delay time corresponding to the level of the programming console 20. as will be seen later, these associations are stored through a table in memory of the programming console 20.
• this connection may consist in connecting the programming console 20 on a bus line 30 and then in detecting, via exchanged messages, each new detonator 1 connected to this same line, sending a message by a newly connected detonator.
• the programming console 20 is connected by radiofrequency link, as described below, to the firing console 10, while the connection between the detonators 1 and the firing console 10 is disabled.
• This second configuration corresponds to a second step, during which transfer from the programming console 20 to the firing console 10, the information concerning the programmed firing plan.
• the programming console 20 and the detonators 1 are connected to the firing console 10, the detonators 1 being connected to the firing console 1 0 by the bus lines 30 and the firing line 10.
• the firing assembly may comprise several lines 30 in parallel, thus forming a two-wire detonator network.
• This third configuration corresponds to a third step, during which the firing console 10 is likely to communicate with the electronic detonators 1, then to a final step, during which the firing console 10 can manage a firing procedure and a setting.
• detonator fire 1 connected to the bus lines 30 connected to the firing line 40, in accordance with the planned firing plan.
• the firing console 10 and the detonators 1 exchange information via binary coded messages, for example in the form of words of a few bytes, on the two-wire line 30/40.
• the firing console 10 is also used to power the electronic modules of the detonators 1. This power supply is the source of energy likely to trigger a firing. In this way, the detonators do not present a risk of inadvertent triggering outside firing sequences.
• a "master" firing console and “slave” firing consoles each attached to a firing line 40 it is the slave consoles that communicate, on one side, with the detonators 1 via the two-wire network. and, on the other side, with the "master" console by radio.
• the firing and programming consoles 20 are of similar structures and differ mainly in their functionality, and therefore in the management software with which they are associated. It should be noted that, for security reasons, only the firing console 10 has firing means, in particular a software for controlling a firing sequence of detonators 1 as well as firing codes. These firing codes can for example be presented to the firing console 10 using a smart card read by a card reader integrated in this console 10.
• a programming console 20 is of portable type equipped with an autonomous power supply 21 to allow an operator to traverse the detonator detonator site, in particular to carry out the operations of the first step (FIG. 2A ).
• the console 20 has a computer bus 22 connecting a processing processor 23, a read-only memory 24 for storing software implementing the functions of the console, an input-output interface 25 for connecting the console 20 or directly to a detonator 1, or on the two-wire network 30, a user interface 26 (including a display screen and an alphanumeric keyboard input) and an RFID reader 27 (radio frequency identification).
• the programming console 20 also includes an RFID tag 28 with a memory chip 280 capable of storing data.
• RFID tag means the conventional association of an RFID chip with an antenna, the RFID chip being provided with communication means according to radio frequency protocols and storage capacities.
• An RFID tag 28 with a capacity of 32 KB has both sufficient capacity for range planning applications according to the invention and a relatively inexpensive acquisition cost.
• the programming console 20 may comprise several RFID tags 28 accessible by the reader 27 and successively solicited when the memory of the previous label is fully used.
• Anti-collision mechanisms are implemented at this reader to allow reading of these labels. Thus, it increases without difficulty the programming capabilities of the console 20.
• the RFID tag 28 is mounted on a removable medium, for example of chip card format. It can be easily extracted for insertion into another programming console or shooting console, simplifying the transfer of data between different units.
• the memory chip 280 stores a table PT forming all or from a firing plan by association of a detonator ID det ID with a delay corresponding to the delay time of the setting. Associated detonator fire.
• This table can be identified by means of a shot plan number possibly associated with an identifier of the firing line or bus lines that will be programmed by this firing plan (for example the identifier of the firing console). shot "slave" attached to the firing line).
• shots plan number possibly associated with an identifier of the firing line or bus lines that will be programmed by this firing plan (for example the identifier of the firing console). shot "slave" attached to the firing line).
• this identifier may be replaced by an identifier of the programming console 20 containing this label.
• This function has different sub-functions such as a write function, a copy function, a muting function and a conventional read function.
• the write function is intended to fill the PT table during the first programming step of the firing plan.
• the copy function makes it possible to copy, by read-write, the content in memory of an RFID tag present in the readout field of the console 20, to the RFID tag 28 of the same console 20. This function is especially used. during the recovery of a partially developed fire plan before the failure of the programming console, or when merging several partial fire plans on the same console 20 to conduct connection tests detonators .
• the muting function makes it possible to deactivate the reader 27 during the voluntary transfer of the firing plane to either the firing console 10 or to another programming console 20 before testing, for example. This inhibition can be triggered by the automatic detection of another radio frequency field, or manually.
• the firing console 10 also has an RFID reader 17 capable in particular of reading the RFID tags 28 of the programming consoles 20 which are presented in its reading field.
• the firing console 10 thus has a transfer function of the tables PT stored in the programming consoles 20 by radio frequency reading. Storage of these transferred PT tables can be operated either in an RFID tag 18 specific to the firing console 10, or, preferably, in a rewritable memory 19, RAM type, of the firing console.
• the other functions and interfaces of the firing console 10 are conventional and similar for example to those described in the publication WO 97/45696.
• the first detonator programming step 1 is conducted by one or more programming consoles 20.
• Each console can, for example, initially recover the identifier (LTi) of the firing line or bus lines that she has to program.
• the programming console 20 reads an RFID tag contained in the "slave" firing console attached to the line or lines to be programmed.
• the operator By traversing the site where the detonators are located, the operator connects individually and successively each detonator 1 to the programming console 20.
• the operator can connect the programming console 20 to the two-wire network 30 (or to a part thereof, for example a firing line) then without the detonators 1. The operator then successively connects each detonator 1 to the network 30.
• This "programming" can consist of entering numbers on a numeric keypad to specify a delay between 1 and 16000 milliseconds by encoding the delay on 14 bits.
• the delay times can follow a logical sequence and the programming console 20 then automatically proposes a delay corresponding to this logical sequence. The operator then validates the proposed delay or seizes another delay.
• the implementation of this solution is generally done when it is easy for the operator to browse the site in the logical order of firing the detonators and programming successively these detonators, in order to take maximum advantage of delays proposed automatically without manual entry.
• the programming console 20 then associates, in RFID memory, the selected delay Tdét the selected detonator 1. This association is stored in the form of a table of correspondences, type look-up table, in the memory chip 280.
• the following table is a simplified example of a firing plan numbered PT1 for the firing line numbered LT1:
• Table 1 PT1 firing plan with n detonators
• the operator When several firing planes are memorized, the operator also indicates which firing plan (and therefore table PTi - LTi) the association entered must be assigned.
• the programmed detonator 1 is then disconnected from the console 20 and reconnected to the network 30.
• the programming console 20 fails (empty battery 21) or is damaged by construction equipment while the operator is on the site, far from the computer center having the shooting console 10.
• the invention makes it possible to easily recover, on site, the firing plan partially created in the programming console and continue programming on a spare console without having to reprogram the already processed detonators.
• the operator takes a backup programming console 20 'identical to the default console 20.
• the operator selects the copy function of the backup console.
• PT table offered by the backup console thanks in particular to PTi and LTi identifiers that can identify the information to recover certain.
• Reading and writing in RFID tags are then conducted in a conventional manner and will not be more detailed here.
• the rescue console recovers the PT shot plan configuration when the first programming console has failed.
• the operator can continue programming other detonators without losing the work already done.
• the first programming step may end with a connection test phase of the detonators 1 to the two-wire network.
• the programming console 20 containing the programmed firing plan is connected to the network.
• the test can be conducted on only part of the network, for example a single bus line 30.
• the programming console 20 must verify that all the detonators stored in the PT table is connected to the network and that there are no detonators intruded on this network.
• each programming console is then used separately for the test.
• Each console has a function of counting the number of detonators connected (via a recovery routine of all connected detonators at a time) and a function of checking the connection of detonators in memory by sending / receiving messages to / of each of these detonators (the console 20 retrieves each memorized identifier and interrogates, by message, the presence on the firing line of the detonator having this identifier).
• the detection of intruders is however delicate because among the detonators not programmed by this console 20, some are by another programming console. Mental or manual operations are then necessary and laborious.
• the test operation it is initially planned to merge (by concatenation for example) the firing plans of several programming consoles 20 on only one of them, said main console.
• said main console For example, it may be the set of consoles 20 having programmed the same firing line LTi.
• the main console can automatically determine the intruder detonators and if the programmed detonators are all connected.
• each of the connected programmed detonators is marked in the table PT (with the aid of a flag for example) and an intruder detonator counter is incremented.
• the RFID reader 27 of the secondary programming consoles 20 is deactivated, via the muting function, and all or part of these secondary consoles are presented in the RFID reading field of the main console.
• the latter transfers the firing plans of each of the secondary consoles to its own memory 280, and merges them into a single table PT, taking into account the number of shot plane PTi and the possible LTi firing line.
• the tests can thus be conducted using a single programming console 20, for the entire network, without disconnecting some detonators.
• a sub-part of the programming consoles may be grouped as a function of zones of the network, for example the firing lines.
• the programming console 20 preferably the main console uniting the overall firing plan resulting from the reunification of the partial firing plans, is close to the firing console 10, as shown in Figure 2B to transfer the firing plan.
• the RFID reader 27 of the programming console 20 is deactivated through the inhibition function.
• This activation can only be authorized after introduction of an appropriate card containing secret codes. Any other security organ may also be used to authorize this activation.
• the table PT of the firing plan is then automatically transferred to the firing console 10 by radiofrequency reading by the reader 17. If several RFID tags are accessible, the firing console 10 may invite the operator to select all or part of these fires. ci and all or part of the tables PTi stored therein, for transfer. The transferred PT table is then stored in RAM memory of the firing console 10.
• this table may be stored in an RFID tag memory 18 also provided in the firing console 10. This configuration makes it possible to implement a copy function to a fire rescue console if necessary, similarly to the copy function provided for programming consoles 20.
• the firing console 10 merges the recovered PT tables to form the overall firing plan, especially in view of the number of firing points. shot plane PTi associated with each PT table of the programming consoles.
• the firing line 40 connecting the firing console 10 to the detonators 1 is activated, as shown in FIG. 2C.
• the firing console 10 can then perform tests prior to the execution of the firing sequence, as described in the publication WO 97/45696: automatic test of the detonator ignition modules online, detonator availability test.
• a table PT in memory of the programming consoles 20 which associates a detonator identifier with a delay has been described above.
• a pre-fire plan can be provided separately, which associates delay times with a set of holes in a physical site configuration.
• the programming by the programming console 20 can then consist of an association of the detonators 1 with the holes, the table PT in memory then associating a detonator to a hole of the site.
• the association of a detonator with a delay is indirectly performed using the pre-firing plan.
• Any firing information other than a time delay or a hole number, may be associated with a detonator at the programming console, provided that this information is used to constitute a firing sequence (detonator identifier - time delay of firing).
• the firing console 10 described above has a structure similar to that of the programming consoles 20, including a radio frequency reader and possibly an RFID tag.
• the invention is, however, compatible with already existing shooting consoles 10 (without radio frequency means).
• the programming consoles 20 have a transfer function similar to that of the publication WO 97/45696, for the automatic transfer of the firing plan in memory to the firing console 10 to which they (20) are connected, by infrared or wired link.
• This function provides for controlling the RF reader 27 of the programming console 20 to read the table PT in memory and to communicate it to the firing console 10 via an appropriate communication interface.
• This automatic transfer function is implemented by the software stored in read-only memory 24.

Landscapes

• Engineering & Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Alarm Systems (AREA)
• Mobile Radio Communication Systems (AREA)
• Air Bags (AREA)
• Read Only Memory (AREA)
• Credit Cards Or The Like (AREA)
• Powder Metallurgy (AREA)
• Fire-Extinguishing By Fire Departments, And Fire-Extinguishing Equipment And Control Thereof (AREA)
• Circuit Arrangement For Electric Light Sources In General (AREA)
• Fire Alarms (AREA)

Priority Applications (1)

Applications Claiming Priority (2)

Publications (2)

Family

ID=42635211

Family Applications (1)

Country Status (17)

Families Citing this family (16)

Family Cites Families (11)

• 2010
  • 2010-02-02 FR FR1050717A patent/FR2955933B1/fr not_active Expired - Fee Related
• 2011
  • 2011-01-28 WO PCT/FR2011/050176 patent/WO2011095730A1/fr active Application Filing
  • 2011-01-28 PE PE2012001090A patent/PE20130522A1/es active IP Right Grant
  • 2011-01-28 UA UAA201210289A patent/UA104510C2/uk unknown
  • 2011-01-28 CA CA2787613A patent/CA2787613C/fr active Active
  • 2011-01-28 AU AU2011212272A patent/AU2011212272B2/en active Active
  • 2011-01-28 BR BR112012019297-3A patent/BR112012019297B1/pt active IP Right Grant
  • 2011-01-28 EP EP11706885.8A patent/EP2531809B1/de active Active
  • 2011-01-28 MX MX2012008920A patent/MX2012008920A/es active IP Right Grant
  • 2011-01-28 EA EA201290739A patent/EA020679B1/ru not_active IP Right Cessation
  • 2011-01-28 US US13/575,715 patent/US8994515B2/en active Active
  • 2011-01-28 ES ES11706885.8T patent/ES2454865T3/es active Active
  • 2011-01-28 PL PL11706885T patent/PL2531809T3/pl unknown
  • 2011-01-28 PT PT117068858T patent/PT2531809E/pt unknown
• 2012
  • 2012-07-30 ZA ZA2012/05728A patent/ZA201205728B/en unknown
  • 2012-07-31 CL CL2012002121A patent/CL2012002121A1/es unknown
  • 2012-08-28 CO CO12146296A patent/CO6561842A2/es not_active Application Discontinuation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events