rEVE Rev 1.

DESIGNER VERSION 5

QUICK START GUIDE

rEVE Rev 1.3

Revision history
Author Date Notes Rev
MA 12/08/16 First Draft 0.1
TO 07/10/16 Proof Read Draft 0.2
TO 11/10/16 First Issue Release 1
TO 02/11/16 Cluster Master Correction 1.1
TO 14/12/16 Renamed section 11.4, conflicted with 10.4 for Confluence import 1.2
TO 22/01/20 Duplications removed in section 13 1.3
rEVE Rev 1.3

1 PURPOSE OF THIS DOCUMENT ..................................................................................... 6

2 SUPPORTED OPERATING SYSTEMS .............................................................................. 6
3 SINGLE CLUSTER AND MULTI-CLUSTER WORKGROUPS. ............................................. 7
3.1 SITUATION 1 SINGLE CLUSTER WORKGROUP ON SEPARATE, UNMANAGED NETWORK.......................... 7
3.2 SITUATION 2: MULTICLUSTER WORKGROUP ON SEPARATE, UNMANAGED NETWORK .......................... 9
3.3 SITUATION 3: SINGLE-CLUSTER NETWORK WITH VARYING IP CLUSTERS IN A MANAGED NETWORK ...... 11
3.4 CLUSTERS: CLUSTER MASKS AND ROUTER IDS ......................................................................... 12
3.5 PRIMARY MASTER AND SECONDARY MASTER ROUTERS ............................................................... 13
3.6 BEFORE YOU CONNECT: PREPARE YOUR PC AND HELVAR ROUTERS TO GO ONLINE ............................ 14
3.7 WINDOWS FIREWALL SETTINGS ........................................................................................... 14
3.8 IP SETTINGS FOR THE CLIENT PC AND HELVAR ROUTERS ............................................................ 14
EXAMPLE: ONE ROUTER ................................................................................................................ 14
3.9 SET YOUR WINDOWS PC NETWORK CARD IPV4 ADDRESS. .......................................................... 14
3.10 CHANGE THE IP SETTINGS OF THE HELVAR ROUTER. ................................................................. 14
4 DESIGN FILE BACKUP ................................................................................................. 16
4.1 AUTOSAVE OF THE .DESIGN FILE .......................................................................................... 17
5 GO ONLINE: CONNECT TO A WORKGROUP ................................................................. 18
5.1 TIME SYNCHRONISATION .................................................................................................... 18
5.2 HOW TO SET 'SYNCHRONISE TIME' TO TRUE BY DEFAULT ............................................................ 18
5.3 GO ONLINE: CONNECT TO THE WORKGROUP........................................................................... 19
6 IDENTIFYING ROUTERS, LOAD INTERFACES, CONTROL DEVICES, INPUT UNITS AND
SUBNETS ............................................................................................................................ 21
6.1 IDENTIFY A ROUTER .......................................................................................................... 21
6.2 IDENTIFY A DEVICE: LOAD INTERFACE .................................................................................... 21
6.3 APPLY NAME AND/ OR GROUP ............................................................................................ 23
6.4 IDENTIFY A DEVICE: CONTROL DEVICE (E.G. BUTTON PANEL) ....................................................... 23
6.5 IDENTIFY A DEVICE: INPUT UNIT .......................................................................................... 23
6.6 IDENTIFY: SUBNET ........................................................................................................... 24
7 GROUPS VIEW ............................................................................................................. 26
7.1 GROUPS VIEW: OVERVIEW .................................................................................................. 26
7.2 VIEWING DEVICES IN A GROUP USING THE GROUPS VIEW ............................................................ 27
7.3 CREATE GROUPS IN GROUPS VIEW: +.................................................................................... 28
7.4 PUTTING DEVICES INTO GROUPS .......................................................................................... 29
7.5 EDITING GROUPS USING A DEVICE’S PROPERTIES WINDOW .......................................................... 30
7.6 COPYING / PASTING DEVICE PROPERTIES ............................................................................... 33
7.7 DELETE GROUPS .............................................................................................................. 33
7.8 GROUP MEMBERSHIPS (PRO MODE ONLY) ............................................................................... 34
7.9 LAST SCENES IN BLOCKS .................................................................................................... 35
7.10 LAST SCENE IN GROUP ...................................................................................................... 36
7.11 WHEN GROUPS EXIST IN ROUTERS ........................................................................................ 36
8 0.1% DIMMING RESOLUTION .................................................................................... 37
8.1 HOW DO I KNOW IF A LOAD INTERFACE DEVICE OFFERS 0.1% DIMMING RESOLUTION?....................... 37
8.2 HOW TO SET LEVELS TO 0.1% RESOLUTION ........................................................................... 38
8.3 EXAMPLE: HOW TO SET MINIMUM AND MAXIMUM LEVEL DALI TYPE 8 COLOUR LED DRIVER ............... 39
8.4 EXAMPLE: HOW TO SET SCENE LEVEL FOR A DALI TYPE 8 COLOUR LED DRIVER AND A 454 DIMMER
CHANNEL .................................................................................................................................. 40

9 COLOUR CONTROL AND COLOUR TEMPERATURE IN THE SCENE TABLE .................... 41

9.1 SCENE TABLE .................................................................................................................. 41
rEVE Rev 1.3

9.2 COPY AND PASTE INTENSITY ............................................................................................... 42

9.3 COPY AND PASTE COLOUR SETTINGS ..................................................................................... 42
9.4 COPY AND PASTE INTENSITY AND COLOUR SETTINGS................................................................. 43
9.5 CHANGE COLUMN WIDTH .................................................................................................... 43
10 PROGRAMMING TUNEABLE WHITE DRIVERS ............................................................. 44
10.1 WHAT ARE THE COLOUR PARAMETERS OF A TUNEABLE WHITE LED DRIVER? .................................... 44
10.2 COLOUR TEMPERATURE VIEW.............................................................................................. 45
10.3 SETTING COLOUR TEMPERATURE LEVELS OF A TUNEABLE WHITE LED DRIVER ................................... 46
10.4 COLOUR TEMPERATURE VIEW: ADJUSTING COLOUR TEMPERATURE ............................................... 47
10.5 PALETTE ........................................................................................................................ 48
10.6 OPTIONS ....................................................................................................................... 49
11 PROGRAMMING COLOUR LED DRIVERS ..................................................................... 49
11.1 WHAT ARE THE COLOUR PARAMETERS OF A COLOUR LED DRIVER? ................................................ 49
11.2 COLOUR VIEW................................................................................................................. 50
11.3 SETTING COLOUR SETTINGS OF A COLOUR LED DRIVER. ............................................................. 51
11.4 ADJUSTING COLOUR TEMPERATURE ...................................................................................... 51
11.5 PICK A COLOUR ............................................................................................................... 51
11.6 PALETTE ........................................................................................................................ 52
11.7 CHROMATICITY DIAGRAM ................................................................................................... 53
11.8 OLD AND NEW SWATCHES .................................................................................................. 54
11.9 OPTIONS ....................................................................................................................... 54
11.10 DALI TYPE 8 .............................................................................................................. 55
12 ROUTING ENTRIES ...................................................................................................... 56
12.1 HOW TO VIEW ROUTING ENTRIES IN THE DEVICES VIEW ............................................................ 56
12.2 HOW TO SET UP A SCENE LINK ............................................................................................. 56
12.3 HOW TO SET UP PRESENCE DETECTION .................................................................................. 58
12.4 CREATE A CONSTANT LIGHT ROUTING ENTRY: SIMPLE SET-UP....................................................... 59
12.5 CREATE A CONSTANT LIGHT ROUTING ENTRY: MORE COMPLEX SET-UP ............................................ 59
13 LOGIC PROGRAMMING DATA DISTRIBUTION, LOGIC AND GROUP HOUSEKEEPING
TOOLS ................................................................................................................................. 63
13.1 LOGIC DATA DISTRIBUTION AND HOUSEKEEPING TOOLS .............................................................. 63
13.2 LOGIC DATA DISTRIBUTION IN DESIGNER ............................................................................... 63
13.3 WHEN TO USE LOGIC HOUSEKEEPING TOOLS ........................................................................... 64
13.4 ACCESSING LOGIC HOUSEKEEPING TOOLS ............................................................................... 65
13.5 ADD; PRUNE; CLEAN ........................................................................................................ 65
13.6 GROUP INFORMATION HOUSEKEEPING.................................................................................... 68
13.7 LIMITS ON NUMBER OF LOGIC ITEMS IN A WORKGROUP .............................................................. 68
13.8 GROUP INFORMATION HOUSEKEEPING.................................................................................... 69
14 TEMPORARY MIN & MAX SETTINGS ........................................................................... 70
14.1 TYPICAL APPLICATIONS OF TEMPORARY MINIMUM AND MAXIMUM ................................................. 70
14.2 BACKGROUND OPERATION .................................................................................................. 70
14.3 WHAT HAPPENS WHEN TEMPORARY LEVELS ARE DISABLED? ......................................................... 70
14.4 CAN TEMPORARY MAXIMUM AND MINIMUM LIMITS BE USED WITH REDIRECTS? ................................ 70
14.5 PRIORITY ....................................................................................................................... 71
14.6 ARE TEMPORARY MAXIMUM AND MINIMUM LEVELS ABSOLUTE? .................................................... 71
14.7 TEMPORARY MAXIMUM LIMIT FOR LOAD SHEDDING: SLOW FADE RECOMMENDED. ............................... 71
14.8 TEMPORARY MINIMUM LIMIT (E.G. FOR ALARMS): SHORT FADE TIME RECOMMENDED. ......................... 71
14.9 HOW TO SET AND ENABLE A TEMPORARY LIMIT TO A LOAD .......................................................... 71
14.10 TRIGGERING TEMPORARY MAXIMUM AND MINIMUM ............................................................... 71
14.11 EXAMPLE: PROGRAMMING AND APPLYING A TEMPORARY MINIMUM LEVEL TO A GROUP. .................. 72
15 UPLOAD ....................................................................................................................... 75
rEVE Rev 1.3

15.1 WHAT IS UPLOAD FOR ....................................................................................................... 75

