CN115243428A

CN115243428A - Fail-safe lighting control system

Info

Publication number: CN115243428A
Application number: CN202210991077.4A
Authority: CN
Inventors: A·A·杰亚瓦狄纳; S·S·坦克塞尔; A·R·欣德; A·简; P·普凯特
Original assignee: Eaton Intelligent Power Ltd
Current assignee: Eaton Intelligent Power Ltd
Priority date: 2015-11-30
Filing date: 2016-11-28
Publication date: 2022-10-25
Also published as: US20170156189A1; CA3013034C; US10383191B2; MX2018006564A; CA3013034A1; WO2017095729A1; DE112016005113T5; CN108370634A

Abstract

A fail-safe lighting control system. A luminaire may include: at least one light source; and at least one power source that receives primary power, wherein the at least one power source generates final power using the primary power, wherein the at least one power source delivers the final power to the at least one light source. The luminaire may further comprise a controller coupled to the at least one power source, wherein the controller detects an adverse event, and wherein the controller controls the at least one power source to provide the final power to the at least one light source during the adverse event.

Description

Fail-safe lighting control system

The present application is a divisional application filed on 2016, 28/11/9, having application number 201680069393.9, entitled "fail-safe lighting control system".

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application serial No. 62/261,123 entitled "Fail-Safe Lighting Control System", filed 11/30/2015, according to 35 u.s.c. § 119, the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates generally to control systems for light fixtures, and more particularly, to systems, methods, and apparatus for fail-safe control systems for light fixtures.

Background

In safety critical lighting applications, such as hazardous environments, the reliability of the lighting system is of vital importance. Unfortunately, the characteristics of these environments (e.g., humidity, extreme temperatures, corrosive gases) may cause a conventional control system used to control the light fixtures to malfunction or otherwise function improperly in such environments, which may make one or more of the light fixtures within the lighting system unreliable (e.g., unavailable, uncontrollable).

Disclosure of Invention

In general, in one aspect, the present disclosure is directed to a light fixture. The luminaire may comprise at least one light source. The light fixture may also include at least one power source that receives primary power, wherein the at least one power source uses the primary power to generate final power, wherein the at least one power source delivers the final power to the at least one light source. The luminaire may further comprise a controller coupled to the at least one power source, wherein the controller detects an adverse event, and wherein the controller controls the at least one power source to provide the final power to the at least one light source during the adverse event.

In another aspect, the present disclosure may generally relate to a lighting system. The lighting system may include a first light fixture having at least one first light source and at least one first power source that receives a first primary power, wherein the at least one first power source generates a first final power using the first primary power, wherein the at least one first power source delivers the first final power to the at least one first light source. The lighting system may also include a controller coupled to the at least one first power source, wherein the controller detects a first adverse event, and wherein the controller controls the at least one first power source to provide the first final power to the at least one first light source during the first adverse event.

In yet another aspect, the present disclosure may generally relate to a controller for a light fixture. The controller may include a control engine coupled to a power source of the luminaire, wherein the controller detects an adverse event, and wherein the controller controls the power source to provide final power to at least one first light source of the luminaire during the first adverse event.

These and other aspects, objects, features and embodiments will be apparent from the following description and appended claims.

Drawings

The drawings illustrate only example embodiments and are therefore not to be considered limiting in scope, for example embodiments may admit to other equally effective embodiments. The components and features illustrated in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the example embodiments. In addition, certain dimensions or orientations may be exaggerated to help visually convey such principles. In the drawings, reference numerals designate like or corresponding, but not necessarily identical, elements.

Fig. 1 illustrates a system diagram of a lighting system including a luminaire, according to some example embodiments.

FIG. 2 illustrates a computing device, according to some example embodiments.

FIG. 3 illustrates a luminaire according to some example embodiments.

Fig. 4 illustrates a system diagram of a luminaire, according to some example embodiments.

FIG. 5 illustrates a system diagram of another luminaire according to some example embodiments.

Fig. 6A-6E illustrate example electrical schematic diagrams of a light fixture, according to some example embodiments.

Fig. 7-10 show flowcharts of how a controller controls a luminaire according to some example embodiments.

Detailed Description

In general, example embodiments provide systems, methods, and apparatus for a fail-safe lighting control system for a luminaire. An example fail-safe lighting control system for a luminaire provides a number of benefits. Such benefits may include, but are not limited to, enhanced fixture reliability, enhanced security against hackers, reduced power consumption, improved communication efficiency, ease of maintenance, and compliance with industry standards applied to fixtures located in certain environments.

In some cases, the example embodiments discussed herein may be used in any type of hazardous environment, including, but not limited to, hangars, drilling rigs (e.g., for oil, gas, or water), workover rigs (e.g., for oil or gas), smelters, chemical plants, power plants, mining operations, wastewater treatment facilities, and steel mills. The user may be any person that interacts with a luminaire having an example fail-safe lighting control system. Examples of users may include, but are not limited to, engineers, electricians, meter and control device technicians, mechanics, operators, hackers, consultants, contractors, and manufacturer representatives.

The example light fixtures described herein having a fail-safe lighting control system (or components thereof, including the controller) may be made of one or more of many suitable materials to allow the light fixture and/or other associated components of the system to meet certain standards and/or regulations, while also maintaining durability in accordance with one or more conditions under which the light fixture and/or other associated components of the system may be exposed. Examples of such materials may include, but are not limited to, aluminum, stainless steel, fiberglass, glass, plastic, ceramic, and rubber.

The example light fixtures with fail-safe lighting control systems described herein, or portions thereof, may be made from a single piece (e.g., according to a molding, injection molding, die casting, or extrusion process). Additionally or in the alternative, an example light fixture having a fail-safe lighting control system may be made from multiple pieces that are mechanically coupled to one another. In this case, the pieces may be mechanically coupled to one another using one or more of a number of coupling methods, including but not limited to epoxy, welding, fastening devices, compression fittings, mating threads, and slotted fittings. One or more pieces mechanically coupled to one another may be coupled to one another in one or more of a number of ways, including but not limited to fixedly, hingedly, removably, slidably, and threadably.

In the above figures, which illustrate example embodiments of a fail-safe lighting control system for a luminaire, one or more of the illustrated components may be omitted, repeated, and/or substituted. Thus, example embodiments of a fail-safe lighting control system for a luminaire should not be considered limited to the specific arrangement of components illustrated in any of the figures. For example, a figure shown in one or more figures or described with respect to one embodiment may be applied to another embodiment associated with a different figure or description.

As defined herein, an electrical enclosure is any type of cabinet or housing within which electrical and/or electronic equipment is disposed. Such electrical and/or electronic devices may include, but are not limited to, controllers (also referred to as control modules), hardware processors, power sources (e.g., batteries, drivers, ballasts), sensor modules, safety barriers, sensors, sensor circuitry, light sources, cables, and electrical conductors. Examples of electrical enclosures may include, but are not limited to, housings for light fixtures, housings for sensor devices, electrical connectors, junction boxes, motor control centers, circuit breaker boxes, electrical housings, conduits, control panels, dashboards, and control cabinets.

In certain example embodiments, a luminaire having a fail-safe lighting control system is to meet certain standards and/or requirements. For example, the national electrical code of code (NEC), the National Electrical Manufacturers Association (NEMA), the International Electrotechnical Commission (IEC), the Federal Communications Commission (FCC), the Institute of Electrical and Electronics Engineers (IEEE) set standards for electrical enclosures, wiring, and electrical connections. Such criteria are met (and/or allowed to be met) as needed using the example embodiments described herein. In some (e.g., PV solar) applications, additional criteria specific to the application may be met by the electrical enclosures described herein.

