Hey Team, I was trying to track down why my 95 Talon ESI tries to cut/hesitate sharply while I am driving sometimes. Love the car, but the problem is getting on my nerves. So I did the keydance and got code 12 and code 36 before the ending codes of 5 and 5.

How do I fix these problems? On top of that, I tried to get my car diagnotic scanned and found out that I have a OBD2 plug (or atleast that is what fits it), but no reading at all (meaning the scanner will not even come on and register). Tried 2 of those and the second one came on, but it asked me to connect the scanner to the plug. Problem is, it was already plugged up to it at the time. So I took the car to a place where they had an OBD1 scanner. Pretty much the same result happened (didn't register at all). So my question now is..., what scanner works well with the 1995 Eagle Talon ESI? Thanks in advance for all your help and ideas.

myndvast

Welcome to the world of 95s. I'd check your coil pack, your ecu, your spark plug wires, your spark plugs... etc.

Every 95 i have ever worked on scanned as OBD2. Thats your problem.

Think of it as OBD2 without all the features of OBD2. Transitional year, not all the programming was complete for mitsu/Eagle.

If you're using the scanner have it set for a 96 not a 95. That's what I usually have to do to get my 95 to read. Depending on the brand of scanner you may have to have the car running.

Edit: I wouldn't worry about those trouble codes. 12 means that the battery has been disconnected recently and 36 is for the pulsed secondary air injection that was recalled and should have been removed years ago. You might want to check with your local dealer to see if that recall was ever performed on your car.

As far as the stuttering goes I'd do a normal check on the usual suspects, pull the plugs and see if there's signs of misfire, wear, lean or rich running. If I were to bet money I'd guess that you had the same issue my 95 has had before... dirty ass injectors.

Does it feel like it's falling on it's face for a split second especially under acceleration or at a specific RPM range?

You can get the super expensive dealer service that costs ~$150 or mix up your own fuel coctail to clean things out for about 1/3 of that cost.
Here's my recipe:
1 5 gallon fuel jug
1 can BG44K
1 qt Lucas fuel system cleaner
1 small bottle Sta-bil fuel stabilizer
1 gallon e85
mix fluids together in the 5 gallon jug and top off the jug with the LOWEST octane fuel you can buy (if you're running turbo use 91 or better)
Run the tank until it's nearly empty, you don't need the dummy light on, and fill with the coctail in the jug. Drive for about 10 miles very gently while the ECU learns the fuel ratios and octane, then romp on the car as hard as you feel safe doing. By the time you get close to empty again you should notice that the stutter is greatly reduced or almost gone.


Edit Edit: I'd change the fuel filter after you're done too, no telling what crud could get broken loose in the tank after that mixture.

As for the hesitating, my 95 does that and sometimes under load it will cut out altogether and gives me whiplash. I found that I have a short or bad connection to the Cam Angle Sensor. At first I found oil leaking into the connector, fixed that and no help, replaced the sensor, same thing. It turns out there is a bad connection in the wire loom somewhere. If I move the loom the condition goes away for a few weeks than back it comes.

I'm still looking.

As for OBDI or OBDII, mine will not work with any scanner. I read somewhere that Chrysler upgraded some of the later 95s with the OBDII codes.

As for your codes, Ignore 12 as for 36 my Chilton says "ignition timing adjustment signal" and says "check harness and connectors"

(sounds a lot like my problem)


BK85

My car was built in May of 94 and my OBDII scanner works just fine in it. I use it everyday (scangaugeII). Code 36 is for the pulsed secondary air injection pump, as stated, and was recalled and removed by the factory. If you are throwing that code, it hasnt been removed, or there is a different ecu in there that hasnt been reflashed.

95 ECUs are also notorious for "shutting down" while running. The car will stall, just out of nowhere turn off, and sometimes wont start again until the ECU stops being a piece and sends power to the ASD relay.

If your wont scan with any connector you have a faulty harness to the ODBII port. Usually the issue is one of the grounds is missing.

Thanks, I will check out your suggestions and let you know what I find out. It seems to me that its probably minor. My car only acts that way every now and then. I'll call the dealership and find out if they can still get rid of code 36. I know it was a recall, but since its been so long I wonder if I can still get it done for free (doubt it). I can ignore code 12, but I am sooooo tired of seeing the CEL. I guess I can ask the dealership if they can clear that one as well.

You mentioned that the harness to the cam sensor was damaged and when you move it things work ok? Is there any heat damage around where it passes by the EGR tube?

Originally posted by RoninEclipse2G
You mentioned that the harness to the cam sensor was damaged and when you move it things work ok? Is there any heat damage around where it passes by the EGR tube?

Nope, the shielding is still fine. One of the first things I did was to move all the wiring as far away from the EGR tube as possible.

On your ECU,, does the harness that plugs into the ECU have two connectors or one long one?

BK85

My 95 ECU harness has one long connector, approx 5-6" long with a bolt going into the ECU. Anything newer uses the 2 shorter connectors that are 2.5-3" long

Originally posted by RoninEclipse2G
My 95 ECU harness has one long connector, approx 5-6" long with a bolt going into the ECU. Anything newer uses the 2 shorter connectors that are 2.5-3" long

Hmm, same as mine.

Can yours get the OBDI codes using the keydance?

BK85

Yeah. It's still technically OBDII but the keydance works up through 97 IIRC.