Bootmod3 OTS Stage 2 CEL issue

[Turboglimk4]

Hey guys, I am having some problems with my BM3. I just put on my catless downpipes and AWE track exhaust. I tuned the car today and when I first tuned it the CEL went off from the downpipes. However on the second drive cycle the CEL came on BM3 shows code 128C01 "Lambda probe before catalytic converter, shoring: probe not properly mounted in exhaust system". I have turned off catalyst monitoring with the tune and every second drive cycle that code sets. The shop that help me install the exhaust is saying it is because there are no cats in the downpipes. I have attached a picture of the laptop screen with the code.

Also what is the BM3 burble setting with this tune. I was messing with the Burble settings and now the burble is set to OEM. Which is the best mild aggressive burble setting?

Thank you in advance any help would be greatly appreciated

-Anthony

[f80er]

Says right there no sensor in your down pipes. Code it out.

[Halim@HCP]

That issue is PRE cat and not a catalytic efficency related code.

Did you make sure to properly install the O2 sensors?

[Turboglimk4]

Originally Posted by f80er

Says right there no sensor in your down pipes. Code it out.

This is pre cat. I have car monitoring off and it still throws the light.

[Turboglimk4]

Originally Posted by Halim@HCP

That issue is PRE cat and not a catalytic efficency related code.

Did you make sure to properly install the O2 sensors?

I had a reputable shop do the install. The shop owner said they didn't have any issues with the install. I guess I will contact him and see if he can take another look at it.

Cat #2 would be the rear cat the "small" one correct ?

[M3SQRD]

The CEL for the pre-CAT O2 sensor is a real CEL. Was the pre-CAT O2 sensor damaged when it was re-installed?

[Halim@HCP]

Originally Posted by Turboglimk4

This is pre cat. I have car monitoring off and it still throws the light.

The secondary O2 sensor is for cat efficiency and that threshold is changed when set to 'off'
Pre cat must be fully functional to read AFR.

[Turboglimk4]

Originally Posted by Halim@HCP

The secondary O2 sensor is for cat efficiency and that threshold is changed when set to 'off'
Pre cat must be fully functional to read AFR.

Update:

Just got the car back from the shop again today,

The shop told me that all exhaust sensors were reading on their scan tool.

He said he reset adaptation for them and the CEL is now staying off.

I reached out to BM3 and SSR Performance, they did confirm that sometimes the system needs to have the adaptation reset.

[mike@x-ph.com]

Originally Posted by Turboglimk4

Update:

Just got the car back from the shop again today,

The shop told me that all exhaust sensors were reading on their scan tool.

He said he reset adaptation for them and the CEL is now staying off.

I reached out to BM3 and SSR Performance, they did confirm that sometimes the system needs to have the adaptation reset.

Let us know how if it goes away after adaptation

[mystermykee]

Reviving this thread.

I'm running into the same issue. I've been running a custom E30 tune for over a year, and the problem started happening after I switched back to the custom E30 tune AFTER running a custom 91 tune for a weekend (long road trip).

Any ideas? I've reset the adaptions and flashed to the E30 tune again for good measure, but still throwing the code after awhile.

[mystermykee]

Bumping for assistance!

[TopJimmy]

Originally Posted by mystermykee

Bumping for assistance!

If you are getting an error on one of the the two pre-cat O2 sensors then reset adaptations and try, re-flash and try, and then look for physical problems with the wiring or sensor. A CEL or Code on the pre-cat sensors is a real fault. On the post-cat a CEL is usually just the low-value reading (but if post-cat fails there is a different error).

Another way to re-push the full flash is to flash to Stock (don't lock) then re-flash to Stg2 E30 again.

[mystermykee]

Originally Posted by TopJimmy

If you are getting an error on one of the the two pre-cat O2 sensors then reset adaptations and try, re-flash and try, and then look for physical problems with the wiring or sensor. A CEL or Code on the pre-cat sensors is a real fault. On the post-cat a CEL is usually just the low-value reading (but if post-cat fails there is a different error).

Another way to re-push the full flash is to flash to Stock (don't lock) then re-flash to Stg2 E30 again.

Thanks for the assistance. I have reset adaptations, but no luck. After an adaptation reset, the fault would come on after a drive cycle, then come off randomly. But as of late, it is just staying on. I will give the flask to stock and re-flash to e30.

[dmikucki]

Very interesting... I also got a lambda code right after catless downpipe install and flashing BM3 stage 2 OTS (code is different than yours) but still relates to the o2 sensor. Haven't been able to dig into it lately with the snow/ car in storage but it's really annoying.

[mystermykee]

I was able to get underneath the car yesterday. O2 sensors are not loose and wires look fine. I flashed to stock then back to my custom e30 tune--code came back. I'm taking the car into the shop next week to get both O2 sensors replaced. Since this started happening, the car has an extremely rough idle on startup. It sometimes doesn't go away until I start driving. I assume because the AFR readings are out of whack.

I've been running DPs and the custom tune for almost two years without issue. The only thing I can infer is the O2 sensors are starting to go bad, but not bad enough to where I"ll get a specific DME error telling me they are bad. But yes....annoying.

[tucked_m4]

Originally Posted by mystermykee

I was able to get underneath the car yesterday. O2 sensors are not loose and wires look fine. I flashed to stock then back to my custom e30 tune--code came back. I'm taking the car into the shop next week to get both O2 sensors replaced. Since this started happening, the car has an extremely rough idle on startup. It sometimes doesn't go away until I start driving. I assume because the AFR readings are out of whack.

I've been running DPs and the custom tune for almost two years without issue. The only thing I can infer is the O2 sensors are starting to go bad, but not bad enough to where I"ll get a specific DME error telling me they are bad. But yes....annoying.

Hi, what was the outcome of this?

[mystermykee]

Originally Posted by tucked_m4

Hi, what was the outcome of this?

Replaced O2 sensor and all is well.