Just tried to upgrade one of my robots with EZB V4 hopping to get something much faster and also to overcome some serious issues and limitations due to EZB V3 losing Digital ports one after the other.
1) This expensive piece of hardware does something totally unbelievable : it CHANGES MY NETWORK'S GATEWAY to its own client's address... How is it even POSSIBLE ? *confused*
2) Both the EZBs' I got are EXTREMELY SLOW. If I don't disable most of the sensors connected to it, and this EVEN in AP MODE, digital ports will simply take up to 30 seconds to respond. In AP mode N mode it is a little bit faster, but still at a pace that makes running any script useless. I also varied the milisecs for all of them, even at 2 seconds delays I have some little improvement only and no one can seriously hope to use a 2 seconds delay on an IR sensor, right?
I tried from different routers, without routers (AP modes) and the only thing that will make it work properly is turning off almost all sensors (2 ulstrasounds, 3 IRs', 2 currents meters and a lux sensor).
Has anyone met the same 2 problems ? I will try to change the power source, especially the power regulator that I use and see if it does something in terms of transfer rate. For the first SO WEIRD problem, here, I'm stuck... no idea what could do that the EZB takes over the router's address on my network forcing me to set all my computers on fixed ip addesses... . It should not be possible at all.
Thanks for your help,
Upgrade to ARC Pro
Your robot can be more than a simple automated machine with the power of ARC Pro!
The router which has DHCP server on my network used to be a Linksys E8350 (not really the kind of "cheap router" or "old router" that you and Alan referred to in your posts.
Now I have a brand new Netgear Nighthawk X6 R8000 and STILL THE SAME problem.
Lately, after creating a robotics class, I wanted to order 10 units of EZBV4 but I was asked not to by my School's IT director due to the fact that this issue ALSO HAPPENS ON OUR NETWORKS at school.
EZB is a great product but on that one your manufacturer messed up pretty well. It is not acceptable that such a device takes over our routers the way it does.
Here are the facts :
IF and ONLY IF my DHCP server is on the same subnet and same IP address base (192.168.1.x) THEN no problem. BUT AS SOON AS it is logged on a wifi network that uses a different subnet and/or simply a different address (like 192.168.5.x at work or 192.168.10.x at home) EZB ASSUMES that there's no DHCP server on the network.
Please, try using it on a different subnet, you'll see, the bug is systematic. This is annoying, not counting my wife yelling when she can't get Internet access on her macbook (@Alan knows that I know how to resolve that issue, it's simpler than this dhcp server issue... )
Sorry for the lashing out here... but I've been trying everything for days until I found out today that this is purely due to subnet or address format difference and therefore that there's nothing I can do. I can change my infrastructure at home, but not at work... it's simply and purelly going to be a loss for you. And we are in the center of Manhattan, and a famous school and a lot of people are looking at what we do. You want me to continue using your hardware... really. Sorry to use this stick and carrot here, but this is truly unbelievable that there's still no fix for this.
Thank you for your understanding.
The dhcp on the current v4 has an issue with some hardware. The upgraded firmware from the tutorial will fix that: http://synthiam.com/Products/ARC
EDIT: I just deleted what I wrote. I struggle with people who do business like this. The American educational system and a lot of the pompous people who work in it are an embarrassment to the American taxpayer. *blush*
Since when the new ones don't have this issue any longer ? Because I received two more not so long ago, like a month or two ago and they still have that issue.
@DJ thanks for you kind answer and again, sorry for expressing my frustration this way.
Happy robot building and hope you get your issue resolved.
The PIK tool is cheap and the flashing is pretty simple. You can also give them recognizable default SSID's which is useful. Just be sure to give each a unique MAC address and don't just flash the default firmware from the download.
i just wanted to say ,you are all great and annest people.
and this forum can take the abuse we do sometimes.
one thing i now for sure.i trust people who gets verbal sometimes.
and show there frustrations.ive seen amazing stuff here on forum.
talking about helping people aldo it looks like waisting your time.
when am here on the forum,it feels like comming home.
Have you eventually made this tuto to connect multiple EZBs together? I tried to make one client to a second one without success.
All of my EZ-B'S have now been flashed with the latest WiFi firmware, so even if it works for me it is no guarantee it will work on the old firmware, although really the bug you were seeing was the second EZ-B being a client of the first instead of a client of your router. If just using 2 EZ-B, that should work putting one in ap mode and the other as a client to the first. Adding a 3rd in client mode without flashing the WiFi chip could see the same issue.
2) Also, how are connecting to the wifi? Is it direct adhoc or client mode through router
3) lastly, you can check what version of wifi you have. There's a the robot program episode that shows or you can READ the ez-b v4 upgrade page here: http://www.ez-robot.com/Shop/AccessoriesDetails.aspx?prevCat=101&productNumber=51