Commissioning & Scanning
Why does my DALI gateway report finding 64 devices during a scan when fewer luminaires are actually installed?
By Lichtvision Engineering · Published
Short answer
When a DALI gateway or controller reports finding exactly 64 devices (the maximum possible on a single DALI line) despite having significantly fewer physical luminaires installed, the scan is being corrupted by severe addressing collisions, a second merged DALI line, or incompatible legacy control gear. During a commissioning scan, the gateway searches for 24-bit random addresses. If two or more devices suffer from an electrical fault or corrupted firmware that causes them to pull the bus low indiscriminately during addressing comparisons, the gateway perceives a continuous stream of valid responses across all 64 short address slots, populating its database with "ghost" fittings. Check that two separate DALI lines haven't been accidentally wired together in the ceiling void, remove legacy DSI/DALI-1 mixed drivers, and use a ProbitSite SmartScan to inspect actual physical GTINs and random addresses.
What the customer asked
A systems integrator commissioning a KNX-DALI building automation system in a municipal building reported a bizarre scan anomaly that halted handover (quotes lightly edited and translated, fully anonymized):
"In three separate zones, our KNX-DALI gateway reports discovering exactly 64 DALI devices after a new initialisation scan. In reality, Room A only has 21 luminaires, and Room B has 57."
"When we try to use the gateway's diagnostic software to blink-test these 64 discovered addresses, half of them do nothing, and several physical luminaires blink simultaneously on multiple addresses."
Why gateways invent "ghost" devices
To assign short addresses (0 to 63), a DALI controller uses a binary search algorithm querying 24-bit random addresses. The controller asks: "Are there any devices with a random address lower than X?" All qualifying devices answer simultaneously by pulling the bus low.
If the bus suffers from signal corruption or hardware incompatibility, this binary search breaks down: 1. Indiscriminate Bus Pull-Down: Faulty optocouplers in a single damaged driver can cause it to answer "Yes" to every single query telegram. The controller assumes every branch of the 24-bit search tree is populated, systematically assigning short addresses 0 through 63 to imaginary devices. 2. Physically Merged Segments: In suspended grid ceilings, electricians occasionally cross-connect the DALI control pairs of Line 1 and Line 2. The combined headcount exceeds 64, causing massive collision storms that gateways interpret as a saturated 64-device bus. 3. Protocol Mixing (DSI/DALI): Connecting older proprietary digital signal gear (such as legacy Tridonic DSI ballasts) onto a modern DALI-2 line corrupts the query answer frames, tricking gateways into registering false positive device discoveries.
How to clear ghost entries and scan accurately
First, physically verify that the segment is isolated. Power down adjacent DALI lines to ensure no cross-line leakage exists in the ceiling distribution boxes.
Next, bypass the automation gateway and plug ProbitSite directly into the segment. Run a SmartScan. Unlike simple gateway commissioning wizards, ProbitSite reads the hardware GTIN, serial numbers, and underlying random addresses of responding gear.
If ProbitSite also spots corrupted answers across all 64 addresses, switch to Expert Mode and run a line bisection test. Disconnect half the line at the local distribution board and re-scan. By narrowing the circuit, you can quickly pinpoint the exact damaged driver or cross-wired loop that is shouting over the bus and generating ghost discoveries.
Diagnose DALI issues like this in seconds
ProbitSite is the DALI-2 certified handheld multimeter built for exactly this kind of on-site fault finding.