Pair, read, and review your car's codes.
Plug a Bluetooth OBD-II dongle into the port under your dash, turn the ignition to ON, and pair it from Chrome. CrankKey reads the standard VIN, capability, stored, pending, and permanent trouble-code services, then sends the validated transient snapshot to the authenticated report endpoint for source-backed enrichment. Clear Codes is not available from connected scanning: only approved diagnostic reads can reach the adapter, while vehicle-changing commands are blocked before dispatch.
Review diagnostic limits before pairingHow the read works. After you pick the adapter from the system Bluetooth picker, the page opens a GATT connection, subscribes to the notify characteristic, reads the standard VIN and capability response, then requests stored, pending, and permanent DTCs. A responder address is evidence only; it does not identify an ABS, SRS, body, transmission, or manufacturer-specific module.
If you have a WiFi-only dongle.Chrome cannot open the raw TCP socket those adapters advertise. Use the vendor app to read, then enter the returned code in CrankKey's lookup.
Reports are transient by default. The browser keeps the raw snapshot for review, while the report request is validated and enriched without persisting or logging the scan. Choose Save diagnostic session after a completed read when you want the complete evidence and optional saved live-data projection in dashboard history.
Live data is capability-gated. After the scan, you can start a bounded read-only graph only for the standard PIDs reported by this adapter or vehicle. Unreported PIDs are not queried; OEM and enhanced-module data is outside this verified path.
Connected scanning is read-only. Clear codes, service resets, programming, coding, and active tests are unavailable. Only the explicitly approved standard diagnostic reads can reach the adapter.