Once all required devices have been configured then the data in the job needs to be saved to the devices. If pre-commissioning or not currently online then this can be done later.
Device data can be saved to one or more of the devices by selecting them in the network view and clicking ‘Save to Device’ from the main ‘Device’ menu or the button on network view tool-strip. Alternatively all changes can be saved for all modified devices by clicking below. This option is also available under the ‘Tools’ menu.
When saving to devices the status and progress can be viewed in the command monitor. 1. Expand 12. Save Data to Devices.
2. Click Show network view. 3. Click Save all modified devices. 4. Click Show command monitor.
TOPIC 6:
CONFIGURING LOAD CONTROLLERS
Topic Overview
The fundamental principle of operation of a Dynalite control network is cantered on grouping related circuits into areas and then recalling Preset scenes for those areas. This method of operation is entirely dependent on the load controllers being commissioned correctly. Once this vital work is completed the project has a solid foundation on which any number of operational features can be applied. This section is focused on getting the logical configuration of the load controllers correct.
Learning outcomes
By the end of this topic you will be able to:
• Identify physical Channels in a Philips Dynalite project. • Configure a load controller using EnvisionProject.
The floor plan and equipment list
Some kind of floor plan is needed to enable the programmer to break up the site into controllable chunks called areas. This plan would ideally be taken from the engineering drawings but could be as simple as a sketch on a pad.
Equipment list
The programmer should be issued with a list of supplied products for a project before they arrive at site. This is the only way to ensure that each device on the network is accounted for.
The Training case V2 contains:
• 2 x DDBC1200 – Ballast Controllers. • 1 x DLP950 – 5 button panel.
• 1 x DPN881D – 8 button panel with key switch. • 1 x DPWE – 5 button panel.
• 1 x DRP96K –6 button panel.
• 1 x DUS704C 0r 1 x DUS804C –Universal Sensor.
The Mini Training Case contains:
• 2 x DDBC1200 – Ballast Controllers. • 2 x DR2P98M – 8 button panel.
Flashing
Flashing is used to identify the location of circuits and devices in a project, this information is then used to determine logical Area and Channel assignments to create a load schedule for
commissioning.
There are 2 levels of Flashing, by device or by individual Channel.
Flashing a device is used to find its physical location, additionally Flashing a load controller enables the identification of all Channel locations simultaneously, in large projects, this allows for the general location of the circuits for a load controller to be quickly identified.
Flashing by Channel is used to identify the specific physical locations of Channels for the load controller, a load schedule maybe created using this information.
EnvisionProject provides support for flashing the following items:
1. Logical Areas – Alternatively sends fade Area (all Channels) 0% and 100% messages. Areas can be flashed from the Logical view.
2. Logical Channels – Alternatively sends set logical Channel level 0% and 100% messages. Logical Channels can be flashed from the Logical view or the logical Preset editor. 3. Physical Channels – Alternatively sends set physical Channel level 0% and 100% messages.
Physical Channels can be flashed from the Logical view, the unassigned Channels view or the physical Preset editor.
4. Load Controllers – Alternatively sends set all physical Channels level 0% and 100%
messages. Load controllers can be flashed from the Network view, the unassigned Channels view or the devices references view.
5. Panels and Sensors – Places the device into setup mode and maintains the device in setup mode by sending “Listen to me” messages. Panels and sensors can be flashed from the Network view or the devices references view.
Once any of the above items are placed into a flashing state their corresponding icons will indicate they are flashing in all views.
The flash period is control by the user settings “Flash on period” and “Flash off period”. The default values for these are 100 milliseconds (1 second). All flashing messages have a zero fade rate.
If a physical Channel is a ballast type or a load controller, logical Area or logical Channel contain a ballast Channel then by default the item will only flash off every second flash cycle. This is to allow ballasts to have sufficient time to flash on. To disable this feature set the user setting “Double on flash for ballast” to false.
To Flash a device complete the steps below:
1. Click on the device you wish to Flash in the Network view.
Fig 85 – Network View
2. Click in the Network view toolbar, the devices display icon will change to the Flash icon. The device is now Flashing.
To Flash individual Channels follow the steps below:
1. Click on the Channel you wish to Flash in the Logical view.
Fig 86 – Logical View
2. Click in the Logical view toolbar, the devices display icon will change to the Flash icon. The device is now Flashing.
Load Schedule
Project: Device Type:
Box No:
Ch # Channel Name Area Name Area # Logical Ch # Dup/Sw
1 2 3 4 5 6 7 8 9 10 11 12
Project: Device Type:
Box No:
Ch # Channel Name Area Name Area # Logical Ch # Dup/Sw
1 2 3 4 5 6 7 8 9 10 11 12
Manual Load Controller Configuration
To manually configure a load controller, complete the steps below:1. Click on the load controller you wish to configure in the Network View, shown in Fig 87 – Network view.
Fig 87 – Network View
2. Click on in the Main Editor Properties.
4. Using information from your load schedule (see section on Load Schedules in this topic), click in the firstPhysical Channels Channel Name field to enter its new Channel name, see Fig 89 – Channel Editor tab.
Fig 89 – Channel Editor tab
5. Hit Enter to move to the next Physical Channels Channel Name field and enter its new
Channel name. Continue this process for the remaining Channels in the load controller. 6. Next we will configure the Logical Areas Using information from your load schedule (see
section on Load Schedules in this topic), click in the firstPhysical Channels Logical Area field to enter its new Area number, see Fig 90 – Channel Editor tab.
Fig 90 – Channel Editor tab
7. Hit Enter to move to the next Physical Channels Logical Area field and enter its new Area
number. Continue this process for the remaining Channels in the load controller.
8. Now we will configure the Logical Channels. Using information from your load schedule (see section on Load Schedules in this topic), click in the firstPhysical Channels Logical
Fig 91 – Channel Editor tab
9. Hit Enter to move to the next Physical Channels Logical Channel field and enter its new
Area number. Continue this process for the remaining Channels in the load controller. 10. Once the required Channel name, Logical number and Logical Area have been added, click
Logical Load Controller Configuration
To logically configure load controllers, complete the steps below:1. Click .
2. Select .
3. Expand each load controller displayed
4. Select a Channel in the list and click to name the Channel.
Fig 92 – Unassigned Channels tab
5. Click and drag the Channel from the Unassigned Channels tab to the correct Area in the Logical view.
Fig 93 – Unassigned Channels tab and Logical view
Note – If you are unsure of which Area to assign a channel, click to flash and identify the location of the channel.
6. Repeat steps 3 & 4 for all the remaining unassigned Channels.
7. Click .
8. Select the load controller/s from the List (it should have in the status column).
TOPIC 7:
CONFIGURING PANELS
Topic Overview
Once the load controllers have been configured, the panels are used to recall the Area Preset scenes to create the required effect for the end user. Panels can be configured to perform many functions directly from the GUI.
Learning outcomes
By the end of this topic you will be able to:
• Setup control panels to send default Preset messages to a defined Area. • Configure individual buttons to perform different functions.
• Competently set up Preset scenes with a lighting designer.
Panel settings
Device Properties Tab
The device properties for panels contain a number of tabs for configuration:
• Device Properties – General panel properties, name, box number, native Area. • Buttons – Button configuration settings.
• Task and Events – Tasking and event information. • IR Buttons – IR button configuration.
• Switches – Switch configuration. • DyNet Ports – DyNet port information.
Fig 94 – Device Properties
Assigning a panel to an Area
To assign a panel to an Area, follow these steps:
1. In the Network view, click on the panel you wish to assign to an Area.
2. Click to display the Change Panel Area dialog.
Fig 96 – Change Panel Area dialog
3. Click to choose from the available Areas.
4. Click on the Area you require and click .
Note –The change options section allows you to apply the Area change to the Whole panel including buttons, sliders, IR buttons and key switches or just for the panel itself which is called the native panel Area.
Fig 98 – Change Options
5. Click to complete the Area change.
6. Click to save the change to the panel.
Changing Panel box numbers
To change a panel’s box number, complete the steps below:
1. Click on the panel you wish to change box numbers then click . 2. Click in the Box Number field and enter the new box number.
3. Confirm the box number is correct in the Change Device Box Number dialog.
Fig 100 – Change Device Box Number dialog
4. Click to complete the box number change.
Enable Area zero messaging
Area zero has a unique function; it broadcasts to all Areas and is useful for controlling a whole network together.
As Area zero broadcast to all Areas and Channels in a network it could be potentially dangerous if there is non- lighting integration of the network say, with a 3rd party security system.
If we use an Area zero message to turn off all the ‘lights’ we will also turn off the security system. With this in mind, should you wish to allow a device on the network to broadcast Area zero
messages, it must be specifically enabled.
To enable Area zero messaging from a panel, complete the steps below:
1. Click .
2. Click in the Area Zero Transmit field to and select Enabled, see Fig 99 – Device Properties tab.
Fig 101 – Device Properties tab
3. Click to save the change to the panel.
Panel Views
When configuring panels in the Buttons tab, 2 views are available, Panel view and Button list view.
provides an image of the panel you are working on, clicking on a button in the image enables you to work on that button, shown in Fig 100 – Panel view.
enables a quick identification of the functions of buttons with icons and a brief description. See Fig 101 – Button view.
Fig 103 – Button view
Configuring Panels
There are a large number of functions that can be applied to buttons in a panel, we will now look at 2 of the most popular, Presets and One Touch.
Configuring Presets
To configure a button on a panel to call a Preset, complete the steps below:
1. Click .
2. Click in the Function Type field.
Fig 105 – Function type
3. Select Preset from the drop down list.
4. In Preset Action, click on Preset.
Fig 107 – Preset Action
5. Select the Preset you require from the drop down list.
Fig 108 – Preset Action
6. In Preset Action, click on Logical Area.
7. Click to select the Area you want.
Fig 110 – Area Selection
8. Click .
9. In Preset Action, click on Fade Time and enter the fade time you want (default is set to 2 seconds).
Fig 111 – Fade Type
Configuring one touch
1. Click .
2. Click in the Function Type field.
Fig 112 – Function Type
3. Select from the 3 One Touch options available in the drop down list: • One Touch Preset Toggle.
• One Touch Ramp Only.
• One Touch Ramp with Program.
4. In Preset Action, click on On Preset.
Fig 114 – On Preset
5. Select the Preset you require from the drop down list. (Default 1).
Fig 115 – Preset Action 6. In Preset Action, click on Off Preset.
Fig 116 – Off Preset
Fig 117 – Preset Action
8. In Preset Action, click on Ramp Rate and enter the ramp time you want (default is set to 5 seconds).
Fig 118 – Ramp Rate
9. In Preset Action, click on Logical Area.
Fig 119 – Logical Area
Fig 120 – Area Selection
11. Click .
12. In Preset Action, click on Logical Channel.
Fig 121 – Logical Channel
14. In Preset Action, click on Fade Time and enter the fade time you want (default is set to 2 seconds).
Fig 123 – Fade Time
TOPIC 8:
CONFIGURING SENSORS
Topic Overview
The DUS704 sensor combines motion detection (PIR), infra-red remote control reception (IR) and ambient light level detection (PE) in the one device. In applications such as homes, lecture theatres and office towers, DUS704 universal sensors can be utilised to detect motion and switch on the lights.
This topic covers the set up and configuration of the universal sensor.
Learning outcomes
By the end of this topic you will be able to:
• Configure Philips-Dynalite sensors for occupancy control function. • Control an Area based on natural light levels.
About the universal sensor
The DUS704 Universal Sensor is an integrated energy management sensor and Area controller. Sensor functions include:
• Occupancy detection. • Light Level Compensation. • Infrared Control.
When rooms are unoccupied, lights can be automatically dimmed or switched off to provide energy savings.
The same sensor provides IR remote control reception to give IR control over lights, audio-visual equipment and blinds. These codes can be stored in learning remote and used to control the lighting, TV etc… from a single remote controller.
In situations where it is critical to maintain precise lighting control for individual workspaces, such as a flight control tower or office workstation, the DUS704 facilitates light compensation. The DUS704 can be placed in an automatic “Daylight Harvesting” mode for energy savings.
The sensor is available in 2 styles, for ceiling and wall mounting.
Fig 124 - DUS704C Fig125 - DUS704W Fig 126 - DUS804C Fig 127 – DUS804C-UP
Occupancy detection
The objective of occupancy detection is to automatically illuminate a space when it is occupied, and reduce or extinguish lighting when it is vacant to save energy. Any number of light fixtures may be controlled for occupancy detection from a single sensor.
Key point - When the DUS704 is powered up, occupancy detection functions are inhibited and no motion actions will be processed for a period of up to 30 seconds while the sensor hardware filters settle and the sensor adjusts itself to the ambient air temperature.
Occupancy detection example
Within the DUS704 a set of Presets is defined, as the occupancy monitoring Presets, typically 3 Presets are defined.
Fig128 – Motion sensor configuration flow chart
In this example, they are named ‘Occupied’, ‘Grace’ and ‘Vacant’. No definition is configured for other Presets.
• For the ‘Occupied’ Preset (Preset 1) the space is illuminated to provide occupants with suitable lighting levels. The DUS704 is configured to change to the ‘Grace’ Preset after 30 minutes of no motion activity.
• In the ‘Grace’ Preset (Preset 2) the space is dimmed to warn any occupants that the lights are about to be automatically turned off. The DUS704 is configured to return to the ‘Occupied’ Preset if motion is detected. If a period of 5 minutes of no motion activity passes the DUS704 will progress to the ‘Vacant’ Preset.
• For the ‘Vacant’ Preset (Preset 4) the lights are turned off to save energy. The DUS704 is configured to select the ‘Occupied’ Preset when motion is detected.
Occupied Preset action
Fig129 – Occupied Preset
‘Occupied’ Preset (Preset 1) actions should include an ‘Unoccupied action’ to go to the ‘Grace’ Preset (Preset 2). The ‘Occupied action’ should be set to ‘No Action’.
The timeout should be set to 1800 seconds (30 minutes).
Grace Preset action
Fig 130 – Grace Preset
The ‘Grace ‘Preset (Preset 2) actions should be to revert to the ‘Occupied’ Preset (Preset 1) when motion is detected, or fall back to the ‘Vacant’ Preset (Preset 4) when there is no motion detected for the time out period.
Vacant Preset action
Fig131 – Vacant Preset
The ‘Vacant’ Preset (Preset 4) actions should recall the ‘Occupied’ Preset (Preset 1) when motion is detected. No action should be configured for the ‘Unoccupied action’.
Configuring occupancy detection
To configure a sensor for motion detection, follow the steps below:
1. In the Network view, click on the sensor that requires configuration and then click in the Properties view.
Fig 132 – Motion detector tab
2. Sensors are configured per Preset, so we’ll start with Preset 1 and move sequentially. Click to configure settings for Preset 1.
3. Each Preset has 2 conditions to be determined, a motion action and a no motion action.
Fig133 – Action chain Editor
4. Click and select .
Fig 134 – Action options list
Fig135 – Action chain editor
6. Click to close the dialog.
7. Click in the Time out field and enter 30 mins, see Fig 134 - Motion detector properties.
Fig136 – Motion detector properties
8. Now we’ll configure the next Preset. Click to configure settings for Preset 2.
9. Click .
10. Click and select .
11. In the Preset Action properties change the Preset number to 1.
Fig 138 – Action chain Editor
12. Click to close the dialog.
13. Click .
14. Click and select .
Fig 139 - Action options list
Fig 140 - Action chain Editor
16. Click to close the dialog.
17. Click in the Time out field and enter 5 mins, see Fig 139 – Motion detector properties.
Fig 141 – Motion detector properties
18. Click to add settings for Preset 3. In our scenario, we are using only 3 Presets, Preset 1 (on Preset), Preset 2 (Grace Preset) and Preset 4 (off Preset). Therefore Preset 3 is unused so we will leave it configured to No Action.
19. Next we’ll configure the final Preset. Click to configure settings for Preset 4.
20. Click .
Fig 142 – Action options list
22. In the Preset Action properties change the Preset number to 1.
Fig 143 – Action Chain Editor
23. Click to close the dialog.
24. Your configuration is complete, double check the setting in the table in the Main properties.
Fig 144 – Motion detector properties
Configuring light level sensing
Open loop light level compensation example
Follow these instructions to configure a sensor for open loop light level compensation:
1. Click in the sensor main properties.
Fig 145 – Light Control tab
2. Click to create a night band Preset,
Fig 146 – Action Chain Editor
4. Click and select .
5. Select the Preset and Fade time you want from the Preset Action properties.