|
Well, from a team that did very poorly in autonomous code, let me share a few tips with you guys to help you out.
1. Keep it simple:
We originally went for the curved approach, in an attempt to follow the line (without sensors..) and we had a lot of problems getting the timing right. I reccomend going for a square turn if you don't have a lot of time to test.
2. Get it working early:
As far as excuses go, the problems for our team (769) were not all the fault of the programmers, but rather the mentors who did not see evidence of the autonomous code helping us in the practice matches (and therefore did not let us run it for 2 matches..which is understandable). We did not have any testing prior to the competition so we were winging it, but I hope you guys have better luck than we did. Showing other teams that you have a useful autonomous code will also be big factor in the choice of alliance partners for the finals, so I stress that you have it working for the whole competition.
|