Swerve Drive Explained: How FRC's Most Popular Drivetrain Works

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.

What swerve drive is

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:

• A drive motor that spins the wheel (how fast you go), and
• A steering (azimuth) motor that rotates the whole wheel assembly to point in any direction (which way you go), plus
• An absolute encoder that always knows which way the module is pointed.

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.

How it works (the intuition)

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.

The COTS options

You almost never build swerve modules from scratch anymore. The popular commercial off-the-shelf (COTS) modules include:

• SDS MK4 / MK4i / MK4n (Swerve Drive Specialties)
• WCP Swerve X / X2 (West Coast Products)
• REV MAXSwerve
• TTB Swerve and others

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.

The trade-offs (should your team run it?)

Swerve is powerful, but it's not free:

Pros: unmatched maneuverability, strong defense evasion, precise auto paths.

Cons:

• Cost. Four modules plus eight motors is a significant chunk of budget.
• Programming complexity. Encoder offsets, odometry, and tuning take real software effort.
• Maintenance. More moving parts means more that can loosen or fail mid-event.

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.

How to learn 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 →