What the 50056 alarm means

Actual torque on a joint is higher than commanded while at low or zero speed — the classic signature of a collision or a jammed arm. Our engineers run into this alarm every week on ABB IRC5 / OmniCore (RobotWare) controllers, and a single on-site inspection usually identifies the problem.

Most common causes

  • The arm really collided or is mechanically stuck
  • Brake on that axis failed to release
  • Incorrect load data making collision supervision too sensitive
  • Hardware fault in the drive or motor
Field note: In our repair stats the first cause has the highest hit rate, so confirm it first before digging further.

Step-by-step field fix

  1. Inspect the cell for an actual collision; if stuck, temporarily disable manual jog supervision and jog clear slowly
  2. Check the brake release circuit for that axis (K42/K43/K44 brake control lines on older cabinets)
  3. Verify the programmed load data matches the real tool
  4. Check the event log for accompanying drive hardware alarms
Safety first: For ABB 50056, this alarm family points at arm motion control: after a reset the arm can move unexpectedly, and anyone inside the working envelope is at strike and pinch risk. The self-serviceable action is Inspect the cell for an actual collision; if stuck, temporarily disable manual jog supervision and jog clear slowly; anything past that falls under the arm working envelope and needs a certified engineer.

How we diagnose motion alarms on site

ABB 50056 belongs to the motion & path family. On ABB 50056 the failing stage is DSQC drive modules (DSQC 600 generation; OmniCore drive units) on the IRC5 / OmniCore - the gap between command and execution: trajectory planning, joint limits, singularities, following error and mechanical resistance. We start reading ABB 50056 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.

The chain involved in ABB 50056 runs: program command -> trajectory planner -> joint targets -> servo execution -> actual position feedback -> deviation compare.

First check whether ABB 50056 only appears at one pose - A six-axis arm near wrist extension or near axis-5 zero has a Jacobian approaching singularity: tiny tool moves demand huge joint rates, and the controller either reports following error or the arm snaps through. When the report is alarms at one position and clean on another path, suspect the singular region first. The fix is not raising speed limits but routing around it: move the part, add an intermediate point, or pass the region in joint interpolation.

Field notes on this page cover ABB 50056 (Joint Collision); written by the Henghuan repair team, updated 2026-10-01.

Real Field Case

Machine: ABB IRB 1200-5/0.9 (2019)

Symptom: A 2019 IRB 1200 raised 50056 (joint collision) mid-cycle and stopped abruptly.

What we did: On site we found the gripper was physically interfering with the workpiece; we corrected the fixture, reset the collision-detection threshold and ran a collision check.

Result: It ran cleanly after removing the interference and we re-tuned the collision sensitivity; about 3 hours.

No luck? Hand it to the team that fixes this daily

Give us the alarm code, robot model and the action at the moment of the alarm, and our engineers can give you a quick read — phone or video remote diagnosis is free.

Get a Free Remote Diagnosis See Repair Services

Hotline: +86-20-39029800 · WhatsApp: +86-188-1886-2860

Related Motion & Path alarms

50204 — Motion Supervision (Collision Detection) Triggered
Same family: this code belongs to the Motion & path alarms family - the page collects all Motion & path-family codes we have handled, with the common inspection order and spares.
Other brands: we also keep field-fix libraries for Yaskawa · Universal Robots · Kawasaki and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the ABB 50056 alarm mean?

Actual torque on a joint is higher than commanded while at low or zero speed — the classic signature of a collision or a jammed arm. Our engineers run into this alarm every week on ABB IRC5 / OmniCore (RobotWare) controllers, and a single on-site inspection usually identifies the problem. ABB 50056 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "The arm really collided or is mechanically stuck".

QCan I clear a ABB 50056 alarm myself?

Whether ABB 50056 clears on its own depends on the outcome of "Inspect the cell for an actual collision; if stuck, temporarily disable manual jog supervision and jog clear slowly". Finish the flow with "Check the event log for accompanying drive hardware alarms" to confirm ABB 50056 - do not skip it. If that step is clean, the second most frequent cause on ABB 50056 is "Brake on that axis failed to release". After clearing ABB 50056, watch it for one shift. A second trip means stop and let an engineer arrive with the right test gear for the arm working envelope.

QFor motion alarms like ABB 50056, can you triage remotely first?

The commonest causes we see on ABB 50056 are "The arm really collided or is mechanically stuck, Brake on that axis failed to release, Incorrect load data making collision supervision too sensitive", so we stock the van against those. For ABB 50056 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For ABB 50056, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what ABB 50056 shows on the FlexPendant event log and system diagnostics, with the cabinet status LEDs and what the machine was doing - phone or video triage is free.

This page on ABB 50056 was written by the Henghuan Robotics repair team from field service experience. Alarm descriptions are our own summary for troubleshooting reference and may vary by controller and software version — when in doubt, check your ABB documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by ABB.