Envision Project Training Guide - 1.0

Training Guide Book

Version 1.0.0

Author: Sam Hentunen. Contents subject to change without notice.

© 2010 Dynalite Intelligent Light Pty Ltd (ABN 97 095 929 829). All permissions reserved. Dynalite, Dimtek, DyNet and DLight and associated logos are the registered trademarks of Dynalite Intelligent Light Pty Ltd.

Not to be reproduced without permission.

2

Contents

3

Contents About Philips Dynalite ............................................................................................ 8

About this course .................................................................................................. 8

TOPIC 1: INSTALLATION ......................................................................................... 9

Topic Overview ................................................................................................. 9

Learning outcomes ............................................................................................. 9

Physical Installation ............................................................................................... 9

Connectivity and cabling ...................................................................................... 9

Wiring diagram ................................................................................................. 10

Recommended DyNet Colour Coding for CAT5 Cable ................................................... 10

RJ12 Socket Connections ..................................................................................... 11

Load Controllers ............................................................................................... 12

Control panels ................................................................................................. 13

Network power supply ........................................................................................ 13

Network bridges ............................................................................................... 14

How the system works ........................................................................................ 14

Default Presets ................................................................................................ 15

Commissioning process - flow chart ........................................................................ 15

TOPIC 2: CONNECTING TO THE NETWORK...................................................................... 17

Topic Overview ................................................................................................ 17

Learning outcomes ............................................................................................ 17

PC Node DTK622 and DMNG-USB-NA .......................................................................... 17

Connecting to the network .................................................................................. 18

Connection Properties ........................................................................................... 19

Connection Status ................................................................................................ 19

About Trunk Connections ....................................................................................... 20

About Spur Connections ......................................................................................... 21

Connecting to the system ....................................................................................... 22

TOPIC 3: ENVISIONPROJECT NAVIGATION ..................................................................... 25

Topic Overview ................................................................................................ 25


Start Job Selector ................................................................................................ 25

Screen Navigation ................................................................................................ 26

Main screen ..................................................................................................... 26

Main Editor ........................................................................................................ 27

Logical View tab ............................................................................................... 27

Network View tab ............................................................................................. 29

Main Editor Properties ........................................................................................... 32

Common Device Properties – Network View .............................................................. 32

Contents

4

Load Controller Properties – Network View .............................................................. 33

Sensor Properties – Network View .......................................................................... 33

Bridge Properties – Network View .......................................................................... 33

Physical Channel Properties – Logical view ............................................................... 34

Logical Properties ................................................................................................ 35

Common Properties – Logical view ......................................................................... 35

Area Properties – Logical view .............................................................................. 35

Preset Properties – Logical view ............................................................................ 35

Monitor Windows ................................................................................................. 36

Application Log ................................................................................................ 36

Command monitor............................................................................................. 37

Network Log .................................................................................................... 38

Docking ............................................................................................................. 39

Menus and Toolbars .............................................................................................. 40

General features ................................................................................................. 40

Loading, searching and creating devices ..................................................................... 42

Loading a device ............................................................................................... 42

Searching For Devices ........................................................................................ 44

Create a Device ................................................................................................ 46

Box Number Arbitration ......................................................................................... 48

Factory Setting Devices ......................................................................................... 49

TOPIC 4: WIZARDS ............................................................................................. 51

Topic Overview ................................................................................................ 51


New Job Wizard .................................................................................................. 51

Sensor Configuration Wizard ................................................................................ 60

Bridge Configuration Wizard ................................................................................ 63

TOPIC 5: THE COMMISSIONING ASSISTANT ..................................................................... 67

Topic Overview ................................................................................................ 67


About the Commissioning Assistant ........................................................................... 67

1. Create Job ...................................................................................................... 68

2. Define Job Details............................................................................................. 69

3. Connect to the Dynalite Network .......................................................................... 69

4. Define Logical Information .................................................................................. 70

5. Add Load Controller Devices ................................................................................ 71

6. Assign Physical Channels ..................................................................................... 72

7. Add User Interface Devices .................................................................................. 73

8. Add Sensor Devices ........................................................................................... 75

9. Create Tasks ................................................................................................... 76

Contents

5

10. Create Events ................................................................................................ 76

11. Define Logical Presets ...................................................................................... 77

12. Save Data to Devices ........................................................................................ 78

TOPIC 6: CONFIGURING LOAD CONTROLLERS .................................................................. 79

Topic Overview ................................................................................................ 79


The floor plan and equipment list ............................................................................. 79

Equipment list ................................................................................................. 80

Flashing ............................................................................................................ 80

Load Schedule ..................................................................................................... 83

Manual Load Controller Configuration ........................................................................ 84

Logical Load Controller Configuration ........................................................................ 87

TOPIC 7: CONFIGURING PANELS ............................................................................... 89

Topic Overview ................................................................................................ 89


Panel settings ..................................................................................................... 89

Device Properties Tab ........................................................................................ 89

Assigning a panel to an Area ................................................................................ 90

Changing Panel box numbers ................................................................................ 92

Enable Area zero messaging ................................................................................. 93

Panel Views ..................................................................................................... 94

Configuring Panels ............................................................................................... 95

Configuring Presets ........................................................................................... 95

Configuring one touch ........................................................................................ 99

TOPIC 8: CONFIGURING SENSORS ............................................................................. 104

Topic Overview ................................................................................................. 104

Learning outcomes ............................................................................................. 104

About the universal sensor ................................................................................... 104

Occupancy detection .......................................................................................... 105

Occupancy detection example ............................................................................ 105

Occupied Preset action ..................................................................................... 106

Grace Preset action ......................................................................................... 106

Vacant Preset action ........................................................................................ 106

Configuring occupancy detection ............................................................................ 107

Configuring light level sensing ............................................................................... 113

Open loop light level compensation example .......................................................... 113

Sensor Calibration ........................................................................................... 117

TOPIC 9: CONFIGURING OTHER DEVICES ...................................................................... 120

Topic Overview .............................................................................................. 120

Learning outcomes .......................................................................................... 120

Contents

6

DTC602 ........................................................................................................... 120

Setting the time ............................................................................................. 120

DNG100BT ........................................................................................................ 122

Wireless DyNet Network Connection ..................................................................... 122

DDMIDC8 ......................................................................................................... 123

Configuring dry contact inputs to send Preset messages ............................................. 123

Configuring analogue inputs to trigger tasks ........................................................... 124

TOPIC 10: SEQUENTIAL TASKING ............................................................................. 125

Topic overview ............................................................................................... 125


About tasking.................................................................................................... 125

TASK EDITOR ...................................................................................................... 126

Opening the EnvisionProject Task Editor ............................................................... 126

Saving your task ............................................................................................. 126

Running a task from a panel .................................................................................. 127

My First task ..................................................................................................... 128

Commenting code .............................................................................................. 129

Task constants .................................................................................................. 129

Goodnight task .................................................................................................. 130

Channel level messaging ...................................................................................... 131

Night mode for bathroom task ............................................................................... 132

Night mode task for panel ................................................................................. 132

Preset Offsets ................................................................................................ 133

New Vector task ................................................................................................ 134

Null ............................................................................................................ 134

Unconditional loop task ....................................................................................... 135

Control Tasks .................................................................................................... 135

Running a task from another device ........................................................................ 136

Panic task ........................................................................................................ 136

Panic Mode ................................................................................................... 137

Unpanic mode ................................................................................................ 137

Enabling buttons in Panic mode .......................................................................... 137

TOPIC 11: CONDITIONAL TASKING ............................................................................ 139

Topic overview ............................................................................................... 139


DyNet messages ................................................................................................. 139

Conditional task applications ................................................................................ 140

Memory Map .................................................................................................. 140

Terminology .................................................................................................. 140

Conditional welcome home task ............................................................................. 141

Contents

7

Configuring the time clock ................................................................................ 143

Extractor fan run on task ..................................................................................... 144

Extractor fan run on task version 2 ...................................................................... 145

Button LED control .......................................................................................... 146

Conditional Loops ........................................................................................... 148

DyNet Packet Sender .......................................................................................... 151

Find & Replace .................................................................................................. 152

Tools > Settings ................................................................................................. 153

User Settings ................................................................................................. 153

System Settings .............................................................................................. 154

Job Settings .................................................................................................. 155

Trouble shooting ................................................................................................ 155

Checking for offline devices ............................................................................... 155

Network Log .................................................................................................. 156

Application Log .............................................................................................. 156

Command Monitor ........................................................................................... 156

Appendix ......................................................................................................... 156

Glossary of terms ............................................................................................ 156

Hot keys .......................................................................................................... 158

DLight 2 to EnvisionProject Translation .................................................................... 159

About this course

8

About Philips Dynalite Philips Dynalite is a highly specialised company whose principal occupation is to provide ‘cutting edge’ solutions for lighting control. Our achievements have been recognised worldwide and Philips Dynalite is generally the system of choice for projects involving integration with third-party vendor’s equipment and for large-scale applications. Philips Dynalite’s philosophy is to provide the best solution possible for each and every project. This is the key to our success. Our considerable investment in Research & Development ensures that we remain at the forefront of our industry. Our position as a world leader in lighting management systems of the future will be sustained through our total commitment to innovation. We are represented around the world by distributors and dealers who are handpicked for their ability to provide the highest possible level of service. From a stock exchange in Shanghai, to a luxury resort in Dubai, from a smart home in Sao Paulo to limestone caves in New Zealand, Philips Dynalite’s innovative solutions deliver intelligent light. Ongoing research and development has enabled Philips Dynalite to create secure automated systems that control tens of thousands of individual light fittings in high-rise office buildings from any location anywhere in the world. Our networks are engineered to deliver instant notification of power or system failure, and report via a local Area network, the internet, or through an SMS gateway to a mobile phone. This provides the assurance necessary in applications where continuous operation is vital, such as road tunnels, computer servers or cold storage units. Philips Dynalite’s modular product design philosophy also improves system flexibility. Through this approach, unique project application requirements can be accommodated over greatly reduced lead times. As an industry leader Philips Dynalite is committed to creating superior lighting control and energy management systems, setting new benchmarks in performance and efficiency. In receiving the International Association of Lighting Designers award for Most Innovative Product, the Philips Dynalite control system has been independently recognised as ‘A user friendly and sensible modular approach, which takes it from the sophisticated domestic setting to large architectural spaces’.

About this course This course is designed to provide each trainee with a broad understanding of the Philips Dynalite system and how it can be used effectively. On completion of this course the trainee will be able to quickly and easily configure a Philips Dynalite system to provide the user with all common functionality. This Training guide is designed to be used in conjunction with the EnvisionProject Training Activity Book

Topic 1: Installation

9

TOPIC 1: INSTALLATION

Topic Overview Dynalite produce a wide range of products that allows each installation to be tailored to the clients exact requirements. This topic describes the types and characteristics of the main product families.

Learning outcomes By the end of this topic you will be able to:

• Understand the cabling requirements for a Dynalite lighting control system.

• Describe the role of Dynalite products and their installation requirements.

Physical Installation

Connectivity and cabling The system communicates over screened, stranded RS485 data cable (such as Cat5) and requires a minimum of three twisted pairs. The cable should be segregated from mains cables by a minimum of 300mm and all devices on the cable should be connected together in a daisy chain configuration.

Fig 1 – Daisy Chain Configuration It is important to note that any data cable that is connected to an energised device is live. Data cable should not be cut or terminated while live. A 5-way pressure pad terminal strip is provided on devices for each data cable termination. Some devices also have an RJ12 connector for temporary connection of portable programming devices.


10

Wiring diagram

Fig 2 – Wiring diagram One pair is paralleled for GND, one pair paralleled for +12V and one pair used for DATA+ and DATA -.

Recommended DyNet Colour Coding for CAT5 Cable

Pair Colour Signal

1 Blue Mate Blue

Data- Data+

2 Orange Mate Orange

}

Paralleled for +12Volts.

3 Green Mate Green

}

Paralleled for Ground.

4

Spare pair if required to repair damaged cable or can be used as a drain for static if unshielded cable used in the installation.


11

RJ12 Socket Connections

Fig 3 – RJ12 Socket

A single pair of cables in CAT5 data cable has a maximum current limit of 2A. This equates to approximately 100 devices. In addition, the maximum cable run for a single piece of Cat5 data cable on a Dynalite network is 1000m. A bridge should be used to connect separate cable runs together if more than 100 devices exist on a network or if a single cable run exceeds its 1km limit.

Fig 4 – Network bridge


12

Load Controllers The controllers basically come in two types, either wall mounted or din rail mounted.

Wall Mounted Controllers These controllers are supplied with mounting feet that allow them to be installed in any suitable location. They are mounted vertically with a clearance of no less than 200mm between each device to allow for sufficient airflow for cooling.

Fig 5- DLE1205 Wall mounted dimmer

Din Rail Mounted Controllers These controllers are installed inside a standard electrical enclosure. The power and data cable should be segregated as per standard practice. The Dynalite product facilitates segregation by having power fed in and out from the top of each device. Data cabling enters the device at the bottom and is segregated in the ELV section. Data cabling is terminated in this segregated section. All data cable that runs within the electrical enclosure must be mains rated for safety. Dynalite data cable is safety rated to 600v.

Fig 6 - DDMC802 Din rail mounted controller


13

Control panels Dynalite produce control panels for both UK and Australian/US style wall boxes. To confirm which panels are suitable for EU wall boxes, check with your Dynalite supplier. Dynalite manufactures their own C-clip for the European style panels to allow this style of panel to be easily installed into an Australian project.

Fig 7 – DR2P Panel

Network power supply The load controllers supply 12vDC via the Cat5 cable to power up control panels as well as other ancillaries. Each device requires a minimum of 10v DC to operate correctly. If the ratio of load controllers to panels and ancillaries is too great an additional power supply is required to supplement the network. This supply is mains powered and din rail mounted. and must be installed in an electrical enclosure. It should be made clear that the maximum current capacity of Cat5 cable is 2A. If this capacity limit is exceeded a Dynalite bridge is required to separate the network into two or more physical parts.

