evoguy333

iTrader: (1)

thank you! ive always hated that check engine light!

JrCRXHF

i can not get this box when i put the code in with note pad.

I have done other code mods like the no lift **** so i really don't know what i am doing wrong.
the last line of my code for my ECU 88590013


<table name="ECU Periphery0" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>
</rom>

JrCRXHF

has anyone had this problem with the code not showing up a box in modify.

Jack_of_Trades

iTrader: (17)

Make sure to add the </table> to the end of the code, just before the </rom> coding. I believe the ROM won't even load if you happened to forget this though.

al\lupo

Sorry, I didn' see your request. I used a 2d table, not a single 1d definition. Here is my xml:

JrCRXHF

With the longer code do i have to add anything into ecuflash app where i adjust my fuel and spark?

I looked and did not see a box or anything to fill out.

JrCRXHF

Well the long code worked good

edit: to start with it worked good but then this morning when i let the car warm up on the cold morning I got a check engine light when I was on my way to the air port so I would think it is the second O2 but i will have to check when i get home.

Any ideas of what i did not do right?

Thanks guys.

al\lupo

My original question keeps the same? Does anyone knows why periphery entries (all, no only the FAA one) are replied many times? Looking at the code it seems like it use only the first entry, but there are too many references to deep look into...

tephra

iTrader: (6)

yeah this happens a lot with other tables, like the pointers to fuel+timing are repeated about 8 times.

I think there is a global variable to offset into these repeats, but yes the first is always the one used...

JrCRXHF

well i have the check engine cell again it took a day to come back does anyone know why i would get it. I left in the rear O2 just put the long code in the ECU i can not get the short code to work no matter how i put it in.


Anyone else having this problem?

joshesh

iTrader: (2)

^I have the same problem, i have double checked - had my tuner look at my rom and i have the modified portion in there - but i still get a CEL from the rear o2 sensor when i get stuck in stop-n-go traffic. Maybe i need to do the resistor mod for the thing to work completely.

mr2driver

iTrader: (11)

This worked great for me! No more rear O2 sensor, horray!! US EVO9 btw.

mrfred

iTrader: (50)

I have a software fix for the Rear O2 CEL for the Evo IX 88590015 ROM. The code simulates the rear O2 signal. It should pass any emissions test. It only elminates the rear O2 CEL. If you want to remove the rear O2 sensor from the car, you'll have to do the resistor mod described in the first post. Here are the entries to add to the ECUFlash "88590015.xml" file:

--- start here (do not add this line) ---
<table name="Rear 02 Sim Hook" category="Rear_02" address="c250" type="3D" level="1" scaling="Hex16">
<table name="Code" type="Static X Axis" elements="1" scaling="Hex16">
<data>Hex16</data>
</table>
<table name="Address" type="Static Y Axis" elements="10">
<data>C250</data>
<data>C252</data>
<data>C254</data>
<data>C256</data>
<data>C258</data>
<data>C25A</data>
<data>C25C</data>
<data>C25E</data>
<data>C260</data>
<data>C262</data>
</table>
</table>

<table name="Rear 02 Sim Subroutine" category="Rear_02" address="4a000" type="3D" level="1" scaling="Hex16">
<table name="Code" type="Static X Axis" elements="1" scaling="Hex16">
<data>Hex16</data>
</table>
<table name="Address" type="Static Y Axis" elements="20">
<data>4A000</data>
<data>4A002</data>
<data>4A004</data>
<data>4A006</data>
<data>4A008</data>
<data>4A00A</data>
<data>4A00C</data>
<data>4A00E</data>
<data>4A010</data>
<data>4A012</data>
<data>4A014</data>
<data>4A016</data>
<data>4A018</data>
<data>4A01A</data>
<data>4A01C</data>
<data>4A01E</data>
<data>4A020</data>
<data>4A022</data>
<data>4A024</data>
<data>4A026</data>
</table>
</table>
--- end here (do not add this line) ---

Then launch ECUFlash. The stock table data values should be (hex data):

Rear O2 sim hook
E408
D525
6613
D002
400B
0009
A002
0009
0000
D6A2


Rear O2 sim subroutine
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF


Change the table data to ("0x" must precede all entries, e.g., 0x0009, 0xD002, etc):

Rear O2 sim hook
0009
0009
0009
D002
400B
0009
A002
0009
0004
A000


Rear O2 sim subroutine
DA06
6AA1
6AAD
4A09
DB05
6BB1
6BBD
4B09
4B01
3ABC
DB03
2BA1
000B
0009
FFFF
6A64
FFFF
6B36
FFFF
6A68


Upload the modified ROM to your ECU, and no more rear O2 CELs.

EDIT: Removed some duplicate values.

EDIT (March 15, 2008): Cleaned up the sim subroutine code. Now four lines shorter.

JrCRXHF

Will this work on the 88590013 files as well?

supersnow

iTrader: (6)

Good question!