|
02/19/2017 3:27 AM
post5093
|
Hi,
We ran the first day of our scrimmage today and it did not go as easily as I had hoped. We ended up finally getting
matches going about 3 hours late after troubleshooting a significant network problem.
When we did initial testing at the beginning of the event, everything was working fine. As we tried to run matches and
more than 1 robot joined the match, all the driver stations would start dropping off the network and they wouldn't come
back.
We eventually traced this to multiple DHCP servers active on the LAN. Best I can tell at this point, when the OpenMesh
radios are put into FMS-Lite mode, the configuration tool leaves DHCP enabled. This is a very bad thing.
Fortunately, it was easy enough to flip all the driver stations to static IPs. That solved that problem. Some of the
robots had similar issues, but not as severe as the DSs.
The next problem also fell on the OpenMesh radios. We configured all the teams without any trouble, but throughout the
course of the day, we found that certain teams' radios would lose their programming and stop connecting to the field (no
green light). Reprogramming would get them working again for another match or two, but then they'd go stupid again.
All teams were using the new AN radios, except for one team who's AN failed hard and they had to borrow an AC, which
worked fine after that.
Hopefully tomorrow won't go any worse.
Terry
|
|
|
|
|