Intelligent illumination device

Information

  • Patent Grant
  • RE50468
  • Patent Number
    RE50,468
  • Date Filed
    Thursday, December 19, 2019
    5 years ago
  • Date Issued
    Tuesday, June 24, 2025
    24 days ago
Abstract
Intelligent illumination device are disclosed that use components in an LED light to perform one or more of a Wide variety of desirable lighting functions for very low cost. The LEDs that produce light can be periodically turned off momentarily, for example, for a duration that the human eye cannot perceive, in order for the light to receive commands optically. The optically transmitted commands can be sent to the light, for example, using a remove control device. The illumination device can use the LEDs that are currently off to receive the data and then configure the light accordingly, or to measure light. Such light can be ambient light for a photosensor function, or light from other LEDs in the illumination device to adjust the color mix.
Description
TECHNICAL FIELD OF THE INVENTION

This invention relates to illumination devices and, more particularly, to controlling illumination devices.


BACKGROUND

Conventional lighting historically has used incandescent and fluorescent bulbs, but recently with the invention of the blue LED, has started to use LED lights. The initial cost of the LED light may be high, but over time the power savings can reduce the overall cost of lighting substantially. Part of the high initial cost of a power efficient LED light is due to the special electronics necessary to create a constant current to the LEDs from a power source. With this special electronics, however, implementation of features such as remote control, dimming, photo-sensing, timing, and color adjustment in the light are possible at very little additional cost. Such features for conventional lighting are performed by separate electronic units that turn power to the light on and off, which add cost and complexity.


Most LED lights today consist of multiple LEDs connected together in series and/or parallel, and are driven by a switching power supply. In an AC mains connected light, the power supply converts from the mains voltage, 85-240V, to a current for the LEDs, while the power supply in a battery powered light converts from the battery voltage to a current for the LEDs. Such circuits are offered by companies such as OnSemi and Supertex for mains connected, and Maxim for battery powered.


Less efficient LED lights simply connect the LEDs to the power supply through a series resistor. Although cheaper, the resistor dissipates substantial power, and when connected to an AC supply, the light has a poor power factor. The power factor is poor since the LEDs only conduct during the peaks in the AC waveform.


The LEDs in a light can be any color or any combination of colors, including white. White LEDs are typically made with a blue LED covered in some type of yellow phosphor. Much of the blue light from the LED is absorbed by the phosphor and re-emitted at lower frequencies corresponding to green, yellow, and some red colors. Some advantages of this approach include low cost and more natural continuous spectrum light. Some disadvantages include low efficiency due to losses in the phosphor, a bluish color from the LED, and reduced reliability due to degradation of the phosphor. Companies such as Cree Lighting and Nichia market such high brightness LEDs.


The spectrum of one particular Cree product shows a sharp peak around 450 nm, which is the blue light produced by the LED, and a broad peak around 550 to 600 nm, which is yellow from the phosphor. At 500 nm and 700 nm, the output power is only 20% of the peak power. In contrast, the spectrum of sunlight is virtually flat from just below 500 nm to just over 700 nm.


To overcome the lack of energy at the red end of the spectrum, Cree Lighting produces a two color overhead LED lamp that includes strings of red LEDs together with strings of phosphor coated blue LEDs. When comparing the spectrum produced by an RGB source, the Cree white LED plus red LED solution, and the standard output from an incandescent bulb, the spectrum of neither the RGB nor the white plus red light match either the incandescent or sunlight spectrum very well, although the white plus red light produces a good cost/performance compromise for many applications.


The ideal LED light from a color spectrum perspective would consist of many different colored LEDs operating at different power levels to produce a rough approximation of either incandescent or sun light. The combination of red, yellow, green, and blue is probably a minimum number of colors. Although this approach should have a good spectrum and be more energy efficient and reliable, control of the relative power levels in each color is difficult and expensive in practice today.


There are challenges to building even a three color (RGB) LED light that controls the color over process variations, temperature, aging, etc. Some techniques include feedback to the RGB driver circuits through three optically filtered photodiodes. Each photodiode is tuned to the color of each LED and is connected to a signal detection and signal processing function on an IC. The signal processor then controls the red, green, and blue drive currents accordingly. Such color filter photodiodes are offered by Hamamatsu, which are relatively expensive and consume board space that would otherwise be dedicated to producing light instead of receiving light.


National Semiconductor offers an RGB LED driver for LCD display backlighting. Their LP5520 can calibrate out the initial variation in LED optical output and then adjust over temperature. However, it does not compensate for aging. Since the output power of some LEDs goes up over time and some go down, the only effective means of compensation is through actual optical power measurement of each light component.


Cree's white plus red LED lamp includes two chains of 6 white LEDs, and one parallel/serial combination of 30 red LEDs, for a total of 36 LEDs. It also includes a photodetector and a temperature sensor to maintain color as described in US Published Patent Application No. 2008-0309255. A wavelength selective photo-detector monitors the shorter emission wavelength (green and shorter) and adjusts the brightness of the red LEDs in response. Likewise, temperature is monitored with a temperature sensing element, which is used to adjust the drive current to the red LEDs to compensate for brightness degradation with increasing temperature. Neither the optical power produced by the red LEDs nor the optical power produced by the white LEDs with wavelengths longer than green are measured. Any changes in red LED brightness over lifetime are not compensated. A cost effective solution for driving and controlling different color LEDs with good color discrimination and without the cost and board space for additional photodetectors and temperature sensors would be beneficial.


Conventional light dimming switches use a triac circuit that only allows the mains AC voltage to be applied to an incandescent light during part of the cycle. For instance, when set at half power, the voltage signal that passes through to the light is zero for the first 90 degrees of the sinusoidal voltage, jumps to the peak amplitude and follows the sinusoid down to zero for the second 90 degrees, stays at zero for the next 90 degrees, and finally jumps to the negative peak voltage and follows the sinusoid back to zero. This approach is a cheap and effective way for a consumer to dim a resistive incandescent bulb.


Although the triac dimmer reduces power consumption in the light bulb, it does not reduce the power that the utility company must produce. Power companies produce current that is in phase with the voltage. As the voltage increases, the current increases. If the entire load on a power generation plant consisted of lights dimmed 50% with triacs, the current produced during the first half of the positive and negative cycles would not go to the bulbs, but it would have to go somewhere. The utility must generate the same amount of power whether the lights are full on or dimmed and must deal with potentially dangerous transients on the grid.


The light from an LED can be reduced by either reducing the drive current or reducing the time that the current is applied by using what is called pulse width modulation (PWM). The current is turned on and off at a rate faster than the eye can see, with the duty cycle proportional to the desired light output. Since the wavelength of light produced by an LED changes with drive current, PWM dimming is sometimes preferred. When replacing an incandescent light with an LED light, an existing triac dimmer still adjusts the power supply to the light. To enable PWM dimming, the LED light circuitry must filter the power supply, detect the duty cycle of the supply, and adjust the PWM duty cycle accordingly, which adds cost and complexity.


Photosensors are commonly used to measure ambient light in a room or daylight outside and to adjust the brightness of a lamp in response. An outdoor lamp may be turned on and off at dusk and dawn respectively, or an indoor lamp may be dimmed such that the light from a window plus the light from the lamp remains constant. For existing technology, such photosensors need to be placed away from lamps so that the light from the lamp does not interfere with the photosensor. Typically, the photosensor is a separate electronic device, which needs to be installed. A lamp with a built in photosensor that is not affected by light output from the lamp and that does not require any wiring changes would be beneficial. Further, a lamp that could provide this functionality without a photosensor would be more beneficial.


Timers that turn a light on and off typically plug into a wall socket and connect and disconnect power to an attached light based on time of day. Such devices are typically bulky. An installed light socket cannot be changed to a timer without significant wiring changes. A replacement bulb that has a timer function built in that does not require additional cost or any wiring changes would be beneficial.


Electrical wiring and lighting switches in a new home or business construction consumes a significant portion of the construction cost. Additionally, light switches with dimmers are much more expensive than simple toggle switches, so therefore are used much less frequently. Lights that could be remotely controlled by for instance a device like a TV remote could significantly reduce wiring costs and provide additional features, which would be beneficial.


The developing world is leapfrogging developed world technology. For instance, solar powered homes are wide spread throughout the developing world (i.e., Kenya, India, etc.) Lighting traditionally has been provided by firewood and recently by kerosene, which are terribly inefficient. The combination of a solar panel, a car battery, and led lights provides a much better solution. During the day, the solar panel charges the battery and at night the led light consumes power. The effectiveness of the re-charging system determines the usefulness of the system. Any solar power efficiency improvement is significant. LEDs are photosensitive and can produce power when exposed to light. Harnessing this energy would be beneficial.


The invention described herein, in various embodiments, provides solutions to the issues described above.


SUMMARY

In certain exemplary embodiments, an improved illumination device uses the components in an LED lamp to perform some or all of the above functions for very low cost. The LEDs that produce light can be periodically turned off momentarily, for example, for a duration that the human eye cannot perceive, in order for the lamp to receive commands optically. The optically transmitted commands can be sent to the lamp, for example, using a remote control device. The illumination device can use the LEDs that are currently off to receive the data and then configure the light accordingly, or to measure light. Such light can be ambient light for a photosensor function, or light from other LEDs in the illumination device to adjust the color mix.


