Dali AIO

From OpenMotics
Jump to navigation Jump to search

Introduction

The AIO Dali implementation supports Dali inputs and outputs.

Following Dali Outputs are supported:

  • Relay outputs
  • Dim controlled outputs
  • Led drivers

Following Dali Inputs are supported:

  • Lunatone Motion sensors
  • Helvar Motion sensors

For Lunatone Motion sensors, following additional items are supported:

  • Temperature measurement
  • LUX measurement

Hardware

The needed Hardware to enable Dali is the following:

  • Dali Power Supply (Lunatone Dali PS)
  • Dali RS232 convertor (Lunatone Dali SCI RS232)

Configuration

Dali Output configuration

The following steps are needed to enable Dali outputs:

  • Use Lunatone Cockpit or another Dali software to assign Dali ID's to the used Dali outputs. Please note the Dali ID's that the software has found and test the individual Dali outputs. Keep track of the dimmed and non-dimmed outputs so they can be linked to the correct type of outputs. In this software, you will also created the necessary groups.
  • A Dali output will be linked to a system (AIO) output. Typically, a virtual output module will be created. Depending on the type of modules found (dimmed and/or non-dimmed) and the number of Dali ID's, more virtual modules must be created.
    • First perform the CLI instruction "output number modules read" to know what and how many output modules that exist. Let's assume in this example that 3 output modules already exist.
    • With the instruction "basic action activate 201 3 111 1 0 0" will create a virtual output ("o"=111) module on position 3 (first position is 0) with ID 111.1.0.0. This is the first module created in this example. See Action Types AIO for a list of all Basic Actions.
    • With the instruction "basic action activate 201 4 100 1 0 1" will create a virtual dimmer ("d"=100) module on position 4 (first position is 0) with ID 100.1.0.1. This is the second module created in this example.
    • Now the 2 additional modules are written on position 3 and 4 so we have 5 modules (0-4) in total. To activate these module, the number of activate output modules must be changed.
    • With the instruction "output number modules write 5" will set the right number of output modules and will activate our virtual output and dimmer module.
    • With the instruction "error list", you must see all modules including the new ones that have been created.
    • Please note that Openmotics uses Dali ID's in a range of 0-63 conform to the Dali specifications. Some vendors (like Helvar) are displaying the Dali ID's in a range of 1-64 so those ID's have to be deducted by 1.
  • Once the modules have been added, we must link the virtual outputs with the Dali outputs.
  • If you perform the instruction "output list", you'll see the full list of existing outputs. Our newly created outputs in our example in this list will be output 24 till 39 (output 24-31 -> Normal output, output 32-39 -> Dimmed output).
  • Let's assume that we have 2 normal Dali outputs (with Dali ID 0 and 5) and 2 dimmable Dali outputs (with Dali ID 7 and 12). The normal outputs will be linked with the virtual output module, the dimmable outputs will be linked with the virtual dimmable outputs.
    • With the instruction "basic action activate 21 20 24 0" will link normal (virtual) output 24 with Dali ID 0.
    • With the instruction "basic action activate 21 20 25 5" will link normal (virtual) output 25 with Dali ID 5.
    • With the instruction "basic action activate 21 20 32 7" will link dimmable (virtual) output 32 with Dali ID 7.
    • With the instruction "basic action activate 21 20 33 12" will link dimmable (virtual) output 33 with Dali ID 12.
    • With the above instructions, we've linked the virtual outputs with the Dali outputs.
    • With the instruction "output list", you're able to see which outputs are linked to which Dali ID's
  • Now, for example, when you switch an output on by using CLI instruction "output on 25", the virtual output will be switched on as well as the Dali output 5.
  • It's also possible to link Dali groups to virtual outputs:
    • Let's assume that you've used Lunatone cockpit to link Dali ID 0 and 5 to Dali group 2 in other words, Dali group 2 can switch off or on the full group in 1 go so both outputs will be switched off or on.
    • Let's link virtual output 26 to group 2.
    • With the instruction "basic action activate 21 20 26 66" will link virtual output 26 with Dali Group 2. All possible Dali ID's have a range from 0 to 63, ID's above 63 are groups in other words 64=Dali Group 0, 65=Dali Group 1, 66=Dali Group 2 etc
  • Now, for example, when you switch an output on by using CLI instruction "output on 26", the virtual output will be switched on as well as the Dali output 0 and 5.

Dali Input configuration

