pepperonichap
I am on a hp laptop running windows 7 with avast disabled. When I turn on my EZB it says that it has successfully connected to my network and when i try to connect to my EZB in client mode it connects and then disconnects after a few seconds, I then get this message:
EZB 0: EZB 1: EZB 2: EZB 3: EZB 4: 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 192.168.1.5: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 System.IO.Stream.ReadByte() at EZ_B.EZB.drdP31fe7H(Int32 , Byte[] cmdData) BbytesToExpect: 1 U Received: Disconnected Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.g0KPD37NHh() at EZ_B.EZB.Connect(String hostname, Int32 baudRate) Disconnected
The EZB can connect when I try it on my dad's computer.
Any help would be great.
@jackphillips1953
The new com board that is coming out soon uses a totally different WiFi chip and should not have this problem. (price and release date not announced yet, but DJ did say we would be able to upgrade existing EZ-B's and not need to buy new ones to get the new board). If the price of that is too high, possibly changing your router to one that responds faster to DHCP requests could be an option. The EZ-B only responds if it doesn't see another response on the network before it's timeout. EZ-Robot never saw the issue using D-Link routers which is why it was so hard for me to convince them of the issue. I do see it on TP-Link routers, which I otherwise love.
3rd option is the programmer that DJ discussed in that thread. I haven't had a chance to try it yet, but I believe you can use it to turn the feature off, or even give the EZ-B's static IP addresses on the network.
If I have time to get it figured out, I might set up a service for USA customers (don't want to deal with international shipping) to reprogram their EZ-Bs, but I'll say now that my time is very short so I don't know when I'll get around to it.
Until I got my new router (I upgraded to higher speed FiOS and Verizon replaced my router with one that responds very fast) I made sure to assign my EZ-B's the lowest available octets on the network and always started them in the same order. That solved the issue with the EZ-Bs not getign the expected addresses but did not help with other devices on the network starting after the EZ-Bs. Not satisfied with that, I got a cheap travel router (again a TP-Link that had the same slow response issue, but this was before I realized it was timing related) and plugged it into one of the LAN ports on my other router, so I was able to give the EZ-B's their own network on a different subnet. The routers handled passing traffic from PCs on the home network to the EZ-Bs on the robot network.
Alan
Everything I said would have made a lot more sense if I actually included the link to the thread I was talking about: https://synthiam.com/Community/Questions/7229
Sorry about that.
Alan
What has to happen is the when attached to network the DHCP server on the V4 must be turned off. No reason for it to on unless in AP mode.
I have 4 of these units plus 3 V3 and not going to replace these units.
I have done the static already using Mac address on router and no good.
So, only way to do that with the current chip is to get the PIK programmer described in the other thread and here: http://synthiam.com/Products/ARC and make a firmware that turns off DHCP. It can't be done from ARC or through a remote firmware updater.
The PIK programmer was really cheap (I think it cost me $16 shipped). I just haven't had time to work with it yet.
I may try and find some time this week. It is pretty much just you and me that are experiencing this issue, and I solved it when Verizon replaced my router, but it would still be an issue if I take my robots somewhere and use my travel router.
Alan
Ok. Let me know what happens when you reprogram.
Thanks.
BTW - I cannot believe other not having same issue. They probably just keep rebooting V4 and reset IP.
My equipment here is not that old and I may want to place this on a work network and cannot afford to have blow up DHCP on that network.
Thanks again.
Jack - it's a silly implementation of the dhcp on that module. It really isn't something that we're proud of, but it was the only capable module at the time available when the ez-b v4 was designed. The upcoming ez.b v4.x/2 will be available as an upgrade, which is an entire new communication board replacement. It is faster, has an up-gradable firmware and was custom created by ez-robot entirely rather than depending on a third party product.
In the meantime, if you wish to remove the dhcp completely from that module, the latest firmware is available in the Software section of this website - labelled OpenIoT. As alan mentioned, it requires a piece of hardware, which is less than $20. The links and all necessary information is provided to you with a step by step instruction.
Simply click on Software and the Open IoT link to get started.
Everything works great with my set up... and I use a cheap $40 Dlink router to boot... No rebooting needed... I assign all my ezbs static IPs and Bob's your uncle... Works great...