Hi all

I'm new to Evo's and EcuFlash and looking for some help to read the ROM currently on the ECU, I recently got a 2004 JDM Evo 8 MR with the usual bolt-on mods - TBE, HKS Intake kit and IC hard piping kit and a Grimmspeed 3 Port and I'm trying to figure out if the ROM has been modified or returned to a stock map.

I'm using a OpenPort 1.3U cable and EcuFlash v1.44. I've been able to download the ROM successfully using EcuFlash 1.44 but when reading the ROM all the scaling seems off see below maps as an example, I'm using the default 2004 JDM Lancer EVO 8 and evo7base definition xml files. The ROM ID is 96260007.




Any help would be great, my next step is to try downloading the ROM using a older version of ECU flash to see if that does anything.

Cheers,
V

 

 

Cheers for trying it out.

I've tried re-downloading, using different versions of EcuFlash 1.32, 1.38 and 1.44 and different operating system Windows 7 and 10 - with all versions I was able to download the ROM successfully and all have the same scaling issue. Would this mean the map has been modified and whoever tuned it had a custom definition/xml file?? Or could it have been re-mapped using a different tool/software?

 

Anyone else have any ideas for my to try?

I was thinking of flashing the stock 96260009 ROM to the ECU which I found on these forums...but I'm keen to know if the current map has been modified.

 

Hi, in your ECUFLASH Rom Metadata folder do you have multiple copies of the rom file? If so, rename the original versions to something else, and make sure the downloaded one is the only one named correctly, if that makes sense. Also, from the two tables you are showing, they look pretty stock, compared to other EVO 8 Stock rom data.

 

See above pic: NOtice how I have the 94170715.xml named correctly, but lower in the pic you see Orig.94170715.orig.xml... THis is so I ecuflash wont use the one named "orig" before and after the rom #.

 

Use 1.44, dont worry about Operating SYstem, most likely it is in one of your XML's. Ill take a quick look.

 

Its the XML you are trying to use.
Have a gander at both of these:
https://evoecu.logic.net/wiki/96260009
https://www.evolutionm.net/forums/ec...6530706-a.html

You may have to do a little work here. Read up. Look at everything related to the above hyperlinks. I also happen to have the 96530706 Rom as well, or you can download it in the V7 thread.

 

Raceghost - Thanks for the reply, I've been away for work and only just had time to get back to the Evo.

I have setup EcuFlash to point to a rom metadata folder I created which holds only two xmls at a time, the evo7base xml and any xml that I'm trying out (just so I know its definitely looking at the xmls I'm working on). So far no luck with xmls I have found online for 96260007 or 96260009. They all seem to have same or slightly different scaling issues.

Is there such thing as a 96260007 Tephramod v7 xml file? just in case its running a version of a tephramod rom?

 

Why not just rescale the load and rpm bars and call it a day? Would take less then a minute to do. Is there something else odd its doing?

 

 

If you don't intend to use e85 in the next year or so then 96260007 is fine. All 9626 rom variants are good for that matter from a tuning point of view.

If you do intend to go with ethanol then you should migrate your tune over to one of the Tephra dual map roms, either Tephrav5 96260512 or Tephrav7 96260709.
Both are excellent but v5 is somewhat easier to tune, especially if the setup has only mild mods.
In any case, you will need a decent xml definition file so you can see the mapping correctly in EcuFlash.

 

Thanks for the reply Merlin.oz, I'm not planning to use e85 anytime soon but I would like to familiarize my self with the Tephra roms. I'm leaning towards flashing a base Tephra v7 rom and starting from there. Would I be best of donating to Tephra and get the JDM 8 MR rom and xml? (96260009)