U013F

Code

Generic U — Network/User

Lost Communication With Pedestrian Alert Control Module

Brand: Generic

Type: U — Network/User

Views: UK: 20 EN: 39 RU: 32

AI status

Completed

ready

Completed 100%

Page language: EN

Pedestrian Alert Control Module failure
Open/short or high-resistance wiring/connectors between module and data bus
Blown fuse or poor power/ground to the module
CAN/LIN bus fault (short to battery/ground, missing termination)
Corrosion, water intrusion or physical damage to connector or module
Module asleep, disabled by wake/sleep logic, or software communication mismatch after update

Pedestrian alert/warning chime or speaker for pedestrian alert may be inoperative
Related dash warning lamp or message (communication fault) displayed
Reduced or altered operation of systems that depend on pedestrian alert data
Possible multiple U01xx/U013x communication codes present
Intermittent operation of pedestrian alert or other networked features

Read all active and stored DTCs from all modules and note freeze frame/occurrence counts
Check for other network communication codes (U0100, U0121, U0140, etc.) that indicate wider bus issues
Visually inspect the Pedestrian Alert module connector and wiring for corrosion, pins pushed out, damage, or water entry
Verify module supply voltage and ground at the connector with key on and engine off
Check fuses and fusible links feeding the module
Measure CAN bus termination resistance between CAN High and CAN Low (expect ~60 ohms total) and check continuity to other modules

Module supply voltage: ~12 V (key on), stable within ~0.5 V
Ground: low resistance to chassis ground
CAN bus idle voltages: CAN High ~2.5–3.5 V, CAN Low ~1.5–1.8 V (nominal around 2.5 V recessive)
CAN differential waveform: valid square-wave data pulses when active; no bus chatter or dominant stuck condition
Heartbeat/periodic status message from module: typically periodic (1–10 Hz) or event-driven depending on implementation
Message frequency and specific CAN IDs vary by manufacturer — verify with OEM data

Retrieve and record all related codes and freeze-frame data from all control modules.
Check battery voltage and charge if low. Clear codes and attempt a key cycle to see if the module returns.
Inspect the Pedestrian Alert module connector and harness for damage, corrosion, or pushed-out pins. Repair as needed.
Verify power and ground at the module connector: measure key-on battery voltage on the power pin and low resistance to chassis on ground.
Check fuses and power distribution feeding the module; replace if blown and re-test.
Use a capable scan tool to poll the Pedestrian Alert module. If it does not respond, check wiring continuity from the module to the nearest gateway/ECU.
Measure CAN High/Low voltages at the module connector with key on. If voltages are abnormal, isolate wiring for short/open and repair.
With an oscilloscope or CAN bus analyzer, verify CAN differential waveform integrity and look for bus errors or stuck dominant states; check termination resistance (~60 ohms).
If wiring, power, and bus appear good and the module does not respond, attempt a module reset or reflash if supported by the OEM tool.
If reprogramming fails or module remains unresponsive, replace the Pedestrian Alert Control Module and perform any required coding or configuration.
After repair or replacement, clear DTCs and verify normal operation and that the code does not return during test drive.