Fourdoor

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

Fourdoor

iTrader: (11)

UPDATE:

The Manifold air temperaturelogging doesn't work on my 2010 Ralliart, but everything else provided by SiC works great!

Keith

FTY Motorsports

iTrader: (2)

awesome thanks man i will test out on the 2010 GSR tomorrow and i will get the 2010 MR rom up ASAP

nj1266

iTrader: (6)

The TPS code in the 2010 Mode23 is different than the ones in Evoscan Mode23 2008. Should we change the code from "x*100/255" to "(x-32)*129/255"?

Clipse3GT

iTrader: (10)

Is there a way to LOG MAF Volts and MAF AIRFLOW in G/S in MODE 23 USA EVO X (for a 2008)?

tephra

iTrader: (6)

yes...

53040010:
MAFV:0x808f48:2:x,1023,/,5,*:1
AirFlow:0x8087d8:2:x,2,*,100,/:3

526800XX:
MAFV:0x808f50:2:x,1024,/,5,*:1
AirFlow:0x8087e0:2:x,2,*,100,/:3


Airflow for 526800xx is untested, let me know

Clipse3GT

iTrader: (10)

Thanks!!!

However here comes in my moment of slight knowledge deficit.

Where do I enter this information. Data edit in EVOSCAN?

Thanks!

tephra

iTrader: (6)

thats the format for my logger.

for evoscan just use notepad to edit the data.xml file

just copy one of the current entries (Load is a good one) and modify the address/name and Eval appropriately

Clipse3GT

iTrader: (10)

Thanks, I didn't check out this logger yet. I hope I will have a chance to try it out tomorrow and tell if these work.

nj1266

iTrader: (6)

Anyone know the request IDs for the 2010 USDM Evo X (55570005) for logging the following parameters:

LTFT- Cruise
LTFT - Idle
STFT
WGDC
WGDC Correction

Thanks a bunch

tephra

iTrader: (6)

use the MUT_TABLE and standard MUT request ID's to find them

WGDC correction wont be available.

tephra

iTrader: (6)

use the MUT_TABLE and standard MUT request ID's to find them

WGDC correction wont be available.

nj1266

iTrader: (6)

If I knew the request IDs for logging the parameters then I would not have asked. I would simply copy the code from the 08 xml and change the request IDs to those of the 2010, save, and test the logging on a 2010 car.

acamus

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.

tephra

iTrader: (6)

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