|
Re: Autonomous scripting language
If we wanted something we didn't already have a script for, or more likely wanted to tweak a script, we could do this in several ways:
-12-position knob on the Kat Box with file name indicator on the Dashboard. The 12 file names are hardcoded, but the string name is sent to Dashboard so we only have to modify the built code to add a new file (we never added a new file during competition). At the end of the season, we had 10 programs, some of them heavily tuned for various driving maneuvers.
-Old/New speed variation control potentiometer, this acted as the hood angle manual override during teleop but was read as old/new in auton
-Change the text file and FTP it to the cRio in the queue - We did this often for delays or ball spacing tweaks and the like.
Using text files allows for very repeatable execution compared to something where you enter the commands every match, easy modification, and easy addition of new scripts.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor
"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack
|