15.2 DIFFERENCES FROM V4 ...................................................................................................... 75
15.3 RECOMMENDED BEST PRACTICE............................................................................................ 76
15.4 DEVICE ALERTS ............................................................................................................... 77
15.5 MATCH AND EQUIVALENT ITEMS .......................................................................................... 78
15.6 STANDARD UPLOAD .......................................................................................................... 79
15.7 CREATE AND UPLOAD ........................................................................................................ 80
15.8 STILL WANT TO UPLOAD AS BEFORE? .................................................................................... 81
rEVE Rev 1.3

1 Purpose of this document

This document is a meant as a reference guide for the basic setup of a Designer version 5 system
and its most commonly used features and operations.

People using this document should be familiar with the architecture and topology of a Helvar router
system with a good understanding of IP subnetting.

Previous version 4 knowledge is recommended but not necessary

2 Supported Operating Systems

Designer 5 is supported on the below operating systems:
- Windows 7, SP1
- Windows 8, 8.1
- Windows 10
rEVE Rev 1.3

To determine which IP settings is best to use for a router system, a good understanding of single
and multi-cluster is initially required.

3 Single cluster and multi-cluster Workgroups.

Whether a system should be a single-cluster or multi-cluster Workgroup depends on:

- Number of routers
- Physical location of routers
- Whether the Ethernet network is unmanaged or managed

This section describes three typical Workgroups and gives example IP settings for the routers and
the PC client.

