Engine

Mercedes-Benz OM654: variant, live-data and failure-chain file

Combines exact Mercedes-Benz OM654 identity, air-fuel management, failure mechanisms and repair verification in one open-access file.

Technical reference8 sourcesUpdated 2026-07-31
Mercedes-Benz
Mercedes-BenzManufacturer identity

Vehicle Identity and Application Matching

TECHNICAL IDENTITY

Engine family architecture

Manufacturer groupMercedes-Benz
Engine familyOM654
Fuel architectureTurbo diesel
Cylinder layout4
Displacement class1597-1950 cm³
Vehicle scopepassenger / van

Registered technical variants in this family

OM654OM654M
MEASUREMENT-BASED DIAGNOSTICS

Technical flow from measurement to verification

  1. Capture freeze-frame/event data, first/last occurrence conditions and system voltage.
  2. Verify power, ground, fuses, connectors and shared reference circuits before replacing parts.
  3. Compare commanded values with actual sensor or actuator feedback under the same operating conditions.
  4. Separate electrical causes from mechanical, hydraulic, pneumatic or flow-related causes with independent measurements.
  5. Recreate the monitor or operating condition after repair and confirm that the fault does not return.

Engine-family technical identity; exact application-specific specifications require VIN/engine-code confirmation.

ENGINE FAMILY

Mercedes-Benz OM654: variant, live-data and failure-chain file

ENGINE IDENTITY

Confirm the Mercedes-Benz OM654 sub-code and vehicle application

The family name is not exact service data.

  • Mercedes-Benz OM654 identity boundary: OM654 subcode, longitudinal/transverse application, output and emissions hardware separated.
  • Architecture: aluminium modular diesel, common rail, variable turbo and generation-dependent 48-V/aftertreatment integration.
  • For Mercedes-Benz OM654, record engine code, ECU software, production date and emissions package together.
  • For Mercedes-Benz OM654, where market differences exist, select parts and bulletins only by VIN.
LIVE DATA

Log the Mercedes-Benz OM654 torque and air-fuel model

Use synchronized logs rather than one PID.

  • Fuel management: rail, injector correction, quantity valve and low-pressure feed.
  • Air/boost management: air mass, boost, HP/LP EGR path, swirl and charge-air cooling.
  • Measurement set: rail, smooth running, boost, EGR, DPF, NOx/SCR, exhaust temperature and thermal management.
  • For Mercedes-Benz OM654, store cold-start, hot-idle and controlled-load logs separately.
FAILURE CHAIN

Separate Mercedes-Benz OM654 symptoms by system

A reputation is not a parts diagnosis.

  • Priority risks: injector circuit/leakage, EGR/DPF/SCR, cooling, oil pressure, turbo and software/campaign state.
  • Differential check: separate aftertreatment faults from fuel, thermostat/EGR, exhaust leakage and NOx sensors.
  • For Mercedes-Benz OM654, lubrication, cooling, fuel, air and aftertreatment can create the same symptom and must be proven separately.
  • For Mercedes-Benz OM654, for modified software/hardware, re-establish the correct targets and compatibility.
REPAIR VERIFICATION

Close the Mercedes-Benz OM654 repair with measurements

Clearing codes is not a delivery criterion.

  • Verification: rail/boost under load, regeneration, NOx conversion, fluid leakage and hot restart.
  • For Mercedes-Benz OM654, compare pre/post-repair live data under the same environment and load.
  • For Mercedes-Benz OM654, add leakage, pressure, adaptation and readiness results to the service record.
  • For Mercedes-Benz OM654, plan a first heat-cycle and follow-up inspection for critical joints and fluid levels.
FIELD WORKFLOW

Evidence-preserving diagnostic sequence

  1. Record Mercedes-Benz OM654 engine code, production, market and ECU identity.
  2. Collect maintenance history, modifications and all current codes.
  3. Log rail, smooth running, boost, EGR, DPF, NOx/SCR, exhaust temperature and thermal management cold, at idle and under load.
  4. Use separate aftertreatment faults from fuel, thermostat/EGR, exhaust leakage and NOx sensors to separate electrical and mechanical causes.
  5. Repair with the variant-correct OEM procedure and part number.
  6. Confirm rail/boost under load, regeneration, NOx conversion, fluid leakage and hot restart during the follow-up drive.
DIFFERENTIAL DECISION MATRIX

Connect the symptom to evidence, not a guessed part

EvidenceObservation / conditionCorrect next action
IdentityOM654 subcode, longitudinal/transverse application, output and emissions hardware separatedConfirm exact engine code and software.
Data deviationrail, smooth running, boost, EGR, DPF, NOx/SCR, exhaust temperature and thermal managementCompare commanded/actual and physical measurement.
Failure chaininjector circuit/leakage, EGR/DPF/SCR, cooling, oil pressure, turbo and software/campaign stateSeparate the root cause with cross-system evidence.
TECHNICAL SOURCES

