Quote:
Originally Posted by Random Dude
In terms of router naming, one issue I ran into when running a scrimmage out in Oregon, was the school I was at already had a router named "FTC_FIELD", which I didn't know at the time. I think it got turned on part way through the morning, and I suddenly had 1/2 my teams complaining they couldn't connect.
Once I tracked that down, I decided to put custom names on all my competition routers. That way if someone accidentally turns on a FTC_FIELD router at a competition, my network won't collapse. I also plan on running around with a WiFi scanner and disabling any rogue access points.
|
My understanding has been that the FCS connects to FTC_FIELD by default whenever it is present. It only looks for and connects to the secondary SSIDs when there is not an FTC_FIELD present.
We've competed up here for the last two weeks. The first event was late in getting started because of interference from routers running their own FTC_FIELD. After that problem was weeded out, the event ran smoothly, for the most part.
This weekend, there were fewer problems with conflicting network names, though we did have some trouble with persistent intermittent connection loss -- if that makes sense -- and it resulted in some pretty terrible consequences to teams and robots. The folks running things were great about troubleshooting it and rerunning matches as necessary, but it still meant that several robots broke or were broken because of our inability to properly control the robots.
The wifi system operates better than the bluetooth system, but I wouldn't go so far as to call it a good system.