Helvar Designer 5 Foundation Course: Initial programming Edition 1 (10 th May 2018). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 1 of 99
Contents A: BEFORE GOING ONLINE... 4 1.1 CHECK WINDOWS COMPATIBILITY... 5 1.2 CONFIRM ADMINISTRATION RIGHTS... 5 1.3 INSTALL DESIGNER... 5 2.1 ALLOW DESIGNER THROUGH FIREWALL(S)... 6 2.2 ALLOW DESIGNER THROUGH WINDOWS FIREWALL [VIDEO AVAILABLE]... 6 3.1 SITUATION 1: SINGLE-CLUSTER WORKGROUP ON SEPARATE, UNMANAGED NETWORK... 8 3.2 SITUATION 2: MULTI-CLUSTER WORKGROUP ON SEPARATE, UNMANAGED NETWORK... 9 3.3 SITUATION 3: SINGLE-CLUSTER NETWORK WITH VARYING IP CLUSTERS IN A MANAGED NETWORK... 12 3.5 PRIMARY MASTER AND SECONDARY MASTER ROUTERS... 15 4.1 CHANGE THE IPV4 SETTINGS OF YOUR PC S NETWORK INTERFACE... 16 5.1 CHANGE THE IP SETTINGS OF THE HELVAR ROUTER... 17 6.1 CHECK ROUTERS HAVE DESIGNER 5 SOFTWARE INSTALLED... 18 7.1 RUN DESIGNER 4... 19 7.2 SAVE THE.DESIGN FILE... 19 7.3 RUN DESIGNER 5 AND OPEN THE BACKED-UP DESIGN FILE... 19 7.4 SHOW ALL ROUTERS IN ROUTERS VIEW... 19 7.5 UPGRADE DESIGNER 4 ROUTERS TO DESIGNER 5... 20 7.6 CHECK LOGIC ENTRIES IN DEVICES VIEW... 20 7.7 ENABLE CLEAN GROUPS AND LOGIC HOUSEKEEPING... 20 7.8 OPEN UPLOAD VIEW... 21 7.10 CREATE LOGIC ITEMS... 21 7.11 CLEAN LOGIC... 21 7.12 SAVE A BACKUP OF THE DESIGNER 5.DESIGN FILE... 22 7.13 CHECK THAT THE UPGRADE AND UPLOAD PROCESS HAS RUN PROPERLY... 22 OVER TO YOU!... 23 B: GO ONLINE... 24 1.1 CONNECT THE ROUTER TO THE PC... 25 1.2 START DESIGNER 5 SOFTWARE ON YOUR PC... 25 1.3 CHECK IN ROUTERS VIEW THAT THE HELVAR ROUTERS:... 25 1.4 SELECT THE GO ONLINE BUTTON (OR FILE > GO ONLINE)... 25 1.6 CHECK PROGRESS OF DESIGNER... 25 1.7 CHECK DESIGNER IS ONLINE... 26 2.1 CREATE A NEW DESIGNER DESIGN FILE... 27 2.2 INSERT A DALI LED DRIVER INTO THE DALI SUBNET OF THE 920 ROUTER... 27 2.3 INSERT A TUNABLE WHITE DALI LED DRIVER INTO THE DALI SUBNET OF THE 920 ROUTER... 28 2.4 INSERT AN ILLUSTRIS 192 PB CONTROL PANEL... 28 2.5 INSERT A 135 BUTTON PANEL... 29 2.6 INSERT A 135 BUTTON PANEL... 29 OVER TO YOU!... 31 C: SUBNETS AND WORKGROUP SETTINGS... 32 1.1 VIEW & RENAME SUBNETS... 33 2.1 CONFIGURE A DALI SUBNET (NAME; CURRENT CONSUMPTION; AUTOHEALING)... 35 2.2 VIEW DEVICES ON A DALI SUBNET... 35 2.3 CONNECT DALI CABLING TO A ROUTER S DALI CONNECTOR... 36 3.1 CONFIGURE A DMX SUBNET: IN/OUT; ENABLED/DISABLED; CONDITION... 39 3.2 PROGRAMMING EXAMPLE: CONFIGURE ROUTER TO CONTROL EXTERNAL DMX DEVICES... 39 3.3 PROGRAMMING EXAMPLE: DMX INPUT CONTROLS LED DRIVER... 43 3.4 PROGRAMMING EXAMPLE: DMX IN CONTROL IN THE EVENING + DALI CONTROL AT OTHER TIMES... 44 4.1 SET S-DIM ADDRESSES FOR A 454 DIMMER... 47 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 2 of 99
4.2 VIEWING AND PROGRAMMING S-DIM DEVICES IN DESIGNER 5... 47 OVER TO YOU!... 49 D: IDENTIFY, NAME AND GROUP DEVICES... 50 1.1. VIEW THE ROUTERS IN A WORKGROUP... 52 1.2. VIEW A ROUTER S SUBNETS IN DEVICES VIEW... 52 1.3. VIEW THE DEVICES IN THE DALI SUBNET... 53 IDENTIFY DEVICES... 54 OVER TO YOU!... 65 E: SCENE TABLE AND EVENT LOG... 66 CHANGING LEVELS IN THE SCENE TABLE... 67 WHAT IS LAST LEVEL?... 69 WHAT IS IGNORE?... 69 RECALLING A SCENE FROM THE SCENE TABLE... 69 RECALLING A SCENE USING GO TO... 69 VIEWING THE EVENT LOG... 70 EXPORTING THE EVENT LOG... 71 OVER TO YOU!... 72 F: SCHEDULES AND CONDITIONS... 73 WHAT IS THE SCHEDULER FOR?... 73 TYPES OF SCHEDULE... 73 SETTING UP A SCHEDULE... 74 WHAT IS A CONDITION IN DESIGNER (IN A ROUTER SYSTEM)?... 75 TYPES OF BOOLEAN CONDITION... 76 TYPES OF CONDITION... 77 SETTING UP A CONDITION... 80 APPLY A CONDITION... 82 HOW TO APPLY A CONDITION... 82 OVER TO YOU!... 82 G: SENSOR CONTROL (OCCUPANCY DETECTION AND CONSTANT LIGHT)... 83 SETTING UP PRESENCE DETECTION... 84 SETTING UP ABSENCE DETECTION... 86 SETTING UP CONSTANT LIGHT... 87 OVER TO YOU!... 88 EXERCISES: CLASSROOM... 89 EXERCISE 1: IDENTIFY; GROUP; PROGRAM SCENES... 89 EXERCISE 2: TWO GROUPS, ONE PANEL... 90 EXERCISE 3: TWO GROUPS, TWO PANELS... 91 EXERCISE 4 TWO GROUPS, TWO PANELS, MULTISENSOR: ABSENCE DETECTION :... 92 EXERCISE 5 TWO GROUPS, TWO PANELS, MULTISENSOR: ABSENCE DETECTION AND CONSTANT LIGHT :... 94 EXERCISE 6: MAKE ABSENCE DETECTION WORK IN CERTAIN HOURS ONLY.... 96 EXERCISE 7: OUTSIDE NORMAL SCHOOL HOURS, APPLY FULLY AUTOMATIC SENSOR CONTROL (PRESENCE DETECTION)... 98 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 3 of 99
A: Before going online What s in this section? This section tells you how to connect Designer software to the Helvar router system. It includes: Installing Designer 5 on your Windows PC Firewall settings Network topology for Designer 5 routers Windows PC IP settings IP settings of Helvar routers Check routers have Designer 5 installed Upgrading from a Designer 4 System to Designer 5 USEFUL TIP If you are in a trainer-led session, this may have been set up for you. If so, your trainer may skip these steps, and begin at the Go Online section. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 4 of 99
Installing Designer 5 on your Windows PC 1.1 Check Windows compatibility Designer 5 is supported on these operating systems: Windows 7, SP1 Windows 8, 8.1 Windows 10 1.2 Confirm administration rights Make sure you have the rights on your PC to be able to: Install software Change your network interface card s IP address 1.3 Install Designer a) Copy setup.exe to your computer b) Open Helvar the Designer.exe setup file c) If Windows opens User Account Control window, answer Yes (Windows 7) d) As your PC goes through the installation steps, Click Next e) Click Install f) Click Finish Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 5 of 99
Firewall settings 2.1 Allow Designer through firewall(s) Allow communication through any other firewalls running on your PC. Note 1: Windows admin rights Your Windows user account will need Administrator Access Rights to the PC to effect these changes. Contact your IT support team if your PC requires Windows administration rights, or ask your IT support team to allow Helvar Designer software through your firewall. Note 2: Multiple versions of Designer on the same PC You can have multiple versions of Designer installed on the same PC (e.g. Designer 4.2.25 and 5.2.1 and 5.4.4). You need to make sure Windows Firewall will allow through each instance of the program. 2.2 Allow Designer through Windows firewall [video available] Note: these instructions are for Windows 7. They are also applicable to Windows 8 and Windows 10, where the process is similar. a) Start > Control Panel > Windows Firewall b) On the left click Allow a program or feature through Windows Firewall c) Click Change Settings and Yes d) If you cannot see Designer software in the list, click Allow another program and search for Designer.exe e) Allow all traffic Domain, Home/Work and Public f) Select OK Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 6 of 99
Network topology for Designer 5 routers BACKGROUND INFO: Single-cluster and multi-cluster workgroups. Systems can be either single-cluster or multi-cluster. This depends on: Number of routers Physical location of routers Whether the Ethernet network is unmanaged or managed The following situations describe three typical workgroups with example IP settings for the routers and the PC client. Situation 1: Single-cluster workgroup on separate, unmanaged network Situation 2: Multi-cluster workgroup on separate, unmanaged network Situation 3: Single-cluster network with varying IP clusters in a managed network Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 7 of 99
3.1 Situation 1: Single-cluster workgroup on separate, unmanaged network This situation is found in small to medium systems. Key features of this situation 2 to 10 routers Independent, unmanaged Ethernet network (i.e. not managed by the building's IT team) Typically one distribution board Routers controlling lighting on a single floor Key features of a single-cluster network Routers use the same cluster comms port Routers have same IP addresses apart from fourth octet Example settings for 4 routers in a single-cluster workgroup on an unmanaged network: PC Client: 10.254.254.99 Subnet mask 255.0.0.0 Router IP address Router subnet mask Cluster comms port Cluster mask 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 In this system, each router communicates with all other routers via the same cluster comms port, i.e. 60005 the default cluster comms port). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 8 of 99
3.2 Situation 2: Multi-cluster workgroup on separate, unmanaged network This situation describes larger systems. Key features of this situation Several routers located in different parts of a building Independent unmanaged Ethernet network (i.e. not managed by the building's IT team) The location of the routers in the building makes it logical to put them in different clusters Key features of a multi-cluster workgroup The different clusters of routers are located: - on different floors - at the various distribution boards available 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 Example settings for routers in a multi-cluster workgroup on an unmanaged network: 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 address Router subnet mask Cluster comms port Cluster mask 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 address Router subnet mask Cluster comms port Cluster mask 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 address Router subnet mask Cluster comms port Cluster mask 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) Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 9 of 99
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. 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: FLOOR 2 are in their own cluster communicate with each other via the 61003 cluster comms port. 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: FLOOR 1 are in their own cluster can communicate with every other router in this cluster (via the 61002 cluster comms port) 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. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 10 of 99
Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 11 of 99
3.3 Situation 3: Single-cluster network with varying IP clusters in a managed network This situation describes small to medium systems. Key features of this situation 2 to 10 routers Managed Ethernet network managed by the building's IT team IT administrator has specified the IP addresses and subnet masks for the Helvar routers so you cannot choose a standard set of IP addresses Typically one distribution board Routers controlling lighting on a single floor. Key features of 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. Example settings PC Client: 10.254.254.99 Subnet mask 255.0.0.0 Router IP address Router subnet mask Cluster comms port Cluster mask 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 it 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. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 12 of 99
Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 13 of 99
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). Examples of 3 different cluster masks and how they affect which clusters a router is in Cluster mask example 1: Cluster mask: 255.0.0.0 Router IP address: 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: 255. 000. 000. 000 Router IP address: 10. 254. 10. 1 CLUSTER Router ID Cluster mask example 2: Cluster mask: 255.255.0.0 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: 255. 255. 000. 000 Router IP address: 10. 254. 10. 1 CLUSTER is 10.254 Router ID is 10.1 Cluster mask example 3: Cluster mask is 255.255.255.0 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. Cluster mask: 255. 255. 255. 000 Router IP address: 10. 254. 10. 1 CLUSTER is 10.254.10 Router ID is 1 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 14 of 99
3.5 Primary Master and Secondary Master routers Role of Primary and Secondary Master routers All routers communicate with each other in a cluster of Helvar routers. 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 with another cluster, it will target the Primary Master of that cluster. The Primary will then 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. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 15 of 99
Windows PC IP settings 4.1 Change the IPv4 settings of your PC s network interface a) Start > Control Panel > Network and Sharing Center b) Open Change adapter settings c) Double click Local Area Connection d) If Windows opens User Account Control window answer Yes e) Open Internet protocol version 4 (TCP/IPv4) and choose Use the following IP address: f) Change IP address to: 10.254.254.63 g) Change Subnet mask to: 255.0.0.0 h) Click OK USEFUL TIP If you run Designer in administrator mode, you can change your PC s IP address from within Designer using Pro Mode (Tools > Edit Network Interfaces). This IP address is suitable when connecting to a Helvar router with the default IP address of 10.254.0.1. The IP address may be different depending on the IP settings of the routers in the workgroup you connect to. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 16 of 99
Helvar routers IP settings 5.1 Change the IP settings of the Helvar router Note: Do not change the IP settings of a Helvar router after you have started programming it with lighting control system information and commands. a) Connect your PC to the Helvar router via Ethernet b) Start Designer 5 c) Select Advanced Mode d) Click OK e) In Routers View (near the bottom of the screen), select one of the routers (the background of the row in Routers View should turn blue) f) Select Properties View. In the IP Settings section, change/check these settings: 1) Address: 10.254.1.10 2) Subnet mask: 255.0.0.0 3) TIP: You can also change the router's workgroup by editing the 'Workgroup Name'.] g) Click 'OK' (the Helvar router will now reboot) h) The router will disappear from 'Routers View' and appear again, this time with the updated IP settings. Other settings can be left unchanged. FOR YOUR REFERENCE: Default settings of this router 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 USEFUL TIP Make sure the IP settings of all Helvar routers in a workgroup have been decided as part of an overall system plan. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 17 of 99
Check routers have Designer 5 installed Note: BEFORE UPGRADING ANY LIVE SYSTEM, TALK TO YOUR HELVAR TECHNICAL REPRESENTATIVE TO DISCUSS IF IT IS NECESSARY AND ANY OTHER TECHNICAL CONSIDERATIONS. 6.1 Check routers have Designer 5 software installed a) Connect your PC to the routers' Ethernet network. b) Check that your PC Ethernet Interface IP settings are compatible with router IP addresses. For example, if the routers IP addresses are 10.254.0.1, set the PC Ethernet Interface to: IP address: 10.254.254.63 Subnet mask: 255.0.0.0 c) Run Designer 5 Identify routers d) EITHER: i. In Routers View, right-click the router and select "Identify". The LEDs on the router's front panel flash, until you click 'Cancel identification' in Designer. ii. OR In Routers view, note the serial number. In the router rack, check the serial number label on each router. Select router, change IP address e) In Routers View, select a router f) In Properties, change the IP address g) Click OK h) Close Designer 5 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 18 of 99
Upgrading from a Designer 4 System to Designer 5 7.1 Run Designer 4 Open the latest version of Designer 4 and connect to the system as usual 7.2 Save the.design file USEFUL TIP a) When connected, save a backup of the system by selecting File and Save As (see Figure 1) Important: Give the Save As file a name which shows it is a Designer 4 back up Figure 1-Save D4 File b) Close Designer 4 7.3 Run Designer 5 and open the backed-up Design file a) Run Designer 5 software b) Select Pro Mode c) Open the saved Designer 4 file (File > Open) 7.4 Show all routers in Routers View a) Make sure Designer 5 is still in Pro Mode b) Look at Routers View (View > Routers) c) By default, the Designer 4 routers are not listed d) To show the Designer 4 routers, select the magnifying glass icon (see Figure 6). Note that the magnifying glass icon is visible only if in Pro Mode. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 19 of 99
Figure 2-Search for D4 Routers e) In Routers View, the Designer 4 routers are listed in red. 7.5 Upgrade Designer 4 routers to Designer 5 USEFUL TIP a) In Routers View, right-click a Designer 4 router and select Upgrade Software. b) When requested, enter the password: ask your trainer, or your Helvar representative for the current router upgrade password. c) Select the Designer 5 software version then Update Do not disconnect from router until the update has been completed. 7.6 Check logic entries in Devices View Background info Logic entries are Conditions, Routing Entries or Scheduler items a) In Devices View, look at the Conditions, Routing Entries and Scheduler items. You will notice that these logic items are all empty. b) When the Designer 4 design file is first opened in Designer 5, no logic entries are listed (see Figure 3). Figure 3- D5 Logic Missing 7.7 Enable Clean Groups and Logic Housekeeping Background info This is required to import logic entries from the Designer 4 file to the Designer 5 file. a) Check that Designer 5 is in Pro Mode b) Tools > Options c) Set Clean Groups to True d) Set Allow Logic Housekeeping to True Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 20 of 99
Figure 4 Clean Logic Options 7.8 Open Upload View a) In Upload View, click the Open Upload Design icon and select the Designer 4 design file. b) In Upload, use compare for the whole system 7.10 Create logic items a) Right-click on system logic in upload window and press Create. 7.11 Clean Logic Background info On a Designer 5 system, running clean logic means that logic items are stored on routers only when required. The software needs to work through these items and store them on the necessary routers. a) In Devices View, right-click the workgroup name, and select Logic > Clean Logic Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 21 of 99
Figure 5- Clean Logic b) The logic entries will now be added to the correct routers (see Figure 5) Figure 6-Logic Items Added 7.12 Save a backup of the Designer 5.design file a) Save a backup. USEFUL TIP IMPORTANT: Ensure that the backup is clearly labelled to differentiate between D4 and D5 backups 7.13 Check that the upgrade and upload process has run properly a) Check some of the load properties, control properties and routing entries have been transferred as expected. For example, check the values for Temporary max. and Temporary min. levels for loads. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 22 of 99
Over to you! Now you ve learnt the basics, it s time to have a go. Try this: If your trainer has a spare router, or if you have a router for training purposes, upgrade the firmware. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 23 of 99
B: Go online What s in this section? This section tells you how to use Designer 5 online. It includes: How to connect to a Helvar workgroup. This is often called Going online or Going online with a workgroup. How to create a virtual system. This enables you to program Designer even if you do not have real routers to connect to. Instructions for this are at the end of this section. BACKGROUND INFO Workgroup A workgroup is a collection of Helvar routers. For most projects, you have one workgroup of routers. For larger projects, you may have several workgroups. When learning Designer 5, you will generally use systems with one workgroup. Offline When Designer is offline, you cannot program the lighting control system but you can: See and identify Helvar routers Change the IP addresses of Helvar routers Change which Workgroup Helvar routers belong to Upgrade Helvar router firmware, for example from Designer 4 to Designer 5, or Designer 5.3 to 5.4. Go online When you have configured the Helvar router IP and other settings in offline mode, you need to go online or connect. When you do this:: Designer connects to a workgroup of routers Designer reads router data (i.e. caches their data to Designer on your PC) You can see Designer s reading of data from the routers You can program the lighting control system Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 24 of 99
1.0 Connecting to a workgroup 1.1 Connect the router to the PC Use Ethernet cable either directly or through a network switch 1.2 Start Designer 5 software on your PC 1.3 Check in Routers View that the Helvar routers: Are on the network (i.e. are visible) Have the an IP address in the same range as your PC network interface (see previous section on Configuring Helvar routers) Have a cluster comms port value of either 60005 or 61000 to 65535. Have Designer 5 firmware 1.4 Select the Go Online button (or File > Go Online) 1.5 Select the workgroup you want to connect to (in the Connect to Workgroup window) a) Also make sure Synchronise Time is selected (ticked) b) Select Connect 1.6 Check progress of Designer Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 25 of 99
BACKGROUND INFO: Designer now begins to communicate with those routers in your selected workgroup. This can take up a minute. During this time it is reading the data from each router about its subnets, devices and the logic programming data (such as schedules, conditions and routing entries). a) Look at the progress bar. It should make steady progress. b) If the progress bar freezes for a long time, go Offline (select the Go Online button again), look in Routers View, and check the following: i. Helvar routers IP addresses ii. iii. iv. Helvar routers cluster comms port settings Helvar routers workgroup names Helvar routers software version v. Also check your PC s firewall settings 1.7 Check Designer is online a) When Designer has connected to the workgroup go to Devices View (Workgroup > Routers > Subnet(s) > Devices). To be certain that Designer is online, check: i. Mode notification The Mode Notification in the bottom right of the Designer 5 screen should now say Online, rather than Offline iv. Subnets v. Devices Image: Designer mode notification Offline ii. Workgroup The workgroup will have the name you specified in Routers View before Designer went online. iii. Routers The routers will have the IP addresses you specified in Routers View before Designer went online Each router will have one or two DALI subnets. A Helvar 920 router will have two DALI subnets and a DMX subnet and S-DIM subnet. The subnets should show the devices which are physically connected (wired) to that subnet. For example, if a router s DALI 1 subnet has 20 DALI LED luminaires connected to it, you expect to see 20 DALI LED drivers in that subnet. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 26 of 99
When you select a device (e.g. an LED driver, a sensor, a button panel or a dimmer) and right-click > Properties, the Properties view should show various properties. vi. Shell device tree If there is only a shell Device tree (e.g. only the name of a workgroup with routers but no subnets or devices or device properties visible), then Designer is not properly connected to the Workgroup. If Designer is not online, check again the items listed in this section ( Check Designer is online ). If you still cannot go online, contact your Helvar representative for help. Creating a virtual system in Designer BACKGROUND INFO: If you do not have a real router system, you can learn how to program Designer using a virtual system. This will give you a small system to program which includes: 1x 920 Router 1x DALI type 6 LED driver (to control the intensity of LEDs) 1x DALI type 8 LED drivers (to control intensity and colour temperature of tunable white LEDs) 1x Illustris panel 1x 135 7-button panel 1x 111 Dual slider control 2.1 Create a new designer design file a) File > New b) In Devices View, right-click Workgroup > Insert > 920 Digidim Router 2.2 Insert a DALI LED driver into the DALI subnet of the 920 router a) In Devices View, expand (click [+] ) the 920 router b) Expand (click [+] ) the first DALI subnet c) Right-click > Insert > Control Gear > LED Devices > DALI LED Driver Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 27 of 99
2.3 Insert a Tunable White DALI LED driver into the DALI subnet of the 920 router a) In Devices View, right-click the first DALI subnet b) Select: Insert > Control Gear > LED Devices > Helvar 35 W ic Tunable White LL35/2-E-DA-IC 2.4 Insert an Illustris 192 PB control panel a) In Devices View, right-click the first DALI subnet b) Select: Insert > Control Devices > Illustris > Illustris 192 PB Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 28 of 99
2.5 Insert a 135 button panel a) In Devices View, right-click the first DALI subnet b) Select: Insert > Control Devices > 130 Button Controls > 135 7 Button Up/Down 2.6 Insert a 135 button panel a) In Devices View, right-click the first DALI subnet b) Select: Insert > Control Devices > Sliders > 111 Double Slider Congratulations! You should now have a virtual system that looks like this: Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 29 of 99
If so, you can now start learning how to program Designer 5! Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 30 of 99
Over to you! Now you ve learnt the basics, it s time to have a go. Try these: A. Creating a system Look at the room you are in now, or think of a room you know well, such as your office. In the Designer 5 Device view, add virtual devices that could be used to effectively control the lighting in that room. B. Go online If your PC is connected to a router system, Go Online. Before you do, note the following: Workgroup name: Router serial number(s): Router IP address(es): Router s software version(s): Cluster Comms Port(s): Router system time(s): Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 31 of 99
C: Subnets and workgroup settings Note: if you are programming DALI systems and not using DMX or S-DIM, your trainer may decide to skip the sections on DMX and S-DIM. If this is the case, we recommend you work through these sections in your own time. What s in this section? This section tells you about the different subnets the router system can control plus the main settings for a Helvar workgroup (set of routers). In particular we will look at: Managing subnets in general (DALI; S-DIM; DMX) Managing DALI subnets Managing DMX subnets o DMX programming examples: Configure router to control external DMX devices DMX input controls LED dimmer DMX in control in the evening; DALI in the daytime Managing S-DIM subnets Managing workgroup settings Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 32 of 99
1.0 Managing all subnets (DALI, S-DIM, DMX) BACKGROUND INFO: How Designer communicates with Helvar routers Designer communicates with the Helvar routers via the Ethernet network. As well as the Ethernet port, the routers have the following subnet connectors: Helvar router Subnets 920 router 2x DALI subnets, S-DIM, DMX 910 router 2x DALI subnets 905 router 1x DALI subnet Helvar routers and subnets 920 ROUTER (2x DALI subnets; 1x S-DIM subnet; 1x DMX subnet) Lighting control devices such as button panels, sensors, LED drivers, ballasts and dimmers are wired to these subnet connections. When Designer goes online, it discovers the workgroup, routers and subnets as well as which devices are connected to each subnet. 1.1 View & rename subnets a) In the Devices view, expand the Workgroup tree (select the [+] ). b) You will see all the routers in that workgroup. Select a router to see its properties. USEFUL TIP: In online mode, you can edit the router name. You can edit other router properties if Designer is offline. c) Expand a router tree (select the [+] ). d) Depending on which type of Helvar router it is, you will see these subnets: Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 33 of 99
920 Router DALI Subnet 1 DALI Subnet 2 S-DIM Subnet DMX Subnet 910 Router DALI Subnet 1 DALI Subnet 2 905 Router DALI Subnet 1 e) To give a subnet a more easy-to-identify name, select the subnet, press F2 and rename it. Managing DALI subnets This section includes: A brief overview of DALI subnets and DALI addresses A short description of how a Helvar router system communicate with DMX devices Instructions on configuring a Helvar router s DALI subnet How to view in Designer the DALI devices on a DALI subnet USEFUL TIP: If you do not have any Helvar routers to connect to you can create a virtual system of routers and other lighting control equipment so you can learn how to program Designer. See Section B Creating a virtual system in Designer. BACKGROUND INFO: What is a DALI subnet? A DALI subnet is a collection of DALI devices all connected to the router on 'one' cable. The DALI protocol is used to communicate between DALI devices on a DALI subnet. DALI addresses Initially, DALI device addresses are automatically set by the router system but you can reassign them. Each DALI device has a unique long address and other information specified in the DALI standard. Helvar routers use this information to identify different types of devices and to differentiate different devices of the same type. For example, whether you have 50 or 5000 DALI LED drivers on a DALI system, Helvar routers can identify the different devices individually. DALI addresses maximum number Up to 64 devices can be connected to each DALI subnet provided that the power requirement of the devices does not exceed the subnet power supply limit of 250 ma. Helvar recommends that you use up to 63 of the available 64 addresses. When connected to a workgroup, the DALI subnet needs at least one free address before it looks for unaddressed devices. This means that if you have more than 64 addresses on the system and then reduce the number to exactly 64, the system will still report as if it has more than 64 devices, until the router is restarted. USEFUL TIP: Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 34 of 99
If you have 64 addressed devices, the system will still behave as expected but it will report that there are too many devices on the subnet. 2.1 Configure a DALI subnet (name; current consumption; autohealing) a) In Devices View, select a DALI subnet b) View and adjust the subnet settings in Properties View c) Name the DALI subnet. Give the DALI subnet a logical name and click OK. The name should be easily identifiable from the lighting schedule and other system diagrams. d) Check current consumption. You can check the subnet s total DALI current consumption (ma) here. The DALI standard specifies that the total current consumption of DALI devices in one DALI circuit (subnet) cannot be higher than 250 ma. USEFUL TIP: Note that this DALI current consumption is not the current consumption of the lamps (light sources). For example, a DALI LED Driver s DALI current consumption is 2 ma, but he LED it drives may be 1 A or more. To see how to enter load power consumption, see Circuit Power Loading in the section on programming DALI load interfaces. e) Enable autohealing. The default mode is True (= enabled ). Autohealing allows the automatic replacement of a single failed DALI device by allowing the new device to assume the same DALI address as the failed unit. 2.2 View devices on a DALI subnet Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 35 of 99
a) In Devices View, expand the DALI tree (select the [+] ) b) Any DALI devices connected to that DALI subnet will be shown. DALI devices include: Load Interfaces (Control Gear) LED drivers, ballasts, dimmers, relays, analogue converters and others. Input Devices (Control Devices) Button panels, Illustris panels, sensors, input units, sliders, rotaries and others. USEFUL TIP: The original DALI standard did not include control devices, so control devices for Helvar router systems must be of Helvar manufacture. 2.3 Connect DALI cabling to a router s DALI connector a) DALI devices are automatically discovered by the router and assigned a DALI address. When you connect the DALI cabling, wait for the DALI bus to refresh, as the router discovers the new device(s). b) After about a minute (when the router is discovering the DALI equipment) you will see the DALI devices in the DALI subnet(s). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 36 of 99
Managing DMX subnets What s in this section? A brief overview of DMX A short description of how a Helvar router system can communicate with DMX devices Instructions on configuring a Helvar 920 router s DMX subnet o Programming example: configure router to control external DMX devices o Programming example: DMX input controls LED driver o Programming example: DMX In control in the evening; DALI control at other times BACKGROUND INFO DMX DMX (Dimmer MultipleX) is a communications protocol developed by USITT (United States Institute for Theatre Technology) which is commonly used to control stage lighting and effects. The DMX standard is intended for lighting and entertainment system designers who want to integrate their systems of lighting equipment and accessories (including dimmers) with controllers made by different manufacturers. DMX Subnet Communication DMX512 is designed to carry repetitive control data from a single controller to one or more receivers. This protocol is intended to be used to control dimmers, other lighting devices and related nonhazardous effects equipment. DMX: fast, constant communication (at least once a second) DMX network communication is at 250,000 bits per second (250 kpbs) and it communicates constantly with the devices on its networks ("universes"). Communication in a DALI network is at a baud rate of 1200 bits per second but it sends far fewer messages than a DMX system. A DMX system sends out signals regularly to the devices on its network. Each DMX device (e.g. DMX spotlight) must be sent a direct level command by the DMX lighting control desk at least once every second. If this signal is not sent and received at least once a second, the DMX device goes to its default status. DALI: Send one command, then send another command only when required On a DALI network, a command is usually sent only once to a load interface. For example, if a button activates a Scene 1 command sent to an LED driver, the message is sent once and the LED driver changes its output level to Scene 1 staying at that level unless it receives a new, different command. The differences in protocol speeds and methods of messaging mean that, when integrating DMX and DALI controls, complications can occur. Depending on the situation, one way of avoiding these is to apply a condition to enable or disable the DMX subnet. An example of this is given in Programming example: DMX In control in the evening; DALI control at other times. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 37 of 99
Helvar 920 router: Select either DMX In or DMX Out The DMX subnet can either be in DMX Out operation or in DMX In operation. A DMX Lighting Control Console (or Lighting Desk) controls the levels of channels. The level range is from 0 to 255. DMX In operation Control DALI or S-DIM channel or group connected to same 920 router In DMX In mode, you can map only directly to the DALI or S-DIM channels connected to same 920 router (and not to another router in the workgroup). In multi-router systems you can use redirects or links to groups to control DMX channels connected to a particular Helvar router. Control of groups: Note the protocol comms speed differences In DMX In mode, a DMX input can control a group but care must be taken that the (fast) DMX protocol is not used to control a device that uses the (slower) DALI protocol or S-DIM. Control DALI subnet, S-DIM subnet or group DMX In can be used to control individual devices in: DALI subnets on the same 920 router S-DIM subnet on the same 920 router Groups that exist in the same 920 router To control groups or devices in DALI or S-DIM subnets connected to other routers, use redirect routing entries or link routing entries. If the DMX subnet is in DMX In operation, then the S-DIM and/or DALI devices are controlled channels (inputs) on their controlled S-DIM and/or DALI subnets. These subnets can support up to 512 channels in from one DMX source. When in DMX In operation and a Helvar router sends a command to a DMX channel (for example a 100% direct level command), the controlled DALI or S-DIM channel responds to that command (for example, goes to 100%). DMX Out operation The DMX subnet can drive up to 512 DMX output channels. When the DMX subnet is in DMX Out operation, if you send a command to set a DMX channel to 100% then the channel goes to 255 on the DMX device. If you send a command to set a DMX channel to 0% then the channel goes to 0 on the DMX device. All other levels are scaled proportionally. If the DMX subnet is in this operation, then the DMX devices on the subnet operate as loads (control gear) such as LED drivers, dimmers, relay units and ballasts. Control gear receives messages from control devices via the router and performs the relevant action: for example, it sets the lighting (lamps) that it controls to the relevant level. Some control may be possible at the device itself. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 38 of 99
3.1 Configure a DMX subnet: In/Out; Enabled/Disabled; Condition a) In Devices View, select the DMX subnet b) View and adjust the subnet settings in Properties View c) Name the DMX subnet by giving it a logical name and click OK. d) Choose the mode of operation: either DMX In or DMX Out. The default mode is DMX In. Select the mode from the drop-down menu, and click OK. USEFUL TIP: DMX Out is for control of external DMX devices such as LED Drivers. DMX In allows a DMX lighting desk to control outputs connected to the router e) Enable or disable the DMX subnet. The default mode is True (= enabled ). To disable the DMX subnet, choose False f) Click OK 3.2 Programming example: Configure router to control external DMX devices Follow these steps to configure a router to be control devices on a DMX network (connected to a 920 router). Note that in this example, we insert only one DMX device. To control more DMX devices, you need to insert more DMX devices in the DMX subnet. USEFUL TIP: To send control messages to a DMX device, the DMX address in the Designer Devices View must match the DMX address on the DMX network connected to the 920 router. The addresses of the actual DMX devices are set locally: follow the manufacturer s instructions. a) Select the DMX subnet in the Devices View. In Properties View, check that: i. Mode is DMX Out ii. iii. Enabled is True Condition is Always. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 39 of 99
b) To insert a DMX device, right-click the DMX subnet in Devices View. c) Select Insert > DMX Device d) To configure the DMX device, go to Devices View: The DMX subnet is named DMX Out Subnet The DMX device is named DMX Channel @... DMX Out Subnet and DMX Channel in Devices View e) Rename the subnet and the device if required (F2). f) Now you need to make the DMX address in the Designer Devices View match the DMX address on the DMX network connected to the 920 router. To change the DMX Channel address: i. In Devices View, select the DMX Channel in the DMX Out Subnet ii. Right-click > Change Device Address Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 40 of 99
iii. Enter the DMX address of the DMX device you want to control (in this example: 512), and select OK. iv. In Devices View, DMX Channel has now been assigned its new DMX address in the DMX Out Subnet: g) If required, you can now group the DMX Channel and program scenes for recall as with other controlled devices. For example, create a DMX address 512 group and put your DMX Channel(s) and a button panel in the group. IMAGE: DMX Channel in a group in Designer 5 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 41 of 99
IMAGE: Button panel set to recall scenes for a DMX Channel in Designer 5 IMAGE: Scenes programmed for a DMX channel (Designer 5 Scene Table). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 42 of 99
3.3 Programming example: DMX input controls LED driver Follow these steps to configure a DMX lighting desk to control an LED driver on DALI subnet 1 of a 920 router. In this example, the DMX device will control a DALI LED driver at address 2 on DALI subnet 1, as shown here: USEFUL TIP: If there is no LED driver on DALI subnet 1, right-click on DALI subnet 1 > Insert > Control Gear > LED Drivers > DALI LED a) Select the DMX subnet in Devices View. In Properties View, check that: i. Mode is DMX In ii. Enabled is True iii. Condition is Always. b) To insert a DMX device, right-click the DMX subnet in Devices View c) Select Insert > DMX Device d) To configure the DMX device, select the DMX device e) Go to Properties view and apply the following settings: i. Controlled Subnet: DALI Subnet 1 ii. Controlled Channel: 2 iii. Fade Time: 12 s (or another fade time you prefer) f) Click OK Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 43 of 99
g) To check the changes, go to Devices View. You will see the DMX input device settings have changed. 3.4 Programming example: DMX In control in the evening + DALI control at other times This programming example is for a space that is for general use during the day (DALI lighting control) but which is used for an entertainment show in the evening (DMX In control). This example assumes that the DMX In system has already been programmed and the DMX signals are mapped to channels in the DMX subnet. Daytime: DALI lighting control In the daytime, a Digidim button panel is used to recall scenes in the DALI lighting system. Evening: DMX lighting desk controlling lights for the show (DMX In of 920 router) In the evening, the lighting technician should: Press button 4 to allow DMX In control before the show Use the DMX lighting desk to control the lighting during the show Press button 3 after the show. Lighting control now reverts to the pre-set schedules and no DMX commands are accepted If the Lighting technician forgets to press button 3 after the show, control will automatically revert to scheduled control at 01:00. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 44 of 99
To achieve this, follow steps a to e: a) Name the controlled group Show Lounge Rename the group for the loads and button panel to Show Lounge (in this example, Block 1, Group number 1) b) Program the lighting scenes: i. Scene 1 ("DAY"): all lights on 100%, 'DMX In' disabled ii. iii. iv. Scene 2 ("NIGHT"): all lights off, 'DMX In' disabled Scene 3 ("ECONOMY"): all lights on at 5%, 'DMX In' disabled Scene 4 ("DMX MODE"): all non-dmx lights off, 'DMX In' enabled ('DMX MODE ACTIVE') c) Create a condition: DMX MODE ACTIVE which is TRUE if Last Scene called in Block was DMX MODE Scene 1.4 i. View > Conditions ii. iii. iv. Right-click (...) Conditions > Insert > AND Condition Rename the AND condition DMX MODE ACTIVE" (right-click > Rename) Right-click "DMX MODE ACTIVE" > Insert > Last Scene in Block v. Select "Last Scene called in block was...". Input these settings in Properties view: vi. Click OK 1) Last Scene in Block 2) Group Name: Show Lounge 3) Group Number: 1 4) Scene Block: 1 5) Scene Number: 4 d) Apply the "DMX MODE ACTIVE" condition to the DMX Subnet i. Mode: DMX In ii. iii. Enabled: True Condition: DMX MODE ACTIVE Now when button 4 is pressed, DMX In is active and DMX commands are accepted. If another scene is recalled (e.g. if buttons 1, 2 or 3 recall scenes 1, 2 or 3), then the DMX ACTIVE condition is False, and DMX In is disabled. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 45 of 99
e) To create a schedule to recall a scene after show time: i. View > Scheduler ii. iii. USEFUL TIP: Right-click > Insert > Scheduled Scene Recall In the Schedule Properties view, input these settings: Common Name: Show Lounge 1 am daily ECONOMY Schedule; Trigger Time Time Style: Clock Time Time: 01:00:00 Schedule action Group Name: Show Lounge Group Number: 3 Fade Time: 16 s Being able to create a schedule to recall a scene after showtime is useful in case the lighting technician forgets to press the "ECONOMY" button (button 3) after the show. To make sure that DMX is disabled by 1 am every morning, you should schedule a scene recall. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 46 of 99
Managing S-DIM subnets BACKGROUND INFO: Helvar 920 routers have one S-DIM subnet which can support up to 128 S-DIM devices within the limits of 252 S-DIM addresses. S-DIM protocol S-DIM is an internal Helvar protocol used to communicate between S-DIM devices (control gear) on an S-DIM subnet. S-DIM can have cable of up to 1000 metres and allows very long fade times. Setting S-DIM addresses S-DIM addresses are set manually at the device by a DIL switch or menu selection. There can be one or more addresses depending on how many channels the device has. For example, a 454 dimmer has 4 dimming channels and so 4 S-DIM addresses. 4.1 Set S-DIM addresses for a 454 dimmer a) On the 454 unit, press both front panel buttons until display shows Ads b) Press the lower button to cycle to the channel that is required to be changed c) Press and hold the lower button to change the address d) Press both front panel buttons to store new address, the display will show 888 USEFUL TIP: On multi-output devices, a base address can be set by selecting bas at step 2. A base address will be assigned to channel 1 and automatically take sequentially addresses for the remaining channels. 4.2 Viewing and programming S-DIM devices in Designer 5 For S-DIM devices to appear in the S-DIM subnet of a 920 router in Designer 5, you must manually set the S-DIM addresses (see above). a) In Devices View, select the S-DIM subnet and [+] to expand the tree. b) Connect the S-DIM cabling and wait for the bus to refresh. You should now see any S-DIM addresses listed. Types of devices can be: USEFUL TIP: Load Interfaces Dimmers Relays Output Control Units If an address is subsequently changed, the original device address will appear as missing and can then be deleted from the router s database. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 47 of 99
Managing workgroup settings What s in this section? This section tells you how to adjust some workroup settings including the geographical location. When you first go online, you should check and adjust these settings. Once set, you can adjust them but generally you won t need to readjust them any further. USEFUL TIP: To adjust workgroup properties, Designer must be online. a) Chose Simple Mode. b) Select Workgroup in Devices View. c) Click to expand the workgroup and you ll see all its available routers. In the example above, the workgroup has just one router. d) When you select the workgroup, you can view and adjust its settings in Properties View (if not open: F4 or View > Properties) Workgroup properties e) In Properties View: i. Verify/set latitude and longitude latitude The correct latitude/longitude must be set for accurate sunrise/sunset time scheduling ii. iii. iv. Sync Router time: usually True (when Designer goes online, the router time is updated to match the PC s time and date) Verify time zone (set from PC) Verify/set daylight saving Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 48 of 99
v. Activate HelvarNET Push Messages (used with BACnet and Tridium integration) Over to you! Now you ve learnt the basics, it s time to have a go. Self-test Make sure you know the answers to these questions: a. What is the maximum number of devices on a DALI subnet? b. Why does each DALI device have a long address? c. Why would you change DALI device short addresses in Designer? d. What subnets does each of these Helvar lighting routers control? a. Helvar 905 router b. Helvar 910 router c. Helvar 920 router e. Why should you rename router and subnets? Try this If you have a real router system, go online, then right-click a subnet (in the Devices View) and select Identify. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 49 of 99
D: Identify, Name and Group devices What s in this section? This section tells you about: Viewing devices in the routers subnets Identifying devices in Identify View Naming conventions BACKGROUND INFO: Lighting loads A lighting load is a lamp and/or the driver, ballast, dimmer or other equipment driving or controlling the lamp. It s called a load because it consumes electricity. Lighting loads include: USEFUL TIP: Mains-powered tungsten lamp Mains-powered tungsten lamp connected to a 452 universal dimmer Flourescent tube connected to a DALI ballast Flourescent tubes connected to a 472 analogue interface unit HID lamp connected to a 499 relay unit When first discussing a lighting control system, one of the first questions is what loads do you want to control?. The (correct) answer to this will determine which control equipment you select for the system. Load interface units/control gear Control gear is equipment connected to lamps to adjust the brightness, colour temperature or colour. Control gear receives messages from control devices via the router and performs the relevant action. For example, a 452 dimmer (connected to 10 tungsten lamps, for example) receives a Scene 1 message from the router and dims the lamps to that level. Load interface units (control gear) include: Dimmers LED drivers Electronic ballasts Ballast controllers 472 analogue input unit 474 relay unit Why is it necessary to identify devices and when? Although the example system in these instructions is very small (with only 5 devices on one DALI subnet), Helvar router systems can control many thousands of devices over many floors of a building and in more than one building. When a new piece of DALI lighting control equipment is first connected to a Helvar router system, it has a generic name. If, for example, you connect 50 DALI LED drivers to a subnet, they will initially all have the same name. You need to identify and logically name the devices in the system to make programming simpler not only for you but for other people who subsequently program the system. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 50 of 99
USEFUL TIP: Once the system has been installed and all wiring has been properly installed, the system is ready for programming (commissioning). To program a system, you need to find out which devices in Designer match the devices on the system diagram (the floor plan(s) with diagrams of the lighting control system). Designer s Identify function lets you do this. When you identify a device, name it logically (for information on naming devices, see the next section). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 51 of 99
1.0 Viewing devices in Designer When you go online in Designer, the program reads the data from the Helvar routers in a workgroup. This information includes which devices (control gear and control devices) are connected to the routers subnet connectors. 1.1. View the routers in a workgroup a) In Devices View, expand the workgroup tree (select the [+] ) to see all the routers in that workgroup. b) Select a router to see its properties. USEFUL TIP: You can edit the router name in online mode. Edit other router properties if Designer is offline. 1.2. View a router s subnets in Devices View a. Expand a router tree (select the [+] ). Available subnets Depending on which type of Helvar router it is, you will see these subnets: 920 Router DALI Subnet 1 DALI Subnet 2 S-DIM Subnet DMX Subnet 910 Router DALI Subnet 1 DALI Subnet 2 905 Router DALI Subnet 1 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 52 of 99
1.3. View the devices in the DALI subnet Expand a subnet (select the [+] ). In this example, the subnet has one of each of these devices: - DALI LED: DALI type 6 LED driver (to control the intensity of LEDs) - LL35/2-E-DA-IC: DALI type 8 LED drivers (to control intensity and colour temperature of tunable white LEDs) - 7-button panel (135) - Dual slider control (111) - Illustris panel (192) Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 53 of 99
Identify devices 2.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. 2.2. Identify a device In Devices View, select a device, right-click > Identify (or select a device and press F3). The Identify View will open. When you identify a device, it will react as follows: Device Router LED driver Dimmer Ballast controller Converter (e.g. 472) Ballast Transformer for LV halogen lamps Relay Button panel Illustris panel Sensor Slider Rotary control Input unit 444 What it does to identify 4 LEDs flash red on its front panel Lamp flashes on and off Relay will open and close LED indicator flashes on and off Nothing: you have to match the serial number, or activate the switch input and check the Event Log. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 54 of 99
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. 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. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 55 of 99
2.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. 2.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. 2.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). 2.6. Identify a subnet To identify a subnet, right-click the subnet and select Identify. This is a useful way to check which physical devices are on a subnet. The devices on the subnet will react depending to the settings in Identify View. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 56 of 99
1. Rename devices When you have identified a device, give it a logical name. Make sure the names match the names on your floor plan (or system diagram) 3.1. Rename devices in Device View a. In Devices View, select a device, right-click > Rename b. Change the name of DALI LED to Room01_LED_01 and click OK. Note: You can also rename devices in Properties View. c. Rename the other devices: Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 57 of 99
You have now identified and renamed the devices in your system. Next, change their DALI addresses and group them. 3.2. Naming conventions Underscore instead of space. Do not put spaces in device names: use _ (underscore) instead. No special characters (accents, : ; ( ) { } [ ] - ) Designer software and Helvar routers can deal with spaces in names, but many other building control systems do not. If the Helvar system is integrated with, or communicates with other control systems, it is best to use computer-friendly characters. Router names Particularly in larger systems, we recommend naming routers based on: - Floor (storey) - Distribution box ID and location (e.g. room location, and which distribution box) Subnets Name them according to the floor and room(s) they are controlling. Devices Start their names with room numbers. E.g. 221_sensor_03 Name in Designer must match name on your diagrams Make sure the names used in Designer are easy to match to the device names on your building diagrams and system diagrams. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 58 of 99
Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 59 of 99
2. Organise short addresses This section tells you: About long and short addresses of DALI devices The order devices are listed in in Devices View Why to change the address of a device How to change the address of a device Long address and short address When manufactured, each DALI device, such as LED drivers, ballasts and dimmers, is given a 24-bit 'long address'. The Helvar router system uses this number to identify devices as unique. The chance of two devices having the same 'long address' (officially called a 'random address') is very small. You can see this 'long address' in the device's Properties View. When a DALI device is connected to a router system, it is given a 'short address' (DALI address) from 1 to 64. This address is after the @ in the device tree. Subnet s devices listed in order of short address In the Devices View, a subnet's devices are listed in order of short address (1 at the top, 64 at the bottom). Why to change the address of a device Listing a subnet's devices in a logical and clear order helps to make commissioning quicker and easier, and makes troubleshooting easier. To change the order of devices, change the short address of a subnet's device. 4.1. How to change the address of a device 1. Select a device > right-click > Change Device Address. Type the new address (1-64). 2. If you type in the address of an existing device, Designer asks you to swap addresses or select the next available address for the other device. 3. Click OK to accept the change. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 60 of 99
3. Group the devices This section tells you: Why to group devices When to group devices What is ungrouped? Grouping control gear (load interfaces) Grouping control devices (input devices) How to group devices: 2 main methods Grouping subdevices Groups View Why to group devices A Helvar router system gives each device a digital address, and allows these individual devices to be controlled individually or as part of a group or groups. To allow devices to be controlled as a group, put the device in a group or groups. To make a sensor control an LED driver, put the sensor and driver in one group. To make a button panel control some LED drivers, ballasts and dimmers, put them in one group. Often all the devices in one room are put in one group. To allow separate control of different rows of lights, put the drivers for each row in one group. When to group devices This is the recommended process for identifying, naming and grouping devices: 1. Identify devices 2. Name devices logically 3. Create groups 4. Name groups logically 5. Put devices into groups Ungrouped A new device will be ungrouped, that is, not assigned to a numbered group. Any devices which are ungrouped can be controlled individually or, with all other ungrouped load interfaces, by broadcast message (a message broadcast to the entire system). Finding ungrouped devices In Groups View (View > Group View) double-click on Ungrouped to see any ungrouped devices. Grouping control gear (load interfaces) Control gear (e.g. LED drivers, ballasts, dimmers) can exist in one group, or in many groups. This means that an LED driver in a classroom could be a member of these groups: - Row of lights near the windows Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 61 of 99
- Back of the classroom - Classroom - All lights on Floor 1 (for emergencies, reports, or for making sure all lights are off) - All lights in the school (for emergencies, reports, or for making sure all lights are off) Grouping control devices (input devices) Control devices (e.g. buttons, button panels, sensors, input units) can exist in one group only. 5.1. How to group devices 5.2. Method 1: Groups view. This method is quick and easy, using drag and drop. a. Create a group in in Groups View by clicking the Add icon. b. Rename groups by highlighting the group and hitting F2 on the keyboard and Enter to save this. c. From the Devices View, highlight all relevant devices and drag into the correct group in the groups window. Multiple devices can be highlighted at the same time and dragged into the correct group by holding Ctrl when selecting. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 62 of 99
d. Double click the group in the groups window to view what devices sit in this group. 5.3. Method 2: Properties view. If you are editing properties in Properties View, it is easy to edit group memberships here too a. In Devices View, select the device (or multiple devices). b. In Properties View edit the group memberships. Use append groups to add devices to groups and select ok to save this. 5.4. Method 3: Grouping Subdevices (e.g. buttons) It is possible to insert buttons from the same device into multiple groups. a. Expand the device to view all available buttons by clicking the Expand icon on the device in the device tree. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 63 of 99
b. Select the relevant buttons required to be grouped together and follow either Method 1 or Method 2 Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 64 of 99
Over to you! Now you ve learnt the basics, it s time to have a go. Self-test Make sure you know the answers to these questions: a. Why do you 'identify devices'? b. When you identify a sensor, what does the sensor do? c. When identifying loads connected to lamps (e.g. LED drivers, ballasts, dimmers) the lamps usually flash on and off. What are two other options when identifying loads that are connected to lamps? d. True / False? In the Identify View, you can name and group devices. e. A 444 Mini Input Unit has no LEDs to help with identification. What can you use to identify a 444 Mini Input Unit, in Designer? f. Why do you rename devices? g. What is the highest possible short DALI address? h. How do you change a device's short DALI address? i. What are two different ways to group a device? Try this Select a DALI subnet and identify and rename the devices using the Identify View (i.e. not the Devices View and Properties View). Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 65 of 99
E: Scene Table and Event Log This section tells you how to: Use the Scene Table to program lighting scenes Recall scenes from the Scene Table, View devices in the routers subnets Using the Event log Scene Table This section tells you: What is the scene table? What is a scene block? What are the default levels? Changing levels in the scene table. What is last level? What is ignore? Recalling a scene from the scene table What is the scene table? In the scene table you program scenes by editing the levels of the different load devices in a group for different scene recalls. The scene table for each device will be the same across multiple groups if that device sits in multiple groups. For example if a device sits in Group 1 and Group 2 and scene 1.1 is changed in Group 1 this will also change the level in Group 2. What is a scene block? Scenes change across multiple groups when altered in the scene table. Different blocks of scenes can help logical programming. For example you can use one Scene Block for summertime scenes (or daytime scenes), and another for winter scenes (or night scenes). There are a total of 8 scene blocks with 16 scenes per block. The scene block is signified by the prefix to the scene number eg. Scene 1.10 defines scene block 1, scene 10. What are the default levels? Out of the box devices will have default levels which sit in the scene table which have been listed out below: Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 66 of 99
There are certain scenes which are reserved for particular features of designer which have been listed out below: Scene 13- OFF scene for a PIR sensor Scene 14- transition scene for the PIR sensor Scene 15- default scene for OFF as recalled on a button (often the O button ). Changing levels in the scene table a. Select the scene table icon from the toolbar at the top of screen. The scene table can also be selected by clicking view>scene table or pressing Ctrl + T. b. Select the relevant group from the groups view to populate the scene table with the selected group. c. To change the default values double click the relevant cell in the scene table and type the desired level, click ok to save this level. When changing the levels in the scene table in live mode these will alter the lights in the field whilst working. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 67 of 99
Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 68 of 99
What is last level? Last Level: a last level (L) command will recall the levels which the lights were on prior to them being switched off. If the lights were to be lowered using a raise lower button to 20% prior to being switched off, a last level scene would bring the lights back on to 20%. In the scene table this is set by inserting an L into the scene table instead of a number. What is ignore? Ignore: an ignore command (*) in the scene table will keep the lights at the level they are currently on when recalled. This is useful in an instance where some lights are needed to be kept the same when altering others scene. In the scene table this is set by inserting a * into the scene table. Recalling a scene from the scene table It is possible to recall a scene from the scene table by double clicking the green arrow on the left hand side. Ensure that you are in Live Mode when double-clicking the arrow for the scene to be actually recalled in the room(s). If Designer is in Blind mode, changes to the Scene table will not take effect in the actual lighting system. Recalling a scene using Go To You can also recall scenes using the Go To icon (in Designer s main Toolbar), which is useful when recalling scenes that involve routing entries. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 69 of 99
Event Log This section tells you: What is the event log? Viewing the event log Exporting an event log file What is the event log? The event log is used to view what is happening in the system in terms of scenes recalled and where these scenes are being recalled from. Whether that be scenes recalled manually from the PC or router, direct levels being recalled or scheduled functions like emergency testing. This is a useful tool to discover why things are happening and when. Viewing the event log a. To view the event log select View>Event Log b. The event log will open up as default in a window at the bottom of the Designer software. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 70 of 99
c. To test the event log use either a go to command from the toolbar at the top of the software or double click the green arrow from the scene table. d. As displayed below this will add the corresponding command line to the event log. This information will include the event, time and date and the source. Exporting the event log It may be necessary to export the event log for future use when trying to fault find on a system when it isn t behaving as expected. There are multiple functions for the event log which are useful when using on a live site, these are listed below: a. Play and Pause- It may be necessary when working on a live site to play and pause the event log as there may be a constant stream of commands coming through from across the system. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 71 of 99
b. Clear- Clear any previously recorded values in the event log so that the user can look at a clean slate. c. Save- The event log can be saved and exported as a.csv file for use at a later date off site. This is useful when troubleshooting. Over to you! Now you ve learnt the basics, it s time to have a go. Self-test: a. In the Scene Table, you can program 8 Blocks of scenes. How many scenes are available in one Scene Block? b. What does '*' mean in the Scene Table? c. When you have typed a number in the Scene Table, which button (in Designer) should you select? d. Why is the Event Log useful for troubleshooting? e. Why might you clear the Event Log? Try this: a. Open the Event Log. In the Devices Tree, use a mimic (button panel or sensor) to recall scenes (or use Go To ). What is shown in the Event Log? Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 72 of 99
F: Schedules and Conditions This section describes how to set up scheduled events and how to program and apply conditions. Scheduler This section describes: What the scheduler is Types of schedule How to set up a schedule What is the Scheduler for? Use the scheduler to automate events. For example, you can set all office lights to go off at 8pm every workday evening. You can use the scheduler for more complex operations, such as having lighting controlled automatically by sensors in the evenings and at weekends, but during working hours, the lighting can be controlled by button panels and sensors. All schedules as default will occur at a set time every day. This in some instances is suitable though other times will require a condition to be added which will be covered in a later exercise. Types of schedule Schedule Scene Recall Recall a scene from the scene table at a set time. Scheduled Daylight Saving Allow the astronomical time clock to adjust for daylight savings times where necessary. If a system contains schedules and this is not set up then the times will at some point in the year be 1 hour out. Scheduled Emergency Tests Run function tests and duration tests on DALI emergency lighting devices. Time Triggered Ethernet Output Send a data string to be output over the Ethernet port at a set time. This is useful when integrating with third party devices or for communication between workgroups. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 73 of 99
Setting up a schedule a. Open the Scheduler: View>Schedule. c) b. Create a schedule: right-click in the schedule window and select insert and the relevant schedule required. d) c. Program the schedule. In the Scheduler view, the new Schedule shows in yellow, signifying that this needs configuration. d. Right-click the schedule and select Properties, to open the Properties view. e. In the properties window enter the schedule parameters. In the example shown above, the group has been allocated and time has been set. This will now recall scene 1.1 in Group 1 at 18:00hrs with a fade time of 2 seconds. e) Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 74 of 99
Conditions This section tells you: What is a condition? Types of boolean condition Terms of the condition Setting up a condition What is a condition in Designer (in a router system)? A condition is a property that lets you control whether, for example: A button is enabled or disabled (for example during daytime and nighttime) Lights in a glass corridor are turned off when outside light reaches a certain level A different scene can be scheduled in summertime and wintertime A button panel is functional only in a school term-time The button panels in a theatre auditorium work only when a button is pressed by the show s technical manager at the end of each show. A sensor system operates as presence detection outside main office hours, but as absence detection during office hours. You can add conditions to various aspects of the Designer programming which perform different computations or actions depending on whether a condition is TRUE or FALSE. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 75 of 99
Types of boolean condition There are 4 boolean expressions available for use in the designer software all of which are listed below (for the example 2 terms are used but any number of terms can be used): Terms of the condition The terms of the condition are the data input into the boolean expression which determine whether the output of the condition is TRUE or FALSE. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 76 of 99
Types of condition Time Range Set a range of times, during which the condition is met. This is useful when creating a condition for a period of up to 24 hours. Note that the period may span two days, such as from 17:30 to 05:45. Example: To enable a button panel to function between 7 am and 6 pm each day, set the Time Range condition (07:00 to 18:00), and name the condition Daily_7_to_18. In the Device Tree, select the button panel, and in the Properties window, select Daily_7_to_18 in the Condition property. Outside those times, the button panel will be disabled. Days of the week Set a range of days, during which the condition is met. Typical uses: Weekdays: select Monday, Tuesday, Wednesday, Thursday and Friday Weekends: select Saturday and Sunday Programming example: To enable a button panel on weekends only (e.g to allow manual control of an office s lights) 1. Create an AND condition 2. On the AND condition, right-click -> Days of the week 3. In the Properties window a. Select Saturday and Sunday b. In the Name row, enter Weekends c. Click OK 4. In Device View, select the button panel 5. In the Properties View, select the Condition Weekends, and click OK Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 77 of 99
Days and month Set a specific calendar day: - A specific day of a specific month - A specific day of Every Month. Examples: - To run an emergency lighting test on 28 th of each month, select 28 and Every Month Annual date range Set a range of days in a year, during which the condition is met. Typical uses: - School term and holiday dates - Seasons - Factory shutdown dates Programming example: To have different scenes in Winter and Summer (for example, intensity levels high in Winter and lower in Summer time) 1. Create an AND condition 2. On the AND condition, right-click -> Annual date range 3. In the Properties window a. Select the dates for Summer b. In the Name row, enter Summer c. Click OK 4. In Groups View, select a group of lights, then open the Scene Table. 5. In the Scene Table, program Scenes in Block 2 for Summer, and Scenes for Block 1 for Winter. 6. In Routing Entries View, create a Scene Redirect routing entry (Block 1 to Block 2) 7. Apply the Summer condition to the Scene Redirect routing entry. 8. In Winter time, the scenes in Block 1 are used, and in Summer time, the scenes in Block 2 are used. Date range Set a range of days spanning any number of years, during which the condition is met. Analogue input Set a range of input values for inputs from the Helvar 942 analogue input device. Typical uses: - Creating a condition for a temperature input (e.g. if temperature higher than 35 degrees C, activate a relay) Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 78 of 99
Switch input Set a condition dependent on a switch input, from a Mini Input Unit (444) or Analogue Input Unit (942). Typical uses: - Control different groups depending on a switch indicating if a partition is open or closed - Enable or disable auditorium button panels depending on a switch in a theatre control room. Programming example: a. With 444 Input Unit set to Edge Mode (Closing contact and Open contact); set the Input Source to, for example, 123. b. Create an AND condition c. On the AND condition, right-click -> Switch Input d. In the Properties window i. Enter the Switch Input s Input Source (123 in this example) ii. Select the group number of the Input Unit iii. Click OK e. When the switch is open, the condition is not met (check in the properties of the Switch input condition > Condition Is Met = False Condition reference Set a reference to another condition in the Conditions view. This Condition reference condition is met only when all terms in the referenced condition are true. Last scene in block Set a condition that is true, if the scene defined in the term is the last scene recalled in the scene block. Example uses: - Disable DMX Input when a specific scene in a block is called - Enable auditorium button panels after a button is pressed in the theatre control room Light Level This term allows you to reference the light level received from a light sensor, either internally or externally. Note: the value received from the light sensor will be from 0 to 200. When setting up the light sensor, check with a luxmeter what lux value in a particular place is equivalent to the value transmitted by the light sensor. For example, 96 (the value from the sensor) may be equivalent to 604 lux on a table top in the room. Typical uses: - Close or open blinds if a certain light level is sensed Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 79 of 99
Setting up a condition Note: to create a condition: a. Choose a Boolean expression (AND, NAND, OR, NOR). b. Within that expression, select Time Range, Days of the Week, Day and Month, Annual Date Range, Date Range, Analogue Input, Switch Input, Condition Reference, Last Scene in Block, or Light Level c. Select the conditions icon from the toolbar (or View > Conditions). d. The conditions window will open as default in the same area as the Devices View. e. Create the condition: four steps i. Right-click Conditions -> Insert -> AND Condition (or other boolean expression). ii. Although the condition is not yet set up, rename the condition to make it easily identifiable. iii. Right-click the newly created condition and select rename or single click and press F2 on the keyboard. iv. Right-click the renamed condition selecting insert to add a term. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 80 of 99
f. Edit the condition s terms Right-click the condition term (e.g. Days of the Week ) and select Properties. g. In the properties window, edit the terms of the condition. There is an option to invert this: select this to make the term inverse of what is selected (e.g. inverse of Monday is all the other days of the week. Is Met The Is Met row shows whether the condition is met or not (TRUE or FALSE) Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 81 of 99
Apply a condition Once the condition has been created, you need to apply the condition to another part of the Designer program. Examples: How to apply a condition i. Apply a days of the week condition to a button panel to enable or disable it. ii. Apply a date range condittion to a schedule, to run a schedule on certain dates only. iii. Apply a time condition to a routing entry, so presence detection runs in the evenings, but absence detection runs in the daytime. Select the relevant item In the Properties View, select the condition created from the drop down menu Click OK. For the condition created in the above example this will be TRUE only on a weekday, therefore anything this is associated with will only be active on a weekday. Over to you! Now you ve learnt the basics, it s time to have a go. Self-test: a. Name two events that the Scheduler can be used to trigger. b. Name one benefit of the Scheduler c. What type of condition would you use: i. if you want to activate blinds when there is bright sunshine? ii. iii. iv. to disable a button panel automatically every weekend? to change lighting control options during school holidays? to change lighting controls when a partition wall is open or closed? Try this: a. On a 135 button panel (you can use a virtual panel), enable button 1 at weekends, and button 2 on weekdays. b. Schedule an LED driver to come on to 45% at 05:45 every Monday. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 82 of 99
G: Sensor control (occupancy detection and constant light) Sensors are used in a Helvar router system to control lighting, based on whether someone is in the room or not, and on the measured ambient light level. This section tells you about: Sensor functions Setting up presence detection Setting up absence detection Setting up constant light Sensor functions Depending on what variant of sensor is being used the designer software has the ability to set these up to provide 3 different functions: Presence detection Lights switch on automatically when someone comes into a room, and are dimmed, then switched off, when nobody is in the room. Absence detection People have to switch on the lights manually (usually using a button panel). When nobody is in the room, the lights are dimmed, then switched off, when nobody is in the room. Constant light The system regulates the light level depending on the light level reading from a photocell in a multisensor. So, for example, if a large amount of daylight is coming in through the windows, the articificial light is dimmed. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 83 of 99
Setting up presence detection a. Identify the sensor to ensure that the sensor is controlling the correct set of luminaires. Right-click the sensor and select identify, as with identifying the luminaires this will cause the sensor to flash. b. As with the grouping of the luminaires the same process applies for the sensors. The simplest way to group them is to highlight the PIR which has been identified then drag and drop to the corresponding group in the groups window. c. Once the PIR is grouped with the luminaires it requires a routing entry for it to function. In the Routing Entries tab right-click and select Insert>Presence Detection, to insert a presence detection routing entry. d. Right-click the routing entry (which will be highlighted in yellow until configured) and select properties to open the properties window. e. The routing entry first needs associating with the relevant group. From the drop down menu in the properties window select the group containing the PIR and the luminaires. After selecting the group type in the relevant scene block. Click OK to save. This is the basic requirment for getting the sensors working, though this will be using default values. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 84 of 99
f. There are several settings which may need changing from default which have been listed out below: Scene Number: shows which scene number within the selected scene block will be recalled upon presence detection, typically L (for Last Level) Fixed or Constant Light: set this depending on whether a standard scene recall (for presence detection or absence detection) or constant light is required. On Time: the duration the luminaires will stay on for when presence is detected. For example, as long as someone is in the room, the lights will stay on for another 10 minutes. Transition Time: after the On Time has ended, the transition time begins. This will recall scene 14 from the scene table which as default is 10%. Exit Delay: when someone turns out the lights, the sensor is deactivated for a short time. This time is the Exit Delay. The Exit Delay stops the sensor from retriggering the lights immediately when somone has just switched off the lights. Without Exit Delay, someone could turn off the lights, but their hand movement could turn the lights back on (via the sensor). Test Mode: When this box is ticked the timeouts are shortened to make testing quicker. Fade Times: the fade times between each of the timeouts can be set from here. g. Click OK. After editing these settings, click the OK button to save the settings. h. To test that the routing entry works double click to PIR either in the device tree or from the groups window. This will bring up a mimic of the PIR. i. To simulate movement click the icon of the stick person on the bottom left of the mimic. To simulate a timeout to transition click the red clock and again to simulate a timeout to off. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 85 of 99
Setting Up Absence Detection To set up absence detection, set up a presence detection routing entry, but then change the Presence Checking from OFF setting: a. In the properties window for the presence detection entry for the option Presence Checking from OFF select the option Never from the dropdown menu. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 86 of 99
Setting Up Constant Light a. Group the sensor with the luminaires (drivers, ballasts etc) that the sensor will help control. b. Create a Constant Light routing entry In the Routing Entries tab right-click and select Insert>Constant Light> Constant Light, to insert a presence detection routing entry. c. Right-click the routing entry and select properties to open up the properties window. d. From the drop down menu select the relevant groups that the light sensor sits in and the desired control group (the group in which the luminaires are). In the instance this is the same group, click OK to save the grouping. e. Now set the target levels of the scenes. It is possible to have up to 12 different target levels which are triggered when recalling constant light scenes 1-12. The target level is a value between 1-200 and is fed back by the light sensor and is visible in the routing entry for constant light. To change the value click the value and type in the desired target level, for the below example a level of 120 has been set for scene 1. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 87 of 99
f. It is then necessary to setup the trigger for the relevant constant light scene, as setup above this is scene 1. It is possible to have the constant light trigger using the PIR itself or by the press of a button, for this example the PIR entry already created will be used. Right-click the PIR routing entry and select Properties. g. In the routing entry actions section of the properties window select the relevant scene number and select Recall Scene (Constant Light) from the drop down menu. Click OK to save. With triggering a constant light entry from a PIR is is only possible to trigger 1 target level scene, if triggered off a scene plate it is possible to utilise all 12 target levels if necessary. Note: The Designer light level is a value (0 to 200) sent by the light sensor depending on the light it detects (i.e. the light level at the ceiling). If you would like to maintain a particular lux level on a table top, for example, place a luxmeter on the table, and adjust the lighting to the desired level. Then, in the Routing Entries window in Designer, view the value (0 to 200) measured by the light sensor. This sensor value will be this value when the required lux level is on the table top. Note that any reflections of light into the light sensor or shadows on the table top will affect whether the sensor value and lux level are equivalent. Over to you! Now you ve learnt the basics, it s time to have a go. Self-test: a. What is the difference between presence detection and absence detection? b. Why is Exit Delay useful? Try this: For a small group of devices (e.g. 1x Illustris, 2x DALI LED drivers, 1x 320 sensor) : a. Set up presence detection. b. Set up absence detection c. Set up Constant Light. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 88 of 99
EXERCISES: CLASSROOM EXERCISE 1: Identify; Group; Program scenes 10 DALI drivers 1 button panel 1 group 1. Identify, name, and group the devices 2. Program these scenes: Scene Main group Scene 1 90% Scene 2 70% Scene 3 20% Scene 4 2% 3. Test it Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 89 of 99
EXERCISE 2: Two groups, one panel 2 groups: Main and Whiteboard 10 DALI drivers o 9 DALI drivers in the main group o 1 DALI driver in the whiteboard group 1 button panel 1. Identify, name, and group the devices 2. Program these scenes: Scene Main group Whiteboard group Scene 1 90% 100% Scene 2 90% 0% Scene 3 20% 100% Scene 4 2% 100% 3. Test it Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 90 of 99
EXERCISE 3: Two groups, two panels 2 groups: Main and Whiteboard 10 DALI drivers o 9 DALI drivers in the main group o 1 DALI driver in the whiteboard group 2 control panels 1. Identify, name, and group the devices 2. Program these scenes: Scene Main group Whiteboard group Scene 1 90% 100% Scene 2 90% 0% Scene 3 20% 100% Scene 4 2% 100% 3. Test it Note: each panel will control its own group, and not affect the other group. Helvar Designer 5 Foundation Course: Initial Programming. Edition 1 Page 91 of 99