I dont mean to intrude and certainly didnt read too far back but the po136 code comes from the second o2 sensor being bad or not being plugged in. What if you disable the 2nd o2 sensor and clear the code. Does it still come back?

 

Mitsukid I sent you the Rear o2 patch in an email please test it out for me

Three new tables to add to your xml.

Essentially whats going to happen is the rear o2 is going to be simulated off the front o2 sensor so if your front O2 is having problems that wont be good.

 

We will find out spiker! ill let you know! ill report back this afternoon!!

 

Ok spike, flashed the ROM looked up the codes and i had a P0134 as well "rear 02 sensor no activity" so i hope this code since it simulates it should wipe that out as well. I flashed it in w/ the values copied over from the ROM you sent me, and it seems to be working! If the "oxygen sensor 2" in evoscan is the Rear 02 sensor then its working because its reporting feedback. Here is the log if you want to open it up and confirm!

 

The code wont wipe the code out if you don' t clear it. I can't easily find where the ODBII code is throwing that error number so we are taking the approach of just fooling the ecu into believing the o2 sensor is working right.

Clear the code and see if it comes back.

 

Here's the patch in case others want to try it.

ROM:
http://www.megaupload.com/?d=A8T5AM6R

XML:
<table name="Rear O2 Sub" category="Rear O2 Simulator" address="36580" type="2D" level="1" scaling="Hex16">
<table name="X" type="Static Y Axis" elements="20"/>
</table>

<table name="Rear O2 Sim Hook" category="Rear O2 Simulator" address="ad96" type="1D" level="1" scaling="Hex16"/>

<table name="Rear O2 Sub Location" category="Rear O2 Simulator" address="ae2c" type="2D" level="1" scaling="Hex16">
<table name="X" type="Static X Axis" elements="2">
</table>
</table>

 

K spiker, so i cleared the code, and less than ten min later i got a code... for a p0141 rear 02 sensor no activity, but no p0136 wtf?? lol

 

That code is for the heater circuit. You still have that heater patch in place right?

 

No the 0x9? i set back to stock by accident i belive.. woops

 

kk

I may have you put it back to stock at some point and test another way of nobbling out the code

 

hmm.. now the p0141 went away, got a p0134 and a p0442 evap code... damn codes wtf lol i have FPI on as well

 

Would you guys recommend transfering the "Desired ISCV" values over from the original ROM, into the Tephra and EVO roms when we do the ECU flash or swap? I'm getting some weird idle stuff, and I don't know if I should tweak it out, or just start from the original values, and then correct from there.

*EDIT* I guess I should elaborate. When I started the car, the idle can sort of rev up to 2200 or so, then drop, and rev, so it sounds like the car is adjusting constantly to idle nicely, hits a ceiling, and starts back over. That's with the A/C on. With the A/C off it idles higher than I have it set for, and comes down to normal as the car warms up.

Also, the real thing I'm trying to address is when I start the car in the morning, I have to basically keep my RPM at the same spot where the car idles, if I let them drop as I put it into gear (meaning let the clutch out) the AFR will lean out, and if I let it enough, to the point of making this "flub flub flub" sound, like the car does't have enough timing or something and the combustion isn't producing power. Thoughts?

Also, this is basically all when cold, when it's warm, it runs primo.

 

The ISCV is the basis for the idle so transferring them over is probably a good idea. The reset of the tables seem to be adders to the ISCV so if the base is too high it will idle too high.

 

Copied over the ISCV values, looks good now. Idles like a champ.

Also, adjusted startup tables, and the car starts like a champ.

Also Also, I've got no P0420 CEL or P0300 so I'm feeling really good.

Thanks Sir!

 

Yup this is what I had to do to fix my idle issues worked awesome.