ABB IRC5 Drive Unit Overcurrent Alarm: Causes and Fixes

Published: 2026-09-10 · By SongWei Robotics Engineering Team · Reviewed by a senior robotics service engineer

A practical troubleshooting guide for maintenance engineers, integrators, and procurement teams.

If your ABB IRC5 controller has just stopped mid-cycle and the FlexPendant is showing an overcurrent alarm, this guide will help you answer three questions fast: what the alarm actually means, how to find the root cause, and whether you should repair or replace the drive unit.

All alarm descriptions below are verified against the official ABB Operating manual – Troubleshooting IRC5 (document 3HAC020738). We work on these systems every day — SongWei Robotics provides tested replacement drive units, repair services, and remote technical support for ABB IRC5 controllers worldwide.

Key Takeaways (TL;DR)

• “Overcurrent” on the IRC5 is a family of alarms, not one single code. The most common ones are 34309 (drive transistor current too high), 34316/34317 (motor current error), 34303/34304 (motor current warning) and 34311/34318 (drive converter saturation). Each points to a slightly different layer of the drive system.
• In the majority of field cases, the root cause is outside the drive unit itself: a damaged motor power cable, a motor winding fault, an incorrect motor configuration, a mechanical overload/collision, or a supply problem on the DC link.
• Diagnose before you swap modules. A 30-minute structured check (event log → configuration → cable resistance → motor insulation → DC link) tells you whether the drive unit is actually the failed component.
• Repair is worth considering when the fault is isolated and recoverable; replace when the unit is physically damaged, repeatedly failing, or downtime cost dominates.
• Never work on the drive system without disconnecting mains power, locking out the supply, and allowing the DC link capacitors to discharge.

1. What “Overcurrent” Actually Means on an IRC5

The IRC5 drive system converts the controller’s regulated DC bus power into precisely controlled three-phase current for each robot axis servo motor. Every drive unit continuously monitors the current through its output transistors (IGBTs) and the torque/current deviation of the motor it drives. When measured current exceeds what the hardware or the configured motor data allows, the controller reacts within milliseconds: it drops to Motors Off to protect the transistors, the motor, and the mechanics.

That protection trip is what you see on the FlexPendant. The exact event log code tells you which protection fired:

1.1 The overcurrent alarm family (verified against ABB 3HAC020738)

1.2 Alarms that travel with overcurrent events

2. How the IRC5 Drive System Is Built (and Why It Matters)

You cannot diagnose an overcurrent alarm efficiently without knowing the power chain. When any one of these layers misbehaves, the symptom ends up looking the same on the FlexPendant — a current alarm.

The chain is only as strong as its weakest link. Overcurrent protection lives in the drive unit, but the cause can sit anywhere from the mains filter to the gearbox. That’s why ABB’s own recommended actions for alarm 34309 are ordered the way they are: check the motor configuration first, then the collision/load question, then measure cable and motor resistance — and only then condemn the drive unit.

3. Root Causes, Ranked by Field Frequency

Based on service cases we see on IRC5-controlled robots (IRB 120/140/1600/2400/2600/4400/4600/6600/7600 families), the realistic distribution for overcurrent-family alarms is roughly:

4. Step-by-Step Diagnosis

4.1 Read the event log like an engineer

On the FlexPendant, open the event log and answer four questions:

• Which joint/axis is named in the alarm (the arg fields)? One axis or several?
• Is it a single 34309 event, or a sequence (e.g., 34303 warning → 34316 error)?
• Are there coinciding 342xx (rectifier/mains) or 344xx (DC link) codes?
• Did anything change recently — motor swap, drive unit swap, restored backup, new tooling, a crash?

A single-axis 34309 that repeats on the same physical move points to cable or mechanics. A 34316 that appeared immediately after a drive unit or motor replacement points to configuration. Multi-axis simultaneous alarms with 344xx codes point to the supply/DC link.

4.2 Check the motor configuration

Per ABB’s recommended action for 34309/34316: verify the motor data in the configuration file for that joint. If a drive unit, motor, or complete controller was recently replaced or a backup was restored, the configured motor data may not match the hardware. Compare the system’s motor type data against the actual motor nameplate and the robot’s product manual. A mismatch here can make a perfectly healthy system trip overcurrent on every acceleration.

4.3 Rule out collisions and overload

The ABB manual explicitly lists axis load too high or motor stalled (possibly due to collision) among the causes for 34309. Inspect the robot and cell for collision marks, check whether the payload or tooling changed, and verify the gripper/workpiece is not jamming the axis. If the alarm occurs at the same program line every time, jog that axis manually at low speed and listen/feel for mechanical binding.

4.4 Measure the motor cable and the motor — separately

This is ABB’s own recommended test, and the single most valuable step. Disconnect the cable before measuring — you need to test the cable and the motor independently:

• Cable: measure phase-to-phase resistance and each phase-to-ground resistance, both at the drive end and, if possible, with the cable disconnected at both ends. Look for phase-to-phase shorts, phase-to-ground shorts, and inconsistent readings between phases. Flex the dress pack while watching the meter — intermittent faults hide in moving cable tracks.
• Motor: with the motor power cable disconnected at the motor side, measure the winding resistance phase-to-phase. The three phase-pairs should read consistently with each other (compare against the motor’s datasheet value if available). Then check insulation resistance phase-to-ground with an appropriate insulation tester per the motor manufacturer’s specification. A low insulation value is a failed motor, not a drive problem.

4.5 Check the supply and DC link side

If the event log shows 34251/34252/34411/34400 alongside the current alarms:

