|Suggestion on waitForStart
|Page 1 of 1|
|Author:||jvcarr [ Fri Feb 07, 2014 1:35 pm ]|
|Post subject:||Suggestion on waitForStart|
Especially with the new V2 motors, we are seeing a lot of motor controller freezes. As an FTA, we could reset the robot between autonomous and teleop, if we knew we had a problem. However, the FCS talks to the NXT correctly, despite the motor controller freeze. If the waitForStart routine included some test to poll the defined motor and servo controllers and then report back to the FCS if one was locked, the FTA could clear the issue (if it happened in autonomous) by power-cycling the robot.
Just a suggestion. I hate it when the autonomous fails, teleop starts, and the robot just sits there, moving its NXT motors and nothing else...
|Author:||tfriez [ Fri Feb 07, 2014 1:39 pm ]|
|Post subject:||Re: Suggestion on waitForStart|
We have methods for polling the motor/servo controller to do just this - however the feature will not be included for this season since FTC Game Design does not want to introduce a new feature that teams have to implement (or create an unfair playing field for those who don't implement it). We've successfully BETA tested it with teams in practice/home trials, but it has not been approved for competition use.
Look for this specific feature for next season, however.
|Page 1 of 1||All times are UTC - 5 hours [ DST ]|
|Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group