In certain exemplary embodiments, an illumination device uses LEDs to produce light and to provide bi-directional communication to a controller that implements power saving features not possible with conventional lighting. The illumination device, for example, can be programmed with modulated light from a remote controller to turn on and off, to adjust brightness or color, and to turn on or off in response to changes in ambient light or timer count values. The LEDs that produce the illumination during normal operation are periodically used to receive modulated light from a controller during short intervals undetectable by the human eye. In response to a command from the remote controller, the illumination device can produce light modulated with data. Additionally, when the remote controller is turned off and is exposed to sunlight, the LEDs in the controller can provide a trickle charge current to maintain full battery power.


In certain aspects, the invention provides a system of an intelligent illumination device and, in some cases, a remote controller. The illumination device, which is typically connected to an. AC mains power supply, can receive commands from the remote controller, which is typically battery powered, via light. The remote controller then programs the lamp for timer or photosensitive operation. For instance, at dusk the lamp could turn on and then go off, the light could come on when power is switched on and goes off a fixed time later, the light could come on and go off at fixed times, or the light could come on at dusk and off at dawn. Dimming could also be enabled or disabled, or could be automatically adjusted based ambient light.


When turned on, the illumination device periodically turns off the LEDs to determine if any commands are being sent or to measure ambient light. The remote control synchronizes to these momentary “light off” periods and sends a command if directed by the user. The commands can be on/off, dim, timer, photo cell, color, etc. When the light is turned off by the remote, ac power is still active. The device goes into a low power mode. When the remote turns the light on, the incident light can power the LEDs and enable the light to turn on. The light can also be turned off by removing AC power and turned on by turning AC power on. Cycling power in a certain sequence can reset the light to a default state.


In certain embodiments, the illumination device uses the photosensitive LEDs (i.e., the red LEDs) to detect received data or DC light during the intervals when the light output is momentarily turned off. For multi-colored light, the illumination device can use a chain of the longest wavelength LEDs (i.e., the red LEDs) to detect the output power of the other colors. With two chains of the longest wavelength LEDs, each chain can measure the output power of the other, thereby enabling a feedback loop to control the output power of each color and the blended color mix.


Once the illumination device (i.e., the “lamp”) is installed in an existing socket that may or may not be connected to a dimming switch, the illumination device can be dimmed by the remote controller. The remote controller sends commands to increment or decrement the output light level during the short “off” periods. The dimming function can be performed by pulse width modulating the LED drive current at a switching frequency preferably locked to the switching regulator frequency or by simply adjusting the LED drive current.


If photosensing is enabled, during the short light off periods, the longest wavelength LED chain can be used to measure ambient light. To do so, the LEDs may be configured in photovoltaic mode, and produce a voltage proportional to incident light. If the voltage is above a level specified through a command, the lamp can turn off in response. If the voltage drops back below the specified level, the lamp can turn on. Such a mechanism enables the light to turn on at night and off during the day. In combination with a timer, the light can turn on at dusk and off after a specified amount of time.


When the timer is enabled, the lamp can turn on and off at different times of day or turn off after a specified amount of time after being turned on. The lamp can be turned on by remote control, by power being applied through a switch, or by the photosensor function. In a mains connected application, the timer is synchronized to the AC frequency for a precise frequency reference.


When powered by a battery, the photosensitive LED chains can provide trickle current to re-charge the battery. A chain of 30 red LEDs (e.g., in the CREE lamp) can produce nearly 1 mW of power that can keep a re-chargeable battery charged in applications, such as emergency lights, that are not used often. For applications such as solar-powered, off-grid systems that are common in the developing world, the charging capability of the lamp can augment that of the solar panel.





DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings.



FIG. 1 an exemplary system diagram of an illumination device and a remote controller.



FIG. 2 is an exemplary list of functions performable by an exemplary illumination device.



FIG. 3 is an exemplary timing diagram of data communication between the illumination device and the remote controller.



FIG. 4 is an exemplary timing diagram of the bit timing and coding scheme for transferring data between the illumination device and the remote controller.



FIG. 5 is an exemplary illumination device block diagram, according to one embodiment.



FIG. 6 is another exemplary illumination device block diagram, according to another embodiment.





The use of the same reference symbols in different drawings indicates similar or identical items. While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.


DETAILED DESCRIPTION

Turning now to the drawings, FIG. 1 is one example of an intelligent illumination device system 10 that comprises the illumination device 11 and the remote controller 12. The remote controller 12 is preferably battery powered like a flashlight or TV remote control and is used to program the illumination device 11 with modulated light. When the illumination device 11 is powered preferably by the AC mains of an electrical socket (e.g., an Edison base socket), the illumination device 11 can be controlled by the remote controller 12. When the illumination device 11 is enabled to produce light (i.e., “turned on” or “producing light”), the illumination device 11 briefly and periodically stops emitting light to detect commands from the remote controller 12 or ambient light from the environment, or to calibrate colors in a multi-colored illumination device 11. When the illumination device 11 is powered by the AC mains, but is not enabled to produce light (i.e., “turned off”), the illumination device enters a low power state. Commands from the remote controller 12 can still be detected by the illumination device 11 in this state. The illumination device 11 responds to the remote controller 12 by momentarily producing light modulated with data. To reset the illumination device 11 to a default state, power to the illumination device 11 is cycled in a specific sequence.



FIG. 1 is just one example of many possible intelligent illumination device systems. For example, the illumination device 11 could be powered with a battery or the remote controller 12 could be powered by the AC mains. In another example, if the illumination device is programmed when it is designed or produced, no remote controller 12 is needed. Examples of pre-programmed devices include pre-configured night lights, and lights that automatically turn of perhaps 1 hour (or other delay) after being turned on. In such case, the functionality of the illumination device may be reduced.


In another example, light from the remote controller 12 could power an un-powered illumination device 11 with light while programming. For instance, a consumer could buy a light bulb replacement including this remote controller. The consumer could then hold the bulb to the remote and configure it to turn off 35 minutes after being turned on, then take the programmed bulb and screw in a socket somewhere. Without this self-powered variant, the bulb would need to be screwed into an energized socket in order to program it, which may be possible, but still perhaps less convenient.


In a further example, the remote controller battery could be charged by sunlight or ambient light when not in use. Additionally, multiple illumination devices 11 could communicate with each other. For example, various governments have recently introduced mandates that certain buildings must have intelligent lights that automatically turn on and off based on whether or not people are present. Some large lighting companies provide systems consisting of lamps with motion detectors and 900 MHz RF transceivers. When one lamp in a room detects motion, it tells the rest of the lights to turn on. The two main issues with this approach are: (1) the lights are expensive, and (2) the RF signal passes through walls to other rooms with no people. The devices described herein could communicate with each other via light which: (1) does not require the expense of the RF circuitry, and (2) does not go through walls. Additionally, functions like dimming or color control could benefit from lamps communicating with each other. For example, a user could program one lamp, and that lamp then reconfigures the other lamps. Additional applications could be security where two lamps constantly communicate with each other. If an intruder passes between them and momentarily blocks the light, the lamps detect this and broadcast info to other lamps in the building in sort of a daisy chain way to a central security system.


Table 2 is an example list of commands 14 for the illumination device 11 that enable the remote controller 12 to turn the illumination device 11 on and off, adjust the output power, and change the color to one of three different settings. Additionally, the illumination device 11 can be configured to automatically turn on in response to a time of day counter reaching a particular count or ambient light dropping below a certain level, and to automatically turn off after a timer reaching a particular count from when the illumination device 11 is turned on or ambient light rising above certain level. In this example, the color mix is always automatically measured and adjusted to a specific setting. The example set of commands 14 can use 4 bits to produce hex codes 13.


Preferably, the hex codes 13 are preceded by a synchronization pattern and followed by parity to produce an 8 bit transfer sequence. Additionally, the commands that set a time must be followed with the actual time. Since there are 1440 minutes in a day, a time with one minute resolution requires 11 bits, which could be sent in two successive transfers after the command.


Table 2 is just one example of many possible sets of commands 14 and hex codes 13. For instance, in a multi-color light each individual component could be dimmed or color calibration could be enabled and disabled. As another example the time of day counter could count days of the week as well. The illumination device 11 could have a subset of these functions or could have a variety of other functions such as strobing or continuous color variation. Additionally, illumination device 11 status and register contents could be read. Further, the assignment of hex codes 13 to commands 14 could be completely different and could contain more or less bits depending on the number of commands 14.



