ravasquez

Hi everyone, I'm asking for help with some issues that my car came with, I brought a Evo V GSR with a TME ECU (TME 2000 GSR) here is my rom info:



So, my issues are this:

1) My MPG sucks is about 9 and I see that my low and high octane fuel map are equal here an image, its OK? How can I improve my MPG?



2) My idle almost of time is in 1k and some times 2k without AC how can I put this back to factory? (750 rpm).

3) I don't know if my current boost level are safe for my engine, because the detonations which I assume because the rich AFR, both gauges measures 21 psi I have two because my turbo timer haves boost gauge and I have a blitz analog gauge on a pod.

I would really appreciate any help, I'm really worry about my engine health because the detonations.

Update 1: I'm on research about my issues, I find a post in the forum talking about the injectors so I check mine and the car have brown injectors, then I search about them and is from the Evo VIII (560cc) so I think its ok, there no upgrade because the V have 560cc injectors, or its an upgrade?

Update 2: I attach log files.
EvoScanDataLog_2017.04.13_13.38.45.csv

merlin.oz

I suggest you reflash with a stock tune and work from there.
Your fuel maps are not the best and who knows what the rest of the mapping is like.
Start with a clean stock tune, or find a decent local tuner.

ravasquez

Thanks for your reply I would do it, there's any way to get a stock rom for my V? I update my post with logfiles.

Update: I already find a stock rom for my V (from here https://evoecu.logic.net/wiki/22580006), but its safe to flash this? My doubt is because I have a EVO VI TME ECU, I open the MUT table and both look very different with the current rom. Sorry about so many questions but I'm new in this stuff.

merlin.oz

the 22580006 rom is an Evo5 Ralliart rom, so there is nothing wrong with flashing that into the car.

Except that the typical flashing xml for that rom is setup for an Evo5 ECU, and the Evo65 requires a slightly different setup xml as it uses a different CPU chip (FA suffix).

And of course you will need a Tactrix OpenPort2 to flash either of these anyway, which I presume you already have.

You would probably be better off with flashing a stock Evo65 TME 27370001 rom.
As xml for this rom is already setup for the TME ECU.

If you intend to embark on an extensive tuning and upgrade program, bigger turbo and injectors etc, then your best rom would be the 27570000 CedyMods rom, which has dual map capability and CEL flash on Knock plus some other goodies.

ravasquez

Thanks again man, I will search for the 65 TME stock rom. I found one rom here in the forum but this one is from some one asking for help about getting better MPG and enable ceddymods, I already downloaded the ceddymods rom from his website, my ecu part number is mr514364 so this have the CPU chip FA?

BTW yes I have the OP 2.0 with the flash cable and reflash adapters

Update: After reading a lot about ECUflash my rom info says I have a MH7202F memory model and internal id 27370001 in this xml file I find that the mem model is MH7202FA I have to change this to match mine? Or is irrelevant? This is the rom info of the stock TME rom I find:



Sorry again about so much questions but I'm scared to brick my ECU, in my country is really hard to find EVO parts.

Update 2: I would let all this info here because can help somebody newbie like me, in the beginning of tuning can be a little frustrated because out there is not a 101 guide, well there some like a 101 but use a lot of technical terms and its complicated if you came with 0 knowledge, so to the point, I found the ceddy mods rom for Evo V through VI and because merlin.oz recommends this rom if in my plans is some extensive tune and actually its my plan, this rom comes in a zip file which have's the rom (.hex) an xml file (definition file) and a file for evoscan (xml file inside evoscan folder) these files goes in the paths as the ceddy mods site says its very easy and clear instructions, so this rom in my situation can be flashed because match my car, so at this point I would really recommend to go step by step, for example I would touch any thing right now, first I would flash my ECU if every thing its ok then I would start to mod stuff, why? Because my car haves a mediocre tune and gives me a lot of issues, so tomorrow I would upload some pics and logs from my new map, thanks again for your help merlin.oz respect!

merlin.oz

Yes the memmodel should be H8539FA for a TME ECU.

ravasquez

There's any way the last time the car was tuned the guy change that? In my current Rom says is without the A

ravasquez

I have this error while trying to flash, any ideas my friend merlin.oz?

[10:31:33.152] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:31:33.152] Device Firmware Version: 1.16.4769
[10:31:33.152] Device Serial Number: TAkIZ9Ji
[10:31:36.171] sending init sequence 2
[10:31:36.171] got 0x13 response instead of 0x11
[10:31:36.171] sending init sequence 3
[10:31:36.543] entering bootloader
[10:31:36.543] sending kernel size (2029)
[10:31:36.543] sending kernel load address (0x0000F000)
[10:31:36.558] uploading kernel
[10:31:36.907] verifying kernel checksum response
[10:31:36.911] kernel valid
[10:31:37.129] kernel get version
[10:31:37.129] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.07
[10:31:37.129] reading kernel comm buffer size
[10:31:37.145] comm buffer size set to 256
[10:31:37.145] reading kernel flash buffer size
[10:31:37.145] flash buffer size set to 1024
[10:31:37.160] -- flashing image to ECU memory --
[10:31:37.566] -- comparing ECU flash memory pages to image file --
[10:31:37.566] seg start len ecu CRC32 img CRC32 same?
[10:31:37.700] LB7 00010000 00003000 ED239356 63A2F553 NO
[10:31:37.716] SB0 00013000 00000200 BD7BC39F BD7BC39F YES
[10:31:37.738] SB1 00013200 00000200 BD7BC39F BD7BC39F YES
[10:31:37.753] SB2 00013400 00000200 BD7BC39F BD7BC39F YES
[10:31:37.753] SB3 00013600 00000200 BD7BC39F BD7BC39F YES
[10:31:37.769] SB4 00013800 00000200 BD7BC39F BD7BC39F YES
[10:31:37.785] SB5 00013A00 00000200 BD7BC39F BD7BC39F YES
[10:31:37.800] SB6 00013C00 00000200 BD7BC39F BD7BC39F YES
[10:31:37.816] SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
[10:31:38.004] LB6 00014000 00004000 EA3E3443 EA3E3443 YES
[10:31:38.206] LB5 00018000 00004000 BEF6372A 1D24B383 NO
[10:31:38.392] LB4 0001C000 00004000 690B37D3 690B37D3 YES
[10:31:38.593] LB3 00020000 00004000 824D955A DA119098 NO
[10:31:38.794] LB2 00024000 00004000 2A89DA00 2F495D12 NO
[10:31:38.980] LB1 00028000 00004000 6A780468 745F22F6 NO
[10:31:39.182] LB0 0002C000 00004000 44965F77 37B0F9F3 NO
[10:31:39.182] kernel flash enable
[10:31:39.182] kernel blank flash page: addr: 0002C000
[10:31:54.294] WARNING: failed to erase page at 0002C000!
[10:31:54.294] kernel flash disable
[10:31:56.301] interface close

Update: I find this thread https://www.evolutionm.net/forums/ec...l#post10419873 and says that the TME ECU memory is H8539FA not H8539F I dint really know how this ECU has been flashed but its works now.