Fig 8 - Din rail mounted network power supply


14

Network bridges A network bridge is commonly used to join together two pieces of Cat5 cable on a communication level while maintaining physical separation. This allows the cable load limit of 100 devices and /or 2A to be overcome, each piece of Cat5 being independent while at the same time being part of the one network. While network bridges are din rail mounted, they do not necessarily need to be installed into electrical enclosures, as they are solely an ELV device being powered from the network. Key Point - The bridge is powered from the 12v and Gnd connection on port 1.

Fig 9 - DDNI485 Network bridge

How the system works The Dynalite network communicates using its own proprietary protocol called DyNet. This is an open protocol that employs an RS485 transport layer to pass messages across the network. The system implements a ‘fully distributed intelligence’ philosophy, which means that every device on the system is independently intelligent and is fitted with its own logic controller. This allows a large amount of the operational processing to be done locally within each device and enables the Dynalite system to be controlled using relatively short message transmissions. While the system is limitless in terms of its scalability (up to 17 million products theoretically on a single network) things are kept simple by using logical group addresses (known as Areas) rather that communicating to individual circuits. This Area grouping is done on a per circuit basis so each individual circuit is programmed with an Area address and an individual Channel address. The areas are then mainly controlled using Preset messages. These are pre-programmed levels that give the required effect to the Area being controlled. When an Area Preset message such as "Area 6 go to Preset scene 3" is transmitted onto the network, every device on the network receives the message at the same instant and checks to see if it has circuits in that Area. If the controller finds it has a circuit in that specified Area it uses an internal look up table to discover the output level for that circuit for Preset 3. It then changes the output level of that circuit using the fade time in the received message. By having multiple layers of Area groupings the system only requires minimal information to control anything from a single circuit to a complete building.


15

Default Presets Dynalite ships all of its products with default Presets configured, these can be changed as required.

Dynalite Preset

Default Values

Preset Light Level P1 100% P2 70% P3 40% P4 0% P5 80% P6 60% P7 50% P8 20%

Commissioning process - flow chart The flowchart below describes the commissioning process using EnvisionProject.

1. Connect to the network

2. Search for devices on the network

(Don’t load device data)

3. Flash load Controllers and Channels

4. Configure Load Controllers (Area no:, Channel name & no:)

5. Name Areas (Logical view)

7. Configure Panels

8. Configure Sensors


16

Fig 10 – Commissioning process

6. Edit Area Presets

9. Configure other devices (Time clocks Touch screens dry

contact inputs)

10. Walk through

Topic 2: Connecting to the network

17

TOPIC 2: CONNECTING TO THE NETWORK

Topic Overview This topic covers physical connections to a Philips Dynalite network for the purposes of commissioning or maintenance. In addition we will discuss configuring EnvisionProject for trunk and spur connections as well as different connection methods such as serial and TCP.


• Describe the method of connection to a Dynalite network.

• Configure EnvisionProject to connect to a Dynalite network.

PC Node DTK622 and DMNG-USB-NA A Dynalite DTK622 PC node is the standard interface for connecting the programming PC to the network. It is available in both USB and RS232 versions.

Fig 11 – Serial and USB versions available


18

Connecting to the network It can be connected to the network in a number of ways.

1. By plugging in the supplied RJ11 terminated cable to the RJ12 socket on the base of a load controller.

Fig 12- Base of controller

2. By plugging into a dedicated network socket.

Fig 13 – Front of panel


19

3. By plugging into the back of a control panel using the supplied Dynalite dingus.

Fig 14- Back of panel

Connection Properties When a job is opened EnvisionProject will automatically connect to the last active connection of the job. This may the trunk or a spur connection. To prevent this uncheck the “Automatically connect when a job is opened” checkbox on the connection settings. The ‘Connect’ and ‘Disconnect’ buttons on the tools menu and toolbar will also connect to the last active connection of the job. The preferred protocol can be set to Dynet1 or Dynet2 for a connection. By default it is set to Automatic which means that Dynet1 will be the preferred protocol for spur connections and trunk connections of jobs that do not contain any devices behind them.

Connection Status The current connection status is available on the right side of the status bar. This will indicate the connection type (Serial, TCP or Ethernet), the location (Trunk or Spur) and the current preferred protocol. The connection status is also available on the network and logical views. Next to the top level job

element in the Network and Logical view will be a or icon. Bridge devices in the Network view will also show a connection icon. When the job is connected at the trunk then all bridges under the trunk will show the “Connected Above” icon to indicate that they are connected from the trunk side. When the job is connected at a spur the spur bridge will show a “Connected” icon and the top level job element will show a “Connected Below” icon to indicate that the job is connected at a lower point. In this case all other spur bridges will be show the “Disconnected” icon.


20

Connection Icons:

- Connected.

- Disconnected.

- Connected Above.

- Connected Below.

About Trunk Connections The RS485 connection settings used can be those defined for the machine or they can be defined in the current job. The machine or job defined RS485 connection can be set to a serial, TCP or no connection. When configuring a connection, a list of the available serial COM ports and TCP connections will be displayed. By default the connection is set to automatically select the most suitable serial connection. To select a specific serial COM port uncheck this option. If using a DNG100BT to provide a TCP connection to the RS485 network then select the IP address and port from the list that match the DNG100BT or if not found then select the custom entry and enter the IP address and port. For jobs where DNG100BT bridges are used to provide an Ethernet trunk then a list of all Ethernet connections will be available in the Ethernet trunk connection settings section. The list will contain an entry for each DNG100BT contained in the job and its IP address, port, device name and current status will be displayed. From here all DNG100BT connections can be enabled and configured. When connecting the trunk all enabled DNG100BT Ethernet connections will be automatically connected.

The trunk can be connected or disconnected using clicking or on the

tab or from the right click context menu of the top level job element in the Network view. This part of the properties window controls trunk connections for a Dynalite project, the options available are:

1. .

2. Preferred protocol – Automatic, DyNet and DyNet2, (see section on Connection Properties).

3. Automatically connect when a job is opened.

Fig 15 – Trunk Connection Settings


21

About Spur Connections To configure a spur connection, select the bridge that connects the spur in the network view and select the Connection Settings tab. The RS485 spur connections are configured exactly the same way as the trunk RS485 connection. Currently EnvisionProject allows only a single trunk or spur connection to be connected at a time. When making a new connection, any other currently active connection will be first automatically disconnected.

The spur can be connected or disconnected using or on the bridges

tab or from the right click context menu of the bridge device in the network view. Dynet2 will be the preferred protocol for trunk connections of jobs that contain at least one device behind a bridge. The Dynet2 protocol will always be used for certain physical messages when communicating with devices that support the DyNet2 protocol. This part of the properties window controls spur connections for a Dynalite project, the options available are:

1. and .

2. Preferred protocol – Automatic, DyNet and DyNet2 (see section on Connection Properties).

3. Automatically connect when a job is opened.

Fig 16 – Spur Connection Settings


22

Connecting to the system EnvisionProject has been designed to automatically detect available Comm ports for connection. Manual configuration of Comm ports is still possible should the automatic connection service fail. To access connection settings:

1. Click on the project Name in the Network View.

Fig 17 – Network View

2. Click to open the properties shown in Fig 18 – Connection settings tab.

3. Click .

Fig 18 – Connection Settings Tab


23

4. When connecting to a DyNet network via RS485 there are 2 main connection settings to choose from:

• Use machine connection settings

• Use job specific connection settings.

Regardless of the option you choose the following settings are edited in the same way.

5. Click on for machine or job specific settings.

6. Connection Type – Allows to select the type of connection use to connect to the DyNet network, the options are listed below: • None - allows for configuration of gateways in a Trunk & Spur network. • Serial – Used for configuring serial connections to the DyNet network, used from PC

nodes USB and serial. • TCP – Used for configuring TCP Ethernet connections to the DyNet network.

Fig 19 – Connection Type

7. Connection Details - This section lists available connections, EnvisionProject will select the best connection for you. Should you wish to select the connection type yourself, uncheck the Automatically select best available connection check box. Baud Rate – Change the baud rate for network communication if required. 9600 is the default rate for communicating on a DyNet network.


24

Fig 20 – Connection Details

8. TX Delay & RX Delay – Defines transmit and receive delay times, they are defaulted to TX=20 and RX=20.

Fig 21 – TX delay & RX delay

9. The button is used to refresh the list of available connections.

10. Click to complete any changes you have made and exit the dialog screen.

Topic 3: EnvisionProject navigation

25

TOPIC 3: ENVISIONPROJECT NAVIGATION

Topic Overview In this topic we introduce you to EnvisionProject, Philips Dynalites main commissioning software. We discuss basic navigation of the main sections of EnvisionProject, Main Editor, Main Editor Properties and the Monitor windows, Finally, we will take a look at loading, searching and creating devices in a Philips Dynalite network.


• Navigate the main windows of EnvisionProject.

• Load devices in a Philips Dynalite network.

• Search for devices in a Philips Dynalite network.

• Create devices in a Philips Dynalite network.

Start Job Selector When EnvsionProject is launched the Start Job Selector will appear. This dialog box allows you to select from a number of commissioning options: • Start new Job Using Wizard – Use EnvisionProject s in-built wizard to walk you through the

commissioning process step by step. • Open Commissioning Assistant – The assistant is a commissioning tool that helps commission

more complex Dynalite networks. • Create new Empty Job – Start the commissioning process from scratch with an empty job. • Open Existing Job – Open a previous job.


26

Fig 22 – Start Job Selector

Note – To stop this dialog from displaying at start up, un-tick the Show at Startup check box.

Screen Navigation

Main screen The EnvisionProjects Main screen is split into 3 sections, Main editor, Main editor properties and the monitor windows as shown in Fig 23 - EnvisionProject Main Screen. The basic process flow in EnvisionProjects Main screen is: Main Editor – Select device or Area to be configured. Main Editor Properties – Edit settings for selected device or Area.

Monitor Windows – Monitor deployment of settings to device on the network.


27

Fig 23 – EnvisionProject Main Screen

Main Editor The main editor has two tabs, with each tab containing an individual editor. These are called the Logical and Network views.

Logical View tab The Logical view represents the logical elements of a Dynalite system. The logical tree displays the logical areas and Channels defined for the current job as well as the physical Channels assigned to each logical Channel. Logical areas may also be grouped using Area folders.


28

Fig 24 – Logical view

Menu bar Icons

Create new folder – Creates a new folder in the Logical view, used for sorting devices in large projects.

Create new Area – Creates a new Area in the Logical View tab.

Create new Channel - Creates a new Channel in the Logical View tab.

Unassign Physical Channel – Delete an assigned physical Channel.

Flash Area or Channel – Selected Areas or Channels can be flashed (See flashing).


29

Areas, Channels and Folders Logical Areas, Channels and folders can be:

• Inserted - using either the tool-strip buttons at the top of the Logical view, the context menu or from the main window Insert menu.

• Cut, copied or pasted – using either the context menu or the main window Edit menu or toolbar.

• Deleted or renamed – using either the context menu or the main window Edit menu or

toolbar.

• Moved or copied – by dragging around the logical tree.

• Synchronise Presets – for Areas only (see Preset Editor Section for details).

• Flashed – Areas and Channels can be flashed (see ‘Flashing’ section below).

Network View tab The Network view contains all the Philips Dynalite devices defined for the current job. The Network tree view also provides the network topology of the Philips Dynalite system. If the Philips Dynalite system is a single level system then all devices will be shown under the top level job item. For multi level systems all devices on the trunk will be directly under the job but devices on a spur will be shown behind the bridge that connects the spur to the trunk.

Fig 25 – Main Editor Network View


30

View

• Devices are grouped in the network tree by their product category. The available product categories are - Load Controllers, User Interface, Sensors, Bridges and Other Devices.

• The network tree provides the following columns for devices - Product Category, Product Type, Product Name, Device Code, Box Number, Serial Number and Device Location. Column width and order can be customised and columns can be shown or hidden by right clicking on the column headers.

• The current status of each device is represented by status icons next to the device icon.

Device status icons indicate if a device has been modified, if its offline and any device errors. Device errors can be the result of having an invalid EEPROM, box number conflicts, circuit breaker trips and logical and physical translation errors. A description of the devices status is shown in a tool-tip and in the status bar.

• Selecting devices in the Network view allows for the devices to be configured using the

device editors (see Device Editors Section below).

Menu bar Icons

Create New Device – Creates new devices in the Network view tab.

- Load Devices from Network – Enable you to search, sign on and load devices and information.

Imported from File – Devices can be imported into the job from device hex files. Multiple hex file can be selected to import multiple devices.

Exported to File – Devices can be exported to a hex file.

Factory Set – Device memory stored in the job will be reset to a factory default image. To factory set the actual device a save to device is subsequently required.

Task Text Editing – An evt file containing the devices tasks and events can be edited. The evt file associated with each device is stored as part of the EnvisionProject job. The compiled task data is currently not saved to the device memory.


31

Load from Device – Loads the device memory form the device into EnvisionProject. The user can select to load only the relevant data or the entire device memory (Relevant data refers to data changed since the last load and Entire device memory loads the whole data map).

Save to Device – Saves the device memory from EnvisionProject to the device. The user can select to save only data that has been modified, all relevant data or the entire device memory (Relevant data refers to data changed since the save and Entire device memory saves the whole data map).

Send Reset – Sends a device reset message to the selected device.

Send Device Sign On – Sends a sign on message to the selected device.

Change Box Number – Changes a devices box number.

Change Area – Changes a devices assigned Area.

