DHT11 Temp & Humidity Sensor icon DHT11 Temp & Humidity Sensor — Read DHT11 temperature and humidity on Arduino (signal pin 4) using EZ-Genuino_DTH11_Uno firmware; exposes $Temp and $Humid variables. Try it →
Germany
Asked

EZ-B V4 Units Troubleshooting

Skip to comments   Jump to end

I have two older EZ-B v4 units that are causing problems. I don’t use them regularly-only occasionally for testing. i made 2,3 reset on both EZBs.  I’ve included logs for both devices.

The first one (EZ-B v4.x/2 c89346552d30) does not produce any sound at startup. I can connect to it, and the servos are working, but the soundboard does not work. I also connected via the web interface and confirmed that both "connection audio chime" and "startup audio chime" are enabled.

Could the speaker be faulty? If so, is it possible to replace it with a standard small speaker?

here is the debug log and the settings from the web interface for EZ-B v4.x/2 c89346552d30. The EZ-B Wi-Fi Robot Controller

Current Configuration
System Name:   EZ-B v4.x/2
SSID:   EZ-B v4.x/2 c89346552d30
WiFi Mode:   Custom AP Mode (Ad-Hoc)
System Uptime:   35 seconds and 404 milliseconds
Model:   EZ-B v4.x/2
Version:   WiFi 3165 v2018.09.30.00

Audio Chimes

Startup Audio Chime:   
ENABLED
 
Connection Audio Chime:   
ENABLED
 

Debug log:

Internet available: True
Another ARC instance already running: False
Current firmware src version is 2026.5.11.0
Available firmware src version is 2026.5.11.0. Downloading: False
Loading firmware src file
22 firmware sources loaded
Windows version: Microsoft Windows NT 10.0.26200.0
Synthiam account: [email protected]
Screen Resolution: 1920x1080 (96x96 DPI, 100% scaling)
ARC Pro Version: 2026.04.14.00
Adding 1 robot skill(s) to page 0:
 - ARC.UCForms.FormConnection (Connection)

Adding 1 robot skill(s) to page 0:
 - ARC.FormBookmarks (Bookmarks)

Discovered EZ-B v4.x/2 (192.168.1.1:23) (Type: EZ-B v4.x/2).
Discovered EZ-B v4.x/2 (192.168.1.1:24) (Type: Camera).
Attempting connection on 192.168.1.1:23
Connected to 192.168.1.1:23 (tx timeout: 2000, rx timeout: 2000, tx buffer: 20000 rx buffer: 20000)
Reports EZB v4 OS With Comm 2
Firmware 'EZ-B v4.x/2 Native Firmware' (0x02) on 'EZ-Robot EZ-B v4.x/2' supports the following capabilities:
 - ADC with 12 bit Resolution
 - Can stream Audio v4 codec
 - Reports battery voltage
 - Reports CPU temperature
 - Read/Write Digital I/O Ports
 - Hardware UART TX/RX with DMA buffer and adjustable baud rate
 - I2C Master
 - LIPO battery protection & shutdown
 - PWM Duty on digital ports
 - PWM servos on digital ports
 - PWM servos on digital ports can release their position
 - servo speed for PWM servos on digital ports
 - Has NVRam configuration and can be restored to default settings
 - Transmit Uart TX on all digital ports
 - Adjustable I2C clock speed
 - Configurable UART TX digital port baud timing
 - Ultrasonic Ping distance sensor support
 - 12 Byte Unique Identifier
 - Can stream video v4 codec
 - Native UART Connectivity from ARC
 - Native WiFi Connectivity from ARC
 - Broadcasts to ARC's PnP network scanner

EZ-B v4.x/2 Native Firmware ID: 65-49-0-0-221-255-58-57-58-37-38-38
Setting battery monitor voltage: 7.0
Setting battery protection: True
Setting i2c rate: 100000
EZ-B voltage is 8.16v
EZ-B temperature is 25.45c
Connected
Adding 1 robot skill(s) to page 0:
 - ARC.UCForms.FormSoundBoardEZBv4 (Soundboard v4)

The second unit (EZ-B v4.x/2 d0bae42be049) also does not produce any startup chime and does not connect at all. When I click "connect," it disconnects immediately. Here is the log output. I tested the battery on a third EZ-B v4 unit, and it works fine-the startup chime plays and the connection is stable. here is the debug log and the settings from the web interface for EZ-B v4.x/2 d0bae42be049

