Crestron
DIN-DALI-2
DIN Rail 2 Channel DALI Interface
Programming Guide – DOC. 7365A
DIN Rail 2 Channel DALI Interface: DIN-DALI-2
•
7
Advanced DALI Console Commands
DALI console commands are available for almost all functions that can be executed
from the DALI configuration tool. In most cases it is much simpler to use the
software tool, but console commands are sometimes the only way to accomplish
lower level debugging.
Console commands can be viewed using
Help debug
.
The syntax of the command generally follows:
[Command] [LOOP] [ADDRESS] [additional data]
•
LOOP
is 1 or 2.
•
ADDRESS
is a value between 0 and 63 or ALL if the command should go
out as a broadcast to everyone. The address UNDEFINED may also be used
for ballasts that have not been addressed.
The following sections discuss several helpful commands in detail.
Discovering what is on the DALI Loop
The software tool does not always show the true state of what is on the loop. It may
not show all devices or it may still show devices no longer present. The discovery
process can be run using the
DALIDISCOVER
command.
Recommended syntax:
DALIDISCOVER [LOOP]
This command triggers a search for ballasts by short address and then by random
addresses on the loop specified. The short address search simply involves querying
every short address 0–63 for the ballast’s long (or random) address. The random
address search is a binary search that queries ballasts based on the long address for
its short address. The binary search finds any ballasts on the link as long as they have
unique long addresses. Ballasts may only have duplicate long addresses if they are in
their factory default state and no addressing has been performed (long address =
0xFFFFFF). The probability of duplicate long address by random chance is
essentially 0%.
QUICK
can be included in the command to search only based on short address. This
is not recommended as ballasts that have duplicate short addresses or no address
assigned do not show up.
Alternative syntax:
DALIDISCOVER [LOOP] [QUICK]
The discover process takes a few minutes. At the end it displays a list of short
address and long addresses. The following are some of the possible results:
•
Duplicate short addresses
: Address conflicts exist and should be resolved
using the software tool or using the
DALISETADDRBYRND
command.
•
Invalid short addresses of 255
: A ballast has not been addressed.
•
Invalid/duplicate long addresses of 0xFFFF
: One or more ballasts are in
the factory default state and have not been addressed.
•
Total number of entries does not match the number of ballasts on the loop
:
Multiple ballasts have not been addressed. They all have short addresses of
255 and long addresses of 0xFFFF and so only show up as one entry.
