Low C-Bus network voltage: units flashing, dropping off or unresponsive

When a customer rings us saying “half the switches in the house are flashing” or “the lights randomly drop off and come back”, nine times out of ten we’re not chasing a dead unit — we’re chasing volts. C-Bus is a SELV network nominally sitting around 36V DC, and the whole system runs off that single pink Cat5 pair. Starve it of voltage and units start blinking, dropping off the network and ignoring commands. This article is the diagnostic sequence our team works through, written for fellow integrators.

The key thing to grab early is your multimeter. C-Bus problems get blamed on programming all the time, but you can’t program your way out of a voltage problem. Measure first, theorise second. The diagram below lays out the network limits we’re working within.

What a healthy C-Bus network looks like

C-Bus is extra-low voltage (SELV) and runs at roughly 36V DC unloaded. In a real installation with units drawing their burden, you’ll see it settle into the low-30s — that’s normal and healthy. The hard floor is around 20V DC: below that, units can’t reliably power their electronics, hold the network clock or transmit, so they start misbehaving.

So your first job is simple: measure across the C-Bus pair (the blue/white-blue conductors carry the signal/power) at several points around the network — at the power supply, mid-run, and crucially at the furthest unit from the supply. You’re building a picture of voltage across the whole segment, not just one reading at the board.

First: low voltage or a single failed unit?

Before you pull the board apart, work out which problem you actually have. This distinction saves hours.

• Many units flashing or dropping off across the network — that’s a network-wide symptom. It points to voltage: insufficient or missing power supply, too much load for the enabled supplies, or excessive voltage drop. Read on.
• One unit dark or flashing while everything else is happy — that’s a single-unit problem, not a network voltage problem. If the rest of the network reads a healthy low-30s and only one DLT is dark, you’re looking at a faulty unit, a bad punch-down on that drop, or a damaged section of cable to that one device. Don’t go adding power supplies chasing a single failed unit.

The C-Bus status indicator on each unit is your free diagnostic. A steady (or correctly pulsing) indicator means the unit sees adequate network voltage and clock. An indicator that’s flashing erratically or off altogether on multiple units is the classic low-voltage signature.

The diagnostic sequence we follow

1. Measure the network voltage at the supply. Put the meter across the C-Bus pair right at the system power supply (e.g. the 5500PS). If it’s already low here, the supply isn’t delivering — check it’s powered and not faulted.
2. Confirm at least one system power supply is present and enabled. This catches more jobs than you’d think. A unit with an integrated supply may have its power-supply function disabled in C-Bus Toolkit, or a dedicated 5500PS was removed during a board change and never replaced. Open Toolkit, check the unit’s properties and confirm the network power supply is enabled. A forgotten or disabled supply starves the whole segment.
3. Measure at the far end of the run. Walk to the unit physically furthest down the cable and measure across the pair. Compare it to the reading at the supply. A drop of a few volts over a long run is expected; a drop that takes the far end near or below 20V is your fault.
4. Add up your enabled supply capacity against the load. Count how many supplies are enabled on the segment and what they deliver versus what your units draw (every unit lists a network burden in milliamps). If load exceeds enabled capacity, voltage sags and units flash. The fix is more enabled supply — but mind the cable limit in the next step.
5. Check you haven’t exceeded 2 A per segment. The pink C-Bus cable can carry a maximum of 2 A of total enabled power-supply capacity per network segment. You add or enable supplies up to that ceiling, and once you need more, you bridge to a new segment rather than piling on supplies. More on this below.
6. Inspect terminations and the cable run. A poor punch-down, a nicked conductor or a section run alongside mains can introduce resistance or noise that drags voltage and corrupts messages. Re-terminate anything suspect and confirm clean, straight pairs.

Power supply capacity and the 2 A rule

Here’s where a lot of voltage problems are born. Every C-Bus unit draws a network burden from the segment. Add up the burdens of all your units and you get the total demand. Your enabled power supplies have to meet that demand — but the cable imposes a hard ceiling of 2 A of total enabled supply capacity per segment.

So the logic runs: tally your load, enable enough supply to comfortably cover it, but never let total enabled supply capacity on a single segment exceed 2 A. If your load genuinely needs more than that — a big house with a lot of units — you split the network with a Network Bridge (5500NB) into separate segments, each with its own supplies, each under the 2 A limit. That’s the proper way to scale, not stacking supplies past the cable’s rating.

Where you put the supply matters

Two networks with identical total supply capacity can behave completely differently depending on where the supplies sit. Push all your supply in at one end of a long run and you’ll get an end-fed network: voltage is fine at the supply and droops badly by the far end, where units flash even though your “total capacity” looks adequate on paper.

The fix is to centralise or distribute supply. Feed power into the middle of a long run so both ends are within easy reach, or split capacity across two points so no single leg has to carry the full drop. This is exactly why we measure at the far end — the maths can say you’re fine while the physics says the end-fed units are starving.

If you’re planning a new install rather than fixing one, get this right on paper before you pull cable. Our notes on designing the C-Bus network and getting started with C-Bus cover supply placement and segment planning in more detail.

Putting it together

When everything’s right you should be able to walk the network with a meter and see the low-30s holding up from the supply all the way to the furthest unit, every status indicator behaving, and units responding crisply to commands in Toolkit. If you’ve added or re-enabled supply and the far end is still soft, check for voltage drop and consider relocating supply or bridging.

And remember the distinction we opened with: a network full of flashing units is a voltage problem; one lonely dark unit on an otherwise healthy network is a unit or cabling problem. Diagnosing the right one first is the whole game. For more on indicator behaviour and message errors, see our C-Bus troubleshooting guides. Schneider Electric’s official Clipsal documentation is also worth a read for unit-specific burden figures — you’ll find it via clipsal.com.

That’s the sequence our team runs on every “flashing switches” call-out, and it sorts the vast majority on the first visit. If you’re a Melbourne C-Bus owner watching your lights drop off, or an integrator stuck on a stubborn low-voltage network, get in touch via our contact page and we’ll help you sort it. Measure first, trust the volts, and the rest follows.

— Adam and the DUKE team