If a component of a figure is described in the figures but is not explicitly shown or labeled, it can be inferred that the label for the corresponding component of another figure is for the component. Conversely, if a component in a figure is labeled but not described, the description of such component may be substantially the same as the description of the corresponding component in another figure. Herein, the numbering scheme of the various components in the drawings is such that each component is a three or four digit number and the corresponding components in the other drawings have the same last two digits.

Additionally, the statement that a particular embodiment (e.g., as illustrated by the figures herein) does not have a particular feature or component does not imply that such embodiment cannot have such feature or component unless specifically stated. For example, features or components described as not being included in example embodiments shown in one or more particular figures can be included in one or more claims corresponding to such one or more particular figures herein for purposes of current or future claims herein.

Example embodiments of a fail-safe lighting control system for a luminaire will be described more fully hereinafter with reference to the accompanying drawings, in which example embodiments of a fail-safe lighting control system for a luminaire are shown. However, the fail-safe lighting control system of a luminaire may be implemented in many different forms and should not be construed as being limited to the example embodiments set forth herein. Rather, these example embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the fail-safe lighting control system of the light fixture to those skilled in the art. For purposes of consistency, similar, but not necessarily identical, elements (also sometimes referred to as components) are identified with similar reference numerals in the various figures.

Terms such as "first", "second", and "in 8230 \8230;" inner "are used only to distinguish one component (or a portion of a component or a state of a component) from another component (or a portion of a component or a state of a component). Such terms are not meant to refer to a preference or a particular orientation and are not meant to limit the fail-safe lighting control system of the light fixture. In the following detailed description of example embodiments, numerous specific details are set forth in order to provide a more thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

Fig. 1 illustrates a system diagram of a lighting system 100 including a controller 104 of a luminaire 102, according to some example embodiments. Lighting system 100 may include one or more sensors 160 (also sometimes referred to as sensor modules 160), a user 150, a network manager 180, and luminaires 102. In addition to the controller 104, the light fixture 102 may include a power source 140, a number of light sources 142, and a relay 136. The controller 104 may include one or more of a number of components. Such components may include, but are not limited to, a control engine 106, a communication module 108, a real-time clock 110, a power module 112, a memory store 130, a hardware processor 120, a memory 122, a transceiver 124, an application interface 126, and (optionally) a security module 128. The components shown in fig. 1 are not exhaustive, and in some embodiments, one or more of the components shown in fig. 1 may not be included in an example light fixture. Any of the components of the example luminaire 102 may be discrete or combined with one or more other components of the luminaire 102.

The user 150 is the same as the user defined above. The user 150 may use a user system (not shown) that may include a display (e.g., a GUI). User 150 interacts with (e.g., sends data to, receives data from) controller 104 of luminaire 102 via application interface 126 (described below). User 150 may also interact with network manager 180 and/or one or more of sensors 160. The interaction between the user 150 and the luminaires 102, the network manager 180, and the sensors 160 is implemented using the communication link 105. Each communication link 105 may include wired (e.g., class 1 cable, class 2 cable, electrical connector) and/or wireless (e.g., wi-Fi, visible light communication, cellular networking, bluetooth, wireless HART, ISA100, power line carrier, RS485, DALI) technology. For example, the communication link 105 may be (or include) one or more electrical conductors coupled to the housing 103 of the light fixture 102 and to the sensor 160. The communication link 105 may transmit signals (e.g., power signals, communication signals, control signals, data) between the luminaire 102 and one or more of the user 150, the network manager 180, and/or the sensors 160.

Network manager 180 is a device or component that controls all or a portion of a communication network that includes controller 104 of light fixture 102 and sensors 160 communicatively coupled to controller 104. The network manager 180 may be substantially similar to the controller 104. Alternatively, the network manager 180 may include one or more of a number of features in addition to or in lieu of those of the controller 104 described below. As described herein, communication with network manager 180 may include communication with one or more other components of system 100 (e.g., another light fixture). In such a case, network manager 180 may facilitate such communication.

The one or more sensors 160 may be any type of sensing device that measures one or more parameters. Examples of types of sensors 160 may include, but are not limited to, passive infrared sensors, photocells, pressure sensors, airflow monitors, gas detectors, and resistance temperature detectors. Parameters that may be measured by the sensor 160 may include, but are not limited to, motion, amount of ambient light, occupancy of space, and ambient temperature. In some cases, one or more parameters measured by sensor 160 may be used to operate one or more light sources 142 of light fixture 102. Each sensor 160 may use one or more of a number of communication protocols. Sensor 160 may be associated with light fixture 102 or another light fixture in system 100.

In certain example embodiments, the sensor 160 may include a battery for at least partially providing power to some or all of the rest of the sensor 160. When the system 100 (or at least the sensor 160) is located in a hazardous environment, the sensor 160 may be intrinsically safe. As used herein, the term "intrinsically safe" refers to a device (e.g., a sensor as described herein) that is placed in a hazardous environment. To be intrinsically safe, the device uses a limited amount of electrical energy so that sparks do not occur as a result of a short circuit or fault that would ignite an explosive atmosphere found in a hazardous environment. Safety barriers are often used with intrinsically safe devices, where the safety barrier limits the amount of power delivered to a sensor or other device to reduce the risk of an explosion, fire, or other adverse condition or event that may be caused by a high amount of power in a hazardous environment. An adverse condition or event may also be an abnormal condition that may not be catastrophic in nature.

According to one or more example embodiments, the user 150, the network manager 180, and/or the sensor 160 may interact with the controller 104 of the luminaire 102 using the application interface 126. In particular, the application interface 126 of the controller 104 receives data (e.g., information, communications, instructions, updates to firmware) from the user 150, the network manager 180, and/or each sensor 160 and sends data (e.g., information, communications, instructions) to the user, the network manager, and/or the sensor. In certain example embodiments, the user 150, the network manager 180, and/or each sensor 160 may include an interface for receiving data from the controller 104 and transmitting data to the sensor. Examples of such interfaces may include, but are not limited to, a graphical user interface, a touch screen, an application programming interface, a keyboard, a monitor, a mouse, a web service, a data protocol adapter, some other hardware and/or software, or any suitable combination thereof.

In certain example embodiments, the controller 104, the user 150, the network manager 180, and/or the sensors 160 may use their own system or a shared system. Such a system may be (or include the following form of) an internet-based or intranet-based computer system capable of communicating with various software. The computer system includes any type of computing and/or communication device, including but not limited to controller 104. Examples of such systems may include, but are not limited to, desktop computers with LAN, WAN, internet or intranet access, laptop computers with LAN, WAN, internet or intranet access, smart phones, servers, server farms, android devices (or equivalents), tablet computers, smartphones, and Personal Digital Assistants (PDAs). Such a system may correspond to the computer system described below with respect to fig. 2.

Further, as discussed above, such systems may have corresponding software (e.g., user software, sensor software, controller software, network manager software). According to some example embodiments, the software may execute on the same or different devices (e.g., a server, a mainframe, a desktop Personal Computer (PC), a laptop, a Personal Desktop Assistant (PDA), a television, a cable box, a satellite box, a kiosk, a telephone, a mobile phone, or other computing device) and may be coupled with the wired and/or wireless segments through communication networks (e.g., the internet, intranets, extranets, local Area Networks (LANs), wide Area Networks (WANs), or other network communication methods) and/or communication channels. The software of one system may be part of the software of another system within system 100 or may operate separately but in conjunction with the software.

