EP2922370B1 - Techniques et interface utilisateur graphique de commande d'éclairage à semi-conducteurs avec distribution de faisceau de lumière réglable électroniquement - Google Patents

Techniques et interface utilisateur graphique de commande d'éclairage à semi-conducteurs avec distribution de faisceau de lumière réglable électroniquement Download PDF

Info

Publication number
EP2922370B1
EP2922370B1 EP15160103.6A EP15160103A EP2922370B1 EP 2922370 B1 EP2922370 B1 EP 2922370B1 EP 15160103 A EP15160103 A EP 15160103A EP 2922370 B1 EP2922370 B1 EP 2922370B1
Authority
EP
European Patent Office
Prior art keywords
solid
luminaire
state luminaire
gui
light
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
EP15160103.6A
Other languages
German (de)
English (en)
Other versions
EP2922370A3 (fr
EP2922370A2 (fr
Inventor
Mervyn Anthony
Jeffrey W. Holt
Michael A. Quilici
Seung Cheol Ryu
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.)
Osram Sylvania Inc
Original Assignee
Osram Sylvania Inc
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
Priority claimed from US14/221,589 external-priority patent/US9801260B2/en
Application filed by Osram Sylvania Inc filed Critical Osram Sylvania Inc
Publication of EP2922370A2 publication Critical patent/EP2922370A2/fr
Publication of EP2922370A3 publication Critical patent/EP2922370A3/fr
Application granted granted Critical
Publication of EP2922370B1 publication Critical patent/EP2922370B1/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/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
    • 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/196—Controlling the light source by remote control characterised by user interface arrangements
    • H05B47/1965—Controlling the light source by remote control characterised by user interface arrangements using handheld communication devices
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F21—LIGHTING
    • F21S—NON-PORTABLE LIGHTING DEVICES; SYSTEMS THEREOF; VEHICLE LIGHTING DEVICES SPECIALLY ADAPTED FOR VEHICLE EXTERIORS
    • F21S10/00—Lighting devices or systems producing a varying lighting effect
    • F21S10/02—Lighting devices or systems producing a varying lighting effect changing colors
    • F21S10/023—Lighting devices or systems producing a varying lighting effect changing colors by selectively switching fixed light sources
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F21—LIGHTING
    • F21S—NON-PORTABLE LIGHTING DEVICES; SYSTEMS THEREOF; VEHICLE LIGHTING DEVICES SPECIALLY ADAPTED FOR VEHICLE EXTERIORS
    • F21S8/00—Lighting devices intended for fixed installation
    • F21S8/02—Lighting devices intended for fixed installation of recess-mounted type, e.g. downlighters
    • F21S8/026—Lighting devices intended for fixed installation of recess-mounted type, e.g. downlighters intended to be recessed in a ceiling or like overhead structure, e.g. suspended ceiling
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F21—LIGHTING
    • F21Y—INDEXING SCHEME ASSOCIATED WITH SUBCLASSES F21K, F21L, F21S and F21V, RELATING TO THE FORM OR THE KIND OF THE LIGHT SOURCES OR OF THE COLOUR OF THE LIGHT EMITTED
    • F21Y2107/00—Light sources with three-dimensionally disposed light-generating elements
    • F21Y2107/10—Light sources with three-dimensionally disposed light-generating elements on concave supports or substrates, e.g. on the inner side of bowl-shaped supports
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F21—LIGHTING
    • F21Y—INDEXING SCHEME ASSOCIATED WITH SUBCLASSES F21K, F21L, F21S and F21V, RELATING TO THE FORM OR THE KIND OF THE LIGHT SOURCES OR OF THE COLOUR OF THE LIGHT EMITTED
    • F21Y2115/00—Light-generating elements of semiconductor light sources
    • F21Y2115/10—Light-emitting diodes [LED]

Definitions

  • the present disclosure relates to solid-state lighting (SSL) fixtures and more particularly to light-emitting diode (LED)-based luminaires.
  • SSL solid-state lighting
  • LED light-emitting diode
  • Traditional adjustable lighting fixtures such as those utilized in theatrical lighting, employ mechanically adjustable lenses, track heads, gimbal mounts, and other mechanical parts to adjust the angle and direction of the light output thereof. Mechanical adjustment of these components is normally provided by actuators, motors, or manual adjustment by a lighting technician. Also, existing lighting fixtures that utilize digital multiplexer (DMX) interfaces to physically control light distribution require entry into that adapter of the address of each individual light-emitting diode (LED) that is to be turned on or off.
  • DMX digital multiplexer
  • US2011/181207A1 discloses a luminaire provided with a housing with light-emitting elements which are located near a light emission side of the housing and which are activated in that a user touches one or more sensors accommodated in a wall of the housing.
  • US2014/070707A1 discloses a lighting control system that includes a display unit with a touch panel for displaying an image of a lighting fixture.
  • the present invention relates to a method of electronically controlling a light beam distribution of a solid-state luminaire including the steps according to claim 1, a non-transient computer program product encoded with instructions according to claim 10 and a graphical user interface on a computing system according to claim 13. Additional features of preferable embodiments are recited in the respective dependent claims.
  • UIs user interfaces
  • the disclosed UI may be configured, in accordance with some embodiments, to provide a user with the ability to control, by wireless and/or wired connection, the light distribution of an associated solid-state luminaire in a given space.
  • the UI may be hosted by any computing device, portable or otherwise, and may be used to control any given light distribution capability provided by a paired luminaire.
  • the user may provide such control without need to know details about the luminaire, such as the quantity of solid-state lamps, or their individual addresses, or the address of the fixture itself.
  • the disclosed techniques may involve acquiring spatial information of the space that hosts the luminaire and/or providing user-selected distribution of light within that space. Numerous configurations and variations will be apparent in light of this disclosure.
  • UIs user interfaces
  • the disclosed UI design logic may be configured, in accordance with some embodiments, to provide a user with the ability to control, by wireless and/or wired connection, the light distribution of an associated solid-state luminaire in a given space.
  • the disclosed UI application may be installed on any computing device, portable or otherwise, and may be used to control one or more light distribution capabilities provided by a given solid-state luminaire.
  • the user may provide such control without need to know details about the associated luminaire, such as the quantity of solid-state lamps, or their individual addresses, or the address of the fixture itself.
  • the disclosed control techniques may involve acquiring spatial information of the space (e.g., room, office, etc.) that hosts the target luminaire and/or providing user-selected distribution of light within that space.
  • the disclosed UI application may be configured to discover the presence of multiple luminaires in a given space and prompt the user to select which luminaire(s) are to be controlled.
  • the UI may be presented as a graphical UI (GUI), while in some other embodiments, the UI may be presented as a photographical UI.
  • GUI graphical UI
  • the disclosed techniques and UIs e.g., graphical UI; photographical UI
  • the present disclosure is not so limited.
  • the disclosed techniques can be used, for example, with non-mobile computing devices (e.g., a desktop computer, a television, etc.), in accordance with some embodiments.
  • non-mobile computing devices e.g., a desktop computer, a television, etc.
  • Numerous suitable host platforms will be apparent in light of this disclosure.
  • FIG. 1A is a block diagram of a lighting system 1000a configured in accordance with an embodiment of the present disclosure
  • Figure 1B is a block diagram of a lighting system 1000b configured in accordance with another embodiment of the present disclosure.
  • system 1000a/1000b may include: a luminaire 100; one or more controllers 200 operatively coupled with luminaire 100; and a computing device 300 communicatively coupled with luminaire 100.
  • computing device 300 may be utilized, in accordance with some embodiments, to control the light output of luminaire 100 (e.g., to customize the light distribution for a given space or surface of incidence).
  • system 1000a/1000b optionally may include an image capture device 400 configured, for example, to capture image data of a given space or surface of incidence to be lighted using luminaire 100. A discussion of these is provided below.
  • computing device 300 may be configured to be directly communicatively coupled with luminaire 100, as described herein. In some other cases, however, device 300 and luminaire 100 optionally may be indirectly communicatively coupled with one another, for example, by an intervening or otherwise intermediate network 500 for facilitating the transfer of data between device 300 and luminaire 100.
  • Network 500 may be any suitable communications network, and in some example cases may be a public and/or private network, such as a private local area network (LAN) operatively coupled to a wide area network (WAN) such as the Internet.
  • LAN local area network
  • WAN wide area network
  • network 500 may include a wireless local area network (WLAN) (e.g., Wi-Fi® wireless data communication technologies).
  • WLAN wireless local area network
  • network 500 may include Bluetooth® wireless data communication technologies.
  • network 500 may include supporting infrastructure and/or functionalities such as a server and a service provider, but such features are not necessary to carry out communication via network 500.
  • Luminaire 100 can have any of a wide range of configurations.
  • FIGs 2A-2B are cross-sectional and plan views, respectively, of a luminaire 100 configured in accordance with an embodiment of the present disclosure.
  • luminaire 100 may include a housing 110 and a plurality of solid-state lamps 130 arranged within the plenum 115 of housing 110.
  • luminaire 100 may be configured, for example, as described in US2015/0085475A1 , titled "Solid-State Luminaire with Electronically Adjustable Light Beam Distribution.”
  • Each lamp 130 may include one or more solid-state emitters 131 (e.g., light-emitting diodes, or LEDs) and tunable electro-optic componentry configured to provide that lamp 130 with its own electronically adjustable light beam, in accordance with some embodiments.
  • Lamps 130 can be electronically controlled individually and/or in conjunction with one another, for example, to provide highly adjustable light emissions from the luminaire 100 (e.g., digitally addressable, pixelated control over light distribution), in accordance with some embodiments.
  • Other suitable configurations for luminaire 100 will depend on a given application and will be apparent in light of this disclosure.
  • the solid-state lamps 130 of luminaire 100 can be electronically controlled individually and/or in conjunction with one another, for example, to provide highly adjustable light emissions from the luminaire 100.
  • luminaire 100 may include or otherwise be communicatively coupled with one or more controllers 200 which can be used to electronically control the output of the emitters 131 individually and/or in conjunction with one another (e.g., as an array or partial array), thereby electronically controlling the light output of luminaire 100 as a whole.
  • a given controller 200 may be responsible for translating received inputs (e.g., directly and/or indirectly received from computing device 300) to control one or more of the solid-state lamps 130 of luminaire 100 to obtain a given desired light distribution.
  • a given controller 200 may be configured to provide for electronic adjustment, for example, of the beam direction, beam angle, beam distribution, and/or beam diameter for each lamp or some sub-set of the available lamps 130 of luminaire 100, thereby allowing for customizing the spot size, position, and/or distribution of light in a given space or on a given surface of incidence.
  • controller 200 may provide for electronic adjustment, for example, of the brightness (dimming) and/or color of light, thereby allowing for dimming and/or color mixing/tuning, as desired.
  • FIG. 1A is a block diagram of a lighting system 1000a configured in accordance with an embodiment of the present disclosure.
  • a controller 200 is operatively coupled (e.g., by a communication bus/interconnect) with the solid-state lamps 130 1- N of luminaire 100.
  • controller 200 may output a control signal to any one or more of the solid-state lamps 130 and may do so, for example, based on wired and/or wireless input received from computing device 300, discussed below.
  • luminaire 100 may be controlled in such a manner as to output any number of output beams 1- N , which may be varied in beam direction, beam angle, beam size, beam distribution, brightness/dimness, and/or color, as desired for a given target application or end-use, in accordance with some embodiments.
  • each solid-state lamp 130 1- N of luminaire 100 includes its own controller 200.
  • each solid-state lamp 130 may be considered as effectively having its own mini-controller, thus providing luminaire 100 with a distributed controller 200.
  • the controller 200 of a given solid-state lamp 130 may be populated, for example, on a printed circuit board (PCB) associated with that lamp 130.
  • PCB printed circuit board
  • a given controller 200 may output a control signal to an associated solid-state lamp 130 of luminaire 100 and may do so, for example, based on wired and/or wireless input received from computing device 300, discussed below.
  • luminaire 100 may be controlled in such a manner as to output any number of output beams 1- N , which may be varied in beam direction, beam angle, beam size, beam distribution, brightness/dimness, and/or color, as desired for a given target application or end-use, in accordance with some embodiments.
  • a given controller 200 may utilize any of a wide variety of digital communications protocol, such as, for example, a digital multiplexer (DMX) interface, a Wi-FiTM protocol, a Bluetooth® protocol, a digital addressable lighting interface (DALI) protocol, a ZigBee protocol, or any other suitable communications protocol, wired and/or wireless, as will be apparent in light of this disclosure.
  • a given controller 200 may be configured as a terminal block or other pass-through such that computing device 300 is effectively coupled directly with the individual solid-state emitters 131 of luminaire 100. Numerous suitable configurations will be apparent in light of this disclosure.
  • control of the emission of luminaire 100 may be provided, for example, by a wired and/or wireless control interface provided by computing device 300, which may be a touch-sensitive electronic device, in some cases.
  • device 300 may include a touch-sensitive display 340 configured to provide a touch-based graphical user interface (GUI) 370 that may be utilized to control the solid-state emitters 131 of the solid-state lamps 130 of luminaire 100 individually and/or in conjunction with one another, as described herein.
  • GUI graphical user interface
  • the touch-sensitive interface may be operatively coupled with the one or more controllers 200, which in turn interpret the input from computing device 300 and provide the desired control signal(s) to one or more of the solid-state emitters 131 of luminaire 100.
  • the touch-sensitive interface may be operatively coupled directly with the solid-state emitters 131 to control them directly.
  • Computing device 300 may be any portable/mobile or non-mobile electronic device configured for wired and/or wireless communication.
  • device 300 may include or otherwise be configured to communicate with a display 340 that is touch-sensitive, as discussed below.
  • Some example suitable devices 300 may include, in part or in whole: (1) a laptop/notebook computer; (2) a tablet computer; (3) a mobile phone or smartphone (e.g., iPhone®, Android®-based phone, Blackberry®, Symbian®-based phone, Palm®-based phone, etc.); (4) a personal digital assistant (PDA); (5) a portable media player (PMP); (6) a cellular handset; (7) a handheld gaming device; (8) a gaming platform/console; (9) a desktop computing system; and/or (10) a television or other electronic visual display.
  • PDA personal digital assistant
  • computing device 300 may include any of a wide range of modules/components, as desired for a given target application or end-use.
  • computing device 300 may be configured for communication between any or all its modules/components, and in some cases, device 300 may include a communications bus/interconnect to that end. It should be noted, however, that the present disclosure is not intended to be limited in form or function to the example device 300 depicted in the figures, and numerous other suitable configurations for device 300 will be apparent in light of this disclosure.
  • device 300 may include a communication module 310, in accordance with some embodiments.
  • Communication module 310 may be configured, for example, to aid in communicatively coupling device 300 with: (1) luminaire 100 (e.g., the one or more controllers 200 thereof); (2) image capture device 400 (if optionally included); and/or (3) network 500, if desired.
  • communication module 310 can be configured, for example, to execute any suitable wireless communication protocol that allows for data/information to be passed wirelessly.
  • each of computing device 300, luminaire 100, and optional image capture device 400 can be associated with a unique ID (e.g., IP address, MAC address, cell number, or other such identifier) that can be used to assist the communicative coupling there between, in accordance with some embodiments.
  • Some example suitable wireless communication methods that can be implemented by communication module 310 of device 300 may include: radio frequency (RF) communications (e.g., Wi-Fi®; Bluetooth®; near field communication or NFC); IEEE 802.11 wireless local area network (WLAN) communications; infrared (IR) communications; cellular data service communications; satellite Internet access communications; custom/proprietary communication protocol; and/or a combination of any one or more thereof.
  • RF radio frequency
  • WLAN wireless local area network
  • IR infrared
  • device 300 may be capable of utilizing multiple methods of wireless communication. In some such cases, the multiple wireless communication techniques may be permitted to overlap in function/operation, while in some other cases they may be exclusive of one another.
  • a wired connection (e.g., USB, Ethernet, FireWire, or other suitable wired interfacing) may be provided between device 300 and: (1) luminaire 100 (e.g., the one or more controllers 200 thereof); and/or (2) image capture device 400, if optionally included.
  • communication module 310 may be configured such that device 300 is able to transmit and/or receive information with respect to any given source/recipient, by wired and/or wireless connection, using any suitable protocol (e.g., LAN-based, Internet-based, cellular-based, satellite-based, or any combination thereof), as desired for a given target application or end-use.
  • device 300 may include one or more processors 320 configured, for example, to perform operations associated with device 300 and any one or more of the modules/components included therein.
  • a given processor 320 may be configured, in some embodiments, to process or otherwise interpret data that is: (1) input from a user (e.g., using a touch-sensitive display 340 and/or application 336 stored in memory 330); (2) input from an image capture device 400 (if optionally included); and/or (3) output to be received by luminaire 100.
  • Other suitable configurations of the one or more processors 320 of device 300 will depend on a given application and will be apparent in light of this disclosure.
  • device 300 may include a memory 330.
  • Memory 330 can be of any suitable type (e.g., RAM and/or ROM, or other suitable memory) and size, and in some cases may be implemented with volatile memory, non-volatile memory, or a combination thereof. Memory 330 may be utilized, for example, for processor workspace and/or to store media, programs, applications, content, etc., on device 300 on a temporary or permanent basis. Also, memory 330 can include one or more modules stored therein that can be accessed and executed, for example, by processor(s) 320.
  • memory 330 may include an operating system (OS) module 332 configured, in accordance with some embodiments, to aid in processing: (1) user input (e.g., received from display 340 and/or an application 336 stored in memory 330); and/or (2) captured image data received from optional image capture device 400.
  • OS module 332 can be implemented with any suitable OS, mobile or otherwise, such as: Android® OS from Google, Inc.; iOS® from Apple, Inc.; Windows Phone® OS from Microsoft Corp.; BlackBerry® OS from BlackBerry Ltd.; Symbian OS; Palm® OS from Palm, Inc. Other suitable types and configurations for OS module 332 will depend on a given application and will be apparent in light of this disclosure.
  • memory 330 may include a user interface (UI) module 334 configured, for example, to provide a graphical user interface (GUI) 370 (discussed below) using display 340 (e.g., which may be touch-sensitive, in some instances).
  • GUI graphical user interface
  • UI module 334 can be programmed or otherwise configured to provide a GUI 370 as variously described herein, such as with reference to the example screenshots of Figures 3A , 3B , 4A , 5A , 6A , 7B, and 7C and/or the methodologies demonstrated in Figures 4C , 5C , and 6C , which will be discussed in turn.
  • UI module 334 may include custom, proprietary, known, and/or after-developed user interface construction code (or instruction sets) that are generally well-defined and operable to present one or more control features via GUI 370 for selection and/or manipulation (e.g., by a user). It should be noted, however, that UI module 334 need not be implemented only in memory 330 (e.g., as generally shown in Figures 1A-1B ), as in some other embodiments, UI module 334 can be implemented in a combination of locations (e.g., memory 330, display 340, etc.), thereby providing the UI module 334 with a degree of functional distributedness. Other suitable configurations for UI module 334 will depend on a given application and will be apparent in light of this disclosure.
  • Memory 330 also may include one or more applications 336 stored therein.
  • memory 330 may include or otherwise have access to an image/video recording application or other software that permits image capturing/video recording using optional image capture device 400, as described herein.
  • memory 330 may include or otherwise have access to an image/video playback application or other software that permits playback/viewing of images/video captured using optional image capture device 400 or other content.
  • one or more applications 336 may be included to facilitate presentation and/or operation of GUI 370.
  • Other suitable applications 330 to be hosted/accessed by device 300 will depend on a given application and will be apparent in light of this disclosure.
  • a given module of memory 330 can be implemented in any suitable programming language, such as, for example: C; C++; objective C; JavaScript; custom or proprietary instruction sets; etc.
  • the modules of device 300 can be encoded, for example, on a machine-readable medium that, when executed by a processor (e.g., such as the one or more processors 320), carries out the desired functionality of that portion of device 300.
  • the computer-readable medium may be, for example, a hard drive, compact disk, memory stick, server, or any suitable non-transitory computer/computing device memory that includes executable instructions, or a plurality or combination of such memories.
  • Other embodiments can be implemented, for instance, with gate-level logic or an application-specific integrated circuit (ASIC) or chip set or other such purpose-built logic.
  • ASIC application-specific integrated circuit
  • Some embodiments can be implemented with a microcontroller having input/output capability (e.g., inputs for receiving user inputs; outputs for directing other components) and a number of embedded routines for carrying out a given desired functionality.
  • the functional modules of device 300 can be implemented in hardware, software, and/or firmware, as desired.
  • Other suitable modules/components for memory 330 will depend on a given application and will be apparent in light of this disclosure.
  • the display 340 of device 300 may utilize any display technology suitable, for example, for the display of images, video, text, or other desired content.
  • display 340 optionally may be touch-sensitive (e.g., to assist with the function of UI module 334, as discussed above), in some embodiments.
  • display 340 may utilize any of a wide range of touch-sensing techniques, such as, for example: resistive touch-sensing; capacitive touch-sensing; surface acoustic wave (SAW) touch-sensing; infrared (IR) touch-sensing; optical imaging touch-sensing; and/or any combination thereof.
  • SAW surface acoustic wave
  • IR infrared
  • touch-sensitive display 340 generally may be configured to detect or otherwise sense direct and/or proximate contact from a user's finger, stylus, or other suitable implement at a given location of display 340.
  • display 340 may be configured to translate such contact into an electronic signal that can be processed by device 300 (e.g., by the one or more processors 320 thereof) and manipulated or otherwise used to trigger a GUI 370 action, such as any of those discussed herein.
  • Touch-sensitive display 340 may permit provision of a GUI 370 including one or more control features (discussed below) which may be utilized, in accordance with some embodiments, to provide input to computing device 300 to be relayed to: (1) the one or more controllers 200 of luminaire 100; and/or (2) image capture device 400, if included.
  • display 340 may be integrated with computing device 300, while in some other case, display 340 may be a stand-alone component configured to communicate with device 300 using any suitable wired and/or wireless communications techniques.
  • Other suitable configurations and touch-sensitive capabilities for display 340 will depend on a given application and will be apparent in light of this disclosure.
  • device 300 may include or otherwise be operatively coupled with a non-touch-sensitive display 340 and have a touch-sensitive surface implemented therewith (e.g., a touch-sensitive track pad).
  • device 300 generally may be capable of translating direct and/or proximate contact of the touch-sensitive surface into an electronic signal that can be processed by device 300 (e.g., by the one or more processors 320 thereof) and manipulated or otherwise used to trigger a GUI 370 action, such as any of those discussed herein.
  • device 300 optionally may include a position and/or motion sensor 350 configured, for example, to aid in determining the orientation and/or movement of computing device 300 with respect to a given point of reference (e.g., a luminaire 100).
  • position and/or motion sensor 350 may be configured as traditionally done and, in accordance with some embodiments, may be communicatively coupled with orientation indicator feature 352, discussed below.
  • position and/or motion sensor 350 may be configured, for example, with geomagnetic sensing capabilities to aid in determining the orientation and/or movement of computing device 300 with respect to a geomagnetic pole (e.g., geomagnetic north). Numerous configurations will be apparent in light of this disclosure.
  • GUI graphical user interface
  • FIGS 3A and 3B illustrate example screenshots of a computing device 300 on which a GUI 370 is displayed, in accordance with some embodiments of the present disclosure.
  • display 340 can be configured to display various GUI 370 menus, sub-menus, features, icons (e.g., light-based icons), and/or buttons (e.g., virtual buttons), hereinafter referred to as GUI control features, that a user may utilize in controlling the performance/behavior of device 300, luminaire 100, and/or optional image capture device 400.
  • GUI control features e.g., virtual buttons
  • GUI 370 may be configured to allow selection from the one or more modules and/or applications stored within device 300 (e.g., within memory 330) to perform any of a wide variety of tasks/operations associated with device 300, luminaire 100, and/or optional image capture device 400.
  • a given GUI control feature can be used, in accordance with some embodiments, to provide a control signal to device 300, luminaire 100, and/or optional image capture device 400 and can be programmed or otherwise configured to that end using any suitable custom, proprietary, known, and/or after-developed techniques, as desired for a given target application or end-use.
  • GUI 370 correspondingly may be provided as a touchscreen interface with touch-sensitive virtual control features.
  • GUI 370 may be configured to provide a graphical canvas 372, in some instances.
  • graphical canvas 372 may include within its bounds two or more selectable nodes 374 which each may correspond, for example, with one or more lamps 130 of luminaire 100.
  • graphical canvas 372 may include a field of selectable GUI control features, elements, icons, and/or other graphical objects that can be used as a selectable node 374, in accordance with some embodiments. Selection of a given node 374 may be made with the user's finger, a stylus, or other suitable implement.
  • the one or more solid-state lamps 130 of luminaire 100 corresponding with such selected node 374 may be turned ON/OFF, in accordance with some embodiments.
  • the dimensions and geometry of graphical canvas 372 may be configured to correspond with the maximum light distribution boundary (or some lesser light distribution boundary, if desired) of luminaire 100 with respect to a given space or other surface of incidence (e.g., floor, wall, ceiling, etc.).
  • the quantity of nodes 374 displayed within graphical canvas 372 may correspond directly (e.g., one-to-one) with the quantity of controllable lamps 130 of luminaire 100.
  • GUI 370 may be configured to provide a photographical canvas 382, in some instances.
  • photographical canvas 382 may comprise, in part or in whole, a photograph or other image captured by image capture device 400 of the target space (e.g., room, surface, etc.) to be lighted by luminaire 100.
  • photographical canvas 382 may comprise, in part or in whole, a computer-generated image of the target space as derived from a photograph or other image (e.g., captured by image capture device 400) and/or from scanning the target space (e.g., three-dimensional modeling, machine learning, etc.).
  • photographical canvas 382 may comprise, in part or in whole, a visual rendition (e.g., line drawing, bitmap, grid array, image map, etc.) representative of the space to be lighted by luminaire 100.
  • a user may alternate between graphical canvas 372 and photographical canvas 382, as desired.
  • photographical canvas 382 may provide a view (e.g., a plan view or other desired view from a given vantage point) of a given space or target surface of incidence that is to be lighted by luminaire 100 and may include within its bounds one or more selectable zones 384 corresponding, for example, to areas which may be lighted by luminaire 100. Selection of a given zone 384 within photographical canvas 382 may be made with the user's finger, a stylus, or other suitable implement.
  • the one or more solid-state lamps 130 of luminaire 100 corresponding with such selected zone 384 may be turned ON/OFF, in accordance with some embodiments.
  • the photographical canvas 382 provided by GUI 370 may aid a user in making specific lighting distribution selections based on which zone(s) 384 of a given space/surface are to be lighted, and in determining whether a given desired lighting distribution has been achieved.
  • photographical canvas 382 may be refreshed or otherwise updated in real time, while in some other cases, refreshing/updating may occur periodically or upon user command using device 300.
  • GUI 370 may present on display 340 one or more GUI control features designed to aid a user in use, manipulation, and/or operation of device 300, luminaire 100, and/or optional image capture device 400.
  • one or more control signals may be output to alter or otherwise control the performance/behavior of device 300, luminaire 100, and/or optional image capture device 400, in accordance with some embodiments.
  • GUI 370 may include one or more virtual control features (e.g., virtual buttons, switches, knobs, pressure sensors, toggles, sliders) that a user may manually manipulate to aid in providing the desired control/operation of device 300, luminaire 100, and/or optional image capture device 400.
  • virtual control features e.g., virtual buttons, switches, knobs, pressure sensors, toggles, sliders
  • computing device 300 may include one or more physical control features (e.g., physical buttons, switches, knobs, pressure sensors, toggles, sliders) to any such end. Numerous configurations will be apparent in light of this disclosure.
  • a given control feature may be assigned to or otherwise associated with any of a wide range of functions/operations of device 300, luminaire 100, and/or optional image capture device 400, as desired for a given target application or end-use.
  • a given GUI control feature may be configured to make a selection from one or more options displayed by GUI 370 on display 340.
  • a given control feature may be configured to enable/disable computing device 300, image capture device 400 (if optionally included), and/or luminaire 100.
  • a given control feature may be configured to perform an image data refresh for optional image capture device 400 to refresh photographical canvas 382.
  • GUI 370 may present an intensity adjustment feature 392 configured to adjust the intensity (e.g., brighten and/or dim) the output of the one or more lamps 130 of luminaire 100.
  • GUI 370 may be configured to allow control of the intensity, color, and/or color temperature of the light emitted by a given solid-state lamp 130 of a paired luminaire 100.
  • GUI 370 may present one or more network connection management features 396 (e.g., a network selection menu, a network/IP address indicator, a network connection refresh button, etc.).
  • computing device 300 may perform a connection refresh upon user instruction; for example, a user may input a command to computing device 300, which causes it to perform a network connection refresh.
  • computing device 300 may be configured to perform a periodic network connection refresh (e.g., based on a user-defined schedule, a given time interval, etc.) or otherwise as frequently as desired for a given target application or end-use.
  • GUI 370 may present a mode selection feature 398 configured to allow for selection between any of the example lighting distribution modes (e.g., such as beam-adjustable mode, point-to-point mode, auto-sequence mode, distribution-adjustable mode, etc., as discussed below) of which luminaire 100 may be capable.
  • GUI 370 may present one or more auto-sequence management features 394 (e.g., a pattern/sequence selection menu, a pattern/sequence start/stop button, a pattern/sequence speed adjuster, etc.) for managing operation of luminaire 100 in an auto-sequence mode.
  • auto-sequence management features 394 e.g., a pattern/sequence selection menu, a pattern/sequence start/stop button, a pattern/sequence speed adjuster, etc.
  • GUI 370 may present an orientation indicator feature 352 configured to indicate the directional heading and/or angular orientation of device 300, for example, with respect to a paired luminaire 100, a geomagnetic heading (e.g., geomagnetic north), or other suitable point of reference.
  • orientation indicator feature 352 configured to indicate the directional heading and/or angular orientation of device 300, for example, with respect to a paired luminaire 100, a geomagnetic heading (e.g., geomagnetic north), or other suitable point of reference.
  • GUI 370 may present one or more navigation features 393, such as a Home button, a Back button to allow a user to go back to a previous menu/sub-menu, and/or a Switch Application button to allow a user to switch between currently active applications, among others.
  • GUI 370 may present one or more status bars 391 configured to convey information, for example, pertaining to the operation, status, and/or performance of device 300, a paired luminaire 100, and/or an optionally included image capture device 400.
  • a given status bar 391 may include a network connection/signal indicator icon that indicates the state of the connection of device 300 with luminaire 100, image capture device 400, and/or network 500 (if present).
  • a given status bar 391 may include a battery life indicator icon that indicates the remaining power available for device 300, luminaire 100, and/or image capture device 400.
  • a given status bar 391 may include a clock icon that indicates the current time.
  • GUI control features e.g., virtual and/or physical
  • options may be displayed by display 340 of device 300, in accordance with other embodiments.
  • a given GUI control feature may be associated with any standard and/or user-defined function, capability, and/or application of device 300, as desired, and may be customized to meet the preferences of a given user.
  • Optional image capture device 400 can be any device configured to capture digital images, such as a still camera (e.g., a camera configured to capture still photographs) or a video camera (e.g., a camera configured to capture moving images comprising a plurality of frames).
  • Image capture device 400 may include components such as, for example, an optics assembly, an image sensor, and an image/video encoder. These components (and others, if any) of image capture device 400 may be implemented in any combination of hardware, software, and/or firmware, as desired for a given target application or end-use.
  • image capture device 400 can be configured to operate using light, for example, in the visible spectrum and/or other portions of the electromagnetic spectrum, including the infrared (IR) spectrum, ultraviolet (UV) spectrum, etc.
  • IR infrared
  • UV ultraviolet
  • image capture device 400 may be aimed (e.g., oriented, focused) such that it captures an image inclusive of a given space, surface of incidence, or other target region to be lighted using luminaire 100.
  • image capture device 400 may capture an image of the lighted area and convey that information, for example, to computing device 300 (e.g., where it may be considered by a user to make a determination as to whether a desired lighting distribution has been achieved).
  • computing device 300 e.g., where it may be considered by a user to make a determination as to whether a desired lighting distribution has been achieved.
  • an image providing an overhead view (e.g., a bird's-eye view) of the lighted space may be conveyed by image capture device 400 to computing device 300.
  • This visual image may be provided to computing device 300, for example, to serve as a photographical canvas 382 for GUI 370, and in some instances may provide the user with improved control over light distribution without having to observe the actual physical space to distribute light in an intended manner.
  • image capture device 400 may be a separate (e.g., stand-alone) device that is configured to communicate with computing device 300 and/or luminaire 100 via wired (e.g., Universal Serial Bus or USB, Ethernet, FireWire, etc.) and/or wireless (e.g., Wi-Fi®, Bluetooth®, etc.) communication.
  • image capture device 400 may be incorporated within computing device 300 (e.g., as a built-in or otherwise on-board image capture device).
  • Some example cases may include: web cameras as may be associated with computers, video monitors, etc.; mobile device cameras (e.g., cell phone or smartphone cameras integrated in, for example, the previously discussed example device); integrated laptop computer cameras; and integrated tablet computer cameras (e.g., iPad®, Galaxy Tab®, and the like).
  • image capture device 400 may be incorporated within luminaire 100. Other suitable placements and configurations for image capture device 400 will depend on a given application and will be apparent in light of this disclosure.
  • luminaire 100 may be configured to be capable of outputting light in any of a wide range of light distribution modes, and device 300 with its GUI 370 may be utilized to control such modes, in accordance with some embodiments.
  • GUI 370 in beam-adjustable mode, in accordance with an embodiment of the present disclosure.
  • a cursor 376 may be displayed over graphical canvas 372.
  • the cursor 376 may be made to encompass one or more nodes 374 (or no nodes 374 at all, if desired).
  • each node 374 that is enclosed by cursor 376 may be toggled into an ON state, which, in turn, may be interpreted by a given controller 200 of luminaire 100 to toggle a lamp 130 corresponding to that node 374 into an ON state. Any node 374 that is not enclosed by cursor 376 may remain in an OFF state; accordingly, a given controller 200 of luminaire 100 may retain any lamps 130 corresponding with those nodes 374 in an OFF state, in accordance with some embodiments.
  • the light distribution of the lamps 130 of luminaire 100 may be controlled using the GUI 370 of device 300, for example, by changing the size (e.g., expanding; shrinking), geometry (e.g., curved; polygonal), and/or position of cursor 376 on graphical canvas 372 to encompass greater, lesser, or otherwise different quantities of nodes 374.
  • adjustment and/or movement of cursor 376 may be made using the user's finger, a stylus, or other suitable touchscreen implement.
  • a user may utilize an inward and/or outward pinch gesture to enlarge and/or diminish the size of cursor 376.
  • a user may drag his finger or a stylus about graphical canvas 372 to reposition cursor 376 thereon.
  • FIG. 4B is a plan view of a luminaire 100 in beam-adjustable mode corresponding with the example node 374 selections depicted in the GUI 370 screenshot of Figure 4A .
  • the lamps 130 corresponding with the selected nodes 374 encompassed by cursor 376 in Figure 4A are in an ON state, whereas those lamps 130 corresponding with nodes 374 not encompassed by cursor 376 in Figure 4A are in an OFF state.
  • adjustment and/or repositioning of cursor 376 may produce a corresponding change in which lamp(s) 130 of luminaire 100 are in an ON state at any given moment.
  • a user can utilize GUI 370 to enter various commands into device 300 to control the size and/or the direction of the light beam output by luminaire 100, thus permitting the user to distribute light in a given space or on a given surface of incidence, as desired.
  • a user can perform a touch-based inward and/or outward pinch gesture to vary the size (e.g., diameter/width) of the light beam output by luminaire 100.
  • the user can drag cursor 376 around within graphical canvas 372 to change the direction of the light beam output by luminaire 100.
  • GUI 370 can be utilized to select a group of nodes 374, and thus a group of lamps 130 (e.g., a sub-set or all available lamps 130 of luminaire 100), to be turned ON, for example, to provide a given lighting distribution in a given region of the target space or surface of incidence.
  • GUI 370 may include an option, for example, to allow a user to operatively group/ungroup nodes 374 (and thus lamps 130) as desired.
  • FIG. 4C is a process flow illustrating an algorithm 700 for controlling a luminaire 100 in a beam-adjustable mode using a touch-sensitive GUI 370, in accordance with an embodiment of the present disclosure.
  • the algorithm 700 of Figure 4C can be implemented, for example, using a computing device 300 (discussed herein), in accordance with some embodiments.
  • algorithm 700 may begin as in block 702 with obtaining from a touch-sensitive display 340 (or other touch-sensitive surface of device 300) an asynchronous user input event (e.g., touching of display 340 with a finger, stylus, etc.).
  • Algorithm 700 may continue as in block 704 with determining whether there are any multi-touch points detected (e.g., detecting whether a user has placed two or more fingers, styluses, etc., on display 340). If no multi-touch points are detected, then algorithm 700 may continue as in block 712 (discussed below) with performing a refresh cursor routine. Otherwise, if multi-touch points are detected, then algorithm 700 may continue as in block 706 with determining whether the multi-touch points are converging. If the multi-touch points are not converging (e.g., are diverging), then algorithm 700 may continue as in block 708 with increasing the size of cursor 376 by a given scaling factor. If instead the multi-touch points are converging, then algorithm 700 may continue as in block 710 with decreasing the size of cursor 376 by a given scaling factor.
  • multi-touch points detected e.g., detecting whether a user has placed two or more fingers, styluses, etc., on display 340. If no multi-touch points are
  • algorithm 700 may continue as in block 712 with performing a cursor refresh routine.
  • cursor 376 may be redrawn on graphical canvas 372 based on its size, geometry, and/or location.
  • Algorithm 700 then may continue as in block 714 with retrieving the array of nodes 374 (e.g., LED points) on graphical canvas 372 and, as in block 716, calculating the distance of each lamp node 374 in the array from the center of cursor 376. Then, algorithm 700 may continue as in block 718 with determining whether the calculated distance is less than the radius of cursor 376.
  • nodes 374 e.g., LED points
  • algorithm 700 may continue as in block 720 with setting a corresponding lamp 130 of luminaire 100 to an OFF state. If instead the calculated distance is less than the radius of cursor 376 (e.g., the node 374 is enclosed by the bounds of cursor 376), then algorithm 700 may continue as in block 722 with setting a corresponding lamp 130 of luminaire 100 to an ON state.
  • algorithm 700 may continue as in block 724 with determining whether there are any remaining lamp nodes 374 in the retrieved array. If there is at least one remaining lamp node 374 in the retrieved array, then algorithm 700 may return to block 716, discussed above. If instead there are no remaining lamp nodes 374 in the retrieved array, then algorithm 700 may proceed as in block 726 with performing a graphical canvas refresh routine. In this routine, graphical canvas 372 may be updated by toggling (e.g., re-coloring, re-shading, etc.) the lamp nodes 374 on graphical canvas 372 based on the ON/OFF states of the lamps 130 of luminaire 100.
  • Algorithm 700 may continue as in block 728 with performing a data generation routine.
  • the intensity values e.g., which may be set by a user, for instance, using an intensity adjustment feature 392 configured to brighten and/or dim the output of the lamps 130 of luminaire 100, as discussed above
  • an array may be generated by setting its values based on the ON/OFF states of the lamps 130 of luminaire 100.
  • the values of the array may be adjusted based on the retrieved intensity values.
  • the generated data may be compiled or otherwise provided, for example, as an ArtNET DMX data packet. Other suitable packet types will depend on a given application and will be apparent in light of this disclosure.
  • algorithm 700 may continue as in block 730 with performing a data output routine.
  • This routine may include determining whether an internet connection (e.g., wired, wireless, or other suitable network connection type) is available for transmission of the data packet.
  • the routine also may include determining whether a luminaire 100 is available for transmission of the data packet (e.g., determining whether a given luminaire 100 is configured as an ArtNET adapter node or other suitable recipient).
  • the routine may include sending the data packet over the connection to a given luminaire 100 using a given suitable protocol (e.g., ArtNET protocol or any other suitable protocol).
  • algorithm 700 may return to obtaining an asynchronous user input event using touchscreen display 340, as in block 702.
  • Figure 5A illustrates an example screenshot of GUI 370 in point-to-point mode, in accordance with an embodiment of the present disclosure.
  • a given node 374 of interest on graphical canvas 372 may be toggled to change the state of a corresponding lamp 130 of a paired luminaire 100.
  • each node 374 that is toggled into an ON state may be interpreted by a given controller 200 of luminaire 100 to toggle a lamp 130 corresponding to that node 374 into an ON state.
  • any node 374 that is not toggled may remain in an OFF state; accordingly, a given controller 200 of luminaire 100 may retain any lamps 130 corresponding with those nodes 374 in an OFF state, in accordance with some embodiments.
  • each lamp 130 can be turned ON/OFF individually, allowing for discrete control over the light distribution of luminaire 100 using the GUI 370 of device 300, for example, to illuminate any desired region of a given space or surface of incidence.
  • toggling of a given node 374 may be made using the user's finger, a stylus, or other suitable touchscreen implement.
  • FIG. 5B is a plan view of a luminaire 100 in point-to-point mode corresponding with the example node 374 selections depicted in the GUI 370 screenshot of Figure 5A .
  • the lamps 130 corresponding with the toggled nodes 374 in Figure 5A are in an ON state, whereas those lamps 130 corresponding with nodes 374 not toggled in Figure 5A are in an OFF state.
  • a user can utilize GUI 370 to enter various commands into device 300 to control the size and/or the direction of the light beam output by luminaire 100, thus permitting the user to distribute light in a given space or on a given surface of incidence, as desired.
  • GUI 370 to enter various commands into device 300 to control the size and/or the direction of the light beam output by luminaire 100, thus permitting the user to distribute light in a given space or on a given surface of incidence, as desired.
  • a user can touch a greater or lesser quantity of nodes 374 to vary the size (e.g., diameter/width) and/or direction of the light beam output by luminaire 100.
  • FIG. 5C is a process flow illustrating an algorithm 800 for controlling a luminaire 100 in a point-to-point mode using a touch-sensitive GUI 370, in accordance with an embodiment of the present disclosure.
  • the algorithm 800 of Figure 5C can be implemented, for example, using a computing device 300 (discussed herein), in accordance with some embodiments.
  • algorithm 800 may begin as in block 802 with obtaining from a touch-sensitive display 340 (or other touch-sensitive surface of device 300) an asynchronous user input event (e.g., touching of display 340 with a finger, stylus, etc.).
  • Algorithm 800 may continue as in block 804 with retrieving the array of nodes 374 (e.g., LED points) on graphical canvas 372 and, as in block 806, calculating the distance of each lamp node 374 in the array from the center of the user touch point. Then, algorithm 800 may continue as in block 808 with determining whether the calculated distance is less than the diameter of a given area around the lamp node 374. If the calculated distance is not less than the diameter, then algorithm 800 may continue as in block 816 with setting the scan state of the lamp node 374 to 'FALSE.' If instead the calculated distance is less than the diameter, then algorithm 800 may continue as in block 810 with determining whether the lamp node 374 is already under scan.
  • nodes 374 e.g., LED points
  • algorithm 800 may proceed as in block 818, discussed below. If instead the lamp node 374 is not already under scan, then algorithm 800 may proceed as in block 812 with setting the scan state of the lamp node 374 to 'TRUE' and toggling the state of the lamp 130, as in block 814.
  • algorithm 800 may continue as in block 818 with determining whether there are any remaining lamp nodes 374 in the array. If there is at least one remaining lamp node 374 in the retrieved array, then algorithm 800 may proceed as in block 806, as discussed above. If instead there are no remaining lamp nodes 374 in the retrieved array, then algorithm 800 may proceed as in block 820 with determining whether a user touch event is up. If a user touch event is not up, then algorithm 800 may proceed as in block 824 with performing a graphical canvas refresh routine, as discussed below. If instead a user touch event is up, then algorithm 800 may proceed as in block 822 with clearing the scan states of all lamp nodes 374 to 'FALSE.'
  • Algorithm 800 may proceed as in block 824 with performing a graphical canvas refresh routine.
  • graphical canvas 372 may be updated by toggling (e.g., re-coloring, re-shading, etc.) the lamp nodes 374 on graphical canvas 372 based on the ON/OFF states of the lamps 130 of luminaire 100.
  • Algorithm 800 may continue as in block 826 with performing a data generation routine. This routine may be performed, in some cases, in substantially the same manner as the data generation routine discussed above with respect to block 728 of Figure 4C . Thereafter, algorithm 800 may continue as in block 828 with performing a data output routine.
  • algorithm 800 may return to obtaining an asynchronous user input event using touchscreen display 340, as in block 802.
  • FIG. 6A illustrates an example screenshot of GUI 370 in auto-sequence mode, in accordance with an embodiment of the present disclosure.
  • the regular or otherwise well-defined arrangement of lamps 130 of luminaire 100 may be exploited, for example, to generate a given desired lighting pattern/sequence with luminaire 100. That is, in accordance with some embodiments, automated lighting patterns may be generated in a given space or on a given surface of incidence by turning appropriate lamps 130 ON/OFF in a given desired pattern and/or sequence.
  • each node 374 that is toggled into an ON state may be interpreted by a given controller 200 of luminaire 100 to toggle a lamp 130 corresponding to that node 374 into an ON state. Any node 374 that is not toggled may remain in an OFF state; accordingly, a given controller 200 of luminaire 100 may retain any lamps 130 corresponding with those nodes 374 in an OFF state, in accordance with some embodiments.
  • toggling of the states of lamps 130 may be made to form a pattern/sequence.
  • the pattern/sequence may be preset or otherwise predetermined and available for selection.
  • a user may provide input through GUI 370 using graphical canvas 372 to generate a user-defined pattern/sequence. Selection of a given auto-sequence mode may be made, for example, from a pattern/sequence selection menu or other auto-sequence management feature 394, as discussed above.
  • one or more of the lamps 130 of luminaire 100 can be turned ON/OFF sequentially and/or simultaneously to form the pattern/sequence.
  • changes to intensity e.g., using an intensity adjustment feature 392 configured to brighten and/or dim the output of the lamps 130 of luminaire 100, as discussed above
  • pattern/sequence speed e.g., using a pattern sequence speed adjuster or other auto-sequence management feature 394, as discussed above
  • the light distribution of the lamps 130 of luminaire 100 may be controlled using the GUI 370 of device 300, for example, to provide any of a wide range of patterns/sequences of illumination in a given space or on a given surface of incidence.
  • selection and/or generation of a given pattern/sequence may be made using the user's finger, a stylus, or other suitable touchscreen implement.
  • a static pattern e.g., a star shape, a ring shape, an arrow shape, an alphanumeric character, etc.
  • FIG. 6B is a plan view of a luminaire 100 in auto-sequence mode corresponding with the example pattern/sequence selection depicted in the GUI 370 screenshot of Figure 6A .
  • the lamps 130 corresponding with the selected nodes 374 utilized by the example pattern/sequence selected in Figure 6A are in an ON state, whereas those lamps 130 corresponding with nodes 374 not (yet, if at all) utilized in the example pattern/sequence selected in Figure 6A are in an OFF state.
  • selection and/or generation of a different pattern/sequence may produce a corresponding change in which lamp(s) 130 of luminaire 100 are in an ON state at any given moment.
  • a user can utilize GUI 370 to enter various commands into device 300 to control the type, speed, and/or intensity of the patterned/sequenced light beam output by luminaire 100, thus permitting the user to distribute light in a given space or on a given surface of incidence, as desired.
  • Figure 6C is a process flow illustrating an algorithm 900 for controlling a luminaire 100 in an auto-sequence mode, in accordance with an embodiment of the present disclosure.
  • the algorithm 900 of Figure 6C can be implemented, for example, using a computing device 300 (discussed herein), in accordance with some embodiments.
  • algorithm 900 may begin as in block 902 with obtaining from a touch-sensitive display 340 (or other touch-sensitive surface of device 300) an asynchronous user input event (e.g., touching of display 340 with a finger, stylus, etc.).
  • Algorithm 900 may continue as in block 904 with determining whether auto-sequence mode has been enabled.
  • algorithm 900 may continue as in block 906 with disabling the associated one or more auto-sequence management features 394 (e.g., a pattern/sequence selection menu, a pattern/sequence start/stop button, a pattern/sequence speed adjuster, etc.) and clearing graphical canvas 372. If instead auto-sequence mode has been enabled, then algorithm 900 may continue as in block 908 with enabling one or more associated auto-sequence management features 394 and clearing graphical canvas 372.
  • auto-sequence management features 394 e.g., a pattern/sequence selection menu, a pattern/sequence start/stop button, a pattern/sequence speed adjuster, etc.
  • Algorithm 900 may continue as in block 910 with loading a currently selected pattern/sequence.
  • the selected pattern/sequence is dynamic (e.g., moving, animated, or otherwise evolving)
  • it may be desirable to load the pattern/sequence, for example, into a buffer.
  • algorithm 900 may proceed as in block 912 with setting the lamp 130 states based on the values of the selected pattern/sequence.
  • algorithm 900 may continue as in block 914 with performing a graphical canvas refresh routine.
  • graphical canvas 372 may be updated by toggling (e.g., re-coloring, re-shading, etc.) the lamp nodes 374 on graphical canvas 372 based on the ON/OFF states of the lamps 130 of luminaire 100 during the pattern/sequence progression.
  • Algorithm 900 may continue as in block 916 with performing a data generation routine. This routine may be performed, in some cases, in substantially the same manner as the data generation routine discussed above with respect to block 728 of Figure 4C .
  • algorithm 900 may continue as in block 918 with performing a data output routine. This routine may be performed, in some cases, in substantially the same manner as the data output routine discussed above with respect to block 730 of Figure 4C .
  • algorithm 900 may proceed as in block 920 with sleeping or otherwise temporarily halting processing for a given period of time based, at least in part, on the current pattern/sequence speed.
  • this sleep period may be in the range of about 0.1-10.0 ms (e.g., about 1.0-2.5 ms, about 2.5-5.0 ms, about 5.0-7.5 ms, about 7.5-10.0 ms, or any other sub-range in the range of about 0.1-10.0 ms).
  • algorithm 900 may proceed as in block 924 with obtaining an asynchronous user input event using touchscreen display 340 (e.g., as discussed above with reference to block 902) and returning to loading the selected pattern/sequence, as in block 910. If instead there are no additional frames remaining to the selected pattern/sequence, then algorithm 900 may proceed as in block 926 with pointing the array index to the first value in the selected pattern/sequence and retuning to loading the selected pattern/sequence, as in block 910.
  • each of the functional boxes and decision points shown in Figures 4C , 5C , and 6C can be implemented, for example, as a module or sub-module that, when executed by one or more processors or otherwise operated, causes the associated functionality as described herein to be carried out.
  • the modules/sub-modules may be implemented, for instance, in software (e.g., executable instructions stored on one or more computer-readable media), firmware (e.g., embedded routines of a microcontroller or other device which may have I/O capacity for soliciting input from a user and providing responses to user requests), and/or hardware (e.g., gate level logic, field programmable gate array, purpose-built silicon, etc.).
  • software e.g., executable instructions stored on one or more computer-readable media
  • firmware e.g., embedded routines of a microcontroller or other device which may have I/O capacity for soliciting input from a user and providing responses to user requests
  • hardware e.g., gate level logic, field programmable gate array, purpose-built silicon, etc.
  • luminaire 100 may be configured to be capable of outputting light in any of a wide range of light distribution modes, and device 300 with its GUI 370 may be utilized to control such modes, in accordance with some embodiments. It should be further noted, however, that the present disclosure is not so limited to the example beam-adjustable, point-to-point, and auto-sequence modes discussed herein.
  • luminaire 100 may be configured for a distribution-adjustable mode. That is, in accordance with some embodiments, luminaire 100 can be used to provide accent lighting or area lighting of any of a wide variety of distributions (e.g., narrow, wide, asymmetric/tilted, Gaussian, batwing, or other specifically shaped beam distribution). By turning ON/OFF and/or dimming/brightening the intensity of various combinations of solid-state emitter devices of luminaire 100, the light beam output may be adjusted, for instance, to produce uniform illumination on a given surface, to fill a given space with light, or to generate any desired area lighting distributions.
  • a wide variety of distributions e.g., narrow, wide, asymmetric/tilted, Gaussian, batwing, or other specifically shaped beam distribution.
  • luminaire 100 can be used to generate any of a wide range of spot shapes, such as, for example, a circle or ellipse, a square or rectangle (e.g., which can be used to fill corner areas), a star, an arrow, or other fanciful or customized shape, as desired.
  • luminaire 100 can be used to generate a user-designated or otherwise custom spot shape (e.g., such as by drawing on a touch-sensitive display 340 of computing device 300).
  • device 300 may include an auto-orientation mode for GUI 370.
  • Figure 7A illustrates an example screenshot of GUI 370 with auto-orientation mode disabled, in accordance with an embodiment of the present disclosure.
  • Figure 7B illustrates an example screenshot of GUI 370 with auto-orientation mode enabled, in accordance with an embodiment of the present disclosure.
  • auto-orientation mode is not enabled (e.g., optional position and/or motion sensor 350 is disabled or omitted)
  • rotation of device 300 with respect to luminaire 100 may not produce a corresponding reorientation of photographical canvas 382.
  • device 300 has been rotated through an angle of about 270°, yet north in the photographical canvas 382 does not align with north on the orientation indicator feature 352.
  • auto-orientation mode may be implemented with graphical canvas 372, discussed above.
  • auto-orientation mode may be implemented through visual data (e.g., an image taken from image capture device 400).
  • auto-orientation mode may permit GUI 370, in part or in whole, to orient itself with respect to the surroundings using information about the space where the light is to be distributed.
  • the acquired orientation information (e.g., geomagnetic data, visual data) can be utilized to orient graphical canvas 372 and/or photographical canvas 382 to the actual orientation of the space itself irrespective of the orientation of computing device 300 (e.g., as held by a user).
  • One example embodiment provides a method of electronically controlling a light beam distribution of a solid-state luminaire, the method including: presenting a field of selectable control features on a graphical user interface on a computing device configured to be communicatively coupled with the solid-state luminaire, wherein at least one of the field of selectable control features is presented as a graphical canvas including two or more selectable nodes each corresponding to one or more light sources of the solid-state luminaire; and adjusting the light beam distribution of the solid-state luminaire based on a selection of one of the two or more selectable nodes.
  • the computing device includes at least one of a laptop/notebook computer, a tablet computer, a mobile phone, a smartphone, a personal digital assistant (PDA), a portable media player (PMP), a cellular handset, a handheld gaming device, a gaming platform, a desktop computer, and/or a television set.
  • the computing device includes a touch-sensitive display on which the field of selectable control features is presented as one or more light-based icons.
  • selection of a selectable node of the graphical canvas toggles a corresponding one or more light sources of the solid-state luminaire on/off.
  • the graphical canvas is configured to maintain its orientation with respect to at least one of a geomagnetic heading and/or the solid-state luminaire.
  • adjusting the light beam distribution of the solid-state luminaire includes at least one of: changing at least one of beam direction, beam angle, beam diameter, beam distribution, brightness, and/or color of light emitted by the solid-state luminaire; and/or producing at least one of a lighting pattern and/or a lighting sequence using the solid-state luminaire.
  • at least one of the selectable control features includes a network connection management feature configured to at least one of establish and/or refresh a network connection between the computing device and the solid-state luminaire.
  • At least one of the selectable control features includes a lighting pattern/sequence management feature configured to at least one of initiate, terminate, and/or adjust a lighting pattern/sequence produced using the solid-state luminaire.
  • the solid-state luminaire and the computing device are configured to be communicatively coupled with one another using at least one of an ArtNET digital multiplexer (DMX) interface protocol, a Wi-Fi protocol, a Bluetooth protocol, a digital addressable lighting interface (DALI) protocol, and/or a ZigBee protocol.
  • DMX ArtNET digital multiplexer
  • Wi-Fi Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • DALI digital addressable lighting interface
  • ZigBee protocol ZigBee protocol
  • the computer program product may include one or more computer-readable mediums, such as, for example, a hard drive, compact disk, memory stick, server, cache memory, register memory, random-access memory (RAM), read-only memory (ROM), flash memory, or any suitable non-transitory memory that is encoded with instructions that can be executed by one or more processors, or a plurality or combination of such memories.
  • a hard drive compact disk
  • memory stick server
  • cache memory register memory
  • RAM random-access memory
  • ROM read-only memory
  • flash memory or any suitable non-transitory memory that is encoded with instructions that can be executed by one or more processors, or a plurality or combination of such memories.
  • the process includes: presenting a field of selectable control features on a computing device configured to communicatively couple with a solid-state luminaire, wherein at least one of the selectable control features is presented as a graphical canvas including two or more selectable nodes each corresponding to one or more light sources of the solid-state luminaire; and adjusting the light beam distribution of the solid-state luminaire based on a selection of one or the two or more selectable nodes.
  • the computing device includes at least one of a laptop/notebook computer, a tablet computer, a mobile phone, a smartphone, a personal digital assistant (PDA), a portable media player (PMP), a cellular handset, a handheld gaming device, a gaming platform, a desktop computer, and/or a television set.
  • the computing device includes a touch-sensitive display on which the field of selectable control features is presented as one or more light-based icons.
  • selection of a selectable node of the graphical canvas toggles a corresponding one or more light sources of the solid-state luminaire on/off.
  • the graphical canvas is configured to maintain its orientation with respect to at least one of a geomagnetic heading and/or the solid-state luminaire.
  • adjusting the light beam distribution of the solid-state luminaire includes at least one of: changing at least one of beam direction, beam angle, beam diameter, beam distribution, brightness, and/or color of light emitted by the solid-state luminaire; and/or producing at least one of a lighting pattern and/or a lighting sequence using the solid-state luminaire.
  • at least one of the selectable control features includes a network connection management feature configured to at least one of establish and/or refresh a network connection between the computing device and the solid-state luminaire.
  • At least one of the selectable control features includes a lighting pattern/sequence management feature configured to at least one of initiate, terminate, and/or adjust a lighting pattern/sequence produced using the solid-state luminaire.
  • the solid-state luminaire and the computing device are configured to be communicatively coupled with one another using at least one of an ArtNET digital multiplexer (DMX) interface protocol, a Wi-Fi protocol, a Bluetooth protocol, a digital addressable lighting interface (DALI) protocol, and/or a ZigBee protocol.
  • DMX ArtNET digital multiplexer
  • Wi-Fi Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • DALI digital addressable lighting interface
  • ZigBee protocol ZigBee protocol
  • GUI graphical user interface
  • the GUI including: a field of selectable control features configured such that selection therefrom electronically controls a light beam distribution of a solid-state luminaire communicatively coupleable with the computing system; wherein at least one of the selectable control features is presented as a graphical canvas including two or more selectable nodes each corresponding to one or more light sources of the solid-state luminaire; and wherein selection of a selectable node of the graphical canvas toggles a corresponding one or more of the light sources of the solid-state luminaire on/off.
  • GUI graphical user interface
  • the computing device includes at least one of a laptop/notebook computer, a tablet computer, a mobile phone, a smartphone, a personal digital assistant (PDA), a portable media player (PMP), a cellular handset, a handheld gaming device, a gaming platform, a desktop computer, and/or a television set.
  • the computing device includes a touch-sensitive display on which the field of selectable control features is presented as one or more light-based icons.
  • the graphical canvas is configured to maintain its orientation with respect to at least one of a geomagnetic heading and/or the solid-state luminaire.
  • electronic control of the light beam distribution of the solid-state luminaire includes at least one of: changing at least one of beam direction, beam angle, beam diameter, beam distribution, brightness, and/or color of light emitted by the solid-state luminaire; and/or producing at least one of a lighting pattern and/or a lighting sequence using the solid-state luminaire.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Circuit Arrangement For Electric Light Sources In General (AREA)

Claims (15)

  1. Procédé de commande électronique d'une distribution de faisceau de lumière d'un luminaire à semi-conducteur (100), le procédé comprenant les étapes consistant à :
    présenter un champ de fonctions de contrôle sélectionnables sur une interface utilisateur graphique (GUI) sur un dispositif informatique (300) configuré pour être couplé en communication avec le luminaire à semi-conducteur (100), au moins une fonction du champ de fonctions de contrôle sélectionnables étant présentée comme une trame graphique (372) comprenant deux ou plusieurs noeuds sélectionnables (374) correspondant chacun à une ou plusieurs sources de lumière (130) du luminaire à semi-conducteur (100) ; et
    régler la distribution de faisceau de lumière du luminaire à semi-conducteur (100) sur la base d'une sélection d'un des deux ou plusieurs noeuds sélectionnables (374).
  2. Procédé selon la revendication 1, dans lequel le dispositif informatique (300) comprend au moins un élément parmi un ordinateur portable/portatif, une tablette, un téléphone mobile, un smartphone, un assistant numérique personnel (PDA), un lecteur média portable (PMP), un combiné cellulaire, une console de jeu portable, une plateforme de jeu, un ordinateur de bureau et/ou un poste de télévision.
  3. Procédé selon l'une quelconque des revendications 1 ou 2, dans lequel le dispositif informatique (300) comprend un affichage tactile sur lequel le champ de fonctions de contrôle sélectionnables est présenté comme une ou plusieurs icônes basées sur la lumière.
  4. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel la sélection d'un noeud sélectionnable (374) de la trame graphique (372) active/désactive une ou plusieurs sources de lumière correspondantes (130) du luminaire à semi-conducteur (100).
  5. Procédé selon l'une quelconque des revendications 1 à 4, dans lequel la trame graphique (372) est configurée pour maintenir son orientation par rapport à au moins l'un d'un cap géomagnétique et/ou du luminaire à semi-conducteur (100).
  6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel le réglage de la distribution de faisceau de lumière du luminaire à semi-conducteur (100) comprend au moins l'une des étapes consistant à :
    échanger au moins un élément parmi une direction de faisceau, un angle de faisceau, un diamètre de faisceau, une distribution de faisceau, une luminosité et/ou une couleur de la lumière émise par le luminaire à semi-conducteur (100) ; et/ou
    produire au moins un élément parmi un motif d'éclairage et/ou une séquence d'éclairage en utilisant le luminaire à semi-conducteur (100).
  7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel au moins l'une des fonctions de contrôle sélectionnables comprend une fonction de gestion de connexion de réseau configurée pour au moins établir et/ou rafraîchir une connexion de réseau entre le dispositif informatique (300) et le luminaire à semi-conducteur (100).
  8. Procédé selon l'une quelconque des revendications 1 à 7, dans lequel au moins l'une des fonctions de contrôle sélectionnables comprend une fonction de gestion de motif/séquence d'éclairage, configurée pour au moins déclencher, terminer et/ou régler un motif/ une séquence d'éclairage produit(e) en utilisant le luminaire à semi-conducteur (100).
  9. Procédé selon l'une quelconque des revendications 1 à 8, dans lequel le luminaire à semi-conducteur (100) et le dispositif informatique (300) sont configurés pour être couplés ensemble en communication en utilisant au moins un élément parmi un protocole d'interface de multiplexeur numérique ArtNET (DMX), un protocole WiFi, un protocole Bluetooth, un protocole d'interface d'éclairage adressable numérique (DALI) et/ou un protocole ZigBee.
  10. Produit de programme informatique non transitoire, codé avec des instructions qui, lorsqu'elles sont exécutées par un ou plusieurs processeurs, provoquent l'exécution d'un processus, le processus comprenant :
    la présentation d'un champ de fonctions de contrôle sélectionnables sur une interface utilisateur graphique (GUI) sur un dispositif informatique (300) configuré pour être couplé en communication avec un luminaire à semi-conducteur (100), au moins l'une des fonctions de contrôle sélectionnables étant présentée comme une trame graphique (372) comprenant deux ou plusieurs noeuds sélectionnables (374) correspondant chacun à une ou plusieurs sources de lumière (130) du luminaire à semi-conducteur (100) ; et
    le réglage de la distribution de faisceau de lumière du luminaire à semi-conducteur (100) sur la base d'une sélection d'un des deux ou plus de deux noeuds sélectionnables (374).
  11. Produit de programme informatique non transitoire selon la revendication 10, dans lequel la sélection d'un noeud sélectionnable (374) de la trame graphique (372) active/désactive une ou plusieurs sources de lumière correspondantes (130) du luminaire à semi-conducteur (100) .
  12. Produit de programme informatique non transitoire selon l'une quelconque des revendications 10 ou 11, dans lequel le réglage de la distribution de faisceau de lumière du luminaire à semi-conducteur (100) comprend au moins l'une des étapes consistant à :
    changer au moins un élément parmi une direction de faisceau, un angle de faisceau, un diamètre de faisceau, une distribution de faisceau, une luminosité et/ou une couleur de la lumière émise par le luminaire à semi-conducteur (100) ; et/ou
    produire au moins un élément parmi un motif d'éclairage et/ou une séquence d'éclairage en utilisant le luminaire à semi-conducteur (100).
  13. Interface utilisateur graphique (GUI) sur un système informatique, la GUI comprenant :
    un champ de fonctions de contrôle sélectionnables configuré de telle sorte qu'une sélection dans celui-ci commande électroniquement une distribution de faisceau de lumière d'un luminaire à semi-conducteur (100) couplé en communication avec le système informatique ;
    au moins l'une des fonctions de contrôle sélectionnables étant présentée comme une trame graphique (372) comprenant deux ou plusieurs noeuds sélectionnables (374) correspondant chacun à une ou plusieurs sources de lumière (130) du luminaire à semi-conducteur (100) ; et
    la sélection d'un noeud sélectionnable (374) de la trame graphique (372) activant/désactivant une ou plusieurs sources de lumière correspondantes (130) du luminaire à semi-conducteur (100).
  14. GUI selon la revendication 13, dans laquelle le dispositif informatique (300) comprend un affichage tactile sur lequel le champ de fonctions de contrôle sélectionnables est présenté comme une ou plusieurs icônes basées sur la lumière.
  15. GUI selon l'une quelconque des revendications 13 ou 14, dans laquelle la trame graphique (372) est configurée pour maintenir son orientation par rapport à au moins l'un d'un cap géomagnétique et/ou du luminaire à semi-conducteur (100).
EP15160103.6A 2014-03-21 2015-03-20 Techniques et interface utilisateur graphique de commande d'éclairage à semi-conducteurs avec distribution de faisceau de lumière réglable électroniquement Active EP2922370B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/221,589 US9801260B2 (en) 2013-09-20 2014-03-21 Techniques and graphical user interface for controlling solid-state luminaire with electronically adjustable light beam distribution

Publications (3)

Publication Number Publication Date
EP2922370A2 EP2922370A2 (fr) 2015-09-23
EP2922370A3 EP2922370A3 (fr) 2015-10-28
EP2922370B1 true EP2922370B1 (fr) 2019-09-11

Family

ID=52780836

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15160103.6A Active EP2922370B1 (fr) 2014-03-21 2015-03-20 Techniques et interface utilisateur graphique de commande d'éclairage à semi-conducteurs avec distribution de faisceau de lumière réglable électroniquement

Country Status (2)

Country Link
EP (1) EP2922370B1 (fr)
CN (1) CN104936339B (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102014109989A1 (de) * 2014-07-16 2016-01-21 Holy Trinity GmbH Verfahren zur Steuerung einer Leuchte mittels eines mobilen Endgeräts
EP3356732B1 (fr) 2015-10-02 2020-11-04 PCMS Holdings, Inc. Système et procédé d'abat-jour numérique
CN106594561A (zh) * 2017-01-05 2017-04-26 李梦成 一种可自主设计的舞台立体灯光装置
US10412802B2 (en) * 2017-03-02 2019-09-10 Osram Sylvania Inc. Luminaire with programmable light distribution

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110181207A1 (en) * 2008-06-05 2011-07-28 Technische Universiteir Eindhoven Luminaire
US20140070707A1 (en) * 2012-09-11 2014-03-13 Panasonic Corporation Lighting control system

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040100507A1 (en) * 2001-08-24 2004-05-27 Omri Hayner System and method for capturing browser sessions and user actions
US9955551B2 (en) * 2002-07-12 2018-04-24 Yechezkal Evan Spero Detector controlled illuminating system
EP1992201B1 (fr) * 2006-02-28 2016-05-18 Koninklijke Philips N.V. Mecanisme d'interaction pour systemes d'eclairage
AU2010257154B2 (en) * 2009-06-03 2014-02-20 Savant Systems, Inc. Virtual room-based light fixture and device control
US9304662B2 (en) * 2011-08-25 2016-04-05 Vmware, Inc. User interface virtualization techniques
CN203104861U (zh) * 2012-11-27 2013-07-31 赵东华 闪光装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110181207A1 (en) * 2008-06-05 2011-07-28 Technische Universiteir Eindhoven Luminaire
US20140070707A1 (en) * 2012-09-11 2014-03-13 Panasonic Corporation Lighting control system

Also Published As

Publication number Publication date
CN104936339A (zh) 2015-09-23
EP2922370A3 (fr) 2015-10-28
EP2922370A2 (fr) 2015-09-23
CN104936339B (zh) 2019-07-26

Similar Documents

Publication Publication Date Title
US9801260B2 (en) Techniques and graphical user interface for controlling solid-state luminaire with electronically adjustable light beam distribution
US10568179B2 (en) Techniques and photographical user interface for controlling solid-state luminaire with electronically adjustable light beam distribution
US11106251B2 (en) Operation of the light management application for a mobile device with motion sensor
CN106095067B (zh) 用于照明系统的基于手势的控制方法和设备
EP2891386B1 (fr) Contrôle de source(s) de lumière par l'intermédiaire d'un dispositif portable
EP2922370B1 (fr) Techniques et interface utilisateur graphique de commande d'éclairage à semi-conducteurs avec distribution de faisceau de lumière réglable électroniquement
US11068144B2 (en) Diamond shaped digitial color selection interface
CN109644532B (zh) 光输出定位
JP6510079B2 (ja) 無線照明制御システム
EP3391711B1 (fr) Procédé de commande de dispositifs d'éclairage
EP3632188B1 (fr) Identification de luminaires et positionnement par constellation
JP2015211035A (ja) 携帯装置を利用して照明をプランニングするシステム及びその方法
CN108886863B (zh) 用于创建动态光效并且根据动态光效控制照明设备的计算机实现的方法
JP2020516800A (ja) ファンの制御方法および装置、並びにファン
EP2922371B1 (fr) Techniques et interface utilisateur photographique pour la commande de luminaires à état solide avec répartition ajustable électroniquement du faisceau lumineux
US20180218594A1 (en) Depth control for home appliances
WO2017043141A1 (fr) Dispositif de traitement d'informations, procédé de traitement d'informations, et programme
EP4294131A1 (fr) Dispositif d'interface utilisateur pour commander des dispositifs d'éclairage réorientables

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

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

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: H05B 37/02 20060101AFI20150921BHEP

17P Request for examination filed

Effective date: 20160426

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

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

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAR Information related to intention to grant a patent recorded

Free format text: ORIGINAL CODE: EPIDOSNIGR71

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

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

INTC Intention to grant announced (deleted)
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: 20190805

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

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

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015037601

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190911

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

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

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

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

Ref country code: SE

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1180181

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190911

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

Ref country code: IT

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

Effective date: 20190911

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

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

Ref country code: NL

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

Effective date: 20190911

Ref country code: AT

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

Ref country code: PL

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015037601

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

PG2D Information on lapse in contracting state deleted

Ref country code: IS

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

Ref country code: DK

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

Effective date: 20190911

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

26N No opposition filed

Effective date: 20200615

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200331

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

Ref country code: LU

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

Effective date: 20200320

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

Ref country code: FR

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

Effective date: 20200331

Ref country code: IE

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

Effective date: 20200320

Ref country code: CH

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

Effective date: 20200331

Ref country code: LI

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

Effective date: 20200331

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

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200320

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

Ref country code: GB

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

Effective date: 20200320

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

Ref country code: DE

Payment date: 20220322

Year of fee payment: 8

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

Ref country code: TR

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

Effective date: 20190911

Ref country code: MT

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

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

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

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230821

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015037601

Country of ref document: DE

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

Ref country code: DE

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

Effective date: 20231003