• Verify the incoming mains voltage is within the specification for your cabinet (and that the transformer jumper, where applicable, is set for the correct voltage — ABB lists this among the recommended actions for supply-related alarms).
• Check for loose or burnt DC bus connections and cabling between the rectifier and the drive units.
• The ABB troubleshooting manual covers the system power supplies (DSQC 604 / DSQC 661 / DSQC 662) with dedicated procedures — e.g., DSQC 604 outputs should measure +24 V < U < +27 V DC, and its AC input 172–276 V (per the official troubleshooting flowchart). Use those procedures to confirm the 24 V systems that the drive infrastructure depends on.

4.6 The structured diagnostic flow

5. Cause – Symptom – Diagnosis – Fix Table

6. Repair vs. Replace: Making the Right Call

When the diagnosis lands on the drive unit itself, the next question is commercial as much as technical. Here is the decision framework we use:

6.1 Replacement considerations specific to IRC5 drive units

• Type matching matters. The IRC5 checks drive unit hardware identifiers against the configuration. The ABB manual (alarm 34313, “wrong drive unit type”) notes that the installed drive unit’s hardware ID must match the configuration — so a replacement must be the correct unit type for that drive module slot, and the system configuration may need to match the installed hardware.
• After any swap, re-verify motor data and run a test before returning to automatic production.
• When replacing, ask your supplier how the unit was tested: at minimum, power-up, self-test, and a load test on a test bench. Ask about the warranty terms for both new and refurbished units.

7. Prevention: Keeping Overcurrent Alarms Away

1. Cable management is half the battle. Inspect dress packs and cable tracks on a schedule. Replace cables at the first sign of jacket damage — an intermittent short always degrades into a hard fault.
2. Keep the event log clean. Investigate every 34303/34304 warning. Warnings are free diagnostics; a stop error costs a shift.
3. Respect the thermal envelope. Overcurrent families travel with overheating families (34306/34307/34308): keep cabinet fans running, clean cooling fins and filters, and verify ambient temperature stays within the cabinet rating.
4. Document every configuration change. Motor or drive swaps and backup restores are the #1 self-inflicted cause of current alarms through wrong motor data.
5. Collision detection and reduced-speed validation. After any mechanical incident, jog axes at low speed and verify motion before running automatic production.
6. Periodic electrical health checks. A yearly winding-resistance and insulation check on each axis motor, and resistance checks on power cables, catches degradation before it trips production.
7. Watch the supply. If your plant sees phase imbalances or brownouts, expect 34251/34411 events — consider supply monitoring as part of the robot cell.

8. Related Products and Spare Parts (Request a Quote)

The following IRC5 drive-system components are the ones most often involved in overcurrent-related repairs and preventive maintenance. No prices are shown — every inquiry is quoted individually based on condition, availability, and destination.

9. FAQ

What does alarm 34309 mean on an ABB IRC5?

34309 means “Drive transistor current too high” — the current through the drive unit’s output transistors for the named joint exceeded the allowed limit, so the system went to Motors Off. Per the ABB troubleshooting manual, the most common causes are an incorrect motor configuration, an overloaded or stalled axis (e.g., after a collision), or a short circuit between motor phases or to ground.

What is the difference between 34303/34304, 34316/34317, and 34309?

34303/34304 are warnings: the current controller detected an excessive torque-current/current deviation but operation continues — you are close to a stop error. 34316/34317 are errors of the same type and stop the system. 34309 is a transistor-level overcurrent: it fires faster and points more directly at hard shorts, stall conditions, or configuration errors. Treat any of them as a reason to diagnose before continuing production.

My IRC5 shows overcurrent only on one specific move. What does that suggest?

A position- or motion-dependent fault strongly suggests the motor power cable (damage in the dress pack/cable track) or mechanics (binding in that portion of travel). Measure the cable phase-to-phase and phase-to-ground while flexing the track, before suspecting the drive unit.

The alarm appeared right after we replaced a drive unit. Did we get a bad unit?

Not necessarily. The IRC5 validates drive unit types and motor data against the system configuration. A mismatch between the installed unit, its slot, or the configured motor data will produce current alarms on a perfectly good unit. Verify the configuration first (alarm 34313 “wrong drive unit type” and the motor data checks cover this).

Can I just reset the alarm and keep running?

You can acknowledge the alarm, but if the root cause remains, it will trip again — and repeated overcurrent events stress the drive unit’s transistors and the motor. A 34303/34304 warning that’s ignored often becomes a 34316 stop error within days. Diagnose it once, properly.

Should I repair or replace a faulty IRC5 drive unit?

If the fault is isolated, the board is in good condition, and downtime allows it, professional repair plus bench testing is usually the economical route. Replace when the unit is physically damaged, has failed repeatedly, or the line cannot wait. See the decision framework in Section 6.

Do you supply tested replacement drive units for IRC5?

Yes — SongWei Robotics supplies new and refurbished IRC5 drive units (e.g., DSQC663, 3HAC025338 family) and related modules, with warranty, and can quote repair of your faulty unit. Use the inquiry form below or contact our engineers with your controller and event log details.

What information should I send when requesting support for an overcurrent alarm?

Robot model (IRB type), controller type and RobotWare version, the exact alarm codes and the joint numbers from the event log, when the fault occurs (Motors On / specific move / random), and any recent changes (motor, drive unit, backup restore, payload change). Photos of the event log help.

References

1. ABB, Operating manual – Troubleshooting IRC5, document 3HAC020738 — event log messages 34303, 34304, 34306–34309, 34311–34313, 34316–34318, 34251, 34265, 34411, 34400; troubleshooting procedures for DSQC 604, DSQC 661, DSQC 662.
2. ABB Robotics — IRC5 controller overview and documentation, new.abb.com/products/robotics.
3. ABB, Product manual – IRC5 (circuit diagrams, unit locations, DC link specifications).