Troubleshooting Error E-1104: EtherCAT Communication Timeout on NXB-CTL-213-010 Controller

Related Products

Tools Required

• Multimeter
• NexBot Integrated Development Environment (NIDE) software
• Laptop with Ethernet port
• Standard set of screwdrivers
• Safety glasses

Article

Overview

Error E-1104 on the NexBot Robotics 213-010 8-Axis EtherCAT Motion Controller (SKU: NXB-CTL-213-010) indicates a critical failure in the real-time communication bus. Specifically, the controller has lost its connection to one or more EtherCAT slave devices (e.g., servo drives, I/O modules, sensors) on the network. This fault will typically cause all robot motion to cease as a safety precaution. This article outlines the common causes and provides a systematic approach to identify and resolve the issue.

Symptom

Operators may observe one or more of the following symptoms:

• An explicit E-1104: EtherCAT Communication Timeout alarm is displayed on the Human-Machine Interface (HMI) or logged in the system diagnostics panel.
• The robot arm (e.g., NexBot R-50, R-100 series) halts motion unexpectedly and enters a fault state.
• The 'ECAT STATUS' LED on the NXB-CTL-213-010 controller is flashing red or is completely off, instead of solid green.
• In the NexBot Integrated Development Environment (NIDE) software, one or more slave devices in the EtherCAT network tree appear as offline or 'Not Present'.
• The 'LINK/ACT' LEDs on the affected slave device(s) may be off.

Cause

The E-1104 error is a general communication fault that can stem from several root causes, ranging from simple physical issues to complex configuration problems. The most common causes are:

1. Physical Layer Fault: The most frequent cause. This includes a disconnected, loose, or damaged EtherCAT cable (e.g., NXB-CBL-NET522-009), or a faulty connector at either the controller or a slave device.
2. Power Supply Interruption: The controller or a slave device has lost its 24VDC operating power, causing it to drop off the network.
3. Slave Device Failure: A hardware failure within an EtherCAT slave device (e.g., a servo drive, I/O block, or encoder like NXB-SNS-ENC521-009) can break the communication chain. Since EtherCAT is a ring topology, a single failed device can bring down all subsequent devices in the chain.
4. Network Configuration Mismatch: The hardware configuration on the physical network does not match the configuration file loaded into the NXB-CTL-213-010 controller. This can happen if a device was replaced with an incorrect model or if the project file is wrong.
5. Electromagnetic Interference (EMI): High levels of electrical noise from nearby power cables, motors, or VFDs can corrupt the EtherCAT signal, leading to communication dropouts.
6. Controller Fault: In rare cases, the EtherCAT master port on the NXB-CTL-213-010 controller itself may have failed.

Resolution Steps

WARNING: Always follow proper Lockout/Tagout (LOTO) procedures before opening control cabinets or disconnecting any components. Ensure all system energy is discharged.

1. Inspect Physical Connections:

• Power down the entire system.
• Visually inspect the entire length of all EtherCAT cables connected to the controller and between each slave device. Look for cuts, abrasions, or sharp bends.
• Firmly re-seat the EtherCAT connectors at the controller's X2 (ECAT OUT) and X3 (ECAT IN) ports and at every slave device. Listen for the audible click of the connector tab locking into place.

1. Verify Power to All Devices:

• With the system powered on, use a multimeter to verify the 24VDC power supply to the NXB-CTL-213-010 controller. The voltage should be stable and within its specified operational range.
• Individually check the 24VDC supply for each slave device on the network. A common failure point is a single device losing power, which breaks the communication link.

1. Isolate the Faulty Device/Cable:

• This is the most effective method for pinpointing the fault. Power down the system.
• Disconnect the main EtherCAT OUT cable from the controller's X2 port.
• Connect the first slave device directly to the controller. Power on the system and check if the error clears and the device comes online.
• If the first device works, power down and add the next device in the chain (Controller -> Device 1 -> Device 2). Power on and test again.
• Continue this process, adding one device at a time, until the E-1104 error reappears. The fault lies with either the last device you added or the cable connecting to it.

1. Check Software Configuration:

• Connect a laptop running the NIDE software to the controller.
• Go online with the controller and perform a bus scan. Compare the discovered physical devices with the devices listed in your project's configuration tree.
• Ensure the correct ESI (EtherCAT Slave Information) files are installed for every device model on your network.

1. Mitigate EMI:

• Ensure all EtherCAT cables are properly shielded and that the shield is correctly terminated to ground.
• Check that EtherCAT communication cables are physically separated from high-voltage motor power cables. Maintain the maximum possible distance and avoid running them in parallel for long runs.

1. Swap Components:

• If you have identified a suspect device or cable through the isolation process (Step 3), swap it with a known-good spare part. If the problem is resolved, replace the faulty component.

Prevention

• Always use high-quality, shielded industrial EtherCAT cables, such as the recommended NXB-CBL-NET522-009.
• Ensure proper cable management and strain relief on all connections to prevent them from vibrating loose or being damaged during machine operation.
• Conduct periodic inspections of all wiring and connections as part of a scheduled maintenance plan.
• Maintain a clean and stable 24VDC power source for all control components.
• Keep a verified backup of the controller's project configuration file.

Keywords