A drive tripped — first steps before you call anyone

What to record, what to check, and why repeated blind resets are the one thing not to do.

A drive trip is the machine protecting itself — and leaving you evidence. The minutes after a trip decide whether that evidence survives. This is a general first-response sequence used in many plants; your own site procedures and the equipment manual always take precedence.

1. Record before you reset

Photograph the fault code on the display, and note the time, the operation in progress and anything unusual before the trip — noises, smells, a heavy load step, a supply dip elsewhere in the plant. Many drives keep an internal event log, but the on-screen code plus operating context is the fastest evidence there is.

2. Do not reset repeatedly

One reset after understanding the code may be reasonable, depending on the fault type and your procedures. Repeated resets against a persistent fault are how minor failures become major ones: each restart into a real fault can stress power components further and can erase the pattern a diagnostician needs. If the fault returns, stop and escalate.

3. Check the environment

• —Temperature — is the room or cabinet unusually hot? Are fans running, filters visibly blocked?
• —Water and moisture — leaks, condensation, recent washdowns near the cabinet.
• —Dust events — recent works, material spills, visible accumulation on vents.

4. Check what changed

Many "drive faults" begin outside the drive. Supply-side events, a mechanical change in the driven load, new cabling, parameter changes, or work on nearby equipment are all worth noting. You are not diagnosing — you are preserving the context a diagnosis will need.

5. Escalate with the evidence

A service request that contains the exact fault code, the operating context, the environment observations and nameplate photos lets a service team arrive prepared — or resolve remotely what can be resolved remotely.