EA288 evo family fuel architecture, cylinder layout, displacement class, application scope and measurement-led diagnostic framework.
QUICK TECHNICAL ANSWERS
What concrete information can you get from this page?
Verified application example: OEM published applications · Source-defined · Engine family / cited applications · Volkswagen Group EA288 evo / 2.0 TDI · Vehicle-specific; resolve by VIN/serial
VERIFIED FACTModel / system fact
Volkswagen official information identifies Volkswagen Group EA288 evo / 2.0 TDI as a turbocharged direct-injection diesel engine family whose current cited applications use TDI evo/evo2 emissions systems.
FAULT SEPARATIONWhen a symptom appears
Preserve freeze-frame, companion DTCs and supply voltage before clearing faults; the first-event context is more useful than a later isolated code.
FIRST MEASUREMENTBefore replacing parts
Preserve RPM/load, supply voltage, relevant temperatures, commanded/actual values and companion DTCs in one freeze-frame/live-data package.
EA288 evo; diesel_turbo_mhev; 4 cylinder/layout; 2000 cc class
What to verify before ordering parts
Do not treat the family name and sub-code as identical; separate production period and market variant.
Emissions level, turbo/injection hardware and sensor/actuator generation can vary inside one family.
Transmission, hybrid system, ECU software and vehicle class can change the service procedure.
Diagnostic approach
Narrow faults by combining mechanical condition, air/fuel flow, pressure, temperature, lubrication, electrical supply and ECU commands rather than using the DTC label alone. Comparing loaded live data with idle measurements is particularly valuable for intermittent and performance faults.
Diesel / heavy-duty chain
Treat common-rail pressure, low-pressure supply, turbo air path, EGR, DPF/SCR and engine protection/derate behaviour as one interacting chain. Aftertreatment faults can affect torque request and field performance.
Confirm exact engine code and application by VIN/model year/market.
Check power supply and ECU communication.
Capture air, fuel/energy, temperature and lubrication data at the same load.
Compare commanded values with physical result.
Verify under the same load after repair.
Source-verified powertrain relationships
No curated engine-transmission relationship is present in the source graph for this family yet. Exact fitment is not inferred.
OEM EVIDENCE DOSSIER
Verified technical facts and application boundary
Volkswagen official information identifies Volkswagen Group EA288 evo / 2.0 TDI as a turbocharged direct-injection diesel engine family whose current cited applications use TDI evo/evo2 emissions systems.[S1]
The cited OEM material places the family in common-rail diesel, turbo/air handling and SCR/aftertreatment architecture in cited current Volkswagen applications; application-specific hardware and calibration must be resolved by engine/vehicle identification.[S1]
Volkswagen erWin is the authoritative path for serial/VIN-specific service limits, wiring, diagnostic procedures and calibration information; catalogue figures are not used as test thresholds.[S2]
Verified application matches
The matches below are published only within the stated market, model-year and evidence scope. Fitment is not extrapolated to uncited variants.
Market: OEM published applications
Model year: Source-defined
Model: Engine family / cited applications
Engine: Volkswagen Group EA288 evo / 2.0 TDI
Transmission: Vehicle-specific; resolve by VIN/serial
Evidence scope: Manufacturer engine/product + service information
System architecture and component relationships
Separate Volkswagen Group EA288 evo / 2.0 TDI diagnosis into engine/ECM, transmission/TCM, ABS/ESC/ADAS and network/power-supply domains before replacing parts.
Correlate commanded versus actual load/torque/boost or mixture data with system voltage, temperatures and companion DTCs at the same operating point.
Where the application includes turbocharging, emissions controls or AWD, treat air/fuel, aftertreatment and driveline control as distinct branches with their own live-data evidence.
DTC / SPN-FMI / symptom discrimination map
Preserve freeze-frame, companion DTCs and supply voltage before clearing faults; the first-event context is more useful than a later isolated code.
For low power or poor response compare commanded versus actual torque/load/air-fuel values at the same RPM and temperature before choosing a component branch.
Separate sensor plausibility, wiring/reference supply, actuator response and mechanical condition so a DTC does not become a parts-replacement instruction.
Measurement and diagnostic strategy
Preserve RPM/load, supply voltage, relevant temperatures, commanded/actual values and companion DTCs in one freeze-frame/live-data package.
Cross-check scan-data plausibility with independent electrical or mechanical measurement only at OEM-approved points and with the correct service procedure; no uncited exact threshold is assumed.
After repair, repeat the same operating condition and compare the original symptom, command-versus-actual deviation and DTC status together.
Exact pinouts, torque values, pressure thresholds or service limits are published only when explicitly verified by the applicable OEM service source.
Fuel path is separated into low-side supply → high-pressure pump → rail → injectors; air path into MAF/MAP → turbo control → intake manifold.
On turbo-petrol architecture, load calculation, boost target/actual, lambda/fuel trim, ignition and knock control are compared in the same event window.
ICE, 12 V, HV/48 V, DC-DC, motor-generator and thermal management are separate control layers; energy flow is aligned with the fault event.
In an EV, HV battery/BMS, contactor-HVIL/isolation, inverter-motor, OBC/DC-DC, 12 V and cooling circuits are separate evidence branches.
Live data to capture for this family
Freeze frame: first/last fault time, RPM, load, vehicle speed, system voltage, core temperatures and companion DTCs.
Live data: rail target/actual, low-side supply where supported, MAF/MAP, boost target/actual, EGR command/feedback.
Live data: calculated load, MAP/boost target-actual, throttle angle, lambda/O2, STFT/LTFT, ignition advance and knock retard.
Electrified layer: SOC/SOH where available, cell delta, pack temperatures, HVIL/isolation, contactor permission, DC-DC output and 12 V voltage.
Engine measurement chain
1) Match vehicle/generation/market/powertrain/driveline identity to the source record; family name alone is not fitment evidence.
2) Preserve freeze frame and companion DTCs before clearing; make the first-fault condition reproducible.
3) Verify power/ground and network communication under load; do not decide from key-on static measurement alone.
4) Compare commanded air/fuel/pressure with an independent physical result; separate sensor bias from real performance loss.
6) After repair, recreate the same load/temperature and verify DTC state, live-data deviation and user symptom together.
This section is an architecture-safe diagnostic layer derived from family identity; application-specific OEM limits are shown only when a verified evidence dossier exists.
Engine root-cause split
If rail pressure is low, separate low-side supply from high-pressure generation: when physical low-side supply is healthy but rail cannot follow target, regulation/pump/injector-leakage branches gain weight.
For low boost, do not jump to turbo replacement: separate MAF/MAP plausibility, charge leak, VGT/wastegate command and exhaust backpressure at the same load point.
On lean/misfire/boost complaints, align fuel trim, lambda, ignition retard and boost deviation on one time base to separate air leak, fuel-delivery and ignition causes.
For READY/charging faults, separate 12 V supply from the HV permission chain first; low 12 V can mimic contactor/HVIL/isolation faults.
For battery performance, use cell delta, temperature spread and voltage deviation under load/charge instead of one SoH percentage alone.