RCCB vs RCBO: Key Differences and When to Use Each

What is the difference between an RCCB and an RCBO? An RCCB (residual current circuit breaker, IEC 61008) trips on earth leakage only and carries no overload or short-circuit protection, while an RCBO (IEC 61009) combines that same leakage-detection element with an MCB in one module, tripping on leakage, overload, and short circuit. Pick the wrong one and a downstream fault either goes uncleared until the leakage current happens to unbalance the core, or a single nuisance trip takes down every circuit sharing that device. This article covers what each device actually switches, how discrimination works when an RCCB feeds a bank of RCBOs, panel-space and cost trade-offs, and where Schneider, ABB, and Siemens draw the RCCB/RCBO line in their catalogs.

What an RCCB Actually Switches

An RCCB senses residual current through a toroidal core and opens all poles when the vector sum of line and neutral current exceeds its rated IΔn. That's the whole job. It has no thermal or magnetic trip element, so a line-to-neutral short circuit or a sustained overload on the protected circuit will not open it — current keeps flowing until the leakage happens to trip the residual element, or until an upstream device further up the board finally clears the fault. Every RCCB installation needs a backup overcurrent device — typically an MCB or fuse — sized to the RCCB's rated conditional short-circuit current Inc (commonly 6 or 10 kA when backed by a compatible MCB).

Schneider's Acti9 iID, ABB's F200 series (F202 in 2P, F204 in 4P), and Siemens' 5SV range are all RCCBs in this sense: 2P or 4P, 25-125 A depending on the line, available across the Type AC/A/F/B spread. None of them will clear a bolted short circuit on their own.

What an RCBO Adds: Overload and Short-Circuit Trip in the Same Module

An RCBO folds the residual-current core and the MCB's thermal-magnetic trip mechanism into one device. Trip on leakage, trip on sustained overload, trip on short circuit — one module, one reset lever, one breaking-capacity rating that already accounts for the internal MCB. ABB's DS201 (1P+N) and DS202C/DS203NC cover this in a bare RCBO form; Schneider does it two ways — the compact Acti9 iDPN Vigi and Reload are single-piece RCBOs, while the Acti9 Vigi iC60 is an add-on residual-current block that clips onto an existing iC60 MCB to build the same function from two parts. Siemens' 5SU1 and 5SV1 are the equivalent compact RCBOs in the SENTRON line.

The functional result is identical to an RCCB plus a separately mounted MCB on the same circuit. The difference is packaging, not protection logic — and packaging is exactly what drives the selection decision below.

Key Differences at a Glance

Discrimination: One RCCB Upstream vs an RCBO on Every Way

Boards that put a single RCCB ahead of a whole bank of MCBs are cheaper to build, but every circuit on that bank shares one trip point. A leaking heater in one room takes out lighting and sockets on the same group. Selectivity between an upstream RCCB and downstream RCBOs solves this the same way overcurrent discrimination does — by separating both current threshold and time.

Put an S-type 300 mA RCCB upstream for fire/equipment protection, and instantaneous 30 mA RCBOs on the individual final circuits, and a leakage fault on one socket circuit clears locally without touching the feeder. What we see in the field is boards built the other way around — a single 30 mA RCCB feeding twenty circuits — where the first nuisance trip from an old immersion heater or a damp outdoor socket blacks out the whole board, and the client calls it "the RCD is faulty" when it did exactly what its rating told it to do.

When RCCB Plus MCB Makes Sense

Split-load consumer units and small distribution boards still use a bare RCCB ahead of a group of MCBs where budget per way matters more than fault isolation — a workshop lighting circuit, a group of non-critical fixed loads, or a board where every circuit runs the same sensitivity and load type anyway. It also suits boards being retrofitted: adding one RCCB ahead of an existing MCB bank is cheaper than swapping every MCB for an RCBO. The trade-off is accepted deliberately, not by default — a board with mixed critical and non-critical circuits on one shared RCCB is a design shortcut, not a design choice.

When an RCBO Is the Better Call

Any final circuit that needs a sensitivity or type different from its neighbors forces an RCBO, because a bare RCCB sets one IΔn and one waveform type for everything downstream of it. A VFD-fed circuit needing Type F sitting next to a socket circuit that only needs Type A is a textbook case — put an RCBO on the VFD way and leave the rest on Type A. EV charge points are the sharpest version of this: a Type B RCBO, or a Type A RCBO paired with a 6 mA RDC-DD, protects one dedicated circuit without forcing Type B sensitivity onto every other way on the board. The same logic applies to fault isolation on critical circuits — server room feeds, fire alarm supplies, freezer circuits — where losing that one circuit on a leakage fault is acceptable, but losing the whole board is not.

Panel Space, Cost, and Maintenance

An RCBO usually occupies more module width than a single MCB — commonly 1.5 to 2 modules on the compact ranges, more on some 4P versions — so a board built entirely from RCBOs needs a wider enclosure than the same circuit count on MCBs plus a shared RCCB. Cost per circuit is higher with individual RCBOs; cost per board can land close either way once you count the RCCB, the extra MCBs, and the busbar work a split-load board needs. Maintenance is where the RCBO usually wins outright: a nuisance trip or a genuine fault shows up on one lever, on one circuit, and everything else on the board stays live while it's investigated. With a shared RCCB, first response after a trip is checking every downstream circuit, because the device that opened gives no clue which one leaked.

Reading the Catalog: Where Schneider, ABB, and Siemens Draw the Line

Schneider ships both approaches: Acti9 iID as the bare RCCB, Acti9 Vigi iC60 as an add-on block for anyone standardizing on iC60 MCBs already, and Acti9 iDPN Vigi/Reload as a factory-integrated RCBO for new final-circuit builds. ABB's F200/FH200 series covers the bare-RCCB end, with DS201, DS202C, and DS203NC as the RCBO line, plus F200 B where a true Type B RCCB is the correct upstream device ahead of an EV or PV feeder. Siemens splits the same way: 5SV RCCBs upstream, 5SU1/5SV1 RCBOs on final circuits, and 5SM3 where a dedicated Type B device is needed on a feeder rather than a full-current-rated RCBO. None of the three treat RCCB and RCBO as interchangeable naming — the module choice tracks directly to whether that point in the board needs shared or isolated protection.

Conclusion

An RCCB switches on leakage alone and needs a backup overcurrent device; an RCBO puts both functions in one module and confines every trip type to a single circuit. Choose a bare RCCB ahead of a group of MCBs where circuits share the same sensitivity and losing the whole group on a leakage fault is acceptable — and grade it S-type against downstream devices if it isn't. Choose an RCBO wherever a circuit needs its own Type, its own IΔn, or must stay live when a neighboring circuit faults. For a working knowledge of the sensitivity and Type choices that feed into this decision, see the RCD protection guide, the breakdown of RCD sensitivity levels, and how to apply both across TT, TN, and IT earthing systems. For the wider terminology question, see MCB vs RCBO vs RCD vs RCCB differences, and for a selection checklist that ties sensitivity, Type, and pole count together, see how to select RCD sensitivity, type, and poles. Browse current stock across residual current devices and RCBOs.