HomeTrouble CodesU0553

U0553 — Invalid Data Received From Lighting Control Module Rear B

Generic OBD-II · all makesNetwork / communication

U0553 is a network communication diagnostic trouble code indicating that a master module (typically the body control module or other gateway module) has received invalid or corrupted data from the Rear Lighting Control Module B over the vehicle's CAN bus communication network. The 'invalid data' designation means the message structure, timing, or content from that module failed the receiving module's validation checks, rather than the data being simply absent. This code is commonly seen on vehicles that use distributed lighting control architecture with multiple rear lighting modules.

Symptoms

What causes it — most likely first

1. Wiring or connector fault at Rear Lighting Control Module B

Corroded, loose, or damaged pins in the module's connector, or chafed/broken wiring between the module and the CAN bus, are the most common cause. Moisture intrusion at rear-mounted connectors is a frequent contributor.

2. Loss of power or ground to the module

A blown fuse, failed ground strap, or corroded power feed can cause the module to transmit erratic or invalid messages. Voltage drop testing at the module connector is the standard check.

3. Failing Rear Lighting Control Module B

The module itself can develop internal faults that produce out-of-specification CAN messages. This is less common than wiring issues but should be considered after the harness is verified.

4. CAN bus communication network problem

Excessive resistance, a short to ground or power on the CAN lines, or a faulty terminating resistor can corrupt data from any module on the segment, including the rear lighting module.

5. Software or calibration mismatch in the module

An outdated, corrupted, or incorrectly flashed calibration can cause a module to transmit messages that fail the receiver's validation. A reflash or reprogramming may resolve it.

6. The module that stored the code is at fault

In rare cases the receiving module (often the BCM) misinterprets a valid message as invalid. This is the least likely cause and should only be pursued after ruling out the module on the other end and the wiring.

How it's diagnosed

  1. Retrieve all stored DTCs from all modules with a capable scan tool and record which module set U0553, then identify related U-codes and B-codes.
  2. Visually inspect the Rear Lighting Control Module B connector and harness for corrosion, bent pins, water ingress, or physical damage; repair as needed.
  3. Perform voltage drop and power/ground tests at the module connector with the circuit loaded to verify supply voltage and ground integrity.
  4. Use an oscilloscope or CAN-capable scan tool to inspect the CAN High and CAN Low waveforms at the rear lighting module for proper voltage levels, termination, and signal integrity.
  5. Command the rear lighting functions on with the scan tool and monitor live data from the module to determine whether it is responding correctly or producing out-of-range values.
  6. If wiring, power, ground, and network integrity are confirmed good, attempt a software reflash of the Rear Lighting Control Module B; replace the module only as a last step.

Code facts & related codes

SystemNetwork / communication
StandardizationSAE generic — identical on every make

Frequently asked

Is it safe to keep driving with code U0553?

In most cases the vehicle remains drivable, but rear lighting functions may be unreliable, which can be a safety concern. Address it promptly, especially if rear lights, brake lights, or turn signals are affected.

Does U0553 mean I need to replace the body control module or PCM?

No. The code specifically points to data coming from the Rear Lighting Control Module B being invalid, which almost always traces to wiring, power/ground, network issues, or the rear lighting module itself. Replacing the BCM or PCM is an expensive step that is almost never the correct fix for this code.

Can I just clear the code and see if it returns?

Clearing the code is a reasonable first step to confirm whether the fault is intermittent or hard-fault. If it returns quickly, the underlying condition is still present and requires diagnosis; clearing it does not fix the root cause.

Why are other U-codes often stored along with U0553?

When a CAN network has a wiring or termination fault, multiple modules on the same bus segment can simultaneously set communication codes. Treating U0553 as the only code and ignoring others can lead to missed root-cause issues on the shared network.