Setting up a Veepeak OBD2 adapter

Which Veepeak do you have?

The Veepeak OBDCheck BLE+ is the one that works on both iPhone and Android — it speaks Bluetooth Low Energy, which is the only Bluetooth flavor Apple lets a normal scan app use. It's the unit we've tested on our own bench and vehicles, on both platforms.

Veepeak also sells classic-Bluetooth variants (the Mini-style units). Those are Android-only — not because the app is fussy, but because iPhones don't expose classic Bluetooth to third-party scan apps at all. If you're an iPhone owner holding a classic-Bluetooth Veepeak, no app can fix that; the BLE+ is the exchange to make.

Not sure which you have? If your iPhone can't find it during an in-app scan but an Android phone can, it's a classic-Bluetooth unit.

Pairing — in the app, not in Settings

This is the single biggest setup mistake, and it isn't your fault: everything else Bluetooth pairs in the phone's Settings, so that's where everyone goes first. BLE adapters don't work that way. They connect directly inside the scan app.

1. Plug the adapter into the OBD2 port — under the dash, driver's side, usually near your left knee. Push until it's fully seated.
2. Turn the ignition ON (engine running or at least key-on — the port is powered by the car).
3. Open the app and scan for adapters from there. In Fixiom: OBD2 tab → Scan for adapters. Your Veepeak appears in the list — tap it.

If you already "paired" it in the phone's Bluetooth settings, that's usually harmless for BLE units — but the connection that matters is the in-app one.

Your first scan

Once connected, the handshake takes a few seconds, then the app can read your VIN (so it knows the exact vehicle), pull codes across stored, pending, and permanent, and start streaming live sensors. In Fixiom all of that is part of the free scan tool — the whole first session costs nothing.

When it won't connect

• The scan finds nothing: check the adapter's LED is lit (seated + port powered), ignition is on, and Bluetooth is enabled on the phone. On iPhone, confirm you have the BLE+ (see above).
• Found, but the connection fails partway: most often the ignition is off or the engine computer is asleep — key on, try again. A phone that was previously connected to the adapter in Settings can occasionally hold it hostage; forget it there and reconnect in-app.
• Connected, but "ECU unreachable": the adapter is fine — the car isn't answering. Ignition fully on (dash lit), then retry. On some vehicles a full engine start is needed.
• Worked yesterday, silent today: unplug the adapter for ten seconds and reseat it. Adapters brown-out during cranking and occasionally need the reset.

What to run on it

A Veepeak is a standard ELM327-style adapter, so it works with the whole ecosystem of third-party scan apps — that openness is exactly why we recommend the class. Our honest take on matching an app to the job is in which app should you run on your adapter. The short version: Fixiom gives you a full free-forever scan tool, plus an AI layer that reads what the adapter streams and reasons over it — and the Veepeak BLE+ is one of the units we validated it on.

Honest limits

These apply to every adapter in this class, not just Veepeak: no Bluetooth adapter of any brand can reach vehicles whose diagnostics moved to CAN-FD (several 2021-and-newer GM trucks and SUVs among others), and some manufacturer-specific modules answer only factory tools. A budget BLE unit is also slower than premium adapters on big jobs like an every-module scan — it gets there, it just takes longer. What it reads is identical: the car reports the same data to a $25 adapter as to a $100 one.

Common questions

Related guides

• Adapter buying guide — Which Bluetooth OBD2 adapters actually work — and which can never work.
• Which app for your adapter? — Free scan tools, coding apps, AI diagnosis — matching the app to the actual job.
• P0420 — Catalyst efficiency below threshold — the code people get quoted a converter for.