C0113 – Meaning, Symptoms, Causes & How to Fix It

C0113 is a chassis-level diagnostic indicator that points to a problem with a wheel-speed related signal or its circuit as interpreted by the vehicle’s stability and brake control systems. It does not guarantee a failed sensor or module; the exact meaning and affected component can vary by make, model, and year. You should approach C0113 with a test-driven mindset: check wiring and connectors, power and ground reference, signal plausibility, and the vehicle network messages before replacing parts. Typical systems involved include Anti-lock Braking System (ABS) and Electronic Stability Control (ESC).

What Does C0113 Mean?

In SAE J2012 formatting C0113 is a chassis diagnostic code indicating a problem in a wheel-speed related circuit or the signal used by chassis control modules. This guide follows SAE J2012 formatting and the standardized DTC descriptions are published in the SAE J2012DA digital annex.

C0113 is shown here without a hyphen Failure Type Byte (FTB). An FTB (when present) provides a subtype or failure detail such as signal high/low, intermittent, or plausibility failure; the base code C0113 remains the system-level indicator and can vary in exact implementation across manufacturers and model years.

Quick Reference

System: Chassis wheel-speed signal/circuit used by ABS/ESC/TCS
Common symptoms: ABS/ESC warning lights, degraded stability control, driveability may be unaffected
First checks: Scan tool data, live wheel-speed values, power/ground at sensor circuits, CAN network health
Typical root areas: Wiring/connectors, sensor plausibility, module input, or network message loss
Approach: Test-driven diagnosis — confirm electrical and network evidence before parts replacement

Real-World Example / Field Notes

Field note 1 — Intermittent connector fault: A vehicle arrived with ABS and ESC lights and C0113 stored. Scan tool showed one wheel-speed channel dropping to zero intermittently while others remained steady. Visual inspection revealed a chafed harness at the wheel well where the sensor pigtail flexed. Backprobing the sensor connector with a digital scope showed signal dropout when the steering was turned. Repair: replace/repair the damaged section and verify consistent sine/square wave on the scope and steady CAN messages before clearing the code.

Field note 2 — Poor ground/reference: Another workshop case had C0113 with low-amplitude speed signals across multiple wheels. Voltage checks at the sensor reference and ground showed elevated resistance in the common ground splice. Tightening and cleaning the ground reduced reference noise and restored plausible wheel-speed amplitudes. Confirmation included stable live data and absence of ERR frames on the Controller Area Network (CAN) scanner.

Field note 3 — Module input plausibility: On a third vehicle the wheel sensor waveforms looked reasonable but the ABS module flagged a plausibility mismatch between wheel-speed sensors. The module was commonly associated with aging internal capacitors in that model, but you must confirm by verifying sensor-to-module wiring continuity, comparing live wheel-speed at matched speeds, and checking Mode $06 or freeze-frame data. Only after failing those electrical and plausibility tests would module replacement be justified.

DISPLAY_LABEL: Chassis Circuit Fault – Speed Signal

Symptoms of C0113

Warning Lamp ABS, ESC, or traction control warning illuminated on the dash.
Poor Brake Feel Reduced stability or unexpected ABS activity under braking.
Traction Interventions Unwanted traction control or stability control interventions during low-speed maneuvers.
Inconsistent Speed Readings Vehicle speedometer or cruise behavior that drops or fluctuates intermittently.
Diagnostic Data Scant or implausible wheel speed sensor values on a scan tool (zero, frozen, or noisy signals).
Intermittent Faults Fault sets and clears with temperature, vibration, or after driving for a while.

Common Causes of C0113

Most Common Causes

– Faulty or intermittent wheel speed sensor signal commonly associated with an ABS/ESC wheel speed input. Note: the exact sensor or module named by OEMs can vary by make/model/year; confirm with wiring and signal tests.
– Wiring damage or poor connector pin contact between the speed sensor and the anti-lock brake system (ABS) control module.
– Corroded or bent connector terminals causing high resistance or intermittent open/short conditions on the sensor circuit.

Less Common Causes

