ABB IRC5 Robot Intermittent Axis Alarm: How to Troubleshoot in Sequence
Learn about recording, connection checks, cause classification, and restart verification methods for ABB IRC5 robot intermittent axis alarms to avoid judging motor, drive, or cable damage based on a single alarm.

In this article
When an intermittent axis alarm occurs on an ABB IRC5 robot, it may involve the power supply, connections, cables, feedback, drive, or mechanical system. Before troubleshooting, complete alarm codes and text, occurrence time, faulty axis, robot posture, program step, and load conditions should be saved. A single axis alarm only indicates that the control system detected an abnormality; it alone cannot prove that the motor, drive module, or robot cable is damaged. This article focuses on the diagnostic sequence when a specific alarm code is not yet determined and does not replace technical instructions for a particular ABB alarm code.
Fault Phenomenon and Scope of Application
This article applies to ABB robots using the IRC5 control system that occasionally or repeatedly experience axis-related alarms during operation.
Common manifestations include:
1. The robot can temporarily resume operation after the alarm is reset;
2. The same alarm reappears during specific postures or movements;
3. The alarm consistently points to the same axis;
4. Multiple axes generate abnormalities simultaneously;
5. Axis alarms are accompanied by power, communication, or feedback-related information;
6. The robot temporarily recovers after a restart but alarms again after running for a period.
If the equipment cannot complete startup, or if a complete alarm code has been obtained, priority should be given to consulting the corresponding controller version and ABB technical documentation for the definition and inspection requirements of that code.
Fault Recording Checklist
Establish a unified record before troubleshooting to avoid losing important information after reset or restart.
Complete alarm code: Code and full text from the ABB event log
Occurrence time: Date and precise time
Faulty axis: Axis number involved in the alarm
Robot posture: Position and posture at the time of fault occurrence
Program step: Program segment or action being executed at that time
Speed and load: Actual operating conditions
Reset possible: Reset operation and result
Time of reoccurrence: How long after resuming operation it appears again
Associated alarms: Power, communication, or feedback alarms appearing simultaneously
These records are used to determine whether the fault occurs randomly or is related to a fixed posture, movement direction, program step, or operating condition.
Safety and Inspection Preparation
Inspectors should first confirm the robot model, IRC5 controller model, system version, and relevant component labels.
All observation, testing, and disassembly work should follow the operating documentation for the corresponding equipment and on-site safety procedures. Actions that may expand mechanical, electrical, or equipment risks should not be repeatedly performed to reproduce the fault.
When component disassembly, electrical measurement, or control parameter checks are required, they should be performed by personnel with appropriate capabilities according to applicable ABB technical documentation. This article does not provide generic values lacking equipment scope, measurement locations, and measurement conditions.
ABB IRC5 Intermittent Axis Alarm Diagnostic Sequence
Step 1: Verify Complete Alarm Information
Save the complete alarm code, alarm text, occurrence time, and associated events from the IRC5 event log.
Do not only record abbreviations like "axis alarm," "motor alarm," or "drive alarm." Similar phenomena may correspond to different event codes and system scopes.
If power, communication, or feedback information exists before or after the alarm, retain the complete sequence according to the occurrence time. A later-appearing axis alarm may be the result of a preceding system abnormality.
Step 2: Confirm Equipment and Component Scope
Record the complete ABB robot model, robot serial number, IRC5 controller model, control system version, axis number involved in the alarm, relevant drive, motor, or cable labels, and confirm whether components have been replaced or configurations modified recently.
Different robots, controller versions, and component revision states may correspond to different inspection requirements, so conclusions from other equipment cannot be directly copied.
Step 3: Check External Connections and Visible Abnormalities
After the equipment is in a state compliant with on-site safety requirements, check the control cabinet's external connections, robot base interface, and cable areas that can be safely observed.
Focus on recording whether connectors are loose, fixing mechanisms are abnormal, cable sheaths are cracked or crushed, plugs are contaminated or have liquid ingress, cable harness fixing positions have changed, and whether the fault appeared after maintenance, relocation, or component replacement.
When visual abnormalities are found, save clear photos of component labels and abnormal locations. Normal visual inspection does not prove that internal cable conductors, feedback lines, or connection contacts are completely normal.
For inspections involving the IRC5 control cabinet scope, refer to the ABB IRC5 Control Cabinet Inspection and Repair page:
https://autonews.best/zh/products/abb-irc5-kong-zhi-gui-yu-ji-xiu
Step 4: Analyze Fault Occurrence Conditions
Under conditions compliant with ABB operating documentation and on-site safety procedures, and by personnel with appropriate capabilities, observe in a controlled environment whether the alarm is related to specific postures or movement directions. Do not repeatedly perform actions that may expand equipment risks to reproduce the fault.
If the alarm only appears near a fixed posture, record the robot position, movement direction, and related harness status, and further check for loose connections, harness pulling, or mechanical interference.
If the alarm mainly appears during acceleration, deceleration, or load change phases, continue judgment based on actual load, mechanical status, brake status, and drive chain. This phenomenon alone cannot prove drive module or motor damage.
If multiple axes alarm simultaneously, first check shared power supply, controller status, and associated events; do not directly conclude that multiple axis components have failed simultaneously.
Step 5: Distinguish Different System Causes
Power Supply Causes
Check whether power-related events exist simultaneously when the alarm occurs and whether the fault affects multiple drives or axes. Specific measurement locations, normal ranges, and test conditions should be based on the corresponding IRC5 controller documentation.
Cable and Connection Causes
If the fault is related to robot posture, vibration, or harness movement, check connector fixation status, cable routing, and visible damage.
Communication or Feedback Causes
Judgment should be based on the complete alarm code, event sequence, relevant connections, and controller records. The sole occurrence of axis stop, jitter, or recovery after reset cannot prove that feedback-related components are damaged.
Drive Causes
Only after power supply, connections, configuration, communication, and mechanical factors have been checked accordingly can the drive module be further evaluated. Component-level judgment requires corresponding model documentation and testing conditions.
Mechanical Causes
Mechanical resistance, brake abnormalities, transmission component status, or load conditions can all affect axis operation. Abnormal sounds or alarms in specific directions can serve as diagnostic clues but cannot alone determine the faulty component.
When to Consider Repair or Replacement
Only when alarm records, fault conditions, connection checks, and component testing collectively point to a specific object is it appropriate to evaluate repair or replacement.
When involving motors, drive modules, feedback-related components, or robot cables, verify the complete model, complete part number, hardware revision version, label identification information, connector count and layout, applicable robot and controller models, and photos of the original component's front, back, and interfaces.
Similar appearance, same number of interfaces, or belonging to the same series alone cannot prove that two components are interchangeable.
Verification After Repair or Replacement
After processing is complete, personnel with appropriate capabilities should perform restart verification under controlled conditions according to ABB operating documentation and on-site safety procedures.
During verification, check whether the original alarm can be cleared normally, whether new associated alarms appear in the event log, whether the involved axis can operate smoothly under permitted conditions, whether abnormalities reappear under the original fault conditions, whether connectors and harnesses experience pulling or interference, and whether the original program, configuration, and safety functions remain normal.
Do not repeatedly perform actions that may expand equipment risks to prove the fault is resolved. The verification process should record operating conditions, duration, and event log results.
Common Diagnostic Errors
1. Only recording the alarm number without saving the complete alarm text;
2. Not exporting alarm history before clearing or restarting the device;
3. Ordering a drive or motor based solely on one axis alarm;
4. Ignoring posture, program step, and load at the time of alarm occurrence;
5. Using incomplete part numbers to find replacement components;
6. Disassembling components without recording original connections and configuration;
7. Considering short-term normal operation after reset as the fault being resolved.
Information Required for Repair Inquiry
ZHB provides independent industrial robot inspection, repair, and maintenance services and supplies related spare parts to overseas customers. When submitting an inspection or repair request, please prepare the robot model, controller model, complete alarm code and text, alarm history, fault occurrence conditions, relevant component labels, and clear photos to verify equipment scope and diagnostic direction.
ABB Robot Repair Service Page:
https://autonews.best/zh/abb-robot-repair
Conclusion
When an intermittent axis alarm occurs on an ABB IRC5 robot, complete event records should be saved first, followed by verifying equipment scope, external connections, fault occurrence conditions, and related systems.
Without specific alarm codes, equipment models, and technical documentation support, diagnostic conclusions should be limited to cause classification and inspection sequence, and should not directly declare that a specific drive, motor, or cable is damaged.
Need a part or repair assessment?
Share the robot model, part number, fault details and destination country with our team.
Contact our team ↗