I'm trying to connect two v4's in one project, but no dice. I know someone had this trouble before, but can't find the thread.
They are both set to client mode, and the both connect individually. I've...
Reset the router, Turned off firewalls, Restarted ARC, Restarted my PC, Disabled antivirus and batteries are fully charged,
but none of that makes any difference. I have one board connecting to #0 and the other on #2. When I run a board search, only one will show up which I think is the last one that successfully connected. When I kill the power to one of the v4's, the other connects fine. As some of you probably know, I'm no networking expert by any stretch of the imagination, but I'm sure I've done right.
Any help would really be appreciated with solving this.
@Steve.... Remember there is always a workaround.... Most of my good ideas came from dead ends and a nap believe it or not.... I either break something or get frustrated because something I think I need badly doesn't work.... I lay down for a nap or just take a break and out of nowhere I get an even better idea.... Here's the thing... I wouldn't have come up with a better idea if I didn't hit a wall in the first place... The cliche is... "One door closes, another one opens..."
@Steve, I feel your pain. Before my ISP replaced my router a couple of weeks ago with one that responds very fast to DHCP requests, I actually had 3 routers in my network. My ISP's router, which I disabled WiFi on because it didn't support current security standards or high speed. Then plugged into that, two wireless routers.
One was my main network for all my computers (192.168.1.x subnet) and the other just for EZ-B's (192.168.0.x). I added route tables so the routers could see each other so a computer on the 192.168.1.x subnet could see the EZ-Bs on teh 192.168.0.x subnet.
The EZ-B router was a travel router powered by USB, so I could unplug it and take it with me if I travelled with my robots and not need to reset them to AP mode or connect them to different networks (I still have it configured with the same credentials as the main router for just this reason, but it is unplugged now).
I still needed to start the EZ-B's in the right order because once one was running, it would hand out IP addresses to the additional EZ-B's, but it was consistent. If EZ-B-1 was 192.168.0.2, then the next EZ-B to start would get 192.168.0.3, the next would get 192.168.0.4, etc.... (I traded my additional ones for wheelchair motors, so just have two now).
If you were in the US so that shipping wouldn't be an issue, I would send you a router that I know works this way, since I have ended up with several spares (I am an occasional Beta tester for one of the router companies). They all are slow to hand out addresses, so don't mask the EZ-B DHCP problem, but they do work with the workaround I described.
Alan
@Richard.
I'm usually the same in regards to having a beer, sleeping on it and getting new ideas. It's just over the past couple of days, I've been fresh out of them (ideas that is, not beers). Anyway I'm in a better frame of mind today and hooked up my SSC and scripted some of my servos thanks to your tutorial, so I'm kinda back on track.
@Alan.
That would have been a very kind offer and I really do appreciate the thought. Thank you.
I'm sure one day I'll get around the multiple board issue and may even consider getting a replacement or additional router for future projects that will use more than one v4.
I am still hoping that DJ gets a solution from the WiFi board manufacturer, and one that can be done without replacing the board. it should just be a command (technically, it should know to turn off DHCP when given the command to go into client mode, but there are reasons for having a DHCP server on a device other than the router, so it is probably configurable).
Alan
@Alan.
Same here. I hope that a solution presents itself form the manufacture soon. I'm certainly not getting a new router any time soon just for this. Only if I need a new one for some other reason as well.