User Manual Light Control Module
- User Manual for LCM Craig Klem August 2009 Introduction This document provides the user with knowledge of the Intu! Light Control Module function, operation and installation. Objectives To describe the function of the Intu! Light Control Module. To describe the operation of the Intu! Light Control Module. To describe the installation of the Intu! Light Control Module. Document History Date 14-Mar-08 17-Aug-09 Author Craig Klem Craig Klem Version 1.00 1.20 Change Justification First Release Updated with Gen 2 info 1 Block Diagram Public Server Functional Description Lighting Control Module Input power from 120/ 277 Installed a maximum of 150 from the nearest ballast controller. Powered continually. No battery operation. Control up to 3 ballasts. Maximum continuous current draw of 100mA. LEDs to indicate its status. Controller will not include switches. Operation and configuration will be accomplished with Zigbee messages. Certified Zigbee and Zigbee Pro mesh stack Zigbee router operation. Messages will be routed to other Light Control Modules Respond to Zigbee messages to turn on its ballast(s). Support over the air boot-loading for SW field upgrades. Diagnostic port for RS232 type messages. There will be two types of ballast controllers: basic controllers and advanced controllers. 2 A basic ballast controller will have all the features listed above and allow for an interface to external occupancy and ambient light sensors. GEN1 design An advanced ballast controller will have all the features listed above plus integrated occupancy and ambient light sensors. GEN2 design The occupancy sensor will detect will someone is present and turn on its ballast(s) and send messages to other ballast controllers to turn on their ballast(s). The light sensor will detect the amount of ambient light and control how many ballasts it turns off as well as send messages to other ballast controllers telling them how many ballasts to turn off. Slot Antenna design integrated into fixture 1 year warranty Temperature range 0C to 85C UL approval mark No user switches. Light nodes will be enabled for network creation within a limited time after power is applied to the light fixture. Operation - Events Description OVERVIEW There are three different event types:
Scheduled: events that are active during a specified time period. These events can be recurring; for example, every weekday between 8 am and 5 pm. Manual: events that are triggered by an external event, for instance a key press on the TouchScreen device. The definition of each Manual event includes a default duration timer (in minutes). When a manual event activate request is received by the gateway, the light group command(s) will be executed. When the timer has elapsed, the light group(s) controlled by the event will be turned off. More detail covering the specifics of manual events follows below. Reactive: events that are triggered by sensor activation. Some light nodes may contain ambient light and/or occupancy sensors, and the reactive events define what is to occur when these sensors change state. SCHEDULEDTYPES Scheduled events contain a start and end date (mm/dd/yyyy) that specifies the range of dates in which the event is active. There are seven types of scheduled events:
Single Run: Specified by a start date/time, and an end date/time, this event is active during that entire timeframe, even if it spans multiple days. Once the end time has been reached, the event will never be active again. 3 Daily: This is used for events that occur on a daily basis, starting and ending at the specified time on the day(s) that it is active. The daily event may be defined to occur every other day, every third day, etc. Weekly: Like daily events, except that period is weeks rather than days. The weekly event may be defined to occur bi-weekly, every three weeks, etc. Additionally, the event can specify which day(s) of the week the event is active. Typically, this type of event would be used to schedule an event that occurs (for instance) every week:
Monday Friday, 8 am through 5 pm. Monthly Numbered: This type is used to define an event that occurs on a specific day of the month. The event may also define monthly, bi-monthly, etc. Monthly Relative: The monthly relative event allows users to specify schedules such as the second Tuesday of month. As with other events, the recurrence may be defined as every other month, every third month, etc. Similar to the weekly type, the event can define which day(s) of the week are active, and indicates the week of the month. Another example of an event that may be defined by this type: the third Monday, Wednesday, and Friday of every fourth month. Yearly Numbered: An event that occurs on a specific day of a specific month, e.g. December 25. The event specifies the month and the day. As with all other scheduled event types, this event can span multiple years. Yearly Relative: Yearly relative implement events such as the second Tuesday of March. The recurrence may be define the month, the day(s) of the week, and the week of the month. Another example: the first Tuesday and Wednesday of May. EVENTSUSPENSION Events are continuously processed by the gateway which operates one or more group of lights. If groups of lights are being controlled manually by a group trigger command, it is quite possible that normal event processing will change the dim level of the groups. Suspension of event processing can be used to override this behavior. Suspending the event processing effectively stops ALL events from being processed, and allows complete manual control of the lights. Installation Operation All light fixtures are installed in the facility including those equipped with the light control module (LCM). Fixtures can be installed in any location within the specification limits. Gateway and TouchScreen are installed near the wireless network of LCMs. The TouchScreen must be within 3ft of the gateway. The installation laptop is connected to public server using an internet browser and a WiFi or WAN connection. 4 The technical support GUI will have a network installation screen for users logged on with this level of access. Installer will issue a Create Network command from the technical support GUI. The Gateway will establish a Zigbee network and be ready to allow nodes to join the network. Installer will initiate the discovery process. (ex: click Start Discovery). The gateway will continuously allow LCMs to join the network and report them to the technical support GUI. Power up or cycle power to a circuit of light fixtures by turning on a circuit breaker. Light control modules will automatically attempt to join the network when powered up. If they fail, they will try again every 10 seconds for up to 15 minutes. LCMs that join the network will show up on the Web GUI as a newly discovered MAC ID. When the installer selects a discovered MAC ID, the light will begin to flash at a 10 second cycle. The installer will map the MAC ID, sensor type and fixture type to the correct location on the Web GUI layout drawing. Installer will then select the next MAC ID in the discovered list. This light will begin to flash and the previous light will stop flashing and remain on. Installer will continue until all MAC IDs are mapped. Power up the next circuit of lights and repeat the mapping procedure. After all the nodes have been joined to the network, the installer will close the network. (ex: click Stop Discovery). Installer will confirm all lights are mapped correctly by selecting a light icon on the layout drawing and confirm the correct light is flashing. A Next button allows the installer to quickly cycle through all lights. After all lights have been confirmed to be mapped correctly, the installer will group lights and confirm group operation is correct. Manual events are defined and downloaded to the gateway. The gateway will automatically update the TouchScreen with the manual event names. Installer will test that manual events operate from the TouchScreen. Reactive events are defined and downloaded to the gateway. Installer will test that the occupancy sensor or ambient light sensor works correctly. Installation is complete. 5 6