The following steps are needed to enable Dali inputs:

  • Use Lunatone Cockpit or another Dali software to assign Dali ID's to the used Dali inputs (motion sensors). Please note the Dali ID'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).
    • Please be aware that Dali is not specific about input devices so each vendor has its own implementation. For the moment, we support Lunatone (each input device will have Dali eID) and Helvar (each input device will have a Dali ID) input devices.
    • 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 which will be read and decoded by the AIO processor. 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.
    • Please also note that the Dali ID's displayed in the Lunatone software is different than the Dali ID's displayed in the Helvar software. In the Lunatone software, ID 0-63 has been used while the Helvar software displays the Dali ID's in a range of 1-64. So to avoid confusion, the Dali ID's used in the Openmotics implementation is 0-63 so when using the Helvar software, please deduct the found ID's by 1.
  • A Dali input will be linked to a system (AIO) input. Typically, a virtual input module will be created. Depending on the number of input Dali ID's/eID's, more virtual modules must be created.
    • First perform the CLI instruction "input number modules read" to know what and how many input modules that exist. Let's assume in this example that 3 input modules already exist.
    • With the instruction "basic action activate 202 3 105 2 0 0" will create a virtual input ("i"=105) module at position 3 (first position is 0) with ID 105.2.0.0. This is the first module created in this example. See Action Types AIO for a list of all Basic Actions.
    • Now 1 additional input module is written on position 3 so we have 4 input modules (0-3) in total. To activate these module, the number of active input modules must be changed.
    • With the instruction "input number modules write 4" will set the right number of input modules and will activate our virtual input module.
    • With the instruction "error list", you must see all modules including the new ones that have been created.
  • Once the modules have been added, we must link the virtual inputs with the Dali inputs.
  • If you perform the instruction "input list", you'll see the full list of existing inputs. Our newly created inputs in our example in this list will be input 24 till 31.
  • Let's assume that we have 2 Lunatone Dali motion sensors (with Dali eID 3 and 4) and 2 Helvar Dali motion sensors (with Dali ID 2 and 3). The normal inputs will be linked with the virtual input module. You have probably see that ID and eID are part of a different range, this is why ID 2 and eID2 can exist in the same Dali network.
    • With the instruction "basic action activate 21 21 24 3" will link virtual input 24 with Dali eID 3 (0-63 is reserved for eID, 64-127 is reserved for ID)..
    • With the instruction "basic action activate 21 21 25 4" will link virtual input 25 with Dali eID 4.
    • With the instruction "basic action activate 21 21 26 66" will link virtual input 26 with Dali ID 2.
    • With the instruction "basic action activate 21 21 27 67" will link virtual input 27 with Dali ID 3.
    • With the above instructions, we've linked the virtual inputs with the Dali inputs.
    • With the instruction "input list", you're able to see which inputs are linked to which Dali ID's
  • Once the above is done, a virtual input is linked with a Dali motion sensor. Please note that, once a motion is detected, the virtual input is pressed and immediately released. The virtual input can now be linked to any Basic Action.

Dali Sensor configuration

The following steps are needed to enable Dali sensors:

  • Use Lunatone Cockpit or another Dali software to assign Dali ID's to the used Dali sensors (motion sensors). Please note the Dali ID's that the software has found and test the individual Dali sensors (for example activate the test led so you know which motion sensor is linked to which Dali ID).
    • Please be aware that Dali is not specific about sensor devices so each vendor has it's own implementation. For the moment, we only support Lunatone as sensor devices.
  • A Dali sensor will be linked to a system (AIO) sensor. Typically, a virtual sensor module will be created. Depending on the number of sensor Dali eID's, more virtual modules must be created.
    • First perform the CLI instruction "sensor number modules read" to know what and how many sensor modules that exist. Let's assume in this example that 3 sensor modules already exist.
    • With the instruction "basic action activate 203 3 115 3 0 0" will create a virtual sensor ("s"=115) module at position 3 (first position is 0) with ID 115.3.0.0. This is the first module created in this example. See Action Types AIO for a list of all Basic Actions.
    • Now 1 additional sensor module is written on position 3 so we have 4 sensor modules (0-3) in total. To activate these module, the number of active sensor modules must be changed.
    • With the instruction "sensor number modules write 4" will set the right number of sensor modules and will activate our virtual sensor module.
    • With the instruction "error list", you must see all modules including the new ones that have been created.
  • Once the modules have been added, we must link the virtual sensors with the Dali sensors.
  • If you perform the instruction "sensor list", you'll see the full list of existing sensors. Our newly created sensors in our example in this list will be sensor 24 till 31.
  • Let's assume that we have 2 Lunatone Dali motion sensors (with Dali eID 3 and 4) with integrated temperature and lux measurement.
    • With the instruction "basic action activate 21 22 24 3" will link virtual sensor 24 with Dali eID 3 (0-63 is reserved for eID, 64-127 is reserved for ID)..
    • With the instruction "basic action activate 21 22 25 4" will link virtual sensor 25 with Dali eID 4.
    • With the above instructions, we've linked the virtual sensors with the Dali sensors.
    • With the instruction "sensor list", you're able to see which sensors are linked to which Dali ID's
  • Once the above is done, a virtual sensor is linked with a Dali motion sensor. Please note that once a temperature or lux sensor is Linked with a virtual system sensor, the values will be updated every 10 seconds.