EP3955705B1 - Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation - Google Patents

Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation Download PDF

Info

Publication number
EP3955705B1
EP3955705B1 EP21201386.6A EP21201386A EP3955705B1 EP 3955705 B1 EP3955705 B1 EP 3955705B1 EP 21201386 A EP21201386 A EP 21201386A EP 3955705 B1 EP3955705 B1 EP 3955705B1
Authority
EP
European Patent Office
Prior art keywords
interface
programming interface
application software
ballast
microprocessor
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
EP21201386.6A
Other languages
German (de)
English (en)
Other versions
EP3955705A1 (fr
Inventor
Markus Mayerhofer
Frank Lochmann
Florian Moosmann
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.)
Tridonic GmbH and Co KG
Original Assignee
Tridonic GmbH and Co KG
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 Tridonic GmbH and Co KG filed Critical Tridonic GmbH and Co KG
Priority to EP24153076.5A priority Critical patent/EP4355033A3/fr
Publication of EP3955705A1 publication Critical patent/EP3955705A1/fr
Application granted granted Critical
Publication of EP3955705B1 publication Critical patent/EP3955705B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/165—Controlling the light source following a pre-assigned programmed sequence; Logic control [LC]
    • 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
    • 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
    • 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/18—Controlling the light source by remote control via data-bus 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/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

