Strange problem with autonomous

[weilin]

It got to be RightBackDriveMotor.rotateTo(200) call because it is the one that has waitForCompletion argument set to true.

I like @Xenon27 idea that it could be something to do with motor overheating, that inhibits V5 builtin motor PID from reaching the target.

Please, first consider trying changing it from using individual motor statements to drivetrain.
https://api.vexcode.cloud/v5/html/annotated.html

VEXcode, motor groups and drivetrain example

There have been quite a few requests for instructions on how to use motor groups and creating a drivetrain with more than 2 motors in VEXcode. I’m going to discuss these classes a little and provide a simple example. What is a motor group ? A motor group collects two or more motors together and allows control as if they were a single entity. Just about all motor class member functions (by that I mean spin, spinTo, setVelocity etc.) are available on the motor group class. We introduced motor…

If that fails too then you can change waitForCompletion to false and add timeout. In the event V5 PID gets stuck you will wait an extra second or two and then will keep driving.

If you abandon V5 PID and need check for encoder position and step time then reading this conversation will be useful:

Exiting a PID loop

My team is trying to implement a PID loop for autonomous this year but the loop doesn’t seem to end it just keeps running. Does anyone have advice? thanks in advance!