Evo X Logging
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yes sorry NJ I should have been more specific.
once you find the MUT_TABLE (as per CT9A) you can then use that as a common reference point for most useful memory addresses
ie MUT0F is ALWAYS the STFT, so in ANY rom if you find the MUT_TABLE then you can find MUT0F easy enough. and therefore you can see the memory address for MUT0F, which will the the STFT
once you find the MUT_TABLE (as per CT9A) you can then use that as a common reference point for most useful memory addresses
ie MUT0F is ALWAYS the STFT, so in ANY rom if you find the MUT_TABLE then you can find MUT0F easy enough. and therefore you can see the memory address for MUT0F, which will the the STFT
hi,
one question, i'm not sure if i'm seeing it right..but i got the 55570005 xml file from GST's link (i assumed that it is ok to download/copy
)...so i used that and applied the necessary changes for the mode 23 for this specific xml file...i noticed that there are no mivec maps...do i have the right xml file? TIA
anthony
one question, i'm not sure if i'm seeing it right..but i got the 55570005 xml file from GST's link (i assumed that it is ok to download/copy
)...so i used that and applied the necessary changes for the mode 23 for this specific xml file...i noticed that there are no mivec maps...do i have the right xml file? TIA anthony
2010 USDM Evo 10 GSR - 55570005
http://norcalmotorsports.org/users/b...ch/2010_evo10/
2010 USDM Lancer Ralliart - 55590006
http://norcalmotorsports.org/users/b.../tech/2010_RA/
- Bryan
http://norcalmotorsports.org/users/b...ch/2010_evo10/
2010 USDM Lancer Ralliart - 55590006
http://norcalmotorsports.org/users/b.../tech/2010_RA/
- Bryan
Hi Bryan,
i downloaded the evo10base from your url...and i still don't see the mivec maps...i had a back up of the evo10base from ecuflash itself...i reverted it back now i can see the mivec maps...are there any important modifications in the evo10base from your evo10base? TIA
anthony
i downloaded the evo10base from your url...and i still don't see the mivec maps...i had a back up of the evo10base from ecuflash itself...i reverted it back now i can see the mivec maps...are there any important modifications in the evo10base from your evo10base? TIA
anthony
Newbie
Joined: Aug 2009
Posts: 22
Likes: 0
From: Calgary
trouble logging 2009 EVOX MR
Car: 2009 EVOX MR (54070007)
I modified the xml for 54070007 per the 1st post and enabled mode23. Evoscan 2.7 beta can connect with openport 2.0 cable but the data values are not correct, other than RPM and ign advance.
Am I missing a file for evoscan? Any other logger that would work?
Thanks.
I modified the xml for 54070007 per the 1st post and enabled mode23. Evoscan 2.7 beta can connect with openport 2.0 cable but the data values are not correct, other than RPM and ign advance.
Am I missing a file for evoscan? Any other logger that would work?
Thanks.
Newbie
Joined: Aug 2009
Posts: 22
Likes: 0
From: Calgary
once you find the MUT_TABLE (as per CT9A) you can then use that as a common reference point for most useful memory addresses
ie MUT0F is ALWAYS the STFT, so in ANY rom if you find the MUT_TABLE then you can find MUT0F easy enough. and therefore you can see the memory address for MUT0F, which will the the STFT
ie MUT0F is ALWAYS the STFT, so in ANY rom if you find the MUT_TABLE then you can find MUT0F easy enough. and therefore you can see the memory address for MUT0F, which will the the STFT
Newbie
Joined: Aug 2009
Posts: 22
Likes: 0
From: Calgary
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Well your going to need mode23 addresses anyways.
If you have a 100% stock ROM you can email it to me <myforumname> @ gmail.com and when I have time I will give you the MUT_TABLE + mode23 addresses...
If you have a 100% stock ROM you can email it to me <myforumname> @ gmail.com and when I have time I will give you the MUT_TABLE + mode23 addresses...
Newbie
Joined: Aug 2009
Posts: 22
Likes: 0
From: Calgary
I found the mode23 address at the beginning of this thread so that is taken care of. I just sent you the stock ROM. Thanks.
Newbie
Joined: Oct 2009
Posts: 60
Likes: 0
From: Los Angeles
For example in 55570005
MUT Table is at 3f244
now when you look at the table in Ecuflash and you know the RequestId from evowiki you can write
logging item in EvoScan.
Example:
0D LTFTMid Fuel Trim Mid (LTFT) % (x-128)/5
Request number is 0D in MUT table so you take value from MUT0x row and D column which is 804575, now you take it and write mode23 EvoScan item as 23804575 using scaling from evowiki
Hope it helps.
MUT Table is at 3f244
now when you look at the table in Ecuflash and you know the RequestId from evowiki you can write
logging item in EvoScan.
Example:
0D LTFTMid Fuel Trim Mid (LTFT) % (x-128)/5
Request number is 0D in MUT table so you take value from MUT0x row and D column which is 804575, now you take it and write mode23 EvoScan item as 23804575 using scaling from evowiki
Hope it helps.
