Things went better today.  Not because there were no problems, but because we knew some workarounds and found more.

There are 4 key problems we ran into and we have workarounds for all of them.

Before you ask, yes, all robots were running the very latest versions of everything:
- Radio firmware 17.3
- DS 17.0a11
- RIO v8

Problem 1: Bad DHCP
- The field AP was configured as a DHCP server as usual.  This has always worked fine in the past.
- Symptom: If you connect driver stations to the network, they sometimes DHCP and sometimes do not.  Also they sometimes
 get an address and then lose it.
- Likely cause: Competing DHCP servers are confusing the allocation of addresses.
- Workaround: Set all the driver stations to static IPs.

Problem 2: OpenMesh AN radio never gets a green light
- All robots were running the new AN radios.  Some radios worked fine, some had this problem almost every match.
- Symptom: The radio boots but the green light never comes on to signify a connection to the field.  The radio does not 
have field connectivity.
- Workaround: Unplug all the ethernet connections from the radio and wait 10-15 seconds.  The green light will come on. 
 Reconnect all the ethernet connections.  Make sure the RoboRIO is in the port closest to power.

Problem 3: RoboRIO won't talk to the DS
- Sometimes the team would plug the RoboRIO into the enet port away from the power connector.
- Symptom: The radio is connected to the field and there appears to be traffic passing but the RoboRIO is not visible to
 the DS.
- Workaround: Move the RoboRIO to the port closest to the power jack.

Problem 4: Magic e-stop
- Most teams never have this problem.  Some teams have it every match.
- Symptom: Immediately at the beginning of autonomous, the robot e-stops without being commanded by the team.
- Workaround: Take the team off of FMS and let them run in at-home mode.  Obviously this would never work at a real 
regional.

Aside from all of these issues, the OffSeason FMS worked like a champ.