Trip-Circuit Supervision in MV Switchgear: Designing Reliable Monitoring for Breaker Trip Coils

Trip-circuit supervision is a coverage claim, not a lamp: the designer must state exactly which DC source, fuse, relay contact, lockout contact, cable, auxiliary contact, secondary plug, trip coil and return conductor are proven in every breaker position. A green indication can coexist with a mechanically stuck breaker, a wrong trip matrix or an unsupervised open conductor.

This advanced design guide focuses on reliability architecture and evidence: failure-mode mapping, supervision-current feasibility, high-resistance defects, dual coils/DC systems, withdrawable breakers, coil-current signatures, alarm response, FAT/SAT and condition-based maintenance. It deliberately distinguishes continuous TCS/TCM from breaker-failure protection and periodic trip-path testing.

Executive rules

Publish a supervised-boundary diagram for breaker open, closed, in transition, test and disconnected positions.
Make the monitor reliably pick up at minimum station DC and maximum circuit resistance, while remaining incapable of energising the trip coil at maximum DC and minimum resistance.
Supervise each genuinely independent trip coil/DC/output path separately; prevent cross-feed between DC systems.
Do not let 52a/52b or rack-position logic create a false healthy state when the secondary plug or coil is unavailable.
Use TCS for electrical continuity, coil-current/travel/timing for dynamic health and 50BF for failed fault clearing.
Alarm with the exact affected breaker/coil/path and a defined operator response; generic “DC fail” is not actionable.
Test by opening every physical node inside the claimed boundary and by tripping at worst permitted DC.
Treat resistor, opto input, auxiliary relay, configuration and TCS DC supply as components that can themselves fail.

1. Protection-chain availability model

The fault-clearing chain is a series system: sensor → protection decision → trip output → DC path → trip coil → mechanism → interrupter. TCS observes only a selected electrical sub-loop. A useful requirements statement is:

“TC1 healthy proves continuity from DC branch fuse F1 through output bypass/supervision path, lockout contact, panel/field cable, service plug, 52a/52b selection, trip coil TC1 and DC return in breaker SERVICE-OPEN and SERVICE-CLOSED states.”

If the circuit does not prove one of those items, remove it from the claim. This prevents a maintenance team from inferring more safety than the wiring provides.

2. FMEA: what continuous TCS sees

Failure	Can TCS detect?	Additional evidence/control
Branch fuse/MCB open	Yes if monitor is downstream and return included	DC-board common alarm and selectivity study
Relay trip contact cannot close mechanically	Only if architecture supervises across/through the output as intended	Output self-test and periodic functional trip
Open interposing/lockout contact or wire	Only when inside active monitored loop	Boundary drawing and point-open tests
Trip coil open	Yes in breaker positions where current passes through coil	Resistance/current signature
High-resistance terminal/coil	Maybe; depends on dropout margin	Voltage/current trending and trip-at-minimum-DC test
Shorted turns/low coil resistance	Often remains “healthy”	Coil-current signature/resistance and fuse duty
Mechanism seized/low stored energy	No	Spring/pressure supervision, timing/travel and 50BF
Main contacts fail to interrupt	No	50BF current persistence
Wrong relay logic/trip matrix	No	End-to-end protection functional test

3. Circuit states to draw explicitly

State	Required question
Breaker closed, trip output open	Does supervision flow through 52a, coil and complete return?
Breaker open, trip output open	Does a 52b/resistor path still prove the coil before close?
Trip output closed	What happens to TCS indication during full trip current and after 52 contacts transfer?
Breaker travelling	Can both/neither 52a/52b create a transient alarm or false healthy?
Test position	Which primary-independent operations and secondary plug paths remain valid?
Disconnected/removed	Is the expected alarm clearly inhibited by a valid position, or is a critical path falsely declared healthy?
DC one-pole earth fault	Can supervision/backfeed unintentionally energise the coil or mask insulation fault?

A closed-only TCS path may be acceptable in a low-risk application, but it cannot claim readiness before energising an open breaker. An open-and-closed scheme commonly uses 52a/52b and limiting paths; exact wiring and resistor values are device-specific. Never transplant a schematic from another TCS input or coil.

4. Quantitative feasibility window

For a simplified current-based monitor:

I_mon = U_DC / (R_limit + R_TCS + R_coil + R_{leads/contacts}).

The design needs a real gap:

I_mon,min > I_{TCS,pickup,max} + margin, while I_mon,max < I_{coil,non-operate,min} / security factor.

