I have a 2014 GSR that was tuned last year and it has an ams widemouth downpipe, ets catted test pipe, and a few other mods (unrelated to the issue) and I've been throwing a P0140 code even though in tephra the o2 was disabled. Since it keeps throwing the code, it won't pass emissions in Pennsylvania. Is there a fix other than getting rid of the test pipe? I had an ams high flow cat on my last Evo and the tuner was able to get rid of the cel through the tune and was wondering if the same could be done with the ets catted test pipe.

I've tried contacting my tuner multiple times and even reached out to another via Facebook and haven't had any responses yet so I figured I'd try on here. Any help would be greatly appreciated so I can keep my X on the road this winter.

Edit:
Internal ID: 59580304
Inherits: 59580004

Thanks,

UxC

 

see if you have Periphery FEA 15, like on older evos
https://www.evolutionm.net/forums/ev...ml#post7672107

 

How would I go about doing that? I've tweaked a few things in ecuflash before but never things I wasn't 100% sure what I was looking at, lol.

 

Those are just toggle switches for me. Put in 0 and save/upload the file. These setting turn off any testing for every OBD code listed
its under Periphery

 

Only thing is that the Periphery doesn't match up to that post as to what's what, lol.

 

Alright so I may have found the fix.

The non-continuous monitor patches weren't enabled, and I kicked back on the rear o2 heater. I didn't throw any codes like I usually do on my way to work, and my afr has actually seemed to be a little more steady than before.

I'll likely try and disable the o2 heater circuit again and see if it throws a code again. Thanks for the info for me to check the Periphery settings. I didn't even realize they were there since I never messed with them.

 

Hello folks, Last week I got tuned and soon after traveling a couple of miles (20ish), code p0140 (no movement identified for o2 sensor, or something to that effect). I'm as of now running the speed circuit test pipe alongside a cbe (stock dp) and had been running it for a spell without any ses/codes being tossed (before the tune). Does anybody has any idea about why it might out of nowhere spring up after the tune? Is there a simple fix/answer for this? I have utilized my OBD-II peruser to clear the code however it simply returns on in the wake of placing a few miles on it. Ive attempted this two times as of now..


Tutuapp 9Apps Showbox

 

This sounds like it is the same issue I had. Are you able to access your rom with ecuflash to be able to check some settings? If so, there's a section with ECU Options (I think it's #1-#6) and there may be a one that needs changed. I changed ecu option 2, bit #1 to 1 and ecu option 4, bit #15 to 1.

There's also a spot in tephramod that's called "non continuous monitor completion patch 1" and "non continuous monitor completion patch 2" that, I believe, simulates the o2 sensor and will basically trick the ecu into not throwing the code due to the test pipe.

There's a bunch of potential fixes that might help. Let me know which you try and I'll help as much as I can with the information that I have from figuring out my own.

 

Hey all, just to add some nifty info for those who run test pipes and still get rear o2 trouble codes. If you use an o2 fouler it most likely will not work any differently then just sticking the o2 sensor back in the hole and the light will most likely come back on. But if you pack the fouler lightly with steel wool it does wonders to keeping the CEL from coming on. Give that a try.