Brake system icon

Brake pad wear via OBD-II: how BMW, Audi, Mercedes "count" remaining life

What OBD-II shows about brake pads on modern cars: wear sensors, calculated brake pad wear, codes C1000, C1100, and why "2000 mi to replacement" on a BMW is not guesswork.

AI-generated 3 min read

On a classic car brake pad wear is a visual inspection only: pull the wheel, look. On modern German cars (BMW, Audi, Mercedes, Volvo) it’s a live parameter the ECU computes as “mileage × driving style × brake temperature”. Via OBD-II you can read “remaining 2000 mi” or “12% life left”. Below — how it works and on which cars.

Two ways to measure wear

1. Wear sensor — electric

  • On front pads — embedded wire
  • When pad wears down to critical thickness (2-3 mm) — wire wears through and opens circuit
  • ECU sees open → turns on “Brake Pad Wear” light
  • Only two states: ok / replace now
  • Sensor is single-use, replaced together with pads

2. Calculated wear (BMW, Audi, Mercedes)

  • No physical sensor per wheel
  • ECU calculates wear from a formula:
    • Mileage since last replacement (from TCB service reset)
    • Braking events (from ABS wheel-speed sensors — which wheels brake more)
    • Temperature (from caliper thermal sensor or calculated)
    • Style (gentle vs aggressive)
  • Result: % remaining, distance to replacement in mi, estimated service date

OBD-II codes

CodeMeaning
C1000Front brake pad wear (fault)
C1100Rear brake pad wear
B1064Brake wear sensor circuit
Custom (VAG, BMW): often no code, just a cluster message

What OBD-II can show

Via Mode 22 UDS (for cars with calculated wear):

  • Front left pad wear (%) — 76% remaining
  • Front right pad wear (%) — 78%
  • Rear left / right pad wear (%) — separate
  • Distance to next service (mi) — computed
  • Brake disc thickness (mm) — on some cars measured by laser
  • Cumulative braking energy (kJ) — “how much you’ve braked in your life”

Car Diagnostics supports these parameters for VAG (Audi, VW, Skoda, Seat), BMW, Mercedes (Xentry protocol), Volvo — see compatibility.

Example: BMW 5 Series (F10, N57)

Via ISTA or our app:

  • Front pad wear: 12% remaining, ~2000 mi
  • Rear pad wear: 32% remaining, ~5300 mi
  • Front disc thickness: 26.4 mm (min 24 mm) → replace together with pads
  • Next brake service due: at 80 000 mi

Everything based on mileage — 62 000 mi without replacement means new pads.

Wear interpretation

StateAction
50%+Don’t worry
30-50%Plan for next service
15-30%Order pads
5-15%Schedule in next 1-2 weeks
< 5% or lightREPLACE NOW — brakes may squeak, disc will be damaged

Practical tips

  • Replace pads and discs together if disc is near min thickness — otherwise new pads wear out fast
  • Don’t “burn” the pads — long downhill braking accelerates wear 3-5x
  • Sync front and rear — one set at 20%, another at 60% is normal (fronts work 3-4x more often)
  • Ceramic pads last longer (35-55k mi) but are more expensive and less aggressive when cold

What AI agent adds

Our Prediction Agent tracks wear trend and warns:

  • “You drive 40% more aggressively than average for this model — wear will accelerate”
  • “Rear pads will finish in 6-7 weeks — time to order”
  • “Front discs will reach min thickness at the same time as pads — order the set”

Almost like having a personal BMW service tech checking your car weekly.

Limits

  • On old cars without sensor and without calculated wear (most Toyota, Honda, Renault, Kia pre-2015) — OBD-II shows nothing. Visual only.
  • On pickups and commercial vehicles — often the metric is disc thickness, not pad %.

Try it on the free tierpair an ELM327 adapter. Standard codes C1000/C1100 on every car. Calculated wear via Mode 22 UDS — on paid tier.