1. Field of the Invention
This invention relates to illumination devices and, more particularly, to controlling illumination devices.
2. Description of Related Art
A wide variety of lighting control systems are currently commercially available for controlling a variety of lighting features from simple on/off switching to complex color adjustment and performance monitoring. Such systems also communicate according to a wide variety of protocols over various communication channels. As an example, a simple system could be just a triac dimmer and a single lamp. As another example, a complex system could be a hierarchical campus wide network. In such a complex system, up to 64 intelligent fluorescent lamp ballasts within a room or group of rooms could be wired together using the Digital Addressable Lighting Interface (DALI) standard, for instance, with an Ethernet enabled DALI controller, which then communicates with other DALI controllers and a computer server over Ethernet within each building. At the top layer of the hierarchy, the computer servers in different buildings within a campus could communicate over the Internet using Internet Protocol (IP).
Some lighting control systems use protocols that are somewhat specific to lighting, such as 0-10V, DMX512, DALI, and Dynalite, while others use protocols that target building automation in general, such as X10, LonWorks, C-Bus, and ZigBee. Still other lighting control systems use industry standard networking protocols such as Ethernet, Wi-Fi, and HomePlug. At the campus wide level with communication over the Internet, such complex lighting control systems can also use telecom networking protocols such as SONET and ATM. All theses standards and protocols communicate at different rates, using different modulation and packetizing schemes, over various communication channels. Such channels include powerline for X10 and HomePlug, RF for ZigBee and Wi-Fi, optical fiber for SONET, and dedicated wires for most of the others including 2 wire DC for 0-10V, twisted pair for DALI and others, and CAT5 for Ethernet.
The 0-10V standard was one of the earliest and simplest lighting control signaling system, which is still supported by many fluorescent ballasts produced by companies such as GE, Philips, and Sylvania. Such ballasts produce light from an attached fluorescent lamp that is proportional to the DC voltage input to the ballast through two wires. Although simple to understand and implement, each ballast must have a dedicated cable to the system controller, which can become very expensive and cumbersome in large installations. Additionally, such a lighting control system can only control light level and cannot extract information from the ballast, such as if a bulb has burned out.
The DMX512 stands for “Digital Multiplex with 512 pieces of information” and is a standard for digital communication commonly used in theaters and production studios. DMX512 communicates over shielded twisted pair cable using EIA-485 standard voltages levels with node connected together in a daisy chain manner. Data is sent one byte per packet at 250 kbaud in a manner similar to RS232. The DMX512 protocol is popular for stage lighting due to the robustness of its cable and the relatively long communication distances.
The DALI standard, which is becoming relatively popular for commercial lighting systems, is similar to DMX512 in that various lamps can be individually controlled using a relatively low data rate digital control bus, however, there are many differences ranging from the type of communication cable and interconnections to data format and messaging requirements. While DMX512 communicates uni-directionally over shielded twisted pair cable between two nodes, DALI communicates bi-directionally over un-shielded twisted pair that can be tapped by up to 64 devices. While all DMX512 data frame comprise one start bit, 8 data bits, and two stop bits, DALI has different sized frames for communication in the different directions with both acknowledge and data bytes in one direction and no acknowledge in the other direction.
Unlike DALI, DMX512, 0-10v, and other protocols developed specifically for lighting, X10 was developed for general home automation of which lighting is an important subset. A further substantial difference is that X10 typically communicates data over the power lines that are already connected to most devices. X10 devices typically communicate one bit of information around each zero crossing of a 50 or 60 Hz AC mains cycle, by coupling bursts of a high frequency signal onto the powerline. As such, the data rate is very low. To compensate, the protocol is very simple in which all packets consist of an 8 bit address and a 4 bit command Since only 16 commands are possible, functionality is limited.
HomePlug is another protocol that uses the power line for communication, however, unlike X10, which was architected for home automation, HomePlug was designed to allow products communicate with each other and the Internet through existing home electrical wiring. A variety of versions of HomePlug have been released with data rates ranging from 10 to 200 Mbit/s. HomePlug achieves such data rates using adaptive modulation and complex error correction algorithms on over a thousand Orthogonal Frequency Division Multiplexed (OFDM) sub-carriers.
Data in a HomePlug network is typically communicated in Ethernet compatible packets, which comprise of a header with about 22 bytes, the payload with up to 1500 bytes, and a CRC code with 4 bytes, however, HomePlug also provides a variety of higher level services that provide, among other things, guaranteed delivery, fixed latency, quasi-error free service, and jitter control. As such, a HomePlug interface is much more complicated than is needed for simply lighting control.
Although communication over a power line is a good solution for some building networking applications, there are some drawbacks. For instance, there can be excessive attenuation between different phases of typically three phase systems, which can be overcome by active repeaters or sometimes with special capacitors. Additionally, signals can propagate through the power line between different buildings causing interference and security concerns. When appliances turn on and off significant noise is generated that can corrupt transmission. HomePlug physical layer interfaces have overcome some of such issues at the expense of complex analog and digital signal processing.
LonWorks is a building automation protocol that typically uses either twisted pair cable at 78 kbit/sec or the power line at a few kilobits per second for the communication channel. For communication over the power line, LonWorks uses dual carrier frequency operation in which messages are sent using one carrier frequency and, if a response is not received, the message is sent a second time using a second carrier frequency. More recent releases of the protocol allow IP data frames to be communicated across a LonWorks network, and a library of commands for a wide variety of appliances and functions have been and continue to be developed for a range of residential and commercial applications.
The C-Bus Protocol targets home automation systems as well as commercial lighting systems. Unlike the X10 protocol, C-Bus typically uses dedicated CAT5 cables and is considered by some to be more robust as a result. Ethernet also typically uses CAT5 cable for communicating between devices in a star topology with a router or switch at the center. Common data rates include 10, 100, and 1000 Mbit/sec, which are all deployed widely worldwide for computer networking. As mentioned previously, Ethernet data frames comprise a header of typically 22 bytes, a payload of up to 1500 bytes, and a CRC of four bytes. In many applications, the payload of an Ethernet frame is an Internet Protocol (IP) packet. Although overkill for simple lighting systems, Ethernet comprises the backbone of a variety of building lighting control networks, such as those from LumEnergi and others.
ZigBee comprises a group of high level communication protocols that typically use the IEEE 802.15.4-2003 standard for Wireless Personal Area Networks (WPANs) as the physical layer. As such, ZigBee typically uses small low power radios to communicate between appliances, light switches, consumer electronic, and other devices in a residence for instance. IEEE 802.15.4 uses either the 868 MHz, 915 MHz, or 2.4 GHz radio frequency bands. Data is direct-sequence spread spectrum coded and then Binary Phase Shift Key (BPSK) or Orthogonal Quadrature Phase Shift Key (OQPSK) modulated prior to transmission. Data is communicated in one of four different types of frames with variable data payload. Such frames include beacon frames, which specify a super-frame structure similar to that of HomePlug, data frames used for transfers of data, acknowledge frames used for confirming reception, and MAC command frame used for controlling the network. The SuperFrame structure allows certain devices guaranteed bandwidth and provides shared bandwidth for other devices. Many aspects of the network enable very low power communication with battery powered devices.
Wi-Fi or 802.11 is a very common wireless network for data communication between computers. A number of versions of the protocol including 802.11a, 802.11b, and 802.11g have been released over the years. The recent version, 802.11g, operates at the 2.4 GHz band and uses Orthogonal Frequency Division Multiplexing (OFDM) and typically achieves about 22 Mbit/sec average throughput. Similar to Ethernet, Wi-Fi frames comprise of a header, payload, and CRC. Similar to 802.15.4, Wi-Fi has a variety of different types of frames for communication management. In general, Internet Protocol (IP) and the associated Transport Control Protocol (TCP) run over Wi-Fi networks.
Although wireless protocols such as ZigBee and Wi-Fi do not need dedicated wires to communicate between devices, nor do they have the limitation previously mentioned associated with power line communication, such wireless networks can be limited by congestion in the increasingly crowded RF spectrum. Additionally, different countries in the world allocate spectrum differently which forces devices to sometimes operate in different frequency bands.
An alternative physical layer communication channel and associated network protocol for lighting control among other applications have been introduced that use modulated visible light traveling through free space to communicate data. According to such visible light communication (VLC) protocol, all devices synchronize to a frequency or phase of the AC mains for instance and produce gaps during which messages can be sent. At other times, lamps using LEDs or any other type of light source, simply produce illumination. During the gap times some number of bytes of data can be sent from one lamp to one or more other lamps that can comprise a complete message in itself, or such data can accumulate over any number of gaps to produce much larger messages.
Using visible light to communicate between lamps and other devices in a lighting system has many advantages over wired, wireless, and powerline communication networks such as those previously described. No dedicated wires are needed, which is important especially for installation in existing buildings. The visible light spectrum is unregulated globally and does not suffer from the congestion and interference common in RF wireless communication. Electrical noise on the powerline, from appliances turning on and off for instance, does not affect communication integrity as in powerline communication protocols. No expensive and complicated analog and digital signal processing is necessary to modulate and demodulate data as in many wireless and powerline protocols. The light source needed to transmit data is necessary anyway to provide illumination, and in the case that the light source is one or more LEDs, the LEDs can operate as the light detector as well. As such, the visible light communication protocol can be implemented in an LED lamp for virtually no additional cost.
A limitation of such a visible light communication protocol is that data cannot be communicated through walls between various rooms in a building. Another limitation is that, other than the remote controller, it is difficult to cost effectively control such a visible light communication network. The invention described herein, in various embodiments, provides solutions to overcome these limitations.
According to one embodiment, an electronic device is provided herein for controlling a lighting system. In certain exemplary embodiments, the electronic device is mounted to a wall in a room or held in a hand, for instance, and comprises a Human Machine Interface (HMI), such as a touch screen or a set of buttons (e.g., dedicated to specific lighting functions or programmable to perform a variety of functions) that are illuminated by a light source. In addition to illuminating the HMI, the light source also transmits messages through free space using visible light to one or more lamps in the room. For example, a HMI could comprise an LCD panel, which is illuminated by an LED backlight for displaying information about the controls or lighting system, and either an overlaid touch screen sensor or additional pushbuttons for entering information. Alternatively, the HMI could comprise just pushbuttons that are illuminated by some light source for use in the dark.
For a handheld electronic device (otherwise referred to herein as a wireless communication device), such as a smart phone or tablet computer, the display backlight could be modulated in a variety of ways including playing a video with alternating light and dark frames to produce light modulated with data. The ambient light sensor available on many handheld electronic devices could be used to receive data transmitted through free space using visible light. An alternative light source in many handheld electronic devices such as smart phones is the camera flash, which typically comprises one or more LEDs that can be modulated through software to transmit data through free space using visible light.
As another example, the light source in an electronic device that is mounted to a wall, for instance, can be synchronized to a frequency or phase of the AC mains, produce communication gaps that are synchronous to the communication gaps used by lamps in the room, and transmit data to the lamps in response to input from a user. Additionally, such an electronic device can have a light detector for receiving information from the lamps that is transmitted through free space using visible light. If the light source is one or more LEDs, then the LEDs can be both the light source and the light detector. In a further embodiment, the light produced by a light source in the electronic device is perceived as unchanging by a user independent of whether data is being transmitted or not. This is accomplished, for instance, by producing a small amount of light continuously when data is not being transmitted and by turning this small amount of light off before or after data is transmitted at high brightness for instance. In this exemplary embodiment, control circuitry within the electronic device is configured to produce commands in response to input directly from a user.
In certain exemplary embodiments, an electronic device comprising an HMI with a light source and a light detector also comprises circuitry to interface to any type of data communication network typically used for lighting or building control information. Such data communication network could communicate over dedicated wires (e.g., Ethernet, DALI, DMX512, and others), the power line (e.g., X10, HomePlug, and others), RF wireless (e.g., ZigBee, Wi-Fi, and others), or any other communication channel including for instance fiber optic cable and wireless infra-red. Such data communication network could interface for instance to a central building controller over Ethernet or DALI, or could interface for instance to a wireless communication device (such as a smartphone) over Wi-Fi, Bluetooth, IRDA, or any other data communication protocol supported by such wireless communication device. In some instances, the electronic device could comprise interfaces to multiple data communication networks, such as Ethernet and Wi-Fi, to support lighting control systems with mixed environments.
In an electronic device comprising an HMI that can communicate through free space using visible light, and interfaces to one or more data communication networks, control circuitry would receive input directly from the user through the HMI, data received from such data communication networks, or data received optically through free space. Such control circuitry in response to such input or data would produce commands encoded and transmitted according to a visible light communication protocol.
In certain exemplary embodiments, a lamp comprises a light source for illuminating an area and transmitting data through free space using visible light, a light detector for receiving data transmitted through free space using visible light, and an interface to one or more other types of data communication networks that carry lighting control information. If one or more LEDs can operate as the light source, then such LEDs could also be operable as both the light source and the light detector. The data communication network could communicate with the lamp over any type of communication channel and communication protocol. The lamp could be a lamp in a ceiling, for instance. In such a lamp, control circuitry receives input from one or more such data communication network or networks and produces commands encoded and transmitted according to a visible light communication protocol such as that described in the one or more priority applications listed herein.
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.
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.
Turning now to the drawings,
In example room1 13, electronic device 16 interfaces between network 12, lamps 17, 18, and 19, and optionally wireless communication device 20. Wireless communication device 20 may or may not be part of building lighting system 10, but if included, can be any type of mobile device including but not limited to mobile phones, smart phones, personal digital assistants (PDA), and mobile computers such as netbooks, notebooks, and laptops. Wireless communication device 20 could also be a stationary device, such as a desktop computer. In some embodiments, wireless communication device 20 may communicate with electronic device 16 using any radio or infra-red frequency wireless communication protocol including, but not limited to, Zigbee, Wi-Fi, and Bluetooth. In some embodiments, wireless communication device 20 may be configured for controlling the lighting system, similar to electronic device 16, and may be considered to be a hand held electronic device.
Network 12 typically might communicate according to the wired DALI or Ethernet standards, or the wireless ZigBee or Wi-Fi standards, but could communicate according to any data communication protocol using wired, wireless, powerline, fiber optic, or any other type of communication channels. Network 12 and optional wireless communication device 20 can communicate according to the same or different wireless protocols, or can communicate over different protocols using different wired or wireless communication channels.
Electronic device 16 represents any electronic device that provides an interface between lamps 17, 18 and 19 and network 12, and that also provides a human machine interface (HMI) 21. HMI 21 is configured to receive input from a user, which is typically used, but not limited to, local control of lamps 17, 18, and 19 in room1 13, for instance. In one embodiment, electronic device 16 could be a device mounted on a wall within room1 13 that enables a user to control the lighting within room1 13 independent of and/or overriding commands from building controller 11. Electronic device 16 could be a device about the size of a conventional light switch or a ganged light switch. In one example, electronic device 16 could be implemented with an HMI 21, such as a display and touch screen that enables a user to select lighting functions from a menu or nested menus for instance. Electronic device 16 also, for instance, could be implemented with an HMI 21, such as a set of buttons that are dedicated to particular functions, such as on/off, dimming, color, timing, and other functions such as those described in the one or more priority application listed herein.
In the example lighting system of
In order for the HMI 21 to be visible in the dark, for instance, the electronic device typically comprises a backlight (or a light source positioned behind the HMI) that illuminates the HMI (e.g., various push buttons or an LCD display with an overlaid touch screen sensor) from behind. Many possible HMIs are possible with the commonality that a light source is typically necessary for a user to see in at least a dark environment. Such a light source typically will be an LED or array of LEDs, but could comprise any type of light source including, for instance, Cold Cathode Fluorescent lamps (CCFL). If the light source is a CCFL or, for instance, a white LED with a phosphor coating, preferentially the electronic device also comprises an additional photo-detector.
According to one embodiment of the invention, the light emitted from the backlight of the HMI is modulated in such a way that one or more of lamps 17, 18, and 19 can detect the data represented by such modulation. In some embodiments, electronic device 16 can also receive data sent by lamps 17, 18, or 19, e.g., through the additional photo-detector, or through the backlight. For example, if the backlight comprises one or more LEDs for illumination and data transmission, and preferentially mono-chromatic LEDs such as red, green, and blue, the LEDs used for illumination and data transmission may also be used to receive data sent by lamps 17, 18, or 19.
According to another embodiment of the invention, wireless communication device 20, which could be any type of computing device with a backlit display such as a smart phone, PDA, or a tablet, netbook, notebook, or desktop computer, may communicate directly with electronic device 16 or with lamps 17, 18, and 19 through free space using visible light. For example, wireless communication device 20 may produce commands in response to input received directly from a user, and may transmit such commands to the electronic device 16 or directly to the lamps 17, 18 and 19 using visible light. As with electronic device 16, the backlight for the display of the wireless communication device 20 can be modulated to transmit data or commands optically to the electronic device 16 or directly to lamps 17, 18, and 19. This can be accomplished in various ways including, but not limited to, playing a video with alternating light and dark frames producing the transmitted data. The ambient light sensor available on many wireless communication devices can also be used as a light sensor to receive data. Alternatively, the camera flash, which typically comprises one or more LEDs on a smart phone, for instance, can also be modulated through software to transmit data to electronic device 16 or to lamps 17, 18, and 19 in the example of
According to another embodiment, a lamp may be used to interface with the network 12 instead of an electronic device. As represented by room2 14, for instance, lamp 22 provides an interface between the lamps 22, 23, and 24 within room2 14 and network 12. As such, lamp 22 comprises a network interface, which is capable of communicating with network 12 according to any protocol using any communication channel including, but not limited to, RF wireless, wired, fiber optic, or power line. In this example room2 14, lamp 22 further comprises a light source for illumination and data transmission, and a light detector for receiving data from lamps 23 and 24. In one embodiment of the invention, if the light source is one or more LEDs, then such LEDs can also operate as the light detector depending on when data is to be sent or received.
As in example room1 13 and wireless communication device 20, wireless communication device 25 in room2 14, for instance, can locally control lamps 22, 23, and 24 by overriding commands from building controller 11 or can implement any functionality supported by lighting system 10. In this example room2 14, wireless communication device 25 communicates with lamp 22, which also provides the interface to network 12. As such, according to one embodiment of the invention, lamp 22 further comprises a wireless interface compatible with wireless (RF, infra-red, etc) communication device 25 and an interface compatible with network 12.
Within the example room1 13 and room2 14, lamps 17, 18, and 19, and lamps 22, 23, and 24 respectively communicate between each other using modulated visible light. When observed by the human eye, although the light is visible, the modulation of the light is typically not discernable and is typically perceived as constant and unchanging light. The maximum distance between any two lamps, for instance lamps 17 and 18, is determined by the brightness and directionality of the data transmitting lamp and the light detection sensitivity of the data receiving lamp. In the example room1 13, lamps 17 and 18 are positioned within such maximum communication distance, and lamps 17 and 19 for instance are positioned beyond such maximum communication distance. According to another embodiment of the invention, lamp 18 in the example room1 13 relays messages sent through modulated visible light between lamps 17 and 19 to enable communication between large numbers of lamps that are large distances apart.
According to the invention, lamps that relay commands first receive data on a light detector and forward such input to control circuitry that regenerates commands in response to such input. For instance, commands can be directed from lamp 17 to lamp 19 only, while lamp 18 simply receives and retransmits such commands along a dedicated path as in the Internet. Alternatively, messages from an example lamp 17 can be broadcast to all lamps in which lamp 18 for instance responds to such broadcast command and also retransmits such command to lamp 19 for instance. As such, commands can be sent through a network of lamps as broadcast messages or through dedicated or ad-hoc paths between particular lamps or groups of lamps. Ad-hoc paths are well known to those practicing in the field of mesh networking, which is commonly used in Zigbee wireless networks for instance.
The embodiments of the invention illustrated by this example
Preferentially, lamps 17, 18, 19, 22, 23, and 24 and optionally electronic device 16 communicate between each other in synchronization with the AC mains 31, as described in one or more priority applications listed herein; however, such devices could communicate according to any communication protocol that uses visible light traveling through free space. Such communication can be between devices that are in or out of synchronization and according to any modulation technique, data rate, or distance. Likewise, any routing or mesh networking protocol can be implemented using such devices that receive and retransmit commands optically through free space. As noted herein, the term “free space” refers to communication within space, but not confined to, for example, an optical fiber. Thus, transfer of commands occurs optically, but not constrained within an optical fiber or any other type of waveguide device, yet is free and able to travel optically in any non-obstructed direction. The example of a building lighting system 10 does not limit the embodiment to a single building, but can be among several buildings or within a portion of the building. Moreover, each room shown in the lighting system 10 is configured according to one example if, for example, there are several rooms controlled by a lighting system. If the system controls only a single room, then the example in
Thus, the lighting system can be controlled with an electronic device 16 that comprises a HMI 21 and provides an interface between lamps 17, 18, 19 and network 12. Alternatively, the lighting system can be controlled with a wireless communication device, e.g., device 25, and interface to the network 12 can be achieved solely with a light source (e.g., lamp 22), which can also function as a light detector. In this case, the HMI can be achieved by a wireless communication device (e.g., device 25) that need not be configured between the lamps 22, 23, and 24 and the network 12.
Accordingly, an electronic device is provided herein having both a light source and a light detector, as well as control circuitry, which is configured to produce commands for controlling the lighting system in response to received input and/or data. The electronic device can further comprise an HMI configured to receive input from a user, and/or a network interface configured to receive data from a network, depending on the configuration shown in the examples of
As shown in
PLI 35 typically comprises an LED driver circuit (not shown) that produces a substantially DC current to produce illumination from LEDs 36 and modulated current to transmit data from LEDs 36. Such substantially AC and DC currents can be combined in many different ways to produce both illumination and transmit data using the same light source. Periodic time slots can be produced in synchronization with the AC mains 31 during which the example DC current is turned off and the example AC current is turned on during gaps in which data is transmitted.
PLI 35 also typically comprises a receiver circuit (not shown) that in this example
VLC network controller 34 interfaces with PLI 35 and memory 37 to receive commands transmitted using visible light through free space, to implement the necessary control circuit functionality of lamp 30, and in some cases, re-transmit commands using LEDs 36 that were previously received by LEDs 36 during gap times. Commands received by the light detector, in this case LEDs 36, can be stored in memory 37 and further processed. Commands that target lamp 30 can be interpreted by VLC network controller 34 and processed locally. For instance, the brightness or color of LEDs 36 can be adjusted by adjusting the substantially DC current applied to LEDs 36 by the driver function within PLI 35. Commands that target other or additional lamps can be stored in memory 37 and re-transmitted by PLI 35 and LEDs 36 during subsequent gap times for instance. Such commands can be routed through a pre-determined path, through an ad-hoc mesh network, or broadcast to all electronic devices for instance. VLC network controller 34 may be configured to communicate such commands according to a visible light communication protocol.
In this example
In this example lamp 40, LEDs 36 operate as both the light source and the light detector for transmitting and receiving data using visible light communicated through free space. LEDs 36 also provide illumination. Wireless 802.11 interface 43 can receive messages from wireless communication devices (e.g., a smart phone) 20 and 25, or from building controller 11, and can forward such messages to processor 42, which can implement the control circuitry functionality necessary to interpret or translate such messages to commands that can be transmitted through free space using visible light (e.g., using LEDs 36 as the light source). Likewise, commands transmitted optically through free space can be received by LEDs 36 operating as light detectors, interpreted or translated by processor 42, and transmitted by Wi-Fi interface 43 back to wireless communication devices 20 and 25 or building controller 11.
Whether or not a lamp includes a processor and separate Wi-Fi interface, as shown in
In the example lamp 40 illustrated in
Wi-Fi interface 43 is just one example of many different network interfaces using many different types of communication channels that are possible. It is also possible to have multiple interfaces to different networks. Some other network examples include X10, DMX512, DALI, Ethernet, ZigBee, HomePlug, LonWorks, C-Bus, Dynalite, Bluetooth, and even SONET and ATM. A typical configuration for lamp 22 in
Electronic device 16 communicates with building controller 11 through network 12 according to any one of many different data communication protocols over any of a variety communication channels including but not limited to CAT5 or twisted pair cable, RF wireless, powerline or fiber optics. Although it need not communicate with device 20, electronic device 16 can also optionally communicate with wireless communication device 20 (which could be a smart phone) using any one of many different RF, infrared, or other wireless communication protocols, including but not limited to Wi-Fi, ZigBee, Bluetooth, IRDA, or others. According to one embodiment of the invention, electronic device 16 communicates with lamps 17, 18, or 19 through free space using modulated visible light that also provides illumination for electronic device 16.
In this example
In this example
The protocol for communicating through free space using visible light can be the same as, or different from, the protocol described in one or more priority applications listed herein. In this example
Electronic device 16 could be battery or solar powered, or powered in any other way instead of being powered by AC mains 31. Electronic device 16 could be synchronized to lamps 17, 18, and 19 through any one of a number means, or not at all. Electronic device 16 could be a mobile computing device such as a smart phone, PDA, or netbook, notebook, or laptop computer, or a stationary computing device such as a desktop computer or even a television.
Menu 84 and the associated functionality described herein is just one possibility. Any number of different menus with totally different functionality is possible. If HMI 21 does not comprise some sort of display, then menu 84 may be replaced by pushbuttons for instance.
The block diagram for the electronic device 16 illustrated in
To minimize possible flicker produced by gaps 101 during which data is transmitted at high brightness, during time 105 preceding gap 101, as shown in
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.
The present application is a reissue of U.S. Pat. No. 9,386,668, issued on Jul. 5, 2016 from U.S. patent application Ser. No. 14/573,207, filed Dec. 17, 2014, which is hereby incorporated by reference herein in its entirety. U.S. Pat. No. 9,386,668 is a continuation-in-part of U.S. patent application Ser. No. 13/231,077 filed Sep. 13, 2011 which is a continuation-in-part of U.S. patent application Ser. No. 12/924,628 filed Sep. 30, 2010 which claims priority to the following: (1) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (2) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (3) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (4) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; which is further a continuation-in-part of U.S. patent application Ser. Nos. 12/806,114; 12/806,117; 12/806,121; 12/806,118; 12/806,126; 12/806,113, all filed Aug. 5, 2010, all of which claim priority to: (1) U.S. Provisional Patent Application No. 61/273,518 filed Aug. 5, 2009; (2) U.S. Provisional Patent Application No. 61/273,536 filed Aug. 5, 2009; (3) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (4) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (5) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (6) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; all of which are further continuations-in-part of U.S. patent application Ser. No. 12/803,805 filed Jul. 7, 2010 which claims priority to: (1) U.S. Provisional Patent Application No. 61/224,904 filed Jul. 12, 2009; (2) U.S. Provisional Patent Application No. 61/273,518 filed Aug. 5, 2009; (3) U.S. Provisional Patent Application No. 61/273,536 filed Aug. 5, 2009; (4) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (5) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (6) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (7) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; which further is a continuation-in-part of U.S. patent application Ser. No. 12/360,467 filed Jan. 27, 2009; and which further is a continuation-in-part of U.S. patent application Ser. No. 12/584,143 filed Sep. 1, 2009 which claims priority to U.S. Provisional Patent Application No. 61/094,595 filed Sep. 5, 2008.
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 | 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 | 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 | 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 |
7510300 | Iwauchi et al. | Mar 2009 | B2 |
7511695 | Furukawa et al. | Mar 2009 | B2 |
7525611 | Zagar et al. | Apr 2009 | B2 |
7553033 | Seki | Jun 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 |
7705541 | Watanabe et al. | Apr 2010 | B2 |
7737936 | Daly | Jun 2010 | B2 |
7828479 | Aslan et al. | Nov 2010 | B1 |
7878488 | Leason | Feb 2011 | B1 |
7885548 | Nelson | Feb 2011 | B1 |
7924243 | Kanai et al. | Apr 2011 | B2 |
8013538 | Zampini et al. | Sep 2011 | B2 |
8018135 | Van De Ven et al. | Sep 2011 | B2 |
8035603 | Furukawa et al. | Oct 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 | 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 |
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 | 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. et al. | Jul 2003 | A1 |
20030133491 | Shih | Jul 2003 | A1 |
20030179721 | Shurmantine et al. | Sep 2003 | A1 |
20030234342 | Gaines et al. | Dec 2003 | A1 |
20040044709 | Cabrera | 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 et al. | 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 | 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 | 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 | Dec 2008 | 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 et al. | Dec 2009 | A1 |
20100005533 | Shamir | Jan 2010 | A1 |
20100052542 | Siemiet et al. | Mar 2010 | A1 |
20100054748 | Sato | Mar 2010 | A1 |
20100061734 | Knapp | Mar 2010 | A1 |
20100096447 | Kwon et al. | Apr 2010 | A1 |
20100117543 | Van Der Veen et al. | May 2010 | A1 |
20100134021 | Ayres | Jun 2010 | A1 |
20100134024 | Brandes | Jun 2010 | A1 |
20100141159 | Shiu et al. | Jun 2010 | A1 |
20100182294 | Roshan et al. | Jul 2010 | A1 |
20100188443 | Lewis et al. | 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 |
20100272437 | Yoon et al. | Oct 2010 | A1 |
20100301777 | Kraemer | Dec 2010 | A1 |
20100327764 | Knapp | Dec 2010 | 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 |
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 |
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 |
20130201690 | Vissenberg et al. | Aug 2013 | A1 |
20130257314 | Alvord et al. | Oct 2013 | A1 |
20130293147 | Rogers et al. | Nov 2013 | A1 |
20130393147 | Rogers et al. | Nov 2013 | |
20140028377 | Rosik et al. | Jan 2014 | A1 |
20150022110 | Sisto | Jan 2015 | A1 |
20180233030 | Knapp | Aug 2018 | A1 |
Number | Date | Country |
---|---|---|
1291282 | Apr 2001 | CN |
1291282 | Apr 2001 | CN |
1396616 | Feb 2003 | CN |
1396616 | Feb 2003 | CN |
1573881 | Feb 2005 | CN |
1573881 | Feb 2005 | CN |
1650673 | Aug 2005 | CN |
1650673 | Aug 2005 | CN |
1849707 | Oct 2006 | CN |
1849707 | Oct 2006 | CN |
101083866 | Dec 2007 | CN |
101083866 | Dec 2007 | CN |
101150904 | Mar 2008 | CN |
101150904 | Mar 2008 | CN |
101331798 | Dec 2008 | CN |
101331798 | Dec 2008 | CN |
101458067 | Jun 2009 | CN |
101458067 | Jun 2009 | CN |
0196347 | Oct 1986 | EP |
0196347 | Oct 1986 | EP |
0456462 | Nov 1991 | EP |
0456462 | Nov 1991 | EP |
2273851 | Jan 2011 | EP |
2273851 | Jan 2011 | EP |
2307577 | May 1997 | GB |
2307577 | May 1997 | GB |
06-302384 | Oct 1994 | JP |
06-302384 | Oct 1994 | JP |
08-201472 | Aug 1996 | JP |
08-201472 | Aug 1996 | JP |
11-025822 | Jan 1999 | JP |
11-025822 | Jan 1999 | JP |
2000-286067 | Oct 2000 | JP |
2001-514432 | Sep 2001 | JP |
2001-514432 | Sep 2001 | JP |
2002-353900 | Dec 2002 | JP |
2004-325643 | Nov 2004 | JP |
2004-325643 | Nov 2004 | JP |
2005-539247 | Dec 2005 | JP |
2005-539247 | Dec 2005 | JP |
2006-093450 | Apr 2006 | JP |
2006-260927 | Sep 2006 | JP |
2006-260927 | Sep 2006 | JP |
2007-047352 | Feb 2007 | JP |
2007-266974 | Oct 2007 | JP |
2007-266974 | Oct 2007 | JP |
2007-267037 | Oct 2007 | JP |
2007-267037 | Oct 2007 | JP |
2008-500583 | Jan 2008 | JP |
2008-507150 | Mar 2008 | JP |
2008-507150 | Mar 2008 | JP |
2008-300152 | Dec 2008 | JP |
2008-300152 | Dec 2008 | JP |
2009-134877 | Jun 2009 | JP |
2009-134877 | Jun 2009 | JP |
2010-525567 | Jul 2010 | JP |
1020080073172 | Aug 2008 | KR |
1020080077353 | Aug 2008 | KR |
9910867 | Mar 1999 | WO |
0037904 | Jun 2000 | WO |
0037904 | Jun 2000 | WO |
03075617 | Sep 2003 | WO |
03075617 | Sep 2003 | WO |
2005024898 | Mar 2005 | WO |
2005024898 | Mar 2005 | WO |
2007069149 | Jun 2007 | WO |
2007069149 | Jun 2007 | WO |
2008065607 | Jun 2008 | WO |
2008065607 | Jun 2008 | WO |
2008129453 | Oct 2008 | WO |
2008129453 | Oct 2008 | WO |
2008152922 | Dec 2008 | WO |
2010124315 | Nov 2010 | WO |
2010124315 | Nov 2010 | WO |
2012005771 | Jan 2012 | WO |
2012005771 | Jan 2012 | WO |
2012042429 | Apr 2012 | WO |
2012042429 | Apr 2012 | WO |
2013142437 | Sep 2013 | WO |
2013142437 | Sep 2013 | WO |
Entry |
---|
Office Action dated May 12, 2001 for U.S. Appl. No. 12/360,467. |
Final Office Action dated Nov. 28, 2011 for U.S. Appl. No. 12/360,467. |
Notice of Allowance dated Jan. 20, 2012 for U.S. Appl. No. 12/360,467. |
Office Action dated Feb. 1, 2012 for U.S. Appl. No. 12/584,143. |
Final Office Action dated Sep. 12, 2012 for U.S. Appl. No. 12/584,143. |
Office Action dated Aug. 2, 2012 for U.S. Appl. No. 12/806,114. |
Office Action dated Oct. 2, 2012 for U.S. Appl. No. 12/806,117. |
Office Action dated Jul. 11, 2012 for U.S. Appl. No. 12/806,121. |
Final Office Action dated Oct. 11, 2012 for U.S. Appl. No. 12/806,121. |
Office Action dated Dec. 17, 2012 for U.S. Appl. No. 12/806,118. |
Office Action dated Oct. 9, 2012 for U.S. Appl. No. 12/806,126. |
Office Action dated Jul. 10, 2012 for U.S. Appl. No. 12/806,113. |
Notice of Allowance dated Oct. 15, 2012 for U.S. Appl. No. 12/806,113. |
Office Action dated Dec. 4, 2013 for U.S. Appl. No. 12/803,805. |
Notice of Allowance dated Jan. 28, 2014 for U.S. Appl. No. 13/178,686. |
Notice of Allowance dated Feb. 21, 2014 for U.S. Appl. No. 12/806,118. |
Office Action dated Apr. 22, 2014 for U.S. Appl. No. 12/806,114. |
Notice of Allowance dated Feb. 4, 2013 for U.S. Appl. No. 12/809,113. |
Notice of Allowance dated Feb. 25, 2013 for U.S. Appl. No. 12/806,121. |
Notice of Allowance dated May 3, 2013 for U.S. Appl. No. 12/806,126. |
Office Action dated Jun. 10, 2013 for U.S, U.S. Appl. No. 12/924,628. |
Office Action dated Jun. 27, 2013 for U.S. Appl. No. 13/178,686. |
Final Office Action dated Jul. 9, 2013 for U.S. Appl. No. 12/806,118. |
Final Office Action dated Jun. 14, 2013 for U.S. Appl. No. 12/806,117. |
Office Action dated Oct. 24, 2013 for U.S. Appl. No. 12/806,117. |
Notice of Allowance dated Oct. 31, 2013 for U.S. Appl. No. 12/924,628. |
Office Action dated Nov. 12, 2013 for U.S. Appl. No. 13/231,077. |
Final Office Action dated Jun. 18, 2014 for U.S. Appl. No. 13/231,077. |
Office Action dated Jun. 23, 2014 for U.S. Appl. No. 12/806,117. |
Notice of Allowance dated Aug. 21, 2014 for U.S. Appl. No. 12/584,143. |
Office Action dated Sep. 10, 2014 for U.S. Appl. No. 12/803,805. |
Office Action dated Mar. 25, 2015 for U.S. Appl. No. 14/305,472. |
Notice of Allowance dated Mar. 30, 2015 for U.S. Appl. No. 14/097,355. |
Office Action dated Apr. 8, 2015 for U.S. Appl. No. 14/305,456. |
Notice of Allowance dated May 22, 2015 for U.S. Appl. No. 14/510,212. |
Office Action dated May 27, 2015 for U.S. Appl. No. 12/806,117. |
Final Office Action for U.S. Appl. No. 12/803,805 dated Jun. 23, 2015. |
Office Action for U.S. Appl. No. 13/970,964 dated Jun. 29, 2015. |
Office Action for U.S. Appl. No. 14/510,243 dated Jul. 28, 2015. |
Office Action for U.S. Appl. No. 14/510,283 dated Jul. 29, 2015. |
Office Action for U.S. Appl. No. 14/510,266 dated Jul. 31, 2015. |
Office Action for U.S. Appl. No. 13/970,990 dated Aug. 20, 2015. |
Final Office Action for U.S. Appl. No. 13/773,322 dated Sep. 2, 2015. |
Notice of Allowance for U.S. Appl. No. 13/970,944 dated Sep. 11, 2015. |
Notice of Allowance for U.S. Appl. No. 14/604,886 dated Sep. 25, 2015. |
Notice of Allowance for U.S. Appl. No. 14/604,881 dated Oct. 9, 2015. |
Notice of Allowance for U.S. Appl. No. 14/510,243 dated Nov. 6, 2015. |
Notice of Allowance for U.S. Appl. No. 12/806,117 dated Nov. 18, 2015. |
Office Action dated Mar. 6, 2015 for U.S. Appl. No. 13/733,322. |
“International Preliminary Report on Patentability and Written Opinion”, Int'l Application PCT/US2009/004953, dated Mar. 8, 2011, 5 pages. |
“International Preliminary Report on Patentability”, Int'l Application PCT/US2010/001919, dated Jan. 26, 2012, 7 pages. |
“International Preliminary Report on Patentability”, Int'l Application PCT/US2010/002171, dated Feb. 16, 2012, 6 pages. |
“Search Report by Registered Search Organization”, JP Application 2012-523605, dated Feb. 25, 2014, 15 pages. |
“The Second Office Action”, CN Application 2010-80032373.7, dated Apr. 15, 2014, 5 pages. |
“Search Report by Registered Search Organization”, JP Application 2012-520587, dated May 30, 2014, 10 pages. |
“The First Office Action”, CN Application 2010-80035731.X, dated Jun. 5, 2014, 5 pages. |
“Notification to Grant Patent Right for Invention”, CN Application 2010-80032373.7, dated Aug. 6, 2014, 2 pages. |
“Notification to Grant Patent Right for Invention”, CN Application 2010-80035731.X, dated Aug. 6, 2015, 2 pages. |
“Decision to Grant a Patent”, JP Application 2012-520587, dated Oct. 21, 2015, 2 pages. |
“Notification of Reason for Refusal”, KR Application 10-2012-7003792, dated Mar. 7, 2016, 7 pages. |
“Notification of Reason for Refusal”, KR Application 10-2012-7005884, dated Apr. 28, 2016, 3 pages. |
“Notice of Final Rejection”, KR Application 10-2012-7003792, dated Jun. 22, 2016, 1 page. |
“Notice of Final Rejection”, KR Application 10-2012-7005884, dated Jul. 20, 2016, 1 page. |
“European Search Report and Search Opinion”, EPC Application 10800143.9, dated Feb. 24, 2017, 10 pages. |
“Supplementary Partial European Search Report”, EPC Application 10806752.1, dated Mar. 8, 2017, 6 pages. |
“European Search Report and European Search Opinion”, EPC Application 10806752.1, dated Jun. 9, 2017, 12 pages. |
Hall et al., “Jet Engine Control Using Ethernet with a BRAIN (Postprint),” AIAA/ASME/SAE/ASEE Joint Propulsion Conference Exhibition, Jul. 2008, pp. 1-18. |
International Search Report & Written Opinion, PCT/US2010/004953, dated Mar. 22, 2010. |
International Search Report & Written Opinion, PCT/US2010/000219, dated Oct. 12, 2010. |
International Search Report & Written Opinion, PCT/US2010/002171, dated Nov. 24, 2010. |
Bouchet et al., “Visible-light communication system enabling 73 Mb/s data streaming,” IEE Globecom Workshop on Optical Wireless Communications, 2010, pp. 1042-1046. |
International Search Report & Written Opinion, PCT/US2010/001919, dated Feb. 24, 2011. |
International Search Report & Written Opinion, PCT/US2012/045392, dated Sep. 19, 2012. |
Partial International Search Report, PCT/US2012/052774, dated Nov. 16, 2012. |
International Search Report & Written Opinion, PCT/US2012/052774, dated Feb. 4, 2013. |
International Search Report & Written Opinion, PCT/US2013/027157, dated May 16, 2013. |
Office Action, CN Application No. 201080032373.7, dated Nov. 4, 2013. |
Chonko, “Use Forward Voltage Drop to Measure Junction Temperature,” (c) 2013 Penton Media, Inc., 5 pages. |
Office Action, JP Application 2012-523605, dated Mar. 11, 2014. |
Office Action, JP Application 2012-520587, dated Jul. 1, 2014. |
Office Action, JP Application 2012-523605, dated Sep. 24, 2014. |
Final Office Action, U.S. Appl. No. 12/806,117, dated Jan. 28, 2015. |
Office Action, CN Application 201080035731.X, dated Feb. 2, 2015. |
Office Action, JP Application 2012-520587, dated Feb. 17, 2015. |
Partial International Search Report, PCT/US2014/068556, dated Mar. 27, 2015. |
International Search Report & Written Opinion, PCT/US2014/068556, dated Jun. 22, 2015. |
Partial International Search Report, PCT/US2015/037660, dated Aug. 21, 2015. |
International Search Report & Written Opinion, PCT/US2015/037660, dated Oct. 28, 2015. |
Partial International Search Report, PCT/US2015/045252, dated Nov. 18, 2015. |
‘Visible-light communication system enabling 73 Mb/s data streaming’, Olivier Bouchet et al., IEEE Globecom 2010 Workshop on Optical Wireless Communications. |
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/US2014/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/US2014/068556 mailed Jun. 22, 2015. |
Final Office Action for U.S. Appl. No. 12/803,805 mailed Jun. 23, 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. |
Final Office Action mailed Jan. 28, 2015 for U.S. Appl. No. 12/806,117. |
Office Action mailed Mar. 6, 2015 for U.S. Appl. No. 13/773,322. |
Office Action mailed Feb. 2, 2015 for CN Application 201080035731.X. |
Office Action mailed Jul. 1, 2014 for JP Application 2012-520587. |
Office Action mailed Feb. 17, 2015 for JP Application 2012-520587. |
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. |
Johnson, “Visible Light Communications,” CTC Tech Brief, Nov. 2009, 2 pages. |
Office Action mailed May 12, 2011 for U.S. Appl. No. 12/360,467. |
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. |
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/806,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. |
Final Office Action mailed Jun. 14, 2013 for U.S. Appl. No. 12/806,117. |
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. |
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. |
Office Action mailed Nov. 4, 2013 for CN Application No. 201080032373.7. |
“Color Management of a Red, Green, and Blue LED Combinational Light Source,” Avago Technologies, Mar. 2010, pp. 1-8. |
Notice of Allowance for U.S. Appl. No. 14/510,243 mailed Nov. 6, 2015. |
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. |
International Search Report & Written Opinion mailed Oct. 28, 2015 for PCT/US2015/037660. |
Office Action for U.S. Appl. No. 13/970,990 mailed Aug. 20, 2015. |
Partial International Search Report for PCT/US2015/037660 mailed Aug. 21, 2015. |
Final Office Action for U.S. Appl. No. 13/773,322 mailed Sep. 2, 2015. |
Number | Date | Country | |
---|---|---|---|
Parent | 13231077 | Sep 2011 | US |
Child | 14573207 | US | |
Parent | 12924628 | Sep 2010 | US |
Child | 13231077 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14573207 | Dec 2014 | US |
Child | 16028320 | US |