– Power or ground faults to the ABS/ESC module or to the sensor reference circuit producing implausible signals.
– Faults in the ABS or vehicle stability control module processing (rare compared with wiring/sensor problems).
– Network communication errors (CAN/LIN) that cause a control module to report implausible speed correlation; these vary by vehicle and require bus-level testing to confirm.

Diagnosis: Step-by-Step Guide

Tools: OBD-II scan tool with ABS/ESC capability, digital multimeter, oscilloscope or lab scope (preferred), wiring diagrams, backprobe pins or breakout harness, insulated picks for connectors, safety stands/ramps, basic hand tools, and a second technician or jumper wires if needed.

Verify the concern: confirm the dash warnings, note when the fault occurred, and reproduce the symptom if safe to do so.
Collect data: connect a capable scan tool, read freeze-frame and live data for wheel speed sensors, ABS module status, and monitor Mode $06 or live waveform captures if available.
Compare signals: check all wheel speed readings for plausibility and correlation while rolling the vehicle by hand or driving slowly—one sensor out of sync suggests a sensor or wiring issue.
Visual inspection: inspect sensor connectors, harness routing, and tone rings for damage, contamination, or missing teeth; wiggle harness while watching live data for intermittent changes.
Power/ground check: with the key on, verify ABS module power and ground circuits with a multimeter; a failing ground or supply will produce weird or missing signals.
Signal verification: backprobe the sensor connector and measure voltage/pulses with an oscilloscope while the wheel is turned. A clean square/AC pulse or expected sine waveform confirms a good sensor signal; a dead, noisy, or clipped waveform indicates a problem.
Wiring tests: check continuity and resistance between the sensor and ABS module; check for shorts to battery or ground. Swap an identical sensor (only if vehicle-specific guidance allows) or use a bench test to confirm sensor plausibility before replacing.
Network check: if signals are good but the module still reports C0113, verify CAN/LIN messages to/from the ABS module and scan for communication errors; intermittent bus errors can masquerade as sensor faults.
Confirm the root cause: correlate a failed test (open wiring, bad waveform, high resistance, lost power/ground, or lost CAN messages) to justify repair—do not replace parts without a failing test result.
Repair verification: after repair or connector service, clear codes and perform a road test while monitoring live data and re-check to ensure the fault does not return and that ABS/ESC monitors complete as expected.

Professional tip: prioritize scope and backprobe testing over swapping parts. A short waveform capture or a wiggle test that reproduces the fault is the fastest way to confirm whether the sensor, wiring, power/ground, or network is at fault—document your readings before replacing modules or sensors.

DISPLAY_LABEL: Chassis Circuit: Wheel Speed/ABS Sensor Correlation

Possible Fixes & Repair Costs

Always confirm the fault with electrical and network tests before replacing parts. Common repair paths for a C0113-style chassis circuit fault focus on wiring/connectors, wheel-speed sensor plausibility, power/ground, and control module communication. Low-cost fixes usually involve connector cleaning or a simple splice repair justified by visual damage or a failed continuity check between the sensor and module. Typical repairs include sensor replacement or harness repair when bench resistance and oscilloscope traces show no valid AC or digital pulse. High-cost repairs can involve control module repair/reprogramming or extensive wiring harness replacement when CAN (Controller Area Network)/low-speed LIN (Local Interconnect Network) diagnostics show message loss or a module-level internal fault.

Estimated cost ranges (parts + labor):

Low: $25–$120 — justified by contaminated/damaged connector found on inspection or a confirmed open/short localized within accessible wiring.
Typical: $150–$450 — justified when bench resistance, supply voltage, and oscilloscope waveform fail at the sensor and a sensor swap or harness repair restores correct signals.
High: $500–$1,200+ — justified only after CAN bus frame checks and module power/ground tests indicate a control module fault, or when extensive harness replacement and programming are required.

Factors affecting cost: labor hours (access difficulty), OEM vs aftermarket parts, need for module programming, and diagnostic time. Do not replace sensors or modules without confirming the failing test: continuity/power/ground checks, sensor waveform plausibility on an oscilloscope, and successful CAN/LIN communication verification.

Can I Still Drive With C0113?

