Light emitting diode-based (LED-based or simply LED) light bulbs are becoming increasingly popular for many reasons. LED light bulbs have a longer lifespan and lesser environmental impact when compared to typical compact fluorescent bulbs. Further still, LED light bulbs are subject to much less of a spectrum shift over the lifetime of the bulb. Many present approaches for LED light bulbs are directed at creating light bulbs which require non-standard connectors.
In at least some embodiments, an LED bulb 100 according to one or more embodiments of the present invention are used in a retrofit manner to replace an existing light bulb in an existing light fixture. As described below, LED bulb 100, in at least some embodiments, comprises a bracket, housing, LED units, and a base arranged to enable the illumination-generating portion to be oriented within an existing light fixture (as a replacement for an existing light bulb or other illumination-generating device) to cause the generation of a desired illumination intensity and/or light pattern. LED bulb 100 may be oriented by, for example, sliding, centering, or rotating housing 102 within bracket 104 and/or performing a similar operation or positioning of the housing separate from the bracket and/or base connector.
In at least some embodiments, LED bulb 100 may be referred to as a retrofit LED bulb as the LED bulb is used to replace existing bulbs in existing fixtures. In some embodiments, the retrofit LED bulbs take advantage of features of the existing light fixture, e.g., light fixture heat sink design and/or capability. The retrofit LED bulb provides the capability to replace an existing bulb with a positionable light-generating device able to be oriented to provide different light patterns as needed by a particular installation, e.g., of a light fixture.
Housing 102 comprises two LED units 106 disposed on a front face 108 of the housing and arranged to generate light in a direction (generally indicated by reference A) away from the front face of the housing. Bracket 104 comprises a power connector 110 for connecting bulb 100 to a power connection, e.g., a receiving socket such as a light socket or other connection mechanism, and powering, via internal connections, LED units 106. In use, power connector 110 of bulb 100 is screwed into a receiving socket to provide power to the LED units 106 and thereby generate light.
Although housing 102 is depicted as comprising two LED units 106, in alternative embodiments housing 102 comprises variously at least one or more than two LED units. In alternative embodiments, LED units 106 may be different sizes and/or shapes.
Housing 102 also comprises a set of vanes 112 arranged about a rear face 114 of the housing for dissipating heat generated by bulb 100. Each vane 112 extends longitudinally along housing 102. In at least some embodiments, housing 102 does not comprise vanes 112. In at least some embodiments, vanes 112 may reside between housing 102 and bracket 104. In some embodiments, vanes 112 may comprise a separate component from housing 102.
Bracket 104 comprises a U-shaped arm 116 arranged to cooperatively couple power connector 110 to housing 102. Arm 116 forms a U-shape connecting to housing 102 at the opposing distal ends of the arm and connecting to power connector 110 at the base of the U shape arm. In alternate embodiments, arm 116 may comprise separate arms, e.g., two, joined together at the power connector 110 connection point.
Arm 116 comprises a flat land portion 118 to which power connector 110 connects, a pair of lengths 120 extending away from land portion 118 at an angle, and a pair of second lengths 122 extending away from angled lengths 120 and providing a connecting point for housing 102. In at least some embodiments, arm 116 is formed of a single piece of material. In at least some embodiments, arm 116 comprises a single rounded piece of material forming the U shape instead of several angularly connected lengths. Arm 116 comprises one or more openings in the lengths.
Arm 116 connects to housing 102 via connecting points 124. Connecting points 124 each connect to an opposing face of housing 102 from the other. In at least some embodiments, connecting points 124 are movably connected to housing 102. In at least some embodiments, connecting points 124 provide a rotatable connection between housing 102 and bracket 104. In at least some embodiments, housing 102 is able to rotate about an axis B which passes through connecting points 124.
In at least some embodiments, connecting points 124 are configured to slide along second lengths 122 in a direction A to/from land portion 118. In this manner, housing 102 may be positioned closer to or farther away from connector 110.
Power connector 110 is electrically coupled with LED units 106 to provide power to the units for light generation. In at least some embodiments, the coupling between power connector 110 and LED units 106 is provided by a wire connection along one or both sides of arm 116. In at least some embodiments, one or both of connecting points 124 provide a rotatable electrical connection to LED units 106 via housing 102.
Power connector 110 may comprise at least one of a plurality of different connectors, e.g., a GU24, GU10, Eli, E12, E17, E26, MR16, MR1I, etc. In at least some embodiments, different mechanisms may be used to connect power connector 110 to arm 106. In at least one embodiment, power connector 110 is formed as an integral part of arm 106. In at least one embodiment, power connector 110 comprises wire leads for connecting bulb 100 to a power source, e.g. a driver circuit or a mains power source. In at least some embodiments, a driver circuit or a ballast may be attached to bracket 104. In at least some embodiments, the driver circuit or ballast may be replaceable. In at least some embodiments, the driver circuit or ballast may be formed as an integral part of bracket 104.
Bracket 104 is coupled in a removable manner with housing 102. Bracket 104 is operatively coupled with housing 102 by one or more removable attaching devices, e.g., screws, bolts, etc., at connecting points 124. In at least some embodiments, different releasable mounting mechanisms may be used to connect bracket 104 with housing 102.
In at least some embodiments, LED units 106 and fan 202 are electrically coupled to a single connection to driver 204. For example, in at least some embodiments, the electrical connection between driver 204 and LED units 106 and fan 202 comprises a single plug connection. The single plug connection may be plugged and unplugged by a user without requiring the use of tools.
In at least some embodiments, housing 102 may comprise a greater number of LED units 106. In at least some embodiments, housing 102 may comprise a greater number of fans 202
LED units 106 generates light responsive to receipt of current from driver 204.
Fan 202 rotates responsive to receipt of current from driver 204. Rotation of fan 202 causes air to be drawn in through vents in front face 108 and expelled via vents in rear face 114. The flow of air through bulb 100 by rotation of fan 202 removes heat from the vicinity of LED units 106 thereby reducing the temperature of the LED unit. Maintaining LED unit 106 below a predetermined temperature threshold maintains the functionality of LED unit 106. In at least some embodiments, LED unit 106 is negatively affected by operation at a temperature exceeding the predetermined temperature threshold. In at least some embodiments, the number of vents is dependent on the amount of air flow needed through the interior of LED bulb 100 to maintain the temperature below the predetermined threshold. In at least some embodiments, fan 202 may be replaced by one or more cooling devices arranged to keep the temperature below the predetermined temperature threshold. For example, in some embodiments, fan 202 may be replaced by a movable membrane or a diaphragm or other similar powered cooling device.
In at least some embodiments, fan 202 is integrally formed as a part housing 102. In at least some other embodiments, fan 202 is directly connected to housing 102. In still further embodiments, fan 202 is physically connected and positioned exclusively within housing 102.
In at least some embodiments, fan 202 may be operated at one or more rotational speeds. In at least some embodiments, fan 202 may be operated in a manner in order to draw air into bulb 100 via the vents on rear face 114 and expel air through vents on front face 108. By using fan 202 in LED bulb 100, thermal insulating material and/or thermal transfer material need not be used to remove heat from the LED bulb interior.
In at least some embodiments, fan 202 operates to draw air away from housing 102 and toward a heat sink adjacent LED bulb 100. For example, given LED bulb 100 installed in a light fixture (see e.g.,
In at least some embodiments, existing light fixtures for using high output bulbs, e.g., high-intensity discharge (HID), metal halide, and other bulbs, are designed such that the light fixture operates as a heatsink to remove the heat generated by the HID bulb from the portion of the fixture surrounding the bulb and the bulb itself. In a retrofit scenario in which LED bulb 100 replaces an existing light bulb, e.g. a HID bulb, in a light fixture designed for the existing light bulb, fan 202 of LED bulb 100 operates to move air from the LED bulb toward the existing heat sink of the light fixture. Because LED bulb 100 typically generates less heat than the existing bulb, the operation of fan 202 in connection with the LED bulb increases the life of the LED bulb within the light fixture. LED bulb 100 including fan 202 takes advantage of the design of the existing light fixture heatsink functionality.
Driver 204 comprises one or more electronic components to convert alternating current (AC) received from connector 110 connected to a power connection 206, e.g., a mains power supply or receiving socket, to direct current (DC). Driver 204 transmits the converted current to LED units 106 and fan 202 in order to control operation of the LED unit and fan. In at least some embodiments, driver 204 is configured to provide additional functionality to bulb 100. For example, in at least some embodiments, driver 204 enables dimming of the light produced by bulb 100, e.g., in response to receipt of a different current and/or voltage from power connector 110.
In at least some embodiments, driver 204 is integrated as a part of housing 102. In at least some embodiments, driver 204 is configured to receiver a range of input voltage levels for driving components of housing 102, i.e., LED units 106 and fan 202. In at least some embodiments, driver 204 is configured to receive a single input voltage level.
Bracket 104 also comprises connection point 124 for removably and rotatably attaching the bracket and housing 102. In at least some embodiments, connection point 124 is a screw. In at least some further embodiments, connection point 124 is a bolt, a reverse threading portion for receipt into housing 102, a portion of a twist-lock or bayonet mechanism.
In operation, if one or more LED units 106 in a particular housing 102 degrades or fails to perform, the entire LED bulb 100 need not be replaced. In such a situation, only housing 102 needs replacing. Similarly, if driver 204 fails or degrades in performance, only housing 102 needs to be replaced. If, in accordance with alternate embodiments, driver circuit 204 is connected external of bulb 100, driver circuit 204 may be replaced separate from bulb 100. Because of the use of releasably coupled components, i.e., bracket 104 and housing 102, the replacement of one or the other of the components may be performed on location with minimal or no tools required by a user. That is, the user may remove LED bulb 100 from a socket, replace housing 102 with a new housing, and replace the LED bulb into the socket in one operation. Removal of LED bulb 100 to another location or transport of the LED bulb to a geographically remote destination for service is not needed. Alternatively, the user may remove driver circuit 204 from between power connection 206 and connector 110, in applicable embodiments, and replace the driver.
Also, if the user desires to replace a particular driver 204 of a bulb 100, the user need only remove and replace the currently connected driver 204. For example, a user may desire to replace a non-dimmable driver with a driver which supports dimming also, a user may desire to replace a driver having a shorter lifespan with a driver having a longer lifespan. Alternatively, a user may desire to replace a housing having a particular array of LED units 106 with a different selection of LED units 106, e.g., different colors, intensity, luminance, lifespan, etc.; the user need only detach housing 102 from bracket 104 and reattach the new housing 102 to the bracket.
In at least some embodiments, front vents 302 may be circular, oval, rectangular, or polygonal or another shape. Front vents 302 may also be slits or other shaped openings to the interior of housing 102. In at least some embodiments, front vents 302 may be formed as a part of the opening in front face 300 for LED unit 200.
In at least some embodiments, LED units 200 may comprise different size, shape, and light-emitting characteristics.
The flow proceeds to electrical connect step 906 wherein the user electrically connects a new housing 102 to bracket 104. For example, the user plugs the single plug electrical connection from housing 102 to bracket 104.
The flow proceeds to coupling step 908 wherein the user connects housing 102 to the new base 104.
Further, as depicted in
Optional I/O device 1606 may comprise an input device, an output device, and/or a combined input/output device for enabling interaction with controller 1502. For example, I/O device 1606 may comprise a user input device such as a keyboard, keypad, mouse, trackball, microphone, scanner, or other input mechanism, and/or an output device such as a display, speakers, or other output mechanism. Additionally, I/O device 1606 may comprise an input and/or an output connection for interacting with one or more sensors, e.g., a light sensor, a temperature sensor, a motion sensor, etc.
Network OF device 1610 comprises a mechanism for connecting to a network. In at least some embodiments, network I/F device 1610 may comprise a wired and/or wireless connection mechanism. In at least some embodiments, processing device 1602 may communicate with another processing device, e.g., a computer system, via network interlace device 1610. In at least some embodiments, controller embodiment 1600 may communicate with another controller embodiment via network interface device 1610, i.e. a first LED bulb according to LED bulb embodiment 1500 may communicate via a network connection with a second LED bulb according to LED bulb embodiment 1500. In this manner, two or more LED bulbs according to the above embodiment may communicate to transfer data and/or control commands between the LED bulbs.
Network OF device 1610 comprises a serial and/or a parallel communication mechanism. Non-limiting, exemplary embodiments of network IT device 1610 include at least a digital addressable lighting interlace (DALI), an RS-232 interface, a Universal Serial Bus (USB) interface, an Ethernet interface, a WiFi interface, a cellular interface, etc.
In at least some embodiments, LED bulb 1700 comprises more than one sensor. In at least some embodiments, sensor 1702 is a temperature sensor, light sensor, motion sensor, voltage sensor. In some embodiments, controller 1502 modifies operation of one or more of LED units 106 responsive to receipt of information and/or data from sensor 1702.
For example, controller 1502 may be configured to execute a temperature control plan in which output of LED units 106 is reduced to a lower level after the controller receives a temperature value exceeding a first predetermined temperature threshold value from temperature sensor 1702. If the detected temperature exceeds a second predetermined temperature threshold value, controller 1502 terminates operation of LED units 106 until the detected temperature value falls below one or both of the predetermined temperature threshold values.
In accordance with another scenario in which sensor 1702 is a motion sensor, controller 1502 may be configured to control operation of LED units 106 based on whether motion is detected by motion sensor 1702 If no motion is detected after a predetermined period of time, controller 1502 terminates or operates at a reduced output one or both of LED units 106.
In accordance with another scenario in which sensor 1702 is a voltage sensor, controller 1502 may be configured to control operation of LED units 106 based on a detected voltage level exceeding or failing to meet (e.g., as in a brownout condition) a predetermined voltage level.
In at least some embodiments, sensor 1702 is electrically coupled with controller 1502 and/or connector 110. In at least some other embodiments, sensor 1702 is electrically isolated from controller 1502 and communicatively coupled with the controller. In some embodiments, sensor 1702 is located external and/or disconnected from LED bulb 1700. In at least some embodiments, controller 1502 performs daylight harvesting by adjusting the output of LED units 106 responsive to light level detected via sensor 1702.
In at least some embodiments, memory 1604 (as a part of controller 1600 (
It will be readily seen by one of ordinary skill in the art that the disclosed embodiments fulfill one or more of the advantages set forth above. After reading the foregoing specification, one of ordinary skill will be able to affect various changes, substitutions of equivalents and various other embodiments as broadly disclosed herein. It is therefore intended that the protection granted hereon be limited only by the definition contained in the appended claims and equivalents thereof.
The present application claims the benefit to and is a continuation of prior application Ser. No. 14/658,790, filed Mar. 16, 2015, entitled “An Improved LED Light Having LED Cluster Arrangements,” which was a continuation-in-part of application Ser. No. 13/731,224, filed Dec. 31, 2012, entitled “LED Light Bulb” (now U.S. Pat. No. 9,091,424), which claimed the benefit to and is a continuation of application Ser. No. 12/996,221, filed Dec. 3, 2010, entitled “LED Light Bulb” (now U.S. Pat. No. 8,979,304), which claimed the benefit to and was a National Stage of International Application No. PCT/US09/46641, filed Jun. 8, 2009, entitled “LED Light Bulb,” which claimed the benefit of U.S. Provisional Application No. 61/059,609, filed Jun. 6, 2008, entitled “LED Light Bulb.” The present application claims the benefit to and is a continuation of prior application Ser. No. 14/810,978, filed Jul. 28, 2015, entitled “LED Light Bulb,” which was a continuation of application Ser. No. 13/731,224, filed Dec. 31, 2012, entitled “LED Light Bulb” (now U.S. Pat. No. 9,091,424), which claimed the benefit to and is a continuation of application Ser. No. 12/996,221, filed Dec. 3, 2010, entitled “LED Light Bulb” (now U.S. Pat. No. 8,979,304), which claimed the benefit to and was a National Stage of International Application No. PCT/US09/46641, filed Jun. 8, 2009, entitled “LED Light Bulb,” which claimed the benefit of U.S. Provisional Application No. 61/059,609, filed Jun. 6, 2008, entitled “LED Light Bulb.” The present application also claims the benefit to and is a continuation of prior application Ser. No. 14/259,116, filed Apr. 22, 2014, entitled “High Efficient LED Lighting Fixture” (now U.S. Pat. No. 9,258,855), which claimed the benefit of U.S. Provisional Application No. 61/814,793, filed Apr. 22, 2013, entitled “High Efficient LED Lighting Fixture. The entire contents of the above (U.S. patent application Ser. Nos. 14/259,116; 14/658,790; 14/834,687; 14/810,978; 13/731,224; 12/996,221; 13/730,090; 61/059,609; and 61/582,101) are incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4638970 | Phelan | Jan 1987 | A |
4931917 | Scherf et al. | Jun 1990 | A |
5268828 | Miura | Dec 1993 | A |
5367219 | Friederichs | Nov 1994 | A |
5410328 | Yoksza et al. | Apr 1995 | A |
5450301 | Waltz et al. | Sep 1995 | A |
5661638 | Mira | Aug 1997 | A |
5785116 | Wagner | Jul 1998 | A |
5897199 | Norris | Apr 1999 | A |
5975726 | Latimer | Nov 1999 | A |
6196300 | Checchetti | Mar 2001 | B1 |
6657862 | Crocker et al. | Dec 2003 | B2 |
6793374 | Begemann | Sep 2004 | B2 |
6815724 | Dry | Nov 2004 | B2 |
6864513 | Lin | Mar 2005 | B2 |
7063130 | Huang | Jun 2006 | B2 |
7144135 | Martin et al. | Dec 2006 | B2 |
7144140 | Sun et al. | Dec 2006 | B2 |
7175302 | Kazar et al. | Feb 2007 | B2 |
7178941 | Roberge | Feb 2007 | B2 |
7344279 | Mueller | Mar 2008 | B2 |
7524089 | Park | Apr 2009 | B2 |
7549774 | Tsai | Jun 2009 | B2 |
7623348 | Otsuki et al. | Nov 2009 | B2 |
7635957 | Tripathi | Dec 2009 | B2 |
7682054 | Hsu et al. | Mar 2010 | B2 |
7686483 | Aubrey | Mar 2010 | B1 |
7810957 | Zeng | Oct 2010 | B2 |
7939837 | Lynch et al. | May 2011 | B2 |
8979304 | Mart | Mar 2015 | B2 |
20030133305 | Chen | Jul 2003 | A1 |
20050174780 | Park | Aug 2005 | A1 |
20050254246 | Huang | Nov 2005 | A1 |
20060002110 | Dowling et al. | Jan 2006 | A1 |
20060007553 | Bogner et al. | Jan 2006 | A1 |
20060022214 | Morgan et al. | Feb 2006 | A1 |
20060262545 | Piepgras et al. | Nov 2006 | A1 |
20070014105 | Noguchi | Jan 2007 | A1 |
20080048585 | Denville | Feb 2008 | A1 |
20080143493 | Nam et al. | Jun 2008 | A1 |
20080285271 | Roberge et al. | Nov 2008 | A1 |
20090086487 | Ruud et al. | Apr 2009 | A1 |
20090213595 | Alexander et al. | Aug 2009 | A1 |
20090237934 | Zeng et al. | Sep 2009 | A1 |
20100124058 | Miller | May 2010 | A1 |
20100134020 | Peng et al. | Jun 2010 | A1 |
20100170263 | Steele | Jul 2010 | A1 |
20100207534 | Dowling et al. | Aug 2010 | A1 |
20100315824 | Chen | Dec 2010 | A1 |
20100328950 | Lai | Dec 2010 | A1 |
20110037387 | Chou et al. | Feb 2011 | A1 |
20110053492 | Hochstein | Mar 2011 | A1 |
20110095867 | Ahmad | Apr 2011 | A1 |
20110114296 | Horng et al. | May 2011 | A1 |
20110146966 | Scherrer | Jun 2011 | A1 |
20110170263 | Uluc et al. | Jul 2011 | A1 |
20120072138 | Walters et al. | Mar 2012 | A1 |
20120081904 | Horng | Apr 2012 | A1 |
20120104951 | Taubert et al. | May 2012 | A1 |
20120223640 | Koplow | Sep 2012 | A1 |
20130093325 | Scarpelli | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
1998101 | Mar 2008 | EP |
1998101 | Mar 2008 | EP |
Number | Date | Country | |
---|---|---|---|
Parent | 14658790 | Mar 2015 | US |
Child | 15019249 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14259116 | Apr 2014 | US |
Child | 14658790 | US | |
Parent | 14834687 | Aug 2015 | US |
Child | 14259116 | US | |
Parent | 14810978 | Jul 2015 | US |
Child | 14834687 | US | |
Parent | 13731224 | Dec 2012 | US |
Child | 14810978 | US | |
Parent | 12996221 | Dec 2010 | US |
Child | 13731224 | US | |
Parent | 13730090 | Dec 2012 | US |
Child | 12996221 | US |