Once we got to version 3.0 we were very happy with the design and its performance especially since we won 2 tournaments in a row. It completes every task efficiently and we are spending the rest of the season tuning autonomous and practicing driving.
We have 1 sensor that tracks the heading of the robot aka its direction at all times then we have a second sensor used for our tuning pid. So we tell the code which direction we want to face and a function does some math between the values of each sensor, and boom we have global turning
why you haven’t changed your bot design that much this year? Is this working pretty well?
Once we got to version 3.0 we were very happy with the design and its performance especially since we won 2 tournaments in a row. It completes every task efficiently and we are spending the rest of the season tuning autonomous and practicing driving.
Like that 👌
Did u code this in vex code pro
We did
@@ltcrobotics6271was it with ez template or just all from scratch
is this states bot?
It is indeed
e
How did you get your pid to be so smooth? Ours works but its really slow
We tuned it. I don’t know what else to say lol except look for a tutorial for tuning it
Is that JAR template
Nope we created this ourselves in vex code pro
Did you get that from Antares?
No. Antares uses jar template made by 2775v we made this from scratch
K cool
How does this work?
We have 1 sensor that tracks the heading of the robot aka its direction at all times then we have a second sensor used for our tuning pid. So we tell the code which direction we want to face and a function does some math between the values of each sensor, and boom we have global turning
How did u do that
Turning pid a second inertial for heading and some math. Aka magic
@@ltcrobotics6271why are yall using 2 inertial sensors💀