If you’re not familiar with JAR Template, it’s a quick way to set up your drivetrain for autonomous. Just follow the instructions to input your drive constants and you can have PID drives, turns, swings, and odom ready to go in about 15 minutes. This thread will mostly contain updates to the documentation as I make new tutorial videos for different aspects of the template.
If you’re not convinced, it only takes 15 minutes to try it out and decide whether you like it. Just follow the installation instructions in the download link and see what happens.
This is the first JAR Template explanation, with the goal of helping teams learn how the template can be implemented and gain a better understanding of the code they’re using.
The next planned explanations will cover odom and drive functions.
Would there be any way to convert the code from this to normal vex code? My school only has Chromebooks and I tried to make odom code and I failed miserably.
@2775Josh, Hey I was hoping you could help me with a problem I am facing with the odom without the tracking wheels. the ODOM is getting no x and y values. I tried printing the values of the odom XY cordinates using vex::task, it was printing 0 the whole time.
Hi, Josh, the middle school team that I coach is trying to use the JAR template and don’t understand how to use the odom_test outputs to help them with setup. I was searching the forum to help them and found your comment. Could you guide them on where to look for more detailed instructions?
The docs are the best I’ve got. Using the odom test is pretty simple: Just run your code, push the robot around, and see if the brain screen says you’re in the right place.
I’m gonna make sure my kids give credit to you for using your template, do i just use team number 2775 or just mention we’re using the JAR template and explaing what JAR means?
Hi, Josh. I am the programmer of Brighton 28646B and we just imported the JAR-Template and I would like to know how to program autonomous. Is it in inches or is it coordinates. We have odometry and I know the JAR-Template is meant for teams whose robots don’t have odometry. I would love to get a reply as soon as I can before our next tournament. Thanks. @2775Josh@2775VSamuel
I dont fully know why it would not stop(would need to see code to figure it out) but break; is an exit statement for switch cases, it essentially just tells the code “hey this case is done” and leaves all the cases and conditions(this also works with while loops and for loops)
