What the 20032 alarm means
The serial measurement board's revolution counters no longer match the stored calibration — typically after the axes were moved with power off or the SMB battery ran low. Automatic operation is blocked until the counters are updated. 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
- Robot arm moved manually while the controller was powered off
- Low or dead SMB battery
- SMB board or resolver cable fault
- Improper shutdown
Step-by-step field fix
- Jog each axis to its mechanical origin marks (align the calibration notches)
- On the FlexPendant: Calibration → Update revolution counters, axis by axis
- Replace the SMB battery if it was low
- If counters drift again quickly, check the resolver cables and SMB board
How we diagnose calibration alarms on site
ABB 20032 belongs to the calibration & measuring board family. On ABB 20032 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 20032 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.
The chain involved in ABB 20032 runs: measuring board acquisition -> zero / position data -> tool and work frames -> program points -> actual motion accuracy.
Step one on ABB 20032 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 20032 (Revolution Counters Not Updated); written by the Henghuan repair team, updated 2026-10-01.
Real Field Case
Machine: ABB IRB 1410 (2016)
Symptom: An IRB 1410 raised 20032 (revolution counters not updated) on startup and would not run in auto.
What we did: After confirming the battery was fine, we updated the revolution counters against the calibration marks and verified each axis.
Result: The alarm cleared and auto operation resumed in about 2 hours.
Can't clear it yourself? Contact us for remote diagnosis
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
50053 — Too Large Revolution Counter Difference 50057 — Joint Not Synchronized 50296 — SMB Memory Data DifferenceFrequently asked questions
QWhat does the ABB 20032 alarm mean?
The serial measurement board's revolution counters no longer match the stored calibration — typically after the axes were moved with power off or the SMB battery ran low. Automatic operation is blocked until the counters are updated. 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 20032 sits in the calibration & measuring board family; on our work orders the highest-frequency trigger for this code is "Robot arm moved manually while the controller was powered off".
QCan I clear a ABB 20032 alarm myself?
Whether ABB 20032 clears on its own depends on the outcome of "Jog each axis to its mechanical origin marks (align the calibration notches)". Finish the flow with "If counters drift again quickly, check the resolver cables and SMB board" to confirm ABB 20032 - do not skip it. If that step is clean, the second most frequent cause on ABB 20032 is "Low or dead SMB battery". Two attempts and still there means stop: ABB 20032 involves axis drop once brakes are released, and running ABB 20032 on can turn a repairable fault into a replacement.
QWhen you handle ABB 20032, will my programs and frames get lost?
The commonest causes we see on ABB 20032 are "Robot arm moved manually while the controller was powered off, Low or dead SMB battery, SMB board or resolver cable fault", so we stock the van against those. For ABB 20032 specifically, we bring the brand's measuring-board type data, mastering fixtures and dial indicators; the backup matters more than the spare. For ABB 20032, on calibration alarms we back up programs and points first, master second, and verify precision before handover. Before we roll, tell us what ABB 20032 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 content on ABB 20032 was written by Henghuan Robotics service engineers from hands-on repair experience. Alarm descriptions are our own reference summary and may differ by controller or software version — defer to ABB documentation, or contact us to confirm. Henghuan is an independent service provider with no affiliation or endorsement by ABB.