ELM327 Mini Scanner: Lives Under the Dash, Talks to Your Phone

The port feeds it battery power on pin 16, which is why nothing ever needs charging. Your app sends OBD2 requests over the radio, the dongle puts them on whichever bus your car uses, and the replies come back as numbers on the phone. The Veepeak VP11 measures 1.89 by 0.98 by 1.26 inches and weighs just over an ounce; the Panlong B02 shares that footprint at 18 grams.

What comes back is the generic engine side of the car, the part every 1996-or-newer US car has to answer:

• Trouble codes: the stored and pending codes behind a check-engine light, which you can clear once the repair is done.
• Live data: RPM, speed, coolant temperature, throttle position, fuel trims, O2 sensors and mass airflow, as dials or graphs.
• Freeze frame: the sensor snapshot the engine computer saved at the moment a code set.
• I/M readiness: which emissions monitors have finished running, useful the week before an inspection.
• Vehicle info: the VIN, plus CID, CVN and battery voltage on the ViaBecs and B02-KD minis.

What stays out of reach matters just as much. Veepeak spells it out for the VP11: nothing from the ABS, SRS, TPMS, gearbox or climate modules, no oil-light reset, no injector coding. Apps built around dedicated hardware, such as BimmerCode, BimmerLink and ABRP, refuse a mini outright.

Android is the easy case. It hands Classic Bluetooth serial to any app, so even the cheapest blue mini works with Torque, Car Scanner and OBD Fusion. Pair it in Android's Bluetooth menu with PIN 1234, then choose it as the adapter inside the app.

iPhones are the trap. iOS keeps Classic Bluetooth serial away from ordinary apps, so a Classic mini never turns up, however often you try to pair it. A Bluetooth LE mini works another way: it stays out of the iOS Bluetooth menu and the app finds it by itself. Veepeak prints NOT for iOS in the VP11's name for exactly that reason.

Wi-Fi is the older workaround. The mini runs its own hotspot, the phone joins it, and OBD Fusion or DashCommand connect to its address. While connected, the phone's Wi-Fi is busy with the dongle; the iPhone setup notes weigh both iOS routes.

• Android only, lowest cost: a Classic mini.
• iPhone today, maybe Android later: a Bluetooth 5.1 mini covers both.
• A household with both kinds of phone: one BLE mini serves everybody.

Elm Electronics, the Canadian firm behind the original chip, has no version 1.5 in its history. That label belongs to the clone world, where it usually marks a copy of the 1.4-era command set running on a Microchip PIC18F25K80. Apps written years ago for the real chip expect those commands, so v1.5 minis stay in demand.

A v2.1 sticker on a clone rarely matches Elm's own v2.1. Many cheap v2.1 minis answer only part of the command list: a basic code read works, while an app's advanced mode or a manual protocol switch fails. The blue v2.1 mini suits Torque and simple reads; the Super Mini V1.5 names its PIC18F25K80 for apps that lean on the fuller set.

• Link: Classic Bluetooth, Bluetooth 5.1 LE or Wi-Fi. It decides which phones can connect.
• Version: v1.5 for broad app support, v2.1 for plain reads, unstated on branded minis such as the Veepeak.
• Chip: PIC18F25K80, often shortened to 25K80. The B02-KD calls its board a dual-board 25K80 chipset.
• Pack: one dongle or two. A two-pack keeps a mini in each car.

Branded minis sidestep the version game. Panlong writes fully ELM327 compliant and names nine OBD2 protocols for its B02, which also carries V1.5 in its model number. A version sticker helps you judge a generic mini, and matters less on a named one.

Two cars in the driveway

The ELM327 Mini 2-Pack puts two blue minis in one order. Leave one in each port and pair both with the same app; the box copy gives PIN 1234 and suggests Torque as the first app. Both show up as OBDII, so rename them in Android's Bluetooth menu to tell them apart.

An iPhone owner who wants a second option

The Panlong PL-B04 is a mini shell with Bluetooth LE. It skips manual pairing: open YMOBD, tap once, and the app connects. Panlong also names Car Scanner, OBD Fusion, DashCommand and Dr. Prius among the third-party apps, and the same dongle serves an Android phone.

The chip hunter

The Super Mini V1.5 puts the PIC18F25K80 in its name, the part most v1.5 clones are built on. Classic Bluetooth keeps it on Android. One blue variant in the family is titled No PIC18F25K while a white one says with PIC18F25K, so read the variant name before you order.

Torque on the dash display

Android head units pair through their own Bluetooth stack, and not every mini gets along with it; Veepeak warns that its VP11 may not. The JOYING v2.1 mini is made for Android car stereos, with PIN 1234, a 45mA draw, a 5 to 10 metre range and a 23-gram shell. Torque then runs full-screen on the dash.

