OBDLinkSX USB: Professional Grade OBD-II Automotive Scan Tool for Windows – DIY Car and Truck Data and Diagnostics

I have been using OBDLink SX for almost 10 years and it's been a great tool for diagnosing and troubleshooting problems on our cars over the years. Recently I had a technical issue that rendered it inoperable - probably a fault of my laptop. I wrote an email to tech support and received an answer back within hours (what other company does that?!). I'm back up and running. Years ago when I was shopping for this it was really difficult to distinguish between the many similar looking OBD readers. I'm so glad I picked this one- these folks are legit.

This does amazing with versatuner! It connects to it with no issue and takes heat well, the cord is nice and long for data logging

My review of the OBDLink SXIt would take too long to describe all that this Scanner can do, so some basics.It is far more than a Code Reader/ Eraser. This unit can read dozens of functions from your ECM (Engine Control Module). It is much like the expensive computers the car dealers have to diagnose problems.The OBDLink SX does the scanning, but you need to connect it to a Laptop, Ipad or smart phone to run the free diagnostics program.This version of OBDLink's scanners, connects via USB. It's the fastest, but other models use WiFi or Bluetooth, if you don't want the cord (more expensive).Beyond doing Trouble Codes, it does a nice job of displaying and logging the graphics of any readings. The screenshot is a 10 second piece of a 20+ minute recording of a sample drive. I put Timing, RPM and Manifold Pressure in my chart, but you can display and record in any parameters you want.I save the graphic charts in "ICloud", so the info is immediately available to me on my other computers, for analysis at home.For the best expert explanation of this device, view the video at:Oops, sorry, can’t show link, but look up “tested obdlink sx” on youtube.I don't have any connection to the company, I'm just enthusiastic about this capable, affordable device.

My purpose to buy / try this device was due to it’s very low price, plus having a couple of laptops setting around, and my 2005 Jeep that I bought new, I hope will last longer then I do. So I felt having the means to decode error codes (check engine) and the ability to turn off that light when it comes on.It came UPS in 3 days, with the ONLY documentation I could find for the OBDlink SX. Simple 6 step, easy to follow instructions, but not as reliable as one might think.So I set off to install on my Dell, Studio, Laptop, 4GB memory, 450 GB hard drive, operating using MS Vista Home Pro, 64 byte. I have been using this computer for over 8 years now, but it's now just a back up.1st, step is to install drivers. So put the disk in the drive, up came the same screen as the instruction. This will be easy, I thought. So following the instructions, I selected SX, then MS software, then install drives. This took a really long time to accomplish, but at least the on-screen feed back was enough to wait it out.Finally it finished, and the screen said the drivers had been loaded.Step 2 in the instructions, “Connect scan tool to PC”. This was the beginning of my journey. The instructions state if drivers were installed correctly, the status indicator should turn yellow. Actually it was off, until plugged into the PC, USB port, then came on yellow, or almost yellow, but not really red (unless you hold the device with the DLC connector up, then the led is mostly red.) This was where I thought this would be a piece of cake. I was wrong.As it turns out, when plugged into any USB port the yellow led lights, the drivers are not needed.Moving on, the instructions 3 & 4, are plugging the scan tool into the vehicle DLC. This is where things really started down hill for me.When plugged in properly, the scan device visual indication is facing the floor, and to low to see without being a contortionist, but the led signal never turned red, with the vehicle key on or off. Still yellow or greenish, but no real change by turning on the key.Here I noticed the instructions jumped to installing the software, so on to the software installation.Well simple enough, click on “OBDwiz” and start through a normal installation routine. 1st a couple of menu boxes flashed by, then “Select installation folder ~ C:\Programfiles (x86)\OBDwiz - “browse or other”, click <next> Confirm installation, clicked <Next>Next the License agreement ~ “I accept”, then click <next>That was the last indication of any feedback of the software being installed. Nothing else, - zippo, just the main OBDLink SX screen. Nothing seemed to be happening but I waited for about 15 minutes after the driver upload experience, nothing.No indication that anything happened, no OBDwiz directory in C:\Programsfiles (x86) directory, nothing in the Start menu area.The Quick Start sheet held no clues as to what to do. So I simply repeated the whole process again, and then again. Nothing changed.So I go on-line, send an email to Scantool.net, “help”. They reply within 24 hours, go to site and download latest version of the software.In the meantime, after sending off the email, I decided to try loading the software on my desktop, another Dell, Inspiron running MS Windows 7.The software loaded like the instructions said it would. In fact I started the program, entered my license key, and everything was great.As this seemed to be a pretty simple software package, and really just controls/reads the scan devise, I decided to try to copy this package to my laptop, using an external hard drive. I did, and it worked! The Laptop took the software like an old DOS machine. I only had to make a shortcut with the OBDwiz icon on the desktop and we were in business.This is when I found out that installed drivers stuff was a joke.When I plugged the scan device into the PC USB port I got a message that I had to install the drivers, which I ignored, knowing I had already installed the drivers in step #1. Big mistake.So I took the PC, scan device and set up in the Jeep. When I tried to connect, I kept getting device not connected or has failed.So left with little else to do, decided to go ahead and comply with that load drivers warning.The 1st time, the initial indication was “drivers installed successfully”, but when I tried to connect got a new message, but amounted to couldn’t find / use the scan device, and something about part of the device was working but part was not.So after a new bootup, I selected to find the needed drivers once again.This time, the outcome was a lot better, in fact “USB, COM 5 ready for service”, was reported.So back to the Jeep, turn on the key, and hit connect! Got device not ready / responding, after trying a half dozen different baud rates.Since the Jeep was not running, and I knew a scan code reader doesn’t read until the motor is running, so I started the engine, and hit connect.This time the scan device locked onto the DLC and my data was being displayed on screen.So after only about 4 hours and lots of luck, my simple plug & play was playing.I have been dealing with computers since before the PC came on the market so have been experiencing these types of event for over 30 years.

My 2012 Jeep Sahara with factory radio did not have a rear view backup camera so I purchased one from Amazon along with this OBDLink SX USB cable and downloaded Appcar DiagFCA software (Requires a $29 VIN license fee) and I got it to work.

Works great!But Didn't work on windows 7. Frame work was an issue. Drivers didn't work right. Firmware may be the issue. I tried it on 2 windows 7 PCs same thing, both times. As soon as I updated it to windows 10, boom it worked.