3.1 SITUATION 1
Single cluster Workgroup on separate, unmanaged network
SMALL TO MEDIUM SYSTEMS: 2 to 10 routers on an independent, unmanaged Ethernet network (not
a network managed by the building's IT team)

Most likely one distribution board; routers controlling lighting on a single floor.

Single-cluster network.
Routers use the same cluster comms port.
Routers have same IP addresses apart from fourth octet.

Here are example settings for four routers in a single-cluster workgroup on an unmanaged network:

Router IP Router subnet Cluster comms Cluster mask

address mask port
Router 1 10.254.10.1 255.0.0.0 60005 255.255.255.0
Router 2 10.254.10.2 255.0.0.0 60005 255.255.255.0
Router 3 10.254.10.3 255.0.0.0 60005 255.255.255.0
Router 4 10.254.10.4 255.0.0.0 60005 255.255.255.0

PC Client: 10.254.254.99, subnet mask 255.0.0.0

In this system, each router communicates with all other routers, via the same cluster comms port
(60005, the default cluster comms port).
rEVE Rev 1.3
rEVE Rev 1.3

3.2 SITUATION 2:
Multicluster Workgroup on separate, unmanaged network
This example has several routers in different parts of a building, and routers on an independent
unmanaged Ethernet network (not managed by the building's IT team). The location of the routers in
the building makes it logical to put routers in different clusters.

The different clusters of routers are located:

- on different floors
- at the various distribution boards available

In a multi-cluster Workgroup:
Routers use various cluster comms ports: one cluster comms port per cluster.
Routers in the same cluster have IP addresses with the same 3rd octet.

PC IP settings
IP address: 10.254.254.99
Subnet mask: 255.0.0.0 (or 255.255.0.0)

FLOOR 3 routers Router IP Router subnet Cluster Cluster mask

address mask comms port
Router 9
(Primary Master) 10.254.3.1 255.0.0.0 61003 255.255.255.0
Router 10
(Secondary Master) 10.254.3.2 255.0.0.0 61003 255.255.255.0

FLOOR 2 routers Router IP Router subnet Cluster Cluster mask

address mask comms port
Router 5
(Primary Master) 10.254.2.1 255.0.0.0 61002 255.255.255.0
Router 6 10.254.2.2 255.0.0.0 61002 255.255.255.0
Router 7 10.254.2.3 255.0.0.0 61002 255.255.255.0
Router 8
(Secondary Master) 10.254.2.4 255.0.0.0 61002 255.255.255.0

FLOOR 1 routers Router IP Router subnet Cluster Cluster mask

address mask comms port
Router 1
(Primary Master) 10.254.1.1 255.0.0.0 61001 255.255.255.0
Router 2 10.254.1.2 255.0.0.0 61001 255.255.255.0
Router 3 10.254.1.3 255.0.0.0 61001 255.255.255.0
Router 4
(Secondary Master) 10.254.1.4 255.0.0.0 61001 255.255.255.0

The routers on each floor:

- are in their own cluster
- can communicate with every other router in this cluster (via the cluster comms port)

Not every router in the cluster can communicate directly with routers in other clusters. This helps to
reduce total system communications traffic, by localising most communications within clusters.
The master routers (Primary master and Secondary master) can communicate with other clusters.
rEVE Rev 1.3

Floor 3
Router 9 IP: 10.254.3.1
Router 10 IP: 10.254.3.2
Cluster Comms Port: 61003

The routers on this floor:

- are in their own cluster
- communicate with each
other via the 61003 cluster
comms port.

Floor 2
Router 5 IP: 10.254.2.1
Router 6 IP: 10.254.2.2
Router 7 IP: 10.254.2.3
Router 8 IP: 10.254.2.4
Cluster Comms Port: 61002

The routers on this floor:

- are in their own cluster
- can communicate with
every other router in this
cluster (via the 61002
cluster comms port)

Floor 1
Router 1 IP: 10.254.1.1
Router 2 IP: 10.254.1.2
Router 3 IP: 10.254.1.3
Router 4 IP: 10.254.1.4

Cluster Comms Port: 61001

The routers on this floor:

- are in their own cluster
- can communicate with
every other router in this
cluster (via the 61001
cluster comms port)

Communications between clusters

Not every router in the cluster can communicate directly with routers in other clusters. This helps to
reduce total system communications traffic, by localising most communications within clusters. The
master routers (Primary master and Secondary master) can communicate with other clusters.
rEVE Rev 1.3

3.3 SITUATION 3:
Single-cluster network with varying IP clusters in a managed
network
SMALL TO MEDIUM SYSTEMS: 2 to 10 routers on a managed Ethernet network, which is a network
managed by the building's IT team. The IT administrator has specified the IP addresses and subnet
masks for the Helvar routers (so you cannot choose a standard set of IP addresses).

Most likely 1 distribution board; routers controlling lighting on a single floor.

Single-cluster network, with varying IP cluster sets.

Routers use the same cluster comms port.
Routers have the IP addresses specified by the IT administrator. These addresses might have
different values for the 3rd octet.

PC Client: 10.254.254.99, subnet mask 255.0.0.0

Router IP Router subnet Cluster comms Cluster mask

address mask port
Router 1 10.254.10.1 255.0.0.0 60005 255.255.0.0
Router 2 10.254.12.2 255.0.0.0 60005 255.255.0.0
Router 3 10.254.13.1 255.0.0.0 60005 255.255.0.0
Router 4 10.254.15.2 255.0.0.0 60005 255.255.0.0

Note that the cluster mask for all routers is 255.255.0.0, because the cluster mask needs to allow
communication across the range of IP addresses of the routers.

In this system, each router communicates with all other routers, via the same cluster comms port.
rEVE Rev 1.3

3.4 Clusters: cluster masks and Router IDs

The cluster mask determines which parts of a router’s IP address make up the cluster, and which
parts of the router’s IP address make up the Router ID (within the cluster).

These are examples of three different cluster masks and how they affect which clusters a router is in.

Cluster mask example 1:

Cluster mask: 255. 000. 000. 000

Router IP address: 10. 254. 10. 1

CLUSTER Router ID

The cluster mask is 255.0.0.0. The Router IP address is 10.254.10.1.

The router is in cluster ‘10’ and the ID of the router (in cluster 10) is 254.10.1.

Cluster mask example 2:

Cluster mask: 255. 255. 000. 000

Router IP address: 10. 254. 10. 1

CLUSTER Router ID

The cluster mask is 255.255.0.0. The Router IP address is 10.254.10.1.

The router is in cluster ’10.254’ and the ID of the router (in cluster 10.254) is 10.1.

Cluster mask example 3:

Cluster mask: 255. 255. 255. 000

Router IP address: 10. 254. 10. 1

CLUSTER Router ID

The cluster mask is 255.255.255.0. The Router IP address is 10.254.10.1.

The router is in cluster ’10.254.10’ and the ID of the router in cluster (10.254.10) is 1.
rEVE Rev 1.3

3.5 Primary Master and Secondary Master routers

Within a cluster of Helvar routers, all routers communicate with each other. Communications from
other routers are handled by the Primary Master router in a cluster. The Primary Master router is the
router with the lowest IP address in a cluster. The Secondary Master router is the router with the
highest IP address in a cluster.

In multi cluster configuration, all routers are aware of the primary master in the other clusters. When
any router needs to communicate to another cluster it will target the primary master of that cluster
then the primary will communicate that message within its own cluster.

What happens if the Master router fails?

The primary master will be replaced automatically by the next lowest IP router in the cluster, a
secondary master will be replaced automatically by the next highest IP router in the cluster.
rEVE Rev 1.3

3.6 Before you connect: prepare your PC and Helvar routers to Go

Online
Windows Firewall settings
IP settings for the client PC and Helvar routers
Start Designer software; check network interface settings
Edit the routers' IP addresses
Connect to a Workgroup

Note:
If the Helvar routers are on a managed network (that is, not on a separate Ethernet network solely
for Helvar routers), consult the IT Administrator for IP settings and firewall options.

3.7 Windows Firewall settings

To prevent Windows Firewall from blocking Designer 5 communicating with Helvar routers, do the
following:
• Network settings (Control Panel > System and Security >
• Allow a program or feature through Windows Firewall.
• Click 'Change settings'.
• Scroll down the list of programs and find 'Helvar Designer' and allow in Domain, Home/Work
(Private) and Public.
You may need to click the 'Details...' button to view the Designer version number.

3.8 IP settings for the client PC and Helvar routers

The instructions here are for a one-router system.

Example: One router

Windows 7 PC, connected via Ethernet cable directly to a Helvar 920 router.
The Ethernet network is separate and not connected to other IT networks.
Windows PC network card IPv4 address: 10.254.0.99; Subnet mask 255.0.0.0
Router IP address: 10.254.0.1, subnet mask 255.0.0.0

3.9 Set your Windows PC network card IPv4 address.

This example uses Windows 7, and the IP addresses selected for Example 1 and Example 2.

• Start > Control Panel > Network and Sharing Center > Change Adapter Settings.
• Right-click the network adapter you want your PC to use to connect to the Helvar workgroup,
and choose Properties
• Double-click "Internet Protocol Version 4 (TCP/IPv4)".
• Select "Use the following IP address:"
• Enter 10.254.0.99
• Subnet mask: 255.0.0.0
• Click 'OK'.

3.10 Change the IP settings of the Helvar router.

Note: make sure the IP settings of all Helvar routers in a Workgroup have been decided as part of an
overall system plan. Do not change the IP settings of a Helvar router after you have started
programming it with lighting control system information and commands.
rEVE Rev 1.3

With your PC connected to the Helvar router via Ethernet, do the following:

• Start Designer 5.

• Put Designer 5 into Advanced Mode.

• Check network interface settings

o Check network interface settings and set 'Sync Router Time' to true.
o Select the 'Workgroup' in the device tree, and in the 'Properties' View, in the IP
Settings section, select 10.254.0.99 (the IP address you have just set for the PC
network adapter).
o In the 'Time and Location' section,
o Sync Router Time: Set this to true.
o See 'Time Synchronisation'
o Click 'OK'.

• Select a Helvar router and change its IP settings

o Select a Helvar router
o Near the bottom of the Designer 5 screen, in 'Routers View', you will see a router, or
list of routers.
o Select one of the routers (the background of the row in Routers View should turn
blue).
o In 'Properties View', in the IP Settings section, change/check these settings:
o Address: 10.254.1.10
o Subnet mask: 255.0.0.0
o [You can also change the router's Workgroup if you like: edit the 'Workgroup Name'.]
o Click 'OK' (the Helvar router will now reboot)
o The router will disappear from 'Routers View' and appear again, this time with the
updated IP settings. Other settings can be left unchanged.

These settings were the default settings when setting up this router and are listed for reference.
Address: 10.254.1.10
Subnet Mask: 255.0.0.0
Gateway: 0.0.0.0
Cluster Mask: 255.255.255.0
Cluster Comms Port: 60005
Cluster ID: 10.254.1.10 (same as 'Address'; greyed out)
Cluster Member ID: 0.0.0.10 (greyed out)
Broadcast Discovery Message: Enable
Disco Broadcast Message: 255.255.255.255
Multicast Discovery Message: Disable
Disco Multicast Address: 239.0.0.1
rEVE Rev 1.3

4 Design file backup

What is a Design file?
A Design file is a backup of your workgroup system and can also act as a simulation of the system if
you are opening it offline.

When to back up the Workgroup design (the design file)

- It is good practice to make regular backups of each Real Workgroup in the network, so that,
if the system fails, you can use the backup to restore the system to working condition.
- Before replacing a faulty device.
- Before entering Upload Mode.

How to save a Workgroup design (in Offline mode)

If the Workgroup Design is a new design, then click file> save as or this icon to open the save
as dialog box. Browse for a folder and type in a different filename, if required, then click Save to save
the Workgroup Design.

For an existing Workgroup Design, click File> Save or this icon , Designer saves the changes to
the previously stored design file.

How to save a Design file for a real Workgroup (in Online mode).

1. Go Online
Connect to the Real Workgroup that you wish to back up.

2. Click to save the Workgroup. Use the "Save As" dialogue box to save the .design file.

Backing up the Design file before replacing a faulty device.

If you are making a backup before replacing a faulty device, save the Design file as a new file. This is
because the backup may not include the data that was stored in the faulty device.
rEVE Rev 1.3

4.1 Autosave of the .design file

The Design file is saved every 5 minutes if Designer is online.
When Designer goes offline, a backup file of the Designer file is saved.

The progress bar indicates when Designer is saving data or making alterations to the Design file.

Autosave and Backup location

Both are saved in the Designer Repository which can be accessed directly from the top menu using

this icon or in :\Users\USERNAME\Documents\Helvar\Designer

Note
Designer 5 also saves a backup of the current Workgroup when you go offline. This makes it
important to 'Go Offline' before closing down Designer, rather than just unplugging the Ethernet
cable, or disconnecting from the network, or shutting down the laptop when you have finished
using Designer.

Backing up the Design file

It is good practice to make regular backups of the Design file, immediately before, during and
immediately after making programming changes.
The Maintaining a .design file backup offsite is recommended,
rEVE Rev 1.3

5 Go Online: Connect to a Workgroup

Before going online with Designer 5, make sure the PC and the Workgroup routers are correctly set
up. See: Section 3 of this document for guidance on IP setup

You 'Go Online' with Designer 5, so that you can see what is on the lighting control network and
monitor and edit (programme) the lighting control system.

5.1 Time synchronisation

When Designer 5 goes online with a Workgroup, you can update the Workgroup's time and date
settings to match the PC's time and date.

If a lighting router system has not been connected to a PC for a while, it is a useful way to make sure
the time and date are correct.
This is particularly important for systems with scheduled events, such as systems which open and
close blinds at times related to sunrise and sunset.
Time synchronization is essential for the more advanced training exercises, because you will need to
change the router system time in order to check that certain schedules and time conditions have
been applied or not.

5.2 How to set 'Synchronise Time' to true by default

You can set 'Synchronise Time' as the default option, so that every time Designer 5 connects to a
Workgroup, the workgroup's routers' time and date settings synchronise with the PC's time and date
settings.

If 'Synchronise Time' is not set as the default, every time you Go Online in Designer 5, you still have
the option to select 'Synchronise Time' using a tick box.

1. Set 'Synchronise Time' to True by default.

1. By default, the Time Synchronisation feature is set to 'False'.
2. Before you Go Online, in the Designer Interface, select Tools > Options >
Synchronise Time.

3. From the drop-down menu, choose True, and click OK.

4. Now, 'Synchronise Time' is set to 'True' by default.
rEVE Rev 1.3

5.3 Go Online: Connect to the Workgroup

1. Select 'Go Online'

1. Click the 'Go Online' icon in the Designer 5 toolbar.

You can also use the File menu (press the 'Alt' key on a PC keyboard and use the down arrow, then
'Enter')

Select Workgroup; Network Interface; Synchronise Time

1. In the 'Connect to Workgroup' dialogue window, select a Workgroup.

If your PC has more than one Network Interface, you can select a different network interface to use
to connect to the Workgroup.
You can choose to synchronise the Workgroup date and time with the PC date and time: use the
check box.
rEVE Rev 1.3

2. Click 'OK'

Designer software will connect to the system and routers will be discovered

Note: Progress is shown in the bottom right of the software.

rEVE Rev 1.3

6 Identifying routers, load interfaces, control devices,

input units and subnets
6.1 Identify a router
To identify a router, select the router (in Routers View when offline, or in Devices View when online),
and right-click > Identify.
The four lights on the front of the router will flash. To cancel identification, click the ‘cancel
identification’ button.

6.2 Identify a device: load interface

To identify a device, select the device in Devices View, right-click > Identify.
The device will begin flashing (or toggling on/off). When identifying a device you have these options
in the Identify View:

Lamp icon: flashes to when ‘Identify’ in progress

The lamp icon is shown, whichever device you choose. Three lamps are shown if you are
identifying subnet.

Device information
Device name and address (Router IP and DALI address)

Maximum
Identify device(s) by setting to their maximum level.
For relays, if you select ‘Off’ then ‘Maximum’ you can manually toggle to identify the relay.

Minimum
Identify device(s) by setting to their maximum level.
Note that DALI minimum level is not zero, and is usually 1% by default.
rEVE Rev 1.3

Cancel Toggle Or Flash (Toggle or Flash)

Click to stop the repeated switching on and off of a load that is being identified.
Click 'Toggle or Flash' to reactivate.

Off
Identify device(s) by switching it off (0%).

Apply Name and/or Group (F7)

Apply to a device the name and group settings entered in the 'Settings' section.

Settings

Update rate:
Make the identified lamp flash faster or slower (or change the intervals between a relay
opening and closing).The default rate is 1 second.
Group:
Add a device to a group. Enter a group number, and click the 'Apply Name and/or Group'
button above. The device will be added to that group.
Name:
Rename a device. Enter a device name, and click the 'Apply Name and/or Group' button
above. The device will be renamed.
Identify relays:
Prevent relays from being identified, or allow them to be identified.
Set 'Identify Relays' is set to 'False' to stop Designer 5 identifying relays.
This function is permanently disabled at identify subnet level.
rEVE Rev 1.3

6.3 Apply Name And/ Or Group

To speed up commissioning, you can use the 'Apply Name and/or Group' Identify function to identify,
name and group devices.

1. In the Devices Tree, select the first device in a subnet.

2. Right-click > Identify
3. In the Identify window, in Settings, enter the groups and name for the device.
4. Click the 'Apply Name and/or Group' button
5. Select the next device in the Device Tree and repeat from step 1.

6.4 Identify a device: control device (e.g. button panel)

To identify a control device, such as a button panel, in Devices View, right-click > Identify.
A green LED will flash on the button panel.

6.5 Identify a device: input unit

To identify an input unit, such as a 440 Input Unit, 444 Mini Input Unit, 445 Switch Interface or 492
Analogue Input Unit, you need to check the serial number on the actual unit against the serial
number in the Properties window (select the device in Devices View and look in the Properties View).
rEVE Rev 1.3

6.6 Identify: subnet

To identify all load interfaces and control devices on a subnet, in Devices View, select the DALI
subnet and right-click > Identify.
Devices on the subnet will begin flashing (or toggling on/off). When identifying a subnet you have
these options in the Identify View:

Lamp icons: flashes to when ‘Identify’ in progress

Three lamps are shown if you are identifying subnet.

Subnet information
Subnet name and address (Router IP and subnet number)

Maximum
Identify subnet by setting all load interfaces to their maximum levels.

Minimum
Identify subnet by setting all load interfaces to their minimum levels.
Note that DALI minimum level is not zero, and is usually 1% by default.

Cancel Toggle Or Flash (Toggle or Flash)

Click to stop the repeated switching on and off of loads on the subnet being identified.
Click 'Toggle or Flash' to reactivate.

Off
Identify subnet by switching devices off (0%).

Apply Name and/or Group (F7)

Apply to the first device in the subnet the name and group settings entered in the 'Settings'
section.
rEVE Rev 1.3

Settings

Update rate: Make the lamp flash-rate faster. The default rate is 1 second.

Group:
Add the first device in the subnet to a group. Enter a group number, and click the
'Apply Name and/or Group' button above.

Name:
Rename the first device in the subnet. Enter a device name, and click the 'Apply
Name and/or Group' button above.

Identify relays:
This function is permanently disabled at identify subnet level..
rEVE Rev 1.3

7 Groups view
7.1 Groups view: overview
Groups view is used for the following:

- View which devices and logic items are in a group (all modes)
- Create and delete groups (Advanced and pro modes)
- Adding devices to a group (Advanced and pro modes)
- Removing devices from a group (Advanced and pro modes)
- Monitoring cluster and router memberships (Pro mode)
- Monitoring the last scenes in blocks and groups (Pro mode)
rEVE Rev 1.3

7.2 Viewing devices in a group using the groups view

To show the Groups View: View > Groups or
Use the icon in the main toolbar.

View devices in a group

Double-click a group to view the devices in it.
The group name is shown in the window title bar, and the devices in that group are listed.
For each device you can see:
- Device description (this can be changed, unlike ‘Device type’)
- Address (IP address and DALI subnet address)
- Type: Type of device (this information cannot be edited)
- Information: any additional information on the device

Groups view: Pro mode

In Pro mode in Groups view (Ctrl + Shift + G; or View > Groups), the Router members column shows
the Cluster Members and the router IDs of routers.

Cluster members: shows the IP addresses of routers which are in a cluster

Router members: shows the router IDs of routers in which each group exists. To view/change a
router ID, select the router in the Device Tree or Routers View and view the Properties window.
Last Scenes in Blocks
Last Scene in Group
NSR means that no scene has been recalled in a block (No Scene Recalled).

Note: Designer does not keep a record of this data when going offline or request it when
going online. The data will populate as the scenes trigger when Designer is online.
rEVE Rev 1.3

7.3 Create groups in Groups view: +

In the Groups view, click the + sign to add a group.

Create multiple groups in Groups view: shift and +

In the Groups view, hold shift, and click the + sign to add multiple groups

Enter how many groups you want to create and at which group number, and click ‘OK’. The
description is appended with the group number
rEVE Rev 1.3

7.4 Putting devices into groups

You can put devices into groups by using Group view and drag and drop, or using the devices’
properties windows.

Drag devices into groups

a) Method 1 (Drag from Device Tree into group name):

Select a device (or select multiple devices, using Ctrl or Shift click) in the Device Tree into
a group. Drag it/them onto the group name in the group view.

b) Method 2 (Drag from Device Tree into open group):

With the group ‘open’, drag another device into the group view (i.e. drag a device into
the group window showing the list of devices in that group).
rEVE Rev 1.3

7.5 Editing groups using a device’s properties window

a) Show device properties

Select a device in the Device Tree. The properties window should be displayed. If not, press
F4 (or View > Properties)
rEVE Rev 1.3

b) Add the device to a new group

