BACKGROUND OF THE INVENTION
There exist various methods for automatically generating and assigning addresses for components of an integrated network. However, if the components of the network include subcomponents that are not directly connect to a network control device, no method exists to easily/automatically assign an address to the subcomponents that also determines their physical location. Because of this limitation, the subcomponents fail to be easily interchanged within the system network without having to manually reassign address information to the components and the subcomponents.
Therefore, there exists a need for improving the interchangeability of components and subcomponents in a system network.
SUMMARY OF THE INVENTION
The present invention provides systems and methods for assigning addresses to one or more components, such as luminaires, in a network. In one example the luminaires include one or more lamp modules. An example method sends a first message from a master control unit to all the luminaires on a broadcast databus, and switches all the luminaires to an addressing mode of operation when they receive this message. A token signal exists between each of the luminaires and is used to select the luminaire on the broadcast databus that responds to the addressing information. The address information is recorded at the luminaires selected by the received token signal. Addresses are assigned to the associated lamp modules and the recorded address information and assigned lamp module addresses are sent to the master control unit. The sent address information and lamp module addresses are stored in non-volatile memory in a system controller, and a luminaire controller.
In one aspect of the invention, the luminaire includes two or more locations having a unique configuration of one or more plug-in pins. Each of the locations is associated with an address known by the luminaire based on the configuration. The lamp modules are attached to a respective configuration of plug-in pins and corresponding physical locations.
BRIEF DESCRIPTION OF THE DRAWINGS
The preferred and alternative embodiments of the present invention are described in detail below with reference to the following drawings:
FIGS. 1-3 illustrate block diagrams of components of the system formed in accordance with the embodiment of the present invention;
FIG. 4 illustrates an example process performed by the components shown in FIGS. 1-3;
FIG. 5 illustrates a particular example formed in accordance with the embodiment of the present invention; and
FIGS. 6A and 6B illustrate an addressing scheme for effectively delivering commands or instructions to luminaires and their associated sublamp modules.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
As shown in FIG. 1, an example system 80 performs automated address assignments for a plurality of luminaires 86 that receive power from a Power Distribution Unit (PDU) 84, and information from a Zone Control Unit (ZCU) 82. The ZCU 82 automatically assigns addresses to each of the luminaires 86 using a token signal sent over a token line and address information sent over a broadcast databus, such as an RS-485 communication databus. The luminaires 86 are separately addressable elements with at least some of the luminaires 86 having one or more sublight/lamp modules. In one embodiment, one or more system(s) 80 reside(s) in a cabin of an aircraft 88, but could be used anywhere luminaire and light module interchangeability is desired.
As shown in FIG. 2, each of the luminaires 86 may include a plurality of lamp modules 102. The luminaires 86 also include a control unit 100 having power conversion circuitry 110 that supplies power to each of the sub (lamp) modules 102, a databus interface 112 that is in communication with the RS-485 communication databus, and a light microcontroller 114. The light microcontroller 114 receives the token signal over the token line and address information from the RS-485 communication databus via the databus interface 112. Also, the databus delivers commands from the ZCU 82 for controlling operation of the luminaire 86 and the sub-modules 102.
In one embodiment, each of the lamp modules 102 are plugged into a location that has a unique set of address bits 104 in the form of plug-in pins. The light microcontroller 114 knows the location of each of the lamp modules 102 based on the address bits 104 of the pin that the lamp module 102 is attached to.
FIG. 3 illustrates an example of the lamp module 102. In one embodiment, the lamp module 102 includes an 8-bit microcontroller 120 with non-volatile memory. The lamp module 102 also includes power drive circuitry 122 and in one embodiment an optical intensity feedback circuit 124. The power drive circuitry 122 controls operation of one of a plurality of light emitting devices (LEDs), such as a red R LED 130, a green G LED 132, a blue B LED 134, and a white W LED 136 with a control signal. Other LED or color configurations may be used. The optical intensity feedback circuit 124 is controlled by an EN (enable) signal sent from the microcontroller 120. Results from the optical intensity feedback circuit 124 are sent back to the microcontroller 120 for storage and/or delivery back to the luminaire 86 or ZCU 82.
FIG. 4 illustrates an example process 200 for assigning addresses to the luminaires 86 of FIG. 1 and the lamp modules 102 shown in FIG. 2. First at a block 210, the ZCU 82 broadcasts over the databus a command message instructing the luminaires 86 to go into an addressing mode of operation. At a block 212, all the luminaires 86 that receive the broadcast command from the ZCU 82 switch to a listening mode and deassert their token (out) signal. Next, at a decision block 214, each of the luminaires 86 determines if the token (in) signal they receive is high. If the token (in) signal is high, then at a block 218, the luminaire 86 is associated with an address that is sent over the databus by the ZCU 82. The luminaire 86 acknowledges that it received the address and has stored the address. The ZCU 82 then proceeds to address the next luminaire 86. The luminaire 86 then asserts token (out) signal to the next luminaire 86.
Next, at a decision block 220, the process 200 returns to complete the association of addresses with luminaires 86 if not all of the luminaires 86 have yet received an address. The associated address is stored with memory associated with the ZCU 82 as well as in memory of the light microcontroller 114 of the luminaires 86.
At a block 222, each of the luminaires 86 assigns an address to any associated lamp module 102. This can be done physically by pin connection layout using plug-in pins 104 or it can be done similar to how the luminaires 86 get assigned an address (using a token signal, see above).
Next at a block 224, the ZCU 82 sends out a request to the luminaires 86 for information regarding the addresses for lamp modules 102 that are associated with the luminaires 86. Next at a block 226, the ZCU 82 receives and stores lamp module address information with the already stored addresses for the associated luminaires.
FIG. 5 illustrates another example implementation of the present invention. An aircraft 280 includes a central-lighting controller (CLC) 282 that is connected to a plurality of strings of luminaires 284. Each of the strings of luminaires 284 is coupled to a unique Universal Asynchronous Receiver Transmitter (UART) 290 located within the CLC 282. A system processor 292, also located within the CLC 282, is in data communication with each of the UARTs 290. The system processor 292 provides instructions to the UART 290 in order to selectively control each of the luminaires 282 within each of the strings as well as each of the lamp modules (not shown) located within each of the luminaires 284.
FIG. 6A illustrates an example serial transmission protocol 300 of instruction messages supplied by a ZCU 82 or similar device to the luminaires 86 or UARTs 290 for controlling luminaire operation and operation of any submodules of the luminaires.
FIG. 6B illustrates an example data packet 320 that has been sent in accordance with the protocol 300 shown in FIG. 6A. The data packet 320 includes addressing information in bytes Address 0 and 1, instruction information, and data integrity information.
While the preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. Instead, the invention should be determined entirely by reference to the claims that follow.
Patent Application
20070260764
