What the 50204 alarm means

The path/collision supervision detected an unexpected force during motion and stopped the robot — either a real collision or supervision too sensitive for the current load. In our ABB service archive this alarm on IRC5 / OmniCore (RobotWare) systems shows up constantly, and the first on-site inspection almost always locates it.

Most common causes

  • Actual collision with fixture, part or guarding
  • Wrong or missing load data (tool/workobject)
  • Brake not fully released on an axis
  • Aggressive acceleration in a tight path
Field note: The first cause is the most common in the field — check it first, then work through the rest.

Step-by-step field fix

  1. Check for a real collision first; jog clear with supervision temporarily reduced if needed
  2. Enter correct tool and payload data
  3. Verify brake operation on the flagged axis
  4. Re-enable full supervision before resuming automatic mode — never leave it disabled in production
Safety first: For ABB 50204, 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 Check for a real collision first; jog clear with supervision temporarily reduced if needed; anything past that falls under the arm working envelope and needs a certified engineer.

How we diagnose motion alarms on site

ABB 50204 belongs to the motion & path family. On ABB 50204 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 50204 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.

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

First check whether ABB 50204 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 50204 (Motion Supervision (Collision Detection) Triggered); written by the Henghuan repair team, updated 2026-10-01.

Can't find the cause? One call can pinpoint it

Just tell us the alarm code, the robot model and which program was running, and our engineers will help you narrow it down — phone and video remote diagnosis are both free.

Get a Free Remote Diagnosis See Repair Services

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

Related Motion & Path alarms

50056 — Joint Collision
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 50204 alarm mean?

The path/collision supervision detected an unexpected force during motion and stopped the robot — either a real collision or supervision too sensitive for the current load. In our ABB service archive this alarm on IRC5 / OmniCore (RobotWare) systems shows up constantly, and the first on-site inspection almost always locates it. ABB 50204 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "Actual collision with fixture, part or guarding".

QCan I clear a ABB 50204 alarm myself?

Whether ABB 50204 clears on its own depends on the outcome of "Check for a real collision first; jog clear with supervision temporarily reduced if needed". Finish the flow with "Re-enable full supervision before resuming automatic mode — never leave it disabled in production" to confirm ABB 50204 - do not skip it. If that step is clean, the second most frequent cause on ABB 50204 is "Wrong or missing load data (tool/workobject)". After clearing ABB 50204, 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 50204, can you triage remotely first?

The commonest causes we see on ABB 50204 are "Actual collision with fixture, part or guarding, Wrong or missing load data (tool/workobject), Brake not fully released on an axis", so we stock the van against those. For ABB 50204 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For ABB 50204, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what ABB 50204 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 50204 was compiled from actual repair records of the Henghuan Robotics repair team. Alarm notes are our own summary for troubleshooting reference only and may vary with controller and software version — please consult ABB documentation or contact us if in doubt. Henghuan is an independent service provider, not affiliated with or endorsed by ABB.