OBDLink CX Bluetooth 5.1 OBD2 Adapter for BimmerCode Review

I spend a good part of my working day with a phone in one hand and an OBD adapter in the other, and the OBDLink CX has lived under the dash of my G20 330i long enough that I have opinions. The CX is a Bluetooth 5.1 Low Energy adapter aimed at BMW, MINI and the A90 Supra, built around BimmerCode and BimmerLink. It is widely recommended for BimmerCode, it is not the only adapter that works, and it is not a universal scanner. Street price around $80.

Short version if you are one click from the buy button: get it if your main job is coding a BMW from a phone, especially an iPhone. Skip it if you want one adapter for the whole driveway or you plan to flash tunes. The rest of this review is the long version, with the caveats spelled out rather than buried.

What the OBDLink CX actually is

Physically it is a small plug, 46 by 23 by 33 mm and about 20 g, with no buttons and no USB port. It runs from the car's 12 V supply across an operating range of 8 to 18 V, draws a typical 55 mA when active and drops below 1 mA in BatterySave mode according to the dealer datasheet. The model number is CX101 and the manufacturer part number is 431101, which is worth remembering when you are checking a listing. Retailers we found list a 3-year warranty, and OBDLink promises lifetime firmware upgrades.

On the wire it speaks the usual set of protocols. ISO 15765 CAN, ISO 11898, SAE J1939, plus the K-line legacy pair ISO 9141-2 and ISO 14230 KWP2000. So it is a proper OBD-II adapter, and it works with the free OBDLink app for generic engine codes and live data on OBD-II compliant cars. What is true is that the CX is optimized for BMW, and coverage beyond BMW is thin, so it is not the adapter to buy for a mixed-brand driveway. If that is you, keep reading, because the MX+ section matters.

One number worth knowing is the maximum PID rate of 26 PIDs per second quoted in a technical listing. That is modest. The CX is a coding-first device, not a data logger. If you want to graph a dozen channels on a track day, this is not the OBDLink for that.

What I could not confirm is the chipset, the official release date, and any formal Bluetooth range figure. OBDLink does not publish them, so I will not pretend to know them either. You will also see talk online of an older, non-5.1 CX. I found no documented separate variant. Every detailed listing describes the same Bluetooth 5.1 BLE device with the same dimensions, so I treat the "old versus new CX" conversation as really being a CX versus MX+ conversation.

Who the CX is for and who should skip it

The pattern I see in the shop is simple. People who buy a CX for BimmerCode on a BMW are generally happy. People who buy a CX expecting a do-everything scanner are not, and it is not the adapter's fault.

The CX is for you if:

• You own a BMW, MINI or 2019+ Supra and want to code comfort features with BimmerCode.
• You use an iPhone, or you want the same adapter to work on both iPhone and Android without fuss.
• You want BimmerLink diagnostics as well, including fault codes across modules, live data and documented service functions.
• You want something you can leave plugged in without worrying about the battery.

Skip it, or at least think harder, if:

• You want one adapter for several brands. The CX is BMW-optimized and that focus is not a footnote.
• You live in Torque Pro, FORScan or AlfaOBD. A detailed 2026 review states plainly that the CX is not compatible with Torque Pro and lists those other apps as not compatible either.
• You want to flash a tune. MHD and bootmod3 do not list the CX, and flashing hardware should be whatever the flasher's own documentation vets.
• You need Windows or Mac software. I found no reliable evidence of CX support there. This is a phone and tablet device.

How it performs on real BMWs

I will split this by chassis generation, because the answer changes, and I will be precise about what the research actually supports versus what I would like to be true.

E-series

BimmerCode-focused guides describe the CX as a common choice for E, F and most G cars. For the E90 specifically, third-party testing reports successful coding sessions. For the E46, I could not find a primary source confirming full CX support, and I am not going to claim it from my own bench either. My E46 is a project car and BimmerCode's current car list is the reference you should check for any E-series model before you spend money. The K-line protocols are in the CX spec sheet, which is encouraging, but a protocol on a datasheet is not the same as a confirmed coding session.

F-series

This is the CX's comfortable middle ground. F-series BMWs and F and J-series MINIs are exactly what the adapter is positioned for, and I found no F-series specific exception list in the research. I also found no source saying MINI F or J cars carry the same Secure Gateway restrictions as newer G-series BMWs, so do not assume the G-series caveats below apply to your F56 or F60.

G-series and Secure Gateway

Here is where I need you to read slowly. The CX is widely reported to work with BimmerCode on G-series cars, with the G20 and G05 called out by name, and review sources describe it as one of the safest BLE choices for modern BMWs. On my own G20 it is the adapter I reach for. But Secure Gateway limits are function-specific, not adapter-specific. The adapter connecting successfully does not mean every module or every option will be available.

