Why Is the Crusher Tripping?

Who this is for and what it does: a bench reference for the maintenance tech, plant electrician, or operator working a crushing and screening circuit that keeps dropping out. It helps you separate a real protective trip from a nuisance one, trace which upstream or downstream condition actually pulled the circuit offline, and decide what to check before you call anyone.

How to use this Keep it open at the panel or on your phone. When the circuit trips, resist the urge to just hit reset and walk away. Work the symptom you actually have, write down what the human-machine interface (HMI) or programmable logic controller (PLC) showed at the moment of trip, and follow the checks. The goal is a cause, not just a machine that runs until it trips again in twenty minutes. A trip is information. The protection did its job and told you something. A "nuisance" trip is not a lie. It usually means the threshold is set tighter than the real process needs, or a sensor is drifting, or a genuine fault is small enough that it looks like noise. Your job is to find out which.

First move: read the first-out, not the last alarm Most modern crusher control systems latch a first-out or first-fault record: the condition that fired first, before the cascade. This is the single most useful piece of data you have. When a crusher stops, everything downstream loses feed and everything upstream backs up, so within a second or two you can have ten alarms standing. Nine of them are consequences. One is the cause. Find the first-out timestamp on the HMI alarm history. Sort by time, oldest first in the trip window. If there is no first-out logic, look at the alarm with the earliest millisecond timestamp and treat downstream conveyor and feeder stops as secondary until proven otherwise. Log the exact trip value if the system captures it (motor amps, lube pressure in pounds per square inch, cavity level percent). "High amps" is a story; "412 A on a 380 A rated motor for 3 seconds" is evidence. If you take nothing else from this guide: chase the first event, not the loudest one.