garyisle
The EZB V4 will not connect to ARC. This projects uses two EZB's: EZB 0 and EZB 1. During a normal power cycle EZB 1 stopped connecting to the ARC app. The other unit EZB 0 continues to operate normally. The EZ builder connection widget provided a notification that it was unable to connect to EZB 1. These units are configured as a WIFI clients each having reserved IP's. I was able to open a browser and connect to the EZrobot web page with the reserved IP. Using the Diagnostic options each of the speaker options 1-8 where selected resulting with the same no audio response. The unit was reset the unit to factory defaults and I was able to log into the web management page via default IP of 192.168.1.1 I tried again the to troubleshoot via the diagnostic options with the same non responsive results. Using the ARC and joining the EZB V4 network via WIFI AP mode at factory defaults the ARC connection widget timed out with the same error. The error log is show below.
Attempting connection on 192.168.1.1:23 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.tR50VFKnEn(Int32 , Byte[] cmdData) BbytesToExpect: 1 U Received: 0 Disconnected Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.eWZ0XeVRYw() at EZ_B.EZB.
what is my next recourse to get this unit up and running again?
I’d take a look at ezrobot’s connection tutorial on their website. But sounds like you may have already tried connecting directly with a factory reset.
The first thing to identify that ezrobot’s website would say about their product is does the ezb make a chime and verbal introduction when powered on after reset?
if it doesn’t, you’ll need to contact ezrobot for product support with this link: https://synthiam.com/About/Contact-Us.aspx
Thanks for posting. It does not chime or make a verbal intro during power up. I will reach out to support.
I noticed that two ezb’s successfully connected on December 15, 2019. Are those the two that are not connecting now? The hardware id’s start with....
If those are the two that worked a few days ago. The question is what has changed on their configuration or the network or your computer in that time? Any power changes or wiring changes?
Those are the units that are being used for the project. The wiring, power and networking have remained the same up till the connection error. V2 has no issues at all.
Do you have a sketch or schematic of what is connected? If something shorter the main micro out, it’ll be worthwhile to identify if something can be altered before replacing with a new unit.
I have the same problem on a regular basis. EZ-B connects, and is working for (quite) some time but sometimes it simply drops the connection with an error. After that I sometimes can connect again, and sometimes I need to power cycle. Untill now I was "blaming" the WIFI and figured out to skip the WIFI and connect the EZ-B via USB to the onboard NUC, but reading this above maybe wise to drop also a reply to notify I recognize this problem
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.qqHrqKBCUx(Int32 , Byte[] cmdData) BbytesToExpect: 2 ? Received: 0 0