P015D code (O2 sensor) after fixing P015B - something else?

[ken_01]

Hello,

 

I am very happy to have acquired a 2013 Silverado with the 5.3l a few months ago. Love this truck so far.

 

But - It threw a P015B code a week ago - O2 sensor, bank 1, sensor 1. No problem - replaced it with new GM part, easy job.

 

Cleared the code, and for the next few days and 250 miles it stayed cleared. All happy.

 

Then one morning, engine light came back on a few minutes after start up. New code this time: P015D - O2 sensor, bank 2, sensor 1.

 

I figure the odds that the same sensor on the other side just happened to fail within days of the first are pretty slim. So what else could it be?

 

Yes, I had a fill up between the two codes. Always the exact same gas - the Shell V-Power, 91-0ctane, zero ethanol. That's what I've been putting in since I bought it - who knows what the previous owner used. I mention this after reading this thread (see, I searched first!) about a similar case of returning P015 codes:

 

http://www.silveradosierra.com/vortec-5-3l-v8/p015b-and-p015d-codes-t619434.html

 

but I'm doubtful of the non-ethanol gas explanation.

 

Any wisdom will be appreciated.

[007matman]

I've had them fail that way myself before and it kind of makes sense when you think about it.. they've both had approximately the same wear and tear, etc.

 

I've always ran ethanol blends and never had a problem with them.

 

Sent from my Pixel XL using Tapatalk

[ken_01]

I've had them fail that way myself before and it kind of makes sense when you think about it.. they've both had approximately the same wear and tear, etc.

 

Hey, thanks for the quick reply. Certainly possible. But at just 60k miles I would have thought this was an early failure, so unlikely to have two go at the same time. Or, maybe I'm looking for the complicated answer when the simple one is really it.

[007matman]

You could try cleaning the connection and re-seating it. If it's had bad gas quite a bit of it's life that could do it too. Otherwise, I'd be at a loss too.

 

Sent from my Pixel XL using Tapatalk

[O_J_Simpson]

Not much to say. Both were at EOL.

[ken_01]

Craziness - cleared the latest code at lunch today. Drove 80 miles of highway, including one stop/start. Stayed clear.

[rjgti]

could be previous fuel trims were on the edge cause the 02 to go outside of expected parameters

[rjgti]

that is a stretch, betting if you look at live data it is done for

[ken_01]

that is a stretch, betting if you look at live data it is done for

Would love to do that. Any way to do so with the tools in an ordinary human's garage?

[rjgti]

yes, there is a gadget to plug into your obd2 port and it bluetooth it too your phome app for your phone is 3.99

[rjgti]

http://mycarneedsthis.com/best-bluetooth-obd2-scan-adapters/

[ken_01]

http://mycarneedsthis.com/best-bluetooth-obd2-scan-adapters/

My goodness. Old dog, new tricks. Looks like my hand held reader is goin bye bye. Thanks a bunch.

[markofthebeach]

My 2013 Yukon (5.3L, 96K miles) threw P015B after putting in 91 octane gas for the first time. There was no rough idle and I wasn't in a huge rush to change the o2 sensor so I just cleared the code to see if it was a coincidence that would come back, or was 91 gas just a shock to the system.  However, this code had a PERMANENT duplicate in OBDII memory. Check engine light went off but that code persisted. 

 

I learned about these PERMANENT codes. They were required on 2009 and newer vehicles to keep people from erasing fault codes to pass state emissions tests. One way to clear them is passing a Universal Trip Drive Pattern. You simply drive the car in a way that convinces the ECM that you fixed the problem. Requirements for a UTDP are 1. Start and idle for 30 sec min. 2. Drive at least 10 min. 3. While driving, go over 40 mph at least 5 min. 4. When done, idle at least 30 sec before shutting off engine or it doesn't count. Repeat this two more times and the permanent DTC will clear. As mine did.