i have a 95 gs fully rebuilt with a hahn super 20g ... the thing is that we can get codes by doing a key dance, basic scan tool or the genisys scan tools .. but we cant get into anything else at all with the genisys to datalog or even get any parameters. it seems that i have a bad connection with my obd 2 connector in the car ... is there thing we can do to fix this. I've searched through and couldnt find anything except that it could possibly be the door lock fuse and it was double checked and works fine. i had an alarm installed prior to the turbo rebuild and install but they assured me that they hadnt touched anything connecting to the pcm. someone helpp :(

Those huge Genysis scan tools are junk.

We used to have those at my work for cars that came into Service that were not Chevrolet's and we could never get into anything else besides the PCM or Body Control Modules. Half the time, we couldnt even get into the EVAP systems.

Have you tried a different scan tool (A good one, like Snap On) ?

no i havent but i can get one from my friends work to try... i threw out code 21 first than replaced my o2 sensor and that got rid of some of the problems but then i kept getting code 43 and 44 . 43 we fixed ignition wires were grounding to the hood. and now we got 15 vss. and it just stopped working all of a sudden. im just getting fusterated with all the codes that keep comming and wanted to get into the pcm somehow and get everything checked out. any ideas ??

The thing about it is that the 95 while it does have an OBD-2 style port it is OBD-1. So you have to use a scanner (Like the Snap-On) that can read the OBD-1 but has an adaptor for the OBD-2 plug.

-Kevin

will the snap on solus one work ? anyone have any idea about where to get a new vss or how to test it for resistance ?

Originally posted by shazow1969
The thing about it is that the 95 while it does have an OBD-2 style port it is OBD-1.

That's not true. While the 95's may not have been fully OBDII compliant (emissions-wise) they are all perfectly capable of communicating with any OBDII datalogger/scantool.

I don't have a lot of experience with expensive commercial scantools (although we did use the SnapOn scanner semi-frequently in the shop), but I have made a few of my own dataloggers from scratch... You can try a bare bones approach to communicating with your ECU via the logger to rule out any breakpoints in the wire harness, etc..

There is a pink wire that runs from your ECU to your OBDII plug. That's the K bus line. If you can connect that wire to pin 7 on the scanner, and connect pins 16 and 5 to a +12V source and ground, respectively, that should be all you need to get all the supported OBDII data.

thanks that sounds alot better... im really not hoping that there is a break in it .. although im kinda thinking there is because i have faulty connections with a basic scan tool and had to wiggle it to even get a code ... (

I recomend Solus or Modis. Stay away from the Mentor. The Mentor is crap.