- Classic Bluetooth, PIN pairing
- Android only, not for iPhone
- Firmware v1.5
The mini most Android owners reach for first: a VP11 that sits flush under the dash, speaks Classic Bluetooth to Car Scanner or Torque, and says plainly that it will not talk to an iPhone.
Veepeak's mini is the VP11, a Classic Bluetooth 3.0 dongle that plugs into the 16-pin port under the steering column and shows up on Android as OBDII. It carries no screen and no app of its own. Everything you see comes from the Android app you pair it with, which makes the choice of app half of the purchase.
Classic Bluetooth is the key word. It is the serial-port style of Bluetooth that Android has always opened to apps, and the reason Torque, OBD Fusion and Car Scanner can talk to the VP11 directly. The flip side is iOS, which keeps that profile closed, so Veepeak prints its warning in capitals: no iPhone, no iPad.
Pairing takes a minute:
Imitation apps are the other trap. Veepeak warns against copies that borrow the Torque or Car Scanner name, then demand a subscription. Install the originals by their developer name; Car Scanner's no-cost tier already covers codes and live data. Connection settings for each app are in the ELM327 mini app setup notes.
| Spec | Value |
|---|---|
| Model | OBDCheck VP11 |
| Connection | Bluetooth 3.0 (Classic Bluetooth) |
| Bluetooth name | OBDII |
| Compatible devices | Android phones and tablets |
| iPhone / iPad | Not supported |
| Android head units | Not recommended, may not be supported |
| OBD-II protocols | J1850 PWM, J1850 VPW, ISO 9141-2, ISO 14230-4 (KWP2000), ISO 15765-4 (CAN) |
| Not supported | MS-CAN, SW-CAN, J1939 |
| Vehicle years | USA 1996+, Canada 1998+, Mexico 2006+, EU 2001+ petrol, 2004+ diesel |
| Excluded vehicles | OBD-I cars, heavy-duty trucks, most motorcycles |
| Functions | Read and clear engine codes, live data, freeze frame, I/M readiness |
| Modules not covered | ABS, SRS, TPMS, transmission, HVAC, body control |
| Compatible apps | Car Scanner, Torque, OBD Fusion, Dr. Prius, OBD JScan, Leaf Spy Pro, EOBD Facile, FORScan Lite |
| Incompatible apps | BimmerCode, BimmerLink, ABRP |
| Power | From the OBD-II port, red power light |
| Dimensions | 1.89 × 0.98 × 1.26 in |
| Weight | 1.12 oz |
| Warranty | One-year replacement |
Plug the VP11 into a 1996-or-newer US car and it reads what every OBD-II engine computer has to share. That covers check-engine codes and their meaning, the snapshot saved when a code was set, readiness monitors for an emissions test, and a stream of live sensor values.
The live data is where most owners end up spending time. Build a Car Scanner dashboard or a Torque gauge screen from these values and leave it on a phone mount:
Coverage by market follows the dates each region made OBD-II mandatory. Veepeak gives the USA from 1996, Canada from 1998, Mexico from 2006, and the EU from 2001 for petrol and 2004 for diesel. OBD-I cars, heavy-duty trucks and most motorcycles are out, and so is anything that talks J1939.
The dongle speaks J1850 PWM, J1850 VPW, ISO 9141-2, ISO 14230-4 KWP2000 and ISO 15765-4 CAN, the five families behind generic engine diagnostics. Two Ford body buses, MS-CAN and SW-CAN, are not supported. That is why FORScan Lite appears on Veepeak's app list with a note: it connects, but only on the high-speed CAN side.
Hybrid owners get a bonus. Dr. Prius reads Toyota and Lexus high-voltage battery health through the VP11, and Leaf Spy Pro is on the compatible list for Nissan Leaf drivers. EV support in general depends on each app's vehicle profile, so open Car Scanner's profile for your model first.
Veepeak is unusually direct about the limits, and they are worth reading before blaming the dongle. The VP11 is a generic engine reader. It does not open ABS, SRS airbag, TPMS, transmission, HVAC or body modules, and it performs no manufacturer-specific functions.
That rules out a group of jobs people often expect from a phone scanner:
App compatibility has a hard edge too. BimmerCode, BimmerLink and A Better Routeplanner (ABRP) are named as incompatible, because they expect adapters with their own hardware and firmware. If coding a BMW is the plan, the mini is the wrong tool from day one.
None of this is a fault in the VP11. Generic OBD-II is a public standard every engine computer must answer, while ABS, airbag and body modules sit behind each maker's own commands. Scanners that reach them carry per-brand software, which a Classic Bluetooth serial dongle does not.
Troubleshooting follows a short order that Veepeak publishes:
The VP11 sits among a crowd of look-alike shells, and the differences hide in the link type and the firmware. It carries no version sticker at all. Veepeak sells it as its own OBDCheck model with a one-year replacement warranty, rather than as a v1.5 or v2.1 clone.
| Mini | Link | Phones | Label |
|---|---|---|---|
| Veepeak VP11 | Bluetooth 3.0 Classic | Android | Branded, no version |
| Panlong B02 | Bluetooth | Android, Windows | V1.5 |
| ViaBecs mini | Bluetooth 5.1 | iPhone and Android | Integrated OBD chipset |
| Blue v2.1 clone | Bluetooth | Android | v2.1, PIN 1234 |
Pick by the phone first and the app second:
The VP11 can stay in the port between drives, and Veepeak designed its compact profile for exactly that. If the car will stand idle for weeks, pull it out anyway: any dongle on the always-live port draws a little current, and an old battery notices. The ELM327 mini manual covers pairing order and overnight use in detail.
Before ordering, confirm three things. The car has a 16-pin OBD-II port and a model year Veepeak covers. The phone runs Android. And the job is generic engine data rather than module coding, since that decides whether any mini is the right tool.
No. It connects over Classic Bluetooth 3.0, which iOS does not open to apps, and Veepeak points iPhone owners to its Bluetooth LE model instead.
Car Scanner ELM OBD2 covers codes, live data and readiness at no cost with the VP11. Torque Lite, OBD Fusion and Dr. Prius also connect, with some features paid.
No. It reads generic engine data only; ABS, airbag, TPMS, transmission and service resets need a scanner built for those modules.
Yes on OBD-II diesels in its coverage, such as EU diesels from 2004. Heavy-duty trucks on J1939 are not supported.
Usually a loose contact. Push the VP11 fully into the port with the ignition on, then retry or test a second app.