Volkswagen EA288 TDI: engine code, thermal management, EGR, DPF and SCR file

Lock down the exact variant

A marketing name is not a service identity.

• Record engine code, ECU hardware/software, production date, emissions package and platform.
• Do not collapse EA189 and EA288 into the same '2.0 TDI' service identity; EGR, thermal, sensor and part architectures differ.
• Confirm SCR/AdBlue, NOx sensors, dual-EGR or turbo configuration by market and emissions level.
• Include transmission code and drivetrain layout in torque-management and test context.

Read the system through measured channels

Use a related data chain, not one screen.

• Evaluate desired/actual rail pressure, metering control, injector corrections and return flow together.
• Log desired/actual boost, VNT position, MAF, EGR commanded/actual and exhaust pressure under matched load.
• DPF calculated soot, ash loading, differential pressure, exhaust temperatures and regeneration history are separate variables.
• Observe coolant circuits, thermostat/pump command and EGR-cooler behaviour for slow warm-up and thermal complaints.

Separate similar symptoms by root cause

Expensive replacement follows evidence.

• Before turbo replacement for low power, separate exhaust restriction, EGR flow, rail pressure and ECU torque limitation.
• For frequent regeneration, sequence injectors, thermostat, short-trip use, differential-pressure sensing and ash loading.
• For NOx/SCR faults, validate sensors, urea quality/dosing, temperature window and exhaust leaks.
• For cold-start smoke, compare glow system, compression, injector leakage, synchronization and fuel drain-back.

Validate the repair reproducibly

Code clearing or a short drive is not enough.

• Compare rail, boost, EGR and DPF data on the same route/load after repair.
• Use adaptations or service regeneration only when mechanical and safety preconditions are met.
• Record warm-up and thermal-circuit behaviour from cold start to full temperature.
• Validate several use cycles without pending powertrain/emissions codes, abnormal regeneration or oil-dilution signs.

How to read this engine family

Diagnosis starts from physical architecture and control chain, not the commercial label.

• Direct injection, boost control, lambda feedback and knock control are parts of one torque model.
• Timing drive, PCV and intake leaks can all create trim, idle and misfire symptoms.

Channels to view on the same timeline

Compare commanded and actual values at the same speed, load and temperature.

• Short/long fuel trims, lambda target/actual, low/high-side fuel pressure
• Boost target/actual, wastegate command, throttle angle and torque request
• Per-cylinder misfire counts, ignition retard, intake-air and coolant temperature

What to eliminate before replacing parts

Do not replace parts before separating mechanical, electrical and control causes.

• Before coils/plugs, separate cylinder-swap evidence, compression/leakage, injector and intake-valve deposits.
• For oil consumption, separate leaks, PCV, turbo sealing, rings and valve seals.

Five steps from first inspection to validation

• Define the complaint precisely: cold/hot, idle/load, speed, fuel level and ambient temperature.
• Before clearing, capture freeze frame, pending/permanent status and companion codes in all modules.
• Verify engine identity from VIN, marking and ECU calibration identity.
• After base mechanical, supply/ground and leak checks, move to commanded/actual live data.
• Reproduce the same operating condition after repair; a cleared code alone is not success.