Safety issue with Driver Station cRIO mode

[Greg McKaskle]

Perhaps a better explanation is that the 2014 protocol and 2015 protocol rearranged the control bits, and perhaps the log file is confusing because of that. I say perhaps because I don't have anything with me to test. But additional log files that work correctly may show that the auto and tele are always flipped with the older protocol and newer tools.

The DS now puts joystick and CPU messages into the log even when everything is normal and this doesn't mean it is reenumerating the joysticks. You should see it with old and new protocol and with cRIO and roboRIO.

I truly would like to understand why the UI is sluggish. Anytime we find this, we try to move the functionality out into its own loop. So the CPU code that .NET can hang for fifteen seconds is out. The mDNS code is out, ... So I would try turning off firewalls and things like that. If you find the thing that causes the UI to get sluggish, please report it.

Greg McKskle