Scan Data Explorer
Eight types of scan evidence. Select each to see its purpose, context and limits.
Four Data-to-Decision Journeys
Follow four diagnostic paths from an initial scan to a justified next test or verification plan.
Scan Evidence & Mode Lab
Compare a stored event with live captures before interpreting the values. Then investigate four fictional cases by choosing which evidence to examine. This lab uses teaching data, not a connected scan tool or an OEM pass/fail limit.
Live data versus stored event
Illustrative fictional engine case: an event record was stored near a high-load complaint. Pick a live capture and compare operating context before making a statement about what changed.
Stored event (fictional)
RPM 2,600 · load 78% · coolant 91°C · vehicle speed 72 km/h · event: hesitation reported. One frame, not a continuous trace.
Selected live sample (fictional)
RPM 750 · load 21% · coolant 42°C · 0 km/h · no hesitation reproduced at idle.
A mismatch in operating state is not proof that a stored event was wrong or that a component failed.
What does this scan-tool service request?
Select a mode to review common purpose, limitations and safe use.
Evidence board — review the essential facts
Select an evidence card.
Choose the supported next step
Case reasoning is browser-local study practice and not a shop test or vehicle release record.
Scan Data Decisions
Six fictional scan-data decisions: preserve context, check source meaning and select the supported next action.
08.3 · Knowledge Check
Answer all ten questions for a browser-local knowledge score. This does not measure hands-on diagnostic competency.
Continue learning
Return to Course Player · Complaint Intake · 08.1 · Service Information · 08.2 · Scan Tools & Gateways · 04.5
Fictional scan captures and OBD descriptions are educational only. Confirm support and applicability before any authorized real-world diagnosis.