C1628

Code

HYUNDAI C — Chassis

CAN Time-out Cluster

Brand: HYUNDAI

Type: C — Chassis

Views: UK: 20 EN: 31 RU: 15

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Broken, shorted or intermittent CAN_H / CAN_L wiring or connectors
Poor ground or low battery/voltage causing module resets
Faulty instrument cluster module
Another module on the CAN bus causing bus errors (short to power/ground)
Missing or incorrect termination (open/failed resistors)
Corroded connectors or water intrusion in harness

Symptoms

Instrument cluster frozen or gauges/needles not updating
Multiple CAN-related warnings or lamp illumination (CAN error, ECU unavailable)
Loss of functions that rely on cluster messages (speedometer, odometer, warning lights)
Intermittent or permanent no-start or drivability effects if other modules lose messages
Stored communication-related trouble codes in other modules

What to check

Retrieve all stored and pending codes from all modules using a capable scan tool
Inspect CAN_H and CAN_L wiring and connectors at the cluster and junction points for damage or corrosion
Measure battery voltage and main grounds; verify stable 12V supply to modules
Check termination resistance between CAN_H and CAN_L (≈60 ohms total for a 2-terminator bus)
Use an oscilloscope or CAN bus analyzer to view CAN_H/CAN_L signals for noise, missing frames or bus-off conditions
Disconnect suspect modules one at a time to see if the timeout stops (isolate faulty node)

Signal parameters

Idle (recessive) voltage: CAN_H ≈ 2.5 V, CAN_L ≈ 2.5 V (lines equal)
Dominant state: CAN_H ≈ 3.5 V, CAN_L ≈ 1.5 V (differential ≈ 2.0 V)
Termination resistance: ≈ 60 ohms measured between CAN_H and CAN_L with ignition off/isolated
Typical bus data rate (vehicle dependent): commonly 250 kbps or 500 kbps for vehicle networks
Look for consistent message frames and correct arbitration IDs for the cluster on the analyzer

Diagnostic algorithm

Connect a factory-capable scan tool, read stored/pending codes in all modules, note freeze frame if present.
Clear codes, cycle ignition and observe whether C1628 returns immediately or after drive cycle.
Verify battery voltage (12–14.5 V) and check primary chassis and engine grounds for corrosion/tightness.
Visually inspect harnesses and connectors at the instrument cluster and major junctions for damage or corrosion; repair as needed.
Measure CAN line resistance across the bus termination (expect ≈60 Ω). If open or incorrect, trace and repair terminations.
Use an oscilloscope or CAN diagnostic tool at the cluster connector to verify CAN_H/CAN_L signal shapes, amplitude and presence of periodic messages.
If bus errors or a noisy frame source is present, systematically disconnect modules (starting with recently repaired/added modules or known-failure modules) to identify the offending node.
If wiring and bus are good but messages to the cluster are still missing, consider replacing or reprogramming the instrument cluster per OEM procedures.
After repairs, clear codes and perform road test and re-scan to confirm the issue is resolved and no new related codes set.

Likely causes

Intermittent/open wiring or connector to the instrument cluster
Failed instrument cluster (internal communication fault)
CAN bus short or excessive noise from another module
Poor battery/ground causing communication timeouts

Fault status

⚠️ Status

CAN timeout detected by instrument cluster — expected CAN messages not received within timeout period. Check CAN bus wiring, terminations, power/ground and cluster communication.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 1.0-3.0 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