What the 10005 alarm means

The joint encoder reports invalid data or lost communication; the position loop cannot close and the joint is disabled. This is one of the most common faults in our repair logs for the AUBO i-series / C-series (ARCS SDK) platform, and the first inspection typically locates the cause.

Most common causes

  • Encoder connector loose inside the joint
  • Cable fatigue from repeated torsion
  • EMI corrupting the encoder signal
  • Encoder hardware failure
Field note: Field experience says the first cause is the most likely — verify it before moving on to the rest.

Step-by-step field fix

  1. Power-cycle and check whether the error returns at enable
  2. Inspect joint cabling for damage
  3. Separate signal cables from high-current runs
  4. Re-run joint zeroing after the signal is stable
  5. Replace the joint module if the encoder fault persists
Safety first: For AUBO 10005, encoder alarms often mean position data cannot be trusted: actual pose may disagree with the system record, so releasing a brake or jogging carries unexpected-motion risk. The self-serviceable action is Power-cycle and check whether the error returns at enable; anything past that falls under position feedback and brake release and needs a certified engineer.

How we diagnose encoder alarms on site

AUBO 10005 belongs to the encoder & position family. On AUBO 10005 the failing stage is dual joint encoders (motor side and output side) on the AUBO collaborative robot controller - the feedback path: encoder body, encoder cable, battery, measuring board and the stored position memory. We start reading AUBO 10005 at the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication.

The chain involved in AUBO 10005 runs: motor-side encoder -> encoder cable -> drive / measuring board acquisition -> position count and zero data -> battery-held memory.

On AUBO 10005 the commonest field report is Encoder connector loose inside the joint; the highest-share cause is plain: The highest-share cause in this family is unglamorous: battery voltage. Absolute encoders hold the position count on a battery while power is off; below threshold the memory is gone and the controller demands a fresh master. Packs are designed for roughly two to three years, but a hot cabinet shortens that a lot. We carry spare packs, and after a swap we master immediately and re-check every axis zero so the customer does not run on an offset.

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

Still stuck? Get an engineer on the line now

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 Encoder & Position alarms

10001 — Joint Overcurrent (JOINT_ERR) 10002 — Joint Overspeed (JOINT_ERR) 10003 — Joint Position Tracking Error (JOINT_ERR) 10004 — Joint Overtemperature (JOINT_ERR) 10006 — Joint Communication Error (JOINT_ERR) 10007 — Joint Voltage Abnormal (JOINT_ERR)
Same family: this code belongs to the Encoder & position alarms family - the page collects all Encoder & position-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 10005 alarm mean?

The joint encoder reports invalid data or lost communication; the position loop cannot close and the joint is disabled. This is one of the most common faults in our repair logs for the AUBO i-series / C-series (ARCS SDK) platform, and the first inspection typically locates the cause. AUBO 10005 sits in the encoder & position family; on our work orders the highest-frequency trigger for this code is "Encoder connector loose inside the joint".

QCan I clear a AUBO 10005 alarm myself?

Whether AUBO 10005 clears on its own depends on the outcome of "Power-cycle and check whether the error returns at enable". Finish the flow with "Replace the joint module if the encoder fault persists" to confirm AUBO 10005 - do not skip it. If that step is clean, the second most frequent cause on AUBO 10005 is "Cable fatigue from repeated torsion". Two attempts and still there means stop: AUBO 10005 involves position feedback and brake release, and running AUBO 10005 on can turn a repairable fault into a replacement.

QFor encoder alarms like AUBO 10005, can it be fixed in one visit?

The commonest causes we see on AUBO 10005 are "Encoder connector loose inside the joint, Cable fatigue from repeated torsion, EMI corrupting the encoder signal", so we stock the van against those. For AUBO 10005 specifically, we carry feedback-path parts: encoder cables, battery packs, connector pins and the measuring-board type data for the brand. For AUBO 10005, encoder alarms are mostly broken cores and dead batteries, both of which ride in the van, so most clear in one visit. Before we roll, tell us what AUBO 10005 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.

This page on AUBO 10005 was written by the Henghuan Robotics repair team from field service experience. Alarm descriptions are our own summary for troubleshooting reference and may vary by controller and software version — when in doubt, check your AUBO documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by AUBO.