U0D95

Lost Communication with Exhaust Aftertreatment Control Module

U0D95 is a generic OBD-II network diagnostic trouble code: Lost Communication with Exhaust Aftertreatment Control Module. It is logged by the engine control unit when the network monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

Code
U0D95
Group
Network
System
Network
Severity
Warning (MIL on, possible limp mode)
Need U0D95 disabled?
RaceTune permanently disables any OBD-II trouble code on supported ECUs — for motorsport, off-road, and export use.
→

What U0D95 means

U0D95 indicates that the primary control module (typically the engine or powertrain control module) has lost communication with the Exhaust Aftertreatment Control Module (EACM) over the vehicle's communication bus, usually CAN. Modern diesel vehicles with complex SCR and DPF aftertreatment systems often use a dedicated control module to manage aftertreatment functions, and the PCM relies on receiving status messages from this module to coordinate DEF dosing, regeneration, and emission monitoring.

Loss of communication can be caused by a failure of the EACM itself, a fault in the CAN bus wiring (open, short to ground, or short to voltage), a blown fuse powering the module, or a poor ground connection. The PCM detects the fault when it does not receive expected messages from the EACM within the defined timeout window. A single module going offline can produce U-code faults on multiple other modules simultaneously, so identifying whether the EACM itself or the bus is at fault is a critical first diagnostic step.

With no aftertreatment control, SCR dosing, DPF regeneration commands, and NOx monitoring are all suspended. Depending on the vehicle, this may trigger an immediate power reduction or a countdown to derate, as the emission system is effectively non-functional. Prompt diagnosis is essential to restore both emission compliance and full vehicle performance.

Common causes

Most-frequently reported root causes when U0D95 is logged.

  • 1
    Failed Exhaust Aftertreatment Control Module with no bus communication output.
  • 2
    Open or shorted CAN bus wiring between the EACM and the main communication network.
  • 3
    Blown fuse or failed power supply relay for the EACM.
  • 4
    Poor or open ground connection at the EACM module chassis ground point.
  • 5
    CAN bus termination resistor fault degrading overall network signal quality.
  • 6
    Damaged wiring harness connector at the EACM module plug.
  • 7
    Software fault in the EACM requiring a module reset or reprogramming.

Symptoms drivers notice

MIL illuminated along with possible additional network U-codes from other modules.
SCR system non-operational; DEF dosing and NOx monitoring suspended.
DPF regeneration commands may be absent if the EACM manages regen triggers.
Potential torque derate or power reduction if the vehicle enforces SCR availability.
Instrument cluster aftertreatment or DEF warning messages displayed.

How to diagnose U0D95

A typical diagnostic flow when this code is present.

  1. 1
    Read all DTCs from all modules to identify the full scope of communication faults and isolate whether the EACM is the only silent node.
  2. 2
    Check fuses and power supply circuits to the EACM with a multimeter.
  3. 3
    Verify EACM ground circuit integrity at the module connector and chassis ground point.
  4. 4
    Inspect the EACM harness connector for corrosion, bent pins, or loose engagement.
  5. 5
    Measure CAN bus differential voltage at the EACM connector to verify bus signal is present.
  6. 6
    Check CAN bus termination resistance (should be approximately 60 ohms across the network when both terminators are intact).
  7. 7
    If bus and power are confirmed good, attempt a module reset or consult OEM reprogramming procedures for the EACM.

Related network codes

Frequently asked questions

Could a dead battery cause U0D95?

A severely discharged battery or a voltage drop event can cause temporary module communication loss. If U0D95 appears only after a battery event and does not return, check battery and charging system health.

Do I need a dealer to diagnose U0D95?

Not necessarily, but accessing the EACM's own stored DTCs and performing module-level resets may require an enhanced scan tool with network access beyond basic OBD-II.

Can U0D95 appear alongside other U-codes?

Yes. If the EACM is offline, any module that expects messages from it will set its own lost-communication code. Resolving U0D95 at the source typically clears the related U-codes.

Is the EACM separate from the PCM on all diesels?

Not on all vehicles. Some integrate aftertreatment control into the main PCM. U0D95 applies specifically to platforms with a dedicated EACM communicating over the vehicle network.

Disabling U0D95 in software

RaceTune can permanently disable U0D95 — and any other OBD-II diagnostic trouble code — on every ECU family we support. The monitor is disabled inside the ECU itself, so the fault stops being logged: the warning light stays off and the engine never enters limp mode for this code. The change is tied to your exact software version.

Permanent
The monitor is disabled in the ECU itself — not just cleared. It cannot return.
Tailored to your file
Each patch is matched to your specific software version — never a one-size-fits-all file.
Reversible
The original file is always preserved. Reflash the stock to return the ECU to factory state.

Software modifications affect emissions compliance and are not road-legal in many jurisdictions. RaceTune service files are intended for motorsport, off-road, and export use.

Got U0D95 in your scan?

Upload your ECU file — we'll identify the exact software version and confirm whether a disable is available for your car.

Upload your file