Home / DTC / U1213 — Fault: absence of communication with the stability control (ESP) ECU: Value received incorrect

U1213 — Fault: absence of communication with the stability control (ESP) ECU: Value received incorrect

Detailed page for trouble code U1213.

32,293codes
58brands
9,839generic
22,454specific
Reset
Code

U1213

DS U — Network/User

Fault: absence of communication with the stability control (ESP) ECU: Value received incorrect

Brand: DS
Views: UK: 1 EN: 1 RU: 3
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Intermittent or failed CAN communication between ESP ECU and gateway/other modules
  • Corrupted CAN messages due to wiring damage, poor connector contacts, or grounding issues
  • Incorrect CAN bus termination or bus voltage problems
  • Faulty ESP (stability control) ECU
  • Software mismatch or corrupted ECU software/calibration
  • Conflicting/duplicate node IDs on CAN bus after aftermarket installation or replacement ECU

Symptoms

  • ESP/traction/ABS warning lamp illuminated
  • Loss of ESP/traction control functionality or degraded brake/ABS operation messages
  • Intermittent or permanent messages on instrument cluster about stability control malfunction
  • Possible drivability issues if other systems rely on ESP data (eg. engine torque cut during slip events)
  • Multiple related communication DTCs stored in gateway and other modules

What to check

  • Read and record all stored DTCs and freeze-frame data from gateway, ESP, ABS, engine ECU and instrument cluster with OEM-capable scan tool
  • Check for corresponding ABS/ESP codes (U0121, etc.) in other modules
  • Inspect battery voltage (while cranking and key ON) and verify good charging system voltage
  • Visually inspect ESP ECU connector and wiring for corrosion, bent pins, water ingress or damage
  • Check ground connections for ESP ECU and chassis grounds for tightness and corrosion
  • Verify CAN bus physical layer: measure CAN_H and CAN_L voltages with key ON (idle), and check termination resistance (approx. 60 Ω across H-L) with battery disconnected

Signal parameters

  • CAN bus IDs used by ESP (module-specific - verify with vehicle-specific data) and message frequency (wheel speeds ~50–100 Hz, IMU data 20–100 Hz)
  • Expected CAN bus speeds (vehicle-dependent; commonly 500 kb/s or 250 kb/s) — confirm with factory data
  • Idle common-mode voltages: CAN_H ~2.5 V, CAN_L ~2.5 V (dominant/differential voltages during traffic) — verify with scope
  • Typical termination: ~60 Ω measured across CAN_H and CAN_L with battery disconnected
  • Common ESP payloads to verify: wheel speeds, yaw rate, lateral acceleration, steering angle, brake pressure, ESP active/inhibit flags (expected value ranges per sensor type)
  • Message timing and CRC/checksum validity where supported by manufacturer

Diagnostic algorithm

  1. Record all DTCs and freeze-frame info from all modules; note any related U- or C-/P-codes.
  2. Confirm battery and charging system voltage stable (12.0–14.8 V) during tests; charge battery if low.
  3. Inspect ESP ECU connector and harness for corrosion, moisture, damage and repair as needed.
  4. With vehicle key ON, check CAN bus voltages at the ESP connector pins: measure CAN_H and CAN_L idle voltages and verify ~2.5 V common-mode and correct differential behavior with a scope.
  5. With battery disconnected, measure resistance across CAN_H and CAN_L at two ends of the bus to confirm proper termination (~60 Ω).
  6. Use OEM scan tool to monitor live CAN messages from the ESP module. Confirm correct message IDs, update rates and reasonable payload values (wheel speeds near zero when stationary, yaw near zero, etc.).
  7. Perform wiggle tests on wiring and connectors while monitoring communication to reproduce the fault. Inspect for intermittent faults.
  8. If the CAN physical layer is clean but messages are corrupted or incorrect, check for software/calibration updates or mismatches; compare part numbers and software versions of the ESP ECU with factory data.
  9. If a wiring short/open or faulty termination is found, repair or replace harness sections and re-test.
  10. If wiring and power/grounds are good and software is current, swap or reprogram ESP ECU (follow manufacturer procedure) and verify whether correct messages are restored.
  11. After repair, clear codes and perform road test to confirm issue does not return and ESP/ABS system operates normally.

Likely causes

  • Poor connector contact or corroded pins on ESP module harness
  • Damaged CAN wiring (chafing, short to ground/12V) between ESP and gateway
  • Low battery/unstable supply or poor ground to ESP ECU causing data corruption
  • Missing/incorrect CAN termination resistor (120 Ω) or partial open termination
  • Software/configuration mismatch after module replacement or incomplete flash

Fault status

⚠️ Status
Invalid/incorrect data received from ESP (stability control) ECU or intermittent/no communication on CAN bus.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email