Thread: LabVIEW Update, Utilities Update, Driver Station Update...which to install and when?
View Single Post
  #3   Spotlight this post!  
Unread 04-03-2011, 10:08
Tom Line's Avatar
Tom Line Tom Line is offline
Raptors can't turn doorknobs.
FRC #1718 (The Fighting Pi)
Team Role: Mentor
  
Join Date: Jan 2007
Rookie Year: 1999
Location: Armada, Michigan
Posts: 2,533
Tom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond repute
Re: LabVIEW Update, Utilities Update, Driver Station Update...which to install and wh
Here's another fun scenario we ran into during testing this past week.

We plugged our netbook into a network this week that had another computer at the same IP address (both static). Windows 7 assigned a new IP address in the 169.XXXXXX range. Going in and changing that back to the correct static address in the tcp/ip properties did nothing. An ipconfig /release /renew did nothing as well. Only changing it to dynamic ip address assignment, then back to static, then adding the correct address would fix it. Windows 7 seems to be a bit dyslexic in this situation.

Of course, we couldn't figure it out solely from the driver station window - the driver station couldn't set the IP properly either once this occured but was also not setting any error message.

Is there a way to modify the driver station IP assignment code so that it checks that it's successfully been changed? Having it appear to change but not actually change caused us a good 30 minutes of headaches until we logged into the developer account and did an ipconfig to check.