Asked — Edited

JD Robot Connection Issue

Hi all,

I recently acquired a used JD robot and am experiencing difficulty connecting it to ARC through the EZ-Robot EZ-B v4. Each time I try to connect, the connection fails. Although I have already reset the EZ-B v4, my PC can successfully connect to it, indicated by the blue light blinking on the back. Interestingly, I am able to connect to and utilize the camera in ARC without any issues.

I'm unsure what's causing this, especially since I never encountered a similar problem with my Roli robot. I would greatly appreciate any assistance or insights into what might be going wrong.

Thank you!

@Athena



Related Hardware (view all EZB hardware)
JD Humanoid by EZ-Robot
JD humanoid robot kit - WiFi-enabled, 16 DOF with metal-gear servos; easy, fun, educational, available from the EZ-Robot online store.
Wi-Fi / USB
Servos 24
Camera
Audio
UART 3
I2C
ADC 8
Digital 24

Related Robot Skills (view all robot skills)
EZB Connection by Synthiam
Connects EZ-B I/O controllers to ARC via COM or IP (5 connections). Supports init scripts, battery monitoring, TCP/EZ-Script server and serial/I2C.
Diagnose EZ-B Wi-Fi connection issues with verbose EZ-B communication logging, ping tests, log export and diagnostic reports for Synthiam support.

ARC Pro

Upgrade to ARC Pro

Subscribe to ARC Pro, and your robot will become a canvas for your imagination, limited only by your creativity.

Author Avatar
PRO
Canada
#1  

Thanks - let’s troubleshoot this stepbystep. Since you can see the camera in ARC but the EZB v4 connection fails, that gives useful clues. Please try the checklist below and paste any status/log text you get (I cannot view images - include the exact text).

  1. Quick checks (most common causes)
  1. Get basic status from ARC (run these in a JavaScript script or the Script Console)
  • Get the configured address for connection index 0:
var addr = controlCommand("Connection","GetAddress",0);
print("Address: " + addr);
  • Check whether ARC thinks the EZB is connected:
var status = controlCommand("Connection","GetStatus",0);
print("Connected?: " + status);

Copy/paste the printed values here.

  1. Test TCP reachability to the EZB
  • If you connect by IP, try a telnet / port test from your PC to the EZB (replace 192.168.1.1 with your EZB IP): Windows CMD:
telnet 192.168.1.1 23

PowerShell:

Test-NetConnection -ComputerName 192.168.1.1 -Port 23

If port 23 is filtered/blocked the test will fail. Paste the Test-NetConnection output if available.

  1. Use the Connection Diagnostic skill (verbose logs)
  • Add Project -> Add robot skill -> General -> Connection Diagnostic
  • In that skill: press Ping EZB and then Copy Log to Clipboard
  • Paste the log text here (do not post screenshots - paste the exact text)

Docs & download links:

  1. Firmware / Mode checks
  • Camera working suggests the EZB’s IP/HTTP is reachable. The connection channel uses a TCP socket/protocol the firewall or firmware may block. Try:
    • Reboot EZB and PC.
    • If the EZB is in "client" mode (connects to ARC), ensure ARC’s TCP EZB Server (if used) is enabled. If EZB is in AP mode, ensure your PC is on the EZB’s WiFi or they’re on the same router/subnet.
    • If firmware mismatch is suspected, consider reflashing the EZB firmware: https://synthiam.com/Support/Hardware/Hardware-Overview
  1. Power & wiring
  • Confirm JD’s power is supplying the EZB properly. Brownouts or low voltage can make the EZB appear to boot (camera works) but fail protocol services. Tell me what battery/how you power JD.
  1. Extra checks if using USB/COM
  • If using COM: open Device Manager, confirm COM port number. In the EZB Connection skill choose that COM and the correct baud. If another app (Putty, serial monitor) is using that COM, close it.

What I need from you now

  1. Are you connecting by WiFi (IP) or USB/COM? What exact address or COM port are you using?
  2. Output of the two ControlCommand prints (Address & Connected?) from step 2.
  3. Result of TestNetConnection or telnet (if using IP).
  4. Paste the Connection Diagnostic log text if you ran it.
  5. ARC version and Windows version.
  6. Any exact error message shown in the ARC status area - paste the text.

I’ll walk through the results and give the next targeted steps (firewall rules, port tests, or firmware updates). Would you like the commands as a single script you can paste into ARC’s Script Console?


I am a customer support GPT-powered AI and still learning. If you have doubts about my response, please use the support documentation to verify my answer.
Author Avatar
PRO
Synthiam
#2  

Oh, one thing to check is if the led goes red after ezb connection from arc. If so, check the rgb led eyes connection. That red led after ezb connection from ARC means the i2c connection to the eyes leds isn’t successful.

You can always remove the rgb led robot skill from the project and try connecting to see if that fixes it.

but these instructions only apply if the red led is on steady after ezb ARC connection.

#3  

Also, I’ll chime in and suggest using the JD Bare project. I don’t believe the Bare project has the rgb animator robot skill, which means it should run successfully without needing the rgb eyes.