Definitive FRC Mechanisms

[Madison]

I was thinking about things I could do to further familiarize my team members with the history of FRC robot design and considered creating a presentation that is a look at the best of the best mechanical and control systems designs.

I thought it might be a fun exercise to debate who and what would be in this presentation here on CD. The notion is simple -- for any or each of the following items, select a robot that, in your opinion, represents the best-in-class in that sort of function. Defend your choice. Add pictures when possible.

This list is not comprehensive. Some of the terms are quite generalized, some are not. Feel free to suggest additional terms.

DRIVE SYSTEMS

• 2WD
• 3WD
• 4WD
• 6WD
• Treads
• Omnidirectional
• Swerve
• Mecanum
• Articulated/Suspension
• Steering
• Cantilevered Wheels
• Live Axle
• Dead Axle
• Brakes
• Stair Climber
• Ramp Climber
• Other

GEARBOXES

• 1 Speed
• 2 Speed
• 3+ Speed
• Continuously Variable Transmission
• Worm Drive
• Clutches
• Winch
• One-Way/Ratchet
• Power Take Off
• Other

MANIPULATORS

• Elevator
• Single Jointed Arm
• Double Jointed Arm
• Triple+ Jointed Arm
• Roller Claw
• Pincer Claw
• Crane Claw
• Vacuum System
• Helix
• Shooter
• Turret
• Linkage
• Lifter
• Balancing
• Hanging
• Grabbing Pipes
• Defense
• Other

CONTROLS

• Robot Control
• Manipulator Control
• Custom Dashboard
• Motor positioning
• Path finding
• Machine Vision
• Other

[Ether]

Originally Posted by Madison

This list is not comprehensive. Some of the terms are quite generalized, some are not. Feel free to suggest additional terms.

Perhaps include mecanum under DRIVE SYSTEMS since that has been the subject of much interest on CD.

I mention this only because I notice that you have Omnidirectional listed, which would be a superset of mecanum, but you also have swerve listed, which is a subset of omnidirectional.

[Madison]

I've added it back. I may have replaced it with omnidirectional when I meant to add them both. Oops.

[Brandon Holley]

I'm going to think on this one for a while before responding...

-Brando

[BrendanB]

Team 16 the Bomb Squad for 3wd swerve, couldn't find any pictures of it.

[Chris is me]

I'd probably personally expand on "linkages" a lot more. Four bar paralellograms in arms are practically ubiquitous, but past that there's so much more you can do with them and so many other robots that use varying linkages for different applications that I think special emphasis should be added on four bar arms.

[EricH]

I'm going to say 254/60/968 and the West Coast Drive (6WD) is the best all-around drive (i.e., does everything well). 118's coaxial swerves are probably the best in the "standard" 4-wheel swerve. Plenty of pictures of 254/60/968 on CD-Media (visible under the hopper in http://www.chiefdelphi.com/media/photos/23573, http://www.chiefdelphi.com/media/photos/26141, http://www.chiefdelphi.com/media/photos/27537). 118's swerves are better seen in the Behind the Design books, but the one from 2007 is at http://www.chiefdelphi.com/media/photos/27221, though poorly visible.

The transmission from 254/968 in 2007 (http://www.chiefdelphi.com/media/photos/27018, http://www.chiefdelphi.com/media/photos/28070) is one of the best 2-speed trannies in FRC, but it's tough to make (and AM sells plenty of 2-speed trannies). It weighs just over 1 lb without the motors, and their robot was plenty good to go with it.

[Ian Curtis]

IMO, 1771 gets a tip of the hat for vacuums (they even got the Championship Xerox Creativity Award!). From the 2008 season.



1771 in 2008
Impeller
1771 2008 Scrimmage Video

[pandamonium]

If the goal is to familiarize your team members with the history of FRC robot design get the kids to do the research! Using blue alliance, chief delphi maybe even youtube the students would get more out of actually doing the research than being told what is good.

I conducted a similar activity recently with our strategy pre-season sub-team where we looked more at performance than at design. However this gave the new students an opportunity to get familiar with certain teams and this process could easily be adapted to fit your design idea. Pick a topic and ask each team to research and present on it, this could be done in an hour or so or more time depending on how in depth you want the information to be.

I hope this helps, if not sorry for not answering your question

[Taylor]

Originally Posted by pandamonium

If the goal is to familiarize your team members with the history of FRC robot design get the kids to do the research! Using blue alliance, chief delphi maybe even youtube the students would get more out of actually doing the research than being told what is good.

I completely agree with that statement, but this thread will ensure the kids find the "right" answers.

[BrendanB]

Originally Posted by pandamonium

If the goal is to familiarize your team members with the history of FRC robot design get the kids to do the research! Using blue alliance, chief delphi maybe even youtube the students would get more out of actually doing the research than being told what is good.

I agree, but it depends who your students are. Are they freshman with no knowledge, seniors with design experience, or even freshman who know more about different teams than you do? Unless they are seniors and juniors who have knowledge of previous machines from teams I will show them the best in each section so I know that they have all seen one of the top machines or parts of a robot.

I really like using thebluealliance for showing match strategy and design in action because then you can show kids a match where omnis are useful in some ways, but all the other times when you will be pushed out of the way by defense. It is one thing to tell, tell, tell; however, show and tell is the best option IMHO.

[pandamonium]

Originally Posted by Taylor

I completely agree with that statement, but this thread will ensure the kids find the "right" answers.

there are many "right answers"! Also I think that students at any level are fully capable of finding "right" answers to these questions.

in addition to the resources I have already mentioned FIRST hands out design awards. These teams win these awards for a reason!

also look at teams that performed really well like the finalists at championships these teams made it that far for a reason!

[Madison]

Originally Posted by pandamonium

there are many "right answers"! Also I think that students at any level are fully capable of finding "right" answers to these questions.

in addition to the resources I have already mentioned FIRST hands out design awards. These teams win these awards for a reason!

also look at teams that performed really well like the finalists at championships these teams made it that far for a reason!

Part of this exercise will, I hope, get people to look beyond award and event winners. Award winning designs are rarely notable and it's likely that there are some great subsystem designs that are strapped to mediocre robots.

I have not yet fully conceptualized what my presentation will look like. I want it to be more than a history lesson, but I also want to be armed with good examples of great system design to present to them as a great benchmark.

[buildmaster5000]

A good starting place on much of what you want has been provided by AM here. It covers the basics of a lot of the topics you mention, but perhaps not to the same depth you desire. Reguardless, they are good resources for teaching new team members.

[sithmonkey13]

I know I might sound like someone tooting their own horn (although I was not on the team at the point), but in 2008, 1178 built Manny, a robot with scissor lift elevator. You can look it up on thebluealliance.net, but here is a basic summary: 2 motor six wheel (West Coast) drive, where each motor only powers the center wheel. 2 tusks (leasing to the name) powered by a window motor to pick up the ball and load it onto the scissor lift. Worked well in competition, from what I hear, it was one of the most reliable robots we have, still worked until we had an issue with the controller (but will soon be updated with a C-RIO). Although it had a few problems (could have been slightly more powerful and maybe a little bit taller) it was an impressive robot, and a team favorite.