Refresh Device Status – Requests information from the device by sending status information requests and other messages. The device information includes the device serial number, hardware and firmware versions and other information for different devices. This information is displayed in the main device properties grid.

Flash – Devices can be flashed (see Flashing in topic X). Note: All above operations can be performed on multiple devices of the same category simultaneously.


32

Main Editor Properties The Main Editor Properties window displays the setting available for the device or Area selected in the Main Editor. For example, if an Area is selected in the Logical view the Main editor will contain the editors for an Area. If a device is then selected in the Network view the Main editor will contain the editors required to configure that device. Device properties differ depending on the type of device, as do Area and Channel details.

Fig 26 – Device Properties tab

Common Device Properties – Network View

1. Device Properties – The device properties editor allows for the simple properties available for each device to be viewed and modified. The number and type of properties available depends upon the type of device selected. Device properties common to all devices includes device name, box number, location, description and start-up settings. Device creation and last modified times are also available to view as properties.

2. Device Details – Provides the product details of the currently selected device. This includes

a description, details and an image of the product.

3. Create Device – The Create Device tab is available as a tab in the device editor when either the top level job item, a category item or a bridge is selected in the network tree (see the Create Device Section below).

4. Port Editor – The port editor allows the device port settings to be edited. The number and

type of ports available differ between devices. The port to edit is selected from the drop down list in the tool-strip at the top of the editor. Unless the advanced properties button is selected only the relevant properties and valid property values for the selected port type will be show.

5. Task Editor – The task editor is available for all devices that support tasking. This task

editor currently only provides a link to edit the task text in an evt file. A graphical task editor is planned to provide users with a simple and easy way to create tasks.


33

Load Controller Properties – Network View

1. Channel Editor – The Channel editor allows the properties of load controller Channels to be viewed and modified. This includes the Channel name, Channel assignment, output type, join, base-link Area and the current value of dynamic Channel properties.

2. Preset Editor – The load controller Preset editor is identical to the logical Preset editor described in the Preset Editor Section above. The only difference is that the “Synchronise Presets” button will synchronise the selected device(s) Preset table with the logical Preset tables defined for the areas to which the devices physical Channels are currently assigned.

Sensor Properties – Network View

1. Calibration – The calibration editor provides a way to calibrate the sensor light control. One point, two point and manual calibration modes are available. The graph can display the raw and lux levels. The properties of the light level graph such as the range, duration and sampling rate can be configured from the settings windows. Calibration is only available when a single sensor is selected.

2. Light Control Editor– The light control editor allows the open or closed loop settings to be

edited. The editor will either show the closed loop Presets levels or the open loop action bands depending on the light control mode selected. When multiple sensors are selected the properties, Preset levels or bands in common can be edited. The graph displays the current lux level of one or more of the selected sensors.

3. Motion Detector Editor – The motion detector editor allows the motion detector properties

and motion Preset actions to be edited. When multiple sensors are selected the properties and Preset actions in common can be edited. The graph displays the current motion level of one or more of the selected sensors. The properties of the motion level graph such as the range, duration and sampling rate can be configured from the settings windows.

4. IR Button Editor – The IR (Infra-Red) button editor allows the function to be performed for

each IR button to be edited. A custom function type allows the press, release, extended press and extended release action lists to be edited directly. To show these actions lists the advanced properties button must be selected. When multiple sensors are selected the buttons with common functions can be edited.

Bridge Properties – Network View

1. Filter Editor – The filter editor allows the list of bridge blocking filters to be viewed and modified. The editor contains a list of all blocking filters and a property grid that displayed the properties of the currently selected filter. Multiple filters can be selected to copy or delete however only a single filter can be edited at a time.

2. Translation Editor – The translation editor allows the list of bridge translation filters to be

viewed and modified. The editor contains a list of all translations filters and a property grid that displayed the properties of the currently selected filter. Multiple filters can be selected to copy or delete however only a single filter can be edited at a time.

3. Connection Settings - The connection settings tab is available to allow the connection

details when connecting to the spur side of a bridge to be defined (see the Connection Section below).


34

Physical Channel Properties – Logical view Physical Channels are automatically added to the Logical view whenever a new load controller is added to the EnvisionProject job. Physical Channels appear under the logical Channel to which they are currently assigned. The Logical view also provides a list of ‘unassigned Channels’ as a tab in the logical editor (see Logical Editor Section below). This is a list of all physical Channels grouped per devices that have not yet been assigned to a logical Channel. Physical Channels can be:

• Assigned – to a logical Channel by dragging them from the list of ‘unassigned Channels’.

• Un-assigned – by selecting “Un-assign Channel” from tool-strip or context menu or by dragging back to the list of ‘unassigned Channels’.

• Re-assigned – by dragging them from one logical Channel to another logical Channel.

• Cut – the cut operation will temporarily un-assign the physical Channel until it is subsequently pasted.

• Renamed – using either the context menu or the main window edit menu or toolbar.

• Edited – Channel properties can be edited by selecting “Edit Channel” from the context

menu or double clicking a physical Channel. This will switch to the Network view and open the Channel editor for the device that the physical Channel belongs to.

• Flashed – (see Flashing section below).

Note: All operations in the logical tree can be performed on multiple items of the same type by selecting multiple items in the tree.

Fig 27 – Logical view


35

Logical Properties Logical editors will be shown in the main window when the Logical view is the current active view. The logical editors shown depend upon the logical item(s) currently selected in the logical tree.

Common Properties – Logical view The following logical editors are available for all selected logical items:

1. Property Editor – The Property Editor allows the properties of logical Areas, Channels and folders to be modified. The properties of logical Channels include Channel type and Channel load properties, these are used to help determine appropriate load controllers when pre-commissioning a job.

2. Unassigned Channels – Contains a list of all physical Channels, grouped per device, that are

currently unassigned (Channels are considered unassigned when they are assigned to Area 1).

Area Properties – Logical view When logical Area(s) are selected the following two additional editors are also available:

1. Device References – Contains a list of all devices that reference the selected Area(s). A context menu provides a link to edit and rename devices.

2. Preset Editor –The Preset editor provides access to view and modify the logical Presets

defined for an Area (see Preset Editor section below).

Preset Properties – Logical view The Preset editor provides two views for editing Presets – a list view and a table view. The list view provides a list of all Presets and a table of Channels for the currently selected Preset. Channel level sliders are provided for adjusting Channel levels. The list view is the best way to manage (add, remove, duplicate and rename) Presets and allows for operations to be performed multiple selected Presets. The table view is a table of Presets and their Channel levels and provides a way to quickly modify Preset Channels levels. Switching between views is done via the view tool-strip button. Presets can be:

• Inserted – using either the context menu or the tool-strip “New” button. Presets can be inserted singularly or in a range. Additionally toggle and panic Presets can be defined.

• Deleted – using either the context menu or tool-strip button. As present numbers must be continuous Presets can only be deleted from the end of the list of Presets.

• Copied, pasted and duplicated – using the context menu, tool-strip buttons or the main

window edit menu. When pasting Presets the user can select to either replace the levels of an existing Preset or create a new Preset. The table view allows multiple Channel level values to be copied and pasted as text.

• Synchronised – using the button on the tool-strip. This will synchronise the device Preset

tables with the logical Area Preset table for any physical Channels currently assigned to logical Channels in the selected Area.


36

Features of the Preset properties include:

• Exclude Channels – Channels can be excluded using the exclude check box or by entering a level of 255 or pressing ‘x’.

• Level precent – the ‘Percent’ option allows Channel levels to be viewed as a percent or an

actual value.

• Lock levels – the ‘Lock Levels’ option allows all the Channel levels for the selected Preset(s) to be modified together.

• Sorting – the Preset list can be sorted by Preset number or name by clicking on the column

header. The Channel list can be sorted by Channel number or name by clicking on the column header.

• Multi Area select – Presets can be changed for multiple areas simultaneously when multiple

areas are selected in the Logical view.

• Send Levels – The user can choose for Channel level messages to be sent when a Preset is selected in the Preset list. On the logical Preset editor the user can alternatively choose for recall Preset messages to be sent when a Preset is selected. The mute option will prevent any messages being sent.

• Current Levels – The Preset list contains a ‘Current Levels’ item that displays the current

Channel levels for the Area or device. Whenever the ‘Current Levels’ item is selected the Preset editor will request the current Channel levels. The user can also change the current Channel levels when the mute option is not selected.

• Current Preset – the current Preset for an Area will be have the text “(Current)” next to

the Preset in the Preset list. If the user setting ‘Request current Preset on Area selection’ is enabled the current Preset will be request when an Area is selected in the Logical view.

• Flashing – Logical and physical Channels can be flashed using the flash checkbox on the

Channel table. The flash checkbox will be disabled when the mute option is selected (see Flashing section below).

Monitor Windows The monitor windows are split into three categories, the Application Log, Command Monitor and the Network Log.

Application Log The application log records the type, date, time and message. It is meant to record all actions by the EnvisionProject, this may include network traffic but also records information related to EnvisionProject such as network connection.

Fig 28 – Application log window


37

Features

• Log messages can be filtered by the following message types – Errors, Warnings, Information and Detailed Information. Debug messages filters can also be enabled.

• The Application Log Viewer can be paused and resumed. Log messages received while paused will be added when the Application Log Viewer is resumed.

• Existing log files can be opened. These will be opened in a new Application Log Viewer

window. Multiple log files can be selected to combine multiple logs in a single Application Log Viewer window.

• Links provide access to open the “Complete Current Log” as well as the next and previous

log files. A new application log file is by default created every day.

• The log entries currently shown in the Application Log Viewer can be saved to file.

• Column width and order can be customised and columns can be shown or hidden by right clicking on the column headers.

• Log messages can be sorted ascending or descending by clicking on the ID column or the

order icon on the toolbar.

• Selected log messages can be copied to the clipboard.

• Log messages can be searched for specific text.

Command monitor The command monitor shows the status of messages on the network, and a more detailed description of the message than can be found in the other windows.

Fig 29 – Command monitor window

Features

• The name, status, progress and details of all network commands can be viewed.

• One or more selected current network commands can be cancelled.

• All current network commands can be cancelled.

• The user is warned when cancelling a write to device network commands as cancelling these network commands can leave a device in an inconsistent state.

• The command monitor will display completed commands. The number of completed

commands can be configured in user settings.


38

• Completed commands can be removed using the “Clear completed commands” tool strip button.

• The order of commands can set to ascending or descending order using the button on the

tool strip or clicking the ID column.

• The command monitor can filter out simple and completed network commands


• Selected network command can be copied to the clipboard.

Network Log The network log shows the direction that messages travel, it also shows a description of the message and the hexadecimal data being sent. This is similar in functionality as the monitor window in DLight2.

Fig 30 – Network log window

Features

• The Network Log Viewer can be paused and resumed. Network packets received while paused will be added when the Network Log Viewer is resumed.

• Existing network logs can be opened. The user can select to open the logs in the existing or a new Network Log Viewer window. Additionally the time zone offset applied to the logs can be overridden. Multiple network logs can be selected to combine multiple logs in a single Network Log Viewer window. When multiple files are opened the Network packets are sorted by GM Time.

• Links provide access to open the “Complete Current Log” as well as the next and previous log files. A new network log is by default created every hour.

• The network packets currently shown in the Network Log Viewer can be saved to file.


• Selected network packets can be copied to the clipboard. These are copied in a tab

separated format to allow them to be easily pasted into a spreadsheet.

• The Network Log Viewer can be searched for the next or all network packets containing specific text or bytes.

• Network packets can be bookmarked to allow easy navigation between packets. Network packet bookmarks are saved with network logs so that particular network packets can be easily identified.


39

• Network packets can be sorted ascending or descending by clicking on the Num column or

the order icon on the toolbar.

• Network packet filtering has yet to be implemented.

Docking The dock-able windows can be docked on any edge of the main window. Each window can be docked together in a group or docked separately. To move or re-dock a window, drag the window by the title bar and drop the window on one the blue square docking icons that appear when you start dragging the window. To separate a window from its group, drag the tab containing its name instead of the window title bar. The dock-able windows can also be free floating windows and positioned anywhere on your screen. Double clicking a dock-able window title bar will cause the window to toggle between its free floating position and it docked position. Finally, dock-able windows can be set to auto-hide to the side of the screen on which they are docked. Auto-hide mode is toggled on and off by clicking the “pin” on the window title-bar. If any of these windows are hidden by clicking the close button on the title bar they can be made visible again from the “View” menu or toolbar.

Fig 31 – View when docking a window


40

Menus and Toolbars The main window contains the following main menu items:

• File – Contains menu items to open, close, save and create EnvisionProject jobs. Future releases of EnvisionProject will contain items to import and export, backup and restore jobs.

• Edit – Contains menu items to undo, redo, cut, copy, paste, delete, rename and find. Undo

and redo will undo any action performed by the user that modified the currently open job. The other edit items are context sensitive and will affect the currently active window or editor.

• View – Contains menu items to toggle showing and hiding the various dock-able windows

and toolbars. The “Reset Window Layout” menu item will return all windows to their original position and size.

• Insert – Contains menu items to insert new items into the network or Logical view. Some of

these items will only be available when the certain items are selected. For example you can only insert a new logical Channel when an Area is selected in the Logical view. These insert items are also available in context menus and on the tool-strip at the top of each of view.

• Device - Contains menu items to perform actions on a currently selected device(s). These

items are only enabled when a device is selected. Again these items are available in the context menu and tool-strip of the Network view.

• Tools – Contains Connect, Disconnect, Stop all Flashing and Settings menu items. Other

tools and utilities will be added in the future.

• Wizards – Contains EnvisionProject wizards and the wizard manager.

• Language – Contains the available languages in EnvisionProject and allows the user to switch between languages. Currently only English is available.

• Help – Currently only contains the “About” menu item. EnvisionProject help will also be

available in this menu in future releases.

