wib011
Resolved by DJ Sures!
I'm hoping someone can help. I have searched and found this topic mentioned several times and I have tried the solutions offered but still no luck. I have done both a firmware update and updated to the latest version of ARC. When trying to connect I get the following message: This device is not an EZ-B. Please follow the online tutorials on the EZ-Robot website. I have tried re-installing/repairing ARC. I currently connect my developer kit through the router. I have reset back to factory settings and connect directly to the ez-b v4 but still get the same issue. I have tried using EZ-B firmware update V4 where I get the following: attempting connection on 192.168.0.53:23 connected to 192.168.0.53:23 Reports 69 and then in a separate window I get the This device is not an EZ-B error. When I click on the Scan for EZ-B v4 it finds two options: EZ-B v4.x/2(192.168.0.53:23)(Type: EZ-B v4.x/2) EZ-B v4.x/2(192.168.0.53:24)(Type: Camera)
If I select the top option and select connect I get the This device is not an EZ-B error and this dialog in green and black at the bottom of the screen:
EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: Windows version: Microsoft Windows NT 10.0.15063.0 Screen Resolution: 1366x768 (96x96 dpi) Version: 2018.05.01.00 Attempting connection on 192.168.0.53: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.FwDTDUYvh5(Int32 , Byte[] cmdData) BbytesToExpect: 1 U Received: 0 Disconnected Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.pvK1h1uI5L() at EZ_B.EZB.Connect(String hostname, Int32 baudRate) Disconnected
If I select the camera option it says connect to EZ-B, not a camera. Batteries are fully charged but don't understand why it is no longer communicating with the PC?
Are you connected WiFi to ezb and an Ethernet connection?
Hi DJ Sures, I'm connected normally wifi through the client method (EB-B connects to my internet and I connect to it through my local router) but get the same results if I reset and connect directly via wifi from my computer to 192.168.1.1 with no internet connection.
Something is definitely interfering with the connection request. And what ever it is returns a capital letter E
Is there a virus scanner or aftermarket firewall running?
Hi DJ Sures,
That's it! I have avast running and even though I've been using it before without any problems, now I'm getting an issue with avast webshield. Turn this off and it connects fine. Having a look in the community under avast I found this:
modify the WebShield.ini in programdata\avast , programdata not programfiles..
Go to (your):\programdata\avast software\avast, Find WebShield.ini, add the following lines:
[General] UseStreamFilter=0
Restart PC.
I'm going to try this next but at least I can connect again. Thanks so much for your help
Great work!
Avast has been the cause of more ARC issues than any other AV/Firewall package out there. There are others that block the connection, but they all throw an error saying a connection was blocked and asking if you want to allow it. Avast just considers port 23 to be dangerous and blocks all connections (they are not wrong that port 23 can be bad, but more-so on inbound than outbound connections, and they should alert the user).
Alan
Yup I had to abandon Avast. So many hours lost to trouble shooting what was going on. Once I traced it to Avast, I removed and issues disappeared.