What the 50053 alarm means

The system detected too large a difference between the actual revolution counter value on the serial measurement board and the value the controller expected — the robot is not calibrated. Manual jogging may still work; automatic operation is blocked. This is one of the most common faults in our repair logs for the ABB IRC5 / OmniCore (RobotWare) platform, and the first inspection typically locates the cause.

Most common causes

  • Arm moved while power was off
  • Faulty serial measurement board, resolver or cables
  • SMB battery failure losing counter data
Field note: Field experience says the first cause is the most likely — verify it before moving on to the rest.

Step-by-step field fix

  1. Update the revolution counters after aligning axes to calibration marks
  2. Check resolver and SMB cables
  3. Test the serial measurement board and replace if faulty
  4. Run a full calibration (fine calibration) before returning to production
Safety first: For ABB 50053, zero mastering usually needs brakes released to move axes onto datum - an unsupported vertical axis can drop during that move. The self-serviceable action is Update the revolution counters after aligning axes to calibration marks; anything past that falls under axis drop once brakes are released and needs a certified engineer. On ABB 50053: backing up programs, points and tool/work frames yourself first is fine; the mastering itself needs released brakes and fixtures, so it is engineer work on site.

How we diagnose calibration alarms on site

ABB 50053 belongs to the calibration & measuring board family. On ABB 50053 the failing stage is SMB serial measurement board (revolution counters held in non-volatile memory on the SMB) on the IRC5 / OmniCore - measurement and calibration data: zero mastering, measuring-board acquisition, tool and work-object frames and data consistency. We start reading ABB 50053 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.

The chain involved in ABB 50053 runs: measuring board acquisition -> zero / position data -> tool and work frames -> program points -> actual motion accuracy.

Arm moved while power was off on ABB 50053 needs board and link separated: The measuring board acquires axis position and holds it across power-off; when its link to the body misbehaves, axis readings disagree or positions no longer match after power-on. We check board supply and battery first, then the communication cable and connectors between board and body. The discriminator is a comparison: one axis reading wrong points at that link or its encoder; several axes wrong at once points at the board itself.

Field notes on this page cover ABB 50053 (Too Large Revolution Counter Difference); written by the Henghuan repair team, updated 2026-10-01.

Real Field Case

Machine: ABB IRB 2600-12/1.65 (2018)

Symptom: An IRB 2600 raised 50053 (revolution counter deviation too large) and was positioning inaccurately.

What we did: We verified each axis against the calibration targets, found one axis with a drifted revolution counter, updated it and re-checked accuracy.

Result: Positioning recovered after the update and the repeatability re-check passed; about 2.5 hours.

Blocked by this alarm? We can help you analyze it over the phone

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 Calibration & SMB alarms

20032 — Revolution Counters Not Updated 50057 — Joint Not Synchronized 50296 — SMB Memory Data Difference
Same family: this code belongs to the Calibration & measuring board alarms family - the page collects all Calibration & measuring board-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 50053 alarm mean?

The system detected too large a difference between the actual revolution counter value on the serial measurement board and the value the controller expected — the robot is not calibrated. Manual jogging may still work; automatic operation is blocked. This is one of the most common faults in our repair logs for the ABB IRC5 / OmniCore (RobotWare) platform, and the first inspection typically locates the cause. ABB 50053 sits in the calibration & measuring board family; on our work orders the highest-frequency trigger for this code is "Arm moved while power was off".

QCan I clear a ABB 50053 alarm myself?

Whether ABB 50053 clears on its own depends on the outcome of "Update the revolution counters after aligning axes to calibration marks". Finish the flow with "Run a full calibration (fine calibration) before returning to production" to confirm ABB 50053 - do not skip it. If that step is clean, the second most frequent cause on ABB 50053 is "Faulty serial measurement board, resolver or cables". Two attempts and still there means stop: ABB 50053 involves axis drop once brakes are released, and running ABB 50053 on can turn a repairable fault into a replacement.

QWhen you handle ABB 50053, will my programs and frames get lost?

The commonest causes we see on ABB 50053 are "Arm moved while power was off, Faulty serial measurement board, resolver or cables, SMB battery failure losing counter data", so we stock the van against those. For ABB 50053 specifically, we bring the brand's measuring-board type data, mastering fixtures and dial indicators; the backup matters more than the spare. For ABB 50053, on calibration alarms we back up programs and points first, master second, and verify precision before handover. Before we roll, tell us what ABB 50053 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 50053 is based on the field experience of the Henghuan Robotics repair team. Alarm explanations are our own summary for troubleshooting reference and may differ across controller and software versions — if unsure, verify against ABB documentation or reach out to us. Henghuan is an independent service provider with no affiliation or endorsement by ABB.