The light fixture 102 may include a housing 103. The housing 103 may include at least one wall forming the cavity 101. In some cases, the housing may be designed to conform to any applicable standard such that the light fixture 102 may be located in a particular environment (e.g., a hazardous environment). For example, if light fixture 102 is located in an explosive environment, housing 103 may be explosion proof. An explosion proof enclosure is an enclosure configured to contain an explosion, which originates from within the enclosure or can propagate through the enclosure, in accordance with applicable industry standards.

Continuing this example, the explosion proof enclosure is configured to allow gas from the interior of the enclosure to escape across the junction of the enclosure and cool as the gas exits the explosion proof enclosure. The junction is also referred to as a flame path and exists where the two surfaces meet and provides a path from inside the flameproof housing to outside the flameproof housing along which one or more gases may travel. The point of engagement may be the mating of any two or more surfaces. Each surface may be any type of surface including, but not limited to, flat surfaces, threaded surfaces, and serrated surfaces.

The housing 103 of the light fixture 102 may be used to house one or more components of the light fixture 102, including one or more components of the controller 104. For example, as shown in fig. 1, a controller 104 (in this case, the controller includes a control engine 106, a communication module 108, a real-time clock 110, a power module 112, a storage library 130, a hardware processor 120, a memory 122, a transceiver 124, an application interface 126, and an optional security module 128), a power source 140, and a light source 142 are disposed in a cavity 101 formed by a housing 103. In alternative embodiments, any one or more of these or other components of the light fixture 102 may be disposed on the housing 102 and/or remotely from the housing 103.

The repository 130 may be a persistent storage device (or set of devices) that stores software and data for assisting the controller 104 in communicating with the user 150, the network manager 180, and the one or more sensors 160 within the system 100. In one or more example embodiments, the repository 130 stores one or more communication protocols 132, operating protocols 133, and sensor data 134. Communication protocol 132 may be any of a number of protocols for transmitting and/or receiving data between controller 104 and user 150, network manager 180, and one or more sensors 160. One or more of the communication protocols 132 may be a time synchronization protocol. Examples of such time synchronization protocols may include, but are not limited to, the Highway Addressable Remote Transducer (HART) protocol, the wireless HART protocol, and the International Society of Automation (ISA) 100 protocol. In this manner, one or more of the communication protocols 132 may provide a layer of security for data communicated within the system 100.

The operating protocol 133 can be any algorithm, formula, logic steps, and/or other similar operating procedure followed by the control engine 106 of the controller 104 at a point in time based on certain conditions. The instances of the operating protocol 133 gradually reduce the power output by the power source 140 to a minimum level when the temperature within the cavity 101 of the luminaire 102 exceeds some threshold temperature. Another example of an operating protocol 133 is calibrating the sensor 160 to account for dust buildup on the sensor 160 over time. This can be achieved, for example, by: capture values measured by sensor 160 with little or no dust accumulation (e.g., at new installation), capture values measured by sensor 160 over time, and track changes in measurements that occur over time in the absence of ambient light. In this case, the controller 104 may send an alert to the user 150 when the dust accumulation on the sensor 160 reaches a certain level, wherein the alert instructs the user 150 to clean the sensor 160. Yet another example of an operating protocol 133 is: one or more communication links 105 with the network manager 180 are checked and if the communication links 105 are not functioning properly, the controller 104 is allowed to operate autonomously with respect to the rest of the system 100.

As another example of an operating protocol 133, a configuration of the controller 104 may be stored in the memory 122 (e.g., non-volatile memory) such that the controller 104 (or portions thereof) may be operational regardless of whether the controller 104 is communicating with the network controller 180 and/or other components in the system 100. Yet another example of an operating protocol 133 is to obtain readings from a nearby sensor (e.g., from a nearby luminaire) if a sensor 160 associated with the luminaire 102 fails, if the communication link 105 between the sensor 160 and the controller 104 fails, and/or for any other reason that the readings of the sensor 160 associated with the luminaire 102 cannot reach the controller 104. To accomplish this, for example, the network manager 180 may instruct the proximity sensor 160 to communicate its readings to the controller 104 using the communication link 105.

Yet another example of an operating protocol 133 is to identify an adverse operating condition or event (e.g., over-voltage, under-voltage, voltage spikes, power surges) based on readings taken by a portion of the controller 104 (e.g., control engine 106, power module 112). In this case, the energy metering module 111 is used to take the readings. The measurements from the energy metering module 111 along with the dimming level setting may be used to detect a failure of the luminaire 102. If the energy metering module 111 fails, another operational protocol 133 is to not use readings from the failed energy metering module 111 to run failure mode analysis and/or to report the failed energy metering module 111 to the network manager 180. Yet another example of an operating protocol 133 is to cause the controller 104 to operate in an autonomous control mode if one or more components of the controller 104 (e.g., the communication module 108, the transceiver 124) that allow the controller 104 to communicate with another component of the system 100 fails.

Some operating protocols 133 may involve anti-hacking measures. For example, the operating protocol 133 may require that if the sensor 160 detects occupancy of an area within the coverage of the sensor 160, the dimming signal (e.g., command) sent from the network manager 180 to the control engine 106 is ignored. As another example, the operating protocol 133 may only allow programming access to the controller 104 with a direct physical connection to the controller 104 and prevent the user 150 (e.g., a hacker) from remotely accessing and/or programming the controller 104 or any portion thereof.

Another example of an operating protocol 133 may be a poor quality firmware from which the controller 104 (or components thereof) is initiated. At firmware update, a copy of the old firmware may be stored in a repository and retrieved if the upgraded firmware is corrupted or becomes corrupted. Any upgrade to the firmware of controller 104 may include security keys and/or other measures to ensure that the firmware is being received from an approved trusted user 150.

The sensor data 134 may be any data associated with (e.g., collected by) each sensor 160 communicatively coupled to the controller 104. Such data may include, but is not limited to, the manufacturer of the sensor 160, the model number of the sensor 160, the communication capabilities of the sensor 160, the power requirements of the sensor 160, and the measurements made by the sensor 160. Examples of the repository 130 may include, but are not limited to, a database (or many databases), a file system, a hard drive, flash memory, some other form of solid state data storage, or any suitable combination thereof. The storage repository 130 may be located on multiple physical machines, each storing all or a portion of the communication protocols 132, the operating protocols 133, and/or the sensor data 134, according to some example embodiments. Each storage unit or device may be physically located in the same or different geographic locations.

The repository 130 may be operatively connected to the control engine 106. In one or more example embodiments, control engine 106 includes functionality to communicate with users 150, network manager 180, and sensors 160 in system 100. More specifically, control engine 106 sends and/or receives information to and/or from repository 130 for communication with user 150, network manager 180, and sensors 160. As discussed below, in certain example embodiments, the repository 130 is also operatively connected to the communication module 108.

In certain example embodiments, the control engine 106 of the controller 104 controls the operation of one or more components of the controller 104 (e.g., the communication module 108, the real-time clock 110, the transceiver 124, the relay 136). For example, the control engine 106 may activate the communication module 108 when the communication module 108 is in a "sleep" mode and the communication module 108 needs to transmit data received from another component (e.g., sensor 160, user 150) in the system 100. As another example, the control engine 106 may operate one or more portions of the one or more relays 136 to control the amount of final power delivered by the power source 140 to the light source 142.