• Virtual Panel Toolbar – Contains a configurable number of buttons that allow users to send recall Preset messages and fade Area messages. A configuration button allows the current Area, fade rate and join to be configured.

Fig 32 – Virtual panel

General features The following is a list of features common across EnvisionProject:

• Undo / Redo – Currently all actions performed can be undone and redone. There is no limit to the number of undo actions. Undo and Redo are available from the edit menu and toolbar.

• Cut / Copy / Paste – Almost all items in EnvisionProject can be cut, copied and pasted. This

also applies to copying between different instances of EnvisionProject.


41

• Move – Many items can be moved by being dragged. As standard with drag operations, holding down the Shift or Control keys will copy the item(s) and right button dragging will provide an option to move, copy or cancel.

• Multi-select – All compatible items can be multi selected. This allows the properties for multiple items to be changed in one action. If the properties of multiple selected items have different values then the background colour of the property will be set to light yellow. Some functionality may not be available when multiple items are selected as not all functionality is valid for multiple items.

• Shortcut keys – Standard windows short cut keys are available and shortcut keys are

provided for most of the menu items. See the menu item for their short cut key. Some common DLight2 shortcut keys have also been implemented such as F8 to toggle between views and Home, End, Page Up and Down for Channel level changes.

• Settings - The job, user and system settings are available in the settings dialog accessible

from the Tools menu.

• Customisation - The location and positions of windows as well as many customisations of individual controls are saved in the EnvisionProject user settings and will be maintained for the next time EnvisionProject starts.

• Job Properties - The top level item in every view represents the current open job. The

properties of the job can be modified by selecting this job item in any view.

• Status Bar – The status bar at the bottom of the main window shows the status of the currently selected item(s) in the Logical or Network view. In the Logical view it will show the total number of areas. In the Network view it will show the total number of devices in the job or category. If a device is selected it will show the details and status of the device. On the right side of the status bar is shown the current connection status.


42

Loading, searching and creating devices Devices can be loaded into a project or searched for on a network, which way you add devices is determined mainly by convenience.

Loading a device

1. Click in the Network view and the Load Devices from Network dialog appears.

2. Select the tab.

Fig 33 – Discovered Devices tab

3. Sign on the device and it will appear in the Dialog list, shown in Fig 34 – Discovered Device shown.


43

Fig 34 – Discovered Device shown

4. Decide if you wish to load data from the devices you are adding. If you do, click the Load device data when adding devices check box.

5. Click .

6. Click to close the dialog.


44

Searching For Devices EnvisionProject has a network device discovery feature to find devices on the network. To find devices follow the steps below:

1. Click in the Network view and the Load Devices from Network dialog appears.

2. Select .

Fig 35 – Search Devices tab

3. Select your search parameters: • Search by product group – searches whole product type i.e. panels. • Search by product – Searches for devices by individual product types.


45

Fig 36 – Search Devices tab

4. If searching by product group, use the dropdown list to select the types of devices you are looking for?

Fig 37 – Search parameters

5. Once all the device types you need have been selected click on the Start Search button.

6. Once the search has completed for each device (each devices completion status is shown) the devices found will be listed as shown in Fig 38 - Found devices shown in Search Devices tab.

7. Now you need to decide weather or not you wish to load the device data. If you starting a new project you should leave the check box un-ticked as there is no need to load data for factory set devices as EnvisionProject is aware of device factory settings.

8. Now click to load the devices marked with a tick in its check box. See Fig 38 – Found devices shown in Search Devices tab.


46

Fig 38 – Found devices shown in Search Devices tab

9. Click to close the search dialog and return to the EnvisionProject Main view.

Create a Device The Create Device tab allows new devices to be added to the EnvisionProject job. The Create Devices tab contains the following three sections:

1. A list of all available Dynalite products. These products are divided into their Product Categories and further divided into the Product Types (or sub-categories).

2. Device properties. This property editor shows the properties of the currently selected

product in the list of products. This also allows for custom device properties such as device name, location and box number to be specified when creating a device.

3. Product details. This provides a description, details and an image for the currently

selected product. Product details can shown or hidden by clicking the “Show Details” button.


47

Creating a device: To create a new device in a project, complete the steps below:

1. In the Network view, click .

2. Select the type of device you wish to add by selecting its tab.

Fig 39 – Create Device

3. Select the type of device you wish to add by selecting its tab.

4. If you have it, enter the devices box number in the Device Properties section, shown in Fig 40 – Device properties.

Fig 40 – Device Properties


48

Features

• A device can be created by either pressing the “Create Device” button, by double clicking a product or dragging the product directly onto the network tree. The device will be created under the currently selected item on the network tree or location it is dragged onto.

• Products in the product list can be viewed as large icons, small icons or in a list.

• Favourite products can be added to either the current job or to the user settings. This is

done by right clicking a product and selecting either “Add to User Favourites” or “Add to Job Favourites”. The product will then be available in the Favourites tab. Products can be removed as a favourite by right clicking a favourite product and selecting “Remove”.

• If the box number property is left blank then an appropriate available box number will be

automatically assigned to the newly created device.

Box Number Arbitration If the search feature detects that 2 devices of the same device type have the same box number you will be prompted to change one of the devices box numbers before you will be able to add them to your project, shown in Fig 41 - Duplicate box numbers are highlighted in orange.

Fig 41 – Duplicate box numbers are highlighted in orange EnvisionProject will suggest a new box number for one of the devices, this will be displayed in the New Box Number column, you are free to override this number with one of your choice if you prefer.

Once the new box number has been decided, click to confirm the change.


49

The Apply New Box Numbers dialog will appear, click once the status column has changed to read Change box number – Successful.

Fig 42 – Apply new Box Numbers dialog

Factory Setting Devices If a device on a Philips Dynalite network fails, a factory set of the device maybe required. As the name suggests, factory setting a device will reset its configuration to the default factory settings. The default settings for load controllers are:

• All Channels to Area 1. • Default Preset levels.

The default setting for panels are:

• Set to Area 1. • Button Presets start with 1.

Fig 43 - Factory Presets


50

To factory set a device, complete the following steps:

1. Click on the device you want to Factory Set in the Network view.

2. Click to open the Factory Set dialog.

Fig 44 – Network View – Factory Set icon

3. Click the Save factory reset data to the device now check box.

Fig 45 – Factory set dialog

Note – If you wish to factory set a device as another type, check the Show all products with the same device code and then select the device you need from the available list.

4. Click to confirm.

Topic 4: Wizards

51

TOPIC 4: WIZARDS

Topic Overview Envision Project provides a number of different wizards to help with the commissioning process. This topic covers the use of the New Job Wizard, a tool for creating projects. Some devices also have wizards to assist and speed up the configuration process, we will look at using the bridge and sensor wizards.


• Use the New Job Wizard to create a Philips Dynalite job.

• Configure sensors using the Sensor Wizard.

• Configure bridges using the Bridge Wizard.

New Job Wizard This release of EnvisionProject contains only a “New Job Wizard” that allows users to commission very basic Dynalite systems. This New Job Wizard is provided as an example of how wizards will be provided in EnvisionProject and is not complete as some of the features such as panels are not currently available in EnvisionProject. The New Job Wizard provides the following steps:

1. Define Job Details – define job and site details as well as some default settings. 2. Define Logical Details – define the logical areas and Channels.

3. Add Load Controllers and Assign Channels – provides functionality to automatically create

the load controllers required for the job. Users can then manually modify load controllers and Channel assignments.

4. Add Control Panels – define the panels required for the job.

5. Report Job Summary – provides a summary and submits to the current job.

Topic 4: Wizards

52

Creating a project using the New Job Wizard To create a project using the New Job Wizard, follow the steps below:

1. From the toolbar menu select Wizards then select New Job Wizard....

Fig 46 – Wizards menu

2. Enter Job details, see Fig 47. – Pre-commissioning wizard step 1of 5 : • Job Name. • Site Contact. • Site Address.

3. Enter job defaults, see Fig 47 – Pre-commissioning wizard step 1of 5 :

• Logical template - Select if available. • Presets per Area – Default number of Presets used for job. • Use DIN rail controllers – true or false. • Default Panel type – Select which panel to use.

Fig 47 – Pre-commissioning wizard step 1 of 5

4. Click to continue to step 2 in the wizard.

Topic 4: Wizards

53

5. Create Areas for your project by clicking . Enter the Area name in the Area Properties.

Note: If you make an error whilst adding Areas, highlight the Area and click .

Fig 48 – Pre-commissioning wizard – Adding Areas

6. Once the Areas have been created it is time to add Channels, highlight an Area and then

click .

7. In the Channel Properties enter the following details: • Channel name – Required • Description – Channel description – Optional • Location – Channel location – Optional • Type – choose the Channels load type – Required. Note: If you make an error whilst adding Channels, highlight the Channel and click

.

Topic 4: Wizards

54

Fig 49 – New Job wizard - Adding Channels

8. Add the required Channels to each Area as shown in Fig 50 – Pre-commissioning wizard – Adding Channels.

Fig 50 – New Job wizard – Adding Channels

9. Click to continue to step 3 of 4 in the wizard.

Topic 4: Wizards

55

10. Now it is time to add load controllers. To add a new Load Controller click and the Create New Device dialog will appear, shown in Fig 51 - Pre-commissioning wizard - Adding load controllers.

Fig 51 – New Job wizard - Adding load controllers

Fig 52 – New Job wizard – Adding load controllers

Topic 4: Wizards

56

11. In the tab, click on the device you wish to add to the project and add following device details:

• Device Name – Optional. • Device Location – Optional. • Device Description – Optional.

Sign on the load controller to discover the Device Properties, its box and serial numbers,

alternately you can manually enter this information, once completed, click .

12. We now need to assign Channels. To do so, we need to drag the physical Channels across from the left hand side of the dialog to the right hand side containing our Areas.

Click and drag the appropriate Channel to the Area you want and drop it. See Fig 53 - Pre-commissioning wizard – Assigning logical Channels.

Fig 53 – New Job wizard – Assigning logical Channels

13. Repeat step 12 for each load controller in your project.


Topic 4: Wizards

57

15. Next, we will configure panels, click . The Pre-commissioning wizard automatically adds a panel to each Area created earlier.

Fig 54 – New Job wizard – Adding panels

16. Click to remove any unwanted panel that may have been created by the wizard.


17. Click to add any extra panels required for your project.

Topic 4: Wizards

58

18. If you wish change a panel type for an Area, Select the panel and in the panel properties

click to choose another panel type.


Note – Click for details of the panel and a larger image.

19. Select the panel type you want and click .

Fig 57 – New Job wizard – Configuring panels

Topic 4: Wizards

59


Fig 58 – New Job wizard Job Summary

21. Review the job summary details and once satisfied, click . EnvisionProject will create the job for you. The details will be visable in the Network and Logical views.

Fig 59 – Created Job Summary

22. Click to finish the New Job Wizard. Note – Devices added by the Pre-Commissioning Wizard still require their box numbers to be changed before saving to devices.

Topic 4: Wizards

60

Sensor Configuration Wizard The sensor configuration wizard allows users to select a sensor function and an IR button configuration. A number of other parameters are requested depending upon the sensor function selected. The available sensor functions are:

• Day / Night Switch – Light level control.

• On / Off Motion Switch – Motion control.

• On Only Motion Switch - On motion control.

• Security Sensor – Combined motion and light level control. To use the sensor configuration wizard, follow the steps below:

1. Left click on the sensor you wish to configure and select Sensor Configuration Wizard....

Fig 60 – sensor right click menu

Topic 4: Wizards

61

2. Use the Drop down menu to select the Sensor Function, shown in Fig 61 - Sensor Configuration Wizard.

Fig 61 – Sensor Configuration Wizard

3. Click in the Logical Area field and click to select the Area you require.


Topic 4: Wizards

62

4. Click on the Area you want and click , shown below:

Fig 63 – Area selection dialog

5. Edit the following Sensor Configuration Parameters as required: • No motion time out – default = 10 sec. • On Preset – default = 1. • On fade – default =2 sec. • Off Preset – default = 4. • Off fade – default = 2 sec.


6. Click to complete the Sensor Configuration Wizard.

Topic 4: Wizards

63

Bridge Configuration Wizard The bridge configuration wizard allows users to select a bridge function. The available bridge functions are Pass All, Translate and Legacy Devices. If the Translate bridge function is selected then the Area and box number range parameters are required.

Translation Mode Translation mode is used in large projects where section need to be isolated from one another say, in a multi floor office installation. To configure a bridge for translation mode, complete these steps:

1. In the Network view, click on the bridge you want to configure.

2. Right click on the bridge and select Bridge Configuration Wizard...

Fig 65 – Bridge right click menu

Topic 4: Wizards

64

3. Select Translate from the Bridge Function drop down list.

Fig 66 – Bridge Configuration Wizard - Translate

4. In the Area and Box number Range enter an Offset value.

5. Click .

6. Click to save the change to the bridge.

Topic 4: Wizards

65

Pass All The pass all function of a bridge is used when we need to exceed either of the limits of CAT5 cable. To configure a bridge for translation mode, complete these steps:

1. In the Network view, click on the bridge you want to configure.

2. Right click on the bridge and select Bridge Configuration Wizard...

Fig 67 – Bridge right click menu

Topic 4: Wizards

66

3. Select Pass All from the Bridge Function drop down list.

Fig 68 – Bridge Configuration Wizard – Pass All

4. Click

5. Click to save the change to the bridge.

Topic 5: The Assistant

67

TOPIC 5: THE COMMISSIONING ASSISTANT

Topic Overview This topic covers the use of the Commissioning Assistant Side Bar, a tool used to guide you through the process of commissioning a Philips Dynalite network.


• Use the Commissioning Assistant Side Bar to commission a Philips Dynalite project.

