Nine times out of ten, pedals that won’t calibrate are not broken. They’re either plugged into the wrong thing, fighting a second driver that also wants to own them, or reporting a raw signal that never reaches the range the software expects. The actual repair usually takes four minutes and involves no screwdriver. The frustrating part is that every brand fails differently, and the forum advice you found (“reinstall the driver”) is a shotgun aimed at the wrong wall.

So here’s the verdict up front: before you buy anything, unplug the pedals from the wheelbase and plug them into the PC by USB if your set supports it, or vice versa. That single swap resolves more calibration failures than any other step, because the two paths use completely different code, and one of them is usually the broken one. If that doesn’t do it, the problem is almost always a load cell sitting outside its expected voltage window, a Hall sensor magnet that’s drifted, or Windows keeping a stale HID descriptor cached from a device you owned two firmware versions ago.

Now the details, because “which of those three” depends heavily on whose pedals are under your desk.

What “not calibrating” actually means

There are three distinct failures and people mash them all into one search term.

The first is that the calibration wizard refuses to run or hangs. Throttle bar sits at 0 no matter how hard you stomp, or it’s pinned at 100 and won’t come down. This is a signal problem: the software isn’t seeing the pedal at all, or it’s seeing a rail.

The second is that calibration completes but the result is nonsense. You set min and max, hit save, and the brake now hits 100% at a third of travel, or the clutch never reaches full. This is a scaling or curve problem, and it’s the most common one on load cell brakes.

Third: it calibrates fine, works fine, and then loses everything on reboot. Different animal entirely. That’s a firmware/EEPROM write failure or a driver that isn’t writing to the base’s persistent memory, and it is the one failure where you genuinely might have a hardware fault.

Figure out which one you have before you touch anything. It saves you an hour.

Fanatec

Fanatec’s problem is that it has two calibration paths and they don’t always agree with each other. Pedals connected via the RJ12 cable to a Podium, DD1, DD2, CSL DD or Gran Turismo DD base are calibrated through the base’s tuning menu or Fanatec Control Panel. Pedals connected by USB (which the Fanatec CSL Elite V2 and ClubSport V3 both support) show up as their own HID device with their own driver page. If you have ever plugged them in both ways, Windows now has two device entries and at least one of them has stale calibration data.

The fix that works: uninstall the Fanatec driver, reboot, then in Device Manager enable “show hidden devices” and delete every greyed-out Fanatec entry you find under Human Interface Devices and under Universal Serial Bus controllers. There will be more than you expect. Then reinstall the driver with the base powered on and the pedals attached by only one method. Not both. Pick one.

Firmware mismatch is the other Fanatec special. The base firmware, motor firmware, and the pedal firmware (yes, the V3s have their own) all have to be on a matching driver package. Fanatec Control Panel will happily let you run a base on 455 with pedals expecting 460, and the symptom is a calibration wizard that runs, appears to save, and reverts. Check the Update tab and update everything, including the parts it lists as “optional.”

On the ClubSport V3s specifically: if your brake calibrates but the whole usable range compresses into the first bit of travel, that’s not calibration. That’s the brake performance kit or the elastomer stack. The V3’s load cell reads force, and if you’ve got the soft elastomer in there and you’re a heavy-footed person, you’ll saturate the cell early. Swap in a firmer elastomer or dial the brake force down in the tuning menu. People spend weeks recalibrating a pedal that just needed a $12 rubber puck.

The community texture here, since you’ll run into it: Fanatec’s hardware is largely good and its support is a long-running sore point. If your calibration failure is genuinely a dead load cell, budget for a slow ticket. Buy the replacement part yourself if it’s out of warranty; the sensor is not exotic.

Moza

Moza’s pedals (Moza SR-P, SR-P Lite, CRP) calibrate through Pit House, and Pit House is the single most common cause of Moza calibration problems. Two things go wrong.

