Compatibility

What DeepDiag works with.

DeepDiag reads the standard OBD-II data a car reports. Coverage beyond the engine and emissions controllers depends on the vehicle, its protocol, and the adapter.

The short answer

  • Car: an OBD-II port, most cars and light trucks sold in the US from 1996 on, or an OBD-II/EOBD vehicle elsewhere.
  • Computer: Windows, macOS or Linux.
  • Adapter: an ELM327-compatible USB adapter, or a Bluetooth Classic adapter that shows up as a serial port once paired. The app detects it automatically.
  • Internet: your computer needs a connection for AI analysis.
  • Subscription: an active Premium subscription, which covers every car you work on.

Cars

DeepDiag targets 12V passenger cars and light trucks with an OBD-II port. In the US, that means most vehicles sold from 1996 on. Cars sold elsewhere with an OBD-II or EOBD port can work where they expose the standard services.

DeepDiag does not support 24V heavy-duty commercial vehicles. It also cannot read a vehicle that has no OBD-II port.

A car having an OBD-II port does not guarantee every module will answer. That is why the app lists what it found and what stayed silent.

Adapters

Any ELM327-compatible USB or Bluetooth Classic adapter should be detected automatically. There is no port picker in normal use.

Some low-cost Bluetooth adapters use only Bluetooth Low Energy. They never show up as a serial port, so DeepDiag cannot use them. Pick a USB adapter, or a Bluetooth adapter that pairs as a serial (COM) port.

Adapter quality varies, especially among inexpensive clones. If the app cannot connect or cannot read the VIN, try another adapter.

For Bluetooth, pair the adapter in your operating system first, then let DeepDiag find it. Step by step: use an ELM327 adapter with a laptop.

What DeepDiag can read

  • Engine and emissions data: stored, pending and permanent trouble codes, freeze frames, live sensor data, emissions readiness and VIN.
  • Additional modules where the vehicle allows it: ABS, airbag and body modules that answer on the vehicle's CAN bus.
  • What stayed silent: a module that does not respond is listed as a no-response address.

Extended module scanning needs a CAN vehicle. On older non-CAN protocols DeepDiag still reads the standard engine and emissions data, but cannot address the additional modules the same way. Some 29-bit CAN addresses are outside what an ELM327 can send.

DeepDiag does not claim every manufacturer-specific module or enhanced code. It reads the standard services the vehicle exposes. New to trouble codes? See how to read one.

If it does not connect

  • Check the adapter is fully seated and the ignition is on.
  • Let auto-detection run, or set the port explicitly if you know it.
  • Unplug and replug the adapter, then try again.
  • Try a USB connection if Bluetooth pairing is unreliable.
  • Close any other scan tool that may be holding the adapter.
  • Try a quality adapter if VIN or live-data reads keep failing.

Still not sure?

Email support@deepwrench.com if you want to check a specific car before subscribing.