Definitions

  • the invention relates to a component for a lighting system that can be largely and essentially freely configured by a user, comprising a ballast for LED lamps or a sensor.
  • the component has a programmable microprocessor that has a relatively high computing power and can communicate in different ways, i.e. with the help of a variety of interfaces.
  • a DALI, SPI, DSI, WLAN, Bluetooth, LAN and/or USB interface can be provided for this purpose.
  • Additional sensors and signal generators can be connected to the component and the microprocessor is connected to the interfaces in order to evaluate sensor signals and signals from signal generators, for example. Based on incoming signals from sensors and/or signal generators, or signals received via the interfaces, the microprocessor can then change the operating properties of the ballast and thus influence the light emission or other functionalities of the ballast, for example. Communication with external communication partners is possible, for example, via LAN, Bluetooth, USB, DALI, WLAN, etc.
  • the component has a programming interface via which application software can be transferred to a storage unit provided in the ballast.
  • This is a software and/or software component that can be executed and run by the microprocessor and that can be part of firmware and/or the operating system or can be executed thereby.
  • the application software is then executed by the microprocessor, among other things.
  • the operating system manages in particular a memory area that can be divided into a user area ("user space") and an operating system kernel area ("kernel space"). This division serves to allow parts of the memory area to be protected.
  • the operating system kernel area is then reserved for executing the operating system kernel, while the user area is intended for executing application software and/or drivers for interfaces and/or devices connected to the microprocessor.
  • the memory area can be part of a memory provided by the memory unit.
  • a user can influence and determine the way in which the component behaves, or how, for example, signals from other sensors or signal generators are evaluated and used to control the at least one light source. It is also possible to configure how an evaluation is processed to control components connected to the component via the interfaces. In particular, the evaluation and processing of input signals can be configured or changed using the application software and in particular a lighting control can be defined depending on the signals detected.
  • a housed operating device for operating lighting devices, preferably LEDs.
  • the housing which is preferably sealed against moisture, has means for mechanically positioning and/or holding at least one communication adapter. These means are arranged on the housing in such a way that a positioned and/or held communication adapter is supplied with energy wirelessly through the housing wall and communicates with an interface within the housing.
  • Printed matter CN103870403A relates to an LED lamp for performing a software update and/or self-definition of a control scheme using a mobile phone or a computer, and a corresponding method.
  • Printed matter EN 102009056152 A1 discloses an electronic system with at least one electronic functional unit, preferably a light source, at least one receiving unit for wireless signal transmission, and at least one remote control unit, which transmits control signals to the electronic functional unit by means of the receiving unit.
  • the remote control unit is part of an object intended for a person, such as a wristwatch, a piece of jewelry, a mobile phone, a PDA or a notebook.
  • Printed matter EN 102009032026 A1 refers to an operating device for lamps with several physical interfaces that are used to transmit control or configuration commands.
  • the invention thus provides a component and a lighting system (BS) or luminaire according to the independent claims. Further developments of the invention are the subject of the dependent claims.
  • a microprocessor 2 is therefore provided which is connected to at least one memory unit 3 so that it can access the memory unit 3 and read data from there as well as write data into it.
  • the microprocessor 2 (eg ARM Cortex-A5x, ARM Cortex-A7x, ...) is preferably provided on a circuit board 1, which preferably has at least one edge, and on which the memory unit 3 can also be mounted.
  • the microprocessor 2 and/or the memory unit 3 can also be provided on a separate circuit board that is connected to the circuit board 1, eg by means of a plug-in socket connection.
  • the circuit board has a programming interface P on the at least one edge and at least one signaling interface S, which can also be mounted on the at least one edge of the circuit board, but also on another edge of the circuit board.
  • the programming interface P is accessible from outside the ballast.
  • the programming interface can be set up for wired or wireless communication.
  • the programming interface P can be a radio interface (Bluetooth, WLAN, ZigBee, RFID, ...) and/or a wired (parallel, RS323, USB, JTAG, GPIO, ...) interface. It is therefore not always necessary for the programming interface P to be exposed to the outside. Rather, the programming interface P can also be accessed inductively from the outside, for example in order to transfer data from a programming device 4 to the memory unit 3 and/or the microprocessor 2 using the programming interface P. This ensures that the ballast V can be designed to suit its place of use and can, for example, have a prescribed protection class (International Protection Code (IP) certification).
  • IP International Protection Code
  • the programming interface P can be exposed to the outside.
  • the programming interface P can thus be accessed via a wired connection.
  • a programming device 4 can thus be connected to the programming interface P via a cable and data can be transferred to or from the memory unit 3 and/or the microprocessor 2.
  • Data transmitted via the programming interface P can be used by the microprocessor 2 or its Information processing can be configured.
  • an application software A (also called an "app") can be transferred to or into the storage unit.
  • This application software A is then executed by the microprocessor 2, it being understood that the microprocessor 2 can also execute a variety of application software components.
  • the programming interface P and the signaling interface S can use the same hardware and be separated only in terms of software.
  • the application software A can also be used to specify how the ballast V interacts with the connected signal sources (sensors, signal generators, etc.). In particular, it can be determined which signals are evaluated or processed and which type of signal generator the ballast V works with. This makes it possible to define the signal sources whose signals are evaluated. Signal sources or interfaces can also be blocked or enabled, and it is possible, for example, to expand or restrict the range of functions of the ballast V.
  • the at least one application software A can also influence the control with which the ballast V controls, for example, the at least one light source.
  • the light source can thus be controlled by the application software A, in particular depending on the incoming signals from the signal sources.
  • the behavior of the connected light sources and/or devices can be changed by, for example, transferring new application software A.
  • An application software A that is stored in the memory unit 3 of the ballast V can of course also change the evaluation of the signals.
  • ballast Vv Another functionality of the application software A is that it also allows the control of the ballast Vv provided functionality can be changed and, in particular, provided interfaces can be activated or deactivated.
  • the range of functions of the ballast V can also be controlled in this way.
  • Communication protocols provided for the communication of the ballast with communication partners, for example other ballasts, operating devices or control centers, can also be activated or deactivated.
  • the ballast V can be adapted for different application scenarios, for example by only requiring individual communication protocols.
  • the functionality of the ballast V can also be expanded if additional communication protocols need to be added or deactivated. This can be the case, for example, if the application scenario for the ballast changes.
  • the application software allows the operating data and/or operating parameters of the ballast V to be recorded, defined, evaluated and changed.
  • the at least one application software A in the memory unit 3 can also be updated and changed. This can then also be done via the programming interface P. It is also possible for more than one application software A to be stored in the memory unit 3 and executed by the microprocessor. Thus, by adding an application software A, additional features of the ballast V can be activated or deactivated. For example, it is possible for one application to only provide basic functionality, while another application software A additional functionalities of the ballast V are deactivated or activated.
  • the application software A can also provide, make available or modify an application programming interface. This application programming interface can then be used to add further software components to the application software that also affect functionalities of the ballast and, in particular, activate or deactivate functions.
  • the microprocessor 2 preferably executes a hardware abstraction subsystem (HAL, Hardware Abstraction Layer).
  • HAL Hardware Abstraction Layer
  • the application software then preferably accesses the programming interface and/or the signaling interface via the hardware abstraction subsystem.
  • the programming interface can be a wireless or wired interface.
  • the signaling interface S can also be a DALI or DSI, SPI, or I 2 C interface.
  • the programming interface P can also be designed in such a way that programming or the transfer of application software is initially not possible.
  • a programming interface that is initially blocked in this way can require that a code or, according to an unclaimed example, an activation key, e.g. a cryptographic key, must first be transferred to the ballast in order to to activate the programming interface P.
  • the programming interface P can only be activated (for example for a predetermined period of time) if the programming interface P has been activated accordingly.
  • the application software can also be transmitted in encrypted form via the programming interface, the ballast having a first code or, according to an unclaimed example, a first activation key, e.g. a cryptographic key, which is stored in the ballast.
  • this first code or activation key is a public key which can be used to decrypt the application software transmitted on the programming interface.
  • this first code or activation key e.g. a cryptographic key
  • the programming device can have a second code or, according to an unclaimed example, a second activation key, e.g. a cryptographic key, which is a type of private key and which can preferably be used for both encryption and decryption.
  • the programming device can enable an encrypted transmission of the application software via the programming interface, whereby the ballast can receive and read this encrypted application software.
  • the programming interface p can only be activated if, for example, a programming device 4 is positioned at a certain distance from the programming interface P or is connected to the programming interface P.
  • the Programming device 4 can then automatically transmit an identifier or a key via the programming interface P to the microprocessor 2, which is recognized by the latter (eg by means of NFC).
  • the microprocessor 2 can then enable a transfer of data to the storage unit 3 and thus the activation of the programming interface P.
  • the ballast V can also have wired or wireless communication interfaces, for example to communicate with other ballasts or operating devices. These communication interfaces are, for example, attached to an edge of the circuit board.
  • the ballast V can also have a converter interface via which one or more further ballasts or converters can be connected to the ballast.
  • the application software A or the microprocessor 2 can thus control one or more further ballasts or converters connected to the ballast V.
  • the microprocessor 2 is in particular a single-chip system (system on a chip, SoC).
  • SoC system on a chip
  • the shape of the circuit board 1 essentially corresponds to an n-gon. Alternatively, a round or oval shape would also be possible.
  • the circuit board can be essentially rectangular, triangular or trapezoidal in shape, and the interfaces provided can be arranged accordingly along the edges of the circuit board 1.
  • the microprocessor 2 with memory unit 3 can be connected to the circuit board wirelessly or be connected by wire.
  • Fig.1 shows a circuit board 1 of a ballast V, on which a microprocessor 2 and a memory unit 3 are arranged.
  • the essentially trapezoidal design of the circuit board 1 shown as an example has four edges, which are marked with a, b, c and d.
  • Different interfaces can now be attached to the edges a, b, c, d of the circuit board 1, which can also be assigned to different functional groups.
  • the interfaces on a first edge a can be set up for communication with other ballasts (converters) or other participants in a lighting system.
  • interfaces are shown as examples, which are designed, for example, as a communication interface for communication using DALI, SPI or I 2 C (Inter-Integrated Circuit) buses/protocols.
  • interfaces for communication with control units can be provided on a second edge b.
  • a DALI, a Bluetooth (Bluetooth Low Energy, BLE) and a LAN interface are shown as examples.
  • An interface P is provided at a third edge c.
  • the interface P is preferably the programming interface. As already mentioned, this can be protected against access by mechanical or software measures or can be activated selectively.
  • a programming device 4 is also shown as an example, from which at least one application software A can be transferred to and/or from the interface P, which is can also be a Bluetooth (e.g. BLE) interface.
  • interfaces are provided on a fourth edge, which are used, for example, to connect sensors and/or other hardware that is to be connected to the ballast. Examples shown here are a WLAN (or WiFi), a USB and a serial RS232 interface. These can, for example, enable communication with a microphone arrangement 5, a humidity sensor 6 and/or a presence sensor 7.
  • the sensors can be active or passive.
  • the programming interface P and the signaling interface S can, for example, also use the same hardware and are only separated in terms of software.
  • the signaling interface S can be used for the encrypted transmission of the application software A, whereby this encrypted transmission in this case forms the programming interface P.
  • the signaling interface S thus also serves for an encrypted transmission of the application software A and thus simultaneously forms the programming interface P.
  • the signaling interface S and the programming interface P use the same hardware as infrastructure in this case, but are separated in terms of software.
  • the programming interface P can use the signaling interface S for data traffic, in particular for the transmission of the application software A.
  • the ballast V can be controlled via a first code or, according to an unclaimed example, via a first activation key, e.g. cryptographic key, which is stored in the ballast V.
  • this first code or activation key e.g. cryptographic key
  • this first code or activation key e.g. cryptographic key
  • the programming device can have a second code or, according to an unclaimed example, a second activation key, e.g. cryptographic key, which is a type of private key and which can preferably be used for both encryption and decryption. In this way, the programming device can enable encrypted transmission of the application software A via the programming interface P, wherein the ballast can receive and read out this encrypted application software.
  • the application software A can be transmitted in individual packets via the programming interface P.
  • these packets can each be provided with a port address.
  • the packets with the port address can be received by the ballast V and assigned to the corresponding port within the ballast.
  • the individual packets can be transmitted in encrypted form via the programming interface P.
  • the ballast V can receive the encrypted packets and be assigned to the corresponding port according to their port address.
  • Fig.1 also shows a further ballast (also called a converter) or at least one further participant in a lighting system 8, which can be communicatively connected to one of the interfaces on the first edge a.
  • the interfaces on the edge a can also be referred to as a converter interface.
  • the interfaces on the second edge b can be connected to, for example, a coupling element 9 (e.g. a switch or router), via which the ballast can be connected to other components/ballasts.
  • a time control circuit 10 or timer can also be connected to one of the interfaces on the second edge b.
  • communication with a remote control 11 via radio or infrared and corresponding interfaces is also possible.
  • the signaling interface is designated as S by way of example. In principle, any interface other than the programming interface can be regarded as a signaling interface S.
  • the circuit board 1 does not have to be a regular geometric body.
  • the interfaces arranged on at least one edge can also be arranged one above the other in a pyramid-like manner.
  • a further interface arranged above/below an interface can be arranged slightly offset from the interior of the circuit board 1.
  • the programming interface can be protected against misuse by separating it in hardware and/or securing it cryptographically.
  • the signaling interface S can be used to connect switches, timers, remote controls, etc.
  • a separate interface can be provided for other signal generators such as sensors (motion sensor, brightness sensor, humidity sensor, microphones, presence sensor, ). However, the corresponding signals can also be fed to the signaling interface.
  • the signaling interface S and optionally other interfaces are preferably a USB interface, I2C interface or DALI interface.
  • the microprocessor 2 can provide suitable microprocessor interfaces for connecting the interfaces.
  • the processing by the microprocessor 2 can be configured via the application software A as explained above, and this can thus change the ballast V and in particular a lighting system or its functionality. It is thus possible for a user to create an application software A that then enables specific functionalities of the ballast V.
  • the at least one application software A can then be used independently of an implementation of the interfaces and configurations used.
  • the microprocessor can, for example, be connected to another ballast or converter via a fourth interface. This interface can be designed as a DALI, SPI or I 2 C interface. Alternatively, the microprocessor can also be integrated in the other ballast or converter.
  • the ballast V can have only a single signaling interface S in terms of hardware, which at the same time forms further interfaces in terms of software.
  • the programming device 4, a microphone arrangement 5, a humidity sensor 6 and/or a presence sensor 7 can be connected to the signaling interface S.
  • further participants T such as further ballasts of a lighting system, for example the lighting system 8, can be connected to the signaling interface S.
  • a coupling element 9 can additionally or alternatively be connected to the signaling interface S.
  • a time control circuit 10 or timer and/or a remote control 11 can also be connected to the signaling interface S.
  • the signaling interface S can simultaneously form the programming interface P.
  • the signaling interface S can be formed by a LAN interface or WLAN interface, which simultaneously forms the programming interface P.
  • the ballast V can also have an I2C interface in order to forward the data transmitted via the LAN interface or WLAN interface to other participants connected to the I2C interface, such as other ballasts and/or sensors. It would be possible for both the LAN interface or WLAN interface and the I2C interface to form the signaling interface S, which simultaneously forms the programming interface P.
  • ballast V can also have a DALI interface, for example to communicate with DALI sensors and/or DALI ballasts connected there.
  • the ballast V it would also be possible for the ballast V to have a signaling interface S and for at least one further interface to be present in hardware in order to connect further participants that cannot communicate according to a protocol of the signaling interface S.
  • the signaling interface S can be formed by a LAN interface or WLAN interface, which simultaneously forms the programming interface P.
  • the ballast V can have a DALI interface in order to communicate, for example, with DALI sensors and/or DALI ballasts connected there.
  • Fig.2 shows an example of a possibility in which the Microprocessor 2 communicates with one or more ballasts 20, 21, 22, 23.
  • Fig. 2a a lamp 24 with a ballast 20 is shown, which has the microprocessor 2 and the memory unit 3.
  • the ballast 20 corresponds in this example to the ballast V of the Fig.1 or the other examples.
  • the memory unit 3 can, for example, be integrated into the microprocessor 2.
  • the microprocessor 2 and the memory unit 3 are arranged within the ballast 20.
  • the microprocessor 2 and the memory unit 3 it would also be possible for the microprocessor 2 and the memory unit 3 to be arranged outside the ballast 20 but within the luminaire 24. At least the microprocessor 2 is connected to the ballast 20.
  • ballasts 21, 22, 23 of luminaires (not shown) are shown, each of which has only one converter, but does not provide a microprocessor themselves.
  • the communication between the various ballasts or converters can then take place, for example, via a DALI bus or an I2C bus.
  • only one of the luminaires or one of the ballasts can be expanded using the application software A.
  • the application software A can also determine the control of the other ballasts (converters), so that, for example, depending on the configuration of the ballast (converter) 20, the application software A can configure or operate the ballast or converter in a way that is appropriate to the situation and location.
  • At least a plurality of ballasts may each have a microprocessor and a memory unit.
  • the plurality of ballasts may have a Signaling interface S, which can simultaneously form the programming interface P, so that the application software A can be transmitted to several ballasts.
  • the microprocessor 2 does not necessarily have to be housed in a luminaire or in a ballast, but can also be provided externally.
  • the microprocessor can be connected to several stations and in particular to several ballasts, converters or luminaires 25, 26, 27 in a network by means of the coupling element 9, wherein the coupling element 9 can be, for example, a gateway with a LAN interface, a WLAN router or a DALI bus master to which several ballasts, converters or luminaires 25, 26, 27 can be connected. Communication with the ballasts, converters or luminaires 25, 26, 27 can then take place digitally via the connection provided, e.g. using the I2C, DALI or DSI protocol.
  • a microprocessor can also be provided in each ballast or in each luminaire.
  • the coupling element 9 it would also be possible for the coupling element 9 to be designed in such a way that it has a LAN interface or WLAN interface.
  • This LAN interface or WLAN interface can form the signaling interface S.
  • the coupling element 9 can also have an I2C interface in order to, for example, forward the data transmitted via the LAN interface or WLAN interface to other participants connected to the I2C interface, such as a ballast V or ballast 20 and/or sensors.
  • both the LAN interface or WLAN interface both the I2C interface form the signaling interface S, which simultaneously forms the programming interface P.
  • data received from the coupling element 9 via the LAN interface or WLAN interface can be passed on via the I2C interface to the ballast V or ballast 20 connected there.
  • a signaling interface S and a programming interface P can be formed at the same time, so that application software A that can be configured via the programming interface P can be executed on the ballast V or 20.
  • the coupling element 9 can also be designed to execute the application software A.
  • the coupling element 9 can also have a DALI interface, for example to communicate with DALI sensors and/or DALI ballasts connected there.
  • the application software A can be transmitted in individual packets via the programming interface P.
  • these packets can each be provided with a port address.
  • the packets with the port address can be received by the microprocessor 2 of the ballast 20 and assigned to the corresponding port within the memory 3.
  • the individual packets can be transmitted in encrypted form via the programming interface P.
  • the microprocessor 2 of the ballast 20 can receive the encrypted packets and match their port address to the corresponding port of the memory unit 3. be assigned to.
  • operating data can be recorded, set and/or evaluated in the ballast V or 20 by the application software
  • operating parameters can be recorded, set and/or evaluated and specified which, for example, specify a dimming/lighting level for a room and/or a maximum/minimum operating temperature, or define when an incoming signal is evaluated as detection of a presence in a room.
  • the limit and/or threshold values for humidity, air pressure, CO2 content or noise level of the environment can be specified, and when these are reached, certain actions are to be carried out by the application software.
  • the application software can, for example, specify that an image is taken via a camera module when certain operating data or operating parameters (for example those supplied by a presence sensor) exceed a threshold value or level.
  • a DALI interface, a Bluetooth interface, a LAN interface, a PLC interface and/or a USB interface can be provided on the hardware side as a signaling interface S.
  • One or more microphones can also be provided.
  • the application software A can also determine how incoming signals are evaluated. For example, filters (noise filters, echo filters, etc.) can be applied to the signals. Parameters and evaluations can also be defined for specific application scenarios (for example, a large room with a large number of Office room dividers (cubicles)) or situations for order picking can be defined. The room size in which an installation is to take place or the number of lights can also be defined in an application software, which can then be selected or specified accordingly. Test programs can also be executed using the application software A.
  • the application software can be created in JAVA, PYTHON, PEARL, C, C++, C#, RUBY, GO,...
  • ballast mentioned above is representative of converters, sensors, lights and other participants in a lighting system.
  • the technologies, designs and protocols mentioned for the interfaces are essentially interchangeable.
  • the interfaces can either be open to the outside or hidden.
  • a selectively openable and closable cover for the respective interfaces is of course also possible.
  • circuit board 1 was described above as being arranged primarily in the ballast, it should be understood that the circuit board 1 can alternatively or additionally be arranged in other participants and components of a lighting system, for example the lighting system 8.
  • the circuit board 1 can also be part of a sensor or an actuator.
  • an intelligent sensor IS which preferably comprises the circuit board 1 as described above. Consequently, the description of the ballast V and the Fig.1 essentially also for the intelligent sensor IS.
  • the intelligent sensor IS can be connected to the lighting system BS.
  • the intelligent sensor IS can also be connected to a higher-level bus system (e.g. an IPv6 bus system, overlay network, ...) and have a microprocessor 2, a memory unit 3 and in particular application software A.
  • the intelligent sensor IS can communicate with the microprocessor 2 via a wire or wirelessly (dashed double arrow).
  • the microprocessor 2 does not necessarily have to be part of the intelligent sensor IS.
  • the intelligent sensor IS can read and store data from several connected sensors NIS, which have no intelligence, ie in particular no microprocessor and memory, via a wire via a bus line BL or wirelessly. Read data can be processed by the microprocessor 2.
  • the lighting system BS can also have further intelligent sensors and thus connect at least two sensors to one another.
  • the bus line BL can form the signaling interface S.
  • the programming interface P and the signaling interface S can use the same hardware and be separated only in software.
  • the intelligent sensor IS can also provide functions and/or limits for the non-intelligent sensors NIS or other intelligent sensors IS can specify or take over.
  • the intelligent sensor IS can control and/or configure one or more ballasts or converters depending on the data acquired, e.g. from the non-intelligent sensors NIS and/or its own data.
  • the non-intelligent sensors NIS can be designed as simple motion detectors (e.g. PIR) or light sensors (e.g. LDR).
  • the intelligent sensor IS can be a thermal imaging camera. If a detection event is recorded by a non-intelligent sensor NIS, it can transmit information to the intelligent sensor IS that a detection event has been recorded.
  • the application software A of the intelligent sensor IS can evaluate the transmitted information in an application-specific manner and, depending on this, control at least one other participant T of the lighting system BS, preferably a ballast or a converter.
  • the intelligent sensor IS and/or the non-intelligent sensors NIS can also be integrated into one or more ballasts or converters.