In the Properties window, in the Groups field, type in ‘3’, and click ‘OK’

The device is added to that group.

c) Append (by number) the device to a new group (using the Properties window)
In the Properties window, in the Append by Number field, type in ‘4’, and click ‘OK’

Append (by Name) the device to an existing group (using the Properties window)
d) In the Properties window, in the Append by Name field, you can select a the name of a group
to add the device(s) to, and click ‘OK’
rEVE Rev 1.3
rEVE Rev 1.3

7.6 Copying / Pasting Device Properties

a) Copy a device in the Device Tree

In the Device tree, select a device.

b) Right-click and select ‘copy’.

c) Paste the device properties onto another device of the same type.
d) In the Device tree, select a similar device and right-click and select ‘paste’.
The device properties are copied to the new device.

7.7 Delete Groups

In the Group view [ (View > Group), or press F6 ], right-click a group, and select ‘Delete’.
rEVE Rev 1.3

7.8 Group Memberships (Pro mode only)

a) It is important to understand the group memberships as they determine where group
messages get sent.

Groups have two sets of memberships:

- Cluster memberships
These determine which clusters the group’s messages get sent to.
Router memberships
These determine which routers within a cluster the group’s messages get sent to.

b) The group membership data can be found in the properties of each group or in the groups
view.
rEVE Rev 1.3

7.9 Last Scenes in Blocks

The Last Scenes in Blocks for a particular group can also be monitor in Designer and in the
same way as the group memberships.

This shows, for the 8 blocks of 16 scenes, the last scene recalled.
For example: 12;8;1;NSR;NSR;NSR;2;NSR
NSR means that no scene has been recalled in a block (No Scene Recalled).

Note: Designer does not keep a record of this data when going offline or request it when
going online. The data will populate as the scenes trigger when Designer is online.
rEVE Rev 1.3

7.10 Last Scene in Group

The Last Scene in Group shows the last scene in that group that was recalled, or ‘No Scene
Recalled’.

View Last Scenes in Blocks and Last Scene in Group in Properties window
You can also view Last Scenes in Blocks and Last Scene in Group in the Properties window of
the group (select the group in the Device Tree)

7.11 When groups exist in routers

A group exists in a Helvar router:

- If a device is assigned to a new group: the group is created on the same router as the
device is connected to.
- If a router needs to know about it because the group is needed for a logic item to
function.
 rEVE Rev 1.3

8 0.1% Dimming Resolution

Designer 5 allows for 0.1% dimming resolution.
This is particularly useful for lower levels of dimming of LEDs.
If the device allows for 0.1% dimming resolution, you can use this resolution when setting the
device's levels in the Properties View and Scene Table.

8.1 How do I know if a load interface device offers 0.1% dimming

resolution?

1. In Designer 5, select the load interface device in the Devices Tree, and right-click > Properties.
2. In Properties View, look at the "Physical Min. Level".

3. If the value is "0.1%", the device should be capable of 0.1% dimming resolution.
If the value is "1.0%", the device does not offer 0.1% dimming resolution.
rEVE Rev 1.3

8.2 How to set levels to 0.1% resolution

You can set levels with 0.1% dimming resolution in two Views:

- the Properties View of a load interface (minimum and maximum levels)

- the Scene Table (Scene Levels).

Setting level values with 0.1% resolution in Properties View

For example for a 454 dimmer channel or DALI Type 8 LED driver, you can set these values with
0.1% resolution:

In the Scene Table

Scene Level

In Properties View
Min. Level
Max. Level
Temporary Absolute Min Level
Temporary Absolute Max Level
Note: the lowest value for 'System Fail Level' and for 'Power On This Channel To' is 1%.
rEVE Rev 1.3

8.3 Example: How to set minimum and maximum level DALI Type 8
Colour LED Driver
Check that Designer 5 is in Editor Mode, or Advanced Mode or Pro Mode.
1. In Devices Tree, right-click the DALI Colour LED driver and select 'Properties'.

2. In Properties View, in the 'Load Levels' section:

- in Min. Level, type 0.2
- in Max. Level, type 99.9

3. Click 'OK'.
rEVE Rev 1.3

8.4 Example: How to set Scene Level for a DALI Type 8 Colour LED
Driver and a 454 dimmer channel
In this example, the LED Driver and the 454 Dimmer channel are in Group 80.

1. Check that Designer 5 is in Editor Mode, or Advanced Mode or Pro Mode.

2. In Groups View, click Group 80.

3. In the Scene Table (View > Scene Table), find the DALI Colour driver and Dimmer channel in the
'channel' row.

4. In the row 'Group 80 Scene 1.2', type the value '0.6' for the Dimmer channel, and type '0.3' for the
DALI Colour LED.

4a. You can use the Intensity View to adjust Scene levels (Intensity levels). View > Intensity and use
one of the sliders, or enter a specific value.

5. Click 'OK'.
rEVE Rev 1.3

9 Colour Control and Colour Temperature in the Scene

Table
Note: Colour scenes are supported in block 1 only. Power on to last colour is not supported; setting a
scene condition called at power up could be a possible alternative.

9.1 Scene Table

The Designer 5 Scene Table shows colour (or colour temperature) as well as level (intensity) in a
scene

Colour Temperature
As you adjust the colour in Colour Temperature View, it changes the colour temperature of the icon in
the selected Scene in the Scene Table.

RGB Colour
As you adjust the colour in Colour View, it changes the colour of the icon in the selected Scene in the
Scene Table.

Ignore
rEVE Rev 1.3

Colour can be ignored, which is shown as a red cross

Copying and pasting colour and intensity

Colour and Level can be copy/pasted either separately or together

9.2 Copy and Paste Intensity

Select a cell or cells in the Scene Table, and then click the Copy Intensity icon to copy the
Intensity (‘level’) value to the clipboard.
Select a cell or cells in the Scene Table, and then click to paste the copied value to the selected
scene(s).
Note: You can also copy and paste levels values from/to a spreadsheet program, such as MS Excel.

9.3 Copy and Paste Colour settings

Select a cell or cells in the Scene Table, and then click the Copy Colour icon to copy the Colour
settings (Colour and Colour Temperature) to the clipboard.
Select a cell or cells in the Scene Table, and then click the Paste Colour icon to paste the copied
settings to the selected scene(s).
rEVE Rev 1.3

9.4 Copy and Paste Intensity and Colour settings

Select a cell or cells in the Scene Table, and then click the Copy Intensity and Colour icon to
copy the Intensity and Colour settings (Colour and Colour Temperature) to the clipboard.
Select a cell or cells in the Scene Table, and then click the Paste Intensity and Colour icon to
paste the copied settings to the selected scene(s).

9.5 Change column width

The column width can be changed, to fit more channels.

rEVE Rev 1.3

10 Programming Tuneable White drivers

Designer 5 allows for control of tuneable white LED drivers, which must be DALI 8 compliant.

Warm and cool colours

Cool colours (bluish white) are colour temperatures over 5000 Kelvin (K).
Warm colours (yellowish light through to red) are lower colour temperatures of about 2700 to
3000 Kelvin.

10.1 What are the colour parameters of a tuneable white LED

driver?
You can see which colour temperatures the LED driver is capable of in two places in Designer 5:

Properties View

In the Devices Tree, right-click the tuneable white device and select Properties. At the bottom of the
Properties window, you will see these properties:

Property Notes
Colour system: For Tuneable White LED drivers, this should
include the text ‘Colour Temperature’
Coolest Colour Temperature: If the device allows, you can set the upper
limit (in Kelvin) for colour temperature
Physical Coolest Colour The highest Kelvin rating that the LED driver
Temperature: is physically capable of.

