EVO X Logging

[Admin]

Hi Guys,
Graphical how to in the second post.

UPDATE: Evoscan 2.6b14 (and now b15) have Mode23 support integrated - You only need this thread for the XML modifications you must do for Mode23 to work
I have spent a fair bit of time looking at the ECU code and I have found a very nice function that we didn't have access to in CT9A-land.
OBD-Mode23 allows you to request ANY memory address and the ECU will fetch the current stored value.
I have tested this on my car - and it *sorta works*.
Hamish is currently integrating this into EvoScan so we should have support very soon.
Now when I say it *sorta works* the ROM needs a slight modification before you can access Mode23.
My preference for logging is that the ROM should be stock and everything should just work - but given our woeful logging experience thus far we are running out of options.
One downside with Mode23 is that every RAM address is unique to a ROMID, so the RAM addresses for 53040010 will be different to 52680018 - This isn't too bad, it will just mean someone needs to post up the relevant addresses for the ROMID in question.
HOWTO:
1) Apply the XML changes to your EcuFlash definition file, if you don't know what ROMID you are dealing with just ask. Modifications to ROM's can cause catastrophic results if you don't know what your doing
2) Download the application zip - in it will be an .exe and a config.txt
3) Edit the config.txt to suit your ROMID - We will be posting up config.txt's for common ROMID's so you can probably just download that.
4) Run the application.
Notes:
1) It's only a console application - so there is no fancy GUI.
2) It records every 5th row to screen, but EVERY row to the log.csv file
3) There isn't much error checking, so don't put anything stupid into the config.txt
4) In the config.txt file the evaluation expression is in RPN notation.
Application:
V1.1 - Is an attachment down here....
you also need a config.txt - I have included the one from my car 53040010 ... ENSURE YOU CALL IT config.txt and put it in the same directory as the .exe.
XML's:
NOTE: The name in EcuFlash describes what changes you need to make (ie 0x05 -> 0x23). IF the CURRENT value doesn't match here STOP AND ASK!!!
52690019
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f121" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8aafd" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8ab02" scaling="Hex16"/>
53040007 -> 53040010
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f145" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8aa59" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8aa5e" scaling="Hex16"/>
52680015 -> 52680020
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f121" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8ab11" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8ab16" scaling="Hex16"/>
52360018
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f58d" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8ada5" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8adaa" scaling="Hex16"/>
53600010
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7efbd" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8aa61" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8aa66" scaling="Hex16"/>
53050006 -> 53050009
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7f145" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8a9f1" type="1D" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" address="8a9f6" type="1D" scaling="Hex16"/>
54060007
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7efc1" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8aa7d" type="1D" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" address="8aa82" type="1D" scaling="Hex16"/>
54070007
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7efc1" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8aa69" type="1D" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" address="8aa6e" type="1D" scaling="Hex16"/>
55570005
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7f10b" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8ad5f" type="1D" scaling="Hex8"/>
<table name="DoMode 0x4D -> 0x5D" category="Misc" address="8ad66" type="1D" scaling="Hex16"/>
53610010
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7efb1" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8a919" type="1D" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" address="8a91e" type="1D" scaling="Hex16"/>
55590006
<table name="IFMode 0x05 -> 0x23 #1" category="Misc" address="7f107" type="1D" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" address="8ad43" type="1D" scaling="Hex8"/>
<table name="DoMode 0x4D -> 0x5D" category="Misc" address="8ad4a" type="1D" scaling="Hex16"/>

Cheers
Dave

[Admin]

Enabling mode23 is really quite easy but it took me an hour of reading though quite a few posts for it to click. hopefully this will help others save time. Do this at your own risk {thumbup}
1) Get an open port 2.0 cable
2)Install Evoscan(http://www.limitless.co.nz/) & ECU Flash(http://www.openecu.org/index.php?title=EcuFlash). ECU Flash contains the drivers you will need for the OP2 cable.
3) Head out to your car and hook up your OP2 cable to your laptop. Open up ECU Flash and download your current ROM.

4) Identify your ROM ID

5) go to the first post in this thread EVOX Logging by Tephra to get the changes you need to make the the xml metadata for Ecu Flash. The ROM ID you just got from above will tell you which 3 lines of XML you will need.

6) Open up your XML metadata definition file located at C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo
the definition file will have the same name as your ROMID
If your ROM looks like the next image then you will need to edit the base file it inherits from. In this example the ROM ID was 52680018. This ROM definition inherits from 52680015.


Copy the XML from step 5 and paste it BEFORE </rom>

7) open up (close it and re-open if is still open) ECU Flash and open the ROM you downloaded in step 3
8) You will now need to edit 3 values. The changes you made the the XML file add 3 entries under the Misc. header in ECU Flash

