WO2016083954A2 - Lighting control apparatus and methods - Google Patents

Lighting control apparatus and methods Download PDF

Info

Publication number
WO2016083954A2
WO2016083954A2 PCT/IB2015/058958 IB2015058958W WO2016083954A2 WO 2016083954 A2 WO2016083954 A2 WO 2016083954A2 IB 2015058958 W IB2015058958 W IB 2015058958W WO 2016083954 A2 WO2016083954 A2 WO 2016083954A2
Authority
WO
WIPO (PCT)
Prior art keywords
node
address
nodes
communication
controller
Prior art date
Application number
PCT/IB2015/058958
Other languages
French (fr)
Other versions
WO2016083954A3 (en
Inventor
Marc Godfriedus Marie Notten
Anteneh Alemu Abbo
Octavio Alejandro SANTANA ARNAIZ
John Brean Mills
Tarek Aydin
John Warwick
Original Assignee
Philips Lighting Holding B.V.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Philips Lighting Holding B.V. filed Critical Philips Lighting Holding B.V.
Publication of WO2016083954A2 publication Critical patent/WO2016083954A2/en
Publication of WO2016083954A3 publication Critical patent/WO2016083954A3/en

Links

Classifications

    • HELECTRICITY
    • H05ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05BELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
    • H05B45/00Circuit arrangements for operating light-emitting diodes [LED]
    • H05B45/20Controlling the colour of the light
    • HELECTRICITY
    • H05ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05BELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
    • H05B47/00Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
    • H05B47/10Controlling the light source
    • H05B47/175Controlling the light source by remote control
    • H05B47/18Controlling the light source by remote control via data-bus transmission

Definitions

  • the present invention relates to lighting control apparatus and methods, and more particularly, to methods and apparatus related to one or more aspects of a networked lighting system for connection and control of various light sources and other devices.
  • LEDs light-emitting diodes
  • Functional advantages and benefits of LEDs include high energy conversion and optical efficiency, du rability, lower operating costs, and many others. Recent advances in LED technology have provided efficient and robust full- spectru m lighting sources that enable a variety of lighting effects in many applications.
  • Some of the fixtures embodying these sou rces feature a lighting modu le, including one or more LEDs capable of prod ucing different colors, e.g., red, green, and blue, as well as a processor for independently controlling the output of the LEDs in order to generate a variety of colors and color-changing lighting effects, for example, as discussed in detail in U.S. Patent Nos. 6,016,038 and 6,211,626, incorporated herein by reference.
  • LED networked lighting systems are built-up out of severa l hundred nodes and each node d rives one or more LEDs.
  • the nodes are connected to a controller with a power bus and a daisy chained data line.
  • the nodes are controlled within the system via the controller and all nodes have a unique add ress.
  • the controller sets, for example, the LED color per node, and sends the LED color per node (i.e., an LED color is set for each address) over the daisy chained data line.
  • each node receives system data, extracts its own data from the system data via the daisy-chain connection, fills the extracted data of the system data with zeroes (no-data), and forwards the system data with filled zeroes to a downstream node where the process repeats.
  • This is a simple uni-directional data flow that suffers from one or more disadvantages.
  • any issue with one of the nodes, or any issue with cabling and/or connections between two nodes will cause interruption of data delivery to any nodes that are connected downstream of the issue in the daisy-chained data line.
  • the unidirectional data flow does not allow for bi-directional communication between the controller and the nodes.
  • the present disclosure is directed to various inventive methods and apparatus related to one or more aspects of a networked lighting system for connection and control of various light sources and other devices.
  • Some embodiments of the present disclosure are directed to a lighting system that includes a plurality of addressable nodes coupled together to form a network and at least one controller coupled to the network and programmed to transmit and receive data to and from the plurality of addressable nodes via a bidirectional data bus connection to the plurality of addressable nodes.
  • the controller may also be programmed to transmit address information via an addressing line to facilitate addressing of the nodes during commissioning of the nodes.
  • the addressing line forms a serial connection between the plurality of addressable nodes.
  • Other embodiments are directed toward methods related to the commissioning of the nodes.
  • Yet other embodiments are directed toward the controller for commissioning and/or controlling the nodes, and/or toward the nodes themselves.
  • a lighting system includes a plurality of nodes and a controller.
  • the nodes each include a node controller, memory, a data communication connection, an address input connection, and an address output connection. At least one node of the plurality of nodes is coupled to and controls at least one LED light source.
  • the data communication connections of the nodes are all coupled to a data bus and the nodes are coupled in series via the address input connections and the address output connections.
  • the controller is coupled to the nodes via the data bus and coupled to the address input connection of a first node of the nodes.
  • the controller is configured to transmit address information to the address input connection of the first node.
  • the node controller of the first node is configured to assign itself a communication address based on receiving the address information, wherein the node controller stores the communication address in the memory of the first node and wherein the node controller is further configured to transmit information over the address output connection of the first node to effectuate assigning of communication addresses by other of the nodes.
  • the controller is further configured to broadcast control data to the plurality of nodes via the data bus, the control data addressed to one or more of the nodes based on respective of the communication addresses assigned by the nodes.
  • the control data comprises first control data addressed to the at least one node, the first control data comprising one or more control parameters for control of the at least one LED light source of the at least one node.
  • the at least one LED light source includes at least one red LED light source, at least one green LED light source, and at least one blue LED light source and the at least one node controls the at least one red LED light source, the at least one green LED light source, and the at least one blue LED light source, based on the control parameters.
  • the controller is further configured to receive operational feedback information from the plurality of nodes via the data bus.
  • the address information comprises the communication address and the node controller of the first node is further configured to adjust the communication address according to a fixed adjustment protocol to create an adjusted communication address— and the information transmitted over the output connection of the first node comprises the adjusted communication address.
  • the first node is configured to transmit an acknowledgement of assignment of the communication address to the controller via the data bus and transmit the adjusted communication address following the transmission of the acknowledgement of assignment of the communication address.
  • the address information comprises an active token
  • the first node is configured to assign itself the communication address based on receiving the active token
  • the information transmitted over the address output connection comprises the active token.
  • the first node is configured to assign a communication address of the first node based on: receiving the address information, receiving address setting information via the data communication connection of the first node, and comparing the address information to the address setting information.
  • the first node is configured to transmit an
  • the acknowledgement of assignment of the communication address to the controller may comprise a serial number of the first node and the controller may be further configured to store an association between the serial number and the communication address.
  • the first node is configured to transmit an
  • the acknowledgement of assignment of the communication address to the controller via the data bus and transmit the information over the address output connection of the first node following transmission of the acknowledgement of assignment of the communication address.
  • the acknowledgement of assignment of the communication address to the controller comprises a serial number of the first node and the controller is further configured to store an association between the serial number and the communication address.
  • a method comprises: receiving address information at a serially connected address input connection of a node, the node coupled to and controlling at least one LED light source; determining, by at least one controller of the node, a communication address based on receiving the address information; storing the communication address in memory of the node; receiving control data at a data bus connected data communication connection of the node; determining, by the controller, that at least a portion of the control data is addressed to the communication address in the memory of the node; and adjusting at least one light output parameter of the LED light source based on the portion of the control data, the adjusting in response to determining that the portion of the control data is addressed to the communication address.
  • the method further comprises receiving values from one or more sensors of the node and transmitting, via the data communication connection of the node, operational feedback information indicative of the values.
  • the method further comprises transmitting information over an address output connection of the node to effectuate assigning of communication addresses by an additional node serially connected to the node via the address output connection.
  • the address information comprises the communication address
  • the method further comprises adjusting the communication address according to a fixed adjustment protocol to create an adjusted communication address— wherein the information transmitted via the address output connection comprises the adjusted communication address.
  • the method further comprises transmitting an acknowledgement of assignment of the communication address via the data bus, wherein transmitting the adjusted communication address occurs after transmitting the acknowledgement of assignment of the
  • the address information comprises an active token and the information transmitted over the address output connection comprises the active token.
  • the method further comprises transmitting an acknowledgement of assignment of the communication address via the data bus, wherein transmitting the active token occurs after transmitting the acknowledgement of assignment of the communication address.
  • the method further comprises transmitting an
  • the acknowledgement of assignment of the communication address to the controller comprises a serial number stored in memory of the node and comprises the communication address.
  • a method comprises: broadcasting node discovery information to a plurality of nodes via a bus connection to the plurality of nodes, the nodes including at least one node that is coupled to and controls at least one LED light source; transmitting address information to an address input connection of a first node of the nodes without transmitting the address information to any other of the nodes, the address information configured to cause the first node to assign itself a communication address based on receiving the address information; and broadcasting control data to the plurality of nodes via the bus connection, the control data comprising first node control data addressed to the first node based on the communication address of the first node.
  • the address information is an active token.
  • the method further comprises: receiving an
  • acknowledgement of assignment of the communication address via the bus connection ; and broadcasting, to the plurality of nodes via the bus connection and in response to receiving the acknowledgment of assignment of the communication address, a request for discovery of the next node.
  • the method further comprises: receiving an
  • the node discovery information comprises address setting information that matches the address information.
  • the address information forms a key that decodes the address setting information.
  • the address information and the address setting information are an exact match.
  • the method further comprises: receiving from the first node an acknowledgement of assignment of the communication address via the bus connection, the acknowledgment of assignment of the communication address comprising a serial number of the first node; and storing in memory an association between the communication address and the serial number.
  • a method comprises: accessing a data structure that defines communication addresses of nodes coupled to a bus connection, the nodes including at least one node that is coupled to and controls at least one LED light source; broadcasting, for each of the communication addresses, an address request message to the nodes via the bus connection, the address request message for a
  • communication address of the communication addresses being configured to solicit a confirmatory response from a node of the nodes that has the communication address; monitoring the bus connection for the confirmatory response to each of the address request messages; determining a missing communication address associated with the address request message of the topologically closest node that failed to provide the confirmatory response in response to the address request message; broadcasting a command to the nodes via the bus connection, the command configured to cause any node that does not have a communication address assigned to assign the missing communication address.
  • an apparatus for use in commissioning and controlling a plurality of nodes wherein the nodes each include a connection for coupling to a data bus and a separate connection for a daisy-chain connection of the nodes, and wherein at least one node of the nodes is coupled to and controls at least one LED light source.
  • the apparatus comprises a data bus connection to couple to the data bus, an addressing connection to couple to a first node of the nodes, memory storing instructions, and a controller operable to execute the instructions stored in the memory. Execution of the instructions by the controller causes the controller to: broadcast node discovery
  • an LED-based lighting unit comprises a data communication connection, an address input connection, an address output connection, at least one LED light source, memory, and a controller.
  • the controller is configured to:
  • the term "LED” should be understood to include any electroluminescent diode or other type of carrier
  • the term LED includes, but is not limited to, various semiconductor- based structures that emit light in response to current, light emitting polymers, organic light emitting diodes (OLEDs), electroluminescent strips, and the like.
  • the term LED refers to light emitting diodes of all types (including semi-conductor and organic light emitting diodes) that may be configured to generate radiation in one or more of the infrared spectrum, ultraviolet spectrum, and various portions of the visible spectrum (generally including radiation wavelengths from approximately 400 nanometers to approximately 700 nanometers).
  • LEDs include, but are not limited to, various types of infrared LEDs, ultraviolet LEDs, red LEDs, blue LEDs, green LEDs, yellow LEDs, amber LEDs, orange LEDs, and white LEDs (discussed further below). It also should be appreciated that LEDs may be configured and/or controlled to generate radiation having various bandwidths (e.g., full widths at half maximum, or FWHM) for a given spectrum (e.g., narrow bandwidth, broad bandwidth), and a variety of dominant wavelengths within a given general color categorization.
  • bandwidths e.g., full widths at half maximum, or FWHM
  • an LED configured to generate essentially white light may include a number of dies which respectively emit different spectra of electroluminescence that, in combination, mix to form essentially white light.
  • a white light LED may be associated with a phosphor material that converts electroluminescence having a first spectrum to a different second spectrum.
  • electroluminescence having a relatively short wavelength and narrow bandwidth spectrum "pumps" the phosphor material, which in turn radiates longer wavelength radiation having a somewhat broader spectrum.
  • an LED does not limit the physical and/or electrical package type of an LED.
  • an LED may refer to a single light emitting device having multiple dies that are configured to respectively emit different spectra of radiation (e.g., that may or may not be individually controllable).
  • an LED may be associated with a phosphor that is considered as an integral part of the LED (e.g., some types of white LEDs).
  • the term LED may refer to packaged LEDs, non- packaged LEDs, surface mount LEDs, chip-on-board LEDs, T-package mount LEDs, radial package LEDs, power package LEDs, LEDs including some type of encasement and/or optical element (e.g., a diffusing lens), etc.
  • the term "light source” should be understood to refer to any one or more of a variety of radiation sources, including, but not limited to, LED-based sources (including one or more LEDs as defined above), incandescent sources (e.g., filament lamps, halogen lamps), fluorescent sources, phosphorescent sources, high-intensity discharge sources (e.g., sodium vapor, mercury vapor, and metal halide lamps), lasers, other types of electroluminescent sources, pyro-luminescent sources (e.g., flames), candle-luminescent sources (e.g., gas mantles, carbon arc radiation sources), photo-luminescent sources (e.g., gaseous discharge sources), cathode luminescent sources using electronic satiation, galvano-luminescent sources, crystallo-luminescent sources, kine-luminescent sources, thermo-luminescent sources, triboluminescent sources, sonoluminescent sources, radioluminescent sources, and luminescent polymers.
  • LED-based sources
  • a given light source may be configured to generate electromagnetic radiation within the visible spectrum, outside the visible spectrum, or a combination of both.
  • a light source may include as an integral component one or more filters (e.g., color filters), lenses, or other optical components.
  • filters e.g., color filters
  • light sources may be configured for a variety of applications, including, but not limited to, indication, display, and/or illumination.
  • An "illumination source” is a light source that is particularly configured to generate radiation having a sufficient intensity to effectively illuminate an interior or exterior space.
  • sufficient intensity refers to sufficient radiant power in the visible spectrum generated in the space or environment (the unit “lumens” often is employed to represent the total light output from a light source in all directions, in terms of radiant power or "luminous flux”) to provide ambient illumination (i.e., light that may be perceived indirectly and that may be, for example, reflected off of one or more of a variety of intervening surfaces before being perceived in whole or in part).
  • spectrum should be understood to refer to any one or more frequencies (or wavelengths) of radiation produced by one or more light sources.
  • the term “spectrum” refers to frequencies (or wavelengths) not only in the visible range, but also frequencies (or wavelengths) in the infrared, ultraviolet, and other areas of the overall electromagnetic spectrum.
  • a given spectrum may have a relatively narrow bandwidth (e.g., a FWHM having essentially few frequency or wavelength components) or a relatively wide bandwidth (several frequency or wavelength components having various relative strengths). It should also be appreciated that a given spectrum may be the result of a mixing of two or more other spectra (e.g., mixing radiation respectively emitted from multiple light sources).
  • color is used interchangeably with the term “spectrum.”
  • the term “color” generally is used to refer primarily to a property of radiation that is perceivable by an observer (although this usage is not intended to limit the scope of this term). Accordingly, the terms “different colors” implicitly refer to multiple spectra having different wavelength components and/or bandwidths. It also should be appreciated that the term “color” may be used in connection with both white and non-white light.
  • color temperature generally is used herein in connection with white light, although this usage is not intended to limit the scope of this term.
  • Color temperature essentially refers to a particular color content or shade (e.g., reddish, bluish) of white light.
  • the color temperature of a given radiation sample conventionally is characterized according to the temperature in degrees Kelvin (K) of a black body radiator that radiates essentially the same spectrum as the radiation sample in question.
  • Black body radiator color temperatures generally fall within a range of approximately 700 degrees K (typically considered the first visible to the human eye) to over 10,000 degrees K; white light generally is perceived at color temperatures above 1500-2000 degrees K.
  • the term "lighting fixture” is used herein to refer to an implementation or arrangement of one or more lighting units in a particular form factor, assembly, or package.
  • the term "lighting unit” is used herein to refer to an apparatus including one or more light sources of same or different types.
  • a given lighting unit may have any one of a variety of mounting arrangements for the light source(s), enclosure/housing arrangements and shapes, and/or electrical and mechanical connection configurations. Additionally, a given lighting unit optionally may be associated with (e.g., include, be coupled to and/or packaged together with) various other components (e.g., control circuitry) relating to the operation of the light source(s).
  • LED-based lighting unit refers to a lighting unit that includes one or more LED-based light sources as discussed above, alone or in combination with other non LED-based light sources.
  • a “multi-channel” lighting unit refers to an LED-based or non LED- based lighting unit that includes at least two light sources configured to respectively generate different spectrums of radiation, wherein each different source spectrum may be referred to as a "channel" of the multi-channel lighting unit.
  • the term “luminaire” is used herein to refer to a lighting fixture, lamp, or other device into which a lighting unit may be installed.
  • a lighting unit in the form of an LED light bulb may be screwed into a socket of a luminaire such as a desk lamp, hanging lamp or standing lamp.
  • the luminaire may be connected to a power source such as AC mains, and may be configured to, among other things, supply power to an installed lighting unit so that the light unit is capable of emitting light.
  • controller is used herein generally to describe various apparatus relating to the operation of one or more light sources.
  • a controller can be implemented in numerous ways (e.g., such as with dedicated hardware) to perform various functions discussed herein.
  • a "processor” is one example of a controller which employs one or more microprocessors that may be programmed using software (e.g., microcode) to perform various functions discussed herein.
  • a controller may be implemented with or without employing a processor, and also may be implemented as a combination of dedicated hardware to perform some functions and a processor (e.g., one or more programmed microprocessors and associated circuitry) to perform other functions. Examples of controller components that may be employed in various embodiments of the present disclosure include, but are not limited to, conventional microprocessors, application specific integrated circuits (ASICs), and field-programmable gate arrays (FPGAs).
  • ASICs application specific integrated circuits
  • FPGAs field-programmable gate arrays
  • a processor or controller may be associated with one or more storage media (generically referred to herein as "memory,” e.g., volatile and nonvolatile computer memory such as RAM, PROM, EPROM, and EEPROM, floppy disks, compact disks, optical disks, magnetic tape, etc.).
  • the storage media may be encoded with one or more programs that, when executed on one or more processors and/or controllers, perform at least some of the functions discussed herein.
  • Various storage media may be fixed within a processor or controller or may be transportable, such that the one or more programs stored thereon can be loaded into a processor or controller so as to implement various aspects of the present invention discussed herein.
  • program or “computer program” are used herein in a generic sense to refer to any type of computer code (e.g., software or microcode) that can be employed to program one or more processors or controllers.
  • addressable is used herein to refer to a device (e.g., a light source in general, a lighting unit or fixture, a controller or processor associated with one or more light sources or lighting units, other non-lighting related devices, etc.) that is configured to receive information (e.g., data) intended for multiple devices, including itself, and to selectively respond to particular information intended for it.
  • information e.g., data
  • addressable often is used in connection with a networked environment (or a "network,” discussed further below), in which multiple devices are coupled together via some communications medium or media.
  • one or more devices coupled to a network may serve as a controller for one or more other devices coupled to the network (e.g., in a master/slave relationship).
  • a networked environment may include one or more dedicated controllers that are configured to control one or more of the devices coupled to the network.
  • multiple devices coupled to the network each may have access to data that is present on the communications medium or media; however, a given device may be "addressable" in that it is configured to selectively exchange data with (i.e., receive data from and/or transmit data to) the network, based, for example, on one or more particular identifiers (e.g., "addresses") assigned to it.
  • network refers to any interconnection of two or more devices (including controllers or processors) that facilitates the transport of information (e.g., for device control, data storage, data exchange, etc.) between any two or more devices and/or among multiple devices coupled to the network.
  • networks suitable for interconnecting multiple devices may include any of a variety of network topologies and employ any of a variety of communication protocols.
  • any one connection between two devices may represent a dedicated connection between the two systems, or alternatively a non-dedicated connection.
  • non-dedicated connection may carry information not necessarily intended for either of the two devices (e.g., an open network connection).
  • various networks of devices as discussed herein may employ one or more wireless, wire/cable, and/or fiber optic links to facilitate information transport throughout the network.
  • user interface refers to an interface between a human user or operator and one or more devices that enables communication between the user and the device(s). Examples of user interfaces that may be employed in various
  • implementations of the present disclosure include, but are not limited to, switches, potentiometers, buttons, dials, sliders, a mouse, keyboard, keypad, various types of game controllers (e.g., joysticks), track balls, display screens, various types of graphical user interfaces (GUIs), touch screens, microphones and other types of sensors that may receive some form of human-generated stimulus and generate a signal in response thereto.
  • Fig. 1 illustrates schematically components of a lighting system that includes lighting nodes coupled in a daisy-chain configuration via a unidirectional communication and addressing line.
  • Fig. 2 illustrates one example of a lighting system that includes a controller and a plurality of nodes that are coupled to one another via a data bus and daisy-chained together via an add ressing line.
  • Fig. 3 illustrates one example of a lighting node, in accordance with various embodiments.
  • Fig. 4A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
  • Fig. 4B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 4A.
  • Fig. 5A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
  • Fig. 5B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 5A.
  • Fig. 6A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
  • Fig. 6B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 6A.
  • Cu rrently available networked lighting systems comprise a plu rality of lighting units or nodes, wherein each lighting unit drives a number of light sou rces ⁇ e.g., a plurality of LEDs). These nodes are connected together to form a network of light sou rces. I n some examples, the networked lighting systems are series-connected or daisy-chained together and use the same data link for addressing the nodes and for data communication pu rposes. A controller of cu rrently available networked lighting systems uses an automatic addressing of nodes in the daisy chain, using any number of addressing schemes and data protocols such as those discussed in U.S. Pat. No. 6,608,453 and U.S. Pat. No.
  • the networked lighting system 100 includes a controller 105 and N light nodes or lighting units 101, 102, and 103. Only three nodes 101-103 are illustrated in FIG. 1, but it is u nderstood additional node(s) may be provided between the node 102 and the node 103.
  • the multiple nodes 101-103 are powered via cou plings to voltage line 106 and grou nd line 108.
  • the nodes 101-103 are coupled together via their commu nication ports to form a series connection of lighting u nits (e.g., a daisy-chain or ring topology), wherein each lighting unit has an input communication port and an output commu nication port.
  • Lighting instructions/data 107 is transmitted by the controller 105 and is provided sequentially to the nodes 101-103 based on their relative positions in the series connection of nodes.
  • the unidirectional networked lighting system 100 can employ any number of protocols.
  • a serial-based communication protocol includes the controller of each node 101-103 in the series connection receiving data, "stripping off” or extracting one or more initial portions of the data sequence intended for it, and transmitting the remainder of the data sequence to the next node in the series connection until the topologically last node 103 is reached .
  • mu lti-bit values one multi-bit value per channel
  • Each lighting unit 101- 103 in the series connection in turn repeats this proceedu re, namely, stripping off or extracting one or more initial portions (mu lti-bit values) of a received data sequence and transmitting the remainder of the sequence.
  • the initial portion of a data seq uence stripped off in turn by each lighting u nit 101-103 may include respective prescribed radiant powers for different available spectra of light ⁇ e.g., different color channels) capable of being generated by the lighting unit.
  • a flag is associated with each portion of a data sequence representing data for mu ltiple channels of a given lighting unit, and an entire data sequence for multiple lighting units is transmitted completely from lighting unit to lighting unit in the serial connection.
  • a lighting unit in the serial connection receives the data sequence, it looks for the first portion of the data seq uence in which the flag indicates that a given portion (representing one or more channels) has not yet been read by any lighting u nit.
  • the lighting u nit Upon finding such a portion, the lighting u nit reads and processes the portion to provide a corresponding light output, and sets the corresponding flag to indicate that the portion has been read . Again, the entire data sequence is transmitted completely from lighting unit to lighting unit, wherein the state of the flags indicate the next portion of the data sequence available for reading and processing.
  • the unidirectional networked lighting system 100 and each of the serial-based commu nication protocols described above may suffer from one or more disadvantages.
  • Applicants have recognized that when a node failure occurs, because the nodes are connected in only a serial configuration, the node failure disrupts data flow to other nodes that are downstream of the node failure.
  • the unidirectional configu ration may not allow bi-directional communication between controller and nodes, therefore preventing commu nications from the nodes for providing operational parameters of individual nodes ⁇ e.g., temperature, LED currents, LED voltages), add ress assignment acknowledgments, etc.
  • Applicants have recognized and appreciated that it would be beneficial to provide methods and apparatus related to an address and data commu nication protocol that enables reliable bi-directional data-communication between a controller and lighting units or nodes and/or that provides the capability to address all the lighting units on an individual basis.
  • methods and apparatus are disclosed that utilize separate add ress and data commu nication paths to enable a robust system that provides flexibility in node add ressing and/or bi-directional commu nication between the nodes and the controller.
  • Fig. 2 illustrates a networked lighting system, according to one embodiment, that includes a controller 220 and a plu rality of nodes 231-233 that are coupled to one another via a data bus 215 and coupled together via a serial addressing line 213.
  • the lighting system of Fig. 2 may provide one or more advantages.
  • the serial addressing line 213 used in a daisy-chain way allows for each of the nodes 231-233 to be individ ually addressable and provides further advantages in add ressing and commissioning of the nodes 231-233 in the system 200.
  • the data bus 215, separate from the serial addressing line 213, enables a more robust and more flexible system that may be less fault prone than previously disclosed series-connected lighting systems.
  • the networked lighting system 200 shown in Fig. 2 comprises a plurality of nodes or lighting units including nodes 231, 232, and 233 that are coupled together to form a network. Additional nodes may be present (as evidenced by the ellipsis of Fig. 2) and connected to one another and the data bus 215 in a similar manner, but are not explicitly illustrated in Fig. 2.
  • the nodes are daisy-chained or series-connected to each other, where node 231 is connected to node 232, which is connected to another node (illustrated by the ellipsis of Fig. 2), and that node or a further downstream node is connected to node 233.
  • the controller 220 is also serially connected to the nodes via a direct series- connection to node 231, which is the topologically first node.
  • the controller 220 comprises a PDS (Power Data Supply).
  • the controller 220 can provide power (via voltage line 211 and ground line 212), control data (via data bus 215), and/or address information (via addressing line 213) to the nodes 231-233.
  • other controllers may be used such as controllers that provide only control data and/or address information to the nodes 231-233.
  • other controllers may provide power to the nodes 231-233 and the nodes may be powered via another source.
  • the data bus 215 from the controller 210 comprises a differential data bus providing both a data input channel and a data output channel. In other embodiments, a channel may be used for both data input and data output.
  • the data bus 215 is connected in parallel to the nodes 231-233.
  • the controller 220 may be configured to interpret lighting instructions/data that are received in an Ethernet protocol (or similar protocol based on Ethernet concepts) from a computing device such as a personal computer (PC) and provide the data via the data output channel of the data bus 215 to effectuate lighting changes and/or other changes from the nodes 231-233.
  • the controller 220 can also receive feedback from the nodes 231-233 via the data bus 215 such as feedback information based on measured values of sensors o the nodes 231-233.
  • the controller 220 and the data bus 215 may be DMX enabled.
  • the lighting system 200 includes an addressing line 213 that is separate from the data bus 215.
  • the addressing line 213 connects each of the nodes 231- 233 in a series-connection and comprises a portion that connects controller 220 to an address input connection of node 231, a portion that connects between an address output of node 231 and an address input of node 232, a portion that connects between an address output of node 232 and an address input of a downstream node (not illustrated), and a portion between an address output of that or another downstream node and an address input of node 233.
  • the addressing line 213 facilitates automatic node discovery and commissioning, using one or more techniques described below with reference to Fig. 4-7.
  • the use of the data bus 215 and the separate addressing line 213 improves robustness against node failure, as well as interconnect and cabling failure. For example, if one of the nodes 231-233 fails in the daisy chain, the data communication via the data bus 215 is not interrupted. Further, the bi-directional nature of the data bus 215 allows bidirectional communication for transmitting control signals from the controller 220 to the nodes 231-233 and transmitting performance data and/or other data from the nodes 231- 233 to the controller 220.
  • Fig. 3 illustrates one of the nodes 231 of the lighting system 200 in further detail.
  • all or aspects of the node 231 can be realized as an application- specific integrated circuit (ASIC).
  • the node 231 comprises a DC/DC conversion circuit 2312 and LED drivers 2313R, G, B, A, W for corresponding colors of LEDs 201R, G, B, A, W.
  • the node 231 further comprises a node controller 2320 and memory 2322. As described in more detail herein, the node controller 2320 may determine a communication address for the node 231 based on input received via data communication connection 2330 and/or address input connection 2342. The node controller 2320 may further assign the communication address in memory 2332 and may transmit information over the address output connection 2344 to effectuate assigning of communication address by one or more other nodes connected serially downstream of the node 231 on an addressing line. The node controller 2320 may also receive sensor values from thermistor 2315 and/or other sensors of the node 231 and transmit, via the data communication connection 2330, operational feedback information that is indicative of the sensor values (and optionally indicative of other values).
  • the DC-DC conversion circuit 2312 in the node 231 may enable higher operation voltage thereby allowing the use of thinner power cables and/or accommodation of more nodes, which may lead to an increase in LED current, such as >100mA per channel for high brightness LEDs and a relatively high supply voltage, such as > 50V.
  • the DC-DC conversion circuit 2312 may down-convert the high voltage bus supply received over lines 211/212 (Fig. 2). Two independent output voltages (Voutl and Vout2) are generated by the DC-DC conversion circuit 2312 to connect to the Red and Amber LEDs 201R, A (Vout2) and Green, Blue, and White LEDs 201G, B, W (Voutl).
  • the output voltages can be chosen such, depending on the number of LEDS, that the voltage conversion is as efficient as possible.
  • the node 231 also contains a voltage regulator 2311 and band gap circuits 2314 to generate voltages to be used in the analog and digital domain of the circuit blocks in the architecture.
  • the node 231 includes a data communication connection 2330, an address input connection 2342, and an address output connection 2344.
  • the data communication connection 2330 may receive control data, including control data that is addressed to the node 231 and the node controller 2320 may adjust the output of one or more of the drivers 2313R, A, B, G, W and/or other components based on the control data that is addressed to the node 231.
  • the control data may include parameters that prescribe radiant powers for different available spectra of light (e.g., different color channels) capable of being generated by the LEDs 201R, A, B, G, W, and the node controller 2320 may adjust one or more drivers and/or other components to achieve the prescribed radiant powers.
  • the node controller 2320 may compare an address associated with control data to a commissioned communication address stored in memory 2322 to identify the control data that is directed to the node 231.
  • the node controller 2320 may also transmit operational feedback information over the data communication connection 2330.
  • the node controller 2320 may transmit the operational feedback information with the communication address of the node 231 or other identifier that enables the controller 220 to identify the information originates from the node 231.
  • This node specific operational feedback information can be used for real-time status diagnostic reporting such as, for example, temperature, LED currents, and/or LED voltages.
  • the controller 220 may optionally utilize the operational feedback information from one or more nodes to alter control data provided to one or more nodes 231-233 to, for example, perform LED color correction and/or color compensation.
  • the networked lighting system 200 described above may utilize one or more address commissioning and/or data communication techniques to enable one or more of its functionalities.
  • Figs. 4A-6B describe some examples of address commissioning techniques that assign communication addresses to the nodes 231-233 in the lighting system 200 via utilization of the addressing line 213. The techniques described provide address
  • control data may be sent by the controller 220 that is addressed only to one of the nodes 231.
  • control data may be sent by the controller 220 that includes a first portion addressed to the node 231 and a second portion addressed to the node 232.
  • each of the nodes in the networked lighting system 200 has a communication address that is unique from the communication address of any other of the nodes in the networked lighting system 200.
  • two or more nodes may optionally share the same address such that they each act on the same control data and respond in an identical fashion.
  • the nodes 231-233 are each assigned a unique serial number during manufacture/assembly and the serial number of a given node is stored in memory of the node. Besides this serial number, each of the nodes 231-233 may have other data stored in memory during manufacture such as, for example, color calibration data based on optical measuring of light output from the light source(s) of the node. As the networked lighting system 200 is installed, the nodes 231-233 are commissioned. The commissioning process enables the controller 220 to determine a communication address for each node in the lighting system 200 and optionally enables the controller 220 to store an association between the unique serial numbers and the communication addresses of the nodes and/or the color calibration data and the communication addresses of the nodes.
  • the serial number of a node may be a 64-bit unique number assigned to the node at assembly and stored in the memory of the node and the communication address may be a 16-bit address associated with the node according to techniques described herein. However, it is appreciated that other address and serial number sizes may be used .
  • address and serial number sizes may be used .
  • Fig. 4A illustrates a method 400 of commissioning according to one embodiment.
  • method 400 comprises use of a token or a flag that is serially communicated via the add ressing line to the topologically first node.
  • the token is then commu nicated serially via the addressing line to the subsequent nodes, one node at a time.
  • each node assigns an add ress and communicates the add ress to the controller via the data bus.
  • the controller determines the position of each commu nication address in the node chain ⁇ e.g., the first acknowledgment corresponds to the topologically closest node and the last acknowledgment corresponds to the topologically farthest node).
  • a controller transmits a non-active token to the address input of a topologically first node.
  • the controller 220 may transmit a non-active token to the add ress input of node 231.
  • the non-active token may be a logic "low” such as a voltage that is less than a threshold.
  • alternative non- active tokens may be utilized such as a logic "high” or a series of bits or other informational packet.
  • the controller broadcasts a request for node discovery via the data bus.
  • the nodes receive the request, causing the nodes to set a non-active token on their add ress output connections and to wait for their address input connections to go active before assigning themselves a communication address.
  • the controller 220 broadcasts, and the nodes 231-233 receive, a request for node discovery on the data bus 215.
  • the nodes 231-233 receive the request and, responsive to the request, set a non-active token ⁇ e.g., a logic "low”) on their add ress output connections and wait for their address input connections to go active ⁇ e.g., a logic "high”).
  • the controller transmits an active token to the topologically first node.
  • the active token is a logic "high” such as a voltage that is greater than a threshold
  • the controller 220 may provide output that sets the add ressing line 213 extending between the controller 220 and the address input connection of the node 231 to "high.”
  • the topologically first node determines and stores a communication address, and transmits an acknowledgment to the controller via the data bus.
  • the controller of the node 231 may identify receipt of the token, generate an address for the node, and store the address in the memory of the node.
  • the node 231 may also acknowledge to controller 220 over the parallel data bus 215 that the communication address of the node 231 has been set, for example, by sending the serial number of the node 231 and optionally the assigned communication address.
  • the topologically first node determines the communication address based on the request for node discovery of block 404.
  • the request may have included the communication address to be used by the next node that receives the active token, and the node 231 may have buffered the communication address as a potential address and assigned the buffered communication address as an actual address in response to receiving the active token.
  • the controller broadcasts a request for the next node via the data bus. For example, once the acknowledgement is received from the node that most recently assigned a communication address (node 231 in the first iteration), the controller 220 broadcasts, and the nodes receive, a request for node discovery via the data bus 215.
  • the node that most recently transmitted the acknowledgement (node 231 in the first iteration) transmits the active token to the topologically next node. For example, in the first iteration and where the active token is a logic "high", node 231 may set its address output to "high" to transmit the active token to the address input of node 232.
  • the topologically next node determines and stores a communication address, and transmits an acknowledgment to the controller via the data bus.
  • a controller of the node 232 may receive the token, generate an address for the node 232, and store the address in the memory of the node 232.
  • the node 232 may also acknowledge to controller 220 over the parallel data bus 215 that the communication address of the node 232 has been set, for example, by sending the serial number of the node 232 and optionally the assigned communication address.
  • the topologically next node determines the communication address based on the most recent request for next node discovery of block 410.
  • the request may have included the communication address to be used by the next node that receives the active token, the topologically next node may have buffered the communication address as a potential address (and cleared out any preceding potential addresses), and assigned the buffered commu nication address as an actual address in response to receiving the active token.
  • each communication address buffered and used as an actual add ress in response to receiving the active token may be u niq ue from any other commu nication addresses assigned to other nodes in the lighting network.
  • the controller 220 may provide requests for node discovery such that multiple nodes will have the same communication add ress when they receive the active token and the mu ltiple nodes will all assign the same communication address and respond to the same control data addressed to that communication address. For example, a first communication address may be assigned to each of the first five nodes, a second
  • each of the acknowledgments sent to the controller 220 may include the determined communication address and/or an assigned serial nu mber of the node that is transmitting the acknowledgment.
  • the controller 220 may utilize the serial nu mbers and communication addresses to create a data structure that defines relationships between the communication addresses and serial numbers. This may be beneficial for various pu rposes such as, for example, determining the serial number of a node that may suffer a futu re communication failure - and providing the serial number to a user to enable the user to identify and replace the node.
  • the controller determines whether all nodes are add ressed . If not, steps in blocks 410, 412, and 414 are repeated until all nodes or the N nodes in the chain are add ressed . If all nodes are addressed, commissioning ends at block 418 and control data may be addressed to the nodes via the data bus based on the communication addresses determined via the method 400 of FIG. 4. In some embodiments, the controller 220 may know the total nu mber of nodes ⁇ e.g., based on input from a user) and the controller 220 may determine all nodes are addressed by determining the nu mber of acknowledgments equals the total number of nodes.
  • the controller 220 may determine all nodes are addressed based on not receiving an acknowledgement within a time out period of the last iteration of block 410. For example, after the last node N receives the token and the address is communicated to the controller, there is a timeout for the subsequent node to reply with the address. The controller may associate this time out with addressing all the nodes in the chain.
  • Fig. 4B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 4A.
  • the communication interactions of Fig. 4B are described with reference to corresponding blocks in Fig. 4A, and the communication interactions of Fig. 4B are labeled with the corresponding blocks of Fig. 4A (in parentheses in Fig. 4B).
  • the controller 220 sends a non-active token to an address input of node 231 at block 402.
  • the controller 220 sends a request for node discovery to the data bus 215 at block 404 and the node 231 sends a non-active token to an address input of the node 232 in response to receiving (via the data bus 215) the request for node discovery at block 404.
  • the controller 220 sends an active token to node 231 at block 406 of Fig. 4A.
  • the node 231 determines and assigns a communication address based on receiving the active token and sends an acknowledgment of assignment of the address to the data bus 215 at block 408.
  • the controller sends a request for the next node to the data bus 215 at block 410 and the node 231 sends an active token to the node 232 at block 412.
  • the node 232 determines and assigns a communication address based on receiving the active token and sends an acknowledgment of assignment of the address to the data bus 215 at block 414.
  • the controller sends a request for the next node to the data bus 215 at block 410.
  • the node 232 would send an active token to the topologically next node and further communications would result between the various components until all nodes are addressed and commissioning ends.
  • Fig. 5A illustrates a method 500 of commissioning according to another embodiment.
  • method 500 comprises a controller sending a token to the topologically first node, wherein the token indicates a communication address for the first node to assign to itself.
  • the first node assigns itself a communication address based on the token, adjusts the token according to an adjustment protocol, and sends the adjusted token to the next node via the addressing line, where the process is repeated.
  • the first node and subsequent nodes may each send an acknowledgment to the controller prior to transmitting the adjusted token to a topologically next node.
  • a controller transmits a non-active token to the address input of a topologically first node.
  • the controller 220 may transmit a non-active token to the add ress input of node 231.
  • the non-active token may be a logic "low" such as a voltage that is less than a threshold.
  • alternative non- active tokens may be utilized.
  • the controller broadcasts a request for node discovery via the data bus.
  • the nodes receive the request, causing the nodes to set the non-active token on their add ress output connection.
  • the controller 220 broadcasts, and the nodes 231- 233 receive, a request for node discovery on the data bus 215.
  • the nodes 231-233 receive the request and, responsive to the request, set a non-active token ⁇ e.g., a logic "low") on their add ress output connections and wait for their add ress input connections to go active ⁇ e.g., a logic "high”).
  • the controller transmits a commu nication add ress to the address input of the topologically first node. For example, the controller 220 sends "Address 1" to the first node 231 using the add ressing line 213.
  • topologically first node stores the communication address in memory as its address, and transmits an acknowledgment to the controller via the data bus.
  • the node 231 assigns Add ress 1 to itself and stores the add ress in the memory.
  • the node 231 sends acknowledgement to the controller 220 over the data bus.
  • the node 231 may send acknowledgement, by sending the serial number of the node 231 and optionally the assigned communication address.
  • the node that most recently stored the communication address as its add ress (the topologically first node in the first iteration) adjusts the communication add ress according to an adjustment protocol and transmits the adjusted commu nication add ress to the topologically next node via the add ressing line.
  • adjusting the communication add ress according to the adjustment protocol comprises incrementing the communication address by a fixed amou nt such as by one or two.
  • Other adjustment protocols may be utilized such as those that decrement and/or those that adjust commu nication addresses in a non-linear fashion.
  • the commu nication address may not be adjusted at every node and/or may otherwise be adjusted such that two or more nodes may share the same communication address.
  • the commu nication address may only be adjusted at every nth node ⁇ e.g., with nodes keeping track of acknowledgments to count nodes).
  • the topologically next node in response to receiving the adjusted communication address, stores the adjusted communication address as its address, and transmits an acknowledgment to the controller via the data bus.
  • the node 232 assigns the adjusted communication address to itself and stores the address in the memory.
  • the node 232 sends acknowledgement to the controller 220 over the parallel data bus.
  • the node 232 may send acknowledgement for example, by sending the serial nu mber of the node 232 and optionally the assigned commu nication address.
  • the controller determines whether all nodes are add ressed . If not, steps in blocks 510 and 512 are repeated u ntil all nodes or the N nodes in the chain are add ressed . If all nodes are addressed, commissioning ends at block 516 and control data may thereafter be addressed to the nodes based on the communication add resses determined via the method 500 of FIG. 5.
  • the controller 220 may know the total nu mber of nodes ⁇ e.g., based on input from a user) and the controller 220 may determine all nodes are addressed by determining the nu mber of acknowledgments equals the total number of nodes.
  • the total nu mber of nodes may be pre-set by a user.
  • the controller 220 may determine all nodes are addressed based on not receiving an acknowledgement within a time out period of receiving an acknowledgment in the last iteration of block 512.
  • each of the acknowledgments sent to the controller 220 may include the determined communication address and an assigned serial nu mber of the node that is transmitting the acknowledgment.
  • the controller 220 may utilize the serial nu mber and commu nication addresses to create a data structure that defines relationships between the node address and serial numbers.
  • Fig. 5B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 5A.
  • the controller 220 sends a non-active token to the address input of node 231 at block 502.
  • the controller 220 sends a request for node discovery to the data bus 215 at block 504 and the node 231 sends a non-active token to the node 232 at block 504 in response to receiving (via the data bus 215) the request for node discovery.
  • the controller 220 sends a communication address to the address input of node 231 at block 506.
  • the node 231 assigns a communication address based on the received communication address and sends an acknowledgment of assignment of the address to the data bus 215 at block 508.
  • the node 231 determines an adjusted communication address based on an adjustment protocol and sends the adjusted communication address to the node 232 at block 510.
  • the node 232 assigns a communication address based on the received adjusted communication address and sends an acknowledgment of assignment of the address to the data bus 215 at block 508 of Fig. 5A.
  • the node 232 would determine a further adjusted communication address and send it to the topologically next node at block 510 and further communications would result between the various components until all nodes are addressed and commissioning ends.
  • Fig. 6A illustrates a method 600 of commissioning according to another embodiment.
  • method 600 is similar to method 500, but includes additional verification, by the nodes, of the addresses communicated via the addressing line based on comparing the address communicated via the addressing line to address setting information sent over the data bus.
  • the controller sends a "clear last token” message to all nodes over the data bus and all nodes clear any tokens they have stored in their token register.
  • the topologically first node compares the token received via the addressing line 213 and the message received via the data bus 215, determines they match, and assigns itself a communication address of X based on them matching.
  • the topologically first node further sends acknowledgement to the controller via the data bus 215.
  • the node that most recently stored the communication address as its address (the topologically first node in the first iteration) adjusts the communication address according to an adjustment protocol and transmits the adjusted communication address to the topologically next node via the addressing line.
  • adjusting the communication address according to the adjustment protocol comprises incrementing the communication address by a fixed amount such as by one or two.
  • Other adjustment protocols may be utilized such as those that decrement and/or those that adjust communication addresses in a non-linear fashion.
  • the "Adjusted Communication Address” of the message will match the adjusted communication address transmitted via the addressing line at block 610.
  • the adjustment protocol may be implemented such that two or more nodes have the same communication address at the end of commissioning.
  • the topologically next node compares the token received via the addressing line 213 and the message received via the data bus 215, determines they match, and assigns itself the adjusted communication address based on them matching. The topologically first node further sends acknowledgement to the controller via the data bus 215.
  • Block 616 ensures that steps in blocks 610, 612, and 614 are repeated until all nodes are covered.
  • the user either user tells the controller the total number of nodes in the string OR there is a timeout for the last node to reply with and Address.
  • the controller broadcasts a "clear last token" message to all nodes over the data bus and the nodes clear tokens in response to receiving the message. The controller may then create node address to serial-number association table.
  • Fig. 6B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 6A.
  • the communication interactions of Fig. 6B are described with reference to corresponding blocks in Fig. 6A, and the communication interactions of Fig. 6B are labeled with the corresponding blocks of Fig. 6A (in parentheses in Fig. 6B).
  • Fig. 6B the controller 220 sends a clear last token message to the all of the nodes via the data bus 215 at block 602.
  • the node 231 assigns a communication address of "X" based on the token received via the addressing line 213 and the message received via the data bus 215 matching one another.
  • the node 231 sends an acknowledgment of assignment of the address to the data bus 215 at block 608.
  • the node 231 determines an adjusted
  • the "X + 1" of the message matches the adjusted communication address transmitted from node 231 to node 232 via the addressing line 213.
  • the node 232 has possession of a token received via the addressing line 213 that matches a message received via the data bus 215.
  • the node 232 determines they match, assigns itself the adjusted communication address based on them matching, and sends acknowledgement to the controller via the data bus 215 at block 614.
  • the node 232 would determine a further adjusted communication address and send it to the topologically next node and further communications would result between the various components until all nodes are addressed and commissioning ends.
  • Yet another embodiment of a method of commissioning is similar to method 600 except the Token (sent via the addressing line 213) forms a key/dehashing function to decode the address setting message sent via the data bus 215. Unless a node has possession of a token received via the addressing line 213 that decodes a message received via the data bus 215, the node will not carry out any actions and will clear its token and message registers.
  • the address of the decoded message may be utilized as the communication address for the node (and adjusted and sent to an address input of a topologically next node in a similar manner as described with respect to Fig. 6A).
  • a specific "clear token register" message is not needed, but token and message pairs must be chosen to ensure that all non-matching message-token pairs decode to a "clear all registers" result.
  • the system and the protocols described enable node fault detection when the networking system suffers from node failure or electrical contact/cable failure.
  • the controller 220 can perform node fault detection by comparing the number of discovered nodes and the number expected by the application. Fault localization is possible as the node following the last discovered addressed is where the problem begins. If the fault is an electrical contact on the addressing line, the nodes can still be operated since they have their address stored locally on memory at initial configuration.
  • Each of the nodes 231-233 would subsequently receive the messages and respond with a corresponding stored node address and serial number associated with the node.
  • the node address stored corresponds to the communication address determined using one of the commissioning protocols described above. If the controller 220 does not receive a response to such a message within a timeout period, the controller moves on to the next expected address in the sequence.
  • the controller 220 Based on the table of addresses and serial numbers, the controller 220
  • the controller 220 determines missing or nonconsecutive Address numbers (those for which no response to the Address Request Message was received).
  • the first such missing address is defined as a specific address (for example Address Y).
  • the controller 220 can then send a message on the parallel data bus 215 to all nodes assigning the node without an address with the specific address (address Y).
  • the controller 220 can then inform the maintenance personnel to remove the topologically next broken node from the string and replace it with a working replacement (currently not assigned an Address number).
  • the controller 220 can then send a message on the data bus to all nodes assigning the node without an address with topologically next missing address. This process can repeat until all nodes are replaced, one at a time.
  • the maintenance personnel can confirm all broken nodes are replaced.
  • inventive embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed.
  • inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein.
  • a reference to "A and/or B", when used in conjunction with open-ended language such as “comprising” can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.
  • At least one of A and B can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.