FIG. 3 is an example timing diagram for communicating commands 14 between the illumination device 11 and the remote controller 12 when the illumination device 11 is producing light. Pulse width modulated light PWM 20 from the illumination device 11 is periodically interrupted by gaps 21 when no light is produced. The gap period 22 in this example is one second. The gap time 23 is equal to one half the mains period or 8.33 mSec at 60 Hz. The remote controller 12 synchronizes to gaps 21 in the PWM 20 light from the illumination device 11 and can send commands CMD 24 during gaps 21. When a CMD 24 is sent from the remote controller 12 and is properly received by the illumination device 11, the illumination device 11 provides a response RSP 25 immediately after CMD 24. The remote controller 12 may preferably be narrowly focused (much like a flashlight) to assist a user in directing the remote commands to a particular illumination device in a room with multiple such illumination devices. The user could see the light beam and shine it directly on one light. This would focus light from the remote on the illumination device and light from the illumination device on the detector in the remote.


In this example, the light from the illumination device 11 is pulse width modulated at 16 times the mains frequency or 960 Hz for 60 Hz AC, to enable dimming without changing LED wavelengths. At full brightness, the off time is very short or non-existent and at low light levels, the on time is short. The frequency of the pulses stays fixed. To prevent the remote controller 12 from losing synchronization with the illumination device 11, the last pulse from the illumination device 11 before a gap 21 is preferably not reduced below a minimum width that the remote controller 12 can detect.


In another example, the one second gap time 22 can be shortened to 200 mSec for instance, after the illumination device 11 and remote controller 12 communicate a first CMD 24 so that successive commands can be communicated faster. This may be important for dimming since there may be many power level steps between low and high power. Once the remote controller 12 stops sending commands, the gap period 22 widens back to one second intervals.


When the illumination device 11 is not producing light, the remote controller 12 does not detect gaps 21 and can send commands CMD 24 at any time. The protocol shown in FIG. 3 remains the same except that the illumination device 11 is not outputting PWM 20 light before and after the transaction.


During gaps 21 when commands CMD 24 are not sent or when the illumination device 11 is not producing light, the illumination device 11 can measure ambient light. The ambient light level is subtracted from the received light when commands CMD 24 are sent and is used to determine when to turn the illumination device 11 on or off when photo-sensor functionality is enabled. More specifically, when the illumination device is receiving commands, the background or ambient light produces a DC offset in the optically induced voltage across the LEDs (or photodiode). This DC offset can be eliminated by measuring the optically induced voltage during gaps 21 when no commands are sent, and subtracting it from the induced voltage when receiving commands. Alternatively, the receiver in the illumination device can high pass filter the induced voltage to remove the DC offset. Since the data rate is low, the receiver may use a digital filter for DC blocking (and equalization). If the DC offset is known prior to receiving a command, the initial state of the digital filter can be set accordingly, and reduce the settling time. When photosensor functionality is enabled, ambient light is measured during gaps 21 when the illumination device is producing light, and measured all the time when not producing light.


Additionally, in a multi-color illumination device 11, the intensity of each individual color can be measured during gaps 21 or when the illumination device 11 is not producing light. For instance, when the illumination device 11 is turned on, the illumination device 11 can briefly measure the intensity of each color before producing the desired light. Then periodically as the illumination device warms up for instance, the color components can be measured during gaps 21.



FIG. 3 is just one example of many possible timing diagrams. The gap period 22 and gap time 23 could be substantially different depending on the applications. The response RSP 25 can be sent at different times or not at all. The commands CMD 24 could even be sent during the off times of the PWM cycle and responses RSP 25 could be variations in PWM duty cycle. To provide additional error protection, commands CMD 24 could be repeated one or more times before taking affect. Many different timing diagrams and communication protocols could be implemented. For an illumination device 11 that is powered by the light from the remote controller 12 instead of a battery or AC mains, the protocol can include significant illumination durations in order to store sufficient charge on a capacitor for instance to power the illumination device 11 and to communicate data.



FIG. 4 is an example timing diagram illustrating the bit level communication between the illumination device 11 and the remote controller 12 when the illumination device 11 is producing light. Communication begins with the illumination device 11 stopping the PWM 20 output. The illumination device synchronization IDSYNC 30 pulse is the last PWM pulse produced by the illumination device 11 prior to a gap 21. The width of IDSYNC 30 is greater than the minimum pulse width detectable by the remote controller 12. Other synchronization sequences, such as short series of pulses, may also be produced before each gap 21. The CMD 24 from the remote controller 12 comprises a synchronization pattern SYNC 31 of 3 ones, a hex code 13, and an even parity bit P32 that are biphase encoded. In this example, the command 14 is “light off”. If the illumination device 11 receives the CMD 24 properly, the response RSP 25 comprises the same biphase encoded SYNC 31, hex code 13, and parity P32 that comprised the CMD 24.


When the illumination device 11 is not producing light, the protocol shown in FIG. 4 remains the same except that the illumination device is not outputting PWM 20 light (nor IDSYNC 30) before and after the transaction.



FIG. 4 is just one example of many possible bit timing diagrams. Instead of biphase encoding, the protocol could use any one of many well known coding schemes such 4b5b, 8b10b, or NRZ. The SYNC 31 could have a wide variety of lengths and sequences including none at all. The hex codes 13 could have more or less bits and parity P32 could be even or odd, more than one bit, or none at all. CRC codes could be used for error detection. For an illumination device 11 that is powered by light from the remote controller 12, the protocol could be substantially different. In particular, it may be necessary to transmit data one bit at a time from the illumination device 11 to the remote controller 12 with the remote controller 12 emitting light to re-charge a capacitor on the illumination device 11 for instance between bits sent from the illumination device 11. Useful transceiver techniques for so doing are described in U.S. patent application Ser. No. 12/360,467 filed Jan. 27, 2009 by David J. Knapp and entitled “Fault Tolerant Network Utilizing Bi-Directional Point-to-Point Communications Links Between Nodes,” and in U.S. Provisional Application No. 61/094,595 filed Sep. 5, 2008 by David J. Knapp and entitled “Optical Communication Device, Method and System,” and in U.S. patent application Ser. No. 12/584,143, filed Sep. 1, 2009 by David J. Knapp and entitled “Optical Communication Device, Method and System,” each of which is hereby incorporated by reference in its entirety.



FIG. 5 is an example block diagram for an exemplary illumination device 11 that comprises an. EMI filter and rectifier 41, an AC to DC converter, a voltage divider, an integrated circuit IC 54, and the LED chain 53. The EMI filter and rectifier 41 produces a full wave rectified version of the AC mains VAC 40, and minimizes both transient disturbances on the mains from affecting the rectified power, and switching noise in the illumination device 11 from affecting the mains. The voltage divider comprises resistors R 42 and R 43 and produces signal S 57 that is a reduced voltage version of the rectified mains signal for IC 54. The AC to DC converter includes inductors 44 and 45 (also referred to herein as inductors L 44 and L 45), capacitors 46 and 47 (also “capacitors C 46 and C 47”), diode 48 (also “diode D 48”), the N-channel switch transistor 49 (also “switch N 49”), and the power controller 62 on integrated circuit 54 (IC. 54). This example shows LED chain 53 comprising of LED 50, LED 51, and LEDn 52, with the dashed line between LED 52 and LEDn 53 indicating that LED chain 53 can include many LEDs. This architecture is typical for monochrome light or white light produced by blue LEDs with a phosphor coating. A multi-color illumination device typically would have separate LED chains for each color.


IC 54 includes memory and control 60, PLL and timing 61, power control 62, receiver 63, and output driver 64. Memory and control 60 includes non-volatile memory for storing configuration information, such as enabling the timer or photo-sensor, and volatile (or non-volatile) memory for settings such as dimming. Memory and control 60 also includes logic that manages the transfer of data with the remote controller 12, produces the pulse width modulated (PWM) LED drive signal S 59, and implements the timers and state machines that control the overall function of IC 54 and the illumination device 11.


PLL and timing 61 includes a phase locked loop that produces a high frequency clock that is phase locked to S 57 when the illumination device is powered. The voltage divider comprising of R 42 and R 43 provides a low voltage version of the rectified mains voltage S 57 that does not exceed the voltage rating of IC 54 and that the PLL locks to. All other circuitry on IC 54 is synchronized to the PLL and timing 61 outputs (not shown).


PLL and timing 61 enables the illumination device 11 to maintain a precise time base for time of day timer functionality by locking to the mains frequency. Likewise, gap period 22 and gap time 23 can be precisely aligned to VAC 40 timing. Such timing could enable multiple illumination devices 11 to synchronize and communicate directly between each other with light. For example, multiple illumination devices (i.e., “IDs”) can sync to each other by first looking for GAPS (e.g., gaps 21) just before producing light. If proper GAPs are found, the illumination device syncs to them. If no gaps are found, there is nothing to sync to and the illumination device effectively becomes a timing master that other illumination devices lock to when turned on. Such an illumination device preferably should also be able to detect if sync is lost and to re-lock. It is further noted that additional embodiments for illumination devices and systems as well as for visible light communication systems and methods are described in U.S. Provisional Patent Application No. 61/336,242, filed Jan. 19, 2010 by David J. Knapp and entitled “Illumination Devices and Related Systems and Methods,” and U.S. Provisional Patent Application No. 61/339,273, filed Mar. 2, 2010 by David J. Knapp, et al., and entitled “Systems and Methods for Visible Light Communication,” each of which is hereby incorporated by reference in its entirety. It is further noted that display related systems and methods, display calibration systems and methods, and LED calibration systems and methods are described in U.S. Provisional Patent Application No. 61/273,518, filed Aug. 5, 2009 by David J. Knapp and entitled “Display and Optical Pointer Systems and Related Methods,” and U.S. Provisional Patent Application No. 61/273,536, filed Aug. 5, 2009 by David J. Knapp and entitled “Display Calibration Systems and Related Methods,” and U.S. Provisional Patent Application No. 61/277,871, filed Sep. 30, 2009 by David J. Knapp and entitled “LED Calibration Systems and Related Methods,” and U.S. Provisional Patent Application No. 61/281,046, filed Nov. 12, 2009 by David J. Knapp and entitled “LED Calibration Systems and Related Methods,” each of which is hereby incorporated by reference in its entirety.


