KNX Bus Diagnostics & Troubleshooting

Bus voltage at no load should be 29–31 V DC (nominal 30 V) and must not fall below 21 V under load (many active participants). Measure with a DC multimeter directly on the red/black terminals of any device in the segment.

Voltage below 21 V indicates an overloaded power supply or a short circuit. Voltage above 32 V can damage devices. Voltage 0 V: power supply failed, fuse checked?

Each line segment requires its own power supply (max. 64 participants, max. 1,000 m cable length per line). Multiple power supplies on the same segment are possible, but only with a choke for decoupling, otherwise the power supplies short-circuit each other.

The ETS bus monitor shows all telegrams in real time: source address, group address, DPT value, telegram type (Write/Read/Response) and timestamp. Filterable by group address or device address. For diagnostics: capture for 5 minutes, then search for unexpected sources or telegram flooding (>1 per second on a GA).

Common fault patterns: device does not respond to switching (CO flag wrong? GA not connected? Device not programmed?). Device switches without user interaction (foreign CO writing to GA, address collision). Bus blocked, no telegram gets through (cable short circuit).

Poor installations manifest as bus noise: many telegrams with wrong CRCs or collisions (ETS reports "No ACK" or "Send error"). Causes: wire gauge too thin, stubs too long (>1 m branch line), missing termination resistors on long lines.

1. Measure bus voltage (21–31 V?). 2. Open ETS bus monitor, capture for 5 min. 3. Filter conspicuous telegrams (flooding, wrong sources, no ACK). 4. Identify suspicious device, disconnect from bus, re-measure voltage. 5. Connect device individually to test setup and program.

For hard-to-locate cable breaks: resistance measurement between bus conductors (with power supply disconnected). An intact line typically has 50–200 Ω (depending on number of device inputs in parallel). Very high value = break; very low value = short circuit.