Evo_Goodness

Can anyone help me with this i got the MUT table working but there seems to be no definitions for 2 byte load or RPM or airflow for this rom anywhere online its driving me nuts..
So if no one has it can i just use a different 2004 EVO 8 rom and move all my stuff to it such as imob codes and stuff will it even fire up im confused this seems to be the only evo 8 USDM rom with no definitions for this....




PS yes i searched the official 2byte load thread few people asked for it but never got an answer

merlin.oz

Unless you are willing to pay for a decent definition xml then yes you are best served by moving to a well supported ROM, like 94170715 TephraMadv7.

LetsGetThisDone

iTrader: (1)

Yeah, just move to a 9417 ROM. It'll run fine.

Evo_Goodness

Problem is moving to 9417 is the big maps in still learning them and a little afraid I might mess it up I know sounds dumb but not sure if I got it right or not hoping to start learning on just a standard rom and work my way up to big maps and speed density

Evo_Goodness

Wait can I move to the standard 94170015 rom and not use tephra just learning my tuning and wanted to start with standard maps

Biggiesacks

yah that should work no problem, its the universal USDM evo 8 rom, which is why the tephra v7 94170715 is based on it.

Evo_Goodness

okay gotcha man thanks before i jump on it and do it do i need to move all 4 under the ECU listing such as. (init code/immobilizer/immobilizer HEX/ECU internal ID)
Or is it just the first 2 ?

roni4g63

iTrader: (1)

I know you want to stay on the standard size map, but I think the tephra modified roms do need need the imob hex to operate, someone please correct me if i am wrong

Evo_Goodness

Yes from what I have read tephra has 2 that you don't touch or the rom changes. I'm wondering about a normal stock rom though though is it all 4 of them I just want to start with a basic stock map that I can get 2 byte load on tune it and move up to tephra big maps

Biggiesacks

its just immobilizer and immobilizer hex. Shops use to change the init code to "Lock" the ecu.

Evo_Goodness

Okay sweet man even the ECU internal ID can be left alone then figured it would need all that stuff sweet

Biggiesacks

yah you need the internal id to match the actual rom your using so that your definition file in ecuflash is correct, otherwise it will reference the wrong memory addresses for that rom. So if your using a 94170015 you want to make sure the ID is 94170015 so that ecuflash loads the correct xml definition file.

Evo_Goodness

Okay I get it now just don't want to mess anything up thanks for all the help on this man

Biggiesacks

your welcome, asking questions is a good sign.

Evo_Goodness

Hmm after flashing it it fires up everything seems good but now my anti lock light flashes with my 1.3u cable plugged in as soon as it's unplugged it goes away is that something Mitsubishi added on later roms.? Doesn't seem to affect anything