Code
U2119
PEUGEOT
U — Network/User
Electrically controlled parking brake automatic trigger wake-up function status word reception anomaly fault: Data invalid
AI status
Completed
Completed
100%
Causes
- Corrupted or malformed CAN/FlexRay/LIN message from EPB or gateway
- Faulty EPB control module or internal software error
- Wiring harness damage, intermittent connector, or poor ground to EPB
- Low or unstable battery/vehicle electrical supply during wake-up
- Bus interference or multiple nodes transmitting conflicting data
- Incorrect module coding/configuration after repair or update
Symptoms
- Automatic EPB trigger (auto-apply/release) does not operate or is unreliable
- EPB warning lamp or message on instrument cluster
- Stored U2119 fault (may reappear after clearing)
- Possible failure to enter/exit sleep or wake modes for parking brake
- Unexpected parking brake behavior (e.g., not engaging or false engagement)
What to check
- Read DTCs and freeze-frame data from all modules (EPB, BCM, gateway, ABS)
- Check vehicle battery voltage and state of charge; ensure >12.4 V during tests
- Check CAN bus presence and activity with a scan tool or CAN analyzer
- Inspect EPB module connector and harness for corrosion, damage or water ingress
- Check module power and ground voltages at the EPB connector
- Attempt to reproduce by cycling ignition/sleep and monitoring message content
Signal parameters
- CAN message identifier and message name for EPB wake-up/status (manufacturer-specific)
- Expected data length (DLC) and valid status‑word byte(s) vs. received payload
- Signal frequency/period on wake sequence (burst on wake then periodic)
- Bit masks within the status word (e.g., ready/fault/wakeup bits) and allowed values
- Timestamp consistency and absence of bit errors or checksum failures if used
Diagnostic algorithm
- Retrieve and record all stored DTCs from EPB, BCM/gateway and ABS modules; note occurrence conditions.
- Check battery voltage and charging system; recharge or connect stable supply if below specification.
- Visually inspect EPB connector(s) and wiring for corrosion, damage, loose pins or water ingress; repair as needed.
- With a CAN/CAN-FD analyzer or scan tool, monitor the EPB wake-up/status message during ignition/sleep cycles; confirm message ID, DLC and payload content.
- If messages are missing or payload is garbage, probe power and ground at the EPB module while reproducing the event; look for voltage dips or intermittent connections.
- Swap or test suspected gateway/relay/terminator if bus wiring and module power are healthy and other modules show comms issues.
- Check for software updates or known manufacturer bulletins for EPB/gateway modules; reprogram or update calibration if applicable.
- If tests indicate module internal failure (no valid messages despite correct power/grounds and wiring), consider replacing or reflashing the EPB control unit.
- After repairs, clear DTCs and perform several wake/sleep cycles to verify no recurrence and restore normal EPB auto-trigger behavior.
Likely causes
- Missing or corrupt CAN message payload from EPB module due to module fault
- Intermittent wiring/connector fault at EPB harness or gateway
- Battery voltage drop during network wake-up leading to invalid status word
- Gateway or ABS/BCM misrouting or software incompatibility after update
Fault status
Status
EPB automatic trigger wake-up status word reception anomaly: data invalid — the control module received a wake/status message but the content did not meet expected format or values.
Repair difficulty: Medium
Diagnostic time: 1-3 hours
Similar codes
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
