Dynalite® Pro Interface

(c) 2009-2015 My Device.

www.mydevice.com.au

This driver helps to control the Dynalite lighting control system. It will allow you to control the system as well as providing 2-way feedback via variables and events.

Note:

Integration Designer only allows a maximum of 4 parameters to be passed to a function. This has meant that several functions need to use a default value for the JOIN parameter. This has been set to 0xff (255). If you require a different JOIN value (and the function doesn't allow you to change it) you can use the Send Dynet Message function.

Please report any bugs found to bugs@mydevice.com.au. Include driver version number and steps to reproduce the issue where possible.

Driver Configuration Settings:

Connection:

Connection Type - Choose from:

Network (EnvisionGateway) - see comments below

XP Serial Port (using a DTK622-232 or similar)

Global Cache (using a DTK622-232 or similar)

Network (100BT)

Network (Slave)

Based on the connection setting above, fill out one (1) of the connection settings below (the non-selected settings will be hidden).

Network Settings:

Address - This is the IP address of the Dynalite network interface.

Port - This should normally be left as 9998 for 100BT or 50000 for EnvisionGateway unless the Dynalite commissioner has indicated otherwise.

Note: if you are using an EnvisionGateway you must configure the EG as a "Dynet Ethernet Access Point".

Serial Settings:

Serial Port - Set the serial port the Dynalite DTK622-232 is connected to. Please note: this driver will NOT work with any other model of dynalite serial interface.

Baud Rate - This should normally be left as 9600 unless the Dynalite commissioner has indicated otherwise.

Global Cache Settings:

IP Address - This is the IP address of the GC100/iTach device.

Serial Port - Set the serial port the Dynalite DTK622-232 is connected to on the Global Cache unit.

Global Settings:

Double Send - Check this box to have the driver send every message twice. This should only be used in high noise environments if messages are failing.

Functions:

Preset Recall Commands:

Set Area to Preset

This function sends a preset to an area.

Area : Destination area (0 - 255)

Preset : Preset to send (1 - 255)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Join : Join byte, normally 0xff (255)

Set Area Range to Preset

This function sends a preset to a range of areas. Useful if you want to for example turn all the lights out for the entire building. This function will send a preset message to all areas from <Start Area> to <End Area> inclusively. Take care to always ensure the <End Area> is greater than the <Start Area>. Join is set to 0xff.

Start Area : Destination area (0 - 255)

End Area : Destination area (0 - 255)

Preset : Preset to send (1 - 255)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Set Area to Panic

This sets an area to panic mode. This can be useful to lock panels.

Area : Destination area (0 - 255)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Join : Join byte, normally 0xff (255)

Set Area to Unpanic

This sets an area back to normal mode. This can be useful to unlock panels.

Area : Destination area (0 - 255)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Join : Join byte, normally 0xff (255)

Set Channel to Preset

This function sets an area channel to a preset.

Assumes a join value of 0xff.

Area : Destination area (0 - 255)

Channel : Channel to set (1 - 255)

Preset : Preset to send (1 - 255)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Level Recall Commands:

Ramp Channel to Level

This function ramps an area channel to a level.

Assumes a join value of 0xff.

Area : Destination area (0 - 255)

Channel : Channel to set (1 - 255)

Level : Percentage (0 - 100)

Fade : The number of 0.02 increments the preset should take to complete. For example, a value of 100 = 0.02 x 100 = 2 seconds.

Stop Fade of Channel

This function stops a ramp.

Area : Destination area (0 - 255)

Channel : Channel to set (1 - 255)

Join : Join byte, normally 0xff (255)

Request Channel Level

This function requests the current level of a channel.

Area : Destination area (0 - 255)

Channel : Channel to set (1 - 255)

Join : Join byte, normally 0xff (255)

Area Status Commands:

Request Current Preset

This function requests the current preset for an area.

Area : Destination area (0 - 255)

Join : Join byte, normally 0xff (255)

Motion Detection:

Occupancy Detection

This function suspends or resumes motion detection for an area/channel.

Area : Destination area (0 - 255)

Channel : Channel to set (1 - 255)

Detection : Suspend/Resume

Join : Join byte, normally 0xff (255)

Events:

Custom Event Trigger

This function allows you to trigger a macro when a specified area goes to a predetermined preset.

For example you could make a remote flip to the cinema page when the light switch was hit as the owner enters the room.

Area : Destination area (0 - 255)

Preset : Preset to send (1 - 255)

Event ID: Event to assign the trigger to (1 - 200)

To create an event trigger follow these steps:

1) Create a new startup macro. That is, a system macro which gets invoked at system startup.

2) For each custom trigger, add a call to "Custom Event Trigger(area,preset,id)" in the startup macro.

Where area = The area you wish to monitor;

preset = the preset that will trigger the event;

id = the custom event the will be triggered.

3) In the events tab of your XP8 add a driver event for each custom trigger.

ie. When 'Custom Event 1' happens on '(Dynalite Interface)' run macro [2] do something.

Physical:

Reboot Device

This function resets a device.

Device: Select the type of device to reboot from the dropdown.

Box: This is the box number of the device. This is usually the last 2 digits of the serial number sticker, or can be found in DLight2 when the device resets.

Start Task

This function starts a task within a device.

Device: Select the type of device from the dropdown.

Box: This is the box number of the device. This is usually the last 2 digits of the serial number sticker, or can be found in DLight2 when the device resets.

Task: Task number to start (1 - 255)

Stop Task

This function stops a task within a device.

Device: Select the type of device from the dropdown.

Box: This is the box number of the device. This is usually the last 2 digits of the serial number sticker, or can be found in DLight2 when the device resets.

Task: Task number to stop (1 - 255)

Pause Task

This function pauses an already running task within a device. To resume the task send the Start Task message.

Device: Select the type of device from the dropdown.

Box: This is the box number of the device. This is usually the last 2 digits of the serial number sticker, or can be found in DLight2 when the device resets.

Task: Task number to pause (1 - 255)

Request Physical State

This function requests the current physical value from a device. This could be the current temperature, light level etc.

Device: Select the type of device from the dropdown.

Box: This is the box number of the device. This is usually the last 2 digits of the serial number sticker, or can be found in DLight2 when the device resets.

Property: Select the type of value you wish to query from the dropdown. Whilst the protocol allows for many properties, in practise I have only seen Lux and Temperature made available.

Store reply in variable: A total of 10 variables are available to store physical values. Be sure to pick a unique id to ensure you don't get unpredictable results.

Network Commands:

Send Dynet Message

This function allows you to send a custom message to the Dynalite network.

Message: A 7 byte hex string indicating the message to be sent. The CRC is automatically appended.

The message string may be in any one of the following formats:

b1:b2:b3:b4:b5:b6:b7

b1,b2,b3,b4,b5,b6,b7

b1b2b3b4b5b6b7

Where bn is a 2 digit hex representation of a byte. Accepted characters are A-F, a-f, 0-9.

Examples:

1c,01,02,03,04,0a,d8

5c:01:02:03:04:05:06

1C2D931249A0CC