View Single Post
  #7   Spotlight this post!  
Unread 23-10-2012, 19:22
vinnie's Avatar
vinnie vinnie is offline
Registered User
FRC #3309 (Friarbots)
Team Role: College Student
 
Join Date: Oct 2010
Rookie Year: 2010
Location: Los Angeles / Anaheim
Posts: 107
vinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond reputevinnie has a reputation beyond repute
Re: Autonomous scripting language

Quote:
Originally Posted by McGurky View Post
I would also suggest that you take into account that a lot of last minute changes to strategy might occur in cue for a variety of reasons(if you have ever been on a drive team, you know what I mean). Whatever your solution is for simplifying autonomous selection, make it something that your drivers will be able to change easily and with little hassle.

For us, it was more important for the drivers to focus on strategy than figuring out the binary codes of a selection panel, or a script like you have posted.

For this reason our team integrated the following tab into our dashboard.


This allowed our drivers to simply change the autonomous routine to a (theoretically) infinite amount of choices. It also allowed our team to adapt to nearly any strategy the alliance was planning.

Just my input into the discussion, take it for what its worth!
This is so much more sophisticated than what we did
We just had a jumper connected to a digital in that would enable or disable autonomous based on whether it was connected or not. We scrapped that in eliminations at Central Valley when we rewrote our autonomous to feed the balls that we had to 1323.