fullymatted.
Back to search
Rennlist

Fuel Trim /O2 sensor issue

Add to repair workspace
Open repair workspace
Original source
3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHFuel Trim /O2 sensor issue

Reported or suspected cause

t the scanner is not able

Suggestion or failed attempt

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that suspect a cause
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suspected cause

Then I want to suspect t the scanner is not able to read the values correctly.

Fuel Trim /O2 sensor issue
Frequently discussed work

Replace sensor

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

I had previously done a reset with the old sensor and it didnt help so I'm satisfied that I did need to replace the sensor.

Fuel Trim /O2 sensor issue
Read full discussion summary

Leading evidence: 't the scanner is not able' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 't the scanner is not able' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace sensor' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.

Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.

Read captured replies

1 matching discussions · 3 captured posts examined · 0 partial discussions

Compare 3 other evidence results

Replace sensor

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

I had previously done a reset with the old sensor and it didnt help so I'm satisfied that I did need to replace the sensor.

Fuel Trim /O2 sensor issue

Replace value occasionally

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

As the scanner only records every 3 seconds it doesn't show the most noticable thing which is that bank 2 O2 sensor fluctuates raplidly whereas bank1 O2 sensor only changes value occasionally.

Fuel Trim /O2 sensor issue

Reset cars ecu

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

It seems I had failed to reset the cars ECU after fitting the new sensor, with the ECU reset the sensor started behaving normally and the car immediately went into closed loop with the fuel trim fluctuating up and down!

Fuel Trim /O2 sensor issue
Frequently discussed actions (3)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Replace sensor

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

I had previously done a reset with the old sensor and it didnt help so I'm satisfied that I did need to replace the sensor.

Fuel Trim /O2 sensor issue

Replace value occasionally

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

As the scanner only records every 3 seconds it doesn't show the most noticable thing which is that bank 2 O2 sensor fluctuates raplidly whereas bank1 O2 sensor only changes value occasionally.

Fuel Trim /O2 sensor issue

Reset cars ecu

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

It seems I had failed to reset the cars ECU after fitting the new sensor, with the ECU reset the sensor started behaving normally and the car immediately went into closed loop with the fuel trim fluctuating up and down!

Fuel Trim /O2 sensor issue
Reported and suspected causes (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

t the scanner is not able

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suspected cause

Then I want to suspect t the scanner is not able to read the values correctly.

Fuel Trim /O2 sensor issue
Coverage and how to read this overview

Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.

3 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Rennlist: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

0 acknowledgements have no verified action link; they do not establish a repair result.

Generation: 20261026T183130Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

Hi, My '98 996C2 is running fine with no noticeable problems and no CEL however I plugged in my OBD2 tool the other day "just for a look" and although there were no fault codes stored I could see that bank 1 O2 sensor was fixed at 0.430V constantly(even during a long run) whereas bank 2 O2 sensor fluctuates up and down as expected. (this is a UK spec car with only 1 O2 sensor per side) As a result of this Bank 1 fuel trim was also fixed at 0 constantly and indicates "open loop fuel system fault". Bank 2 fuel trim constantly moves up and down and indicates "closed loop" as you would expect only changing to open loop occasionally e.g. when in overrun. So I purchased a new 02 sensor (Correct Bosch replacement part number) and fitted it. Now the Bank 1 O2 sensor reading does now fluctuate but not as much as bank2. At idle it spends most of the time around 0.040V and occasionally changes up to as much as 0.8 during a drive. However the strange thing is that the bank 1 fuel trim is still locked at 0 and never moves no matter what - idle, accelerating , overrun. Bank 1 still indicates "open loop - system fault" . I have attached a short excel spreadsheet showing results from a short drive . As the scanner only records every 3 seconds it doesn't show the most noticable thing which is that bank 2 O2 sensor fluctuates raplidly whereas bank1 O2 sensor only changes value occasionally. Anybody got any ideas??? Thanks

POST 2Original post

Quotes source post: 12604468

No CEL? Then I want to suspect t the scanner is not able to read the values correctly. That it can only read the values every 3 seconds is in itself a red flag. What you should see is both O2 sensor readings fluctuating between 0.1V to 0.7V at idle at about once a second. The DME constantly varies the air/fuel mixture from just a bit too rich to a bit too lean to know that it has control of the fueling. In the lean case this supplies oxygen to the converters which store this and use it to process exhaust gases. You can't see this of course because the car isn't equipped with the sensors after the converters. At higher RPMs the DME varies the fuel mixture more often maybe several times a second. At this rate you would need an analog scope to constantly monitor and view the voltage emitted by the sensors. Absent a CEL and O2 sensor related or fueling related error codes, and absent any pending error codes, I'm thinking your scanner just is not up to the task and you are chasing what appears to be a phantom problem.

POST 3 / ORIGINAL POSTEROriginal post

SOLVED! It seems I had failed to reset the cars ECU after fitting the new sensor, with the ECU reset the sensor started behaving normally and the car immediately went into closed loop with the fuel trim fluctuating up and down! I had previously done a reset with the old sensor and it didnt help so I'm satisfied that I did need to replace the sensor. I should of said that the scanner does update about once a second, its only in datalog mode it seems to switch to 3 second update for some reason. Incidentally I dont get a CEL even if I unplug both O2 sensors (perhaps I would eventually?) maybe one of the differences between euro spec and US spec cars? Anyway, thanks for you help.

This is a source reference. Confirm exact model applicability in the original material.