You can often drive with this code present, but it depends on what the tests show. If the fault disables ABS (Anti-lock Brake System), ESC (Electronic Stability Control), or traction control, you lose those safety aids — driving in wet, icy, or emergency-braking conditions becomes riskier. Use a scan tool to check ABS/ESC status and live wheel-speed data; if wheel-speed readings are implausible or missing, avoid high-speed or hazardous driving until the fault is verified and repaired.

What Happens If You Ignore C0113?

Ignoring the code can leave ABS/ESC/TCS systems degraded or disabled, increasing stopping distances and loss-of-control risk in low-traction situations. It may also allow further wiring or module damage if the underlying electrical issue worsens.

Last updated: March 1, 2026

Key Takeaways

C0113 is a chassis-level circuit fault often tied to wheel-speed or ABS-related signal correlation. Follow a test-driven diagnostic: confirm the symptom, gather scan data (including Mode $06/Live data), prioritize wiring/connectors, check power and ground, and verify CAN/LIN frames before replacing parts. Repairs should be justified by clear test evidence: failed continuity, missing sensor waveform, or confirmed module communication loss. Safety systems may be affected — treat ABS/ESC advisories seriously.

Vehicles Commonly Affected by C0113

C0113-type faults are commonly seen across many manufacturers and vehicle types — passenger cars, SUVs, and light trucks. Reports are frequently associated with European makes (commonly seen on BMW and Mercedes models), Asian brands (often reported on Toyota and Honda platforms), and American trucks/SUVs. Exact definition and affected components can vary by make, model, and year; always confirm by checking the vehicle’s wiring diagrams and performing basic electrical and CAN/LIN testing.

FAQ

Can I clear C0113 with a cheap OBD-II reader?

Yes, many basic OBD-II scanners can clear stored chassis codes, but clearing does not diagnose the cause. If the underlying electrical or communication fault persists, the code will return. Use a capable scan tool to capture freeze-frame, Mode $06 data, and live wheel-speed values after clearing. Reappearance of the code during test drives or when specific conditions recur indicates the need for the step-by-step electrical and CAN/LIN tests described earlier.

Is C0113 usually a sensor problem?

Not necessarily. C0113-style codes often correlate with wheel-speed sensor signals but do not guarantee a failed sensor. The fault can be wiring, connectors, power/ground, or controller communication. Confirm with a multimeter and oscilloscope: correct sensor resistance and a clean AC/digital waveform at the sensor connector with proper supply voltage confirms a good sensor. Missing waveform, open/short continuity, or absent CAN frames point elsewhere.

Can a weak battery or charging issue cause C0113?

Yes. Voltage instability or low system voltage can corrupt sensor signals or module operation, leading to communication and plausibility failures. Verify battery resting voltage, charging system voltage under load, and stable supply at the ABS/ESC module and sensors. If voltage tests show drops or noise and resolving charging/battery faults clears network errors and restores valid sensor data, charging system repair is the justified fix.

How long does professional diagnosis take for C0113?

Diagnosis time varies but typically takes 1–3 hours for a thorough, test-driven approach: scan tool data capture, visual wiring inspection, power/ground checks, continuity testing, and waveform recording on an oscilloscope. If initial tests point to module-level issues or hard-to-access harness damage, additional bench testing or disassembly adds time. Accurate diagnosis prevents unnecessary parts replacement and lowers total repair cost.

Will replacing a wheel-speed sensor fix the code?

Sometimes, but only when tests show the sensor is at fault. Replace a sensor if bench resistance, live scope waveform, and plausibility tests confirm the sensor is producing no or incorrect pulses while wiring and module power/ground/CAN signals are good. If replacing the sensor does not restore valid data, continue diagnosing wiring, connectors, and module communication before replacing other components.

Quick Glossary

ABS: Anti-lock Braking System. Helps prevent wheel lock-up during hard braking.
ESC: Electronic Stability Control. Uses braking/torque control to help keep the vehicle stable.
TCS: Traction Control System. Reduces wheelspin by applying brakes and/or reducing engine power.
CAN: Controller Area Network. Vehicle communication bus used by control modules to share data.
Wheel speed sensor: Sensor that reports wheel rotation speed to ABS/ESC systems.
Intermittent: Comes and goes. Often caused by a loose connection, vibration, moisture, or internal component failure.

C0113 – Chassis Circuit Fault — Wheel Speed Signal