[mesamb1]

Well thank you so much for joining us for our rookie regional. Glad to hear you guys liked it!!

I, personally, had expected multiple field failures, but the nice thing about being week 5 is that the field techs have all of that stuff under control.

[Travis Hoffman, you have a great student! it is really done well and is particularly ambitious with out a labview mentor, but I shake my fist at your c++ compiler]

I would argue about the I variable(if it was giving dangerous results, you could be seeing some round off errors there), but that is as good as anyway to tune it.

If you have the time tonight(you may be swamped). In a very separate folder from your normal code(careful not to get a dependency error in your main code) just recreate your autonomous code in a subvi(just download the file you uploaded with a new name, and create a global variable file in the folder). then get rid of all of the motor references, and just set the arm to always be where it is desired. Then graph the drive output. It is not slick but it will give you a timing idea of how long things are being run. If your code is waiting for a variable, not running at the same time, ect. that will show up in the graphs. Far from the way you SHOULD test it, but it is a sans-robot way you CAN test it