OBDII Scanner can't connect(Resolved)
 

I have tried 4 or 5 different scanners and they all have the same message. "Error communicating with vehicle".
I have checked the following on the ALDL port,
pins 4 and 5 for ground, pin 16 for 12 volts with key on and I verified continuity from the blue PCM harness pin 7 to ALDL pin 2.
The car runs and drives fine but the SES light is on and it's running rich.

I may be wrong. But as far as I know, the pre 98' F-Bodies are OBD I. They may have an OBD II Plug but are ODB I.

-Mat

1996 was the first year for OBDII.

Have you connected to it before using an OBDII scanner?
96 & 97 LT1s can be converted to OBDI and still use the OBDII connector, just like the 95 LT1s, which came from the factory as OBDI with an OBDII connector.

Yes I have scanned it many times.
This problem started after I installed the engine out of a 95 Firehawk. I used my PCM and harness. The 95 doesn't have a Crankshaft position sensor so that would be a DTC. I installed my EVAP solenoid, coil and a new 96 Knock sensor. My rear O2s have been disabled in a previous tune by Madtuner.

TTT

Any ideas?

I had same problem and was pulling hair when guy to me to check cig lighter cause obdII shares same fuse and sure nuff fuse was bad replaced it and problem solve, hope this helps.

check your fuses

anyone got the 100$ :P

lol sorry wrong thread HAHAHAHA

Problem solved!
Put this one in the "Dumbest things I've done" thread.
Here's what happened. During the time I was swapping engines, I ended up with 3 PCMs. One was my original(OBD2), one was out of the 95 Firehawk(OBD1) that I parted out and a 3rd one. I had marked each of them, but, somehow I switched the 96 with the 95 and installed it in my car.
I discovered this when trying out the other PCMs to see if the one in the car was fried. The car ran better and I checked the service numbers and Voilla!
All the pieces of the puzzle fell together after that. The high idle, running rich, the ALDL port not working, etc.