2C32 and 2C6C Error Codes - Bad O2(s)?

So my car has not been running right and when I went to datalog it, it appears to confirm the issue. Summary: No timing and car studders on partial throttle. Bad o2 sensor, both or upstream causing bad readings?


Car: 2009 335i, FBO + AE Exhaust running procede rev 3 with backend fuel flash.


So I have the two error codes listed in the subject. I also have the misfire and voltage supply error, but searched and found that is 2-step and NLS. I turned off the procede, map 0, as well as reload default maps and the problem persists. Guessing it is a sensor. Below is the log, but AFR's and fuel trims are not matching as well as I am dropping a lot of timing, which I am guessing is the engine protecting itself. Given the 2C32 is a trimming error and the other is a system check, the logs at least confirm this.


I have also noticed on occasion (rare, only if I leave my car on and still only occasionally) white smoke coming from the passenger exhaust. Anyone provide some feedback?


Not enough rep for a link.
datazap.me/u/am3ricus/lamda-sensor

The sticky says about 2C32:

2C32:
2C32 Lambda probe in front of catalytic converter 2, trimming control
EXPLANATION: ECU software is not compatible with o2 ****.
FIX: Currently no solution other than reinstalling your factory cats. You may also delete codes when they appear and live with the problem.

By reinstalling factory cats, do you mean factory exhaust? It has had catless DPs for a while now with no issues, but only 1-2k miles with the catless AE. Would factory exhaust resolve?

Sorry, can't edit last post. I did read prior to posting that the DPFix was causing issues and that had to be removed. In JB instances installing jumpers instead of the DPFix, but the only change from prior logs to the one above was the addition of AE catless exhaust from stock exhaust.

It's probably just a bad O2 sensor.
Can't tell which one, though...

Uninstall the DPFix if you still have in installed. I recently had similar codes on my car and removing the DPFix put everything back to normal.

I have Procede rev3 so as far as I know it is all software driven / suppressed. I purchased it with the MS downpipes so I haven't been in there to check and didn't do any prodding when I installed the catback.

Is there a way to test the o2s like swap them one by one with bank 1 and see if it moves? Do I have to pull the downpipes off to access them?

I am throwing 2c32 and 2c2c on my car with jb4/bms e85 flash, vrsf fmic, walbro inline and plm downpipes. The car ran great for like 3 weeks when I got this setup, then all of the sudden, it throws these codes ever so often after clearing it.

Yeah it won't throw a code for 30 minutes but if I go WOT it starts to pull and you can feel it pull timing. It just doesn't have any balls.