Embodiments of the present disclosure generally relate to a light fixture configuration module, and in particular to a fixture configuration module that controls a light fixture to produce light within a particular range.
In recent years, a movement has gained traction to replace incandescent light bulbs with light fixtures that employ more efficient lighting technologies as well as to replace relatively efficient fluorescent light fixtures with lighting technologies that produce a more pleasing, natural light. One such technology that shows tremendous promise employs light emitting diodes (LEDs). Compared with incandescent bulbs, LED-based light fixtures are much more efficient at converting electrical energy into light, are longer lasting, and are also capable of producing light that is very natural. Compared with fluorescent lighting, LED-based fixtures are also very efficient, but are capable of producing light that is much more natural and more capable of accurately rendering colors. As a result, light fixtures that employ LED technologies are expected to replace incandescent and fluorescent bulbs in residential, commercial, and industrial applications.
Unlike incandescent bulbs that operate by subjecting a filament to a desired current, LED-based light fixtures require electronics to drive one or more LEDs. The electronics generally include a power supply and a special control circuitry to provide uniquely configured signals that are required to drive the one or more LEDs in a desired fashion. The presence of the control circuitry adds a potentially significant level of intelligence to the light fixtures that can be leveraged to employ various types of lighting control.
Various embodiments of the present disclosure are directed to a light fixture, electronics that control a light fixture, a computer readable medium configured with software instructions that (when executed) control a light fixture, and/or methods of controlling a light fixture. Particular embodiments are directed to a fixture configuration module that controls the light fixture to produce light in accordance with particular lighting parameters. Such a fixture configuration module may be removably coupled to the light fixture or may be integrated with the electronics of the light fixture, according to particular embodiments. In some such embodiments, the fixture configuration module controls the light fixture to produce the light in accordance with a stored range for a given lighting parameter. The stored range identifies at least a subset of values of the lighting parameter supported by the light fixture to produce light.
Particular embodiments are directed to a fixture configuration module. The fixture configuration module comprises range control circuitry and fixture control circuitry. The range control circuitry is configured to store a range of a lighting parameter. The range identifies at least a subset of values of the lighting parameter supported by the light fixture to produce light. The fixture control circuitry is communicatively coupled to the range control circuitry and is configured to control the light fixture to produce the light in accordance with the range stored by the range control circuitry.
In some embodiments, the fixture configuration module further comprises user interface circuitry communicatively coupled to the fixture control circuitry independently of the range control circuitry. The user interface circuitry is configured to receive one or more values of the lighting parameter. To control the light fixture to produce the light in accordance with the range, the fixture control circuitry is configured to control the light fixture to produce the light at such values of the lighting parameter received by the user interface circuitry that are within the range stored by the range control circuitry. In some such embodiments, to receive the one or more values of the lighting parameter, the user interface circuitry comprises radio circuitry configured to receive the one or more values of the lighting parameter via radio communication. In some further such embodiments, the radio circuitry is configured to receive a software license enabling remote management of the light fixture, and control the light fixture to produce the light at such values of the lighting parameter received via the radio communication that are within the range stored by the range control circuitry in response.
In some embodiments, the range control circuitry comprises a mechanical switch configured to designate the range of the lighting parameter from a plurality of different ranges by positioning the mechanical switch to one of a plurality of respective switch positions. In some such embodiments, the range control circuitry further comprises near-field communication (NFC) circuitry configured to program the range control circuitry with a range received via NFC signaling, and the plurality of respective switch positions comprises a first position corresponding to the range programmed by the NFC circuitry and a second position corresponding to a different range not programmed by the NFC circuitry. In some further such embodiments, the fixture configuration module further comprises a connector communicatively coupled to the fixture control circuitry. The connector is configured to removably couple with a corresponding connector of the light fixture and transfer electrical power from the light fixture to the fixture control circuitry while the connector is coupled to the corresponding connector of the light fixture. To program the range control circuitry with the range received via the NFC signaling, the NFC circuitry is communicatively coupled to non-volatile memory and further configured to store the range received via the NFC signaling in the non-volatile memory while powered by magnetic induction produced by the NFC signaling and while the connector is decoupled from the corresponding connector of the light fixture. Additionally or alternatively, the range control circuitry further comprises a further mechanical switch, wherein the mechanical switch and further mechanical switch are configured to designate ranges for different respective lighting parameters of the light fixture. In some such embodiments, the ranges for the different respective lighting parameters comprise a color temperature range and a brightness range.
In some embodiments, the fixture configuration module further comprises a mechanical reset button communicatively coupled to the range control circuitry and configured to produce a reset signal. The range control circuitry is configured to override the range of the lighting parameter stored by the range control circuitry with a default range responsive to receiving the reset signal.
Other embodiments are directed to a method of controlling a light fixture. The method is implemented by a fixture configuration module. The method comprises storing a range of a lighting parameter. The range identifies at least a subset of values of the lighting parameter supported by the light fixture to produce light. The method further comprises controlling the light fixture to produce the light in accordance with the stored range.
In some embodiments, controlling the light fixture to produce the light in accordance with the stored range comprises controlling the light fixture to produce the light at such values of the lighting parameter, received by a user interface of the fixture configuration module, that are within the stored range. In some such embodiments, receiving the values of the lighting parameter comprises receiving the values of the lighting parameter via radio communication. In some further such embodiments, the method further comprises receiving a software license enabling remote management of the light fixture, and in response, controlling the light fixture to produce the light at such values of the lighting parameter received via radio communication that are within the stored range.
In some embodiments, the method further comprises designating the range of the lighting parameter from a plurality of different ranges by positioning a mechanical switch of the fixture control module to one of a plurality of respective switch positions. In some such embodiments, the method further comprises programming the fixture configuration module with a range received via near-field communication (NFC) signaling. The plurality of respective switch positions comprises a first position corresponding to the programmed range received via the NFC signaling and a second position corresponding to a different range not received by the NFC circuitry. In some further such embodiments, the method further comprises removably coupling, via a connector of the fixture configuration module, with a corresponding connector of the light fixture, and receiving electrical power from the light fixture in response. Programming the fixture configuration module with the range received via the NFC signaling comprises storing the range received via the NFC signaling in a non-volatile memory of the fixture configuration module while powered by magnetic induction produced by the NFC signaling and while the connector is decoupled from the corresponding connector of the light fixture. Additionally or alternatively, the method further comprises designating a different range of a different lighting parameter of the light fixture using a further mechanical switch of the fixture configuration module. In some such embodiments, the range is a color temperature range of the light fixture, and the different range is a brightness range of the light fixture.
Yet other embodiments are directed to a non-transitory computer readable medium storing software instructions for controlling a programmable fixture configuration module, wherein the software instructions, when executed by processing circuitry of the programmable fixture configuration module, cause the programmable fixture configuration module to perform any of the methods disclosed herein.
Additional embodiments are directed to a light fixture comprising range control circuitry and fixture control circuitry. The range control circuitry is configured to store a range of a lighting parameter. The range identifies at least a subset of values of the lighting parameter supported by the light fixture to produce light. The fixture control circuitry is communicatively coupled to the range control circuitry and is configured to control the light fixture to produce the light in accordance with the range stored by the range control circuitry.
In some embodiments, the light fixture further comprises driver circuitry communicatively coupled to the fixture control circuitry. To control the light fixture to produce the light, the fixture control circuitry is configured to send control signaling to the driver circuitry. The driver circuitry is configured to respond to the control signaling by driving electrical power to solid-state lighting based on the control signaling. In some such embodiments, the light fixture further comprises a printed circuit board on which at least the driver circuitry and the fixture control circuitry are integrated.
The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
It will be understood that when an element such as a layer, region, or substrate is referred to as being “on” or extending “onto” another element, it can be directly on or extend directly onto the other element or intervening elements may also be present. In contrast, when an element is referred to as being “directly on” or extending “directly onto” another element, there are no intervening elements present. Likewise, it will be understood that when an element such as a layer, region, or substrate is referred to as being “over” or extending “over” another element, it can be directly over or extend directly over the other element or intervening elements may also be present. In contrast, when an element is referred to as being “directly over” or extending “directly over” another element, there are no intervening elements present. It will also be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present.
Relative terms such as “below” or “above” or “upper” or “lower” or “horizontal” or “vertical” may be used herein to describe a relationship of one element, layer, or region to another element, layer, or region as illustrated in the Figures. It will be understood that these terms and those discussed above are intended to encompass different orientations of the device in addition to the orientation depicted in the Figures.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including” when used herein specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
For clarity in understanding the disclosure below, to the extent that “one of” a conjunctive list of items (e.g., “one of A and B”) is discussed, the present disclosure refers to one (but not both) of the items in the list (e.g., an A or a B, but not both A and B). Such a phrase does not refer to one of each of the list items (e.g., one A and one B), nor does such a phrase refer to only one of a single item in the list (e.g., only one A, or only one B). Similarly, to the extent that “at least one of” a conjunctive list of items is discussed (and similarly for “one or more of” such a list), the present disclosure refers to any item in the list or any combination of the items in the list (e.g., an A only, a B only, or both an A and a B). Such a phrase does not refer to at least one of each of the items in the list (e.g., at least one of A and at least one of B).
As will be described in detail below, particular aspects of the present disclosure may be implemented entirely as hardware, entirely as software (including firmware, resident software, micro-code, etc.), or as a combination of hardware and software. For example, embodiments of the present disclosure may take the form of a non-transitory computer readable medium storing software instructions in the form of a computer program that, when executed on a programmable device, configures the programmable device to execute the various methods described below.
As will be discussed in greater detail below, various embodiments of the present disclosure are directed to a light fixture, electronics that control the light fixture, a computer readable medium configured with software instructions that (when executed) control the light fixture, and/or methods of controlling the light fixture. Particular embodiments are directed to a fixture configuration module that controls the light fixture to produce light in accordance with particular lighting parameters. Such a fixture configuration module may be removably coupled to the light fixture or may be integrated with the electronics of the light fixture, according to particular embodiments.
While the disclosed light fixture 10 illustrated in
In general, troffer-type light fixtures, such as the light fixture 10, are designed to mount in a ceiling. In most applications, the troffer-type light fixtures are mounted into a drop ceiling (not shown) of a commercial, educational, or governmental facility. As illustrated in
Turning now to
The type of lenses 14, the type of LEDs, the shape of the cover 22, and any coating on the bottom side of the cover 22, among many other variables, will affect the quantity and quality of light emitted by the light fixture 10. As will be discussed in greater detail below, the LED array 20 may include LEDs of different colors or color temperatures, wherein the light emitted from the various LEDs mixes together to form a white light having a desired color temperature and quality based on the design parameters for the particular embodiment.
As used herein, the term LED may comprise packaged LED chip(s) or unpackaged LED chip(s). LED elements or modules of the same or different types and/or configurations. The LEDs can comprise single or multiple phosphor-converted white and/or color LEDs, and/or bare LED chip(s) mounted separately or together on a single substrate or package that comprises, for example, at least one phosphor-coated LED chip either alone or in combination with at least one color LED chip, such as a green LED, a yellow LED, a red LED, etc. The LED module can comprise phosphor-converted white or color LED chips and/or bare LED chips of the same or different colors mounted directly on a printed circuit board (e.g., chip on board) and/or packaged phosphor-converted white or color LEDs mounted on the printed circuit board, such as a metal core printed circuit board or FR4 board. In some embodiments, the LEDs can be mounted directly to the heat sink or another type of board or substrate. Depending on the embodiment, the lighting device can employ LED arrangements or lighting arrangements using remote phosphor technology as would be understood by one of ordinary skill in the art, and examples of remote phosphor technology are described in U.S. Pat. No. 7,614,759, assigned to the assignee of the present invention and hereby incorporated by reference.
In those cases where a soft white illumination with improved color rendering is to be produced, each LED element or module or a plurality of such elements or modules may include one or more blue shifted yellow LEDs and one or more red or red/orange LEDs as described in U.S. Pat. No. 7,213,940, assigned to the assignee of the present invention and hereby incorporated by reference. In some embodiments, each LED element or module or a plurality of such elements or modules may include one or more blue LEDs with a yellow or green phosphor and one or more blue LEDs with a red phosphor. The LEDs may be disposed in different configurations and/or layouts as desired, for example utilizing single or multiple strings of LEDs where each string of LEDs comprise LED chips in series and/or parallel. Different color temperatures and appearances could be produced using other LED combinations of single and/or multiple LED chips packaged into discrete packages and/or directly mounted to a printed circuit board as a chip-on board arrangement. In one embodiment, the light source comprises any LED, for example, an XP-Q LED incorporating TrueWhite® LED technology or as disclosed in U.S. patent application Ser. No. 13/649,067, filed Oct. 10, 2012, now U.S. Pat. No. 9,818,919, entitled “LED Package with Multiple Element Light Source and Encapsulant Having Planar Surfaces” by Lowes et al., the disclosure of which is hereby incorporated by reference herein, as developed and manufactured by Cree, Inc., the assignee of the present application. If desirable, other LED arrangements are possible. In some embodiments, a string, a group of LEDs or individual LEDs can comprise different lighting characteristics and by independently controlling a string, a group of LEDs or individual LEDs, characteristics of the overall light out output of the device can be controlled.
In some embodiments, each LED element or module may comprise one or more LEDs disposed within a coupling cavity with an air gap being disposed between the LED element or module and a light input surface. In any of the embodiments disclosed herein each of the LED element(s) or module(s) can have different or the same light distribution, although each may have a directional emission distribution (e.g., a side emitting distribution), as necessary or desirable. More generally, any Lambertian, symmetric, wide angle, preferential-sided or asymmetric beam pattern LED element(s) or module(s) may be used as the light source. For example, the LEDs in the fixtures may include LED components having multiple color temperatures.
By providing a lighting fixture that includes a string, a group of LEDs or individual LEDs can comprise different lighting characteristics and by independently controlling a string, a group of LEDs or individual LEDs, characteristics of the overall light out output of the device can be controlled. Traditionally, a single fixture may include multiple stock keeping unit (SKU) identifiers. For example, a particular fixture style may come in a 4000 lumen output model or 5000 lumen output model. For each of those lumen outputs, the fixture may come in a 3000 k correlated color temperature (CCT), 3500 k CCT, 4000 k CCT, or 5000 k CCT. Each of those configurations would have a its own SKU. By using an LED configuration as described above, a single LED fixture having a single SKU can be stocked, and the fixture configuration module described below allows for selecting any of the above listed lumen and/or CCT configurations.
As is apparent from
With continued reference to
The driver module 30 is coupled to the LED array 20 through the cabling 28 and directly drives the LEDs of the LED array 20 based on control signaling provided by the fixture configuration module 32. The driver module 30 may be provided on a single, integrated module, may be divided into two or more sub-modules, and/or may be integrated with the fixture configuration module 32, according to various embodiments.
The fixture configuration module 32, in some embodiments, is a communications module that acts as an intelligent communication interface facilitating communications between the driver module 30 and other light fixtures 10, a remote control system (not shown), and/or a portable handheld commissioning tool 36, which may also be configured to communicate with a remote control system in a wired or wireless fashion. The fixture configuration module 32 may additionally or alternatively be a control module that acts as a manual configuration interface facilitating local control of the driver module 30 by a manual user and/or the portable handheld commissioning tool 36 within a limited range.
According to particular embodiments, the fixture configuration module 32 may enforce operating limits on the light fixture 10. That is, the light fixture 10 may support a particular range of values with respect to a given lighting parameter (such as color temperature or brightness), and the fixture configuration module 32 may control the light fixture 10 to produce light in accordance with a range that is a subset of those supported values. For example, the fixture configuration module 32 may limit the light fixture 32 to producing light at color temperatures between 3000K and 4200K, even though the light fixture 10 supports producing light at color temperatures anywhere between 2700K and 5500K. Additionally or alternatively, the fixture configuration module 32 may limit the light fixture 32 to producing light at a lumen level between 2800 lumens and 3100 lumens, even though the light fixture 10 supports producing light at lumen levels anywhere between 1000 lumens and 5000 lumens. One or more of these ranges and/or lighting parameter values may be preprogrammed, field programmable, user-configurable, and/or remotely controllable according to various embodiments, as will be described in greater detail below.
In the embodiment of
Other embodiments include arrangements in which the fixture configuration module 32, driver module 30, and/or other electronics of the light fixture 10 are integrated. For example, the fixture configuration module 32 and driver module 30 may be implemented on the same PCB and/or use shared components. In particular, the fixture configuration module 32 and driver module 30 may share one or more microprocessors (not shown in
In other embodiments, a cable may be used to connect the respective connectors of the driver module 30 and the fixture configuration module 32, other attachment mechanisms may be used to physically couple the fixture configuration module 32 to the driver module 30, or the driver module 30 and the fixture configuration module 32 may be separately affixed to the inside of the electronics housing 26. In such embodiments, the interior of the electronics housing 26 is sized appropriately to accommodate both the driver module 30 and the fixture configuration module 32. In many instances, the electronics housing 26 provides a plenum rated enclosure for both the driver module 30 and the fixture configuration module 32.
With the embodiment of
In embodiments where the electronics housing 26 and the supplemental housing 34 will be mounted within a plenum rated enclosure, the supplemental housing 34 may not need to be plenum rated. Further, the fixture configuration module 32 may be directly mounted to the exterior of the electronics housing 26 without any need for a supplemental housing 34, depending on the nature of the electronics provided in the fixture configuration module 32, how and where the light fixture 10 will be mounted, and the like. The latter embodiment wherein the fixture configuration module 32 is mounted outside of the electronics housing 26 may prove beneficial when the fixture configuration module 32 facilitates wireless communications with the other light fixtures 10, the remote control system, or other network or auxiliary device. In essence, the driver module 30 may be provided in the plenum rated electronics housing 26, which may not be conducive to wireless communications. The fixture configuration module 32 may be mounted outside of the electronics housing 26 by itself or within the supplemental housing 34 that is more conducive to wireless communications. A cable may be provided between the driver module 30 and the fixture configuration module 32 according to a defined communication interface. As an alternative, which is described in detail further below, the driver module 30 may be equipped with a first connector that is accessible through the wall of the electronics housing 26. The fixture configuration module 32 may have a second connector, which mates with the first connector to facilitate communications between the driver module 30 and the fixture configuration module 32.
The embodiments that employ mounting the fixture configuration module 32 outside of the electronics housing 26 may be somewhat less cost effective, but provide significant flexibility in allowing the fixture configuration module 32 or other auxiliary devices to be added to the light fixture 10, serviced, or replaced. The supplemental housing 34 for the fixture configuration module 32 may be made of a plenum rated plastic or metal, and may be configured to readily mount to the electronics housing 26 through snaps, screws, bolts, or the like, as well as receive the fixture configuration module 32. The fixture configuration module 32 may be mounted to the inside of the supplemental housing 34 through snap-fits, screws, twistlocks, and the like. The cabling and connectors used for connecting the fixture configuration module 32 to the driver module 30 may take any available form, such as with standard category 5 (cat 5) cable having RJ45 connectors, edge card connectors, blind mate connector pairs, terminal blocks and individual wires, and the like. Having an externally mounted fixture configuration module 32 relative to the electronics housing 26 that includes the driver module 30 allows for easy field installation of different types of fixture configuration modules 32, communications modules, or modules with other functionality for a given driver module 30.
As illustrated in
As an alternative, the fixture configuration module 32 may be configured as illustrated in
The rear of the module housing 38 illustrated in the example of
The rear housing section 42 is provided with two pairs of elongated channel guides 56. Each pair of the channel guides 56 are biased toward the outside of the rear housing section 42, and form a channel, which will receive the snap-lock connector 44. Once the snap-lock connectors 44 are extended far enough into the channel formed by the pair of channel guides 56, barbs on the housing locking members 52 will engage the inside surfaces of the channel guides 56 and effectively lock the snap-lock connectors 44 in place in the channel formed by the channel guides 56.
Also located on the outside surface of the rear housing section 42 is a flame barrier 58, which is configured to surround an opening 580 that extends into the module housing 38. A connector 60, which provides an electrical interface to the electronics of the fixture configuration module 32, extends into or through the opening 580. In the illustrated embodiment, the flame barrier 58 is a continuous wall that surrounds the opening 580 and extends from the exterior surface of the rear housing section 42. The flame barrier 58 is square, but may form a perimeter of any desired shape. The flame barrier 58 is configured to mate flush against the electronics housing 26 of the light fixture 10 or a mating component provided thereon. The channel guides 56 may extend to and form part of a connector rim 62, which effectively provides an aesthetically pleasing recess in which the button member 50 of the snap-lock connector 44 may reside.
As shown in
In the particular example illustrated in
The particular mechanical switches 90 illustrated in
The lighting parameter to which each switch corresponds may be formed and/or printed on the front housing section 40, as shown in
Other embodiments of the fixture configuration module 32 additionally or alternatively include a mechanical reset button accessed through a hole 92 in the front section housing 40. The hole 92 may be sized such that actuation of the mechanical reset button may require insertion of a thin tool (e.g., paperclip, thumbtack, toothpick) as a safety measure against accidentally resetting the fixture configuration module 32. In particular, the mechanical reset button may be configured to produce a reset signal upon actuation. This reset signal may cause the fixture configuration module 32 to override one or more of the ranges used by the fixture configuration module 32 to limit operation of the light fixture 10, as will be discussed further below. Other embodiments may include a reset button that is mounted to the front housing section 40 such that a user may actuate the reset button without the use of a tool.
Other embodiments may have additional or alternative input mechanisms, any or all of which may be mechanical and/or electronic in nature. Further details concerning the mechanical inputs and electronics of the fixture configuration module 32 according to various embodiments will be discussed in greater detail below.
Turning now to
The front housing section 40 and the rear housing section 42 may be formed from a variety of materials, such as fiberglass, thermoplastics, metal, and the like. In this instance, the front housing section 40 is formed from a thermoplastic. As illustrated in
Also illustrated in
When the snap-lock connectors 44 are in place, the free end of the spring member 48 rests against a proximate side of the flame barrier 58. When the snap-lock connector 44 is in place, the spring member 48 may be slightly compressed or not compressed at all. As such, the spring member 48 effectively biases the snap-lock connector 44 in an outward direction through the channels formed by the respective pairs of channel guides 56. In essence, pressing and releasing the button member 50 of the snap-lock connector 44 moves the fixture locking member 46 inward and then outward. If a user applies pressure inward on the button member 50 and thus presses the snap-lock connector 44 inward, the spring member 48 will further compress. When the pressure is released, the spring member 48 will push the snap-lock connector 44 back into its normal resting position. As will be described below, pressing both of the snap-lock connectors 44 inward via the button members 50 will effectively disengage the communications module 32 from the electronics housing 26 of the light fixture 10.
As the fixture configuration module 32 is snapped into place on the electronics housing 26 of the light fixture 10, as illustrated in
The fixture configuration module 32 may be readily released from the electronics housing 26 by pressing both of the snap-lock connectors 44 inward via the button members 50 and then pulling the fixture configuration module 32 away from the electronics housing 26 of the light fixture 10. Pressing the snap-lock connectors 44 inward effectively moves the barbs inward and into the respective openings of the locking interfaces 72, such that they can readily slide out of the respective openings of the locking interfaces 72. Thus, the fixture configuration module 32 may be readily attached and removed from the electronics housing 26 in a fluid and ergonomic fashion, without the need for additional tools. In the illustrated embodiment, the flame barrier 58 rests securely against the exterior surface of the electronics housing 26 of the lighting fixture 10 and acts to seal off the connector interface for the connectors 60 and 70. Thus, the flame barrier 58 may provide a plenum flame barrier for the connector interface and the electronics housed within the fixture configuration module 32.
According to various embodiments, modules of any type of capability may be configured in the same manner as one or more embodiments of the fixture configuration module 32 described herein. Thus, any number of modules that provide one or more special functions may be housed in a similar housing and connected to the driver module 30. According to such embodiments, the functionality provided by the electronics within the housing 34 may vary in order to provide the desired functionality. For example, such modules may be used to provide one or more functions, such as wireless communications, occupancy sensing, ambient light sensing, temperature sensing, emergency lighting operation, and the like.
The interface circuitry 130 may be a controller hub configured to control the input and output (I/O) data paths of the electronics 100. Such I/O data paths may include data paths for wirelessly exchanging signals with local devices and/or over a communications network. Such I/O data paths may additionally or alternatively include one or more buses (e.g., an I2C bus) for exchanging signaling with a light fixture 10. Such data paths may additionally or alternatively include data paths for exchanging signals with mechanical switches 90 and/or buttons for receiving input from a user.
In particular, the interface circuitry 130 may comprise one or more transceivers, each of which may be configured to send and receive communication signals over a particular radio access technology. For example, the interface circuitry may comprise a far-field radio transceiver for communicating with one or more devices on a wireless local area network (WLAN) and/or an NFC transceiver for communicating with a nearby device (e.g., the commissioning tool 36) via NFC signaling. Other embodiments additionally or alternatively include one or more other forms of transceivers configured to send and receive communication signals over one or more of a wireless medium, wired medium, electrical medium, electromagnetic medium, and/or optical medium. Examples of such transceivers include (but are not limited to) BLUETOOTH, ZIGBEE, optical, and/or acoustic transceivers.
The interface circuitry 130 may also comprise one or more mechanical switches 90, buttons, graphics adapters, display ports, video buses, touchscreens, graphical processing units (GPUs), Liquid Crystal Displays (LCDs), and/or LED displays, for presenting visual information to a user. The interface circuitry 130 may also comprise one or more pointing devices (e.g., a mouse, stylus, touchpad, trackball, pointing stick, joystick), touchscreens, microphones for speech input, optical sensors for optical recognition of gestures, and/or keyboards for text entry.
The interface circuitry 130 may be implemented as a unitary physical component, or as a plurality of physical components that are contiguously or separately arranged, any of which may be communicatively coupled to any other, may communicate with any other via the processing circuitry 110, or may be independently coupled to the processing circuitry 110 without the ability to communicate with one or more other components, according to particular embodiments. For example, the interface circuitry 130 may comprise output circuitry 140 (e.g., an I2C bus configured to exchange signals with the light fixture 10) and input circuitry 150 (e.g., receiver circuitry configured to receive communication signals over WLAN and/or NFC signaling). Similarly, the output circuitry 540 may comprise a WLAN transmitter, whereas the input circuitry 550 may comprise one or more mechanical switches 90. Other examples, permutations, and arrangements of the above and their equivalents are included according to various aspects of the present disclosure.
Other embodiments of the electronics 100 of the fixture configuration module 32 may be configured according to the example illustrated in
The electronics 100 in the example of
In some embodiments, the range control circuitry 210 comprises a mechanical switch 90 configured to designate such a range from a plurality of different ranges by positioning the mechanical switch 90 to one of a plurality of respective switch positions. For example, the lighting parameter to which the range pertains may be color temperature, and a user 295 may position the mechanical switch 90 to a first position to designate a “cool white” range of, e.g., 3100K to 4500K, whereas positioning the mechanical switch 90 to a second position may designate a “warm white” range of, e.g., 2000K to 3000K. Other ranges, including ranges that may overlap, may be designated according to other embodiments and may be based on the particular lighting parameter to be limited using the range control circuitry 210. Other embodiments may further comprise a further mechanical switch 90 configured to designate another range for a different lighting parameter of the light fixture, such as brightness, as mentioned above.
In some embodiments, the range may be programmed in the range control circuitry 210 by the commissioning tool 36. In particular, the range control circuitry 210 may include a transceiver with which to exchange signaling with the commissioning tool 36 in order to receive the range. In the particular example illustrated in
According to particular embodiments, the fixture control circuitry 220 may be configured to transfer a range from the range control circuitry 210 to the light fixture 10, such that the light fixture 10 may enforce the range with respect to a particular lighting parameter regardless of whether or not the fixture configuration module 32 is subsequently decoupled from the light fixture 10. This may, for example, enable a user 295 to briefly couple the same fixture configuration module 32 to each of a plurality of light fixtures 10 in order to limit the range of operation of each. According to other embodiments, the fixture control module may refrain from transferring the range to the light fixture 10, such that the light fixture 10 is no longer limited to a range stored by the range control circuitry 210 once the fixture configuration module 32 is decoupled.
In at least some embodiments in which the range control circuitry 210 comprises a mechanical switch 90, the range received via NFC signaling may be designated by positioning the mechanical switch 90 to a given position. Further, in some such embodiments, positioning the mechanical switch 90 in one or more other positions may designate other respective ranges not programmed by the NFC circuitry 230. Thus, a user 295 may, e.g., use the mechanical switch 90 to set the range to the range programmed via NFC signaling or to a predefined range (e.g., programmed in a read only memory (ROM) or other form of non-volatile memory 240), as desired.
As discussed above, the electronics 100 may, in some embodiments, comprise a connector 60 communicatively coupled to the fixture control circuitry and configured to removably couple with a corresponding connector 70 of the light fixture 10. In some embodiments, the connector 60 of the fixture configuration module 32 transfers electrical power from the light fixture 10 to the fixture control circuitry 220 while they are coupled via the connector 60. The connector 60 may additionally or alternatively transfer control signaling between the fixture control circuitry 220 and the light fixture 10.
In some embodiments, the electronics 100 further comprise user interface circuitry 270 that is communicatively coupled to the fixture control circuitry 220, independently of the range control circuitry 210. For example, the range control circuitry 210 and user interface circuitry may comprise respective communication circuitry (e.g., NFC circuitry 210 and radio circuitry 280), each of which is separately and distinctly connected to the fixture control circuitry 220 (e.g., via separate respective buses).
According to embodiments, the user interface circuitry 270 is configured to receive one or more values of the lighting parameter (e.g., via one or more of the input mechanisms described above). In particular, the user interface circuitry 270 may comprise radio circuitry 280, e.g., to permit remote management of the light fixture 10 by a remote device 290 (such as a workstation, laptop, or server connected by direct wireless connection or via a network to the fixture configuration module 32). In such embodiments, the fixture control circuitry 220 may be configured to control the light fixture to produce the light at such values of the lighting parameter received by the user interface circuitry 270 that are within the range stored by the range control circuitry 210 (e.g., and reject or ignore such values of the lighting parameter received by the user interface circuitry 270 that are not within such range, according to some embodiments).
In some embodiments, the remote management features discussed above may require a separate software license in order to be enabled in the user interface circuitry 270. For example, the radio circuitry 280 may be configured to receive a software license from the remote device 290, and in response, enable a command interface through which the values of the lighting parameter may be received. According to some such embodiments, the absence, expiration, invalidation, and/or cancellation of the software license may disable the remote management features. Nonetheless, the range control circuitry 210 and fixture control circuitry 220 may continue to operate as previously described.
In some embodiments, the electronics 100 may further comprise a mechanical reset button 250 that is communicatively coupled to the range control circuitry 210 and is configured to produce a reset signal. In such embodiments, the range control circuitry 210 may be configured to override the range of the lighting parameter stored by the range control circuitry 210 with a default range (e.g., a factory default range) responsive to receiving the reset signal.
It should be noted that any or all of the electronics 100 described above may, in particular embodiments, be electronically integrated with each other and/or may be electronically integrated with some or all further electronics of the light fixture, e.g., on one or more PCBs. According to particular embodiments circuitry of the driver module 30 and the fixture control circuitry 220 are electronically integrated.
In view of the above, particular embodiments of the present disclosure include various methods of controlling a light fixture 10 implemented by a fixture configuration module 32. An example of such a method 400 is illustrated in
Another example of a method 300 implemented by a fixture configuration module 32 and consistent with various embodiments described herein is illustrated in
The fixture configuration module 32 is not coupled to the light fixture 10, and thus not receiving electrical power from the light fixture 10 via its connector 60. Nonetheless, the fixture configuration module 32 stores the range received via the NFC signaling in a non-volatile memory 240 of the fixture configuration module 32 while powered by magnetic induction produced by the NFC signaling (block 315).
In this example, the fixture configuration module 32 has a mechanical switch 90 (e.g., a rotary dial) corresponding to the lighting parameter, and may be positioned to one of a plurality of switch positions. One of said switch positions corresponds to the range programmed into the fixture configuration module 32 and received via the NFC signaling. Another of said switch positions corresponds to a different range that is preprogrammed in non-volatile memory 240 and is not received by the NFC circuitry. For example, this different range may be programmed during manufacturing using an EEPROM programming device (or other device). According to this example, the preprogrammed range and the range received via NFC signaling are stored in respective locations of the non-volatile memory 240, and the mechanical switch 90 designates which location in that non-volatile memory 240 (and correspondingly, which range) is to be used for limiting operation of the light fixture 10 (block 320). In particular, the fixture configuration module 32 designates one of these ranges from the plurality of different ranges responsive to a user 295 positioning the mechanical switch 90 to one of the switch positions.
In this example, the fixture configuration module 32 has a further mechanical switch 90 corresponding to a different lighting parameter. Accordingly, the fixture configuration module 32 designates a range of the different lighting parameter using this further mechanical switch 90 (block 325). In particular, the mechanical switch and the further mechanical switch 90 may designate a color temperature range of the light fixture 10 and a brightness range of the light fixture 10, respectively.
The fixture configuration module 32 is then removably coupled, via a connector 60 of the fixture configuration module 32, with a corresponding connector 70 of the light fixture 10, and receives electrical power from the light fixture 10 in response (block 330). Under the electrical power of the light fixture 10, the fixture configuration module 32 receives a software license (e.g., wirelessly from a remote device 290) and enables remote management of the light fixture 10 in response (block 335).
Having enabled remote management, the fixture configuration module 32 receives one or more values of the lighting parameter (e.g., through radio communication with the remote device 290) (block 340). The fixture configuration module 32 controls the light fixture 10 to produce light at such values of the lighting parameter that are received and are within the corresponding designated range (block 345).
The fixture configuration module 32 also has a mechanical reset button 250. If the reset button 250 is pressed (block 350, yes), the fixture configuration module 32 overrides the range of the lighting parameter received via NFC signaling and stored in the non-volatile memory 240 with a default range in response (block 355). Otherwise (block 350, no), the range received via NFC is not overridden.
If the fixture configuration module 32 is not decoupled from the light fixture 10 (block 360, no), the fixture configuration module 32 will continue to receive further lighting parameter values (block 340) and controlling the light fixture according to the designated ranges (block 345), until the fixture configuration module 32 is either reset (block 350, yes) and/or decoupled (block 360, yes). Once the fixture configuration module 32 is decoupled (block 360, yes), the method 300 ends.
Embodiments of the present disclosure may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the disclosure. In particular, other methods may include one or more combinations of the various functions and/or steps described herein. Although steps of various processes or methods described herein may be shown and described as being in a particular sequence or temporal order, the steps of any such processes or methods are not limited to being carried out in any particular sequence or order, absent an indication otherwise. Indeed, the steps in such processes or methods generally may be carried out in various different sequences and/or orders while still falling within the scope of the present disclosure. Moreover, embodiments of the fixture configuration module 32 may be arranged in a variety of different ways, including (in some embodiments) according to different combinations of the various hardware elements described above. Accordingly, the present embodiments described herein are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.
This application is a continuation of prior U.S. patent application Ser. No. 16/930,533, filed Jul. 17, 2020, which is a continuation of U.S. patent application Ser. No. 16/410,493 filed May 13, 2019, now U.S. Pat. No. 10,721,808, which is a continuation of prior U.S. patent application Ser. No. 15/783,505 filed Oct. 13, 2017, now U.S. Pat. No. 10,342,102, which is a continuation-in-part of prior U.S. patent application Ser. No. 13/868,021 filed Apr. 22, 2013, now U.S. Pat. No. 9,980,350, which is a continuation-in-part of U.S. patent application Ser. No. 13/782,040 filed Mar. 1, 2013, now U.S. Pat. No. 8,975,827, which claims the benefit of U.S. Provisional Application No. 61/738,749 filed Dec. 18, 2012, which is a continuation-in-part of U.S. patent application Ser. No. 13/589,899, now U.S. Pat. No. 10,219,338, and of Ser. No. 13/589,928, now U.S. Pat. No. 10,506,678, each of which was filed Aug. 20, 2012, and each of which claims the benefit of U.S. Provisional Application No. 61/666,920 filed Jul. 1, 2012, the disclosures of all of which are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
1099061 | Lane | Jun 1914 | A |
D259514 | Welch | Jun 1981 | S |
5079680 | Kohn | Jan 1992 | A |
5471119 | Ranganath et al. | Nov 1995 | A |
6100643 | Nilssen | Aug 2000 | A |
6118230 | Fleischmann | Sep 2000 | A |
6137408 | Okada | Oct 2000 | A |
6160359 | Fleischmann | Dec 2000 | A |
6166496 | Lys et al. | Dec 2000 | A |
6437692 | Petite et al. | Aug 2002 | B1 |
6441558 | Muthu et al. | Aug 2002 | B1 |
6528954 | Lys et al. | Mar 2003 | B1 |
6735630 | Gelvin et al. | May 2004 | B1 |
6826607 | Gelvin et al. | Nov 2004 | B1 |
6832251 | Gelvin et al. | Dec 2004 | B1 |
6859831 | Gelvin et al. | Feb 2005 | B1 |
6914893 | Petite | Jul 2005 | B2 |
6948829 | Verdes et al. | Sep 2005 | B2 |
6990394 | Pasternak | Jan 2006 | B2 |
7009348 | Mogilner et al. | Mar 2006 | B2 |
7020701 | Gelvin et al. | Mar 2006 | B1 |
7031920 | Dowling et al. | Apr 2006 | B2 |
7103511 | Petite | Sep 2006 | B2 |
7139562 | Matsui | Nov 2006 | B2 |
7288902 | Melanson | Oct 2007 | B1 |
7305467 | Kaiser et al. | Dec 2007 | B2 |
D560006 | Garner et al. | Jan 2008 | S |
7344279 | Mueller et al. | Mar 2008 | B2 |
D565771 | Garner et al. | Apr 2008 | S |
D567431 | Garner et al. | Apr 2008 | S |
7396146 | Wang | Jul 2008 | B1 |
D582598 | Kramer et al. | Dec 2008 | S |
7482567 | Hoelen et al. | Jan 2009 | B2 |
7484008 | Gelvin et al. | Jan 2009 | B1 |
D586950 | Garner et al. | Feb 2009 | S |
D587390 | Garner et al. | Feb 2009 | S |
D588064 | Garner et al. | Mar 2009 | S |
7502054 | Kalapathy et al. | Mar 2009 | B2 |
D594576 | Chan et al. | Jun 2009 | S |
7549772 | Wang | Jun 2009 | B2 |
7587289 | Sivertsen | Sep 2009 | B1 |
7638743 | Bartol et al. | Dec 2009 | B2 |
7649456 | Wakefield et al. | Jan 2010 | B2 |
7677767 | Chyn | Mar 2010 | B2 |
7868562 | Salsbury et al. | Jan 2011 | B2 |
7924174 | Gananathan | Apr 2011 | B1 |
7924927 | Boesjes | Apr 2011 | B1 |
8011794 | Sivertsen | Sep 2011 | B1 |
3035320 | Sibert | Oct 2011 | A1 |
D663048 | Chen | Jul 2012 | S |
8274928 | Dykema et al. | Sep 2012 | B2 |
8275471 | Huizenga et al. | Sep 2012 | B2 |
8344660 | Mohan et al. | Jan 2013 | B2 |
8364325 | Huizenga et al. | Jan 2013 | B2 |
8466626 | Null et al. | Jun 2013 | B2 |
8497634 | Scharf | Jul 2013 | B2 |
8511851 | Van De Ven et al. | Aug 2013 | B2 |
8536792 | Roosli | Sep 2013 | B1 |
8536984 | Benetz et al. | Sep 2013 | B2 |
D703841 | Feng et al. | Apr 2014 | S |
D708360 | Shibata et al. | Jul 2014 | S |
8952627 | Tomiyama et al. | Feb 2015 | B2 |
9041315 | Cho et al. | May 2015 | B2 |
9351381 | Verfuerth et al. | May 2016 | B2 |
9408268 | Recker et al. | Aug 2016 | B2 |
9538617 | Rains, Jr. et al. | Jan 2017 | B2 |
9686477 | Walters et al. | Jun 2017 | B2 |
10219338 | Harris | Feb 2019 | B2 |
10274183 | Randolph et al. | Apr 2019 | B2 |
20020195975 | Schanberger et al. | Dec 2002 | A1 |
20040002792 | Hoffknecht | Jan 2004 | A1 |
20040051467 | Balasubramaniam | Mar 2004 | A1 |
20040139741 | Balle et al. | Jul 2004 | A1 |
20040193741 | Pereira | Sep 2004 | A1 |
20050111234 | Martin et al. | May 2005 | A1 |
20050127381 | Vitta | Jun 2005 | A1 |
20050179404 | Veskovic | Aug 2005 | A1 |
20060022214 | Morgan et al. | Feb 2006 | A1 |
20060044152 | Wang | Mar 2006 | A1 |
20060066266 | Li Lim | Mar 2006 | A1 |
20060125426 | Veskovic | Jun 2006 | A1 |
20060262545 | Piepgras et al. | Nov 2006 | A1 |
20070013557 | Wang | Jan 2007 | A1 |
20070040512 | Jungwirth et al. | Feb 2007 | A1 |
20070085700 | Walters et al. | Apr 2007 | A1 |
20070126656 | Huang et al. | Jun 2007 | A1 |
20070132405 | Hillis | Jun 2007 | A1 |
20070189000 | Papamichael | Aug 2007 | A1 |
20070291483 | Lys | Dec 2007 | A1 |
20080088244 | Morishita | Apr 2008 | A1 |
20080088435 | Cash et al. | Apr 2008 | A1 |
20080111498 | Budike | May 2008 | A1 |
20080158887 | Zhu et al. | Jul 2008 | A1 |
20080197790 | Mangiaracina | Aug 2008 | A1 |
20080203945 | Deurenberg et al. | Aug 2008 | A1 |
20080218087 | Crouse et al. | Sep 2008 | A1 |
20080225521 | Waffenschmidt et al. | Sep 2008 | A1 |
20080273754 | Hick et al. | Nov 2008 | A1 |
20090086492 | Meyer | Apr 2009 | A1 |
20090184616 | Van De Ven et al. | Jul 2009 | A1 |
20090212718 | Kawashima et al. | Aug 2009 | A1 |
20090219727 | Weaver | Sep 2009 | A1 |
20090231832 | Zukauskas | Sep 2009 | A1 |
20090237011 | Shah | Sep 2009 | A1 |
20090262189 | Marman | Oct 2009 | A1 |
20090267540 | Chemel et al. | Oct 2009 | A1 |
20090284169 | Valois | Nov 2009 | A1 |
20090302994 | Rhee et al. | Dec 2009 | A1 |
20090302996 | Rhee et al. | Dec 2009 | A1 |
20090305644 | Rhee et al. | Dec 2009 | A1 |
20090315485 | Verfuerth et al. | Dec 2009 | A1 |
20090315668 | Leete, III et al. | Dec 2009 | A1 |
20100007289 | Budike, Jr. | Jan 2010 | A1 |
20100060195 | Tsuboi et al. | Mar 2010 | A1 |
20100110699 | Chou | May 2010 | A1 |
20100134051 | Huizenga et al. | Jun 2010 | A1 |
20100150122 | Berger | Jun 2010 | A1 |
20100177509 | Pickard | Jul 2010 | A1 |
20100182294 | Roshan | Jul 2010 | A1 |
20100203515 | Rigler | Aug 2010 | A1 |
20100262296 | Davis et al. | Oct 2010 | A1 |
20100270935 | Otake et al. | Oct 2010 | A1 |
20100295473 | Chemel et al. | Nov 2010 | A1 |
20100295946 | Reed | Nov 2010 | A1 |
20100301770 | Chemel et al. | Dec 2010 | A1 |
20100301773 | Chemel et al. | Dec 2010 | A1 |
20100301774 | Chemel et al. | Dec 2010 | A1 |
20110025469 | Erdmann et al. | Feb 2011 | A1 |
20110031897 | Henig et al. | Feb 2011 | A1 |
20110057581 | Ashar et al. | Mar 2011 | A1 |
20110080120 | Talstra et al. | Apr 2011 | A1 |
20110095709 | Diehl et al. | Apr 2011 | A1 |
20110101871 | Schenk et al. | May 2011 | A1 |
20110115407 | Wibben et al. | May 2011 | A1 |
20110133655 | Recker | Jun 2011 | A1 |
20110137757 | Paolini | Jun 2011 | A1 |
20110156596 | Salsbury | Jun 2011 | A1 |
20110178650 | Picco | Jul 2011 | A1 |
20110182065 | Negley et al. | Jul 2011 | A1 |
20110199004 | Henig et al. | Aug 2011 | A1 |
20110199020 | Henig et al. | Aug 2011 | A1 |
20110221350 | Staab | Sep 2011 | A1 |
20110249441 | Donegan | Oct 2011 | A1 |
20110254554 | Harbers | Oct 2011 | A1 |
20110298598 | Rhee | Dec 2011 | A1 |
20120002406 | Leadford et al. | Jan 2012 | A1 |
20120007725 | Penisoara et al. | Jan 2012 | A1 |
20120040606 | Verfuerth | Feb 2012 | A1 |
20120050535 | Densham et al. | Mar 2012 | A1 |
20120082062 | Mccormack | Apr 2012 | A1 |
20120086345 | Tran | Apr 2012 | A1 |
20120091915 | Ilyes et al. | Apr 2012 | A1 |
20120126705 | Pezzutti et al. | May 2012 | A1 |
20120130544 | Mohan et al. | May 2012 | A1 |
20120135692 | Feri et al. | May 2012 | A1 |
20120136485 | Weber | May 2012 | A1 |
20120139426 | Ilyes et al. | Jun 2012 | A1 |
20120143357 | Chemel et al. | Jun 2012 | A1 |
20120147604 | Farmer | Jun 2012 | A1 |
20120153840 | Dahlen et al. | Jun 2012 | A1 |
20120176041 | Birru | Jul 2012 | A1 |
20120206050 | Spero | Aug 2012 | A1 |
20120223657 | Van De Ven | Sep 2012 | A1 |
20120224457 | Kim et al. | Sep 2012 | A1 |
20120229048 | Archer | Sep 2012 | A1 |
20120230696 | Pederson et al. | Sep 2012 | A1 |
20120235579 | Chemel et al. | Sep 2012 | A1 |
20120235600 | Simonian et al. | Sep 2012 | A1 |
20120242242 | Linz et al. | Sep 2012 | A1 |
20120242254 | Kim | Sep 2012 | A1 |
20120271477 | Okubo et al. | Oct 2012 | A1 |
20120286700 | Maxik et al. | Nov 2012 | A1 |
20120299485 | Mohan et al. | Nov 2012 | A1 |
20120306375 | van de Ven | Dec 2012 | A1 |
20120306377 | Igaki et al. | Dec 2012 | A1 |
20120320262 | Chung | Dec 2012 | A1 |
20130002157 | Van De Ven | Jan 2013 | A1 |
20130002167 | Van De Ven | Jan 2013 | A1 |
20130013091 | Cavalcanti et al. | Jan 2013 | A1 |
20130026953 | Woytowitz | Jan 2013 | A1 |
20130033872 | Randolph et al. | Feb 2013 | A1 |
20130049606 | Ferstl et al. | Feb 2013 | A1 |
20130051806 | Quilici et al. | Feb 2013 | A1 |
20130057395 | Ohashi | Mar 2013 | A1 |
20130063042 | Bora | Mar 2013 | A1 |
20130069539 | So | Mar 2013 | A1 |
20130077299 | Hussell et al. | Mar 2013 | A1 |
20130088155 | Maxik et al. | Apr 2013 | A1 |
20130088168 | Mohan et al. | Apr 2013 | A1 |
20130147366 | Huizenga | Jun 2013 | A1 |
20130154831 | Gray | Jun 2013 | A1 |
20130155392 | Barrilleaux et al. | Jun 2013 | A1 |
20130155672 | Vo et al. | Jun 2013 | A1 |
20130200805 | Scapa et al. | Aug 2013 | A1 |
20130221857 | Bowers | Aug 2013 | A1 |
20130229784 | Lessard et al. | Sep 2013 | A1 |
20130293112 | Reed et al. | Nov 2013 | A1 |
20130307419 | Simonian | Nov 2013 | A1 |
20130320862 | Campbell et al. | Dec 2013 | A1 |
20130328486 | Jones | Dec 2013 | A1 |
20130342911 | Bartol et al. | Dec 2013 | A1 |
20140001959 | Motley et al. | Jan 2014 | A1 |
20140001962 | Harris | Jan 2014 | A1 |
20140001963 | Chobot et al. | Jan 2014 | A1 |
20140001977 | Zacharchuk et al. | Jan 2014 | A1 |
20140062678 | de Clercq et al. | Mar 2014 | A1 |
20140072211 | Kovesi et al. | Mar 2014 | A1 |
20140167621 | Trott et al. | Jun 2014 | A1 |
20140167646 | Zukauskas et al. | Jun 2014 | A1 |
20140212090 | Wilcox et al. | Jul 2014 | A1 |
20140268790 | Chobot et al. | Sep 2014 | A1 |
20140312777 | Shearer et al. | Oct 2014 | A1 |
20150008827 | Carrigan et al. | Jan 2015 | A1 |
20150008829 | Lurie et al. | Jan 2015 | A1 |
20150022096 | Deixler | Jan 2015 | A1 |
20150042243 | Picard | Feb 2015 | A1 |
20150048758 | Carrigan et al. | Feb 2015 | A1 |
20150189724 | Karc et al. | Jul 2015 | A1 |
20150195883 | Harris et al. | Jul 2015 | A1 |
20150305119 | Hidaka et al. | Oct 2015 | A1 |
20150342011 | Brochu | Nov 2015 | A1 |
20150345762 | Creasman et al. | Dec 2015 | A1 |
20150351169 | Pope et al. | Dec 2015 | A1 |
20150351191 | Pope et al. | Dec 2015 | A1 |
20150382424 | Knapp et al. | Dec 2015 | A1 |
20160029464 | Hughes | Jan 2016 | A1 |
20160100086 | Chien | Apr 2016 | A1 |
20160302279 | Pope et al. | Oct 2016 | A1 |
20160323972 | Bora et al. | Nov 2016 | A1 |
20170265277 | Nolan | Sep 2017 | A1 |
20170280533 | Dimberg et al. | Sep 2017 | A1 |
Number | Date | Country |
---|---|---|
2426769 | May 2002 | CA |
2511368 | May 2002 | CA |
101444145 | May 2009 | CN |
2440017 | Apr 2012 | EP |
11345690 | Dec 1999 | JP |
2001155870 | Jun 2001 | JP |
2003178889 | Jun 2003 | JP |
2010050069 | Mar 2010 | JP |
2010073633 | Apr 2010 | JP |
2010198877 | Sep 2010 | JP |
2012226993 | Nov 2012 | JP |
20060050614 | May 2006 | KR |
20110001782 | Jan 2011 | KR |
20110095510 | Aug 2011 | KR |
2001026068 | Apr 2001 | WO |
2001026333 | Apr 2001 | WO |
2001026335 | Apr 2001 | WO |
2002039242 | May 2002 | WO |
2003047175 | Jun 2003 | WO |
2004109966 | Dec 2004 | WO |
2006095316 | Sep 2006 | WO |
2006130662 | Dec 2006 | WO |
2007102097 | Sep 2007 | WO |
2009011898 | Jan 2009 | WO |
2009076492 | Jun 2009 | WO |
2009145747 | Dec 2009 | WO |
2009151416 | Dec 2009 | WO |
2009158514 | Dec 2009 | WO |
2010010493 | Jan 2010 | WO |
2010047971 | Apr 2010 | WO |
2010122457 | Oct 2010 | WO |
2011070058 | Jun 2011 | WO |
2011087681 | Jul 2011 | WO |
2011090938 | Jul 2011 | WO |
2013050970 | Apr 2013 | WO |
2014120971 | Aug 2014 | WO |
Entry |
---|
Non-Final Office Action for U.S. Appl. No. 16/930,533, dated May 17, 2021, 6 pages. |
Examiner-Initiated Interview Summary for U.S. Appl. No. 16/930,533, dated Aug. 31, 2021, 2 pages. |
Notice of Allowance for U.S. Appl. No. 16/930,533, dated Nov. 24, 2021, 9 pages. |
Author Unknown, “Cluster Analysis”, Wikipedia-the free encyclopedia, Updated May 21, 2013, Retrieved on May 30, 2013, http://en.wikipedia.org/wiki/cluster_analysis, 16 pages. |
Author Unknown, “Controlling LEDs,” Lutron Electronics Co., Inc., Jan. 1, 2011, 16 pages. |
Author Unknown, “IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements—Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications—Amendment 3: Data Terminal Equipment (DTE) Power via the Media Dependent Interface (MDI) Enhancements,” Standard 802.3at-2009, Sep. 11, 2009, The Institute of Electrical and Electronics Engineers, Inc., 141 pages. |
Author Unknown, “IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements—Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications—Amendment: Data Terminal Equipment (DTE) Power Via Media Dependent Interface (MDI),” Standard 802.3af-2003, Jun. 18, 2003, The Institute of Electrical and Electronics Engineers, Inc., 133 pages. |
Author Unknown, “Multi-Agent System”, Wikipedia—the free encyclopedia, Updated Apr. 18, 2013, Retrieved May 30, 2013, http://en.wikipedia.org/wiki/multi-agent_system, 7 pages. |
Author Unknown, “Section 16950: Distributed Digital Lighting Control System,” Lighting Control Devices, Apr. 30, 2013, 20 pages. |
Author Unknown, “System Design Guide—Lighting Control & Design: System Overview,” Lighting Control and Design, Form No. 1382.057, Accessed Aug. 9, 2013, 4 pages. |
Author Unknown, “System Overview & Introduction,” nLight Network Lighting Controls, Accessed: Aug. 9, 2013, 4 pages, http://nlightcontrols.com/lighting-controls/overview. |
Author Unknown, “The System: Components,” Simply5, Accessed: Aug. 9, 2013, 2 pages, http://simply5.net/how.html. |
Author Unknown, “White Paper: Breakthrough video technology solves persistent image problems with fluorescent lights and LEDs, while maintaining wide dynamic range,” 2009, Pixim, Inc., 7 pages. |
Author Unknown, i2C-Bus: What's That?, Updated 2012, Retrieved May 30, 2013, http://www.i2c-bus.org, 1 page. |
Number | Date | Country | |
---|---|---|---|
20220217821 A1 | Jul 2022 | US |
Number | Date | Country | |
---|---|---|---|
61738749 | Dec 2012 | US | |
61666920 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16930533 | Jul 2020 | US |
Child | 17706305 | US | |
Parent | 16410493 | May 2019 | US |
Child | 16930533 | US | |
Parent | 15783505 | Oct 2017 | US |
Child | 16410493 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13868021 | Apr 2013 | US |
Child | 15783505 | US | |
Parent | 13782040 | Mar 2013 | US |
Child | 13868021 | US | |
Parent | 13589928 | Aug 2012 | US |
Child | 13782040 | US | |
Parent | 13589899 | Aug 2012 | US |
Child | 13589928 | US |