Dual Trip-Coil and Dual DC-Supply Schemes: Independence, Supervision and Failure Modes

A practical redundancy guide exposing common-mode failures across DC sources, MCBs, relay contacts, terminals, cables, plugs, coils and mechanisms.

Two trip coils do not create redundant tripping if they share one battery, one fuse, one cable, one relay output, one terminal block or one mechanically jammed release. Independence must be engineered from fault detection and DC source through every contact/conductor to the breaker mechanism, then proved under single-failure and maintenance states.

This guide compares dual-coil/dual-supply architectures, common-mode failures, trip-circuit supervision, selectivity, output contact duty, breaker interfaces, testing and practical availability metrics.

Executive conclusions

  • State the required success criterion: trip with any one channel unavailable, or merely provide a spare coil?
  • Draw fault-containment zones from Battery/Charger A and B to Trip Coil 1 and 2.
  • Remove common protection, terminals, cables, plugs and relay contacts where independence is required.
  • Check whether two coils actuate independent releases or one common trip bar/latch; mechanical common mode remains.
  • Coordinate simultaneous versus separate coil energisation with the breaker manufacturer.
  • Size DC circuits at worst battery/end voltage and temperature with actual coil inrush/current and cable drop.
  • Supervise each channel across meaningful breaker positions without allowing monitor current to pick up a coil or auxiliary relay.
  • Ensure output contacts can make/carry/interrupt the DC inductive duty or use qualified interposing/suppression.
  • Test every channel independently and in single-failure/maintenance combinations.
  • Use event/alarm naming that identifies the failed channel and does not hide common DC loss.

1. Standards boundary

ReferenceContribution
IEC 62271-1:2017+AMD1:2021Common auxiliary/control equipment and supply/service framework
IEC 62271-100:2021+AMD1:2024AC circuit-breaker and operating-mechanism requirements/tests
IEC 62271-200:2021+AMD1:2024MV assembly and auxiliary/control circuit integration
IEC 60255-27:2023Product safety for protection equipment; functional availability must be separately designed
IEC 61082-1:2014Electrotechnical document presentation
IEEE C37.11-2022AC HV breaker electrical-control requirements when the IEEE regime is specified

Obtain exact breaker coil voltage limits, burden/time, permitted simultaneous energisation and auxiliary-contact ratings from the manufacturer. Do not infer them from IEC general wording. A protection relay safety certificate does not prove its output contact is suitable for the trip-coil inductive duty.

2. Define required independence

  • N: one trip path; any single failure can block tripping.
  • Two coils, one supply: mitigates coil/open-wire failure but not DC-source/distribution loss.
  • Two supplies, common command/output: source redundancy can be defeated by common control or improper paralleling.
  • Two independent channels: separate source, protection, logic/output, cable/terminal and coil; mechanism may remain common.
  • Diverse protection/tripping: independent principles/devices/channels reduce systematic/common-mode risk.

Specify credible single failures and allowed maintenance: battery/charger out, MCB trip, earth fault, broken conductor, relay unavailable, terminal work, coil open/short, breaker plug problem and common mechanism failure. Define required alarm time and whether automatic actions remain secure.

3. Independence matrix

ElementChannel AChannel BReview question
DC sourceBattery/charger/bus ABattery/charger/bus BAny deliberate/unintended tie or common AC charger source?
Feeder protectionMCB/fuse AMCB/fuse BSelective with downstream short; physically segregated?
Detection/logicRelay/output ARelay/output BIndependent CT/VT/IED or common input/systematic dependency?
MarshallingTB/cable/plug ATB/cable/plug BCommon connector, route, knife link or multicore damage?
ActuatorTrip coil 1Trip coil 2Independent releases or shared trip bar/latch?
SupervisionTCS ATCS BDetects its own full path and common DC loss?

Mark physical fire/flood/arc/EMC separation as well as schematic separation. Two wires in the same removable plug can be lost by one loose connector.

4. Common architecture options

Option A: both protection systems trip both coils

Maximises command paths but cross-couples channels. Use separate output contacts/diode isolation as engineered, prevent DC-source paralleling and check that a ground/short on one matrix cannot disable both. Testing/maintenance isolation is more complex.

Option B: Protection A → Coil 1; Protection B → Coil 2

Clear separation and easier fault tracing. Each protection principle/channel must cover required faults; failures in one CT/VT/logic path leave only the other. Breaker-failure initiation and lockout outputs must be coordinated.

