'88 - OBD I computer hardware/software to read the interface
Thread Starter
Burning Brakes
Joined: Jul 2009
Posts: 1,184
Likes: 40
From: Overland Park, KS
2017 C4 of the Year Finalist
'88 - OBD I computer hardware/software to read the interface
I'm in the early parts of working on a code 42 on my dead stock '88 Anniversary that has an L98 350 engine. It's very hard where I live to find any place to even get an ODB I code read - I finally found one through a neighbor but it seemed like an imposition for them to do it.
While I had hoped the vendor(s) would be of more help I've found I need to call on my past career as an IT software and hardware specialist. I purchased a OBD I to USB cable, installed the driver for the chip that's "buried" in the cable and installed several software packages on my Windows 10 64 bit laptop.
I gotten WINaldl to work so far but I had to use the 10K resistor option to accomplish this. I also have TunerPro installed but it hasn't worked so far but it's also a more complex package. While there are websites this whole thing seems to need better documentation as the ECM chips, cable settings, files needed, etc.
More later.
While I had hoped the vendor(s) would be of more help I've found I need to call on my past career as an IT software and hardware specialist. I purchased a OBD I to USB cable, installed the driver for the chip that's "buried" in the cable and installed several software packages on my Windows 10 64 bit laptop.
I gotten WINaldl to work so far but I had to use the 10K resistor option to accomplish this. I also have TunerPro installed but it hasn't worked so far but it's also a more complex package. While there are websites this whole thing seems to need better documentation as the ECM chips, cable settings, files needed, etc.
More later.
Team Owner
Joined: Dec 2000
Posts: 90,675
Likes: 304
From: SE NY
Cruise-In II Veteran
Where did you get your h/w, s/w??
I also have a 35th Anni and my AutoXray recently died so I need to pick up materials so I can use my Win 10 laptop for diagnosis.
Thanks for any help.
I also have a 35th Anni and my AutoXray recently died so I need to pick up materials so I can use my Win 10 laptop for diagnosis.
Thanks for any help.
Thread Starter
Burning Brakes
Joined: Jul 2009
Posts: 1,184
Likes: 40
From: Overland Park, KS
2017 C4 of the Year Finalist
The first vendor that I tried that is in the midwest never responded to my emails or voice mail message. I ended up with buying it from: http://www.aldlcable.com (appears to be same as http://www.obd2allinone.com).
The WINaldl software is from: http://winaldl.joby.se/ - note that the version 1.09f is dated 1/13/2007 - rather obviously no longer being developed. I didn't have to use compatibility mode on my Win 10 64 bit laptop which indicates to me that the code was well written. The chip driver shows as FTDI, date 6/16/2016, version 2.12.18.0 which I installed off the unlabelled CD that came with the cable by running CDM21218_Setup.exe - I personally dislike unlabelled CDs but I haven't noticed any malware.
The tunerpro software is from: http://www.tunerpro.net - this is much more complex and I've got to get my '61 ready so I'm not working on it right now.
Digging out the ECM involves some research. The Service Parts Identification indicates an L98 engine as the original - mine is also a numbers matching engine. For 1988 the ECM is 1227165 which is all WINaldl needs.
The vendor says to use hyperterminal if you can't get data but like other great Windows components it's been removed by Microsoft (sad). I downloaded hype!terminal from sourceforge. When I worked my favorite was putty to access systems that used serial comm and I think it would actually work well.
The comm port (COM3) setup is 2400/8/none/1/none while the WINaldl setup is COM3 at 4800 (really?). When have more time I will take a better look at this. The COM3 setup is the default from the driver install - it should be fine to leave it there forever.
The WINaldl software is from: http://winaldl.joby.se/ - note that the version 1.09f is dated 1/13/2007 - rather obviously no longer being developed. I didn't have to use compatibility mode on my Win 10 64 bit laptop which indicates to me that the code was well written. The chip driver shows as FTDI, date 6/16/2016, version 2.12.18.0 which I installed off the unlabelled CD that came with the cable by running CDM21218_Setup.exe - I personally dislike unlabelled CDs but I haven't noticed any malware.
The tunerpro software is from: http://www.tunerpro.net - this is much more complex and I've got to get my '61 ready so I'm not working on it right now.
Digging out the ECM involves some research. The Service Parts Identification indicates an L98 engine as the original - mine is also a numbers matching engine. For 1988 the ECM is 1227165 which is all WINaldl needs.
The vendor says to use hyperterminal if you can't get data but like other great Windows components it's been removed by Microsoft (sad). I downloaded hype!terminal from sourceforge. When I worked my favorite was putty to access systems that used serial comm and I think it would actually work well.
The comm port (COM3) setup is 2400/8/none/1/none while the WINaldl setup is COM3 at 4800 (really?). When have more time I will take a better look at this. The COM3 setup is the default from the driver install - it should be fine to leave it there forever.
