Took it to the dealer and they stated that it seems to be some kind of "Phantom" code. The US models don't have these radiator valve pieces and/or CEL related issues. I honestly have no idea what that means.
They submit an incident form/ticket relating to this CEL 21B055.
My car currently has a FI exhaust catted (200CEL) turboback full system. Have the sensors in the designated ports. An Eventuri intake system. I do not have a tune.
The car has been driven with the full exhaust without a tune for 3K miles with not a single issue. Added the intake later and driven with that for an additional 1K miles with no issues or tune.
Today during 70 degree New England weather I took a turn at a light (90 degree turn) and went about 70% throttle through turn all the way into a straight and instantly the light turned on. Only the CEL came on, no vehicle messages or anything. Car was still driving perfectly fine like nothing happened.
I put it back to comfort mode and dropped it straight off at the dealer, and found out the results mentioned above.
At this point I just have to wait unless anyone else has some true/solid reasoning behind why this happens?
BMW electronics can be rather finicky at times and the software is not always foolproof. It could be a case that the DME is setting an erroneous fault code that a future software update will fix. BMW does have some issues with various vehicles where such fault codes will be stored and trigger the CEL after two drive cycles (as it pertains to emissions), but at the same time the driver will not experience any drivability concerns. Until BMW releases a software level that addresses the concern, there is not much to be done, unfortunately. If you are not experiencing any issues while driving, I would recommend continuing as usual.
this code is present on BONE stock untouched cars,and its on every flashing platform unless coded out. Im certain its an option on other BMWs but not on the Supra, and it was just a coding issue. My car had it on delivery and still would if i hadn't coded it out.
Its not an MHD, Ecutek, or BM3 issue. It is in fact normal and can simply be coded out.