Warmest Colour Temperature: If the device allows, you can set the lower
limit (in Kelvin) for colour temperature.
Physical Warmest Colour The lowest Kelvin rating that the LED driver
Temperature: is physically capable of.
Primary Count: The number of different colour light sources
within the device.

NOTE: It is currently not a compulsory part of the DALI standard to communicate these settings to
the router therefore it is possible the values for each field are not populated.
rEVE Rev 1.3

10.2 Colour Temperature View

To open Colour Temperature View:

- Make sure the LED driver is in a group. In this example, the LED driver is in Group 80.
- In Groups View (View>Groups, or Ctrl+Shift+G), select a group which contains the device you
want to view properties for.
- In the Scene Table (View > Scene Table or Ctrl+T), select a scene in the LED driver’s column (in
the example below, scene 1.3)

- In the Colour Temperature View (View > Colour Temperature), you can see the colour
temperature settings for the selected Scene. If ‘Allow non-gamut temps" is unticked, black lines
should show the physical warmest and physical coolest colour temperatures of the driver.

-
NOTE: It is currently not a compulsory part of the DALI standard to communicate the warmest and
coolest colour limits to the router therefore it is possible the gamut (black lines) will not appear if that
is the case.
rEVE Rev 1.3

10.3 Setting colour temperature levels of a tuneable white LED

driver
Open Colour Temperature View:
- Make sure the LED driver is in a group. In this example, the LED driver is in Group 80.
- In Groups View (View>Groups, or Ctrl+Shift+G), select a group which contains the device you
want to view properties for.
- In the Scene Table (View > Scene Table or Ctrl+T), select a scene in the LED driver’s column (in
the example below, scene 1.3)

In the Colour Temperature View (View > Colour Temperature), you can see the colour temperature
settings for the selected Scene. If ‘Allow non-gamut temps" is unticked, black lines should show the
physical warmest and physical coolest colour temperatures of the driver.
rEVE Rev 1.3

10.4 Colour Temperature View: Adjusting Colour Temperature

Use one of these methods to adjust the colour temperature for the scene:

Palette
Select one of the predefined colour temperature swatches, or create your own colour
temperature swatch. Click OK in the Scene Table to apply the change.

Colour Temperature slider

Move the cursor to pick a colour temperature. Click OK in the Scene Table to apply the change.

Mired
Type in the colour’s mired value (microreciprocal degrees) [more details
https://en.wikipedia.org/wiki/Mired ]

K: kelvin
Type in the colour temperature in kelvins

Note: as you adjust a colour temperature, the following linked items all change:
- position of the cursor
- colour temperature mired value
- colour temperature K value
- Scene Table swatch colour
- position of the cursor in the Colour Temperature View

As you select colour temperatures, the Colour view cursor moves to the black body locus (Planckian
locus) on the Chromaticity Diagram.
rEVE Rev 1.3

10.5 Palette

Select a swatch in the palette to pick a scene colour temperature (then click OK in the Scene Table)
The palette contains predefined swatches representing colour temperatures and custom colour
temperatures.

Predefined swatch colour temperatures

The predefined swatch colour temperatures range from 1700 K to 50000 K.
You cannot delete or adjust a predefined colour temperature swatch.

To move a colour temperature swatch up or down the palette click the UP or DOWN controls (up and
down arrows above the palette).

Custom (user-defined) swatch colour temperatures

You can create custom swatch colour temperatures and save them in the palette.
These custom colour temperatures are saved when you save a Workgroup Design.

To create a custom swatch colour temperature select a colour temperature on the slider or enter a
value in the Mired or K windows, and click the + control above the palette.

To delete a custom swatch colour temperature select a custom swatch colour temperature in the
palette, and click the – above the palette.

To move a swatch up or down the palette click the UP or DOWN controls (up and down arrows above
the palette).

To rename a custom swatch select the swatch name and click once (or press F2), type the new
name, and then press Enter.

Slider
Click and drag the cursor to pick a colour temperature. You can also use the mouse wheel, and the
cursor keys. Click OK in the Scene Table to apply the change.
The black lines in the slider show the device’s gamut: see Allow non-gamut temps.

Mired
Type in the colour's mired value (micro reciprocal degrees). The mired value is given by: M = 100000
/ T , where T is the colour temperature in kelvins.
Note: The SI unit is the reciprocal megakelvin (MK−1), shortened to mirek.

K: kelvin
Type in the colour temperature in kelvins.
rEVE Rev 1.3

10.6 Options
Ignore
If ignore is selected and this scene is recalled, the colour of the lamp will not change from previous
recalled colour. In the Scene Table, a box with a cross will appear on the left of the currently
selected scene/channel cell.
The Ignore setting in the Colour view is the same as the Ignore setting here.
Note: An asterisk ( * ) displayed on the right of the cell means the level (= intensity) is set to
Ignore.

Allow non-gamut temps

When editing scenes for a ‘live’ colour device, black lines on the slider will show the colour
temperature limits of the device. Click/tick the box to remove the constraint (the limits will be shown
by dashed lines), and allow any colour temperature on the slider to be selected (the cursor can be
moved anywhere within the slider).

11 Programming Colour LED drivers

Designer 5 allows for control of colour LED drivers, which must be DALI 8 compliant.

11.1 What are the colour parameters of a colour LED driver?

You can see what the colour parameters of the LED driver is capable of in two places in Designer 5:

Properties View

In the Devices Tree, right-click the colour LED driver and select Properties. At the bottom of the
Properties window, you will see these properties:

Property Notes
Colour system: For colour LED drivers, this will show ‘Colour
X, Y’
Coolest Colour Temperature: If the device allows, you can set the upper
limit (in Kelvin) for colour temperature
Physical Coolest Colour The highest Kelvin rating that the LED driver
Temperature: is physically capable of.

Warmest Colour Temperature: If the device allows, you can set the lower
limit (in Kelvin) for colour temperature.
Physical Warmest Colour The lowest Kelvin rating that the LED driver
Temperature: is physically capable of.
Primary Count: The number of different colour light sources
within the device.

NOTE: It is currently not a compulsory part of the DALI standard to communicate these settings to
the router therefore it is possible the values for each field are not populated.
rEVE Rev 1.3

11.2 Colour View

To open Colour View:

- Make sure the LED driver is in a group. In this example, the LED driver is in Group 80.
- In Groups View (View>Groups, or Ctrl+Shift+G), select a group which contains the device you
want to view properties for.
- In the Scene Table (View > Scene Table or Ctrl+T), select a scene in the LED driver’s column (in
the example below, scene 1.3)

- In the Colour View (View > Colour), you can see the colour temperature settings for the selected
Scene. If ‘Allow non-gamut colours’ is unticked, a black triangle in the chromacity diagram will
show the colour range of the LED driver.

NOTE: It is currently not a compulsory part of the DALI standard to communicate the colour
range limits to the router therefore it is possible the gamut (black triangle) will not appear if
that is the case.
rEVE Rev 1.3

11.3 Setting colour settings of a colour LED driver.

View the LED drive in Colour View

11.4 Adjusting Colour Temperature

11.5 Pick a colour

Use one of these methods to pick a colour for the scene:

Palette
Select one of the predefined colour swatches, or create your own colour swatch. Click OK in the
Scene Table to apply the change.

Chromaticity Diagram
Move the cursor to pick a colour. Click OK in the Scene Table to apply the change.

Colour co-ordinates
Type in the colour’s X and Y co-ordinates. Click OK in the Scene Table to apply the change.
The colour coordinates represent those of the CIE 1931 xy chromaticity diagram.
To display the grid displaying the XY co-ordinates of the colour, tick the 'Show grid' option.
Note: as you pick a colour, the following linked items all change:
- position of the cursor
- colour coordinates
- 'New' swatch colour
- Scene Table swatch colour
rEVE Rev 1.3

11.6 Palette

Select a swatch in the palette to pick a scene colour (then click OK in the Scene Table)
The palette contains predefined swatch colours and custom swatch colours.

Predefined swatch colours

The predefined swatch colours are red, orange, yellow, lime, green, cyan, pale blue, blue, dark
blue, purple, magenta, pink, white, and turquoise.
You cannot delete or adjust a predefined swatch.

To move a swatch up or down the palette click the UP or DOWN controls (up and down
arrows above the palette).

Custom (user-defined) swatch colours

You can create custom swatch colours and save them in the palette.
These custom colours are saved when you save a Workgroup design.

To create a custom swatch colour select a colour in the X-Y chromaticity diagram or enter
the X-Y colour co-ordinates), and click the '+' control above the palette.

To delete a custom swatch colour select a custom swatch colour in the palette, and click the
'-' above the palette.

To move a swatch up or down the palette click the UP or DOWN controls (up and down
arrows above the palette).

To rename a custom swatch select the swatch name and click once (or press F2), type the
new name and press Enter.
rEVE Rev 1.3

11.7 Chromaticity diagram

Picking a colour
Use the mouse to drag the cursor and select a colour. The colour of the 'New Swatch' and of the
current scene's swatch in the Scene Table will change as the cursor is moved.
Click OK in the Scene Table to apply the new colour to the scene.

Black-body locus (Planckian locus)

The black arc in the Chromaticity diagram represents the possible range of white light as the
colour temperature changes. Note that part or the entire black-body locus may be outside the
device's gamut.
As you select colour temperatures in the Colour Temperature View:
- the changes are shown in the swatch in the scene table, and
- chromaticity information for the device is lost, and the colour changes to a white light at the
selected temperature. This means that in the chromaticity diagram, the cursor moves to the
black-body locus (Planckian locus).
- if the black-body locus is outside the gamut, and 'Allow non-gamut colours' is unticked, it is not
possible to edit colour temperature.

Cursor
Use the mouse to drag the cursor and select a colour. Click OK in the Scene Table to apply the
change.
If "Allow non-gamut colours" is selected (ticked), any colour can be selected in the Chromaticity
diagram.
If "Allow non-gamut colours" is not selected (unticked), you can select only those colours which
the device is physically capable of reproducing (the cursor remains be inside the Device colour
gamut).

Device colour gamut

Use the mouse to drag the cursor and select a colour. Click OK in the Scene Table to apply the
change.
Note: the chromaticity diagram used by Designer 5 is a CIE 1931 xy chromaticity diagram.
rEVE Rev 1.3

11.8 Old and New Swatches

Old
The 'Old' swatch shows the colour currently stored in the scene.

