Just turned 3k miles. My UltraGauge just informed me of a pending P0132, for primary O2 sensor high voltage. Since its pending, no MIL has been set yet.

Is this common on these cars? I've only seen oxygen sensor issue on older cars. Pretty surprised to see it on my new car.

 

I've driven a bit more and so far, the code hasn't set. Looks like the pending code went away. I guess the downside of running an obd scanner all the time is it tell me little things that normally people wouldn't see, until the MIL/CEL sets. Hopefully, this is a rare occurrence in my car. So far, the Accent has been fun to drive. It's my little go-kart. I'm 6'4", so it does feel small

 

can be either a fluke or an early indication of a faulty sensor or even possibly wiring problem.

if it happens again use your warranty. thats why its there.

 

Warranty will only cover a hard set code, pending codes don't mean anything to warranty

The code has to be set, and the light has to be on

Thanks
Duro

 

Does your scanner have live data? Check the sensor values with the engine running, after sitting overnight, and see how fast that sensor warms up, it could be a loose connection or something. I wouldn't worry about it unless it sets a hard code (cel on), or if the readings are lazy (defective sensor).

 

I've driven a few hundred miles since and my Ultra Gauge has never again flagged a pending code. I agree with the above post that until a hard code is set, no need to bother the dealer. Was it not for having an OBD tool plugged in full time, I would have never even known about this event. Since it didn't progress into a full-blown DTC, i'm not worried about it. Still have 97k left on my warranty

My OBD scan tool does read live data, as does my permanently mounted Ultra Gauge. The Actron scan tool i have is sweet for O2 stuff as it will also graph data. I checked it out and all seemed well. When the pending code set on me before, the car was already warm. I stopped for 10 minutes to get food and it flagged the pending code right after the engine was restarted. Could have been just a brief freakout on the part of the ECU. Who knows. I'll keep an eye on it, but it was hopefully an isolated incident.