Commissioning and Administration Guide Redwood Manager Version 3.
Table of Contents Table of Contents i Introduction 4 Redwood Director and Redwood Engines Accessing the Redwood Manager Admin Console Navigating the Tabs of Redwood Manager Dashboard Tab Control Tab Reporting Tab Maintenance Tab Location Editor Tab Locations and Fixtures Planning a Location Hierarchy Defining Locations Adding a Location Renaming a Location Moving a Location Deleting a Location Assigning Fixtures to Locations Naming Fixtures Flashlight Naming of Fixtures Using Blink to Name Fix
Where did that Motion Signal come from? Copying Events Managing Events and Policies from “All Locations” Events Configuration Report Scenes 23 23 24 24 25 Adding Scenes to Locations Activating and Deactivating a Scene Setting Scene Control Switches 25 26 26 Sensor Calibration and Sensitivity 27 Ambient Light Calibration Setting Motion Sensor Sensitivity 27 28 User Accounts Login Logout View and Edit Users Create Users Deleting Users Alerts and Alarms
Power LED Indicator Port LED Indicators Ethernet LED Indicator Install Fixtures Tool Redwood Support Page Configuration Section Statistics Section Actions Section Logs Other Basic Support Info Commissioning and Administration User Guide 37 37 37 38 39 39 40 40 40 40 40 iii
Introduction Before you can begin using the Redwood Systems Building and Lighting Platform, you must commission the light Fixtures and Switches. Commissioning is performed after the physical infrastructure is installed. The Redwood Manager makes it easy to step through the process. As an administrator, in addition to commissioning, you can manage and control the Redwood System lights.
Dashboard Tab Within the Redwood Manager, the Dashboard tab provides a high-level view of the entire system. Sensor measurements such as the total power consumed, the ambient temperature, ambient light levels, and motion counts are aggregated over all Locations and plotted on a graph. A baseline value can be overlaid on these plots to show a comparative picture. The “Zoom In” button allows the selection of specific time windows.
Reporting Tab The Reporting tab shows the available data collected by the Redwood Sensors. Graphs can be viewed over various timescales. Temperature can be displayed in either Fahrenheit or Celsius. A “zoom” feature is also provided to show a more detailed view of a given dataset. The data displayed is live and will refresh automatically. Placing the mouse cursor over a part of the report’s line will show the exact time-value pair at that point.
Maintenance Tab Information on each light Fixture and Wall Switch is available in the Maintenance tab. Select a Fixture to view manufacturing information and other internal data. You can also modify the settings for the temperature and power alarms, DPIR Sensors, and Scene Control Wall Switches on the Maintenance tab.
Location Editor Tab The organization of fixtures and locations is done through the Redwood Manager’s Location Editor tab. Fixtures are stored in locations within a hierarchical tree structure. "All Locations" appears at the top of the tree. Sub-locations can be created within top-level locations and can be nested in multiple levels. Fixtures may be at any location in the hierarchical tree, except under "All Locations".
Locations and Fixtures Before you begin the commissioning process, make sure that all lights have completed the selfdiscovery process and are lit. After the system is installed, the recommended order of the commissioning process is: 1. Identify and define Locations (typically floors and rooms). 2. Give the Fixtures meaningful names. 3. Assign the Fixtures to Locations. 4. Verify the settings. 5. Create Events and Policies to control the lights. 6. Assign the Events and Policies to Locations. 7.
Wall Switches will behave differently depending on whether they are associated with a “parent” or “child” Location. Typically, a Wall Switch can control Fixtures that are in the same Location. However, if a Wall Switch is placed in a “parent” Location that has Fixtures in its “child” Locations, it can control the dimming of these Fixtures as well.
Adding a Location 1. To add a parent Location, click All Locations and then click the 2. To add a sub-Location, click the parent Location and then click the button that appears. button that appears. 3. A new Location will be automatically added as a child of the Location you started with. This Location will be called “Location” plus a number like “123”. 4. Click Apply, at the bottom left of the screen.
Assigning Fixtures to Locations After creating Locations, you can assign Fixtures and Wall Switches to their appropriate Locations. The number next to each Location indicates the number of Fixtures within that Location. Newly discovered Fixtures and Wall Switches are automatically placed in the Unassigned Location. If a Sensor is unassigned, the Sensor’s LED indicator light will be solid red. If a Wall Switch is unassigned, the Wall Switch’s LED indicator light will be solid green.
Naming Fixtures Each Fixture is identified by a Name and a set of data that is determined by the Gateway/Adapter that is connected to the Fixture. When commissioning the system you can edit the Name of the Fixture to be something more meaningful to the end-user than the default value which is the ID of the Gateway/Adapter.
5. (Optional) Assign a light level to the Fixtures from the Location is drop-down menu. The default is Normally Lit. You might need to change the light level to match the current light level in the Location if high-ambient light causes a Fixture to think it “sees” the flashlight before commissioning begins. Fixtures that are not ready for commissioning because of high-ambient light have a red dot next to the Fixture’s icon.
10. To save this configuration change, click Apply, at the bottom left of the screen. LED Status Port Status The Sensor or Wall Switch is not ready for commissioning. The possible explanations are: Flashlight commissioning has not yet been initiated. The Sensor in question is not in the 'flashlight' Location. Off Flashing Red/Green Solid Red/Green The Sensor or Wall Switch is ready for commissioning and has not yet been named. The Sensor or Wall Switch has been successfully named.
Wall Switch You can commission a Wall Switch using the same flashlight commissioning process as with a fixture by shining a flashlight at the light sensor. You can also manually commission a Wall Switch by connecting it to an Engine. When detected, the Wall Switch will automatically be placed in the Unassigned group. You can then drag and drop the Wall Switch to the desired location. To add a Wall Switch manually: 1. In the Location Editor tab, select the Location. 2.
Adding Additional Hardware After Commissioning You can add Fixtures at any time after the initial configuration is complete. When detected, they are automatically placed in the Unassigned group. You can add Fixtureless Gateways to the same Locations as LEDs and fluorescents. They do not participate in light-control features nor limit the functionality for a Location. To add a Fixture or switch: 1. In the Location Editor tab, select the Location. 2. Drag the Fixtures you want to add to the Location. 3.
Events and Policies A Policy is a set of rules that define what to do—which actions are performed by the lights in a specific Location. A Policy identifies the light levels, occupancy mode and timeouts, and when to turn daylight harvesting on and off. An Event is a set of rules that define when to perform an action on the lights.
Events At a high level, an Event can be thought of as the “when and why” of a lighting change. Each Location has a set of prioritized Events – several Events may be “active” at once due to scheduling or external signals, but only the Event with the highest priority will actually apply its lighting Policy. To create an Event: 1. Select the Location from the Location Settings tab. 2. Click 3.
Prioritizing Events Events occur in the order that they are prioritized for each Location. The current Event priorities for a given Location are seen on the Location Settings tab for the Location. Several Events can be active at the same time because of scheduling or external signals, but only the Event with the highest priority applies its lighting Policy. For instance, a regularly scheduled Event on a Monday can be overridden by a holiday.
5. To control Fixtures based on motion, select an occupancy mode from the drop-down menu. In Standard mode, triggering only one motion sensor turns on the Location’s lights. In Multi-Sensor Occupancy mode, the Sensor count defines the number of Sensors that must trigger to activate the lights. Only a single Sensor needs to detect motion to keep the lights on. In Vacancy mode, the lights must be turned on manually. Motion does not turn on the lights, but lack of motion turns them off.
Motion Groups You can use the Motion Groups Feature in Redwood manager for when, in the course of defining your Events and Policies, it becomes necessary to trigger an Event to occur in a given Location (or specific Fixture in a Location) based upon motion (occupancy) seen by a Sensor not associated with that Location (or Fixture). With this technique a single motion signal can be “shared” with multiple Locations, in effect allowing them to share a single Sensor.
Un-Sharing a Motion Signal 1. Select the Location (or Fixture) that has the Sensor you want to “share” motion from using the Maintenance tab. 2. Select Configuration on the pull-down directly below the Maintenance tab. You will see a listing of the current Locations that are Recipients of motion signals from this Donor Location. 3. Select the Recipient Location on the list that you wish to stop receiving motion signals and click on the icon. 4. You will be asked to confirm.
Managing Events and Policies from “All Locations” Policies and Events can be used in multiple Locations, so often you will want to mange them as a cross-Location set. To view All Events and Policies: 1. Select “All Locations” from the Location Settings tab. 2. Select either Polices or Events on the top of the dialog box. 3. Hover over any item in the list to view the Locations in which the Event or Policy is assigned. A yellow marker next to an Event indicates that it is active in one or more Locations. 4.
Scenes A Scene is used to adjust a Location’s Fixtures to achieve a desired lighting effect for a specific period of time. Scenes apply to specific Locations, and as such are not global settings. You can create Scenes for short Events, like a presentation. For example, a common Scene in a conference room is presentation mode—the lights near the projector screen are turned off completely, while the other Fixtures are slightly dimmed.
Activating and Deactivating a Scene Activating a Scene immediately sets the Fixtures to their specified levels. When a Scene is activated, you cannot perform task-tuning, but you can use Wall Switches and overrides. Deactivating a Scene returns the lighting Policy to what is specified in the prioritized Event list. To activate or deactivate a Scene: 1. Click the Location Settings tab or the Control tab. 2. Select the Scene to activate or deactivate.
Sensor Calibration and Sensitivity Ambient Light Calibration Redwood Sensors are shipped calibrated, except for the ambient light Sensor. The ambient light Sensor has an adjustable dynamic range. You must calibrate it based on the light level of the space. (Calibration might not be needed if you are not using the daylight harvesting feature.) IMPORTANT NOTE Note that not calibrating only prevents the daylight harvesting feature from working, so calibration may not be needed in all installations.
To calibrate a Fixture: 1. In the Location Editor tab, select a Location. You can calibrate only one Location at a time. 2. Click the Calibrate Fixtures button. The process takes about 10 minutes. The lights fully turn on for about 2 minutes so that the Sensors can assess the maximum light reading. The lights then turn off to establish a zero-light level reading. Finally, the Fixtures step through light levels in 10% increments. 3. Wait for calibration to complete before making any other changes.
User Accounts Individual user logins can be created for each person that will access Redwood Manager. These user accounts each consist of a unique Username and a related Password. When a user is logged into the system the actions they are able to perform will be limited by the Roles that are assigned to them. There are three Roles that can be assigned to a User: User – A user is someone who can access Redwood Manager to control lights via task tuning, selecting scenes, and issuing policy overrides.
View and Edit Users 1. To access the list of current system Users click on the Configuration (or “Sprocket”) Menu found at the top right of the screen. 2. On the resulting configuration dialog box the Users tab will provide a list of all current systems users, their ID, Name, Email and Role. 3. Click the Pencil icon to the right of the user that you wish to edit. 4. All of the information related to the user account will be displayed in editable form. Edit the account information needed. 5.
Alerts and Alarms Dashboard Alarms The Redwood Manager Dashboard displays important system messages to the administrator in the form of Alarms at the bottom of the screen. These Alarms range from minor informational points to major notifications about potential system issues, so it is important to monitor these on a regular basis.
Configuration Menu The Configuration (or “Sprocket”) Menu is found at the top right of the screen and allows access to a set of general systems configuration items. Cluster The Cluster tab is used to define which Cluster a given Engine is part of in terms of the Cluster Name, the Engine ID and IP Address of the Master in that Cluster and the Local Engine ID. For more information, see the Networking Guide. Network The Network tab identifies the IP communications settings for the given Engine.
Configuration Backups After you have completed the initial configuration, create a backup of the settings. Before making major changes to the commissioning, make sure that you have a backup so that you can restore the original configuration if needed. You can also use the configuration file to restore the system if something happens. Creating a Backup The configuration file engine.cfg is saved on your local computer. The file contains the system settings, including Policies, Scenes, and schedules.
11. Reboot the Engine. On the Actions tab, click the Reboot button. After the Engine reboots, it rejoins the Cluster. Reverting System to Factory Default Settings Caution: Reverting the configuration cannot be undone. However, you can restore the configuration from a saved configuration file. To revert the system to the factory default configuration: 1. Click the Option button in the upper right of the Redwood Manager. 2. In the Engine Configuration screen, click the Actions tab. 3.
Upgrades Redwood will periodically release software upgrades that add functionality and new features. If you have an active Support Agreement you will be notified of any available upgrades via Redwood’s technical support group. IMPORTANT NOTE Once you perform an upgrade to a later version you cannot downgrade back to a prior release. Upgrades to all Redwood Systems software and firmware are performed from the Redwood Administrator Console by electing the Update Software button.
Troubleshooting You can monitor the operational health of your system using the following methods: Alerts and Alarms LEDs on the front panel of the Redwood Engine Using the Fixtures tool from the Admin Console Log files from the Redwood Support page Alerts and Alarms Alarm Possible Cause Possible Solution LED Indicators The front panel of the Redwood Engine 3 (ENG-3-4834) has LEDs to communicate the system status.
Power LED Indicator Power LED Engine Status No power is being delivered to the Engine. Blinking Engine is booting, but not yet running. Engine is on and functioning normally. Engine is experiencing a problem. Call Redwood Support. Port LED Indicators Each port on the Engine has an LED to communicate status. After a period of inactivity, the LEDs are turned off to save energy. You can check the status by pressing the Show Status button on the Engine’s faceplate.
Install Fixtures Tool The Engine’s ports will be shown along with a representation of the Cluster and several other data tables. Clicking a Fixture in the table on the lower left will display configuration information such as the Fixture’s vendor and its required number of ports. The Engine that powers this selected Fixture will be highlighted in the upper right table.
The following information can also be obtained from the Fixtures tab: Missing: Displays a list of Fixtures that have been disconnected since the system was powered on. Errors: Displays a list of disabled Fixtures and lists the error that the Engine detected. Warnings: Shows Fixtures that are working under conditions that the Engine considers unusual. For example, a warning is raised if plugged-in ports are not located side-by-side on an Engine.
Statistics Section Internally, the statistics gathered by the Sensors are stored in a compact file format. It is via the Download Statistics link that you can retrieve the statistics for each Engine. It is not recommended that users use this method without Redwood Support. Actions Section There are two links that permit you to restart or reboot the Engine. These links perform the same function as the restart and reboot function from the Action tab under the Options button .
www.commscope.com Visit our Web site or contact your local CommScope representative for more information. © 2014 CommScope, Inc. All rights reserved. All trademarks identified by ® or ™ are registered trademarks or trademarks, respectively, of CommScope, Inc. This document is for planning purposes only and is not intended to modify or supplement any specifications or warranties relating to CommScope products or services.
