Oxygen sensor fault codes

[Massa in Perth]

Hi all, I replaced both O2 sensors in November and I am starting to get daily CELs relating to the sensors again! Light will come on at random and disappear again just as unpredictably a few seconds or a minute later.
Car is running fine.

I used the genuine Bosch part although bought online from a seller in Latvia.

Is anyone able to shed any light on whether the problem is definitely the sensors or whether it could be something else?

Many thanks in advance, Toby

 

[Maser Sod]

Is it for a 3200?

If so, I used to get them all the time, to the point where I just started ignoring them. Used to flick on and off, especially if I was crawling in traffic.

 

[Massa in Perth]

Oops, yes sorry 3200. It was good for a month or so then started throwing CELs. Did you get to the bottom of yours?

 

[voicey]

I can't really see the text properly - are the top two P0130 & P0150? They are sporadic or intermittent warning codes. I would start with the checking the wiring.

 

[mchristyuk]

Massa,

I used to suffer from this on my previous 3200 and my current one. I found that it only ever happened when I was in slow moving traffic, or had previously been in slow moving traffic and not given the car a good run (e.g. to the red line!). What cured it for me was making sure I put some RedEx in the tank each time I filled up and making sure I only used "good" petrol and not cheap standard supermarket fuel.

I think like most cars, the 3200 will "gunge" up the engine a bit if it's not worked out properly, and that can lead to poor running which helps muck up the Lambda sensors. Good blast getting everything nice and hot always seemed to fix it.. I think the RedEx wasn't really necessary if using something like Shell V-Power all the time, but for the times I had to use Supermarket fuel then I think it helped keep the engine a bit cleaner!

Cheers

Mark

 

[Contigo]

Yep mine hates running on Normal unleaded, everytime I put it in it throws Boost errors and also lambda codes. Stick to BP SUL and it is fine.

 

[Maser Sod]

Did you get to the bottom of yours?

Not really, like others I just used to give the car a blast and it would tend to go away.

I stopped worrying about the CEL after a while, it was such a common occurrence on my car.

 

[Massa in Perth]

Sorry Voicey, yes, P0130 and P0150, also ox1171 and ox1172, which seems to accompany the first two). Thanks all, I use Shell Ultimate 98 only and she's a daily driver, mostly 2000 to 2500 rpm or stop start in traffic.

As long as it's not a precurser to something else (TB, TP, Injector problems etc) then I can relax a bit.

Sounds like a blast is in order once it cools down here... (44.4 Celcius here today!!), cheers, Toby

 

[BL330]

**** that is hot, nearly 112 degrees in the old money! That's why they invented spare cars so your baby can be safely tucked away.

 

[Massa in Perth]

Got to work before 7 and she stayed under the building in the car park all day!

 

[Maser Sod]

Another thing to point out is that turbocharged engines can be more susceptible to incorrect air-fuel mixing than n/a engines (e.g. when dump valve releases). This can cause odd readings and also soot on lambda sensors where the fuel hasn't burnt properly.

Somebody more knowledgeable than I am on the 3.2 twin turbo V8 could probably shed more light on this.

 

[Massa in Perth]

P0150 just popped up again, with x1172. Says Bank 2 sensor 1. Misfire as well.

Anyone know which side of the engine is Bank 1 and Bank 2? Thanks!

 

[jluis]

Cylinder 1 is the first cylinder on your left when you are looking at the engine from its front (drivers side for UK/au cars)
I would say that side is bank 1

 

[daverichardson]

Misfire ?
HT Coil?

 

[Massa in Perth]

Thanks Dave, I think the coils throw a code when they are on the way out? Plus it's intermittent (nothing for a couple of months then this!) so I reckon it's wiring..

Just in case anyone hasn't found this site here's a link. It has loads of fault codes and diagnostic info. Just click on any code and then a box comes up into which you type your error code: http://www.datsc.com/tabid/123/Diagnostics/Maserati/Default.aspx

 

[Massa in Perth]

Dusting off this old thread - getting P0130 again, with 0x1171 and 0x1225.

About P0130 I found this:
P0130 - 02 Sensor Circuit Malfunction (Bank I Sensor 1)


OBD-II Trouble Code Technical Description

02 Sensor Circuit Malfunction (Bank I Sensor 1)

What does that mean?

The O2 sensor produces a voltage based on oxygen content in the exhaust. The voltage varies between .1 and .9 Volts, .1 indicating lean and .9 indicating rich.



The ECM constantly monitors this voltage while in closed loop to determine how much fuel to inject. If the ECM determines that the O2 sensor voltage was too low (less than .4 Volts) for too long (for more than 20 seconds (time varies with model)), this code is set.

Potential Symptoms

Depending if the problem is intermittent or not, there may be no symptoms other than MIL (malfunction indicator lamp) illumination. If the problem is constant, then symptoms may include one or more of the following:
•MIL illumination
•Engine runs rough, missing or stumbling
•Blows black smoke from tail pipe
•Engine dies
• Poor fuel economy

Causes

Usually the cause of P0130 is a bad oxygen sensor, however this isn't always the case. If your o2 sensors haven't been replaced and they are old, it's a good bet that the sensor is the problem. But, It could be caused by any of the following:
• Water or corrosion in the connector
•Loose terminals in the connector
•Wiring burnt on exhaust components
• Open or short in the wiring due to rubbing on engine components
• Holes in exhaust allowing unmetered oxygen into exhaust system
• Unmetered vacuum leak at the engine
• Bad o2 sensor
• Bad PCM

There are separate codes for low oxygen and hi oxygen readings, so this looks electrical rather than fuel mix. I'm gonna pull out both sensors on the weekend and swap them over, then see whether the fails changes to Bank 2 sensor 1 (P0150) or not. Will post fi9ndings

 

[davy83]

FWIW if you can get a PC based ODBII reader on your car and i am using dash command these days on my phone or i-pad you can look at the live output from the O2 sensors. I put them on a plot so you can see the recent history, and the signal should sort of do a merry dance between lean and rich and bounce up and down, once the engine is at its running condition, if its static or just stuck in one position it is not working well, maybe you could log the O2 sensors during a trip where this has been happening and see what they are doing, it might help you get a feel for whats going on.