Nine times out of ten, a brake pedal that spikes to 100% for a frame and then drops back is not a dead load cell. It’s a wiring or grounding problem, a USB power problem, or a sensitivity curve you set months ago and forgot about. Actual load cell failure happens, but it’s the last thing on the list, and I’d rather you spend twenty minutes with a controller-input window open than $150 on a replacement cell you didn’t need.

The diagnostic order that has worked for me across a Fanatec CSL Elite LC, a Heusinkveld Sprint, a set of Moza SR-P pedals, and one Thrustmaster T-LCM that lived a hard life: rule out software first (curves, deadzones, competing apps), then USB and power, then cables and connectors, then the sensor itself. Work that list top to bottom and you’ll find it. Skip to the bottom and you’ll probably buy something you didn’t need.

What “spiking” actually looks like, and why it matters which kind you have

Before touching anything, open a raw input viewer. Windows’ Game Controllers panel (joy.cpl) is fine, though the bar is coarse. DIView or the brand’s own software (Fanatec Control Panel, Moza Pit House, Heusinkveld SmartControl, Simucube Tuner) shows a finer readout. Sit with your foot off the pedal and watch for a minute. Then hold roughly half pressure and watch again.

Three distinct behaviors show up and they point at different causes:

A flat line that occasionally jumps to full or zero for a single frame with your foot resting on the pedal is almost always electrical. Loose connector, ground noise, a USB hub that’s browning out, an RJ12 cable with a cracked crimp.

A jittery, fuzzy signal that wanders a few percent up and down constantly, even at rest, is usually noise on the analog side. Cheap USB extension cables do this. So does a load cell amp board sitting right next to a wheelbase power brick.

A signal that’s fine at low pressure but goes erratic or plateaus at high pressure points at the mechanical stack: elastomers or springs binding, the pedal arm bottoming on the cell housing, or the cell itself being overloaded or physically damaged. This is the one where the cell really might be dead.

Write down which of those you’re seeing. It shortens everything that follows.

Step one: software, because it’s free and it’s more often the cause than people admit

Start with the input curve. Most sims let you set a brake sensitivity or gamma value. iRacing has a brake force factor in the options and a separate curve slider; ACC has a gamma value per axis (I run 1.0 on load cells, never higher); Le Mans Ultimate and rF2 have sensitivity settings under the controls JSON that people modify once and forget. A steep curve near the top makes a perfectly linear, healthy cell look like it “jumps” from 70% to 100% over a tiny pressure change. That’s not spiking. That’s you asking for it.

Reset the curve to linear. Remove any deadzone at the top end (a max deadzone of 5% on a 100kg-rated cell clips the top of your travel and feels like the pedal “locks” at full). Then retest in the raw viewer, not in the sim. If the raw viewer is clean and the sim isn’t, the problem is entirely in the sim’s config.

Next, close everything that talks to the pedals. This one bites people constantly. If you have Fanatec’s software, SimHub, and a sim all polling the same device, and you’ve also got a Logitech or Thrustmaster driver lingering from an old wheel, you can get periodic stutters in the axis readout. SimHub in particular has a “vibration” or “pedal rumble” feature that, when mis-set, sends output that some pedal controllers interpret badly. Kill SimHub, retest.

Last software item: firmware. Fanatec’s load cell pedal firmware went through a run in 2023 where the brake reported momentary spikes on certain CSL Elite V2 units; a firmware update fixed it. Moza fixed a Pit House calibration bug that caused SR-P brakes to briefly report full throttle when the pedal was released quickly. Check the brand’s changelog for the words “brake” or “load cell” before assuming hardware.

Step two: USB and power

Pedal controllers are analog-to-digital converters. They are sensitive to dirty power in a way a wheel button box isn’t.

If the pedals plug into the wheelbase (Fanatec’s RJ12 setup, Moza’s pedal port on the R5/R9/R12, Thrustmaster’s DIN cable), skip ahead to cables. If they’re USB, do these in order:

Plug directly into a motherboard USB port, not a front panel header and not a hub. Front panel headers on many cases share a single internal connector and pick up noise from the case fans. Powered hubs are usually fine; unpowered hubs are the single most common cause of the “one-frame spike” symptom I’ve seen. The controller loses power for a few milliseconds during a voltage sag and the last reported value gets held or zeroed.

Disable USB selective suspend in Windows power options. This is an old fix and it still applies. It won’t cause continuous spiking but it does cause the “brake reads 100% for a moment after I’ve been sitting in the pits” symptom.

Try a different, shorter USB cable. If you’re using a 3m or 5m extension to reach a rig across the room, that’s a suspect. The USB spec limits passive cable length and load cell amp boards with weak drivers push right against that. Heusinkveld specifically recommends against long extensions on their older Sprint controllers for exactly this reason.

One more: a wheelbase with a big power brick (any direct drive unit, really) radiates. If your pedal USB cable runs parallel to the wheelbase power cable for a metre, move it. Cross them at right angles instead. I fixed a persistent Sprint jitter this way after a week of blaming the cell.

Step three: cables and connectors

This is where most real hardware faults live.

On Fanatec pedals, the RJ12 cable between pedals and base is a known weak point. The plastic latch tab breaks, the cable sits slightly loose in the socket, and vibration from hard braking wiggles it enough to drop contact for a frame. Pull the cable, look at the tab, check the pins for corrosion or one that sits lower than the others. Replace the cable (they’re cheap, under $15) before touching anything else. Same story for the internal RJ12 between the load cell board and the pedal set’s main board on the CSL Elite and ClubSport V3: unplug and reseat both ends.