Abstract

A lighting system (200), comprising a plurality of addressable nodes (231-233) coupled together to form a network, at least one addressable node of the plurality of addressable nodes coupled to at least one LED light source, and at least one controller (220) coupled to the network and programmed to transmit and receive data to and from the plurality of addressable nodes via a bidirectional data communication channel (215) that forms a bus connection to the plurality of addressable nodes. The controller may be programmed to transmit address information via an addressing line (213) to facilitate addressing of the nodes during commissioning of the nodes. The addressing line forms a serial connection between the plurality of addressable nodes.

Description

LIGHTI NG CONTROL APPARATUS AND M ETHODS
Technical Field
[0001] The present invention relates to lighting control apparatus and methods, and more particularly, to methods and apparatus related to one or more aspects of a networked lighting system for connection and control of various light sources and other devices.
Backgrou nd
[0002] Digital lighting technologies, i.e., illumination based on semiconductor light sources, such as light-emitting diodes ("LEDs"), offer a viable alternative to traditional fluorescent, HI D, and incandescent lamps. Functional advantages and benefits of LEDs include high energy conversion and optical efficiency, du rability, lower operating costs, and many others. Recent advances in LED technology have provided efficient and robust full- spectru m lighting sources that enable a variety of lighting effects in many applications. Some of the fixtures embodying these sou rces feature a lighting modu le, including one or more LEDs capable of prod ucing different colors, e.g., red, green, and blue, as well as a processor for independently controlling the output of the LEDs in order to generate a variety of colors and color-changing lighting effects, for example, as discussed in detail in U.S. Patent Nos. 6,016,038 and 6,211,626, incorporated herein by reference.
[0003] Many LED networked lighting systems are built-up out of severa l hundred nodes and each node d rives one or more LEDs. The nodes are connected to a controller with a power bus and a daisy chained data line. The nodes are controlled within the system via the controller and all nodes have a unique add ress. The controller sets, for example, the LED color per node, and sends the LED color per node (i.e., an LED color is set for each address) over the daisy chained data line.
[0004] The above described LED networked lighting systems use the same connection for add ressing of the nodes as for data-communication pu rposes. All the nodes are connected in a daisy chain manner and there is automatic add ressing of nodes via the daisy chain connection. After addressing, each node receives system data, extracts its own data from the system data via the daisy-chain connection, fills the extracted data of the system data with zeroes (no-data), and forwards the system data with filled zeroes to a downstream node where the process repeats. This is a simple uni-directional data flow that suffers from one or more disadvantages. For example, due to the daisy-chain connection between the nodes, any issue with one of the nodes, or any issue with cabling and/or connections between two nodes will cause interruption of data delivery to any nodes that are connected downstream of the issue in the daisy-chained data line. Also, for example, the unidirectional data flow does not allow for bi-directional communication between the controller and the nodes.
[0005] Thus, there is a need in the art to provide methods and apparatus that optionally overcome one or more of the above drawbacks and/or other drawbacks.
Summary
[0006] The present disclosure is directed to various inventive methods and apparatus related to one or more aspects of a networked lighting system for connection and control of various light sources and other devices. Some embodiments of the present disclosure are directed to a lighting system that includes a plurality of addressable nodes coupled together to form a network and at least one controller coupled to the network and programmed to transmit and receive data to and from the plurality of addressable nodes via a bidirectional data bus connection to the plurality of addressable nodes. The controller may also be programmed to transmit address information via an addressing line to facilitate addressing of the nodes during commissioning of the nodes. The addressing line forms a serial connection between the plurality of addressable nodes. Other embodiments are directed toward methods related to the commissioning of the nodes. Yet other embodiments are directed toward the controller for commissioning and/or controlling the nodes, and/or toward the nodes themselves.
[0007] In one aspect, a lighting system is provided that includes a plurality of nodes and a controller. The nodes each include a node controller, memory, a data communication connection, an address input connection, and an address output connection. At least one node of the plurality of nodes is coupled to and controls at least one LED light source. The data communication connections of the nodes are all coupled to a data bus and the nodes are coupled in series via the address input connections and the address output connections. The controller is coupled to the nodes via the data bus and coupled to the address input connection of a first node of the nodes. The controller is configured to transmit address information to the address input connection of the first node. The node controller of the first node is configured to assign itself a communication address based on receiving the address information, wherein the node controller stores the communication address in the memory of the first node and wherein the node controller is further configured to transmit information over the address output connection of the first node to effectuate assigning of communication addresses by other of the nodes. The controller is further configured to broadcast control data to the plurality of nodes via the data bus, the control data addressed to one or more of the nodes based on respective of the communication addresses assigned by the nodes.
[0008] In some embodiments, the control data comprises first control data addressed to the at least one node, the first control data comprising one or more control parameters for control of the at least one LED light source of the at least one node. In some of those embodiments the at least one LED light source includes at least one red LED light source, at least one green LED light source, and at least one blue LED light source and the at least one node controls the at least one red LED light source, the at least one green LED light source, and the at least one blue LED light source, based on the control parameters.
[0009] In some embodiments, the controller is further configured to receive operational feedback information from the plurality of nodes via the data bus.
[0010] In some embodiments, the address information comprises the communication address and the node controller of the first node is further configured to adjust the communication address according to a fixed adjustment protocol to create an adjusted communication address— and the information transmitted over the output connection of the first node comprises the adjusted communication address. In some of those embodiments, the first node is configured to transmit an acknowledgement of assignment of the communication address to the controller via the data bus and transmit the adjusted communication address following the transmission of the acknowledgement of assignment of the communication address.
[0011] In some embodiments, the address information comprises an active token, the first node is configured to assign itself the communication address based on receiving the active token, and the information transmitted over the address output connection comprises the active token. In some of those embodiments, the first node is configured to assign a communication address of the first node based on: receiving the address information, receiving address setting information via the data communication connection of the first node, and comparing the address information to the address setting information. In some of those embodiments, the first node is configured to transmit an
acknowledgement of assignment of the communication address to the controller via the data bus and transmit the active token over the output connection following the
transmission of the acknowledgement of assignment of the communication address. The acknowledgement of assignment of the communication address to the controller may comprise a serial number of the first node and the controller may be further configured to store an association between the serial number and the communication address.
[0012] In some embodiments, the first node is configured to transmit an
acknowledgement of assignment of the communication address to the controller via the data bus and transmit the information over the address output connection of the first node following transmission of the acknowledgement of assignment of the communication address. In some of those embodiments, the acknowledgement of assignment of the communication address to the controller comprises a serial number of the first node and the controller is further configured to store an association between the serial number and the communication address.
[0013] In another aspect, a method is provided that comprises: receiving address information at a serially connected address input connection of a node, the node coupled to and controlling at least one LED light source; determining, by at least one controller of the node, a communication address based on receiving the address information; storing the communication address in memory of the node; receiving control data at a data bus connected data communication connection of the node; determining, by the controller, that at least a portion of the control data is addressed to the communication address in the memory of the node; and adjusting at least one light output parameter of the LED light source based on the portion of the control data, the adjusting in response to determining that the portion of the control data is addressed to the communication address. [0014] In some embodiments, the method further comprises receiving values from one or more sensors of the node and transmitting, via the data communication connection of the node, operational feedback information indicative of the values.
[0015] In some embodiments, the method further comprises transmitting information over an address output connection of the node to effectuate assigning of communication addresses by an additional node serially connected to the node via the address output connection. In some of those embodiments, the address information comprises the communication address, and the method further comprises adjusting the communication address according to a fixed adjustment protocol to create an adjusted communication address— wherein the information transmitted via the address output connection comprises the adjusted communication address. In some versions of those embodiments, the method further comprises transmitting an acknowledgement of assignment of the communication address via the data bus, wherein transmitting the adjusted communication address occurs after transmitting the acknowledgement of assignment of the
communication address.
[0016] In some embodiments, the address information comprises an active token and the information transmitted over the address output connection comprises the active token. In some versions of those embodiments, the method further comprises transmitting an acknowledgement of assignment of the communication address via the data bus, wherein transmitting the active token occurs after transmitting the acknowledgement of assignment of the communication address.
[0017] In some embodiments, the method further comprises transmitting an
acknowledgement of assignment of the communication address via the data bus, wherein transmitting the information over the address output connection of the node occurs after transmitting the acknowledgement of assignment of the communication address. In some of those embodiments, the acknowledgement of assignment of the communication address to the controller comprises a serial number stored in memory of the node and comprises the communication address.
[0018] In another aspect, a method is provided that comprises: broadcasting node discovery information to a plurality of nodes via a bus connection to the plurality of nodes, the nodes including at least one node that is coupled to and controls at least one LED light source; transmitting address information to an address input connection of a first node of the nodes without transmitting the address information to any other of the nodes, the address information configured to cause the first node to assign itself a communication address based on receiving the address information; and broadcasting control data to the plurality of nodes via the bus connection, the control data comprising first node control data addressed to the first node based on the communication address of the first node.
[0019] In some embodiments, the address information is an active token.
[0020] In some embodiments, the method further comprises: receiving an
acknowledgement of assignment of the communication address via the bus connection; and broadcasting, to the plurality of nodes via the bus connection and in response to receiving the acknowledgment of assignment of the communication address, a request for discovery of the next node.
[0021] In some embodiments, the method further comprises: receiving an
acknowledgement of assignment of the communication address via the bus connection; and generating the first node control data based on receiving the acknowledgment of assignment of the communication address.
[0022] In some embodiments the node discovery information comprises address setting information that matches the address information. In some of those embodiments, the address information forms a key that decodes the address setting information. In some of those embodiments, the address information and the address setting information are an exact match.
[0023] In some embodiments, the method further comprises: receiving from the first node an acknowledgement of assignment of the communication address via the bus connection, the acknowledgment of assignment of the communication address comprising a serial number of the first node; and storing in memory an association between the communication address and the serial number.
[0024] In another aspect, a method is provided that comprises: accessing a data structure that defines communication addresses of nodes coupled to a bus connection, the nodes including at least one node that is coupled to and controls at least one LED light source; broadcasting, for each of the communication addresses, an address request message to the nodes via the bus connection, the address request message for a
communication address of the communication addresses being configured to solicit a confirmatory response from a node of the nodes that has the communication address; monitoring the bus connection for the confirmatory response to each of the address request messages; determining a missing communication address associated with the address request message of the topologically closest node that failed to provide the confirmatory response in response to the address request message; broadcasting a command to the nodes via the bus connection, the command configured to cause any node that does not have a communication address assigned to assign the missing communication address.
[0025] In another aspect, an apparatus for use in commissioning and controlling a plurality of nodes is provided, wherein the nodes each include a connection for coupling to a data bus and a separate connection for a daisy-chain connection of the nodes, and wherein at least one node of the nodes is coupled to and controls at least one LED light source. The apparatus comprises a data bus connection to couple to the data bus, an addressing connection to couple to a first node of the nodes, memory storing instructions, and a controller operable to execute the instructions stored in the memory. Execution of the instructions by the controller causes the controller to: broadcast node discovery
information to the plurality of nodes via the bus connection; transmit address information to the first node of the nodes via the addressing connection without transmitting the address information to any other of the nodes, the address information configured to cause the first node to assign itself a communication address based on receiving the address information; and broadcast control data to the plurality of nodes via the bus connection, the control data comprising first node control data addressed to the first node based on the communication address of the first node.
[0026] In another aspect, an LED-based lighting unit is provided that comprises a data communication connection, an address input connection, an address output connection, at least one LED light source, memory, and a controller. The controller is configured to:
receive address information at the address input connection; determine a communication address based on receiving the address information; store the communication address in the memory; receive control data at a data communication connection of the node;
determine that at least a portion of the control data is addressed to the communication address in the memory; and adjust at least one light output parameter of the LED light source based on the portion of the control data, the adjusting in response to determining that the portion of the control data is addressed to the communication address. [0027] As used herein for purposes of the present disclosure, the term "LED" should be understood to include any electroluminescent diode or other type of carrier
injection/junction-based system that is capable of generating radiation in response to an electric signal. Thus, the term LED includes, but is not limited to, various semiconductor- based structures that emit light in response to current, light emitting polymers, organic light emitting diodes (OLEDs), electroluminescent strips, and the like. In particular, the term LED refers to light emitting diodes of all types (including semi-conductor and organic light emitting diodes) that may be configured to generate radiation in one or more of the infrared spectrum, ultraviolet spectrum, and various portions of the visible spectrum (generally including radiation wavelengths from approximately 400 nanometers to approximately 700 nanometers). Some examples of LEDs include, but are not limited to, various types of infrared LEDs, ultraviolet LEDs, red LEDs, blue LEDs, green LEDs, yellow LEDs, amber LEDs, orange LEDs, and white LEDs (discussed further below). It also should be appreciated that LEDs may be configured and/or controlled to generate radiation having various bandwidths (e.g., full widths at half maximum, or FWHM) for a given spectrum (e.g., narrow bandwidth, broad bandwidth), and a variety of dominant wavelengths within a given general color categorization.
[0028] For example, one implementation of an LED configured to generate essentially white light (e.g., a white LED) may include a number of dies which respectively emit different spectra of electroluminescence that, in combination, mix to form essentially white light. In another implementation, a white light LED may be associated with a phosphor material that converts electroluminescence having a first spectrum to a different second spectrum. In one example of this implementation, electroluminescence having a relatively short wavelength and narrow bandwidth spectrum "pumps" the phosphor material, which in turn radiates longer wavelength radiation having a somewhat broader spectrum.
[0029] It should also be understood that the term LED does not limit the physical and/or electrical package type of an LED. For example, as discussed above, an LED may refer to a single light emitting device having multiple dies that are configured to respectively emit different spectra of radiation (e.g., that may or may not be individually controllable). Also, an LED may be associated with a phosphor that is considered as an integral part of the LED (e.g., some types of white LEDs). In general, the term LED may refer to packaged LEDs, non- packaged LEDs, surface mount LEDs, chip-on-board LEDs, T-package mount LEDs, radial package LEDs, power package LEDs, LEDs including some type of encasement and/or optical element (e.g., a diffusing lens), etc.
[0030] The term "light source" should be understood to refer to any one or more of a variety of radiation sources, including, but not limited to, LED-based sources (including one or more LEDs as defined above), incandescent sources (e.g., filament lamps, halogen lamps), fluorescent sources, phosphorescent sources, high-intensity discharge sources (e.g., sodium vapor, mercury vapor, and metal halide lamps), lasers, other types of electroluminescent sources, pyro-luminescent sources (e.g., flames), candle-luminescent sources (e.g., gas mantles, carbon arc radiation sources), photo-luminescent sources (e.g., gaseous discharge sources), cathode luminescent sources using electronic satiation, galvano-luminescent sources, crystallo-luminescent sources, kine-luminescent sources, thermo-luminescent sources, triboluminescent sources, sonoluminescent sources, radioluminescent sources, and luminescent polymers.
[0031] A given light source may be configured to generate electromagnetic radiation within the visible spectrum, outside the visible spectrum, or a combination of both. Hence, the terms "light" and "radiation" are used interchangeably herein. Additionally, a light source may include as an integral component one or more filters (e.g., color filters), lenses, or other optical components. Also, it should be understood that light sources may be configured for a variety of applications, including, but not limited to, indication, display, and/or illumination. An "illumination source" is a light source that is particularly configured to generate radiation having a sufficient intensity to effectively illuminate an interior or exterior space. In this context, "sufficient intensity" refers to sufficient radiant power in the visible spectrum generated in the space or environment (the unit "lumens" often is employed to represent the total light output from a light source in all directions, in terms of radiant power or "luminous flux") to provide ambient illumination (i.e., light that may be perceived indirectly and that may be, for example, reflected off of one or more of a variety of intervening surfaces before being perceived in whole or in part).
[0032] The term "spectrum" should be understood to refer to any one or more frequencies (or wavelengths) of radiation produced by one or more light sources.
Accordingly, the term "spectrum" refers to frequencies (or wavelengths) not only in the visible range, but also frequencies (or wavelengths) in the infrared, ultraviolet, and other areas of the overall electromagnetic spectrum. Also, a given spectrum may have a relatively narrow bandwidth (e.g., a FWHM having essentially few frequency or wavelength components) or a relatively wide bandwidth (several frequency or wavelength components having various relative strengths). It should also be appreciated that a given spectrum may be the result of a mixing of two or more other spectra (e.g., mixing radiation respectively emitted from multiple light sources).
[0033] For purposes of this disclosure, the term "color" is used interchangeably with the term "spectrum." However, the term "color" generally is used to refer primarily to a property of radiation that is perceivable by an observer (although this usage is not intended to limit the scope of this term). Accordingly, the terms "different colors" implicitly refer to multiple spectra having different wavelength components and/or bandwidths. It also should be appreciated that the term "color" may be used in connection with both white and non-white light.
[0034] The term "color temperature" generally is used herein in connection with white light, although this usage is not intended to limit the scope of this term. Color temperature essentially refers to a particular color content or shade (e.g., reddish, bluish) of white light. The color temperature of a given radiation sample conventionally is characterized according to the temperature in degrees Kelvin (K) of a black body radiator that radiates essentially the same spectrum as the radiation sample in question. Black body radiator color temperatures generally fall within a range of approximately 700 degrees K (typically considered the first visible to the human eye) to over 10,000 degrees K; white light generally is perceived at color temperatures above 1500-2000 degrees K.
[0035] The term "lighting fixture" is used herein to refer to an implementation or arrangement of one or more lighting units in a particular form factor, assembly, or package. The term "lighting unit" is used herein to refer to an apparatus including one or more light sources of same or different types. A given lighting unit may have any one of a variety of mounting arrangements for the light source(s), enclosure/housing arrangements and shapes, and/or electrical and mechanical connection configurations. Additionally, a given lighting unit optionally may be associated with (e.g., include, be coupled to and/or packaged together with) various other components (e.g., control circuitry) relating to the operation of the light source(s). An "LED-based lighting unit" refers to a lighting unit that includes one or more LED-based light sources as discussed above, alone or in combination with other non LED-based light sources. A "multi-channel" lighting unit refers to an LED-based or non LED- based lighting unit that includes at least two light sources configured to respectively generate different spectrums of radiation, wherein each different source spectrum may be referred to as a "channel" of the multi-channel lighting unit. The term "luminaire" is used herein to refer to a lighting fixture, lamp, or other device into which a lighting unit may be installed. For example, a lighting unit in the form of an LED light bulb may be screwed into a socket of a luminaire such as a desk lamp, hanging lamp or standing lamp. The luminaire may be connected to a power source such as AC mains, and may be configured to, among other things, supply power to an installed lighting unit so that the light unit is capable of emitting light.
[0036] The term "controller" is used herein generally to describe various apparatus relating to the operation of one or more light sources. A controller can be implemented in numerous ways (e.g., such as with dedicated hardware) to perform various functions discussed herein. A "processor" is one example of a controller which employs one or more microprocessors that may be programmed using software (e.g., microcode) to perform various functions discussed herein. A controller may be implemented with or without employing a processor, and also may be implemented as a combination of dedicated hardware to perform some functions and a processor (e.g., one or more programmed microprocessors and associated circuitry) to perform other functions. Examples of controller components that may be employed in various embodiments of the present disclosure include, but are not limited to, conventional microprocessors, application specific integrated circuits (ASICs), and field-programmable gate arrays (FPGAs).
[0037] In various implementations, a processor or controller may be associated with one or more storage media (generically referred to herein as "memory," e.g., volatile and nonvolatile computer memory such as RAM, PROM, EPROM, and EEPROM, floppy disks, compact disks, optical disks, magnetic tape, etc.). In some implementations, the storage media may be encoded with one or more programs that, when executed on one or more processors and/or controllers, perform at least some of the functions discussed herein. Various storage media may be fixed within a processor or controller or may be transportable, such that the one or more programs stored thereon can be loaded into a processor or controller so as to implement various aspects of the present invention discussed herein. The terms "program" or "computer program" are used herein in a generic sense to refer to any type of computer code (e.g., software or microcode) that can be employed to program one or more processors or controllers.
[0038] The term "addressable" is used herein to refer to a device (e.g., a light source in general, a lighting unit or fixture, a controller or processor associated with one or more light sources or lighting units, other non-lighting related devices, etc.) that is configured to receive information (e.g., data) intended for multiple devices, including itself, and to selectively respond to particular information intended for it. The term "addressable" often is used in connection with a networked environment (or a "network," discussed further below), in which multiple devices are coupled together via some communications medium or media.
[0039] In one network implementation, one or more devices coupled to a network may serve as a controller for one or more other devices coupled to the network (e.g., in a master/slave relationship). In another implementation, a networked environment may include one or more dedicated controllers that are configured to control one or more of the devices coupled to the network. Generally, multiple devices coupled to the network each may have access to data that is present on the communications medium or media; however, a given device may be "addressable" in that it is configured to selectively exchange data with (i.e., receive data from and/or transmit data to) the network, based, for example, on one or more particular identifiers (e.g., "addresses") assigned to it.
[0040] The term "network" as used herein refers to any interconnection of two or more devices (including controllers or processors) that facilitates the transport of information (e.g., for device control, data storage, data exchange, etc.) between any two or more devices and/or among multiple devices coupled to the network. As should be readily appreciated, various implementations of networks suitable for interconnecting multiple devices may include any of a variety of network topologies and employ any of a variety of communication protocols. Additionally, in various networks according to the present disclosure, any one connection between two devices may represent a dedicated connection between the two systems, or alternatively a non-dedicated connection. In addition to carrying information intended for the two devices, such a non-dedicated connection may carry information not necessarily intended for either of the two devices (e.g., an open network connection). Furthermore, it should be readily appreciated that various networks of devices as discussed herein may employ one or more wireless, wire/cable, and/or fiber optic links to facilitate information transport throughout the network.
[0041] The term "user interface" as used herein refers to an interface between a human user or operator and one or more devices that enables communication between the user and the device(s). Examples of user interfaces that may be employed in various
implementations of the present disclosure include, but are not limited to, switches, potentiometers, buttons, dials, sliders, a mouse, keyboard, keypad, various types of game controllers (e.g., joysticks), track balls, display screens, various types of graphical user interfaces (GUIs), touch screens, microphones and other types of sensors that may receive some form of human-generated stimulus and generate a signal in response thereto.
[0042] It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.
Brief Description of the Drawings
[0043] In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention.
[0044] Fig. 1 illustrates schematically components of a lighting system that includes lighting nodes coupled in a daisy-chain configuration via a unidirectional communication and addressing line.
[0045] Fig. 2 illustrates one example of a lighting system that includes a controller and a plurality of nodes that are coupled to one another via a data bus and daisy-chained together via an add ressing line.
[0046] Fig. 3 illustrates one example of a lighting node, in accordance with various embodiments.
[0047] Fig. 4A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
[0048] Fig. 4B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 4A.
[0049] Fig. 5A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
[0050] Fig. 5B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 5A.
[0051] Fig. 6A illustrates an example method that may be performed by/with a lighting system configured with selected aspects of the present disclosure.
[0052] Fig. 6B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 6A.
Detailed Description
[0053] Cu rrently available networked lighting systems comprise a plu rality of lighting units or nodes, wherein each lighting unit drives a number of light sou rces {e.g., a plurality of LEDs). These nodes are connected together to form a network of light sou rces. I n some examples, the networked lighting systems are series-connected or daisy-chained together and use the same data link for addressing the nodes and for data communication pu rposes. A controller of cu rrently available networked lighting systems uses an automatic addressing of nodes in the daisy chain, using any number of addressing schemes and data protocols such as those discussed in U.S. Pat. No. 6,608,453 and U.S. Pat. No. 6,777,891 which are incorporated herein by reference. [0054] Referring to Fig. 1, one example of a currently available unidirectional networked lighting system 100 is described . The networked lighting system 100 includes a controller 105 and N light nodes or lighting units 101, 102, and 103. Only three nodes 101-103 are illustrated in FIG. 1, but it is u nderstood additional node(s) may be provided between the node 102 and the node 103. The multiple nodes 101-103 are powered via cou plings to voltage line 106 and grou nd line 108. The nodes 101-103 are coupled together via their commu nication ports to form a series connection of lighting u nits (e.g., a daisy-chain or ring topology), wherein each lighting unit has an input communication port and an output commu nication port. Lighting instructions/data 107 is transmitted by the controller 105 and is provided sequentially to the nodes 101-103 based on their relative positions in the series connection of nodes.
[0055] The unidirectional networked lighting system 100 can employ any number of protocols. One example of a serial-based communication protocol includes the controller of each node 101-103 in the series connection receiving data, "stripping off" or extracting one or more initial portions of the data sequence intended for it, and transmitting the remainder of the data sequence to the next node in the series connection until the topologically last node 103 is reached . For example, considering a serial interconnection of multiple channel {e.g., "R-G-B") lighting units 101-103, mu lti-bit values (one multi-bit value per channel) may be extracted by each lighting u nit from the received data seq uence. Each lighting unit 101- 103 in the series connection in turn repeats this procedu re, namely, stripping off or extracting one or more initial portions (mu lti-bit values) of a received data sequence and transmitting the remainder of the sequence. The initial portion of a data seq uence stripped off in turn by each lighting u nit 101-103 may include respective prescribed radiant powers for different available spectra of light {e.g., different color channels) capable of being generated by the lighting unit.
[0056] I n another example of a serial-based commu nication protocol, rather than stripping off an initial portion of a received data sequence, a flag is associated with each portion of a data sequence representing data for mu ltiple channels of a given lighting unit, and an entire data sequence for multiple lighting units is transmitted completely from lighting unit to lighting unit in the serial connection. As a lighting unit in the serial connection receives the data sequence, it looks for the first portion of the data seq uence in which the flag indicates that a given portion (representing one or more channels) has not yet been read by any lighting u nit. Upon finding such a portion, the lighting u nit reads and processes the portion to provide a corresponding light output, and sets the corresponding flag to indicate that the portion has been read . Again, the entire data sequence is transmitted completely from lighting unit to lighting unit, wherein the state of the flags indicate the next portion of the data sequence available for reading and processing.
[0057] The unidirectional networked lighting system 100 and each of the serial-based commu nication protocols described above may suffer from one or more disadvantages. For example, Applicants have recognized that when a node failure occurs, because the nodes are connected in only a serial configuration, the node failure disrupts data flow to other nodes that are downstream of the node failure. Also, for example, the unidirectional configu ration may not allow bi-directional communication between controller and nodes, therefore preventing commu nications from the nodes for providing operational parameters of individual nodes {e.g., temperature, LED currents, LED voltages), add ress assignment acknowledgments, etc.
[0058] Thus, Applicants have recognized and appreciated that it would be beneficial to provide methods and apparatus related to an address and data commu nication protocol that enables reliable bi-directional data-communication between a controller and lighting units or nodes and/or that provides the capability to address all the lighting units on an individual basis. For example, methods and apparatus are disclosed that utilize separate add ress and data commu nication paths to enable a robust system that provides flexibility in node add ressing and/or bi-directional commu nication between the nodes and the controller.
[0059] Fig. 2 illustrates a networked lighting system, according to one embodiment, that includes a controller 220 and a plu rality of nodes 231-233 that are coupled to one another via a data bus 215 and coupled together via a serial addressing line 213. Compared to the lighting system described in Fig. 1, the lighting system of Fig. 2 may provide one or more advantages. For example, the serial addressing line 213 used in a daisy-chain way allows for each of the nodes 231-233 to be individ ually addressable and provides further advantages in add ressing and commissioning of the nodes 231-233 in the system 200. The data bus 215, separate from the serial addressing line 213, enables a more robust and more flexible system that may be less fault prone than previously disclosed series-connected lighting systems.
[0060] The networked lighting system 200 shown in Fig. 2 comprises a plurality of nodes or lighting units including nodes 231, 232, and 233 that are coupled together to form a network. Additional nodes may be present (as evidenced by the ellipsis of Fig. 2) and connected to one another and the data bus 215 in a similar manner, but are not explicitly illustrated in Fig. 2. The nodes are daisy-chained or series-connected to each other, where node 231 is connected to node 232, which is connected to another node (illustrated by the ellipsis of Fig. 2), and that node or a further downstream node is connected to node 233. In addition, the controller 220 is also serially connected to the nodes via a direct series- connection to node 231, which is the topologically first node. In one example the controller 220 comprises a PDS (Power Data Supply). The controller 220 can provide power (via voltage line 211 and ground line 212), control data (via data bus 215), and/or address information (via addressing line 213) to the nodes 231-233. However, other controllers may be used such as controllers that provide only control data and/or address information to the nodes 231-233. For example, other controllers may provide power to the nodes 231-233 and the nodes may be powered via another source.
[0061] In some embodiments the data bus 215 from the controller 210 comprises a differential data bus providing both a data input channel and a data output channel. In other embodiments, a channel may be used for both data input and data output. The data bus 215 is connected in parallel to the nodes 231-233. In one example, the controller 220 may be configured to interpret lighting instructions/data that are received in an Ethernet protocol (or similar protocol based on Ethernet concepts) from a computing device such as a personal computer (PC) and provide the data via the data output channel of the data bus 215 to effectuate lighting changes and/or other changes from the nodes 231-233. The controller 220 can also receive feedback from the nodes 231-233 via the data bus 215 such as feedback information based on measured values of sensors o the nodes 231-233. In other examples, the controller 220 and the data bus 215 may be DMX enabled.
[0062] In addition, the lighting system 200 includes an addressing line 213 that is separate from the data bus 215. The addressing line 213 connects each of the nodes 231- 233 in a series-connection and comprises a portion that connects controller 220 to an address input connection of node 231, a portion that connects between an address output of node 231 and an address input of node 232, a portion that connects between an address output of node 232 and an address input of a downstream node (not illustrated), and a portion between an address output of that or another downstream node and an address input of node 233. The addressing line 213 facilitates automatic node discovery and commissioning, using one or more techniques described below with reference to Fig. 4-7.
[0063] The use of the data bus 215 and the separate addressing line 213 improves robustness against node failure, as well as interconnect and cabling failure. For example, if one of the nodes 231-233 fails in the daisy chain, the data communication via the data bus 215 is not interrupted. Further, the bi-directional nature of the data bus 215 allows bidirectional communication for transmitting control signals from the controller 220 to the nodes 231-233 and transmitting performance data and/or other data from the nodes 231- 233 to the controller 220.
[0064] Fig. 3 illustrates one of the nodes 231 of the lighting system 200 in further detail. In some embodiments, all or aspects of the node 231 can be realized as an application- specific integrated circuit (ASIC). The node 231 comprises a DC/DC conversion circuit 2312 and LED drivers 2313R, G, B, A, W for corresponding colors of LEDs 201R, G, B, A, W.
Although the 5 LED drivers ("RGBAW" drivers) are shown, the number of channels and drive capability can be modified. The node 231 further comprises a node controller 2320 and memory 2322. As described in more detail herein, the node controller 2320 may determine a communication address for the node 231 based on input received via data communication connection 2330 and/or address input connection 2342. The node controller 2320 may further assign the communication address in memory 2332 and may transmit information over the address output connection 2344 to effectuate assigning of communication address by one or more other nodes connected serially downstream of the node 231 on an addressing line. The node controller 2320 may also receive sensor values from thermistor 2315 and/or other sensors of the node 231 and transmit, via the data communication connection 2330, operational feedback information that is indicative of the sensor values (and optionally indicative of other values).
[0065] The DC-DC conversion circuit 2312 in the node 231 may enable higher operation voltage thereby allowing the use of thinner power cables and/or accommodation of more nodes, which may lead to an increase in LED current, such as >100mA per channel for high brightness LEDs and a relatively high supply voltage, such as > 50V. The DC-DC conversion circuit 2312 may down-convert the high voltage bus supply received over lines 211/212 (Fig. 2). Two independent output voltages (Voutl and Vout2) are generated by the DC-DC conversion circuit 2312 to connect to the Red and Amber LEDs 201R, A (Vout2) and Green, Blue, and White LEDs 201G, B, W (Voutl). The output voltages can be chosen such, depending on the number of LEDS, that the voltage conversion is as efficient as possible. The node 231 also contains a voltage regulator 2311 and band gap circuits 2314 to generate voltages to be used in the analog and digital domain of the circuit blocks in the architecture.
[0066] As described above, the node 231 includes a data communication connection 2330, an address input connection 2342, and an address output connection 2344. The data communication connection 2330 may receive control data, including control data that is addressed to the node 231 and the node controller 2320 may adjust the output of one or more of the drivers 2313R, A, B, G, W and/or other components based on the control data that is addressed to the node 231. For example, the control data may include parameters that prescribe radiant powers for different available spectra of light (e.g., different color channels) capable of being generated by the LEDs 201R, A, B, G, W, and the node controller 2320 may adjust one or more drivers and/or other components to achieve the prescribed radiant powers. The node controller 2320 may compare an address associated with control data to a commissioned communication address stored in memory 2322 to identify the control data that is directed to the node 231.
[0067] The node controller 2320 may also transmit operational feedback information over the data communication connection 2330. For example, the node controller 2320 may transmit the operational feedback information with the communication address of the node 231 or other identifier that enables the controller 220 to identify the information originates from the node 231. This node specific operational feedback information can be used for real-time status diagnostic reporting such as, for example, temperature, LED currents, and/or LED voltages. The controller 220 may optionally utilize the operational feedback information from one or more nodes to alter control data provided to one or more nodes 231-233 to, for example, perform LED color correction and/or color compensation. [0068] The networked lighting system 200 described above may utilize one or more address commissioning and/or data communication techniques to enable one or more of its functionalities. Figs. 4A-6B describe some examples of address commissioning techniques that assign communication addresses to the nodes 231-233 in the lighting system 200 via utilization of the addressing line 213. The techniques described provide address
information in a daisy chain manner from controller 220 to node 231 until node 233 to facilitate address commissioning. Once commissioned, the nodes 231-233 in the networked lighting system 200 each have a communication address or identification number stored in memory, which can be used to address control data that is communicated by the controller 220 to one or more of the nodes 231-233 via the data bus 215. For example, control data may be sent by the controller 220 that is addressed only to one of the nodes 231. Also, for example, control data may be sent by the controller 220 that includes a first portion addressed to the node 231 and a second portion addressed to the node 232. After some embodiments of commissioning, each of the nodes in the networked lighting system 200 has a communication address that is unique from the communication address of any other of the nodes in the networked lighting system 200. In some embodiments two or more nodes may optionally share the same address such that they each act on the same control data and respond in an identical fashion.
[0069] In various embodiments, the nodes 231-233 are each assigned a unique serial number during manufacture/assembly and the serial number of a given node is stored in memory of the node. Besides this serial number, each of the nodes 231-233 may have other data stored in memory during manufacture such as, for example, color calibration data based on optical measuring of light output from the light source(s) of the node. As the networked lighting system 200 is installed, the nodes 231-233 are commissioned. The commissioning process enables the controller 220 to determine a communication address for each node in the lighting system 200 and optionally enables the controller 220 to store an association between the unique serial numbers and the communication addresses of the nodes and/or the color calibration data and the communication addresses of the nodes. In some embodiments, the serial number of a node may be a 64-bit unique number assigned to the node at assembly and stored in the memory of the node and the communication address may be a 16-bit address associated with the node according to techniques described herein. However, it is appreciated that other address and serial number sizes may be used . There are several implementation options to address commissioning between the controller and the nodes as described below with reference to Figs. 4A-6B. These methods use both the add ressing line 213 and the parallel data bus 215 in the commissioning.
[0070] Fig. 4A illustrates a method 400 of commissioning according to one embodiment. I n summary, method 400 comprises use of a token or a flag that is serially communicated via the add ressing line to the topologically first node. The token is then commu nicated serially via the addressing line to the subsequent nodes, one node at a time. As the token is received by each node, each node assigns an add ress and communicates the add ress to the controller via the data bus. By sequentially receiving acknowledgement from each node, the controller determines the position of each commu nication address in the node chain {e.g., the first acknowledgment corresponds to the topologically closest node and the last acknowledgment corresponds to the topologically farthest node).
[0071] At block 402, a controller transmits a non-active token to the address input of a topologically first node. For example, the controller 220 may transmit a non-active token to the add ress input of node 231. I n some embodiments the non-active token may be a logic "low" such as a voltage that is less than a threshold. In other embodiments alternative non- active tokens may be utilized such as a logic "high" or a series of bits or other informational packet.
[0072] At block 404, the controller broadcasts a request for node discovery via the data bus. The nodes receive the request, causing the nodes to set a non-active token on their add ress output connections and to wait for their address input connections to go active before assigning themselves a communication address. For example, the controller 220 broadcasts, and the nodes 231-233 receive, a request for node discovery on the data bus 215. The nodes 231-233 receive the request and, responsive to the request, set a non-active token {e.g., a logic "low") on their add ress output connections and wait for their address input connections to go active {e.g., a logic "high").
[0073] At block 406, the controller transmits an active token to the topologically first node. For example, where the active token is a logic "high" such as a voltage that is greater than a threshold, the controller 220 may provide output that sets the add ressing line 213 extending between the controller 220 and the address input connection of the node 231 to "high."
[0074] At block 408, in response to receiving the active token, the topologically first node determines and stores a communication address, and transmits an acknowledgment to the controller via the data bus. For example, the controller of the node 231 may identify receipt of the token, generate an address for the node, and store the address in the memory of the node. The node 231 may also acknowledge to controller 220 over the parallel data bus 215 that the communication address of the node 231 has been set, for example, by sending the serial number of the node 231 and optionally the assigned communication address. In some embodiments, the topologically first node determines the communication address based on the request for node discovery of block 404. For example, the request may have included the communication address to be used by the next node that receives the active token, and the node 231 may have buffered the communication address as a potential address and assigned the buffered communication address as an actual address in response to receiving the active token.
[0075] At block 410, the controller broadcasts a request for the next node via the data bus. For example, once the acknowledgement is received from the node that most recently assigned a communication address (node 231 in the first iteration), the controller 220 broadcasts, and the nodes receive, a request for node discovery via the data bus 215.
[0076] At block 412, the node that most recently transmitted the acknowledgement (node 231 in the first iteration) transmits the active token to the topologically next node. For example, in the first iteration and where the active token is a logic "high", node 231 may set its address output to "high" to transmit the active token to the address input of node 232.
[0077] At block 414, in response to receiving the active token, the topologically next node determines and stores a communication address, and transmits an acknowledgment to the controller via the data bus. For example, a controller of the node 232 may receive the token, generate an address for the node 232, and store the address in the memory of the node 232. The node 232 may also acknowledge to controller 220 over the parallel data bus 215 that the communication address of the node 232 has been set, for example, by sending the serial number of the node 232 and optionally the assigned communication address. In some embodiments, the topologically next node determines the communication address based on the most recent request for next node discovery of block 410. For example, the request may have included the communication address to be used by the next node that receives the active token, the topologically next node may have buffered the communication address as a potential address (and cleared out any preceding potential addresses), and assigned the buffered commu nication address as an actual address in response to receiving the active token. As described herein, in some embodiments each communication address buffered and used as an actual add ress in response to receiving the active token may be u niq ue from any other commu nication addresses assigned to other nodes in the lighting network. In other embodiments, the controller 220 may provide requests for node discovery such that multiple nodes will have the same communication add ress when they receive the active token and the mu ltiple nodes will all assign the same communication address and respond to the same control data addressed to that communication address. For example, a first communication address may be assigned to each of the first five nodes, a second
communication address assigned to each of the next ten nodes, etc.
[0078] I n some embodiments, each of the acknowledgments sent to the controller 220 {e.g., at blocks 408 and 414) may include the determined communication address and/or an assigned serial nu mber of the node that is transmitting the acknowledgment. The controller 220 may utilize the serial nu mbers and communication addresses to create a data structure that defines relationships between the communication addresses and serial numbers. This may be beneficial for various pu rposes such as, for example, determining the serial number of a node that may suffer a futu re communication failure - and providing the serial number to a user to enable the user to identify and replace the node.
[0079] At block 416 the controller determines whether all nodes are add ressed . If not, steps in blocks 410, 412, and 414 are repeated until all nodes or the N nodes in the chain are add ressed . If all nodes are addressed, commissioning ends at block 418 and control data may be addressed to the nodes via the data bus based on the communication addresses determined via the method 400 of FIG. 4. In some embodiments, the controller 220 may know the total nu mber of nodes {e.g., based on input from a user) and the controller 220 may determine all nodes are addressed by determining the nu mber of acknowledgments equals the total number of nodes. In some embodiments the controller 220 may determine all nodes are addressed based on not receiving an acknowledgement within a time out period of the last iteration of block 410. For example, after the last node N receives the token and the address is communicated to the controller, there is a timeout for the subsequent node to reply with the address. The controller may associate this time out with addressing all the nodes in the chain.
[0080] Fig. 4B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 4A. For ease in explanation, the communication interactions of Fig. 4B are described with reference to corresponding blocks in Fig. 4A, and the communication interactions of Fig. 4B are labeled with the corresponding blocks of Fig. 4A (in parentheses in Fig. 4B).
[0081] In Fig. 4B the controller 220 sends a non-active token to an address input of node 231 at block 402. The controller 220 sends a request for node discovery to the data bus 215 at block 404 and the node 231 sends a non-active token to an address input of the node 232 in response to receiving (via the data bus 215) the request for node discovery at block 404.
[0082] The controller 220 sends an active token to node 231 at block 406 of Fig. 4A. The node 231 determines and assigns a communication address based on receiving the active token and sends an acknowledgment of assignment of the address to the data bus 215 at block 408. The controller sends a request for the next node to the data bus 215 at block 410 and the node 231 sends an active token to the node 232 at block 412. The node 232 determines and assigns a communication address based on receiving the active token and sends an acknowledgment of assignment of the address to the data bus 215 at block 414. The controller sends a request for the next node to the data bus 215 at block 410. Although not illustrated in FIG. 4B, the node 232 would send an active token to the topologically next node and further communications would result between the various components until all nodes are addressed and commissioning ends.
[0083] Fig. 5A illustrates a method 500 of commissioning according to another embodiment. In summary, method 500 comprises a controller sending a token to the topologically first node, wherein the token indicates a communication address for the first node to assign to itself. The first node assigns itself a communication address based on the token, adjusts the token according to an adjustment protocol, and sends the adjusted token to the next node via the addressing line, where the process is repeated. The first node and subsequent nodes may each send an acknowledgment to the controller prior to transmitting the adjusted token to a topologically next node. [0084] At block 502, a controller transmits a non-active token to the address input of a topologically first node. For example, the controller 220 may transmit a non-active token to the add ress input of node 231. I n some embodiments the non-active token may be a logic "low" such as a voltage that is less than a threshold. In other embodiments alternative non- active tokens may be utilized.
[0085] At block 504, the controller broadcasts a request for node discovery via the data bus. The nodes receive the request, causing the nodes to set the non-active token on their add ress output connection. For example, the controller 220 broadcasts, and the nodes 231- 233 receive, a request for node discovery on the data bus 215. The nodes 231-233 receive the request and, responsive to the request, set a non-active token {e.g., a logic "low") on their add ress output connections and wait for their add ress input connections to go active {e.g., a logic "high").
[0086] At block 506, the controller transmits a commu nication add ress to the address input of the topologically first node. For example, the controller 220 sends "Address 1" to the first node 231 using the add ressing line 213.
[0087] At block 508, in response to receiving the communication add ress, the
topologically first node stores the communication address in memory as its address, and transmits an acknowledgment to the controller via the data bus. For example, the node 231 assigns Add ress 1 to itself and stores the add ress in the memory. The node 231 sends acknowledgement to the controller 220 over the data bus. For example, the node 231 may send acknowledgement, by sending the serial number of the node 231 and optionally the assigned communication address.
[0088] At block 510, the node that most recently stored the communication address as its add ress (the topologically first node in the first iteration) adjusts the communication add ress according to an adjustment protocol and transmits the adjusted commu nication add ress to the topologically next node via the add ressing line. In some embodiments adjusting the communication add ress according to the adjustment protocol comprises incrementing the communication address by a fixed amou nt such as by one or two. Other adjustment protocols may be utilized such as those that decrement and/or those that adjust commu nication addresses in a non-linear fashion. Also, in some embodiments the commu nication address may not be adjusted at every node and/or may otherwise be adjusted such that two or more nodes may share the same communication address. For example, in embodiments where it is desirable for two or more nodes to share the same add ress, the commu nication address may only be adjusted at every nth node {e.g., with nodes keeping track of acknowledgments to count nodes).
[0089] At block 512, in response to receiving the adjusted communication address, the topologically next node stores the adjusted communication address as its address, and transmits an acknowledgment to the controller via the data bus. For example, the node 232 assigns the adjusted communication address to itself and stores the address in the memory. The node 232 sends acknowledgement to the controller 220 over the parallel data bus. For example, the node 232 may send acknowledgement for example, by sending the serial nu mber of the node 232 and optionally the assigned commu nication address.
[0090] At block 514 the controller determines whether all nodes are add ressed . If not, steps in blocks 510 and 512 are repeated u ntil all nodes or the N nodes in the chain are add ressed . If all nodes are addressed, commissioning ends at block 516 and control data may thereafter be addressed to the nodes based on the communication add resses determined via the method 500 of FIG. 5. In some embodiments, the controller 220 may know the total nu mber of nodes {e.g., based on input from a user) and the controller 220 may determine all nodes are addressed by determining the nu mber of acknowledgments equals the total number of nodes. For example, the total nu mber of nodes may be pre-set by a user. In some embodiments the controller 220 may determine all nodes are addressed based on not receiving an acknowledgement within a time out period of receiving an acknowledgment in the last iteration of block 512.
[0091] I n some embodiments, each of the acknowledgments sent to the controller 220 {e.g., at blocks 508 and 512) may include the determined communication address and an assigned serial nu mber of the node that is transmitting the acknowledgment. The controller 220 may utilize the serial nu mber and commu nication addresses to create a data structure that defines relationships between the node address and serial numbers.
[0092] Fig. 5B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 5A. For ease in explanation, the commu nication interactions of Fig. 5B are described with reference to corresponding blocks in Fig. 5A, and the commu nication interactions of Fig. 5B are labeled with the corresponding blocks of Fig. 5A (in parentheses in Fig. 5B). [0093] In Fig. 5B the controller 220 sends a non-active token to the address input of node 231 at block 502. The controller 220 sends a request for node discovery to the data bus 215 at block 504 and the node 231 sends a non-active token to the node 232 at block 504 in response to receiving (via the data bus 215) the request for node discovery.
[0094] The controller 220 sends a communication address to the address input of node 231 at block 506. The node 231 assigns a communication address based on the received communication address and sends an acknowledgment of assignment of the address to the data bus 215 at block 508. The node 231 determines an adjusted communication address based on an adjustment protocol and sends the adjusted communication address to the node 232 at block 510. The node 232 assigns a communication address based on the received adjusted communication address and sends an acknowledgment of assignment of the address to the data bus 215 at block 508 of Fig. 5A. Although not illustrated in FIG. 5B, the node 232 would determine a further adjusted communication address and send it to the topologically next node at block 510 and further communications would result between the various components until all nodes are addressed and commissioning ends.
[0095] Fig. 6A illustrates a method 600 of commissioning according to another embodiment. In summary, method 600 is similar to method 500, but includes additional verification, by the nodes, of the addresses communicated via the addressing line based on comparing the address communicated via the addressing line to address setting information sent over the data bus.
[0096] At block 602, the controller sends a "clear last token" message to all nodes over the data bus and all nodes clear any tokens they have stored in their token register. At block 604, the controller broadcasts an "Address = X + Node Enable" token to the address input of the topologically first node. For example, the controller 220 send the token to the first node 231 in the chain using the addressing line 213.
[0097] At block 606, the controller sends an "If No Address Set Then Node Address = X" message to all nodes over the data bus. At block 608, the topologically first node has possession of both an "Address = X + Enable" token via the addressing line 213 and the "If No Address Set Node Address = X" message via the data bus 215. All other nodes have the "If No Address Set Address Message = X" via the data bus 215, but do not have the "Address = X + Enable". Thus, all nodes except the topologically first node perform no further action. At block 608, the topologically first node compares the token received via the addressing line 213 and the message received via the data bus 215, determines they match, and assigns itself a communication address of X based on them matching. The topologically first node further sends acknowledgement to the controller via the data bus 215.
[0098] At block 610, the node that most recently stored the communication address as its address (the topologically first node in the first iteration) adjusts the communication address according to an adjustment protocol and transmits the adjusted communication address to the topologically next node via the addressing line. In some embodiments adjusting the communication address according to the adjustment protocol comprises incrementing the communication address by a fixed amount such as by one or two. Other adjustment protocols may be utilized such as those that decrement and/or those that adjust communication addresses in a non-linear fashion.
[0099] At block 612, the controller sends and the nodes receive a "If No Address Set Then Node Address = Adjusted Communication Address" message to all nodes via the data bus. The "Adjusted Communication Address" of the message will match the adjusted communication address transmitted via the addressing line at block 610. As described herein, in some embodiments the adjustment protocol may be implemented such that two or more nodes have the same communication address at the end of commissioning.
[00100] At block 614, the topologically next node has possession of both an "Adjusted Communication Address" token via the addressing line 213 and the "If No Address Set Then Node Address = Adjusted Communication Address" message via the data bus 215. All other nodes do not have the Adjusted Communication Address" token via the addressing line 213. Thus, all nodes except the topologically next node perform no further action. At block 616, the topologically next node compares the token received via the addressing line 213 and the message received via the data bus 215, determines they match, and assigns itself the adjusted communication address based on them matching. The topologically first node further sends acknowledgement to the controller via the data bus 215.
[00101] Block 616 ensures that steps in blocks 610, 612, and 614 are repeated until all nodes are covered. As described above, the user either user tells the controller the total number of nodes in the string OR there is a timeout for the last node to reply with and Address. At block 620, the controller broadcasts a "clear last token" message to all nodes over the data bus and the nodes clear tokens in response to receiving the message. The controller may then create node address to serial-number association table.
[00102] Fig. 6B illustrates an example of communication interactions between various components of the example lighting system of Fig. 2 that may occur according to the example method of Fig. 6A. For ease in explanation, the communication interactions of Fig. 6B are described with reference to corresponding blocks in Fig. 6A, and the communication interactions of Fig. 6B are labeled with the corresponding blocks of Fig. 6A (in parentheses in Fig. 6B).
[00103] In Fig. 6B the controller 220 sends a clear last token message to the all of the nodes via the data bus 215 at block 602. The controller 220 sends an "Address = X + Node enable" token to the address input of node 231 at block 604. The controller 220 sends an "If No Address Set Then Node Address = X" message to all nodes over the data bus 215 at block 606 of Fig. 6A.
[00104] The node 231 assigns a communication address of "X" based on the token received via the addressing line 213 and the message received via the data bus 215 matching one another. The node 231 sends an acknowledgment of assignment of the address to the data bus 215 at block 608. The node 231 determines an adjusted
communication address of "X+l" based on an adjustment protocol and sends the adjusted communication address with a node enable to the node 232 at block 610.
[00105] The controller 220 sends an "If No Address Set Then Node Address = X + 1" message to all nodes via the data bus 615 at block 612. The "X + 1" of the message matches the adjusted communication address transmitted from node 231 to node 232 via the addressing line 213. The node 232 has possession of a token received via the addressing line 213 that matches a message received via the data bus 215. The node 232 determines they match, assigns itself the adjusted communication address based on them matching, and sends acknowledgement to the controller via the data bus 215 at block 614. Although not illustrated in FIG. 6B, the node 232 would determine a further adjusted communication address and send it to the topologically next node and further communications would result between the various components until all nodes are addressed and commissioning ends. [00106] Yet another embodiment of a method of commissioning is similar to method 600 except the Token (sent via the addressing line 213) forms a key/dehashing function to decode the address setting message sent via the data bus 215. Unless a node has possession of a token received via the addressing line 213 that decodes a message received via the data bus 215, the node will not carry out any actions and will clear its token and message registers. If a node has possession of a token received via the addressing line 213 that decodes a message received via the data bus 215, the address of the decoded message may be utilized as the communication address for the node (and adjusted and sent to an address input of a topologically next node in a similar manner as described with respect to Fig. 6A). In embodiments of this approach, a specific "clear token register" message is not needed, but token and message pairs must be chosen to ensure that all non-matching message-token pairs decode to a "clear all registers" result.
[00107] In some embodiments the system and the protocols described enable node fault detection when the networking system suffers from node failure or electrical contact/cable failure. In one embodiment, the controller 220 can perform node fault detection by comparing the number of discovered nodes and the number expected by the application. Fault localization is possible as the node following the last discovered addressed is where the problem begins. If the fault is an electrical contact on the addressing line, the nodes can still be operated since they have their address stored locally on memory at initial configuration.
[00108] During field replacement of broken nodes (after initial commissioning) when the addressing line daisy-chain connection 213 is broken, replacement should be performed one-at-a time using an emergency address setting protocol that only makes use of the data bus 215. For example, maintenance personnel may remove the topologically closest broken node from the string and replace the node with a new working replacement. The new node would not be assigned an address. The controller 220 can put the networked lighting system 200 into an address Checking Mode using an Emergency Address Setting Protocol. The controller 220 can generate a Node Address and corresponding Serial Number routing table by sending series of Address Request Messages on the parallel data bus to the nodes in the system. Each of the nodes 231-233 would subsequently receive the messages and respond with a corresponding stored node address and serial number associated with the node. The node address stored corresponds to the communication address determined using one of the commissioning protocols described above. If the controller 220 does not receive a response to such a message within a timeout period, the controller moves on to the next expected address in the sequence.
[00109] Based on the table of addresses and serial numbers, the controller 220
determines missing or nonconsecutive Address numbers (those for which no response to the Address Request Message was received). The first such missing address is defined as a specific address (for example Address Y). The controller 220 can then send a message on the parallel data bus 215 to all nodes assigning the node without an address with the specific address (address Y). The controller 220 can then inform the maintenance personnel to remove the topologically next broken node from the string and replace it with a working replacement (currently not assigned an Address number). The controller 220 can then send a message on the data bus to all nodes assigning the node without an address with topologically next missing address. This process can repeat until all nodes are replaced, one at a time. The maintenance personnel can confirm all broken nodes are replaced.
[00110] While several inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.
[00111] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.
[00112] The indefinite articles "a" and "an," as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean "at least one."
[00113] The phrase "and/or," as used herein in the specification and in the claims, should be understood to mean "either or both" of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with "and/or" should be construed in the same fashion, i.e., "one or more" of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the "and/or" clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to "A and/or B", when used in conjunction with open-ended language such as "comprising" can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.
[00114] As used herein in the specification and in the claims, "or" should be understood to have the same meaning as "and/or" as defined above. For example, when separating items in a list, "or" or "and/or" shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as "only one of" or "exactly one of," or, when used in the claims, "consisting of," will refer to the inclusion of exactly one element of a number or list of elements. In general, the term "or" as used herein shall only be interpreted as indicating exclusive alternatives (i.e. "one or the other but not both") when preceded by terms of exclusivity, such as "either," "one of," "only one of," or "exactly one of." "Consisting essentially of," when used in the claims, shall have its ordinary meaning as used in the field of patent law. [00115] As used herein in the specification and in the claims, the phrase "at least one," in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase "at least one" refers, whether related or unrelated to those elements specifically identified. Thus, as a non- limiting example, "at least one of A and B" (or, equivalently, "at least one of A or B," or, equivalently "at least one of A and/or B") can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.
[00116] It should also be understood that, unless clearly indicated to the contrary, in any methods claimed herein that include more than one step or act, the order of the steps or acts of the method is not necessarily limited to the order in which the steps or acts of the method are recited.
[00117] In the claims, as well as in the specification above, all transitional phrases such as "comprising," "including," "carrying," "having," "containing," "involving," "holding," "composed of," and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases "consisting of" and "consisting essentially of" shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03.

