Model-level fault code lists for the drives, PLCs, servo packs and machine tools we guide on most. Each list covers the alarm classes you are most likely to meet, what they commonly mean, how likely each cause is, and the first remote check to run — plus a link to the official manual. We guide remotely; we do not perform physical hardware repair.
Overvoltage, ground fault and drive fault lists with likelihood ratings and the first remote check for each condition.
Diagnostic buffer events, LED patterns and program alarms — including the error-code-401 internal error path.
Overcurrent, communication and drive fault classes with the parameter-side checks that resolve most of them.
Servo alarm classes, following error and overcurrent conditions with the tuning and feedback checks behind them.
Major and minor faults, recoverable conditions and what the controller's fault log tells you about each.
CPU faults and Ethernet communication errors with the addressing and configuration checks that clear them.
Alarm 123 axis servo, overtravel and alarm-history patterns for the VF series — with load-based checks.
Spindle overload (SP9029), servo alarms and PMC ladder messages — read through load trends, not guesswork.
No-start conditions, latched faults and control-source mismatches — the enable-chain checks that resolve most.
For the deep walkthroughs behind these codes: browse by equipment type, by symptom or by control technology.
A fault code names a condition, not a broken part. The same code can be raised by a loose cable on one machine and by a drifted parameter on another — which is why every entry in our lists pairs the code with a likelihood and a first check, rather than a verdict.
If your machine is down and the cost of guessing wrong is high, start from the troubleshooting library or submit the case with a photo of the fault screen.
Codes describe a condition detected by the drive or controller, and that condition depends on the wiring, the application and the parameters around it. A ground-fault code on one ACS580 may be a chafed cable; on another it is an insulation issue in the motor. Context — when it appears and what changed — is what turns a code into a diagnosis.
Only after reading it. A cleared-but-unread fault list is the most common reason an intermittent fault becomes a weekend outage. Read the list, photograph it, then clear — and if it re-latches, that re-latch is itself diagnostic evidence.
Yes. The lists cover the alarm classes we see most often; they are not the manufacturer's complete registry. Submit the exact code, the model and a photo of the screen — a specialist will interpret it against the official documentation and the field pattern.
Submit your case with the model, the exact code and a photo of the screen — we'll connect you with a specialist for remote diagnostic and guidance.
We do not perform physical hardware repair, we do not replace parts or components, and we do not guarantee that every fault can be resolved. Our service is remote diagnostic and operational guidance only.