Evo X Logging
And thanks again to tephra for figuring out mode23 and hamish for integrating it. So for those variables that we could get through either CAN or Mode23, which is faster?
Thanks for helping Hamish out with the testing!
Hello all. Excuse my ignorance. My friend is using romid: 52360016
Is the correct sequence of events that I need to follow to get EvoScan logging?
1. upgrade evoscan to the beta just posted, simply extract files to the evoscan program folder and overwrite existing files
2. identify the three xml elements which identify for ecuflash the bytes which need to be changed in the rom
3. edit the file for my rom located in:
/c/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo
4. add the 3 xml elements as the last children of the "rom" element
5. open the cars current rom file with ecuflash
6. edit the new tables identified, for example, if listed is "IFMode 0x05 -> 0x23 #1"... this means i must change the existing value of "0x05" to "0x23" and this changes that byte.
7. flash the car with the adjusted rom
8. change the evoscan "data.xml" manually with what i want to log. but I will probably need to wait for someone to find the addresses for my particular rom?
Hope I got the steps right. Thanks for all your help. Tephra I need to send you some money and evo4mad thank you for making EvoScan.
Is the correct sequence of events that I need to follow to get EvoScan logging?
1. upgrade evoscan to the beta just posted, simply extract files to the evoscan program folder and overwrite existing files
2. identify the three xml elements which identify for ecuflash the bytes which need to be changed in the rom
3. edit the file for my rom located in:
/c/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/evo
4. add the 3 xml elements as the last children of the "rom" element
5. open the cars current rom file with ecuflash
6. edit the new tables identified, for example, if listed is "IFMode 0x05 -> 0x23 #1"... this means i must change the existing value of "0x05" to "0x23" and this changes that byte.
7. flash the car with the adjusted rom
8. change the evoscan "data.xml" manually with what i want to log. but I will probably need to wait for someone to find the addresses for my particular rom?
Hope I got the steps right. Thanks for all your help. Tephra I need to send you some money and evo4mad thank you for making EvoScan.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yeh I am investigating hooking the wb analogue output upto the rear02 sensor (like we do for CT9A)
even with evoscan this is my preferred method of logging WB02 - less cables, less LC1 screwup's, much much faster logging
even with evoscan this is my preferred method of logging WB02 - less cables, less LC1 screwup's, much much faster logging
thanks just sent you $30 via paypal from bjv@---------.com.
Being the greedy and impatient bastard that I am... could anyone help me with a data.xml logging a few basics like rpm, timing, knock, tps, etc?
romid is: 52360016
Rom can be found here: http://clubctrl.com/jonathan_original.zip
Thanks!
romid is: 52360016
Rom can be found here: http://clubctrl.com/jonathan_original.zip
Thanks!
Or am I being stupid and the data.xml that comes with beta14 will work fine? My ROM is a JDM.
Did some quick testing tonight using the latest beta of evoscan. I'm still figuring out how to make the logs show everything I want, but here's what I got so far:

When I try to graph vs. RPM it seems to smooth out the data too much. What am I doing wrong?

Also I changed the 14.5 in the PSI formula to 12.73 since I'm at ~4000 feet.

When I try to graph vs. RPM it seems to smooth out the data too much. What am I doing wrong?

Also I changed the 14.5 in the PSI formula to 12.73 since I'm at ~4000 feet.
Last edited by TravisF; Jun 8, 2009 at 07:57 PM.



