e:cue Knowledge Base - DALI-2 Movement and Presence sensor settings and Sympholight configuration

DALI-2 Movement and Presence sensor:

Timer	Time	abbrev	description
Repeat timer	report time	t_report	When the repeat event is set, this timer defines, when the next event is sent at the latest.
Hold timer	hold time	t_hold	A hold time t_hold is only considered, when the sensor is a movement sensor. It defines the time that is needed without motion, after that the sensor switches back from occupied to vacant.
Deadtime timer	dead time	t_deadtime	The time, an instance has to wait between sending one event after another.
-	switching time	t_switch	The switching time defines the duration in the Sympholight workflow that shall be started by the sensor.
-	trigger time	t_trigger	The trigger time of the Presence Sensor block in the workflow.

General information

For DALI input devices it is not allowed to send multiple events in one transaction. So different events are fired with the interval t_deadtime. It could make sense to keep this as short as possible and it makes sense use as few event types as necessary.
You will have to switch on or off events and set the sensor timer in the Properties view of the selected "Virtual Device" in the Setup tab.

Standard Setup

Usually the user wants to be free in decision, how to handle the motion or occupancy events.

Now the "DALI Presence Sensor" block in the workflow has also a trigger time. This trigger may not interfere with the logic behind. Especially when you have more than one presence sensor that detect motion for the same group of fixtures it makes sense to use the "DALI Presence Sensor" block only as a trigger block and not its timer functionality.

- Then keep the default for the selected events "Occupied Event" and "Movement Event".

- The "Report Timer" is not used and does not need to be changed.
- The "Hold Timer" t_hold needs to be set to half to 2/3 of the shortest switching time t_switch .

- Set the t_trigger to 1s and use only the "Motion Start" event out port of the "DALI Presence Sensor" block.

- Build the timer with the available workflow logic instead, here "Single Delay" or "Multi Delay" blocks.

Alternative Setup

With the following setups you can use movement or true presence sensors. With using the "Report Timer" we ensure periodic updates of the sensor state, but raise the traffic on the DALI bus. With the used formulas we assure, that the DALI bus is not flooded, especially when using more than one sensor on the line.
- Here use the "Occupied Event", "Movement Event" and "Report Event".

Movement Sensor

A true presence sensor does not have a hold time, so the following recommendation is for movement sensors only.

Report time t_report and hold time t_hold are the same and need to be set to half to 2/3 of the shortest switching time t_switch.
(t_hold = t_report = t_switch * ²/₃.. ²/₄)
The "DALI Presence Sensor" block trigger time t_trigger has to be set to half the report time.
(t_trigger = t_report / 2 = t_switch * ¹/₃.. ¹/₄ )

True Presence Sensor

A true presence sensor does not have a hold time, so this does not need to be considered here.

Report time t_report needs to be set to half to 2/3 of the shortest switching time t_switch.
(t_report = t_switch * ²/₃.. ²/₄)
The "DALI Presence Sensor" block trigger time t_trigger has to be set to half the report time.
(t_trigger = t_report / 2 = t_switch * ¹/₃.. ¹/₄ )

Example: The shortest duration, after which the light shall switch, is 300s.
- Then a possible trigger time is 100s.
- Then a possible report time and hold time are 150s.
=> only every 150s one or two evens are sent over the DALI bus.

Alternative Line Setup

If you want to use both, movement and presence detection, you will have to use the "DALI Presence Sensor Line" block.
- Set the line, address and instance, then you can react to the "Occupied Event" and "Movement Event".
- With a true presence sensor it could make sense to switch on the "Vacant Event" and "No Movement Event".
Try out, which of the setups above will fit best.