Key takeaways
When a machine stops, the clock starts. This index collects all of our troubleshooting guides in one place so maintenance technicians and plant engineers can jump straight to the fault in front of them, whether it is a Fanuc alarm, a tripping overload relay, or a conveyor that will not track.
Control alarms tell you which subsystem raised the fault before you open a single cabinet. Start with the guide for your control family:
Variable frequency drives and servo systems fail with the same physics across every brand: overcurrent means shorts or jams, overvoltage on deceleration means regeneration, overtemperature means cooling.
Mechanical failures announce themselves early in noise, vibration, temperature, and backlash. These guides cover reading those signals and deciding repair versus replace:
Hydraulics, pneumatics, and the utility room fail quietly: pressure sags, moisture creeps in, seals weep. These guides cover the diagnosis:
Each guide follows the same structure, because good troubleshooting is a discipline, not a memory test. Read the alarm or symptom precisely and write it down before clearing anything. Work the causes in order of likelihood, cheapest checks first. Respect stored energy: lock out and tag out, verify zero energy, support suspended loads, and never bypass interlocks or safety devices.
One caution applies everywhere: exact code meanings differ by model, series, and firmware. These guides give you the diagnostic logic and the commonly documented patterns; the manufacturer manual for your specific machine is always the final authority.
The plants that stop fighting the same faults share one habit: every stop becomes a data point. Log each fault as a downtime event with a cause code, and track MTBF and MTTR per asset. A sensor that fails monthly, a coupling that dies every quarter, a chronic low-air alarm: the pattern only becomes visible, and fundable, when it is counted. That is the availability side of OEE for manufacturing, and it is where troubleshooting stops being firefighting and becomes reliability engineering.
Most of the faults in these guides announce themselves as short stops nobody writes down. Fabrico is computer-vision-verified OEE plus closed-loop maintenance execution: cameras catch stops and micro-stops that manual logs and sensors miss, and maintenance work orders close the loop from detection to fix, so every fault in this index becomes a counted, categorized event with a repair history. Book a Fabrico demo to see it on your own machines.
Start with the guide for your control or drive family above to understand the fault category and first checks, then confirm the exact code in the manufacturer's alarm or fault list for your specific model and firmware. Never act on a guessed code meaning.
Record the complete alarm text, code, and axis or device identifier before clearing anything. The alarm history and the fault's context are diagnostic gold, and they disappear with the reset.
When the fix requires opening drive cabinets beyond your qualification, when safety devices are involved, when the fault points to control hardware or firmware, or when a documented recovery procedure requires OEM tooling. A good fault log makes that call cheaper and faster.
Because the repair addressed the symptom, not the cause: the misalignment behind the coupling failure, the contamination behind the valve jam, the undersized air supply behind the pressure faults. Logging every occurrence with a cause code is what exposes those patterns.
Connexion
Blog
