OBDInsight Read-only diagnostics

Your diagnostic workspace

OBDInsight

Understand your vehicle’s data. One clear view, with no guesswork.

Connect a compatible Bluetooth LE adapter for read-only measurements, or use the manual tools below. Imported values are a snapshot, not live vehicle data. No code clearing or vehicle control.

Live workspace / experimental BLE

Vehicle overview

Not connected

Start with a connection

Checking browser compatibility. Manual diagnostics are always available below.

Park safely before using this workspace. Enable the ignition only as directed by your vehicle and adapter manuals.

NO VEHICLE DATAMissing readings are unavailable, not zero.

Assign each gauge to a sensor below. Assignments last until this page is reloaded; multiple gauges can show the same sensor. Scales are display ranges, not safe operating limits. Out-of-scale values remain visible numerically.

Engine speedMode 01 · PID 0C
— rpmUnavailable · no reading
Vehicle speedMode 01 · PID 0D
— km/hUnavailable · no reading
Coolant temperatureMode 01 · PID 05
— °CUnavailable · no reading
Calculated engine loadMode 01 · PID 04
— %Unavailable · no reading
Throttle positionMode 01 · PID 11
— %Unavailable · no reading
Intake air temperatureMode 01 · PID 0F
— °CUnavailable · no reading
Control module voltageMode 01 · PID 42
— VUnavailable · no reading

Stored trouble codes

Mode 03 · engine ECU 7E8 only · not pending or permanent codes

Unavailable — connect an adapter and request codes.

    A code reports a condition, not a failed part. Look up a code for context.

    Adapter compatibility & connection help

    This experimental client requires HTTPS and Web Bluetooth (typically Chrome or Edge on a supported desktop or Android device). Safari, Firefox and iOS browsers are not supported. Bluetooth Classic ELM327 adapters cannot connect through Web Bluetooth.

    Only BLE ELM-compatible adapters exposing the Nordic UART service are selectable: 6e400001-b5a3-f393-e0a9-e50e24dcca9e, write characteristic …0002…, notify characteristic …0003…. UUID compatibility alone does not establish adapter compatibility.

    The client is limited to 11-bit CAN at 500 kbit/s, physically addressed engine ECU 7E0 → 7E8, supported Mode 01 measurements and single-frame Mode 03 responses. Other protocols, other ECUs and multi-frame codes are rejected, not guessed. No real adapter/browser combination has been hardware-verified for this release.

    Sample age measures when this browser received a response, not when the ECU measured it. A defective adapter replaying a matching response during a later identical request cannot be detected by this UART protocol.

    If a connection fails, check adapter power, close other apps using it, and reconnect deliberately. There is no automatic reconnect or command replay. Use manual import when your hardware is incompatible. Live data stays in this browser’s memory and is not uploaded or saved.

    01 / Code reference

    Look up a trouble code

    Use a five-character DTC such as P0300. Lowercase and surrounding spaces are normalized.

    P, B, C or U; then 0–3; then three hexadecimal characters. One code only.

    02 / Response interpreter

    Import a diagnostic snapshot

    Paste headerless, fully assembled positive responses, one per line. This is a text import, not a connection to an adapter.

    • Use saved, already assembled response bytes from one ECU and one session, not a complete scanner log.
    • Use complete hex byte pairs, spaced or compact: 41 0C 1A F8 reports an engine-speed snapshot of 1,726 rpm.
    • CAN headers, ISO-TP fragments, timestamps and adapter status text are not accepted. Ask your existing tool for compatible output; do not guess how to remove framing.

    Only have a five-character code such as P0300? Look it up above. No response text yet? Try the fictional sample below.

    Spaced bytes or compact hex. Maximum 8,192 bytes, 64 lines, 256 bytes per response. Accepted format and supported measurements. Do not paste VINs or personal data. Imports are processed on the server but not saved by the app.

    The sample submits no pasted response text and is not connected to your vehicle.

    Before you paste

    1. Use an existing trusted diagnostic tool to obtain a saved response. Manual import never sends requests to that tool or your vehicle.
    2. Copy only headerless, fully assembled response bytes from a single ECU/session. Remove timestamps and tool annotations. Do not remove framing unless your tool has already assembled and decoded it.
    3. Paste one response per line and interpret it. Compare results with vehicle-specific documentation and a qualified technician.
    Accepted format and known limitations

    43 01 33 00 00 reports P0133 with trailing zero-pair padding. 410C1AF8 reports 1,726 rpm. Mode 03 takes complete two-byte DTC pairs; zero pairs are trailing padding only.

    Supported positive responses: 43 (stored DTCs) and 41 PIDs 0C (rpm), 0D (km/h), 05 (coolant °C), 04 (load %), 11 (throttle %), 0F (intake air °C), 42 (control module voltage V). No DTC count byte is accepted after 43.

    An optional exact request echo (03 or a supported 01xx request) is accepted only immediately before its matching response. A lone ELM > prompt or one trailing prompt is allowed. Echoes are never executed.

    Not supported: CAN headers (e.g. 7E8), ISO-TP length/sequence framing, multi-frame fragments, multiple ECU responses or duplicate PIDs, negative responses, NO DATA, adapter status text, other modes/PIDs, logs with timestamps, comma-separated bytes or uploaded files. They produce errors; the parser never guesses how to strip headers or assemble frames.