Quote:
Originally Posted by NalaTI
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.
|
I agree, there are so many factors involved it almost can't be one problem, it might be some robots wired different, programing (we use labview), field control,Samantha, ect. So many things could have caused they shutting down of the robots. Like we had metal shavings in a sensor and that shut down our robot for about a week and it took a long time to find out why it kept reading 0 volts, so there is small things that can really mess up the robots, but if we share what broke/messed up our robot at practice and how to fix it then that can help other teams with the same problem and save a lot of time
