A clear, beginner-friendly explanation of swerve drive in FRC — how the modules work, the math behind it, COTS options, and whether your team should run it.
to read
words
sections
Swerve drive has gone from an elite-team novelty to the most common drivetrain at the top of FRC. If you've watched a recent match and seen robots slide sideways and spin while moving, that's swerve. Here's how it actually works — without the intimidating math.
A swerve drive is a holonomic drivetrain: it can move in any direction and rotate independently, at the same time. It does this with (usually four) swerve modules, one near each corner of the robot. Each module has:
Because every wheel can point and spin independently, the robot can translate in any direction regardless of which way it's "facing." That's what makes swerve feel so agile.
You don't need to derive the kinematics to understand it. The driver commands three things: forward/back speed, left/right speed, and rotation. The robot's code runs inverse kinematics to figure out, for each of the four modules, the exact angle and speed that combine to produce that overall motion. WPILib provides this math out of the box (SwerveDriveKinematics), so you mostly configure it rather than write it from scratch.
Add field-oriented control — where "push the stick forward" means "move toward the far end of the field" no matter which way the robot is turned — and swerve becomes incredibly intuitive to drive.
You almost never build swerve modules from scratch anymore. The popular commercial off-the-shelf (COTS) modules include:
They differ in size, gearing, motor compatibility (NEO, NEO Vortex, Kraken X60, etc.), and how you maintain them — but all give you a proven module so you can focus on the rest of the robot.
Swerve is powerful, but it's not free:
Pros: unmatched maneuverability, strong defense evasion, precise auto paths.
Cons:
A well-built tank/west-coast drive is still completely competitive and far simpler. The honest rule: a reliable tank drive beats a poorly-tuned swerve every time. Run swerve when your team has the budget and the software capacity to support it.
If your team is ready to take it on, learn it in this order: the drivetrain mechanics, then WPILib command-based programming, then odometry and path-following. We cover each step in the free Programming and Mechanical tracks on LearnFRC, and the official WPILib docs are excellent for the code side.
Want the full path from drivetrain basics to a swerve-driving robot? Start the free Programming track →
This article is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed — publicly, in the corrections log.
Keep going
You came here for one answer. These lessons teach the same subject properly, in the order a team actually learns it. All 47 are free and none of them need an account to read.
Go deeper
This article pairs with a full structured design course — swerve layout, assemblies, worked mini-projects. A free account saves your progress lesson by lesson.
Save my progressKeep reading
Structured lessons and quizzes across every department. Create a free account to save your progress, track your team, and earn a certificate.