EZB Disconnecting

Note: An unwanted EZB disconnection occurs when ARC disconnects from the EZB without notice during an active and valid connection.

This guide is intended for situations where a connection was previously working but is now disconnecting. If you are unable to connect to the EZB at all, please use the Connection Troubleshooting Guide.

ARC release candidates undergo extensive stress testing across multiple virtual machines before being released to the public. One of the most demanding tests involves controlling four robots continuously (24/7) connected to Exosphere.

These Exosphere robots perform ongoing reliability, efficiency, and stability testing for ARC. They operate with multiple cameras, tracking systems, Wi-Fi and USB connections, NMS, and more. Because these robots are always online and accessed globally, ARC itself is highly unlikely to be the root cause of random disconnections or freezing.

1. Power

Power issues are the most common cause of disconnections, especially in DIY robot builds. Motors and servos can draw significant current, particularly under load.

  • Measure current draw: Determine both average and peak current usage of your robot.
  • Verify power supply capacity: Ensure your power source can handle peak current demands.
  • Avoid powering motors through EZB pins: While controllers like the EZ-Robot IoTiny and EZ-B v4 offer convenient power pins, their internal traces may not support high current loads. This can cause a brown-out, where the controller shuts down or becomes unstable due to insufficient power.
View Power Supply Tutorial

2. Wi-Fi Connection

Wi-Fi-enabled EZB controllers (such as ESP32, EZ-Robot IoTiny, and EZ-B v4) provide flexibility but are also a common source of instability. Wireless environments can introduce interference, congestion, and signal degradation.

Recommendation: For production or mission-critical robots, use a USB connection instead of Wi-Fi whenever possible.
  • Check Wi-Fi channel congestion: Use a scanning tool to identify less crowded channels and switch accordingly.
  • Improve signal stability: Reduce distance to the router, minimize interference, or consider a wired connection.
Download Wi-Fi Scan Tool

3. Communication Timeouts

Many sensors and peripherals communicate with the EZB using protocols such as I2C. These devices often require precise timing and acknowledgment signals.

Loose wiring, electrical noise, or unstable connections can cause communication timeouts. When this happens, the EZB may become unresponsive while waiting for a reply, making ARC appear frozen or disconnected.

  • Inspect I2C connections: Ensure all wiring is secure and properly connected (e.g., RGB Eyes, compass, accelerometer).
  • Check known weak points: For example, EZ-Robot JD Humanoid robots may disconnect if the RGB Eyes cable is loose or faulty.
  • Eliminate noise sources: Keep signal wires short and away from high-current components.

4. ARC Project

Finally, review your ARC project configuration. Excessive scripting or rapid communication with the EZB can overload the communication channel.

  • Reduce script load: Avoid multiple scripts continuously looping and sending commands.
  • Throttle communication: Add delays where appropriate to prevent flooding the EZB with requests.
  • Test incrementally: Disable parts of the project to isolate the cause of the issue.