[jspatz1]

We experienced this delay in Kansas City. Had never seen it before reaching the field there. The delay would even persist AFTER our matches, while testing tethered in the pit or practice field. Re-imaging the cRio would solve it, but I believe it returned at least once again and required the same fix. One theory offered to us was that the field shut-down of the cRio left the memory full of vision data that was never cleared and somehow caused this delay. Don't know if this is correct, but abandoning our vision entirely did seem to prevent it from coming back. We would like to solve the problem while still getting our vision back.

Between this and the widespread comm problems we and others have experienced on the field, it would appear that negotiating the pitfalls in the control and communication system are as important a part of the challenge this year as the game itself. You can't always prevent them even with thorough testing, but make sure you get to the field on Thursday so you can check your system with the FMS, and make sure you use proper power-up procedures at your matches.