Confirmed: Evo ROM Can Be Flashed to Lancer ECU
Hey link i'm sure you remember bud but i still wanted to know if load and ipw were capping out 
If you wanted to log them directly can use these
Load limit:
Mut00 = 6A84
Mut01 = 6A85
Fuel cap
Mut02 = 6A90
Mut03 = 6A91

If you wanted to log them directly can use these
Load limit:
Mut00 = 6A84
Mut01 = 6A85
Fuel cap
Mut02 = 6A90
Mut03 = 6A91
Last edited by RoadSpike; May 28, 2010 at 12:53 PM.
i just went back in to my emails to get those muts and ask it they were it but u beat me to it and also lil update i dont think the knock light is working ive done a few logs and would accel or wot and make the light go on, did this multiple time and when i looked at my logs i didnt have any knock so the light was just flashing for no reason?
Last edited by link62; May 28, 2010 at 01:18 PM.
sure i didnt forget...
i just went back in to my emails to get those muts and ask it they were it but u beat me to it
and also lil update i dont think the knock light is working ive done a few logs and would accel or wot and make the light go on, did this multiple time and when i looked at my logs i didnt have any knock ur the light was just flashing for no reason?
i just went back in to my emails to get those muts and ask it they were it but u beat me to it and also lil update i dont think the knock light is working ive done a few logs and would accel or wot and make the light go on, did this multiple time and when i looked at my logs i didnt have any knock ur the light was just flashing for no reason?
Edit:
Link if you would put the coutdown timer muts into the 04 and 05 so we can see if its doing that during the test.
Last edited by RoadSpike; May 28, 2010 at 01:21 PM.
was it this mut?
Check Var:
MUT04 = 8D1E
MUT05 = 8D1F
edit: also forgot to mention that mdp does log in evoscan
Last edited by link62; May 28, 2010 at 01:39 PM.

here's the countdown timer variable
MUT04 = 8D06
MUT05 = 8D07
The check var may need to be logged later

Edit:
Of course I'll need the usual array of things like 1byte load and stuff
Last edited by RoadSpike; May 28, 2010 at 01:43 PM.
ok sending u the logs now
for the fuel, load one i did a bunch of wot pull to make it lean out
and for the knock one i did a bunch of short burst of accelerating to have the light flash
for the fuel, load one i did a bunch of wot pull to make it lean out
and for the knock one i did a bunch of short burst of accelerating to have the light flash
Ok so for the knock I don't see the timer counting down however there are random spots of knock sum in it so maybe thats setting the light off like it should.
For the WOT I see its capping it out to like 14.33 ms of pulse.
Lets try the load and fuel limit nobble its under miscellaneous default should be 0x2ab1 change it to 0x9. You'll need to be set to developer to see the table.
For the WOT I see its capping it out to like 14.33 ms of pulse.
Lets try the load and fuel limit nobble its under miscellaneous default should be 0x2ab1 change it to 0x9. You'll need to be set to developer to see the table.
Ok so for the knock I don't see the timer counting down however there are random spots of knock sum in it so maybe thats setting the light off like it should.
For the WOT I see its capping it out to like 14.33 ms of pulse.
Lets try the load and fuel limit nobble its under miscellaneous default should be 0x2ab1 change it to 0x9. You'll need to be set to developer to see the table.
For the WOT I see its capping it out to like 14.33 ms of pulse.
Lets try the load and fuel limit nobble its under miscellaneous default should be 0x2ab1 change it to 0x9. You'll need to be set to developer to see the table.
the knock light goes off all the time at accel so it hard to see if it real knock or not like in the log after the high 12 and 4 i kept accelerating and had the light go off but there was no knock present
ok ill i changed them is there anything i need to log for the mut or anything?
the knock light goes off all the time at accel so it hard to see if it real knock or not like in the log after the high 12 and 4 i kept accelerating and had the light go off but there was no knock present
the knock light goes off all the time at accel so it hard to see if it real knock or not like in the log after the high 12 and 4 i kept accelerating and had the light go off but there was no knock present
Just log the fuel and load limits like in your wot log

