Hi
Over the weekend wires from my rear o 2 sensor got wrapped around the drive shaft. It pulled some of the sensor wires out of the connector body where it meets the wiring harness.

I was able to solder the wires back onto the connector, but now I can't clear the check engine light with the code scanner.

It didn't present as a no buss but most of the other system data was un-readable.

What are the chances that I damaged the computer? Is there anything protecting the computer from a shorted input?

Thanks for any input

Bob

 

Bump

Okay so I replaced the oxygen sensor. Had to go back a few times with the reader to clear the check engine light. Got it to go off for about 4 miles then came back on. Now I'm really starting to lean towards the fact that the computer is damaged. Is there anything else I should be looking at? Is there anyway to test the oxygen sensors at their connector with a VOM meter? I don't want to throw a new computer in it only to find out that its not the problem.

Thanks for any help

Bob

 

What code is popping up? If it's an O2 sensor code, I would say you have something wrong with the repaired wiring.

 

What code(s) is your scanner showing?

 

Thanks for the reply. I think I figured it out. I checked the wiring diagram which showed a fuse (#24 in the PDC [15A]) ahead of both the O2 sensors. Sure enough it was blown. Threw in a new fuse and this time the OBD reader cleared the CEL immediately. Ill keep my fingers crossed that was it. Ill post again if anything changes.

Thanks again

Bob

 

Oh.....and a BTW. I also figured out what caused this whole mess. The upper tranny mount bolts fell out. DOH!!!!! The drivetrain was flopping like a fish and grabbed the wires.

Found replacements bolts at NAPA. M12x1.75x25 if anyone's interested.

TBH, I heard something fly a week or so ago when I was on the highway which caused a little rumbling after, but I thought I threw a wheel weight.

Oh well.,....its a Jeep

Took a lickin' and kept on ticken'

Thanks again

Bob