Technical Instruction The LxOEM lighting controller is designed to be configured in several ways. As a programmable controller, it can be fully programmed and configured at the ligthing panel manufacturing factory with EIKON LOGICBUILDER. This method works best when all configuration variables are known in advance. As a BACnet Protocol Revision v9.0 controller, the LxOEM supports BACnet configuration, backup and restore with third party tools. The capabilities and ease of use of these tools varies significantly. Depending upon the capabilities of the selected tool a technician can: Change parameters and BACnet discoverable properties, objects: input type, group assignments, relays, etc. Commission and start-up equipment Adjust set points and other control parameters View current trends stored in the controller Set and change schedules in the controller (if programmed with a schedule) BACnet backup and restore Again, the capabilities of these tools varies greatly and OEMCtrl will not take support requests on configuration of the LxOEM with third party tools. Document Purpose The purpose of this document is to demonstrate how to configure and commission a LxOEM controller using the OEMCtrl Field Assistant tool. With Field Assistant and a permission key issued by the manufacturer (when necessary) a technician can: Upload parameters from the controller to Field Assistant Commission and start-up lighting panels Adjust set points and other control parameters View current trends stored in the controller Set and change schedules in the controller Configure control areas by associating switches and relays in groups Run preconfigured reports which display locked values, points list, network I/O, alarm sources, equipment and controller status, and test and balance configurations Download programs, schedules, parameters to controllers Export updated source files - Save configuration parameters Terms to Know To use Field Assistant effectively, you must understand these terms: Source Files Parameters Import Export Download Upload Includes any or all of the following files: Control programs (.equipment) Graphics (.view) BACview files (.bacview) Drivers (.driver) Editable BACnet properties within a control program or driver Brings files into Field Assistant. Import source files (sourcefiles.zip) from the Field Assistant Launcher. NOTE Your manufacturer or representative must supply the source files. Takes source files from your Field Assistant system to use in another system. Export source files (sourcefiles.zip) from the Field Assistant Launcher. Field Assistant sends source files, schedules, or parameters from Field Assistant to the controller. Field Assistant receives source files or parameters from the controller and stores them in Field Assistant. High Level Process Overview Purchase Field Assistant tool with associated local access cable Install Field Assistant tool with license Get Permission Key and driver from lighting control panel manufacturer Discover and Configure Save / Backup changes 1025 Cobb Place Boulevard. Kennesaw, GA 30144. (770) 429.3060. Fax (770) 429.3061.
ON 1 2 3 4 5 6 7 8 The programming tools supplied to the panel manufactures allows them to apply a permissions framework to the LxOEM lighting controller. Applying this security framework is entirely at the discretion of the manufacturer. If the manufacturer has not applied a security framework, no permission key will be necessary. To purchase Field Assistant and the USB local access cable, contact your lighting panel supplier. Options for Configuration Field Assistant can be installed on a laptop and connected directly to the controller with the USB local access cable. This is the recommended method as it lowers the complexity of connections. Alternately, you can connect over an OEMCtrl BACnet Router. Warning By design, Field Assistant will not work over third party BACnet Routers. The reason an OEMCtrl router is required is to enforce the security permissions framework to protect the algorithmic intellectual property of the lighting panel manufacturer. BACnet IP - [to Laptop] Optional Method Considerations: Requires an OEMCtrl BACnet MS/TP to IP router 1-n connections Laptop to controller(s) Requires purchase of Field Assistant and EULA compliance OEMCtrl BACnet Router IP MS/TP A+ B- S 1 2 3 BACnet MS/TP 0 0 0 S B- A+ RX TX AUTO OVER USB Connection - [to Laptop] 5-Pin Local Access Connection Recommended Method PWR RUN Model Considerations: 1-1 connection Laptop to controller Requires USB Dongle Requires purchase of Field Assistant and EULA compliance Field Assistant must be attached to the controller local access cable - USB Link Kit 5V A6 A5 A4 A3 A2 A1 G R 1 2 3 4 5 6 7 8 LEXP PORT RELAYS 1-32 RELAYS 33-64 N G 17 18 19 20 21 22 23 24 R N R N If your computer does not already have the USB Link Kit driver installed, install it before you connect the USB Link Kit to your computer or try to use the Field Assistant tool. G 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 G Figure 1
Launching Field Assistant When you launch Field Assistant, you ll be prompted to: Create (or select an existing) System Name Import / Export Source Files Select Communication options For the purpose of this document, we ll operate under the assumption that this is your first experience with Field Assistant and that you re using the recommended connection method (connected directly to the controller with the USB local access cable) and no permission key is required System Name First, create a new system by selecting the next to the System Name drop down box. You will be presented with a dialogue box and prompted to enter a name. Though the field will accept any alpha numeric content [letters and numbers, no spaces], it is recommended that you select a name that will make sense to other users. Click the button. symbol Do not begin your System Name with a number. Do not use special characters other than a dash or an underscore. Do not exceed 40 characters. Do not use capital letters or spaces. In the directory where you installed Field Assistant, it will create all of the files, folders and data structures necessary to support configuration in the webroot \ system name you selected folder. So, if you installed in the default location, and used our example system name, Field Assistant would place these files in: C:\Field_Assistant_5.2\webroot\lighting_system_1st_floor_office_2 Next, copy the lighting panel manufacturer supplied driver file into the drivers folder of the newly created file structure. If you installed in the default location, and used our example system name, you would copy the manufacturer supplied driver here: C:\Field_Assistant_5.2\webroot\lighting_system_1st_floor_office_2\drivers All valid OEMCtrl drivers will have the file extension.driver Steps so far Install USB Link Kit driver Install licensed Field Assistant Connect USB Link Kit to controller and laptop Start Field Assistant Create System Copy.driver file to drivers directory
Next, if you have source files provided by your lighting panel manufacturer / representative, click browse to your sourcefiles.zip, then click [Open]. If you haven t been given sourcefiles.zip from the lighting panel manufacturer, that is OK. The only required elements for configuration are the.driver file and a permission key if the lighting panel manufacturer applied the optional security framework. Next, select your System Time Zone. Your selection applies to your current system when you click Next, under Communications, select the method you are using to connect to a controller or system: IP network (not explicitly covered in this document) Local Access - select your USB Comm port from the drop-down list. If you are using a USB Link Kit (USB-L), you must connect it to your computer and the controller before launching Field Assistant in order for your Comm port to appear in the drop-down list. If you do not see your Comm port, close the Field Assistant Launcher, make the connection, then restart Field Assistant. Next, Click to start your system. Field Assistant will find and display the controller you are connected to and any other controllers on its local network. You must upload source files for any controllers you need to work with. If you did everything correctly, you should see a screen like the one below. Note the discovered controller on the left panel. The information in the right panel is related to the highlighted controller. Depending upon the configuration of the system, you may receive a warning message like this: This is a programmable controller. To add a control program, go to the Devices Manage page and click on the Add Control Program button on the top. You can ignore this message as it is for a different kind of controller.
Next, confirm communication with the LxOEM controller by clicking the button. If everything is working correctly, you ll receive a pop up window with some detailed information. Example below.
Steps so far Install USB Link Kit driver Copy.driver file to drivers directory Confirmed communication by clicking [Module Status] Configure Equipment Depending upon the configuration, programming and lighting panel manufacturer supplied permissions you can view and adjust equipment from the following pages: Driver Property Pages Install licensed Field Assistant Imported sourcefiles.zip (if supplied) Connect USB Link Kit to controller and laptop Selected system time zone Start Field Assistant Selected communication Create System Started system Select the System in the navigation tree (left white box), rightclick the controller and select Driver Properties where you can: Upload changed parameters Download schedules and parameters Check status and error messages Adjust Daylight Saving Time View model, IP address, drivers, device ID Edit device names Configure Input Configuration - such as Momentary ON, State Change, etc. Configure Groups Relay and switch associations Adjust Blink Timer Settings If you haven t been given sourcefiles.zip from the lighting panel manufacturer this will be the limit of your configuration capability. Graphics Pages If you have been given sourcefiles.zip from the lighting panel manufacturer, have the appropriate permissions issued by the lighting panel manufacturer, and they have applied these optional pages, you can view and adjust your essential lighting controls on most Graphics pages. Graphics typically display the current status of light equipment and may include an adjustable points within control or other editable properties. This is a highly customizable, manufacturer option and may or may not be present. Some typical controls that may appear on a graphics page are: Button or switch to turn equipment on or off Input field to set a property value Drop-down list to select a state Interactive room sensor to override an unoccupied schedule Set point graph to adjust set points Trend graph to view trend information Link to jump to another Field Assistant page SuperLight, Inc.
Logic Pages If you have been given sourcefiles.zip from the lighting panel manufacturer, have the appropriate permissions issued by the lighting panel manufacturer. The Logic page shows the control program for a piece of equipment. Field Assistant updates the live data (yellow text) every few seconds and whenever you click the Logic button. The control program uses exact property values for its calculations, but values are rounded to 2 decimal places when displayed on the Logic page. Key Property Configuration Most critical configuration of the LxOEM can be accomplished directly on the Driver Property pages. This section will cover the key, available properties that can be configured, the basics on how to configure them. To access the Driver Properties Page - select the System in the navigation tree (left white box), right-click the controller and select Driver Properties.
Device Provides key BACnet Object Information Items you might configure on this page: BACnet Object Name: This is the name the controller and panel are known as on the BACnet network and they must be unique. BACnet ID Device Scheme:: There are 2 choices here available via drop down box Not Autogenerated: Requires that the panel be unique on the network, or have a unique BACnet Object Name (see above) - This is not recommended. Autogenerated: Recommended - This makes the default BACnet Object Name a concatenation of BACnet Device ID Base (typically the BACnet Vendor ID - 24) and the Rotary Switch Address on the Controller. In Autogenerated mode, changing the rotary switch address changes the BACnet Object Name. This is highly convenient as, since you have to provide a unique address anyway, the created BACnet Object Name will also, likely be unique by default. Location and Description: these are text fields for relevant information. Though there are other editable fields on this page, it is recommended that they not be adjusted unless you are a BACnet Expert. Notification Classes There are five Notification Class Pages - they contain BACnet Notification information that: Defines how alarms are prioritized with TO-OFFNORMAL, TO-FAULT, and TO-NORMAL alarms Defines whether these categories of alarms require acknowledgement Defines what recipient controllers should receive the alarms It is recommended that only very experienced individuals make adjustments to these pages. Calendars By default, there are five BACnet Calendar Pages - used to define an object used to describe a list of calendar dates. It is recommended that only very experienced individuals make adjustments to these pages. Common Alarms These are BACnet alarms common to the controller. Most of this information is available in the Module Status page. It is recommended that only very experienced individuals make adjustments to these pages. Custom Translation Tables There are three of these table pages by default. These tables are for non-linear inputs not covered by the Sensor Type choices in the Analog Input. These values are typically not adjusted unless a special, atypical sensor is added to the system.
Panel Configuration Provides the panel Model Type information. In the example to the right, the panel type is set to LC32 which is a 32 relay panel controlling Gruner 704QL 3-pin relays. Items you might configure on this page: Blink Timer: A group with a Blink Assignment will be on for this duration after the blink warning. Blink Duration: A group s lights will blink off for this long during a blink warning. It is not recommended that Relay Pulse Recovery Time or Repeat Relay Command Interval be adjusted without the specific direction of the lighting panel manufacturer. Input Configuration This is one of the key configurations a technician is likely to adjust. The properties on this page allow the technician to adjust how inputs affect the system and how the building s occupants can interact with the lighting system. Input numbers on this page are correlated to the phyiscal inputs on the LxOEM controller as well as any input expanders (LEXPs) present. To adjust the operation of an input: Select the input # by clicking the box to the left of the input # - you can select multiple inputs at once. In the Set all selected to drop down, pick the type of input action you wish to apply. Click the button Input Type Descriptions ON OFF For this type of device... Select this function... To have the input... Digi-Touch 2-button switch or thirdparty momentary switch Momentary ON Momentary OFF Only turn the lights on. Only turn the lights off. ON/ OFF ON/ OFF For this type of device... Select this function... To have the input... Digi-Touch 2-button switch Momentary ON/OFF Toggle the lights on and off. For example, one press of a switch button turns the lights on, a second press of the button turns the lights off.
Continued on next page For this type of device... Select this function... To have the input... Third-party maintained switch State Change Turn the lights to the opposite of their current state. For example, you press a switch button to turn the lights on. A schedule expires and turns lights off. When you next press the button, the lights turn on. NOTES DO NOT use for an LVS switch. For a DDN switch, this functionality is the same as Momentary On/Off. For this type of device... Select this function... To have the input... Occupancy sensor or thirdparty maintained switch connected to a switch input Maintained For this type of device... Select this function... To have the input... Third-party maintained switch Override On or Override Off Toggle the lights on or off when the input state changes. For example, the lights turn on when an occupancy sensor detects occupancy. Select Normally Open or Normally Closed to reflect the input s wiring. Turn the lights on or off, overriding any other switch or program input controlling the same group. Select Normally Open or Normally Closed to reflect the input s wiring. When the Override input is removed, the group returns to the last commanded state. NOTE A group should have only one input configured as an override input. Additional Information about Configurable Properties Input Status Page This page shows the physical status of the panel s inputs. Lighting Groups A lighting group is a logical linking of inputs and relays. Each input in the group controls all the relays in the group. For example, if Group 3 consists of Inputs 6, 7, and 8, and relays 4 and 6, activating any one of the three inputs will affect the lighting connected to relays 4 and 6. On the Lighting Groups page, enter a descriptive name for as many lighting groups as your system needs. You can also enter a group s name on its individual Group page. The Lighting Groups page shows the current status of each group. You can also see a group s status on its individual Group page.
Relay Commanded State This page shows the current commanded state of each relay in the lighting panel. NOTE If an operator uses a relay s manual override switch to change its state, the Relay Commanded State page will not show that change. This state... ON OFF Indicates... The last command to the relay was on The last command to the relay was off Unknown No command has been sent to the relay since the panel was last powered up. Group 1 through 64 Each group defined on the Lighting Groups page has an individual page where you can see the group s present status and define the following for the group. Typically the lighting panel manufacturer will ship the panel with some pre-defined lighting groups, inputs and relay assignments. Management of lighting groups is one of the key items of reconfiguration for a facility manager. Lighting groups allow for more sophisticated building control, energy management and user comfort. Group Command Blink Assignment Input Assignments You can select an option to manually control the group. You can have the lights blink once at a certain amount of time before an occupancy schedule expires to warn the occupants that the lights are about to turn off. On the Panel Configuration page, you can define 2 different warning times (Blink Timer 1 and Blink Timer 2). In the Blink Assignment field, select the Blink Timer that you want the group to use. Enter the address of each switch input, DDN button, or DDN occupancy sensor to be included in the group. The address of a DDN switch button or sensor is determined by its DIP switch settings. If you change a Group s input assignments, first click OK to accept the changes, then click [Update] to refresh the table. The Member of Group(s) column shows all groups that the input is assigned to. The Configuration column allows you to see or edit each input s configuration. Relay Assignments NOTE Analog inputs are read through logic only, and are not included in a group. Enter the number of each relay to be included in the group. If you change a Group s relay assignments, first click OK to accept the changes, then click [Update] to refresh the table. The Member of Group(s) column shows all groups that the relay is assigned to. The status column shows the commanded state of each relay assigned to the group