Primary and official sources

  1. Vehicle safety, recalls and manufacturer communications · NHTSA
  2. 40 CFR Part 86 – Vehicle emissions and OBD requirements · U.S. Government Publishing Office
  3. Bosch Mobility technical knowledge · Robert Bosch GmbH
  4. XENTRY workshop information · Mercedes-Benz AG

Exact capacity, torque, pressure and service interval must be verified by engine sub-code and OEM documentation.

Engine-family application research

This section connects a verified manufacturer relation to the model catalog; listed model families do not mean confirmed part/application fitment. Verify full code, build period, market and software identity.

Continue to workshop technical center → · Maintenance and ownership decisions →

Engine-family deep diagnostic matrix

An engine family is not an exact vehicle application by itself. Use this sequence after vehicle/model and engine-code identity have been verified.

Use manufacturer service information and verified vehicle identity for exact OEM procedures, values and part applications.

6-step technical decision tree

  • Verify identity
  • Preserve first-event data
  • Compare command and feedback
  • Confirm with physical measurement
  • Isolate root cause
  • Retest under the same condition after repair

Source-verified powertrain relationships

The relationships below come only from existing curated relation records; they are not exact vehicle/model fitment claims.

OEM EVIDENCE DOSSIER

Verified technical facts and application boundary

  1. Mercedes-Benz identifies OM 654 as the four-cylinder diesel member of a new engine family and describes it as its first all-aluminium four-cylinder diesel. [S1]
  2. The OM 654 manufacturer description lists steel pistons, stepped combustion bowls, NANOSLIDE cylinder coating and fourth-generation common-rail injection. [S1]
  3. The exhaust aftertreatment elements are packaged directly on the engine; Mercedes-Benz also describes multiway EGR combining cooled high- and low-pressure EGR. [S1]

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.

System architecture and component relationships

  • Diagnostic architecture separates low/high-pressure fuel, turbo/air path, high+low-pressure EGR and the engine-mounted DPF/SCR/NOx/EGT aftertreatment chain.
  • For EGR faults, correlate air mass, boost, HP/LP EGR commands and exhaust pressure/temperature behavior.
  • Because aftertreatment is close-coupled, sensor temperature ordering and dosing behavior should be time-correlated with the actual thermal event.

DTC / SPN-FMI / symptom discrimination map

  • For low power/rail faults, capture low-side supply, rail target/actual and injector corrections at the same load.
  • For EGR/boost faults, branch MAF, boost, EGR command and charge-air/exhaust leak or restriction tests separately.
  • For NOx/SCR faults, correlate EGT sequence, upstream/downstream NOx and dosing command rather than condemning the catalyst from one sensor code.

Measurement and diagnostic strategy

  • Capture cold-engine sensor rationality, then observe EGT/NOx/EGR behavior through a controlled warm-up.
  • Do not invent exact pressure thresholds without the applicable service procedure; use target-versus-actual deviation and independent supply verification.
  • After repair, recreate comparable temperature/load and verify derate, fault state and PID normalization together.

Exact pinouts, torque values, pressure thresholds or service limits are published only when explicitly verified by the applicable OEM service source.

Evidence provenance and primary sources

  1. Mercedes-Benz Group – The future of the diesel engine, OM 654 · OEM-primary · 2026-08-15
  2. Mercedes-Benz Group – Sustainability presentation: OM 654 · OEM-primary · 2026-08-15

Other names and search terms

OM654Mercedes-Benz OM654
RELATED TECHNICAL TOPICS

Topics in the same system and fault chain

Technical Sources and Verification

  1. Mercedes-Benz resmî kurumsal sitesi
  2. Wikidata structured data (CC0)
SERVICE DECISION LINKS

Connect this record to a real service decision

Ownership and cost links

Technical depth link

Read this record through operating principle, energy/network relationships, measurements and failure patterns, not the part name alone.

Explore technical mysteries →
TECHNICAL DOSSIER EXPANSION

What should be verified when deepening this record?

Within an engine family, sub-code, displacement, turbo, injection, emissions level and software generation can vary. Connect compression/leakage, lubrication, air path, fuel pressure, synchronization and aftertreatment data in one diagnostic chain.

Engine Atlas →

How to verify the technical identity

The same model name can carry different engines, transmissions, emissions packages and ECU software across years and markets. Verify VIN/chassis, engine code, production period and controller identity together before selecting parts or procedures. If an exact value is not supported, AutoAtlas does not fill the gap by guessing.

Engine families · Technical diagnostic atlas

Engine-family research coverage

Mercedes-Benz OM654: variant, live-data and failure-chain file engine code, family, application, common-problem, live-data, air/fuel, emissions and measurement intents are connected around the same engine identity.

Deep technical guides

Deep symptom diagnostics

Connect technical research to the next decision

Do not treat a family name as exact application; verify vehicle/model, code, market and controller identity before moving to maintenance or repair decisions.

Sources & freshness

Sources & freshness

Exact technical values, prices and failure rates are not invented without verified vehicle/manufacturer evidence.

Explore →