OBDLink App 2026: Which App to Use, What It Costs, iPhone vs Android, and What to Do When It Won't Connect

This page is about software. Whether the OBDLink MX+ itself is worth $139.95 — its warranty, its hardware, the full 47-make coverage table — is answered in our OBDLink MX+ review, and we do not repeat it here. What follows is the question owners ask the day the box arrives: which app do I open, what does it cost, and why is it not connecting.

The answer in 60 seconds: which app for which job

Each row is a job, and the app beside it is the one OBDLink's own pages or the app maker's listing point to for that job. Prices are from the App Store and Google Play, read on 30 September 2026; the section on third-party apps has the detail.

🟢 = taken from the maker's page or store listing we opened, not a verdict on quality; ⚪ = a store rating. Prices go stale; every one was read on 30 September 2026.

Which app should an OBDLink owner open first, and where does PulsCar stand in this? The OBDLink app, for three reasons printed on OBDLink's own pages. It is included with every OBDLink adapter; OBDLink's FAQ says it is free for all OBDLink users; and it is the app in which OBDLink's manufacturer add-ons are free for MX+ owners. Much of what a third-party app adds is a specific job — coding a BMW, reaching a Ford module the add-on does not, reading a hybrid battery — and most of those apps charge for it. PulsCar's app works with the OBDLink MX+, so we have a commercial interest in it; it is separate from the free sound check near the end. The rule that governs every app on this page is OBDLink's own: the adapter talks to one app at a time, so close one before you open the next, or the second one may fail to connect.

How we checked, and what we could not read

Everything below was read on 30 September 2026 and saved as text: OBDLink's app page, compatible-apps page, FAQ, product pages, the "OEM-Specific Enhanced Diagnostics Support Coverage" PDF, the Troubleshooting Guide PDF (Revision C, August 2025) and 28 articles from its support knowledge base; the OBDLink app on the App Store and Google Play; the listing of every third-party app in the price table, on each store where it is listed; and the app makers' own pages, from FORScan, BimmerCode, JScan and scan my T3SLA. The full list is at the end. OBDLink's Carbyte, a GM disabler that also pairs with a phone, is not covered.

Ratings are shown with their count, because a 3.7 from 88 people and a 4.8 from 32,692 are different facts; Google Play's displayed rating comes with the exact count from the listing's data. Prices are US store prices on the day, and in-app lists are what each store printed — up to ten items on the App Store, a price range on Google Play.

What we could not read. The Google Play address OBDLink gives for FORScan Lite returned "not found" (HTTP 404); FORScan's own news page explains why, and we quote it below. The US App Store listing for scan my T3SLA showed no ratings. We did not install or test any app, and we ran no connection test of our own: every behaviour described here is the maker's description, not our measurement.

What the OBDLink app is, and what it costs

The OBDLink app is OBD Solutions' own software for its adapters, on iPhone, iPad and Android. Its page opens by saying it "is included with your purchase of any OBDLink adapter" and "can read diagnostic trouble codes (DTCs), and clear check engine lights." The same page lists the rest: reading "information from your car's many computer modules", "perform OEM maintenance procedures", trip maps, live parameters, custom dashboards and fuel economy. It "works with all 1996 and newer cars and light trucks sold in the United States" — for gasoline cars, the same year the California Air Resources Board's OBD II fact sheet draws: "All 1996 and newer model year gasoline and alternate fuel passenger cars and trucks are required to have OBD II systems."

What it costs has three layers, and OBDLink's FAQ separates them in one answer: "The OBDLink app and OBDwiz software are free for all OBDLink users; however, OBDLink/OBDwiz add-ons and third-party apps may require a separate purchase or subscription."

Two limits on the add-ons matter before you pay for one. OBDLink says the manufacturer packages are "available primarily for vehicles sold in North America". And OBDLink names three families as exclusive to the MX+: "Add-ons that are exclusive to OBDLink MX+ include: GM; Honda, Acura; and Hyundai, Kia." For owners of any other OBDLink model, the support article adds that bought add-ons "are not guaranteed to access all OEM-specific PIDs/DTCs", and gives an LX example: with an LX and a Ford, you "will not be able to read certain Ford PIDs that come from the MS-CAN network." Which makes are covered at all, and to what depth, is OBDLink's coverage table, set out make by make in our MX+ review.

The app store picture, for the app itself: the App Store shows 4.8 from 12,695 ratings and version 7.4.0, dated July 15, 2026; Google Play shows 4.7 from 20,524 ratings, "Updated on Jul 15, 2026", and 1M+ downloads ⚪. On the App Store it needs "iOS 15.0 or later."

Which adapters the OBDLink app works with, on iPhone and on Android

The OBDLink app is locked to OBDLink hardware, and the two stores say so in bold, with NOT in capitals. The App Store: "The OBDLink app exclusively works with OBDLink MX+, OBDLink CX, and OBDLink MX WiFi OBD adapters" and "The app will NOT function with any other brand of OBD adapter." Google Play lists nine OBDLink models and says "The app will NOT work with any other brand of OBD adapter." Put together with OBDLink's own tables, this is the matrix.