About the Commissioning Assistant In addition to the wizards EnvisionProject provides a Commissioning Assistant side bar. Unlike the wizards that provide a completely separate set of user interfaces the Commissioning Assistant side bar walks a user through each step of commissioning a Dynalite system using the main DLight4 interface. Each step is explained in detail and links are provided to direct you to the area required in EnvisionProject to perform the task. Some steps contain tips to further assist you. Where the Pre-commissioning Wizard can only be used for pre-commissioning basic Dynalite systems the Assistant can be used to commission a system of any size. The Assistant is also ideal for those who haven’t commissioned a system recently and need reminding of some of the steps. To enable the Commissioning Assistant side bar, select it from the View menu in the EnvisionProject toolbar shown below in Fig 69 – view toolbar menu.

Fig 69 – View toolbar menu


68

Fig 70 – Commissioning Assistant Side Bar

1. Create Job To begin a new job must be created.

1. Expand 1. Create Job.

2. Click Create a new job.

Fig 71 – 1. Create Job

Next save the new job to a job file. It is a good idea to save the job after completing each of the steps.

1. Click Save job to a file.

2. Enter a file name and click .


69

2. Define Job Details The name of the job and other site contact details can be entered into the site properties editor. This is available when the top most job item is selected in either the logical or network views.

1. Expand 2. Define Job Details

2. Click on Show site properties editor.

3. Enter job details.

Fig 72 – 2. Define Job Details

Tips:

• Additional job properties can be added using the ‘Add Property’ button in the tool strip.

3. Connect to the Dynalite Network Much of a Dynalite job can be commissioned offline so if pre-commissioning a job then skip this step. If the computer was attached to a Dynalite RS485 network when the job was opened or created then it should have automatically connected to the network. The current connection status can be seen in both the window title and the status bar. If the job is not automatically connected or you wish to connect via an Ethernet connection then open the connection settings. The connection settings can be accessed from the ‘Tools’ menu.

1. Expand 3. Connect to the Dynalite Network..

2. Click Show connection settings.

3. See Connecting to the System page 22.

Fig 73 – 3. Connect to the Dynalite Network


70

4. Define Logical Information This requires defining the logical areas and logical channels for a job. Logical areas and channels are added into the logical view using the ‘Area’ and ‘Channel’ menu items under the main “Insert” menu or using the ‘Insert Area’ or ‘Insert Logical Channel’ buttons on the logical view tool-strip.

1. Expand 4. Define Logical Information

2. Click Show logical view.

3. Click to add an Area. 4. Enter the name for the Area. 5. Repeat steps 3 and 4 for all the Areas in your project.

Fig 74 – 4. Define Logical Information

A logical Area should be created for each room or large open spaces may have an Area for each section. A logical channel should be created for each circuit of group of circuits that are to be controlled together. Provide meaningful names that describe each and logical channel.

Tips: • All items in the logical and physical trees can be renamed using F2. • Areas and channels can be copied and pasted.


71

5. Add Load Controller Devices Load controllers can be added using the ‘create new device window’. If the box number is known it can be manually entered or if the load controller is signed-on the box number will be automatically filled. If pre-commissioning or the load controller is not yet installed then don’t worry about the box number as it can be changed later to match the actual box number. This also applies to other devices such as control panels and sensors. Alternatively load controllers can be added by searching the Dynalite network from the ‘load devices from network’ window. Once the load controllers have been added they will be shown in the network view. From the network view these load controllers can then be later configured. Provide a meaningful device name and location for each load controller. 1. Expand 5. Add Load Controller Devices. 2. Click Open controllers in ‘create new device’ window. 3. Click Search in ‘load devices from network’ window.

4. Click .

5. Click .

6. Click the device search dialog. 7. Click Select load controller in network view.

Fig 75 – 5. Add load Controller Devices


72

6. Assign Physical Channels Assigning physical channels involves associating the load controller physical channels (or circuits) with a logical address. This is done by assigning each physical channel to a logical area and logical channel. Once a physical channel is assigned to a logical channel it will be shown under that logical channel in the logical view. The best way to assign physical channels is from the unassigned channels list. This is a list of all physical channels that have not yet been assigned to a logical address. To assign an unassigned physical channel simply drag it from the unassigned channels list onto the appropriate logical channel in the logical view. The logical view also allows physical channels to be reassigned to different logical channels by dragging them to another logical channel. 1. Expand 6. Assign Physical Channels.

2. Click Show logical view and ‘unassigned channels list’.

3. In the click and drag the unassigned channels to the appropriate Areas in the Network view.

Fig 76 – Assigning Logical Channels

Fig 77 – 6. Assign Physical Channels


73

Tips: • If unsure about which circuit is wired to a physical channel then flashed the channel

from either the unassigned channels list or the logical view. • If a physical channel is dragged onto an area then a new logical channel will be

automatically created. • If a physical channel has not been explicitly named then when assigned it will be

automatically named to that of the area and logical channel names. • Multiple physical channels can be selected and assigned together.

An alternative option is to only define logical area and then go through the list of unassigned physical channels. Identify and name each physical channel and then drag onto the area in which it is to be assigned. A logical channel will be automatically created with a name matching the physical channel.

7. Add User Interface Devices User control panels can be added using the ‘create new device window’. If the box number is known it can be manually entered or if the panel is signed-on the box number will be automatically filled. Alternatively user control panels can be added by searching the Dynalite network from the ‘load devices from network’ window. Once the control panels have been added they will be shown in the network view. To configure control panel buttons select each panel in the network view. By default each control panel button is usually configured to send area preset messages, however each button can be reconfigured individually.

1. Expand 7. Add user Interface Devices

2. Click Open panels in ‘create new device’ window.

3. Click Search panels in ‘load devices from network’ window.

4. Click .

5. Click .

6. Click Select control panel in the network view.


74

Fig 78 – 7. Add User Interface Devices

Tips:

• Control panels can be flashed to help identify them. • Use the ‘Change Area’ function to configure a control panel and its buttons to an area. • If configuring many control panels of the same type then configure one and copy and

paste the panel onto others. Then use the ‘Change Area’ function to update the area only.

• Panel buttons can be multi-selected to change a common property or for copy and pasting.


75

8. Add Sensor Devices Sensors can be added using the ‘create new device window’. If the box number is known it can be manually entered or if the sensor is signed-on the box number will be automatically filled. Alternatively user control panels can be added by searching the Dynalite network from the ‘load devices from network’ window. Once the sensors have been added they will be shown in the network view. To configure sensors select one or more sensors in the network view and run the ‘sensor wizard’. The sensor wizard is available from the main ‘Device’ menu or from the button on network view tool-strip.

1. Expand 8. Add Sensor Devices.

2. Click Open sensors in ‘create new device’ window.

3. Click Search sensors in ‘load devices from network’ window.

4. Click .

5. Click .

6. Click Select sensor in the network view.

Fig 79 – 8. Add Sensor Devices


76

Tips: • Sensors can be flashed to help identify them. • Use the ‘Change Area’ function to change the area of a sensor. • If configuring many sensors to perform a similar function then configure one and copy

and paste the sensor onto others. Then use the ‘Change Area’ function to update the area only.

• Sensors can also be multi-selected to compare or configure together.

9. Create Tasks Tasks are used to provide a sequence of pre-defined actions and can contain conditional logic. To add a task select the device in the network view on which a task is required to run and select the ‘Task and Event’ editor.

1. Expand 9. Create Tasks.

2. Click Show network view.

Fig 80 – 9. Create Tasks

10. Create Events Events are actions that occur at a scheduled point in time. A device with a time clock is required on the network to run schedules. Timeclocks can be added using the ‘create new device window’. If the box number is known it can be manually entered or if the timeclock is signed-on the box number will be automatically filled. Alternatively timeclocks can be added by searching the Dynalite network from the ‘load devices from network’ window. To add an event select a timeclock in the network view on which a event is required to run and select the ‘Task and Event’ editor.

1. Expand 10. Create Events.

2. Click Open timeclocks in ‘create new device’ window.

3. Click Search timeclocks in ‘load devices from network’ window.

4. Click .

5. Click .

6. Click Select timeclocks in the network view.


77

Fig 81 – 10. Create Events

11. Define Logical Presets The logical presets (or scenes) are used to define pre-defined light levels for each area. The preset editor is available when an area is selected in the logical view. The light levels for each logical channel can be adjusted per preset by selecting a preset and moving the ‘level adjust’ slider to the required level. The preset editor also allows additional presets to be created.

1. Expand 11. Define Logical Presets. 2. Click Show preset editor.

Fig 82 – 11. Define Logical Presets

Tips:

• The current levels can be changed without effecting the preset levels by selecting the ‘Current Levels’ item.

• A preset table view is provided for quickly entering preset levels in a table.


78

12. Save Data to Devices Once all required devices have been configured then the data in the job needs to be saved to the devices. If pre-commissioning or not currently online then this can be done later. Device data can be saved to one or more of the devices by selecting them in the network view and clicking ‘Save to Device’ from the main ‘Device’ menu or the button on network view tool-strip. Alternatively all changes can be saved for all modified devices by clicking below. This option is also available under the ‘Tools’ menu. When saving to devices the status and progress can be viewed in the command monitor.

1. Expand 12. Save Data to Devices. 2. Click Show network view.

3. Click Save all modified devices.

4. Click Show command monitor.

Fig 83 – 12. Save Data to Devices

Topic 6: Configuring Load Controllers

79

TOPIC 6: CONFIGURING LOAD CONTROLLERS

Topic Overview The fundamental principle of operation of a Dynalite control network is cantered on grouping related circuits into areas and then recalling Preset scenes for those areas. This method of operation is entirely dependent on the load controllers being commissioned correctly. Once this vital work is completed the project has a solid foundation on which any number of operational features can be applied. This section is focused on getting the logical configuration of the load controllers correct.


• Identify physical Channels in a Philips Dynalite project.

• Configure a load controller using EnvisionProject.

The floor plan and equipment list Some kind of floor plan is needed to enable the programmer to break up the site into controllable chunks called areas. This plan would ideally be taken from the engineering drawings but could be as simple as a sketch on a pad.

Fig 84 – Philips Dynalite training case floor plan


80

Equipment list The programmer should be issued with a list of supplied products for a project before they arrive at site. This is the only way to ensure that each device on the network is accounted for. The Training case V2 contains:

• 2 x DDBC1200 – Ballast Controllers.

• 1 x DLP950 – 5 button panel.

• 1 x DPN881D – 8 button panel with key switch.

• 1 x DPWE – 5 button panel.

• 1 x DRP96K –6 button panel.

• 1 x DUS704C 0r 1 x DUS804C –Universal Sensor. The Mini Training Case contains:

• 2 x DDBC1200 – Ballast Controllers.

• 2 x DR2P98M – 8 button panel.

Flashing Flashing is used to identify the location of circuits and devices in a project, this information is then used to determine logical Area and Channel assignments to create a load schedule for commissioning. There are 2 levels of Flashing, by device or by individual Channel. Flashing a device is used to find its physical location, additionally Flashing a load controller enables the identification of all Channel locations simultaneously, in large projects, this allows for the general location of the circuits for a load controller to be quickly identified. Flashing by Channel is used to identify the specific physical locations of Channels for the load controller, a load schedule maybe created using this information. EnvisionProject provides support for flashing the following items:

1. Logical Areas – Alternatively sends fade Area (all Channels) 0% and 100% messages. Areas can be flashed from the Logical view.

2. Logical Channels – Alternatively sends set logical Channel level 0% and 100% messages. Logical Channels can be flashed from the Logical view or the logical Preset editor.

3. Physical Channels – Alternatively sends set physical Channel level 0% and 100% messages.

Physical Channels can be flashed from the Logical view, the unassigned Channels view or the physical Preset editor.

4. Load Controllers – Alternatively sends set all physical Channels level 0% and 100%

messages. Load controllers can be flashed from the Network view, the unassigned Channels view or the devices references view.


81

5. Panels and Sensors – Places the device into setup mode and maintains the device in setup mode by sending “Listen to me” messages. Panels and sensors can be flashed from the Network view or the devices references view.

Once any of the above items are placed into a flashing state their corresponding icons will indicate they are flashing in all views. The flash period is control by the user settings “Flash on period” and “Flash off period”. The default values for these are 100 milliseconds (1 second). All flashing messages have a zero fade rate. If a physical Channel is a ballast type or a load controller, logical Area or logical Channel contain a ballast Channel then by default the item will only flash off every second flash cycle. This is to allow ballasts to have sufficient time to flash on. To disable this feature set the user setting “Double on flash for ballast” to false. To Flash a device complete the steps below:

1. Click on the device you wish to Flash in the Network view.


2. Click in the Network view toolbar, the devices display icon will change to the Flash icon. The device is now Flashing.

3. Click to stop device Flashing.


82

To Flash individual Channels follow the steps below:

1. Click on the Channel you wish to Flash in the Logical view.

Fig 86 – Logical View

2. Click in the Logical view toolbar, the devices display icon will change to the Flash icon. The device is now Flashing.

3. Click to stop device Flashing.


83

Load Schedule

Project: Device Type:

Box No:

Ch # Channel Name Area Name Area # Logical Ch # Dup/Sw 1

2

3

4

5

6

7

8

9

10

11

12

Project: Device Type:

Box No:

Ch # Channel Name Area Name Area # Logical Ch # Dup/Sw 1

2

3

4

5

6

7

8

9

10

11

12


84

Manual Load Controller Configuration To manually configure a load controller, complete the steps below:

1. Click on the load controller you wish to configure in the Network View, shown in Fig 87 – Network view.


2. Click on in the Main Editor Properties.

Fig 88 – Channel Editor tab

3. Flash Channels as required, (see section on Flashing for more details).


85

4. Using information from your load schedule (see section on Load Schedules in this topic), click in the first Physical Channels Channel Name field to enter its new Channel name, see Fig 89 – Channel Editor tab.


