[enrita]

I am constantly getting these codes, tried to do reset adaptation but they wont go away (also got a Engine Cell once) . If they are only O2 sims related i dont mind but i wonder if one of the front lambda could be misreading and messing with my afr ratio somehow.

2C7E:
2C7E Lambda probe behind catalytic converter, trimming control
Error will cause a warning light
Error is not currently present
Test conditions have been completed
Signal or value below threshold

Freeze Frame Information
Event 1Odometer 64856kms 40299miles
voltage Lambda probe behind catalytic converter bank 1 0.04 V
voltage Lambda probe in front of catalytic converter bank 1 1.74 V
Lambda shifting return valve 1 0.00 -
input signal return valve 1 0.00 V

Event 2Odometer 65136kms 40473miles
voltage Lambda probe behind catalytic converter bank 1 0.04 V
voltage Lambda probe in front of catalytic converter bank 1 1.82 V
Lambda shifting return valve 1 0.00 -
input signal return valve 1 0.00 V

Event 3Odometer 65248kms 40543miles
voltage Lambda probe behind catalytic converter bank 1 0.10 V
voltage Lambda probe in front of catalytic converter bank 1 1.93 V
Lambda shifting return valve 1 0.00 -
input signal return valve 1 0.00 V



2C6C:
2C6C Lambda probe behind catalytic converter 2, system check
Error will cause a warning light
Error is not currently present
Test conditions have been completed
Signal or value below threshold

Freeze Frame Information
Event 1Odometer 64864kms 40304miles
voltage Lambda probe in front of catalytic converter bank 2 1.50 V
resistor Lambda probe behind catalytic converter bank 2 512.00 ohm
Engine speed 1,504.00 rpm
voltage Lambda probe behind catalytic converter bank 2 0.63 V



2C6A:
2C6A Lambda probe behind catalytic converter, muddled
Error will cause a warning light
Error is not currently present
Test conditions have been completed

Freeze Frame Information
Event 1Odometer 65144kms 40478miles
Engine temperature 93.75 ∞C
time since start end 435.20 s
voltage Lambda probe behind catalytic converter bank 1 0.04 V
voltage Lambda probe behind catalytic converter bank 2 0.63 V

2C7E:
2C7E Lambda probe behind catalytic converter, trimming control
Error will cause a warning light
Error is not currently present
Test conditions have been completed
Signal or value below threshold

Freeze Frame Information
Event 1Odometer 64624kms 40155miles
voltage Lambda probe behind catalytic converter bank 1 0.02 V
voltage Lambda probe in front of catalytic converter bank 1 1.89 V
Lambda shifting return valve 1 0.00 -
input signal return valve 1 0.00 V

Event 2Odometer 64760kms 40239miles
voltage Lambda probe behind catalytic converter bank 1 0.00 V
voltage Lambda probe in front of catalytic converter bank 1 1.97 V
Lambda shifting return valve 1 0.00 -
input signal return valve 1 0.00 V



2C6A:
2C6A Lambda probe behind catalytic converter, muddled
Error will cause a warning light
Error is not currently present
Test conditions have been completed

Freeze Frame Information
Event 1Odometer 64632kms 40160miles
Engine temperature 102.75 ∞C
time since start end 1,561.60 s
voltage Lambda probe behind catalytic converter bank 1 0.02 V
voltage Lambda probe behind catalytic converter bank 2 0.33 V

Event 2Odometer 64760kms 40239miles
Engine temperature 101.25 ∞C
time since start end 768.00 s
voltage Lambda probe behind catalytic converter bank 1 0.04 V
voltage Lambda probe behind catalytic converter bank 2 0.61 V

[jpirelli]

Were these O2 sim related or what?

[Chrisred]

I get same codes. Are O2 sensors bad??

[jpirelli]

Originally Posted by Chrisred

I get same codes. Are O2 sensors bad??

I think it might be due to the new BMW software. Rear O2's are now used for fueling from what I've read?

[anerbe]

Had problems with these - somehow after multiple trips to dealer without solution, they ended up cleaning the intake ports/walnut blasting, and this has removed the errors. Haven't had the codes trip for a month (previously, it would trip 1-2 times a week).

