A consolidated reference for the Schneider ATV320 fault codes you are most likely to trip, with the common remote-checkable cause for each and the menu to verify before you consider a replacement drive.
The ATV320 shows a letter fault code on the display together with a stored fault history you can walk through on the drive keypad. Pairing the displayed code with the live values (output current, bus voltage, speed) and the recent-change log is how a remote specialist separates an application issue from a genuine hardware fault.
| Fault source | Where you see it | What it tells you |
|---|---|---|
| Displayed code | ATV320 keypad | The letter code that classes the trip |
| Fault history | Drive menu (Fault history) | Recent codes in sequence with timestamps |
| Live values | Monitoring menu | Output current, bus voltage, motor frequency at the moment |
The table lists the most common ATV320 codes, their meaning, and the first remote check. Likelihood reflects field frequency.
| Code | Meaning | Likelihood | First Remote Check |
|---|---|---|---|
| OCF | Overcurrent — output current above rating | High | Note output current trend; check for a jam, winding fault or wrong motor data |
| PHF | Input phase loss — mains missing a phase | Med–High | Check line voltage and input fuses/contactor at the moment of trip |
| USF | Undervoltage on DC bus — supply too low | Med | Verify AC line voltage and input supply; look for a droop or sag under load |
| OPF | Output phase loss — motor cable or winding broken | Med | Confirm all three motor phases and the motor cable continuity |
| OLF | Motor overload — thermal protection tripped | Med | Check motor current vs nameplate and the load profile over time |
| OSF | Overspeed — speed exceeded the limit | Low–Med | Review the speed reference and the deceleration; check for an unstable reference |
| SCF | Short circuit — output or braking circuitry | Low | Isolate the motor cable and confirm with insulation checks before deciding |
Several ATV320 codes share a root cause family. Reading the output current, bus voltage and the fault history sequence together is what identifies the actual trigger.
Work through these in order. Each step is something you can perform and report back on without opening the drive or removing parts.
Note the displayed code and the fault history sequence. The code's position in the sequence tells you which trip started it.
Note output current, bus voltage and frequency around the trip. Overcurrent vs undervoltage vs phase loss is told apart by these numbers, not the code alone.
Was there a parameter change, a motor swap, a wiring edit or a mains event right before? Recent-change logs usually reveal the trigger.
Confirm the motor nameplate data and the deceleration/ramp settings match the load. Parameter or drive-configuration errors are common one-shot trip causes.
After aligning parameters and confirming the supply path, reset and verify the drive holds without a repeated trip for a sustained run.
An ATV320 trip is an overcurrent, supply or phase-loss path more often than a board failure. Cross-reference the specific conditions: Overcurrent fault · Communication error · All motor/drive symptoms · VFD technology.
OCF is an overcurrent fault — the drive detected more output current than allowed. Common remote-checkable causes include motor winding faults, wrong motor nameplate parameters, or a mechanical jam. It is often recoverable without swapping the drive.
PHF is input phase loss and USF is DC bus undervoltage — both supply-side issues you can check remotely from line voltage and input fuses/contactor, and not usually a drive hardware failure.
Yes. Share the fault code, drive menu values and what changed; a specialist interprets the code and guides recovery. We never take control of your drive.
Send the fault code, fault history and live values. We interpret it and guide recovery remotely — no drive replacement unless it is genuinely required.
Submit Your Case Connect With SpecialistsWe do not perform hardware repair, we do not replace parts, and we cannot promise a 100% resolution. Our role is limited to remote diagnostic and step-by-step guidance based on the information, photos and logs you share.
The most common trip path in detail.
When the drive drops off the fieldbus or HMI.
A related drive fault reference for another vendor.
Full drive and controller troubleshooting collection.