ABB Error 100000 — Firmware RobotWare — tout module fault
ErrorABB 100000 (“Firmware RobotWare — tout module fault”): This code comes in 12 variants (IRC5 / Omnicore · S4C / S4C+ / IRC5 · IRC5). Likely part: World Zones / Unité d'E/S DeviceNet (World Zones / Unité d'E/S DeviceNet).
Updated 2026-10-22 · LogrobotLM reference
What it means
This code comes in 12 variants (IRC5 / Omnicore · S4C / S4C+ / IRC5 · IRC5). Main case: Internal error: single, generic code of the "Internal" category of the log. The number carries no information; all the diagnostic value is in the text, in the form "<Module>.c <line> <message>" — the RobotWare firmware source file and the line that issued the error. Examples recorded in the field and in the community: Servo.c 2154, Hpjts.c 4791, Refsup.c 728, Wzone.c 1086, Servots.c 7016, pgmsym.c 3195.
What to check
- Never treat "Internal error" as a diagnosis: note the complete module, line and message.
- Then group by module to see the family involved (Servo = servo control, Refsup = reference supervision, Wzone = World Zones, Hpjts = manual jogging).
- Correlate to the second with the other categories: the internal error often precedes the public message.
- If an isolated module appears only once with no correlated event, a software reload is generally sufficient; if it recurs, trace back to the hardware.
- Note: Does not exist in the ABB event manual: code not publicly documented, specific to the internal category. The source line varies with the RobotWare version (Hpjts.c 4713 in RW5, 4791 in RW6.08): compare modules, never line numbers, from one cabinet to another.
Part to check / replace
ABB 100000 points to the hardware below — start here before ordering.
Tap a part for every code that points to it — and verify the exact variant for your controller before ordering.
Indicative field information — the robot manufacturer's manual and safety procedures always prevail. Never bypass a safety device; apply lockout/tagout (LOTO) before any physical intervention. How this reference is built →