On Thrustmaster T-LCM, the load cell plugs into the controller board with a small JST-style connector that isn’t captive. Users on r/simracing regularly report intermittent readings that go away after reseating that plug. While you’re in there, check the wire strain relief. The T-LCM has thin wires and the ones going to the cell fatigue where they enter the housing.

On Moza SR-P, the pedal-to-base cable uses a proprietary plug and the strain relief is decent, but the socket on the pedal side is on a small PCB that can crack if the pedal is dropped or overtightened to a plate. Wiggle the plug gently while watching the raw readout. Any change is your answer.

Heusinkveld and Simucube-style setups use proper ribbon or shielded cables and rarely fail here, but they do have amp boards with screw terminals on some revisions, and a screw terminal that has loosened over two years of braking vibration will produce exactly the one-frame spike pattern. Tighten every terminal you can find.

Generic rule: with the raw viewer open, flex, tap, and wiggle every cable and connector in the chain while watching. Physical fault, physical response.

Step four: the mechanical stack

Load cells measure force through compression. Anything between your foot and the cell that binds, stick-slips, or bottoms out will produce a non-linear or erratic reading, and it can feel like an electrical fault when it isn’t.

Elastomer stacks (Fanatec, Moza SR-P, Thrustmaster T-LCM) take a set over time and can develop a “notch” where they transition from one durometer to the next. Pull the stack, inspect each piece, and look for cracks or a flat face that’s deformed. Replacements are cheap and worth having on hand.

Spring-and-damper setups (Heusinkveld, Asetek Invicta, Simagic) can bind if the guide rod isn’t centred or if a preload nut has walked. If the brake feels fine for the first 40% and then jumps or gets erratic at higher force, this is a strong candidate. Check that the pedal arm isn’t contacting the cell housing at full travel; on the CSL Elite LC there’s a known issue where mounting the pedal at a shallow angle lets the arm hit the load cell bracket edge.

Also check the mount. A pedal plate that flexes under braking (many desk-mounted pedals, and some aluminium profile setups with the pedal deck bolted at only two points) shifts the load path off-axis. Load cells are meant to be loaded straight down their axis; off-axis force reads as noise. If your pedal tray visibly moves when you brake hard, that alone can produce spiking, and a Next Level Racing or Sim-Lab pedal deck upgrade fixes it better than any new pedal will. Stiffen first.

Step five: the cell itself

If everything above is clean and you still see erratic readings, or you see the high-pressure plateau/erratic pattern, the cell may be gone. Load cells fail by overload (someone standing on the pedal, or bracing on it to get in and out of a rig) or by a fatigued gauge. Symptoms: the reading drifts at rest and doesn’t settle, the reading is nonlinear at the top of the range, or the reading changes noticeably with temperature.

Most brands sell the cell separately. Fanatec’s CSL LC kit runs around $130 to $150 and includes the amp board; Moza sells a replacement SR-P load cell for around $60; Heusinkveld sells cells and elastomers as spares. Before you buy, borrow a friend’s or test a spare if you can, because I’ve watched three people replace cells only to find a USB hub was the actual problem.

The one-page checklist

1. Open a raw input viewer and characterise the spike pattern (single-frame, constant jitter, or high-force erratic).
2. Reset sensitivity to linear, zero any max deadzone, close SimHub and competing drivers, update firmware.
3. Direct motherboard USB, no unpowered hub, short cable, USB suspend off, route away from wheelbase power.
4. Reseat and inspect every connector; replace suspect RJ12/DIN/JST cables.
5. Inspect elastomers/springs, check for arm contact, stiffen the pedal mount.
6. Only then replace the cell.

FAQ

Why does my load cell brake spike to 100% when I release the pedal? Two common causes. First, a curve with a “release” or “brake pressure hold” setting in the pedal software (Moza’s Pit House and SimHub both have this) that misfires on fast release. Second, elastomer rebound: a stack that has taken a set can momentarily spring past neutral and load the cell briefly. Try a linear curve, then inspect the stack.

Can I fix load cell drift by recalibrating? Recalibrating resets the zero point and the max. It won’t fix drift that keeps moving after calibration. If the zero point wanders more than a couple of percent over a session, that’s the cell or its amp, not calibration.

Is a hall effect or potentiometer brake less prone to this? Potentiometer brakes (Logitech G29/G923, older Thrustmaster) fail differently: they develop a dead spot or noisy band as the track wears. Hall sensors are generally cleaner but measure travel, not force, so they aren’t a replacement for a load cell if you want consistent braking. A healthy load cell with clean wiring is still the best option; don’t downgrade because of one bad cable.

Before you order anything

Buy a replacement load cell only after you’ve done all of this: characterised the spike pattern in a raw viewer, tested on a direct motherboard USB port with a short cable, reseated every connector, and confirmed the pedal mount doesn’t flex. If the reading is still erratic at high force after that, order the cell. If the spike went away when you moved the USB cable, pull the extension and buy a proper powered hub or a short shielded USB cable instead. And if the whole tray moves when you brake hard, put the money into a Sim-Lab or Next Level Racing pedal deck first, because a new cell on a flexing mount will start spiking again in a month.