[Greg McKaskle]

Since you mention the RIOLog issue, because of the new radio, one thing you may want to try is to move the ethernet connection to the roboRIO to the other radio port. I believe you want it connected to the one next to the power connector.

While it is totally fine to list issues on CD, that isn't the same as a bug report. With the new website, I'm not certain where the official reporting location is, but perhaps the ScreenStepsLive bugs would be appropriate.

As for static IP addresses, they were never ideal, and the old system used them because it was too difficult to get DHCP and all of the other modern services up and going in all configurations. The benefit of static IPs are that it is a manually controlled, rigid, simple system. The downside is that things are manual and must adhere to the system at all times. Taking a programming laptop online to submit code or look up a manual, then back to the robot was error prone and tedious. DNS and mDNS let the computer and devices do these tasks for you, but they aren't bulletproof. Static IPs aren't bulletproof either. The roboRIO and DS fallback to static IPs, mostly as a safety net, so they should continue to work, but they are not the recommended setup, and for example, I don't know that they get much testing, beta or otherwise.

Feel free to do whatever meets your needs at your shop, but when you come to an event, it is best to follow the current FRC guidelines for configuring your radio, computers, firmware versions, etc.

Greg McKaskle