Capstone: turn the complaint into an evidence map, prove the failed branch, and verify the repair.
Safety/service boundary: This is a fictional teaching environment. Follow current OEM procedures and qualified-service requirements. Do not open pressurized common-rail circuits, defeat emissions/protection strategies, force unsafe regeneration, or treat normalized lab indices as vehicle specifications.
Translate no-start, hard-start, low-power, smoke, surge and warning-lamp complaints into reproducible operating conditions before choosing tests.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Organize evidence into cranking/compression, air/boost, fuel/rail, electronic control, aftertreatment and protection/thermal branches.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Verify cranking speed and synchronization, then separate compression-heat, air, rail-pressure/injection and control-permission problems.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Compare requested torque/load with usable air, boost response, rail response, derate status and exhaust restriction before replacing parts.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Use smoke color/condition only as one clue and correlate it with air mass, injection quality, temperature, oil/coolant evidence and aftertreatment state.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Recognize that a single symptom can originate in electrical supply, sensor plausibility, air, fuel, mechanical, thermal or emissions systems—and that protective derates can be commanded responses.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Recreate the original condition, compare before/after evidence, verify monitors/commands as applicable, document the root cause and avoid declaring success from a cleared code alone.
Foundation: identify the system role. Technician: connect evidence to tests. Deep: explain cross-system interactions and limits.
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Use this checkpoint to ask: what should happen, what evidence proves it, and what other system could create the same symptom?
Normalized teaching indices (0–100), not OEM specifications.
Evidence: Cranking speed is acceptable and CKP/CMP sync is present; rail actual remains far below commanded.
Evidence gate: explain why the evidence supports Fuel/rail response branch and name one competing branch you would rule out.
Evidence: Rail follows command; boost/air-mass response is low and charge-air evidence is abnormal.
Evidence gate: explain why the evidence supports Air/boost branch and name one competing branch you would rule out.
Evidence: Air and rail respond normally; aftertreatment restriction/derate evidence is active.
Evidence gate: explain why the evidence supports Aftertreatment/protection branch and name one competing branch you would rule out.
Evidence: Multiple sensors sharing a reference shift together while mechanical evidence remains stable.
Evidence gate: explain why the evidence supports Electrical/reference/control branch and name one competing branch you would rule out.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.
Rate 0–3 using observable evidence and require the learner to explain the reasoning.