S
ShaneL
Guest
Is there an economical way to read the DTC codes without having to shell out $500? This stupid light has ben giving me greif for the whole week and I can't figure it out.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You will still need to reset the light, this tool will not reset it.HTRK-1 said:Because you're car is a 1996, this may work for you...Not bad for under $40.
http://www.harborfreight.com/cpi/ctaf/Displayitem.taf?itemnumber=46030
In 1994, Chevrolet went to a 16 pin ALDL connector in preparation for the federally mandated change to the much more capable OBD-II (On Board Diagnostics - Version 2) system.
As with the 1990-1993 model, you can display codes on the speedometer but the pins to be shorted are different:
Beginning in 1994, you short pin "12" to pin "4" and once again turn the ignition switch to "On" without starting the engine.
The speedometer will display any codes using the same protocol as the 1990-1993 model but there are some changes in the designation for the modules plus additional modules are added:
Module "1" is still the CCM module.
Module "4" is now called the PCM module (Powertrain Control Module) because automatic transmission computer control was added to Engine Control Module in 1994.
Module 7 (on the 1996 model only) is the RTD module. (This is the Real Time Dampening module which replaced the Selective Ride Control module in 1996).
Module 9 is the ABS/ASR module number from 1994 through 1996.
Finally, Module "A", the DERM (Dynamic Energy Control Module --- the air bag control module) will be requested to show any codes.
Just like the 1990-1993 display, you read the codes on the speedometer and read the module number on the trip odometer.
Again, you can cause the codes to repeat by turning the ignition off for five seconds and then back on.
Turn the ignition off and remove the short to restore normal operation.
You did this on a 96 OBDII?ShaneL said:I was able to recover the cosed using this technique and I would like to know whast they stand for now. I got the following from module 1 the CCM. H31, H33, H35, AND H37.
Thanks for the help and I hope that some others can use this information.
Module 1 CCM DTCsShaneL said:I was able to recover the cosed using this technique and I would like to know whast they stand for now. I got the following from module 1 the CCM. H31, H33, H35, AND H37.
Thanks for the help and I hope that some others can use this information.
bnhynum said:Where did you get those code descriptions. I'm getting C12 on Module 1 then H48 and H42 on module 4.
Isn't that what's been said, i.e - get a scan tool for the PCM stuff (for shanel)? :confused CCM codes discussed do work well for many things.Skant said:Whoa whoa whoa! I also have a 1996, and I've been through this.
1996 was around the time that the switch from OBD1 to OBD2 happened. Many manuals say that the 1996 Corvette does not respond to OBD1 methods (like that shorting the pins trick)... but in fact it does.
HOWEVER...
You're only talking to _part_ of the computer. You're only seeing some of the elements that happen to still be compatible with OBD1. It doesn't _really_ work all the way... that's why GM says you can't use this mode. It's half baked. A remnant. A partially functional backward compatibility mode that they didn't disable completely. It doesn't really work, but it looks like it does.
And most importantly, it probably won't show you the information you're looking for. Even though the code is real and is not historical.
I'm afraid that if you want to know what's going on with your 1996, you'll need to get access to a proper OBD2 scanner. Sorry. No other method will work correctly.
OBD2 is dramatically more advanted than OBD1. And it has a zillion more fault codes. That's why any particular fault you get isn't likely to have any backward compatibility to appear on the half baked OBD1 backward compatibility mode. It's pretty useless. When I tried it on mine, the OBD1 stuff reported no fault codes at all. When clearly there was. In your case, you found some old historical OBD1 compatible codes, but that's not why your engine light is on. You just can't see the OBD2 codes that are tripping that light using that method.
Hope that helps...
- Skant