When VAC 40 is turned off, capacitor C 47 can maintain power to IC 54 for some period of time. If VAC 40 is turned off and on within this time, IC 54 can remain powered. To reset the illumination device 11 to a default state, VAC 40 can be turned off and on a number of times for specified amounts of time. For instance, the reset sequence could be 3 short off and on intervals, followed by 3 longer off and on intervals, and followed finally by 3 more short off and on intervals. PLL and timing 61 monitors signal S 57, signals IC 54 to enter a low power state when signal S 57 stays low, and measures the time between short VAC 40 off and on periods. When PLL and timing 61 detects the proper VAC 40 off and on sequence, IC 54 is reset to a default state.


Power control 62, together with the external components inductors L 44 and L 45, capacitors C 46 and C 47, diode D 48, and switch N 49, and current sensing feedback from output driver 64, implement the AC-to-DC converter function. The configuration implemented is the well known Single Ended Primary Inductor Converter (SEPIC). Switch N 49 is turned on and off by power control 62 at a relatively high frequency such as 1 MHz, with the duty cycle varying to produce the desired current through LED chain 53. When switch N 49 is closed, the current from L 44 and L 45 is pulled through switch N 49 and charge stored on the capacitor C 46 provides current to LED chain 53. When switch N 49 is open, the current through inductors L 44 and L 45 flows through the diode D 48 and to LED chain 53 and C 47.


Power control 62 compares voltage feedback signal Vfb 65 from output driver 64 to an internal reference voltage to produce an error signal that adjusts the duty cycle of the control signal S 58 that is coupled to switch N 49. The signal Vfb 65 is produced by LED chain 53 current flowing through a small resistor in output driver 64 (not shown). When LED chain 53 is turned off, Vfb 65 becomes a divided down version of V+ 55, which occurs when receiving data and during the PWM dimming off times. A control loop adjusts the feedback divider to maintain V+ 55 at the same voltage as when LED chain 53 is on.


When output driver 64 turns the current to LED chain 53 on or off, large voltage transients can occur on V+ 55 before the power control 62 can adjust to the new duty cycle of signal S 58. When the LED chain 53 current is turned off, V+ 55 will go high until the duty cycle of S 58 is reduced, and when the LED chain 53 current is turned on, V+ 55 will go low until the duty cycle of S 58 is increased. To minimize such transients, power control 62 receives information from memory and control 60 in advance of when such changes will occur and adjusts S 58 duty cycle the instant such a change is needed. Just prior to the output driver 64 turning the LED chain 53 current off, power control 62 measures S 58 duty cycle and stores the result. This duty cycle is restored instantly the next time LED chain 53 current is turned off to prevent V+ 55 from spiking high. Likewise, the S 58 duty cycle is measured when the LED current is turned on, and the result is stored, and then restored to prevent V+ 55 from spiking low.


Output driver 64 turns LED chain 53 current on and off with a switch connected to ground (not shown). Current flows from V+ 55 to ground through LED chain 53 and the switch, when the switch is on, and no current flows when the switch is off. A small resistor in series with the switch produces Vfb 65 when the switch is on. When the switch is on, a control loop compares the output of a variable voltage divider from V+ 55 to Vfb 65 and adjusts the divider until the output equals Vfb 65. When the LED chain 53 current is turned off, the V+ 55 voltage divider loop is also turned off and the voltage divider remains fixed. While the LED chain 53 current is off, this divided version of V+ 55 is forwarded to power control 62 through Vfb 65.


Receiver 63 can receive data from the remote controller 12, when the LED chain 53 current is turned off by output driver 64. Modulated light from remote controller 12 is converted to a voltage signal S 59 by LED chain 53, which operates in photo-voltaic mode as in a solar panel. Receiver 63 high pass filters S 59 to block the DC content from ambient light and to cancel the low bandwidth of the photo-voltaic LED chain 53. Such bandwidth typically supports up to 1 k bits per second (1 kbps), but with the proper equalization filter the data rate can be increased by 10 times or more. To support the protocol in FIGS. 3 and 4, 2 kbps are needed. Receiver 63 comprises an A/D converter and a digital filter to equalize signal S 59. Timing recovery is not needed since the data is sent from the remote controller 12 synchronously to the AC mains frequency that IC 54 is locked to. The output of the digital filter is simply sampled at the appropriate times.


When the illumination device 11 is not producing light, the remote controller 12 detects the absence of gaps 21. Since the remote controller 12 is not synchronized to the gaps 21 from the illumination device 11, and since the remote controller 12 is battery powered, data from the remote controller 12 is asynchronous to the timing in the illumination device 11. Provided the remote controller 12 has a precise oscillator, such as a quartz crystal, the remote controller 12 and the illumination device reference clocks will typically be within a couple hundred parts per million of each other. The illumination device 11 resets a timer clocked at high frequency on the falling edge of the third SYNC 31 pulse and uses this timer to sample received data and produce transmitted data. The drift between the two reference clocks over the 16 mSec period of one transfer is insignificant.


The illumination device 11 measures ambient light during gaps 21, and also when the illumination device 11 is not producing light, by measuring the average voltage of signal S 59 with the A/D converter in receiver 63. The A/D converter should be architected to have small DC errors, such as the well known chopper stabilization architecture, to measure very low light levels.



FIG. 5 is just one example of many possible illumination device 11 block diagrams. For example, an illumination device 11 architecture for multi-colored light could comprise of an LED chain 53 and output driver 64 for each component color. Example color combinations could comprise of red, green, and blue, or of red, yellow, green, and blue, or of red and white. During gaps 21, and also when the illumination device 11 is not producing light, the lower light frequency LEDs can measure the light intensity of each other and of the higher light frequency LEDs. For instance, in a red and white illumination device, during gaps 21 for instance, the white LED chain could produce light and the red LED chain could be connected to the receiver and could measure the light power. If the red LEDs are organized in two separate chains with separate output drivers, during gaps 21 for instance, one red LED chain could measure the light power of the other. By measuring the light power from each LED chain, the illumination device could adjust the current to the different LED chains to maintain a specific color point for instance over LED variations, temperature variations, and LED lifetime. A single receiver 63 could be shared and connected at different times to different LED chains, or multiple receivers 63 could be implemented.


In another example illumination device 11 can be powered by the remote controller 12 during configuration. The receiver 63 could be powered by an LED chain receiving modulated light and could store configuration information in the non-volatile memory included within memory and control 60. The average voltage induced across the LED chain by light is typically significantly lower than the voltage necessary to produce light from the same LED chain. The induced voltage could be stored across capacitor C 47 and a smaller segment of the LED chain 53 could be connected to output driver 64 to emit responses to the remote controller 12. The communication protocol to configure an illumination device 11 when not powered could be different from FIG. 3 to enable capacitor C 47 to be re-charged after each emitted light pulse. Useful techniques for so doing are described in the aforementioned U.S. application Ser. No. 12/360,467 and the aforementioned U.S. Provisional Application No. 61/094,595.


The block diagram for an illumination device 70 that is powered by a battery 71 (instead of the AC mains 40) would have a battery 71 and potentially a different type of switching power supply such as the well known buck, boost, boost buck, or flyback. With a re-chargeable battery, ambient light or sunlight incident on the LEDs 53 could produce power to re-charge the battery 71. A block diagram for such an illumination device 70 is shown in FIG. 6 as having power control 62 that manages the battery charger 72. An illumination device 11 powered by the AC mains could also have any of a wide variety of different AC-DC converters, such as the boost buck or flyback. Such an illumination device could also have a backup re-chargeable battery (as shown in FIG. 6) that enables the illumination device to maintain the time of day counter when power goes off. The timing for the illumination device 11 could also be based on a local crystal oscillator instead the mains frequency for instance.


As a further example, the block diagram for an illumination device that uses a silicon photodiode instead of LEDs for instance for receiving data would have the receiver 63 connected to the photodiode instead of LED chain 53. Such architectures would be particularly useful for illumination devices that only use phosphor coated white LEDs that do not operate well in photo-voltaic mode. The silicon photodiode could receive commands 24 from the remote controller 12, measure ambient light, and measure emitted light from the LED chain.


