|
Re: Picking A Drive Team
2607, for the past few years, has not had to pick drivers. We are a fairly small team, and we just let whoever wants to drive drive the robot. I, as our head programmer, write the code specifically for our primary driver and primary copilot, and the others either adapt or have me add a driver toggle (which I don't recommend, we almost destroyed our Logo Motion arm because one of the copilots didn't know there was a switch that inverted the controls.) (We had one dedicated pilot, and two pilot/copilots, and they made up the entirety of people who wanted to control the robot.)
The only thing we pick is the driver we base any human error prevention code off of. One of our drivers rammed something during Logo Motion, and our minibot tray came off.
Then, in Rebound Rumble, he tried to get a ball under the opposing alliances bridge, and earned us our only technical foul all season.
Since these events happened, we always joke about how we need to use the code to stop him from doing something with the robot.
However, yesterday, he was replaced by someone who drove our t-shirt robot off of the stage during a school show. (No one was hurt even a little bit, and the robot should be fine too.)
__________________
2011-2014 - FRC 2607 - Student
2012-2012 - FLL 2249 - Coach
2015- ???? - FRC 4791 - Mentor
|