As another example, control engine 106 may use real-time clock 110 to obtain the current time. Real time clock 110 may enable controller 104 to control light fixtures 102 even when controller 104 is not in communication with network manager 180. As yet another example, control engine 106 may direct energy metering module 111 to measure and send power consumption information for light fixtures 102 to network manager 180. In some cases, the control engine 106 of the controller 104 may generate and send a dimming signal (e.g., 0V-10V DC) to the power supply 140, which causes the power supply 140 to adjust the light output of the light source 142. In other words, the dimming signal from the control engine 106 to the power source 140 instructs the power source 140 to deliver an amount of final power to the light source 142, and this amount of final power corresponds to the amount of light output by the light source 142.

Control engine 106 may be configured to perform a number of functions that help ensure fail-safe operation of controller 104 during any of a number of adverse conditions or events. For example, the control engine 106 may gradually reduce the power output by the power source 140 to a minimum level when the temperature (measured by the sensor 160) within the cavity 101 of the light fixture 102, as formed by the housing 103, exceeds a certain threshold temperature. As another example, control engine 106 may calibrate sensor 160 to account for dust accumulation on sensor 160 over time. This can be achieved, for example, by: capture values measured by the sensor 160 with little or no dust accumulation (e.g., at the time of new installation), capture values measured by the sensor 160 over time, and track changes in the measurements over time that occur when ambient light is not present. In this case, the controller 104 may send an alert to the user 150 when the dust accumulation on the sensor 160 reaches a certain level, wherein the alert instructs the user 150 to clean the sensor 160.

As another example, control engine 106 may examine one or more communication links 105 between controller 104 and network manager 180 and allow controller 104 to operate autonomously from the rest of system 100 if communication links 105 are not functioning properly. As yet another example, control engine 106 may store the configuration of controller 104 (or portions thereof) in memory 122 (e.g., non-volatile memory) such that controller 104 (or portions thereof) is operational regardless of whether controller 104 is communicating with network controller 180 and/or other components in system 100. As yet another example, the control engine 106 may obtain readings from a proximate sensor (e.g., from a proximate light fixture) if the sensor 160 associated with the light fixture 102 fails, if the communication link 105 between the sensor 160 and the controller 104 fails, and/or for any other reason that the readings of the sensor 160 associated with the light fixture 102 cannot reach the controller 104. To accomplish this, for example, network manager 180 may instruct proximity sensor 160 to communicate its readings to control engine 106 of controller 104 using communication link 105 upon a request from control engine 106.

As yet another example, the control engine 106 can identify a poor operating condition or event (e.g., over-voltage, under-voltage, voltage spikes, power surges) based on readings taken by a portion of the luminaire 102 (e.g., the control engine 106, the power source 140). In this case, metering may be used to take readings, and such metering capability may be included in control engine 106. If such metering fails, control engine 106 may be configured to run failure mode analysis without using readings from the failed metering. Additionally or in the alternative, control engine 106 may report the failure metric to network manager 180. As yet another example, the control engine 106 may cause the controller 104 to operate in an autonomous control mode if one or more components of the controller 104 (e.g., the communication module 108, the transceiver 124) that allow the controller 104 to communicate with another component of the system 100 fails.

Control engine 106 may also be configured to prevent an unauthorized user (hacker) from attempting to access controller 104 and/or some other component of system 100. For example, if the sensor 160 detects occupancy of an area showing light emitted from the light source 142 of the light fixture 102, the control engine 106 may ignore the dimming signal sent from the controller 104 to the power supply 140. As another example, control engine 106 may only allow access and/or reprogramming of controller 104 (or portions thereof) with a direct physical connection to controller 104 and thus prevent user 150 (e.g., a hacker) from remotely accessing and/or programming controller 104 or any portion thereof.

In some example embodiments, the control engine 106 may be used to communicate dimming functionality to the power supply 140. For example, if the user 150 sends instructions to adjust the light output of the light source 142, the control engine 106 may send a signal to the power source 140, either alone or using one or more relays 136, that instructs the power source 140 to adjust the amount of final power delivered by the power source 140 to the light source 142 such that the light emitted by the light source 142 corresponds to the dimming level requested by the engine 106. In any case, the control engine 106 may use the data (e.g., thresholds, sensor data 134, operating protocols 133) stored in the repository 130 while the control engine 106 controls the power supply 140.

Control engine 106 may provide control, communication, and/or other similar signals to user 150, network manager 180, and one or more of sensors 160. Similarly, control engine 106 can receive control, communication, and/or other similar signals from user 150, network manager 180, and one or more of sensors 160. Control engine 106 may control each sensor 160 automatically (e.g., based on one or more algorithms stored in control engine 106) and/or based on control, communication, and/or other similar signals received from another device over communication link 105. Control engine 106 may include a printed circuit board on which hardware processor 120 and/or one or more discrete components of controller 104 are positioned.

In certain example embodiments, control engine 106 may include an interface that enables control engine 106 to communicate with one or more components of light fixture 102 (e.g., power supply 140). For example, if the power supply 140 of the luminaire 102 operates according to IEC standard 62386, the power supply 140 may include a Digital Addressable Lighting Interface (DALI). In this case, the control engine 106 may also include DALI to enable communication with the power supply 140 within the luminaire 102. Such an interface may operate in conjunction with or independent of the communication protocol 132 used to communicate between the controller 104 and the user 150, the network manager 180, and the sensors 160.

Control engine 106 (or other component of controller 104) may also include one for performing its functionOr a plurality of hardware components and/or software elements. Such components may include, but are not limited to, universal asynchronous receiver/transmitter (UART), serial Peripheral Interface (SPI), direct Attachment Capability (DAC) storage, analog-to-digital converters, inter-integrated circuits (I) ² C) And a Pulse Width Modulator (PWM).

By using the control engine 106 as described herein, the controller 104 may operate in a fail-safe mode, illuminating the light source 142 despite an adverse condition or event (e.g., wireless network information time to power back ON (ON) after power down, failure of a component of the controller 104, hacking, dust accumulation ON the sensor 160, loss of communication with the network manager 180). In other words, if an adverse condition or event occurs that affects the operation of the luminaire 102 or any portion thereof (including the control engine 106), the controller 104 ensures that the light source 142 of the luminaire 102 emits light.

The communication module 108 of the controller 104 determines and implements a communication protocol (e.g., a communication protocol from the communication protocols 132 of the repository 130) used when the control engine 106 communicates with (e.g., sends signals to, receives signals from) one or more of the user 150, the network manager 180, and/or the sensors 160. In some cases, the communication module 108 accesses the sensor data 134 to determine whether a communication protocol is used to communicate with the sensor 160 associated with the sensor data 134. Additionally, the communication module 108 can interpret the communication protocol of the communications received by the controller 104 such that the control engine 106 can interpret the communications.

The communication module 108 may send and receive data between the network manager 180 or the user 150 and the controller 104. The communication module 108 may transmit and/or receive data in accordance with a given format of a particular communication protocol 132. The control engine 106 may use the communication protocol 132 information stored in the repository 130 to interpret data packets received from the communication module 108. Control engine 106 may also facilitate the transfer of data between one or more sensors 160 and network manager 180 or user 150 by converting the data into a format understood by communication module 108.

