Thread: WiFi/Bridge/CRIO Boot Conflict
View Single Post
  #23   Spotlight this post!  
Unread 22-02-2011, 11:54
jwakeman jwakeman is offline
Registered User
FRC #0063 (Red Barons)
Team Role: Mentor
  
Join Date: Jan 2011
Rookie Year: 2010
Location: 16510
Posts: 182
jwakeman is just really nicejwakeman is just really nicejwakeman is just really nicejwakeman is just really nicejwakeman is just really nice
Re: WiFi/Bridge/CRIO Boot Conflict
We have been using the DAP in AP mode. I also noticed that it takes much longer (gets there eventually though) for the laptop to communicate with the robot when power on the robot is cycled compared to when we just reboot the robot from the Drivers Station.

However, in the case of power cycling the robot I have also noticed that if I disable the WiFi radio on the laptop and reenable it I can get comms much faster. So the sequence is:

1. Power off the robot
2. disable WiFi on the laptop
3. Power on the robot
4. Wait roughly 20 or 30 seconds for the robot and DAP to come up
5. Enable WiFi on the laptop

This get me connected much faster than if I just leave WiFi enabled on the laptop and power cycle the robot. Maybe this doesn't have any value for fixing comm issues during competition but I thought it might provide some clues as to the root cause.