[jbbjjbt]

Bill,
Our two teams never had any issues with the field management system or bluetooth that only affected only our robots. There was at least one match where all four robots on the field were disabled in teleop.

We use LabView, so I can't comment on RobotC. But we've had many issues when practicing and also on the field at the tournament where the hitech motor controllers go bizerk (sp?). I don't know if it is a hardware or a software issue. Our 177 bot stopped during autonomous during its second match and never recovered. The NXT brain was still running and communicating, it's just the motor and servo controllers that were messed up. The team came up with a fix or we wouldn't have had a very successful day. Our 3165 bot decided on its own to do a little spin dance at the end of autonomous. It sure wasn't in the programming. Fortunately it always recovered when teleop started.

Again, I don't know about robotC, but in Labview, the original FTC Move Motors commands had issues and would stay sometimes stay running for 2.5 seconds. Also if an encoder didn't reset, all sorts of weird results can happen. Most of these issues were corrected with updates.

Many teams had not updated their software and were having issues that had been taken care of earlier in the season.

There are no RF links that I am aware of. The Logitech controllers are hooked directly to the computer running the Field Management System using USB cables.