The communication module 108 may send and/or retrieve data (e.g., communication protocols 132, operating protocols 133, sensor data 134, operating information, error codes) directly to and/or from the repository 130. Alternatively, the control engine 106 may facilitate the transfer of data between the communication module 108 and the repository 130. The communication module 108 may also provide encryption to data sent by the controller 104 and decryption to data received by the controller 104. The communication module 108 may also provide one or more of a number of other services related to data sent from and received by the controller 104. Such services may include, but are not limited to, packet routing information and procedures to be followed in the event of data interruption.

The real time clock 110 of the controller 104 may track clock time, time intervals, amounts of time, and/or any other measure of time. The real-time clock 110 may also count the number of event occurrences, whether with or without regard to time. Alternatively, control engine 106 may perform a counting function. The real-time clock 110 is capable of tracking multiple time measurements simultaneously. The real time clock 110 may track the time period based on instructions received from the control engine 106, based on instructions received from the user 150, based on instructions programmed in software of the controller 104, based on some other condition or according to some other component, or according to any combination thereof.

The real-time clock 110 may be configured to track time when no power usage, such as a super capacitor or battery backup, is delivered to the controller 104 (e.g., a power module 112 failure). In this case, the real time clock 110 may communicate any aspect of time to the controller 104 when power delivery to the controller 104 resumes. In this case, the real-time clock 110 may include one or more of a number of components (e.g., a super capacitor, an integrated circuit) for performing these functions.

The energy metering module 111 of the controller 104 measures one or more power components (e.g., current, voltage, resistance, VAR, watts) at one or more points within the luminaire 102. The energy metering module 111 may include any of a number of measuring devices and related devices, including but not limited to, voltmeters, ammeters, power meters, ohmmeters, current transformers, voltage transformers, and electrical wiring. The energy metering module 111 may measure the power component continuously, periodically, based on the occurrence of an event, based on a command received from the control engine 106, and/or based on some other factor.

The power module 112 of the controller 104 provides power to one or more components of the controller 104 (e.g., the real time clock 110, the control engine 106). Additionally, in certain example embodiments, the power module 112 may provide power (e.g., secondary power) to the power supply 140 of the luminaire 102. The power module 112 may include one or more of a number of single or multiple discrete components (e.g., transistors, diodes, resistors) and/or a microprocessor. The power module 112 may include a printed circuit board on which the microprocessor and/or the one or more discrete components are positioned. In some cases, the power module 112 may include one or more components that allow the power module 112 to measure one or more power elements (e.g., voltage, current) delivered to and/or transmitted from the power module 112. Alternatively, the controller 104 may use the energy metering module 111 to measure one or more power elements flowing in, flowing out, and/or flowing within the controller 104.

The power module 112 may include one or more components (e.g., transformers, diode bridges, inverters, converters) that receive power from a source external to the light fixture 102 (e.g., via a cable) and generate power of a type (e.g., alternating current, direct current) and level (e.g., 12V, 24V, 120V) that may be used by other components of the controller 104 and/or the power supply 140. Additionally or in the alternative, the power module 112 may itself be a source of electrical power to provide signals to other components of the controller 104 and/or the power supply 140. For example, the power module 112 may be a battery or other form of energy storage device. As another example, the power module 112 may be a localized photovoltaic power generation system. The power module 112 also has sufficient isolation in the associated components of the power module 112 (e.g., transformers, optocouplers, current and voltage limiting devices) so that the power module 112 is certified to provide power to intrinsically safe circuits.

In certain example embodiments, the power module 112 of the controller 104 also provides power and/or control signals, either directly or indirectly, to one or more of the sensors 160. In this case, control engine 106 may direct power generated by power module 112 to sensor 160 and/or power source 140 of light fixture 102. In this way, power may be conserved by sending power to the sensors 160 and/or the power source 140 of the light fixture 102 when such devices require power, as determined by the control engine 106.

According to one or more example embodiments, the hardware processor 120 of the controller 104 executes software, algorithms, and firmware. Specifically, hardware processor 120 may execute software on control engine 106 or any other portion of controller 104 and software used by one or more of user 150, network manager 180, and/or sensors 160. In one or more example embodiments, hardware processor 120 may be an integrated circuit, a central processing unit, a multi-core processing chip, a SoC, a multi-chip module including multiple multi-core processing chips, or other hardware processor. Hardware processor 120 is known by other names including, but not limited to, computer processors, microprocessors, and multi-core processors.

In one or more example embodiments, hardware processor 120 executes software instructions stored in memory 122. Memory 122 includes one or more cache memories, a main memory, and/or any other suitable type of memory. The memory 122 may include volatile and/or nonvolatile memory. According to some example embodiments, the memory 122 is located separately within the controller 104 from the hardware processor 120. In some configurations, the memory 122 may be integrated with the hardware processor 120.

In certain example embodiments, the controller 104 does not include the hardware processor 120. In this case, as an example, the controller 104 may include one or more Field Programmable Gate Arrays (FPGAs), one or more Insulated Gate Bipolar Transistors (IGBTs), and/or one or more Integrated Circuits (ICs). The use of FPGAs, IGBTs, ICs, and/or other similar devices known in the art allows the controller 104 (or portions thereof) to be programmable and function according to certain logic rules and thresholds without the use of a hardware processor. Alternatively, FPGAs, IGBTs, ICs, and/or the like may be used in conjunction with one or more hardware processors 120. Alternatively, FPGAs, IGBTs, ICs, and/or the like may be used in conjunction with one or more hardware processors 120.

The transceiver 124 of the controller 104 may send and/or receive control and/or communication signals. In particular, transceiver 124 may be used to communicate data between controller 104 and user 150, network manager 180, and/or sensors 160. The transceiver 124 may use wired and/or wireless technology. Transceiver 124 may be configured in such a way that control and/or communication signals transmitted and/or received by transceiver 124 may be received and/or transmitted by another transceiver that is part of user 150, network manager 180, and/or sensor 160. The transceiver 124 may use any of a number of signal types, including but not limited to radio signals.

Where transceiver 124 uses wireless technology, any type of wireless technology may be used by transceiver 124 to transmit and receive signals. Such wireless technologies may include, but are not limited to, wi-Fi, visible light communication, cellular networking, and bluetooth. Transceiver 124 may use one or more of any number of suitable communication protocols (e.g., ISA100, HART) in transmitting and/or receiving signals. Such communication protocols may be stored in the communication protocols 132 of the repository 130. Further, any transceiver information about the user 150, the network manager 180, and/or the sensor 160 may be part of the sensor data 134 (or similar area) of the repository 130.

Optionally, in one or more example embodiments, the security module 128 protects interactions between the controller 104, the user 150, the network manager 180, and/or the sensors 160. More specifically, the security module 128 authenticates communications from the software based on a security key that verifies the identity of the source of the communications. For example, the user software may be associated with a security key that enables the software of the user 150 to interact with the controller 104 and/or the sensor 160. Further, in some example embodiments, security module 128 may restrict the receipt of, request for, and/or access to information.

As mentioned above, in addition to the controller 104 and its components, the light fixture 102 may include a power source 140, one or more light sources 142, and an optional relay 136. The light source 142 of the light fixture 102 is a device and/or component commonly found in light fixtures for allowing the operation of the light fixture 102. The light fixture components 142 may be electrical, electronic, mechanical, or any combination thereof. The light fixture 102 may have one or more of any number and/or type of light sources 142. Examples of such light sources 142 may include, but are not limited to, local control modules, light sources, light engines, heat sinks, electrical conductors or cables, terminal blocks, lenses, diffusers, mirrors, air moving devices, shutters, dimmers, and circuit boards.

