Autonomous Longer????

[Qbranch]

Originally Posted by thefro526

Personally I think autonomous could be longer if there were more objectives. Look at the 06 game. you could score low, score high, or even just block another bot. I think just about everyone had an autonomous that year.

And hey, with 30 seconds... you might even endeavour to go around and try to pick up some balls...

-q

[Cooley744]

ummmm. a short auto is good, cuz that's what makes it bonus. short time period and takes a lot of time to get make it and get it right, but if you do...ur amazing lol.

[efoote868]

I wholeheartedly welcome it. This year I'm leading programming/electronics, and this is the second year in a row in which we have more than 4 programmers. This means that we can effectively give people specific tasks.

This year, the programmers will also be given their own drive base. This will allow us to test and tweak a huge amount more, instead of the typical 3 days from ship, "Get it done!".

With easyC becoming a viable option for many new teams, I don't think a longer autonomous with better goals, more points, etc. will tip the teams more, in fact, it'll make it more equal. I don't know, lets wait and see what FIRST churns out.

[Laaba 80]

Originally Posted by efoote868

With easyC becoming a viable option for many new teams

Have you used EasyC on an FRC bot? I tried it on a VEX bot, and i wasnt very impressed with the things it could do. I didn't spend a whole lot of time looking at it though, so I may have missed something.

[TheOtherGuy]

Originally Posted by Laaba 80

Have you used EasyC on an FRC bot? I tried it on a VEX bot, and i wasnt very impressed with the things it could do. I didn't spend a whole lot of time looking at it though, so I may have missed something.

EasyC is mostly advantageous when it comes to sensors and simplicity. The way the program handles the routines is hidden from the user and you therefore only have to worry about what you want to do in the program and not how the heck to do it. (take the camera for example. We didn't have an autonomous mode during the FRC season because we just couldn't get the camera to work right in MPLab. Once I got a hold of EasyC Pro, it was within an hour that I got that camera tracking spot-on!)

[bear24rw]

Originally Posted by TheOtherGuy

you therefore only have to worry about what you want to do in the program and not how the heck to do it.

I still hate the fact that you don't know how it's doing it.. i like to be in complete control of the code were writing and the hidden routines kinda bug me

[neutrino15]

Originally Posted by Chris_Elston

Auto mode was not worth 6 weeks of work for 2 points and a keeper... Auto mode last year was worth 30 points plus a 10 point bonus. SWEET.
The amount of time for auto mode to us doesn't really matter, but what it means to the match play does. It's gotta be worth it or gain an advantage.

I agree. Autonomous should be a more vital part of the whole game. However, you must remember, even though auton is the progger's time to shine, we also have to make driving the thing as simple as possible. Many techniques used during autonomous can be reused during driver operated period. This makes the extra you must write to "automate" it all minimal. As long as you programmed well, tried to fake OO as much as possible, it really isn't a waste of our time.