
Steve1DH

So I've got my EZ-B v4. It works in AP mode and connects to my network in Client mode. So far so good. When I scan in ARC , the EZ-B gets located, but it disconnects and requires a firmware update. No problem I thought.
When I get into the firmware update I see that it will only connect to the EZ-B in AP mode, so I reset the EZ-B to be in AP mode and I connect in the firmware, but I get an error. (screen shot below)
I thought I would rule out an issue with my laptop so I installed ARC on my son's laptop and tried all of the above actions and got the same error.
I hope I'm just missing something and it's an easy fix.
@DJ I have attached a zip of the logs just in case they are needed.
Logs.zip
I haven't needed to update mine. I just updated to the latest ARC and connected again without needing to update firmware...
Code:
And there are times where it doesn't give this error but the debug states the following-
EZB 0:
EZB 1:
EZB 2:
EZB 3:
EZB 4:
2014-05-28 2:03 PM - TCP Server stopped
2014-05-28 2:03 PM - TCP Server stopped
2014-05-28 2:03 PM - TCP Server stopped
2014-05-28 2:03 PM - TCP Server stopped
2014-05-28 2:03 PM - TCP Server stopped
2014-05-28 2:03 PM - Attempting connection on 192.168.0.112:23
2014-05-28 2:03 PM - *Warning: There is 10 bytes of unexpected data available on the TCP connection... Clearing
2014-05-28 2:03 PM - Unexpected Data: 27 91 50 74 27 91 49 59 49 102
2014-05-28 2:03 PM - Connected to 192.168.0.112:23
2014-05-28 2:03 PM - EZ-B reports EZ-Robot OS v25.5
2014-05-28 2:03 PM - Welcome to EZ-B v3!
2014-05-28 2:03 PM - Connected
2014-05-28 2:04 PM - *Warning: There is 74 bytes of unexpected data available on the TCP connection... Clearing
2014-05-28 2:04 PM - Unexpected Data: 251 1 255 251 3 255 253 3 87 101 108 99 111 109 101 46 32 84 121 112 101 32 60 114 101 116 117 114 110 62 44 32 101 110 116 101 114 32 112 97 115 115 119 111 114 100 32 97 116 32 35 32 112 114 111 109 112 116 13 10 255 251 1 255 251 3 255 253 3 7 13 10 35 32
2014-05-28 2:04 PM - 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 System.IO.Stream.ReadByte()
at EZ_B.EZB.(Int32 , Byte[] )
2014-05-28 2:04 PM - BbytesToExpect: 1
2014-05-28 2:04 PM - U
Received:
2014-05-28 2:04 PM - Disconnected
2014-05-28 2:04 PM - Disconnected
2014-05-28 2:04 PM - Disconnected
Hope this helps with the diagnosis. *confused*
Does it do that on every device (PC, laptop, windows tablet) you have tried to connect with?
EZB 0:
EZB 1:
EZB 2:
EZB 3:
EZB 4:
2014-05-28 2:17 PM - TCP Server stopped
2014-05-28 2:17 PM - TCP Server stopped
2014-05-28 2:17 PM - TCP Server stopped
2014-05-28 2:17 PM - TCP Server stopped
2014-05-28 2:17 PM - TCP Server stopped
2014-05-28 2:18 PM - Attempting connection on 192.168.0.112:23
2014-05-28 2:18 PM - *Warning: There is 19 bytes of unexpected data available on the TCP connection... Clearing
2014-05-28 2:18 PM - Unexpected Data: 27 91 50 74 27 91 49 59 49 102 255 251 1 255 251 3 255 253 3
2014-05-28 2:18 PM - Connected to 192.168.0.112:23
2014-05-28 2:18 PM - EZ-B reports EZ-Robot OS v8.7
2014-05-28 2:18 PM - Welcome to EZ-B v3!
2014-05-28 2:18 PM - Connection Failed: System.Exception: Invalid EZ-Robot OS Version. Please Upgrade.
EZ-B Reports v8.7. This copy of ARC requires v16.6
Would you like to view the help tutorial with instructions on how to upgrade the EZ-Robot OS?
at EZ_B.EZB.Connect(String hostname, Int32 baudRate)
2014-05-28 2:18 PM - Disconnected
I think your right that ARC thinks it's connecting to a v3.
Just trying to think of what else DJ & co may need to know to solve this one.
There is no EZ-B v4 firmware update. As the release notes say, it is for the V3 only: http://www.ez-robot.com/Community/Forum/posts.aspx?threadId=5652
The ip address you are connecting to is not an EZ-B v4
If you scan the network, you will find that there will be another device accidently answering with the same message as a v4. This is something we can't control. Because we do not own every network device ever made, other devices will occasionally respond with a similar connection string.
You can see that your images and copy and paste text have different ip addresses. For example, in one image you are connecting to 192.168.1.12 and the text is 192.168.1.11
If you are connecting in AP Mode the ip address is 192.168.1.1 and never changes.
If you are connecting in client mode, you must find the proper ip address for the ez-b v4. Use the scan tool to find it. You can watch this video to help:
I was even running in AP mode along with an network cable plugged in so I still had an internet connection.
When I use the scan tool it also picks up my router. I assume the scan tool scans for a specific open port or something similar which other devices may also have, therefore making it seem like it's found an EZ-B V4 when the reality is it hasn't.
The device on the IP address not being an EZ-B didn't cross my mind however I have just double checked what DJ has said and can confirm that when I use my router IP it gives the same error message and info about a firmware upgrade.
I think we have success.
It may be an issue similar to what Dave is battling with in as much that the DHCP server of your router isn't correctly assigning the EZ-B with an IP. This can be due to many things.
Most commonly it is the MAC filtering. Make sure that if it is enabled that your EZ-B is in the allow list.
The EZ-B will think it's connected to a network if your router assigns a 169.x.x.x IP address due to router settings (and even sometimes poor routers - my brothers does this if more than a handful of devices are connected on the WiFi)
However ARC will always connect to the first EZB and I've never gotten that firmware update message.
I've moved my router within a few feet of my EZB's exploring signal strength as a possible cause and still had the problem. I have no idea what's happening here. I've got a new router arriving tomorrow. I'll see if that helps.
Also In my router my MAC Filter is off along with my firewall trying to eliminate any possible problems, Didn't help.
@DJ said in a previous post that he had success keeping his EZB from connecting to outer devices. Not sure what he meant or what that means to us. *confused*
I think ARC v2014.05.29.00 may be on it's way and hopefully DJ will add some of the details to the Release Notes.
What it means to us? Less confusion like Steve originally had in this topic.
Thanks everyone for the help and suggestions.
@Rich - my router sees the EZ-B but it does not want to show me an IP for it, it just had it as static. The only way to know what device was the EZ-B was to toggle the EZ-B on and off to see what MAC address changed. Like I said there was no IP shown for the EZ-B, or at least not anywhere in the router software that I could find with my little networking knowledge.
As I was messing with my old router (yes now it's old apparently (just under 3yrs)) I found out D-Link discontinued it. *confused*
So... I was able to convince my loving wife to let me get a new router. Thanks for the help on that Dave. I had my wife (since she was out) pick up the ASUS RT-AC66U.
Hooked it up and got everything going in a flash.
Once again, thanks to everyone who assisted with this but the I have to give the credit to.... This is hard. Now I know why everyone has trouble with this. Since Rich stuck it out and kept directing me in where to look, I give it to him.
Thanks Everyone.
Just on the router side of things, my recommendation will always be a router which is capable of running DD-WRT firmware (the most awesomest of firmwares out there IMO). I know all Buffalo routers come with this as standard now but it can be put on many others.
DD WRT homepage
Supported Devices
The Asus RT-AC66U is on the list too. A very worthwhile upgrade in my opinion but probably not for the feint of heart.
You'd have to check the settings of the "all in one" for an option to enable "modem mode" (or words to that effect) to be sure.
You can get routers with cable modems built in, my ISP needs to enable the MAC address for it to work but that's a simple process. It's usually down to the ISP for that requirement though, some don't care.