What the E.21 alarm means

The ERC controller lost communication with one or more servo drives on the internal bus; affected axes are disabled. We see this alarm constantly when servicing ESTUN ERC / ED3L controller + ESTUN servo systems, and the first on-site pass usually pins down the cause.

Most common causes

  • Communication cable between controller and drives damaged or loose
  • Drive power supply off or tripped
  • Bus termination or node address conflict
  • EMI from nearby high-current equipment
Field note: Based on our handling experience the first cause is the most frequent — use it as your starting point.

Step-by-step field fix

  1. Check that all drives have control power and show normal status LEDs
  2. Reseat the bus communication cables at both ends
  3. Verify node addresses are unique and match the configuration
  4. Check cable routing away from motor power cables
  5. Replace the communication cable or the failing drive node
Safety first: For ESTUN e-21, when communication drops, controller and external devices can disagree about state; at reconnect, external axes or tooling may act on stale commands. The self-serviceable action is Check that all drives have control power and show normal status LEDs; anything past that falls under external axes and tooling interlocks and needs a certified engineer.

How we diagnose communication alarms on site

ESTUN e-21 belongs to the communication family. On ESTUN e-21 the failing stage is ESTUN robot controllers (motion-control-platform based) on the ESTUN robot controllers (motion-control-platform based) - the data link: fieldbus, Ethernet, cabinet-to-body communication and external device interfaces. We start reading ESTUN e-21 at the pendant alarm list (A.xxx / E.xxx segments) and the servo panel display code.

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

If Communication cable between controller and drives damaged or loose on ESTUN e-21 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 ESTUN e-21 (Servo Communication Timeout); written by the Henghuan repair team, updated 2026-10-01.

Blocked by this alarm? We can help you analyze it over the phone

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 Communication alarms

A.02 — Parameter Setting Error A.10 — Overcurrent A.30 — Regeneration Error / Regenerative Overload A.40 — Main Circuit Overvoltage A.41 — Main Circuit Undervoltage A.51 — Overspeed
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 INOVANCE · EFORT · JAKA and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the ESTUN e-21 alarm mean?

The ERC controller lost communication with one or more servo drives on the internal bus; affected axes are disabled. We see this alarm constantly when servicing ESTUN ERC / ED3L controller + ESTUN servo systems, and the first on-site pass usually pins down the cause. ESTUN e-21 sits in the communication family; on our work orders the highest-frequency trigger for this code is "Communication cable between controller and drives damaged or loose".

QCan I clear a ESTUN e-21 alarm myself?

Whether ESTUN e-21 clears on its own depends on the outcome of "Check that all drives have control power and show normal status LEDs". Finish the flow with "Replace the communication cable or the failing drive node" to confirm ESTUN e-21 - do not skip it. If that step is clean, the second most frequent cause on ESTUN e-21 is "Drive power supply off or tripped". When ESTUN e-21 keeps coming back it is not a one-off trigger - especially if Replace the communication cable or the failing drive node is where you get stuck. Do not keep producing through ESTUN e-21.

QFor communication alarms like ESTUN e-21, how long does a site visit take?

The commonest causes we see on ESTUN e-21 are "Communication cable between controller and drives damaged or loose, Drive power supply off or tripped, Bus termination or node address conflict", so we stock the van against those. For ESTUN e-21 specifically, we carry common bus cables, connectors, termination resistors and shield terminals. For ESTUN e-21, communication work is about tracing the physical link segment by segment; most cases close in one visit. Before we roll, tell us what ESTUN e-21 shows on the pendant alarm list (A.xxx / E.xxx segments) and the servo panel display code and what the machine was doing - phone or video triage is free.

This page on ESTUN e-21 is based on the field experience of the Henghuan Robotics repair team. Alarm explanations are our own summary for troubleshooting reference and may differ across controller and software versions — if unsure, verify against ESTUN documentation or reach out to us. Henghuan is an independent service provider with no affiliation or endorsement by ESTUN.