QualifiedMedium risk

Whole circuit / board nuisance tripping

A whole circuit or board protective device trips intermittently with no obvious single cause — affecting several loads — and you need a systematic way to corner it.

Safety first

Repeated tripping protects against a real fault. Don't bypass or upsize protection. Isolate before working and be ready for loss of supply to multiple loads.

Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.

Full detail — causes, the why, and common mistakes.

Likely causes

Ranked from most to least likely.

  1. 1

    One intermittent faulty load among several

    Most likely

    A single appliance/circuit with an intermittent fault trips the shared device only sometimes.

  2. 2

    Cumulative loading/leakage near the limit

    #2

    Combined load or leakage sits near the device threshold and trips on peaks.

  3. 3

    Event-triggered (a specific load switching)

    #3

    The trip happens when a particular load switches (inrush/leakage spike).

  4. 4

    Loose connection / shared neutral

    Least likely

    A loose connection or shared-neutral issue causes intermittent faults.

Reports are saved on this device to reflect what you actually find.

Testing sequence

Work through one test at a time. Expected reading and what each result means.

Test 1 of 3
1

Log each trip with what was running/switching at the time to find a correlation.

Expected reading

A correlation between trips and a load/event.

If it passes

Correlated to a load/event — target that.

If it fails

No correlation — split the board/circuit to divide and conquer.

View all expected readings at once
1. Log each trip with what was running/switching at the time to find a correlation.
A correlation between trips and a load/event.
2. Divide the circuits/loads into groups; run with half connected to narrow down which half holds the fault.
The fault follows one group, narrowing the search.
3. On the suspect load/group, test for the specific fault (insulation, current, connections) per its nature.
A definite fault on the suspect load/connection.

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    Board nuisance tripping

    → step 2
  2. 2
    decision

    Does logging correlate trips to a load/event?

    Yes→ step 3No→ step 4
  3. 3
    result

    Target the correlated load/event.

  4. 4
    decision

    Does dividing the load localise the fault to a group?

    Yes→ step 5No→ step 6
  5. 5
    result

    Subdivide further to the culprit, then test that load.

  6. 6
    result

    Trips with all split off — examine shared wiring/neutral/device.

Common mistakes apprentices make

  • Upsizing or bypassing the protection instead of finding the fault.
  • Not logging what's running when it trips.
  • Testing everything at once instead of dividing the load.
  • Forgetting shared-neutral and loose-connection causes.

When to stop & escalate

If the device itself is at fault or the loading is genuinely at the limit by design, that's a review rather than a quick fix. Never defeat the protection to stop nuisance trips.

If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.

Related faults

Learn the theory

How the gear and circuits behind this fault actually work.