Multiple illumination devices could also communicate with each other. In this example, an illumination device 11 could execute a protocol to synchronize to other illumination devices and to arbitrate for transmission bandwidth. When turned on, an illumination device 11 could monitor the ambient light, search for gaps 21 with the proper gap period 22 and gap time 23, and synchronize to the gaps 21 if found. If all the illumination devices are connected to the AC mains, then very precise synchronization is possible. Illumination devices could arbitrate for bandwidth according any one of many well known arbitration protocols. For instance, if two illumination devices transmit at the same time, both illumination devices detect the collision and wait a random amount of time before trying to communicate again. As another possibility, a CMD 24 could include a priority code that indicates in the case of a collision, which illumination device stops transmitting.


As used herein, an illumination device is assumed to produce a general light, usually of a human-perceivable nature, but possibly infrared or some other wavelength. An illumination device enabled to produce light (i.e., “turned on”) may be thought of as being set to an “on-state” (i.e., having its illumination state set to an on-state), even though, as described above, there may be very short periods of time during which the light source is momentarily turned “off” and is not actually emitting light, such as during the gaps, and during the off-times in a PWM signal. The on-state and off-state of the illumination device should be clear in the context described above and not confused with the on and off status of the actual light source.


An illumination device may be set to an on-state or off-state by any of several events, such as application/removal of power to the illumination device (such as by energizing the light socket into which the illumination device is inserted), by a timer event, by ambient light control, and by a remote command.


Exemplary block diagrams are depicted herein. However, other block partitionings of an illumination device may be provided. As used herein, an illumination device attribute may represent an operational state or a configuration parameter of the illumination device. Examples include the illumination state, timer settings, delay settings, color settings for each of one or more light sources within the illumination device, photosensing mode settings, dimmer settings, time-of-day, etc.


While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown and described by way of example. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed.

Claims
  • 1. An illumination device comprising: a light source configured to provide illumination when said illumination device is physically coupled to a power source and set in an on-state; anda light detector integrated circuit configured to: detectlight, during certain times when the light source is not providing illumination, an optically modulated data command received from an external device, wherein the data command includes configuration data; to automatically adjust the illumination device based on the detectedreceived configuration data; and , receivingif the illumination device is physically decoupled from the power source, receive light from the external device to power an un-powered said illumination device that is separate from an AC mains socket before screwingthe integrated circuit to store the received configuration data prior to physically coupling the Illuminationillumination device intoto the AC mains socketpower source.
  • 2. The illumination device ofas recited in claim 1, wherein the light source comprises a first LED configured to provide the illumination, and wherein the first LED is also configured to be the light detectorconvert incident light to electrical energy during certain times when the first LED is not providing illumination.
  • 3. The illumination device as recited in claim 2 further comprising a second LED, wherein the first LED detects light emitted from the second LED.
  • 4. The illumination device as recited in claim 3wherein the integrated circuit is further comprising a control circuitconfigured to adjust a color of light produced by the illumination device.
  • 5. The illumination device as recited in claim 4 wherein light produced by the first LED or the second LED or both are adjusted in order to adjust the color.
  • 6. A method for operating an illumination device comprising: when said illumination device is set in an on-state, engagingcausing a light source included in said illumination device to provide illuminationilluminate;and usingcausing said light source to cease illumination for a period of time while detecting, via a light detector integrated circuit of the illumination device, incident light, wherein the incident light is one or more of ambient light, light from a second light source included in the illumination device, or an optically transmitted command; and to detect light during certain times when the light source is not providing illumination, to automatically adjust theadjusting, by the light detector integrated circuit, a level of illumination of said light source based on the incident light; and detected light, receiving light to powerwhen said illumination device is set in an un-powered state in which said illumination device an unpowered said illumination device that is separate from an AC mains socket before screwing the Illuminationa power source prior to coupling said illumination device into the AC mains socketto said power source, receiving light and an optically transmitted command comprising configuration data from an external device, the light to power the integrated circuit to store the configuration data.
  • 7. The method as recited in claim 6, wherein the engagingfirst causing step comprises engaging a first LED to provide illumination, and wherein the usingdetecting step in the second causing step comprises using the first LED to detectconvert the incident light to electrical energy during certain times when the first LED is not providing illumination.
  • 8. The method as recited in claim 7 wherein the usingdetecting step comprises using the first LED to detect light emitted from a second LED.
  • 9. The method as recited in claim 8 further comprising adjusting a color of light produced by the illumination device.
  • 10. The method as recited in claim 9 wherein the adjusting step comprises adjusting light produced by the first LED or the second LED or both in order to adjust the color.
  • 11. An illumination device comprising: a light source configured to provide illumination when the illumination device is set in an on-state; anda light control circuit configured to: control the light source at first times to provide pulse-width-modulated (PWM) illumination at a modulation frequency;periodically turn the light source off at second times to produce periodic gaps in the PWM illumination at a frequency less than the modulation frequency of the PWM illumination;configure the light source during the periodic gaps to detect incident light originating from outside the illumination device, wherein the incident light comprises an optically modulated data command conveyed by an external device;control the illumination device responsive to the incident light detected by the light source, wherein to control the illumination device comprises to: demodulate the incident light to decode the optically modulated data command conveyed by the external device; andchange an attribute of the illumination device in response to the data command decoded from the incident light; andcontrol the light source during third times for transmitting a response to the external device after receiving the data command.
  • 12. An illumination device comprising: a first LED configured to: provide illumination; andwhen not providing illumination, output a voltage signal related to light incident on the first LED; andan integrated circuit coupled to the first LED, the integrated circuit configured to: receive the voltage signal;responsive to a physical connection of the illumination device to a power source, adjust the illumination produced by the first LED based on the received voltage signal; andresponsive to a physical separation of the illumination device from the power source, use the received voltage signal to power the integrated circuit to store configuration information received from an external device.
  • 13. The illumination device as recited in claim 12 further comprising a second LED, wherein the light incident on the first LED is light emitted from the second LED.
  • 14. The illumination device as recited in claim 13 wherein the integrated circuit is further configured to adjust a color of light produced by the illumination device.
  • 15. The illumination device as recited in claim 14 wherein the color of light of the first LED or the second LED or both are adjusted.
  • 16. The illumination device as recited in claim 12 wherein the light incident on the first LED comprises an optically transmitted command from the external device and wherein the integrated circuit is further configured to change an attribute of the illumination device in response to the command.
  • 17. The illumination device as recited in claim 16 wherein the integrated circuit is further configured to transmit a response to the external device after receiving the command.
RELATED APPLICATIONS

This applicationThe present application is a reissue of U.S. Pat. No. 9,848,482, issued on Dec. 19, 2017 from U.S. patent application Ser. No. 15/296,258, filed Oct. 18, 2016, which is hereby incorporated by reference herein in its entirety. U.S. patent application Ser. No. 15/296,258 is a divisional of U.S. patent application Ser. No. 12/803,805. U.S. patent application Ser. No. 12/803,805 claims priority to the following provisional application: Provisional Application Ser. No. 61/224,904 entitled “INTELLIGENT ILLUMINATION DEVICE,” which was filed on Jul. 12, 2009, and is hereby incorporated by reference in its entirety. This applicationU.S. patent application Ser. No. 12/803,805 also claims priority to the following provisional applications: U.S. Provisional Patent Application Ser. No. 61/273,518 filed Aug. 5, 2009 by David J. Knapp and entitled “Display and Optical Pointer Systems and Related” Methods;” U.S. Provisional Patent Application Ser. No. 61/273,536 filed Aug. 5, 2009 by David J. Knapp and entitled “Display Calibration Systems and Related Methods:;” U.S. Provisional Patent Application Ser. No. 61/277,871 filed Sep. 30, 2009 by David J. Knapp and entitled “LED Calibration Systems and Related Methods:;” U.S. Provisional Patent Application Ser. No. 61/281,046 filed Nov. 12, 2009 by David J. Knapp and entitled “LED Calibration Systems and Related Methods:;” U.S. Provisional Patent Application Ser. No. 61/336,242 filed Jan. 19, 2010 by David J. Knapp and entitled “Illumination Devices and Related Systems and Methods:;” and U.S. Provisional Patent Application Ser. No. 61/339,273 filed Mar. 2, 2010 by David J. Knapp, et al. and entitled “Systems and Methods for Visible Light Communication.” This applicationU.S. patent application Ser. No. 15/296,258 is also a continuation-in-part application of the following co-pending patent applications: U.S. patent application Ser. No. 12/360,467 filed Jan. 27, 2009 by David J. Knapp and entitled “Fault Tolerant Network Utilizing Bi-Directional Point-to-Point Communications Links Between Nodes;” and U.S. patent application Ser. No. 12/584,143, filed Sep. 1, 2009 by David J. Knapp and entitled “Optical Communication Device, Method and System;” which in turn claims priority to U.S. Provisional Patent Application Ser. No. 61/094,595 filed on Sep. 5, 2008 by David J. Knapp and entitled “Optical Communication Device, Method and System.”