Two practical consequences. On an iPhone the choice is the MX+ or the CX — "only OBDLink MX+ and CX currently support iOS" — and the cheaper CX cannot use the add-ons OBDLink names as exclusive to the MX+: GM, Honda and Acura, Hyundai and Kia. If you already own a generic ELM327 dongle, the OBDLink app is not for you; the apps that accept any adapter are in the third-party table below.

The first connection, step by step

Doing the first connection in OBDLink's order avoids several of the problems its troubleshooting articles list. OBDLink's getting-started article for iOS and Android, modified on June 14, 2026, gives the order, and the first instruction in its connection section is a safety warning worth repeating: "Don't run your vehicle's engine in an enclosed garage."

1. Install the OBDLink app from the App Store or Google Play, open it and tap Settings, Set Up New Adapter. OBDLink's connection troubleshooting article is explicit that the app's Connection Wizard is the way in: "You must use the Connection Wizard in the OBDLink app the first time you connect a new adapter or if you add a new vehicle."
2. Pick your adapter by its picture, then start the engine with the Start button — or, the article says for a car with a key, "turn the key to Accessory (Acc) mode." Elsewhere OBDLink recommends the engine running.
3. Plug the adapter into the OBD port, which is "In most cases" in the driver's footwell below the steering wheel, and check that the green power light is on.
4. Press the Pair button — "Only MX+ and LX adapters have this button." The button is a security feature by OBDLink's own description: the MX+ page, which calls it the Connect button, says it "requires physical access to enable Bluetooth pairing".
5. Choose the adapter in the phone's Bluetooth list and wait. OBDLink's figure is "It may take 45-60 seconds." On Android you may need to scroll the list.
6. Choose a network. The app asks which vehicle diagnostic network to open; OBDLink's advice is "We recommend that you select Generic OBD2 for everyday use."
7. Allow location "While Using App" and agree to registration, as OBDLink recommends. The article shows a message that "registration is required"; OBDLink's quick start guide says location data "is used to enable the map feature and stays on the device".
8. Fill in the Vehicle Editor. The app tries to read the VIN and fill in year, make, model and option itself. If it cannot, fill all four by hand: "All 4 fields must contain text or you may not be able to download OEM Enhanced Add-Ons." Set the fuel type (E85 if that is what you burn) and the engine size from the owner's manual so the fuel economy figures mean something.

That last step is the one people skip, and it is the one that later makes "Get Enhanced OEM Add-Ons" appear or not. If the app offers no add-on for your car after the Vehicle Editor is complete, OBDLink's reading is simple: "your vehicle is not supported for enhanced diagnostics. Standard OBD-II diagnostics are available for your vehicle."

What each part of the OBDLink app does

The home screen is a set of icons, and OBDLink documents each with its own support article. In the order an owner meets them:

Three details in those articles change how useful the app is. The report is the thing to send a mechanic. OBDLink's app page calls it "a full diagnostic report that you can save and send to your mechanic", and the diagnostics article says it can take "1-2 minutes" to build; store one before you clear anything. The readiness screen starts at None. The monitors article says "Not all states have a readiness standard" and that the default is None, so pick your state and your car's model year, or the screen will not judge your state's standard. Manufacturer PIDs come built in for two makes. Settings, Manufacturer PIDs has sections for GM on CAN ("typically, vehicles from 2007 and newer"), GM on J1850 ("typically, vehicles from 1996-2006") and Subaru on CAN; other makes reach manufacturer data through the add-ons.

One more detail explains an empty gauge: the getting-started article says a PID shown "in red text" is one your car does not support, so choose gauges while connected.

Enhanced add-ons: downloading them and picking the right network

The add-ons are where the OBDLink app goes past a generic code reader, and the download has its own sequence in OBDLink's diagnostics article. With the engine running and the app connected, tap Settings, Get Enhanced OEM Add-Ons, pick the manufacturer, then the model year, then Get and Choose. OBDLink's note about the free add-on is "We recommend that you tap GET FREE ADD-ON to use all your OBDLink adapter features." The download may take "1-2 minutes", and the app may ask to disconnect the adapter while it downloads.

Then the part that confuses people: the network. Every time you connect, the app can ask which of the car's diagnostic networks to open, and the default, "Prompt", asks every time. Generic OBD2 is OBDLink's everyday choice, but it is not where every module lives. OBDLink's own example is a Toyota: "if you have a Toyota vehicle and you want to view Tire Pressure Monitor PIDs, you must select the Tire Pressure Monitor network. If you selected Generic OBD2 or Network A, you will not be able to access Tire Pressure Monitor PIDs." To change it, go to Settings, Vehicle Editor, Enhanced Network. GM, Honda and Acura, and Hyundai and Kia skip this step; OBDLink says "You do not need to select a vehicle network for these manufacturers."

On a car with manufacturer live parameters, the first scan of an enhanced network "may take 1-2 minutes", and its results are saved. If no add-on is offered for your car at all, OBDLink points to third-party apps; for its worked example, a 2018 Audi Q5, "you could review the Carista app to confirm support for your vehicle."

