What the 10106 alarm means

The periodic maintenance timer has elapsed — the controller reminds the user that scheduled service (gearbox oil, general inspection) is due. It is a warning, not a fault. This fault ranks high in our ABB IRC5 / OmniCore (RobotWare) service records, and the first site inspection usually finds the source.

Most common causes

  • Scheduled service interval reached
  • Timer never reset after the last service
Field note: The first cause shows up most on real machines, so verify it before you go further.

Step-by-step field fix

  1. Perform the due maintenance (oil change, inspection) per the product manual
  2. Reset the timer: Program Editor → Debug → Call Routine → ServiceInfo, run it with the enabling switch and select RESET for the elapsed counter
  3. Confirm the elapsed time reads zero and PP to main
Safety first: For ABB 10106, service work needs lock-out/tag-out: an e-stop alone is not isolation - servos stay live and an accidental enable will move the axis. What you can check yourself first is Perform the due maintenance (oil change, inspection) per the product manual; mechanical areas and rotating parts handling is not a DIY job.

What we recommend for maintenance reminders

ABB 10106 belongs to the maintenance due family. On ABB 10106 the failing stage is DSQC drive modules (DSQC 600 generation; OmniCore drive units) on the IRC5 / OmniCore - not a fault but a due-date signal: runtime or cycle counters reached a service interval and the controller asks for maintenance. We start reading ABB 10106 at the FlexPendant event log and system diagnostics, with the cabinet status LEDs.

The chain involved in ABB 10106 runs: runtime / cycle counters -> service item due -> reminder alarm -> stop window planned -> consumables changed and re-checked.

After ABB 10106 is handled we leave a written record: A machine with complete service records is plainly worth more in the used market, and faults are easier to attribute when the history exists. After each service we issue a written record: what was changed, which consumable grades were used, the precision re-check result and the next interval suggestion. That record serves the customer's asset management and any later trade-in or sale. For multi-robot sites we keep a per-serial file so the fleet can be tracked as one.

Field notes on this page cover ABB 10106 (Service Time Reminder (Maintenance Due)); written by the Henghuan repair team, updated 2026-10-01.

Still guessing? Let a professional engineer save you time

Tell us these three: alarm code, robot model, and the operating condition at the alarm. ABB 10106 is a diagnosis our engineers do daily, and phone/video remote diagnosis is free.

Get a Free Remote Diagnosis See Repair Services

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

Related Maintenance alarms

10012 — Guard Stop (Protective Stop) State 10013 — Emergency Stop State 20032 — Revolution Counters Not Updated 38103 — Communication with SMB Interrupted 50053 — Too Large Revolution Counter Difference 50056 — Joint Collision
Same family: this code belongs to the Maintenance due alarms family - the page collects all Maintenance due-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 10106 alarm mean?

The periodic maintenance timer has elapsed — the controller reminds the user that scheduled service (gearbox oil, general inspection) is due. It is a warning, not a fault. This fault ranks high in our ABB IRC5 / OmniCore (RobotWare) service records, and the first site inspection usually finds the source. ABB 10106 sits in the maintenance due family; on our work orders the highest-frequency trigger for this code is "Scheduled service interval reached".

QCan I clear a ABB 10106 alarm myself?

Whether ABB 10106 clears on its own depends on the outcome of "Perform the due maintenance (oil change, inspection) per the product manual". Finish the flow with "Confirm the elapsed time reads zero and PP to main" to confirm ABB 10106 - do not skip it. If that step is clean, the second most frequent cause on ABB 10106 is "Timer never reset after the last service". Do not chase takt through a repeating ABB 10106. Left alone, maintenance due faults tend to graduate from repairable to must-replace.

QABB 10106 is only a maintenance reminder - do I need an engineer on site?

The commonest causes we see on ABB 10106 are "Scheduled service interval reached, Timer never reset after the last service", so we stock the van against those. For ABB 10106 specifically, we stock consumables against the interval table: grease, batteries, filter mats, belts - changed in one visit to avoid a second stop. For ABB 10106, a maintenance reminder can be planned rather than rushed, but fit it into the nearest stop window. Before we roll, tell us what ABB 10106 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 10106 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.