New
The 'New' swatch shows the colour currently selected (but not yet stored).
Click OK to apply the new colour to the scene. The 'New' swatch then becomes the same colour
as the 'Old' swatch.

11.9 Options

Ignore
If this scene is recalled, the colour of the lamp will not change. A crossed-out swatch will be
displayed for this scene in the scene table.
The Ignore setting in the Colour Temperature view is the same as the Ignore setting here.

Allow non-gamut colours

When editing scenes for a ‘live’ colour device, a black triangle on the chromaticity diagram shows
the limits of the colours which the device is capable of showing, and the cursor remains within
these limits.
Click/tick the box to remove the constraint (the gamut will be shown by a dashed line), and allow
any colour on the chromaticity diagram to be selected (the cursor can be moved anywhere within
the Chromaticity Diagram).

Show grid
Show the grid displaying the XY co-ordinates of the colour.
rEVE Rev 1.3

11.10 DALI Type 8

DALI Type 8 brings Colour Control to DALI devices.

DALI Type 8 is a part of the DALI (1) Standard – EN62386 Part 209.

Control gear (ballasts & drivers) are categorised into different types:

DALI Type 0: fluorescent ballasts

DALI Type 6: LED drivers
DALI Type 8: LED Colour Drivers (including RGB colour, and tuneable white)

As with other parts of the DALI standard, any driver that conforms to part 209 will
allow colour control. A driver can support Colour Temperature, RGB, or both.
rEVE Rev 1.3

12 Routing Entries
12.1 How to view routing entries in the Devices View
In Pro mode (see User modes), routing entries affecting devices in a router’s groups are listed in the
device tree for each router in Devices Vies

Put Designer 5 into ‘Pro Mode’

In Devices View, view Routing Entries

12.2 How to set up a scene link

When scene recall commands are sent to a group, this link sends the commands to another scene,
block or group

Commonly used: Colour chase sequences, partition room joins (with condition)

1. Open Routing Entries View

(View > Routing Entries; or click the icon).

In the Properties View:

Link Duration

This is the time it takes for the link to take effect.

1. In the Routing Entry section, click in the Link Duration field.

2. Enter the link duration time (in hh:mm:ss.ms)

Fade Time

The fade time is the time it takes the channel(s) to change from one scene to another.

1. In the Routing Entry section, click in the Fade Time field.

2. Enter the fade time (in hh:mm:ss:ms)

Cancel Trigger Scene Recall

If you want the scene recall command not to be sent to the initial group:
rEVE Rev 1.3

1. In the Routing Entry section, click in the Cancel Trigger Scene Recall field.
2. Click , and then select True.

Log Cancelled Trigger Scene Recall

If you want the scene recall command not to be sent to the initial scene:

1. In the Routing Entry section, click in the Cancel Trigger Scene Recall field.
2. Click , and then select true.

Allow Further Routing

If you want to permit further routing entries from occurring:

1. In the Routing Entry section, click in the Allow Further Routing field.
2. Click , and then select True.

Condition

Apply a condition to the link:

1. In the Routing Entry section, click in the Condition field.

2. Click , and then select a condition from the drop-down menu. See Conditions for more
information.

Link Type

When in complex mode, if a scene in the same block is called before the scene link happens, then the
scene link is still performed afterwards.

When in simple mode, if a scene in the same block is called before the scene link happens, then the
scene link is not performed.

1. In the Routing Entry section, click in the Link Type field. Notice that Complex is set by
default.
2. Click , and then select a link type from the drop-down menu.

Routing Entries Trigger

Enter the group, scene block and scene number from which you want to link the command.

1. In the Routing Entry Trigger section, click in the Group field, and then enter the group
2. Click in the Scene Block field, and then enter the scene block.
3. Click in the Scene Number field, and then enter the scene.

Routing Entries Action

Enter the group, scene block and scene number to which you want the command to be linked, and
the action performed.

1. In the Routing Entry Action section, click in the Group field, and then enter the group.
2. Click in the Scene Block field, and then enter the scene block.
rEVE Rev 1.3

3. Click in the Scene Number field, and then enter the scene.
4. Click to apply the changes.

12.3 How to set up presence detection

In this example, you want to recall Scene 1 in Group 80.

2. Put the presence detector in Group 80.

In Devices View, select the sensor. In Properties View, in the Groups row, type 80 and click
‘OK’.
Note: a sensor can exist in one group only.
Now, the sensor is in the same Group as the load interfaces it is controlling.

3. Open Routing Entries View

(View > Routing Entries; or click the icon).

4. Insert Routing Entry

In Routing Entries View, right-click in a blank area >select Insert > Presence Detection.

5. Enter settings in Properties View

In Properties View (right-click the routing entry row on Routing Entries View and choose
Properties) and enter these values:

1. Name
Type the routing entry name “Group 80 Presence”.
Naming your routing entries logically, to help you edit your system later.

2. Routing Entry Trigger: Group

Select Group 80 from the drop-down menu.
This means that the sensor (which will trigger the routing entry) is in Group 80.

Leave Scene Block as ‘1’.

3. Routing Entry Action: Scene Number

Leave this is a ‘1’ (the default value).
This is the Scene which will be recalled when the Presence Detector detects movement
and triggers the routing entry.

4. Click ‘OK’.
rEVE Rev 1.3

12.4 Create a constant light routing entry: simple set-up

In this example, the 312 Multisensor is used to control one group of loads, Group 90.

1. Put the 312 Multisensor in Group 80.

In Devices View, select the sensor. In Properties View, in the Groups row, type 90 and click
‘OK’.
Note: a sensor can exist in one group only.
Now, the sensor is in the same Group as the load interfaces it is controlling.

2. Open Routing Entries View

(View > Routing Entries; or click the icon).

3. Insert Routing Entry

In Routing Entries View, right-click in a blank area > select Insert > Constant Light >
Constant Light.

4. Enter settings in Properties View

In Properties View (right-click the routing entry row on Routing Entries View and choose
Properties) and enter these values:

5. Name
Type the routing entry name “Group 90 Constant Light”.
Name your routing entries logically, to help you edit your system later.

6. Light Sensor: Group

In the ‘Light Sensor’ section, select Group 90 from the drop-down menu.

7. Controlled Group
In the ‘Controlled Group’ section, select Group 90 from the drop-down menu.

8. Click ‘OK’.

12.5 Create a constant light routing entry: more complex set-up

Follow the same example as above, but create extra routing entries which use the same Light Sensor,
but different Controlled Group.
rEVE Rev 1.3

Scaling

Scaling is the rate at which light levels are adjusted during Constant Light operation (0 % being the
slowest rate, and 100 % being the fastest rate).

Notes:
For multiple Controlled Groups, the relative size of the scaling indicates how much faster or
further one Controlled Group will vary in comparison to another Controlled Group. For example,
the lights in the Controlled Groups all start at 50 %, and the first of the Controlled Groups has
a scaling factor of 20 % and the second a scaling factor of 10%, with the measured light level
being above the target level. By the time the lights in the first Controlled Group are reduced to
a level of 30 % (20 % lower than their starting level), the lights in the second Output Group
are changed by half (10/20) of this, i.e. from 50 % to 40 % level (10 % lower than their
starting level).

When Constant Light operation causes the Controlled Group with the largest scale factor to
reach minimum or maximum, the other Controlled Groups are not adjusted further in that
direction. This prevents groups, other than the main Controlled Group, from being sent to
minimum or maximum when this may not be required.
1. Click in the Percentage field of the Scaling section.
2. Enter the percentage (0 – 100 %) of scaling. The default is 100 %.
3. Click 'OK'

Response Rates

Up Rate

This is the rate at which the Light Sensor adjusts the lighting when the measured light level is lower
than the target level. The range is /10 % to ×10 % and the default is x1%.

1. Click in the Up Rate field and click.

2. Select a rate from the drop-down menu.
3. Click

Down Rate

This is the rate at which the Light Sensor adjusts the lighting when the measured light level is higher
than the target level. The range is /10 % to ×10 % and the default is x1%.

1. Click in the Down Rate field and click.

2. Select a rate from the drop-down menu.
3. Click
rEVE Rev 1.3

Dead Band Size

Dead Band

This defines the range within which the measured light level is considered to be close enough to the
target level, preventing further adjustment. This is used to prevent the sensor constantly searching
for the target light level and therefore the levels flickering up and down. The range is ± 2 % to
± 10 % and the default is ± 4 %.

1. Select a range from the drop-down menu in the Dead Band field.
2. Click OK.

Target Levels

You can set the target light levels for each of the On Scenes (1–12). During Constant Light operation,
the output light level of the load in the Controlled Group is adjusted, with the aim of making the
measured light level equal to the target level.

Note:
The target levels correspond to the measured light level.
1. In the Target Levels section, click in Target Level for Scene... field for the scene you want to set
the target level for. Notice that they are set to '100' by default.
2. Enter a number (0-200) or click and choose from 'Last Level' or 'Fixed Light' (to ignore Constant
Light).
3. Click 'OK'.

Lights Off Levels

This is the light level at which the loads will be turned off because ambient light is sufficient. In other
words, if the amount of ambient light reaches or exceeds the lights off level, then the loads' output
(lights) will be gradually decreased, until they are off.

Notes:
The lights off level must be set to a higher value than the target level. This is because you do not
want the lights to turn off before the target level is reached.

If you input a value of less than 5 greater than the target level, Designer enforces a value of 5
greater than the target level.

You can set lights off levels for each Scene (1-12).
1. In the Lights Off Levels section, click in Lights Off Level for Scene... field for the scene you
want to set the lights off level for. Notice that the lights off levels are set to 'Disabled' by default.
2. Enter a number (0-199) or click and select 'Disabled' (to not use lights off levels).
3. Click ‘OK’
rEVE Rev 1.3

Calling Constant Light Scenes

You can call Constant Light Scenes from buttons (sub devices) which are configured to recall
Constant Light Scenes.
You can also call Constant Light Scenes from Go To and the Scene Table. See 'Go To' a Constant
Light Scene for steps on how to call a Constant Light Scene from 'Go To' and the Scene Table.

Constant light: key terms

312 Multisensor light sensor

The light level sensor in the 312 Multisensor can detect levels of ambient light and adjust the light
levels to compensate for changes in ambient light.

Constant Light
the load output (LED driver/ballast/dimmer) is automatically adjusted to compensate for changes in
ambient light.

Fixed Light
the load output is NOT adjusted by the light sensor.