OBDLink's coverage PDF is dated October 21, 2021, and the release notes have added model years since — version 7.4.0, on July 15, 2026, says "Added enhanced diagnostics for 2026 Ford vehicles." For your exact car, the Vehicle Editor is the answer, not the PDF.

Reading and clearing codes without losing the evidence

Clearing a code takes two taps in the OBDLink app — the three-dot menu, then Clear Codes — and they are the taps to hold back on. OBDLink's diagnostics article puts two warnings next to it. The first is about how: "You should only clear codes with the ignition ON and the engine OFF. You should never try to clear codes with the engine running." The second is about what you lose: "The freeze frame data is deleted when you clear codes." Freeze frame is the snapshot the engine computer takes when it stores a code — in OBDLink's example, coolant temperature, engine RPM and vehicle speed — and it may help a mechanic see what the engine was doing when the code set.

Clearing also resets the car's self-tests. The California Air Resources Board's fact sheet explains that incomplete monitors mean the car "has not been operated enough since the on-board memory was last cleared to allow all of the OBD system checks to complete", and under EPA's test procedure for state OBD inspection programs, 40 CFR 85.2222, when tests are incomplete, "the customer shall be instructed to return after the vehicle has been run under conditions that allow completion of all applicable onboard tests." A second incomplete result fails the car, with limited exceptions: up to two unset monitors on a 1996-2000 car, one on a 2001 or newer car. Clear a light shortly before an emissions test and you may be sent away, or fail, with monitors that are not ready.

So the order with any app on this page, the OBDLink app included, is: if the light is flashing rather than steady, skip this routine and read our check engine light guide first; otherwise read the code, open its freeze frame, store the report, fix the cause, and only then clear — with the ignition on and the engine off — and drive before any inspection. For a manufacturer code the app has no text for, OBDLink's article passes on what "Some users have reported success" with: an internet search of the year, make and model with the code in quotes. What the common codes mean, and when a light is urgent, is covered in our check engine light guide, and clearing a light safely in our reset guide.

Third-party apps on OBDLink's list: prices, ratings, and what their own listings say

OBDLink is open about its adapters working with other people's software. Its compatible-apps page opens: "While all OBDLink tools include a capable diagnostic app, many third-party apps are available that can greatly expand the utility of the tool." That page names 17 app entries and the OBDLink models each supports; the MX+ apps page features 15, five of which the first page does not list, and claims the MX+ "is supported by dozens of popular third-party automotive apps—more than any other OBD adapter." We cannot test that superlative, and OBDLink itself hedges its list in a support article: "This page is not an exhaustive list of third-party apps that support OBDLink adapters," and "Our support team can't answer detailed questions about non-OBDLink apps."

What neither OBDLink page gives is a price. We read each app's own listing on each store OBDLink links it on; this is what they said on 30 September 2026. Ratings are the store's, with the count; "OBDLink lists" means the platforms and adapters on OBDLink's compatible-apps page.

Read the table as three kinds of app. General diagnostics — OBD Fusion, Car Scanner, Torque Pro, OBD Auto Doctor — cover the same everyday jobs as the free OBDLink app, each with extras of its own, and they also accept other brands of adapter; OBDLink's own line on OBD Fusion says it "contains the same functionality as the free OBDLink app", and OBD Fusion's Android listing says its maker, OCTech, LLC, is "the developers of TouchScan and OBDwiz for Windows and OBDLink for Android." Make-specific tools — FORScan, BimmerCode, Carista, AlfaOBD, OBD JScan, the hybrid apps, scan my T3SLA — often reach modules and settings the OBDLink app does not, especially on makes it has no add-on for, and most of the paid unlocks sit here (Hybrid Assistant is free). Display and track apps — DashCommand, RealDash, Harry's LapTimer — lean toward dashboards, logging and lap timing, though DashCommand's listing also says it reads and clears check engine lights.

Four things to check before you pay: three places where an app's own listing does not confirm OBDLink's list, and one where the newest iPhone version is years old. Carista: OBDLink lists the MX+ and the CX for it on iOS, but Carista's own listing recommends its own scanner and says the app "can also be used with other compatible OBD2 adapters such as OBDLink CX, OBDLink MX Bluetooth or LX adapters" — the MX+ is not named, which is not the same as excluded. Car Scanner on iPhone: OBDLink lists the MX+ and CX, while Car Scanner's App Store text asks for a Wi-Fi or Bluetooth 4.0 (Bluetooth LE) ELM327-compatible adapter and its recommended brands on iOS do not include OBDLink; its Android listing names OBDLink first. FORScan Lite on Android: OBDLink's MX+ apps page still marks it Android and iOS; FORScan's own site says the app left Google Play and new Android licenses are on hold, below. DashCommand on iPhone: both lists name the MX+, but the newest version on the App Store is dated February 14, 2023, while the Android listing was updated on September 18, 2026.

Ford, Lincoln, Mercury and Mazda: the OBDLink add-on or FORScan