The 3 changes highlighted above tell you what your changing the values to.
The 1st entry you will change the value from 0x05 to 0x23
The 2nd entry you will change the value from 0x05 to 0x23
The 3rd entry you will change the value from 0x42 to 0x52


9) After making the 3 changes save your ROM and flash it back to your car

10) fire up Evoscan and start logging with mode23 enabled.
Evoscan beta 18 - verified


This thread is just a simple step by step how-to. Tephra gets full credit for enabling mode23. Any questions in regards to the steps I listed above I should be able to answer
please let me know if i missed anything

[Admin]

So after a brainwave I looked and found the counters pertaining to DTC discovery.
You know - how long does the ECU have to detect the condition for before pooping out a DTC?
Anyways here is my list so far:
53040010:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="631ea" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="631e0" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549c0" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549bc" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549be" type="1D" scaling="Hex16"/>
<table name="DTC P0247 Disable 0xF99F -> 0xF19F" category="Misc" address="92ba6" type="1D" scaling="Hex16"/>

52680015 -> 52680020:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="631ae" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="631a4" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549b2" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549ae" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549b0" type="1D" scaling="Hex16"/>
<table name="DTC P0247 Disable 0xF9DF -> 0xF1DF" category="Misc" address="9356a" type="1D" scaling="Hex16"/>

52360016:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="62b9a" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="62b90" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549a8" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549a4" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549a6" type="1D" scaling="Hex16"/>

52360018:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="631b2" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="631a8" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549b6" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549b2" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549b4" type="1D" scaling="Hex16"/>

52690019:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="631ae" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="631a4" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549b2" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549ae" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549b0" type="1D" scaling="Hex16"/>
<table name="DTC P0247 Disable 0xF9DF -> 0xF1DF" category="Misc" address="93556" type="1D" scaling="Hex16"/>

53040007:

<table name="DTC P1238 Disable 0x0384 -> 0xFFFF" category="Misc" address="631b2" type="1D" scaling="Hex16"/>
<table name="DTC P1241 Disable 0x03E8 -> 0xFFFF" category="Misc" address="631a8" type="1D" scaling="Hex16"/>
<table name="DTC P1235 Disable 0x0026 -> 0xFFFF" category="Misc" address="549bc" type="1D" scaling="Hex16"/>
<table name="DTC P1233 Disable 0x0028 -> 0xFFFF" category="Misc" address="549b8" type="1D" scaling="Hex16"/>
<table name="DTC P1234 Disable 0x0028 -> 0xFFFF" category="Misc" address="549ba" type="1D" scaling="Hex16"/>

IF THE BEFORE NUMBERS, ie 0x0384 or 0x03E8 or 0x26 etc, DON'T MATCH - then STOP and ASK!!!!!
OK - you need todo 1235/1233/1234 all together, otherwise you will still get codes if you JUST disable 1235

[Admin]

Hi All,
Just a quick announcement to say I think I have worked out how to disable the trims affecting WOT fueling.
Thanks to Acamus for some seriously hard core disassembling
Ok we all know how the Fuel Trims work, basically MAFHz bins, so Low/Medium/High
Usually High isn't used, here is why:

Left is stock, Right is my modified one
So the High FT won't be used unless the MAFHz goes above 1593.75, which won't really happen on stock turbo.
So I have modified the High bin so it's lower. And thus gets used.
Now here's the best part, because of how the STFT works, the High FT should really NEVER get populated with anything OTHER than 0%.
I have done a log and you can see the High FT being used in the fueling calculations, and you can also see it being set to 0%, so now I don't have my Cruise (Med) Trim affecting WOT.

<scaling name="LT Trim Hz" units="Hz" toexpr="x*6.25" frexpr="x/6.25" format="%.2f" min="0" max="1593.75" inc="6.25" storagetype="uint8" endian="big"/>
<table name="Closed Loop - LT Trim Control" category="Fuel" address="5557f" type="2D" level="2" scaling="LT Trim Hz">
 <table name="Conditions" type="Static Y Axis" elements="4">
 <data>Low -> Mid</data>
 <data>Mid -> Low</data>
 <data>Mid -> High</data>
 <data>High -> Mid</data>
 </table>
</table>

That's for 53040010, but also should work for 526800XX - If your values for above don't look very similar to mine then something's wrong.
If your interested in logging trims then find the MUT_TABLE - then you have the addresses you need to log:
MUT0F = STFT
MUT0C = LTFT_Low (Usually Idle)
MUT0D = LTFT_Medium (Usual Cruise)
MUT0E = LTFT_High (Usually not used, but that's what this MOD is all about)
MUT50 = Copy of the trim currently in affect
DISCLAIMER: DO NOT USE THIS UNLESS YOU HAVE A WIDEBAND AND LOG YOUR ECU
Cheers
D.