EP2782428B1 - Installation d'éclairage de secours dotée d'une fonction d'interface vers des systèmes de gestion technique de bâtiment et procédé de communication associé - Google Patents

Installation d'éclairage de secours dotée d'une fonction d'interface vers des systèmes de gestion technique de bâtiment et procédé de communication associé Download PDF

Info

Publication number
EP2782428B1
EP2782428B1 EP14160816.6A EP14160816A EP2782428B1 EP 2782428 B1 EP2782428 B1 EP 2782428B1 EP 14160816 A EP14160816 A EP 14160816A EP 2782428 B1 EP2782428 B1 EP 2782428B1
Authority
EP
European Patent Office
Prior art keywords
data
lighting system
interface device
contact
emergency lighting
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.)
Active
Application number
EP14160816.6A
Other languages
German (de)
English (en)
Other versions
EP2782428A3 (fr
EP2782428A2 (fr
Inventor
Roland Pasedag
Frank Dr. phil. nat. Ranostaj
Matthias Harms
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.)
RP Technik GmbH Profilsysteme
Original Assignee
RP Technik GmbH Profilsysteme
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 RP Technik GmbH Profilsysteme filed Critical RP Technik GmbH Profilsysteme
Priority to PL14160816T priority Critical patent/PL2782428T3/pl
Publication of EP2782428A2 publication Critical patent/EP2782428A2/fr
Publication of EP2782428A3 publication Critical patent/EP2782428A3/fr
Application granted granted Critical
Publication of EP2782428B1 publication Critical patent/EP2782428B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B5/00—Visible signalling systems, e.g. personal calling systems, remote indication of seats occupied
    • G08B5/22—Visible signalling systems, e.g. personal calling systems, remote indication of seats occupied using electric transmission; using electromagnetic transmission
    • G08B5/36—Visible signalling systems, e.g. personal calling systems, remote indication of seats occupied using electric transmission; using electromagnetic transmission using visible light sources
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
    • H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
    • H05B47/10—Controlling the light source
    • H05B47/105—Controlling the light source in response to determined parameters
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
    • H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
    • H05B47/10—Controlling the light source
    • H05B47/175—Controlling the light source by remote control
    • H05B47/19—Controlling the light source by remote control via wireless transmission
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
    • H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
    • H05B47/20—Responsive to malfunctions or to light source life; for protection
    • H05B47/21—Responsive to malfunctions or to light source life; for protection of two or more light sources connected in parallel
    • H05B47/22—Responsive to malfunctions or to light source life; for protection of two or more light sources connected in parallel with communication between the lamps and a central unit
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B7/00—Signalling systems according to more than one of groups G08B3/00 - G08B6/00; Personal calling systems according to more than one of groups G08B3/00 - G08B6/00
    • G08B7/06—Signalling systems according to more than one of groups G08B3/00 - G08B6/00; Personal calling systems according to more than one of groups G08B3/00 - G08B6/00 using electric transmission, e.g. involving audible and visible signalling through the use of sound and light sources
    • G08B7/062—Signalling systems according to more than one of groups G08B3/00 - G08B6/00; Personal calling systems according to more than one of groups G08B3/00 - G08B6/00 using electric transmission, e.g. involving audible and visible signalling through the use of sound and light sources indicating emergency exits

Definitions

  • the present invention relates to an emergency lighting system in which a plurality of emergency lights, such as a first emergency light and a second emergency light, both of which can communicate with one another and with other radio subscribers such as a central control system via a radio link, can be connected via an interface device to wired building control systems or building control devices such as building management systems . Furthermore, the present invention relates to a data transmission through which the data of the one system, e.g. B. the emergency lighting system to the other system, for. B. can be transferred to a fire alarm system. In addition, the present invention relates to a measure for inserting a special activation signal such as an activation bit in a data structure such as a data tuple of an emergency lighting system.
  • a special activation signal such as an activation bit in a data structure such as a data tuple of an emergency lighting system.
  • the present invention also deals with the interface device, which is equipped with the functions and capabilities mentioned above, the transition connection point from the one building system, e.g. B. the emergency lighting system to the other building management system, e.g. B. represents the fire alarm system.
  • the present invention relates to emergency lighting systems according to the preamble of claim 1, a method for notifying a building control system about data from an emergency lighting system according to the preamble of patent claim 18 and an interface device according to the preamble of patent claim 19.
  • Examples are the quite central standards DIN EN 50172 and DIN EN 50171, which u. a. be observed in the Federal Republic of Germany.
  • emergency lighting systems may at least partially include emergency lighting such as permanent lighting (permanent lighting emergency) or standby lighting (emergency lighting in standby mode), which, primarily in the form of a single battery lamp, equipped with radio modules controlled by those modules, switched on, switched off and can be monitored, there are other building systems such as fire alarm systems that can still be implemented wired between their individual participants.
  • emergency lighting such as permanent lighting (permanent lighting emergency) or standby lighting (emergency lighting in standby mode)
  • emergency lighting such as permanent lighting (permanent lighting emergency) or standby lighting (emergency lighting in standby mode)
  • At least some older or already installed emergency lighting systems operate with emergency lights, all of which are connected to supply cables such as NYM cables and supplied from a central emergency power source to form a cable-bound overall system.
  • the DE 10 2007 024 422 A1 presents a luminaire that should be used as a safety or escape sign luminaire and has a slot for a plug-in module.
  • the plug-in module can be a radio module such as a Bluetooth radio module or a WLAN radio module. Thanks to the modularity described there, it is possible to use the light with a radio module as well without delivering such radio modules.
  • the luminaire is realized with a "backplane".
  • the German patent application only discusses individual mechanical and structural aspects of a corresponding luminaire without examining the overall system in more detail. With regard to the representation of what an emergency light luminaire can look like, this patent application is fully incorporated in the present description.
  • An emergency lighting system is described in more detail as an example of the commercially available systems.
  • Such a system is offered by the ETAP group of companies under the name "ETAP Safety Manager".
  • a coordinator KH12 must be installed as a communication device in the (radio-based) emergency lighting system, whose communication is based on the IEEE 802.15.4 standard with a transmission power of 1 mW in a frequency range of 2.4 GHz .
  • a certain number of safety lights is assigned to such a coordinator KH12.
  • the coordinator KH12 offers a cable connection interface for the construction of the ESM bus internal to the emergency lighting system.
  • Another lighting system with LED lights is from the US 2010/271 802 A1 (Inventor: MV Recker et al .; publication date: October 28, 2010) known, which in numerous examples, such as. B. in Figure 11, a control unit and locally separated from it describes one or more wireless LED light bulbs.
  • a control takes place via a radio frequency (RF), which can be received and decoded in a receiver of the LED light bulb. Additional sensors can be integrated into the lighting system.
  • the (LED) light bulbs should be able to establish communication via a building management unit. Interfaces and interface components are shown on some components of the lighting system.
  • a designated interface device appears in the entire description of the US 2010/271 802 A1 not to be addressed, but only the installation of an interface such as a USB connector, e.g. B.
  • a smoke detector with acoustic alarm device is the subject of DE 203 09 338 U1 (Owner: Axel Benkhardt; registration date: September 11, 2003).
  • the smoke detector should be equipped with a programmable voice module in order to send messages to people in the event of a fire, so that these people can more easily get to safety. It is also proposed that the smoke detector can switch a transmitter on or off in order to send control signals to a receiver by radio.
  • the devices are to be equipped with components for wireless communication and enable the transmission of monitoring parameters, even when the monitored devices are switched off.
  • a data transmission via intermediary units to a server can be carried out using known network technology.
  • the WO 2012/023 087 A1 (Applicant: Koninklijke Philips Electronics NV; Date of publication: February 23, 2012) shows that a system for monitoring by means of radar units, for. B. can be integrated into street lamps of street lighting, so that each street lamp comprises a transmitter unit. These units can now interfere with each other. Frequency covers which can be caused by noise in the sidebands are mentioned as a notable source of error.
  • the company deals with the use of commands according to the "DALI protocol" (Digital Addressable Lighting Interface) in wireless networks for monitoring lighting systems for home, office and public areas WO 2013/016 534 A1 (Applicant: Verified Energy, LLC; publication date: January 31, 2013).
  • DALI protocol Digital Addressable Lighting Interface
  • the US 2008/224 026 A1 (Applicant: Barton A. Pasternak; publication date: September 18, 2008) is concerned with a lighting system in which the lighting on different floors of a building is switched sequentially, with sequential activation using radio frequencies. In safety-relevant situations, however, the control intended to save energy should be switched off.
  • the object of the invention is achieved by an emergency lighting system according to claim 1.
  • Advantageous communication methods and methods for notifying a building control system about data from an emergency lighting system by means of a corresponding interface device are presented in claim 18.
  • An interface device for the emergency lighting system is presented in claim 19.
  • Advantageous further developments can be found in the dependent claims.
  • the emergency lighting system is a distributed lighting system that is equipped with various lights, such as. B. emergency lights in permanent switching or emergency lights in standby lighting or with safety lights, is built, it should be - due to the control or communication system of the emergency lighting system used - if a larger number of lights, for. B. fifty or more lights, belong to the emergency lighting system.
  • Emergency lighting systems in which at least some of the luminaires are designed as single-battery luminaires, have a particularly low susceptibility to external influences damaging the supply lines (fire, vandalism, earthquakes, mechanical vibrations).
  • a single battery lamp has its own Emergency power supply such as an accumulator, which provides energy for a lighting device for the self-contained luminaire, if via a supply cable such. B. Mains cable does not have sufficient supply voltage.
  • the emergency lighting system has at least one excellent interface, which is created by an interface device. If there are to be interfaces to several other building management systems (e.g. to a fire alarm system and an intrusion alarm system), of course, several interface devices can also be part of the emergency lighting system. However, it is also advantageous if an interface device offers contacts and interfaces to several other systems, so that actually not multiple interface devices are to be used just because several other building management systems are to be connected. At least the emergency lighting system includes a first emergency light and a second emergency light.
  • the interface device offers a contact group equipped with safety functions and less sensitive to interference.
  • Different devices of the emergency lighting system are connected to each other via a radio channel. It is often expedient to have a center via which communication that has taken place between the radio subscribers can be stored or visualized or archived or made accessible. It can e.g. B. a single frequency can be selected on which all radio participants of an emergency lighting system communicate (e.g. 868 MHz). Another emergency lighting system, e.g. B. on another floor of a building, can communicate on a slightly different frequency, e.g. B. to 870 MHz. It is particularly advantageous if the radio subscribers of an emergency lighting system exchange their data on a common radio channel. Here, data from different radio subscribers can be stored in a combined data set, e.g. B.
  • the data tuple can be a data tuple, transmitted from one radio subscriber to a second radio subscriber.
  • the transmission of the data tuple provides information or contains data from several radio subscribers, ideally from all radio subscribers of the emergency lighting system, i.e. H. in an embodiment of all emergency lights of the emergency lighting system, of all interface devices of the emergency lighting system and of a central device such as a computer.
  • only a single data tuple in the control center has to be broken down into its objects in order to obtain information about all radio subscribers.
  • the interface device has several function modules.
  • a function module is a radio module.
  • a possible connection point is one comprising two individual contacts
  • the radio module communicates with other similar transmitters and receivers of the emergency lights belonging to the emergency lighting system.
  • the radio module forms a radio node between several radio nodes present in the emergency lighting system.
  • An output contact in particular on a communication board of the interface device, is designed as a collective fault contact.
  • the collective fault contact can come into an switched-on state, although there may be a voltage interruption in a control circuit of a switch of the collective fault contact.
  • Such behavior of the collective fault contact can also be referred to as a collective fault contact with a "fail-safe". Even if it should happen that there is insufficient voltage at the interface device, an interference-free state can still be assumed.
  • the emergency lighting system is designed as a "multi-hop system".
  • the communication paths do not have to be established right from the start.
  • the data tuple is passed on from radio subscriber to radio subscriber. Provides the control computer of a radio subscriber, for. If, for example, the calculation logic of an emergency light luminaire determines that the data tuple obtained does not have the most current data for the device that houses the radio subscriber, the part of the data tuple assigned to the device is updated first and only then is the data tuple with the most up-to-date values possible forwarded.
  • the interface device works in the same way.
  • the interface device also takes up a data tuple, secondly clarifies whether anything in the data tuple needs to be updated, thirdly puts its data into the data tuple or into the data tuple and finally sends the data tuple for the radio module (if possible to everyone) other radio subscribers.
  • the interface device as a radio node thus promotes communication between the other radio participants by itself representing a point, a step or a jump point or a node for the transmission after the received data tuple has been updated. It makes sense if the data tuple can communicate operating states, malfunctions and operating times of individual emergency lights to other radio users. So z. B. based on the operating time, an expected remaining light duration can be estimated. On the basis of a message relating to the operating state, it can be "fed back" whether a switch-on or a switch-off command has actually caused the requested reaction in the activated emergency light lamp.
  • the interface device can also be viewed as a monitored radio node, which identifies a number of different sources of interference at a specially designated contact, the collective interference contact.
  • the data tuple which has or includes data from several emergency lights, is not only sent again by the other emergency lights, but also by the interface device.
  • the interface device could also be referred to as a repeater.
  • the collective fault contact can be used as a transition point for a telecommunications unit.
  • At least one collective fault contact is helpful as an interface. If another building management system, such as a fire alarm system or a key switch, is to influence the emergency lighting system without the entire emergency lighting system being exposed to a risk of permanent damage, an input contact is one of the few, in one configuration, e.g. B. as the only, liaison (s) beneficial.
  • An emergency lighting system can also be described using its individual components.
  • the emergency lighting system is set z. B. together in an embodiment of three or more emergency lights, an interface device, a central device for radio-based communication and a central control logic.
  • the emergency lighting system operates with its own radio channel.
  • all information which is intended for the emergency light lamps or which is sent back by the emergency light lamps is transmitted on this radio channel. Status data are therefore exchanged via this radio channel.
  • Various radio subscribers hear the radio channel, e.g. B. equipped with radio modules from emergency lights. If a status signal such as the switching on of all lights is transmitted, the emergency lights react by switching their lights on immediately.
  • the interface device also represents a radio node. The interface device enriches or extends the radio network, which is composed of the radio subscribers.
  • the input contact is a galvanically decoupled wide-range voltage contact.
  • The can be connected to a wide-range voltage contact various building management system devices can be connected.
  • a voltage swing is considered to be a wide-range voltage, which starts at least above a protective extra-low voltage (e.g. 63 volts) and extends into the usual luminous power supply voltage range (e.g. 232 volts). In one embodiment, this would be a voltage range from 64 volts to beyond 230 volts.
  • a protective extra-low voltage e.g. 63 volts
  • luminous power supply voltage range e.g. 232 volts
  • this would be a voltage range from 64 volts to beyond 230 volts.
  • Different fire alarm systems work with different voltages to indicate to other devices that a fire alarm priority has occurred.
  • the input contact is expediently designed as a contact for switching on all emergency lights and ensures that information on the input contact is given preferential treatment or priority.
  • input information e.g. B.
  • a switching pulse or a continuous voltage can turn on at least some of the emergency lights of the emergency lighting system in the sequence. Due to the design as a galvanically isolated contact, the input contact is protected against incorrect wiring, interference from the other building management system or other voltage peaks.
  • a fastener is available on the input contact for connecting cables.
  • An emergency light that is the first to emit a data tuple does this on a radio channel.
  • the first emergency light luminaire picks up the data from the second emergency light luminaire and combines it with its data to form a revised data tuple that can be sent out again.
  • Each emergency light lamp works as a radio node for the other radio participants on the radio channel.
  • the interface device also picks up the received data tuples and forwards them if necessary, updated.
  • the interface device partly takes on the function of a repeater.
  • a data tuple that is broken down into its objects when it arrives at a destination can be called a monitoring tuple.
  • a data tuple can be a transmission tuple at one point in time and a monitoring tuple at another, in particular later point in time.
  • the implementation of the data from the emergency lighting system to the other Building management system, e.g. B. to the fire alarm system, is carried out by a data conversion.
  • the data conversion converts the data from the emergency lighting system into a form that can be processed by the fire alarm system.
  • a communication path for the data takes place over several stations.
  • Data from at least one emergency light lamp is intercepted by radio from the interface device.
  • the interface device has a radio module.
  • the data is recorded via the radio module.
  • the data is then passed through the interface device in processed form and made available at the collective fault contact.
  • the collective fault contact can also be called a sum connection.
  • the data is therefore forwarded in an integrated or compressed form.
  • a microcontroller is provided in the interface device.
  • the microcontroller is programmed so extensively that it can perceive different sources of interference.
  • the microcontroller can identify at least two sources of interference of different types (e.g. a calculation error in the microcontroller itself as the first source of interference and untrustworthy data of a data tuple as the second source of interference, for example using checksums). If a source of interference overlays the data of a data tuple with the weight that an undisturbed reception can no longer be assumed, the logic of the microcontroller can determine this situation, the situation of the untrustworthy data of a data tuple.
  • the microcontroller identifies the presence of at least one source of interference or the intervention in data of a data tuple.
  • Control information should be able to be integrated into the data direction from the other building management system into the emergency lighting system.
  • An activation signal can be integrated in this way.
  • the input on the interface device can e.g. B. be designed as an input for a fire alarm signal. Such a design is therefore a fire alarm input.
  • the activation signal is to be integrated in a data tuple of an emergency lighting system. The activation signal can become part of the data tuple.
  • the individual components and assemblies of the emergency lighting system can communicate with each other.
  • radio data exchange takes place between emergency lights in the emergency lighting system.
  • One emergency light lamp exchanges its data tuple with another emergency light lamp.
  • the interface device acts as whether it would be a further emergency light luminaire, although it can be seen from the supplemented data in the data tuple that it is an interface device.
  • the interface device receives a data tuple via its radio module. It is first checked whether the data tuple is to be regarded as a processable data tuple, i.e. whether there are sufficient, valid-looking data components in the data tuple. The validity can e.g. B. on the basis of checks and checksums that have been met or met.
  • the data tuple is temporarily stored in a memory managed by a microcontroller intended for processing. Thus, the data tuple is available over a longer period, e.g. B.
  • Information about a signal that is present at the fire alarm input is inserted into the data tuple.
  • the data tuple is thus supplemented by further information.
  • An object in the data tuple that does not previously exist or has not passed a validity test is updated.
  • an actuality stamp can be built into the data tuple for each object, or at least for the entire data tuple.
  • the data tuple to be regarded as revised is offered to the neighboring or the other radio subscribers.
  • the data tuple which is preferably provided with a timed update stamp, ie with an update stamp adapted to the time given at the time of processing, is made available to further radio subscribers of the emergency lighting system via the radio module.
  • the radio module receives a data tuple, a microcontroller processes the data tuple and the radio module sends out the more current data tuple again.
  • the interface device in which both the previously described data conversion and the insertion of an activation signal into a data tuple can ideally be carried out, has a microcontroller for these tasks.
  • the microcontroller includes program routines that can perform data conversion.
  • the same microcontroller includes program routines that fill the data tuple.
  • the radio module connected to the microcontroller collects data tuples and sends out data tuples processed by the microcontroller. Before sending out a data tuple, the information in the data tuple is updated, revised or adapted to the latest events on the interface device.
  • the interface device significantly reduces the risk of mutual interference between the different building management systems.
  • a further risk of errors and poorly functioning mutual controls of the different building management systems is reduced by the fact that due to the collection of the most diverse faults on a collective fault contact, data overload and unnecessary information transfer are prevented.
  • the information from one building management system can be easily monitored by the other building management system. Sophisticated analysis systems, which could have occurred in the other building management system, are no longer required because the information has been reduced to the bare minimum.
  • Another function module is a circuit board for cable-guided signals, impulses, switching or control information.
  • the different function modules can be set apart from one another.
  • all function modules of the interface device can be integrated in a circuit board. Structurally, functionally or in terms of layout, at least two blocks or areas can be identified in the interface device, a radio module and a communication board. Other areas, such as B. for a long-distance bus such as an RS-232 bus, may be present in the interface device.
  • the communication board represents the link to the cable-based connections of other devices or other building management systems.
  • An electrical line connection is preferably provided between the radio module of the interface device and the communication board.
  • an electronic part is provided in the interface device for the connection of further building control systems, which can be referred to as a communication board.
  • This part of the interface device can be divided into a separate assembly, so this part can be viewed as a separate section for communication.
  • Connection lines are present between the radio module and the section that can be referred to as the communication board.
  • the communication board has contacts that are accessible from the outside. In one embodiment, the contacts can be used as input contacts. In another embodiment, the contacts are to be used as output contacts. Entrance or exit are determined on the basis of the direction of information flow, whether a signal should be transmitted via the contact from the interface device (output contact) or whether a signal should be transmitted via the contact into the interface device (input contact).
  • the communication board takes over hardware filter tasks.
  • the other building management system must be notified in response to the presence of at least one source of interference.
  • the other building management system is thus aware that there is some kind of malfunction in the emergency lighting system.
  • the reporting of faults can be connected to a timer or a timer. Only if, after a particularly stable design of the interface device, at least for a minimum period of z. B. several seconds, i.e. less than 10 seconds, there is a fault, the collective fault contact is switched.
  • the collective fault contact is designed as a connection point for communication cables.
  • the operation is carried out at a simple (voltage) level.
  • the building management system can thus be a wired building management system, at least with regard to its fault input.
  • the output contact offers, as a collective fault contact, in particular at least two fastening elements such as spring terminal strips, luster terminals, screw terminals or plug contact terminals.
  • the common fault contact comprises an electromagnetic component that can implement the function of an electrical changer.
  • a typical changeover contact for the application in question is an electromagnetic relay with a contact tongue that switches back and forth between changeover contacts depending on the current level.
  • Such a relay can also be implemented electronically.
  • Particularly low resistances via the changeover contacts e.g. below 10 ohms are favorable, so that the collective fault contact can be available as a contact loop for the other building management system.
  • inductive and capacitive influences caused by the changeover contact should be negligible.
  • Particularly advantageous emergency lighting systems include various lights.
  • a The stand-by lights are a separate category of lights.
  • the emergency lights in the standby mode only switch on if the emergency lighting system has detected a special malfunction or a special (switching) pulse.
  • the presence of standby light lamps reduces the power consumption in phases in which no special switch-on request has been forwarded to a control center of the emergency lighting system via the interface device.
  • an interface device that has both a collective fault contact and a fire alarm contact is advantageous.
  • the interface device comprises several contacts.
  • a contact is the collective fault contact.
  • a contact is the fire alarm contact.
  • the interface device is provided in its own housing so that it is protected as much as possible. So that the interface device can be set up at a location where the interface device can possibly also act as a repeater, the interface device should be an independent electronic device.
  • the interface device is independent.
  • the interface device is also a radio subscriber. However, the interface device is a radio subscriber that can be arranged at a different location than the other radio subscribers.
  • the interface device is installed in a top-hat rail housing. More specifically, the interface device encompasses the top-hat rail housing.
  • the interface device is not intended to illuminate a room, although it can have individual LEDs.
  • the interface device should therefore be attached to places where it is not intended for the production of illuminated areas, but as part of improving communication via the radio channel.
  • the interface device is therefore developed for an area that is usually not intended for illumination.
  • the interface device can also be called a dark area device, because it should be installed in areas such as B. in control cabinets that are dark or not illuminated in regular operation.
  • a microcontroller can be present in the interface device as an electronic assembly between the radio module on the one hand and the collective fault contact on the other hand.
  • the microcontroller acts on the collective fault contact in such a way that the collective fault contact changes its state by controlling the microcontroller, e.g. B. by changing the contact tongue from one contact to another contact of the relay.
  • the collective fault contact should be as low a fault as possible.
  • a contact becomes a contact that is as interference-free as possible when a predetermined state can be assumed by the collective fault contact, which can also be reached when there is no current or a falling voltage.
  • a fail-safe contact can be realized by an inverse working control circuit for the actuation of the switching part of the contact (e.g. in the form of an operating high control circuit to be held, which causes negative (low) information of the collective fault contact). If the collective fault contact is a connection loop, the z. B. is realized electromechanically with the aid of a relay, any signal sequence can be returned to itself from the other building management system via the connection loop. The emergency lighting system does not need any precautions that deal with how the other building management system internally signals a detected fault.
  • the common fault contact closes a loop that z. B. is guided via a first cable from an output of the control center of the other building control system to the first contact of the common fault contact and is returned from a second contact via a second cable to the control center of the other building control system.
  • Such an electrical loop realized by means of electromechanical components, is considered to be particularly insensitive to faults.
  • the interface device has at least two pairs of output contacts, that is to say at least four output contacts, two of which belong to one output.
  • the interface device has at least two input contact pairs, ergo at least four input contacts. Two input contacts are always combined to form one input. Both the interface device as a whole, as well as the one input with respect to the other input or the one output with respect to the other output, are particularly charge and voltage-resistant if each contact pair is galvanically decoupled or galvanically isolated from another contact pair.
  • the circuitry in the interface device is further simplified if there is only one power supply module as an input voltage circuit. All modules, circuit boards and parts of the electronics can be made from this input voltage circuit of the interface device. Several different voltages do not have to be applied to the interface device. Likewise, multiple versions of the input voltage circuits are not required.
  • the microcontroller can be designed, in particular programmed, in such a way that it works as a logical OR module. As soon as the microcontroller is designed as a logical connecting element, the microcontroller can test the different faults. If there is a fault, the collective fault contact is activated. In one embodiment, a switching pulse for the collective fault contact is caused on the basis of at least one, preferably two or more triggering events. Faults that cause the collective fault contact to react can, for. B. be a detected fault, such. B. due to an alarm signal received by radio transmission such as a fire alarm bit. Monitoring in the interface device itself, e.g. B.
  • Another cause of a signal at the collective fault contact can be a fault on a radio channel, e.g. B. finding that no transmission data tuples have arrived for a quarter of an hour. The data of the data tuple can also be analyzed. If these no longer work conclusively or if the checksum does not match the data tuple, a data bit error can lead to a reaction on the collective fault contact.
  • the microcontroller may have an additional bus connection.
  • Such bus connections can e.g. B. a connection for an RS-232 bus, for an RS-422 bus, for an RS-485 bus or for an ESA-Net bus.
  • a PCMCIA bus is helpful.
  • a USB bus is equally useful.
  • a web server interface could also be implemented with the microcontroller on the radio module. With such interfaces and bus systems, the interface device can be programmed, monitored, reconfigured or even changed by a PC.
  • the interface device can also be described in that it is an independent, independent, mountable or individually arrangable electrical or electronic box.
  • the box offers connections for cable connections.
  • the box can establish a radio communication channel.
  • the interface device can also be viewed as a transition device from wired communication, control or influencing to radio-based communication or vice versa.
  • the box decouples the wired network components from the radio-communicating network components.
  • the box is a transition device from a network, e.g. B. an emergency lighting system on another network, for. B suitable for a fire alarm system. Events, damage and uncontrollable or undesirable conditions in one network have no damaging effect on the other network.
  • the separation and encapsulation of one network from the other network by the box contributes to this.
  • the box could also be called "gateway" of two network topologies.
  • the box connects two differently communicating networks, a wired network with a wirelessly communicating network.
  • Failures and events in a measurement section on the wired side e.g. B. through a voltage path or through a voltage loop, alternatively through a current loop, can be transferred to the radio-based side using the box.
  • FIG. 1 shows a building 3.
  • Building 3 is equipped with an emergency lighting system 1.
  • the emergency lighting system 1 includes a central unit 13 and an interface device 51.
  • the emergency lighting system 1 includes the first, second and third lamps 19, 21 and 23 and a repeater 29.
  • the emergency lighting system 1 has a first unit 17 and a second unit Unit 18 equipped.
  • the second luminaire-spanning unit 18 can, as shown, be arranged in the vicinity of a luminaire 24.
  • the central unit 13 is provided for the (at least temporarily) energy supply 31.
  • the central unit 13 there is advantageously a luminaire monitor 32 which, at a first quick glance, shows the state of the emergency lighting system 1 with all the luminaires 19, 21, 23, 24 and other luminaires (not shown) in adjacent rooms and the luminaire-spanning units 17, 18 and the Repeater 29 displays.
  • the central unit 13 is preferably arranged in a first fire section 9, the fire resistance of which is produced by a separate concrete trough 5.
  • the escape corridor 7 is located in a second fire section 11, which is kept separate from the first fire section 9.
  • the interface device 51 is an independent electronic device, in particular of all other radio subscribers, such as the unit 17 that crosses the lights and the lights 19, 21, 23, 24 and the repeater 29.
  • the interface device 51 is intended to be used as a dark area device.
  • the interface device 51 is part of the emergency lighting system 1, but it does not illuminate an escape route area.
  • the interface device 51 can be mounted on a mounting rail such as a top-hat rail (not shown).
  • the interface device 51 therefore has a top-hat rail housing 53 with which the interface device 51 can be mounted on such a top-hat rail.
  • the interface device 51 is in a data exchange by means of at least one radio channel 55, via which status data can be transmitted, with a further radio subscriber, such as the unit 17 spanning the lights and the lights 19, 21, 23, 24 and the repeater 29, of the emergency lighting system 1.
  • the interface device 51 represents a radio node, communicating on the radio channel 55, the interface device 51 communicating with other radio modules 33, 34, 35, 36, 37, 38, 39.
  • the radio modules 33, 34, 35, 36, 37, 38, 39 can also be designed as high-frequency communication modules.
  • the radio module of the interface device 51 is connected to a communication board via connecting lines (not shown) connected.
  • the communication board is in turn equipped with at least one output contact 63 comprising at least two fastening means.
  • the output contact 63 is a common fault contact, which preferably comes into an switched-on state when a voltage interruption occurs in a control circuit of a switch of the common fault contact.
  • the interface device 51 can operate as a collective fault contact via the output contact 63 of the communication board.
  • the communication board is also equipped with an input contact 61.
  • the input contact 61 is a galvanically decoupled wide-range voltage contact.
  • the wide-range voltage contact which can cover voltages in a range from 50 volts to 400 volts, can be used as a fire alarm contact.
  • the emergency lights, lights 19, 21, 23 and 24, of the emergency lighting system 1 can be switched on via the input contact 61.
  • the first emergency light luminaire, also abbreviated as first luminaire 19 has a radio channel 55 via which data about a state of the second emergency light luminaire, which can also be abbreviated as second luminaire 21, can be forwarded.
  • One of the emergency lights, lights 19, 21, 23 or 24, should be configured as a standby light.
  • the interface device 51 forms a communicative connection with the fire alarm system 59 via the input contact 61 and the output contact 63.
  • the fire alarm system 59 is connected to a sensor, such as a fire sensor 65, via the connecting cable 67.
  • the high-frequency communication modules of repeaters such as repeater 29 and of lights 19, 21, 23, 24 contain intermediate memories 41 and are equipped, for example, with an antenna 46. It is advantageous if, in particular, the repeater 29 is equipped with two or more antennas spaced from one another in order to be able to carry out the communication transmission from another position in the event of impairment of reception or due to high-frequency emission due to interference.
  • Another antenna 46 ' is part of the high-frequency communication module 34.
  • the individual lights 19, 21, 23, 24 each have their own high-frequency communication module 36, 37, 38, 39.
  • the monitoring data of the individual lights 19, 21, 23, 24 and the other network nodes in the form of the luminaire-spanning units 17, 18 and the repeater 29 are passed on to the central unit 13 with the aid of the high-frequency communication modules 34, 35, 36, 37, 38, 39 and the transmission modules 40, 40 '.
  • the central unit 13 comprises at least one high-frequency communication module 33
  • the synchronization module 15 forms an up-to-date reference 42 with which, in particular, an up-to-date stamp is set.
  • the synchronization module 15 can also be integrated in the repeater 29 or in a lamp 19, 21, 23, 24.
  • FIG Figure 2 shows a section of an emergency lighting system 101 and a second building management system 157, this overall system in a more schematic representation than in FIG Figure 1 is shown.
  • the emergency lighting system 101 is equipped with an arrangement of high-frequency communication modules 136, 137, 138, 139, which are distributed in two rooms R1, R2. Parallel to the emergency lighting system 101, there is a building management system 157 in the rooms such as room R1.
  • B. represents a burglar alarm system.
  • the first high-frequency communication module 136 installed in the first light 119
  • the second high-frequency communication module 137 connected to the second light 121
  • the third high-frequency communication module 138 connected to the third light 123, are located in the first room R1.
  • the second room R2 comprises one fourth luminaire 124 with the high-frequency communication module 139, which is spaced apart from the luminaire-spanning unit 117 via the communication path length 173.
  • Further communication path lengths 173 'and 173 "exist between the high-frequency communication module 139 and an interface device 151 or between the interface device 151 and the first light-covering unit 117.
  • the communication path lengths 173' and 173" on one side and the communication path length 173 on the other side compared to one another, it can be seen that the communication path length 173 spans the greatest distance between two devices with high-frequency communication modules such as the high-frequency communication module 139.
  • the interface device 151 By arranging the interface device 151, so to say halfway, the interface device can be used as a repeater;
  • the interface device 151 takes data tuples (cf. Figure 4 ) and sends it on.
  • Transmission tuples that are emitted by the first lamp 119 or the first high-frequency communication module 136 can reach the luminaire-overlapping unit 117 through the wall W via the first communication path P1 and can be analyzed or utilized after receipt by the luminaire-overlapping unit 117.
  • Monitoring tuples of the second lamp 121 also come out of the second high-frequency communication module 137 via path P2 to the luminaire-covering unit 117.
  • monitoring tuples of the third high-frequency communication module 138 can no longer reach the luminaire-spanning unit 117 via the direct path P3.
  • the group of people M represents a total signal shield 175. Due to the inventive design of the emergency lighting system 101, monitoring tuples are also communicated via the short paths KP2, KP3 and KP1 between the high-frequency communication modules 136, 137, 138 located in the room R1.
  • the fourth high-frequency communication module 139 is also involved in this exchange of monitoring tuples, and the interface device 151 with its radio module (see Figure 3 ).
  • the high-frequency communication modules 136, 137 and 139 and the interface device 151 thus act as communication nodes for the indirect forwarding of monitoring tuples from the high-frequency communication module 138 to the unit 117 that spans the lights.
  • a monitoring tuple of the third light 123 can receive and transmit via the short path KP2 from the first high-frequency communication module 136 the communication path P1 are forwarded to the luminaire-spanning unit 117.
  • a monitoring tuple of the third luminaire 123 can also be received by the second high-frequency communication module 137 via the short path KP3 and transmitted to the luminaire-spanning unit 117 via the communication path P2.
  • monitoring data of the third luminaire, which were received by the second high-frequency communication module 137 are also supplied via the short path KP1 to the first high-frequency communication module 136, which can subsequently also forward the monitoring data via the communication path P1.
  • So z. B. short-term transmission interference on a short path KP1, KP2, KP3 can be avoided. Even if the communication paths P1, P2, P3 and the (communication) path P4 should be interrupted because e.g. B.
  • the communication path length 173 is too long for a signal that is too weak at that moment, so that the communication paths P1, P2, P3 and P4 are all interrupted for a period of time, but thereafter, for example, the communication path P1 is available for a short period of time, All test results arrive from the lights 119, 123 and 121 from the temporary storage of the light 121 to the temporary storage of the light 124, in order to then reach communication unit P5 and P6 as far as the unit 117. Is the communication path P4 available at a later time because the If the communication path length 173 can be bridged, the test results finally reach the monitoring unit 117 which spans the lights.
  • the interface device 151 can perform the function of a repeater and establish the connection to the unit 117 spanning the lights via the two communication paths P5 and P6.
  • the data exchange and the control functions in the emergency lighting system 101 are ensured because there is no specification as to which path a surveillance tuple takes from a high-frequency communication module 136, 137, 138, 139 to the unit 117 that spans the lights.
  • the components of a monitoring tuple can simultaneously strive for their destination via a plurality of communication paths, with only the arrival time being delayed, in particular with the number of passed high-frequency communication modules 136, 137, 138, 139.
  • Determinations as to when a fault is to be expected can be found in the relevant standards and can be 1 day, 1 week or, depending on the circumstances, one month.
  • the probabilities for transmission problems between the high-frequency communication modules 136, 137 and 138 in room R1 via the short paths KP1, KP2, KP3 were assumed to be negligible compared to possible transmission problems through a wall W.
  • the use of short paths between high-frequency communication modules 136, 137, 138 in the same room R1 increases the probability of transmission to a unit 117 that spans luminaires to more than 99%, although the individual probability of transmission in each case, that is, between a high-frequency communication module 136, 137, 138 and a luminaire overlapping 117, is only 80%.
  • the interface device 151 is a transition component between the emergency lighting system 101 and the other building management system 157 which is still present.
  • the interface device 151 is connected to the building management system via the connecting cable 167.
  • the risk of radio interference from one building management system emergency lighting system 101 to the other building management system 157 is reduced by the cable routing in the second building management system 157.
  • the first light 119 receives data via the short path KP1 from the second light 121 via a data tuple.
  • the high-frequency communication module 136 then sends a data tuple with data from the first light 119 and the second light 121 to the fourth high-frequency communication module 139 as well as to the interface device 151 with its radio module such as radio module 239 (see Figure 3 ).
  • the lights 119, 121, 123 and 124 can be configured on site. In this way, a luminaire 119 can become a standby light luminaire as required.
  • FIG. 3 shows the interior of an interface device 251 based on the illustration of a circuit diagram with schematic electronics and electrical symbols.
  • the interface device 251 comprises several assemblies.
  • One module is the radio module 239, to which further sub-modules such as the modules 245, 246, 247, 249, 250 belong.
  • the radio module 239 has an antenna 246 which is connected to an RF radio part 245.
  • On the board of the Radio module 239 is a bus connection 247 for a standard serial bus such as an RS-232 bus, an RS-485 bus or an RS-422 bus.
  • the circuit board of the radio module 239 includes a web server 249.
  • An Ethernet connector 250 is added to the radio module 239.
  • the radio module 239 is inserted into a connector strip 254.
  • the plug connector 254 leads electrically to the common fault contact, which is composed of the two parts of the common fault contact 269, 269 '.
  • the radio module 239 further comprises a microcontroller 243.
  • An analog driver stage 244 is connected to the microcontroller 243 and is controlled by the microcontroller 243. Via the analog driver stage 244, relays can be actuated beyond the connector strip 254 or kept in switched or unswitched states. Such a relay is part of the collective fault contact 269, 269 '.
  • the second part of the common fault contact 269 ' is implemented by a changeover contact.
  • the changer 269 ' is moved into different switching positions by the coil of the first part 269 of the collective fault contact.
  • a field effect transistor FET of the "enhancement" type is located in the line connection between the plug connector 254 and the common interference contact 269, 269 '. With the help of the field effect transistor FET, the drive signal originating from the analog driver stage 244 is inverted for the first part 269 of the collective interference contact.
  • An LED4 also present in the first part 269 of the common fault contact indicates the operating state of the common fault contact 269, 269 '.
  • Further output contacts 263, 264 are implemented with the aid of relay circuits, similar to the common fault contact 269, 269 '.
  • the interface device 251 comprises three output contact assemblies such as the output contacts 263, 264 or the common fault contact 269, 269 '.
  • the interface device 251 has a power supply unit U v .
  • the power supply unit U v supplies a wide variety of voltages through voltage supply modules U v1 , U v2 .
  • the interface device 251 has input contacts such as the input contact 261 or the fire alarm input 265. Both the fire alarm input 265 and the further input contact 261 are galvanically decoupled via optocouplers OK1, OK2.
  • the output contacts like the output contacts 263, 264 are also galvanically decoupled due to the use of the relays. This means that all input contacts and output contacts are galvanically decoupled from one another and from the voltages of the power supply unit U v .
  • LEDs such as the LED3, LED4, LED5, LED6 are present behind each assembly of the input contacts such as the input contact 261 and the output contacts such as the output contacts 263, 264 and the common fault contact 269, 269 '. With further LEDs such as LEDs LED1, LED2, the presence of a sufficient supply voltage from the power supply unit U v can be recognized. Despite the existing LEDs LED1, LED2, LED3, LED4, LED5, LED6, it is a device in a top-hat rail housing that is not intended for lighting purposes. The LEDs LED1, LED2, LED3, LED4, LED5, LED6 are only used for faster visual recognition during maintenance of a Emergency lighting system 1 (cf. Figure 1 ), 101 (cf. Figure 2 ).
  • the microcontroller 243 of the radio module 239 has what in Figure 3 is not immediately visible, a control program with which both the individual output contacts 263, 264 and input contacts 261 can be controlled, monitored and measured, as well as manipulation software for data tuples, received as transmission tuple 179 or monitoring tuple 181, 183, 185, 187, 189, 191 (see Figure 4 ).
  • the microcontroller 243 receives individual data tuples via the antenna 246 and the RF radio part 245.
  • the microcontroller 243 stores the received data tuple in an internal memory and supplements objects in the data tuple with those from the output contacts 263, 264 or at the common fault contact 269, 269 '. displayed states.
  • FIG 4 is schematically a segment from the emergency lighting system 101, which is more extensive in Figure 2 is shown, shown in more detail along with their data tuples.
  • a transmission tuple 179 is transmitted by the luminaire-spanning unit 117 with the high-frequency communication module 134, which reaches the first high-frequency communication module 136 of the first lamp 119 via the communication path P1 and the second high-frequency communication module 137 of the second lamp 121 via the path P2. Due to a signal shield 175, the transmission tuple 179 cannot penetrate beyond the communication path length 173 of the communication path P3 to the third high-frequency communication module 138 of the third light 123.
  • the transmission tuple 179 in the form of a monitoring tuple has a first component 193, a second component 194 and a plurality of further components 195, 195 ', 195 ", which are arranged sequentially in the transmission tuple 179.
  • Each component 193, 194, 195, 195 ', 195 "of the transfer tuple 179 has an actuality stamp 197, which in particular determines a point in time at which the component of the transfer tuple 179 was updated.
  • the first component of the transmission tuple 179 is provided for the recording of monitoring data DK1, DK1 'of the first high-frequency communication module 136, as are the corresponding further odd-numbered components for recording additional monitoring data DK2, DK2' and DK3, DK3 'of the transmission tuple 179 of the second high-frequency communication module 137 or are assigned to the third high-frequency communication module 138.
  • the second component 194 of the transmission tuple 179 carries the control data SK1 intended for the first high-frequency communication module 136. Accordingly, the further even-numbered components of the transmission tuple 179 carry control commands in the control data SK2, SK3, each for the second high-frequency communication modules 131 and the third high-frequency communication module 138 are determined.
  • the control data for the lights 119, 121, 123 are also each provided with an update stamp, such as the update stamp 197.
  • the further data of the part of the emergency lighting system 101, which is otherwise not shown, are also documented in the transmission tuple 179, but are summarized as further data DTN in order to simplify the representation in the last component of the transmission tuple 179.
  • a validity supplement 199 of the transmission tuple 179 is used to control the transmission quality of the data in the components of the transmission tuple 179.
  • B. performed by the radio frequency communication module 136.
  • the combination of control data and monitoring data shown in this example into a common, uniform transmission tuple leads to a particularly simple implementation of each individual high-frequency communication module such as high-frequency communication module 134, 136, 137, 138, 139.
  • the transmission tuple 179 also has a component for an alarm signal AS.
  • the component of the alarm signal AS is assigned a processable value if an external event of another building management system 157 (cf. Figure 2 ) has occurred.
  • the lights 119, 121, 123 in their operating state, for. B. be changed by switching on.
  • the radio-frequency communication modules 136, 137 transmit a corresponding, identical transmission tuple 179 in time after receipt of the transmission tuple 179 with control data SK1, SK2, SK3.
  • the high-frequency communication modules 136, 137, 138 work as repeaters. There is an efficient and rapid distribution of tax data, which is necessary, for example, to set an up-to-date reference 42 (cf. Figure 1 ) via the high-frequency communication modules 136, 137, 138 is useful.
  • a first monitoring tuple 181, 185, 189 is transmitted by the high-frequency communication modules 136, 137, 138.
  • the first component of invalid data X in the first lamp 119 based on the transmission tuple 179 was replaced by current monitoring data DK1 of the first lamp 119 and the actuality stamp 197 and the validity supplement 199 were also updated.
  • the validity supplement 199 is a self-correcting checksum from which it can be determined whether the transmission tuple 179 was received without errors.
  • the monitoring tuple 181 reaches the second high-frequency communication module 137, the third high-frequency communication module 138 and the high-frequency communication module 134 of the luminaire-covering unit 117.
  • the second high-frequency communication module 137 Before receiving the monitoring tuple 181 of the first high-frequency communication module 136, the second high-frequency communication module 137 also sends out a first monitoring tuple 185, which the current monitoring data DK2 in of the third component based on the transmission tuple 179.
  • the first component of the first monitoring tuple 185 which is assigned to the first high-frequency communication module 136, therefore still contains invalid data X.
  • the monitoring tuple 185 from the second high-frequency communication module 137 only reaches the first high-frequency communication module 136 with non-valid data X in all components, so that the received monitoring tuple 185 in the first high-frequency communication module 136 is rejected.
  • the first monitoring tuple 185 of the second high-frequency communication module 137 is received in valid form by both the third high-frequency communication module 138 and the high-frequency communication module 134.
  • the monitoring data DK2 of the second light 119 are thus present in the third high-frequency communication module 138.
  • the first high-frequency communication module 138 received the first monitoring tuple 183, 185, the latter had already sent out a monitoring tuple 189, which, owing to the fact that the transmission tuple 179 was not received, only made a valid data entry of status information of the third light 123 as monitoring data DK3 in the contains the corresponding component of the first monitoring tuple 189, the remaining components of which are described with non-valid data X.
  • This first monitoring tuple 189 only reaches the high-frequency communication modules 136, 137, but not the high-frequency communication module 134 of the luminaire-crossing unit 117.
  • the analysis of the first monitoring tuple 189 in the high-frequency communication modules 136, 137 in connection with temporarily stored data shows that there is a transmission problem on the third high-frequency communication module 138.
  • This information is written into the second monitoring tuples 183 and 187, which are emitted by the high-frequency communication modules 136, 137, by updating the component for the control data SK3 to the third lamp 123 in the form of control data SK3 '.
  • the second monitoring tuple 187 is emitted From the second high-frequency communication module 137, all the current monitoring data for the lights 119, 121, 123 are already written into the monitoring tuple 187.
  • the monitoring data DK2 'of the second luminaire 121 are up to date.
  • the monitoring tuple 187 of the luminaire-crossing unit 117 is used to inform the control data SK3' that there is a transmission problem with the third high-frequency communication module 138.
  • the reception problem of the first monitoring tuple 185 by the first high-frequency communication module 136 was noted as an updated control data record SK2 'in the second monitoring tuple 183 of the first high-frequency communication module 136, so that this information is also received by the unit 117, but via the communication path P1. Due to the electromagnetic interference 177, the monitoring tuple 183 does not contain any monitoring data about the second lamp 119, but the monitoring data DK1 'of the first lamp is up to date.
  • the monitoring data DK2 only reach the first communication module 136 via the short path KP3 and the short path KP2 with the second Monitoring tuple 191, which the third high-frequency communication module 138 emits, together with an update of the monitoring data DK3 'of the third light 123.
  • the data record DK2 can only be included in the corresponding component of a third monitoring tuple (not shown) of the first high-frequency communication module 136.
  • a transmission can be accomplished without an initiation by the luminaire-crossing unit 117.
  • the high-frequency communication modules 136, 137, 138 in the lights 119, 121, 123 are controlled by a timer (not shown graphically), only dependent on their operating parameters or on measured values, send monitoring tuples 181, 183, 185, 187, 189, 191.
  • a time-overlapping arrival which makes data reception impossible due to the collision, from several monitoring tuples 181, 185, for example at the high-frequency communication module 137, is prevented by different operating parameters and thus different timing of the timers.
  • the timers work with non-equidistant time intervals which depend on the operating parameters when the transmission of a transmission tuple is repeated, in order to avoid this in the event of a random collision during the next repetition.
  • the circuit after Figure 3 can be in one piece or divided into several boards or even housings in an emergency lighting system 1, 101 (see Figures 1 and 5) be installed.
  • an emergency lighting system 1 101 (see Figures 1 and 5) be installed.
  • the lamp 24 can be used as a "single-battery lamp” (it is also referred to as "self-contained”).
  • a lamp such as lamp 23 (see Figure 1 )
  • only the circuit part is present, the one in the upper left area with the reference symbol U v in the circuit Figure 3 is shown, arranged in a centralized manner, this is referred to as a central or group battery-supplied emergency lighting system.
  • Such emergency lighting systems are also known as CPS (Central Power Supply) or LPS (Low Power Supply).
  • Another relay (not shown) can follow in the circuit Figure 3 be installed. It can be used to control lamps.
  • the radio module after Figure 3 can be used as a retrofit kit 239, e.g. B. as a plug-in module, designed for previously common lights in emergency lighting systems.
  • the luminaire housing is made of metal or plastic, tests have shown that only a negligible attenuation occurs in a frequency band around 868 MHz.