The family's other member, the SYGAV adapter, is also made for Android head units and rules out the iPhone. Before ordering either, check that your stereo runs full Android and can install Torque from its app store. A stereo built only for hands-free calls usually has no way to talk to a data dongle.

• Two cars: the blue mini 2-pack.
• iPhone, second option: the Panlong PL-B04.
• Full v1.5 command set: the Super Mini V1.5.
• Stereo screen: the head-unit mini.

The split follows history. Classic Bluetooth serial was the first cheap wireless link for OBD2, Android apps such as Torque grew up on it, and its parts cost the least. Bluetooth LE minis came later, once iPhone owners wanted in without joining a hotspot.

Each camp gives something up:

• Android Classic minis: the cheapest route and the widest Android app support, with no iPhone support at all.
• Bluetooth LE minis: one dongle for both phones and no PIN prompt; YMOBD is the suggested app on the ViaBecs, Panlong PL-B04 and B02-KD.
• Wi-Fi minis: work on iPhone, Android and Windows, but occupy the phone's Wi-Fi, and the SCCJGL model rules out diesel cars.
• Head-unit minis: Classic Bluetooth minis made for a stereo's pairing menu rather than a phone's.

Families count designs, not names. The blue v2.1 family alone spans KVAEY, Dickno and stymart shells in singles and two-packs, and the Super Mini V1.5 family runs to more than ten near-identical variants. Counting every variant would only show how many labels one board wears.

Fuel type splits the camps too. The Panlong minis cover light diesels and the B02-KD names 12V gasoline and diesel vehicles. The Wi-Fi mini excludes diesel, and the blue v2.1 minis exclude hybrids and EVs, so a diesel or hybrid owner starts with a shorter shortlist.

1. Diesel: Panlong B02 V1.5, Panlong PL-B04 or B02-KD.
2. Hybrid: the Veepeak or a Panlong with Dr. Prius, because the app decides how much of a hybrid it can read.
3. Gasoline, 12V: any mini that matches your phone.

1. Phone. Android takes any mini; an iPhone needs Bluetooth LE or Wi-Fi; an Android head unit needs a mini made for car stereos.
2. Car. Most US cars from 1996 on speak OBD2, as do most EU petrol cars from around 2001, with diesels following around 2004. For hybrids and EVs the app sets the limits, and several minis exclude them.
3. App. Choose the app first, then confirm the mini names it. Car Scanner covers most needs, with Torque and OBD Fusion close behind.
4. Version. v1.5 or a named brand for demanding apps; v2.1 is enough for plain code reads.
5. Pack. One mini per car saves swapping and re-pairing.
6. Fit. The port often sits low near the pedals. A shell under two inches long clears your knee; press it fully home, as Veepeak advises.

Names confuse more than specs do. The blue v2.1 minis come as KVAEY, Dickno and stymart, all in the same shell with PIN 1234. The Super Mini V1.5 appears under a generic brand in blue and in white. Treat the family as the product and the brand as packaging.

Two picks stand apart from the clone families. The Veepeak Mini and the Panlong B02 V1.5 are branded Android minis with clear app lists and written support notes. That counts for a lot on the evening an app refuses to connect.

• Worth reading on the box: link type, version, chip, PIN, and the apps it names.
• Safe to skip: professional-grade claims and function counts such as 17 functions; every mini reads the same generic engine data.
• Worth a second look: any note ruling out iOS, diesel, hybrids or head units.

The Wi-Fi mini and the B02-KD round out the set for iPhone and Windows users, and the ViaBecs Bluetooth 5.1 is the first BLE mini to try.

1. Find the port. It usually sits under the steering column, near your right knee.
2. Plug in, ignition on. Key to ON or engine running; the mini's light comes on from pin 16 power.
3. Connect by link. Classic: pair OBDII in Android's Bluetooth menu with PIN 1234, or 0000 or 6789 on some units. BLE: skip the phone's menu and connect inside the app. Wi-Fi: join WiFi_OBDII, then open the app.
4. Choose the adapter in the app. In Torque or Car Scanner, select the paired mini and leave the protocol on automatic.
5. Add one gauge. Coolant temperature first: it proves the link works and shows when the engine is warm.

If the phone pairs but the app cannot reach the engine, push the mini deeper into the port and retry with the engine running. When a Panlong or ViaBecs mini is missing from the phone's Bluetooth list, that is normal; the app finds it. The PIN and pairing manual covers the stubborn cases.

Leaving the mini plugged in is a judgment call. The JOYING mini states a 45mA draw, roughly one amp-hour a day if the port stays live with the car off. A daily driver shrugs that off; a car parked for a fortnight may not, so pull it out before a long break.

• Daily driver: leave it in and let the app reconnect each trip.
• Weekend car: unplug it after each session.
• Shared car: a PIN-protected Classic mini, or keep it in the glovebox.