Good luck.

[jpirelli]

Originally Posted by anerbe

Had problems with these - somehow after multiple trips to dealer without solution, they ended up cleaning the intake ports/walnut blasting, and this has removed the errors. Haven't had the codes trip for a month (previously, it would trip 1-2 times a week).

Good luck.

Which codes did you have?

[anerbe]

Originally Posted by jpirelli

Which codes did you have?

2C7B / 2C7C

They would trip in aggressive throttle input at higher gears (higher load/low rpm), causing CEL occasionally. When it would trip, there would be a sudden bog of the vehicle, and if the CEL was thrown, there would be reduced power.

[danniexi]

Originally Posted by enrita

I am constantly getting these codes, tried to do reset adaptation but they wont go away (also got a Engine Cell once) . If they are only O2 sims related i dont mind but i wonder if one of the front lambda could be misreading and messing with my afr ratio somehow.

I was in a similar situation as well. In the beginning I constantly read the live data for on my COBB AP (Lambda Bank 2). I found out that randomly the values would freeze, not respond. Lambda probe 1 was responding without issues. I had the dealer install a new pre-cat O2 sensor (bank 2), and the codes (as well as misfires and CEL) went away.

Recently, I've been getting similar codes as you (trimming, line test, shear test, etc. etc.). The O2 values on both banks were pretty much identical with no read issues.

From what I assume, these shouldn't be related to the pre-cat O2 sensors. As I had mentioned earlier, I replaced a faulty one recently, and I can't imagine it to go bad again in such a short period of time.

I've been clearing the codes + resetting adaptations every so often. The car has been driving perfectly with no issues, so at this point, I'm not sure of any solution.

Originally Posted by jpirelli

I think it might be due to the new BMW software. Rear O2's are now used for fueling from what I've read?

Source? I always assumed that the post-cats had nothing to do with the problems above, so I never bothered with taking out the O2 sims. If what you say is the case, O2 sims may be the culprit.

[jpirelli]

Originally Posted by danniexi

I was in a similar situation as well. In the beginning I constantly read the live data for on my COBB AP (Lambda Bank 2). I found out that randomly the values would freeze, not respond. Lambda probe 1 was responding without issues. I had the dealer install a new pre-cat O2 sensor (bank 2), and the codes (as well as misfires and CEL) went away.

Recently, I've been getting similar codes as you (trimming, line test, shear test, etc. etc.). The O2 values on both banks were pretty much identical with no read issues.

From what I assume, these shouldn't be related to the pre-cat O2 sensors. As I had mentioned earlier, I replaced a faulty one recently, and I can't imagine it to go bad again in such a short period of time.

I've been clearing the codes + resetting adaptations every so often. The car has been driving perfectly with no issues, so at this point, I'm not sure of any solution.


Source? I always assumed that the post-cats had nothing to do with the problems above, so I never bothered with taking out the O2 sims. If what you say is the case, O2 sims may be the culprit.

Shiv said it himself...

Originally Posted by shiv@vishnu

So far so good.

I can't say exactly what we did with respect to idle stability. But I can say that the newer DME updates now use the rear o2 sensor voltages for fuel determination and NOT for just testing for catalyst inefficiency. Which is why all the current wire-in (and our original software-based) o2 sims have been giving some cars problems with respect to o2 codes and misfire.

If private beta testing keeps going as well as it has been going, I'll post up the new maps and firmware within the next few days.

Shiv

I'm currently experimenting with different values for the O2 modifier. I went from 50% to 75%. Someone in another thread stated he was getting similar codes and his O2 modifier was too strong (50%) so he went weaker to 75%.

Originally Posted by Rockstarr

It seems that my O2 settings were too strong (50%). I reset the lambda adaption and set the Procede O2 Modifier setting to 100%. This got rid of the 2c31 code and gave me the cat conversion codes. I ended up at 75% as the final setting running the 2/23 stage 2 maps.

The only recent change is the addition of my Dinan CAI with a K&N filter included. Does anyone know if this would have caused the need to change the O2 settings?