Claims

1. A lighting system, comprising:
a plurality of nodes (231-233) each including a node controller, memory, a data communication connection, an address input connection, and an address output connection, wherein at least one node of the plurality of nodes is coupled to and controls at least one LED light source (201R, A, B, G, W);
wherein the data communication connections of the nodes are all coupled to a data bus and wherein the nodes are coupled in series via the address input connections and the address output connections;
a controller (220) coupled to the nodes via the data bus and coupled to the address input connection of a first node of the nodes;
wherein the controller is configured to transmit address information to the address input connection of the first node;
wherein the node controller of the first node is configured to assign itself a communication address based on receiving the address information, wherein the node controller stores the communication address in the memory of the first node and wherein the node controller is further configured to transmit information over the address output connection of the first node to effectuate assigning of communication addresses by other of the nodes;
wherein the controller is further configured to broadcast control data to the plurality of nodes via the data bus, the control data addressed to one or more of the nodes based on respective of the communication addresses assigned by the nodes.
2. The lighting system of claim 1, wherein the control data comprises first control data addressed to the at least one node, the first control data comprising one or more control parameters for control of the at least one LED light source of the at least one node.
3. The lighting system of claim 2, wherein the at least one LED light source includes at least one red LED light source, at least one green LED light source, and at least one blue LED light source and the at least one node controls the at least one red LED light source, the at least one green LED light source, and the at least one blue LED light source, based on the control parameters.
4. The lighting system of claim 1, wherein the controller is further configured to receive operational feedback information from the plurality of nodes via the data bus.
5. The lighting system of claim 1, wherein the address information comprises the communication address and wherein the node controller of the first node is further configured to adjust the communication address according to a fixed adjustment protocol to create an adjusted communication address, and wherein the information transmitted over the output connection of the first node comprises the adjusted communication address.
6. The lighting system of claim 5, wherein the first node is configured to transmit an acknowledgement of assignment of the communication address to the controller via the data bus and transmit the adjusted communication address following the transmission of the acknowledgement of assignment of the communication address.
7. The lighting system of claim 1, wherein the address information comprises an active token, wherein the first node is configured to assign itself the communication address based on receiving the active token, and wherein the information transmitted over the address output connection comprises the active token.
8. The lighting system of claim 7, wherein the first node is configured to assign a communication address of the first node based on:
receiving the address information,
receiving address setting information via the data communication connection of the first node, and
comparing the address information to the address setting information.
9. The lighting system of claim 7, wherein the first node is configured to transmit an acknowledgement of assignment of the communication address to the controller via the data bus and transmit the active token over the output connection following the
transmission of the acknowledgement of assignment of the communication address.
10. The lighting system of claim 9, wherein the acknowledgement of assignment of the communication address to the controller comprises a serial number of the first node and wherein the controller is further configured to store an association between the serial number and the communication address.
11. The lighting system of claim 1, wherein the first node is configured to transmit an acknowledgement of assignment of the communication address to the controller via the data bus and transmit the information over the address output connection of the first node following transmission of the acknowledgement of assignment of the communication address.
12. The lighting system of claim 11, wherein the acknowledgement of assignment of the communication address to the controller comprises a serial number of the first node and wherein the controller is further configured to store an association between the serial number and the communication address.
13. A method, comprising:
receiving address information at a serially connected address input connection of a node, the node coupled to and controlling at least one LED light source;
determining, by at least one controller of the node, a communication address based on receiving the address information;
storing the communication address in memory of the node;
receiving control data at a data bus connected data communication connection of the node;
determining, by the controller, that at least a portion of the control data is addressed to the communication address in the memory of the node; and
adjusting at least one light output parameter of the LED light source based on the portion of the control data, the adjusting in response to determining that the portion of the control data is addressed to the communication address.
14. The method of claim 13, further comprising:
receiving values from one or more sensors of the node; and
transmitting, via the data communication connection of the node, operational feedback information indicative of the values.
15. The method of claim 13, further comprising transmitting information over an address output connection of the node to effectuate assigning of communication addresses by an additional node serially connected to the node via the address output connection.
16. The method of claim 15, wherein the address information comprises the communication address, and further comprising:
adjusting the communication address according to a fixed adjustment protocol to create an adjusted communication address, and wherein the information transmitted via the address output connection comprises the adjusted communication address.
17. The method of claim 16, further comprising:
transmitting an acknowledgement of assignment of the communication address via the data bus;
wherein transmitting the adjusted communication address occurs after transmitting the acknowledgement of assignment of the communication address.
18. The method of claim 15, wherein the address information comprises an active token and wherein the information transmitted over the address output connection comprises the active token.
19. The method of claim 18, further comprising:
transmitting an acknowledgement of assignment of the communication address via the data bus;
wherein transmitting the active token occurs after transmitting the
acknowledgement of assignment of the communication address.
20. The method of claim 15, further comprising:
transmitting an acknowledgement of assignment of the communication address via the data bus;
wherein transmitting the information over the address output connection of the node occurs after transmitting the acknowledgement of assignment of the communication address.
21. The method of claim 20, wherein the acknowledgement of assignment of the communication address to the controller comprises a serial number stored in memory of the node and comprises the communication address.
22. A method, comprising:
broadcasting node discovery information to a plurality of nodes via a bus connection to the plurality of nodes, the nodes including at least one node that is coupled to and controls at least one LED light source;
transmitting address information to an address input connection of a first node of the nodes without transmitting the address information to any other of the nodes, the address information configured to cause the first node to assign itself a communication address based on receiving the address information; and
broadcasting control data to the plurality of nodes via the bus connection, the control data comprising first node control data addressed to the first node based on the communication address of the first node.
23. The method of claim 22, wherein the address information is an active token.
24. The method of claim 23, further comprising:
receiving an acknowledgement of assignment of the communication address via the bus connection;
broadcasting, to the plurality of nodes via the bus connection and in response to receiving the acknowledgment of assignment of the communication address, a request for discovery of the next node.
25. The method of claim 22, further comprising:
receiving an acknowledgement of assignment of the communication address via the bus connection; and
generating the first node control data based on receiving the acknowledgment of assignment of the communication address.
26. The method of claim 22, wherein the node discovery information comprises address setting information that matches the address information.
27. The method of claim 26, wherein the address information forms a key that decodes the address setting information.
28. The method of claim 26, wherein the address information and the address setting information are an exact match.
29. The method of claim 22, further comprising:
receiving from the first node an acknowledgement of assignment of the
communication address via the bus connection, the acknowledgment of assignment of the communication address comprising a serial number of the first node; and
storing in memory an association between the communication address and the serial number.
30. A method, comprising:
accessing a data structure that defines communication addresses of nodes coupled to a bus connection, the nodes including at least one node that is coupled to and controls at least one LED light source;
broadcasting, for each of the communication addresses, an address request message to the nodes via the bus connection, the address request message for a communication address of the communication addresses being configured to solicit a confirmatory response from a node of the nodes that has the communication address;
monitoring the bus connection for the confirmatory response to each of the address request messages; determining a missing communication address associated with the address request message of the topologically closest node that failed to provide the confirmatory response in response to the address request message;
broadcasting a command to the nodes via the bus connection, the command configured to cause any node that does not have a communication address assigned to assign the missing communication address.
31. An apparatus for use in commissioning and controlling a plurality of nodes, the nodes each including a connection for coupling to a data bus and a separate connection for a daisy-chain connection of the nodes, at least one node of the nodes coupled to an controlling at least one LED light source, the apparatus comprising:
a data bus connection to couple to the data bus;
an addressing connection to couple to a first node of the nodes ;
memory storing instructions;
a controller operable to execute the instructions stored in the memory, wherein execution of the instructions by the controller causes the controller to:
broadcast node discovery information to the plurality of nodes via the bus connection,
transmit address information to the first node of the nodes via the addressing connection without transmitting the address information to any other of the nodes, the address information configured to cause the first node to assign itself a communication address based on receiving the address information, and
broadcast control data to the plurality of nodes via the bus connection, the control data comprising first node control data addressed to the first node based on the communication address of the first node.
32. An LED-based lighting unit (231, 232, 233), comprising:
a data communication connection (2330);
an address input connection (2342);
an address output connection (2344);
at least one LED light source (201R, A, B, G, W);
memory (2322); and a controller (2320) configured to:
receive address information at the address input connection,
determine a communication address based on receiving the address information,
store the communication address in the memory,
receive control data at a data communication connection of the node, determine that at least a portion of the control data is addressed to the communication address in the memory, and
adjust at least one light output parameter of the LED light source based on the portion of the control data, the adjusting in response to determining that the portion of the control data is addressed to the communication address.
PCT/IB2015/058958 2014-11-25 2015-11-19 Lighting control apparatus and methods WO2016083954A2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201462084243P 2014-11-25 2014-11-25
US62/084,243 2014-11-25
US201562148433P 2015-04-16 2015-04-16
US62/148,433 2015-04-16