The power supply 140 of the light fixture 102 receives power (e.g., primary power, secondary power) from an external source (e.g., wall outlet, energy storage device). The power supply 140 uses the power it receives to generate and provide power (also referred to herein as final power) to one or more of the light sources 142. Power supply 140 may be referred to by any of a number of other names, including but not limited to drivers, LED drivers, and ballasts. The power supply 140 may be substantially the same as or different from the power module 112 of the controller 104. The power module 140 may include one or more of a number of single or multiple discrete components (e.g., transistors, diodes, resistors) and/or a microprocessor. The power module 140 may include a printed circuit board on which the microprocessor and/or the one or more discrete components are located and/or a dimmer.

The power supply 140 may include one or more components (e.g., transformers, diode bridges, inverters, converters) that receive power from the power module 112 of the controller 104 (e.g., via cables) and generate power of the type (e.g., alternating current, direct current) and level (e.g., 12V, 24V, 120V) usable by the light sources 142. Additionally or in the alternative, the power source 140 may receive power from a source external to the light fixture 102. Additionally or in the alternative, the power source 140 may itself be a source of electrical power. For example, the power source 140 may be a battery, a localized photovoltaic power system, or some other independent source of electrical power.

The relay 136 may be and/or include any type of switch for ensuring that power is delivered to the power source 140 such that the light source 142 is fully illuminated when there is a disruption or adverse event (e.g., a power outage, improper control of the light fixture 102) in the normal or intended operation of the light fixture 102. The relay 136 may be solid state, electromechanical, or some combination thereof. The relay 136 may include a contact (e.g., contact 537 of fig. 5, below) and a coil (e.g., coil 538 of fig. 5, below) electrically coupled to a dimming signal originating from the control engine 106. When an interruption of normal or expected operation of the light fixture 102 occurs, the coil of the relay 136 changes state (e.g., is de-energized), which opens the contacts of the relay 136. When the contacts of the relay 136 are open, the dimming interface of the power supply 140 senses a high input impedance. The high input impedance at the dimming interface of the power supply 140 automatically delivers full power to the light source 142, which leaves the fully illuminated light source 142 until the contacts of the relay 136 reclose, which maintains a low impedance dimming connection. More details regarding the relay 136 are provided below with respect to fig. 5.

As described above, the light fixture 102 may be placed in any of a variety of environments. In this case, the housing 102 of the luminaire 102 may be configured to comply with applicable standards for any of a variety of environments. For example, the luminaire 102 may be rated as a zone 1 or zone 2 housing according to NEC standards. Similarly, any of the sensors 160 or other devices communicatively coupled to the light fixtures 102 may be configured to comply with applicable standards for any of a variety of environments. For example, sensor 160 may be rated as a zone 1 or zone 2 shell according to NEC standards.

Fig. 2 illustrates one embodiment of a computing device 218 implementing one or more of the various techniques described herein and representing, in whole or in part, elements described herein, according to some example embodiments. Computing device 218 is one example of a computing device and is not intended to suggest any limitation as to the scope of use or functionality of the computing device and/or its possible architecture. Neither should the computing device 218 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example computing device 218.

Computing device 218 includes one or more processors or processing units 214, one or more memory/storage components 215, one or more input/output (I/O) devices 216, and a bus 217 that allows the various components and devices to communicate with one another. The bus 217 represents one or more buses of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 217 includes wired and/or wireless buses.

Memory/storage component 215 represents one or more computer storage media. Memory/storage component 215 includes volatile media (such as Random Access Memory (RAM)) and/or nonvolatile media (such as Read Only Memory (ROM), flash memory, optical disks, magnetic disks, and so forth). Memory/storage component 215 includes fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a flash memory drive, a removable hard drive, an optical disk, and so forth).

The one or more I/O devices 216 allow a customer, utility or other user to input commands and information to the computing device 218, and also allow information to be presented to the customer, utility or other user and/or other components or devices. Examples of input devices include, but are not limited to, a keyboard, a cursor control device (e.g., a mouse), a microphone, a touch screen, and a scanner. Examples of output devices include, but are not limited to, a display device (e.g., a monitor or projector), speakers, output to a lighting network (e.g., a DMX card), a printer, and a network card.

Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Implementations of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer-readable media can be any available non-transitory medium or media that can be accessed by a computing device. By way of example, and not limitation, computer-readable media may comprise "computer storage media".

"computer storage media" and "computer readable media" include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, computer readable media such as RAM, R0M, EEPR0M, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

According to some example embodiments, computer device 218 is connected to a network (not shown) (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) such as the internet, a cloud network, or any other similar type of network) via a network interface connection. Those skilled in the art will appreciate that many different types of computer systems exist (e.g., desktop computers, laptop computers, personal media devices, mobile devices such as cell phones or personal digital assistants, or any other computing system capable of executing computer-readable instructions), and that in other example embodiments, the aforementioned input and output devices take other forms, now known or later developed. Generally speaking, the computer system 218 includes at least the minimum processing, input, and/or output devices necessary to practice one or more embodiments.

Further, those skilled in the art will appreciate that in certain example embodiments, one or more elements of the above-described computer device 218 are located at a remote location and connected to the other elements over a network. Further, one or more embodiments are implemented on a distributed system having one or more nodes, where each portion of an implementation (e.g., control engine 106) is located on a different node within the distributed system. In one or more embodiments, the node corresponds to a computer system. Alternatively, in some example embodiments, the node corresponds to a processor having an associated physical memory. In some example embodiments, the node may alternatively correspond to a processor having shared memory and/or resources.

Fig. 3 illustrates a luminaire 302 according to some example embodiments. Referring to fig. 1-3, the luminaire 302 of fig. 3 is a physical embodiment of the luminaire 102 of fig. 1. The light fixture 302 of fig. 3 includes a housing 303, a number of light sources 342, and a sensor 360 coupled to the housing 303.

Fig. 4 illustrates a system diagram of a luminaire 402, according to some example embodiments. Referring to fig. 1-4, the luminaire 402 of fig. 4 is substantially similar to the luminaire 102 of fig. 1, except that internal connections (communication links 405) are shown between and within the controller 404, the sensor 460, the power source 440, and the light source 442. The controller 404 includes a relay 436, a control engine 406, a power module 412, and a real time clock 410. Although not shown in FIG. 4, the light fixture 402 of FIG. 4 includes a housing 303, a number of light sources 342, and a sensor 360 coupled to the housing 303. In this case, the relay 436 is used to act as an on/off switch with respect to the power delivered from the power source 440.

Fig. 5 illustrates a system diagram of another luminaire 502, according to some example embodiments. Referring to fig. 1-5, the light fixture 502 of fig. 5 is substantially similar to the light fixture 402 of fig. 4, except that the relay 536 serves a different purpose than the relay 436 of fig. 4. Specifically, the relay 536 of fig. 5 provides high impedance to the dimmer interface of the power supply 540 in the event of a failure of the controller 504. In this case, the relay 536 includes a contact 537 (or in some cases, an optical switch 537) and a coil 538 (or in some cases, an LED 538). Generally, the coil 538 of the relay 536 has an enabled state (e.g., energized, illuminated) and a disabled state (e.g., de-energized, not illuminated). The contacts 537 have an open state and a closed state. When the coil 538 is in the enabled state, the contacts 537 are in one state (e.g., closed). While the coil 538 is in the disabled state, the contacts 537 are in another state (e.g., open).

