|
Re: Your teams design procedures
well, our team at kickoff has our own meeting, that spans over 3 days, with each day doing something else:
Day One - students, and mentors, are dissuaded to think about robots, we think about what we want to do and what we want to accomplish, and what will win the game (this year we decided to not have ramps since we assumed that there would be ramps aplenty to choose from, and I think we werent far from the truth). One key thing that people tend to overlook is logistics (time spent moving across field, under defense, etc). Always try to factor that in.
Day Two - Rough design of what the robot can do to complete our objective, minor sketches. When dealing here, remember the wonderful acronym KISS (Keep It Simple Stupid).
Day Three - Specific design features of what the robot can be built to do, detailed sketches (Dont get overzealous, there is a construction deadline...).
Then, for the remaining build season, we try to construct a complete replica of our robot on Pro-E CAD, which helps when making parts cause it gives you a sense of assembly. We waterjet and CNC most parts, with the talented machinists finishing off the work in their own way. This year, since our 2k5 and 2k4 robot had a similar design, we could use those robots as a real-life test to our design, since most of us know what looks great on paper is sometimes misleading.
hope that helps...
__________________
"I drift not because it is a quicker way around a corner, but it is the most exciting way" - Keiichi Tsuchiya
"...and remember, don't be an Initial D-ouche, Drift Responsibly" - Me, after showing a few members Initial D
The next statement I make is true. The last statement I made was false.
Pink Team Awards (Click it, you know you want to)
Base Driver 2k7!
Attending : Krunch Off-Season?
|