For the Ford group, "obdlink mx+ ford" has two answers that stack rather than compete. The first is free with an MX+: the OBDLink app's Ford add-on. OBDLink's coverage PDF marks Ford, Lincoln, Mercury and Mazda for both manufacturer trouble codes and manufacturer live parameters, with model rows such as the F-150 for "1997-2000, 2002-2020" and the Explorer for "1996-2000, 2002-2020"; the app's release notes have since added the 2023, 2024, 2025 and 2026 Ford model years. The MX+ matters here for a hardware reason: it reads Ford's medium-speed CAN network (MS-CAN, a second network where Ford keeps some modules), and OBDLink warns that with an LX and the paid Ford add-on, "you will not be able to read certain Ford PIDs that come from the MS-CAN network."

The second is FORScan, which goes further. Its home page says it "can detect modules which are not visible for regular OBD2 scanners", runs test and service procedures, and that "Version of FORScan for Windows can also perform configuration and programming functions." Its supported-vehicle lines are specific: "Ford, Lincoln, Mercury models of 1996 - 2024MY", with 2025 and newer supported on a "'best-effort' commitment", and Mazda "1996 - 2022MY up to 6G", with the warning that "Mazda 7G models (new Mazda 3, CX-30, MX-30, CX-50 etc) are supported partially or not supported at all!" Its adapter list recommends OBDLink twice: the EX as the "recommended USB adapter for Windows version of FORScan" and the MX+ as the "recommended Bluetooth adapter for Lite versions of FORScan (iOS, Android)".

Where you run it decides what it costs and whether you can get it at all:

The Android row is the surprise. FORScan's news page says "FORScan Lite was removed from Google Play Market" (December 27, 2024), and on December 10, 2025: "Due to numerous complaints from users unable to download or install the application after purchase, as well as attempts to use low-quality adapters, it has been decided to temporarily suspend sales of FORScan Lite licenses for Android." The same entry says support for existing users continues, and the download page still offers a free FORScan Demo for Android "to check compatibility before purchasing". Existing license holders still get updates — version 1.5.31 for Android came out on May 14, 2026. So a Ford owner with an Android phone, an MX+ and no FORScan license has, today, the OBDLink app's Ford add-on on the phone, or FORScan for Windows on a laptop; the address OBDLink still gives for FORScan Lite on Google Play returned "not found" when we tried it.

So: use the OBDLink Ford add-on first, free on an MX+. Reach for FORScan when you need a module or a procedure the add-on does not show, try the free Viewer before paying on an iPhone, and read FORScan's warnings before changing any configuration — that is not a read-only act.

Toyota and Lexus, hybrids included

For "obdlink mx+ toyota" and "obdlink mx+ lexus", the OBDLink app is the strongest of its own cases. OBDLink's coverage PDF marks Toyota, Lexus and Scion for manufacturer codes and manufacturer live parameters, and the model rows run long: the Camry "1996-2021", the RAV4 "1996-2021", the Highlander "2001-2021", the Prius "2001-2021", the Lexus RX350 "2007-2021" and the RX450h "2010-2021". The app page names Toyota, Lexus and Scion among the makes with enhanced diagnostics that reach "additional modules such as ABS, Airbag, Transmission, 4x4, and Body Control modules." The App Store also lists a "Toyota 2010 Enhanced" package at $14.99 for owners of other OBDLink adapters.

Two Toyota-specific details from OBDLink's own articles. Pick the network for the module you want. OBDLink's tire-pressure example is a Toyota: Generic OBD2 will not show tire-pressure data; the Tire Pressure Monitor network will. There is a customisation page. The 6.4.1 release notes, from July 24, 2024, added "a customization page that's available with the Toyota and Lexus enhanced add-on"; OBDLink does not say what it changes, so treat it as something to open and read before touching.

Hybrids are where OBDLink sends owners elsewhere. Its Troubleshooting Guide says "The OBDLink app included with the adapter only connects with OBD-II (emissions-related) data, so you likely will not be able to connect and read much (if any) data from your vehicles", and its error-message article says "the OBDLink app is not designed to read this type of data" on an electric or hybrid car. The app does carry some hybrid data — version 6.4.1, in July 2024, "Added EV and Hybrid energy and energy economy PIDs" — but OBDLink's later guide and article still point hybrid owners elsewhere, and for hybrid data OBDLink's compatible-apps page names two Toyota hybrid apps, both Android. Hybrid Assistant describes itself as "a free Android App that helps you get the most out of your Toyota/Lexus Hybrid car." Dr. Prius says it helps "to examine the health of the High Voltage battery", and warns that "It is generally NOT a good idea to use WiFi OBD2 adapter due to the interruption of the internet during the connection." Both are Android-only on OBDLink's list; an iPhone owner should check before counting on a battery check.

Carista also names Toyota, Lexus and Scion among the makes with "Advanced app settings", and BimmerCode lists the Toyota Supra. Both are free downloads with paid in-app items, and both change settings, so both belong after the free OBDLink add-on, not before.

GM, Honda, Hyundai, Kia, and the Jeep and RAM group