Landscapes

  • Circuit Arrangement For Electric Light Sources In General (AREA)

Claims (12)

  1. Composant pour un système d'éclairage (BS), qui est un appareil ballast (V) pour des moyens d'éclairage à DEL ou un capteur intelligent (IS), le composant présentant en outre : un microprocesseur (2) comportant au moins une unité de mémoire (3) et une carte de circuit imprimé (1), comportant au moins une interface de programmation (P), et au moins une interface de signalisation (S) montée sur celle-ci, le microprocesseur pouvant être configuré par l'intermédiaire de l'interface de programmation (P) et au moins un logiciel d'application (A) exécutable par le microprocesseur (2) pouvant être transmis par l'intermédiaire de l'interface de programmation (P) dans l'au moins une unité de mémoire (3), le logiciel d'application (A) influençant au moins l'une des fonctionnalités suivantes du composant :
    - interaction avec d'autres capteurs,
    - évaluation de signaux transmis à l'interface de signalisation,
    - commande du moyen d'éclairage,
    - activation/désactivation d'interfaces du composant,
    - activation/désactivation de protocoles de communication et
    - détection, réglage et/ou évaluation de données de fonctionnement et/ou de paramètres de fonctionnement du composant,
    caractérisé en ce que
    l'interface de programmation (P) est d'abord bloquée pour une transmission du logiciel d'application (A) et peut être activée par transmission d'un code au composant pour la transmission du logiciel d'application (A) par l'intermédiaire de l'interface de programmation (P) dans l'au moins une unité de mémoire (3).
  2. Composant selon la revendication 1, l'au moins un logiciel d'application (A) fournissant, mettant à disposition et/ou modifiant une interface de programmation d'application.
  3. Composant selon la revendication 1 ou 2, le microprocesseur exécutant un sous-système d'abstraction matérielle, par l'intermédiaire duquel l'au moins un logiciel d'application (A) accède à l'interface de programmation (P) et/ou l'interface de signalisation (S).
  4. Composant selon l'une des revendications précédentes, l'interface de programmation (P) étant une interface sans fil ou câblée, comprenant une interface Bluetooth, WLAN, LAN, GPIO ou Zigbee.
  5. Composant selon l'une des revendications précédentes, l'interface de signalisation (S) servant à la connexion d'au moins une unité de signalisation parmi : commutateur, bouton-poussoir, minuteur, commande à distance, détecteur de présence (5), capteur de clarté, capteur d'humidité (6), capteur de température et microphone (5).
  6. Composant selon l'une des revendications précédentes, l'interface de signalisation (S) étant conçue comme une interface DALI, DSI, SPI, USB ou I2C.
  7. Composant selon l'une des revendications précédentes, l'interface de programmation (P) et l'interface de signalisation (S) utilisant le même matériel et étant séparées l'une de l'autre uniquement côté logiciel.
  8. Composant selon l'une des revendications précédentes, le composant étant un appareil ballast et l'appareil ballast (V) communiquant sans fil et/ou de manière câblée par l'intermédiaire d'au moins une interface avec d'autres appareils ballast et/ou au moins un convertisseur (8).
  9. Composant selon l'une des revendications précédentes, le logiciel d'application (A) libérant ou bloquant au moins une fonction fournie par un élément parmi interface de programmation (P), interface de signalisation (S) et/ou interface de programmation d'application.
  10. Composant selon l'une des revendications précédentes, toutes les interfaces étant disposées sur au moins un bord (a, b, c, d) de la carte de circuit imprimé (1).
  11. Composant selon l'une des revendications précédentes, le microprocesseur (2) étant un système à une puce.
  12. Système d'éclairage (BS) ou éclairage comportant un composant selon l'une des revendications précédentes.
