Introduction
IEC 62386-303 describes DALI control devices that are defined as occupancy sensors.
DALI control devices according to IEC 62386-303 correspond to instance type 3. The type of an instance can be queried with the function block FB_DALI103QueryInstanceType.
Input value
The current state (inputValue) of the light sensor can be queried via the function block FB_DALI103QueryInputValue.
The variable can assume four values:
inputValue | Occupancy | Movement |
|---|---|---|
16#00 | No | No |
16#55 | No | Yes |
16#AA | Yes | No |
16#FF | Yes | Yes |
For simplification the graphics below only show whether an area is occupied or vacant.
Timer
IEC 62386-303 defines specific timers with which the sending of the different events can be influenced.
The respective time is calculated from
Time | Multiplier | Preset value of the multiplier | Tincr Incremental value | Tdefault Default value | Tmin lowest possible set value | Tmax highest possible set value |
|---|---|---|---|---|---|---|
Tdeadtime | tDeadtime | 2 | 50 ms | 100 ms | 0 s | 12.75 s |
Thold | tHold | 90 | 10 s | 15 min | 1 s | 42 min 20 s |
Treport | tReport | 20 | 1 s | 20 s | 1 s | 4 min 15 s |
 | Set the times so that as few events as possible are sent. If too many events are sent, this can have a negative effect on the behavior of the application. |
Event filter
DALI control devices are capable of sending different events. The event filter consists of an 8-bit value, where each individual bit defines whether an event is blocked or released. The event is released if the corresponding bit is set, otherwise it is blocked.
The function block FB_DALI103QueryEventFilter can be used to read the value of the event filter; the function block FB_DALI103SetEventFilter can be used to write to it.
The event filter (see eventFilter) must be configured accordingly in order to trigger time-controlled events.
Bit | Event | Description |
|---|---|---|
0 | Occupied | Occupancy detection |
1 | Vacant | Area vacant detection |
2 | Repeat | Event repeat |
3 | Movement | Movement detection |
4 | No Movement | No Movement detection |
5 | - | reserved |
6 | - | reserved |
7 | - | reserved |
| Release only those events that you need for the application. If too many events are sent, this can have a negative effect on the behavior of the application. |
Input Notification event
With instance type 3 it is possible to release different events with the help of the event filter. All events are sent from the DALI control device by a Input Notification and can be received with FB_DALIGetInputNotification.
The possible events (Event Name column) and their binary representation (Event Information column) are listed in the following table.
Event Name | Event Information | Description |
|---|---|---|
No Movement | 2#00_0000_XXX0 | No movement detected. |
Movement | 2#00_0000_XXX1 | Movement detected. |
Vacant | 2#00_0000_X00X | The area is not occupied. |
Still Vacant | 2#00_0000_X10X | The area is vacant over a lengthy period. The event occurs at regular intervals as long as the vacant condition is satisfied. |
Occupied | 2#00_0000_X01X | The area is occupied. |
Still Occupied | 2#00_0000_X11X | The area is occupied over a lengthy period. The event occurs at regular intervals as long as the occupied condition is satisfied. |
Presence Sensor | 2#00_0000_0XXX | The current event was triggered by an occupancy sensor. |
Movement Sensor | 2#00_0000_XXX1 | The current event was triggered by a movement sensor. |
The points marked with X can assume a value of either 0 or 1 and thus combine several events with one another.
Motion sensor
The instance detects exclusively whether there is movement in the room or not.
If no movement was detected within a certain time, the area is regarded as vacant.
Occupancy sensor
The instance detects occupancy of the room. Some devices detect occupancy and movement.
Further information can be found in IEC 62386-303.
Events with HOLD TIMER
On expiry, the time Treport triggers the "Repeat" event (bit 2 of the event filter) (see tReport). The time then starts over. The previous event remains active during the time Treport. Treport is restarted by a newly detected event.
Thold provides for a hold time following the detection of movement (see tHold). Not all devices support this variable.
Events with CANCEL HOLD TIMER
If the DALI device supports the hold timer, it can be deactivated via the command FB_DALI303CancelHoldTimer.
The hold timer was deactivated before the expiry of its set time. The Vacant und No Movement events are triggered immediately at this moment.
Deadtime timer
Several events may not be sent from an instance at the same time. To avoid this a dead time (Tdeadtime) can be activated (see tDeadtime).
If the Deadtime Timer is active, an instance should not send any further events until the timer Tdeadtime has expired. The timer is restarted after the sending of an event.
If a new event occurs before the current event is sent, then the new event replaces the existing one. This can happen if the bus is not available or if the timer TDeadtime is in use.
If Treport < Tdeadtime, then Treport should be equal to Tdeadtime regardless of the value that Treport previously had.