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.
Here are two of my ezbs connected...
Thanks Richard.
I just tried it again but still no joy. Funny, my router won't let me change the third set of numbers (mine being "0" and yours "255"). Don't know if that makes any difference. And I just realised what I said about "one board in client and another in AP", which wouldn't work anyway. This is a royal pain in the butt.
I guess it's back to the SSC then.
if you connect one on number 0 and the other on 2 it worked for me
@nomad.
That's exactly what I tried (mentioned in post #1) as I remember a post you made a while back saying as much.
Thanks anyway.
make one of them 192.168.0.2 and the other 192.168.0.3. Always start the one with 192.168.0.2 first. don't use the EZ-B search, just type 192.168.0.3 for the second one. As long as the first board is "2" whether your router responds first, or the first EZ-B responds first, the second one will be "3".
(the 3rd octet that you can't change would be changed in a different place in the router. Every device on the router needs the same 1st three octets -called the subnet- no need to change it though).
Note: you can have on in client and one in AP and still have internet access, but you need 2 wireless adapters in your computer and they can't be on the same subnet. Since your router is on the 192.168.0.x subnet and the EZ-B in AP mode is on 192.168.1.x, that would not be an issue.
Alan
I tried changing the last numbers to 100 and 200 and connected as you mentioned above, but the same problem persisted.
I also set one board back to AP but I was still unable to connect it to ARC, with the same "timed out" error showing. I'll try your advice again tomorrow with a clear head and see if I have any better luck.
Thanks again Alan.
So I tried again this morning following Alan's steps. I changed the IP reservations for both boards to .2 and .3 and nether connected. I then changed the reservation ip for board one so the v4's IP was 192.168.0.20, run a ping test which returned the correct info. I connected it to ARC and that was fine.
I then powered up the second board, changed the IP to 192.168.0.30 and ran the ping test again for the new IP, and got the following results (both boards saying that they "are now connected to your network")...
I'm not at a loss of what to do now. Is there anyone else using a Virgin media Superhub 2 with multiple boards who can help?
I'm thankful for the help offered to me so far, but I'd also appreciate some input from EZ robot on this, as it really shouldn't be this difficault to connect multiple boards. I'm now aware that there is a bug that Alan mentioned, but other people are managing to connect more than one v4 to their projects and I also know of members who have had trouble too, and as I mentioned, I know little about networking and routers. This reminds me of the trouble I had connecting a HP computer to an EZ-B when I first started.
Steve.
@steve,
i rode your post, but i must say i only know FritzBox or Netgear Routers.
But also a "Virgin media Superhub 2" must have a webinterface (like 192.168.1.1) and there mustbe wlan or Lan Settings.
And there normaly you can "add" new periphery. Normaly must open a popup window where you can fill in the data you want.
Then you go to the ARC and search for this two EZB4
(First you must connect the EZB4 Controller to new WLAN Net, but i think this you already have done)