Three things the research flags that I see echoed by owners. First, modules can simply be missing in BimmerCode on a G20, which is what a Reddit thread about a 330i describes. Second, some G-series ECUs are reported to need an ENET cable rather than Bluetooth, with the head unit given as the example. Third, one source warns that coding past what Secure Gateway allows can fail or trigger faults that may need ISTA to clear. Coverage is described as a moving target that shifts with app version, chassis and ECU. Treat the CX as a compatible adapter for BimmerCode on G-series, not as a key that unlocks BMW's security. No adapter at this price is that.

iPhone vs Android and app support

The CX is BLE only. That is the whole reason it exists alongside the MX+. On an iPhone you do not pair it in iOS Settings. You plug it in, turn the ignition on, open the app and connect from inside the app. In BimmerCode that means Settings, then Adapter, then choose OBDLink CX. Guides note that location permission may be requested because BLE discovery on mobile needs it. This is normal, not a privacy stunt.

On Android the flow is the same in spirit. Enable Bluetooth, grant the app its permissions including location if asked, and connect inside the app. Some generic Android guides still say to pair in system Bluetooth first. That advice is aimed at classic Bluetooth adapters in general, and it is not consistently shown as necessary for the CX's BLE workflow. I did not find a solid, sourced bug list for specific iOS 17 or 18 or Android 14 or 15 versions, so if someone tells you a particular OS release broke the CX, ask them for the evidence.

App support is where honesty matters most, because the old review got it wrong and a lot of marketing gets it wrong too. What is explicitly supported:

• BimmerCode for coding. This is the primary use case and the reason the CX turns up on every BimmerCode adapter list I have read.
• BimmerLink for diagnostics. That means reading and clearing fault codes across engine and many body and chassis modules including ABS on supported cars, live data, and documented service functions such as battery registration, service reset and parking brake service mode. Do confirm your exact model, year and function against BimmerLink's own documentation, because a car being on the list does not prove every function.
• OBDLink app for generic OBD-II engine codes and live data.
• Car Scanner ELM, named as compatible in a recent expert review.

What is not supported or unconfirmed. Torque Pro is explicitly called not compatible in a detailed 2026 review, and I am ignoring one comparison table that lists Torque for the CX because it contradicts its own body text and looks like MX+ features copied across. Carly is a closed ecosystem selling its own adapters and nothing lists the CX, so treat that as unsupported. MHD and bootmod3 do not list it. ProTool does not list it. Windows OBDwiz is plausible as a generic interface but undocumented for the CX. No account or subscription is required for the CX hardware itself. The coding app is a separate purchase, but that is true of every adapter on this page. If you want the app-by-app view in one place, our BimmerCode adapter guide goes deeper.

OBDLink CX vs MX+ vs Vgate vs Veepeak

The MX+ is the interesting one. It is OBDLink's flagship, uses classic Bluetooth rather than BLE, and works with a far wider set of apps and brands. It is also listed as a BimmerCode-supported adapter. If you want one adapter for a BMW and a Ford and Torque Pro on the weekend, it is the better buy even at roughly half again the price. For BMW-only coding, the consensus across the guides I read is that the CX offers equal or better stability at a lower price, with BLE that iPhones prefer. The two sources I found disagree on the exact MX+ Bluetooth version, so I will stick to "classic Bluetooth". I have compared them in detail in OBDLink CX vs MX+ and reviewed the flagship separately in our OBDLink MX+ review.

The Vgate vLinker BM+ is the value pick and is named in BimmerCode's supported adapter list. At a street price around $40 to $60 it is hard to argue against for a few tweaks on an F30. What is not consistently published is the exact Bluetooth version, so if iPhone reliability is your priority the CX is the safer money. Our vLinker BM review covers it properly.

The Veepeak OBDCheck BLE+ is the other BLE adapter guides list for iPhone coding. I did not find a verified US street price in our research, so check the listing. Side-by-side tables I read place the CX above the Veepeak for coding reliability and speed, particularly on newer chassis, though those are qualitative judgements rather than published benchmarks. See our Veepeak OBDCheck BLE review for the detail.

And the generic ELM327 clone for the price of a coffee? Every BimmerCode-focused source I read calls anything outside the supported list a gamble. I agree. Cheap clones are where the battery drain and dropped-session horror stories actually come from.

Setting it up and fixing connection problems

"OBDLink CX not connecting" is a real search and a real complaint. In the posts I found it is the most common negative theme for the CX, ahead of anything hardware related. Almost all of it comes down to phone-side state and the fact that BLE does not behave like the Bluetooth speaker in your kitchen. Here is the order I work through.