Current Configuration
System Name:   EZ-B v4.x/2
SSID:   EZ-B v4.x/2 d0bae42be049
WiFi Mode:   Custom AP Mode (Ad-Hoc)
System Uptime:   5 minutes, 9 seconds and 518 milliseconds
Model:   EZ-B v4.x/2
Version:   WiFi 3165 v2017.01.05.00
Audio Chimes

Startup Audio Chime:   
ENABLED
 
Connection Audio Chime:   
ENABLED
 

Debug log:

Attempting connection on 192.168.1.1:23
Connected to 192.168.1.1:23 (tx timeout: 2000, rx timeout: 2000, tx buffer: 20000 rx buffer: 20000)
Reports EZB v4 OS With Comm 2
Firmware 'EZ-B v4.x/2 Native Firmware' (0x02) on 'EZ-Robot EZ-B v4.x/2' supports the following capabilities:
 - ADC with 12 bit Resolution
 - Can stream Audio v4 codec
 - Reports battery voltage
 - Reports CPU temperature
 - Read/Write Digital I/O Ports
 - Hardware UART TX/RX with DMA buffer and adjustable baud rate
 - I2C Master
 - LIPO battery protection & shutdown
 - PWM Duty on digital ports
 - PWM servos on digital ports
 - PWM servos on digital ports can release their position
 - servo speed for PWM servos on digital ports
 - Has NVRam configuration and can be restored to default settings
 - Transmit Uart TX on all digital ports
 - Adjustable I2C clock speed
 - Configurable UART TX digital port baud timing
 - Ultrasonic Ping distance sensor support
 - 12 Byte Unique Identifier
 - Can stream video v4 codec
 - Native UART Connectivity from ARC
 - Native WiFi Connectivity from ARC
 - Broadcasts to ARC's PnP network scanner

TCP Comm Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Sent: 2
Bytes Expected: 12
Received (0 bytes):
Disconnected
EZ-B v4.x/2 Native Firmware ID: 0-0-0-0-0-0-0-0-0-0-0-0
Setting battery monitor voltage: 7.0
Setting battery protection: True
Not connected attempting to initEZB from Connection Control. System.Exception: Not connected
   at EZ_B.Uart.SetBaudClock(BAUD_RATE_ENUM baudRate, Int32 clockSpeed)
   at ARC.UCForms.FormConnection.hrVHhV7oqIydvt2LgltD(Object , BAUD_RATE_ENUM , Int32 )
   at ARC.UCForms.FormConnection.R2FeOqaDLRW(Int32  , ConfigurationFormV2  )
Connected
EZB Not Responding:Unable to connect to 192.168.1.1:23. This PC appears to be connected to a network with the IP address that was specified. However, the connection could not be established with the EZB.

Would you like to view the tutorial for connecting to WiFi EZB devices?

Related Hardware (view all EZB hardware)
EZ-B V4
EZ-B V4 by EZ-Robot
EZ-B v4/2 robot controller: dual Cortex ARM, Wi-Fi, audio/video, 24 servo/digital ports, I2C/UART, camera and Synthiam ARC control for custom robots
Wi-Fi / USB
Servos 24
Camera
Audio
UART 3
I2C
ADC 8
Digital 24

Related Robot Skills (view all robot skills)
Thumbnail
Soundboard (EZB) by Synthiam
Play WAV/MP3 via EZ-B v4, manage tracks, add timed scripts for synced robot actions, control via ControlCommand(), volume and clipping indicators.
Requires ARC
Audio
Thumbnail
Connection Diagnostic by Synthiam
Diagnose EZ-B Wi-Fi connection issues with verbose EZ-B communication logging, ping tests, log export and diagnostic reports for Synthiam support.
Requires ARC v6
Communication
Jump to end

ARC Pro

Upgrade to ARC Pro

Unlock the true power of automation and robotics by becoming a proud subscriber of Synthiam ARC Pro.

Author Avatar
PRO
Canada
Twitter YouTube GitHub
#1  

Thanks - good details and logs. Short summary of likely causes and a prioritized troubleshooting plan below so you can isolate which unit needs repair or part replacement.

