Make sure all 4 files have been extracted from the zip file before running. The "MALF.csv" file has to do with the DTC mapping. It tells the app where to find them in the received data string. It must be in the same folder with the scan9495.exe file.

 

I think i missed a file or 2 then. I will double check and try it again. Thanks for the reply.

 

Double checked and i have the malf and malf 93 csv files,txt doc and the app in the file. Still nothing as far as DTC reading

 

i had not dl ed v2.6, just tried that and it seems to be working properly

 

Version 2.6 only adds a few ABS actuators. Nothing to do with the DTC's.

 

Not sure what i had done wrong but it pulled a code immediately when i started the scan. thanks again.

 

Found it a great thread and had a question if this odb1 cable will also work with Chevrolet C/K 88-94 trucks?

 

No, it won't.

 

Hey,

Just wanted to say this is great stuff. I bought the Red Devil River cable just to avoid troubleshooting cable issues. Plugged it into my Win10 laptop and it loaded the driver automatically. Unzipped the software, fired it up, and it found the COM port automatically. Plugged it into the car, turned the key, clicked SCAN and it immediately worked. Couldn't have been easier!!!

Thanks for creating this software!

BTW, I have an M6. I don't know if you've gotten all the info you wanted for the M6 but if there's any way I can help, let me know.

John

 

Thanks for the kind words. Maybe I should make a list of testimonials like this one :-)

 

Thanks GaryDoug, Scan9495 and the cable idea worked great. I used them to fix my ABS brakes. I don't have a LT1 car, I have a 95 Buick Skylark with the same brake system, e.g. Delco VI. The EBCM on my Skylark looks different from the LT1 cars but Scan9495 still communicated and gave me the ABS diagnostic info I needed. I got the original idea to build the cable from your instructions but I built it a little differently per the youtube video "OBD1 LT1 USB programming data log cable $10". The cable also works with TunerPro which I am using for my engine since its not a LT1 engine.

As far as I can tell there is no other option for reading ABS codes for 94/95 GM cars like these other than getting access to a Tech I or OTC Air Bag/ABS scanner.

 

Thanks for the feedback OldFaithfull.

You really didn't need to use the resistor and diode shown in the video. Those are only needed for the full RS232 driver types. The simple FTDI-based device you have is not that type (it is TTL).

I preferred to use the adapter that is enclosed at the USB end so the adapter card is not out in the open, but some of those don't have the LED's anymore.

Keep in mind that the adapter may not work with the new FTDI drivers, so try to get a driver set from 2013 or older. My web site storage area has some.

 

I have read other users who had success without the resistor and diode, I simply haven't tried it that way.

The Windows driver updates are pretty much automatic and out of my control on my computer. So to avoid the FTDI driver/chip bricking war that has been going on I bought my FTDI device from a US distributor out of Dallas for $20.

 

The bricking is pretty much history now, but the latest FTDI driver will not work with a cloned device. It will not brick it. You can control the driver installations in the pc settings, but it is more difficult with Windows 10 now.

$20-$25 is the standard price for a genuine FTDI USB-TTL serial adapter. Here is one that works for a little less:

 

Gary, thanks for providing this valuable tool. I appreciate your hard work.

I'm hoping you can assist me with an issue I'm having with the program. I'm getting an error message that reads:

Unhadled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.


What am I doing wrong? Thanks for your help.