OtoDünyam
ENGINE FAMILY DOSSIER

Heavy Duty Global DAF PACCAR MX-13 Engine Family

DAF PACCAR MX-13 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: North America EPA current · PACCAR MX-13

VERIFIED FACTModel / system fact

PACCAR currently lists the EPA MX-13 at 405–510 hp and 1,550–1,850 lb-ft.

FAULT SEPARATIONWhen a symptom appears

For low rail pressure, compare commanded and actual rail pressure under load and independently verify low-side supply/filter restriction.

FIRST MEASUREMENTBefore replacing parts

Cross-check electronic rail-pressure PIDs with independent fuel-supply testing, then branch target-vs-actual deviation into sensor, control valve, pump, leakage or supply restriction.

Primary source: PACCAR EPA MX-13 official product page

Engine identity

Manufacturer group
Heavy Duty Global
Engine family
DAF PACCAR MX-13
Fuel / energy architecture
Turbo diesel
Cylinder layout
6
Displacement class
12900 cc
Vehicle scope
heavy truck

DAF PACCAR MX-13; diesel_turbo; 6 cylinder/layout; 12900 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.

J1939 SPN/FMI →

ENGINE DIAGNOSTIC FLOW

Measurement sequence

  1. Confirm exact engine code and application by VIN/model year/market.
  2. Check power supply and ECU communication.
  3. Capture air, fuel/energy, temperature and lubrication data at the same load.
  4. Compare commanded values with physical result.
  5. 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.

curated_relationDAF TraXon

DAF heavy truck

OEM EVIDENCE DOSSIER

Verified technical facts and application boundary

  1. PACCAR currently lists the EPA MX-13 at 405–510 hp and 1,550–1,850 lb-ft. [S2]
  2. PACCAR’s TX-12 page lists MX-13 among compatible engines. [S3]
  3. The MX-13 product page links directly to manufacturer oil specifications, maintenance intervals and service/diagnostic-tool resources. [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.

Market: North America EPA current

Engine: PACCAR MX-13

Evidence scope: current PACCAR product family

System architecture and component relationships

  • Separate low-pressure fuel supply from common-rail high-pressure control during diagnosis.
  • Air management correlates turbo/VGT, charge-air path, MAP/boost and EGR behavior.
  • Aftertreatment involves DPF/SCR/DEF/NOx/EGT elements; separate a sensor fault from a real exhaust-chemistry/flow problem.

DTC / SPN-FMI / symptom discrimination map

  • For low rail pressure, compare commanded and actual rail pressure under load and independently verify low-side supply/filter restriction.
  • For low boost, correlate VGT/boost command, actual MAP/boost, charge-air leak testing and exhaust backpressure/aftertreatment state.
  • For derate, preserve first SPN/FMI event order with aftertreatment temperature/NOx/DEF data rather than diagnosing by clearing the active code.

Measurement and diagnostic strategy

  • Cross-check electronic rail-pressure PIDs with independent fuel-supply testing, then branch target-vs-actual deviation into sensor, control valve, pump, leakage or supply restriction.
  • Compare EGT sensors for cold rationality and then for thermal response along exhaust flow when hot.
  • After repair, recapture rail/boost target-vs-actual, derate and aftertreatment state at the same load.

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. PACCAR EPA MX-13 official product page · OEM-primary · 2026-08-15
  2. PACCAR current powertrain product ranges · OEM-primary · 2026-08-15
  3. PACCAR TX-12 official compatibility data · OEM-primary · 2026-08-15
ENGINE DIAGNOSTIC DEPTH

Architecture evidence package

  • 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.

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.
  • Aftertreatment: DPF differential pressure, soot/ash calculations, EGT chain, NOx in/out and SCR/DEF dosing enable.
  • Live data: calculated load, MAP/boost target-actual, throttle angle, lambda/O2, STFT/LTFT, ignition advance and knock retard.

Engine measurement chain

  1. 1) Match vehicle/generation/market/powertrain/driveline identity to the source record; family name alone is not fitment evidence.
  2. 2) Preserve freeze frame and companion DTCs before clearing; make the first-fault condition reproducible.
  3. 3) Verify power/ground and network communication under load; do not decide from key-on static measurement alone.
  4. 4) Compare commanded air/fuel/pressure with an independent physical result; separate sensor bias from real performance loss.
  5. 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.

Related technical centers

DTC Academy → · Vehicle Universe →

Sources & freshness

Sources & freshness

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

Explore →