[nothingman]

HELP!! My car has a CEL and is running really rough. I've exhausted every solution I can think of to fix it and am hoping someone here may have a suggestion before I have to tow the car to the dealer and admit defeat.

I have a lot of experience with cars having done engine swaps, rebuilds, and aftermarket turbos on Nissans and Hondas in my younger days. I stopped all of that and graduated to a BMW M3 in 2005. Yes, I'm old. Point is, I know my way around an engine bay.

A little history on the car for reference: In January I flashed my 2017 to BM3 stage 1 and have driven it for months without issue. I also made a few changes with Bimmercode including removing the nag screen and upgrading id5 to id6 lite. On 4/24, I flashed my car back to "stock and lock DME" via BM3 and took the car to the dealer. They did an oil change and flashed the latest ISTEP software upgrade. I then drove the car on the stock DME flash for a few weeks.

Here's where the problem began: On 5/12, I installed a Fabspeed Sportcat and flashed the car to BM3 stage 2. I already had a new intercooler on order and figured I would watch the IAT's and not push it hard until IC installation. Immediately after the cat install and DME flash, I drove to a Sunoco 10 miles from home and topped off the 9-10 gallons of 93 octane already in the car with 2-3 gallons of 100 octane race fuel. As soon as I started the car back up after fueling I got a CEL and made this forum post. I drove the 10 miles back home and hooked up my laptop and read the lamda codes below:

Engine (DME)
12B104 lambda probe heating before catalytic converter, control cable disruption
12B304 No description available (this post says it's a "Lambda probe heating after catalyst activation: Line Break")

Since the problem began, I have also started receiving the following code:
201101, DME, tamper protection, recognized program or data manipulation

I understand the tamper code is likely the result of the dealer performing the ISTEP update and flashing back to BM3 as per this post. I can live with that, it's the lambda codes I'm concerned with.

Can someone with ISTA+ run the codes above and give me the recommended suggestions?

Since the CEL began, I have taken the following steps to fix it and none of them have worked:

1. Clear the codes with BM3. I did this again after every step below.
2. Double and triple-checked the lambda sensor wiring and connections including making sure the dark grey/black sensor is the top (first sensor from the turbo) and the light grey sensor is secondary further down.
3. Flashed the DME back to "stock flash and lock DME" via BM3.
4. Replaced the 02 sensor with this brand new one part #11787596908.
5. Checked every single fuse.
6. Re-installed the stock cat.

Currently, the car is in stock configuration with the stock cat and stock DME flash tune. Should I reach out to Fabspeed or PTF and see if they have ever seen a similar issue? Without a solution, I'll be stuck taking my car to the dealer and bending over.

Just to be clear, I'm not blaming Fabspeed Motorsport or proTUNING Freaks BM3 for any of my issues.

[CantComplain]

Hi nothingman, sorry you're going through this.

First off, sorry I won't be able to help but will subscribe to this thread as I've been considering BM3 for some time and am ready to pull the trigger. Overdue actually, and I'll be watching this thread closely. I already have the FabSpeed catted dp and will possibly consider running this setup (that is, sportcat and BM3 Stage 2) without an intercooler upgrade for daily driving duties and occasional glory runs but not hardcore track use. I also have done all of the bimmercode changes you have. I know this is a common combination and hopefully this helps in that the vendors will want to ensure that you're well supported.

The one question I have for you is about when the CEL occurred. In this thread you said after the trip to the gas station, but in the other you said it was immediately after installing the downpipe. For troubleshooting purposes (i.e. step #1: what did you change last?), I would think that would be important.

Hopefully you just dinged the o2 sensor or something and can replace it cheaply--that may be what I would do first, possibly replacing the dp gaskets if you pulled it out again. But I'm also concerned, selfishly, about the tamper code. I would hesitate to run this setup if that's expected.

Best of luck, please post as you progress.

[nothingman]

Originally Posted by CantComplain

The one question I have for you is about when the CEL occurred. In this thread you said after the trip to the gas station, but in the other you said it was immediately after installing the downpipe. For troubleshooting purposes (i.e. step #1: what did you change last?), I would think that would be important.

Hopefully you just dinged the o2 sensor or something and can replace it cheaply--that may be what I would do first, possibly replacing the dp gaskets if you pulled it out again.

Thanks for your concern. To your question, in the other thread I indicated it was immediately after installing the downpipe since the gas station trip was literally 10 minutes after the installation. After completing the downpipe install, I flashed BM3 stage 2 and then went to the gas station. I should mention I’ve used this exact same 100 octane Sunoco fuel on BM3 stage 1 many times before and never had a problem.

I already replaced the upper O2 sensor and it didn’t help anything.

[mua]

hmm, you did not make a mistake on the two sensors?
I read about something on the german "2ertalkforum" with identical problems. dont remember the failure codes, but the same symtoms while driving.
in the end... his workshop made the mistake... they reversed the 2 sensors from the sportcat... that was causing all the problems.

[Poochie]

http://f80.bimmerpost.com/forums/sho....php?t=1318465

[nothingman]

Originally Posted by mua

hmm, you did not make a mistake on the two sensors?
I read about something on the german "2ertalkforum" with identical problems. dont remember the failure codes, but the same symtoms while driving.
in the end... his workshop made the mistake... they reversed the 2 sensors from the sportcat... that was causing all the problems.

Can someone please take a picture of the upper sensor wiring and post it for me?

[bi0hazard]

Sorry OP. Please tell us what PTF say.

[PackPride85]

Sounds like a downpipe issue, not a tune issue.

[CantComplain]

Originally Posted by nothingman

Can someone please take a picture of the upper sensor wiring and post it for me?

Not a picture, but here's the BMW diagram:

https://parts.bmwofsouthatlanta.com/...category=17314

Seems pretty straightforward, the short dark gray cable with the ribbing goes to the forward hole in the downpipe, #1 in the diagram below. the lighter gray smooth cable goes to the rear sensor, #2.

#1 cable connects to the side that has 2 yellow cables on the other side of the connector
#2 cable connects to the side that has 2 red cables on the other side of the connector

[nothingman]

The more I think about this, the more I can’t help but think the problem is DME related. I have the stock cat on the car. I know the O2 sensors are in the correct locations. I know they aren’t damaged, and the upper sensor is brand new.

Do you think the ISTEP update combined with the BM3 flash could have caused a problem?

[McPurrs]

I think your flash went bad, maybe istep related, maybe not. And I think when they hook you up to the computer, you are going to have warranty issues...

[Nezil]

Do you know what istep version you were before? You could potentially flash back to that earlier version, I believe E-Sys can do this, even though BMW dealers never will.

Coding with E-Sys is very common, flashing istep less so, but it can be done. I know that cookiesowns has some experience with doing this...maybe talk with him. The download packages are large, but if it saves you trouble with the dealer, I'd do it.

[cookiesowns]

Doubt it's ISTEP related. It sounds like a O2 sensor problem.

[gtaM2]

Originally Posted by nothingman

The more I think about this, the more I can’t help but think the problem is DME related. I have the stock cat on the car. I know the O2 sensors are in the correct locations. I know they aren’t damaged, and the upper sensor is brand new.

Do you think the ISTEP update combined with the BM3 flash could have caused a problem?

did the new sensor come with the wire? im thinking the problem with your car is actually what is being diagnosed, if its not the sensor its probably the wire/connecton?

[CantComplain]

Just a shot in the dark, BimmerCode has a couple recent updates, including earlier today (iOS) that includes "Updated coding data for cars that received a software update at the dealership recently"

Can't imagine that coding anything with an older version would have caused an issue but if there was a glitch between the old version of BimmerCode and an new version of ISTEP, who knows?

[Nezil]

I was going to suggest getting a copy of ISTA+ up and running, so that you can take a (better) look at the error messages. I know BM3 has error message handling, but ISTA+ has a bit more information on the errors.

For example... I have the center channel speaker unplugged, and that gives an error from the amplifier module that ISTA+ actually identifies as a failed speaker, or open circuit. BM3 just says unknown error.

Another thing to try is looking at logs. I think BM3 has the ability to log the Lambda data directly from the O2 sensors, and this might actually show you an issue with one of them. I'm inclined to think that it is an O2 sensor because that seems the most reasonable given the symptoms. As gtaM2 said though, it could be the wiring or connector that's the issue rather than the sensor itself. Either way data from the sensor would tell you this.

[nothingman]

I may have had an aha! moment last night while laying in bed. Unfortunately, I can’t test my theory until I get home tonight from work

Keep your fingers crossed for me. I’ll update the post tonight after my findings.

[proTUNING Freaks]

Hey nothingman, please reach out to our support if any help needed, here'a a link:

https://bootmod3.atlassian.net/servi...tomer/portal/1

Given the codes it seems to be an o2 sensor issue or potentially swapped pre and post cat o2s. Tune won't cause those codes even if we tried and you'll have them if you switch back to stock as well

As for tamper, it won't be there if you flash back stock and lock. While tuned in it goes away as well unless you forget to wait after flashing and just start the car. In that case just a simple reflash and wait will make it go away. In any case let us know through tech support and we'll be able to

[bi0hazard]

Originally Posted by proTUNING Freaks

Hey nothingman, please reach out to our support if any help needed, here'a a link:

https://bootmod3.atlassian.net/servi...tomer/portal/1

Given the codes it seems to be an o2 sensor issue or potentially swapped pre and post cat o2s. Tune won't cause those codes even if we tried and you'll have them if you switch back to stock as well

As for tamper, it won't be there if you flash back stock and lock. While tuned in it goes away as well unless you forget to wait after flashing and just start the car. In that case just a simple reflash and wait will make it go away. In any case let us know through tech support and we'll be able to

proTUNING Freaks What do you recommend when taking the car in for service? Should BM3 flash back to stock and lock? Will anything get messed up when the dealer flashes newest BMW software update? Should people with tunes decline BMW updates?

[boostm3]

Nothingman, waiting with baited breath to find out how this saga ends.. last we heard, you had an AHA moment.. Spill! Inquiring minds need to know.

[nothingman]

Problem fixed!!!

I'm sure many of you saw this coming, so I'll just go ahead and provide this disclaimer:



Yes, this entire experience can be summarized by telling you I'm an idiot. But that said, if this thread helps just one person in the future from making the same stupid mistake I did then it is worth it.

Before I tell you how I fixed the problem, you should know the problem itself is glaringly obvious in one of the pictures in my very first thread of this post. I'm going to save the answer for the post below to give those of you who are curious enough an opportunity to go back to the first post and try to figure it out.

[gtaM2]

oh the suspense...