Quote:
Originally Posted by SuperBK
Also, we switched to static IP addresses.
|
Quote:
Originally Posted by Jpatterson1710
That's funny, because as an FTAA my first step to troubleshoot issues at the DS is to make sure its set to DHCP.
|
Me too, I'm pretty sure it's not recommended anymore to use static IPs with the field.
IIRC, the problem last year was going between the field and the pits - one environment had a DHCP server and the other didn't. So when you went from the field to the pits, the DS laptop realized it's old DHCP lease from the field was invalid and tried to obtain a new one, but since there was no DHCP server, it timed out (slow!) and fell back to a 169.whatever link-local address. This wasn't a connection problem, per se, since mDNS could handle it once everything resolved. But it could take some time for everything to work (and may have required a force DHCP refresh by disabling/reenabling the adapter).
One way around this problem is to take last year's dlink radio, turn the wifi off, and use it as a DHCP server in the pit that you connect your DS and robot to so you can tether.
I also think the DS update this year that enabled regular DNS in addition to mDNS when finding the robot may have had some effect.