Landscapes

  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Circuit Arrangement For Electric Light Sources In General (AREA)
  • Alarm Systems (AREA)

Claims (19)

  1. Installation d'éclairage de secours (1, 101)
    avec un appareil à interface (51, 151, 251) qui est équipé d'un module radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239)
    ou avec plusieurs appareils à interface (51, 151, 251) qui sont équipés de modules radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239)
    et avec au moins une première lampe d'éclairage de secours (19, 119) et
    avec au moins une seconde lampe d'éclairage de secours (21, 121) qui sont en liaison l'une avec l'autre par un canal radio (55),
    cependant que des données (177, 185, 187, DK1, DK2, DK3, DK2', DK3) peuvent être transmises sur le canal radio (55) par la seconde lampe d'éclairage de secours (21, 121) qui est équipée d'un module radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239),
    cependant que des données (179, 181, 183, 185, 187, 189, 191, DK2, DK2') sur un état de la seconde lampe d'éclairage de secours (21, 121) peuvent être transférées par la première lampe d'éclairage de secours (19, 119) qui est équipée d'un module radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239) et
    cependant que l'appareil à interface (51, 151, 251) représente un nœud radio (P1, P2, P3), qui communique (SK1, SK2, SK3) sur le canal radio (55), à l'aide de son module radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239) et
    l'appareil à interface (51, 151, 251) présente au moins un contact (61, 63, 261, 263, 264, 265),
    caractérisé en ce que
    la au moins une première lampe d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) et la au moins une seconde lampe d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) et l'appareil à interface (51, 151, 251) peuvent être amenés dans un échange de données au moyen du au moins un canal radio (55), par lequel des données d'état (177, 179, 181, 183, 185, 187, 189, 191) peuvent être transmises, avec un autre utilisateur radio (29, 33, 35, 36, 37, 38, 39, 134, 136, 137, 138, 139) de l'installation d'éclairage de secours (1, 101) vers lequel une voie de communication n'est pas encore établie dès le début, cependant que l'appareil à interface (51, 151, 251) est équipé d'une pièce électronique qui présente une minuterie ou un élément temporisateur pour le branchement d'au moins un système de gestion de bâtiment (57, 157, 59)
    et qu'un contact (61, 63, 261, 263, 264, 265) du au moins un contact (61, 63, 263, 264, 265) est un contact de sortie (63, 263, 264) qui présente, en tant que contact qui centralise les perturbations (269, 269'), un nombre de différentes perturbations pour informer le système de gestion de bâtiment (57, 157, 59) sur des perturbations et
    qui ne peut être commuté que lorsqu'une perturbation intervient pendant une durée minimale et qu'un contact (61, 63, 261, 263, 264, 265) du au moins un contact (61, 63, 263, 264, 265) est un contact d'entrée (61, 261, 265) qui est un contact de tension à découplage galvanique pour une tension longue portée ou
    qui sert à raccorder un module radio déporté (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239) par des câbles de liaison et
    que le module radio (33, 34, 134, 35, 36, 136, 137, 38, 138, 39, 139, 239) de l'appareil à interface (51, 151, 251) comprend un microcontrôleur (243) avec un programme de commande si bien que
    des lampes d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) de l'installation d'éclairage de secours (1, 101) peuvent être mises en circuit par le contact d'entrée (61, 261, 265) par des objets complétés par le microcontrôleur (243) dans un tuple de données qui est communiqué sur le au moins un canal radio (55).
  2. Installation d'éclairage de secours (1, 101) selon la revendication 1, caractérisée en ce que le contact qui centralise les perturbations (269, 269') comprend un changeur.
  3. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce qu'au moins une lampe d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) est configurée comme une lampe de veille.
  4. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que l'appareil à interface (51, 151, 251) présente un contact qui centralise les perturbations (269, 269') aussi bien qu'un contact de signalisation d'incendie (265).
  5. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que le contact d'entrée (61, 261, 265) est un contact de signalisation d'incendie (265).
  6. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que l'appareil à interface (51, 151, 251) est un appareil électronique autonome.
  7. Installation d'éclairage de secours (1, 101) selon la revendication 6, caractérisée en ce que l'appareil à interface (51, 151, 251) est découplé des câbles de tous les autres utilisateurs radio (19, 119, 21, 121, 23, 123, 24, 124, 29).
  8. Installation d'éclairage de secours (1, 101) selon la revendication 6 ou 7, caractérisée en ce que l'appareil à interface (51, 151, 251) est un appareil de zone sombre monté sur un rail de fixation.
  9. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que le contact qui centralise les perturbations (269, 269') peut être actionné par un microcontrôleur (243) en étant commandé par un microcontrôleur (244).
  10. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que le contact qui centralise les perturbations (269, 269') a une boucle de couplage qui n'est pas sujette aux perturbations.
  11. Installation d'éclairage de secours (1, 101) selon la revendication 10, caractérisée en ce que la boucle de couplage est réalisée de manière électromécanique.
  12. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que l'appareil à interface (51, 151, 251) comprend au moins deux paires de contacts de sortie (63, 263, 264, 269, 269') et au moins deux paires de contacts d'entrée (61, 261, 264) parmi lesquelles chaque paire de contacts (61, 261, 63, 263, 264, 265, 269, 269') est découplée galvaniquement des autres paires de contacts (63, 263, 264, 265, 2, 269', 61, 261).
  13. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que l'appareil à interface (51, 151, 251) comprend un circuit de tension d'entrée (Uv, Uv1, Uv2) qui peut être alimenté par une alimentation en tension de secteur.
  14. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que le microcontrôleur (243) est configuré pour fonctionner comme logique OU.
  15. Installation d'éclairage de secours (1, 101) selon la revendication 14, caractérisée en ce qu'une impulsion de commutation pour le contact qui centralise les perturbations (269, 269') peut être générée par le microcontrôleur (243) en raison d'un ou de deux ou de plusieurs des évènements déclencheurs suivants :
    en raison d'un signal d'alarme (AS) reçu par transmission radio,
    en raison d'une perturbation dans l'appareil à interface (51, 151, 251),
    en raison d'une perturbation sur un canal radio (55),
    en raison d'un message d'erreur ou
    en raison d'une erreur de bit de données (177).
  16. Installation d'éclairage de secours (1, 101) selon l'une des revendications précédentes, caractérisée en ce que le microcontrôleur (243) est connecté à un module radio (33, 34, 134, 35, 36, 136, 37, 137, 38, 138, 39, 139, 239).
  17. Installation d'éclairage de secours (1, 101) selon la revendication 16, caractérisé en ce que le microcontrôleur présente une connexion de bus (247), une connexion IsaNet ou une interface de serveur internet (249).
  18. Procédé pour informer un système de gestion de bâtiment (57, 157) par des données (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') d'une installation d'éclairage de secours (1, 101),
    cependant que les données (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') sont acquises par radio par au moins une lampe d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) par un appareil à interface (51, 151, 251) avec un module radio (33, 34, 134, 35, 36, 136, 37, 137, 38, 138, 39, 139, 239),
    caractérisé en ce que
    les données acquises (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') sont mises à la disposition d'un contact qui centralise les perturbations (269, 269') de l'appareil à interface (51, 151, 251) et qu'un microcontrôleur (243) de l'appareil à interface (51, 151, 251) identifie au moins deux sources de perturbations (AS, 177)
    qui s'opposent à une réception sans perturbations d'un jeu de données des données (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') envoyées comme tuple de surveillance (179, 181, 183, 185, 187, 189, 191) cependant qu'une analyse de tuples de surveillance (183, 185, 187) ou une analyse de tuples de surveillance (183, 185, 187) avec des données mises en cache, par le microcontrôleur programmé (243), est une base de l'identification des sources de perturbations (AS, 177) et,
    en cas d'existence d'au moins l'une des sources de perturbations (AS, 177), le contact qui centralise les perturbations (269, 269') n'est commuté qu'après une durée minimale d'une perturbation,
    contact par lequel une information pour le système filaire de gestion de bâtiment (57, 157) peut être transmise.
  19. Appareil à interface (51, 151, 251) qui présente un module radio (239), caractérisé en ce que l'appareil à interface (51, 151, 251) exerce aussi bien un procédé pour informer un système de gestion de bâtiment (57, 157) par des données (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') d'une installation d'éclairage de secours (1, 101) selon la revendication 18 qu'une insertion d'un signal d'activation (AS) dans un tuple de données (179, 181, 183, 185, 187, 189, 191) pour une installation d'éclairage de secours (1, 101) dans un même microcontrôleur (243) de l'appareil à interface (51, 151, 251) avec une utilisation subséquente du même module radio (33, 34, 134, 35, 36, 136, 37, 137, 38, 138, 39, 139, 239) pour une réception d'un tuple de données (179, 181, 183, 185, 187, 189, 191) et pour l'émission d'un tuple de donnés adapté sur le plan informationnel (179, 181, 183, 185, 187, 189, 191), cependant que les données (179, 181, 183, 185, 187, 189, 191, DK1, DK1', DK2, DK2', DK3, DK3', DTN, AS, SK1, SK2, SK2', SK3, SK3') de l'installation d'éclairage de secours (1, 101) sont des données échangées par radio entre des lampes d'éclairage de secours (19, 119, 21, 121, 23, 123, 24, 124) et que l'insertion comprend ici une opération d'insertion comprenant les étapes suivantes :
    l'appareil à interface (51, 151, 251) reçoit le tuple de données (179, 181, 183, 185, 187, 189, 191) du module radio (33, 34, 134, 35, 36, 136, 37, 137, 38, 138, 39, 139, 239), le tuple de données (179, 181, 183, 185, 187, 189, 191) est mis en cache dans une mémoire (41) administrée par le microcontrôleur (243),
    une information sur un signal (AS) à une entrée de signalisation d'incendie (265) est insérée dans le tuple de données (179, 181, 183, 185, 187, 189, 191) dans une composante du tuple de données (179, 181, 183, 185, 187, 189, 191) qui est prévue à cet effet et
    le tuple de données (179, 181, 183, 185, 187, 189, 191) est destiné à la mise à disposition par le module radio (33, 34, 134, 35, 36, 136, 37, 137, 38, 138, 39, 139, 239) à plusieurs utilisateurs radio (19, 119, 21, 121, 23, 123, 24, 124, 29) de l'installation d'éclairage de secours (1, 101).
EP14160816.6A 2013-03-22 2014-03-20 Installation d'éclairage de secours dotée d'une fonction d'interface vers des systèmes de gestion technique de bâtiment et procédé de communication associé Active EP2782428B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PL14160816T PL2782428T3 (pl) 2013-03-22 2014-03-20 Instalacja oświetlenia awaryjnego z funkcją łącza do układów zarządzania budynkiem i związany z tym sposób komunikacji

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
DE102013102964.7A DE102013102964B4 (de) 2013-03-22 2013-03-22 Notlichtbeleuchtungsanlage mit Schnittstellenfunktion zu Gebäudeleitsystemen und dazugehöriges Kommunikationsverfahren

Publications (3)

Publication Number Publication Date
EP2782428A2 EP2782428A2 (fr) 2014-09-24
EP2782428A3 EP2782428A3 (fr) 2015-12-23
EP2782428B1 true EP2782428B1 (fr) 2020-05-27

Family

ID=50473018

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14160816.6A Active EP2782428B1 (fr) 2013-03-22 2014-03-20 Installation d'éclairage de secours dotée d'une fonction d'interface vers des systèmes de gestion technique de bâtiment et procédé de communication associé

Country Status (3)

Country Link
EP (1) EP2782428B1 (fr)
DE (1) DE102013102964B4 (fr)
PL (1) PL2782428T3 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102016217903A1 (de) 2016-09-19 2018-03-22 Fischer Akkumulatorentechnik Gmbh Automatisiertes Erkennen der Zuordnung von Notleuchten zu Stromkreisen

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6972679B2 (en) * 2003-05-20 2005-12-06 Yi-Chia Liao Multi-processor burglar-proof apparatus
DE20309338U1 (de) * 2003-06-17 2003-09-11 Benkhardt Axel Rauchmelder
US20060154642A1 (en) * 2004-02-20 2006-07-13 Scannell Robert F Jr Medication & health, environmental, and security monitoring, alert, intervention, information and network system with associated and supporting apparatuses
US8362713B2 (en) * 2006-03-28 2013-01-29 Wireless Environment, Llc Wireless lighting devices and grid-shifting applications
US7772540B2 (en) * 2007-03-06 2010-08-10 Pasternak Barton A RF controlled sequential lighting system
DE102007024422A1 (de) 2007-05-25 2008-11-27 Cooper Crouse-Hinds Gmbh Leuchte und Schienenmodul
US7990252B2 (en) * 2007-09-19 2011-08-02 Barton Robert A Safety system and method for conventional lighting fixtures
US8497634B2 (en) * 2008-10-23 2013-07-30 Innovation Works, Inc. Wireless lighting system for staircases and passageways
DE102009017213B4 (de) 2009-04-09 2012-08-02 Uwe Lindner Notlicht mit intelligenten Zusatzmodulen
WO2012023087A1 (fr) * 2010-08-16 2012-02-23 Koninklijke Philips Electronics N.V. Système de radars multiples
EP2441643B1 (fr) * 2010-10-18 2017-12-06 ALSTOM Transport Technologies Système pour surveiller le fonctionnement d'appareils ferroviaires
IT1403519B1 (it) * 2010-12-28 2013-10-31 Ova G Bargellini S P A Rete di interconnessione di apparati per l'illuminazione d'emergenza e procedimento di gestione della stessa
WO2013016534A1 (fr) * 2011-07-27 2013-01-31 Verified Energy, Llc Encapsulation d'instructions dali dans des réseaux sans fil
DE102011053883B4 (de) 2011-09-23 2022-03-10 Rp-Technik Gmbh Notlichtbeleuchtungsanlage mit Datenkommunikationsfähigkeiten

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2782428A3 (fr) 2015-12-23
DE102013102964B4 (de) 2016-08-25
DE102013102964A1 (de) 2014-09-25
PL2782428T3 (pl) 2020-11-16
EP2782428A2 (fr) 2014-09-24

Similar Documents

Publication Publication Date Title
EP0345493B1 (fr) Dispositif de surveillance, de commande et de régulation d'une installation technique de systèmes d'automation de bâtiments
EP2573630B1 (fr) Installation d'éclairage de secours équipée de fonctions de communication de données
DE102009022874B4 (de) Sicherheitsbeleuchtungsanlage mit spezieller Endstromkreistopologie und endstromkreisbildende Schalteinheiten
DE19811894A1 (de) Verfahren zum Inbetriebnehmen eines Bussystems sowie entsprechendes Bussystem
DE102011087152B4 (de) Testsystem und Testverfahren für Kabelbäume
EP2720098A1 (fr) Système de sécurité pour une installation comprenant un chemin de signal de test avec un chemin de retour
DE102021105553B4 (de) Notlichtbeleuchtungsanlage mit Fail-Safe-Funktion und Verfahren zu ihrem Betrieb
EP0125387B1 (fr) Méthode et dispositif de signalisation de risque
DE202017103605U1 (de) Beleuchtungseinrichtung
EP0776108A2 (fr) Système de bus en particulier pour une installation électrique
EP2782428B1 (fr) Installation d'éclairage de secours dotée d'une fonction d'interface vers des systèmes de gestion technique de bâtiment et procédé de communication associé
EP1246150B1 (fr) Système d'alarme d'incendie
EP2502354B1 (fr) Système d'installation électrique
EP2224641A2 (fr) Appareil d'installation électrique/électronique
EP2568391A2 (fr) Module, système présentant un module de ce type et procédé d'attribution d'adresses bus parallèles
WO2018215301A1 (fr) Émission de signal d'état
DE3634564A1 (de) Schaltungsanordnung zur uebertragung nachrichtentechnischer signale
DE1817148C3 (de) Rufanlage, insbesondere zur Verständigung zwischen Kranken, Pflege- und Wirtschaftspersonal in Krankenhäusern
EP2911128A1 (fr) Système d'alarme de dangers
DE19927869C1 (de) Elektroinstallationseinrichtung für Gebäude
DE102022125428A1 (de) System zum Ubertragen eines Signals mit einem Datenpaket zu und von einem aus einer Mehrzahl von Controllern
DE3420795A1 (de) Verfahren zur datenuebertragung von digitalen und analogen daten
DE202021003976U1 (de) Schaltbare Steckdose und System mit einer schaltbaren Steckdose
CH697645B1 (de) Verfahren und Vorrichtung zur Errichtung einer ereignisgesteuerten, leitungs- und verbindungslosen Kommunikation.
DE10217354B4 (de) Türstation einer Hauskommunikationsanlage

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: 20140320

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

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

Owner name: RP-TECHNIK GMBH

RIC1 Information provided on ipc code assigned before grant

Ipc: H02J 9/00 20060101ALI20150716BHEP

Ipc: H05B 37/03 20060101ALI20150716BHEP

Ipc: H05B 37/02 20060101AFI20150716BHEP

Ipc: G08B 25/10 20060101ALN20150716BHEP

Ipc: G08B 7/06 20060101ALI20150716BHEP

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: G08B 5/36 20060101ALN20151119BHEP

Ipc: G08B 7/06 20060101ALI20151119BHEP

Ipc: H05B 37/02 20060101AFI20151119BHEP

Ipc: H05B 37/03 20060101ALI20151119BHEP

Ipc: H02J 9/00 20060101ALI20151119BHEP

Ipc: G08B 25/10 20060101ALN20151119BHEP

R17P Request for examination filed (corrected)

Effective date: 20160621

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20181204

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20191030

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAL Information related to payment of fee for publishing/printing deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR3

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502014014214

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H05B0037020000

Ipc: H05B0047190000

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTC Intention to grant announced (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H05B 47/19 20200101AFI20200312BHEP

Ipc: G08B 7/06 20060101ALI20200312BHEP

Ipc: H05B 47/105 20200101ALI20200312BHEP

Ipc: H05B 47/21 20200101ALI20200312BHEP

Ipc: G08B 5/36 20060101ALI20200312BHEP

GRAR Information related to intention to grant a patent recorded

Free format text: ORIGINAL CODE: EPIDOSNIGR71

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

INTG Intention to grant announced

Effective date: 20200417

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: AT

Ref legal event code: REF

Ref document number: 1275979

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200615

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502014014214

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: ABP PATENT NETWORK AG, CH

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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: 20200928

Ref country code: NO

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: 20200827

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: 20200527

Ref country code: IS

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: 20200927

Ref country code: LT

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: 20200527

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: 20200828

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

Ref country code: LV

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: 20200527

Ref country code: RS

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: 20200527

Ref country code: BG

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: 20200827

Ref country code: HR

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: 20200527

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

Ref country code: AL

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: 20200527

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

Ref country code: RO

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: 20200527

Ref country code: CZ

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: 20200527

Ref country code: EE

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: 20200527

Ref country code: SM

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: 20200527

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: 20200527

Ref country code: ES

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: 20200527

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

Ref country code: SK

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: 20200527

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502014014214

Country of ref document: DE

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: 20210302

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

Ref country code: SI

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: 20200527

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

Ref country code: MC

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: 20200527

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

Ref country code: IE

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

Effective date: 20210320

Ref country code: LU

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

Effective date: 20210320

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

Ref country code: BE

Payment date: 20220321

Year of fee payment: 9

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

Ref country code: FR

Payment date: 20230324

Year of fee payment: 10

Ref country code: AT

Payment date: 20230301

Year of fee payment: 10

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

Ref country code: HU

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

Effective date: 20140320

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

Ref country code: SE

Payment date: 20230314

Year of fee payment: 10

Ref country code: PL

Payment date: 20230316

Year of fee payment: 10

Ref country code: GB

Payment date: 20230322

Year of fee payment: 10

Ref country code: DE

Payment date: 20230223

Year of fee payment: 10

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: 20200527

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

Ref country code: IT

Payment date: 20230328

Year of fee payment: 10

Ref country code: CH

Payment date: 20230401

Year of fee payment: 10

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230331

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: 20230331

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

Ref country code: NL

Payment date: 20240320

Year of fee payment: 11

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

Ref country code: AT

Payment date: 20240301

Year of fee payment: 11

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

Ref country code: MK

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: 20200527

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

Ref country code: DE

Payment date: 20240301

Year of fee payment: 11

Ref country code: GB

Payment date: 20240320

Year of fee payment: 11