Quote:
Originally Posted by Alan Anderson
The problem is that the roboRIO itself doesn't connect to the FMS, and it can't know whether or not to be a DHCP server until after it is already talking to the Driver Station.
I can't think of a reliable way to have a DHCP server decide to be active only when the FMS is not present. There are too many chances for it to be running before the DS has made the FMS connection. My preference would be for a separate physical device in the Ethernet tether between DS and robot bridge.
|
I expect the FMS DHCP is in the FMS's radio (access point might be a better name.) Since you are on a VPN at that point, each team would have their own DHCP. The RoboRIO cannot connect to the DS until it has an IP in the DS's subnet so it has to get that from the DHCP first. It would be interesting to know if the RoboRIOs subnet mask was still 255.255.255.0 at this point.
A couple of options for DCHP in the pits would be one on your DS. Probably not a good idea since you would have to remember to turn it on & off. Another would be a wired router. You would have to remember to plug it into the the robot radio before turning it on. Or you could go back to static IPs as outlined in screen steps
Other than it taking annoyingly long, we did not have issues connecting in the pit using to default method.