EP1325282B1 - Procede pour le raccordement d'amorces a un systeme de mise a feu - Google Patents

Procede pour le raccordement d'amorces a un systeme de mise a feu Download PDF

Info

Publication number
EP1325282B1
EP1325282B1 EP01982381A EP01982381A EP1325282B1 EP 1325282 B1 EP1325282 B1 EP 1325282B1 EP 01982381 A EP01982381 A EP 01982381A EP 01982381 A EP01982381 A EP 01982381A EP 1325282 B1 EP1325282 B1 EP 1325282B1
Authority
EP
European Patent Office
Prior art keywords
logger
log
manager
data
detonator
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP01982381A
Other languages
German (de)
English (en)
Other versions
EP1325282A1 (fr
Inventor
Walter Aebi
Jan Petzold
Heinz Schäfer
Andreas Zemla
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orica Explosives Technology Pty Ltd
Original Assignee
Dynamit Nobel AG
Dynamit Nobel GmbH Explosivstoff und Systemtechnik
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dynamit Nobel AG, Dynamit Nobel GmbH Explosivstoff und Systemtechnik filed Critical Dynamit Nobel AG
Publication of EP1325282A1 publication Critical patent/EP1325282A1/fr
Application granted granted Critical
Publication of EP1325282B1 publication Critical patent/EP1325282B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

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
    • F42D1/055—Electric circuits for blasting specially adapted for firing multiple charges with a time delay

Definitions

  • the invention relates to a method for connecting igniters to an ignition system according to the preamble of the first claim.
  • An ignition system consists of a large number of detonators, which are connected to a bus line, which in turn starts from a so-called logger.
  • a logger is a data reading and storage device in which the relevant data of a detonator can be stored.
  • An ignition system can consist of several ignition circuits, that is, there are several loggers, to each of which a bus line is connected with a plurality of detonators. The loggers in turn are connected to an ignition device or a tripping device, a so-called blaster, from which the detonators can be ignited in a predetermined time sequence on the basis of an ignition command.
  • detonators which have an identification code.
  • This can for example consist of an identification number or a barcode, which are externally applied to the igniter and can be read.
  • the identification code can also be stored in the electronics of the detonator. When this identification code is stored in the logger, the detonator can be addressed with the logger's programming and storage electronics if a function, such as a delay time, is to be stored in the detonators.
  • the detonators After laying the bus line from the logger, the detonators are connected with their ignition cable to the bus line of their assigned logger, be logged. If several loggers are distributed with corresponding bus lines in the area, the logging on of the detonators to the bus lines can take place simultaneously.
  • the subsequent person the logger
  • the logger can also tell the logger the geographic coordinates of the borehole into which the igniter is lowered.
  • the borehole coordinates as well as the identification code of the detonator can be combined to form a so-called address under which the respective detonator can be individually addressed by the logger.
  • the determination of the coordinates of the borehole can be done, for example, by means of GPS (Global Positioning System) or by means of the DGPS (Differential Global Positioning System).
  • the logging of the detonator to the bus line is carried out in particular in the opencast mining under conditions that initially not visible to damage, especially on the isolation of the detonator and the ignition cables can lead. Such damage can lead to shunts, in particular to shunt igniter to igniter. If these shunts occur between detonators which are simultaneously connected to different bus lines, then errors in the data transmission can occur, for example due to loss or forgery of the signals to be transmitted or due to intrusion of signals from a foreign detonator.
  • the object of the present invention is to provide a method with which the described disturbances and errors can be avoided.
  • Each of the loggers carries a transmitting and receiving device, a log data transmitter, which has its own identification code and the Transmission of the identification codes and the data of the geographical coordinates of the detonator to its associated logger is used.
  • These transceivers are designed for bidirectional contact both with their associated logger and the Anlog Manager.
  • the Anlog Manager is in bidirectional contact with all loggers as well as with all log data transmitters that carry the loggers. The contact can be made via lines or via radio.
  • an igniter is to be logged on to the bus line of a logger by a logger.
  • the logger who wants to connect the detonator logs in with his log data transmitter at the Anlog Manager, who recognizes him by the identification code and thus can assign the associated logger.
  • the logging can be done, for example, that a signal with the identification code is transmitted to the Anlog Manager by pressing a button, for example by radio.
  • the Anlog Manager acknowledges the logon with a signal to the logger. If no other igniter is connected at the moment, an enable signal for logging on the igniter is transmitted. Otherwise, a message appears that the data transmission is not possible. As a result, it is advantageously avoided that a distortion of the signals to be transmitted occurs due to the above-described possibilities of error.
  • the signals can be communicated visually, acoustically or mechanically, for example by vibrations, to the logger by the log data transmitter.
  • the logger associated with the logger is switched to reception by the log-on manager, so that the corresponding data can be read in from the igniter to be connected.
  • This logger can only be addressed by the Anlog Manager if it knows its identification code.
  • the Anlog Manager can contact directly to the responsible logger so that it can receive the signals of the logger associated with the log data transmitter or the data of a logging on to the bus itself igniting detonator.
  • the logger If the logger has now received confirmation from the log-on manager that the detonator can be connected to the bus line, he performs this connection and acknowledges the log-on by transmitting the identification code and possibly the position of the connected detonator, if this has been determined For example, by using the GPS or the DGPS is possible.
  • the logger If the logger now recognizes that the transmitted data is incomplete or faulty due to the possible errors described above, it can immediately report the error and, for example, make it visible to the logger on a display. As a result, faulty igniter or a faulty connection can be detected immediately.
  • two or more loggers may log in to the Anlog Manager at the same time.
  • the Anlog Manager only allows logging on during a time, so that only one logger at a time is offered the opportunity to connect a detonator and in each case only the data of a detonator is transmitted to the associated logger.
  • the other loggers are informed by a signal that they are, so to speak, in a waiting position and the release only takes place when the current log-on process of a detonator is completed.
  • a waiting loop can be provided in the Anlog Manager, in which the respective loggers are arranged in chronological order according to the order of the incoming message and, if appropriate, the waiting position is displayed to them.
  • the logger acknowledges this to the log data transmitter with an acknowledgment signal.
  • the logger can then inform the log-in manager of the successful log-on of the detonator with a signal.
  • the acknowledgment signal of the logger can also go directly to the log-on manager and serve on the log data transmitter only as an indicator for a successful log-on.
  • the Anlog Manager may enable the next sequencer on hold to log on to the next detonator.
  • the logger just watching the connection has successfully performed a detonator, knows that he can register the connection of the following detonator.
  • Anlog management can also be performed if the detonator automatically logs on to the logger when it is connected to the bus.
  • the logger must first alert the log-in manager that he intends to log in an igniter.
  • the Anlog Manager will then check to see if a detonator is already logging in at the same time. If this is the case, the logger, to whose bus line a detonator is to be logged on, is blocked for receiving the data until the log-on procedure of a preceding detonator on another logger has been completed.
  • the logger After confirming receipt of the signals of the logged-on detonator by the acknowledgment signal of the logger, either the logger can notify the log-in manager of the successful log-on or the signal goes directly to the log-on manager.
  • the Anlog Manager then sends an enable signal to the logger, to whose bus the detonator is to be logged on. If the detonator is then connected to the bus line, it automatically sends its identification code to its logger, which acknowledges the connection when the signals are received correctly and stores the identification code, optionally with the geographical coordinates of the detonator, as the address.
  • the inventive method gives the highest possible security in the simultaneous logging of detonators in an ignition system with multiple ignition circuits and thus multiple loggers.
  • the Anlog Manager is also suitable for coordinating the transmission of the delay times from the blaster via the loggers to the individual detonators. Since this data transmission can also be hindered and disturbed by the above-described possibilities of damage to the detonators or ignition lines, it is advantageous if each detonator is addressed individually. In this case, the logger and the blaster must have an address so that they can be addressed by the log-on manager. The Anlog Manager then allows the data transfer from the Blaster only to the logger and from there only to the detonators, which should also be addressed and locks the other loggers.
  • the blaster can signal the end of the data transfer by means of a signal to the Anlog Manager.
  • the respective logger can report to the Anlog Manager that the reception of the delay time data by the detonators has taken place and the programming of the individual detonators has been completed. Based on these signals, the Anlog Manager can switch off the previous logger and switch the subsequent logger to receive.
  • the inventive method ensures that in the signal transmission after connecting the detonator and the subsequent programming of the delay times, the signal transmission of a detonator or a logger is not disturbed by the signal transmission of another detonator or logger and that errors in the transmission are detected immediately and the respective Sender or receiver, the detonator or the logger can be assigned.
  • the present illustration shows an ignition system 1 with four separate ignition circuits 2 to 5.
  • Each of the ignition circuits 2 to 5 consists of a bus line 6 to 9, each emanating from a logger 10 to 13 and at the igniter 14 with its ignition line 15 in the Connection point 16 connected, that is logged on.
  • all four ignition circuits 2 to 5 is a person to Anlogger 17 to 20, busy to igniter to the respective bus lines 6 to 9.
  • the Anlogger 17 is just about to log an igniter 14 with its ignition line 15 in a connection point 16 to the bus line 6 of the ignition circuit 2.
  • the logger 20 wants to proceed.
  • Each of the loggers 17 to 20 has a transmitting and receiving device, a log data transmitter 21 having its own identification code. These log data transmitters 21 are suitable for bidirectional contact both with the respective loggers 10 to 13 and with the log-on manager 22.
  • a simultaneous connection of detonators 14 by the logger 17 and the Anlogger 20 would come with a shunt of the igniter to a threat to data transmission.
  • both the logger 17 and the logger 20 have logged in via their log data transmitters 21 to the log-on manager 22, stating the respective identification code.
  • the log-on manager 22 may assign the loggers to the respective logger based on the identification codes of the respective log data transmitters 21.
  • the logger 17 is assigned to the logger 10 and the logger 20 to the logger 13.
  • the Anlogger 17 as symbolized by the radio contact 23, before the Anlogger 20 at Anlog Manager 22 reported, the radio contact with the dashed line 24 is symbolized, so that the Anlog Manager 22 via the indicated radio contact 25 the Logger 10 turns on and the logger 17 allows the connection of a fuze 14 before the logger 20.
  • the permission to log the igniter 14 in the connection point 16 this transmits, in the present case by means of the log data transmitter 21, also by radio, the identification code of the igniter 14 and optionally the position of the borehole to the logger 10. This data transmission is symbolized by the radio contact 26.
  • the data of the detonator is transmitted to the logger 10, this reports the proper receipt of the data on the indicated radio link 26 to the log data transmitter 21 of the Anloggers 17. This then acknowledges the successfully completed Anloggvorgang means of a signal via the radio link 23 to the Anlog Manager 22. Thereupon, via the indicated radio contact 24, the message to the log data transmitter 21 of the logger 20 with the release notification for logging the ready held detonator 14 to the bus line 9. If the igniter has been successfully connected to the bus line 9 by the logger 20, then He acknowledges this connection by means of a radio signal to the Anlog Manager 22, so that this can pass the release for logging a detonator to another Anlogger.
  • the detonators are programmed with regard to their time delay from the ignitor or the tripping device, the so-called blaster 27.
  • This can be connected via lines 28 to 31 to the respective ones Loggers 10 to 13 connected. But it may also, as not shown here, a radio link between the blaster 27 and the respective loggers exist. Furthermore, there is a connection via a line 32 or via an indicated radio link 33 between the blaster 27 and the log-on manager 22.
  • the log-on manager 22 is equipped to separately switch the loggers 10 to 13 on and off when from the blaster 27 in the respective ignition circuits 2 to 5, for example, the delay times in the detonators 14 are to be stored.
  • first of the blaster 27 is a message to the log-on manager 22, which is the logger 10 to 13 of the ignition circuits 2 to 5 to be addressed.
  • the log-on manager 22 has entered via the radio contact 34 indicated here with the logger 10 in connection and has turned it on to receive the data from the blaster 27, while the other wireless contacts 35, the subsequent loggers 11 to 13 connected will not be able to receive data specific to logger 10 only.
  • the detonators can be ignited by the blaster 27 via the respective loggers.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)
  • Ignition Installations For Internal Combustion Engines (AREA)
  • Lighting Device Outwards From Vehicle And Optical Signal (AREA)
  • Debugging And Monitoring (AREA)

