[MrRoboSteve]

I posted before on my feelings about the success of the control system. We need a physically rough game to make a final statement of success (hint hint GDC).

We used the current monitoring as a substitute for limit switches in one scenario.

Some areas for improvement:

. Transition between tethered in the pit and connected to the field was a continual issue.

. Certain laptops had trouble connecting when operating on battery. Theory is that certain network chipsets have some deep power saving mode that interferes with connectivity.

. physical retention for control cables at the roboRIO -- maybe someone should design a 3d printed part that sticks to the top/side of the unit, with retention like the Jaguar?

. Time between cold boot of robot and field connectivity was a lot longer this year than last. We actively avoided the power cycle this year, because it took so long. Maybe that was good, though, in the end, because we identified some faster ways of fixing things.

--

Regarding the complaint about match length, we did a fair amount of checking match length at one regional and didn't run into issues with running time. Jared, was there an event you noticed the issue at?