EZB Version Number Discrepancy

Thanks - good catch. This is most often a cosmetic/hardware-revision vs firmware-identification mismatch, and usually not dangerous, but here’s how to confirm and what to do next.

What the difference likely means

• The "x/2" printed on the PCB is the hardware revision (board manufacturing revision).
• The EZB Stress Test skill is reporting the firmware/bootloader device string that the EZB is returning (reported as "V4 x/1"). If the device ID string in firmware/bootloader hasn’t been updated to match the new PCB label, the skill will show the older ID.
• In short: it’s frequently just a label/ID mismatch between firmware and physical silkscreen. It won’t usually affect operation unless a firmware feature specifically targets one hardware revision.

How to verify (stepbystep)

1. Connect to the EZB as you normally do in ARC.
2. Open the EZB webserver in your browser (when connected to the EZB WiFi): http://192.168.1.1
   • Go to the System / Info or Firmware page and note the Firmware Version and any Hardware or Board Revision fields shown there.
3. Run your Connection Diagnostic skill (you already have it): use the Ping / verbose log and look for the exact firmware/ID string printed there. Copy the log (Copy Log button).
4. Re-run the Firmware Update Tool (from the ARC EZB Firmwares page) and confirm it reports the latest firmware installed. If prompted, choose the firmware build that is explicitly for EZB v4 x/2 (if available). ARC EZB firmware info: https://synthiam.com/Support/Hardware/EZ-B-v4 and https://synthiam.com/Support/Hardware/Hardware-Overview
5. After updating, reboot the EZB and re-check the webserver and Connection Diagnostic log to see whether the reported string changed.

If the reported string still shows x/1 after reinstalling the latest firmware

• Most likely the firmware’s internal device string hasn’t been updated to reflect the new PCB printing - a cosmetic mismatch only. Functionally the controller will behave the same.
• If you want confirmation, paste the relevant lines from your Connection Diagnostic log (the lines that show the version string) and I’ll review it and tell you whether it’s purely an ID string or something to worry about.

What I recommend

• If the board works normally (servos, ADC, UART, audio work) you can safely continue testing - this is typically not critical.
• If you’d like definitive matching of label vs firmware, run the Firmware Update Tool one more time and then paste the Connection Diagnostic log here (use the Copy Log button). I’ll help read the log and confirm whether the firmware recognized the hardware or is simply returning an older identifier.

Want to paste your Connection Diagnostic log here (just the lines that show the EZB version) and I’ll verify?

Post a picture of the top board of your ezb

Also if you're connecting over COM/UART/USB it will show as a V1 because it isn't using the wifi module

OK, that explains this. I am connecting over Com/UART/USB.

To post a picture of the top board I'm going to have to pull the EZB from the robot. That will have to be later on after I get through this stage. Thanks,

you don't need to post a picture if you are connecting over com uart because that's why it's reporting v1

That’s expected behavior - good catch, and no cause for concern.

Short explanation

• When you connect over COM/UART/USB ARC talks to the EZ-B’s main controller over a serial link. The WiFi module (and its identifying string) is not queried over that path, so the skill reports the controller string that identifies as "V4 x/1".
• When you connect via the EZB WiFi (AP or client) and open the EZB webserver, the WiFi/board revision information (x/2) will be visible and reported by skills that query the WiFi module. In other words: USB/serial = V1 string; WiFi connection = x/2 string (if the firmware/bootloader reports that string).

How you can verify

1. If you can temporarily connect the EZB over WiFi, open the webserver at: http://192.168.1.1
   Check System / Info or Firmware - you’ll see firmware and (when accessed over WiFi) board/revision fields.
2. Use the Connection Diagnostic skill (Project Add robot skill Communication Connection Diagnostic) and copy the log (Copy Log button). The log will show the ID string ARC received on the link you used (USB vs WiFi).
3. If you want to, post the one or two lines from the Connection Diagnostic log that show the version string and I’ll confirm the meaning.

Links

• EZB v4 info: https://synthiam.com/Support/Hardware/EZ-B-v4
• Connection Diagnostic skill: https://synthiam.com/Support/Skills/Communication/Connection-Diagnostic?id=16164
• WiFi connection troubleshooting (if you want to switch to WiFi): https://synthiam.com/Support/troubleshooting/Troubleshoot-WiFi-Connections

Next steps / Offer

• If you’re fine continuing over USB/serial, you can ignore the cosmetic mismatch - functionality won’t be impacted.
• If you want definitive matching of the printed x/2 label with the firmware/bootloader ID, I can walk you through connecting the EZB over WiFi (or through the firmware update steps over WiFi) and re-checking the reported string. Would you like instructions to switch the board to WiFi (AP) mode now, or would you rather post the Connection Diagnostic log lines here?