I received the OBDLink SX USB adapter today in the mail. The adapter was well packaged and fast shipped.
On initial inspection the adapter appears to be well engineered and it sports red semi-translucent cord insulation covering a braid shielded USB cable. The adapter itself is also enclosed within a red semi-translucent box. It feels good in the hand, its nice and its a bit sexy too. Heh heh.
To support my diagnostic effort to fix my 2003 Ford Escape which has been towed into the Ford dealership four times, yet their technicians have been unable to diagnose the intermittent failure, I purchased the following to (hopefully) enable my own diagnosis of the problem:
1x set of red Ford service manuals:
- 2003 Escape Workshop Manual
- 2003 Escape Wiring Manual
- 2003 Ford Car/Truck Powertrain Control / Emissions Diagnosis Service Shop Manual
1x HP 8640 EliteBook 35,56cm/14" Win7 (Home-Premium...yech!) 'small' LapTop fits on passenger seat
1x ScanTools OBDLink SX USB Adapter
1x set of modification components from JameCo detailed in last post
Today I plugged in the SX into the LapTop, the adapter wasn't detected and the adapter status LED glowed RED. I looked all over the ForScan site for installation info, and aside from a fairly simple document which did not identify drivers I could find nothing too useful. However, I did seem to remember back when I first found ForScan a post regarding FTDI drivers.
I opened the Device Manager on the LapTop, plugging in the SX USB cable into the USB port, the Device Manager, emitted a yellow USB flag indicating a driver problem, along with a message stating that a USB driver was unsucessful installing.
I vectored over to the fellows at ftdi-chip for drivers:
Downloaded: Windows x86 (32bit) and x64 (64bit) drivers (for archive) version: 2.12.28 which includes both the VCP and the D2XX drivers, both of which are required for Windows 7 USB driver installation. Both are compressed into a zip archive file format. As my HP LapTop is a 64bit machine I installed the 64bit FTDI drivers. If your machine is Windows 7 32bit processor, install the 32bit driver.
To install the drivers I followed the FTDI Installation guide at:
I downloaded: "Windows 7 Installation Guide"
Driver setup installed perfectly first time.
To unzip the drivers file (CDM v2.12.28 WHQL Certified.zip), I downloaded and used the **EXCELLENT** www.peazip.org
peazip archiver program to unzip the files into a temporary installation directory. I have been using peazip for nine years. It opens and unarchives virtually everything.
After driver installation, I unplugged and re-plugged the OBDLink SX USB adapter cable and the status LED changed from RED to peuce YELLOW indicating that adapter is talking to the computer via the USB drivers. I have as yet to hookup the LapTop + OBDLink SX USB adapter to my car, which I'll do tomorrow. However, I did run the ForScan Windows Beta version 2.3.20 program, which initially did not connect to the SX adapter.
I fiddled around with the ForScan SETTINGS page, selecting
Connection Type: COM & checked Auto-Connect
COM Settings: Auto
Baud Rate: Auto
Exited the program and reinstantiated (eg, restarted) the program, which then scanned through the COM PORT enumeration table, finding COM5 and then connected the program to the OBDLink SX adapter!!! Yipee!
So that's it for now. As soon as the JameCo package of modification parts arrive in the mail, I'll make the mods, documenting as I proceed and take a few support photos for y'all.