Hi,

I have a 2014 EDM Lancer Evolution X 5MT.
Rom ID: 50845084.

"Mode 23 - IFMode 0x05 -> 0x23 #1" is OK
"Mode 23 - IFMode 0x05 -> 0x23 #2" is OK

"Mode 23 - DoMode 0x4B -> 0x5B" gives me a "no match"

The definition file that comes with EcuFlash seems to be incorrect.
Anyone that could help me?

attached rom and screenshot.

 

Don't proceed with that edit! Something is amiss.



I took a closer look at this.


I actually have concerns about "50845084" ROM ID being read correctly in the first place.

It looks to me like EcuFlash is looking at the ID digits in the same place it has always looked... but that the digits themselves have shifted!


In my 53610013 ROM, that block looks like this...

0x50028 53 61 53 61
0x5002c 00 13 00 00
0x50030 00 43 00 00

But in the "50845084" ROM I have here, it's laid out like...

0x50028 50 84 50 84
0x5002c 50 84 50 84
0x50030 00 02 00 00



This means the ROM might be "50840002" or "50840003", but we don't see the second half (0002 or something else)...

...which means EcuFlash can't tell one incremental point-release from another.


And then stuff like this would happen... at some point. Which could be today.


There's a forum member directly from Tactrix on EvoM, isn't there? Could someone please pm them, and point them at this thread?

I reckon EcuFlash needs to identify these ROMs differently.


Rich

 

I might have figured out this myself. Not tried yet though.

"Mode 23 - DoMode 0x4B -> 0x5B" was looking at address "8ae5b"

It should be address "8ae5a" I think.
When compared to other roms the address that it points to is always the address before "4B"

I'm am no expert on this. And any help is appriciated.

richardjh, thanks for the reply.
I have actually tried to flash this (inputted 0x5B manually). The flashing works fine, but when I try and log the idle is all over the place. So I flashed back to last working rom.

 

I have not seen an EDM rom for a 5MT beyond the 5691xxx roms down in Australia.
However the final edition rom is something different so maybe the same as this.
I'll have a look at it...


and yeah the 5084 repeating thing doesn't look right
the NA roms changed the identifier placeholder aswell from memory?


edit nope 52690002 is the aussie FE rom
mivec/timing the same, fuel a bit leaner, boost I haven't got yet

 

Changed the address with one place, "8ae5a" Works fine. Now I need to figure out the addresses for logging in evoscan.

 

any update on this?

 

Could somebody help me with addressed for logging in EvoScan?

 

For the brave of heart, this 5084 ROM is included in the RAX Patch v3 "limited public test" phase...

https://www.evolutionm.net/forums/ec...est-phase.html

...which includes RAX Fast Logging. Paired with EvoScan set to "RAX Fast Logging" mode, that eliminates the need to know any ROM-specific logging addresses. It all just works...

Just bear in mind, this stuff is still in its trial phase.

Rich

 

richardjh, Can the RAX Patch be used together with stand alone logging with Taxtrix OpenPort 2?

 

Not without a large amount of messing around, no. Not at present. It would either need some extra smarts to pull logging items out of the block-read bit-mashed data, or post-processing of "gibberish" looking logs to extract the various items out.

Rich

 

yeh i defined the 50845084 from an 2014 or 2015 EDM car...

if the mode23 stuff is wrong (and for somereason it is on a lot of ecuflash defs) as you have found its off by 1 byte (usually)...

 

Tephra or Richardjh, could one of you help me find the logging addresses in my ROM?

Only found the RPM one for now.
Will of course give you a donation for your time spent doing this.

 

5002e looks like the address for the ROM id, which is weird. ID should be a 50840002.

 

Sorry to hitchhike... Are you having 50855085 (2014+ EDM SST) available?

 

Hi I'm also using the 50845084 definition file on a EDM Evo 2014.
Thanks for the tip, after changing DoMode adress as you mentioned, it doesn't idle as crazy anymore if you start a log on evoscan.
"Mode 23 - DoMode 0x4B -> 0x5B" was looking at address "8ae5b"

Have you found a definition file for evoscan? would be great if you can share.

Thanks!