Option C: main and backup trip paths

Primary protections use one coil; independent backup/lockout/remote trip uses the other. Availability depends on detection/clearing time and whether loss of main channel is alarmed promptly enough.

5. Prevent unintentional DC paralleling

  • shared relay contacts with common internal commons;
  • test switches/jumpers bridging A and B;
  • common indication lamp, TCS module or suppression device;
  • wrong diode direction/voltage/current rating or diode short failure;
  • interposing relay coils/contacts powered from mixed systems;
  • breaker internal wiring that connects coil returns;
  • earthing/ground-fault detector arrangements and inadvertent ground;
  • portable test equipment connected across systems.

Trace galvanic paths in normal, trip, test, fuse-open and ground-fault conditions. Labelling two potentials “+DC1” and “+DC2” does not prove separation.

6. Trip coil and mechanism interface

  • rated voltage and permissible operating range at the coil terminals;
  • cold/hot resistance, inrush/steady current and energisation duration;
  • minimum pulse/energy and release/latch force;
  • duty limit and maximum sustained voltage if auxiliary contact fails;
  • coil insulation/suppression polarity and inductive energy;
  • simultaneous Coil 1+2 energisation permission/effect;
  • mechanical release independence and common latch/shaft failure;
  • 52a/52b/mechanism contact sequence that interrupts current;
  • coil replacement/identification and plug/terminal arrangement.

Simultaneous coils may produce no faster opening because both act on one latch, while doubling DC current and contact duty. Some designs permit it; others restrict it. Obtain written manufacturer data.

7. DC voltage-drop and current calculation

For each channel, calculate minimum coil-terminal voltage with the battery/DC bus at its design minimum, charger unavailable where required, maximum route length, conductor/terminal/contact resistance at temperature, protective-device drop and simultaneous load. A simple loop approximation is:

Vcoil = Vsource,min − Itrip × Rloop,max − ΣVcontacts/devices

  • use the manufacturer coil V–I/resistance/operation data, not nameplate watts alone;
  • include positive and negative conductors;
  • include cable, terminals, links, relay/interposing contacts, MCB/fuse and breaker plug;
  • apply copper temperature and conductor-area tolerances;
  • check simultaneous trips and DC feeder/battery impedance;
  • check maximum voltage/temperature and coil duty too.

8. Output contact and interposing relay duty

  • DC making, carrying and inductive breaking rating at actual voltage/current/L/R;
  • contact material/series contacts and minimum load for supervision;
  • coil suppression effect on release time and insulation stress;
  • welded contact/failed auxiliary contact causing prolonged energisation;
  • interposing relay operate/release voltage, burden, contact duty and supervision;
  • failure of common output card/internal auxiliary supply;
  • arc/creepage and IEC 60255-27 product-safety interface.

Do not apply an AC contact rating to DC inductive interruption. A flyback diode strongly delays coil-current decay and can affect timing; only use manufacturer-approved suppression/orientation.

9. Protection output allocation

  • main/backup protection outputs and self-supervision failure;
  • lockout/master trip and manual emergency trip;
  • breaker-failure initiation/retrip/remote trips;
  • busbar/differential trip matrix and isolation of bay faults;
  • SCADA/remote trip authority and cybersecurity boundary;
  • direct hardwired versus GOOSE command diversity;
  • output contact/card/module commonality;
  • test/maintenance blocking without disabling both channels.

A single lockout relay with two contacts can still be a common mechanism/coil failure. Decide whether that is acceptable from the reliability/safety study.

10. Trip-circuit supervision per channel

  • DC source/feeder protection and conductors;
  • trip output/contact or bypass supervision path;
  • test/terminal links and breaker plug;
  • coil continuity and return;
  • breaker open/closed/service/test states required;
  • monitor current below pickup for coil/auxiliary devices;
  • alarm delay for contact transition but prompt failure detection;
  • separate A/B/common DC failure alarms and SCADA quality.

Many simple TCS circuits cannot see the entire path in every breaker position. Publish a supervision coverage matrix and residual blind spots; dual coils do not justify assuming the unsupervised channel is healthy.

11. DC protection and selectivity

  • interrupting capacity at maximum DC fault current and time constant;
  • minimum fault current at remote cable end sufficient for timely operation;
  • selectivity with upstream battery/distribution protection;
  • polarity and suitability of DC MCB/fuse;
  • common-cause trip from shared auxiliary/contact fault;
  • earth-fault monitoring in unearthed DC systems and second-fault risk;
  • segregation/fire protection of A/B feeders and routes;
  • safe isolation/lockout and indication.

