Quote:
|
I wonder if it would ever be possible for FIRST to add a rule allowing teams to keep their robots for an extra week but only allow software to work on it? Unfortunately, this is probably too unenforceable and would leave a large opportunity for abuse, and would extend the build season which a lot of people are (rightfully) opposed to. Unfortunately I just don't see how else autonomous modes can improve. Anyone have ideas?
|
Here's my two cents worth:
FIRST must support this (autonomous) part of the game better. Last year when we were given the IR challenge, we experienced many mishaps at regional competitions that made the IR sensors unreliable; the alumimum diamond plate around the playing field reflected the IR signal everywhere,the left and right IR beacons were sometimes crossed, and at one regional the beacons weren't even turned on! (they were eventually turned on)
This year, fifteen seconds is really tight! You really don't want to risk your robot getting damaged by making it go full speed during autonomous mode. There are a few things I would like to suggest to make this year autonomous (camera) mode more likely to be accomplished- First, allow more time (about 20 seconds). Second, the vision tetras should be placed randomly on the playing field with one on the left side and the other on the right side. Right now, some combinations are just impossible. Third, make sure the light is at a good level with no shadow on the playing field. Last, make sure no judges or FIRST volunteers place something like a Mountain Dew can around the playing field. Our robot actually locked on to a Mountain Dew can at Grand Rapids. If we are tracking green and yellow on the field, make sure green and yellow are only on the target!
