Home / DTC / U1108 — No communication with the engine management ECU fault: No signal

U1108 — No communication with the engine management ECU fault: No signal

Detailed page for trouble code U1108.

32,741codes
59brands
10,284generic
22,457specific
Reset
Code

U1108

DS U — Network/User

No communication with the engine management ECU fault: No signal

Brand: DS
Views: UK: 4 EN: 6 RU: 6
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Blown fuse or interrupted +12V supply to engine ECU
  • Poor or missing ground at engine ECU
  • Damaged, corroded or disconnected ECU connector pins
  • Open, shorted or short-to-voltage/ground on vehicle network wiring (CAN H/L or LIN)
  • Failed engine management ECU (internal fault)
  • Other control module driving/bus-dominating the network

Symptoms

  • Malfunction Indicator Lamp (MIL) or warning lights illuminated
  • Reduced engine functionality or limp-home mode (may not start in some cases)
  • Engine data (RPM, coolant temp, fuel trim) not available on scan tool
  • Cruise control, traction control or stability systems may be disabled
  • Intermittent or permanent loss of remote diagnostics/telemetry

What to check

  • Read all stored DTCs and freeze frame data from all modules (scan tool capable of manufacturer networks)
  • Verify battery voltage is stable >12.5V with ignition on and during cranking
  • Inspect fuses and fusible links related to engine ECU power and ignition circuits
  • Visually inspect engine ECU connector for corrosion, pushed-out pins, water ingress or damage
  • Attempt communication to engine ECU with scan tool; note timeout or BUS OFF messages
  • Check for other network DTCs (U0xxx, U1xxx, U0073, etc.) that indicate broader bus faults

Signal parameters

  • CAN idle voltages: both CAN_H and CAN_L near ~2.5V (recessive)
  • CAN dominant state: CAN_H ~3.5V and CAN_L ~1.5V during transmission
  • Differential voltage on CAN during messaging ~1.5–2.5V when active
  • Termination resistance across CAN H-L ≈ 60 ohms (two 120Ω in parallel)
  • Bus load/traffic (messages per second) and presence of engine-ECU-specific message IDs
  • Module supply voltage at ECU pins (battery voltage with key ON) and ground continuity

Diagnostic algorithm

  1. Confirm and record U1108 and any related DTCs from all modules; capture freeze-frame and network errors.
  2. Verify vehicle battery condition and charging system; ensure stable supply voltage during diagnostics.
  3. Check fuses and power feeds to the engine ECU; restore any missing power or replace blown fuses.
  4. Visually inspect and secure the engine ECU connector; look for corrosion, bent pins or water damage. Repair or reseal as required.
  5. Attempt to communicate with the engine ECU directly at the connector using an OEM-capable scan tool; note whether the ECU responds.
  6. Measure pin voltages at the ECU harness: supply and ground pins, CAN_H and CAN_L idle voltages; compare to expected values.
  7. Check CAN bus termination resistance across CAN_H and CAN_L; if out of range, isolate sections of the bus to find the fault.
  8. If CAN voltages are incorrect, inspect wiring for shorts to ground/voltage and continuity between modules and junctions; repair any damaged wiring/splices.
  9. Disconnect suspect modules (other than ECU) one at a time to determine if another device is causing bus domination or errors.
  10. If wiring and power/ground are good and ECU does not respond, consider ECU reprogramming/reflash per manufacturer procedure; if still no communication, replace the ECU following OEM pairing/coding steps.
  11. Clear DTCs and perform road/test or network verification to confirm restoration of communication.
  12. Note: follow manufacturer-specific service information and safety procedures for ECU replacement and programming.

Likely causes

  • Faulty or loose ECU connector/terminals
  • CAN bus wiring open, shorted, or poor splice within engine bay harness
  • Blown ECU power fuse or fusible link
  • Bad ground strap from engine/chassis to vehicle ground
  • Failed engine ECU hardware or firmware lock-up
  • Another module causing bus errors or preventing normal wake-up

Fault status

⚠️ Status
No communication with Engine Management ECU detected on vehicle network — no signal received.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0 - 3.0 hours
Your experience will help others
+100 karma for a short comment :)
Send to email