US Referenced Citations (293)
Number Name Date Kind
4029976 Fish et al. Jun 1977 A
4206444 Ferlan Jun 1980 A
4402090 Gfeller et al. Aug 1983 A
4713841 Porter et al. Dec 1987 A
4745402 Auerbach May 1988 A
4809359 Dockery Feb 1989 A
5018057 Biggs et al. May 1991 A
5093744 Sato et al. Mar 1992 A
5103466 Bazes Apr 1992 A
5181015 Marshall et al. Jan 1993 A
5193201 Tymes Mar 1993 A
5218356 Knapp Jun 1993 A
5299046 Spaeth et al. Mar 1994 A
5317441 Sidman May 1994 A
5383044 Borchardt Jan 1995 A
5541759 Neff et al. Jul 1996 A
5619262 Uno Apr 1997 A
5657145 Smith Aug 1997 A
5797085 Beuk et al. Aug 1998 A
5905445 Gurney et al. May 1999 A
5929845 Wei et al. Jul 1999 A
6016038 Mueller et al. Jan 2000 A
6067595 Lindenstruth May 2000 A
6069929 Yabe et al. May 2000 A
6084231 Popat Jul 2000 A
6094014 Bucks et al. Jul 2000 A
6094340 Min Jul 2000 A
6108114 Gilliland et al. Aug 2000 A
6127783 Pashley et al. Oct 2000 A
6147458 Bucks et al. Nov 2000 A
6150774 Mueller et al. Nov 2000 A
6234645 Borner et al. May 2001 B1
6234648 Borner et al. May 2001 B1
6250774 Begemann et al. Jun 2001 B1
6333605 Grouev et al. Dec 2001 B1
6344641 Blalock et al. Feb 2002 B1
6356774 Bernstein et al. Mar 2002 B1
6359712 Kamitani Mar 2002 B1
6384545 Lau May 2002 B1
6396815 Greaves et al. May 2002 B1
6414661 Shen et al. Jul 2002 B1
6441558 Muthu et al. Aug 2002 B1
6448550 Nishimura Sep 2002 B1
6495964 Muthu et al. Dec 2002 B1
6498440 Stam et al. Dec 2002 B2
6513949 Marshall et al. Feb 2003 B1
6577512 Tripathi et al. Jun 2003 B2
6617795 Bruning Sep 2003 B2
6636003 Rahm et al. Oct 2003 B2
6639574 Scheibe Oct 2003 B2
6664744 Dietz Dec 2003 B2
6692136 Marshall et al. Feb 2004 B2
6741351 Marshall et al. May 2004 B2
6753661 Muthu et al. Jun 2004 B2
6788011 Mueller et al. Sep 2004 B2
6806659 Mueller et al. Oct 2004 B1
6831569 Wang et al. Dec 2004 B2
6831626 Nakamura et al. Dec 2004 B2
6853150 Clauberg et al. Feb 2005 B2
6879263 Pederson et al. Apr 2005 B2
6965205 Piepgras et al. Nov 2005 B2
6969954 Lys Nov 2005 B2
6975079 Lys et al. Dec 2005 B2
7006768 Franklin Feb 2006 B1
7014336 Ducharme et al. Mar 2006 B1
7038399 Lys et al. May 2006 B2
7046160 Pederson et al. May 2006 B2
7072587 Dietz et al. Jul 2006 B2
7088031 Brantner et al. Aug 2006 B2
7119500 Young Oct 2006 B2
7135824 Lys et al. Nov 2006 B2
7161311 Mueller et al. Jan 2007 B2
7166966 Naugler, Jr. et al. Jan 2007 B2
7194209 Robbins et al. Mar 2007 B1
7233115 Lys Jun 2007 B2
7233831 Blackwell Jun 2007 B2
7252408 Mazzochette et al. Aug 2007 B2
7255458 Ashdown Aug 2007 B2
7256554 Lys Aug 2007 B2
7262559 Tripathi et al. Aug 2007 B2
7294816 Ng et al. Nov 2007 B2
7315139 Selvan et al. Jan 2008 B1
7319298 Jungwirth et al. Jan 2008 B2
7329998 Jungwirth Feb 2008 B2
7330002 Joung Feb 2008 B2
7330662 Zimmerman Feb 2008 B2
7339332 Cull et al. Mar 2008 B2
7352972 Franklin Apr 2008 B2
7358706 Lys Apr 2008 B2
7359640 Onde et al. Apr 2008 B2
7362320 Payne et al. Apr 2008 B2
7372859 Hall et al. May 2008 B2
7400310 LeMay Jul 2008 B2
7445340 Conner et al. Nov 2008 B2
7511695 Furukawa et al. Mar 2009 B2
7525611 Zagar et al. Apr 2009 B2
7554514 Nozawa Jun 2009 B2
7573210 Ashdown et al. Aug 2009 B2
7583901 Nakagawa et al. Sep 2009 B2
7606451 Morita Oct 2009 B2
7607798 Panotopoulos Oct 2009 B2
7619193 Deurenberg Nov 2009 B2
7649527 Cho et al. Jan 2010 B2
7659672 Yang Feb 2010 B2
7683864 Lee et al. Mar 2010 B2
7701151 Petrucci et al. Apr 2010 B2
7737936 Daly Jun 2010 B2
7828479 Aslan et al. Nov 2010 B1
7851737 Crouse Dec 2010 B2
7878488 Leason Feb 2011 B1
7885548 Nelson Feb 2011 B1
8013538 Zampini et al. Sep 2011 B2
8018135 Van De Ven et al. Sep 2011 B2
8040299 Kretz et al. Oct 2011 B2
8044899 Ng et al. Oct 2011 B2
8044918 Choi Oct 2011 B2
8057072 Takenaka et al. Nov 2011 B2
8075182 Dai et al. Dec 2011 B2
8076869 Shatford et al. Dec 2011 B2
8159150 Ashdown et al. Apr 2012 B2
8174197 Ghanem et al. May 2012 B2
8174205 Myers et al. May 2012 B2
8283876 Ji Oct 2012 B2
8299722 Melanson Oct 2012 B2
8362707 Draper et al. Jan 2013 B2
8471496 Knapp Jun 2013 B2
8503886 Gunasekara et al. Aug 2013 B1
8521035 Knapp et al. Aug 2013 B2
8556438 McKenzie et al. Oct 2013 B2
8569974 Chobot Oct 2013 B2
8595748 Haggerty et al. Nov 2013 B1
8633655 Kao et al. Jan 2014 B2
8653758 Radermacher et al. Feb 2014 B2
8680787 Veskovic Mar 2014 B2
8704666 Baker, Jr. Apr 2014 B2
8721115 Ing et al. May 2014 B2
8749172 Knapp Jun 2014 B2
8773032 May et al. Jul 2014 B2
8791647 Kesterson et al. Jul 2014 B2
8816600 Elder Aug 2014 B2
8886045 Pederson Nov 2014 B2
8886047 Knapp Nov 2014 B2
8911160 Seo et al. Dec 2014 B2
9386668 Knapp Jul 2016 B2
9509525 Knapp Nov 2016 B2
9848482 Knapp Dec 2017 B2
10210750 Knapp Feb 2019 B2
10847026 Knapp et al. Nov 2020 B2
20010020123 Diab et al. Sep 2001 A1
20010030668 Erten et al. Oct 2001 A1
20020014643 Kubo et al. Feb 2002 A1
20020033981 Keller et al. Mar 2002 A1
20020047624 Stam et al. Apr 2002 A1
20020049933 Nyu Apr 2002 A1
20020134908 Johnson Sep 2002 A1
20020138850 Basil et al. Sep 2002 A1
20020171608 Kanai et al. Nov 2002 A1
20030103413 Jacobi, Jr. et al. Jun 2003 A1
20030122749 Booth, Jr. Jul 2003 A1
20030133491 Shih Jul 2003 A1
20030179721 Shurmantine et al. Sep 2003 A1
20030234342 Gaines Dec 2003 A1
20040044709 Cabrera et al. Mar 2004 A1
20040052076 Mueller et al. Mar 2004 A1
20040052299 Jay et al. Mar 2004 A1
20040101312 Cabrera May 2004 A1
20040136682 Watanabe Jul 2004 A1
20040201793 Anandan et al. Oct 2004 A1
20040208632 Dietz Oct 2004 A1
20040220922 Lovison et al. Nov 2004 A1
20040257311 Kanai et al. Dec 2004 A1
20040263802 Seki et al. Dec 2004 A1
20050004727 Remboski et al. Jan 2005 A1
20050030203 Sharp Feb 2005 A1
20050030267 Tanghe et al. Feb 2005 A1
20050053378 Stanchfield et al. Mar 2005 A1
20050077838 Blumel Apr 2005 A1
20050110777 Geaghan et al. May 2005 A1
20050117190 Iwauchi et al. Jun 2005 A1
20050169643 Franklin Aug 2005 A1
20050200292 Naugler, Jr. et al. Sep 2005 A1
20050207157 Tani Sep 2005 A1
20050242742 Cheang et al. Nov 2005 A1
20050259439 Cull et al. Nov 2005 A1
20050265731 Keum et al. Dec 2005 A1
20060012986 Mazzochette et al. Jan 2006 A1
20060056855 Nakagawa Mar 2006 A1
20060115386 Michaels et al. Jun 2006 A1
20060145887 McMahon Jul 2006 A1
20060164291 Gunnarsson Jul 2006 A1
20060198463 Godin Sep 2006 A1
20060220990 Coushaine et al. Oct 2006 A1
20060227085 Boldt, Jr. et al. Oct 2006 A1
20070007898 Bruning et al. Jan 2007 A1
20070040512 Jungwirth et al. Feb 2007 A1
20070109239 den Boer et al. May 2007 A1
20070132592 Stewart et al. Jun 2007 A1
20070139957 Haim et al. Jun 2007 A1
20070147843 Fujiwara Jun 2007 A1
20070230322 Morita Oct 2007 A1
20070248180 Bowman et al. Oct 2007 A1
20070254694 Nakagwa et al. Nov 2007 A1
20070279346 den Boer et al. Dec 2007 A1
20070291197 Furukawa et al. Dec 2007 A1
20080061717 Bogner et al. Mar 2008 A1
20080067942 Watanabe et al. Mar 2008 A1
20080107029 Hall et al. May 2008 A1
20080120559 Yee May 2008 A1
20080136334 Robinson et al. Jun 2008 A1
20080136770 Peker et al. Jun 2008 A1
20080136771 Chen et al. Jun 2008 A1
20080150864 Bergquist Jun 2008 A1
20080174530 Booth et al. Jul 2008 A1
20080186898 Petite Aug 2008 A1
20080222367 Co Sep 2008 A1
20080235418 Werthen et al. Sep 2008 A1
20080253766 Yu et al. Oct 2008 A1
20080265799 Sibert Oct 2008 A1
20080297066 Meijer et al. Dec 2008 A1
20080297070 Kuenzler et al. Dec 2008 A1
20080304833 Zheng Dec 2008 A1
20080309255 Myers et al. Dec 2008 A1
20080317475 Pederson et al. Dec 2008 A1
20090010654 Shin et al. Jan 2009 A1
20090026978 Robinson Jan 2009 A1
20090040154 Scheibe Feb 2009 A1
20090049295 Erickson et al. Feb 2009 A1
20090051496 Pahlavan et al. Feb 2009 A1
20090121238 Peck May 2009 A1
20090171571 Son et al. Jul 2009 A1
20090189776 Cheron et al. Jul 2009 A1
20090196282 Fellman et al. Aug 2009 A1
20090245101 Kwon et al. Oct 2009 A1
20090278789 Declercq et al. Nov 2009 A1
20090284511 Takasugi et al. Nov 2009 A1
20090303972 Flammer, III Dec 2009 A1
20100005533 Shamir Jan 2010 A1
20100052542 Siemiet Mar 2010 A1
20100054748 Sato Mar 2010 A1
20100061734 Knapp Mar 2010 A1
20100096447 Kwon et al. Apr 2010 A1
20100117543 Van et al. May 2010 A1
20100134021 Ayres Jun 2010 A1
20100134024 Brandes Jun 2010 A1
20100141159 Shiu et al. Jun 2010 A1
20100182294 Roshan Jul 2010 A1
20100188443 Lewis Jul 2010 A1
20100188972 Knapp Jul 2010 A1
20100194299 Ye et al. Aug 2010 A1
20100201274 Deixler Aug 2010 A1
20100213856 Mizusako Aug 2010 A1
20100259931 Chemel et al. Oct 2010 A1
20100272437 Yoon et al. Oct 2010 A1
20100284690 Rajagopal et al. Nov 2010 A1
20100301777 Kraemer Dec 2010 A1
20100327764 Knapp Dec 2010 A1
20110002695 Choi et al. Jan 2011 A1
20110031894 Van De Ven Feb 2011 A1
20110044343 Sethuram et al. Feb 2011 A1
20110052214 Shimada et al. Mar 2011 A1
20110062874 Knapp Mar 2011 A1
20110063214 Knapp Mar 2011 A1
20110063268 Knapp Mar 2011 A1
20110064420 Rajagopal et al. Mar 2011 A1
20110068699 Knapp Mar 2011 A1
20110069094 Knapp Mar 2011 A1
20110069960 Knapp et al. Mar 2011 A1
20110076024 Damink Mar 2011 A1
20110133654 McKenzie et al. Jun 2011 A1
20110148315 Van Der Veen et al. Jun 2011 A1
20110150028 Nguyen et al. Jun 2011 A1
20110248640 Welten Oct 2011 A1
20110253915 Knapp Oct 2011 A1
20110299854 Jonsson et al. Dec 2011 A1
20110309754 Ashdown et al. Dec 2011 A1
20120001567 Knapp Jan 2012 A1
20120056545 Radermacher et al. Mar 2012 A1
20120153839 Farley et al. Jun 2012 A1
20120229032 Van De Ven et al. Sep 2012 A1
20120235579 Chemel et al. Sep 2012 A1
20120299481 Stevens Nov 2012 A1
20120306370 Van De Ven et al. Dec 2012 A1
20130016978 Son et al. Jan 2013 A1
20130088522 Gettemy et al. Apr 2013 A1
20130108275 Knutson et al. May 2013 A1
20130183042 Knapp et al. Jul 2013 A1
20130201690 Vissenberg et al. Aug 2013 A1
20130257314 Alvord et al. Oct 2013 A1
20130293147 Rogers et al. Nov 2013 A1
20140028377 Rosik et al. Jan 2014 A1
20150022110 Sisto Jan 2015 A1
20180233030 Knapp Aug 2018 A1
20220299190 Chemel et al. Sep 2022 A1
Foreign Referenced Citations (45)
Number Date Country
1291282 Apr 2001 CN
1396616 Feb 2003 CN
1573881 Feb 2005 CN
1650673 Aug 2005 CN
1849707 Oct 2006 CN
101083866 Dec 2007 CN
101150904 Mar 2008 CN
101322441 Dec 2008 CN
101331798 Dec 2008 CN
101458067 Jun 2009 CN
0196347 Oct 1986 EP
0456462 Nov 1991 EP
2273851 Jan 2011 EP
2307577 May 1997 GB
06-302384 Oct 1994 JP
08-201472 Aug 1996 JP
11-025822 Jan 1999 JP
2000286067 Oct 2000 JP
2001-514432 Sep 2001 JP
2002353900 Dec 2002 JP
2004-325643 Nov 2004 JP
2005-539247 Dec 2005 JP
2006093450 Apr 2006 JP
2006-260927 Sep 2006 JP
2007047352 Feb 2007 JP
2007-266974 Oct 2007 JP
2007-267037 Oct 2007 JP
2008500583 Jan 2008 JP
2008-507150 Mar 2008 JP
2008-300152 Dec 2008 JP
2009-134877 Jun 2009 JP
20080073172 Aug 2008 KR
20080077353 Aug 2008 KR
9910867 Mar 1999 WO
0037904 Jun 2000 WO
03075617 Sep 2003 WO
2005024898 Mar 2005 WO
2007069149 Jun 2007 WO
2008065607 Jun 2008 WO
2008129453 Oct 2008 WO
2008152922 Dec 2008 WO
2010124315 Nov 2010 WO
2012005771 Jan 2012 WO
2012042429 Apr 2012 WO
2013142437 Sep 2013 WO
Non-Patent Literature Citations (98)
Entry
PCT/US2009/004953, “International Preliminary Report on Patentability and Written Opinion,” dated Mar. 8, 2011.
Hall et al., “Jet Engine Control Using Ethernet with a Brain (Postprint),” AIAA/ASME/SAE/ASEE Joint Propulsion Conference and Exhibition, Jul. 2008, pp. 1-18.
Kebemou, “A Partitioning-Centric Approach for the Modeling and the Methodical Design of Automotive Embedded System Architectures,” Dissertation of Technical University of Berlin, 2008, 176 pages.
O'Brien et al., “Visible Light Communications and Other Developments in Optical Wireless,” Wireless World Research Forum, 2006, 26 pages.
Zalewski et al., “Safety Issues in Avionics and Automotive Databuses,” IFAC World Congress, Jul. 2005, 6 pages.
“Visible Light Communication: Tutorial,” Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs), Mar. 2008.
International Search Report & Written Opinion, PCT/US2010/000219, mailed Oct. 12, 2010.
International Search Report & Written Opinion, PCT/US2010/002171, mailed Nov. 24, 2010.
International Search Report & Written Opinion, PCT/US2010/004953, mailed Mar. 22, 2010.
International Search Report & Written Opinion, PCT/US2010/001919, mailed Feb. 24, 2011.
U.S. Appl. No. 12/924,628, filed Sep. 30, 2010.
Office Action mailed May 12, 2011 for U.S. Appl. No. 12/360,467.
Final Office Action mailed Nov. 28, 2011 for U.S. Appl. No. 12/360,467.
Notice of Allowance mailed Jan. 20, 2012 for U.S. Appl. No. 12/360,467.
Office Action Mailed Feb. 1, 2012 for U.S. Appl. No. 12/584,143.
Final Office Action Mailed Sep. 12, 2012 for U.S. Appl. No. 12/584,143.
Office Action Mailed Aug. 2, 2012 for U.S. Appl. No. 12/806,114.
Office Action Mailed Oct. 2, 2012 for U.S. Appl. No. 12/806,117.
Office Action Mailed Jul. 11, 2012 for U.S. Appl. No. 12/806,121.
Final Office Action Mailed Oct. 11, 2012 for U.S. Appl. No. 12/806,121.
Office Action mailed Dec. 17, 2012 for U.S. Appl. No. 12/806,118.
Office Action mailed Oct. 9, 2012 for U.S. Appl. No. 12/806,126.
Office Action mailed Jul. 10, 2012 for U.S. Appl. No. 12/806,113.
Notice of Allowance mailed Oct. 15, 2012 for U.S. Appl. No. 12/806,113.
International Search Report & Written Opinion mailed Sep. 19, 2012 for PCT/US2012/045392.
Partial International Search Report mailed Nov. 16, 2012 for PCT/US2012/052774.
Office Action mailed Nov. 4, 2013 for CN Application No. 201080032373.7.
Notice of Allowance mailed Jan. 28, 2014 for U.S. Appl. No. 13/178,686.
Notice of Allowance mailed Feb. 21, 2014 for U.S. Appl. No. 12/806,118.
Office Action mailed Apr. 22, 2014 for U.S. Appl. No. 12/806,114.
International Search Report & Written Opinion for PCT/US2012/052774 mailed Feb. 4, 2013.
Notice of Allowance mailed Feb. 4, 2013 for U.S. Appl. No. 12/809,113.
Notice of Allowance mailed Feb. 25, 2013 for U.S. Appl. No. 12/806,121.
Notice of Allowance mailed May 3, 2013 for U.S. Appl. No. 12/806,126.
International Search Report & Written Opinion, PCT/US2013/027157, May 16, 2013.
Office Action mailed Jun. 10, 2013 for U.S. Appl. No. 12/924,628.
Office Action mailed Jun. 27, 2013 for U.S. Appl. No. 13/178,686.
Final Office Action mailed Jul. 9, 2013 for U.S. Appl. No. 12/806,118.
Final Office Action mailed Jun. 14, 2013 for U.S. Appl. No. 12/806,117.
Johnson, “Visibile Light Communications,” CTC Tech Brief, Nov. 2009, 2 pages.
Chonko, “Use Forward Voltage Drop to Measure Junction Temperature,” © 2013 Penton Media, Inc., 5 pages.
Office Action mailed Oct. 24, 2013 for U.S. Appl. No. 12/806,117.
Notice of Allowance mailed Oct. 31, 2013 for U.S. Appl. No. 12/924,628.
Office Action mailed Nov. 12, 2013 for U.S. Appl. No. 13/231,077.
Final Office Action mailed Jun. 18, 2014 for U.S. Appl. No. 13/231,077.
Office Action mailed Jun. 23, 2014 for U.S. Appl. No. 12/806,117.
Notice of Allowance mailed Aug. 21, 2014 for U.S. Appl. No. 12/584,143.
Office Action mailed Sep. 10, 2014 for U.S. Appl. No. 12/803,805.
“Color Management of a Red, Green, and Blue LED Combinational Light Source,” Avago Technologies, Mar. 2010, pp. 1-8.
Office Action mailed Jan. 28, 2015 for U.S. Appl. No. 12/806,117.
Office Action mailed Feb. 2, 2015 for CN Application 201080035731.
Office Action mailed Jul. 1, 2014 for JP Application 2012-520587.
Office Action mailed Feb. 17, 2015 for JP Application 2012-520587.
Office Action mailed Mar. 11, 2014 for JP Application 2012-523605.
Office Action mailed Sep. 24, 2014 for JP Application 2012-523605.
Office Action mailed Mar. 25, 2015 for U.S. Appl. No. 14/305,472.
Notice of Allowance mailed Mar. 30, 2015 for U.S. Appl. No. 14/097,355.
Office Action mailed Apr. 8, 2015 for U.S. Appl. No. 14/305,456.
Notice of Allowance mailed May 22, 2015 for U.S. Appl. No. 14/510,212.
Office Action mailed May 27, 2015 for U.S. Appl. No. 12/806,117.
Partial International Search Report mailed Mar. 27, 2015 for PCT/U82014/068556.
“LED Fundamentals, How to Read a Datasheet (Part 2 of 2) Characteristic Curves, Dimensions and Packaging,” Aug. 19, 2011, OSRAM Opto Semiconductors, 17 pages.
International Search Report & Written Opinion for PCT/U82014/068556 mailed June 22, 2015.
Office Action for U.S. Appl. No. 13/970,964 mailed Jun. 29, 2015.
Office Action for U.S. Appl. No. 14/510,243 mailed Jul. 28, 2015.
Office Action for U.S. Appl. No. 14/510,283 mailed Jul. 29, 2015.
Office Action for U.S. Appl. No. 14/510,266 mailed Jul. 31, 2015.
Office Action for U.S. Appl. No. 13/970,990 mailed Aug. 20, 2015.
Partial International Search Report for PCT/U82015/037660 mailed Aug. 21, 2015.
Final Office Action for U.S. Appl. No. 13/773,322 mailed Sep. 2, 2015.
Notice of Allowance for U.S. Appl. No. 13/970,944 mailed Sep. 11, 2015.
Notice of Allowance for U.S. Appl. No. 14/604,886 mailed Sep. 25, 2015.
Notice of Allowance for U.S. Appl. No. 14/604,881 mailed Oct. 9, 2015.
International Search Report & Written Opinion for PCT/U82015/037660 mailed Oct. 28, 2015.
Office Action for U.S. Appl. No. 14/573,207 mailed Nov. 4, 2015.
Notice of Allowance for U.S. Appl. No. 14/510,243 mailed Nov. 6, 2015.
Bouchet et al., “Visible-light communication system enabling 73 Mb/s data streaming,” IEEE Globecom Workshop on Optical Wireless Communications, 2010, pp. 1042-1046.
Notice of Allowance for U.S. Appl. No. 12/806,117 mailed Nov. 18, 2015.
Partial International Search Report for PCT/US2015/045252 mailed Nov. 18, 2015.
Office Action mailed Mar. 6, 2015 for U.S. Appl. No. 13/733,322.
International Preliminary Report on Patentability, Int'l Application PCT/US2010/001919, Jan. 17, 2012, 6 pages.
International Preliminary Report on Patentability, Int'l Application PCT/US2010/002171, Feb. 7, 2012, 5 pages.
Office Action, U.S. Appl. No. 12/803,805, Dec. 4, 2013, 19 pages.
Search Report by Registered Search Organization, JP Application 2012-523605, Feb. 25, 2014, 15 pages.
The Second Office Action, CN Application 2010-80032373.7, Apr. 15, 2014, 5 pages.
Search Report by Registered Search Organization, JP Application 2012-520587, May 30, 2014, 10 pages.
The First Office Action, CN Application 2010-80035731.X, Jun. 5, 2014, 5 pages.
Notification to Grant Patent Right for Invention, CN Application 2010-80032373.7, Aug. 6, 2014, 2 pages.
Final Office Action, U.S. Appl. No. 12/803,805, Jun. 23, 2015, 33 pages.
Notification to Grant Patent Right for Invention, CN Application 2010-80035731.X, Aug. 6, 2015, 2 pages.
Decision to Grant a Patent, JP Application 2012-520587, Oct. 21, 2015, 2 pages.
Notification of Reason for Refusal, KR Application 10-2012-7003792, Mar. 7, 2016, 7 pages.
Notification of Reason for Refusal, KR Application 10-2012-7005884, Apr. 28, 2016, 3 pages.
Notice of Final Rejection, KR Application 10-2012-7003792, Jun. 22, 2016, 1 page.
Notice of Final Rejection, KR Application 10-2012-7005884, Jul. 20, 2016, 1 page.
European Search Report and Search Opinion, EPC Application 10800143.9, Feb. 24, 2017, 10 pages.
Supplementary Partial European Search Report, EPC Application 10806752.1, Mar. 8, 2017, 6 pages.
European Search Report and European Search Opinion, EPC Application 10806752.1, Jun. 9, 2017, 12 pages.
Provisional Applications (8)
Number Date Country
61224904 Jul 2009 US
61273518 Aug 2009 US
61273536 Aug 2009 US
61277871 Sep 2009 US
61281046 Nov 2009 US
61336242 Jan 2010 US
61339273 Mar 2010 US
61094595 Sep 2008 US
Divisions (1)
Number Date Country
Parent 12803805 Jul 2010 US
Child 16721214 US
Continuation in Parts (2)
Number Date Country
Parent 12360467 Jan 2009 US
Child 12803805 US
Parent 12584143 Sep 2009 US
Child 12803805 US
Reissues (1)
Number Date Country
Parent 15296258 Oct 2016 US
Child 16721214 US