Quote:
Originally Posted by team F.T.C 4240
I started to wonder if it wasn't some of the robots and not just the field control, because we had no problems, even when the other 3 robots shut off in one of our matches we just kept going and it worked perfect so it might not be "just" the field control, also if you push the "mode" button on the controller it will disable the joysticks, making teams think that the robot is unresponsive, but you can still move the servo's. I hope that helped 
~Derrick |
We also had no real problems except in two matches. The first was when all four robots lost communication for about 3 seconds, and the second was after they reset all the USB controllers and our arms person had the joystick pressed back so it thought zero was in the wrong place.
I definitely believe that most of the individual problems were robot related -- specifically the comms from NXT to motor/servo controller. Dick Swan (RobotC author) talked to us at our booth and we proved to him the RobotC bug relating to those communications and PID. I expect that there's another bug in there as well that's related to a similar firmware design problem. The connectors on the NXT are not really designed for this environment and that's an issue that has to be solved as well.
However, I do also believe that there were problems with the wifi network, and the combination of all of the above made it miserable for lots of teams.