Patent Grant
8742686
The present application is generally directed towards providing control and management of LED systems via a network.
The Lighting Emitting Diode (LED) lighting industry is a fast growing market. LED lighting offers a strong value proposition as a lighting solution by reducing maintenance expense and lowering energy requirements for lighting systems while not producing hazardous materials. As such, traditional lighting original equipment manufacturers (OEMs) continue to adopt the LED light source for typical lighting applications. However the lack of standardization in the industry and special requirements for powering and controlling LED systems are a barrier to entry. There currently exists no LED “bulb” that provides adequate illumination as a light source. Most fixture manufacturers create new or retrofit existing luminaries to accommodate LED light sources. These LED light sources require proper thermal management and optical design. In addition to the overall mechanics, the electrical requirements of an LED source may be demanding. The LED is a low voltage DC device and sensitive to voltage and current fluctuations.
Some companies have developed packaged drivers, “LED Drivers”, for LED luminaries. These LED drivers are essentially constant current power supplies configured to provide a set current value to the LEDs despite the input voltage to the luminaire. For example, an LED driver may take a 120VAC input and provide a 350 mA constant current output. In addition to these packaged “LED Drivers,” other semiconductor OEMs are developing LED Driver “chips.” These LED chips are integrated circuits that may be incorporated at the board level to integrate sensing technology and digital or analog input for providing power to the LED luminaire.
There are two typical LED driver customers. The first is what may be considered a traditional lighting OEM customer. These traditional OEM companies have specialized in packaging to incorporate standard ballasts and bulbs into metal and plastic housings with all components being plug and play and typically color coded. In most cases, this type of LED customer uses the traditional ballast style “LED Driver” packaged such that wire leads may be easily connected to predefined inputs and outputs. The second type of customer is one who understands electronic design and designs a printed circuit board (“PCB”) that will accommodate an LED driver chip. This type of customer will specifically customize the PCB for the target application.
It is unlikely to find these two types of customers are one in the same. As such, the LED OEM driver typically provides either the simple plug and play LED driver or a customized LED driver solution. The first type of customer uses the simple LED Driver plug and play solution that provides conventional and convenient means of hookup. However, these plug and play solutions offer no means of advanced lighting control, such as flashing sequences, color mixing, etc. The second type of customer may obtain an advanced control solution but through the integration of highly sophisticated control system in which the programming is done at the job site such that sequencing and effects may be achieved at the control panel level. However, these integrated systems are complex, require much setup, customized for every job, and are expensive such that only the highest end applications receive such integration.
The systems and methods of the present disclosure described herein addresses the large void in the OEM LED driver market between the simple plug and play LED driver and the customized and complex integrated LED driver systems. The present disclosure provides an LED control and management system to create sophisticated, networked and integrated LED based lighting systems without requiring knowledge of electronic design or complex programming. This LED control system provides a level of simplicity and user friendliness of the previous plug and play LED driver solution while providing the advanced control capabilities of the more complex, integrated systems. Additionally, the LED control system offers versatility such that each module of the system may be configured to function as needed for the overall system. A configuration package of the solution provides a simple configuration tool to configure the functionality of each of the modules without complexity.
In overview, the LED control system of the present solution includes a programmable LED Control Module (“LCM”), a programmable User Interface Module (“UIM”) and a computer based configuration software package (“CSP”). The UIM and LCM modules are network enabled devices that communicate with each other to form a lighting network for controlling and managing one or more LCD sources. This network may be wireless. The LCM controls the light output of various off the shelf or custom designed LED Drivers which power LEDs installed to an LED Light Fixture. The UIMs receive digital data or analog signals in which they interpret and provide the correct commands and sequences to the LCMs via wireless or wired communication. The LCM receives the commands from the UIM to control the light output of the LED in accordance with the command. The CSP provides a configuration tool to create rules or command sequences for controlling the lighting based on triggers from the signals received by the UIM.
The present disclosure offers many advantages including standardization of the LCM and UIM that may be configured to interface with any digital and/or analog input and to provide any LED driver output. Real time data available from any type and form of input, such as physical sensors or Internet input may trigger and influence the lighting effects managed via the UIM and LCM. The system leverages and uses any existing LED source and driver technology such that the LCM control system is an addition to instead of a replacement for this technology. Furthermore, the integration of wireless communications between the LCM and UIM modules enables the deployment of advanced illumination capabilities for retrofit installations The use of user friendly, drag and drop and wizard based configuration software allows any non-technical designer to create advanced lighting control rules.
In some aspects, the present disclosure is related to systems and methods for executing a user specified rule to control lighting effects in a lighting network. The lighting network may comprise an interface module in communication with one or more lighting control modules. The interface module may receive a rule for controlling a lighting network. The interface module may be in communication with one or more lighting control modules of the lighting network. The rule may comprise a user identified input and a user specified lighting effect to occur via the one or more lighting control modules responsive to the user identified input. The interface module may detect the receipt of the user identified input and execute, in response to the detection, the rule to trigger the user specified lighting effect via the one or more lighting control modules.
In some embodiments, the interface module receives a set of executable instructions comprising the rule. In numerous embodiments, the interface module receives the rule comprising a user specified predetermined threshold of the user identified input for which to trigger the user specified lighting effect. Sometimes, the interface module may receive data as input via one or more analog or digital ports of the interface module. Sometimes the interface module may receive data as input via a network port of the interface module. In some embodiments, the interface module detects the user identified input from a stream of data received via a port. In a variety of embodiments, any one of lighting network components communicates one or more instructions to the one or more lighting control modules to produce the user specified lighting effect. Sometimes, any one of lighting network components communicates one or more instructions to the one or more lighting control modules to produce the user specified lighting effect for a user specified time period. The instructions may be communicated via a variety of ways to program the one or more lighting control modules.
In some aspects, the present disclosure is related to systems and methods for configuring a user specified rule to control lighting effects in a lighting network which comprises an interface module in communication with one or more lighting control modules. A configuration tool may receive a user's identification of an input to be received via an interface module for controlling one or more lighting control modules of a lighting network. The configuration tool may receive a user's specification of a lighting effect to occur via the one or more lighting control modules and responsive to the user identified input. In many embodiments, the configuration tool provides for execution on the interface module a rule comprising the user specified lighting effect to occur via the one or more lighting control modules responsive to the user identified input.
In some embodiments, the configuration tool or any other lighting network component receives a user's identification of a value of data that may be received by an analog or digital interface of the interface module. In many embodiments, the configuration tool or any other lighting network component receives a user's identification of a value of data that may be received via network interface of the interface module. Sometimes, the configuration tool may receive a user's identification of the input based on a type of interface configured on the interface module. In some embodiments, the configuration tool or any other lighting network component receives a user's specification of the lighting effects as a sequence of one or more instructions to communicate to the one or more lighting control modules. The configuration tool may also receive a user's specification of the lighting effects as a sequence of one or more instructions to communicate to the one or more lighting control modules. In some embodiments, the configuration tool receives a user's specification of the lighting effect as an identification of a program to execute on the one or more lighting control modules. In a number of embodiments, the configuration tool receives a user's specification of the lighting effect as an identification of a program to execute on the interface module. In a number of embodiments, the user specifies a lighting scheme for the lighting effect. The configuration tool may generate a set of executable instructions representing the rule. In some embodiments, any lighting network component may communicate the set of executable instructions to the interface module.
The details of various embodiments of the present solution are set forth in the accompanying drawings and the description below.
The foregoing and other objects, aspects, features, and advantages of the present invention will become more apparent and better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.
For purposes of reading the description of the various embodiments of the present invention below, the following descriptions of the sections of the specification and their respective contents may be helpful:
Prior to discussing the specifics of embodiments of the systems and methods of the LED control system and lighting network of the present solution, it may be helpful to discuss the network and computing environments in which such embodiments may be deployed. Referring now to
The lighting network 175 may include a plurality of network enabled devices, such as a network enabled UIM 102 communicating via a network 104 with one or more network enabled LCMs 106. As will be described in further detail below, each of these network enabled devices may have a network address for communicating with each other. Each of the network enabled UIMs 102 and LCMs 106A-106N may communicate via a wired and/or wireless network using any type and form of protocol. In some embodiments, the UIM and LCMs communicate over an Internet Protocol or Ethernet based network. In various embodiments, the lighting network 175 may be considered to include those lighting related devices in communication with each other to perform any of the functionality and operations described herein. As such, in some embodiments, the lighting network 175 includes the UIM 102 and one or more LCMs 106A-106N. In other embodiments, the lighting network 175 includes the UIM 102 and the LCM and any LED drivers 107A-107N and LEDs 108A-108N controlled and managed by the LCM and/or UIM. In yet another embodiment, the lighting network 175 includes the CSP 120 in communication with the UIM 102. In further embodiments, the lighting network includes the UIM 102, the CSP 120 and any LCMs 106A-106N.
The lighting network 175 may be established, organized, configured or arranged to have one or more lightings groups, such as lighting group 176A (generally referred to as a lighting group 176) as depicted in
In the lighting network 175, the UIM 102 provides various interfaces, such as analog or digital interfaces, that may be configured to perform tasks, such as any lighting related task described herein. The UIM 102 receives input from these interfaces that influences or controls output to the LCM 106, which in turn controls and drives the LED drivers 107 and LED source 108. A first UIM 102 may communicate via a network 104 with and manage a plurality of LCMs 106A-106N. In some embodiments, a plurality of UIMs 102A-102N may be used to communicate with and manage a plurality of LCMs 106A-106N. In other embodiments, a first UIM 102A and a second UIM 102B may both communicate with and/or manage the same LCM 106 or set of LCMs 106A-106N. In one embodiment, a UIM 106 may be used to communicate and manage a lighting group 176.
The UIM 102 may also provide status, feedback or any other information about the operation and performance of the lighting network 175, or any portion thereof, such as a specific LCM or LED driver. For example, the UIM may present a web page via the network 104 to a user to determine the status of various operational aspects of the lighting network 175. The UIM 106 may include any monitoring and/or logging agents to detect and capture any activity of the operations and performance of the lighting network 175, or any portion thereof. In one embodiment, the UIM 102 provides information on the status of the network 104 between the UIM and any LCMs 106. In another embodiment, the UIM 102 provides information on the status of an LCM 106.
The LCM 106 provides a mechanism and means to interface digital controls and logic to a typical or otherwise “dumb” LED fixture 108. The LCM 106 receives input, commands or instructions from the UIM 102 and/or CSP 120 with respect to controlling, managing, driving or otherwise directing the operation of the LED driver 107 and corresponding LED source 108. The LCM 106 provides any type and form of output to transmit signals to a corresponding LED driver 107. The LCM 106 may include any type and form of communication interface, analog and/or digital, to communicate with an LED driver 107. In some embodiments, the LCM 106 may communicate with the LED driver 107 via any type and form of software communication interface, such as an application programming interface (API). In other embodiments, the LCM 106 may communicate with the LED driver 107 using any type and form of hardware interface.
An LCM 106 may communicate with one or more LED drivers 107. In some embodiments, a first LCM 106A communicates with a first LED driver 107A and a second LCM 106B communicates with a second LED driver 107B, and a third LCM 106C communicates with a third LED driver 107C, and so on. In other embodiments, a first LCM 106B communicates with a first LED driver 107A and a second LED driver 107B. In yet another embodiment, a first LCM 106A and a second LCM 106B are both used to communicate with one or more LED drivers 107. In some cases, a second LCM 106B may be used concurrently with a first LCM 106A for communicating with an LED driver 107. In other cases, the second LCM 106 may used as backup or a redundant LCM to the first LCM 106A for communicating with one or more LED drivers 107.
The LED driver 107 may include any type of logic, function or operation for controlling the current and/or power delivered to an LED source 108. The LED driver 107 may include software, hardware or any combination of software and hardware. In various embodiments, the LED driver 107 functions as an electronically-controlled current source providing a predetermined amount of current to one or more attached LED lighting modules 108 in response to received control signals. In one embodiment, the LED driver 107 acts as or provides a constant current power supply configured to provide a set current value to the LEDs despite the input voltage to the luminaire. For example, an Advance Transformer LED driver 107 may take a 120VAC input and provide a 350 mA constant current output whereas the current is controlled and the voltage is stepped down, a typical “buck” topology. In some cases, the LED driver 107 may “boost” voltages in the case where the input voltage is lower than the forward voltage of the LEDs to be powered. In one case, the LED driver 107 may be configured as a “buck-boost” whereas the input voltage may be stepped up or stepped down as required. In some embodiments, these LED Drivers 107 offer dimming via a “PWM” (pulse width modulated signal), or analog control voltages including 0 to 10V control voltages. In other cases, the LED driver 107 may pulse the power input to the LED source on and off in order to adjust the intensity of the LED source 108.
The LED driver 107 may include a voltage-controlled current source, a current-controlled current source, a power MOSFET (Metal Oxide Semiconductor Field Effect Transistor), power amplifiers, power transistors, or high-current op-amps as well as resistive, capacitive and switching elements. In some embodiments, the LED driver includes current-limiting circuit elements at its output, so that current levels in excess of an LED's maximum rated value may not be exceeded. The driver 107 may include one or more input ports, e.g., a signal-control receiving port and an override control port, and one or more output ports, e.g., one or multiple signal output ports, a driver status port, and one or more current sensing ports. The LED driver 107 may receive and send pulse-width modulated signals, e.g., square wave signals with variable duty cycle. The input ports of the LED driver 107 may include over-voltage protection and surge protection to prevent damage by transient electrical fluctuations at its input ports.
In some embodiments, the LED driver 107 may be an ASIC (Application Specific Integrated Circuit), or a commercially produced, off-the-shelf LED driver chip. The driver 107 may be packaged in a housing, as a separate element of the lighting network 175, or may be incorporated into another element of the network or lighting group, e.g. into an LCM 106A or into an LED lighting assembly 108A. As an ASIC or commercially-available driver chip, the driver may be incorporated onto a printed circuit board (PCB) for custom-design or original-equipment manufacturing circuit applications. The LED driver 107 may have an external power supply, which powers internal circuitry in the driver and provides a source of amperage for the attached LEDs 108. The external power supply may be dedicated to the LED driver or shared with another element in the lighting network, e.g., an LCM.
In one embodiment, a first LED driver 107 communicates with or controls a single LED source 108. In other embodiments, a first LED driver 107A communicates with or controls a plurality of LED sources 108A-108N. In other embodiments, a first LED driver 107A communicates with or controls a first LED source 108A while a second LED driver 107B communicates with or controls a plurality of LED sources 108B-108N.
Examples of commercially-available LED drivers include an ADM8845 series LED driver chip, providing up to 30 mA current and connections for six LEDs, or an AD8240 series chip which must be used with an external transistor to provide sufficient drive current. Both of these driver chips are available from Analog Devices, Incorporated of Norwood, Mass. Other similar LED driver chips include: an FAN5607 LED driver chip, available from Fairchild Semiconductor Corporation of South Portland, Me., an STP16CP596 LED driver chip, available from STMicroelectronics of Lexington, Mass., or an LM27952 driver chip, available from National Semiconductor Corporation of Santa Clara, Calif. An example of a packaged LED driver includes an LEDD1 driver, available from Thorlabs of Newton, N.J., or a SmartDriver VDX driver, available from i2Systems of Morris, Conn.
The LED lighting source 108 may include any type and form of Lighting Emitting Diode (LED) based luminaire or luminaire source, such as an LED lighting assembly. In some embodiments, the LED 108 may comprise one or more semiconductor p-n junction light-emitting diodes. The LED assembly 108 may be constructed, designed or adapted to receive current from a LED driver 107 and direct the current across the one or more p-n junctions in forward bias. In various embodiments, the brightness or intensity of light output from a diode is substantially proportionally related to the amount of current flowing across the p-n junction. The LED source 108 may include resistors to limit current flow across the one or more diodes, and may include heat sinks in thermal contact with the diodes so as to dissipate from the diodes. Optical elements, such as lenses or diffusers may be placed over the LEDs to concentrate or disperse emitted light. Wavelength shifting methods, such as thin films containing organic fluorescent molecules or inorganic phosphorescent molecules, may be included with the diodes to absorb and re-emit radiation at wavelengths shifted from the LED's natural emission spectrum. The LED source 108 may include one or more diodes, each emitting radiation at distinct wavelengths, e.g. red, amber, green, and blue. In other embodiments, the LEDs may comprise organic light-emitting diodes (OLEDs) or phosphorescent light-emitting diodes (PHOLEDs) or a combination of LEDs, OLEDs and PHOLEDs. In some embodiments, the LEDs 108 within an assembly may be mounted on an electromechanically-moveable element, so that the direction of light output from the LED assembly may be controlled. In yet other embodiments, an LED driver 107 may be incorporated within the LED lighting assembly 108.
Examples of commercially-available LED lighting assemblies or LEDs include the VML lighting assembly series, the Apeiron SDi Tri-Light, the V-Line series lighting assemblies, all available from i2Systems of Morris, Conn. Additional examples include the Lumispot or LinkLED lighting assemblies, available from Dialight Corporation of Farmingdale, N.J. or the Titan LED Light Engines available from Lamina of Westamptom, N.J. Alternatively, examples of individual LEDs include the ASMT series light sources, available from Avago Technologies of Andover, Mass.
Still referring to
Although
Referring now to
Although
Referring now to
Computing Device
The configuration software package (CSP) 120 may be deployed as and/or executed on any type and form of computing device 100, such as a computer, network device or appliance capable of communicating on any type and form of network and performing the operations described herein. In some embodiments, any of the functionality, operations or logic of the UIM 102, LCM 106, LED Driver 107 and/or LED 108 described herein may be supported by, configured via, performed by or deployed on a computing device 100. In other embodiments, any portion of the UIM 102, LCM 106, LED Driver 107 and/or LED 108 may include or comprise any portion of the computing device 100 described below.
The central processing unit 101 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 122. In many embodiments, the central processing unit is provided by a microprocessor unit, such as: those manufactured by Intel Corporation of Mountain View, Calif.; those manufactured by Motorola Corporation of Schaumburg, Ill.; those manufactured by Transmeta Corporation of Santa Clara, Calif.; the RS/6000 processor, those manufactured by International Business Machines of White Plains, N.Y.; or those manufactured by Advanced Micro Devices of Sunnyvale, Calif. The computing device 100 may be based on any of these processors, or any other processor capable of operating as described herein.
Main memory unit 122 may be one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor 101, such as Static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM), synchronous DRAM (SDRAM), JEDEC SRAM, PC100 SDRAM, Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM), Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM). The main memory 122 may be based on any of the above described memory chips, or any other available memory chips capable of operating as described herein. In the embodiment shown in
The computing device 100 may support any suitable installation device 116, such as a floppy disk drive for receiving floppy disks such as 3.5-inch, 5.25-inch disks or ZIP disks, a CD-ROM drive, a CD-R/RW drive, a DVD-ROM drive, tape drives of various formats, USB device, hard-drive or any other device suitable for installing software and programs such as the CSP 120, or portion thereof. The computing device 100 may further comprise a storage device 128, such as one or more hard disk drives or redundant arrays of independent disks, for storing an operating system and other related software, and for storing application software programs such as any program related to the CSP 120. Optionally, any of the installation devices 116 could also be used as the storage device 128. Additionally, the operating system and the software can be run from a bootable medium, for example, a bootable CD, such as KNOPPIX®, a bootable CD for GNU/Linux that is available as a GNU/Linux distribution from knoppix.net.
Furthermore, the computing device 100 may include a network interface 118 to interface to a Local Area Network (LAN), Wide Area Network (WAN) or the Internet through a variety of connections including, but not limited to, standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56 kb, X.25), broadband connections (e.g., ISDN, Frame Relay, ATM), wireless connections, or some combination of any or all of the above. The network interface 118 may comprise a built-in network adapter, network interface card, PCMCIA network card, card bus network adapter, wireless network adapter, USB network adapter, modem or any other device suitable for interfacing the computing device 100 to any type of network capable of communication and performing the operations described herein.
A wide variety of I/O devices 130a-130n may be present in the computing device 100. Input devices include keyboards, mice, trackpads, trackballs, microphones, and drawing tablets. Output devices include video displays, speakers, inkjet printers, laser printers, and dye-sublimation printers. The I/O devices 130 may be controlled by an I/O controller 123 as shown in
In some embodiments, the computing device 100 may comprise or be connected to multiple display devices 124a-124n, which each may be of the same or different type and/or form. As such, any of the I/O devices 130a-130n and/or the I/O controller 123 may comprise any type and/or form of suitable hardware, software, or combination of hardware and software to support, enable or provide for the connection and use of multiple display devices 124a-124n by the computing device 100. For example, the computing device 100 may include any type and/or form of video adapter, video card, driver, and/or library to interface, communicate, connect or otherwise use the display devices 124a-124n. In one embodiment, a video adapter may comprise multiple connectors to interface to multiple display devices 124a-124n. In other embodiments, the computing device 100 may include multiple video adapters, with each video adapter connected to one or more of the display devices 124a-124n. In some embodiments, any portion of the operating system of the computing device 100 may be configured for using multiple displays 124a-124n. In other embodiments, one or more of the display devices 124a-124n may be provided by one or more other computing devices, such as computing devices 100a and 100b connected to the computing device 100, for example, via a network. These embodiments may include any type of software designed and constructed to use another computer's display device as a second display device 124a for the computing device 100. One ordinarily skilled in the art will recognize and appreciate the various ways and embodiments that a computing device 100 may be configured to have multiple display devices 124a-124n.
In further embodiments, an I/O device 130 may be a bridge 170 between the system bus 150 and an external communication bus, such as a USB bus, an Apple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWire bus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a Gigabit Ethernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a Super HIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or a Serial Attached small computer system interface bus.
A computing device 100 of the sort depicted in
In other embodiments, the computing device 100 may have different processors, operating systems, and input devices consistent with the device. For example, in one embodiment the computer 100 is a Treo 180, 270, 1060, 600 or 650 smart phone manufactured by Palm, Inc. In this embodiment, the Treo smart phone is operated under the control of the PalmOS operating system and includes a stylus input device as well as a five-way navigator device. Moreover, the computing device 100 can be any workstation, desktop computer, laptop or notebook computer, server, handheld computer, mobile telephone, any other computer, or other form of computing or telecommunications device that is capable of communication and that has sufficient processor power and memory capacity to perform the operations described herein.
B. User Interface Module (UIM) and LED Control Module (LCM)
Referring now to
In overview, the UIM 102 may include an electronic device designed, constructed or adapted to receive data and output electronic signals in response to the received data. The UIM 102 may include any preprogrammed instructions or rules associated with the received data. In some cases, the UIM 102 may be programmable. The various data interfaces 202, 204, 206 and 214 may be used to adapt or operationally program the UIM 102 to execute specific lighting-control tasks. For example, executable code or instructions may be programmed into the UIM 102 using the CSP 120 and computer interface port 214. Data received from ports 202, 204 and 206 may affect the operational results of the executable code, and change the electronic signals output to the LED drivers 107 at ports 210 and 212.
In some embodiments, the UIM 102 may include a reduced instruction set computer (RISC), programmable logic controller (PLC), microprocessor, microcontroller (MCU), application specific integrated circuit (ASIC), digital signal processor (DSP), or a combination of these hardware components. Any one of these components, or combination thereof, may serve as a central processor or central controller for the UIM. The central processor or controller may be adapted to receive and execute computer code such as C, C++, RISC instruction sets, Basic, assembly language, programming language for microcontrollers, Java, or vendor proprietary machine language code. The UIM may further include peripherals such as analog-to-digital converters (ADC), digital-to-analog converters (DAC), various types of memory such as RAM, ROM, DRAM, SRAM, EPROM, EEPROM, Flash Memory, or Cache, and various types of serial communications interfaces such as inter-integrated circuit (I2C) or serial peripheral interface (SPI) bus. In various embodiments, the UIM 102 is electrically powered through a power port 208 with a local power supply. The UIM 102 further includes one or more interface ports, e.g. computer interface port 214, digital input port 202, analog input port 204, and internet port 206, and one or more output ports, e.g. a radio-frequency port 210, and network port 212.
In other embodiments, the UIM 102 may be a computing device 100 such as a personal computer or a laptop. The configuration software package 120 may then be executed on the UIM 102 in some embodiments, and data transmitted to the LCMs through a network port, such as a wireless connector.
In yet other embodiments, the UIM 102 may be comprised of fixed, i.e. non software-programmable, electronic circuitry. For example, the UIM may comprise any combination of TTL (Transistor-Transistor Logic), logic chips, resistors, capacitors, potentiometers, field-effect transistors (FETs), transistors, switches, jumpers, and op-amp chips mounted on a printed circuit board (PCB). In these embodiments, functionality of the UIM may be reprogrammed by changing circuit elements.
In various embodiments, the UIM 102 may be small in size, measuring less than 10 cm along any edge. The UIM may be constructed on a small, custom printed circuit Board (PCB) and enclosed in an electronic housing. The housing may provide shielding from electromagnetic interference EMI, and provide a panel for data port connections. In other embodiments, the UIM may be designed and constructed as any type and form of appliance, any type and form of peripheral, such as a USB device, or in any form factor of a computing device 100, or portion thereof, such as a card. As those ordinarily skilled in the art will appreciate, the form of the UIM may be designed and constructed for many environments and have a size and form factor in accordance with such environments.
Computer interface port 214 may be used to program the UIM's internal processor. The port 214 may include a single or multiwire connection adapted to support communications between an external processor, such as a personal computer, laptop computer or any portable computing device adapted to run the configuration software package 120, and the UIM's internal processor or electronics. The external computer may be one that supports any of the following operating systems: Windows, Mac OS, Unix, and Linux. Serial or parallel communication protocols may be employed over port 214. The communications protocols employed over port 214 may include, without limitation, RS-232, RS-485, modbus, Ethernet, IEEE 802.3, USB, SCSI, FireWire, ATM, TCP, UDP, ZigBee, Bluetooth and AppleTalk. In other embodiments, computer interface port 214 may be a wireless port supporting, e.g., IEEE 802.11 wireless communication protocols or Bluetooth technology. In yet another embodiment, the computer interface may include any type and form of network interface or Network Interface Card for communicating with a computing device 100 over a network 104.
As shown in
In various embodiments, the UIM 102 includes one or more digital ports 202. The digital ports 202 may be adapted to receive various digital signals, such as TTL, CMOS and ECL (emitter coupled logic) signals, which may be representative of the state of an external element or condition. In some embodiments, the input impedance of the digital ports 202 is high, greater than about 1,000 ohms so that low-current signals may be detected. In other embodiments where high-speed digital signals are input to the UIM, the input impedance at the digital port 202 may be low, e.g. less than about 100 ohms. Field effect transistors (FETs), bipolar junction transistors (BJTs), logic chips or digital-to-analog converters (DACs) may be employed as signal-receiving circuit elements at the digital input ports. Voltages appearing on the digital ports may range from about −5 volts to about 24 volts in various embodiments.
Signals applied to the digital input ports may be derived from a variety of sources including, but not limited to, a pulse-width modulation (PWM) source, toggle switches, jumper pins, sensors with digital output, a computer, another UIM, an ASIC, or an LED control module 106. In some embodiments, the logic level of one or more digital ports 202 may determine the manner in which code programmed into the UIM's controller is executed. For example, a logic level of “1” appearing at a particular digital input port may initiate the execution of a subroutine within the controller's code. In additional embodiments, the logic level appearing at a port may be, in effect, passed to an LCM. For example, a PWM signal applied to a digital port may be relayed to an LCM to control the intensity of an LED. The logic level of the digital ports may be monitored continuously by the UIM's controller, or monitored only upon conditions established by executable code within the controller. For example, the signal level of one digital port may only be sampled pending the status of a signal level at another digital port or analog port. In some embodiments, the logic level of one or more ports may be set manually via toggle switches or jumper pins.
In various embodiments, the UIM 102 includes one or more analog ports 204. The analog inputs are useful for monitoring continuously-varying state conditions, e.g. environmental temperature, humidity, pressure, wind speed, wind direction, ambient light level, motion, speed, proximity, fluid flow, and acoustic amplitude. Analog signals from sensors adapted to monitor such continuously-varying conditions may be applied to one or more of the UIM's analog ports 204. In additional embodiments, user-supplied control signals, e.g. a 0-10 V control signal or a control signal derived from a conventional light dimmer, may be applied to the analog input ports. Analog ports with low impedance, e.g. less than about 100 ohms, may be included in the UIM 102 for high-speed signals, and ports with high impedance, greater than about 1,000 ohms, may be included for low-level signals.
Operational amplifiers (op-amps) may be employed as signal-receiving circuit elements for the analog ports 204. The signal level of the analog ports 204 may be monitored continuously by the UIM's controller, or monitored only upon conditions established by executable code within the controller. In some embodiments, the signal level appearing on an analog port 204 may be, in effect, passed by the UIM's controller to an LED control module. For example, the percentage of relative humidity may be monitored by an electronic sensor, and its output applied at an analog port 204 and relayed to an LCM to control the blue-intensity component of a yellow-blue LED lighting combination. In additional embodiments, the signal level appearing at an analog port may trigger, as in a threshold-detection application, the execution of a subroutine within the controller's code. For example, a sensed temperature in excess of a predefined level, may initiate the execution and transmission of a section of controller code which causes flashing of red LEDs.
The UIM 102 may include an Internet port 206, adapted for communication with any type and form of device via the Internet. These devices may exist within a personal area network (PAN), local area network (LAN), campus area network (CAN), metropolitan area network (MAN), wide-area network (WAN), or the Internet. Examples of data that may be received by the UIM through the internet port 206 include, but are not limited to, room occupancy, local weather conditions, remote weather conditions, traffic flow, metropolitan power flow, Stock Exchange information, number of website hits, and rate of online orders. The Internet port 206 may be a wired or wireless Ethernet port adapted to support any of a variety of network or Interface protocols. In some embodiments, the Internet port 206 may include any type and form of Network Interface Card for communicating on a network 104. The Internet port 206 may include or interface to a network stack, such as a TCP/IP (transport control protocol/Internet protocol) stack.
The UIM 102 may include any type and form of address 220 or addressing scheme for identifying or communicating with or from the UIM 102. An electronically-recognized address 220 may be pre-assigned to the UIM or dynamically configured. In some embodiments, the address 220 may be hard-wired during manufacture of the UIM. In other embodiments, the address may be set upon installation using a dual in-line package (DIP) switch incorporated into the UIM. In other embodiments, the UIM's address may be set by a lighting network system administrator accessing address configuration via ports 214 or 206. In yet other embodiments, the UIM's address may be dynamically configured via dynamic host configuration protocol (DHCP). In one embodiment, the address 220 is an Internet Protocol (IP) address. In other embodiments, the address 220 is a Media Access Control (MAC) address. In some embodiments, the address 220 is an Ethernet Protocol address. In yet one embodiment, the scheme or encoding of the address 200, or any portion thereof, may identify the manufacturer of the UIM or any functionality of the UIM.
In various embodiments, the UIM 102 may include one or more radio-frequency (RF) wireless network ports 210 and/or one or more wired network ports 212. In various embodiments, the ports 210 and 212 are used for bidirectional communication between the UIM and one or more LCMs 106A-106N. In some embodiments, the UIMs and LCMs communicate via wireless RF signals. Communications protocols used between the UIM and LCMs may be any of a variety of established Internet or industry protocols, e.g. IEEE 802.11, or may be a proprietary protocol developed by the manufacturer. In one embodiment, the ports may include commercial off-the-shelf Ethernet port hardware. In other embodiments, the ports may include one or more application-specific integrated circuits (ASICs) designed to support a selected communication protocol.
Communication between the UIM and LCM may be secure, encrypted or authenticated in either direction or in both directions. In some embodiments, the LCM only recognizes or acknowledges data transmitted by a pre-specified UIM. For example, a unique product identity code may be assigned to each UIM by the manufacturer, and this unique code may accompany each data transmission from the UIM to the LCMs. The LCMs, programmed to accept data accompanied by the unique code, may then authenticate the data transmission and process the instructions issued by the UIM. Such authentication would prevent other nearby UIMs from inadvertently seizing control of the LCMs. The two-way communication between the UIM and LCM may then be used to configure the one or more LCMs on the lighting network for desired lighting operations, or to relay real-time commands, such as changes in states at the UIM's digital 202, analog 204 or Internet 206 interface ports, from the UIM to one or more LCM's.
In operation, the UIM 102 may be installed, in some embodiments, at a location along with one or more LCMs 106A-106B. The LCMs are located within RF range of the UIM, or are electronically connected to the UIM via wires connecting ports 212 on the UIM to ports 212A on the LCMs. Attached to each LCM is one or more LED drivers 107 and one or more LED lighting assemblies 108. Any desired sensed or control signals, digital and analog, are connected to data ports 202 and 204. Optionally, an internet connection is established at port 206. Once installed, the UIM is powered on through port 208. Desired lighting instructions or rules, in the form of executable code, are then downloaded to the UIM's internal processor via ports 214 or 206. The executable code may provide for monitoring and incorporation of data appearing at data ports 202, 204 and 206. For example, weather conditions may be monitored over the internet port 206, and audio signals may be monitored over analog port 204, and these inputs reflected in data output from the UIM's processor. The code is executed in the UIM 102, and results are transmitted as instructions to the LCMs 106A-106N in the lighting network 175. Each LCM then executes the received instructions to control lighting within its lighting group 176. The instructions received by the LCMs may affect one or more of several lighting parameters, e.g. lighting intensity, lighting color, rate of change of lighting intensity, rate of change of lighting color, rate of repetitive change in lighting color, and rate of repetitive change in lighting intensity. In this manner, dynamic visual lighting displays can be created and readily modified.
In operation, the UIM may provide various interfaces that may be configured to enable specific LED lighting tasks which are executed over the lighting network 175. These tasks may be preset by an OEM customer, or may be set upon installation of the UIM, LCM and LED devices. Interfaces to the UIM may be analog or digital.
In some embodiments, an analog interface may include an on/off switch, a potentiometer, a light sensor, a proximity sensor, a temperature sensor, an adjustable or constant voltage, or a conventional SCR type dimmer switch such as those readily available off the shelf at most large retailers, e.g. Home Depot, Lowes, etc. In various embodiments, the analog interface may trigger an event within the UIM such that rules may be executed to produce a desired lighting effect. By way of example, upon receiving a temperature input corresponding to 50 degrees C., on or more LCMs may signal an increase in LED current output to 80% intensity. In another example, upon engaging a conventional toggle switch, on or more LCMs may signal an increase in LED current with a linear fade up to 100% over 3 seconds. In another example, a UIM may be configured to receive a 0 V to 10 V analog input such that a 1 V input produces an LED light output of 0% and a 9 V input yields a light output of 100%, with any intervening voltage producing a linearly proportional light output. Additionally in this example for voltages greater than 9 V, one or more LCMs may provide various PWM outputs to be engaged, each PWM output controlling an LED driver operatively communicating with different color LEDs, e.g. red, green, blue, and the LEDs may strobe and flash to create a lightening effect of varying intensity and on/off duration. Another example mode of operation may include sequencing multiple LCM's respective outputs on and off with various dimming curves, such that a light show may be created within a lighting space, including configurations such as light color and/or intensity chasing effects.
In other modes of operation, digital inputs to the UIM may affect various LED lighting dynamics. The UIM may be connected to a local area network (LAN) having Internet access, and may have an IP address, e.g. static or assigned via dynamic host configuration protocol (DHCP). The UIM may receive digital data through the network, e.g. the UIM may be configured to receive internet data from its manufacturer's servers or to receive local temperature data. By way of example, when the received temperature signal corresponds to −20 C or colder, an LCM activates a blue LED, and when the temperature data indicates 40 C or hotter, the LCM activates a red LED, and any temperature in between shall be a mixture or graduated shade between blue and red. In some embodiments, a UIM may be assigned to control an LCM having three PWM signal outputs, controlling light out put from one or more red, green, and blue LEDs. In this embodiment color mixing is enabled by controlling the PWM signals delivered to each of the three LEDs. In some embodiments, digital interfaces may be serial or parallel network type interfaces.
Although a UIM 102 is shown with specific ports in
Although described as “input” and “output” ports, data ports on the UIM may be adapted, constructed or designed to be bidirectional. For example, the computer interface port 214, the digital ports 202, the analog ports 204, the Internet port 206, the RF port 210 and network port 212 may be adapted to transmit and receive data. To receive data through any UIM port in various embodiments, the UIM provides for the port and its associated internal electronics to change their state from transmit mode to “listen” mode. In listen mode, any signal appearing on the port may be directed to the UIM's processor, or to a peripheral data-storage buffer or cache for subsequent processing.
Although programming of the UIM's internal processor or internal electronics has been described as enacted over computer interface port 214, in various embodiments programming of the UIM's internal processor may also occur via the Internet port 206. For example, new application software, such as software developed by the UIM manufacturer, may be downloaded over the Internet, through port 206 and programmed into the UIM's processor. In this manner, any improvements to the operation of the lighting network system developed by the manufacturer may be delivered to the customer post installation without the need to modify or exchange installed hardware.
Advantages of the UIM include its ease of configurability and reconfigurability, functional versatility, low cost and form factor. In embodiments where the UIM is configurable via the computer software package (CSP) 120 and downloaded firmware, new lighting schemes and displays may be altered simply by bringing a laptop computer within range of the UIM and wirelessly transferring data from the computer to the UIM. This obviates the need for removal, reworking, and reinstallation of a light-controlling device. Since lighting schemes can be selected through a computer interface and computer programming, the UIM enables high versatility in adapting any installed lighting elements to a desired or custom lighting display. In various aspects, the UIM provides a standardization of lighting control for various lighting elements. Since the UIM does not require custom design for each lighting installation, costs associated with custom electronic manufacture and custom installations can be eliminated reducing the overall cost of ownership of the lighting system. In some embodiments, a small sized UIM enables the UIM to be mounted in a hidden location, and easily installed at location by a system engineer, contractor, or home user.
Referring now to
The LCM 106A may comprise software, hardware or any combination of hardware and software. In various embodiments, the LCM may include a central processor, such as a reduced instruction set computer (RISC), programmable logic controller (PLC), microprocessor, microcontroller (MCU), application specific integrated circuit (ASIC), digital signal processor (DSP), or a combination of these hardware components. Any one of these components, or combination thereof, may serve as a central processor or central controller for the LCM. The central processor or controller may be adapted to receive and execute computer code such as C, C++, RISC instruction sets, Basic, Assembly, Java, or vendor proprietary machine language code. The LCM may further include peripherals such as analog-to-digital converters (ADC), digital-to-analog converters (DAC), various types of memory such as RAM, ROM, DRAM, SRAM, EPROM, EEPROM, Flash Memory, or Cache, and various types of serial communications interfaces such as inter-integrated circuit (I2C) or serial peripheral interface (SPI) bus. The LCM may be assembled on a printed circuit board (PCB) using a variety of off-the-shelf IC chips, or assembled on a PCB using several custom-designed ASICs. The LCM may have a unique lighting network address 220A, so that it may be recognized and independently controlled by a UIM 102. In other embodiments, the LCM may include fixed electronic circuitry, and not adapted to receive external data input during operation.
The physical size of the LCM 106 is, in various embodiments, smaller than about 10 cm, as measured along any edge of the device. In certain embodiments, the LCM is small enough to be incorporated into an LED lighting assembly. In other embodiments, the LCM is a small handheld unit which is mounted in close proximity to one or more LED drivers 107. In additional embodiments, one or more LED drivers 107 may be incorporated into a packaged unit including one or more LCMs. For embodiments where the LCM is operable via wireless communications, an antenna may be incorporated into the LCM housing, and the housing would be substantially transparent to the wireless transmissions. As those ordinarily skilled in the art will appreciate, the form of the LCM may be designed and constructed for many environments and have a size and form factor in accordance with such environments.
Electrical power may be provided to the LCM through port 208A. Power supplied to this port may include, but not be limited to, alternating voltage and current, e.g. 12 VAC, 24 VAC, or 120 VAC, or direct voltage and current, e.g. 5 VDC, 9 VDC, 12 VDC, or 24 VDC. The power may be provided from a wall-mounted power supply, or from existing facility supplies, e.g. 120 VAC. In various embodiments, the power supply chord may be hard-wired to the LCM, or may be removably attached via a power jack to the LCM. In alternative embodiments, power may be provided by a battery, which may be mounted external to the LCM or incorporated into the LCM unit.
The LCM may be adapted to receive and transmit any type and form of digital data through a wireless RF network port 210A and a wired network port 212A. Circuit elements at these ports may include, but not be limited to, such peripherals as analog-to-digital converters (ADC), digital-to-analog converters (DAC), application specific integrated circuit (ASIC), digital signal processor (DSP), any of a variety of Ethernet port hardware, or a combination of these hardware components. The data received at the network ports 210A and 212A may be from a UIM 102, from a personal computer, or from another device configured to communicate with the LCM. Types of communications and protocols supported at these ports may include RS-232, RS-485, Ethernet 10/100, Ethernet 10/100/1000, TCP/IP, UDP/IP, IEEE 802.3, IEEE 802.11, Bluetooth, and ZigBee.
In some embodiments, each LCM 106A is assigned a device address 220A-220N, which permits independent control of multiple LCMs on a lighting network 175. The address may be programmed into the LCM during manufacture, or it may be reconfigurable and established during installation. In some embodiments, multiple LCMs may have identical addresses so that they may be controlled in concert. In yet other embodiments, the LCMs address may be dynamically configured via dynamic host configuration protocol (DHCP). For example, the LCM may receive an address 220 from the UIM, which in some embodiments, may act as the DHCP. In one embodiment, the address 220 of the LCM is an Internet Protocol (IP) address. In other embodiments, the address 220 is a Media Access Control (MAC) address. In some embodiments, the address 220 is an Ethernet Protocol address. In yet one embodiment, the scheme or encoding of the address 200, or any portion thereof, may identify the manufacturer of the LCM or any functionality of the LCM.
One or more digital output ports 222A may be included with the LCM. Digital signals supported at the output ports 222A may include CMOS, ECL and TTL signals. The output electronics for these ports may include high impedance FETs or low impedance digital line drivers. Types of signals output by the ports 222A may further include PWM signals. The PWM signal may comprise a square-wave signal having a variable duty cycle as well as a variable frequency. Increases or decreases in the duty cycle can be used to increase or decrease light output from LEDs. In various embodiments, one of the output ports 222A may drive one or more LED drivers 107A, and as many as 50. In other embodiments involving color mixing, individual ports 222A can be assigned to LEDs having distinct colors, e.g. red, amber, green, and blue.
In various embodiments, the PWM output from any of the ports 222A may also be programmed for various frequencies depending on the application. For example, a slow 100 Hz frequency, which avoids issues related to FCC EMI regulations, may be employed for general lighting applications, whereas for a machine vision application higher frequencies may be required since slow frequencies may produce undesirable aliasing effects in high speed cameras used for such applications.
The LCM may have one or more analog output ports 224A. These ports may include a current buffer or voltage follower op-amp circuit element, which provides output voltages ranging from about −24 VDC to +24 VDC. The analog output port may be used to drive one or more LED drivers, in some embodiments as many as 50 LED drivers. The analog output port may provide a voltage-reference signal, e.g. 0-10 VDC, useful for some commercial off-the-shelf LED drivers. For example, a signal level of 0 VDC output from the LCM to an LED driver may cause the LED light output to be turned off, i.e. 0%, a signal level of 10 VDC may cause the LED light output to be turned fully on, i.e. 100%, and any value between 0 VDC and 10 VDC may cause a corresponding linear adjustment of the LED light output.
A power FET port 226A may be included in the LCM 106A. A circuit element for this port may include a power MOSFET, which can supply output current levels in excess of 100 amps. The power FET port may be used to directly drive one or more LED assemblies 108A, bypassing the LED driver 107A. In some embodiments, the port 226A may simply be used to turn one or more LEDs on and off. In other embodiments, the signal at port 226A may be modulated rapidly, greater than about 60 Hz, providing a pulse width modulation signal capable of dimming the light output from one or more LED assemblies.
In operation, the LCM provides a means for interfacing digital, or digital and analog controls to common, passive or “dumb” LED fixtures. The LCM 106A may receive lighting instructions or rules from one or more UTMs 102 located near the LCM or connected to the LCM via the wired network port 212A. The LCM processes the instructions and outputs control signals through some or all of its output ports 222A, 224A and 226A to operate one or more LED drivers 107A and LED lighting assemblies 108A. In some embodiments, the LCM may be incorporated into one LED lighting assembly 108A, the assembly designated as a “smart” LED assembly, and one or more “dumb” LED assemblies may be operatively connected so that their action mimics the action of the “smart” assembly. In some embodiments, the control signals are produced by the LCM's internal processor according to a set of instructions or rules transmitted to the LCM by the UIM 102. For example, the instructions may be to continuously vary duty cycles synchronously on three square wave signals applied to each of three ports 222A, where each of these signals is operatively applied to LED assemblies, through the LED driver 107A such that one port 222A activates a red LED assembly, one a green LED assembly and one a blue LED assembly. The square-wave signals may be TTL type signals, having a voltage swing from about 0 VDC to about 5 VDC, in some embodiments. The net result of such an instruction set would be to maintain a constant illumination color while continuously varying illumination intensity. In another embodiment, the instructions may be to continuously vary duty cycles asynchronously on three square wave signals applied to each of three ports 222A. The net result of such an instruction set may be to continuously vary both illumination color and intensity. In yet other embodiments, instructions or rules may be created in real time at the UIM 102 in response to pre-selected events or conditions, and transmitted to the LCMs over the lighting network so that real-time event tracking can be reflected in light-output from the LED assemblies. For example, the UIM may track temperature, wind speed, or ambient noise level through its analog input ports 204, process the data internally in real time, and continuously transmit new instruction sets to the LCM as these environmental parameters change.
In operation, the FET output port 226A may be used in some embodiments to enable and disable power applied to one or more LED drivers, or one or more LED lighting assemblies. This use of the FET port may override all other lighting commands to enable or disable lighting. Similarly in operation, the analog output port 224A may be used to provide graduated scaling of light output intensity from the LEDs. For example, a 1 VDC output from port 224A may cause a reduction in light output to 10% of maximum output for all LEDs controlled by the LCM 106A, whereas a 9 VDC output from port 224A may cause an increase in LED lighting intensity to 90% of maximum output. In operation, controlling signals output from ports 222A, 224A, and 226A may be applied to one or more LED drivers simultaneously or sequentially to obtain a desired lighting display.
Although the LCM 106A in
Although
In yet another embodiment, each of the LCMs 106A-106B may include all the functionality of a UIM, or any portion thereof, and the control of lighting may be distributed over the network 104. For example, LCM 106A may sense humidity, 106B may sense wind speed, and 106N may sense temperature. The information gathered by each LCM may be shared across the network 104, and affect operation of each LCM. In this embodiment, new rules or instructions established externally may be downloaded to any one of the LCMs, and the receiving LCM would then distribute the new rules across the network.
Advantages of the LCM include its ease of configurability and reconfigurability, functional versatility, low cost and form factor. In embodiments where the LCM is configurable via the computer software package (CSP) 120 and downloaded firmware, new lighting schemes and displays can be altered simply by bringing a laptop computer within range of the UIM and wirelessly transferring data from the computer to one or more UTMs existing within the lighting network. Data is then transferred from the one or more UTMs to each LCM within the network. This obviates the need for removal, reworking, and reinstallation of any light-controlling device. Since lighting schemes can be selected through a computer interface and computer programming, the LCM enables high versatility in adapting any installed lighting elements to a desired or custom lighting display. In various aspects, the LCM provides a standardization of lighting control for various lighting elements. Since the LCM does not required custom design for each lighting installation, costs associated with custom electronic manufacture and custom installations can be eliminated reducing the overall cost of ownership of the lighting system. In some embodiments, the potentially small size of the LCM enables it to be mounted in a hidden location, and easily installed at location by a system engineer, contractor, or home user. In some embodiments the LCM may be incorporated into an LED lighting assembly by the manufacturer, eliminating the need for any additional installation tasks and time related to the LCM.
C. Configuration Software Package (CSP)
Referring now to
In one embodiment, the configuration tool 320 includes any type and form of graphical modeling tool for creating, modifying, editing or otherwise configuring a representation of a lighting network 174. In some embodiments, the configuration tool 320 includes any type and form of block modeling tool. In other embodiments, the configuration tool 320 includes a user interface and system for creating, generating or otherwise configuring elements on a screen and linking or forming relationships between elements, such as found in a network diagram or system architecture diagram.
The configuration tool 320 of the CSP includes any type and form of user interface. In one embodiment, the configuration tool 320 comprises any type and form of command line interface. In various embodiments, the configuration tool 320 comprises any type and form of graphical user interfaces. The graphical user interfaces may include any arrangement and combination of graphical user interface elements, including menus, drop down lists, choose lists, trees, drag and drop elements, etc. In some embodiments, the configuration tool 320 includes any type and form of setup, configuration or installation wizards to guide a user step by step through a setup, configuration or installation of a lighting network 175 or any component thereof, such as a UIM 102.
In some embodiments, the CSP 120 is used to configure a UIM or the lighting network and not to operate a UIM or a portion of the lighting network. Therefore, in these embodiments, once the CSP configures each UIM on the network, the CSP may no longer be required and the UIM and linked LCMs will function together as predefined by the CSP. In other embodiments, the CSP 120 may used during operation of the UIM or lighting network to dynamically change the configuration or logic of the UIM on the fly or on an as needed or ad-hoc basis. In one embodiment, the CSP 120 may be used as a testing tool for any UIM or any portion of the lighting network to test the functionality, logic or operations to what may be expected.
The configuration tool 320 of the CSP may include any of the following features such as: 1) drag and drop components (UIM, LCM) and component functionality, 2) drag and drop pre created programs, 3) drag and drop analog and digital inputs, 4) create rules 350 with no complex programming, and 5) create relationships, no complex programming. Using drag and drop components and pre-defined and configurable component functionality, a user, such as an OEM customer, may fully define the lighting system using setup guides that walk the user through the set up process. Through Drag and Drop icons, the user selects a defined quantity of LCMs and configures each address for functionality. Via the configuration tool 320, these user may review detailed features of a specific LCM while also being able to review the overall system allowing the creation of relationships between these drag and drop components, such as relationships between the LCMs and UIMs. In some cases, in order to link a drag and drop a component for configuring an LCM or UIM, an address, such as a unique address, of the LCM or UIM must be associated with the drag and drop component.
In some embodiments, the configuration tool 320 provides a user interface for configuring one or more rules 350 for a UIM in controlling or managing the lighting network 175. A rule 350 may include any type and form of logic for specifying, defining or otherwise configuring the behavior, action, command or instructions to be performed by the UIM and/or LCM, or any other portion of a lighting network 175, in response to any type and form of input. In some embodiments, a rule 350 triggers, generates or otherwise provides an event based on an input. The input may include any type of analog or digital information or data received via any port of the UIM and/or LCM. For example, the input may include data from one or more sensors interfaced to the UIM. The output or event may include any type and form of directives, commands or instructions to the LCM and/or LED driver. For example, the output may include instructions to change the lighting affect in any manner, such as triggering a sequence of changes to the color of lights in any sequence or combination. In some embodiments, the rules 350 may cause the lighting control and affects thereof to have a relationship with or correspond to input from the external environment. For example, the weather and/or time of day input, or any changes thereof, to the UIM may case a rule 350 to trigger a change in the lighting via the LCM in a configured or desired manner.
The configuration tool 320 may comprise any type and form of business rules, logic, operations or functionality to provide any form of executable instructions 325 to be created, generated or otherwise provided for use by a UIM 102. In some embodiments, the set of executable instructions used by the UIM may be referred to as firmware 325. The executable instructions or firmware 325 may include any type and form of source code, object code, libraries, APIs, header files, data files and configuration files in accordance with the operation of the UIM. These programmed executable instructions may be stored in any type and form of memory of the UIM, such as read-only memory, permanent or semi-permanent memory.
The configuration tool 320 may include a code generation engine for generating code or firmware 325 for the UIM based on the configuration specified by a user via the user interface. The configuration tool 320 may generate the code representing the configuration using any type and form of instruction set, such as C, C++, RISC instruction sets, Basic, assembly language, programming language for microcontrollers, Java, or any vendor proprietary machine language code. The code generation engine may generate source code and then compile the source code into executable form. The configuration tool 320 may include any type and form of download or export functionality to install or otherwise provide the firmware 325 to the UIM such as via interface 214.
By way of example, some of the features of the configurability of the CSP 120 are discussed below. It should be noted that in order to further ease configuration, most of the features as noted below may be asked in a systematic order via a “wizard” setup guide or would be available via drop down menus. Examples of a wizard setup guide will follow in discussions of
When configuring a specific LCM 106, the user interface of the configuration tool 320 may include user interface elements providing configurable to 1) enable or disable each output of the LCM, 2) select or specify a frequency of enabled PWM output, and 3) select or specify a voltage range of enabled analog output. The configuration tool 320 may include drag and drop icons to represent LED Drivers connected to or to be connected to the LCM under configuration. In some embodiments, the configuration tool 320 provides drag and drop icons to represent LEDs 108 connected to or to be connected to the LED drivers. Although generally discussed herein as drag and drop icons any type and form of graphical user interface elements may be used to represent LCMs, LED drivers and LEDs using the configuration tool.
Via the user interface of the configuration tool 320, a user may view the following types of data and relationships in connection with an LCM 106: 1) which UIM module is this particular LCM linked to, 2) which LCM modules are similar in configuration, 3) which LCM modules are connected to the same UIM modules. In some embodiments, the user may view the address 220 of an LCM via the configuration tool and change or modify this address. The configuration tool 320 may allow the user to assemble LEDs and LED drivers such that the overall function as configured may be simulated prior to exporting code to the UIM. When configuring a specific UIM, the user interface of the configuration tool 320 may provide user interface elements for the assignment of LCMs to the specific UIM. In some embodiments, this assignment of LCMs to UIMs may be done graphically via a linking element. In other embodiments, the assignment of LCMs to UIMs may be performed by the user via selection from a choose list or drop down list of via text or other entry. The configuration tool 320 may provide a user interface to define any of the inputs of the UIMs. In some embodiments, the inputs may be available as drag and drop icons, for example, if a temperature sensor is selected, simply drag in a temperature sensor and connect. The configuration tool 320 may provide a user interface to define the function of an LCM once the UIM receives an input, such as via one or more rules 350. The configuration tool 320 allows a user to view, configure or change the address of this particular UIM and also see when the address may have been last updated.
In some embodiments, once the function, operating, and relationship parameters are defined for the UIM in advance via the CSP 120, the UIM will function or act as an embedded system with the purpose of operating as defined. In addition and in one embodiment, any LCM assigned to the UIM will be notified via the LCM's address of its purpose and commands. For example, upon power up of the UIM and applicable LCMs, the UIM may notify all LCMs that are assigned thereto of the LCM's respective configuration. If the LCM loose power, the LCMs may hold the previous state until connection is reestablished. If the LCM fails to connect to a UIM, the UIM may indicate an error code and continue to operate normally less the missing component.
Once the overall system definition has been completed, the possible lighting effects are endless. A user may create any combination of configurations for UIMs and LCMs for a lighting network 175 with any type and form of rules 350 that may be supported by the system. The rules 350 provides any desired lighting effects based on inputs available to the UIM and output control provided by the LCM and LED drivers. While the interface is a relative simple GUI, some users may prefer templates or pre-created configuration for getting started. In some embodiments, the configuration tool 320 provides drag and drop pre-created, pre-defined or otherwise predetermined programs or configurations. A user may drag and drop via the configuration tool a program similar to that of which is trying to be accomplished. In addition to drag and drop, the CSP 120 will attempt to apply the sequence to the Lighting Network as defined, prompting the user for input and by analyzing the devices present. For example, a user may select a pre-created program for “Chasing Lights”. At that point, the CSP may prompt the user via a survey to select options regarding the overall effect, thus at the completion of the customer survey, the Chasing Lights program also having recognized the quantity of LCMs will have created any desired or suitable program per the user requirements. The program may be further modified such as via tweaking of time values, intensity values, etc. . . .
As the UIM includes capability for various inputs, whether sensor, switch, or data, the configuration tool 320 may be designed or constructed such that inputs may be dragged and dropped into the graphical user interface and assigned to the applicable UIM. Through this assignment, the user may be informed of features available such as data that may be referenced and used accordingly in the associated programs. For example, with an “Internet” digital input, the user may have accessible: weather data, stock information, sun rise times, sun set times, sports scores, etc. Any of the Internet data may be queried or obtained via any network or Internet connected computing device, such as a server available to the UIM. The configuration tool 320 may provide the user with the option to select which of this data is relevant to the program or desired to use with the rules 350.
For example, the UIM 102 may have access via the Internet port any data and information on the local weather, including temperature data, such as the local high temperature for the day and the local low temperature for the day. In this case, the user may select the local high and local low temperatures for the day as data input such that this data may be available in a field for configuration. The user may then create rules 250 or a program 325 such that this data is used as a variable for creating a lighting effect via the UIM and the lighting network. In some embodiments, each UIM may have a defined number of potential inputs and that multiple inputs may be incorporated into the configuration of the UIM. For example, when a switch connected to a UIM is engaged, weather data may available as input to a rule 350. When a switch is disengaged, the UIM may run a pre-defined program.
In addition to defining the configuration of the UIM and LCM within a lighting network, the configuration tool 320 of the CSP provides a user interface for a user to create rules and relationships. For example, a rule 250 may be configuration of an “IF” statement whiles relationships being may be for example how an LCM at a first address interacts with the UIM of a second address. Rules may be configured via “wizard” configuration or may be configured via scripting depending on the experience of the user. In some embodiments, a rule 350 creates a definition or otherwise established a relationship that links the input on the UIM to the output of one or more LCMs. For example, a rule may created that specified if the local high temperature for the day exceeds 70 F, then set LCM at the first address to “pink light”. This pink light for example may have been defined earlier by the user via the configuration tool 320 as the combination of 50% intensity of PWM output 1 and 75% intensity of PWM output 2, which in turn mixes blue and red to create pink.
Other rules may be created based on the variable input data available to the UIM. In addition, rules may be created that are triggered by the input data into the UIM and perform a plurality of actions. For example, a rule 350 may specify if the local high temperature for the day exceeds 70 F, then set LCM at a first address to “pink light”, set LCM at a second address to “blue light”, and LCM at a third address to “yellow light”; hold this state for 2 seconds, then run a lighting effects program identified as Chase 3. For example, Chase 3 rule or program may have been defined through the wizard as a program that would start LCM 1 at TBD color, then chance the color of LCM 1 to the color of LCM 3, the color of LCM 3 to LCM 2, the color of LCM 2 to LCM 1 and cycle over a period of 1 second.
The advantages of the CSP 120 and configuration tool 320 is the ability for pre-set or predetermined designs and intelligent setup guides/wizards to guide the user through the configuration process as well as making intelligent decisions as to what components of the setup may be automated and what components should be asked of the user. In some embodiments, the configuration tool 320 or CSP 120 may have an advanced scripting mode which works well for more technology savvy users, such that via a programming language, script or command line commands configure any portion of the lighting network 175 as desired.
Through the use of intelligent configuration menus, the configuration tool 320 of the CSP 120 asks the user questions regarding the system configuration that lead to additional questions based on the user's responses. This type of menu configuration is demonstrated by example via the corresponding embodiments depicts in
Referring now to
Next, at
At a next step in the wizard configuration process of the configuration tool 320, the user may configure the UIM 102. In the example embodiment of the user interface depicted in
Based on the number of user interfaces specified in the screen of
Referring now to
Although
Referring now to
Once the user is satisfied with the configuration, the user may select an export button of the configuration tool 320 to download, upload, export or otherwise transmit the corresponding firmware 325 or configuration updates to the UIM 320. In some embodiments, the selection of the export button triggers a code generation process for the CSP 120 to generate executable instructions or firmware 325 corresponding to the completed configuration for the UIM. Upon completion of the generated code, the CSP may download or provide the code to the UIM via interface 214.
D. Methods for Configuring and Executing User Specified Rules to Control Lighting
Referring now to
In further details, at step 405, a user identifies, via a configuration tool, any type and format of one or more inputs to an interface module for configuring a rule. A user identified input may comprise any data type or a portion of a data stream. The input may include a specific value of a specific data type out of plurality of data types available on the interface module. The user may identify any input selected from a plurality of inputs available via any part or interface of the interface module. In some embodiments, the user identifies a threshold value to be compared against a stream of values from a source, such as a detector or a sensor. The user identified threshold value for the value from the sensor may be the input identified by the user to be used for configuring a rule. In some embodiments, the user identifies a color of light as an input for configuring a rule. In a number of embodiments, the user identifies a value corresponding to a brightness level as an input configuring a rule. In a number of embodiments, the user identifies a source or a stream of data from a website or a webpage as an input for configuring a rule. In some embodiments, the user identifies an analog or a digital value as an input for configuring a rule. In some embodiments, the user identifies a data point as an input to be used for configuring a rule. Sometimes, the user may identify a color, a luminance value or a brightness value to be used as an input for configuring a rule.
In a variety of embodiments, the user identifies a stream of data from a website as an input for configuring a rule. For example, the stream of data identified may correspond to a weather information about a particular location. In some embodiments, the user identifies a stream of data corresponding to a stock information from the stock market as an input for configuring a rule. In identifying the input, the user may specify the port or interface of the interface module and/or one or more data values received via the port or the interface. In some embodiments, in identifying the input the user specifies a data stream from a plurality of streams of data inputs and further specify one or more specific data points within the selected stream. The user may identify any data or value to be received via any type and form of network interface to the interface module. In some embodiments, the user identifies any portion of a network packet as an input. The user may identify or specify any part or a header of a network packet of any type and form of protocol. The user may identify from plurality of data streams traversing the interface module, a data stream based on a unique identifier of the source of the data stream and further identify specific network packets or data to be used as inputs. In some embodiments, the user identifies a voltage value, such as a 0V or a 10V value as an user input for configuring a rule. In some embodiments, the user identifies a value corresponding to a threshold value for a motion sensor as an input for configuring the rule. In many embodiments, the user identifies a value corresponding to a threshold value for a temperature sensor as an input for configuring the rule. In some embodiments, the user identifies a value corresponding to a threshold value for a timer as an input for configuring the rule.
At step 410, the user via the configuration tool specifies any type and form of lighting effects for the rule to trigger responsive to the user identified inputs. The lighting effects may include any one or more of the following, in any combination: turning lights on or off, introducing delay to turning light on or off or to any other lighting effect, timing loops for managing a plurality of light sources, color changes, changes to temperature of one or more lights, dimming, fading of lights, change of intensity, brightness, or wavelength, pulsing of light, flash of light and more. In some embodiments, the user specifies via the configuration tool the intensity or wavelength of the light to be emitted in response to one or more user identified inputs. In many embodiments, the user specifies the continuous light output or a pulsing of light output to be emitted in response to one or more user identified inputs. In various embodiments, the user specifies via the configuration tool a number of colors of light to be emitted from a number of light sources in response to one or more user identified inputs. In some embodiments, the user specifies a sequence of lights to be emitted, such as for example a sequence to emit a green light, followed by a red light, followed by a yellow, etc. In a number of embodiments, the user specifies via the configuration tool a loop sequence assigning the order in which specific light sources will emit when the user identified input is encountered. In some embodiments, the user specifies via the configuration tool the pulse duration for the pulses of light the light sources will emit in response to one or more user identified inputs. In many embodiments, the user specifies the timing scheme for the synchronized output of a plurality of light sources. The timing scheme may specify duration of time for which each light source will emit in response to one or more user identified inputs. Sometimes, the user may specify a first lighting effect to take place in response to a first user identified input and a second lighting effect to take place in response to a second user identified input. In some embodiments, the user specifies a third and fourth lighting effects for the rule to trigger in response to a third user identified input. In many embodiments, the user specifies a specific lighting effect for the rule to trigger in response to two user identified inputs. In some embodiments, the user specifies a lighting effect requiring one or more controllers controlling plurality of light sources to turn the plurality of light sources on or off in a specific order. In many embodiments, the rule may instruct one or more LCMs to implement one or more lighting effects via any number of light sources.
At step 415, the configuration tool generates one or more user specified rules in a form of executable instructions to execute via the interface module or any component of the lighting network. In some embodiments, the configuration tool generates any number of rules in any type and form of executable instructions, such as an executable file, application, program, library, process, script or service. In many embodiments, the configuration tool generates one or more rules in a form of a source code. In some embodiments, the configuration tool generates one or more rules in a form of a compiled code. In various embodiments, the configuration tool generates one or more rules in a form of an executable file. The configuration tool may generate any number of rules in a form of a script. In some embodiments, the configuration tool generates one or more rules in a form of a library of rules. In many embodiments, the configuration tool generates one or more rules in a form of functions ready to be implemented. In some embodiments, the configuration tool generates one or more rules in a form of an interpreted code, such as java code or a java script. In a plurality of embodiments, the configuration tool generates one or more user specified rules in a form of functions, logic functions or procedures to execute the rules.
In some embodiments, at step 415, the configuration tool generates executable instructions for the user specified rule to represent a specific user identified input. In some embodiments, the configuration tool generates a rule in a form of user executable instructions to represent a specific user specified lighting effect. The configuration tool may generate one or more of executable instructions of the user specified rule to be executed by one or more controllers of the LEDs 108, such as an LCM 106. In some embodiments, the configuration tool generates executable files comprising functions, signals and instructions from components such as sensors or detectors, algorithms or software, circuitry or controllers used to operate or control any one of UIM 102, LCM 106, LED drivers 107 and LEDs 108. Each of the executable files may be executed by one or more control modules, such as LCM 106, one or more LED drivers 107 or one or more LED 108. In some embodiments, the configuration tool generates a rule comprising an executable program or a code comprising steps, commands, instructions and data enabling a control module, such as a LCM 106, to implement, trigger or execute each user specified lighting effect. In a plurality of embodiments, the configuration tool generates a rule comprising an executable program or a code comprising steps, commands, instructions and data enabling a control module, such as a LCM 106, to implement, trigger or execute each user identified input. The generated rules may comprise information specifying which LED 108 sources will be utilized, which LCM 106 control modules will be utilized and when. The generated rules may be stored by the interface module for further use in case the user identifies same user inputs or same user specified lighting effects. The generated rules may be created or generated each time the user identifies new inputs or specifies new lighting effects.
At step 420, the interface module receives or is provided the executable instructions comprising the user specified rule via any type and form of interface. The interface module may receive executable instructions comprising the user specified rule via any configuration file, boot file, uploaded or downloaded file, file received via a network or from a file stored on the interface module. In some embodiments, the interface module receives or is provided the executable instructions comprising one or more user specified rules from the configuration tool. In many embodiments, the interface module receives or is provided the executable instructions comprising one or more user specified rules from a user's computer via a network 104. In some embodiments, the interface module receives or is provided the executable instructions from configuration files stored on a network. In some embodiments, the interface module receives or is provided executable files by loading boot files. In some embodiments, the interface module is provided executable files via a file transfer protocol (FTP) transmission. In a number of embodiments, the interface module receives or is provided the executable instructions over the network 104. Sometimes, the configuration tool provides the executable instructions to the interface module over the network 104. Sometimes, the user takes the executable instructions from the configuration software and provides them to the interface module.
At step 425, in operation of the interface module, the interface module receives data via one or more ports or interfaces. The interface module may receive a plurality of streams of data via any number of communication means. The data received by the interface module may comprise any stream of data, stream of values or readings, instructions, commands, signals, calibration values or any data points traversing the interface module. In some embodiments, the interface module receives data from a plurality of sources, such as sensors, circuits, controllers, websites comprising data from stock markets or weather, and more. The interface module may monitor the data as the data traverses the module. The interface module may differentiate data from one data source from data from another data source. The data traversing the interface module may include any number of instructions which may be used to control, command or operate any one of the interface module, control module, such as a LCM 106, driver, such as a LED driver 107 or a lighting source, such as a LED 108. The interface module may receive data, instructions or signals via any communication means. In some embodiments, the interface module includes one or more communication ports receiving commands, instructions or data via a network port, such as a modem connected to network 104. In a number of embodiments, the interface module includes one or more wireless communication links which receive commands, instructions or data via a wireless signal or a wireless port. In some embodiments, the interface module receives data via a port receiving a radio signal or a radio wave. In a number of embodiments, the interface module receives data via a port receiving a satellite signal. In a plurality of embodiments, the interface module receives data via a plurality of ports of the same or different kinds. In a number of embodiments, the interface module receives data via any number of ports from any one, or any combination of a configuration tool, LCM 106, LED 107 or LED 108.
At step 430, the interface module detects from any of the received data from any of its ports the user identified input of the rule. The interface module may detect the user identified input from the received data using any detection or matching technique. In some embodiments, the interface module detects the user identified input by reading, parsing and interpreting data received such as portions of a network packet or one or more data values. In some embodiments, the interface module identifies the user identified input from the received data by parsing the received data and matching the parsed data to the user identified input. In some embodiments, the interface module detects from a plurality of data traversing the interface module the user identified input. In some embodiments, the user identified input is detected from a stream of data from a plurality of streams of data traversing the interface module. In some embodiments, the interface module detects from a network port a first user identified input, and from another communication port a second user identified input. In some embodiments, the interface module detects a plurality of user identified inputs from a variety of data streams or data sources traversing the interface module via any number of communication ports. In a plurality of embodiments, the interface module detects from the received data a plurality of user identified inputs of the rule. In some embodiments, the interface module detects a plurality of user identified inputs from a plurality of portions of data received from a plurality of interface module communication ports.
At step 435, the interface module, responsive to the detection of the user identified input of the rule, executes the rule. The interface module and/or any other component of the lighting network may execute any executable instruction of the user specified rule or any portion thereof. In some embodiments, the interface module executes the rule. In many embodiments, the LCM executes the rule. In many embodiments, the interface module executes a first part of the rule and another component of the lighting network executes a second portion of the rule. In some embodiments, the interface module instructs a component, such as a LCM, to execute the rule. In some embodiments, the interface module is already executing the executable instruction of the user specified rule to detect the user specified input. Upon detection, additional instructions, logic, operating or functions of the executable instruction are executed. In some embodiments, the interface module executes the rule generated in response to the detection of the user specified input. In many embodiments, the interface module executes the rule generated in response to a portion of data received by the interface module. In some embodiments, the interface module creates or generates the rule in response to a portion of data received by the interface module. In a number of embodiments, the interface module modifies the rule generated in response to a portion of data received by the interface module. The interface module may modify the rule generated in response to an input, a command, a signal or an instruction from the data received by the interface module. The interface module may execute the modified rule.
At step 440, the interface module, responsive to execution of the rule, causes the triggering of the one or more lighting effects specified by the rule via any type and form of interface to one or more control modules, such as a LCM 106. In some embodiments, the interface module causes triggering of the lighting effects via any component of the lighting network. In some embodiments, the interface module triggers one or more lighting effects specified by the rule via the control module such as an LCM 106, a driver such as a LED driver 107 or a lighting source such as a LED 108. In many embodiments, the interface module triggers one or more lighting effects specified by the rule via any number or any type of lighting network components, such as any number of LCMs, LEDs and more. In some embodiments, the interface module transmits one or more of the executable instructions to the LCM 106 to specify, control or instruct the LCM 106 to execute the lighting effects specified by the user. The interface module may, in response to the execution of the rule, transmit one or more executable instructions to a component or a device on the lighting network 175 to trigger the execution of the one or more user specified lighting effects. In some embodiments, the interface module, responsive to the execution of the rule, causes triggering of the one or more lighting effects specified by the rule according to the identified inputs by the user. In some embodiments, the interface module, responsive to the execution of the rule, causes triggering of the one or more lighting effects specified by the modified rule. In some embodiments, the rule triggers one or more other rules to be executed by any number of lighting network components.
The present application claims priority to U.S. Provisional Application No. 60/974,721 filed on Sep. 24, 2007, herein incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4139770 | Beyersdorf | Feb 1979 | A |
| 5264997 | Hutchisson et al. | Nov 1993 | A |
| 5465199 | Bray et al. | Nov 1995 | A |
| 5561346 | Byrne | Oct 1996 | A |
| 5659582 | Kojima et al. | Aug 1997 | A |
| 5783909 | Hochstein | Jul 1998 | A |
| 5803579 | Turnbull et al. | Sep 1998 | A |
| 5909429 | Satyanarayana et al. | Jun 1999 | A |
| 5947587 | Keuper et al. | Sep 1999 | A |
| 6013988 | Bucks et al. | Jan 2000 | A |
| 6016038 | Mueller et al. | Jan 2000 | A |
| 6040663 | Bucks et al. | Mar 2000 | A |
| 6094014 | Bucks et al. | Jul 2000 | A |
| 6127783 | Pashley et al. | Oct 2000 | A |
| 6147458 | Bucks et al. | Nov 2000 | A |
| 6150774 | Mueller et al. | Nov 2000 | A |
| 6157093 | Giannopoulos et al. | Dec 2000 | A |
| 6166496 | Lys et al. | Dec 2000 | A |
| 6194839 | Chang | Feb 2001 | B1 |
| 6201353 | Chang et al. | Mar 2001 | B1 |
| 6211626 | Lys et al. | Apr 2001 | B1 |
| 6234645 | Borner et al. | May 2001 | B1 |
| 6234648 | Borner et al. | May 2001 | B1 |
| 6236331 | Dussureault | May 2001 | B1 |
| 6238065 | Jones | May 2001 | B1 |
| 6249088 | Chang | Jun 2001 | B1 |
| 6250774 | Begemann et al. | Jun 2001 | B1 |
| 6253530 | Price et al. | Jul 2001 | B1 |
| 6288497 | Chang et al. | Sep 2001 | B1 |
| 6292901 | Lys et al. | Sep 2001 | B1 |
| 6299329 | Mui et al. | Oct 2001 | B1 |
| 6304464 | Jacobs et al. | Oct 2001 | B1 |
| 6305818 | Lebens et al. | Oct 2001 | B1 |
| 6340864 | Wacyk | Jan 2002 | B1 |
| 6340868 | Lys et al. | Jan 2002 | B1 |
| 6384545 | Lau | May 2002 | B1 |
| 6411046 | Muthu | Jun 2002 | B1 |
| 6441558 | Muthu et al. | Aug 2002 | B1 |
| 6443592 | Unger et al. | Sep 2002 | B1 |
| 6445139 | Marshall et al. | Sep 2002 | B1 |
| 6459919 | Lys et al. | Oct 2002 | B1 |
| 6489731 | Bruning et al. | Dec 2002 | B1 |
| 6495964 | Muthu et al. | Dec 2002 | B1 |
| 6507158 | Wang | Jan 2003 | B1 |
| 6507159 | Muthu | Jan 2003 | B2 |
| 6510995 | Muthu et al. | Jan 2003 | B2 |
| 6513949 | Marshall et al. | Feb 2003 | B1 |
| 6528954 | Lys et al. | Mar 2003 | B1 |
| 6552495 | Chang | Apr 2003 | B1 |
| 6576881 | Muthu et al. | Jun 2003 | B2 |
| 6577080 | Lys et al. | Jun 2003 | B2 |
| 6577512 | Tripathi et al. | Jun 2003 | B2 |
| 6580309 | Jacobs et al. | Jun 2003 | B2 |
| 6586890 | Min et al. | Jul 2003 | B2 |
| 6596977 | Muthu et al. | Jul 2003 | B2 |
| 6608453 | Morgan et al. | Aug 2003 | B2 |
| 6609813 | Showers et al. | Aug 2003 | B1 |
| 6617795 | Bruning | Sep 2003 | B2 |
| 6621235 | Chang | Sep 2003 | B2 |
| 6630801 | Schuurmans | Oct 2003 | B2 |
| 6636003 | Rahm et al. | Oct 2003 | B2 |
| 6639368 | Sheoghong | Oct 2003 | B2 |
| 6676284 | Wynne Willson | Jan 2004 | B1 |
| 6692136 | Marshall et al. | Feb 2004 | B2 |
| 6720745 | Lys et al. | Apr 2004 | B2 |
| 6724159 | Gutta et al. | Apr 2004 | B2 |
| 6734639 | Chang et al. | May 2004 | B2 |
| 6741351 | Marshall et al. | May 2004 | B2 |
| 6762562 | Leong | Jul 2004 | B2 |
| 6777891 | Lys et al. | Aug 2004 | B2 |
| 6788011 | Mueller et al. | Sep 2004 | B2 |
| 6796680 | Showers et al. | Sep 2004 | B1 |
| 6796686 | Jacob et al. | Sep 2004 | B2 |
| 6801003 | Schanberger et al. | Oct 2004 | B2 |
| 6806659 | Mueller et al. | Oct 2004 | B1 |
| 6831569 | Wang et al. | Dec 2004 | B2 |
| 6853150 | Clauberg et al. | Feb 2005 | B2 |
| 6853151 | Leong et al. | Feb 2005 | B2 |
| 6859644 | Wang | Feb 2005 | B2 |
| 6922022 | Bucks et al. | Jul 2005 | B2 |
| 6930452 | De Krijger et al. | Aug 2005 | B2 |
| 6932477 | Stanton | Aug 2005 | B2 |
| 6933685 | Gutta et al. | Aug 2005 | B2 |
| 6933767 | Bucks et al. | Aug 2005 | B2 |
| 6965205 | Piepgras et al. | Nov 2005 | B2 |
| 6969954 | Lys | Nov 2005 | B2 |
| 6972525 | Bucks et al. | Dec 2005 | B2 |
| 6975079 | Lys et al. | Dec 2005 | B2 |
| 6992803 | Chang | Jan 2006 | B2 |
| 6998594 | Gaines et al. | Feb 2006 | B2 |
| 7014336 | Ducharme et al. | Mar 2006 | B1 |
| 7030572 | Nijhof et al. | Apr 2006 | B2 |
| 7031920 | Dowling et al. | Apr 2006 | B2 |
| 7038398 | Lys et al. | May 2006 | B1 |
| 7038399 | Lys et al. | May 2006 | B2 |
| 7064498 | Dowling et al. | Jun 2006 | B2 |
| 7067992 | Leong et al. | Jun 2006 | B2 |
| 7071762 | Xu et al. | Jul 2006 | B2 |
| 7113541 | Lys et al. | Sep 2006 | B1 |
| 7118248 | Wynne Willson | Oct 2006 | B2 |
| 7132804 | Lys et al. | Nov 2006 | B2 |
| 7135824 | Lys et al. | Nov 2006 | B2 |
| 7139617 | Morgan et al. | Nov 2006 | B1 |
| 7140752 | Ashdown | Nov 2006 | B2 |
| 7161311 | Mueller et al. | Jan 2007 | B2 |
| 7161313 | Piepgras et al. | Jan 2007 | B2 |
| 7161556 | Morgan et al. | Jan 2007 | B2 |
| 7178941 | Roberge et al. | Feb 2007 | B2 |
| 7180252 | Lys et al. | Feb 2007 | B2 |
| 7186003 | Dowling et al. | Mar 2007 | B2 |
| 7202608 | Robinson et al. | Apr 2007 | B2 |
| 7202613 | Morgan et al. | Apr 2007 | B2 |
| 7202641 | Claessens et al. | Apr 2007 | B2 |
| 7204622 | Dowling et al. | Apr 2007 | B2 |
| 7221104 | Lys et al. | May 2007 | B2 |
| 7228190 | Dowling et al. | Jun 2007 | B2 |
| 7231060 | Dowling et al. | Jun 2007 | B2 |
| 7233115 | Lys | Jun 2007 | B2 |
| 7233831 | Blackwell | Jun 2007 | B2 |
| 7242152 | Dowling et al. | Jul 2007 | B2 |
| 7253566 | Lys et al. | Aug 2007 | B2 |
| 7255457 | Ducharme et al. | Aug 2007 | B2 |
| 7255458 | Ashdown | Aug 2007 | B2 |
| 7256554 | Lys | Aug 2007 | B2 |
| 7262559 | Tripathi et al. | Aug 2007 | B2 |
| 7267461 | Kan et al. | Sep 2007 | B2 |
| 7274160 | Mueller et al. | Sep 2007 | B2 |
| 7300192 | Mueller et al. | Nov 2007 | B2 |
| 7308296 | Lys et al. | Dec 2007 | B2 |
| 7309965 | Dowling et al. | Dec 2007 | B2 |
| 7314289 | Montagne | Jan 2008 | B2 |
| 7319298 | Jungwirth et al. | Jan 2008 | B2 |
| 7323676 | Duijve | Jan 2008 | B2 |
| 7329998 | Jungwirth | Feb 2008 | B2 |
| 7350936 | Ducharme et al. | Apr 2008 | B2 |
| 7352138 | Lys et al. | Apr 2008 | B2 |
| 7352339 | Morgan et al. | Apr 2008 | B2 |
| 7353071 | Blackwell et al. | Apr 2008 | B2 |
| 7354172 | Chemel et al. | Apr 2008 | B2 |
| 7358679 | Lys et al. | Apr 2008 | B2 |
| 7358681 | Robinson et al. | Apr 2008 | B2 |
| 7358706 | Lys | Apr 2008 | B2 |
| 7358929 | Mueller et al. | Apr 2008 | B2 |
| 7358961 | Zwanenburg | Apr 2008 | B2 |
| 7387405 | Ducharme et al. | Jun 2008 | B2 |
| 7388665 | Ashdown | Jun 2008 | B2 |
| 7394210 | Ashdown | Jul 2008 | B2 |
| 7420335 | Robinson et al. | Sep 2008 | B2 |
| 7423387 | Robinson et al. | Sep 2008 | B2 |
| 7432668 | Zwanenburg et al. | Oct 2008 | B2 |
| 7443209 | Chang | Oct 2008 | B2 |
| 7449847 | Schanberger et al. | Nov 2008 | B2 |
| 7453217 | Lys et al. | Nov 2008 | B2 |
| 7459864 | Lys | Dec 2008 | B2 |
| 7462997 | Mueller et al. | Dec 2008 | B2 |
| 7463070 | Wessels | Dec 2008 | B2 |
| 7482565 | Morgan et al. | Jan 2009 | B2 |
| 7482760 | Jungwirth et al. | Jan 2009 | B2 |
| 7490953 | Holten et al. | Feb 2009 | B2 |
| 7490957 | Leong et al. | Feb 2009 | B2 |
| 7495671 | Chemel et al. | Feb 2009 | B2 |
| 7502034 | Chemel et al. | Mar 2009 | B2 |
| 7505395 | Ashdown et al. | Mar 2009 | B2 |
| 7507001 | Kit | Mar 2009 | B2 |
| 7511436 | Xu | Mar 2009 | B2 |
| 7511437 | Lys et al. | Mar 2009 | B2 |
| 7515128 | Dowling | Apr 2009 | B2 |
| 7520634 | Ducharme et al. | Apr 2009 | B2 |
| 7521872 | Bruning | Apr 2009 | B2 |
| 7525254 | Lys et al. | Apr 2009 | B2 |
| 7538499 | Ashdown | May 2009 | B2 |
| 7542257 | McCormick et al. | Jun 2009 | B2 |
| 7550931 | Lys et al. | Jun 2009 | B2 |
| 7550935 | Lys et al. | Jun 2009 | B2 |
| 7557521 | Lys | Jul 2009 | B2 |
| 7569807 | Matheson | Aug 2009 | B2 |
| 7572028 | Mueller et al. | Aug 2009 | B2 |
| 7573209 | Ashdown et al. | Aug 2009 | B2 |
| 7573210 | Ashdown et al. | Aug 2009 | B2 |
| 7573729 | Elferich et al. | Aug 2009 | B2 |
| 7598681 | Lys et al. | Oct 2009 | B2 |
| 7598684 | Lys et al. | Oct 2009 | B2 |
| 7598686 | Lys et al. | Oct 2009 | B2 |
| 7619370 | Chemel et al. | Nov 2009 | B2 |
| 7652236 | Cortenraad et al. | Jan 2010 | B2 |
| 7654703 | Kan et al. | Feb 2010 | B2 |
| 7656366 | Ashdown | Feb 2010 | B2 |
| 7658506 | Dowling | Feb 2010 | B2 |
| 7659673 | Lys | Feb 2010 | B2 |
| 7659674 | Mueller et al. | Feb 2010 | B2 |
| 7665883 | Matheson | Feb 2010 | B2 |
| 7667409 | Geerts et al. | Feb 2010 | B2 |
| 7675238 | Cortenraad et al. | Mar 2010 | B2 |
| 7687753 | Ashdown | Mar 2010 | B2 |
| 7688002 | Ashdown et al. | Mar 2010 | B2 |
| 7689130 | Ashdown | Mar 2010 | B2 |
| 7703951 | Piepgras et al. | Apr 2010 | B2 |
| 7710369 | Dowling | May 2010 | B2 |
| 7712926 | Matheson | May 2010 | B2 |
| 7714521 | Qian | May 2010 | B2 |
| 7731387 | Cortenraad et al. | Jun 2010 | B2 |
| 7731389 | Draganov et al. | Jun 2010 | B2 |
| 7731390 | Van Gorkom et al. | Jun 2010 | B2 |
| 7737643 | Lys | Jun 2010 | B2 |
| 7738002 | Ashdown et al. | Jun 2010 | B2 |
| 7740375 | Zou et al. | Jun 2010 | B2 |
| 7766489 | Duine et al. | Aug 2010 | B2 |
| 7766518 | Piepgras et al. | Aug 2010 | B2 |
| 7772787 | Ashdown et al. | Aug 2010 | B2 |
| 7777427 | Stalker, III | Aug 2010 | B2 |
| 7781979 | Lys | Aug 2010 | B2 |
| 7802902 | Moss et al. | Sep 2010 | B2 |
| 7806558 | Williamson | Oct 2010 | B2 |
| 7808191 | Wu | Oct 2010 | B2 |
| 7809448 | Lys et al. | Oct 2010 | B2 |
| 7810974 | Van Rijswick et al. | Oct 2010 | B2 |
| 7845823 | Mueller et al. | Dec 2010 | B2 |
| 7850347 | Speier et al. | Dec 2010 | B2 |
| 7854539 | Van Duijneveldt | Dec 2010 | B2 |
| 7868562 | Salsbury et al. | Jan 2011 | B2 |
| 7878683 | Logan et al. | Feb 2011 | B2 |
| 7878688 | Paulussen et al. | Feb 2011 | B2 |
| 7893631 | Speier | Feb 2011 | B2 |
| 7893661 | Ackermann et al. | Feb 2011 | B2 |
| 7894050 | Ashdown et al. | Feb 2011 | B2 |
| 7906917 | Tripathi et al. | Mar 2011 | B2 |
| 7911151 | Xu | Mar 2011 | B2 |
| 7914173 | Paulussen et al. | Mar 2011 | B2 |
| 8022632 | Schulz et al. | Sep 2011 | B2 |
| 8026673 | Lys | Sep 2011 | B2 |
| 20020074559 | Dowling et al. | Jun 2002 | A1 |
| 20030132721 | Jacobs et al. | Jul 2003 | A1 |
| 20030133292 | Mueller et al. | Jul 2003 | A1 |
| 20040052076 | Mueller et al. | Mar 2004 | A1 |
| 20040090191 | Mueller et al. | May 2004 | A1 |
| 20040178751 | Mueller et al. | Sep 2004 | A1 |
| 20050236998 | Mueller et al. | Oct 2005 | A1 |
| 20050275626 | Mueller et al. | Dec 2005 | A1 |
| 20060002110 | Dowling et al. | Jan 2006 | A1 |
| 20060022214 | Morgan et al. | Feb 2006 | A1 |
| 20060076908 | Morgan et al. | Apr 2006 | A1 |
| 20060114201 | Chang | Jun 2006 | A1 |
| 20060152172 | Mueller et al. | Jul 2006 | A9 |
| 20060221606 | Dowling | Oct 2006 | A1 |
| 20060262521 | Piepgras et al. | Nov 2006 | A1 |
| 20060274526 | Weston et al. | Dec 2006 | A1 |
| 20060290624 | Ashdown | Dec 2006 | A1 |
| 20070063658 | Van Der Veeken | Mar 2007 | A1 |
| 20070086912 | Dowling et al. | Apr 2007 | A1 |
| 20070115658 | Mueller et al. | May 2007 | A1 |
| 20070145915 | Roberge et al. | Jun 2007 | A1 |
| 20070153514 | Dowling et al. | Jul 2007 | A1 |
| 20070230159 | Cortenraad et al. | Oct 2007 | A1 |
| 20070258240 | Ducharme et al. | Nov 2007 | A1 |
| 20070273290 | Ashdown et al. | Nov 2007 | A1 |
| 20080042599 | Ashdown | Feb 2008 | A1 |
| 20080043464 | Ashdown | Feb 2008 | A1 |
| 20080048582 | Robinson | Feb 2008 | A1 |
| 20080062413 | Ashdown et al. | Mar 2008 | A1 |
| 20080089060 | Kondo et al. | Apr 2008 | A1 |
| 20080094005 | Rabiner et al. | Apr 2008 | A1 |
| 20080122386 | De Brouwer et al. | May 2008 | A1 |
| 20080136331 | Schmeikal | Jun 2008 | A1 |
| 20080136796 | Dowling | Jun 2008 | A1 |
| 20080140231 | Blackwell et al. | Jun 2008 | A1 |
| 20080164826 | Lys | Jul 2008 | A1 |
| 20080164854 | Lys | Jul 2008 | A1 |
| 20080167734 | Robinson et al. | Jul 2008 | A1 |
| 20080183081 | Lys et al. | Jul 2008 | A1 |
| 20080239675 | Speier | Oct 2008 | A1 |
| 20080265797 | Van Doorn et al. | Oct 2008 | A1 |
| 20080278092 | Lys et al. | Nov 2008 | A1 |
| 20080278941 | Logan et al. | Nov 2008 | A1 |
| 20080290251 | Deurenberg et al. | Nov 2008 | A1 |
| 20080297066 | Meijer et al. | Dec 2008 | A1 |
| 20080298330 | Leitch | Dec 2008 | A1 |
| 20080315798 | Diederiks et al. | Dec 2008 | A1 |
| 20090002981 | Knibbe | Jan 2009 | A1 |
| 20090021175 | Wendt et al. | Jan 2009 | A1 |
| 20090021182 | Sauerlaender | Jan 2009 | A1 |
| 20090072761 | Wessels | Mar 2009 | A1 |
| 20090128059 | Joosen et al. | May 2009 | A1 |
| 20090134817 | Jurngwirth et al. | May 2009 | A1 |
| 20090160364 | Ackermann et al. | Jun 2009 | A1 |
| 20090168415 | Franciscus Deurenberg et al. | Jul 2009 | A1 |
| 20090179587 | Van Der Veen et al. | Jul 2009 | A1 |
| 20090179596 | Willaert et al. | Jul 2009 | A1 |
| 20090189448 | Verschueren | Jul 2009 | A1 |
| 20090224695 | Van Erp et al. | Sep 2009 | A1 |
| 20090230884 | Van Doorn et al. | Sep 2009 | A1 |
| 20090243507 | Lucero-Vera et al. | Oct 2009 | A1 |
| 20090278473 | Van Erp et al. | Nov 2009 | A1 |
| 20090284174 | Sauerlander et al. | Nov 2009 | A1 |
| 20090321666 | Hilgers | Dec 2009 | A1 |
| 20100007600 | Deurenberg et al. | Jan 2010 | A1 |
| 20100026191 | Radermacher et al. | Feb 2010 | A1 |
| 20100045478 | Schulz et al. | Feb 2010 | A1 |
| 20100072901 | De Rijck et al. | Mar 2010 | A1 |
| 20100072902 | Wendt et al. | Mar 2010 | A1 |
| 20100079085 | Wendt et al. | Apr 2010 | A1 |
| 20100079091 | Deixler et al. | Apr 2010 | A1 |
| 20100084995 | Baaijens et al. | Apr 2010 | A1 |
| 20100091488 | Ijzerman et al. | Apr 2010 | A1 |
| 20100094439 | Van De Meulenhof et al. | Apr 2010 | A1 |
| 20100102732 | Peeters et al. | Apr 2010 | A1 |
| 20100117543 | Van Der Veen et al. | May 2010 | A1 |
| 20100117656 | Snelten | May 2010 | A1 |
| 20100118531 | Montagne | May 2010 | A1 |
| 20100127633 | Geerts et al. | May 2010 | A1 |
| 20100134041 | Radermacher et al. | Jun 2010 | A1 |
| 20100134042 | Willaert | Jun 2010 | A1 |
| 20100148689 | Morgan et al. | Jun 2010 | A1 |
| 20100164399 | Radermacher et al. | Jul 2010 | A1 |
| 20100165618 | Vissenberg et al. | Jul 2010 | A1 |
| 20100171771 | Otte et al. | Jul 2010 | A1 |
| 20100181936 | Radermacher et al. | Jul 2010 | A1 |
| 20100188007 | Deppe et al. | Jul 2010 | A1 |
| 20100194293 | Deurenberg et al. | Aug 2010 | A1 |
| 20100231133 | Lys | Sep 2010 | A1 |
| 20100231363 | Knibbe | Sep 2010 | A1 |
| 20100244707 | Gaines et al. | Sep 2010 | A1 |
| 20100244734 | Van Herpen et al. | Sep 2010 | A1 |
| 20100259182 | Man et al. | Oct 2010 | A1 |
| 20100264834 | Gaines et al. | Oct 2010 | A1 |
| 20100271843 | Holten et al. | Oct 2010 | A1 |
| 20100289532 | Wendt et al. | Nov 2010 | A1 |
| 20100301780 | Vinkenvleugel | Dec 2010 | A1 |
| 20100308745 | Delnoij | Dec 2010 | A1 |
| 20110025205 | Van Rijswick et al. | Feb 2011 | A1 |
| 20110025230 | Schulz et al. | Feb 2011 | A1 |
| 20110035404 | Morgan et al. | Feb 2011 | A1 |
| 20110042554 | Hilgers et al. | Feb 2011 | A1 |
| 20110090684 | Logan et al. | Apr 2011 | A1 |
| 20110095694 | Justel et al. | Apr 2011 | A1 |
| 20110285292 | Mollnow et al. | Nov 2011 | A1 |
| 20110291812 | Verbrugh | Dec 2011 | A1 |
| 20120019670 | Chang et al. | Jan 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-03017733 | Feb 2003 | WO |
| Entry |
|---|
| “1-Wire Products Deliver a Powerful Combination . . . ”, Mixed-Signal Design Guide, Dallas Semiconductor Maxim, 2005, 7 pages. |
| “Conductivity with the BS2/OWL2”, EME Systems, 2002, pp. 1-3. |
| “Dimmable Fluorescent Ballast”, ATAVRFBKIT/EVLB001, User Guide, ATMEL, 2007, pp. 1-33. |
| “High-side current sensing for driving a string of white LEDs”, EDN, 1 page. |
| “Understanding Boost Power Stages in Switchmode Power Supplies”, Application Report, Texas Instruments, Mixed Signal Products, Mar. 1999, pp. 1-28. |
| “Understanding Buck Power Stages in Switchmode Power Supplies”, Application Report, Texas Instruments, Mixed Signal Products, Mar. 1999, pp. 1-32. |
| Barberis, C. “Precision current sink costs less than $20”, EDN Design Ideas. |
| Bellcomb Technologies Incoporated, “Edges, Joiners, Attachments, Web Address: http://www.bellcomb.com/caps/edges.htm”, Apr. 22, 2007, pp. 1-3. |
| Bookmarks Menu—Controllers/Wireless—Deisgn Ideas, dated Dec. 6, 2012, 2 pages. |
| Bowling, S. “Buck-Boost LED Driver Using the PIC16F785 MCU”, Microchip, AN1047, 2006, pp. 1-12. |
| By Staff, DALI Delivers Control and Cost Savings, Headaches Too, Consulting-Specifying Engineer, Jun. 2002, 2 pages. |
| Canny, D. “Controlling slew times tames EMI in offline supplies”, EDN Design Ideas, Nov. 14, 2002. |
| Control Freak Addict Data Sheet, Copyright 2008, Creative Lighting, 5 pages. |
| Curtis, K. “High Power IR LED Driver Using the PIC16C781/782”, Microchip, TB062, 2002, pp. 1-8. |
| CybroTech, Managing Lights with Dali, TN-012, rev 2, Cybrotech Ltd., 2007, 11 pgs. |
| Cypress Perform, Implementing an Integrated DMX512 Receiver, Item ID: 39762, Dec. 16, 2009, 1 pg. |
| Cypress Semiconductor Corporation, PowerPSoC (TM) Intelligent LED Driver, Document No. 001-46319, Rev. *G, 2009. |
| Dali-AG website, Dali at work, 1 pg. |
| Davidovic, et al., Lead-Acid Battery Charger Becomes A Subfuction In A Microcontroller, The Authority on Emerging Technologies for Design Solutions, Mar. 2007, 2 pages. |
| Davmark Ltd., Dali-Protocol, 2007, 6 pages. |
| Di Jasio, “A Technique to Increase the Frequency Resolution of PICmicro MCU PWM Modules”, Microchip, AN1050, 2006, pp. 1-10. |
| Dietz, et al. “Very Low-Cost Sensing and Communication Using Bidirectional LEDs”, Mitsubishi Electric Research Laboratories, Jul. 2003, 19 pgs. |
| Distler, T. “LED Effects Stream TM v2.0 Protocol (Revision C)”, Jun. 2, 2005, pp. 1-5. |
| Dunn, J. “Matching MOSFET Drivers to MOSEFTs”, Microchip, AN799, 2004, pp. 1-10. |
| Fosler, R. “The RS-232/DALI Bridge Interface”, Microchip, AN811, 2002, pp. 1-8. |
| Fosler, R. “Use a microcontroller to design a boost converter”, EDN design ideas, Mar. 4, 2004, pp. 74-75. |
| Fosler, R., et al. “Digitally Addressable DALI Dimming Ballast”, Microchip, AN809, 2002, pp. 1-18. |
| Ghulyani, L. “Simple MPPT-Based Lead Acid Charger Using bq2031”, Texas Instruments, Dec. 2009, pp. 1-5. |
| Google Search Results for dali query group, search completed on Apr. 8, 2010, accessed at google.com, http://www.google.com/search?hl=en&c1ient=firefox-a&rls=org.mozilla:en-, 2 pages. |
| Hardwick, M. “DC power wire also carries clock or data”, EDN Design Ideas. |
| Hexcel Composites, “Sandwich Panel Fabrication Technology”, Web Address: http://www.hexcel.com/NR/rdonlyres/B4574C2C-0644-43AC-96E2-CC15967A4b)5/4547 Sandwich Fabrication.pdf, Jan. 1997, pp. 1-16. |
| High-Side Current Monitor, ZETEX, Apr. 2001, ZXCT1009, Issue 3, pp. 1-8. |
| Implementing Infrared Object Detection, http://web.archive.org/web/20080528042614rejwww.seattlerobotics.org/guide/infrared.html, original publication date known, retrieved Apr. 7, 2010, seattlerobotics.org, 4 pages. |
| Jackson, S. “Circuit protects bus from 5V swings”, EDN Design Ideas, Nov. 14, 2002. |
| Klepin, K. “Temperature Compensation for High Brightness LEDs using EZ-Color (TM) and PSoC Express”, Cypress Perform, AN14406, Aug. 10, 2007, pp. 1-4. |
| Kremin, V. et al. “Multichannel LED Dimmer with CapSense Control—AN13943”, Cypress Perform, Jul. 20, 2007. |
| Kropf, B. “Firmware—RGB Color Mixing Firmware for EZ-Color (TM)—AN16035”, Cypress Perform, Jun. 13, 2007, pp. 1-7. |
| Lager, A. “Use a 555 timer as a switch-mode power supply”, EDN Design Ideas, Nov. 14, 2002. |
| Lee, M. Shunt Battery Charger Provides 1A Continuous Current, EDN Magazine, 1997. |
| Locher, R. “Introduction to Power MOSEFETs and their Applications”, Fairchild Semiconductor (TM), Application Note 558, Rev B, Oct. 1998, 15 pgs. |
| Miller, R. “Digital addressable lighting interface protocol fosters systems interoperability for lower costs and greater design flexibility”, RNM Engineering, Inc., Apr. 2003, pp. 1-20. |
| Nell, S. “VCO uses programmable logic”, EDN Design Ideas, Nov. 14, 2002. |
| News & Events DALI Digital addressable lighting interface lamp luminaire control, accessed at http://www.dali-ag.org/ on Apr. 8, 2010, original publication date unknown, updated Apr. 8, 2010, 1 pg. |
| O'Loughlin, M. “350-W, Two-Phase Interleaved PFC Pre-regulator Design Review”, Texas Instruments, Application Report, Revised Mar. 2007, pp. 1-. |
| O'Loughlin, M., PFC Pre-Regulator Frequency Dithering Circuit, Texas Instruments, May 2007, pp. 1-8. |
| Perrin, R. Inexpensive Relays Form Digital Potentiometer, EDN Design Ideas, 1998, 2 pages. |
| Petersen, A. “Harness solar power with smart power-conversion techniques”, EDN, Green Electronics designfeature, Feb. 4, 1999, pp. 119-124. |
| Prendergast, P. “How to Design a Three-Channel LED Driver”, Cypress Perform, Jan. 2008, pp. 1-9. |
| Renesas, R8C/25 Demonstration Example for DALI Lighting Protocol Stack, REU05BOO77-0100/Rev. 1.00, Jul. 2008, 14 pgs. |
| Richardson, C., Matching Driver to LED, National Semiconductor, Jan. 2008, 5 pgs. |
| Richardson. C., LM3404 Driving a Seoul Semi Zpower P4 1A LED-RD-I34, National Semiconductor, Apr. 2007, 6 pages. |
| Shanmugam, S. “Design of a linear Fresnel lens system for solar photovoltaic electrical power source”, Center for Robotics Research. |
| Shill, M. “Simple logic probe uses bicolor LED”, EDN Design Ideas. |
| Software Design Specification, Z-Wave Protocol Overview, Z wave the wireless language, Zensys A/S, May 9, 2007, pp. 1-16. |
| Soundlight, Operating Manual, DALI and DMX Dekoder 7064A-H Mk1, 2008, 8 pgs. |
| Takahashi A., Methods and Features of LED Drivers, National Semiconductor, Mar. 2008, 3 pgs. |
| Universal Powerline Bus Communication Technology, Overview, PCS Powerline Control Systems UPB (Universal Powerline Bus), Jan. 8, 2002, pp. 1-13. |
| UPB Technology Description, PCS—Powerline Control Systems, UPB (Universal Powerline Bus), Version 1.4, Apr. 16, 2007, 68 pages. |
| Use Gate Charge to Design the Gate Drive Circuit for Power MOSEFETs and IGBTs, International Rectifier, Application Note AN-944, 5 pgs. |
| Van Dorsten, Arian, A Low Cost Step-up Converter by IC 555, posted Jul. 21, 2007, http://www.eleccircuit.comla-low-cost-step-up-converter-by-ic-5551, retrieved Apr. 7, 2010, 2 pages. |
| Walma, K., DALI: Forerunner of Today's Breakthrough Lighting Technology, Feb. 2007, 2 pages. |
| Wikipedia, Digital Addressable Lighting Interface, original publication date unknown, Retrieved from:Retrieved from “http://en.wikipedia.org/wikiJDigital—Addressable—Lighting—Interface” accessed on Apr. 8, 2010, 3 pages. |
| Witt, J. “Switched-capacitor regulator provides gain”, EDN Design Ideas. |
| Wojslaw, C. “DPP adds versatility to VFC”, EDN, design ideas, Nov. 14, 2002, pp. 99-110. |
| Young, R. “Power circuit terminates DDR DRAMs”, EDN Design Ideas, Nov. 14, 2002. |
| Zarr, R. Driving High-Power LEDs, Machine Design, Oct. 2007, 3 pages. |
| Zensys ASCII Interface, VIZIA, 2007. |
| Zetex, High-Side Current Monitor, Apr. 2001, Issue 3, 8 pages. |
| Z-Wave Vizia Etc thread, retrieved at http://groups.google.com/group/comp.home.automation/browse—thread/thread/449c2c66934dfSfb/fSI12116a8231aa1?Ink=st&q=z-wave&rnum=98#fSI12116a8231aa1, www.ztech.com, 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20090085500 A1 | Apr 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60974721 | Sep 2007 | US |
