Heavy-Duty & Trucks / Technical editorial
Heavy-Duty Diesel No-Start: Symptom Classification and Evidence Checks
On this page
A click without rotation, slow rotation and normal cranking without combustion are different symptoms. Classify the actual failure before ordering batteries, a starter, sensors or fuel-system parts.
This guide concerns conventional heavy-duty diesel diagnostic planning. It uses Delco Remy electrical guidance and a historical Detroit two-filter fuel-system document. Neither supplies universal specifications for every truck.
Start with the observed symptom
| Symptom | Evidence to establish | Avoid assuming |
|---|---|---|
| No crank | Start request, permission, supply and starter-circuit behavior | A click proves the starter received adequate power |
| Slow crank | Actual rotation, battery performance, circuit losses and applicable mechanical checks | Fuel pressure is necessarily the initiating problem |
| Crank-no-start | Rotation, supported permission/synchronization data and applicable fuel evidence | One low displayed value identifies a failed pump |
| Starts then stops | Time sequence, supply, operating state and shutdown evidence | The cause is always an immobilizer |
Safety boundaries come before test attempts
Secure the vehicle against movement and follow the required transmission, parking and restraint instructions. Keep personnel and test leads clear of fans, belts and other moving equipment. A vehicle that would not start can start during diagnosis.
Do not bridge starter terminals or bypass start-permission safeguards as an informal test. Follow specified cranking duration and cooling requirements rather than repeating extended attempts.
Never loosen high-pressure fuel lines during cranking or search for leaks with fingers. Use the actual qualified fuel-system procedure. Do not introduce starting fluid or improvised priming methods without explicit manufacturer instructions.
Delco Remy example: loaded testing matters
Delco Remy's June 2023 starter-cranking guidance identifies main-cable voltage drop as relevant to slow-crank and click/no-click complaints. Its separate voltage-drop guidance distinguishes positive and negative circuit losses under a defined loaded test.
This supports checking both supply and return paths instead of condemning a starter from a sound or resting voltage alone. The published test load and limits belong to their stated arrangement; they are not copied here as universal controller or cable thresholds.
Use the applicable vehicle and component procedure, correct test equipment and relevant load conditions. A clean-looking terminal does not establish acceptable electrical performance.

Detroit example: cranking data forms a sequence
A 2015 Detroit hard-start/no-start document for a two-filter system begins with a Fuel System Integrity Check log and cranking speed, then considers fuel compensation pressure, engine state, synchronization and other fuel-system evidence.
The important planning lesson is the sequence and application context, not a universal pressure or speed figure. The document's numerical limits, routines and repair branches must not be transplanted to another injection system.
Preserve requested and reported values with their units and operating state. A zero speed display can reflect more than a failed sensor; low reported pressure requires the actual application-specific diagnostic path.
No-start diagnostic evidence worksheet
| Gate | Record | Reason to pause |
|---|---|---|
| Identity | Vehicle, engine, controller and relevant software | Only a badge or displacement is known |
| Classification | No crank, slow crank, crank-no-start or starts/stops | Every condition is described simply as no-start |
| History | Last successful start, temperature and recent service | Failure after maintenance is ignored |
| Electrical | Battery assessment and prescribed loaded circuit tests | Resting voltage is the entire supply check |
| Control | Actual start request, permission and relevant state | An interlock bypass is proposed |
| Cranking | Speed, synchronization and application-specific fuel data | Unsynchronized screenshots are treated as one event |
| Communication | Expected controllers, full fault records and supply context | Every missing module is called defective |
| Acceptance | Required repeat conditions and final checks | One restart is treated as proof against all intermittent faults |
Build a repeatable assessment
- Record the exact symptom and safe test conditions.
- Preserve supported-system faults, identity and event evidence before clearing.
- Follow the applicable electrical and start-control checks for the symptom class.
- For crank-no-start, use the actual engine procedure to evaluate rotation, control state and fuel evidence.
- Perform only approved targeted tests that distinguish possible causes.
- Verify the repair under relevant conditions and retain original and final records.

Keep the data list focused and record actual update/timing limitations. Do not write guessed sensor relationships, pressure limits or cylinder procedures into a general checklist.
Our OBD-II and J1939 evidence guide separates controller-reported symptoms from repair conclusions. Our CAN scope guide explains why physical signal measurements and message availability are different checks.
Programming is not a generic no-start remedy
Require an applicable service instruction or replacement requirement before programming. Resolve relevant supply and communication instability first, then confirm hardware, software package, permissions and prescribed preparation.
For a Detroit replacement context, our injector and ECM service guide distinguishes data entry, programming and commissioning. It does not establish coverage for every no-start vehicle.
Verify the actual repair objective
Repeat the prescribed starting and affected-function checks under comparable conditions. Inspect restored connections and service work using the correct safe procedure.

For hot, cold or intermittent complaints, state what conditions were actually tested and arrange appropriate follow-up. A normal workshop test does not erase the driver's recorded failure.
Frequently asked questions
Does a click prove the starter is faulty?
No. Establish supply, loaded circuit behavior and the applicable control evidence.
Does low reported pressure prove pump failure?
No. Use the actual injection-system fault procedure and evaluate its required evidence.
Is one restart enough?
Not necessarily. Verify the relevant conditions and document intermittent-test limits.
References and scope
- Delco Remy starter-cranking guidance, June 2023 — loaded circuit-loss relevance.
- Delco Remy voltage-drop guidance, June 2013 — defined positive/negative circuit test context.
- 2015 Detroit hard-start/no-start, two-filter system — historical application-specific diagnostic sequence, not a universal current procedure.
The worksheet is editorial guidance. No universal pressure, cranking speed, voltage threshold or replacement decision is supplied. The cover and inline images are generated illustrations, not actual workshop evidence.
More articles to explore
A Checklist for Choosing Diagnostic Hardware That Won’t Go Obsolete
A Checklist for Choosing Diagnostic Hardware That Won’t Go Obsolete
How to Use Flex by Magicmotorsport for Advanced Bench and Boot Flashing
How to Use Flex by Magicmotorsport for Advanced Bench and Boot Flashing
Top Features to Look for in a Professional Diagnostic Tablet
Top Features to Look for in a Professional Diagnostic Tablet
Comments