EB2 PureTech 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: Stellantis Europe 48 V Hybrid evidence · Current hybrid references · Peugeot 208/3008/5008 and Corsa hybrid examples · 1.2 L PureTech/EB2 family boundary · e-DCS6
VERIFIED FACTModel / system fact
Stellantis 48 V hybrid applications pair a 1.2 L gasoline engine with the electrified e-DCS6 dual-clutch transmission.
FAULT SEPARATIONWhen a symptom appears
For under/overboost DTCs branch leakage, wastegate/VGT command, sensor feedback and exhaust backpressure separately.
FIRST MEASUREMENTBefore replacing parts
Preserve RPM, load, boost/MAP/MAF, lambda/fuel trim, rail pressure and misfire data in one freeze-frame package.
EB2 PureTech; petrol_turbo; 3 cylinder/layout; 1199 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.
ENGINE DIAGNOSTIC FLOW
Measurement sequence
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
The relationships below come only from existing curated relation records; they are not exact vehicle/model fitment claims.
Split the engine family into air/boost, fuel-pressure/injection, ignition/combustion, exhaust/aftertreatment and ECU torque-control layers.
At the same load point capture boost target/actual, MAP/MAF, lambda/fuel trims, rail pressure and misfire/combustion indicators.
Where variable valve timing or cylinder management is used, correlate commanded/actual angle or state with oil temperature/pressure and engine load.
DTC / SPN-FMI / symptom discrimination map
For under/overboost DTCs branch leakage, wastegate/VGT command, sensor feedback and exhaust backpressure separately.
For lean/rich or misfire complaints compare fuel delivery, injector, ignition and airflow evidence at the same load point.
For VVT/valvetrain DTCs evaluate electrical command-actual angle difference together with oil/thermal condition.
Measurement and diagnostic strategy
Preserve RPM, load, boost/MAP/MAF, lambda/fuel trim, rail pressure and misfire data in one freeze-frame package.
Where needed cross-check boost or fuel-pressure PIDs with an independent pressure/flow test allowed by the service procedure; do not invent target values.
After repair repeat target-actual deviation and misfire/combustion capture at the same speed-load-temperature point.
Exact pinouts, torque values, pressure thresholds or service limits are published only when explicitly verified by the applicable OEM service source.
On turbo-petrol architecture, load calculation, boost target/actual, lambda/fuel trim, ignition and knock control are compared in the same event window.
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: calculated load, MAP/boost target-actual, throttle angle, lambda/O2, STFT/LTFT, ignition advance and knock retard.
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
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.