Setup Individual DALI Inputs
- 1 How does it work?
- 2 Give the DALI devices an ID
- 3 How to use DALI
How does it work?
When using individual DALI inputs, you want to link a DALI input like a motion sensor (with a DALI ID/eID) with an OpenMotics system output to allow an action when movement is detected. 16 DALI inputs per CAN Control module can be programmed.
a DALI network may use both IDs and eIDs to identify (input) objects:
- Lunatone motion sensors use eIDs (0-63)
- Helvar motion sensors use IDs (0-63)
On the same DALI network IDs and eIDs can coexist.
Important note: OpenMotics uses DALI IDs in a range of 0-63 conform to the DALI specifications. Some vendors (like Helvar's Digidim Toolbox) display in their software the DALI IDs in a range of 1-64 so those IDs have to be deducted by 1!
To do so, first the DALI IDs will be generated by using the DALI Cockpit software (for Lunatone motion sensors) or the Digidim Toolbox (for Helvar motion sensors). Secondly, the found DALI IDs and eIDs will be entered in the eeprom of the Gateway module. Once these are entered, the Gateway will synchronize those eeprom pages with the CAN Control module(s). The CAN Control module will detect new inputs and will generate new Input modules that will be added when the next discovery mode is done. After this, the DALI input will act/react as any other input in the system.
The DALI ID's are entered in the following pages:
Page 100 : Contains all IDs/eIDs for the first CAN Control that’s been added to the Gateway Page 101 : Contains all IDs/eIDs for the second CAN Control that’s been added to the Gateway Page 102 : Contains all IDs/eIDs for the third CAN Control that’s been added to the Gateway Page 103 : Contains all IDs/eIDs for the fourth CAN Control that’s been added to the Gateway
see Memory Model for more details.
In every one of the above eeprom pages, the structure is as follows:
- Byte 0-63 is used to program a DALI Output with switch only capacity (like a relay)
- Byte 64-127 is used to program a DALI Output with dim functionality
- Byte 128-143 is used to program a DALI Input (Lunatone/Helvar Motion sensor)
When a DALI Input is linked to a system output, it will act as a normal input and you can use all instructions which are applicable on any system input.
Give the DALI devices an ID
To start the Individual DALI Input setup, we first will start assigning the DALI ID's by using the Lunatone Cockpit software.
To do that, the Lunatone SCI (Connector A) must be connected to an USB-RS232 convertor which is connected to a PC with Lunatone Cockpit software installed. This software can be downloaded free of charge from the Lunatone website.
Start the Cockpit software
Go to the menu item "DALI bus - Bus interface" and set the right COM port (see Device Manager of your windows machine to find the right COM port) of your connected USB-RS232 convertor.
Assign DALI IDs in a new installation
When performing a fresh installation where no DALI IDs are assigned yet, follow the below steps
Go to the menu item "DALI bus - Addressing" and select "Complete new installation", press next.
Make sure your DALI power supply is connected otherwise no devices will be found.
Once all devices are found, note the eIDs (Lunatone) and the IDs (Helvar) of the found motion sensors that have been found. Please note that on a mixed network (Helvar and Lunatone), the Cockpit software will indicate the found Helvar motion sensors as "unknown devices". The Lunatone sensors can be configured using Lunatone Cockpit software, the Helvar sensors must be configured using the Helvar software so we advice to use 1 brand to remain simplicity in initial setup.
Assign DALI ID/eID's in an existing DALI installation
When performing an installation where DALI ID's are already assigned on that particular DALI network, follow the below steps
Go to the menu item "DALI bus - Addressing" and select "System extension", press next.
Once all devices are found, note the IDs/eIDs that have been given to the individual devices.
Configuring DALI Inputs in Lunatone or Helvar software
The following steps are needed to enable DALI inputs:
- Use Lunatone Cockpit (for Lunatone motion sensors) or Helvar software (for Helvar motion sensors) to assign DALI IDs/eIDs to the used DALI inputs (motion sensors). Please note the DALI ID/eID's that the software has found and test the individual Dali inputs (for example activate the test led so you know which motion sensor is linked to which Dali ID).
- When configuring a motion sensor as input, the "Event Message Mode" needs to be configured in other words, when a motion is detected, an event message will be posted on the DALI Bus. The DALI address that is used in the below configuration is the Destination address of the event message.
- For ease of use, please configure the destination address to be the same as device DALI address that you're configuring.
- For Lunatone devices, set in the Tab "Motion Sensor", "Destination address" for 1: "None", 2:, 3: and 4: also on "none".
Find the right CAN Control
If you’ve more than 1 CAN Control module, you can use the list below to find the right order.
Let’s first do the discovery of your modules, if this is already done, this is fine but just do the below also:
Go to maintenance mode, “connect” and perform following command:
module discover start
Push the button of every CAN Control module. If none of the CAN Control modules are initialized yet, the first init button on the CAN Control you push is the first module, the second init button is the second module etc…
Note down the “C” ID’s the module is returning for which DALI functionality is used and keep track from which module these are. Once this is done, return to normal mode by using following instruction:
module discover stop
Note: Once a new CAN Control module is added, it can take a while before the full eeprom is synchronized so you’ll get some errors on the bus which is normal.
Next, check the order of the CAN Control modules for which DALI functionality is used by using following instruction:
In the input section of the error list, you’ll see all your input modules including all your CAN controls. You also see the module type (like “I” for input, “T” for temperature and “C” for CAN control). Check the order so you know which eeprom page you must use for your DALI modules.
Page 100 : Contains all IDs/eIDs for the first CAN Control module in the list or that’s been added to the Gateway module Page 101 : Contains all IDs/eIDs for the second CAN Control module in the list or that’s been added to the Gateway module Page 102 : Contains all IDs/eIDs for the third CAN Control module in the list or that’s been added to the Gateway module Page 103 : Contains all IDs/eIDs for the fourth CAN Control module in the list or that’s been added to the Gateway module
Program the DALI IDs
Now you know in which page (100, 101, 102 or 103) you have to program your Dali IDs/eIDs, you start programming in the correct page your DALI devices, below is an example:
eeprom write 101 128 5 ;as an example, our DALI bus is connected to our second CAN Control and we’re programming DALI eID5 (Lunatone Motion Sensor) eeprom write 101 129 6 ;DALI eID6 (Lunatone motion sensor) ... eeprom write 101 130 66 ;DALI ID2 (Helvar motion sensor -> 66-64=2) eeprom write 101 131 71 ;DALI ID7 (Helvar motion sensor -> 71-64=7) WARNING: The IDs shown above for the Helvar motion sensors are as displayed in the Lunatone software (0 based). Helvar motion sensor with ID = 2 will be shown as ID = 3 in the Helvar software! …
Note: As you can see in the above example, the eeprom address (for example 101 128) is not different for eIDs (Lunatone) or IDs (Helvar). The data byte that is written is however different:
- eIDs (Lunatone) databyte is the following: Databyte = eID so in other words when you want to program eID 23 you use databyte 23.
- IDs (Helvar) databyte is the following: Databyte = ID+64 so in other words when you want to program ID 10 you use databyte 74. Note that this is the ID as shown in the Lunatone software, NOT the Helvar software!
The second step is to synchronize the DALI ID pages. If you know which DALI ID pages (100, 101, 102 and/or 103) you have to synchronize, you can immediately synchronize the right page, otherwise start at 100 and let the system do the rest (automatically, page 101, 102 and 103 will also be done).
sync page 101
If you want to follow where you stand in synchronization, you can follow the sync process by using instruction
sync debug on
This will display the page and byte that has been synchronized. To exit the debug mode, please use instruction
sync debug off
After the sync is done, apply the instruction
Now the necessary virtual inputs are created in the CAN Control module and must be added to the Gateway module. Since were are programming, in our example, page 101 we know we are using the second CAN Control module:
discover can control 2 ; Add all the modules of the second CAN control
All the modules (existing and new) will now appear. After this is done, exist the discovery mode:
module discover stop
You will now receive errors on the newly created virtual inputs. This is normal since input pages must be synchronized now.
Note: If you have more than 1 CAN Control module with DALI devices connected, you can have the same DALI IDs in both CAN Control modules.
The DALI IDs/eIDs as well as the necessary virtual input modules should be synchronized before it will properly work so a copy of the Master eeprom must be copied into the CAN Control modules. Before everything is synchronized, multiple errors can occur and this can be ignored. Since the whole synchronization process can take a while before this is done, you can speed up things by using the following procedure in maintenance mode:
Let us first synchronize the input modules:
sync page 1 ;sync the first input module
Wait 15 seconds (since only the first 5 bytes must be synchronized)
sync page 2 ;sync the second input module
Wait 15 seconds
sync page 3 ;sync the third input module …
Up to the last input module. By using the instruction
you know how many input modules that you have.
Please note that all input modules (virtual and non virtual) must be synchronized for the CAN Control and DALI functionality to properly work.
Note: The synchronization is a process that continues in the background so Master and CAN control are synchronizing all the time.
How to use DALI
Once the appropriate pages are synchronized, you can start using the DALI modules. The DALI modules will act like normal modules so all instructions that exist for normal input modules (except for indicate instructions) can be used.
In maintenance, the DALI modules can be easily found since those input modules are indicated by the letter “C” in the last column.
To find the right input module, use following instruction
input debug on
Generate some movement on the sensor you want to find.
In the portal, the DALI input modules can be programmed, linked to outputs, set actions, etc.