EP21201386.6A 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation Active EP3955705B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP24153076.5A EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE202015106224.9U DE202015106224U1 (de) 2015-11-17 2015-11-17 Vorschaltgerät für Leuchtmittel mit Mikroprozessor und Programmierungsschnittstelle
EP16797910.3A EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation
PCT/EP2016/077994 WO2017085182A1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP16797910.3A Division EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation
EP16797910.3A Division-Into EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP24153076.5A Division-Into EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation
EP24153076.5A Division EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation

Publications (2)

Publication Number Publication Date
EP3955705A1 EP3955705A1 (fr) 2022-02-16
EP3955705B1 true EP3955705B1 (fr) 2024-05-08

Family

ID=57345949

Family Applications (3)

Application Number Title Priority Date Filing Date
EP24153076.5A Pending EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation
EP21201386.6A Active EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation
EP16797910.3A Active EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP24153076.5A Pending EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP16797910.3A Active EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Country Status (6)

Country Link
US (1) US10257912B2 (fr)
EP (3) EP4355033A3 (fr)
CN (1) CN108605399A (fr)
AT (1) AT16920U1 (fr)
DE (1) DE202015106224U1 (fr)
WO (1) WO2017085182A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102020117446A1 (de) 2020-07-02 2022-01-05 Zumtobel Lighting Gmbh Vorrichtung mit multifunktionalem Anschluss für Nicht-DALI-Bediengeräte
US11966213B2 (en) * 2020-08-03 2024-04-23 Abl Ip Holding Llc Handheld programmer for LED drivers

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7619539B2 (en) 2004-02-13 2009-11-17 Lutron Electronics Co., Inc. Multiple-input electronic ballast with processor
DE102004061294B4 (de) * 2004-12-20 2020-03-19 Tridonic Gmbh & Co Kg Verfahren zur Programmierung eines Betriebsgerätes für Leuchtmittel, Schnittstelle für ein Betriebsgerät für Leuchtmittel und Betriebsgerät für Leuchtmittel
CN101199237A (zh) * 2005-06-02 2008-06-11 皇家飞利浦电子股份有限公司 照明系统以及用于控制照明系统的方法
US9338839B2 (en) * 2006-03-28 2016-05-10 Wireless Environment, Llc Off-grid LED power failure lights
US8491159B2 (en) * 2006-03-28 2013-07-23 Wireless Environment, Llc Wireless emergency lighting system
US8994276B2 (en) * 2006-03-28 2015-03-31 Wireless Environment, Llc Grid shifting system for a lighting circuit
US20070288738A1 (en) * 2006-06-09 2007-12-13 Dale Jason N System and method for selecting a random processor to boot on a multiprocessor system
DE102007004397B4 (de) * 2007-01-29 2019-06-13 Tridonic Gmbh & Co Kg Verfahren und System zur Datenübertragung
WO2009097900A1 (fr) * 2008-02-08 2009-08-13 Osram Gesellschaft mit beschränkter Haftung Dispositif et procédé en particulier pour la commande d'une lampe
US8543249B2 (en) * 2008-04-14 2013-09-24 Digital Lumens Incorporated Power management unit with modular sensor bus
DE102008053486A1 (de) 2008-10-28 2010-05-27 Osram Gesellschaft mit beschränkter Haftung Elektronisches Vorschaltgerät mit standardisierten Datenschnittstelle
DE102009032026A1 (de) 2009-07-07 2011-01-13 Tridonicatco Gmbh & Co. Kg Betriebsgerät für Leuchtmittel
US8492988B2 (en) * 2009-10-07 2013-07-23 Lutron Electronics Co., Inc. Configurable load control device for light-emitting diode light sources
DE102009056152A1 (de) * 2009-11-27 2011-06-01 Ledon Lighting Jennersdorf Gmbh Beleuchtungsfernsteuerung
WO2011106868A1 (fr) * 2010-03-01 2011-09-09 Led Roadway Lighting Ltd. Système de commande centralisée sans fil de réverbères basé sur un système de positionnement global (gps)
DE102010025082A1 (de) 2010-06-25 2011-12-29 Hella Kgaa Hueck & Co. Beleuchtungsvorrichtung für Straßen
US9049753B1 (en) * 2011-08-19 2015-06-02 Appalachian Lighting Systems, Inc. Lighting device monitor and communication apparatus
US8547036B2 (en) * 2011-11-20 2013-10-01 Available For Licensing Solid state light system with broadband optical communication capability
DE102011086702A1 (de) 2011-11-21 2013-05-23 Tridonic Gmbh & Co. Kg Konfiguration von Betriebsgeräten für Leuchtmittel
DE102012011049A1 (de) 2012-06-02 2013-12-05 Diehl Aerospace Gmbh Leuchtvorrichtung mit einem zumindest eine LED aufweisenden Leuchtmittel
US10064251B2 (en) * 2013-03-15 2018-08-28 Cree, Inc. Updatable lighting fixtures and related components
KR20150009880A (ko) * 2013-07-17 2015-01-27 삼성전자주식회사 직관형 발광 장치
PT3036976T (pt) 2013-08-19 2020-01-20 Signify Holding Bv Dispositivo de iluminação programável e método e sistema para programação de dispositivo de iluminação
US9332619B2 (en) * 2013-09-20 2016-05-03 Osram Sylvania Inc. Solid-state luminaire with modular light sources and electronically adjustable light beam distribution
US10154569B2 (en) * 2014-01-06 2018-12-11 Cree, Inc. Power over ethernet lighting fixture
DE102014200297A1 (de) * 2014-01-10 2015-07-16 Tridonic Gmbh & Co Kg Betriebsgerät und Kommunikationsadapter für den Außeneinsatz
CN103870403A (zh) * 2014-02-16 2014-06-18 金德奎 可用手机或电脑进行软件更新和/或自定义控制方案的led灯具及其方法