5. Hit Enter to move to the next Physical Channels Channel Name field and enter its new Channel name. Continue this process for the remaining Channels in the load controller.

6. Next we will configure the Logical Areas Using information from your load schedule (see section on Load Schedules in this topic), click in the first Physical Channels Logical Area field to enter its new Area number, see Fig 90 – Channel Editor tab.


7. Hit Enter to move to the next Physical Channels Logical Area field and enter its new Area number. Continue this process for the remaining Channels in the load controller.

8. Now we will configure the Logical Channels. Using information from your load schedule (see

section on Load Schedules in this topic), click in the first Physical Channels Logical Channel field to enter its new Channel number, see Fig 91 – Channel Editor tab.


86


9. Hit Enter to move to the next Physical Channels Logical Channel field and enter its new Area number. Continue this process for the remaining Channels in the load controller.

10. Once the required Channel name, Logical number and Logical Area have been added, click

in the Network view toolbar to save the settings to the load controller.


87

Logical Load Controller Configuration To logically configure load controllers, complete the steps below:

1. Click .

2. Select .

3. Expand each load controller displayed

4. Select a Channel in the list and click to name the Channel.

Fig 92 – Unassigned Channels tab

5. Click and drag the Channel from the Unassigned Channels tab to the correct Area in the Logical view.


88

Fig 93 – Unassigned Channels tab and Logical view

Note – If you are unsure of which Area to assign a channel, click to flash and identify the location of the channel.

6. Repeat steps 3 & 4 for all the remaining unassigned Channels.

7. Click .

8. Select the load controller/s from the List (it should have in the status column).

9. Click to save changes to the device.

Topic 7: Configuring Panels

89

TOPIC 7: CONFIGURING PANELS

Topic Overview Once the load controllers have been configured, the panels are used to recall the Area Preset scenes to create the required effect for the end user. Panels can be configured to perform many functions directly from the GUI.


• Setup control panels to send default Preset messages to a defined Area.

• Configure individual buttons to perform different functions.

• Competently set up Preset scenes with a lighting designer.

Panel settings

Device Properties Tab The device properties for panels contain a number of tabs for configuration:

• Device Properties – General panel properties, name, box number, native Area.

• Buttons – Button configuration settings.

• Task and Events – Tasking and event information.

• IR Buttons – IR button configuration.

• Switches – Switch configuration.

• DyNet Ports – DyNet port information.

• Product details – Picture and description of panel.


90


Assigning a panel to an Area To assign a panel to an Area, follow these steps:

1. In the Network view, click on the panel you wish to assign to an Area.



91

2. Click to display the Change Panel Area dialog.

Fig 96 – Change Panel Area dialog

3. Click to choose from the available Areas.

Fig 97 – Area Selection dialog


92

4. Click on the Area you require and click .

Note –The change options section allows you to apply the Area change to the Whole panel including buttons, sliders, IR buttons and key switches or just for the panel itself which is called the native panel Area.

Fig 98 – Change Options

5. Click to complete the Area change.

6. Click to save the change to the panel.

Changing Panel box numbers To change a panel’s box number, complete the steps below:

1. Click on the panel you wish to change box numbers then click .

2. Click in the Box Number field and enter the new box number.



93

3. Confirm the box number is correct in the Change Device Box Number dialog.

Fig 100 – Change Device Box Number dialog

4. Click to complete the box number change.

Enable Area zero messaging Area zero has a unique function; it broadcasts to all Areas and is useful for controlling a whole network together. As Area zero broadcast to all Areas and Channels in a network it could be potentially dangerous if there is non- lighting integration of the network say, with a 3rd party security system. If we use an Area zero message to turn off all the ‘lights’ we will also turn off the security system. With this in mind, should you wish to allow a device on the network to broadcast Area zero messages, it must be specifically enabled. To enable Area zero messaging from a panel, complete the steps below:

1. Click .

2. Click in the Area Zero Transmit field to and select Enabled, see Fig 99 – Device Properties tab.


94

Fig 101 – Device Properties tab


Panel Views When configuring panels in the Buttons tab, 2 views are available, Panel view and Button list view.

provides an image of the panel you are working on, clicking on a button in the image enables you to work on that button, shown in Fig 100 – Panel view.

Fig 102 – Panel view


95

enables a quick identification of the functions of buttons with icons and a brief description. See Fig 101 – Button view.

Fig 103 – Button view

Configuring Panels There are a large number of functions that can be applied to buttons in a panel, we will now look at 2 of the most popular, Presets and One Touch.

Configuring Presets To configure a button on a panel to call a Preset, complete the steps below:

1. Click .

Fig 104 – Buttons tab


96

2. Click in the Function Type field.

Fig 105 – Function type

3. Select Preset from the drop down list.

Fig 106 – Function Type drop down list


97

4. In Preset Action, click on Preset.

Fig 107 – Preset Action

5. Select the Preset you require from the drop down list.


6. In Preset Action, click on Logical Area.

Fig 109 – Logical Area


98

7. Click to select the Area you want.

Fig 110 – Area Selection

8. Click .

9. In Preset Action, click on Fade Time and enter the fade time you want (default is set to 2 seconds).

Fig 111 – Fade Type



99

Configuring one touch

1. Click .


Fig 112 – Function Type

3. Select from the 3 One Touch options available in the drop down list: • One Touch Preset Toggle. • One Touch Ramp Only. • One Touch Ramp with Program.

Fig 113 – Function Type drop down list


100

4. In Preset Action, click on On Preset.

Fig 114 – On Preset

5. Select the Preset you require from the drop down list. (Default 1).


6. In Preset Action, click on Off Preset.

Fig 116 – Off Preset

7. Select the Preset you require from the drop down list. (Default 4).


101


8. In Preset Action, click on Ramp Rate and enter the ramp time you want (default is set to 5 seconds).

Fig 118 – Ramp Rate

9. In Preset Action, click on Logical Area.

Fig 119 – Logical Area

10. Click to select the Area you want.


102

Fig 120 – Area Selection

11. Click .

12. In Preset Action, click on Logical Channel.

Fig 121 – Logical Channel

13. Select the Logical Channel you require from the drop down list.

Fig 122 – logical Channel drop down


103

14. In Preset Action, click on Fade Time and enter the fade time you want (default is set to 2 seconds).

Fig 123 – Fade Time


Topic 8: Configuring Sensors

104

TOPIC 8: CONFIGURING SENSORS

Topic Overview The DUS704 sensor combines motion detection (PIR), infra-red remote control reception (IR) and ambient light level detection (PE) in the one device. In applications such as homes, lecture theatres and office towers, DUS704 universal sensors can be utilised to detect motion and switch on the lights. This topic covers the set up and configuration of the universal sensor.


• Configure Philips-Dynalite sensors for occupancy control function.

• Control an Area based on natural light levels.

About the universal sensor The DUS704 Universal Sensor is an integrated energy management sensor and Area controller. Sensor functions include:

• Occupancy detection.

• Light Level Compensation.

• Infrared Control. When rooms are unoccupied, lights can be automatically dimmed or switched off to provide energy savings. The same sensor provides IR remote control reception to give IR control over lights, audio-visual equipment and blinds. These codes can be stored in learning remote and used to control the lighting, TV etc… from a single remote controller. In situations where it is critical to maintain precise lighting control for individual workspaces, such as a flight control tower or office workstation, the DUS704 facilitates light compensation. The DUS704 can be placed in an automatic “Daylight Harvesting” mode for energy savings. The sensor is available in 2 styles, for ceiling and wall mounting.

Fig 124 - DUS704C Fig125 - DUS704W Fig 126 - DUS804C Fig 127 – DUS804C-UP Ceiling Mounted Wall Mounted Ceiling Mount Ceiling Mount


105

Occupancy detection The objective of occupancy detection is to automatically illuminate a space when it is occupied, and reduce or extinguish lighting when it is vacant to save energy. Any number of light fixtures may be controlled for occupancy detection from a single sensor. Key point - When the DUS704 is powered up, occupancy detection functions are inhibited and no motion actions will be processed for a period of up to 30 seconds while the sensor hardware filters settle and the sensor adjusts itself to the ambient air temperature.

Occupancy detection example Within the DUS704 a set of Presets is defined, as the occupancy monitoring Presets, typically 3 Presets are defined.

Fig128 – Motion sensor configuration flow chart

In this example, they are named ‘Occupied’, ‘Grace’ and ‘Vacant’. No definition is configured for other Presets.

• For the ‘Occupied’ Preset (Preset 1) the space is illuminated to provide occupants with suitable lighting levels. The DUS704 is configured to change to the ‘Grace’ Preset after 30 minutes of no motion activity.

• In the ‘Grace’ Preset (Preset 2) the space is dimmed to warn any occupants that the lights

are about to be automatically turned off. The DUS704 is configured to return to the ‘Occupied’ Preset if motion is detected. If a period of 5 minutes of no motion activity passes the DUS704 will progress to the ‘Vacant’ Preset.

• For the ‘Vacant’ Preset (Preset 4) the lights are turned off to save energy. The DUS704 is

configured to select the ‘Occupied’ Preset when motion is detected.


106

Occupied Preset action

Fig129 – Occupied Preset

‘Occupied’ Preset (Preset 1) actions should include an ‘Unoccupied action’ to go to the ‘Grace’ Preset (Preset 2). The ‘Occupied action’ should be set to ‘No Action’. The timeout should be set to 1800 seconds (30 minutes).

Grace Preset action

Fig 130 – Grace Preset

The ‘Grace ‘Preset (Preset 2) actions should be to revert to the ‘Occupied’ Preset (Preset 1) when motion is detected, or fall back to the ‘Vacant’ Preset (Preset 4) when there is no motion detected for the time out period.

Vacant Preset action

Fig131 – Vacant Preset

The ‘Vacant’ Preset (Preset 4) actions should recall the ‘Occupied’ Preset (Preset 1) when motion is detected. No action should be configured for the ‘Unoccupied action’.


107

Configuring occupancy detection To configure a sensor for motion detection, follow the steps below:

1. In the Network view, click on the sensor that requires configuration and then click

in the Properties view.

Fig 132 – Motion detector tab

2. Sensors are configured per Preset, so we’ll start with Preset 1 and move sequentially. Click

to configure settings for Preset 1.

3. Each Preset has 2 conditions to be determined, a motion action and a no motion action.

Click .


108

Fig133 – Action chain Editor

4. Click and select .

Fig 134 – Action options list

5. In the Preset Action properties change the Preset number to 2.


109

Fig135 – Action chain editor


7. Click in the Time out field and enter 30 mins, see Fig 134 - Motion detector properties.

Fig136 – Motion detector properties

8. Now we’ll configure the next Preset. Click to configure settings for Preset 2.

9. Click .


Fig 137 - Action options list


110


Fig 138 – Action chain Editor


13. Click .


Fig 139 - Action options list



111

Fig 140 - Action chain Editor


17. Click in the Time out field and enter 5 mins, see Fig 139 – Motion detector properties.

Fig 141 – Motion detector properties

18. Click to add settings for Preset 3. In our scenario, we are using only 3 Presets, Preset 1 (on Preset), Preset 2 (Grace Preset) and Preset 4 (off Preset). Therefore Preset 3 is unused so we will leave it configured to No Action.

19. Next we’ll configure the final Preset. Click to configure settings for Preset 4.

20. Click .



112



Fig 143 – Action Chain Editor


24. Your configuration is complete, double check the setting in the table in the Main properties.

Fig 144 – Motion detector properties

25. Click to save the settings to the sensor.


113

Configuring light level sensing

Open loop light level compensation example Follow these instructions to configure a sensor for open loop light level compensation:

1. Click in the sensor main properties.

Fig 145 – Light Control tab

2. Click to create a night band Preset,

3. Click .


114





115

5. Select the Preset and Fade time you want from the Preset Action properties.

Fig 148 – Action chain editor Band 1

6. Click to continue.

7. Click to create a day band Preset.

8. Click .




116

10. Select the Preset and fade time you want from the Preset Action properties.

Fig 150 – Action chain editor Band 2

11. Click to continue.

12. Click to save the settings to the sensor.

Start up delay When the DUS704 is powered up, occupancy detection functions are inhibited and no motion actions will be processed for a period of up to 30 seconds while the sensor hardware filters settle and the sensor adjusts itself to the ambient air temperature.


117

Sensor Calibration Follow these instructions for one point light sensor calibration:

1. In the Network view, click on the sensor that requires calibration then click in the properties view.

Fig 151 – Calibration tab

2. Click to show the Raw Level.


118


3. In the Lux Level field, enter your desired lux level.



119

4. Click .


5. When the confirmation dialog appears, click .

Fig 155 – Confirmation dialog

Topic 9: Configuring Other Devices

120

TOPIC 9: CONFIGURING OTHER DEVICES

Topic Overview This topic covers the configuration of Philips Dynalite time clocks and Ethernet gateways for wireless connectivity to a DyNet network.


• Configure the 100BT product range for wireless connectivity to a DyNet network.

• Configure time clocks.

DTC602 The DTC602 is an astronomical 365 day timeclock with Sunrise/Sunset tracking, automatic Daylight Saving adjustment, and po werful macro and conditional logic functions.

Setting the time To set the time on a time clock, follow the steps below:

2. Right click on the time clock in the Network view.

3. Select Set Realtime Clock....

Fig 156 – Time clock right click menu


121

4. Select the way you wish to set up the time: • Synchronise with PC time. • Manually set device time.

If you choose Manually Set Device Time, complete these extra steps:

• Enter the time you require. • Enter a date using the calendar drop down.

Fig 157 – Realtime clock dialog

5. Click to apply the changes.

6. Click to finish.


122

DNG100BT The DNG100BT/DDNG100BT/DMNG100BT product range is Philips Dynalites ethernet gateway, It can be utilised as a network bridge or to facilitate wireless connection to a Philips Dynalite network. For Bridge configuration see section on Bridge Wizards.

