What the 10003 alarm means

The joint could not follow the commanded trajectory — following error exceeded the limit — so the controller halted motion. We fix this AUBO i-series / C-series (ARCS SDK) fault almost daily, and one round of on-site checks usually confirms what is going on.

Most common causes

  • Obstruction or collision in the path
  • Payload above rating
  • Brake dragging on the joint
  • Encoder signal intermittent
Field note: We have tallied real cases: the first cause tops the list, so start your diagnosis there.

Step-by-step field fix

  1. Clear obstructions and check for damage
  2. Correct the payload configuration
  3. Verify brake release on the joint
  4. Check encoder/cable condition through the dress pack
  5. Re-run at reduced speed and watch tracking error in diagnostics
Safety first: For AUBO 10003, this alarm family points at arm motion control: after a reset the arm can move unexpectedly, and anyone inside the working envelope is at strike and pinch risk. The self-serviceable action is Clear obstructions and check for damage; anything past that falls under the arm working envelope and needs a certified engineer.

How we diagnose motion alarms on site

AUBO 10003 belongs to the motion & path family. On AUBO 10003 the failing stage is joint-integrated drives (motor, drive and reducer in one joint); joint faults report by joint number on the AUBO collaborative robot controller - the gap between command and execution: trajectory planning, joint limits, singularities, following error and mechanical resistance. We start reading AUBO 10003 at the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication.

The chain involved in AUBO 10003 runs: program command -> trajectory planner -> joint targets -> servo execution -> actual position feedback -> deviation compare.

If Obstruction or collision in the path on AUBO 10003 comes with a feeling of drag, the direction is clear: Following error that stays high on one axis only is usually rising mechanical resistance, not a weak servo. We turn the axis by hand with the brake released to feel smoothness, and listen to the reducer for once-per-revolution knocking - a single tick per turn on an RV reducer usually means internal bearing or cycloid damage. Grease that is black, dry or carries metal powder is the plainest evidence. Left alone, this graduates from a motion alarm to a scrapped reducer.

Field notes on this page cover AUBO 10003 (Joint Position Tracking Error (JOINT_ERR)); written by the Henghuan repair team, updated 2026-10-01.

Not sure? Don't force it — contact an engineer

Tell us these three: alarm code, robot model, and the operating condition at the alarm. AUBO 10003 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 Motion & Path alarms

10002 — Joint Overspeed (JOINT_ERR) 40001 — Target Out of Workspace 40002 — Singularity in Path
Same family: this code belongs to the Motion & path alarms family - the page collects all Motion & path-family codes we have handled, with the common inspection order and spares.
Other brands: we also keep field-fix libraries for ROKAE · Dobot · FANUC and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the AUBO 10003 alarm mean?

The joint could not follow the commanded trajectory — following error exceeded the limit — so the controller halted motion. We fix this AUBO i-series / C-series (ARCS SDK) fault almost daily, and one round of on-site checks usually confirms what is going on. AUBO 10003 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "Obstruction or collision in the path".

QCan I clear a AUBO 10003 alarm myself?

Whether AUBO 10003 clears on its own depends on the outcome of "Clear obstructions and check for damage". Finish the flow with "Re-run at reduced speed and watch tracking error in diagnostics" to confirm AUBO 10003 - do not skip it. If that step is clean, the second most frequent cause on AUBO 10003 is "Payload above rating". If AUBO 10003 returns after two clears, or the checks point at Obstruction or collision in the path, stop the cell and call a professional robot repair engineer.

QFor motion alarms like AUBO 10003, can you triage remotely first?

The commonest causes we see on AUBO 10003 are "Obstruction or collision in the path, Payload above rating, Brake dragging on the joint", so we stock the van against those. For AUBO 10003 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For AUBO 10003, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what AUBO 10003 shows on the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication and what the machine was doing - phone or video triage is free.

The content on AUBO 10003 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 AUBO documentation, or contact us to confirm. Henghuan is an independent service provider with no affiliation or endorsement by AUBO.