Prepare for ASE S2 by mastering decision order, not just part names: for each complaint family (no-start, hard-start, low power, smoke), write the measurement sequence, what each result rules out, and the next test. Practice with labeled worked scenarios and a scan-data rubric until your decisions, not your memorized specs, feel automatic.
Sorting a no-start or hard-start into four measurable inputs
Every diesel no-start or hard-start reduces to four inputs: sufficient cranking speed, fuel delivered at adequate pressure and correct timing, adequate cylinder compression, and enough combustion heat support from glow plugs or intake heaters.
Each input maps to a test. Cranking speed is compared with the engine's cranking specification. Fuel delivery is checked as transfer pressure and, on common rail engines, rail pressure during cranking. Compression is assessed with a gauge, a relative compression test, or leak-down. Heat support is verified through glow plug or intake heater current and resistance. Compression ignition is the key contrast with gasoline engines: there is no spark to check, and injection timing is governed by the ECM and cam position inputs rather than a distributor or ignition coil.
Build a ruling-out habit in a fixed order. Verify fuel supply quality first: air leaks on the suction side, a restricted filter, or gelled fuel in cold weather all starve injection. Then confirm the ECM is actually commanding injection. Only then move to mechanical causes such as compression. The exhaust tells you which branch you are in: white smoke during extended cranking means fuel is entering the cylinders, which shifts suspicion toward glow system function or compression. No smoke at all points back to fuel delivery. Writing that branch for each symptom family is the core study task.
Common rail versus HEUI versus pump-line-nozzle: what changes for diagnosis
In a common rail system, a high-pressure pump fills a shared rail and injectors fire on ECM command. In HEUI, engine oil pressure hydraulically intensifies fuel at each injector. In older pump-line-nozzle designs, the pump sets both pressure and timing.
These architectures change your first measurement. On a common rail engine you compare actual rail pressure to desired rail pressure with a scan tool; a shortfall directs you toward the supply, the high-pressure pump, or the pressure regulator, not necessarily the injectors. On an HEUI engine, the equivalent question is injection pressure on the oil side: oil level, high-pressure oil pump output, and the injection pressure regulator. On mechanically timed pump systems, diagnosis leans toward pump setup, supply, and nozzle condition instead. Same complaint, different decision tree.
This is why the fuel system family matters as a comparison topic and not a vocabulary list. An exam item framed around a rail pressure reading only makes sense for a common rail design, while a low injection oil pressure finding belongs to HEUI. Mixing the two produces plausible-sounding but wrong answer choices. The table below contrasts the three designs at a conceptual level; exact specifications vary by engine and manufacturer, so treat it as a decision aid rather than a service specification.
| Feature | Common Rail | HEUI | Pump-Line-Nozzle |
|---|---|---|---|
| Pressure generation | High-pressure pump fills a shared rail | Engine oil pressure intensifies fuel at the injector | Injection pump builds pressure for each line |
| Timing control | ECM commands each injector electronically | ECM controls the oil-side actuation | Largely mechanical pump timing |
| Key first measurement | Actual vs desired rail pressure | High-pressure oil (injection pressure) side | Pump timing and fuel supply |
| Characteristic diagnostic fork | Supply/pump/regulator vs injector command | Oil side vs injector side | Mechanical setup vs nozzle condition |
Interpreting cylinder contribution and balance-rate data correctly
Cylinder contribution testing isolates which cylinder produces less power, typically by briefly disabling each injector and comparing RPM drop, exhaust temperature change, or ECM-reported deviation between cylinders.
The interpretation rule is comparative: healthy cylinders show similar RPM drops or temperature deltas, while a weak cylinder barely changes the reading when it is disabled. But the test answers which cylinder, never why. Low compression, an injector delivering too little fuel, a leaking valve, or a restricted air path to that cylinder can all produce the same weak contribution. The contribution test narrows the search; a compression test, injector trim data, or a valve inspection decides the cause.
On common rail engines, balance or trim data adds a second layer: the ECM reports the fuel quantity correction it applies to keep each cylinder even. A consistently large correction on one cylinder suggests that injector is drifting out of calibration, while a weak contribution with normal correction points away from the injector and toward the cylinder's mechanical health. Practice narrating this fork aloud: contribution result first, then the correction data, then the follow-up test that separates fuel-side from mechanical causes.
Scenario one: cranking no-start on a common rail engine
On a cranking no-start with a common rail engine, compare actual rail pressure to desired pressure during cranking before touching anything mechanical. Near-zero actual pressure directs you to fuel supply, the high-pressure pump, or the pressure regulator, not the injectors.
Picture a pickup diesel that cranks strongly but will not start. The tempting mistake is pulling all injectors for bench testing, which costs days and may find nothing. The better sequence uses a scan tool during cranking: suppose the desired rail pressure is commanded at roughly 200 bar as an illustrative example while actual reads near zero. That single comparison eliminates compression and glow as the first suspects, because injection cannot occur without rail pressure. Next, check the supply side: filter restriction, an air leak on the suction line, and the transfer pump. If supply is healthy, the fork narrows to the high-pressure pump or the rail pressure regulator. Treat any specific numbers here as labeled worked examples from a service manual, not universal specifications.
The smoke observation refines the tree. If the engine cranks and emits white smoke, fuel is reaching the cylinders, so the supply branch is largely cleared and suspicion shifts to glow system function or compression, especially on a cold-weather complaint. If there is no smoke at all, the fuel delivery branch stays at the top. This is why the comparison matters: a single actual-versus-desired reading plus a smoke observation sorts the complaint into one branch in minutes, while guesswork at the injector level resolves neither branch.
Scenario two: low power with black smoke, where air and aftertreatment meet
Low power with black smoke means fuel is being injected but not fully burned, usually because available air cannot match the fuel: a restricted intake, turbo underboost, a stuck-open EGR valve, or excessive exhaust backpressure from a restricted aftertreatment device.
Picture a medium-duty diesel that is sluggish under load and pours black smoke on hills. The tempting mistake is replacing the turbocharger on the assumption that low power equals low boost. The better sequence compares boost actual with boost command at wide-open throttle, checks intake restriction, and verifies EGR valve position. At full load the EGR should be at or near closed; if it is stuck open, combustion air is displaced and smoke results even with a healthy turbo. If boost is well below command with EGR closed, then a turbo issue or a boost leak rises on the list. If boost matches command yet smoke persists, the question shifts toward overfueling on the injector side.
The interaction between air management and aftertreatment is where the concept gets genuinely hard: a restricted diesel particulate filter raises exhaust backpressure, which can suppress boost and cut power in a way that imitates turbo failure. Replacing the turbo in that scenario leaves the cause in place, which is why backpressure belongs in the low-power tree before any component replacement. Study the smoke colors as a triad, since each one opens a different decision tree: black indicates excess fuel relative to air, white indicates unburned fuel from cold operation, poor compression, or late injection, and blue indicates oil consumption.
A weekly scan-data exercise with a self-check rubric
Run one structured data session each week: record rail pressure, boost, EGR position, and balance or trim data at idle, during a snap throttle, and at steady cruise, then write out the cause of every deviation you observe.
Use any diesel you can access legitimately: a shop vehicle with permission, a school lab engine, a training module, or a simulator. Build a table with columns labeled idle, snap throttle, and cruise, and record rail pressure actual versus desired, boost actual versus command, EGR position, and coolant temperature. Expected observations: rail pressure tracks desired within tolerance at idle and cruise; boost rises smoothly toward the commanded value under load; EGR sits at or near closed at full load and open at light cruise; balance corrections sit near uniform across cylinders. A snapped throttle that momentarily dips rail pressure below desired is a normal transient, not a fault, and recognizing that distinction is part of the exercise.
Score each session on this rubric, two points per item: correct PID selection for the complaint you are simulating; a comparison of actual against desired rather than absolute values alone; a written cause hypothesis for each deviation; and a named next test for each finding. A total of seven or more means move to the next session type; below seven, repeat with a different complaint family such as a simulated cold hard-start. This score is a learning milestone for your own tracking, not a prediction of exam results, and repeating the exercise with varied complaints is what builds the branching habit.
A four-week preparation sequence and concrete readiness checks
Split preparation into four weeks: fuel systems and start diagnosis, then air management and aftertreatment, then scenarios and contribution testing, then mixed timed case review plus deliberate rework of every item you answered incorrectly.
In week one, write a one-page decision tree for the no-start and hard-start families, covering all three fuel system architectures from the comparison above. Week two covers turbo, EGR, and aftertreatment interactions, ending with the low-power scenario tree. Week three is application: work through practice items at /free-practice/ase-s2-diesel-engines-sde and convert every incorrect answer into a written note on which measurement would have changed your decision. Week four is consolidation: mixed timed case review, rereading your decision trees, and reworking your error log rather than adding new content.
Check readiness with four observable behaviors rather than a feeling. First, explain common rail versus HEUI diagnosis out loud without notes in under two minutes. Second, narrate a complete no-start decision tree from complaint to first branch without gaps. Third, score eight or more on the scan-data rubric across two different complaint families. Fourth, for each worked scenario, state the mistake, the better decision, and why it matters in three sentences. For administrative specifics such as scheduling, eligibility, and current test content, rely on the issuing organization at ase.com rather than third-party notes, since those details are controlled by ASE.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.