• Welcome to the Contour Enthusiasts Group, the best resource for the Ford Contour and Mercury Mystique.

    You can register to join the community.

B1S2 O2 Sensor Fuel Trim constantly 99.06

saj

New CEG'er
Joined
Aug 8, 2013
Messages
24
Location
Norway
I have used AutoEnginuity live data grid. I am not familiar to this and need some help.
Do I need to replace O2 Lamda sensors? I appreciate any comments
 

Attachments

  • Duratec 3l AutoEn&#.jpg
    Duratec 3l AutoEn&#.jpg
    158.9 KB · Views: 0
I don't know :). Where should I look? The uim? I have just taken this of for changing sparking plugs. And I have dtc p0443.
 
your o2 sensors should have a consistent voltage, once a vacuum leak develops, i believe the voltage increases, telling the computer to add more fuel. do research because it could still be a bad sensor, but why throw parts at it?
 
honestly i just looked at your picture again and i cannot tell you what that parameter is for. you will have to find out in the program. what iv been talking about is the short term fuel trim
 
The sensor in question is a down stream O2 sensor. Its there to monitor the pre-cat. I am not sure why it would read that way unless the sensor is bad. Try swapping down stream sensors and see if the reading changes to B2S2.


Wait a second. Fuel trim make no sense for a downstream O2 Sensor. It doesn't appear there is one for the other bank, so this might just be a false reading.
 
The Mondeo/(Contour) in Europe has only two O2 sensors. May be it is the software. The reader does not show P0171/72 for lean/rich. But I like to follow it up. The last month the tps have increased. I am not happy with that ;-)
I Googled and found this for Autoenginuity supported sensors:
B1S2 Catalyst Temperature Command Secondary Air Status
B1S2 O2 Sensor Fuel Trim Commanded EGR
B1S2 O2 Sensor Output Voltage Commanded Equivalence Ratio
B1S2 Wide Band O2 Sensor 2 Voltage
Commanded Evaporative Purge
B1S2 WBO2 Sensor Equivalence Ratio Commanded Throttle Actuator Control
B1S2 Wide Band O2 Sensor Voltage
Control Module Voltage
 
My knowledge to O2 sensors has increased a little bit. :confused: and I appreciate comments to this:
If the definition of B1S2 means that this Bank#1 and S2 is the the sensor after the cat, then this can explain the graf. The S2 do not exsist on Mondeo of Europe. There are only two of them sited on each of manifold before the cat (and before the y-pipe). The software should only show value of B1S1 and B2S1.
Any comments?:help:
 
My knowledge to O2 sensors has increased a little bit. :confused: and I appreciate comments to this:
If the definition of B1S2 means that this Bank#1 and S2 is the the sensor after the cat, then this can explain the graf. The S2 do not exsist on Mondeo of Europe. There are only two of them sited on each of manifold before the cat (and before the y-pipe). The software should only show value of B1S1 and B2S1.
Any comments?:help:

Yes B1S2 would be bank 1 and the down stream or the O2 sensor after the cat in the exhaust manifold.

If the down stream sensors do not exist then you should only see B1S1 and B2S1.
 
Thanks for comment. I will check the cat too. I hope to get the litre pr mile down.
 
If you car does not have downstream sensors, then ignore the reading. It's just a default since the AE software is expecting a North American OBDII car with four sensors.

Bottom line - it is not a problem, just a curiosity in the software.
 
Thanks, I will do that. The engine is using to much qasoline. Before it was about 8 l pr 10 km, now it is about 11l pr 10 km. I have changed sparking plugs (Motorcraft) and cleaned the uim.
But still the same.
 
After research and looking under and inside the engine room - the 3.0l has 4 sensors. I am going to exchange the B1S2 sensor. Software Diagnostic reports that. But there is no DTC error.
 
What you can try first is to swap the lower sensors. If the bank that isn't reading switch you have confirmed that it is the sensor and not some other issue.
 
Closing the thread. I have replaced the B1S2 sensor and a tuning spesialist help to measure. No error code. But the software I used needs an update (I think)
 
Back
Top