I have all kinds of codes reading and I was told my catalytic converter’s were clogged. Should they be cleaned or replaced? I have a 2013 Jeep Wrangler Sahara unlimited 4dr 3.6L v6 engine it has 170k miles….Codes being read are p2127 p2122 p0522 u0101 u11c2
I have all kinds of codes reading and I was told my catalytic converter’s were clogged.
None of those codes have anything to do with your catalytic converter.
https://www.obd-codes.com/p2127
https://www.obd-codes.com/p2122
https://www.obd-codes.com/p0522
https://www.obd-codes.com/u0101
https://www.engine-codes.com/u11c2.html
Don't those codes imply the issue is in the CAN Bus system?
What should I do then?
Hey Chuck yea I figured out the problem. I forgot to plug back in the connector to the accelerator when I changed my blend door actuator. I appreciate the help guys, the issue I was having was with my accelerator
your "forum experience" shines brightly Chuck {pear}:laughingoutloud:
@jaye, thanks for letting us know, that kind of thing trips all of us up at one time or another! Also a single simple problem can trigger a cascade of codes. Stay away from the shop that told you needed a catalytic converter!!
@hixster, thanks, no special insight here though, was just hoping it was something simple!
Have your battery and alternator tested.
Make sure your battery cables aren't corroded.
Also, watch this video so you know how a test is done to see if the catalytic converter(s) is clogged so nobody can talk you into replacing your cats without performing the test.
https://youtu.be/qJTmddbOxMk?t=18
What should I do then?
The first 2 codes p2127, p2122 are throttle position sensor codes. And the P0522 code was tripped by the oil pressure sensor.
The U0101 code means your TCM (Transmission Control Module) is not communicating with modules/sensors it needs so it can shift properly.
The U11C1 code was tripped because your Jeep's main computer (ECU) lost communication with these sensors.
You didn't mention any issues like warning lights, rough running engine or poor shifting. Have you noticed any 'driveabilty' issues like these?
