Evo X Logging
#841
Evolved Member
iTrader: (11)
Just a few notes for USDM users of the code provided by SiC:
In the "Mode23 USA EVOX" and "Mode23 USA RA EVOX" area of EvoScan the formula for throttle positions is "(x-32)*129/255" instead of "x*100/255" Not sure why it is different, and not (yet) sure which one is correct for us to use.
All temperatures provided by SiC are in metric units. For US units use "1.8*x-40" instead of "x-40"
Speed provided by SiC is in kph. For MPH use "1.26*x" instead of "x*2"
Thanks,
Keith
#844
Evolved Member
iTrader: (6)
Just a few notes for USDM users of the code provided by SiC:
In the "Mode23 USA EVOX" and "Mode23 USA RA EVOX" area of EvoScan the formula for throttle positions is "(x-32)*129/255" instead of "x*100/255" Not sure why it is different, and not (yet) sure which one is correct for us to use.
All temperatures provided by SiC are in metric units. For US units use "1.8*x-40" instead of "x-40"
Speed provided by SiC is in kph. For MPH use "1.26*x" instead of "x*2"
Thanks,
Keith
In the "Mode23 USA EVOX" and "Mode23 USA RA EVOX" area of EvoScan the formula for throttle positions is "(x-32)*129/255" instead of "x*100/255" Not sure why it is different, and not (yet) sure which one is correct for us to use.
All temperatures provided by SiC are in metric units. For US units use "1.8*x-40" instead of "x-40"
Speed provided by SiC is in kph. For MPH use "1.26*x" instead of "x*2"
Thanks,
Keith
#854
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
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.
#855
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