Skip to content
All work

Automotive

An OBD scanner that reads every module and writes to 0 of them, with AI diagnosis

Plug in, scan the standard and maker-specific modules, and get a plain explanation of likely causes and next checks.

Client
Internal tool
System
Car Doctor
My role
Design and build
When
Oct 2026, first truck test pending
Car Doctor dashboard, sample data
Sample dataLive OBD readings, scans and recordings for AI-assisted diagnosis.

01 / Problem

What wasn't working.

Consumer code readers stop at the engine codes. Dealer tools can write to modules, which is a risk in the wrong hands. Most people just want to know what is wrong and what to check next.

02 / Approach

What I built.

  1. 01

    USB OBD adapter on a small local server. Scans 11-bit CAN at 500k and a 29-bit module sweep.

  2. 02

    Every command passes a read-only allow-list. It cannot reflash or write.

  3. 03

    A fault knowledge base, checked by a validator before it is used.

  4. 04

    Claude explains likely causes and the next physical check, in plain language.

03 / Architecture

How the pieces connect.

PythonFlaskSocketCANSTN2120Claudesystemd
VehicleOBD adapterUSBScan layerread-onlyDashboardDiagnosisClaudeFault knowledgevalidatedVehicleOBD adapterUSBScan layerread-onlyDashboardDiagnosisClaudeFaultknowledgevalidated
DeviceEdge / networkServicePeople / UIAIData

04 / Result

0

writes to the vehicle. Read-only by design. A local dashboard that turns a scan into a short list of things to look at. Tested against a simulator; first real truck test is next.

Read-only

Allow-listed commands. No writes, ever.

Module sweep

Goes past engine codes into body and chassis modules.

Plain answers

Likely cause and the next thing to check.

Local dashboard

Runs on a machine next to the adapter, in a browser.

Have a problem like this one?

Book a call

Next step

Tell me what isn't working.

A 30-minute call. You describe the problem, I tell you straight whether it's worth fixing and roughly what it costs.

Book a call