Asset-specific reader binding
An OBD-capable asset can remember its preferred Reader Library entry; known non-OBD assets can remain explicitly NO CODE READER without needless reconnect attempts.
Crank Main • OBD-II diagnostic evidence
Codes / Reader
Codes / Reader is Crank’s OBD-II diagnostic path: bind the right Reader to the selected asset, reconnect deliberately when that saved Reader becomes available, verify the live vehicle, scan supported code states, and preserve qualified evidence before any supported clearing operation.
Saved Reader reconnectDeep Scan theaterForeground Reader handoffFail-closed reset evidence
Current capability map
What this section does.
Crank treats the shared OBD channel as a controlled diagnostic resource. The operator-selected foreground task owns the lane, while destructive actions must prove safety and preserve real vehicle evidence before they are allowed to continue.
Saved-reader availability reconnect
Crank can watch for the selected asset’s saved Reader and reconnect when it genuinely becomes available, while preserving the operator’s manual-disconnect cooldown and non-OBD suppression rules.
Startup connection truth
When a saved Reader connection becomes authoritative during startup, the opener can wake and dock into Crank Main instead of remaining visually asleep while a live Reader already exists.
Live vehicle identity recovery
When the connected vehicle and selected packet disagree, Crank can identify the live vehicle and offer a controlled switch instead of blending the contexts.
Foreground Reader handoff
When the operator deliberately starts Codes work, Runtime yields the shared Reader lane after any already-in-flight command finishes. Codes owns the transaction until it releases focus.
MIL truth first
The scan presents malfunction-indicator state and diagnostic evidence before assuming a green or healthy condition.
Stored / pending / permanent states
Supported code categories are separated so the operator can see the different kinds of DTC evidence instead of flattening them into one list.
Deep Scan Theater
Longer scans show progress, retries and the developing evidence story rather than freezing on an unexplained wait.
Selected-code explanation
The selected DTC can be carried directly into the explain or search path without forcing the operator to re-enter the code.
OBD communications reporting
The app can surface communication health during diagnostic activity instead of leaving the operator to guess whether a long operation is alive.
Atomic pre-clear evidence
Reset preflight can hold one focused Codes/Reader lease across the initial safety proof and the complete pre-clear evidence sweep, so the evidence belongs to the same controlled diagnostic operation.
Coordination failure is not vehicle evidence
Busy, focus-wait or reserved-channel messages cannot be accepted as if they came from the vehicle. If required evidence is denied or incomplete, the reset path fails closed.
Final safety recheck + verification
Supported clearing remains gated by parked/engine-state safety, explicit confirmation, a final safety recheck immediately before the clear command, and post-reset verification afterward.
Reader hygiene
Disconnect cooldown, stale-link flushing and wrong-reader guards reduce cross-session contamination and accidental reconnect behavior.
Operating flow
How it fits together.
Step 1Select asset + reader
Step 2Verify live identity
Step 3Scan codes
Step 4Preserve evidence
Step 5Clear only through safety gate
Crank truth boundary: A DTC is evidence, not a parts conviction—and a coordination message is not vehicle data. Crank is designed to preserve qualified context before destructive actions and to stop rather than pretend when the required evidence cannot be acquired.