Create your free account and get 10 bonus questions when you confirm your email. No card needed. Create free account

Try it free

U0155: Loss of Communication with Instrument Panel Cluster (IPC) Control Module

Severity: high

Updated: 15 Nov 2026 · Generic OBD-II code (SAE J2012 / ISO 15031-6). Written with AI and reviewed; translated automatically from the Spanish original.

What it means

This code indicates that a module that expects data from the instrument panel cluster (IPC), usually the engine ECU or another module on the network, is not receiving a response from the IPC through the vehicle's communication network. The module monitors the messages it exchanges over the CAN bus and records the fault when the cluster stops responding for a set period of time. That is why the fault can appear even when the cluster is switched on, because what has been interrupted is the dialogue between modules. As this is a loss of communication, the most common causes are usually in the power supply, the earth, the wiring or the connectors, but an internal fault in the cluster or a module that blocks the network can also be responsible. Which module records the code and with what timings depends on the manufacturer.

Can I keep driving?

Only as far as you need to, and gently.

This fault can cause serious damage or affect safety. Avoid motorways, heavy loads and high revs, and have it diagnosed as soon as possible. If the engine shakes, loses power or a red light comes on, stop where it is safe.

If in doubt, put safety first: a red or flashing warning light, smoke, a burning smell or any change in the brakes or steering are reasons to stop.

Got U0155? Ask about your car

Tell us your car and what you notice: we answer right here, no account needed.

Symptoms

  • Instrument cluster switched off, blank or with sections not illuminated.
  • Warning lights that do not come on or stay permanently lit, such as the engine fault, ABS or airbag lights.
  • Brake, oil pressure, temperature or charging warnings that do not appear on the cluster. Without them, the driver may not notice a serious problem.
  • Speedometer, rev counter or fuel gauge with no reading or with inconsistent values.
  • Error messages on the central screen or the cluster relating to other systems.
  • Intermittent faults that come and go depending on temperature, vibration or the condition of the battery.
  • Other systems that depend on the network, such as the climate control or the radio, may behave erratically.
  • If the cluster does not show speed or warnings, drive with caution. If in any doubt about brakes, steering or airbag, do not drive the vehicle and take it to a garage.

Common causes

  • Faulty power supply or earth to the instrument cluster, with cuts or voltage drops.
  • Weak battery or poor battery connection, which causes low voltages on the network.
  • Damaged, corroded or loose cluster connector or wiring.
  • Internal fault in the instrument cluster module itself.
  • Problem in the communication network, such as a CAN bus cable that is cut, short-circuited or poorly terminated.
  • Another module on the network that is blocking or overloading the bus.
  • Fuse related to the cluster blown, although this usually comes with other symptoms.
  • Network architecture and the number of modules vary widely between makes and models, so the most likely cause depends on the manufacturer.

What to check

  • Check the battery: resting voltage and voltage with the engine running, and the condition of the terminals.
  • Check the power supply fuses for the cluster and the ECU.
  • Visually inspect the cluster connector and the accessible cables, looking for corrosion, moisture or damage.
  • Read all modules on the network with a scanner to see which ones respond and which do not.
  • Consult the workshop manual for the CAN network diagram and the bus resistance measurement points, as the values depend on the vehicle.
  • Measure the cluster's power supply and earth directly at the connector with a multimeter, taking care not to cause short circuits. On hybrid or electric vehicles do not handle high-voltage cables (normally orange): that part is for a trained professional.
  • Do not work on the wiring near the airbag or the seatbelt pretensioners without specific training, as a mistake can deploy or disable them.
  • If the network is suspected, check the continuity and insulation of the bus cables and measure the terminating resistance.
  • As a last step, replace or reprogram the cluster only if the other checks rule out other causes, and do so with the manufacturer's tools.

Frequently asked questions

Can a low battery cause this fault even if the cluster is in good condition?

Yes, it can. When the battery voltage drops below the minimum working level of the network (roughly ≈10 V; the exact value depends on the vehicle), modules can intermittently stop communicating and record faults like this one. It is worth measuring the battery and the charging system before replacing any module. If the code clears after charging or replacing the battery, that is a strong hint that the power supply was the cause, though you should still clear the codes and check that it does not return.

Can I just clear it? Clearing the code does not fix the fault: if the cause is still there, it comes back, and with the engine warning light on the car will fail its roadworthiness test (MOT in the UK).

General information about a generic code. The exact causes depend on the make and engine: confirm them with a diagnosis before replacing parts.

More codes: network and communication

All OBD codes in English