For car enthusiasts and DIY mechanics, having an OBD2 code reader is essential for diagnosing car problems at home. When considering options for my 2020 Pacifica Hybrid, the price of the OBDLink MX+ seemed steep at $119. Discovering the OBDLink EX on sale for $40 during Cyber Monday sparked the question: could this cheaper, cabled option offer similar functionality, especially when paired with software like AlfaOBD?
The OBDLink EX is often highlighted for its compatibility with Ford, Lincoln, Mazda, and Mercury vehicles, particularly with ForScan software. However, the AlfaOBD website suggests it, along with the MX+, for Chrysler vehicles due to their MS-CAN interfaces. My hope was that the EX, used with Android scanning apps like alfaOBD and the OBDLINK App, would effectively support my Pacifica Hybrid. Being new to these diagnostic interfaces, I wasn’t sure if there were crucial details I was overlooking. (Note: Connecting the EX to an Android phone requires a USB to USB-C OTG adapter).
One practical concern arose immediately: the location of the OBD connector in the Pacifica. It appeared the EX adapter might dangle in a position that could be bumped or damaged when entering and exiting the vehicle. The wireless MX+ would certainly avoid this potential issue.
Despite the slight worry about the physical connection, the attractive price was too good to ignore. I decided to purchase the OBDLink EX. A YouTube video review revealed a 30% discount code, bringing the total cost down to a very reasonable $27.17 after tax when ordering directly from obdlink.com.
The OBDLINK EX arrived quickly after ordering. Initial testing began on a Windows 11 PC using ODBWiz software. Installing the USB drivers manually, as per OBDLink’s instructions, was necessary. The OBDWiz installation process wasn’t perfectly smooth, with a missing file folder that required manual creation to resolve errors. Despite these minor hiccups, a quick test on a 2004 Toyota Camry indicated basic functionality.
Next, I attempted to use the OBDLink EX with the OBDLink app on my Android phone. Unfortunately, the app did not recognize the cabled EX as a supported device. A support request was submitted to ScanTool.net, and their helpful team promptly asked for clarification, initiating the troubleshooting process. Early indications were positive that compatibility should be possible, but getting it working on Android was a priority, as a phone is much more convenient than a laptop for quick diagnostics. My Pacifica was unfortunately unavailable for testing with the alfaOBD app at this time due to repairs.
This initial experience highlighted that setting up a cheaper OBD2 reader like the EX might not be entirely seamless. It raised the question of whether the more expensive MX+ offered a more “plug and play” experience.
Further progress was made getting the OBDLink EX to function with ODBwiz on my Windows 11 laptop. The focus then shifted back to achieving Android compatibility. It turned out that the latest revision of the EX cable (version 2.2) had a compatibility issue with the current OBDLink Android app. The OBDLink help desk remained highly responsive and supportive throughout the process.
Finally, the resolution came! Within a week of identifying the compatibility problem with the newest EX cable, the OBDLink App was updated. This update successfully addressed the issue, and the OBDLink EX cable 2.2 now works flawlessly with my Android cell phone. The initial bumps in the road were overcome, and the cheap OBDLink EX proved to be a viable and cost-effective OBD2 code reader solution. The next step is to explore the alfaOBD app to fully utilize the capabilities of this affordable tool.
