The controller did not publish an engine-speed signal during the event.
CASE 09Starting + networkIntermediate8 minutes
Intermittent no-start
2014 gasoline hatchback · Occasionally cranks but will not start
Simulated evidenceNo vehicle commandsEvery decision explained
THE FAILURE SCENE
The vehicle starts normally during the first inspection. A time-stamped event capture from the owner is available.
Captured supply is not the leading abnormality for this event.
The captured path did not show total controller loss.
The scan did not publish an immobilizer fault, subject to coverage.
DECISION 1 / 3
What should the first report say?
The symptom is not currently present.
AUTHORSHIP · SOURCES · CORRECTIONS
See how this page earns trust.
These links are primary-source starting points for the page's scope. They do not replace the current manufacturer procedure, wiring, specification, or service information for a specific vehicle.
Publisher
ScanWrench Editorial is the working byline for this library. Joshua Black, founder and publisher, is responsible for publication decisions, disclosures, and corrections.
A reviewed date means an editorial scope and safety check. It is not an ASE credential, OEM authorization, or vehicle-specific repair approval.
Primary sources
- SAE J2012 — Diagnostic Trouble Code DefinitionsSAE International · Standardized DTC structure, definitions, and manufacturer-controlled ranges.
- SAE on-board diagnostics standards indexSAE International · Primary standards family for regulated OBD services, identifiers, and transport context.
- NHTSA datasets and APIsNational Highway Traffic Safety Administration · Primary U.S. recall, complaint, investigation, rating, and manufacturer-communication data.
Revision history
- Simulation review: claim boundaries, safety language, internal links, and cited source scope checked.
No material correction is hidden. Material additions and corrections are dated above when they occur.
Report a possible correction ↗