Re: Rookie Team Tips!
As stated before, keep it simple!
We are a veteran team that changed leadership last year. We developed an overcomplicated design that eventually became unsafe in addition to not working. In the end we changed our kicking system and drive train at competition. I would also advice to plan the season, for example: two weeks design, two weeks build, and two weeks programing and testing. If you don't have a good programming mentor or team member that knows his/her stuff, keep that really really simple (I would use labview). It is really easy to develop programming bugs, especially with a complicated drive system. This one is from experience. Most of all, have fun. It can be really stressful when something does not work. Take a break, come back the next day, and always remember you are in this to learn and have fun, winning is just a benifit if you get there.
Julian Binder
Team Captain 852
|