Calculate I_mon,min at battery end-of-discharge/minimum permitted DC, hot/high coil and lead resistance, maximum resistor/input tolerance.
Calculate I_mon,max at charger boost/equalise maximum, cold/minimum coil resistance and minimum resistor tolerance.
Use guaranteed TCS pickup/dropout and trip-coil non-operate/pickup data, not typical values.
Check continuous resistor dissipation and abnormal/open-coil voltage: P = I²R or V²/R for the actual path.
Check resistor pulse/voltage/creepage, cabinet temperature and single-fault failure (short/open).
Check opto input leakage and semiconductor output leakage; several parallel monitor inputs can sum into meaningful coil current.

5. Worked worst-case screening example

Illustrative only. A nominal 110 Vdc system operates from 88 to 121 V. The complete monitor path has an 8.2 kΩ limiting resistor (±5%), a trip coil ranging from 1.05 kΩ cold to 1.35 kΩ hot, and 0.10 kΩ maximum leads/contacts. Ignore TCS input resistance only for this preliminary screen.

Minimum monitoring current ≈ 88/[8.2×1.05 + 1.35 + 0.10] kΩ = 8.73 mA.
Maximum monitoring current ≈ 121/[8.2×0.95 + 1.05] kΩ = 13.69 mA.
A TCS guaranteed pickup of 7 mA appears feasible at low voltage; a trip coil must have a guaranteed non-operate current comfortably above 13.69 mA with the project security factor.
Recalculate using actual TCS input impedance, resistor temperature coefficient, parallel paths and DC earth-fault cases.

The IEC breaker requirement that a trip release operates within its specified control-voltage range is not a guarantee that the project’s nominal opening-time band is maintained at the minimum voltage. TCS proves continuity/sufficient monitoring current—not trip-coil force or breaker clearing time. Perform trip timing at the specified worst control voltage when project performance depends on it.

6. Detecting high-resistance defects

A binary TCS threshold may tolerate a terminal resistance large enough to cause excessive voltage drop during full trip current. Therefore continuity is not the same as low impedance.

Calculate maximum total loop resistance that still lets the coil operate at minimum DC: R_loop,max ≤ U_DC,min/I_{coil,pickup,max}, using the OEM definition and margin.
Measure voltage at the coil while tripping, not merely open-circuit DC at panel terminals.
Trend monitor current/voltage if the IED exposes analogue values; set a maintenance band above binary dropout.
Inspect thermal damage, loose terminals, plug contacts and flexible wiring where resistance is intermittent.
Use four-wire resistance/controlled coil-current measurements only under isolated OEM-approved conditions.
Trip at minimum DC during outage and verify coil current, mechanism release and main-contact timing.

7. Trip-coil current signature: dynamic evidence

A recorded coil-current waveform can reveal more than TCS continuity. Typical stages include initial current rise, armature movement/change in inductance, mechanism unlatching, auxiliary-contact interruption and decay. Exact shape is breaker/coil dependent.

Compare peak/steady current, time to armature movement, coil energisation duration and auxiliary-contact cutoff with a known-good baseline.
Low current may indicate high circuit resistance/low DC; excessive current may indicate coil damage/shorted turns.
Delayed armature signature can indicate mechanical friction or weak magnetic force.
Long energisation can overheat a coil if 52a fails to interrupt; verify coil duty and anti-burnout logic.
Synchronise coil current with trip output, DC voltage, 52a/52b and main-contact timing for diagnosis.
Use trending as condition evidence, not an automatic condemnation without OEM limits and repeatable measurement setup.

8. Dual trip coils and dual DC supplies

Use separate branch protection, cables/terminals, relay outputs and TCS channels for each claimed independent path.
Map which protections, lockout, manual emergency trip and BF retrip use TC1 and TC2.
Check common mechanism, latches, 52 contacts and breaker plug—two coils do not remove all common modes.
Prevent TCS resistor/opto paths from cross-feeding DC-A and DC-B with one supply isolated or earthed.
Label alarms precisely: “Q1 TC1 circuit fail / DC-A,” “Q1 TC2 circuit fail / DC-B.”
Define degraded operation: one coil failed may allow controlled continued service, close inhibit or immediate outage depending risk/redundancy.
Test each coil with the other DC supply physically isolated, then both energised and each pole-earth scenario.

9. Withdrawable breaker and secondary-plug logic

Place the secondary plug and flexible truck wiring inside the monitored boundary wherever feasible.
Use service/test/disconnected indications with plausibility; do not mask TCS on a single unreliable position contact.
In TEST, prove the actual trip coil and mechanism without energising the primary circuit.
In DISCONNECTED/removed, distinguish an expected unavailable trip path from an unexplained failure; show “breaker removed/TCS unavailable,” not “healthy.”
Check 52a/52b operation in test and service, including contact timing relative to main contacts.
Inspect plug pin retention/contamination and flexible conductors as high-probability intermittent defects.

10. Alarm delay and operating response

The pickup delay must ride through the normal interval when 52a/52b change and the trip output energises, including worst breaker time and contact bounce. It must still expose a real open circuit before the next credible fault demand. Use measured transition plus relay/input tolerance; do not apply one delay to every breaker type.

