LaXGSR

Thanks so much SiC!! I was just about to ask for that 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?

SiC

iTrader: (1)

I think the stand alone mode23 is quicker but this new build of Evoscan is way faster than before, we were getting 120/sec on my mini laptop (EeePc). The good thing is that now it's in Evoscan so you can hook up your WB O2

LaXGSR

Yes, you won't believe how frustrating it was for me to take mode23 logs and wb02 logs separately this past weekend Thanks for helping Hamish out with the testing!

crcain

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.

tephra

iTrader: (6)

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

tephra

iTrader: (6)

crcain - yup you got it right

crcain

thanks just sent you $30 via paypal from bjv@---------.com.

tephra

iTrader: (6)

thanks man

crcain

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!

crcain

Or am I being stupid and the data.xml that comes with beta14 will work fine? My ROM is a JDM.

crcain

And can I upgrade direct from 2.5 to 2.6beta14? Or must I be on a previous 2.6beta?

LaXGSR

The data.xml that comes with it should work for JDM according to SiC. Also, you can just install 2.5 and copy the 2.6 beta 14 .exe and data.xml files in. That should work fine.

SiC

iTrader: (1)

^ Yes, it'll already work with the JDM 5236 & 5237 series without touching the Data.xml

TravisF

iTrader: (1)

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.

bluexgyr

Can anybody help with an XML for 53040010 so i can make these changes.
Sorry for any inconvenience