GM, Honda and Acura, Hyundai and Kia are the add-on families OBDLink names as exclusive to the MX+, and the MX+ is the adapter that reads GM's single-wire CAN network. OBDLink's coverage table gives these makes manufacturer trouble codes but not manufacturer live parameters, and its own worked example, a 2012 Chevrolet Malibu, ends: "The OBDLink app can only request the OEM DTCs and clear them." Since then the app has added built-in GM manufacturer PIDs, and version 6.9.1 "Fixed a bug that prevented reading enhanced DTCs with the Honda and Hyundai/Kia OBDLink MX+ add-ons". For these makes, the OBDLink app on an MX+ is the first route. Several apps on OBDLink's list name these makes in their own listings, at different depths. Carista gives "Advanced app settings" for "certain" Acura, Buick, Cadillac, Chevrolet, GMC, Honda, Hyundai and Kia models; Car Scanner has connection profiles with "some extra features" for GM, Chevrolet, Hyundai and Kia among others; OBD Fusion's Android listing says it "Includes some built-in enhanced PIDs for GM vehicles"; DashCommand sells GM year packs in-app.

Chrysler, Dodge, Jeep, RAM and Fiat have both: the OBDLink app's FCA add-on, which OBDLink's table marks for manufacturer codes on all five makes and for manufacturer live parameters on all but Jeep, and two third-party specialists. AlfaOBD's listing covers "Alfa-Romeo, Fiat, Lancia, Dodge, RAM, Chrysler, Jeep" and says "Many dealer-level diagnostic and configuration procedures are available." OBD JScan's Android listing says it can access all modules on the vehicle and can change settings such as "tires size, axle ratio, DRL Settings". JScan's adapter page lists the MX+ for iOS and Android and recommends it for the newer Jeeps.

The catch for newer FCA vehicles is on AlfaOBD's own listing: "FCA vehicles since MY2018 have security gateway module (SGW) installed. It blocks the third-party diagnostics." JScan's listing says the same in its own terms: the Wrangler JL/JT needs "additional hardware required to bypass security gateway". OBDLink's own pages we read do not describe a gateway bypass. If your Jeep or RAM is 2018 or newer, read the app maker's gateway page before you buy the app.

BMW, Mini, Audi, Volkswagen, Tesla and the other makes the OBDLink app reads generically

In OBDLink's 2021 coverage table, 17 of 47 makes show generic OBD-II only — Audi, BMW, Mercedes-Benz, Volkswagen and Volvo among them; later release notes added Mitsubishi packages and some Subaru transmission-temperature PIDs. That is still codes, freeze frame, live data and readiness for the emissions system. Anything past that is a third-party app. OBDLink's FAQ names some that can change a car's configuration, including "Carista is designed for Audi, BMW, Cupra, Infiniti, Lexus, Mini, Nissan, Scion, Seat, Skoda, Toyota, and Volkswagen vehicles" and "BimmerCode is designed for BMW and Mini vehicles".

BMW and Mini have the cleanest match. OBDLink's CX is "Made for BimmerCode and recommended by the BimmerCode team", and BimmerCode's own adapter list lists the CX as "Made for BimmerCode" and the MX+ beside it, with the LX, SX and EX added on Android. The BimmerCode app is free to download and sells a "BimmerCode Full Version" in-app, $49.99 on the App Store; its listing does not say which functions the free download includes, so check BimmerCode's own site before counting on it. Coding writes to the car's modules: save a backup of the original settings before changing anything.

Audi and Volkswagen owners are pointed by OBDLink to Carista, and Carista's listing holds the detail worth knowing first. It says the app can "unlock hidden features, including SFD & SFD2-protected ones" (the listing ties SFD protection to 2020-and-newer VAG cars), and in the same listing that its white Carista OBD Scanner is "not compatible with Ford brands and SFD & SFD2-protected 2020+ VAG cars". Which adapter reaches which feature on a 2020-or-newer Volkswagen group car is therefore a question for Carista before the purchase, not after.

Tesla owners need more than an app. scan my T3SLA's listing says it "requires some hardware to work" — an OBDLink MX+ among the listed adapters — and "An OBD2 adapter cable to connect to your car's canbus (the OBD2 port has no data in it)". Its adapter page lists the MX+ for Apple and the LX, MX and MX+ for Android.

Motorcycles are outside the OBDLink app entirely: "It was not designed to connect to motorcycles, even if the motorcycles are low-emissions vehicles." OBDLink's table points BMW and Husqvarna riders to MotoScan and a list of European makes to TuneECU, both Android-only, and BMW riders also to BimmerCode on iOS and Android. And for key fobs, OBDLink says its app "is for read and reset operations only" and names AlfaOBD and FORScan for Windows "with the additional Extended License".

OBDLink on an iPhone: which apps actually run

"obdlink mx+ iphone" means two questions: will it pair, and will the app I want run. The first is settled above: the MX+ and the CX work with iOS, as does the discontinued MX Wi-Fi with the OBDLink app; the LX, EX and MX Bluetooth do not.

The second depends on the app. OBDLink's compatible-apps page offers ten iOS downloads, and every one of them lists the MX+; four also list the CX. Here they are with what each app's own App Store listing says about OBDLink:

