This could easily be user error but I’m running into the following problem:
When I first turn on and activate the motors they run fine for about a minute, after that they get progressively weaker to the point that you can hear the motors are turning, but have virtually no power. Tried it when the battery is plugged in, same problem. But it’s not consistent, one day it will work every time and the next this will happen. Any thoughts?
There’s likely too much load on it. Unlike with 393s, V5 senses when it is being overworked and slows itself down. We encountered the same issue when we used our flywheel (set for V5 with 100 rpm) with our 200rpm motors just to test it
Note that the motor API offers has telemetry, including temperature, torque and power. Both in VCS and PROS. vex::motor::temperature(units), motor_get_temperature(port), pros::motor::get_temperature().
You can try graphing (or printing) your motor temperature with time.
I also just remembered: You can get a lot of stats on the brain’s screen. If you go to the info for that motor, it should tell you what the command rpm is and the real rpm. If the command is at 200 rpm (for a motor with a green gear casing) then the motor is being overworked. If the command is less than 200 rpm, then programming would be the issue