Resolved by DJ Sures!
I have an odd problem that happens sometimes. I'll preface this issue by saying this has happened in the past a number of years ago.
I have a robot that has three EZB's connected to ARC (Two regular EZB's and one IoTiny) over WIFI in client mode. The two full sized EZB's are v4's. My problem is that sometimes the ARC connection skill will connect to the two big EZBs in the wrong order. The address stays the same in the connection skill but it will swap the two EZBs when connecting. When this happens ARC will not control the robot properly as the script commands are being sent to the wrong EZB. For example I have Kangaroo/Sabertooth motor controllers that are attached to Uart ports on one EZB positioned in connection 0 and need encoder homing commands to work. These commands are being sent to the other EZB. Another example is I have my sound system attached to one EZB. When this swapping issue happens sound files will play out of the other EZB's mini speaker.
To correct this I have to go back into the Connection Skill and do a scan for the correct EZB that belongs in the proper connection slot. When I do this I notice that the second to last number in the address has indeed swapped. The EZB with 192.168.13.23 becomes 192.168.22.23 and visa versa.
I know one of these units is an older model. Maybe a v4.x/1. The bottom board could even be one of the first 100 that was hand assembled in Canada when this model was first released. It has the old large yellow antenna looking thing soldered to this bottom board. The top board has been updated. I can't confirm how old the second EZB is right now as I'm not near it and won't be for a while. It also may be an older model v4.x/1 but just as well may be a newer v4.x/2.
I've had this issue happen on different WIFI networks with different and new routers.
I have another robot that surly has three of the newer EZB v4.x/2 and has not had this issue happen.
Does anyone have any insight on what is happening and how to stop it? I have ordered a new EZB in hopes that this is an anomaly of the old model EZB v4.x/1 bottom board.
I think you should assign static ip’s to ezbs. Not sure why I ever said otherwise but maybe I didn’t fully understand the issue before. When the ezb’s are dynamically assigned, the ips will be assigned in order of which boots fastest on some routers. So I’d go into your router and hardcode the ip for each device in the dhcp settings
Thanks @DJ. I'll give it a try. It'll be a few months before I can get back to this issue. The robot with the this issue is up in Long Island NY at a friends home and I'm back home in Florida. I'll report back then.
Oh wow. That might be why it happened when you brought the robot there. Because it was a new internet and router connection. That means the ip addresses would all change. So if they were hardcoded next time it wouldn’t be a problem
Actually when I got there I did an ARC Connection Control scan on each EZB and reentered their new network IPs. The next day after I had entered them the EZB's switched IPs. Head scratcher.
I think entering a static IP address when I get back may be the best solution in the long run. I'll also be installing a new EZB to replace a damaged one at that time.
On a related note, when I was there earlier this week I tried to log into his router's settings interface and failed. I was going to try the static IP address trick but for some reason I keep getting taken to an actual internet web page instead of the router's settings interface. I ran out of time because I had to catch a flight out. Hopefully I'll be able to access the router when I get back up there.