Home / DTC / U2119 — Electrically controlled parking brake automatic trigger wake-up function status word reception anomaly fault: Data invalid

U2119 — Electrically controlled parking brake automatic trigger wake-up function status word reception anomaly fault: Data invalid

Detailed page for trouble code U2119.

35,619codes
59brands
11,925generic
23,694specific
Reset
Code

U2119

CITROEN U — Network/User

Electrically controlled parking brake automatic trigger wake-up function status word reception anomaly fault: Data invalid

AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Corrupted or malformed status word sent by EPB control unit or sender module
  • Intermittent or permanent wiring damage, corrosion, or loose connector at EPB module or gateway
  • CAN/LIN bus noise, short to battery/ground, or missing termination
  • Faulty EPB control module (software or hardware fault)
  • Incompatible or corrupted software/calibration after module replacement or update
  • Low battery or unstable supply voltage during module wake-up sequence

Symptoms

  • EPB warning lamp or message on instrument cluster
  • Automatic parking brake trigger/wake-up not available or behaves intermittently
  • Parking brake may not engage/disengage automatically; manual control usually still works
  • Related communication or gateway errors logged in other modules
  • Possible reduced functionality or limp-home behavior for parking brake system

What to check

  • Read all stored, pending and freeze-frame codes from all modules with a full-capability diagnostic tool
  • Check battery voltage and charging system health (stable >12.4V with ignition on)
  • Inspect EPB module connectors, pins, and harness for corrosion, damage or water ingress
  • Scan bus status (CAN/LIN) for errors, bus-off conditions or excessive error counters
  • Check for recent module programming or battery disconnect events
  • Observe live data/status word from EPB module and compare to expected values

Signal parameters

  • Message type: CAN or LIN status word frame from EPB control unit (manufacturer-specific ID)
  • Typical parameters to record: CAN ID (manufacturer-specific), DLC (data length), raw data bytes of status word
  • Expected bit fields: wake-up request bit, auto-trigger enable bit, status bits for EPB readiness — compare to OEM spec
  • Valid ranges: status-word bit patterns per OEM documentation (invalid if reserved or all-FF/00 where active data expected)
  • Bus speed: vehicle CAN bus (commonly 500 kb/s or 250 kb/s) or LIN baud rate per vehicle spec
  • Signal quality: dominant/recessive levels, absence of repeated error frames or excessive retries

Diagnostic algorithm

  1. Capture and record the U2119 occurrence details: timestamp, ignition state, other simultaneous codes and freeze frame data.
  2. Confirm battery voltage and health. If low, charge or connect stable supply, then clear codes and re-test.
  3. Using a diagnostic tool, monitor the EPB status word message on the bus (live data or bus trace). Note DLC, payload and timing. Look for malformed frames (all 0x00/0xFF bytes, truncated payloads, or unexpected bit patterns).
  4. Inspect physical connections: disconnect battery, visually inspect and reseat EPB module connectors, check for bent pins, corrosion or water ingress. Repair any damaged wiring or terminals.
  5. Probe CAN/LIN lines at the module: check for proper bus voltage, termination, and waveform integrity with an oscilloscope. Look for reflections, noise or shorts.
  6. Check for other ECUs reporting communication issues. If gateway issues present, perform gateway/module diagnostic tests per manufacturer procedures.
  7. If message is missing or malformed only from EPB, attempt a soft reset/power cycle of the EPB module and repeat tests. Reflash or update EPB software if a newer revision or known fix exists.
  8. If module continues to send invalid data after wiring and software checks, consider replacement of the EPB control unit and verify with known-good module or bench test per OEM guidance.
  9. After repairs or software updates, clear all codes, perform functional test of automatic EPB trigger/wake-up and re-check for reoccurrence. Log final test results.

Likely causes

  • Loose/corroded connector or damaged wiring between EPB module and vehicle bus/gateway
  • Temporary CAN/LIN communication glitch (low battery, interference) — intermittent
  • Faulty EPB control unit sending malformed status word
  • Software mismatch or corrupted module flash after recent service or update

Fault status

⚠️ Status
Invalid data received for EPB automatic trigger wake-up status word — receiving module flagged 'data invalid'.
🟡 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