One C-Bus channel or output isn’t working but the rest are fine

One of the most common calls we get from fellow integrators (and from our own techs out on a service run) is this: “Everything in the house is working, but one downlight circuit — or one set of garden lights — just sits there dead.” Good news first: when it’s a single channel and the rest of the network is happy, you’ve already narrowed the problem down massively. The network, the power supply and the comms are almost certainly fine. The fault lives in that one channel, its programming, or the load on the end of it.

This article walks through the diagnostic sequence we use at DUKE to isolate a dead channel on a C-Bus relay or dimmer output unit. Work through it in order — it goes from “easiest, no tools” to “pull the unit”, and most faults are sorted well before the end.

The diagram above shows a typical C-Bus relay output unit wired into a board — the pink C-Bus cable carrying the SELV network on one side, and the switched mains channels heading out to their circuits on the other. Keep that picture in your head: the comms side and the load side are completely separate worlds, and knowing which side you’re chasing is half the battle.

Step 1: Confirm the unit itself is online

Before you touch anything, look at the C-Bus status indicator on the front of the output unit. A steady (or healthy slow-blink, depending on the model) C-Bus LED tells you the unit is seeing good network voltage and is talking on the bus. If the rest of the system is working and this unit’s indicator is steady, the network clock, the 5500PS system power supply and your unit burden are all doing their job.

That single observation rules out a whole category of faults. You are not chasing a flat network, a missing clock, or a comms dropout. The problem is downstream — either the channel’s programming or the physical load it drives.

Step 2: Use the local override to test the channel at the board

Every Clipsal relay and dimmer output unit has local override/test buttons — one per channel — on the front face. This is your single most useful diagnostic. Press the override button for the affected channel and watch (and listen to) the load.

1. Press the channel’s local override button. On a relay you should hear a distinct mechanical click as the contacts close; on a dimmer the channel should ramp the load up.
2. If the load switches on from local override: the output stage and the load wiring are healthy. The fault is in software — group assignment or programming. Jump to Step 3.
3. If the load does NOT respond to local override: the unit’s own hardware can’t drive the load. The problem is either the load-side circuit (breaker, wiring, the fitting) or a failed output stage. Go to Step 4.

This split — “does it work from the button at the board?” — is the fork in the road. It instantly tells you whether you’re a software job or a sparky job.

Step 3: Check the Group Address mapping in Toolkit

If local override drives the load but the switch or scene doesn’t, the channel is healthy but it isn’t listening to the right Group Address. This is far and away the most common cause we see, especially after a board change, a unit swap, or a partial reprogramme.

Connect with C-Bus Toolkit through your network interface (PCI 5500PC, a 5500CN CNI, or a 5500PCU) and open the unit’s properties:

• Confirm the channel has a Group Address assigned at all. An unprogrammed channel is set to a default/unused group and will do absolutely nothing from the network even though the hardware is perfect.
• Confirm it’s the right group. We’ve lost count of how often a channel got mapped to the group for a different circuit during commissioning — so the switch is working, just driving the wrong (or a deleted) output.
• Confirm the application is correct. Channels should be on the Lighting application (56) for normal switched/dimmed loads. A channel accidentally sitting on another application won’t respond to your Lighting group commands.
• Check it isn’t disabled or held by the Enable (203) or Trigger Control (202) applications from some logic that’s gone stale.

Once you correct the Group Address, send the changes to the unit and test from the actual switch. If you’re shaky on how groups map switches to outputs, we’ve covered the fundamentals in our C-Bus programming notes.

Step 4: When local override won’t drive the load

If pressing the local button does nothing at the load, the network and software are off the hook — this is a physical fault. Treat relays and dimmers slightly differently.

For a relay channel

• Listen for the click. If you hear the relay click on override but the load stays dead, the contacts are switching but no power is reaching the fitting — look downstream.
• Check the output breaker / MCB feeding that channel’s circuit. A tripped or off breaker is a classic “one circuit dead” cause that has nothing to do with C-Bus.
• Check the load-side wiring and the fitting itself. A failed downlight driver or a loose active at the channel terminal will mimic a C-Bus fault perfectly.
• No click at all on override? The output stage for that channel may have failed (see Step 5).

For a dimmer channel

• Check minimum load. C-Bus dimmers need a minimum connected load to operate reliably. If LED lamps were swapped in and the load dropped below the dimmer’s minimum, the channel can refuse to fire or behave erratically. Confirm against the unit’s spec — units like the L5504D2U have a stated minimum per channel.
• Check edge mode (leading vs trailing). A channel set to the wrong dimming mode for the connected LED driver can sit dead, flicker, or buzz. Set the correct edge mode for the load in Toolkit.
• Check the load type and lamp compatibility. Non-dimmable LED lamps on a dimmer channel will misbehave no matter what you do at the bus.

Step 5: A genuinely dead output stage — replace the unit

If the channel won’t drive its load even from local override, the breaker is on, the wiring is sound and the load is known-good, you’re looking at a failed output stage inside the unit. Output units don’t generally fail channel-by-channel, but it does happen — a relay contact welds or burns out, or a dimmer’s output device fails.

There’s no field repair for a failed channel. The fix is to replace the output unit. When we do this, we:

1. Isolate the board and confirm dead.
2. Record the existing unit’s Unit Address, channel-to-group mapping and any custom ramp rates / edge modes from Toolkit first.
3. Swap in the replacement unit (electrician work) and re-terminate the load and C-Bus cable.
4. Re-address the new unit and restore the channel mappings, then test every channel from both local override and the network.

Where you can, move the dead circuit to a known-good spare channel as a temporary measure to confirm the diagnosis before ordering a replacement — if the load springs to life on a different channel of the same unit, you’ve confirmed it’s that one channel’s output stage at fault.

The short version

Steady C-Bus LED = network is fine. Local override drives the load = software/group problem, fix it in Toolkit. Local override doesn’t drive the load = physical fault, check breaker, load and minimum load/edge mode, and if the channel is genuinely dead, replace the unit. Re-mapping Group Addresses is a software job anyone with Toolkit can do; the unit swap and load wiring is for the licensed sparky.

That’s the same sequence our techs run on every “one circuit’s out” callout, and it’ll have you to the root cause quickly. If you’d rather we sorted it — or you’ve reached the unit-replacement stage and want a Melbourne C-Bus electrician on site — get in touch with the DUKE team and we’ll take it from here.

Cheers,
Adam and the DUKE team