Creating the right manipulator for a challenge is one of the hardest parts of the FIRST Robotics Competition (FRC). In my four years as a student, it was always my team's biggest failing point. Though the game challenge in FRC changes from year to year, there are often tasks that are similar to ones from previous years. For example, the 2012 game, Rebound Rumble, had clear elements of the 2001 game, Diabolical Dynamics, and of the 2006 game, Aim High. For this reason, it is beneficial to be familiar with basic manipulator designs used in previous games.
This tutorial will provide an overview of manipulators commonly used in the FIRST Robotics Competition (FRC). Each step will discuss a general manipulator type and provide examples of implementations of the manipulator.
This tutorial was made through the Autodesk FIRST High School Intern program.
Prerequisites:
A willingness to learn
Photo Credit:
http://www.andymark.com/Presentations-Education-s/194.htm
This tutorial will provide an overview of manipulators commonly used in the FIRST Robotics Competition (FRC). Each step will discuss a general manipulator type and provide examples of implementations of the manipulator.
This tutorial was made through the Autodesk FIRST High School Intern program.
Prerequisites:
A willingness to learn
Photo Credit:
http://www.andymark.com/Presentations-Education-s/194.htm
Remove these ads by
Signing UpStep 1: General Guidelines
Before I jump into the nuts and bolts of different manipulators, I wanted to provide some general guidelines that will help you choose and design a manipulator.
First, let strategy drive your manipulator design, not vice versa. What this means is that your manipulator should achieve the design requirements your team decided upon in forming a strategy, instead of forming a strategy based upon the manipulator you cobble together.
Second, design within your teams’ limits. If you know you just don’t have the resources to build the super-complicated manipulator that you think will dominate every aspect of the game, don’t do it! Go for the simpler one that you can build and will fulfill one role really well. However, also don’t be afraid to push your team to overcome your limits. For example, my team pushed ourselves to build a practice bot this past year, and it ended up being really beneficial.
Third, always have active control of the gamepiece. For example, if a ball needs to be transported through your robot, do it with a conveyor, not a ramp. If you don’t actively control the gamepiece, it will inevitably jam or fall out of your manipulator.
Finally, prototyping and iterative development are key to building a successful manipulator. Start out with a prototype, and then iteratively improve it until you are ready to build a final version. Even then, be looking for improvements that will make it better.
Photo Credit: http://www.chiefdelphi.com/media/photos/30826
First, let strategy drive your manipulator design, not vice versa. What this means is that your manipulator should achieve the design requirements your team decided upon in forming a strategy, instead of forming a strategy based upon the manipulator you cobble together.
Second, design within your teams’ limits. If you know you just don’t have the resources to build the super-complicated manipulator that you think will dominate every aspect of the game, don’t do it! Go for the simpler one that you can build and will fulfill one role really well. However, also don’t be afraid to push your team to overcome your limits. For example, my team pushed ourselves to build a practice bot this past year, and it ended up being really beneficial.
Third, always have active control of the gamepiece. For example, if a ball needs to be transported through your robot, do it with a conveyor, not a ramp. If you don’t actively control the gamepiece, it will inevitably jam or fall out of your manipulator.
Finally, prototyping and iterative development are key to building a successful manipulator. Start out with a prototype, and then iteratively improve it until you are ready to build a final version. Even then, be looking for improvements that will make it better.
Photo Credit: http://www.chiefdelphi.com/media/photos/30826
Visit Our Store »
Go Pro Today »
As for complacency setting in, I would argue that that isn't the case. Every year sees new and creative solutions to the unique problems presented by the game challenge. Actually, a fair number of the examples fit into this category. When similar challenges appear, similar solutions also appear simply because they are optimal solutions.
This Instructable wasn't meant to simply provide designs for other teams to copy, but to inform them about good solutions to common problems. Often times, new teams spend time trying to "reinvent the wheel" for "solved problems" when their time and creativity could be put to better use solving the unique challenges presented by the game.
Thanks for taking the time to check the Instructable out and for the feedback!