EZ-Bv4 Firmware Updater Issue

First, thanks - good detail in your report. A few quick questions before steps so I can narrow this down:

• How are you connecting when you run the Firmware Updater: WiFi (IP/AP) or USB/COM?
• When you power the EZB v4, do you hear the startup sound? Does the camera stream in ARC (if you have a camera attached)?
• Can ARC otherwise control the EZB (move servos, read sensors) or does it connect only briefly then drop immediately?
• Do you have a USB/COM connection available (Device Manager shows a COM port) to try an alternate update path?

Troubleshooting steps to try now

1. Verify power and reduce load

• Use a stable power source (7.4V is common for 2S LiPo / safe for most EZRobot servos).
• Remove servo and heavy-load peripherals while updating. Brownouts during updates can break a flash process and cause disconnects.

2. Determine whether the I/O processor is responding

• If the EZB does NOT play the startup sound or ARC connection stalls during the firmware ID stage, the bottom I/O board may be unresponsive (manual symptom). If the communication board is alive but the I/O board is dead, the updater will connect briefly then drop - exactly what you’re seeing.
• Quick check: does the camera stream work? Camera can still work when the I/O board is damaged because the top comm board handles video. If camera works but startup sound and I/O features do not, that points to I/O board failure.

3. Try a direct AP connection and web page check

• Power the EZB, connect your PC to the EZB WiFi (AP mode), then open https://192.168.1.1 in a browser.
• If the web page loads, the EZB communications board is alive. The web page may show battery/firmware info. If you cannot reach the page, note any error.

4. Try updating via USB/COM (alternate path)

• If you’ve been using WiFi, try connecting the EZB via USB/serial to your PC and update using the COM port in ARC.
• In Windows Device Manager, confirm the USB serial driver (COM port) appears (CH340/CP210x, etc.).
• In the Connection control -> CONFIG -> COM/USB Connection tab, ensure the correct baud (default) and try enabling DTR/RTS if required. Then run the Firmware Updater on that COM connection.

5. Run the Connection Diagnostic skill and capture logs

• In ARC: Project -> Add robot skill -> General -> Connection Diagnostic (add it).
• Start the skill, click Ping EZB and let it run. Use the Copy Log to Clipboard button and paste the log here. The diagnostic output will show where in the handshake it fails (useful to confirm whether the firmware ID is returned or the log stops earlier).
• Also copy/paste the ARC status window logs (bottom of ARC) after an update attempt.

6. Try multiple networks was good - next try a direct PC EZB singlenetwork (no router) connection

• Connect your PC directly to the EZB AP or to the same single WiFi network (no VPNs or multiple adapters). Disable other network adapters temporarily (or disable internet adapter) so ARC communicates only with the EZB.

7. Confirm ARC & Updater versions and the exact updater you run

• You said you tried both previous and newest ARC - good. Please tell me the exact ARC versions you tested and the firmware updater dialog messages (copy the text if possible).

Why this often happens (short explanation)

• If the connection establishes but then immediately disconnects, the top comm CPU may accept a TCP session but the I/O processor never returns its firmware ID or responds to commands. That behavior is described in the EZB v4 manual and usually indicates the bottom I/O board is not responding (electrical damage or I/O failure). But we must confirm with logs before assuming hardware failure.

What I need from you

• The Connection Diagnostic log (paste here).
• Answer the questions at top (WiFi or USB, startup sound, camera, ARC control working).
• If possible, attach the exact text/error from the ARC status window when updater disconnects.

Links and references

• EZB v4 firmware / hardware overview: https://synthiam.com/Support/Hardware/EZ-B-v4
• EZB Connection skill info: https://synthiam.com/Support/Skills/Communication/EZB-Connection?id=16041
• Connection Diagnostic skill info (how to capture verbose connection logs): https://synthiam.com/Support/Skills/Communication/Connection-Diagnostic?id=16164
• Connection troubleshooting: https://synthiam.com/Support/troubleshooting/Connection-Troubleshooting

Next steps after you post logs

• I’ll read the diagnostic output and tell you whether it’s a likely I/O board fault, a WiFi/handshake timing issue we can fix, or a driver/COM issue. If it’s a hardware I/O problem, I’ll explain the symptoms clearly and what to test next (e.g., more verification steps you can do at home).

If you want, start by running the Connection Diagnostic and pasting its log here (or paste the ARC status window text). I’ll analyze it and give the specific next action.