One: Pit House needs to be running as administrator to write calibration to the pedals’ memory. Run it normally and the wizard completes, shows green, and forgets everything at the next power cycle. If your Moza pedals lose calibration every reboot, that is very probably all this is. Right click, Run as administrator, redo the calibration, close Pit House properly.

Two: Pit House updates have shipped more than one regression on pedal calibration. If you’re on a version from the last month or two and calibration suddenly stopped working after an update, check the Moza Discord before you assume hardware failure. The community there is fast and blunt about it, and Moza usually pushes a fix within a couple weeks. Rolling back Pit House is a legitimate move.

The SR-P load cell brake also has a mechanical range setting that people miss. There’s an adjustment on the brake for preload, and if it’s cranked, the cell already reads a load at rest, so the “release the pedal” step of calibration records a nonzero minimum. Result: the game thinks you’re always braking 8%, and your car won’t accelerate properly. Back the preload off, recalibrate at true zero, then reapply preload if you want it.

Moza is a newer brand and the software shows it. The hardware is genuinely competitive at the price; Pit House is not.

Logitech

If you have a G29, G920, G923 or the newer Logitech Pro Pedals, there is no calibration wizard in the traditional sense, and that trips people up. G HUB has no pedal calibration page. The G29/G920 pedals self-calibrate every time the wheel does its startup sweep, which is why the wheel needs to complete that full lock-to-lock rotation on boot with nothing obstructing it. If the wheel is mounted so the rim hits your desk during the sweep, or you grabbed it while it was moving, calibration is garbage and pedals can be part of the collateral.

Unplug it. Plug it back in. Hands off. Let it finish.

If a G29 pedal is genuinely stuck, the cause is nearly always the potentiometer, and they wear out. The throttle is usually first because it sees the most travel. Symptom: jitter at part throttle, or a dead zone that appears halfway. You can clean a pot with contact cleaner and buy yourself another six months, and on a set of pedals this old that’s the correct economic call. Beyond that, do not spend money repairing a G29 pedal set. Replace it.

The G923’s brake uses a rubber cone, not a load cell, and it fatigues. If your G923 brake got mushy and now reads full brake at half travel, the cone is compressed. Cheap to replace.

Thrustmaster

T-LCM, T3PA, T3PA-Pro. The T-LCM is the interesting one because it’s a load cell and it has a dedicated calibration procedure that people skip.

Thrustmaster’s Control Panel has a pedal calibration option, but the T-LCM also stores its own calibration in the pedal set, and the two can disagree. If the brake behaves wrong, do the pedal-side calibration first: with the pedals plugged in, there’s a documented button-hold sequence to reset the load cell range. Then, and only then, verify in the Windows game controller properties page (joy.cpl, still the best diagnostic tool nobody uses) that the brake axis goes 0 to 100 with your actual foot pressure.

That’s the trick, incidentally, for every brand. joy.cpl in the Run box shows you the raw axis. If the axis moves cleanly there, your pedals are fine and your problem is in the sim or the driver layer. The same tool diagnoses a wheel that pulls to one side. If it doesn’t move there, no amount of iRacing config is going to save you.

Thrustmaster’s other quirk: their pedals draw power through the wheelbase on some configurations, and an underpowered USB hub will produce exactly the symptoms of a calibration failure. Plug into a rear motherboard port. Not the hub, not the monitor, not the front panel.

Simagic, Asetek, Heusinkveld

Group these because they behave similarly: high-end pedals, dedicated USB connection, their own configuration software (SimPro Manager, RaceHub, SmartControl), and generally the calibration works because that’s the whole point of paying $500 to $1,200 for pedals.

When they do fail, it’s the software’s device permissions on Windows 11, or two config apps running at once. Heusinkveld SmartControl and Simagic’s SimPro Manager will both try to claim a device, and if you’ve ever owned both brands, close the other one. Sounds stupid. It’s the answer more often than it should be.

