Trip-free operation ensures that a breaker cannot be held closed by a close command when an opening command or release condition requires it to open. It is a mechanical and functional property distinct from anti-pumping.

Learning objectives

Distinguish trip-free from anti-pumping, understand simultaneous command behaviour and design a safe verification test.

Core engineering principles

Trip priority protects the fault-clearing function

When closing and opening commands coincide, the mechanism must not defeat the trip requirement. The exact response depends on the breaker design and timing of the commands.

Mechanical design matters

Trip-free behaviour is normally embedded in the latch and linkage so the main contacts cannot be held closed by maintaining the close release.

Anti-pumping acts after the first attempt

Trip-free ensures opening; anti-pumping prevents repeated re-closing from a maintained command. A scheme can have one property without correctly implementing the other.

Remote logic should not mask mechanical behaviour

PLC or relay logic can prioritise trip, but the breaker’s declared property must still be verified within its approved control arrangement.

Test timing must be controlled

Applying trip before, during or immediately after close can produce different traces. The procedure should define command overlap and expected final state.

Engineering application method

  1. Step 1: Review manufacturer definition and control diagram.
  2. Step 2: Define simultaneous and near-simultaneous test cases.
  3. Step 3: Apply close and trip commands through normal circuits.
  4. Step 4: Verify the breaker opens or remains open and cannot be held closed.
  5. Step 5: Confirm anti-pumping separately after the trip-free test.

Practical example

If a close pushbutton is jammed while protection energises the trip coil, trip-free design allows the breaker to open. Anti-pumping then prevents another close until the maintained command is removed.

Common mistakes

  • Using trip-free and anti-pumping as synonyms.
  • Testing only PLC command priority.
  • Holding coils energised beyond their duty.
  • Leaving command timing undefined.
  • Assuming final indication proves the mechanical sequence.

Design and review checklist

  • Does trip have effective priority?
  • Is behaviour mechanically supported?
  • Are overlapping commands tested safely?
  • Is coil duty respected?
  • Is anti-pumping verified separately?

Standards basis and official sources

Engineering note: Verify the contracted standard edition, amendments, manufacturer evidence and project-specific studies before applying these principles to a supplied assembly.

Similar Posts