Summary diagnosis (from your logs)

  • EZ-B v4.x/2 c89346552d30 (Unit A)

    • ARC connects, servos work, camera discovered.
    • No startup / connection chime audible even though chimes are enabled.
    • EZ-B reports normal voltage (8.16 V) and firmware ID returns valid values.
    • Likely causes: speaker failure / speaker connector loose / audio amplifier issue or speaker wiring. Because the board and I/O are responding (servos/camera) the lower-board communication looks OK.

  • EZ-B v4.x/2 d0bae42be049 (Unit B)

    • Web UI accessible, but ARC connection fails immediately; firmware ID is all zeros in the log and connection TCP errors appear.
    • This pattern (top comm board reachable but lower I/O board not responding / firmware ID = zeros) matches the "EZB Not Responding / I/O processor not returning firmware ID" case described in the docs - commonly a damaged bottom I/O board or failure in the inter-board communication.
    • Less likely: transient network/firewall problem (since your other EZ-B and battery behave normally).

Stepbystep troubleshooting (do these in order)

  1. Quick checks and information I need
  • What LED pattern/colors do you see at boot for each board? (solid red/blue flashing/etc.)
  • Does the camera stream work for each unit (open camera page in ARC or browser)? You said servos work on Unit A; does its camera stream?
  • Can you physically swap the speaker between Unit A and Unit B (or test Unit A’s speaker on the working third EZ-B)? This is the fastest way to confirm speaker vs board.
  1. Test playing audio from ARC (software test)
  • In ARC, add the Soundboard (EZB) skill and try:
    • Play a random track:
      controlCommand("Soundboard v4", "Track_Random")
    • Or play a named file (replace filename):
      controlCommand("Soundboard v4", "Play", "audioFile.mp3", true)
  • Watch the ARC status/log while doing this. If ARC reports the audio command sent to the EZB but nothing audible, that points to speaker/hardware.
  1. Physical speaker check (Unit A first)
  • Power OFF the EZ-B (disconnect battery).
  • Open the case and locate the speaker connector on the bottom board. Reseat the connector (unplug and plug back in).
  • Check speaker wiring and connector for corrosion, bent pins, or cold solder joints.
  • With a multimeter, measure speaker resistance across its leads. Typical small speakers read a few ohms to tens of ohms (if open circuit / infinite resistance, the speaker is bad).
  • If you have a known-good speaker (from the working EZ-B), swap it in and test audio again.

Speaker replacement guidance

  • Yes - you can replace the internal speaker with a standard small speaker, but use a conservative safe choice:
    • Typical replacement: 8 impedance, rated ~0.5 W to 3 W (small speakers 0.5-2 W are common).
    • Keep the speaker small so it fits the enclosure (often ~0.5-1.5" diameter).
    • Ensure polarity and connector match (or solder leads to the speaker connector pins). Always power OFF when connecting.
    • Avoid high-power speakers that present low impedance or short circuits that could overload the on-board amplifier.
  • If you want, tell me the physical dimensions of the factory speaker and I’ll recommend a specific impedance/power size to match.
  1. Firmware / config tests (Unit B)
  • In the web UI you can try a factory reset (restore defaults) and power-cycle:
    • On the web UI choose Restore Defaults (or press/reset per hardware manual) then power-cycle and try connect again.
  • Use the Connection Diagnostic skill in ARC (Project Add Skill General Connection Diagnostic) and run its ping/log tool while attempting to connect. Save/copy the diagnostic log and post if it changes since your logs above.
  • If the firmware ID still reads all zeros and TCP disconnects immediately, that likely means the bottom I/O processor is not responding. This is usually hardware damage on the lower board (see Synthiam docs). Reflashing top WiFi firmware won't help if the I/O processor is dead.
  1. Electrical check (if comfortable)
  • With the unit powered on, measure the voltage present at the speaker connector (careful): if audio is commanded, you may see AC variations on the speaker pins. If you see stable DC with no AC while playing audio, that suggests amp/signal issue.
  • Check continuity between the top board and the lower board board-to-board connector if you open the unit - look for broken pins, cracked solder joints.
  1. Repair / replacement options

What I recommend you try next (in order)

  1. Swap speakers between Unit A and your confirmed-working EZ-B. Report whether the chime follows the speaker.
  2. If swap not possible, open Unit A and reseat/inspect speaker connector and measure speaker resistance. Report result.
  3. For Unit B: press/reset to factory defaults from web UI, power cycle, then run Connection Diagnostic in ARC and paste the new log here. Note LED pattern on power-up (solid red? solid blue? flashing).
  4. If you want, I can walk you step-by-step through opening the unit and testing the speaker and board voltages (tell me which tools you have: multimeter, small screwdrivers, spare speaker).

Tell me results of the quick tests (LED patterns, camera working, speaker swap / resistance reading) and I’ll give the next exact steps - including safe speaker replacement instructions or board-level checks for the likely I/O-board failure.


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.
Login to post a comment