Publications (2)

Publication Number Publication Date
WO2016083954A2 true WO2016083954A2 (en) 2016-06-02
WO2016083954A3 WO2016083954A3 (en) 2016-10-13

Family

ID=54705244

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2015/058958 WO2016083954A2 (en) 2014-11-25 2015-11-19 Lighting control apparatus and methods

Country Status (1)

Country Link
WO (1) WO2016083954A2 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018162313A1 (en) 2017-03-09 2018-09-13 Philips Lighting Holding B.V. Device, system, and method for determining an address of a component arranged in a structure
CN109379812A (en) * 2018-11-26 2019-02-22 无锡德芯微电子有限公司 LED autocoding address circuit and coding method
US10667369B2 (en) 2017-03-09 2020-05-26 Signify Holding B.V. Device, system, and method for determining an address of a component arranged in a structure
CN112929282A (en) * 2019-12-06 2021-06-08 西安诺瓦星云科技股份有限公司 Display control card topological relation identification method and LED display control system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6016038A (en) 1997-08-26 2000-01-18 Color Kinetics, Inc. Multicolored LED lighting method and apparatus
US6211626B1 (en) 1997-08-26 2001-04-03 Color Kinetics, Incorporated Illumination components
US6608453B2 (en) 1997-08-26 2003-08-19 Color Kinetics Incorporated Methods and apparatus for controlling devices in a networked lighting system
US6777891B2 (en) 1997-08-26 2004-08-17 Color Kinetics, Incorporated Methods and apparatus for controlling devices in a networked lighting system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070260764A1 (en) * 2006-04-10 2007-11-08 Honeywell International Inc. Semi-automatic token generated addressing
DE102007044817A1 (en) * 2007-09-20 2009-04-09 Insta Elektro Gmbh Method for configuring a lighting bus system
TW200950578A (en) * 2008-05-23 2009-12-01 Semisilicon Technology Corp Parallel-type single-line addressing lamp apparatus

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6016038A (en) 1997-08-26 2000-01-18 Color Kinetics, Inc. Multicolored LED lighting method and apparatus
US6211626B1 (en) 1997-08-26 2001-04-03 Color Kinetics, Incorporated Illumination components
US6608453B2 (en) 1997-08-26 2003-08-19 Color Kinetics Incorporated Methods and apparatus for controlling devices in a networked lighting system
US6777891B2 (en) 1997-08-26 2004-08-17 Color Kinetics, Incorporated Methods and apparatus for controlling devices in a networked lighting system

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018162313A1 (en) 2017-03-09 2018-09-13 Philips Lighting Holding B.V. Device, system, and method for determining an address of a component arranged in a structure
US10667369B2 (en) 2017-03-09 2020-05-26 Signify Holding B.V. Device, system, and method for determining an address of a component arranged in a structure
CN109379812A (en) * 2018-11-26 2019-02-22 无锡德芯微电子有限公司 LED autocoding address circuit and coding method
CN109379812B (en) * 2018-11-26 2024-02-27 无锡德芯微电子有限公司 LED automatic coding address circuit and coding method
CN112929282A (en) * 2019-12-06 2021-06-08 西安诺瓦星云科技股份有限公司 Display control card topological relation identification method and LED display control system
CN112929282B (en) * 2019-12-06 2023-08-15 西安诺瓦星云科技股份有限公司 Display control card topological relation identification method and LED display control system

Also Published As

Publication number Publication date
WO2016083954A3 (en) 2016-10-13

Similar Documents

Publication Publication Date Title
US9854651B2 (en) Programmable lighting device and method and system for programming lighting device
US9072142B2 (en) LED lighting unit with color and dimming control
US10356869B2 (en) Apparatus and methods for external programming of processor of LED driver
US20020047628A1 (en) Methods and apparatus for controlling devices in a networked lighting system
US10383192B2 (en) Contactless LED lighting fixture and LED lighting network including contactless LED lighting fixture
US10034354B2 (en) Splittable light strings and methods of splitting light strings
WO2016083954A2 (en) Lighting control apparatus and methods
WO2016001780A1 (en) Proxy for legacy lighting control component
US11564294B2 (en) Drivers with simplified connectivity for controls
JP2013539181A (en) Method and apparatus for operating a group of luminaire nodes
WO2016206996A1 (en) Registering lighting node calibration data
WO2009027901A2 (en) Apparatus for configuration of lighting fixtures
WO2019170506A1 (en) System and method for automatically recommissioning a lighting node using wireless signal characteristics
WO2016139148A1 (en) Opto-isolated dimming control for outdoor lighting appliance

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15801266

Country of ref document: EP

Kind code of ref document: A2