[martin417]

Since the advent of the CrIO in 2009, we have found that if we turned the robot on in the queue (as directed by the FTA and volunteers), prior to the FMS displaying our team number, we had issues 100% of the time. If we waited until we were on the field with our team number displaying on the FMS, before we turned the bot on, we had no issues. This has caused friction between our drive team and the volunteers and the FTA at every regional, but especially this year at North Carolina. Every year, we confirm the behavior in front of the FTA in a practice match that if we turned on in queue, without our team number displayed on the FMS, we have many problems, camera issues, encoder and / or gyro issues, loss of comms, or extremely long delay in connecting to the field.

In 2009, at the recommendation of the FTA, our programmer (who is now a programmer for Sony) used a default robot project (in C++) and tried it on the field with the same result, so it is not our code.

For the record, we always program in C++, and use gyros encoders, cameras, and other sensors every year.