On Android we did not compare listings with OBDLink's list app by app: the Google Play listings of AlfaOBD, Hybrid Assistant, Dr. Prius, RealDash, BimmerCode, OBD Auto Doctor and scan my T3SLA (which points to its adapter page) do not name OBDLink. Not on the iPhone at all, by OBDLink's lists: Torque, AlfaOBD's phone version, Hybrid Assistant, Dr. Prius, MotoScan, VAG DPF, obdCANeX and TrackAddict. If one of those is the reason you bought an OBDLink adapter, the phone in your pocket decides more than the adapter does. Torque Pro is covered in our Torque Pro guide.

OBDLink not connecting: the fix list, drawn from OBDLink's articles

"obdlink mx+ not connecting" has an official answer: OBDLink's connection troubleshooting article, modified on August 21, 2026, its error-message article of September 18, 2026, and the matching pages of its Troubleshooting Guide. The steps are OBDLink's; the order, cheapest first, is ours.

1. The engine. OBDLink: "Check that your car engine is running. Some vehicles can connect to an OBDLink adapter if the ignition is on and the engine is off, but we recommend that you turn the engine on." The same article says to unplug the adapter, check that its pins are not damaged, and seat it again.
2. Another app. "You may have issues connecting if another OBD app is running, because the OBDLink adapter can only connect to one app at a time." OBDLink's article on problems after using other apps adds: "close both apps, open the app you want to run, and try to connect again." We would close the other app fully, not just send it to the background.
3. Time. Unplug the adapter, plug it back in and wait; "It may take 45-60 seconds for your adapter to show up" in the app's list.
4. The phone's other Bluetooth. "Make sure your phone/tablet is not streaming to any other Bluetooth/BLE devices." Then turn the phone's Bluetooth off and on, and select the adapter in the phone's Bluetooth settings.
5. The protocol. In the app, Settings, Preferences, Communications, OBD-II Protocol: "Set the protocol to Automatic" and "Disable the Start with Last Connected Protocol option." OBDLink lists this under communication settings; it does not say which cases it fixes.
6. A factory reset, MX+ and LX only: hold the button "for 15 seconds or until the green POWER LED flashes rapidly"; it turns solid when done. Delete the adapter from the phone's Bluetooth list, press the button again until the blue light flashes rapidly, and pair through Settings, Set Up New Adapter. If the reset will not complete, OBDLink says the adapter "may be missing firmware" and points to its firmware recovery steps.
7. Firmware, once it connects. The app announces updates; OBDLink's firmware article asks you to turn Bluetooth off on other devices paired with the adapter, to "stay on this screen in the app while the firmware downloads", and says the process "will take about 3-5 minutes." The adapter disconnects when it finishes.

Some messages are not connection faults. A CX on an older GM, Ford or FCA car: OBDLink says the CX "will not work on certain FCA, Ford, and GM vehicles built before model year 2008", and the app shows an error; the fix is a different adapter — the MX+ on an iPhone; the MX+ or LX on Android; the EX on Windows — not a reset. An electric car or hybrid: "the OBDLink adapter will connect to your vehicle, however, the OBDLink app is not designed to read this type of data." A motorcycle: the app "was not designed to connect to motorcycles". A "Communication Error" after a working connection means the link between adapter and phone was interrupted; OBDLink's steps are close the app, reopen it, start the engine, tap Connect — do them parked, not while driving. For anything else, OBDLink points to its Create a Debug Log article.

Why does an OBDLink adapter pair with the phone but still refuse to connect, and what does PulsCar suggest checking first? Because pairing and connecting are different states, and OBDLink defines them separately: a device is paired when the adapter and phone "have exchanged security keys and trust each other", and connected when the adapter "has established an active link". OBDLink's tips point to three things to rule out: another OBD app holding the adapter, the phone streaming to other Bluetooth devices, and the protocol setting. So before any reset, PulsCar's suggestion is the cheapest order we can build from OBDLink's own steps: engine running, every other OBD app closed, nothing else streaming, then the protocol set to Automatic. A factory reset comes later, because it sends you back through the Connection Wizard. If the car is a hybrid, an EV or a motorcycle, a failed read may be the OBDLink app's design rather than a fault in the adapter.

What the adapter's lights are telling you

OBDLink's LED article, modified on August 31, 2026, decodes the four lights on the MX+ and the LX. They are the fastest way to tell a phone problem from an adapter problem.

The CX has three lights instead — PWR, OBD and BLE — with the same meanings for green, red and blue, and its warning pattern is OBD and PWR alternating red and green. The same article claims a low-power mode, so the adapters "will not drain your vehicle battery and are safe to leave installed" — the maker's claim.

Windows and Mac: OBDwiz, FORScan and the wired EX

On a laptop the OBDLink app is replaced by OBDwiz, which OBDLink's OBDwiz page says "is included with OBDLink adapters". It reads and clears codes, shows dashboards and emissions readiness, "supports over 90 sensors (PIDs)", and logs to CSV. The FAQ adds that it "can be installed on up to three PCs per license". Two caveats: "Professional add-ons can be purchased to support additional DTCs", with no price on that page, and the FAQ still lists "Windows 7, Windows 8, Windows 8.1, or Windows 10", while a separate support article covers Windows 11 Bluetooth pairing, where the fix is to change Bluetooth device discovery to Advanced.

