LabVIEW Update, Utilities Update, Driver Station Update...which to install and when?

[jhersh]

A new (optional) driver station update is available that will ease proper configuration of the driver station laptop's IP configuration (making you more likely to successfully connect to the field). You can find it here: http://joule.ni.com/nidu/cds/view/p/id/2263/lang/en

-Joe

[MamaSpoldi]

Originally Posted by jhersh

A new (optional) driver station update is available that will ease proper configuration of the driver station laptop's IP configuration (making you more likely to successfully connect to the field).

Joe - can you define what that means, i.e. what was changed? We had problems at a Week 0 event and were completely unable to connect to the field throughout the event despite the best efforts of the FIRST FTAs there. However, we have since received a replacement cRIO from National Instruments which appears to be able to connect to the DLink without issue.

Trying to decide if we should consider updating or not...

[jhersh]

Originally Posted by MamaSpoldi

Joe - can you define what that means, i.e. what was changed? We had problems at a Week 0 event and were completely unable to connect to the field throughout the event despite the best efforts of the FIRST FTAs there. However, we have since received a replacement cRIO from National Instruments which appears to be able to connect to the DLink without issue.

Trying to decide if we should consider updating or not...

When in doubt, upgrade! The only change was to have the DS replace an IP address in windows instead of adding it. Having multiple IP addresses will make the field unable to talk to the DS.

Joe

[Tom Line]

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.