Mitsubishi Lancer Evolution 4/5/6/7/8/9 EvoScan Project v0.8

[mlr]

Maf frequency-is obd-style feature is actualy not connected to load value used in the tables - it has upper limit on 1600.But u can run MAF>2100 on evo.Actually engine sees what is the numbers of maf pulses between CAS pulses. So the limit is increasing proportionatly to rpm...I dont know exactly hov maf scale table works-but i suppose it uses maf pulses between CAS on one axis of the table and rpm on the other side of the table....

[Blak94GSX]

Update
- Added Coolant tmp
- Ability to remove some lines from the graph. (In settings).

Great work! Thanks for putting your time in on this. I am a big fan of donations towards otherwise free software if you could set up a simple page for the software with a PayPal donation link I would like to contribute for your efforts.

The next logical step I think is to add the ability to select which items to plot instead of having a finite list. Personally I like to look at Ignition Timing, TPS, O2 Voltage, and Knock Sum for tuning, and also graph the fuel trims and other sensors for review occasionally.

[alwaysinboost]

does anyone recall how to fix the coolant temp reading in EVOScan? I did the timing adjustment but don't recall seeing any posts about doing the coolant adjustment. Mine reads around 260+.

[alwaysinboost]

The ECU doesn't output over 1600Hz on the logger channel. The DSMs have always been that way as well.

bummer, I was able to get readings in the 1800's on my SAFC previously.

Mine actually stops recording at 1603.9Hz.

[Blak94GSX]

The AFC sits between the MAF and the ECU, so the AFC will display the full range. An OBD style logger gets the value from the ECU, and in this case the ECU won't report anything over 1600.

From a tuning standpoint, I don't think Airflow is particularly important anyway, but it is handy to know if you want to compare before/after changes to see if the pumping efficiency of the motor changed a measurable amount.

[alwaysinboost]

From a tuning standpoint, I don't think Airflow is particularly important anyway, but it is handy to know if you want to compare before/after changes to see if the pumping efficiency of the motor changed a measurable amount.

that is exactly why I like to see that value. For example running the airbox with the lid & without will give you different HZ values.

Thanks for that explaniation, it makes sense.

[shiftdsme]

any possibility of a direct download link from www.limitless.co.nz/evoscan for those who have already registered??

[Evo4Mad]

any possibility of a direct download link from www.limitless.co.nz/evoscan for those who have already registered??

I am away on holiday at the moment - back tomorrow, I will have the rest of all week of my holiday to play with programming this I will be emailing registered users an EvoScan v0.8 download link within the next 24hrs. Here is a preview of new features:

UPDATE:
1) Increased Datalogging Speed! yay.
- Added Log To File option
- Added Log To Screen option
- Added Logging SuperSpeed option
To get maximum speed - Disable Log To Screen, and Enable Logging Superspeed. Less effect is noticed on 2000ghz laptops with a/c power, but slower laptops or laptops running off the battery benefit a lot of speed!
2) Increased Stability of start/stop datalogger.
3) Added AYC Info to Data.xml
4) Added DTC Fault Code Info to Data.xml
5) New Log File Format! yay. - Thanks for all of your feedback on this - results now cross-tabulated with easy to use LogId/Date/Time/Seconds
6) Altered DataItem Calculations:
- Increased accuracy on FuelTrim calcs. (Fuel Trims: <100% (lean) >100% (rich) )
- Fixed accuracy on Timing Adv calc.
- Added DataLog="Y" to xml file for default datalogging items ticked.
- Implemented Multiple ECUs to XML file.
7) Added DTC Trouble Code Support
- DataLog Active/Stored Fault Codes
- Retrieve EFI Fault Codes
- Clear EFI Fault Codes
Added simultaneous WideBand SerialPort Logging Support (untested)
9) Added View Log Files Menu Item
10) Added ABS Info to Data.xml

[evo-mutsu]

