Pin16

U0400

Invalid Data Received

Severity
High
Driving
Drive only to a garage

A module is receiving data over the vehicle's data bus that it can tell is wrong, without naming which module sent it. The message is arriving intact but the values in it fail a plausibility check - out of range, a bad checksum, or a counter that stopped advancing. Because the source is not named, this code is a starting point rather than an answer: the module that is actually at fault will usually have stored its own code saying so.

Possible causes

What you might notice

What to check, in order

  1. Read the codes from every module on the vehicle. This code does not name the sender, so the module that does name a fault is where to start - and there is almost always one.
  2. Check battery voltage and the earth points. An unstable supply is the most common reason several modules start producing values that fail plausibility checks.
  3. Find out what was worked on recently. This code appearing after a repair, a battery change or a module replacement usually points straight back at that work.
  4. Look for aftermarket wiring spliced into the bus - alarms, trackers, dash cameras, tow bar electrics. A badly-made splice corrupts messages without breaking the network.

Read this code from your own car

Plug an ELM327 adapter into the OBD-II port under the dashboard. Pin16 reads every stored, pending and permanent code, explains each one like this page does — offline, with no account — and shows what the car recorded when the fault was set.

Get Pin16 on Google Play

Where this code sits