USA
Asked
Resolved Resolved by DJ Sures!

EZ-B V4 No Longer Connecting, Shows Firmware 0000000

Skip to comments   Jump To End

Please see below the logs when trying to connect from connection diagnostics

How do I fix this? It was working perfectly until today

EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: Windows version: Microsoft Windows NT 10.0.17763.0 Screen Resolution: 1280x720 (96x96 dpi) EZ-Builder Version: 2019.05.08.00 Attempting connection on 192.168.1.1:23 Connection Failed: System.TimeoutException: The operation has timed out. at EZ_B.EZB.Connect(String hostname, Int32 baudRate) Disconnected Attempting connection on 10.10.10.1:23 Sending: 85 clientStream.Read Expecting: 1 bytes Received: 42 Connected to 10.10.10.1:23 Reports EZB v4 OS With Comm 2 Firmware 'EZ-B v4.x/2 Native Firmware' 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

Sending: 2 Comm Err: System.IO.IOException: 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. ---> System.Net.Sockets.SocketException: 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 at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at EZ_B.EZB.mSZQFbMyx5(Int32 , Byte[] cmdData) BbytesToExpect: 12

Received: 0 0 0 0 0 0 0 0 0 0 0 0 Disconnected EZ-B v4.x/2 Native Firmware ID: 0-0-0-0-0-0-0-0-0-0-0-0 Connected Attempting connection on 10.10.10.1:23 Connection Failed: System.TimeoutException: The operation has timed out. at EZ_B.EZB.Connect(String hostname, Int32 baudRate) Disconnected Attempting connection on 192.168.1.1:23 Sending: 85 clientStream.Read Expecting: 1 bytes Received: 42 Connected to 192.168.1.1:23 Reports EZB v4 OS With Comm 2 Firmware 'EZ-B v4.x/2 Native Firmware' 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

Sending: 2 Comm Err: System.IO.IOException: 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. ---> System.Net.Sockets.SocketException: 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 at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at EZ_B.EZB.mSZQFbMyx5(Int32 , Byte[] cmdData) BbytesToExpect: 12

Received: 0 0 0 0 0 0 0 0 0 0 0 0 Disconnected EZ-B v4.x/2 Native Firmware ID: 0-0-0-0-0-0-0-0-0-0-0-0 Connected Attempting connection on 192.168.1.1:23 Sending: 85 clientStream.Read Expecting: 1 bytes Received: 42 Connected to 192.168.1.1:23 Reports EZB v4 OS With Comm 2 Firmware 'EZ-B v4.x/2 Native Firmware' 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

Sending: 2 Comm Err: System.IO.IOException: 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. ---> System.Net.Sockets.SocketException: 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 at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at EZ_B.EZB.mSZQFbMyx5(Int32 , Byte[] cmdData) BbytesToExpect: 12

Received: 0 0 0 0 0 0 0 0 0 0 0 0 Disconnected EZ-B v4.x/2 Native Firmware ID: 0-0-0-0-0-0-0-0-0-0-0-0 Connected

Related Hardware EZ-B v4
Related Controls EZB Connection EZ-B v4 Info Connection Diagnostic EZB Connections

ARC Pro

Upgrade to ARC Pro

Don't limit your robot's potential – subscribe to ARC Pro and transform it into a dynamic, intelligent machine.

PRO
Synthiam
#1  

Does the ezb make the startup sound when power is applied? Why does the IP address in your log keep changing from 192.168.1.1 to 10.10.10.10?

Did you read the diagnostic connection info about firewalls and virus scanners?

#2   — Edited

I connected first straight to the EZB access point, then connected in wi-fi mode and test again. Firewall and anti-virus both disabled. Was working perfectly until powered today and had this issue. I disconnected the EZB speaker (needed the space) so not sure about booting sounds from the board

#3  

DJ thank you for your prompt response. After resetting EZB multiple times, I was able to connect to it and updated firmware. Seems to be working fine again

Thank you

#4  

DJ

Thank you. It is resolved but once in a wile I get this disconnections and does not allow to reconnect until multiple tries. I will let you know if it keeps doing it. Thanks for your support

Login to post a comment