• Plug the CX in fully. One forum-style report describes a fit issue with a particular OBD port that looked like a connection failure and was really a physical one. Check it is seated.
• Turn the ignition on, or start the engine. The adapter needs the car awake.
• Wait. A troubleshooting guide says the CX can take 45 to 60 seconds to become visible after insertion. A delay is not a fault.
• Connect inside the app. In BimmerCode go to Settings, then Adapter, then OBDLink CX. Do not chase it in iOS Bluetooth settings.
• Check permissions. The app needs Bluetooth and, for BLE discovery, location.
• If it connected once and now drops right after pairing, restart the phone. That was the fix in the Reddit report I found, and it is the fix I see most often.
• Still stuck? Unplug and reinsert, toggle Bluetooth off and on, forget any stale pairing, close competing OBD apps. OBDLink support notes a phone busy with other Bluetooth devices can cause intermittent failures.
• In the OBDLink app, set the protocol to Automatic and disable Start with Last Connected Protocol if detection is failing.

Now the part that actually damages cars. No source I found blames the CX for bricking a module. The risk described is low vehicle voltage or an interruption during a write. That is the adapter-agnostic truth of coding, and it is why third-party guides recommend turning off accessories and keeping voltage stable while you code.

For a full walkthrough with screenshots, our OBDLink and BimmerCode coding guide is the companion to this review. If it still will not connect, work through our OBDLink CX not connecting checklist.

Leaving it plugged in

OBDLink says its adapters use BatterySaver low-power mode, are safe to leave installed and will not drain the battery. The CX datasheet puts standby draw under 1 mA. Third-party BMW guides say it sleeps when the car sleeps. One owner reports six months connected with no drain, including periods when the car sat. I leave mine in the G20 and have not had reason to regret it.

Two honest caveats. OBDLink does not publish the exact wake conditions for the CX, so I cannot tell you whether it wakes on voltage change or bus activity. And every BMW has its own parasitic draw picture, so a car that already sits for weeks on a marginal battery does not need another variable. Unplug it if the car is going into hibernation. That is a hedge, not a warning about the CX. The battery drain complaints I actually find online are about cheap ELM327 clones without proper sleep modes, not genuine CX units.

How to avoid a fake OBDLink

Counterfeits with copied box art are reported on Amazon and eBay, though the volume of fakes is far higher for generic ELM327 dongles than for the CX specifically. The checklist I use is short.

• Buy from the OBDLink or ScanTool.net storefront, or a marketplace listing explicitly sold by the manufacturer. Third-party sellers with vague names are where the trouble starts.
• Price sanity. Street price is around $80. A guide citing European pricing puts the normal window at roughly $75 to $100. Far below that on a "new" unit is a red flag, not a bargain.
• Packaging. Sealed, original, undamaged, with clear OBDLink and ScanTool.net identity. Generic boxes, reprinted labels or "compatible with OBDLink" wording are not it.
• Identity check. Open the OBDLink app and confirm the adapter is recognized as an OBDLink device. An unknown or generic identity is a strong warning.
• Firmware check. Genuine units accept vendor-app firmware updates. Clones commonly fail to update or report inconsistent firmware.
• Behavior. Unstable readings, frequent drops and failures on basic OBD modes are classic clone symptoms.

Is it worth the price

Listed price is $79.95, snapshots show it at that figure on Amazon, and a comparison source shows offers as low as $75.95. Reviewers place the street price around $79 to $99. My view is that $75 to $85 is a fair buy, up to about $90 is acceptable from a trusted retailer with proper returns, and anything below $75 is an unusually good moment. I do not have verified price-history data for Prime Day or Black Friday, so I will not promise you a sale date. If the price is in the fair band and you need the adapter, waiting is unlikely to save you more than lunch money.

Against the MX+ at around $120 to $140, the CX saves you real money if BMW is your only target. Against the vLinker BM+ at around $40 to $60, you are paying roughly double for the OBDLink name, BLE 5.1, the 3-year warranty and the consistency of being the adapter that BMW coding guides reach for first. Whether that premium is worth it depends on how much a dropped session in the middle of a write would annoy you. For me, a lot.

Final verdict

The OBDLink CX does one job well. It is a BLE adapter for coding and diagnosing BMWs, MINIs and the A90 Supra from a phone, it is widely recommended for BimmerCode, and it plays nicely with BimmerLink for the diagnostics you actually want, including ABS faults and battery registration. On my G20 it has been the adapter I trust for the everyday coding people ask me about.

Its limits are real and I have not hidden them. The app ecosystem is narrow, it is not a multi-brand tool, throughput is modest, and Secure Gateway on G-series cars will still stop you at the door for some functions no matter what you plug in. I could not find it on a BimmerCode primary page, only in the guides and adapter lists that consistently name it, and I could not confirm E46 support from a primary source either.

Rating 4.4 out of 5. If you code a BMW from a phone, this is the default. If your needs go beyond that, our best BMW coding tool roundup will point you elsewhere, and the MX+ or an ENET cable is the honest next step.