View Single Post
  #6   Spotlight this post!  
Unread 07-02-2013, 22:11
EricH's Avatar
EricH EricH is online now
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,749
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Rule G05 and Autonomous

Quote:
Originally Posted by MagiChau View Post
When placing the ROBOT on the FIELD it is typical for teams to push it into proper position. However, to record encoder counts would require the robot to be running. This means you would have to wait for your robot to turn on before you can actually finish placing it. I don't think the field crew will like the possibility of how long your team could take to be ready for a match factoring in the ~25 seconds for a robot to be on.
G05 is not the issue. G07, delay of game, would factor in, however. Robots that take too long to set up get disabled for the match.

BUT! I have a solution! Presumably, you will know (or can dial in) your optimal shooting position before competition matches begin. Some moving of the robot either manually or with the controls should give you an encoder count to move a certain distance. Namely, the distance between the pyramid and your favorite shooting spot. Input that value into your code as the distance to move, and all you have to do is remember to turn the robot on (and anything else on your prematch checklist).
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk