2012 – Elset

Design Process

Elset was built to play Rebound Rumble on the ideas of simplicity and imagery; the goal of the robot was to be able to shoot from the key to the three point hoop and to tip and balance the bridge. The team built Elset with the idea of keeping the number of actuated parts to a minimum because each actuator is heavy, and increases the chances of robot failure. Donning a sleek blue and silver color scheme, Elset can achieve all the parts of the 2012 game while remaining very connected to the imagery of the team and staying simple.

Elset at the 2012 Kettering Competition.

Naming

At the Saturday meeting of week 5, the team gathered together at lunch to vote upon a name for our 2012 robot. Quentin, our lead mentor, was out of town, but gave captain Jeffrey H. the suggestion of “Elset.” As students gathered ideas, Jeffrey wrote them down on a giant whiteboard. After roughly fifteen submissions were entered, voting began. In the first round of voting, students got to vote for as many names as they liked, leaving the top five favorite names on the board. In the second round, students got one vote. The name with the highest number of votes won the contest, which was Elset.

Elset is the username that Tim, the LabView programming mentor, had for many things. Tim did a huge amount of work in the 2011 season, teaching and mentoring the only student programmer on the team in the 2010 and 2011 season. His work was so vital to the team, yet it seemed like as though he was unnoticed for his hard work. After moving to Colorado at the beginning of the 2012 season, Tim still kept in touch with the team via Skype and email, helping out the team of programmers by reviewing code and commenting on the progress. That’s true commitment. For a man’s work to be so important yet unseen, it was only right to honor Tim in the 2012 season.

Elset, relaxing in the pits of Kettering University

Robot Specifications

Drive Train

  • 4 CIM Motors
  • 2 Super Shifters
  • 4 6” High Traction wheels
  • 2 6” Pneumatically actuated Omni-wheels

Elevator

  • 1 BaneBot RS-775-18V
  • Motor goes through a 16:1 Gearbox and is attached to one roller
  • 7 10” O-rings are stretched over two rollers

Hopper

  • 1 2-wire 393 VEX motor
  • Motor un-jams balls in case two balls enter the elevator at once

Shooter

  • 1 Window Motor
  • Motor is coupled directly to a foam feeder wheel
  • 2 BaneBot RS-550-12V
  • BaneBots are coupled to a CIM-U-LATOR Gearbox
  • 2 Rubber Treaded 2010 8″ FIRST Wheel

Bridge Tipper

  • 2 6” pistons
  • Actuates and rests at 51°
  • Uses mechanical advantage to displace the force of the bridge into the horizontal plane
  • Lined with “Self Lubricating Plastic” to prevent robot and field damage

“Solenoid Π” (Pi)

  • 1 14″ Piston
  • Actuates when the robot is off the edge of the bridge
  • Lowers the swing force of bridge by displacing it into the piston

Miscellaneous Facts

  • First year that Team 3322 used pneumatics.
  • First actuating drive train.
  • Shooter components were water-jetted by Team 67, the HOT Team.
  • “Solenoid 3” is actually solenoid valves 5 and 6 in programming; “solenoid 3” was the code-name for the project.
  • First robot to use PID in order to control the speed of the shooter wheel.
  • No vision targeting…yet (contrary to the placement of the camera).
  • The use of netting returns to Team 3322’s robot! Our rookie year robot used netting as well.
  • Can go over the bump, even though the robot was not designed to do so.