Heusinkveld’s Sprints are worth a specific note: the brake is a genuine load cell and SmartControl gives you a curve editor. If people say their Heusinkveld brake “won’t calibrate right,” what’s usually happening is they set the maximum at a force they can only hit by trying, so 80% braking in-game requires a leg press. Set your max at a force you can hit repeatedly, comfortably, lap after lap, at Spa in the Porsche 911 GT3 R going into Les Combes on lap 40 when your leg is tired. Not at the force you can hit once fresh.

The load cell truth nobody tells you

A load cell brake doesn’t measure travel. It measures force. So “calibration” is really you telling the software what force equals 100%.

Set it too low and the brake is twitchy and you’ll lock the fronts constantly. Set it too high and you’ll never reach full ABS threshold and you’ll be complaining that the car won’t stop. Most people set it far too high the first week because pressing hard feels satisfying, then wonder why they’re two seconds off pace.

Starting point: aim for roughly 40 to 50 kg of force at 100% if you’re a normal-sized adult with a rigid rig. On a wheel stand or a desk mount, go lower, because you’ll push yourself backwards before you reach 50 kg and the whole thing is academic. Then live with it for a week and adjust. The real test is whether you can hold a consistent 85% brake through a long braking zone without thinking about it. If you can’t, your max is wrong.

This is also why “my brake calibrated but feels awful” is the most common version of this complaint, and it is not a calibration bug. It’s a setting you chose badly.

Quick diagnostic order

That last row deserves a sentence. iRacing, ACC, and rF2 all cache their own controller configuration, and if the device GUID changed (which it does when you switch cable paths, or update firmware), the sim is looking for a device that no longer exists. Delete the controller config in the sim’s Documents folder and remap. iRacing’s is in Documents\iRacing\controls. This costs you five minutes and fixes a genuinely maddening class of problem where the pedals work perfectly on the desktop and do nothing on track.

FAQ

Why do my pedals lose calibration every time I restart my PC? Almost always a permissions problem: the configuration software can’t write to the pedals’ persistent memory, so it holds calibration in RAM and loses it. Run the config app as administrator. If that doesn’t stick, the base and pedal firmware are on different versions, or the EEPROM on the pedal controller is failing, which is the one scenario here that’s a real hardware fault.

Should I calibrate in the software or in the sim? Software, always, and then leave the sim’s settings at linear with zero deadzone. Calibrating twice (once in the driver, once as a deadzone or curve in iRacing) stacks two transformations on top of each other and you end up with a pedal that responds strangely and you can’t work out why. Get the raw axis right first.

My brake calibrates fine but I still can’t modulate it. Is the pedal bad? No. Your max force is set too high, or you’re on a potentiometer brake and expecting load cell behavior. A rubber-cone or spring brake measures position, so you’re modulating with distance, which every human is worse at than modulating with pressure. That’s the entire reason load cell brakes are the single biggest upgrade in sim racing and why people bang on about them incessantly. They’re right to. Our best load cell pedals under $200 guide covers the affordable options.

Before you order anything

Check three things, in this order.

Plug your pedals into a rear motherboard USB port directly and open joy.cpl. If all three axes sweep cleanly from 0 to 100, your hardware is fine and every remaining problem is software. Don’t buy pedals.

If an axis is dead or noisy and it’s a Logitech or an older Thrustmaster with potentiometers, it’s the pot, and a set of used pedals costs less than your time. Replace, don’t repair.

If your brake calibrates fine but feels like a light switch, you don’t have a calibration problem, you have a spring brake, and no amount of fiddling fixes that. That’s when a load cell upgrade is actually justified: the Fanatec ClubSport V3 if you’re already in Fanatec’s world and want to keep the RJ12 path, the Moza SR-P if you want load cell braking at the lowest sane price and can tolerate Pit House, or the Heusinkveld Sprint if you’re going to be doing this for years and want to stop thinking about pedals entirely. Skip the mid-tier stuff in between. It exists to make the top tier look expensive. For the full ranking, see our best sim racing pedals guide.