View Single Post
  #34   Spotlight this post!  
Unread 06-04-2015, 18:37
jgalbraith jgalbraith is offline
Registered User
AKA: James Galbraith
FRC #0231 (High Voltage)
Team Role: Mentor
 
Join Date: Dec 2011
Rookie Year: 2012
Location: Houston
Posts: 4
jgalbraith is an unknown quantity at this point
Re: RoboRIO / FMS / mDNS / lessons learned

We ran into this problem at LoneStar on a regular basis (i.e. failure to reconnect to robot after returning to the pit, Driver Station showing a 169.254.X.X address). The key here (as already noted) is the 169.254.X.X address. Ever since Windows Vista (/ward against evil eye), the Windows IP stack generates the 169.254.X.X address if it cannot find a DNS server. This default address is also sticky and hard to flush from the standard GUI interfaces.

The problem lies with the driver station running Windows 7+. The roboRIO seems to be doing what its supposed to do, its just not being sent a DNS query by the driver station.

The fix - reset the ethernet adapter IP system.

The solution: Generate a batch file in Notepad that invokes the windows command line net shell interface. Use it to reset the IP system.

One line, should read:

Code:
netsh int ip reset
Or you could write it out fully:

Code:
netsh interface ip reset
Save the file as with a .bat extension somewhere handy with a memorable title (e.g. reset_ip.bat). Execute it by double clicking on it or any other conventional method.

Our experience is that this fixes the problem in seconds.

Hope this helps. Good luck in this last week of District competitions and at Championship if you are fortunate enough to go.
Reply With Quote