Twelve packet-owned selections
The selected asset can carry its own 12 gauge choices instead of sharing one global layout across unrelated vehicles or equipment.
Crank Main • live operating instruments
Runtime Gauges
Runtime Gauges turns supported live data into an instrument-like 12-position operating view. Crank preserves qualified values between polls, prioritizes the gauges currently on glass, paints fresh responses as soon as they qualify, and keeps source, freshness and Aura evidence part of the display contract.
12 asset-owned selectionsQualified-value retentionImmediate live paintAura evidence
Current capability map
What this section does.
The current Runtime architecture is built to behave like instrumentation, not a list of scan results. A good value is not discarded simply because another request was omitted, delayed or temporarily unavailable.
Availability check
Crank can inspect which live data points the current reader and vehicle actually support before the operator assigns them.
Qualified values stay instrument-like
Once a Reader-backed gauge has a valid qualified sample, it retains that last qualified value between polls instead of rotating back through WAITING or UNAVAILABLE during an otherwise healthy session.
Partial-response protection
If a Reader or vehicle returns only part of a multi-data request, omitted values keep their prior qualified samples. Crank can demote that session to single-request polling rather than repeatedly erasing good evidence.
Glass-first acquisition
Visible gauges receive foreground acquisition priority so RPM, throttle, speed and other current-glass instruments are not stranded behind slower background work.
Immediate streaming paint
A fresh on-glass value can paint as soon as its Reader response qualifies instead of waiting for the rest of the acquisition sweep to finish.
Fortune / Aura isolation
Heavier forecasting and Aura analysis run outside the instrument streaming lane, allowing the numeric gauges to stay responsive without sacrificing the evidence system behind them.
Phone-only equipment support
Non-OBD assets can use their own phone/interface gauge selections; a generic phone-only bundle is only a fallback or template.
OBD communication status
Runtime can report whether the live link is active during the gauge session instead of leaving the operator to infer connection health from a frozen number.
Diagnostic truth preflight
Before presenting a clean green state, Runtime can hydrate last-known evidence and perform a quick evidence check when connected.
Source and freshness authority
Crank distinguishes OBD, phone/GPS and other sources while tracking whether Reader evidence is actually fresh enough to support the visible state.
Foreground Reader discipline
When the operator deliberately enters Codes / Reader, Runtime yields the shared OBD lane after any in-flight command finishes and resumes when focus returns.
Caller-aware Aura detail
Tapping Crank from Runtime can open full Aura/detail information and return to the Runtime caller instead of losing the operator’s place.
Operating flow
How it fits together.
Step 1Load selected asset
Step 2Check available data
Step 3Assign 12 gauges
Step 4Run live instruments
Step 5Review Aura / evidence
Crank truth boundary: A gauge can look beautiful and still be wrong if its source is stale, unsupported or disconnected. Runtime treats qualified response age, source authority and real connection state as part of the instrument—not as hidden implementation details.