Why does my DALI tester show a 'bus traffic' error and refuse to scan, and can I test the line without disconnecting the gateway?

What the customer asked

An engineer testing a DALI installation contacted us after their first scan failed. Their bus had an active KNX-DALI gateway, and they were puzzled (quotes lightly edited and translated, fully anonymized):

"Even though our KNX-DALI gateway works to the DALI-2 standard, I still get a 'Bus Traffic' error, is that normal?"

"It would be great to see the bus traffic directly on the line, without having to decouple from it."

"Only after switching off the DALI gateway can I check the line with a scan."

Why the "bus traffic" message appears

A ProbitSite scan runs in two steps: first it asks every device on the bus to stay quiet (a quiet-mode request), then it queries each device individually. The trouble starts at step one. A single-master application controller, the role many KNX-DALI gateways play, is not required by the DALI standard to honour that quiet request, and it is only allowed to operate as the sole master on the segment. So it keeps sending telegrams even while the tester is connected. As our engineers describe it:

"To prevent faults on the installation, ProbitSite stops and shows 'bus traffic'. This behaviour is normal."

A second, less common cause is manufacturer-specific commands that are not part of the DALI standard, something that was especially common with older DALI-1 systems.

Is it a fault? No.

ProbitSite first checks whether a bus voltage is already present and, if so, does not add its own. When it then detects other telegrams on the line, it deliberately withdraws rather than transmit into live traffic, a safety behaviour that protects the running installation. The message is information, not a defect in your device.

How to scan the line

Give ProbitSite a quiet bus: take the gateway or controller off the line or power it down, then run the scan. With the gateway disconnected you can light the whole installation using "Press OK to identify all". To blink individual luminaires, run a scan first; afterwards you can step through the discovered devices (long-press the left/right button) and identify them one by one. Our on-site video demonstrates the individual blink, see the ProbitSite on-site walkthrough on our website.

Good to know

Newer ProbitSite software handles interfering telegrams more gracefully, so a scan often succeeds even when another controller is talking, as long as it does not block the actual measurement. Where a full scan still is not possible, powering down the single master remains the reliable route.