U0658

Code

Generic U — Network/User

Lost Communication With Windshield Temperature Sensor

Brand: Generic

Type: U — Network/User

Views: UK: 19 EN: 42 RU: 21

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Open or short in sensor wiring or connector
Corroded, bent, or pushed-out connector pins
Failed windshield temperature sensor
Failed or unpowered control module that reads the sensor
Network bus fault (CAN/LIN) or missing termination
Blown fuse or bad power/ground to sensor or module

Symptoms

No windshield temperature reading in HVAC or instrument cluster
Automatic climate/defogging behaves poorly or falls back to default
One or more communication-related U-codes stored
Intermittent HVAC operation or wrong temperature display
Possible general network communication warnings

What to check

Scan vehicle and record all U-codes and freeze frame data
Check for related network codes (U0100, U0121, U0140, U0073, etc.)
Verify battery voltage is within specification
Visually inspect sensor, connector, and harness for damage or corrosion
Check sensor connector for water intrusion or bent pins
Use scan tool to monitor live data stream for windshield temp message presence and frequency

Signal parameters

Network message ID for windshield temp sensor (CAN or LIN dependent on vehicle)
Payload: ambient/windshield temperature value (°C or °F) or fault/status bytes
Message frequency: periodic update (typically 0.5–10 Hz depending on design)
Electrical: sensor supply voltage and ground presence at connector
CAN bus idle state ~2.5 V per line (verify CAN_H and CAN_L voltages) and termination ~60 Ω across CAN_H/ CAN_L

Diagnostic algorithm

Connect a diagnostic scan tool. Retrieve and note U0658 and any other codes and freeze frame data. Attempt to view live windshield temp data.
Clear the code(s) and drive or cycle vehicle to see if U0658 returns or is intermittent.
If the message is absent, inspect the windshield temp sensor connector and wiring for corrosion, water intrusion, pin damage, or loose terminals.
With ignition ON (engine off if specified), backprobe the sensor connector and verify reference supply voltage and ground presence per vehicle spec. Do NOT apply high voltages.
If supply/ground present but no data, monitor the network lines with a scope or lab tool: check for CAN/LIN traffic and the presence of the sensor message ID. Verify CAN_H/CAN_L voltages and termination resistance (≈60 Ω).
Perform continuity checks from the sensor connector to the receiving module(s) to locate opens or shorts. Wiggle wiring to reproduce intermittent faults.
If wiring and network are good, substitute a known-good sensor if available or bench-test the sensor per manufacturer procedure.
If a module is not responding on the network or is bus-off, diagnose that module for power, ground, and proper operation; repair as needed.
After repair or replacement, clear codes and verify system operation, confirm message presence in live data, and perform a test drive or environmental test if needed.
If network problems persist, consult vehicle-specific wiring diagrams and service information for detailed module locations and message routing; consider manufacturer technical support.