here is also the min AFR log

 

finally tha Knock Max counts.

i will apriciate any help in LoadCal as i am still cant find why it is not correctly calculated. at least am sure that it shouldnt reach 300 according to my boost level.

 

jjf

i did modify the protocols.XML file as per your post. so i was able to log the AFRMAP successfully using LogWorks2. (if any body want the file i can forwaded to you)

then i used the evoscan approach as it is more accurate than mitsulogger.

attache is the math trace formula.

why it is still not accurate. as if i used the same rpm and ignition timing degrees to determine the load from the stock map, i can find differences.?

 

@fbikawi
What is your ECU ID?
I have just found the 2 Byte load addresses for an EVO 7, id 99860002
Maybe this will help you out.

 

I changed my injector latency to a static value .. I think that's your problem ..

If everything is stock .. even our injector latency values are different from the USDM Evos

Use this as your injector latency computation
(-0.1026*battery)+1.9226 ..

 

JoeBee,

my ecu id is 98640014..it is different. i am not sure about 2 byte load, but i tried using mitsulogger to check 2 byte load and the data reading speed were very slow with funny figures for all sensors?


gunzo,

u are my hero. yes your formula is correct i check it with the Injector Battery Voltage table in my stock map and it is working.

4.69 = 3.312
7.03 = 1.680
14.06 = 0.480
18.68 = 0.240

i will change the formula in LogWorks to calculate correct injector latency. it should work.

thanks for all. and still interested to know about 2 byte load.

 

You can try the 2 Byte Load here:
https://www.evolutionm.net/forums/sh...46#post4071146

 

Hi

This is the same ECU ID as mine, I run a hex modifed to output real load, I can post up the ECUflash xml changes if you like.

MB

 

great, please do. and if you can attach the xml file i will appriciate it.

till now i couldnt log the real load.

thanks

 

Looking at your knock sums you posted, you have a few up there at the 5 counts. You might want to re visit the fueling and timing to reduce that. try to keep it at mo more than 3 counts anywhere. I usually do several back to back 1-4 WOT runs then check the last one for knock. That way you factor in heat soak . AFR looks OK so maybe take out 1 degree in the affected load cells. What boost are you running 1.7-1.8 bar?

Milburn

 

that is the problem i am running only 1.3 bar (1.5 spike) and the load calculation is not correct.

i am tring to understand how to log real load (2 byte)?

 

Note this will only work for a JDM 7 using 98640014 xml deff.
Add these lines to your xml def for ecuflash


<table name="RequestID00" category="Misc" address="2e9e2" type="1D" level="1" scaling="uint16"/>

<table name="RequestID01" category="Misc" address="2e9e6" type="1D" level="1" scaling="uint16"/>

Then change RequestID00 to 34908 and request ID01 to 34909 in ECUflash, you can now log real load in Mitislogger or Evoscan with the appropeiate additions for each logger

Evoscan
<DataListItem DataLog="Y" Display="Load0" LogReference="Load0" RequestID="00" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="Load1" LogReference="Load1" RequestID="01" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="2byteLoad" LogReference="2byteLoad" RequestID="FF" Eval="((256*[Load0])+[Load1])*0.3125" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="2 byte load read from ECU" />

Mistislogger

<Request LogReference="requestID00" RequestID="00" Eval="x" Unit="INT" Logged="y" Response="2"/>
<Request LogReference="requestID01" RequestID="01" Eval="x" Unit="INT" Logged="y" Response="2"/>

<Request LogReference="Load" RequestID="FF" Eval="((256*requestID00)+requestID01)*10/32" Unit="2byteLoad" Logged="y" Response="2"/>

ROM file changes courtesy jcsbanks, loggers a couple of smart people on here who unfortunately I can't remember, beer has interfered in this process.

MB

 

I think gunzo should give all 7 owners on here an outing in his works ride, I'm sure he can get a "D" for a few days..................."I have control...oh cr@p"

MB

 

i did the above modifications and i will try it later today. i think it will work

thank to burgers22, JoeBee, gunzo, jcsbanks and all the other great guys.

i dont feel lonely any more being an EVO VII driver while most others driving EVO VIII. we have a great EVO VII group here.

 

Yes you should try !! nothing beats afterburn !!


My fastest timing 1.75M / 1185MPH / 1896KMH