Claims (12)

  1. Procédé de raccordement d'amorces (14) à un système de mise à feu (1) qui se compose de plusieurs circuits de mise à feu (6-9) où une pluralité d'amorces sont raccordées aux bus (2-5) respectifs partant d'un enregistreur (10-13) connecté à l'unité de déclenchement (27) qui est associée à tous les enregistreurs et à partir de laquelle les amorces (14) sont allumées dans un ordre chronologique prédéterminé, suite à une instruction d'allumage, caractérisé par le fait qu'il est prévu un gestionnaire de raccordement (22) qui est en contact bidirectionnel avec les enregistreurs (10-13), l'unité de déclenchement (27) et les moyens de transmission de données de raccordement (17-20) des enregistreurs qui transmettent les données des amorces (14) à l'enregistreur (10-13); par le fait que lors du raccordement des amorces aux bus (2-5) des circuits de mise à feu (6-9) du système de mise à feu, l'opérateur de raccordement (17-20), c'est-à-dire la personne effectuant le raccordement des amorces, appelle le gestionnaire de raccordement (22); par le fait que le gestionnaire (22) identifie l'opérateur de raccordement (17-20) à l'aide d'un code d'identification qui lui est associé et l'affecte à l'enregistreur (10-13), au bus (2-5) duquel l'opérateur de raccordement (17-20) souhaite raccorder les amorces (14); par le fait que le gestionnaire de raccordement (22) vérifie si, à l'instant de l'appel, une amorce (14) est raccordée et si des données sont transmises; par le fait qu'en l'absence de transmission de données, l'enregistreur (10-13) associé au bus (2-5) est commuté sur réception en vue de la transmission des données de l'amorce (14) à raccorder; par le fait que si une autre amorce (14) est déjà en cours de raccordement, le gestionnaire de raccordement (22) envoie au dispositif de transmission de données de raccordement (21) un message lui indiquant qu'une transmission de données est impossible; par le fait que le raccordement de l'amorce (14) à l'enregistreur (10-13) associé n'est autorisé que si la transmission de données de l'autre amorce (14) est terminée; et par le fait que les données transmises par les amorces (14) constituent la base pour l'ordre chronologique de l'allumage des différentes amorces (14).
  2. Procédé selon la revendication 1, caractérisé par le fait que lors de l'appel de l'opérateur de raccordement, avec son code d'identification, le gestionnaire de raccordement s'adresse directement à l'enregistreur concerné et, lorsque celui-ci n'est pas occupé par une transmission de données, le commute à la réception des signaux du moyen de transmission de données de raccordement associé à l'enregistreur, respectivement à la réception des données d'une amorce qui se manifeste spontanément lors du raccordement au bus.
  3. Procédé selon la revendication 1 ou 2, caractérisé par le fait que lorsque l'opérateur de raccordement a reçu du gestionnaire de raccordement la confirmation qu'il peut raccorder l'amorce au bus, il réalise ce raccordement de l'amorce et le confirme par la transmission du code d'identification.
  4. Procédé selon la revendication 3, caractérisé par le fait que la position de l'amorce raccordée dans le système de mise à feu est transmise au gestionnaire de raccordement.
  5. Procédé selon une des revendications 1 à 4, caractérisé par le fait que lorsque deux ou plus de deux opérateurs de raccordement appellent le gestionnaire pour raccorder des amorces, le gestionnaire insère les appels dans une boucle d'attente en fonction de leur ordre d'arrivée, indique le cas échéant la position d'attente et n'autorise ensuite une opération de raccordement que si une opération de raccordement précédente d'une amorce a été achevée avec succès ou si la prise de connaissance du message d'erreur d'un raccordement non correct a été confirmée.
  6. Procédé selon une des revendications 1 à 5, caractérisé par le fait que lorsque les données transmises lors du raccordement sont incomplètes ou erronées, l'enregistreur indique l'erreur au moyen de transmission de données de raccordement et ladite erreur est signalée sur le moyen de transmission de données de raccordement ou est visualisée sur un moyen d'affichage de celui-ci.
  7. Procédé selon une des revendications 1 à 6, caractérisé par le fait que si un opérateur de raccordement a raccordé une amorce avec succès à un bus, l'enregistrer confirme cela par un signal de confirmation sur le moyen de transmission de données de raccordement, puis l'opérateur de raccordement indique au gestionnaire que le raccordement a été effectué avec succès.
  8. Procédé selon une des revendications 1 à 6, caractérisé par le fait que si un opérateur a raccordé une amorce avec succès à un bus, l'enregistreur le signale directement au gestionnaire de raccordement et un signal correspondant apparaît sur le moyen de transmission de données de raccordement.
  9. Procédé selon une des revendications 1 à 8, caractérisé par le fait que la transmission des temps de retard de l'unité de déclenchement, via les enregistreurs, aux différentes amorces est coordonnée par le gestionnaire de raccordement qui affecte une adresse non seulement aux différentes amorces mais aussi à l'unité de déclenchement et aux enregistreurs, en vue d'une réponse individuelle, par le fait que la transmission des données est régulée par le gestionnaire de raccordement de manière telle que l'unité de déclenchement ne s'adresse toujours qu'à un seul enregistreur et ce dernier ne s'adresse toujours qu'à une seule amorce et les autres enregistreurs sont bloqués, et par le fait que lorsque la transmission de données de l'unité de déclenchement à l'enregistreur concerné et de là aux amorces est terminée, l'enregistreur signale au gestionnaire de raccordement la réception correcte des données par les amorces, et par le fait qu'à la fin de la programmation des amorces connectées à un enregistreur, cet enregistreur est coupé par le gestionnaire et l'enregistreur suivant est commuté sur réception.
  10. Procédé selon une des revendications 1 à 9, caractérisé par le fait que la transmission des signaux entre le gestionnaire de raccordement et les moyens de transmission de données de raccordement s'effectue de manière bidirectionnelle par radiotechnique.
  11. Procédé selon une des revendications 1 à 10, caractérisé par le fait que la transmission des signaux entre le gestionnaire de raccordement et les enregistreurs s'effectue de manière bidirectionnelle par radiotechnique.
  12. Procédé selon une des revendications 1 à 11, caractérisé par le fait que la transmission des signaux entre le gestionnaire de raccordement et l'unité de déclenchement s'effectue de manière bidirectionnelle par radiotechnique.