Alarm state	Required response example
One of two independent coils failed	Immediate annunciation, maintenance deadline, verify healthy alternate; close policy per risk
Only trip path failed while breaker closed	Critical alarm; controlled de-energisation using upstream/alternate breaker
Breaker open, trip unavailable	Close inhibit until repaired unless authorised risk process says otherwise
Momentary TCS dropout	Latched SOE/maintenance event plus present-state indication
TCS device/internal supervision failed	Declare path “not supervised,” never default to healthy

11. Digital/remote-I/O implementation

Model present circuit state, latched alarm, breaker/rack position and data quality separately.
For remote binary I/O, include its DC supply, field wetting voltage, input threshold, GOOSE/network and configuration in the availability claim.
Stale/invalid quality must become “unknown/unavailable,” not healthy.
Secure configuration inversion and alarm masking under change control.
Synchronise TCS, trip output, coil current, 52 contacts and main-contact/breaker current events for diagnosis.
Test restart, loss/recovery of communications, redundant path switchover and firmware/settings updates in all breaker states.

12. TCS does not replace 50BF

TCS can alarm an open trip coil before a fault, but it cannot guarantee the breaker mechanism or interrupter will clear. BF starts on an actual protection trip and checks current/position persistence; it must isolate adjacent/upstream sources if clearing fails. A mature scheme uses continuous TCS, periodic dynamic trip tests and 50BF as three distinct layers.

13. Design specification checklist

breaker, trip-coil and station-DC min/nominal/max/boost data;
guaranteed coil pickup/non-operate, resistance/temperature and duty;
exact monitored boundary in every breaker/rack/output state;
TCS input/relay pickup/dropout, impedance, tolerances and delay;
limiting resistor value/tolerance/temp coefficient/continuous/pulse/voltage rating;
dual-coil/DC isolation and common-mode analysis;
alarm text, priority, latching, close inhibit and degraded-mode response;
50BF interaction, retrip coil and lockout;
field/remote I/O quality and communication failure behaviour;
FAT/SAT point-open, worst-DC trip and periodic test requirements.

14. FAT/SAT point-open matrix

Trace the supervision loop on the as-built schematic for every state and mark its limits.
Measure minimum/nominal/maximum DC assumptions and actual monitor current/voltage.
Open DC fuse/MCB, each positive/return link, relay/output bypass, interposing/lockout contact, terminal, field core, plug pin, 52a/52b path and coil lead separately.
Insert controlled resistance to find TCS dropout and compare with maximum trip-loop resistance.
At maximum DC/minimum resistance, prove monitoring path cannot operate or heat the coil/resistor unsafely.
At minimum DC/maximum resistance, trip and record coil voltage/current, mechanism/main-contact timing and successful clearing.
Operate breaker repeatedly; validate alarm delay through 52 contact transitions.
Test service/test/disconnected/removed positions and invalid position contacts.
Test dual coils independently with alternate DC isolated, both energised and cross-feed/earth-fault checks.
Fail TCS auxiliary supply/input, remote I/O, GOOSE/network and configuration quality; verify “unavailable,” not healthy.
Verify exact SCADA/SOE text, latch/reset, close inhibit and maintenance bypass indication.
Restore all links/fuses/test switches and perform final end-to-end trip from protection to breaker.

15. Maintenance strategy

continuously alarm present/latched TCS state and monitor DC earth/voltage separately;
trend monitor current and trip-coil signatures where available;
periodically test open-circuit detection at representative field endpoints, not only inside the relay;
trip each coil/path at controlled intervals and worst practicable DC, measuring breaker timing;
inspect plugs, flexible truck wiring, terminals and resistors for heat/mechanical damage;
recalculate supervision window after coil, relay input, resistor, DC range or wiring changes;
investigate every momentary TCS dropout with SOE/coil current instead of increasing delay blindly.

16. Frequent mistakes

Mistake	Consequence	Correction
Green lamp = whole trip chain healthy	Coverage overstated	State-by-state boundary claim
Continuity = low resistance	Coil starves on real trip	Voltage/current test at minimum DC
Copied resistor	Monitor blind or coil creeps/trips	Worst-case feasibility calculation
One TCS for two coils	Failed path hidden/common mode	Independent monitoring and alarms
Breaker removed shown healthy	Unavailable protection masked	Explicit unavailable state
No TCS self-failure mode	Monitor dies silently	Self-supervision/fail-to-unknown
TCS used instead of BF	Mechanical/interruption failure uncleared	50BF current-supervised backup

References and further reading

Engineering note: A TCS manufacturer circuit is authoritative for its input and resistor arrangement. Recalculate and retest after any coil, DC, cable, relay or auxiliary-contact change.