Also Published As

Publication number Publication date
CN108605399A (zh) 2018-09-28
AT16920U1 (de) 2020-12-15
EP3955705A1 (fr) 2022-02-16
EP4355033A3 (fr) 2024-05-29
EP3378286A1 (fr) 2018-09-26
EP4355033A2 (fr) 2024-04-17
EP3378286B1 (fr) 2022-03-09
US10257912B2 (en) 2019-04-09
US20180270932A1 (en) 2018-09-20
WO2017085182A1 (fr) 2017-05-26
DE202015106224U1 (de) 2017-02-20

Similar Documents

Publication Publication Date Title
EP3683691B1 (fr) Dispositif pour la connexion en tant que noeud de bus à un bus de données différentiel à deux fils d'un système de bus de données pour la transmission de données d'éclairage pour des moyens d'éclairage
DE102014012252A1 (de) Verhindern einer verkehrsanalyse
DE102011086702A1 (de) Konfiguration von Betriebsgeräten für Leuchtmittel
DE102011053883B4 (de) Notlichtbeleuchtungsanlage mit Datenkommunikationsfähigkeiten
WO2008009637A1 (fr) Appareil de commutation, système de commande d'une lampe et système de commande de lampe pour un bâtiment comportant au moins un dispositif d'éclairage
DE102016210414B4 (de) Adresszuweisung und Konfigurierung von Komponenten eines Beleuchtungssystems mittels Transponder
EP3955705B1 (fr) Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation
EP3391713B1 (fr) Protocolisation décentralisé des états de fonctionnement de composants de la technique du bâtiment
EP3375259B1 (fr) Système et procédé de détermination de position d'une balise mobile
EP3339873A1 (fr) Fonctionnement d'un dispositif d'émission d'une installation d'éclairage comportant un dispositif d'éclairage
DE102016125631A1 (de) Installieren oder Ändern eines ablauffähigen Rechnerprogramms in einem Beleuchtungssystem
DE102015216112A1 (de) Verfahren zur Konfiguration einer Beleuchtungskomponente, konfigurierbare Beleuchtungskomponente und System mit einer derartigen Beleuchtungskomponente
DE102018119923A1 (de) Beleuchtungssystem und Steuerung
EP3427548B1 (fr) Système d'éclairage à configuration automatique de balises
EP2702834B1 (fr) Dispositif de fonctionnement pour moyen d'éclairage et adaptateur pour alimenter ledit dispositif de fonctionnement en énergie
DE202014106166U1 (de) Gebäudetechnik-Kommunikationssystem
DE102020123332B4 (de) Basismodul eines Netzwerkaufbaus sowie Netzwerkaufbau und Verfahren zum Konfigurieren eines Erweiterungsmoduls des Netzwerkaufbaus
WO2018114065A1 (fr) Activation et désactivation de l'unité de réception d'un dispositif d'éclairage
DE102014019534A1 (de) Vorrichtung zur verwendung in einem dynamischen netzwerk und dynamisches netzwerk
EP3113323B1 (fr) Dispositif d'interaction ayant des fonctionnalites integrees destinees a generer, traiter et emettre et recevoir des declencheurs
DE102020117446A1 (de) Vorrichtung mit multifunktionalem Anschluss für Nicht-DALI-Bediengeräte
AT518226A2 (de) Steuersystem und Verfahren
EP4152895A1 (fr) Système d'éclairage
DE102013108927A1 (de) Vorrichtung und Verfahren zur Steuerung von Leuchten
DE102019103889A1 (de) Ein- und Auskoppelung von Daten und Datentransport über elektrische Versorgungsleitung von Beleuchtungssystemen

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

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

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AC Divisional application: reference to earlier application

Ref document number: 3378286

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

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: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220420

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

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

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

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

AC Divisional application: reference to earlier application

Ref document number: 3378286

Country of ref document: EP

Kind code of ref document: P

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

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

Ref legal event code: R096

Ref document number: 502016016532

Country of ref document: DE