Patent Publication Number: US-11026302-B2

Title: Outdoor lighting fixtures control systems and methods

Description:
CROSS-REFERENCE TO RELATED PATENT APPLICATIONS 
     This application is a Continuation of U.S. application Ser. No. 16/154,322, filed Oct. 8, 2018, incorporated herein by reference in its entirety. U.S. application Ser. No. 16/154,322 is a Continuation of U.S. application Ser. No. 14/330,231, filed Jul. 14, 2014, incorporated herein by reference in its entirety. U.S. application Ser. No. 14/330,231 is a Continuation of U.S. application Ser. No. 13/902,449, filed May 24, 2013, incorporated herein by reference in its entirety. U.S. application Ser. No. 13/902,449 is a Continuation of U.S. application Ser. No. 12/550,270, filed Aug. 28, 2009, incorporated herein by reference in its entirety. U.S. application Ser. No. 12/550,270 is a Continuation-In-Part of U.S. application Ser. No. 12/240,805, filed Sep. 29, 2008, incorporated herein by reference in its entirety, which is a Continuation-In-Part of U.S. application Ser. No. 12/057,217, filed Mar. 27, 2008, incorporated herein by reference in its entirety. U.S. application Ser. No. 12/550,270 is also a Continuation-In-Part of U.S. application Ser. No. 11/771,317, filed Jun. 29, 2007, incorporated herein by reference in its entirety. 
    
    
     BACKGROUND 
     The present application relates generally to the field of lighting systems and lighting fixtures. The present application further relates to lighting fixture control systems and methods. 
     Control of lighting fixtures has conventionally been accomplished via hardwired switches. Some conventional lighting fixtures include a wireless receiver or transceiver for receiving commands from a control station. Conventional lighting fixtures have typically not been adaptable to different environmental changes or situations. 
     SUMMARY 
     One embodiment relates to a system for controlling lighting. The system includes a control module coupled to a driver. A light source coupled to the driver is configured to receive controlled power from the driver. A first sensor is configured to cooperate with the control module to detect occupancy and control the power delivered from the driver to the light source according to a signal provided to the control module by the first sensor, while a second sensor is configured to cooperate with the control module to detect ambient light and control the power delivered from the driver to the light source according to a signal provided to the control module by the second sensor. A graphical user interface (GUI) executing on a controller device wirelessly coupled to the control module is configured to communicate with the control module to configure the operation of the control module. The GUI is configured to execute on a touch-sensitive display configured to facilitate user interaction with the controller, and is operable to create one or more control groups, each group comprising multiple control modules. The GUI is also operable to control the driver to control the on/off state of the light source. The control module is programmable to cause the driver to control the light source according to the detection by the first sensor of occupancy, turning on the light source upon detecting that an area monitored by the first sensor is occupied and turning off the light source after a configurable delay period upon detecting that the area monitored by the first sensor is not occupied. The control module is programmable to cause the driver to control the light source according to the detection by the second sensor of ambient light. The system is configurable to include a switch to cause the light source to be turned on without regard to occupancy detected by the first sensor or ambient light detected by the second sensor. 
     Alternative exemplary embodiments relate to other features and combinations of features as may be generally recited in the claims. 
    
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
       The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which: 
         FIG. 1  is a perspective view of a lighting fixture system  10  including a lighting fixture  100  wired to a controller  300 , according to an exemplary embodiment; 
         FIG. 2A  is a schematic side-view of lighting fixture system  10  shown in  FIG. 1 , according to an exemplary embodiment; 
         FIG. 2B  is a diagram of a facility lighting system  200  for use with lighting fixture system  10 , according to an exemplary embodiment; 
         FIG. 3  is a block diagram of controller  300  shown in  FIGS. 1-2B , according to an exemplary embodiment; 
         FIG. 4  is a block diagram of a control computer for a facility lighting system such as that shown in  FIG. 2 , according to an exemplary embodiment; 
         FIG. 5A  is flow chart of a control process for controller  300 , according to an exemplary embodiment; 
         FIG. 5B  is a flow chart of a process for control computer  202  shown in  FIGS. 2B and 4 , according to an exemplary embodiment; 
         FIG. 6  is a diagram of an exemplary control system and related control activity, according to an exemplary embodiment; 
         FIG. 7  is a flow chart of a process for controlling multiple lighting fixtures in a zone based on sensor input, according to an exemplary embodiment; and 
         FIGS. 8-22  are illustrations of graphical user interface screens that may be caused to be displayed by control computer  202  shown in previous Figures for allowing user control of the lighting systems described herein, according to an exemplary embodiment. 
     
    
    
     DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS 
     Before turning to the figures, which illustrate the exemplary embodiments in detail, it should be understood that the application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting. 
     Referring generally to the Figures, a controller local to a lighting fixture is configured to intelligently utilize information available to the controller. The controller may conduct its own control decisions based on, for example, input from a motion sensor or ambient lighting sensor local to the controller. The controller may also include communications electronics for receiving “on/off” or other commands from a remote source (e.g., a network of lighting fixtures, a master controller, etc.). Regardless of the source for control decisions of the controller, the controller is configured to log usage information for the lighting fixture in memory local to the controller. In various exemplary embodiments, the controller includes communications electronics for communicating the logged information to other devices. The logged usage information may be used by other devices in the execution of a system-wide control scheme, in the execution of control algorithms relating particularly to the lighting fixture and controller that logged the information, or otherwise. The controller local to the lighting fixture can also use its own logged usage information during its local control decisions. 
     The controllers described herein can also relate to or be configured to control the electricity provided to devices other than lights. The controllers provided to lighting fixtures distributed around a space can advantageously be used to create a “grid” or wireless infrastructure in a facility that can be used to carry data communications from control systems and user interfaces to wireless relays located remotely from the control systems. 
     Referring now to  FIG. 1 , an underside perspective view of a fluorescent lighting fixture system  10  is shown, according to an exemplary embodiment. Lighting fixture system  10  includes a lighting fixture  100  and a controller  300 . Controller  300  is connected to lighting fixture  100  via wire  14 . Controller  300  is configured to control the switching between different states of lighting fixture  100  (e.g., all lamps on, all lamps off, some lamps on, etc.). According to various embodiments, controller  300  is further configured to log usage information for lighting fixture  100  in a memory device local to controller  300 . Controller  300  may further be configured to use the logged usage information to affect control logic of controller  300 . Controller  300  may also or alternatively be configured to provide the logged usage information to another device for processing, storage, or display. Controller  300  is shown to include a sensor  112  coupled to controller  300  (e.g., controller  300 &#39;s exterior housing). Controller  300  may be configured to use signals received from sensor  112  to affect control logic of controller  300 . Further, controller  300  may be configured to provide information relating to sensor  112  to another device. 
     Referring still to  FIG. 1 , lighting fixture  100  is shown to include a housing  102  (e.g., frame, fixture pan, etc.) within which fluorescent lamps  12  are housed. While various Figures of the present application, including  FIG. 1 , illustrate lighting fixtures for fluorescent lamps, it should be noted that embodiments of the present application may be utilized with any type of lighting fixture and/or lamps. Further, while housing  102  is shown as being fully enclosed (e.g., having a door and window covering the underside of the fixture), it should be noted that any variety of lighting fixture shapes, styles, or types may be utilized with embodiments of the present application. Further, while controller  300  is shown as having a housing that is exterior to housing  102  of lighting fixture  100 , it should be appreciated that controller  300  may be physically integrated with housing  102 . For example, one or more circuit boards or circuit elements of controller  300  may be housed within, on top of, or otherwise secured to housing  102 . Further, in other exemplary embodiments, controller  300  (including its housing) may be coupled directly to housing  102 . For example, controller  300 &#39;s housing may be latched, bolted, clipped, or otherwise coupled to the interior or exterior of housing  102 . Controller  300 &#39;s housing may generally be shaped as a rectangle (as shown), may include one or more non-right angles or curves, or otherwise configured. In an exemplary embodiment, controller  300 &#39;s housing is made of plastic and housing  102  for the lighting fixture  100  is made from metal. In other embodiments, other suitable materials may be used. 
     Referring now to  FIG. 2A , a diagram of lighting fixture system  10  is shown, according to an exemplary embodiment. Lighting fixture  100  is shown to include two lamp sets  108 ,  110  with two fluorescent lamps forming each lamp set. Each lamp set  108 ,  110  may further include one or any number of additional fluorescent lamps. Lighting fixture  100  is further shown to include first ballast  104  and second ballast  106 . However, while some embodiments described herein relate to the utilization of multiple lamp sets or ballasts within a single lighting fixture, it should be appreciated that many embodiments of the present application may only include a single lamp set and a single ballast. In other embodiments, more than two ballasts and lamp sets may be included in a single lighting fixture. While the fluorescent lamps are illustrated as tube lamps extending lengthwise relative to the lighting fixture, the fluorescent lamps may be compact fluorescent bulbs, lamps or bulbs of any other type or technology, run perpendicular to the length of the lighting fixture, or be otherwise oriented. Controller  300  is shown as wired to ballasts  104 ,  106  via wires  280 ,  281  (which may be contained within one cable or wire loom such as shown in  FIG. 14 ). 
     Referring now to  FIG. 2B , a diagram of a facility lighting system  200  for use with lighting fixture system  10  including controller  300  and lighting fixture  100  is shown, according to an exemplary embodiment. Facility lighting system  200  is shown to include control computer  202  that is configured to conduct or coordinate control activities relative to multiple lighting fixture controllers such as controller  300 . 
     Control computer  202  is preferably configured to provide a graphical user interface to a local or remote electronic display screen for allowing a user to adjust control parameters, turn lighting fixtures on or off, or to otherwise affect the operation of lighting fixtures in a facility. For example, control computer  202  is further shown to include touch screen display  210  for displaying such a graphical user interface and for allowing user interaction (e.g., input and output) with control computer  202 . Various exemplary graphical user interfaces for display on touch screen display  210  and control activities associated therewith are described in subsequent paragraphs and with reference to subsequent Figures of the present application. It should be noted that while control computer  202  is shown in  FIG. 2B  as housed in a wall-mounted panel it may be housed in or coupled to any other suitable computer casing or frame. The user interfaces, examples of which are shown in  FIGS. 8-22 , are intended to provide an easily configurable lighting and/or energy management system for a facility. The user interfaces are intended to allow even untrained users to reconfigure or reset a lighting system using relatively few clicks. In an exemplary embodiment, the user interfaces do not require a keyboard for entering values. Advantageously, users other than building managers may be able to setup, interact with, or reconfigure the system using the provided user interfaces. 
     Referring further to  FIG. 2B , control computer  202  is shown as connected to master transceiver  240 . Master transceiver  240  may be a radio frequency transceiver configured to provide wireless signals to a network of controllers such as controller  300 . In  FIG. 2B , master transceiver  240  is shown in bi-directional wireless communication with a plurality of lighting fixture controllers  300 ,  262 ,  271 , and  272 .  FIG. 2B  further illustrates controllers  300  and  262  forming a first logical group  260  identified as “Zone I” and a second logical group  270  identified as “Zone II.” Control computer  202  may be configured to provide different processing or different commands for “Zone I” relative to “Zone II.” While control computer  202  is configured to complete a variety of control activities for lighting fixture controllers  300 ,  262 ,  271 ,  272 , in many exemplary embodiments of the present application, each controller associated with a lighting fixture (e.g., controllers  300 ,  262 ,  271 ,  272 ) includes circuitry configured to provide a variety of “smart” or “intelligent features” that are either independent of control computer  202  or operate in concert with control computer  202 . A detailed block diagram of such a controller is shown in  FIG. 3 . 
     Referring now to  FIG. 3 , a detailed block diagram of controller  300  is shown, according to an exemplary embodiment. Controller  300  is generally configured to include circuitry configured with an algorithm to control on/off cycling of connected lighting fixtures, an algorithm to log usage information for the lighting fixture, an algorithm configured to prevent premature restrikes to limit wear on the lamps and ballast, and an algorithm configured to allow controller  300  to send and receive commands or information from other peer devices independently from a master controller or master transceiver. 
     Controller  300  is shown to include power relays  302  configured to controllably switch on or off high voltage power outputs that may be provided to first ballast  104  and second ballast  106  via wires  280 ,  281 . It should be noted that in other exemplary embodiments, power relays  302  may be configured to provide a low voltage control signal, optical signal, or otherwise to the lighting fixture which may cause one or more ballasts, lamps, and/or circuits of the fluorescent lighting fixture that the controller serves to turn on and off. While power relays  302  are configured to provide high voltage power outputs to ballasts  104 ,  106 , it should be appreciated that controller  300  may include a port, terminal, receiver, or other input for receiving power from a high voltage power source. In embodiments where a relatively low voltage or no voltage control signal is provided by relays  302 , power for circuitry of controller  300  may be received from a power source provided to the lighting fixtures or from another source. In any embodiment of controller  300 , appropriate power supply circuitry (e.g., filtering circuitry, stabilizing circuitry, etc.) may be included with controller  300  to provide power to the components of controller  300  (e.g., relays  302 ). 
     Referring still to  FIG. 3 , controller  300  is shown to include control circuit  304  which receives and provides data or control signals from/to power relays  302  and sensor circuit  310 . Control circuit  304  is configured to cause one or more lamps of the fluorescent lighting fixture to turn on and off via control signals sent to power relays  302 . Control circuit  304  can make a determination that an “on” or “off” signal should be sent to power relays  302  based on inputs received from wireless controller  305  or sensor circuit  310 . For example, a command to turn the lighting fixture “off” may be received at wireless transceiver  306  and interpreted by wireless controller  305 . Upon recognizing the “off” command, wireless controller  305  provides an appropriate control signal to control circuit  304  which causes control circuit  304  to switch one or more of power relays  302  off. Similarly, when sensor circuit  310  including sensor  112  experiences an environmental condition, logic module  314  may determine whether or not the controller and control circuit  304  should change “on/off” states. For example, if a high ambient lighting level is detected by sensor  112 , logic module  314  may determine that control circuit  304  should change states such that power relays  302  are “off.” Conversely, if a low ambient lighting level is detected by sensor  112 , logic module  314  may cause control circuit  304  to turn power relays  302  “on.” Other control decisions, logic and activities provided by controller  300  and the components thereof are described below and with reference to other Figures. 
     When or after control decisions based on sensor  112  or commands received at wireless transceiver are made, in some exemplary embodiments, logic module  314  is configured to log usage information for the lighting fixture in memory  316 . For example, if control circuit  304  causes power relays  302  to change states such that the lighting fixture turns on or off, control circuit  304  may inform logic module  314  of the state change and logic module  314  may log usage information based on the information from control circuit  304 . The form of the logged usage information can vary for different embodiments. For example, in some embodiments, the logged usage information includes an event identifier (e.g., “on”, “off”, cause for the state change, etc.) and a timestamp (e.g., day and time) from which total usage may be derived. In other embodiments, the total “on” time for the lighting fixture (or lamp set) is counted such that only an absolute number of hours that the lamp has been on (for whatever reason) has been tracked and stored as the logged usage information. In addition to logging or aggregating temporal values, each logic module  314  may be configured to process usage information or transform usage information into other values or information. For example, in some embodiments time-of-use information is transformed by logic module  314  to track the energy used by the lighting fixture (e.g., based on bulb ratings, known energy draw of the fixture in different on/off/partial on modes, etc.). In some embodiments, each logic module  314  will also track how much energy savings the lighting fixture is achieving relative to a conventional lighting fixture, conventional control logic, or relative to another difference or change of the lighting fixture. For the purposes of many embodiments of this application, any such information relating to usage for the lighting fixture may be considered logged “usage information.” In other embodiments, the usage information logged by module  314  is limited to on/off events or temporal aggregation of on states; in such embodiments energy savings calculations or other calculations may be completed by a control computer  202  or another remote device. 
     In an exemplary embodiment, controller  300  (e.g., via wireless transceiver  306 ) is configured to transmit the logged usage information to remote devices such as control computer  202 . Wireless controller  305  may be configured to recall the logged usage information from memory  316  at periodic intervals (e.g., every hour, once a day, twice a day, etc.) and to provide the logged usage information to wireless transceiver  306  at the periodic intervals for transmission back to control computer  202 . In other embodiments, control computer  202  (or another network device) transmits a request for the logged information to wireless transceiver  306  and the request is responded to by wireless controller  305  by transmitting back the logged usage information. In a preferred embodiment a plurality of controllers such as controller  300  asynchronously collect usage information for their fixture and control computer  202 , via request or via periodic transmission of the information by the controllers, gathers the usage information for later use. 
     Wireless controller  306  may also be configured to handle situations or events such as transmission failures, reception failures, and the like. Wireless controller  306  may respond to such failures by, for example, operating according to a retransmission scheme or another transmit failure mitigation scheme. Wireless controller  306  may also control any other modulating, demodulating, coding, decoding, routing, or other activities of wireless transceiver  306 . For example, controller  300 &#39;s control logic (e.g., controlled by logic module  314  and/or control circuit  304 ) may periodically include making transmissions to other controllers in a zone, making transmissions to particular controllers, or otherwise. Such transmissions can be controlled by wireless controller  306  and such control may include, for example, maintaining a token-based transmission system, synchronizing clocks of the various RF transceivers or controllers, operating under a slot-based transmission/reception protocol, or otherwise. 
     Referring still to  FIG. 3 , sensor  112  may be an infrared sensor, an optical sensor, a camera, a temperature sensor, a photodiode, a carbon dioxide sensor, or any other sensor configured to sense environmental conditions such as a lighting level or human occupancy of a space. For example, in one exemplary embodiment, sensor  112  is a motion sensor and logic module  314  is configured to determine whether control circuit  304  should change states (e.g., change the state of power relays  302 ) based on whether motion is detected by sensor  112  (e.g., detected motion reaches or exceeds threshold value). In the same or other embodiments, logic module  314  may be configured to use the signal from the sensor  112  to determine an ambient lighting level. Logic module  314  may then determine whether to change states based on the ambient lighting level. For example, logic module  314  may use a condition such as time of day in addition to ambient lighting level to determine whether to turn the lighting fixture off or on. During a critical time of the day (e.g., when a staffed assembly line is moving), even if the ambient lighting level is high, logic module  314  may refrain from turning the lighting fixture off. In another embodiment, by way of further example, logic module  314  is configured to provide a command to control circuit  304  that is configured to cause control circuit  304  to turn the one or more lamps of the fluorescent lighting fixture on when logic module  314  detects motion via the signal from sensor  112  and when logic circuit  314  determines that the ambient lighting level is below a threshold setpoint. 
     Referring yet further to  FIG. 3 , control circuit  304  is configured to prevent damage to lamps  108  or  110  from manual or automatic control activities. Particularly, control circuit  304  may be configured to prevent on/off cycling of lamps  108 ,  110  by holding the lamps in an “on” state for a predefined period of time (e.g., thirty minutes, fifteen minutes, etc.) even after the condition that caused the lamp to turn on is no longer true. Accordingly, if, for example, a low ambient lighting level causes control circuit  304  to turn lamps  108 ,  110  on but then the ambient lighting level suddenly increases (the sun comes out), control circuit  304  may keep the lamps on (even though the on condition expired) for a predetermined period of time so that the lamps are taken through their preferred cycle. Similarly, control circuit  304  may be configured to hold the lamp in an “off” state for a predefined period of time since the lamp was last turned off to ensure that the lamp is given time to cool or otherwise settle after the last “on” state. 
     Referring yet further to  FIG. 3 , logic module  314  or control circuit  304  may be configured to include a restrike violation module (e.g., in memory  316 ) that is configured to prevent logic module  314  from commanding control circuit  304  to cause the fluorescent lamps to turn on while a restrike time is counted down. The restrike time may correspond with a maximum cool-down time for the lamp—allowing the lamp to experience its preferred strike-up cycle even if a command to turn the lamp back on is received at wireless transceiver  306 . In other embodiments, logic module  314  or control circuit  304  may be configured to prevent rapid on/off switching due to sensed motion, another environmental condition, or a sensor or controller error. The logic module  314  or the control circuit  304  may be configured to, for example, entirely discontinue the on/off switching based on inputs received from the sensor by analyzing the behavior of the sensor, the switching, and a logged usage information. By way of further example, the logic circuit  314  or the control circuit  304  may be configured to discontinue the on/off switching based on a determination that switching based on the inputs from the sensor has occurred too frequently (e.g., exceeding a threshold number of “on” switches within a predetermined amount of time, undesired switching based on the time of day or night, etc.). Logic module  314  or control circuit  304  may be configured to log or communicate such a determination. Using such configurations, logic module  314  and/or control circuit  304  are configured to self-diagnose and correct undesirable behavior that would otherwise continue occurring based on the default, user, or system-configured settings. 
     According to one embodiment, a self-diagnostic feature would monitor the number of times that a fixture or device was instructed to turn on (or off) based upon a signal received from a sensor (e.g. motion, ambient light level, etc.). If the number of instructions to turn on (or off) exceeded a predetermined limit during a predetermined time period, the logic module  314  and/or control circuit  304  could be programmed to detect that the particular application for the fixture or device is not well-suited to control by such a sensor (e.g. not an optimum application for motion control or ambient light-based control, etc.), and would be programmed to disable such a motion or ambient light based control scheme, and report/log this action and the basis. For example, if the algorithm is based on more than four instructions to turn on (or off) in a 24 hour period, and the number of instructions provided based on signals from the sensor exceeds this limit within this period, the particular sensor-based control function would be disabled, as not being optimally suited to the application and a notification would be logged and provided to a user or facility manager. Of course, the limit and time period may be any suitable number and duration intended to suit the operational characteristics of the fixture/device and the application. In the event that a particular sensor-based control scheme in a particular zone is disabled by the logic module and/or control circuit, the fixture or device is intended to remain operational in response to other available control schemes (e.g. other sensors, time-based, user input or demand, etc.). The data logged by the logic module and/or control circuit may also be used in a ‘learning capacity’ so that the controls may be more optimally tuned for the fixtures/devices in a particular application and/or zone. For example, the logic module and/or control circuit may determine that disablement of a particular sensor-based control feature occurred due to an excessive number of instructions to turn on (or off) based on signals from a particular sensor that occurred within a particular time window, and may be reprogrammed to establish an alternate monitoring duration that excludes this particular time window for the particular sensor-based control scheme to ‘avoid’ time periods that are determined to be problematic. This ability to learn or self-update is intended to permit the system to adjust itself to update the sensor-based control schemes to different time periods that are more optimally suited for such a control scheme, and to avoid time periods that are less optimum for such a particular sensor-based control scheme. 
     Referring now to  FIG. 4 , a more detailed block diagram of control computer  202  is shown, according to an exemplary embodiment. Control computer  202  may be configured as the “master controller” described in U.S. application Ser. No. 12/240,805, filed Sep. 29, 2008, and incorporated herein by reference in its entirety. Control computer  202  is generally configured to receive user inputs (e.g., via touchscreen display  210 ) and to set or change settings of lighting system  200  based on the user inputs. 
     Referring further to  FIG. 4 , control computer  202  is shown to include processing circuit  402  including memory  404  and processor  406 . In an exemplary embodiment, control computer  202  and more particularly processing circuit  402  are configured to run a Microsoft Windows Operating System (e.g., XP, Vista, etc.) and are configured to include a software suite configured to provide the features described herein. The software suite may include a variety of modules (e.g., modules  408 - 414 ) configured to complete various activities of control computer  202 . Modules  408 - 414  may be or include computer code, analog circuitry, one or more integrated circuits, or another collection of logic circuitry. In various exemplary embodiments, processor  406  may be a general purpose processor, a specific purpose processor, a programmable logic controller (PLC), a field programmable gate array, a combination thereof, or otherwise and configured to complete, cause the completion of, and/or facilitate the completion of the activities of control computer  202  described herein (e.g., as variously shown and described in and with references to  FIGS. 1-22 ). Memory  404  may be configured to store historical data received from lighting fixture controllers or other building devices, configuration information, schedule information, setting information, zone information, or other temporary or archived information. Memory  404  may also be configured to store computer code for execution by processor  406 . When executed, such computer code (e.g., stored in memory  404  or otherwise, script code, object code, etc.) configures processing circuit  402 , processor  406  or more generally control computer  202  for the activities described herein. 
     Touch screen display  210  and more particularly user interface module  408  are configured to allow and facilitate user interaction (e.g., input and output) with control computer  202 . It should be appreciated that in alternative embodiments of control computer  202 , the display associated with control computer  202  may not be a touch screen, may be separated from the casing housing the control computer, and/or may be distributed from the control computer and connected via a network connection (e.g., Internet connection, LAN connection, WAN connection, etc.). Further, it should be appreciated that control computer  202  may be connected to a mouse, keyboard, or any other input device or devices for providing user input to control computer  202 . Control computer is shown to include a communications interface  220  configured to connect to a wire associated with master transceiver  240 . 
     Communications interface  220  may be a proprietary circuit for communicating with master transceiver  240  via a proprietary communications protocol. In other embodiments, communications interface  220  may be configured to communicate with master transceiver  240  via a standard communications protocol. For example, communications interface  220  may include Ethernet communications electronics (e.g., an Ethernet card) and an appropriate port (e.g., an RJ45 port configured for CATS cabling) to which an Ethernet cable is run from control computer  202  to master transceiver  240 . Master transceiver  240  may be as described in U.S. application Ser. Nos. 12/240,805, 12/057,217, or 11/771,317 which are each incorporated herein by reference. As described in U.S. application Ser. No. 12/240,805, in general, the master transceiver  240  can communicate with other devices using a network protocol (WiFi network, Ethernet network, IP network, LAN, WAN, ZigBee network, Bluetooth Piconet, etc.). Communications interface  220  and more generally master transceiver  240  are controlled by logic of wireless interface module  412 . Wireless interface module  412  may include drivers, control software, configuration software, or other logic configured to facilitate communications activities of control computer  202  with lighting fixture controllers. For example, wireless interface module  412  may package, address format, or otherwise prepare messages for transmission to and reception by particular controllers or zones. Wireless interface module  412  may also interpret, route, decode, or otherwise handle communications received at master transceiver  240  and communications interface  220 . 
     Referring still to  FIG. 4 , user interface module  408  may include the software and other resources for the display of  FIGS. 8-22  and the handling of automatic or user inputs received at the graphical user interfaces of control computer  202 . While user interface module  408  is executing and receiving user input, user interface module  408  may interpret user input and cause various other modules, algorithms, routines, or sub-processes to be called, initiated, or otherwise affected. For example, control logic module  414  and/or a plurality of control sub-processes thereof may be called by user interface module  408  upon receiving certain user input events. User interface module  408  may also be configured to include server software (e.g., web server software, remote desktop software, etc.) configured to allow remote access to the screens shown in  FIGS. 8-22 . User interface module  408  may be configured to complete some of the control activities described herein rather than control logic module  414 . In other embodiments, user interface module  408  merely drives the graphical user interfaces and handles user input/output events while control logic module  414  controls the majority of the actual control logic. 
     Control logic module  414  may be the primary logic module for control computer  202  and may be the main routine that calls, for example, modules  408 ,  410 , etc. Control logic module  414  may generally be configured to provide lighting control, energy savings calculations, demand/response-based control, load shedding, load submetering, HVAC control, building automation control, workstation control, advertisement control, power strip control, “sleep mode” control, or any other types of control. In an exemplary embodiment, control logic module  414  operates based off of information stored in one or more databases of control computer  202  and stored in memory  404  or another memory device in communication with control computer  202 . The database may be populated with information based on user input received at graphical user interfaces (e.g., shown in  FIGS. 8-22 ) and control logic module  414  may continuously draw on the database information to make control decisions. For example, a user may establish any number of zones, set schedules for each zone, create ambient lighting parameters for each zone or fixture, etc. This information is stored in the database, related (e.g., via a relational database scheme, XML sets for zones or fixtures, or otherwise) and recalled by control logic module  414  as control logic module  414  proceeds through its various control algorithms. 
     Control logic module  414  may include any number of functions or sub-processes. For example, a scheduling sub-process of control logic module  414  may check at regular intervals to determine if an event is scheduled to take place. When events are determined to take place, the scheduling sub-process or another routine of control logic module  414  may call or otherwise use another module or routine to initiate the event. For example, if the schedule indicates that a zone should be turned off at 5:00 pm, then when 5:00 pm arrives the scheduling sub-process may call a routine (e.g., of wireless interface module) that causes an “off” signal to be transmitted by master transceiver  240 . Control logic module  414  may also be configured to conduct or facilitate the completion of any other process, sub-process, or process steps conducted by control computer  202  described herein. 
     Referring further to  FIG. 4 , device interface module  410  facilitates the connection of one or more field devices, sensors, or other inputs not associated with master transceiver  240 . For example, fieldbus interfaces  416  and  420  may be configured to communicate with any number of monitored devices  418  and  422 . The communication may be according to a communications protocol which may be standard or proprietary and/or serial or parallel. Fieldbus interfaces  416 ,  420  can be or include circuit cards for connection to processing circuit  402 , jacks or terminals for physically receiving connectors from wires coupling monitored devices  418 ,  422 , logic circuitry or software for translating communications between processing circuit  402  and monitored devices  418 ,  422 , or otherwise. In an exemplary embodiment, device interface module  410  handles and interprets data input from the monitored devices and controls the output activities of fieldbus interfaces  416 ,  420  to monitored devices  418 ,  422 . 
     Fieldbus interfaces  416  and  420  and device interface module  410  may also be used in concert with user interface module  408  and control logic module  414  to provide control to the monitored devices  418 ,  422 . For example, monitored devices  418 ,  422  may be mechanical devices configured to operate a motor, one or more electronic valves, one or more workstations, machinery stations, a solenoid or valve, or otherwise. Such devices may be assigned to zones similar to the lighting fixtures described above and below or controlled independently. User interface module  408  may allow schedules and conditions to be established for each of devices  418 ,  422  so that control computer  202  may be used as a comprehensive energy management system for a facility. For example, a motor that controls the movement of a spinning advertisement may be coupled to the power output or relays of a controller very similar if not identical to controller  300 . This controller may be assigned to a zone (e.g., via user interfaces at touchscreen display  210 ) and provided a schedule for turning on and off during the day. In another embodiment, the electrical relays of the controller may be coupled to other building devices such as video monitors for informational display, exterior signs, task lighting, audio systems, or other electrically operated devices. 
     Referring further to  FIG. 4 , power monitor  450  is shown as coupled to fieldbus interfaces  416  in an exemplary embodiment. However, power monitor  450  may also or alternatively be coupled to its own controller or RF transceiver  451  for communicating with master transceiver  240 . Power monitor  450  may generally be configured to couple to building power resources (e.g., building mains input, building power meter, etc.) and to receive or calculate an indication of power utilized by the building or a portion of the building. This input may be received in a variety of different ways according to varying embodiments. For example, power monitor  450  may include a current transformer (CT) configured to measure the current in the mains inlet to a building, may be coupled to or include a pulse monitor, may be configured to monitor voltage, or may monitor power in other ways. Power monitor  450  is intended to provide “real time” or “near real time” monitoring of power and to provide the result of such monitoring to control computer  202  for use or reporting. When used with power monitor  450 , control logic module  414  may be configured to include logic that sheds loads (e.g., sends off signals to lighting fixtures via a lighting fixture controller network, sends off signals to monitored devices  418 ,  422 , adjusts ambient light setpoints, adjusts schedules, shuts lights off according to a priority tier, etc.) to maintain a setpoint power meter level or threshold. In other exemplary embodiments, control logic module  414  may store or receive pricing information from a utility and shed loads if the metered power usage multiplied by the pricing rate is greater than certain absolute thresholds or tiered thresholds. For example, if daily energy cost is expected to exceed $500 for a building, control logic module  406  may be configured to change the ambient light setpoints for the lighting fixtures in the building until daily energy cost is expected to fall beneath $500. In an exemplary embodiment, user interface module  408  is configured to cause a screen to be displayed that allows a user to associate different zones or lighting fixtures with different demand/response priority levels. Accordingly, a utility provider or internal calculation determines that a load should be shed, control logic module  414  will check the zone or lighting fixture database to shed loads of the lowest priority first while leaving higher priority loads unaffected. 
     Referring now to  FIG. 5A , a flow chart of a process  500  for controller  300  is shown, according to an exemplary embodiment. Process  500  is shown to include receiving a signal from an environment sensor at control circuitry (e.g., sensor circuit  310 , control circuit  304 ) (step  501 ). Process  500  further includes using the control circuitry to determine whether the lighting fixture should change states (step  502 ). Controller  300  is configured to log usage information for the lighting fixture when states are changed (step  503 ). As mentioned above, logging usage information may include tracking an aggregate “time on” for each ballast or lamp set of the lighting fixture. When a lamp or lamp set is replaced, controller  300  or control computer  202  may allow a user to “reset” logged usage information in whole or in part so that the logged usage information may be used for lamp maintenance prediction. For example, when controller  300  reports usage information to control computer  202 , control logic module  414  of the control computer may examine the received usage information to determine whether a lamp or lamp set is near the end of its normal usage life. If a lamp or lamp set is determined to be at the end of its normal usage life, control logic module  414  may command user interface module  408  to cause a warning or other message or report to be displayed via touchscreen display  210 . 
     Referring still to  FIG. 5A , process  500  is further shown to include transmitting the logged usage information (step  504 ). Controller  300  may be configured to transmit the logged usage information back to control computer  202  for processing, archival, or action. In other embodiments, where the logged usage information includes an indication of an event (e.g., a message indicating “I have turned off due to adequate ambient light”), controller  300  may transmit the logged usage information for use by other controllers in its zone. Controller  300  may also be configured to receive a command from a remote device (e.g., control computer  200 , another lighting fixture controller, a wireless router, etc.) (step  505 ) and to cause one or more lamps (e.g., lamp sets, ballasts, etc.) of the lighting fixture to turn on or off based on the received commands (step  506 ). 
     Referring now to  FIG. 5B , a flow chart of a process  510  for control computer  202  is shown, according to an exemplary embodiment. Process  510  is shown to include receiving a submetered power level (e.g., in the form of a data message) from a power monitoring device (e.g., power monitor  450 ) or devices (e.g., distributed metering devices) (step  511 ). Process  500  may further include receiving logged usage information from the lighting network (e.g., usage information logged as described above with respect to controller  300  or process  500 ) (step  512 ) and calculating the power level or power usage for the lighting network using the received usage information (step  513 ). Control computer  202  may be configured to output the calculated or received power level or usage information (e.g., via a display, via a website, via a report) or control computer  202  may be configured to take one or more actions based on the usage. For example, step  508  may include comparing the metered or calculated power level to a threshold, tiers of a tier-based system, pricing structure, budget information, or requested values from the power supplier (step  514 ). Based on the comparison, control computer  202  may determine and execute a control strategy for shedding loads (step  515 ). Various control strategies for shedding loads or demand-based control strategies are described in U.S. application Ser. No. 12/240,805, the entirety of which is incorporated by reference. In an exemplary demand-based control scheme, the master controller  202  monitors and controls the designated lighting fixtures within the facility based on signals received from various sensors. Each sensor is operable to monitor any one or more of a wide variety of parameters associated within a predefined interior space (e.g. designated environment, room, etc.) within the facility, such as but not limited to, ambient light level, motion, temperature, sound, etc., and provide a sensor output signal associated with the parameter to the master controller  202 . Alternatively, a switch (e.g. pushbutton, etc.) may be provided so that a user can manually initiate an output signal. 
     Referring now to  FIG. 6 , an exemplary control activity for a system of controllers as described herein is illustrated, according to an exemplary embodiment. As described in  FIG. 2B , lighting fixtures (or more particularly controllers for lighting fixtures) can be grouped into zones. Rather than reporting motion, ambient light, or other sensed conditions back to master controller  202  for processing or action, controllers such as controller  300  may be configured to broadcast commands or conditions to other RF transceivers coupled to other controllers in the same zone. For example, in  FIG. 6 , lighting zone I includes four controllers. When motion is detected by sensor  112  of controller  300 , logic module  314  and/or control circuit  304  causes wireless transceiver  306  to transmit an indication that motion was detected by the sensor. Accordingly, control circuits of the controllers receiving the indication can decide whether or not to act upon the indication of motion. The RF signals including an indication of motion may also include a zone identifier that receiving controllers can use to determine if the signal originated from their zone or another zone. In other exemplary embodiments, controller  300  may address messages to particular controllers (e.g., the addresses of neighbors or the addresses of other controllers in the zone). Logic module  314  may further be configured to cause the radio frequency transceiver to transmit commands to other radio frequency transceivers coupled to other fluorescent lighting fixtures. For example, logic module  314  and/or control circuit  304  may be configured to interpret a signal received at the radio frequency transceiver as indicating that motion was detected by another device in the zone. In an exemplary embodiment of the lighting fixture controller, some will be configurable as relay devices and when so configured, will relay any commands or information the controller receives from other zone controllers. Controller  604  is illustrated to be configured as such a relay device. When controller  604  receives broadcast  600  indicating motion from controller  300 , controller  604  relays broadcast  600  via transmission  602  to other zone devices (e.g., controller  606 ). This way, an event such as motion can be propagated to each of the lighting fixtures in a zone without network traffic to main controller  240  and/or without necessitating direct control of the lighting fixtures by main controller  240 . This activity may be configurable (e.g., via a GUI provided by control computer  202 ) so that only some controllers are relays, all controllers are relays, or so that no controllers are relays and only devices within range of the detecting controller act on its broadcasts. Further, the relay or rebroadcast can be address-based or more similar to a true broadcast. For example, in an address-based relay, the controller serving as a relay may know the addresses of certain network controllers to which to transmit the relayed information. In another example, the broadcast may be general and not addressed to any particular controller, controllers, or zone. 
     To implement zone control activities, each controller may be configured to store a lighting zone value in memory (e.g., memory  316 ). This value may be used, for example, to determine whether another device sending a command is associated with the lighting zone value stored in memory. For example, controller  271  may include a lighting zone value of “II” in memory and controller  300  may include data representative of controller  300 &#39;s lighting zone value (e.g., “I”) with its transmission indicating that motion was detected. When controller  271  receives the lighting zone value, controller  271  (e.g., a control circuit or logic circuit thereof) may compare “I” and “II” and make a determination that controller  271  will not act on the received indication of motion (i.e., controller  271  leaves its relays off while all of the controllers in zone I switch their relays on. 
     Referring now to  FIG. 7 , a flow chart of a process  700  for controlling multiple lighting fixtures in a zone based on sensor input is shown, according to an exemplary embodiment. Process  700  is shown to include receiving signals from a sensor (e.g., sensor  212 ) coupled to a first controller for a first zone (step  702 ). Once received, circuitry of the first controller can determine whether the received signals represent an event that should be acted upon (e.g., by changing lighting states, etc.) in the first zone (step  704 ). Process  700  is further shown to include using circuitry of the first controller to transmit a command and/or an indication of the event with a first zone identifier (step  706 ). The transmission is received by a controller in a second zone. Circuitry of the controller in the second zone determines that the transmission is for another zone and does not act on the received transmission (step  708 ). The transmission may also be received by a second controller for the first zone (step  710 ). Circuitry of the second controller for the first zone inspects the received transmission and acts on the information of the transmission when the controller discovers that its stored zone identifier matches the received zone identifier (step  712 ). The second controller for the first zone may also be configured as a relay node and to retransmit the received command or indication to other first zone controllers (e.g., controller  606 ). 
     Control Configurations and Related Graphical User Interfaces of the Control Computer 
     Referring now to  FIGS. 8-22 , a variety of graphical user interfaces (GUIs) that may be shown on an electronic display in communication with control computer  202  are shown, according to various exemplary embodiments. 
       FIG. 8  is an illustration of a login screen that may be provided to a display screen such as touchscreen display  210  by control computer  202 , according to an exemplary embodiment. It should be appreciated that trademarks, markings, or information other than Orion and InteLite II may be shown on the login screen. By clicking on the login button, a user may be prompted for a password, username, or other credentials that the system checks to log the user into control computer  202 . 
       FIG. 9  is an illustration of a main menu screen  900  that may be provided to a display by control computer  202 , according to an exemplary embodiment. At main menu screen  900 , control computer  202  causes the screen to display buttons (which could be other UI elements such as hyperlinks) for launching a lighting layout (button  902 ) mode, launching an emissions offset calculator (button  904 ), and entering a setting mode (button  906 ). Main menu screen  900  can also include an override utility  910  including, for example, an all rights on button  911  and an all lights off button  912 . Lighting layout modes or features are described in subsequent Figures (e.g.,  FIG. 10 ). The emissions offset calculator launched by button  904  may provide a screen or report that compares the power usage of the current lighting system compared to conventional or historical lighting systems. The power usage of the current lighting system may be calculated based on usage information from lighting fixture controllers or based on power meter readings from, for example, power monitor  450  shown in  FIG. 4 . The emissions offset calculator screen can show the results of aggregations or calculations that equate the power savings to cost savings, an equivalent amount of carbon credits, an equivalent emissions value, or another environmental values that quantifies the reduced financial and/or environmental impact due to the improved lighting system and/or control strategies at work in a facility when one or more of the features contained herein are implemented. 
       FIG. 10  is an illustration of a lighting layout or lighting zones screen  1000  that may be provided to a display by control computer  202  when button  902  of  FIG. 9  is selected, according to an exemplary embodiment. Screen  1000  is shown to include a map (e.g., grid, layout, floor plan) including boundaries defining a plurality of lighting zones (labeled in screen  1000  as L Zone  10 , L Zone  20 , L Zone  30 , and L Zone  40 ). In screen  1000 , each zone is shown to include a zone identifier  1002  and a lighting fixture icon  1004 . The lighting fixture icon  1004  can be located at a coordinate on the map corresponding to the actual geolocation for the lighting fixture. More than one lighting fixture icon  1004  may be associated with each zone and in some instances many (10+) lighting fixtures may be associated with any given zone depending on the application (e.g., warehousing, construction site, etc.). The left side of screen  1000  is shown to include GUI tools  1006  and  1008  for allowing a user to navigate around the map, lighting zones, and fixtures. For example, GUI tool  1006  allows for a user to click in a plurality of directions so that the map moves relative to the viewable window of screen  1000 . GUI tool  1008  allows for a user to click in order to zoom in or zoom out. Further, a “home” button allows a user to return to a home screen or home view. 
       FIG. 11  is an illustration of lighting zones screen  1000  from  FIG. 10 , but including a lighting zone dialog box  1102  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Dialog box  1102  is displayed to a user when, for example, lighting fixture icon  1004  associated with a particular lighting zone is clicked or otherwise selected. Dialog box  1102  includes a current status indicator  1104  as well as controls  1106 ,  1108 , and  1110  for changing the status of the lighting fixture. For example, current status indicator  1104  is illustrated to indicate that zone  10 &#39;s lighting fixture is “all on.” On a computer screen, this may be indicated by yellow lamps in the illustration of the lighting fixture rather than black lamps. In other embodiments, “on” may be indicated by a glow on top of the lighting fixture, a glow coming from behind the lighting fixture, an “ON” icon, text indicating the status (e.g., similar to that shown in controls  1106 - 1110 , etc.), or otherwise. To change the status of the lighting fixture from “all on” to “all off” or “half on”, the user can click control  1106  or  1108 . With reference to previous Figures, when such a selection is made, control computer  202  may recognize the selection and cause a command for the appropriate lighting fixture controller (e.g., controller  300 ) to be broadcast from master transceiver  240  via RF communications. Making such a selection may place the lighting fixture into a manual mode of operation permanently or temporarily. In an exemplary embodiment, control computer  202  tracks and controls the mode of operation for each lighting fixture and/or each zone. If a zone is configured for other than manual operation and dialog box  1102  is used to change the state of a lighting fixture in the zone, the lighting fixture may maintain the user selected state for some period of time before returning to the state commanded by the mode of operation programmed to control the zone. For example, a zone may be configured to turn on or off according to a schedule which may be set or adjusted by clicking on button  1114 . Control computer  202  may be configured to turn on or off based on ambient light sensed by, e.g., sensor  112  shown in previous Figures. Ambient lighting settings for the zone may be set or adjusted by clicking button  1116  on dialog box  1102 . Closing the dialog box via button  1118  may cause computer  202  to save settings or changes made to the lighting zone. If manual mode button  1112  is clicked, control computer  202  may disable the schedule-based control, ambient lighting control, or other logic controls and cause the lighting zone to be controlled manually. Clicking manual mode  1112  may cause the lighting zone to be in a manual mode for the remainder of the day, for some longer or shorter period of time, or permanently (until again changed). 
       FIG. 12  is an illustration of a scheduling screen  1200  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Screen  1200  may be displayed, for example, when schedule button  1114  is selected from dialog box  1102 . A slider control (or other GUI control) may be provided for each day of the week, allowing a user to select a period of time during any day of the week when the lights in a zone should be turned on and one or more periods of the day when the lights in a zone should be turned off. For example, in the illustration shown in  FIG. 12 , the lights for a zone are scheduled to be off all day on Sunday and Saturday while they are Scheduled to be on (indicating by the shading) during varying working hours during the week. Once a schedule is set for a zone, control computer  202  may send appropriate command signals to the lighting fixtures in the zone to cause the lighting fixtures in the zone to turn on or off according to the schedule. 
       FIG. 13  is an illustration of a lighting zone ambient light setting screen  1300  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Screen  1300  may be displayed, for example, when button  1116  of dialog box  1102  is clicked. Screen  1300  is shown to include three slider controls (although in various exemplary embodiments, other types of controls may be used for level setting/selection)  1302 ,  1304 , and  1308 . Slider  1302  may be used to set an ambient lighting level for a first ballast (e.g., ballast  104  shown in  FIG. 2A ) of lighting fixtures in a zone, while slider  1304  may be used to set an ambient lighting level for a second ballast (e.g., ballast  106  shown in  FIG. 2A ) of the lighting fixtures in the zone. Control computer  202  may be configured to turn a ballast on or off depending on the current ambient reading for a fixture or zone relative to the set points selected via sliders  1302 ,  1304 . For example,  FIG. 13  illustrates that for the zone affected by screen  1300 , ballast  1  requires a sixty percent or greater ambient light reading before control computer  202  will cause ballast  1  to turn off. On the other hand, ballast  2  only requires a fifteen percent or greater ambient light reading before control computer  202  will cause ballast  2  to turn off Accordingly, three different levels of lighting (and energy use) may be set up via sliders  1302 ,  1304 . That is: when ambient light levels are below fifteen percent, both ballasts will be controlled to be on; when ambient light levels are at or above fifteen percent but below sixty percent, only ballast  1  will be on; when ambient light levels are at or above sixty percent, both ballasts will be off and the space will be lit by natural light (e.g., coming through windows). Dead band slider  1308  may allow a user to adjust the responsiveness of the system by creating one or more dead band percentage points that a system may be able to stay within before causing the system to change states. That is, on a cloudy day where the ambient lighting level is fluctuating around fifteen percent, a dead band percentage of a few points may prevent the lighting fixtures from being commanded to oscillate. A user may track current ambient reading levels via display element  1306  and use the current level to assist in slider  1302 ,  1304  selections. Using screen  1300  for any given building zone, a user may be able to find an acceptable balance of artificial and natural light that will result in significant energy cost savings relative to an “all on” or ambient light independent control system while meeting illumination requirements for a space (e.g., foot-candle requirements). Screen  1300  may also advantageously provide a user with the ability to provide a greater number of light intensity “steps” within a building which may advantageously improve occupant comfort. These settings may be compiled by controller  202  for zones, lighting fixtures within zones, or individual lighting fixtures and transmitted to the controllers for incorporation into the controllers&#39; memory and/or control algorithms. 
       FIG. 14  is an illustration of a lighting zones detail screen  1400  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Lighting zones detail screen may be obtained by “zooming in” using controls  1008 . Particularly, once zoomed in, a user may be provided an icon such as icon  1402  for each lighting fixture (rather than a single fixture icon representing the lights within a zone, as may be provided when “zoomed out” in some embodiments). Further an alpha-numerical identifier (or other identifier) for each lighting controller may be shown with each lighting fixture icon so that a manager of the building space can better identify each lighting fixture in the building or zone. For example, zone  1420  is shown to include at least three different lighting fixture controllers indicated by three different icons. Each lighting fixture icon (e.g., icon  1402 ) may be shaded a different color to indicate current status (e.g., all on, off, partially on, etc.). In other embodiments each lighting fixture icon may be shaded or otherwise identify the control setting for the lighting fixture (e.g., motion-based, ambient-light based, schedule-based control, demand-based control, manual control, automatic control, etc.). In some embodiments, each lighting fixture icon (e.g., icon  1402 ) is clickable or otherwise selectable such that a dialog box  1502  shown in screen  1500  of  FIG. 15  is caused to be displayed by control computer  202 . Dialog box  1502  is shown to identify the device and to include similar manual control options (e.g., all off, half on, all on) as shown above when controlling the entire zone. Button  1504  is shown as a “Confirm Status” button that, when pressed, causes control computer  202  to change the state of the particular device relating to dialog box  1502 . Using this feature, a building manager can confirm that they are changing settings or otherwise correctly identifying the correct device. 
       FIG. 16  is an illustration of an application settings screen  1600  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Screen  1600  is shown to include a default schedule button  1602 , a default ambient light setting button  1604 , a facility setting button  1606 , a rezone layout button  1608 , and a lighting zone setting button  1610 . Default schedule button  1602  may cause a screen to be displayed that is similar to screen  1200  shown in  FIG. 12 . Entries made to the default schedule may serve as the base for zone or fixture specific edits. Default ambient light setting button  1604  may cause a screen to be displayed that is similar to screen  1300  shown in  FIG. 13 , however, rather than being applicable for one zone or lighting fixture, the screen triggered by default ambient light setting button  1604  may be applicable for all zones controlled by control computer  202 . Facility setting button  1606  may be used to set any number of global variables that may affect the entire facility (e.g., whether to respond to demand-based control requests received from power providers, how frequently to poll controllers for logged usage information, etc.). 
       FIG. 17  is an illustration of a change settings screen  1700  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Screen  1700  may be shown to a user when button  1608  is clicked. Screen  1700  may generally be used to change zone boundaries, to move lighting fixture icons from zone to zone, to remove lighting fixtures from a zone, or otherwise. Zone boundaries may be edited by, for example, dragging boundaries such as boundary  1702  on a displayed grid. Lighting fixtures may be moved by, for example, clicking and dragging a lighting fixture. A dialog box may be used to reassign a lighting fixture to a different zone when a lighting fixture icon (e.g., icon  1704 ) is clicked or otherwise selected. For example, in dialog box  1800  shown in  FIG. 18 , device  17958  associated with icon  1704  is being reassigned to lighting zone  30  (i.e., the L Zone ID stored in device  17958  will change to 30 once “Save Settings” is pressed). 
       FIG. 19  is an illustration of a lighting zone setting screen  1900  may be provided to a display by control computer  202 , according to an exemplary embodiment. When a user selects a zone for changing the settings of (e.g., by clicking an the lighting fixture icon associated with the zone, by clicking the zone title, etc.), screen  2000  shown in  FIG. 20  may be displayed. For example, in screen  2000 , a user has selected L Zone  30  as the zone to edit. The identifier for the zone (i.e., L Zone Name) may be changed via text box  2004 , the default schedule for the zone may be changed via schedule button  2006 , the ambient lighting settings for the zone may be changed via button  2008 , and an ambient sensor id may be set via box  2010 . Changes to the lighting zone may be saved via button  2012 . Whether the zone is generally in automatic mode or manual mode may be changed via button  2002 . In some embodiments only one ambient sensor may be used to provide ambient light readings to an entire zone. In such instances, an entire zone may be assigned to an identifier of the chosen ambient sensor. This assignment or relationship information may be propagated out to the individual controllers and/or stored in a database of memory  404  and acted on by control computer  202 . In instances where a zone includes devices other than lighting fixtures coupled to wireless controllers, associating a sensor with such a zone will cause control computer  202  to communicate to the controller for the sensor that the sensor readings should be communicated back to the master controller rather than merely acted upon locally (e.g., controller to controller). When control computer  202  receives sensor readings from a zone sensor, control computer (e.g., the control logic module thereof) sends commands appropriate for the sensor readings to the other devices. 
       FIG. 21  is an illustration of an automatic mode screen  2100  including automatic mode dialog box  2104  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Automatic mode dialog box  2104  may be caused to be displayed by control computer  202  upon a user clicking an “auto mode” button such as button  2102 . Automatic mode may cause all of the lights to use their motion, ambient light, or schedule-based controls rather than rely on manual actuation. Automatic mode may be utilized unless a fixture or zone is “brought out” of manual mode by user command. 
       FIG. 22  is an illustration of an override mode screen  2200  including override mode dialog box  2204  that may be provided to a display by control computer  202 , according to an exemplary embodiment. Override mode dialog box  2204  may be caused to be displayed by control computer  202  upon a user clicking an “all lights on” button such as button  2202 . Override or manual mode may cause the lighting fixture controllers and control computer  202  to temporarily or permanently ignore other control scheme settings such as motion control, schedule control, and the like. Override mode may be on a timer, expire at the end of the day, or may be permanent until the user selects one or more automatic mode features for lighting fixtures or zones of the system. 
     Various Exemplary Embodiments 
     It should be noted that the screens shown in  FIGS. 8-22  are exemplary only and may vary depending on the control computer, intended display device, user preference, or otherwise. One or more functions may be combined onto a few number of screens or expanded onto a greater number of screens. Aspects shown and described as being within dialog boxes may be options or controls shown on main screens, “next” screens in a sequence of screens, or otherwise. Items referred to as buttons may be any clickable, selectable, or otherwise interactive controls for facilitating the user interface features described. In yet other embodiments audio (e.g., via speakers integrated with control computer  202 , via an external audio system coupled to control computer  202 , etc.) may be used for prompting the user for input and/or for receiving input from a user (e.g., via a microphone and voice recognition circuit/module). Further, other user input mechanisms of the past, present or future may be provided to the systems described above to provide the features discussed throughout the present application or with particular reference to  FIGS. 8-22 . 
     Further, the construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure. 
     The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. 
     Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions. 
     Although the figures may show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.