Input Group and Output Group (Controlled Group)

Constant Light operation involves two groups:

Input Group
The light sensor, and control devices (buttons, infrared commands, PIR sensors) that are required to
recall or adjust Constant Light, must be in this group.

Output Group (Controlled Group)

The loads (LED drivers/ballasts/dimmers) must be in the Controlled Group.
This is the group that the Light Sensor will send step up or down commands to, while it tries to
maintain the desired light level (the target level).

Constant Light adjusts output light levels (by affecting the loads in the Controlled Group), according
to the ambient light level measured by the Light Sensor in the Input Group, in order to achieve the
target light level.

A Constant Light routing entry defines the Input and Controlled Groups, as well as the target levels.

Simple Constant Light set-up: Input Group is same as Controlled Group

If a light sensor controlling Constant Light of only one group of loads, the Input Group and Controlled
Group can be the same group.

More complex Constant Light set-up

If more than one Controlled Group is required, the Input Group and Controlled Groups must be
different.
For example, in a large room with a large amount of daylight: one part of the room might be affected
by sunlight more than other parts. In this situation, you may want different groups of the room's
lighting to be adjusted at different rates.
rEVE Rev 1.3

13 Logic programming data distribution, logic and group

housekeeping tools

13.1 Logic data distribution and housekeeping tools

Designer 5 handles logic items (routing entries, schedules and conditions) in a way which makes
efficient use of routers’ system memory.
Designer 5 also includes simple-to-use housekeeping tools to ‘tidy up’ after adding, removing or
editing logic items, which frees up router memory.
When programming routing entries, schedules and conditions, it helps to understand this logic
distribution process, and what each of the ‘logic housekeeping’ functions does.

13.2 Logic data distribution in Designer

Designer 4

In a Designer 4 workgroup, all logic programming data is stored in each and every router in that
workgroup.

Advantage: even if all but one router fails, the logic programming data is retained in the
remaining router.
Disadvantage: scalability becomes an issue, as processing and memory capacity could
potentially be reached in each router.

Designer 5
In a Designer 5 workgroup, not all logic programming data is stored in each and every router in that
workgroup.
In a Designer 5 workgroup, logic programming data is distributed based on the groups that 'exist' in
each router.
If a group exists in a router and the logic item uses that group then the logic programming is stored
in that router.
This distribution of logic programming data makes more efficient use of routers’ system memory.

Note: In Designer 5, each routing entry has a unique ID number and timestamp, easing the internal
administration of logic data.
rEVE Rev 1.3

13.3 When to use Logic housekeeping tools

Designer automates the process as much as possible and will perform a degree of housekeeping on
its own. However below is a list of key circumstances where manual housekeeping is recommended
or necessary.

More than one router (recommended)

Designer 5’s logic housekeeping tools are for when you are creating and editing routing entries,
schedules and conditions that affect groups in more than one router.
If your workgroup has only one router, Designer will administer the logic items in the router, if Clean
Groups is set to True in Tools > Options.

When making major changes to routing entries, schedule or conditions (recommended)

If you are about to make a number of changes to router entries, it is good practice to manually ‘clean’
logic data.
This does not clear all logic data from routers in the workgroup: it removes logic data that does not
apply to groups which contain devices connected to particular routers’ subnets.

When adding individual routers to a workgroup (necessary)

If you are adding a router to a workgroup and the workgroup features routing entries, schedules or
conditions, you need to use Designer 5’s logic housekeeping tools.

When merging workgroups (necessary)

If you are merging a separately programmed set of routers, and the workgroup features routing
entries, schedules or conditions, you need to use Designer 5’s logic housekeeping tools.
rEVE Rev 1.3

When permanently removing routers from a workgroup (necessary)

If you are permanently removing a router from a workgroup, and the workgroup features routing
entries, schedules or conditions, you need to use Designer 5’s logic housekeeping tools.

Splitting a workgroup to create more than one workgroup (necessary)

If you are splitting a workgroup, to create other smaller workgroups, original workgroup featured
routing entries, schedules or conditions, you need to use Designer 5’s logic housekeeping tools.

13.4 Accessing Logic housekeeping tools

Pro mode, then check ‘Logic Housekeeping’ is allowed

c) Put Designer in Pro Mode

d) Tools > Options > Allow Logic Housekeeping = True

e) In the Device tree, right-click the Workgroup; select Logic

Note: Right clicking on the workgroup will perform the functions across all routers in the
workgroup. It is also possible to right click on just the individual routers to perform the
same at individual router level. Clean is the exception and can only be performed at
workgroup level.

13.5 Add; Prune; Clean

rEVE Rev 1.3

You can Add, Prune or Clean the following:

Logic [including routing entries, schedules and conditions];

Routing Entries [routing entries only];
Schedules [schedules only];
Conditions [conditions only]

Add
‘Add’ propagates logic to a newly added router which has groups which should be included in existing
routing entries, schedules and conditions.
If you have programmed some logic items before a router is included in the workgroup, you need to
use the ‘Add’ tool.
You can choose to Add Logic (all logic items), or to add routing entries only, conditions only, or
schedules only.

Example: Workgroup of 8 routers. You add an extra router and create groups.
The new router’s groups are affected by logic items in the existing workgroup.
You connect the new router to the workgroup, and the router is detected and its devices appear in
the device tree.
At this stage, routing entries, schedules and conditions affecting the new router will not include
devices on the new router. You now need to send the logic programming data to the new router.
Right-click the workgroup, Logic > Add logic
Programming data for the logic items that affect groups in the new router will now be sent to the new
router.

Prune
‘Prune’ removes logic programming data from routers which do not have groups that are included in
existing routing entries, schedules and conditions.
You can choose to Prune Logic (all logic items), or to prune routing entries only, conditions only, or
schedules only.

Example: you split a workgroup to create two smaller workgroups.

At this stage, in each new workgroup, the logic programming data for routing entries, schedules and
conditions that used to affect the removed routers are still in both workgroups. You now need to
‘prune’ (cut out) the logic programming data that is no longer needed.
Right-click the workgroup, Logic > Prune logic
Programming data that is no longer needed is now removed.

Clean = ‘Add’ & ‘Prune’

rEVE Rev 1.3

‘Clean performs the actions both of ‘Add’ and ‘Prune’, propagating logic programming as necessary
and removing logic programming data from routers.
You can choose to Clean Logic (all logic items), or to clean routing entries only, conditions only, or
schedules only.

Verifying if a logic housekeeping process (Add, Prune or Clean) is complete.

Device Tree
When in Pro mode under the device tree, then under each router’s subtree, the groups and logic
items involving the router are listed. You can check there to see if these logic items have been
updated as expected or not. There is also now a “Client” visable under the Device tree, this is the
aggregation of all the groups and logic items in all of the routers for the workgroup i.e. a workgroup
level grouping and logic item list.

Note: Logic items are not saved into the routers until they are grouped or in the case of certain
conditions, assigned to devices or other grouped parameters. Care needs to be taken when creating
the logic items and leaving them unassigned or ungrouped as exiting Designer without doing so or
saving a backup file will result in a loss of the unassigned and ungrouped logic programming.
rEVE Rev 1.3

13.6 Group information housekeeping

Group housekeeping should be carried out in the same scenarios as logic housekeeping:

- When making major changes to routing entries, schedule or conditions

- When adding individual routers to a workgroup
- When merging workgroups
- When permanently removing routers from a workgroup
- Splitting a workgroup to create more than one workgroup

You can clean groups in the same way as you can clean logic. This process recalculates the groups
which need to be in each router, and then deletes and adds the required groups.

This can be done at router level or workgroup level:

Right-click (workgroup or router) > Groups > Clean groups.

13.7 Limits on number of logic items in a Workgroup

In Pro mode, you can view the limits on the quantities of routing entries, schedules and conditions in
a Workgroup (Tools > Options).

The recommended system limit is 3000 logic items.

The recommended single router limit is 700 logic items.

The maximum system limit is 5100 logic items.

The maximum single router limit is 1000 logic items.

It is never recommended to approach the limit of any system. The result being that it will
most likely fail or drastically degrade performance in real world scenarios.
rEVE Rev 1.3

13.8 Group information housekeeping

Group housekeeping should be carried out in the same scenarios as logic housekeeping:

- When making major changes to routing entries, schedule or conditions

- When adding individual routers to a workgroup
- When merging workgroups
- When permanently removing routers from a workgroup
- Splitting a workgroup to create more than one workgroup

You can clean groups in the same way as you can clean logic. This process recalculates the groups
which need to be in each router, and then deletes and adds the required groups.

This can be done at router level or workgroup level:

Right-click (workgroup or router) > Groups > Clean groups.
rEVE Rev 1.3

14 Temporary MIN & MAX settings

14.1 Typical Applications of Temporary Minimum and Maximum
Temporary Maximum: place an upper limit on the brightness of all lamps in a group

There might be times when you want to put a limit on the maximum level of all lights in a group, so
that any lamps brighter than the Temporary Maximum Limit will be turned down. Any output that is
set to a level that is lower that the Temporary MAX will not be affected. Only outputs that are above
this level will be lowered. Any output that is not needed when load shedding is active, can be turned
OFF by setting the Temporary MAX level to 0.

Example 1: power supplied by generator or central battery

If power is being supplied by a generator or central batter, an input from the generator/
battery system can signal when load shedding is needed, enabling the Temporary Maximum is
used to reduce the load levels and reduce energy use.

Example 2: power company request

A signal is sent from your power company’s smart meter that ‘load shedding’ is required. A
Temporary Maximum Level is applied to lighting loads to ease the load on the power network.

Example 3: Electricity provider high tariff rate

Electricity providers can set higher kWh tariffs at different times and days. Reduce energy
usage at the higher rates to save on energy and therefore bills.

Temporary Minimum: make sure lamps in a group are at least a certain level
You may want to make sure all lamps in a group are at least a certain level, so that any lamps that
were off or below the temporary minimum level will be turned up.

Example 1: Fire Alarm Trigger

A trigger from the fire system enables temporary minimum levels so minimum lighting levels
are kept in order to safely exit the building.

Example 2: Security Alarm Trigger

A trigger from the security system enables temporary minimum levels in order identify or
highlight threats

14.2 Background operation

Whilst temporary min or temporary max are enabled, operations are still active in the system. This
will mean that functions such as PIRs will continue to time out, constant light will still be in operation,
and panels can still be triggered, but there will be no change to scene levels outside the temporary
levels.