EP01982381A 2000-09-30 2001-09-28 Procede pour le raccordement d'amorces a un systeme de mise a feu Expired - Lifetime EP1325282B1 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
DE10048707 2000-09-30
DE10048707 2000-09-30
DE10147726 2001-09-27
DE10147726A DE10147726A1 (de) 2000-09-30 2001-09-27 Verfahren zum Anschluß von Zündern an ein Zündsystem
PCT/EP2001/011275 WO2002031431A1 (fr) 2000-09-30 2001-09-28 Procede pour le raccordement d'amorces a un systeme de mise a feu

Publications (2)

Publication Number Publication Date
EP1325282A1 EP1325282A1 (fr) 2003-07-09
EP1325282B1 true EP1325282B1 (fr) 2007-08-08

Family

ID=26007236

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01982381A Expired - Lifetime EP1325282B1 (fr) 2000-09-30 2001-09-28 Procede pour le raccordement d'amorces a un systeme de mise a feu

Country Status (8)

Country Link
EP (1) EP1325282B1 (fr)
AT (1) ATE369540T1 (fr)
AU (2) AU1398002A (fr)
CA (1) CA2423936C (fr)
DE (2) DE10147726A1 (fr)
ES (1) ES2291364T3 (fr)
WO (1) WO2002031431A1 (fr)
ZA (1) ZA200302767B (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4143499B1 (fr) * 2020-04-29 2024-06-19 Detnet South Africa (Pty) Ltd Détermination de position de détonateur

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6941870B2 (en) 2003-11-04 2005-09-13 Advanced Initiation Systems, Inc. Positional blasting system
AU2006207830B2 (en) * 2005-01-24 2011-05-19 Orica Australia Pty Ltd Wireless detonator assemblies, and corresponding networks
ES2378893T3 (es) * 2005-02-16 2012-04-18 Orica Explosives Technology Pty Ltd Aparato de voladura de seguridad mejorada con analizador biométrico y método de voladura
FR2984484B1 (fr) * 2011-12-19 2018-06-15 Davey Bickford Systeme de mise a feu de plusieurs ensembles de detonateurs electroniques
US12025420B2 (en) 2020-05-15 2024-07-02 Detnet South Africa (Pty) Ltd Blasting system

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5295438A (en) * 1991-12-03 1994-03-22 Plessey Tellumat South Africa Limited Single initiate command system and method for a multi-shot blast
EP0604694A1 (fr) * 1992-12-31 1994-07-06 Union Espanola De Explosivos S.A. Dispositif électronique pour détonations successives
GB9423313D0 (en) * 1994-11-18 1995-01-11 Explosive Dev Ltd Improvements in or relating to detonation means
US5714712A (en) * 1996-10-25 1998-02-03 The Ensign-Bickford Company Explosive initiation system
EP0897098A3 (fr) * 1997-08-13 1999-12-15 SMI Technology (Pty) Limited Système de mise à feu avec un contrÔleur connectable par moyen de câbles électriques
US6079333A (en) * 1998-06-12 2000-06-27 Trimble Navigation Limited GPS controlled blaster
WO2000009967A1 (fr) * 1998-08-13 2000-02-24 Expert Explosives (Proprietary) Limited Dispositif de tir
DE19945790A1 (de) * 1998-10-29 2000-05-04 Dynamit Nobel Ag Zündeinrichtung für Zünder, die mittels Funk auslösbar sind und Verfahren zum Auslösen dieser Zünder
SE515809C2 (sv) * 2000-03-10 2001-10-15 Dyno Nobel Sweden Ab Förfarande vid avfyring av elektroniksprängkapslar i ett detonatorsystem samt ett detonatorsystem innefattande elektroniksprängkapslarna

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4143499B1 (fr) * 2020-04-29 2024-06-19 Detnet South Africa (Pty) Ltd Détermination de position de détonateur

Also Published As

Publication number Publication date
DE50112840D1 (de) 2007-09-20
ATE369540T1 (de) 2007-08-15
DE10147726A1 (de) 2002-07-25
ES2291364T3 (es) 2008-03-01
AU2002213980B2 (en) 2007-04-26
EP1325282A1 (fr) 2003-07-09
ZA200302767B (en) 2005-10-26
CA2423936C (fr) 2009-08-11
CA2423936A1 (fr) 2003-03-27
WO2002031431A1 (fr) 2002-04-18
AU1398002A (en) 2002-04-22

Similar Documents

Publication Publication Date Title
DE69024446T2 (de) Zeitvorrichtung
DE3342430C2 (fr)
DE60216784T2 (de) Ferngesteuertes zündsystem mit frequenzdiversität
DE69021174T2 (de) Einrichtung zur Zündung von Explosivkörpern.
DE19983678B4 (de) Bohrloch-Aktivierungssystem
DE3231113A1 (de) Vorrichtung zur sequentiellen signaluebertragung
EP0093872A1 (fr) Procédé pour la transmission de valeurs mesurées dans un système de contrôle
EP1088294B1 (fr) Systeme d'automatisation avec detecteur radio
US6945174B2 (en) Method for connecting ignitors in an ignition system
EP1325282B1 (fr) Procede pour le raccordement d'amorces a un systeme de mise a feu
EP0267528B1 (fr) Système numérique de transmission de données comprenant des répéteurs adressables et des dispositifs de localisation d'erreurs
DE10084519B3 (de) Verfahren und System zum Steuern eines Spreng-Netzwerks
DE3336600A1 (de) Datenuebertragungssystem
DE10356349A1 (de) Verfahren und Einrichtung zum Sprengen von Gesteinsmassen oder dergleichen Massen Übertage oder Untertage
EP1125094B1 (fr) Dispositif d'allumage pour amorces pouvant etre declenchees par radio et procede pour declencher ces amorces
EP1234157B1 (fr) Procede d'echange de donnees entre un dispositif de programmation et de declenchement de detonateurs electroniques et lesdits detonateurs
DE2551204B2 (de) Schaltungsanordnung zur Herstellung von Datenverbindungen in Datenvermittlungsanlagen
EP0903953B1 (fr) Procédé de lecture centrale de données de consommation attachées à des sites de données distribués dans des immeubles, en particulier pour chauffage et eau chaude
DE3538484C2 (fr)
DE19945790A1 (de) Zündeinrichtung für Zünder, die mittels Funk auslösbar sind und Verfahren zum Auslösen dieser Zünder
DE2557214C2 (de) Verfahren zur Einphasung von Schlüsselgeräten im Halbduplexbetrieb ohne Hilfskanal
AT408399B (de) Einrichtung mit mehreren voneinander unabhängigen, mit von einem aussentemperaturfühlerbeaufschlagten regelgeräten versehenen heizgerät
DE1437360A1 (de) Mit Abtastung arbeitende Informationsuebertragungsanlage
DE10059988B4 (de) Verfahren zur zeitgleichen Auslösung eines Schaltvorgangs in mehreren Empfängern eines Funksystems
DE1591070A1 (de) Verfahren zur Auffindung eines Identifizierungssighals einer Station in einem Teilzeit-Vielfachzutritt-Satelliten-Nachrichtensystem

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030502

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: DYNAMIT NOBEL GMBH EXPLOSIVSTOFF- UND SYSTEMTECHN

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REF Corresponds to:

Ref document number: 50112840

Country of ref document: DE

Date of ref document: 20070920

Kind code of ref document: P

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: ORICA EXPLOSIVES TECHNOLOGY PTY LTD

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

NLT2 Nl: modifications (of names), taken from the european patent patent bulletin

Owner name: ORICA EXPLOSIVES TECHNOLOGY PTY LTD

Effective date: 20071128

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
ET Fr: translation filed
REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2291364

Country of ref document: ES

Kind code of ref document: T3

GBV Gb: ep patent (uk) treated as always having been void in accordance with gb section 77(7)/1977 [no translation filed]

Effective date: 20070808

BERE Be: lapsed

Owner name: DYNAMIT NOBEL G.M.B.H. EXPLOSIVSTOFF- UND SYSTEMT

Effective date: 20070930

REG Reference to a national code

Ref country code: IE

Ref legal event code: FD4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070930

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071109

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080108

Ref country code: IE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: GB

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20080509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070928

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070928

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20070930

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170920

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20171002

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20180828

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20180910

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 50112840

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190402

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20191104

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180929

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190929

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190930