does anyone recall how to fix the coolant temp reading in EVOScan? I did the timing adjustment but don't recall seeing any posts about doing the coolant adjustment. Mine reads around 260+.

Open Evoscan dir
\DataSettings\data.xml

change the formula from " + 308" to "+ 238"?

[evo-mutsu]

any possibility of a direct download link from www.limitless.co.nz/evoscan for those who have already registered??

I am away on holiday at the moment - back tomorrow, I will have the rest of all week of my holiday to play with programming this I will be emailing registered users an EvoScan v0.8 download link within the next 24hrs. Here is a preview of new features:

UPDATE:
1) Increased Datalogging Speed! yay.
- Added Log To File option
- Added Log To Screen option
- Added Logging SuperSpeed option
To get maximum speed - Disable Log To Screen, and Enable Logging Superspeed. Less effect is noticed on 2000ghz laptops with a/c power, but slower laptops or laptops running off the battery benefit a lot of speed!
2) Increased Stability of start/stop datalogger.
3) Added AYC Info to Data.xml
4) Added DTC Fault Code Info to Data.xml
5) New Log File Format! yay. - Thanks for all of your feedback on this - results now cross-tabulated with easy to use LogId/Date/Time/Seconds
6) Altered DataItem Calculations:
- Increased accuracy on FuelTrim calcs. (Fuel Trims: <100% (lean) >100% (rich) )
- Fixed accuracy on Timing Adv calc.
- Added DataLog="Y" to xml file for default datalogging items ticked.
- Implemented Multiple ECUs to XML file.
7) Added DTC Trouble Code Support
- DataLog Active/Stored Fault Codes
- Retrieve EFI Fault Codes
- Clear EFI Fault Codes
Added simultaneous WideBand SerialPort Logging Support (untested)
9) Added View Log Files Menu Item
10) Added ABS Info to Data.xml

awesome... cant wait

[mbaran]

Sweet, can't wait.

Will this version introduce load logging. It would be nice to log the (est) boost on the engine to make sure its hitting target.

Thanks again!

[mchuang1]

Sweet, can't wait.

Will this version introduce load logging. It would be nice to log the (est) boost on the engine to make sure its hitting target.

Thanks again!

No one knows the algorithm yet.

[shiftdsme]

one of the members of evolutionm.net came up with this as a starting point

http://forums.evolutionm.net/showpost.p ... stcount=13

and the thread is...

http://forums.evolutionm.net/showthread ... ht=evoscan

I finally made a few logs today and wanted to try to take a stab at the load formula. I know from my DSMLink experience that it is mainly based off of mass airflow/revolution, along with a few other variables that can change it slightly.

So, looking at my Evoscan logs with the logreader, I came up with this equation which seems to work pretty decently for my car. Maybe a few of you can test it out and see what you come up with:

Load = Maf Hz/ Engine RPM * some variable(s)

For my car I used the "some variable(s)" as a constant of 852, based on a few quick calculations.

So, for example in one of my logs, I was at 1308Hz at 4656 RPM (right at the end of a spoolup after going WOT in 2nd), and my EvoScan log showed timing as 2*.

So, 1308/4656*852=239 So, looking at the 240 load column in my stock map at 4500RPM, the timing value is 2. So that checks out.

Using one more data point: A different run at the top of third I had 1585Hz at 6781 RPM, and the log showed 17* timing.

1585/6781*852=199 So, in the 200 load column in my stock map at 6500, it is 15* timing and at 7000 it is 18* timing. So, 17* checks out there, too.


Obviously, this isn't an exact forumula since I used a constant where I know there are variables, but I think this may help a few people out to get an idea of what there load number is. I know someone already posted how to find what load column you are in, but if this load forumla checks out and you find a constant that seems to work on your setup, you can use the forumla to calculate what load column you are in when you are knocking and how much timing is being pulled as a result.


Eric

[gsrboi80]

brillant

[Evo4Mad]

I am searching high and low for the Load and Speed values all yesterday. Even did 2 hrs of driving logging