So I've got a 2010 SE with a stage 2 kit and after two months of normal operation my ecu threw a P2096 code. I read up on the cause and am not too concerned, but I will be picking up a wideband soon so I can confidently say my AFR is ok. My main problem is that the code won't clear using the Accessport. I followed the steps and waited 10 + seconds before turning the car back on and the light never goes out.

Anyone have any experience with codes not clearing correctly using the AP. I am open to the possibility that their is an electrical issue which is why the code throws right away, but being that P2096 is associated with air flow I wouldn't think it would immediately get thrown upon startup.

 

First and foremost, are you running a testpipe. I also have this code which I never did on my 2008 MR with the same exhaust setup. It's a 2010+ specific code and it will throw it if you are running a testpipe. The COBB team is aware of the issue and are looking at getting a fix for us, but currently, the only thing you can do is run a HFC or disable the rear O2 sensor with ATR software. Completely disabling the sensor will prohibit it from self cleaning and will probably need a faster replacement should you activate it again someday.

Some others have claimed that they're throwing this code from exhaust leaks, but I don't believe this to be true for most cases. I'm going to try out a "J" bend rear O2 extension (defouler) piece this friday to see if it helps with the issue, otherwise just have to wait until COBB figures it out as I'm not planning on running a cat on an Evo!

As for resetting the code with the AP, I'm pretty sure you're resetting it when your car is still running correct? Turn off the car, then turn the keys to the point where your engine dash lights are lit and air is blowing out of the vents, but don't crank the car. Pull the code and reset the ECU, then turn off the car and it will be good to go for another 50-80miles before it lights up again LOL

 

Thanks for the info and I did reset the ECU while it was not running; however, the code did not clear. I had to reflash my map to get it to go away. What's weird is that it took 2 months before the error. Perhaps the difference in exhaust and intake just take awhile to show themselves?

 

So I also thought there might be a caveat because I have a 2010 SE that uses an MR map. Perhaps Mitsubishi changed the ECU just slightly and this is a bug with the recognition of the Cobb accessport. As I am a software dev, I did all the software things to verify it didn't work and can confirm that using the accessport reset ecu function does not work on my car.

 

Hmmm well, I'll take your word for it that you did it correctly. Are you running a test pipe or HFC? At this point, I would just give COBB tuning a phone call or email so that they are aware of more people throwing this code and maybe have more insight as to why your ECU reset feature doesn't work. The SE is just a name they threw onto a 2010 Evo X SST. Other than a few parts difference, the ECU should be identical to the MR ECU.

 

Yea, I was gonna log a bug with Cobb and have been in contact with Braden about accessport issues. About the only thing I didn't try was the Konami code, couldn't remember it at the time :-)

Right now I am running a test pipe and my data logs don't show anything to be concerned about (i.e. low knock, maf scaling). If anything worthwhile comes back from Cobb I'll post it here but so far their response to technical questions has been lack luster, to the point I'm likely switching to ECU flash (better dev community).

 

Heeh, thought you might be running a testipe! I'll let you know how my physical O2 J extension piece works out. It's supposed to simulate enough of a difference to make the car think that the cat is still in the bag

 

I got the j extension and it still throws the code

 

Same here with an "L shaped" o2 spacer. I'm trying the AMS one next. It has 3 inserts to adjust the exhaust flow to the O2 sensor.

 

AMS with the medium insert still throwing the code. Trying the other size inserts soon. Not having good luck with this. May even go AMS HFC if none work.

 

Having the same problem with mine:l

 

But does it look like my T1R J extension as pictured above? My first try with a straight medium insert spacer didn't do much for me.

Can't help you with the 2011+ Go bug COBB and tell them that Evo owners prefer testpipes!

 

I did try a J style extension first. Now on to this straight one.

I replaced every gasket in the exhaust. Still on. Next step is trying a new O2 sensor and hoping for the best. If that doesn't do it then IDK what to do.

 

You're having the same problem?

 

Your J extension is pointing the wrong direction. 180 off.