In this particular configuration, the contacts 537 of the relay 536 are electrically coupled to a 0V-10V DC dimming signal generated by the controller 504 and the power supply 540, which receives power via the link 505 and generates final power that corresponds to the dimming signal and is used to adjust the amount of light emitted by the light source 542 based on the dimming level. Also, the coil 538 of the relay 536 is electrically coupled to the power terminals of the controller 504. When the controller 504 (or more specifically, the control engine) is operating normally, the power terminals of the controller 504 send voltage through the coil 538 of the relay 536 and place the coil 538 in an enabled state. In this case, the coil 538 is an LED 538 and is illuminated in the enabled state, which closes the contacts 537. With the contacts 537 closed, a 0V-10V DC dimming signal flows from the controller 504 through the closed contacts 537 to the power supply 540.

When the controller 504 loses power, malfunctions, or otherwise ceases to function, there is no voltage at the power terminals of the controller 504. Thus, the coil 538 of the relay 536 is in a disabled state. Thus, the 0V-10V DC dimming signal generated by the controller 504 does not reach the power supply 540. Therefore, power supply 540 assumes no dimming, and thus directs light source 542 to emit full light output. In this manner, if the controller 504 fails, the relay 536 ensures that the light source 542 emits full light output. In certain example embodiments, the relay 536 is an optical device and, thus, there is no possibility of arcing or sparking. In this way, the relay 536 may be safely used in a hazardous environment.

Fig. 6A-6E illustrate example electrical schematic diagrams of a luminaire 602, according to some example embodiments. Specifically, referring to fig. 1-6E, the light fixture 602 of fig. 6A-6E shows example circuitry for a combination of a plurality of sensors 660 (in this case, current/voltage sensors and temperature sensors), a relay 636, a portion of a power supply 640, a real-time clock 610, a control engine 606 (including a hardware processor 620), an energy metering module 611, and a communication module 608 and an application interface 626. Each of these components of the light fixture 602 may include one or more of a number of components, including but not limited to resistors, capacitors, inductors, transformers, ICs, transistors, diodes, optocouplers, fuses, and varistors. Any of the components of the light fixture 602 shown in fig. 6A-6E may have any variety of different configurations and/or components.

Fig. 7-10 illustrate flow charts of how a controller controls a luminaire according to some example embodiments. While the various steps in these flowcharts are presented and described sequentially, one of ordinary skill in the art will appreciate that some or all of the steps are performed in a different order, combined, or omitted, and some or all of the steps are performed in parallel according to example embodiments. Further, in one or more of the example embodiments, one or more of the steps described below are omitted, repeated, and/or performed in a different order. Additionally, one of ordinary skill in the art will appreciate that in certain example embodiments, additional steps not shown in fig. 7-10 may be included in performing these methods. Accordingly, the specific arrangement of steps should not be construed as limiting the scope. Additionally, a particular computing device as described (e.g., of fig. 2 above) may be used to perform one or more of the steps of the methods of fig. 7-10 or any other method described or inferred herein.

Referring to fig. 1-10, the method 751 of fig. 7 begins at step 752 where a user (e.g., user 150) dims the light output of a light source (e.g., light source 142) of a luminaire (e.g., luminaire 102). For example, a user may manipulate a dimmer selection using a user interface (e.g., digital controller, dial, slider bar) to instruct a controller (e.g., controller 104) regarding an adjustment of the amount of light output by the light source.

In step 753, when the controller receives a dimming instruction from a user, the controller determines whether there is occupancy of the space in which the luminaire is located. The controller may use one or more of a number of components of the light fixture (e.g., sensor 160) to determine whether there is occupancy of the space in which the light fixture is located. If no space occupancy is detected, the process proceeds to step 754 where the controller controls the power supply (e.g., power supply 140) according to the dimming command. When this occurs, the power supply delivers the adjusted level of final power to the light source, which in turn adjusts the light output of the light source to a level corresponding to the user requested dimming level.

On the other hand, if the presence of space usage is detected, the process proceeds to step 755 in which the controller determines whether the user requested dimming level is above a threshold (e.g., as stored in the repository 130). If the user requested dimming level is above the threshold, the controller controls the power supply (e.g., power supply 140) according to the dimming command. When this occurs, the power supply delivers the adjusted level of final power to the light source, which in turn adjusts the light output of the light source to a level corresponding to the user requested dimming level.

On the other hand, if the user requested dimming level is below the threshold, the controller ignores the dimming instruction from the user. Alternatively, if the user requested dimming level is below the threshold, the controller sets the dimming level at the threshold. In other words, the controller instructs the power source (e.g., power source 140) to deliver the adjusted level of final power to the light source, which in turn adjusts the light output of the light source to a level corresponding to the threshold.

In this case, the threshold may be a safe value that requires the light fixture to emit a minimum amount of light when the space is occupied so that the occupant sees sufficient light. Such a threshold may be installed in firmware in such a way that the user does not change the threshold. Alternatively, the threshold may be adjusted by the user. Also, the controller may use one or more other sensors (e.g., photocells) to determine the amount of ambient light in the space. In some example embodiments, dimming instructions from a user may be followed rather than ignored, such as if the amount of ambient light in the space is above a threshold.

Method 845 of fig. 8 begins at step 846, where the control profile of the luminaire is set by the user. The control profile may include any of a variety of types of data. Examples of such data may include, but are not limited to, dimming threshold with occupancy, dimming threshold without occupancy, occupancy delay time, and the time zone in which the light fixture is located. Once the control profile is received, the process proceeds to step 847 where the control profile is stored in a store (e.g., store 130). This control profile is then used by the control engine to control the power supply 140. In some cases, the control profile (or portions thereof) may be altered at any time, such as by a user or by a control engine based on historical data. Alternatively, the user may be the manufacturer and the control profile (or portions thereof) may remain unchanged once the luminaire leaves the manufacturer.

The method 961 of FIG. 9 illustrates what may occur during power savings and outages using an example embodiment. In step 962 of method 961, once the energy metering module (e.g., energy metering module 111) determines that the primary power delivered to the controller (e.g., controller 104) and/or the power source (e.g., power source 140) is interrupted, the controller may set the dimming value at 100% (i.e., the light source emits the maximum amount of light that it is capable of emitting). Further, in some cases, the controller 104 may use the energy metering module on some basis (e.g., continuously, periodically) to determine when a power savings or outage condition has ended. In addition, the controller 104 may use a secondary power source (e.g., a super capacitor) to continue providing power to a real-time clock (e.g., the real-time clock 110) when it is determined that a power savings or outage occurs. In this way, the time value of the real-time clock is less likely to be compromised.

In step 963, the controller may use a real-time clock (e.g., real-time clock 110) to verify a time value associated with the power save/power off condition and determine whether the time value is corrupted. If the time value is not corrupted, the process continues to step 965 where the controller uses the settings stored in the repository (e.g., repository 130) to determine the control profile settings for the power saving/outage time.

If the time value is corrupted, the process continues to step 964 where the controller determines if the time of the real time clock is updated during the joining process. If the time is updated during the splicing process, the process proceeds to step 965, discussed above. If the time is not updated during splicing, the process proceeds to step 962, discussed above.

The method 1071 of fig. 10 illustrates, using an example embodiment, what happens when a sensor (e.g., sensor 160) becomes idle or loses communication with a controller (e.g., due to a failure of a communication link (e.g., communication link 105)). In step 1072, the controller (e.g., controller 104) disables wireless data transfer with the sensor. In step 1073, the controller determines whether the luminaire has its own sensor that can perform the same function (or its equivalent) as the disabled sensor. If the lamp has its own sensor, the controller uses a sensor integrated with the luminaire. In this case, the controller may use the sensor data of the integrated sensor stored in the storage library.

