What the 50057 alarm means

After a power-down or failure, a joint's position is too far from where the system expected it — usually caused by an improper shutdown. This fault appears in a large share of our ABB IRC5 / OmniCore (RobotWare) service tickets, and the first round of on-site checks usually finds the source.

Most common causes

  • Hard power-off instead of a proper shutdown sequence
  • Axis moved while powered down
  • SMB data inconsistency
Field note: Most of the time the problem is the first item on the list, so ruling it out saves you half the time.

Step-by-step field fix

  1. Restart with a B-start (advanced restart) to restore the last good state
  2. Always shut down via FlexPendant: Restart → Advanced → Shutdown, never by cutting mains
  3. Update revolution counters after recovery
  4. If it recurs, investigate the SMB battery and board
Safety first: For ABB 50057, 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 Restart with a B-start (advanced restart) to restore the last good state; anything past that falls under axis drop once brakes are released and needs a certified engineer. On ABB 50057: 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 50057 belongs to the calibration & measuring board family. On ABB 50057 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 50057 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.

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

Step one on ABB 50057 is the same as the system family: Step one on calibration alarms matches the system family: back up. Programs, points, tool frames, work-object frames, zero data - all of it, before any action. The reason is cost: rebuilding calibration data is expensive, a complex work-object frame can consume half a day of teaching and TCP calibration needs dedicated fixtures. After the backup we decide whether the data itself is corrupt or acquisition is faulty; if it is the latter, a board swap restores from backup instead of re-teaching.

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

If you can't fix it, reach our engineers directly

Send the alarm code, the robot model and a description of what was happening at the alarm. Our engineers handle ABB 50057 every day, and remote diagnosis by phone/video is 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 50053 — Too Large Revolution Counter Difference 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 50057 alarm mean?

After a power-down or failure, a joint's position is too far from where the system expected it — usually caused by an improper shutdown. This fault appears in a large share of our ABB IRC5 / OmniCore (RobotWare) service tickets, and the first round of on-site checks usually finds the source. ABB 50057 sits in the calibration & measuring board family; on our work orders the highest-frequency trigger for this code is "Hard power-off instead of a proper shutdown sequence".

QCan I clear a ABB 50057 alarm myself?

Whether ABB 50057 clears on its own depends on the outcome of "Restart with a B-start (advanced restart) to restore the last good state". Finish the flow with "If it recurs, investigate the SMB battery and board" to confirm ABB 50057 - do not skip it. If that step is clean, the second most frequent cause on ABB 50057 is "Axis moved while powered down". When ABB 50057 keeps coming back it is not a one-off trigger - especially if If it recurs, investigate the SMB battery and board is where you get stuck. Do not keep producing through ABB 50057.

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

The commonest causes we see on ABB 50057 are "Hard power-off instead of a proper shutdown sequence, Axis moved while powered down, SMB data inconsistency", so we stock the van against those. For ABB 50057 specifically, we bring the brand's measuring-board type data, mastering fixtures and dial indicators; the backup matters more than the spare. For ABB 50057, on calibration alarms we back up programs and points first, master second, and verify precision before handover. Before we roll, tell us what ABB 50057 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.

The notes on ABB 50057 were summarized by the Henghuan Robotics repair team from on-site service. The alarm interpretation is our empirical summary for troubleshooting reference and may vary by controller and software version — please check ABB documentation or contact us with questions. Henghuan is an independent service provider, not affiliated with or endorsed by ABB.