Skip to main content
OBD-II Diagnostic Trouble Code
U0155

Lost communication with instrument panel cluster (IPC) control module

U
Network
modules / CAN bus
0
Generic
SAE standard
1
Network subsystem
55
Lost communication with instrument panel cluster (IPC) control module
Severity · general guide
High
Losing the speedometer, fuel gauge and warning lights removes critical information, and where the cluster ties into security the car may not start.
Code type
Generic
System
Network
Standard
ISO/SAE Controlled
Fault type
Communication Loss
Quick answer

Not recommended — driving without a working speedometer or warning lights is unsafe and often illegal, and if it causes stalling or a no-start the car isn't reliably driveable. Diagnose before relying on it. U0155 means a module (often the engine or body computer) has stopped receiving data from the instrument panel cluster — the dashboard module that runs the speedometer, tachometer, gauges and warning lights — over the vehicle's communication network. Common causes are a blown fuse or bad ground at the cluster, low battery voltage, or damaged network wiring. Because you can lose the speedometer and warning lights (and some cars won't start), it should be diagnosed before relying on the vehicle.

What U0155 means

Modern vehicles link their modules over a CAN data bus. U0155 sets when a module stops receiving the periodic messages it expects from the instrument panel cluster — in other words the cluster has gone silent on the network, whether from lost power or ground, broken bus wiring, or an internal cluster failure. It is a network fault, not a mechanical one.

Symptoms

  • Check-engine light and/or several warning lights on
  • A dead, frozen or erratic instrument cluster — gauges at zero, pegged or flickering
  • Speedometer, tachometer or fuel and temperature gauges not reading
  • Warning lamps illuminated or behaving oddly
  • Intermittent stalling, or in some vehicles a no-start
  • Other network (U) codes stored alongside it if the bus fault affects several modules

Common causes

  • A blown fuse or a power/ground fault feeding the cluster
  • Low battery or charging voltage — modules drop offline during cranking and log comms codes
  • Damaged network (CAN) wiring to the cluster — chafed, broken, shorted or corroded
  • A faulty connector at the cluster (corrosion, water, a backed-out pin)
  • An internal cluster or transceiver failure
  • Aftermarket devices — OBD dongles, alarms or add-ons loading or disrupting the bus
  • Less common: a gateway module fault, a bus-termination problem, or a bad splice

Severity & driving advice

Severity: High — Losing the speedometer, fuel gauge and warning lights removes critical information, and where the cluster ties into security the car may not start.

Can I drive? Not recommended — driving without a working speedometer or warning lights is unsafe and often illegal, and if it causes stalling or a no-start the car isn't reliably driveable. Diagnose before relying on it.

Diagnostic approach

  1. Scan all modules and note the patternPull codes from every module. U0155 alone points at the cluster's power, ground or wiring; U0155 plus many other U-codes points to a shared bus or gateway fault.
  2. Check battery and charging firstConfirm battery voltage and charging output are healthy — low voltage makes modules drop offline and set false comms codes, so fix this before deeper diagnosis.
  3. Verify cluster power and groundConfirm the cluster's fuses are good and that it has both power and a clean ground; a blown fuse or bad ground makes the cluster go silent.
  4. Inspect the connector and wiringLook at the cluster connector and network wiring for corrosion, water, chafing or damage, and wiggle-test to catch intermittents.
  5. Measure the CAN busCheck CAN-High and CAN-Low continuity and resistance (about 60 ohms across the two lines on a healthy bus) to find opens, shorts or termination problems between the gateway and the cluster.
  6. Rule out add-on devicesRemove any aftermarket OBD dongle, alarm or accessory and recheck — these commonly load or corrupt the bus and trigger U-codes.
  7. Isolate the clusterIf power, ground and wiring are good and the bus reads correctly, the cluster itself is likely failed; confirm before replacing, since clusters often need programming.

FAQ

Is my whole cluster dead — do I need a new one?

Not necessarily. Most U0155 cases are a blown fuse, bad ground, low battery or damaged wiring; replace the cluster only after power, ground and the network check out good.

Could a cheap OBD dongle cause this?

Yes. Aftermarket dongles and add-on electronics are a well-known cause of bus-communication codes; unplug them and retest first.

Why won't my car start with this code?

In vehicles where the cluster takes part in the network security handshake, losing cluster communication can block starting; restoring the connection usually restores starting.

Can a weak battery really set a network code?

Yes. When cranking voltage sags, modules briefly power down and drop off the bus, logging codes like U0155; charge or replace the battery and clear the code before chasing wiring.