Asmodeus6

iTrader: (7)

You blew the line off.

05blackevo8

iTrader: (2)

Where is the line?
Thanks for the help

wesside

iTrader: (16)

follow underneath the throttle body back towards the passenger side its underneath the intake manifold. I had mine blow off and after the 2nd time I put a zip tie on it, not the easiest thing so put the zip tie on the line first get it back on and zip it

Asmodeus6

iTrader: (7)

I've been running this since my last post. + a few hundred miles. No more codes, and no problems.

Fabulous stuff!

thekuai

iTrader: (8)

will this work for rom 96420011?

tephra

iTrader: (6)

no

mrfred

iTrader: (50)

Sorry, but nope. Haven't seen that ROM before. Must be only a few cars with it.

alan678

iTrader: (18)

This patch is the shiznit! Been rolling with it since this past sunday with no code here (about 400 miles and over 10 starts)

mrfred

iTrader: (50)

Yep, it works. :-)

Warrtalon

iTrader: (6)

Hopefully, this will have a simple answer. I'm having an issue where when I add this to my 96940011 definition file, it doesn't show up in EcuFlash. My Internal ID shows 96940011, my status screen shows "96940011 (79 tables) inheriting evo7base (73 tables)," and I'm putting the new tables at the end of my definition file just above the closing ROM tag.

If I put these tables into my evo7base file, then they show up in EcuFlash, but not if I only do them in the 96940011. I removed it from the base file, because I know that's not right, but I am not sure what other factors could make this not show up. My user level is set to Advanced (also tried Developer), and I checked both boxes for displaying invalid tables and those beyond my user level. None of this makes these show up. IT's as if EcuFlash is not referencing my file, or I've put the code in the wrong place.

Warrtalon

iTrader: (6)

Whoa, that's wierd. I had made a copy of my old XML file, and just appended a ".old" to it. Apparently, EcuFlash still was using that file even though it has the wrong name just because 96940011 is still at the front. I changed the filename so that "Old." is in front, and then it started referencing my new file. Kinda scary.

Only able to change these tables in Developer mode, but it does work.

mrfred

iTrader: (50)

The *ROM*.xml file that ECUFlash uses is not dependent on the file name. It parses each of the files to look for the ROM ID code. The ROM ID tag is in the third line, e.g.,:

<xmlid>96940011</xmlid>

Nothing to do with your problem, but thought I'd mention it so you understand how it works. Using the "Old" at the beginning of the file probably made it come after the new file you're using.

Anyhow, seems that newer versions of ECUFlash have some issues with the tag ["level"=1]. Try changing it to ["level"=2] for each of the entries that makeup this patch.

Warrtalon

iTrader: (6)

Yeah, that's not good for keeping backup files - have to store them elsewhere, but many people probably don't know that.

Smike

iTrader: (8)

Just wanted to say THANK YOU!

Last week the car started to throw the PO138 code (Bank 1, Sensor 2) High Voltage. This patch fixed that right up. Time to take back the replacement 02 sensor!

Smoothgangsta

iTrader: (11)

Is this available for the IX 88590015?

Edit: I see that ECUFlash 1.38 has the updated .xml tables for the ECU and under the Periphery field is the ECU Peripher0 that can be changed as stated in https://www.evolutionm.net/forums/sh...75&postcount=1.

Since I am running a high flow cat would this eliminate the P0420 or any other cat efficiency CEL, and would this allow me to not have to put the mechanical o2 fix on and still be able to pass emissions?