Quote:
Originally Posted by ChrisMcK2186
2186 reporting in!!
Week 1:
After much deliberation on what we want the robot to do, we decided to continue deliberating in hopes that it will solve itself. The design has evolved, devolved, evolved again, been lost, found, and turned into beaurocratic compost. The leadership can be found weeping in the corner, engineers trying fruitlessly to get a grasp on the problem and the programmers, the programmers seem complete unaware of what is happening.
Seriously, we have started the drive system to find out a transmission is not performing to proper standards, our frame base has been constructed and we have our wheels. Still not quite sure what the robot will do (my hopes are a coffee machine  ) but it will be worked out today.
McKenzie out. |
I severly suggest that you lay down the tools and pick up the pencil and paper (or AutoCAD). Last year, 675 proceeded to take the path you're on right now. We had an overweight, under-supported robot that only performed it's task to a mediocre level, with no autonomous mode. We shipped an unfinished robot to San Jose, and didn't get any practice when we got there.
This year, due to some planning, we have a design and are in the process of making it a reality. However, due to the fact that our Team Leader (Mr. Greg Weaver) or one of the higher-ups (Blake or Robin) said we aren't to divulge any information, and the fact that I'd much rather not say, that's all you're going to know for now.
Come March, our secrecy will all be obviated. Stay tuned.
Michael Baker, Team 675, Phantom Robotics, Chassis & Pneumatic assembly and design team, 2007 Season.