Would Someone mind looking over my autonomous.

[j.cole]

Yeah she helped me a lot and I appreciate all her work it was just kinda throwing me off. She spent a lot of time over with us lookin at the code.

I never thought of leaving it at 100 & -100 but that's a good idea. I haven't had any problems with accuracy but if I do I'll keep that in mind.

I made a graph on the front panel of the teleop with the setpoint and the process variable. Then we had a mentor there that could look at the graph and figure out what needed to change in our gains also we left out a I because it's dangerous and unnecessary. So basically its a visual tune.

As of now I'd rather not recombine them because I wanna see if it works first.

That's what I'm thinking for why I'd rather not recombine them.

Knoxville was a lot of fun and I think all of the teams were surprised at how smoothly everything was going I think all of our other students said they liked it too. I'd like to go back in the future but it probably won't happen while I'm a student.

[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

[Travis Hoffman]

Originally Posted by mesamb1

[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]

Jordan is on Team 379. I just hang out at their shop and harass them from time to time.

You were right about the "great student" part, however.

[j.cole]

Thanks for all the help guys i prolly shouldave listened to you guys in the first place about combining the while loops because I was having trouble on thursday and the NI Rep (i never got his name cool dude, are all NI reps awesome?) told me to combine them and it worked. Aside from that it works as it should (it likes to veer right but that's a physical problem)