BMW N47 Crank-No-Start — Diesel No-Start Diagnostic Workflow

The problem

A BMW N47 crank-no-start is a true no-start: the starter cranks the engine at normal speed but combustion never catches and the engine does not run. This is a different fault class from a long crank (which eventually starts) — the diagnostic priority order is different, and the evidence that closes each branch is different.

This page is the N47-specific crank-no-start path. It is narrower than the N47 engine hub and deeper than the generic cranks-but-won't-start symptom guide, which covers the symptom across all engines.

Vehicle-specific verified specification required — the N47 spans multiple years, platforms, and DDE versions; injection-enable thresholds and authorization logic are software specific.

Differentiate crank-no-start from its neighbours

• No-crank — starter does not turn; battery, terminals, starter, terminal-50, CAS/EWS authorization. A different investigation entirely.
• Long crank but eventually starts — pressure build, bleed-down, cranking speed; the long-crank path, not this one.
• Start-and-stall — starts then dies; idle control, immobiliser re-check, fuel supply after start, vacuum/air-path on some configurations.
• Crank-no-start — cranks at normal speed, never fires. This page.

Evidence branches

Work in this order — each branch closes before the next:

1. Cranking voltage — a healthy crank at normal speed with adequate voltage. A sagging voltage destabilises the DDE and sensors before any system is genuinely at fault; confirm supply and grounds first.
2. Engine-speed signal — does the DDE see a clean RPM during cranking? RPM in live data does not prove crank-signal integrity; a missing or corrupt crank signal means no injection trigger.
3. Crank/cam synchronization — scope the pair; both signals can look fine individually but correlate wrong. A sync failure means the DDE cannot enable injection.
4. Fuel-pressure build — does rail pressure reach the injection-enable threshold during cranking? A pressure that does not build points to low-side supply, HPFP, or control — in that evidence order.
5. Pressure plausibility — does the rail-pressure sensor's number match reality? A biased sensor can report pressure that is not there, or no pressure when pressure exists.
6. Injector / fuelling authorization — where evidence is available, is the DDE commanding injection once the enable thresholds are met? Immobiliser / CAS / EWS authorization blocks injection before any fuel fault; confirm authorization if pressure is present but there is no injector command.
7. Electrical supply — fuses, relay, supply to the DDE and fuel system; a missing supply produces a no-start with no mechanical fault.
8. Communication — can the scan tool talk to the DDE? "No communication" redirects to DDE power/ground, then bus, then gateway — before any engine diagnosis.
9. Mechanical condition — compression; a mechanical cause is a hypothesis requiring confirmation, not a first jump.

Do not automatically blame one part

• Timing — a timing concern is the most invasive; confirm with crank/cam correlation on a scope and with compression before condemning it. Do not jump to timing from a no-start alone.
• Fuel pump — confirm supply, sensor, and control first; the HPFP is rarely the first answer when the chain has not been isolated.
• Crank sensor — only if the crank signal is corrupt on a scope or there is a related code; RPM in live data is not proof of integrity.
• Injectors — only if authorization and pressure are confirmed and a balance/contribution test isolates a problem.

Each is a hypothesis to be confirmed, not the first answer.

ISTA workflow positioning

ISTA exposes DDE faults, freeze-frame/environmental data, the engine-speed and pressure live values, requested vs actual, and the test plan. Use it to confirm the crank signal, the pressure build, and the authorization status; MechanIQ helps structure and reason from that evidence. Do not reproduce proprietary BMW procedures.

Relevant tests

• Battery / ground voltage drop under cranking load.
• Crank and cam scope — confirms signal presence, integrity, and correlation.
• Requested vs actual rail pressure during crank — confirms whether pressure reaches the enable threshold.
• Mechanical gauge correlation of the rail-pressure sensor — confirms plausibility.
• Injector command / authorization check where supported.
• Compression / relative compression — only after signal, pressure, and electrical causes are exonerated.

Next-best-test logic

1. Confirm cranking voltage and speed are normal.
2. Confirm the engine-speed / crank signal and crank/cam sync on a scope.
3. Log requested vs actual rail pressure during crank and confirm pressure reaches the enable threshold.
4. Correlate the rail-pressure sensor against a gauge.
5. Confirm injector authorization if pressure is present but there is no command.
6. Only then form the mechanical hypothesis and confirm with compression.

Confirmation criteria

Confirm the cause only when the evidence isolates one branch: crank signal and sync confirmed, pressure build confirmed (or proven absent with a cause), authorization confirmed, and the no-start reproducibly explained by one element.

Repair verification

After repair, clear DDE fault memory, and crank the engine under the same condition that failed. The repair is verified when the N47 starts promptly and live data shows pressure reaching command and injector command present during crank.

CTA

Have BMW scan data, live values, or test results? MechanIQ can help organise the evidence, rank the diagnostic hypotheses, and identify the next best test.

Trademark disclaimer

MechanIQ is independent software and is not affiliated with or endorsed by BMW AG. BMW, N47, DDE, CAS, EWS, and ISTA are trademarks of their respective owners. All specifications are guidance only; vehicle-specific verified specification required.