An active diagnostic engine built for the bay. It calculates the one test worth running, reads the waveform you capture, and re-ranks every suspect before you've set the scope down.
P0300, intermittent, only above 4,500 RPM. Two shops threw plugs and coils at it — twice. Watch Lane Pilot roll-call the bus and chase the misfire past the ignition system everyone already replaced.
THE DIAGNOSTIC WORKFLOW
Connect your $15 OBD-II dongle. Lane Pilot discovers every module that answers, captures freeze-frame data and pulls live PIDs in seconds — then names the ones a secure gateway kept it out of, instead of calling the car clean.
Web Bluetooth · Any ELM327Librarian, NHTSA and Shop Data retrieve at once; the Mechanic synthesises and the Foreman runs the safety pass. Result: a cited, ranked test plan in 30–90 seconds.
Multi-Agent · All Makes · 30–90sRe-scan after the repair, then arm I/M Monitor Watch — it polls the readiness monitors every 5 seconds and beeps when they all set. Evidence on the RO.
I/M Monitor Watch · Mode 01 PID 01Built from this car's live data, real-world failure patterns, and recall records — every suggested repair prompting the tech for video evidence on the RO.
New pump in. The gateway rejected the command — so Lane Pilot named the NRC, showed the SGW guidance card for your shop's token path, and streamed live rail pressure so you can watch the new HPFP track. No "should be fixed." The RO carries the evidence — and the two coil jobs it didn't need.
Everything you just watched ran in a browser tab.
On a $15 adapter.
No tablet. No proprietary VCI. No unlock fees.
The other way to do this costs $4,000 and lives in a locked drawer.
THE PLATFORM
Active Bayesian reasoning. Calculates which physical test eliminates the most possible causes per minute of labor.
Drop scope captures straight into the chat — .CSV export or a screenshot. The engine reads the signal and re-ranks the suspect list, same turn.
Deterministic math. Real telemetry. The engine reasons on numbers it cannot invent.
IOControl 0x2F overrides run behind a fail-closed allowlist and a VSP-gated security-access engine, every request audited. The command catalogue is being rebuilt against capture-verified sources.
29-bit capture, live module roll-call, CSV + PEAK .trc export.
Writes locally, syncs when WiFi allows. Dead zones in the bay survive.
POST /v1/diagnose → cited plan in 30–90s. Any scanner, any platform.
Phone-mic envelope analysis. Anchored to RPM, it splits 0.5× valvetrain from 1.0× bottom-end — and stays quiet when it can't be sure.
worked examples · not shop data
2022 BMW M240i B58 · P0300 under load → high-pressure fuel pump
2018 Ford F-150 3.5L EcoBoost · P0016 cold rattle → cam phasers, not the chain
P0300 under load on B58: plugs & coils — wrong diagnosis
Every diagnosis feeds the loop. Every confirmed fix makes the next one faster.
Per-VIN diagnostic history
A dealer network keeps a scan history on every vehicle it services — one brand, on their side of the counter. An independent bay starts from zero. LanePilot closes that gap: every scan is saved against the VIN — a per-vehicle diagnostic database your shop builds automatically. Yours until you delete it.
The Diagnostic Engine reads the last five visits — the complaint, the codes that were stored, and the fix.
Flags a calibration change since the last visit — reflashed or tuned.
Trims, MAF, timing and O2 graded against that vehicle's own prior sessions.
How many miles and warm-up cycles ago the codes were cleared.
The first scan of a vehicle establishes its baseline — the record starts paying off the second time it comes in.
The language model never does the math. Margins, limits, and z-scores are computed in code and handed to the model as ground truth it cannot change — so every verdict is deterministic, auditable, and repeatable.
PLATFORM ARCHITECTURE · VERIFIABLE · NOT A CLAIMPlug in what you already own. First scan in minutes.