I am having problems connecting to 2 EZB's at the same time. I have 2 EZBv4's on my InMoov robot. Whichever v4 I turn on first it will connect to but not the other.
I have set the static IP's for both controllers into my router (Asus RT-N12B1) and when I scan the router to see the connected clients, it will only show the first controller that was turned on. I have my router 6 ft from the controllers and my computer is connected to the router with a cable.
I am very familiar with setting up the v4's in client mode so that is not an issue.
I have in the past been able to connect to both at the same time, however, I had to shut everything down and now I can't them both to connect again. I have reset the controllers and started all over again but no luck.
Very frustrated! Thanks
Upgrade to ARC Pro
Unleash your creativity with the power of easy robot programming using Synthiam ARC Pro
I have 2 EZ-B's, and I have them both set with their MAC addresses reserved in my router.
One gets IP address 192.168.1.105 and the other gets 192.168.1.106.
Whichever one boots up first successfully gets its address. whichever one boots up second gets 192.168.1.2, doesn't show up in my DHCP client list (I found it using the ARC find EZ-B function) and the router log shows this set of errors:
if I reverse the startup order, it is the MAC of the other EZ-B and the address of 192.168.1.106 which is offered and refused.
My router is a TP-Link Archer C8 if that makes any difference.
Again, the first EZ-B to start got an address from the DHCP server (192.168.1.105, since I have some other devices that had leases, either permanent, or that grabbed them first for 100-104), and the second one rejected the offer of 192.168.1.106 and came up as 192.168.1.2.
Going to try one more time, but setting my router to start handing out addresses at 192.168.1.2 and see how the EZ-Bs respond.
More to follow.
What I want to test though is whether there is a number range where they will except permanent address assignment or negotiate DHCP correctly and a range where they won't, which is why I need to reset the router to give out lower range IP addresses. My wife is chatting with a friend, so it may be a while (and maybe tomorrow since it has been a long day and I kind of want to go to bed soon).
I changed my server to start handing out addresses beginning with 2 instead of 100. Both EZ-Bs successfully negotiated DHCP with no logged errors. One got address 2, and the other got address 3. (my other running computers kept their addresses over 100 because their lease had not expired during the reboot, and two of them have permanently assigned addresses).
I then set those as the reserved addresses, and could still reboot in either order and they would keep the addresses.
However, when I assigned 5 and 6 instead, again, only the first booted would get the assigned address, and the second would fail the negotiation and would take address 2.
Setting the reservations back to 1 and 2 and it worked again, with no errors in the logs regardless of the boot order.
I also discovered they are doing some kind of interaction with each other because while testing the batteries got low on one of the devices and it kept disconnecting and reconnecting to the network. Once I unplugged it to change the batteries, the other EZ-B immediately disconnected from the network and needed to be restarted to connect.
I may try to set up Wireshark to sniff the network (not sure if any of my laptops have WNIC capable of network sniffing. I used to have one, but it was 802.11g only) just because I am curious about what interaction is occurring, but for now the simple solution is to set your router to start handing out addresses a the lowest possible octet, and reserve the lowest possible IP addresses for the EZ-Bs and they will work with reserved addresses.
I haven't restarted my router or changed much since then however. I haven't installed any ARC updated in months either. I have noticed that I'll have conflicts with other devices with static IP's on my network when my EZB's are connected. Then sometimes those other device won't connect. Example would be my ipod. If I connect to the two EZB's first the ipod usually can't connect to the network. My wife has problems with some of her devices connecting to our network also. I haven't looked for help on this as I was thinking it was a conflict with the way I have my static IP's listed. If I redo the static IP's for the non connecting devices that seems to clear it up. However I just mention this to maybe illustrate that there may be an DHCP handling issue somewhere.
They also confuse my computers that use 802.11n WiFi if the computer is started after the EZ-B. The computers are unable to get addresses at all until I shut off any running EZ-Bs so that the computer can get its address from the router instead. (the computers with 802.11ac wireless don't see the additional DHCP servers so are not effected).
This is a major networking flaw. It is a very bad thing to have multiple DHCP servers on a network. Hopefully this is something that DJ can fix with a firmware update.