12. Failure-mode analysis

FailureExpected response
Battery/feeder A lostAlarm A; channel B remains isolated and fully capable
Coil 1 openTCS A alarm in specified states; Coil 2 trips
Coil 1 shortSelective protection A isolates; B/source B unaffected
Output A weldedBreaker auxiliary contact interrupts coil within duty; alarm/coil protected
Common breaker plug looseIf both channels share plug, independence claim must reflect common loss
Mechanism latch jammedBoth coils may fail; breaker failure trips upstream/adjacent sources
DC ground A then second groundDetection/response prevents cross-channel/common trip or failure

13. Physical segregation and EMC

  • separate A/B DC distribution boards/terminal groups/cables/routes as required;
  • avoid both channels under one knife/link/connector cover;
  • separate from high-energy AC/CT circuits and primary conductors;
  • twist/route outgoing and return together to reduce loop area;
  • apply shield/earth rules without cross-bonding DC systems unintentionally;
  • protect against one panel fire/water/arc/rodent event where reliability target requires;
  • label channel/polarity unambiguously at both ends.

14. FAT and SAT test matrix

  1. Verify as-built separation/continuity/insulation and no A–B galvanic tie.
  2. Measure coil/circuit resistance and minimum terminal voltage under realistic supply/load.
  3. Trip each coil from each allocated protection/lockout/manual path.
  4. Open each MCB/fuse/link/plug/conductor point and verify channel alarm plus other-channel success.
  5. Test breaker open/closed/test/service TCS coverage and alarm delays.
  6. Test simultaneous commands and prolonged-contact failure within approved procedure.
  7. Prove breaker-failure action for common mechanism failure.
  8. Verify event/SCADA naming, time stamp and channel discrimination.
  9. Restore all links/blocks/settings and independently inspect normal state.

15. Maintenance and condition monitoring

  • trend TCS alarms, DC feeder trips, coil resistance/current and trip timing;
  • operate/test each channel at defined risk-based intervals;
  • inspect terminal/plug/contact corrosion and tightness by approved methods;
  • verify battery/DC bus minimum-voltage and simultaneous-trip capability;
  • replace coils/auxiliary contacts by manufacturer criteria and retest;
  • control temporary jumpers/blocks during maintenance with independent restoration;
  • reassess independence after relay, battery, terminal or breaker retrofit.

16. Common design mistakes

MistakeCorrection
Two coils called redundantTrace source-to-mechanism common modes and success criterion
Two batteries share one trip MCBIndependent selective feeders/protection and no unintended tie
Both channels in one multicore/plugSegregate or explicitly accept/document common failure
Relay contact rated by AC valueVerify actual DC inductive duty
TCS only in closed positionDefine required coverage/open/test/service circuits
Diodes added for isolationAnalyse polarity, rating, failure and supervision
Both coils always energisedConfirm manufacturer permission and DC/contact duty

17. Required engineering deliverables

  • reliability/success criterion and single-failure/FMEA;
  • A/B independence matrix and physical routing/layout;
  • complete trip/lockout/breaker-failure schematics;
  • DC short-circuit/selectivity and voltage-drop calculations;
  • coil/output contact/interposing/suppression manufacturer data;
  • TCS coverage/alarm matrix;
  • terminal/cable/plug segregation and labels;
  • FAT/SAT single-failure test procedures/results;
  • settings/SCL/relay-output allocation baseline;
  • maintenance and modification/revalidation plan.

18. Availability claims and proof-test interval

If the project assigns a numerical availability or probability-of-failure-on-demand target, model channel failure rates, common-cause factor, diagnostic coverage and proof-test interval. Two channels only improve availability when hidden failures are discovered and repaired before the next demand.

  • separate detected, undetected, repairable and common mechanism failures;
  • use field/manufacturer failure data with stated uncertainty;
  • credit TCS only for the break points/states it actually covers;
  • include maintenance-induced failures and both-channel outage time;
  • derive functional trip-test interval from risk and operational constraints;
  • feed alarms, coil-current/timing trends and test results back into the model.

References

Safety note: Trip circuits can operate breakers unexpectedly and may be supplied from multiple independent batteries. Establish all energy sources, block/isolating boundaries and operations authority before testing. Never disable both trip channels without an approved outage/risk control.

LearnSwitchgear

Search the engineering library