Mercedes-Benz OM651: injection, timing, turbo and emissions file

Map sub-code, turbo and emissions package

OM651 does not mean one hardware set.

• Record full engine code, ECU, injector parts/codes, production date and vehicle application.
• Identify single/twin turbo, DPF, SCR/AdBlue, EGR cooler and fuel-system revision.
• Separate manual/automatic, commercial/passenger and market emissions level.
• Check VIN campaigns, software and previous injector/timing/turbo work.

Observe cranking, rail, air and exhaust in one event

Smoke and limp can involve several systems.

• Compare cranking speed, rail desired/actual, injector corrections and return flow cold and hot.
• Log boost desired/actual, actuator, MAF, EGR command/actual and intake leakage under load.
• Read DPF pressure, exhaust temperatures, soot/ash and regeneration history with oil level.
• Where SCR is fitted, log NOx sensors, DEF dosing/quality and inducement state.

Separate fuel, timing and emissions roots

Injector or turbo replacement needs evidence.

• For hard start sequence battery/cranking, rail build, return flow, compression and glow.
• For timing suspicion combine CKP/CMP correlation, adaptation, oil condition and mechanical verification.
• For low boost separate leaks, actuator, turbo staging, EGR/MAF and DPF backpressure.
• For frequent regeneration resolve thermostat, duty cycle, injector imbalance and sensor offset before blaming DPF.

Complete coding, adaptation and load testing

Check interacting systems after repair.

• Apply correct injector/ECU coding, learning and sealing procedures.
• After turbo/timing work document oil circuit, timing and foreign-object risk.
• Compare cold start, hot load, rail/boost and emissions data with pre-repair logs.
• Confirm XENTRY quick test, pending codes, DPF/SCR counters and VIN campaigns.

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.