14.3 What happens when temporary levels are disabled?

Due to background operation, upon disablement of temporary min or max, the loads will then revert
to their current state of operation instead of their last state before enablement.

14.4 Can Temporary Maximum and Minimum limits be used with

Redirects?
Yes.
rEVE Rev 1.3

14.5 Priority
Temporary levels have a set priority. Temporary MIN will override Temporary MAX. This behaviour is
designed to support fire alarm (lights ON) having a higher priority than load shedding (lights
OFF/DIM)

If a device is set to a lower max than it’s temporary max or higher min than its temporary min. The
actually max and min level will take priority over the temporary one.

14.6 Are Temporary Maximum and Minimum Levels absolute?

The settings are capped absolute levels.

14.7 Temporary maximum limit for load shedding: slow fade

recommended.
It is recommended that when activating "Enable Temporary Absolute Max", that the fade time is
relatively long. This means that those lamps above the Temporary Maximum Level will slowly dim
down to the Temporary Maximum Level but people in the areas affected may not notice. If the
Temporary Maximum Level is called with a short fade time, it will probably be very noticeable.

14.8 Temporary minimum limit (e.g. for alarms): short fade time
recommended.
When activating the Temporary Minimum Limit, it is most likely an emergency situation, such as an
alarm.
The Temporary Minimum Level turns up (increases the intensity of) loads in a group to a certain
level. It is recommended that when activating "Enable Temporary Absolute Min", that the fade time is
short. This means that those lamps below the Temporary Minimum Level will quickly become brighter
until they reach the Temporary Minimum Level. People in the areas affected should notice this. If the
Temporary Maximum Level is called with a long fade time, it may not give the impression that people
should be alert to an alarm or danger.

14.9 How to set and enable a temporary limit to a load

There are two steps:
1. Set the Temporary Maximum or Minimum Limit for an LED driver, dimmer or ballast (load
interface).
2. Program a button, input device or schedule to send an “Enable Temporary Max” command to
that load interface.

The properties are configured in each device, but are then enabled at the group level.

14.10 Triggering Temporary Maximum and Minimum

Commands for enabling and disabling temporary min and max are sent only by input devices such as
button panels, 444 and 942 input units.
rEVE Rev 1.3

14.11 Example: Programming and applying a Temporary

Minimum Level to a Group.
This example uses group 88, containing an LED driver and a 452 Dimmer.
In an emergency, applying the Temporary Min Level will put both these devices up to at least 90%
brightness.
The Temporary Min Level will be called using a two-button panel (a Helvar 131).

Identify devices in the Group.

1. Open Groups View (View > Groups)
2. Double-click Group 88.
3. If required, identify the LED driver and the 452 Dimmer (right-click > Identify)

Select both devices, set Temporary Minimum Level (and Temporary Maximum Level, if
required)

4. Select both devices in Groups view (Ctrl-click).

5. In Properties View (View > Properties), set:
Temporary Absolute Min Level: 90%
(You can also set the Temporary Absolute Max Level: 45%)

6. Click ‘OK’.
rEVE Rev 1.3

Program the buttons to call Temporary Max and Temporary Min.

7. In Devices View, find the 313 button panel, expand it and click the first button.

8. In Properties View (the properties for the button), in the ‘Press’ section, set ‘Function’ to
“Enable Temporary Absolute Min”. Leave the fade time as 2 seconds.
rEVE Rev 1.3

9. In Devices Tree, select the other button, and program its Press Function (see step 8) to
‘Disable Temporary Absolute Min’. Leave the fade time as 2 seconds.
10. Click ‘OK’.
11. Check the programming: in Groups View, double-click the button panel

12. Click button ‘1’ to check that the loads (see View > Channel Graph) are at a minimum of
90%.

13. Click button ‘0’ to check that the loads revert to their previous levels.

14. If required, you can follow similar steps to programme another control (buttons, input units,
schedules) to enable the Temporary Maximum Level.
rEVE Rev 1.3

15 Upload
15.1 What is upload for
The Upload View is used to copy information from one design file to another. This can be used for
programming offline, restoring previous versions of workgroup, or programming replaced hardware

Upload works both with an online workgroup or an offline design file.

Upload allows for copying ALL workgroup information, or just a portion of it.

15.2 Differences from v4

The way that Upload works has changed since version 4. If you are familiar with v4, then v5 will be
easy to use.

There are some differences to be aware of however

• When you click FINISH, ALL selected changes are sent to the workgroup. Previously you were
prompted for the type of changes to commit
• V5 will check the information when it is sent. Any groups or routing entries not used by the
workgroup will not be sent to the routers. V4 would send ALL information.
• With v4 it was possible to append information, such as routing entries. V5 does not allow for
this to happen.
• V5 supports drag/drop, which is often more intuitive than using the toolbar icons

The process and options for uploading backup files to a system has altered to be in line with the
distributed grouping and logic philosophy. The change has simplified the process along with giving
the user more flexibility on what data to upload and to which router.

In version 4 and previous version 5 builds, the upload finish choices were: Device Data Only,
Overwrite, Append and Cancel.

Now, the finish choice has been simplified to just Upload or Cancel
rEVE Rev 1.3

The associated features of the upload process such as compare, match, un-match, and create still
remain the same and function in the same way as they did previously.

15.3 Recommended best practice

• Always ensure that backups are taken before and after any uploads are done
• Check the information carefully before committing changes
• Groups are created during the upload process. A second upload process may be needed to
copy across the group information, such as names.
rEVE Rev 1.3

15.4 Device Alerts

When you attempt to match a pair of items, then a pictogram (a device alert) appears beside them in
the trees to indicate the status of the attempted match (as shown here, for example: ).

Device Alert Meaning

At least one descendent item is not matched.

Parent items equivalent, children equivalent

This item and the item with which it is matched are equivalent,
and all child items are equivalent or similar.

Parent items similar, children similar

This item and the item with which it is matched are similar, and
all child items are equivalent or similar.

Equivalent
This item and the item it is matched with are equivalent.

Similar
This item and the item it is matched with are similar.

Parent equivalent, children not matched

This item and the item with which it is matched are equivalent,
and at least one child item is not matched.

Parent similar, children not matched

This item and the item with which it is matched are similar, and
at least one child item is not matched.

Not matched
This item is not matched with another item.

Missing
This item is missing from the real lighting system.

Item created
This item has had a copy created for it in the real workgroup /
workgroup design during this Upload session, and the two items
are matched.
rEVE Rev 1.3

15.5 Match and Equivalent Items

The terms match and equivalent have special meanings that you should be aware of:

Similar Two items that are sufficiently similar to be associated with

each other. (Nothing else is implied by this relationship
between the items.)

Equivalent A pair of matched items that have identical properties. Child

items of the pair are not considered.

New Upload Design

Creates a new Workgroup Design for upload into the real workgroup / workgroup design .

Open a Design for Upload

Opens an existing workgroup design for upload into the real workgroup / workgroup design.

Save Upload Design

Saves the Upload Design (workgroup design for upload).

Save Upload Design As

Saves the Upload Design in a different name and/or location.

Compare
Compares an item (and all child items) in the Upload Design with an item (and all child items)
in the real workgroup / workgroup design.

Restore Previous Matches

Restores the previous matches that were broken.

Match
Forces a match between an item in the Upload Design and an item in the real workgroup /
workgroup design.

Break Match
Breaks a match between an item in the Upload Design and an item in the real workgroup /
workgroup design.

Create
Creates an item in the real workgroup (even though it has not been discovered by Designer)
or the workgroup design.
rEVE Rev 1.3

This is useful if you want to include an item, from your upload design that is not currently
present in the real workgroup / workgroup design. When such a device has been created, the
item in the upload design is matched automatically with the new item created in the real
workgroup / workgroup design.

Finish
Upload the Upload Design to the real workgroup / workgroup design according to the
matches that have been established using the Upload tools.

Cancel
Discard all existing matches.

Expand Trees to Router Level

Expands both Devices Trees to router level.

Expand Trees to Subnet Level

Expands both Devices Trees to subnet level.

Expand Trees to Device Level

Expands both Devices Trees to device level.

Expand Trees to Non-Equivalent Level

Expands both Devices Trees to router, subnet and device level.

15.6 Standard Upload

Simply performing a compare and finish upload will overwrite any changes between matched
items of the system and backup file. The upload will create groups but will not create/ add any new
items such as devices or logic items. Devices or logic items which exists in the system but not in the
backup file will NOT be deleted.

The below image shows an example where a compare at workgroup level followed by a finish upload
has been performed. It shows that the device and group information has been uploaded across but
has not created/ added the logic items. In this example, only the client subtree is exposed however
the same applies for all the routers in the workgroup
rEVE Rev 1.3

The standard upload operation should be performed if the user wants to update changes to the
system and the number of devices and logic items are the same between backup and the system.

15.7 Create and Upload

To create/ add logic items and devices which exist in the backup file but not in the system, a compare
then create should be performed before finishing .

The below image shows the same system and backup file as the previous example now with the
create function performed. The logic items have now also been created in the system, along with the
groups. In this image, only the client subtree is exposed however the same applies for all the routers
in the workgroup.
rEVE Rev 1.3

The create and upload operation should be performed if the user wants to update AND add changes
to the system. Example: if routers have been erased and configuration needs to be restored from a
backup.

15.8 Still want to Upload as before?

Where the majority of users will choose just to carry out the standard upload or create and upload,
the need may arise where the previous options of uploading is required. Below is a short guide on
how to achieve Device Data Only, Append and Overwrite in the new way of uploading:

Device Data Only: Compare and match only the router subnets. This will only upload data of those
devices for the selected subnets along with their grouping information. If there are devices in the
backup file which do not exist in the system and require adding, such as virtual devices, then also
perform a Create as part of the upload process. Note: you may need to unmatch any undesirable
items from the compare.

Append: At client level, compare and match only the logic items. This will only upload the logic
items. If there are logic items in the backup file which do not exist in the system and require adding,
rEVE Rev 1.3

then also perform a Create as part of the upload process. Note: you may need to unmatch any
undesirable items from the compare.

Overwrite: Delete all logic items in the workgroup, then carry out a create and upload operation as
covered in section 15.7. It is also recommended to perform a clean logic and clean groups after the
upload as well.

END