[cn555ic]

Same symptoms. Driving and cruising with AC on. Then out of now where the oil temps plummet and when I come to a stop the fan blasting high. I know what u are describing. So far after a correct reset of procede and adaptations via command center, so far so good. I also reloaded firmware and software

[Spoolin335]

The Procede is doing something that causes the water temp to read incorrect and fail high. This causes the engine fan to turn on and thus cooling the water which will cool the oil i guess. There does not seem to be a definite fix yet as i have reset the adaptations many times and still have the same issue.

[OpenFlash]

The default wg position (90%) setting keeps the wastegates closed to improve spool-up and reduce wg rattle. But in doing so, it also draws more current through the wg control circuit which, in a few cars, strangely triggers the 12003 code. To eliminate this, just set wg position to 30% and you should be good to go.

[najin23]

Originally Posted by NiVeDh

I never had the radiator blind code, only 2EE3. I have a 6MT - no transmission issues related to this.

I've had the 2EE3 code multiple times with the older maps (before 3-30). I wasn't particularly beating on the car - just normal city driving - and it happened. The symptoms included the oil temperature dropping, from 240F to 170F in a matter of minutes, and the radiator fan going on at full blast.

The code means "coolant temperature sensor, plausibility, gradient". The BMW Tech said that the code doesn't actually mean that the coolant temperature sensor is defective as that would probably cause it to not read anything. It means that the coolant temperature somehow increased over the set limit or it did this "too quickly" (hence the "gradient").

I seriously doubt the coolant was actually overheating... probably just a PROcede glitch which has been resolved in the new maps as far as I can tell.

I don't know what the radiator blind code means but my bet is, it's the PROcede. You never know with these beta maps.

This exactly happened when I turned on AC. The fan started running, oil temp went down from ~230 to 170, then water went from 195 to 210+. I was kind of scared of stall, so pulled over to a parking lot, let it run for about a minute or two, then shut the engine. After about 3min, cranked again, and my JB4 mobile was reading the water 150! I sensed immediately that it was the sensor issue. Plus, it was a very pleasant dry 78F degree day, and I wasn't pulling at all. The fan didn't kick on again, then I came home did the coolant flush just in case. The next day, checked the coolant level, and it was normal. Days later, CEL came on the way to work, then this code 2EE3 was there. Erased it. Does anyone know what could the issue?
Thanks.

[ragingpanda]

I'm resurrecting this thread from the dead because I am now throwing this code randomly 2ee3 running mhd though with upgraded turbos. Once it comes up, the fan turns on full blast until I shut down the car. I have already replaced my coolant temperature sensor and the issue still persists.

[ragingpanda]

Ok, so I figured out that if I flash any map with the 'performance' coolant target map, 2ee3 will get triggered eventually driving normally. I flashed my current map with the stock coolant target and I am no longer throwing that code if anyone runs into a similar issue.