Specifications


  • Name The 2012
  • Status Disassembled
  • Weight 105 lbs
  • Dimensions 
  • Frame 2"x1" Al welded box tubing, belly pan
  • Drivetrain 4 CIM, 3.5" roughtop treaded wheels x8
  • Language C++

 Competitions


  • Sacramento Regional
  • Silicon Valley Regional Champions with 254 and 971
  • Championships, Galileo Division
  • CalGames 2012
Menlo Atherton Robotics FIRST FRC Team 766 2012 Robot Rebound Rumble Competition

 Robot Abilities


There were 2 versions of the 2012 robot.

First Iteration: Regionals and Championships

  • Drivetrain - 4 powered 8 inch AndyMark wheels, 1 CIM and gearbox per wheel. 2 unpowered 3.5inch roughtop treaded wheels in the middle could be retracted on large (2 inch) pneumatic pistons to allow for easy crossing of bump and climbing on bridges, and the robot could turn with them down. (At least by design, see stories section for description of how it worked)
  • Shooter - 2 Fisher Price motors drive 2 AndyMark 6 inch wheels
  • Intake - polycord belts driven by motor
  • Tower - leads up to shooter, polycord belts driven by BaneBots motor/gearbox
  • Bridge lowering arm - driven up and down by motor, locked by piston. At first used a single piston (see 1st Iteration picture) which didn't really work.
  • Programmed in LabView.

Second Iteration: CalGames 2012

  • Shooter - 2 BaneBots RS550 drive 8 inch Colson wheel. (heavy, acts somewhat like a flywheel) Manually adjustable hood allows for change of shooter angle in pits outside of matches.
  • Intake - polycord belts driven by motor
  • Tower - leads up to shooter, polycord belts driven by BaneBots motor/gearbox
  • Bridge lowering arm - driven up and down by motor, locked by piston

 Game Summary


For a more detailed explanation, see the Wikipedia article and the game animation.

Each two minute match (preceded by a 15 second autonomous period) was between two alliances of three robots each. The game pieces were small 8 inch diameter foam basketballs. The field had basketball hoop targets at each end (in a pattern of 1 on top, 3 points, 2 in the middle level, 2 points, and one on the bottom, 1 point.) In the middle of the field there were 3 balancing ramps; at the end of the match points would be awarded for balancing on one of the team ramps, or 'coopertition' points would be awarded for balancing on the center one with a member of the other alliance. Coopertition points do not add to the match points but do factor into a team's ranking in the standings.

 Fun Facts/Stories


  • The first iteration's drivetrain was a unique idea to try to conquer the bump in the center of the field. What resulted was a robot which went over the bump extremely smoothly, but could not turn at all. Once the robot was finished, it so turned out that the robot was literally perfectly balanced, which we attempted at during design but did not expect for it to actually happen. Before we adjusted things, if the wheels were down, we could run the wheels of the robot at full speed and it would not move at all. Even when we adjusted the balance of the robot, the center of gravity was still largely over the unpowered wheels, so we still could barely turn. With the wheels raised, the powered wheels were too far apart to make turning practical.
  • During an outreach event, Image iconwe managed to pop a pneumatic tube, creating an alarmingly loud noise. The cause was found to be that the tube was weakened by the compressor, which had been running often during the preceding time, and had become quite warm. Later robots had more brass pneumatic connectors between the compressor and the tube.
  • The rebuild of the robot was the first time the team had completely rebuilt a robot over the summer, as the 2006 summer modifications still retained the base and drivetrain of the previous iterations.
  • The second iteration was the first Team 766 robot to use C++ code.