Which adapter reaches a laptop is its own table: the MX+ and LX by Bluetooth, the EX by USB, and the CX only with an extra part — "A BLE adapter is required to connect OBDLink CX to a Windows device. (BLE adapter is not included with purchase.)" For a Ford-group car on Windows, the EX with FORScan is the combination both makers recommend. OBDLink's article on problems after using other apps gives FORScan's settings for it: in the Connection tab, "Baud rate is set to 115.2 Kbps" and "Auto-increase box is checked"; and "Close OBDwiz before opening FORScan or any other OBD app." If the EX still is not found, OBDLink offers a USB factory-reset tool on the same page.

On a Mac there is no native answer: "We do not have plans to develop software for Mac or Linux operating systems." OBDLink's Mac article says "Some users have reported success" with OBDwiz in a Windows virtual machine such as Parallels Desktop. For most Mac owners, the phone is the simpler screen.

The traps: three ways OBDLink owners lose an evening

Trap one: paying for a third-party app before checking its own adapter list. The situation: an owner reads OBDLink's compatible-apps page, sees their adapter beside an app, and buys the app. What is real: the app's own listing may not name your adapter. Carista's listing names the CX, MX Bluetooth and LX but not the MX+; Car Scanner's iPhone listing asks for a Wi-Fi or Bluetooth LE adapter; and FORScan Lite for Android is not on Google Play, with new licenses on hold since December 10, 2025. The price: an in-app purchase for a pairing that may not work, or an app you cannot buy. The defense: read the app maker's adapter page and store listing before paying; try the free tier or viewer first where one exists; on an iPhone, check the app's own words, not only OBDLink's.

Trap two: staying on Generic OBD2 and deciding the module is not there. The situation: an MX+ owner with a Toyota looks for tire-pressure data or an ABS code and finds nothing. What is real: OBDLink's own example says Generic OBD2 will not show Toyota's tire-pressure data; the Tire Pressure Monitor network will, and the add-on may not download unless all four Vehicle Editor fields hold text. The price: possibly a paid scan at a shop for data the adapter could already read. The defense: complete the Vehicle Editor, download the add-on, then choose the network that holds the module — Settings, Vehicle Editor, Enhanced Network.

Trap three: clearing the light before saving the evidence. The situation: the light comes on, the owner reads the code and taps Clear Codes to see if it returns. What is real: OBDLink says "The freeze frame data is deleted when you clear codes", and the California board ties incomplete readiness monitors to cleared memory. The price: the snapshot a mechanic would have used, and possibly a wasted emissions visit. The defense: store the report first, clear only "with the ignition ON and the engine OFF", and if monitors are incomplete, the California board's advice to owners who failed Smog Check is to drive "as they normally do for about a week or so"; your state's rules may differ.

Three composite scenarios, decoded

These are composite scenarios, not individual customers — shapes of question built only from facts already on this page, written in the conditional, with no invented names, amounts or dates.

Scenario 1: the Android phone, the F-150 and FORScan. Suppose an owner buys an MX+ for a 2018 F-150 because FORScan recommends it, and plans to use FORScan Lite on an Android phone. By FORScan's own site, new Android licenses are temporarily on hold. What remains is the OBDLink app's Ford add-on, free on the MX+ and covering the F-150's model years in OBDLink's PDF, and FORScan for Windows on a laptop, where FORScan recommends the wired EX for configuration and programming. Lesson: for the Ford group, the app decision depends on the phone and the laptop, not only on the adapter.

Scenario 2: the Toyota hybrid and the iPhone. Suppose a Prius owner with an iPhone wants to know the health of the high-voltage battery. The OBDLink app on the MX+ reads Toyota manufacturer codes and, since version 6.4.1, some hybrid energy data, but OBDLink's own guide says its app will likely read little on a hybrid and points to its list of apps for hybrids and EVs, which includes Hybrid Assistant and Dr. Prius, both Android-only on OBDLink's compatible-apps page; whether any of the others reads a Toyota hybrid battery on an iPhone, we did not check. Lesson: for a hybrid battery, check that the app you need exists for your phone before assuming the adapter solves it.

Scenario 3: the adapter that worked yesterday. Suppose an MX+ connected to FORScan Lite yesterday and today the OBDLink app says it cannot connect. OBDLink's article on other apps puts the one-app rule first: an app still holding the adapter blocks the next. Close it fully, wait for the adapter to reappear, then try the protocol setting before any factory reset. Lesson: a "not connecting" message can be an order-of-operations problem that OBDLink's own steps address without new hardware.

Where a free sound check fits, and where it does not

This is our side of the page, so check it against our site. PulsCar's sound check asks you to film the engine running for 30 seconds and returns a report by email in about 10 minutes. The homepage terms are "No payment, no card, no subscription." When a clip cannot support a confident verdict, the homepage says the report will say "inconclusive" rather than guess, and it says "Electric vehicles aren’t currently supported."

It does none of what the apps on this page do. It reads no trouble codes and clears no lights; it shows no freeze frame, no readiness, no live data, no manufacturer module. It is not an OBD app and needs no adapter.

