What the 10001 alarm means

The affected joint's drive stage detected current above the protection limit; the AUBO controller disables the joint to protect the power electronics. Codes 10001-10022 are joint-level faults reported through the AUBO SDK/ARCS interface. 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

  • Collision or jammed joint
  • Motor cable short or connector contamination
  • Payload well above the configured value
  • Joint drive hardware fault
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 the collision and inspect the joint for damage
  2. Verify payload and tool data in the controller
  3. Check motor connectors for oil, coolant or bent pins
  4. Re-enable and jog the joint slowly while watching current
  5. Service or replace the joint module if overcurrent repeats with no load
Safety first: For AUBO 10001, this alarm family involves the DC bus, which sits at several hundred volts and stays charged for minutes after power-off - touching terminals is a shock hazard. On site you may not carry out the first step yourself: Clear the collision and inspect the joint for damage. Beyond that it is the DC bus and power stage work - leave it to a professional. On AUBO 10001: checking incoming voltage at the disconnect and looking at breakers and fuses is fine to do yourself; opening the cabinet to touch bus terminals or pulling power modules needs a qualified electrician.

How we diagnose drive alarms on site

AUBO 10001 belongs to the drive & power stage family. On AUBO 10001 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 fault sits on the energy chain: mains input, rectification, DC bus, braking resistor, inverter power devices and the drive board. We start reading AUBO 10001 at the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication.

The chain involved in AUBO 10001 runs: three-phase mains -> rectifier -> DC bus (bus capacitors) -> brake chopper / braking resistor -> inverter (IGBT) -> motor.

Collision or jammed joint is common on AUBO 10001, but look at the duty cycle: Cells with high-inertia loads or frequent start-stop cycles return far more regenerative energy than a plain transfer cell, and the braking resistor lives in a hot cycle that shortens its life. When we suspect this family we ask what changed: if the takt was raised recently or a heavier fixture went on, the alarm cluster usually lines up with that process change. Replacing the resistor alone will not fix it - the chopper rating and resistor wattage have to be re-checked against the new duty.

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

No luck? Hand it to the team that fixes this daily

Send the alarm code, the robot model and a description of what was happening at the alarm. Our engineers handle AUBO 10001 every day, and remote diagnosis by phone/video is free.

Get a Free Remote Diagnosis See Repair Services

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

Related Drive & Power Stage alarms

10007 — Joint Voltage Abnormal (JOINT_ERR)
Same family: this code belongs to the Drive & power stage alarms family - the page collects all Drive & power stage-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 10001 alarm mean?

The affected joint's drive stage detected current above the protection limit; the AUBO controller disables the joint to protect the power electronics. Codes 10001-10022 are joint-level faults reported through the AUBO SDK/ARCS interface. 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 10001 sits in the drive & power stage family; on our work orders the highest-frequency trigger for this code is "Collision or jammed joint".

QCan I clear a AUBO 10001 alarm myself?

Whether AUBO 10001 clears on its own depends on the outcome of "Clear the collision and inspect the joint for damage". Finish the flow with "Service or replace the joint module if overcurrent repeats with no load" to confirm AUBO 10001 - do not skip it. If that step is clean, the second most frequent cause on AUBO 10001 is "Motor cable short or connector contamination". When AUBO 10001 keeps coming back it is not a one-off trigger - especially if Service or replace the joint module if overcurrent repeats with no load is where you get stuck. Do not keep producing through AUBO 10001.

QFor drive/power alarms like AUBO 10001, what spares do you bring on site?

The commonest causes we see on AUBO 10001 are "Collision or jammed joint, Motor cable short or connector contamination, Payload well above the configured value", so we stock the van against those. For AUBO 10001 specifically, we stock the van along the energy chain: braking resistors, bus capacitors, input fuses, drive-board supply parts and the common power modules for the brand. For AUBO 10001, drive alarms usually stop the whole line, so they sit at the front of our dispatch queue. Before we roll, tell us what AUBO 10001 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 10001 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.