User's Manual

Table Of Contents

ADDICT v3.0.1 User Manual DALI Functionality

The following example shows that the 4

detected packet was a “Query Ballast” command from

a master (another term for controller) to the device with address 3, 16.06s after the ADDICT

started sniffing. A reply of FF (in hexadecimal, 255 in decimal, and indicates a “yes” reply to the

query command) is also shown, and was detected 0.01s later.

Replies are always 1 byte, and are always displayed in hexadecimal.

Pressing enter will cause the screen to toggle between showing a decoded description of the

packet and the raw packet data (shown as a hexadecimal value). The following example shows a

“go to scene 6” command sent from a master to all devices in both descriptive and raw format.

Note: the raw hexadecimal packet data will only make sense if a listing of DALI commands and

their respective codes is available to the user. It was included to allow for the display of any

“extended” DALI commands used by a controller that would normally be specific to a device and

unknown to the ADDICT

Commands sent from a controller to a DALI device (also known as a slave device) are always 2

bytes long for standard DALI (e-DALI is 3-bytes long).

The following example shows two consecutive packets detected 1s apart. It also shows that the

device with address 14 does not have a lamp failure since it didn’t respond to the query

command and therefore the second screen shows the ADDICT has moved on to the next address

to query its lamp status.

Since it is possible for DALI devices to have different replies to the same query command (and

different response times), typically a query command sent to more than one device will cause

invalid data to be generated on the line. However, these situations can sometimes still produce

usable information.