If the luminaire does not have its own sensor, the process continues to step 1075 where the controller is adapted to operate without disabling the sensor. For example, if a disable sensor is associated with the detection of a light level, the controller may disable daylight harvesting from its operating mode and instead transition to a schedule mode. As another example, if the disabled sensor is associated with occupancy, the controller may assume that someone is always present in the space associated with the light fixture.

After completion of either step 1074 or step 1075, the process proceeds to step 1076 where a determination is made as to whether the sensor continues to be idle or lack of communication with the controller. If the sensor continues to be disabled, the process returns to step 1073. If the sensor is no longer disabled, the process continues to step 1077 where the controller determines whether to return to using the previously disabled sensor or to maintain operation with the integrated sensor. This determination may be made based on one or more of a number of factors, including but not limited to user preferences, one or more protocols, the amount of time the sensor was disabled, and whether a previously disabled sensor was fully functional. The controller may test a previously disabled sensor to determine the functional range of the sensor.

Example embodiments provide a fail-safe lighting control system for a luminaire. In particular, certain example embodiments allow a luminaire to emit full light output when any of a number of adverse events occur. In this manner, example embodiments may eliminate the risk of lamp systems or portions thereof being hacked. In addition, example embodiments allow complex control systems with many components to be used with light fixtures while maintaining the reliability of the light fixture. In some cases, a luminaire with an example fail-safe lighting control system may be located in a particular environment (e.g., a hazardous environment). In this case, the luminaire may comply with one or more applicable standards for the environment. Communications between the luminaires with the example fail-safe lighting control system and other components of the system (e.g., users, sensors, network managers) may be implemented using wired and/or wireless technologies.

While the embodiments described herein have been made with reference to example embodiments, those skilled in the art will appreciate that various modifications are well within the scope and spirit of the present disclosure. Those skilled in the art will appreciate that the example embodiments described herein are not limited to any particular discussed application, and that the embodiments described herein are illustrative and not limiting. From the description of the example embodiments, those skilled in the art will appreciate equivalents to the elements shown therein and ways to construct other embodiments using the disclosure will be understood by practitioners in the art. Accordingly, the scope of example embodiments is not limited herein.

Claims

1. A light fixture, comprising:

at least one light source;

at least one power source that receives primary power, wherein the at least one power source uses the primary power to generate final power, wherein the at least one power source delivers the final power to the at least one light source;

a controller coupled to the at least one power source, wherein the controller:

detecting a failure of at least one control component, wherein the at least one control component is to facilitate controlling operation of the light fixture based on an operating protocol;

controlling the at least one power supply to provide the final power to the at least one light source during a failure of the at least one control component using another operating protocol that is followed at a point in time based on certain conditions; and

determining whether to revert to the operating protocol or continue with the other operating protocol based on one or more predetermined factors when the controller detects that the failure of the at least one control component has ceased,

wherein the operating protocol and the another operating protocol are algorithms or formulas.

2. The light fixture of claim 1, wherein the final power provided by the at least one power source to the at least one light source during a failure of the at least one control component is a maximum amount of power, wherein the at least one light source uses the maximum amount of power to produce full light output.

3. The light fixture of claim 2, wherein the controller comprises a switch, wherein the switch of the controller changes state during a failure of the at least one control component, wherein the switch is coupled to the at least one power source.

4. The light fixture of claim 3, wherein the failure of the at least one control component comprises a malfunction of the controller, wherein the switch automatically changes state according to the other operating protocol during the malfunction of the controller.

5. The light fixture of claim 1, wherein the failure of the at least one control component comprises an excessive dust accumulation on a sensor, wherein the sensor is coupled to the controller, wherein the excessive dust accumulation on the sensor causes the controller to malfunction.

6. The luminaire of claim 1, wherein the failure of the at least one control component comprises a failure of a sensor, wherein the sensor provides a measurement to the controller, wherein the controller uses the measurement to determine the light output of the at least one light source.

7. The luminaire of claim 6, further comprising:

an additional sensor disposed proximate to the at least one light source, wherein the additional sensor provides a sensor reading to the controller during a failure of the at least one control component.

8. The luminaire of claim 1, wherein the failure of the at least one control component comprises a cut-off communication between the controller and a network manager.

9. The luminaire of claim 1, wherein the failure of the at least one control component comprises at least one selected from the group consisting of: detecting an overvoltage, detecting an undervoltage, detecting a voltage spike, and detecting a voltage surge.

10. The light fixture of claim 1, wherein the failure of the at least one control component comprises a failure of a communication module of the controller.

11. The light fixture of claim 1, wherein the failure of the at least one control component comprises a failure of a transceiver of the controller.

12. The luminaire of claim 1, further comprising:

a housing, wherein the failure of the at least one control component comprises exceeding a threshold temperature within the housing.

13. The light fixture of claim 1, wherein the failure of the at least one control component comprises an inability to meter energy associated with the controller.

14. The luminaire of claim 1, wherein the failure of the at least one control component comprises unauthorized access to the controller.

15. The luminaire of claim 1, further comprising:

a power module coupled to the controller, wherein the power module includes an energy storage device capable of delivering secondary power to a real time clock of the controller.

16. The light fixture of claim 15, wherein the failure of the at least one control component comprises a loss of the primary power delivered to the at least one power source, wherein the energy storage device delivers the secondary power to the real-time clock during the failure of the at least one control component, and wherein the real-time clock maintains a time value during the failure of the at least one control component using the secondary power.

17. The luminaire of claim 1, wherein the failure of the at least one control component comprises a request by a user to dim the light output of the at least one light source below a threshold when a sensor detects occupancy within a space in which the light output is directed.

18. An illumination system, comprising:

a first light fixture, the first light fixture comprising:

at least one first light source; and

at least one first power source that receives a first primary power, wherein the at least one first power source uses the first primary power to generate a first final power, wherein the at least one first power source delivers the first final power to the at least one first light source; and

a controller coupled to the at least one first power source, wherein the controller:

detecting a first failure of at least one first control component, wherein the at least one first control component is to facilitate controlling operation of the first light fixture based on an operating protocol;

controlling the at least one first power source to provide the first final power to the at least one first light source during a first failure of the at least one first control component using another operating protocol that is followed based on certain conditions at a point in time; and

19. The lighting system of claim 18, further comprising:

a second light fixture, the second light fixture comprising:

at least one second light source; and

at least one second power source that receives second primary power, wherein the at least one second power source generates second final power using the second primary power, wherein the at least one second power source delivers the second final power to the at least one second light source,

wherein the controller is further coupled to the at least one second power source, wherein the controller is further to:

detecting a second fault of at least one second control component, wherein the at least one second control component is to facilitate controlling operation of the second luminaire based on the operating protocol; and

controlling the at least one second power source to provide the second final power to the at least one second light source during a second failure of the at least one second control component using the another operating protocol followed at a point in time based on certain conditions.

20. A controller for a luminaire, comprising:

a control engine coupled to a power supply of the luminaire, wherein the controller is configured to:

detecting a failure of at least one control component, wherein the at least one control component is to facilitate controlling operation of the luminaire based on an operating protocol; and

controlling the power supply to provide final power to at least one first light source of the luminaire during a failure of the at least one control component using another operating protocol that is followed based on certain conditions at a point in time; and