Wireless DyNet Network Connection To configure a 100BT device for wireless Dynet connection, follow the steps below:

1. In the Network view click on the Network Gateway you wish to configure.

2. Click .

3. Choose if you want to use a static IP address.

Fig 158 – Ethernet Gateway tab

Static IP Addressing • Select False from the drop down list.

Manual IP Addressing

• Select True from the drop down list. • Enter a logical IP Address – Required. • Enter a Subnet mask – Optional. • Enter a Gateway – Optional.


123

4. Change the Passive TCP field to Enabled.

Fig 159 – Ethernet Gateway tab

5. Enter 12345 into Local TCP port number field.

6. Click to save the settings to the network gateway.

DDMIDC8 The DDMIDC8 is designed to enable cost effective input integration to the Philips Dynalite control system from third party systems such as Security, HVAC and BMS. The interface incorporates a Programmable Logic Controller that can process comprehensive conditional and sequential logic and arithmetic functions.

Configuring dry contact inputs to send Preset messages To configure DDMIDC8 dry contact inputs, follow the steps below:

1. In the Network view click on the DDMIDC8 you wish to configure.

2. Click .

3. In the logical Area field, click to select the Area you require.

4. In the Function field, select Preset from the drop down menu.

5. In the Preset field, select the Preset you require.

6. Click to save the settings to the device.


124

Configuring analogue inputs to trigger tasks To configure DDMIDC8 analogue inputs, follow the steps below:

1. In the Network view click on the DDMIDC8 you wish to configure.

2. Click Analogue.

3. In the logical Area field, click to select the Area you require.

4. .

5.


Topic 10: Sequential Tasking

125

TOPIC 10: SEQUENTIAL TASKING

Topic overview This topic covers the most frequently used type of tasking which is the sequential task. It uses real examples to reinforce understanding and these examples can be directly applied to future projects both from a sales and a programming perspective.


• Use a text editor to create sequential tasks.

• Save tasks to a panel.

• Assign tasks to buttons.

• Implement Preset ‘offsets’.

• Change the Preset function of a button as needed.

About tasking It is through tasking that the Dynalite control system really comes into its own. Tasks allow a system to be completely tailored to the needs of even the most demanding of clients and most tasks are relatively straightforward to build once you understand a few simple commands. Tasks can be broken down into two basic types. There are sequential tasks that run from top to bottom through the code and execute each command in a fixed sequence. Then there are conditional tasks that can change in operation based on variables such as the time of day, weather, current system status etc. Of the two, sequential tasks are the easier ones to follow and understand for the new user. They are the task types created by the Wizard’s Task page and so we will explore these tasks first.


126

TASK EDITOR The task editor is a built in feature of EnvisionProject that enables you to write tasks for a Philips Dynalite network. Tasking allows for the creation of large variety of lighting effects and additionally control of third party systems can be achieved.

Opening the EnvisionProject Task Editor To open the EnvisionProject Task Editor:

1. Click on the device you wish to edit tasks for in the Network view.

2. Select the tab.

3. Click to open the editor.

Saving your task

Once your task has been written, click to save the task to the device.

Fig 161 – EnvisionProject Task Editor


127

Running a task from a panel Once the task has been saved to a device then one last step remains, assigning it to a button.

1. Click .

Fig 162 – Buttons tab


Fig 163 –Function type

3. Select Local Task from the drop down list.

Fig 164 – Function type drop down list

4. Enter the task number you require.


128

Fig 165 – Button properties

5. Click to save the settings to the panel.

My First task My first task is a simple lighting path way, this is commonly used in tasks such as ‘Welcome home’ and ‘baby’s crying’. This task sets Areas 2, 3, 4 and 5 to Preset 1 with a delay of 1 second between each step.

Fig 166 – My First task The Preset messages allow Area Preset messages to be written in a simpler straightforward way; The Preset message can carry up to 5 values; Area, Preset, Fade, Join level and Bank. Each of these values has a default value if it is not declared in the Preset message or by a local default. Preset message defaults:

• Area = 1.

• Preset = 1.

• Fade = 0.2 seconds.

• Join = 0xFF (All join levels on).

• Bank = 1.


129