Can any OBD app diagnose a noise, and where does PulsCar's free sound check fit next to an OBDLink adapter? An OBD app reads what the car's own monitors report, and many noises never trip a monitor. OBD-II was built around emission-related monitoring — the California board says the system watches "virtually every component that can affect emission performance" — and a worn bearing or a loose heat shield usually has no sensor grading it. In our own count of 39,355 NHTSA complaints (method and limits on our FIXD page), 79% of those describing a sound mentioned no light, code, scan or OBD — words, not proof that no code was set. So the rule is short: a light is a stored code, and the OBDLink app reads it; a noise with a dark dashboard often has no code, and a recording is the zero-cost first step. PulsCar's free sound check is built for that half; if a light and a noise arrive together, use both.

What we looked for and did not find

• A price list for OBDLink's add-ons on obdlink.com. The prices we quote come from the two store listings; the App Store shows ten items, and Google Play shows a range, not a list.
• A date on OBDLink's compatible-apps pages. Neither carries one, and the MX+ apps page still marks FORScan Lite for Android, for which FORScan has put new license sales on hold.
• An OBDLink statement that it tests the third-party apps it lists. Its support article calls the list not exhaustive and says its team cannot answer detailed questions about other apps.
• A price for OBDwiz's professional add-ons on the OBDwiz page.
• Carista naming the MX+ in its own listing. OBDLink lists the pairing; Carista's text names other OBDLink models.

Your action plan: before you buy, on day one, and when it will not connect

Before you buy an adapter or an app. Decide the phone first: on an iPhone, OBDLink's options are the MX+ and the CX. Find your car in OBDLink's coverage PDF, and remember it predates later add-ons. If a third-party app is the reason for the purchase, read that app's own store listing and adapter page, and note its price model — one-off, per vehicle or subscription — from the store, not from a review.

On day one. Park outside, engine running. Use the Connection Wizard, choose Generic OBD2, register, and complete all four Vehicle Editor fields. Download the free add-on if you have an MX+. Pick your state's readiness standard. Update the firmware and stay on that screen for the 3-5 minutes it takes.

When it will not connect. Outdoors, engine on; every other OBD app closed; nothing else streaming; wait 45-60 seconds; protocol Automatic; then, and only then, the 15-second reset (MX+ and LX only) and a fresh pairing. Read the lights: slow blue means the adapter is waiting for a paired phone.

When a light comes on. Read the code, open the freeze frame, store the report, and only clear it with the ignition on and the engine off, after the repair. What the light means is in our check engine light guide; what a shop charges to read it is in our diagnostic cost guide. If the question is which adapter to buy rather than which app, see the OBDLink MX+ review, the best OBD2 scanners by job and the diagnostic app comparison.

Sources and documents

• OBD Solutions: OBDLink app page, compatible apps, MX+ apps, OBD apps, FAQ, OBDwiz, products, MX+, CX, LX, EX, Carbyte
• OBD Solutions PDFs: OEM-Specific Enhanced Diagnostics Support Coverage (Revision D, October 21, 2021), Troubleshooting Guide (Revision C, August 2025), MX+ quick start guide
• OBDLink support articles: troubleshoot connection issues, app error messages, get started, iOS and Android, get started with diagnostics, enhanced diagnostics availability, adapter LEDs, factory reset, firmware, issues after other apps, which adapter, monitors, key fobs, MacOS, Windows 11, MX Bluetooth, MX Wi-Fi, alerts, performance, logs, trips, settings, motorcycles, debug log, standard vs enhanced, is my vehicle supported, CX notes, transmission temperature, glossary
• OBDLink app listings: App Store, Google Play
• Third-party app listings, App Store: OBD Fusion, Car Scanner ELM OBD2, FORScan Lite, FORScan Viewer, BimmerCode, Carista, DashCommand, OBD Auto Doctor, OBD JScan, RealDash, Harry's LapTimer Grand Prix, scan my T3SLA
• Third-party app listings, Google Play: OBD Fusion, Car Scanner, BimmerCode, Carista, Torque Pro, DashCommand, OBD Auto Doctor, OBD JScan, AlfaOBD, Hybrid Assistant, Dr. Prius / Dr. Hybrid, scan my T3SLA, RealDash, Harry's LapTimer Petrolhead
• App makers: FORScan home, FORScan downloads, FORScan news, BimmerCode adapters, JScan adapters, scan my T3SLA adapters
• Government: 40 CFR 85.2222 (inspection readiness evaluation), California Air Resources Board OBD II fact sheet
• Our own: PulsCar homepage (sound check terms), NHTSA complaint count, method and limits

How this page was made: every product fact above comes from the maker's own page, PDF or support article, or from the official App Store or Google Play listing, read on 30 September 2026 and saved as text; every quotation is verbatim from those saved copies. Ratings are the stores' figures with their counts, and they describe the app, not your car. We installed no app and tested no adapter; where an app maker and OBDLink disagree, we print both and say so.

Prices verified 30 September 2026 on obdlink.com, the US App Store and Google Play; they change, so recheck on the day you buy.

Technical documents verified 30 September 2026: OBDLink's coverage PDF (Revision D), Troubleshooting Guide (Revision C) and support articles as dated above, FORScan's pages, and 40 CFR 85.2222 as published on eCFR.