Load limit:
Mut00 = 6A84
Mut01 = 6A85
Fuel cap
Mut02 = 6A90
Mut03 = 6A91
Hmm it doesn't use any different variable than knocksum so i'll check on the code later. It could be hitting a point where it saw knock but it was removed later by the ecu too before it could be logged.
Just log the fuel and load limits like in your wot log
Load limit:
Mut00 = 6A84
Mut01 = 6A85
Fuel cap
Mut02 = 6A90
Mut03 = 6A91
Just log the fuel and load limits like in your wot log

Load limit:
Mut00 = 6A84
Mut01 = 6A85
Fuel cap
Mut02 = 6A90
Mut03 = 6A91
Hey bro i was checking out your 1 byte load and its not right you're logging something else which isn't the right value.
Didn't see MDP logged either its mut request 38 labled as Boost(MDP) in evoscan.
Here's something to add to your evoscan logging xml file.
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.3*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="Displays state of the throttle. High voltage or % value means a more open throttle. When logging engine activity (especially on the dyno), it is useful to log throttle position. This makes it easy to see when a power run begins and ends i.e. when the driver's foot is depressing the accelerator fully. Some mitsubishis show up to 20% when your foot is off the accelerator, and will show a max of 90-99% when your foot is fully applied, this is normal.
" Priority="1" Visible="False" />
Didn't see MDP logged either its mut request 38 labled as Boost(MDP) in evoscan.
Here's something to add to your evoscan logging xml file.
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.3*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="Displays state of the throttle. High voltage or % value means a more open throttle. When logging engine activity (especially on the dyno), it is useful to log throttle position. This makes it easy to see when a power run begins and ends i.e. when the driver's foot is depressing the accelerator fully. Some mitsubishis show up to 20% when your foot is off the accelerator, and will show a max of 90-99% when your foot is fully applied, this is normal.
" Priority="1" Visible="False" />
Last edited by RoadSpike; May 28, 2010 at 05:32 PM.
i did have it checked it was in front of speed and i think i know what happened evoscan messed up and put mdp for gear case i have gear further down and not checked and ok i got 1 byte in now lol sorry my bad not having it in there
also on my way home from work i had a code for p1400 which i look up and it said it was P1400 Manifold Differential Pressure Sensor Circuit Malfunction (Mitsubishi)
also i still leaned out when i went wot
also on my way home from work i had a code for p1400 which i look up and it said it was P1400 Manifold Differential Pressure Sensor Circuit Malfunction (Mitsubishi)
also i still leaned out when i went wot
Hey bro i was checking out your 1 byte load and its not right you're logging something else which isn't the right value.
Didn't see MDP logged either its mut request 38 labled as Boost(MDP) in evoscan.
Here's something to add to your evoscan logging xml file.
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.3*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="Displays state of the throttle. High voltage or % value means a more open throttle. When logging engine activity (especially on the dyno), it is useful to log throttle position. This makes it easy to see when a power run begins and ends i.e. when the driver's foot is depressing the accelerator fully. Some mitsubishis show up to 20% when your foot is off the accelerator, and will show a max of 90-99% when your foot is fully applied, this is normal.
" Priority="1" Visible="False" />
Didn't see MDP logged either its mut request 38 labled as Boost(MDP) in evoscan.
Here's something to add to your evoscan logging xml file.
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.3*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="Displays state of the throttle. High voltage or % value means a more open throttle. When logging engine activity (especially on the dyno), it is useful to log throttle position. This makes it easy to see when a power run begins and ends i.e. when the driver's foot is depressing the accelerator fully. Some mitsubishis show up to 20% when your foot is off the accelerator, and will show a max of 90-99% when your foot is fully applied, this is normal.
" Priority="1" Visible="False" />
i did have it checked it was in front of speed and i think i know what happened evoscan messed up and put mdp for gear case i have gear further down and not checked and ok i got 1 byte in now lol sorry my bad not having it in there
also on my way home from work i had a code for p1400 which i look up and it said it was P1400 Manifold Differential Pressure Sensor Circuit Malfunction (Mitsubishi)
also i still leaned out when i went wot
also on my way home from work i had a code for p1400 which i look up and it said it was P1400 Manifold Differential Pressure Sensor Circuit Malfunction (Mitsubishi)
also i still leaned out when i went wot

Thinking if the maf scaling is tweaked a bit it would add more fuel where it needs to be.



