With the new season VRC 26/27 Override there is a new drive train motor limit of 55W. Whats the best way to optimize the drive train and not to overheat the motor by using 44W 600rpm. Can you guys share what your teams are working on? Thanks in Advance.

Just think of your own solutions. The season has been active for like a bit more than two weeks. See what ratios work and dont and then ask for feedback

@lacsap Already said it perfectly in another post: [image] Plans for Override aligner? How about you share your ideas first and then ask what ideas other have… I think this is a general problem on the forum for asking possible solutions before thinking of your own.

Are you planning on using 44w 600 rpm? This won’t work at all, no matter how you optimize it.

450 rpm 2.75 with 55 watts works quite well. I encourage you to tinker with slower drive configs compared to other years considering the loss of 11 watts. That being said, the mentioned ratio is plenty fast.

44W 600rpm will definitely overheat. the teams tried before and motors begin to overheat after 2 matches.

thanks Lucas, i think its the gear arrangement that is challenging as its requires compound gear trains. thats the part that i feel its hard to teach the junior teams on

my team plans on doing a 450 rpm, 44W x-drive. That would give you a similar max speed to a 600 rpm direct drive

Hey, do you know if there is some kind of math that I can do to figure out if my motors are going to overheat with my drivetrain? I want to see if I can determine that before I make my chassis, if at all possible.

I would recommend that you stop looking at RPM and switch to IPS (inches per second - or cm per second). The field is 144 inches across so it makes it very easy to understand how quickly your robot can move within the area. Here are some recommended speeds for chassis. Note that friction and weigh…

I totally agree with your statement.

Override 55W Drive Train Ideas

VEX V5 Technical Support

voleary May 15, 2026, 4:57am 3

@lacsap Already said it perfectly in another post: