Quote:
Originally Posted by Sperkowsky
Our single objective is a simple reliable robot that can stack from the hp station or the landfill.
[...]
We want to be able to cap a six stack which is why we have the raised hook to lift the recycling cans off.
[...]
Our biggest design factor has to be reliability
|
Now comes the fun part. I'm only going to pick on you for a few of the items you listed--see above--but as an exercise, you might want to go through this with your team. It'll give you a great insight into designing a competitive robot (or other product).
Why? Please answer for all three items. (Does not have to be made public.)
--Why do you want to be able to stack from either location? Why is that important, or IS it important? Why is stacking important? (OK, seriously, I'm getting a little on the off-base side here. But, this is something that if we'd never seen the game before, I'd most definitely be asking.)
--Why a 6-stack? Can you do shorter if need be (ability vs need, definitely something to look at)? Why is the recycling can important?
--Why is reliability the biggest design factor? What about competitiveness? Or coolness? (TBH, I know what you're getting at. But, again, if this were at the beginning of the season, I'd be looking at "is an unreliable high-point item better than a reliable medium-point item?"--I often come back with "no" myself.)
Now, back to your other question of what design will work the best: That's for you to figure out. Start by answering these questions... and that'll give you some requirements... and any design you come up with will need to be evaluated against those requirements.
1) Is it important to be able to go over the scoring platforms?
2) What orientation do we expect to handle totes in?
3) Is it important to be able to keep pool noodles out of the drivetrain?
4) Is it important to protect the drivetrain from robot-robot collisions?
Those questions would answer ground clearance, overall width, and a couple of key addons (or not-so-key addons). A good answer for #1 might come back as "It is not important, but doing so places these limits on play. We can't handle those, therefore it is important (or vice-versa)." Which would then translate into a requirement "This robot SHALL (or does not have to) be able to go over the scoring platforms with ease". This will then drive some ground-clearance decisions. Some searching of CD-Media or FRC Designs will probably turn up some passable drivebases that could be adapted to fit your requirements.