Commenting code Comments are an important part of tasking as they are used to describe steps in task Add comments to help you and others easily understand the operation of the task. Comments are preceded by 2 forward slash (//).

Fig 167 – Comments

Task constants The task we have just discussed contains a number of constant values such as the delay and Preset number. When this is the case we can declare a default value at the start of the task and that value will be used in the task whenever that expected value is not given. The task will then look like this:

Fig 168 – Task constants

Sequential task applications Now that we can send multiple Preset messages from a single button press, we can consider what useful operational features we can offer to the end user.


130

Goodnight task The most common feature in a home is the master bedroom bedside panel button that puts the house into night mode. All the task requires is a sequence of Preset messages that start from the lighting that is furthest from the master bedroom and work back to the bedrooms. The fade and delay can be adjusted to create the desired effect during the shutdown.

Fig 169 –Goodnight task The default-Preset value has been overwritten on line 26 (A=4, P=9) to send the outside lights to a specific Preset to give a security setting for the exterior lighting. The declared fade on line 30 (A=7, F=10) allows the corridor lighting to fade off slowly. This gives visible feedback to the user as well as a nice effect of the house slowly going to sleep. If it had suited the application the delay could have been overwritten in any of the Delay() lines.


131

Channel level messaging Channel level messages allow individual Channel levels to be set using a task. This function allows a task to have full individual Channel control over an Area. The example below sends Area 2, Channel 1 to 100%.

Fig 170 – Channel level message

Code Description C Any Channel from 1 to 255 L Any level from 0 to 100% A To specify an Area

F To specify a Fade rate, (8 bit only i.e. max 5secs)

J To specify a Join Level Channel Level message defaults:

Type Default Area 1

Channel 1

Level 1%

Fade 0.2 seconds Join 0xFF (All join levels on)

Key Point - The maximum fade time available when using a Channel Level message is 5.1 seconds.


132

Night mode for bathroom task Providing a button to turn the lights on to different levels during the ‘day/night’ in a bathroom is a straightforward function that creates a great effect and also a great selling point in a home. A time clock sends a message to the dimmers that changes which Preset they go to at different times. So during the day when the ‘on’ button is pressed the dimmers send the lighting to Preset 1 or 100%. After sunset the button still sends a Preset 1 but the dimmers apply an offset of 4 (as an example) and go to Preset 5 or 60%. Added to the goodnight task is a message that sends a Preset offset of 8 so when the ‘On’ button is pressed the dimmers go to Preset 9. At sunrise the time clock sends an offset of 0 and each Preset returns to its true levels. In this way the user uses the same button but gets a light level suited to the time of day. To further refine this feature we can add a function that allows the user to ramp the lighting to full whatever the current levels by just holding the button down for 1 second.

Night mode task for panel

Fig 171 – Night mode with ramp task To achieve this functionality both tasks in Fig 171- Night mode with ramp task need to be assigned to the same button. Task 6 is assigned to the Press Action and task 7 is assigned to the Release Action for the button, Fig 169 – Button properties shows the configuration.

Fig 172 – Button Properties With this task the on button for the bathroom is configured to run task 3 on a press and task 4 on a release. If the user holds the button down for more than 1 second then line 46 will be transmitted and the lights will go to full. If the user presses the button momentarily task 4 will run and stop task 3 before the go to full command is sent.


133

Preset Offsets Add the Preset offset command to the end of the goodnight task to set the bathroom lighting for night mode.

Fig 173 – Preset Offset Key point - The offset must be reset to 0 by a clock at Dawn or as required to return system to normal operation.

Sending Preset offset from the clock

Fig 174 – Reset day mode for toilets event


134

New Vector task New Vector provides the ability to create a task those roles through a number of functions. The functions are called in a rotating order e.g. on/off, Preset 1, Preset 2, Preset 3 etc. It works by resetting the start pointer for a task each time it runs. This allows the task to start at different points in the code each time it is run. It is commonly used to create Toggle buttons. E.g. on first press do this, on second press do something else.

Fig 175 – New vector task Key Point - This is a simple method of toggling messages and should be used sparingly. It doesn’t automatically do cross tracking which means that if 2 panels in the same Area are performing the New Vector function extra code is required to keep the panel functions synchronized. In this situation conditional tasking is the preferred option. (This is explained in a later course).

Null The null command will cause the task to stop as soon as that line in the code is reached. If the Null was omitted from this code it would only ever turn the lights off.

3 Speed fan task Now we will use the NewVector function and create a 3 speed fan control task, this task uses has 4 flags to toggle between instead of just 2 as in our original example.

Fig 176 – New vector 3 speed fan task


135

Unconditional loop task Below is an example of a task which creates an unconditional loop:

Fig 177 – Unconditional loop

Control Tasks A control task is a task that is added to a .evt file to control another task within the task engine. It may be used to cancel unconditional loops or to stop and restart a task that has been previously suspended in its operation with a ‘Delay’ message. StartTask(x) - Will start Task x within the device. CancelTask(x)or StopTask(x) - Will stop Task x instantly. PauseTask(x) - Will pause Task x at the point it has reached in its code. CancelTask and StartTask can be used together to restart a Task that is currently running.

Fig 178 – Control task examples


136

Running a task from another device It is possible to store a task on one device and have other devices on the network access that task. This is useful for saving tasking space and reduces unnecessary duplication of information on the network. To achieve this, we simply need to add a single line of code to any task we want other devices to access. In the example below, line 14 shows the start command. The start commands role is to listen on the network for messages of a certain type (an Area 200, Preset 1 message in the example below) and once received it is to execute the next line of code below.

Fig 179 – Start command Once the line has been added to the task there is one more step to complete. We need to get the device ‘calling’ the task to send out a ‘dummy’ Preset message. In the example above the message is for Area 200, Preset 1. So if say the task is meant to run from another panel, then we need to configure a button on that panel to send the dummy Preset message for Area 200.

Panic task The Panic Preset is a general Preset that can be configured in each dimmer if required. From the factory the Panic Preset is 100%. Panic would be used for security integration to combine with burglar alarm trip and emergency situations such as smoke alarm triggers. The Panic message also locks out all buttons that are configured to control the Area that the panic Preset is sent to.


137

Panic Mode Earlier we covered the use of the start command, we have added a Start command line into the example shown. In this instance, in addition to writing and adding these tasks to a device, we need to configure a dry contact input that would be connected to a 3rd party security system. The dry contact input will send the dummy Preset message when the alarm is triggered. Philips Dynalite has several device solutions available.

Fig 180 – Panic task

Unpanic mode Unpanic mode puts the system back into its pre-panic state, therefore any lights that were on before panic mode was triggered will remain on once Unpanic initiated. Note in our example that we have used a different Preset message to trigger Unpanic

Fig 181 – Unpanic task

Enabling buttons in Panic mode If a button is to ignore this message it needs to be specifically enabled by:

1. In the tab, click .

2. Change the Enable when panel disabled field to True.


138

Fig 182 – Buttons tab – Enable when panel disabled

3. Click to save the settings to the panel.

Topic 11: Conditional Tasking

139

TOPIC 11: CONDITIONAL TASKING

Topic overview This topic takes us beyond standard tasking into the realms of conditional logic. As with the previous topic, we will use real life examples to assist in the learning process.


• Explain the need for conditional tasks.

• Use 3rd party dry contact inputs to send messages onto the Dynet network.

• Implement the Panic feature.

• Create conditional toggle buttons.

• Define each panel button’s led status.

DyNet messages If a message can be transmitted onto the network and seen in the monitor window it can be recreated in a task. To do this we can apply the DyNet message command. The DyNet message uses the first 7 values from the message that is displayed in the monitor window as shown below. Each value must be preceded by 0x, which classifies the value as a hexadecimal value to the compiler. Monitor message: 1c 03 00 09 00 ff ff da Area 3 HOLD PROGRAM Preset 1 DyNet Message:

Fig 183 – DyNet string


140

Conditional task applications When tasks have to change in operation to match the current state of the home they require the use of conditional logic. The methods we will use are similar in operation to what are often referred to in programming as do-while or if-else functions.

Memory Map

DyNet Bus

@0 @1 @2 @3 @4 @5 @6 @7Receive Buffer contains last received message (Read Only)

Accumulator

Code manipulation Area.

User RAM. Storage Area. (Read/Write)

~0 ~1 ~2 ~3 ~4 ~5 ~6 ~7

~8 ~9 ~10 ~11 ~12 ~13 ~31………

X X0 1 2 3 4 5 6 Op Code

Transmit Buffer for messages to be sent onto the network (Write Only)

Inside the processor

Figure 184 - Memory map

Terminology Below is a list of the terminology that you will need to become familiar with in order to utilise conditional tasking. See the Glossary in the Appendix for a more comprehensive list of arguments and labels:

• Start(x,x,x,x,x,x,x) - Passive command that listens to the network for defined values. An x is a wild card.

• ~0 (tilde zero) - This is a reference to a tilde (~) memory location inside the panel that

holds the task. There are 64 tilde locations on a current 9 series panel (~0 to ~63).

• @3 (at three) - The @ symbol is used to refer to the receive buffer on the panel containing the task.

• LDA (argument)- load the accumulator - This is a single byte memory location where a

value can be temporarily stored when the task has to use it. Each task has its own accumulator.

• STA (argument) - store the accumulator

• CMP (argument) – compare


141

• BRZ (Label) -branch zero

• NULL (Label) - If a null is placed in the code the task will terminate as soon as it reaches this line.

See the Glossary in the Appendix for a more comprehensive list of arguments and labels.

Conditional welcome home task This task can be triggered from a button press or alternatively from a third party input such as an alarm interface. It will light the house to allow the occupant to enter the building safely as well as light the interior and exterior of the building to create a desired effect. This task could be written in a number of ways but to make it operate effectively it needs to change in operation depending on the time of day. You would only want the house to light up on your return if it was evening or night. To effect this operation we need to use a network time clock and apply conditional logic to our task. Method:

• Clock sends an Area 200 Preset 2 message at sunset to set night mode.

• Clock sends an Area 200 Preset 1 message at sunrise to set day mode.

• One task listens for the clock message and sets a flag in the panel.

• Welcome home task checks the status flag when it starts: o Day = path 1. o Night = path 2.

In our example we are using task 1 as the clock message monitoring task and task 2 as the task that runs when the welcome home is triggered. While this task looks at a specific application it can be modified to provide a huge range of functions. See example on following page:


142

Fig 185 – Conditional welcome home task


143

Configuring the time clock The process of creating events for a time clock is completed in the .evt file. Fig 186 – Time clock events shows and enabled event configured to reset the PresetOffset for the bathroom.

Fig 186 – Time clock events


144

Extractor fan run on task It is often requested and sometimes a regulatory requirement that a bathroom extractor fan runs for a specific period of time after the bathroom light is turned off. This can be a fixed function task that always runs on after the lights are turned off or it could have an override feature that allows the user to cancel the fan if it is not required. The fixed toggle function will provide multi action control from a single button. The different button press actions always following in order.

Fig 187 – Extractor fan run task


145

Extractor fan run on task version 2 If the button is pressed during the extractor fan run on it will turn the fan off and cancel the delay. On the next button press the lights will come on and the fan will start. The preferred option depends on the client’s requirements. Alternatively the user could have multiple buttons for lighting Presets and fan control. This would be useful when the fan is required during the day when the lighting is not necessary.

Fig 188 – Extractor fan run task with forced shut off


146

Button LED control We now need to consider the LED function associated with a task. Whenever a button is assigned to a task the operation of that button’s led becomes the responsibility of the task. When the LED goes on and when it goes off. Dynalite’s LED calculator allows you to create the led command line then copy it into the task at the point you want the led to change state.

To access the LED calculator, click in the EnvisionProject Task Editor. The LED will then appear as shown below:

Fig 189 – LED Calculator plug-in

To use the LED calculator, follow these steps:

1. Use the drop down menu to choose the panel type you require.

Fig 190 – LED Calculator drop down menu


147

2. Select the button you want to work on, click on it to cycle through the available choices On, Off or Leave.


4. In the .evt file, find the location in the task you need and hit Ctrl+ V.

In Fig 191 – Extractor fan run task with LED tracking below, the led on button 1 will illuminate when the light is turned on and extinguish once the extractor fan has been turned off. These messages can be used to change the state of the whole panel for applications such as illuminating the ‘on’ button once the house goes to goodnight to allow the user to see which button to press in the dark to turn the lights on. A task sent at dawn could send a Preset request to each Area and the responses would reset each panel’s LED’s to indicate the current Preset state.

Fig 191 – Extractor fan run task with LED tracking


148

Conditional Loops Some users request feedback to indicate that the extractor fan is running whilst the light is off. This can be achieved by making the buttons LED flash whilst the fan is in the run on stage. To make the button LED flash we can use a conditional loop. A conditional loop is a section of code that runs continually for a specified number of times. Loops can be achieved using a variety of programming methods, the method you choose is dependent on programming limitations or personal preference. The example below shown in Fig 191 - Extractor fan run task with conditional loop type 1 uses and additional loop task and adds a stop, start and a delay lines to the original task.

Fig 192 – Extractor fan run task with conditional loop type 1


149

The example in Fig 192 - Extractor fan run task with conditional loop type 2 uses the accumulator to control the run time of the loop. Line 80 resets the value in the accumulator so that it can be used to control the number of times the loop runs.



150

The example shown in Fig 194 - Extractor fan run task with conditional loop type 3 uses the X register to achieve a conditional loop. The X register can be thought of as another accumulator where a value can be stored.


Topic 12: Advanced Features

151

DyNet Packet Sender The DyNet packet sender is used to send messages onto the network from EnvisionProject. A number of different default messages have been loaded into the packet sender, you can also add additional messages of your own.

To access the DyNet packet sender, click in the Logical View or in the Virtual Panel.

To send a message, double click on the message you wish to send or click .

Fig 195 – DyNet Packet Sender

To create new message click and then select from the pre defined Logical and Physical packets or create a completely new message.

Fig 196 – Add new message

Enter the name you want for the message and add the packet information below.

Topic 12: Advanced Features

152

Find & Replace The find and replace function enables you to find and replace text in the Logical view. In the Logical view, click Ctrl + F to show the Find dialog box. It’s functionality is similar to the search and replace feature found in Windows.

Fig 197 – Find & Replace

Appendix

153

Tools > Settings

User Settings View

• Max application log view items – Set the maximum number of items displayed in the Application Log view.

• Max Network log view items - Set the maximum number of items displayed in the Network Log view.

• Maximum completed commands in Command Monitor….. – Set the maximum number of completed commands displayed in the Command Monitor view

• Number of files in recent file list – Set the number of recent files displayed in the File menu and in the Start Job Selector.

• Number of undo / redo items – Set the maximum number of undo / redo steps available in the undo / redo menus.

• Enable custom products – Enables custom products to be displayed in the Create Device tab.

• Enable application log debug filters – Make visible the debugging filters in the Application Log view.

Behaviour • Default fade time (Milliseconds) – Set the default fade time used in jobs • Open multiple task editor windows - Allow multiple task editor windows to be open at

the same time. • Request current preset on Area selection – A request current Preset message is sent

when selecting the Area in the Logical view. • Disable device discovery filter – Disabling the device discovery filter means the identity

of devices will only be requested when the search network window is open. • Request sign-on when device created – A request device sign on message will be sent

when a device is added to the job. • Enable memory editor – Allow use of the memory editor (use at own risk). • Show Application Log on error – When an error is detected, switch the monitor windows

to the Application Log to display error details.

Flashing • Flash on period (Milliseconds) – Set the time an area /channel / device flashes on. • Flash off period (Milliseconds) - Set the time an area /channel / device flashes off. • Flash on level (%) – Set the lighting on level for flashing. • Flash off level (%) – Set the lighting off level for flashing. • Double on flash for ballasts – Set to true to improve flashing usability for ballasts.

Motion Detector

• Sample Period (Milliseconds) – Set the polling interval for the motion sensor graph. • Sample retry ratio – Set the ratio used to poll offline sensors, set to a low interval to reduce

network traffic. • Maximum – Set the maximum range for the PIR motion detection graph. • Minimum - Set the minimum range for the PIR motion detection graph. • Duration (Minutes) – Set the time period for which the motion sensor graph displays

information.

Appendix

154

Light Control • Sample Period (Milliseconds) - Set the polling interval for the motion sensor graph. • Sample Retry Ratio - Set the ratio used to poll offline sensors, set to a low interval to

reduce network traffic. • Maximum - Set the maximum range for the light level detection graph. • Minimum - Set the minimum range for the light level detection graph. • Duration (Minutes) - Set the time period for which the motion sensor graph displays

information. • PE Band Overlap – Allows for overlapping band settings for open loop light level control

configuration.

System Settings Auto Save

• Enabled – Turn on /off the auto save feature. • Interval (Minutes) – Set how often EnvisionProject auto saves an open job.

Comms Engine

• Number of Concurrent Commands – Set the number of commands that can be completed simultaneously. The lower the number the faster individual commands are completed.

Application Log

Application Logging • Write messages to file – Set to true to save message to log file. • Log message type – Select the types of messages that are logged. • Maximum file size – Set the logs maximum size.

Log File Backups • Backup removal system – Select the type of removal for backups, Maximum days or

Maximum size. • Maximum backup days –Set the maximum number of days a backup will exist before it is

automatically removed. • Maximum backup size – Set the maximum size for a backup file before it is

automatically removed.

Network Provider Network Provider Logging

• Write packets to file – Logs network provider traffic. • Log bad packets – Set to enable log to record bad packets. • Maximum file size (KB) – Set maximum file size for log.

Logging File Backups

• Backup removal system - Select the type of removal for backups, Maximum days or Maximum size.

• Maximum backup days - Set the maximum number of days a backup will exist before it is automatically removed.

• Maximum backup size - Set the maximum size for a backup file before it is automatically removed.

Appendix

155

Job Settings Behaviour

• Number of initial presets created for each Area – Set the default number of Presets available for each Area.

Job File • Save discovered devices – Set to true to save discovered devices to job file.

Trouble shooting We have provided some tips for you to pursue in the event there is problem during the commissioning process. The topic of troubleshooting is quite large and this section is not designed to be a comprehensive guide to troubleshooting but more a group of points to get you started.

Checking for offline devices Checking to see if a device is online can help diagnose device issues as well as locating breaks in the network. To check to see if a device is online:

1. In the Network view, right click on the device you wish to check.

2. Select Send Sign-On.

Fig 198 – Device Right-Click menu

3. Check the Status column in the Network view, if this appears the device is offline. This process can be useful for checking single devices but sometimes it would be more convenient

Appendix

156

Network Log This screen logs network traffic and is often the first place to check if a device doesn’t behave correctly. i.e. if a button on a panel is not working correctly check to see if the message you are expecting can be seen in the network log.

Application Log The application log records the type, date, time and message. It is meant to record all actions by the EnvisionProject, this may include network traffic but also records information related to EnvisionProject such as network connection.

Command Monitor The command monitor shows the status of messages on the network, and a more detailed description of the message than can be found in the other windows.

Appendix

Glossary of terms Start(0xlc,200,x,x,x,x,0xff) - A passive command that listens to the network for defined values. An x is a wild card. In the example we are looking for any message on the network that starts with 1c, ends with ff and is sent to Area 200. ~0 (Tilde zero) – This is a reference to a tilde (~) memory location inside the panel that holds the task. There are 64 such memory locations in a 9 series Universal Panel and they are referenced as ~0 to ~63. Each tilde memory location can hold one byte, which means any number from 0 to 255. @3 (At three) – The @ symbol is used to refer to the receive buffer on the panel containing the task. As every message is 7 bytes long plus the checksum (last value and never included), the receive buffer locations are referenced as @0 to @6. Therefore @3 is the 4th value in the received message and in our example is the value that is used as the day or night flag. LDA Argument (Load the accumulator) – Every task has its own working Area referred to as the accumulator. This is a single byte memory location where a value can be temporarily stored when the task has to use it. The command LDA will copy a value from the argument into the accumulator so the task can use it. The argument can be either a memory location such as @x or ~x or it can be an absolute number from 0-255. If an absolute number is used it is referred to by the symbol #. E.g. LDA#2 will put the value of 2 into the accumulator. STA Argument (Store the accumulator) – This command will copy whatever value is currently in the accumulator and paste it into the tilde memory location referred to in the argument. CMP Argument (Compare) – This command will compare the value currently stored in the accumulator with the argument. The argument can be either a defined value such as #10 or it can be a reference to a tilde memory location. The result of the comparison is used to make decisions in the task. The CMP comparison subtracts the value of its argument from the value in the accumulator. While the result of the comparison is stored in the panel’s memory it does not change the value in the accumulator.

Appendix

157

BRZ Label (Branch zero) – If the result of the CMP comparison is zero then both the accumulator and the argument values must be the same (accumulator = 5 and argument = #5. 5-5=0). When this is the case the task will branch (jump) to the label referenced in the BRZ command. Label – This is a marker in the code. It has no functional operation other than being a pointer that the code can refer to. A label has 4 rules:

• It is case sensitive. When it is referenced in a command such as BRZ, ‘Day’ and ‘day’ is not the same thing.

• It must start with a letter. ‘FirstMarker’ is fine but ‘1stMarker’ is not. • It cannot contain any gaps. ‘First_Marker’ is fine but ‘First Marker’ is not. • A colon is required for the label itself but not for its reference. The label is FirstMarker: but

the reference is: BRZ FirstMarker. Null - Every task runs from top to bottom unless a branch command causes it to deviate from this course. If a null is placed in the code the task will terminate as soon as it reaches this line.

Hot Keys

158

Hot keys Alt + 1 Logical view Alt + 2 Network view Alt + 5 Commissioning Assistant Alt + 6 Application log Alt + 7 Network log Alt + 8 Command monitor Alt + A Change Area Alt + B Change box number Alt + C Channel Editor tab (When a load controller is highlighted in the Network view) Alt + E Edit Memory Alt + F Factory set Alt + W Open wizard Alt + T Open task editor Alt + P Buttons tabs (Panels) Preset editor (Load controller) Alt + X Export to file Alt + R Set Realtime Clock... Alt + F4 Exit Ctrl+1-8 Send a Preset message Ctrl + A Insert new Area Ctrl + C Copy Ctrl + H Insert new Logical Channel Ctrl + E Insert new folder Ctrl + F Find Ctrl + D Add new device Ctrl + L Load devices from network Ctrl + I Import devices from file Ctrl + R Insert Preset Ctrl +I Open file Ctrl + N New Ctrl + O Open

Hot Keys

159

Ctrl + L Open Load Devices from Network dialog Ctrl + V Paste Ctrl + Y Redo Ctrl + X Cut Ctrl + F10 Open DyNet Sender F2 Rename F3 Find Next Shift +F3 Find Previous F4 Request device information F5 Send Reset F6 Send Sign on F7 Flash Device\Channel F8 Toggle Network/Logical view F11 Load data from device F12 Store data to device Home Top of Network/Logical view End Bottom of Network/Logical view

DLight 2 to EnvisionProject Translation EnvisionProject DLight 2 Connection Settings Comms Main Editor Properties Edit dialog / Configure dialog Main Editor System Supervisor Window Network View Physical View Network Log Monitor Window Search Devices Config Search List Save to Device Dump Task editor Crimson Editor

Documents

Envision Project Training Guide - 1.0