What the 10006 alarm means

The controller lost its internal bus link to a joint module; the robot stops until the link is restored. We are very familiar with this alarm on AUBO i-series / C-series (ARCS SDK) systems — usually the first on-site inspection is enough to confirm the cause.

Most common causes

  • Internal bus cable or connector fault
  • Joint module power dip
  • Node addressing conflict after a module swap
  • EMI on the bus
Field note: Our ticket data shows the first cause is by far the most common — start there to avoid dead ends.

Step-by-step field fix

  1. Note which joint drops out and power-cycle
  2. Reseat accessible connectors to the joint
  3. Check for new interference sources near the cell
  4. Verify module firmware versions are matched
  5. Replace the cable or joint module if dropouts repeat
Safety first: For AUBO 10006, when communication drops, controller and external devices can disagree about state; at reconnect, external axes or tooling may act on stale commands. On site you may look at after confirming power-off the first step yourself: Note which joint drops out and power-cycle. Beyond that it is external axes and tooling interlocks work - leave it to a professional.

How we diagnose communication alarms on site

AUBO 10006 belongs to the communication family. On AUBO 10006 the failing stage is AUBO collaborative robot controller - the data link: fieldbus, Ethernet, cabinet-to-body communication and external device interfaces. We start reading AUBO 10006 at the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication.

The chain involved in AUBO 10006 runs: physical layer (cable / connector / shield) -> link layer (protocol / baud / node ID) -> application layer (data mapping / handshakes).

If Internal bus cable or connector fault on AUBO 10006 is intermittent and a reboot buys a while: Intermittent drops that a reboot clears for a while are usually interference. Power cables sharing a trunk with communication cables, poor common grounding between drives and robot, or a shield landed at both ends forming a ground loop all produce exactly this. We check spacing between communication and power runs, single- versus double-ended shield landing, and the cabinet earth-bar connections. The fix is often re-routing and re-grounding - no hardware - but it needs a coordinated stop.

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

Still unresolved? Our engineers are standing by

Give us the alarm code, the robot model and what it was doing when the alarm hit. Our engineers run these diagnostics daily, and remote diagnosis by phone or video is free.

Get a Free Remote Diagnosis See Repair Services

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

Related Communication alarms

50001 — External Interface Communication Error
Same family: this code belongs to the Communication alarms family - the page collects all Communication-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 10006 alarm mean?

The controller lost its internal bus link to a joint module; the robot stops until the link is restored. We are very familiar with this alarm on AUBO i-series / C-series (ARCS SDK) systems — usually the first on-site inspection is enough to confirm the cause. AUBO 10006 sits in the communication family; on our work orders the highest-frequency trigger for this code is "Internal bus cable or connector fault".

QCan I clear a AUBO 10006 alarm myself?

Whether AUBO 10006 clears on its own depends on the outcome of "Note which joint drops out and power-cycle". Finish the flow with "Replace the cable or joint module if dropouts repeat" to confirm AUBO 10006 - do not skip it. If that step is clean, the second most frequent cause on AUBO 10006 is "Joint module power dip". When AUBO 10006 keeps coming back it is not a one-off trigger - especially if Replace the cable or joint module if dropouts repeat is where you get stuck. Do not keep producing through AUBO 10006.

QFor communication alarms like AUBO 10006, how long does a site visit take?

The commonest causes we see on AUBO 10006 are "Internal bus cable or connector fault, Joint module power dip, Node addressing conflict after a module swap", so we stock the van against those. For AUBO 10006 specifically, we carry common bus cables, connectors, termination resistors and shield terminals. For AUBO 10006, communication work is about tracing the physical link segment by segment; most cases close in one visit. Before we roll, tell us what AUBO 10006 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 notes on AUBO 10006 were summarized by the Henghuan Robotics repair team from on-site service. The alarm interpretation is our empirical summary for troubleshooting reference and may vary by controller and software version — please check AUBO documentation or contact us with questions. Henghuan is an independent service provider, not affiliated with or endorsed by AUBO.