ECUFlash accel enrichment table not really accel enrichment?
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Any developments on this?
I finally had time to turn off lean spool on my personal Evo (I know, I know
), the AFR is constant in each gear now but I still get a big ol AFR enrichment right at peak load when banging through the gears. It's almost a full AFR point dip.
I tried bringing down the accel enrichment numbers but it didn't do much.
...
I finally had time to turn off lean spool on my personal Evo (I know, I know
), the AFR is constant in each gear now but I still get a big ol AFR enrichment right at peak load when banging through the gears. It's almost a full AFR point dip.I tried bringing down the accel enrichment numbers but it didn't do much.
...
If you decreased the values, then its possible that AFR could jump even further during accel.
ok that was freaky, we both posted at the same time, lol!
So when you say further, you mean jump richer? It didn't really make any difference when I decreased the number.
I'm trying to finger out what is causing this enrichment... hrm
So when you say further, you mean jump richer? It didn't really make any difference when I decreased the number.
I'm trying to finger out what is causing this enrichment... hrm
Would this be a conclusive test?
Someone near a mountain data log their car in various pulls - normal 3rd gear pull, quick run through the gears, wot run through the gears, and maybe a few others.
Then drive to the top of a nearby mountain and do the same. If the Accel Enrichment table is a barometric adjustment, the proof should be readily apparent.
Someone near a mountain data log their car in various pulls - normal 3rd gear pull, quick run through the gears, wot run through the gears, and maybe a few others.
Then drive to the top of a nearby mountain and do the same. If the Accel Enrichment table is a barometric adjustment, the proof should be readily apparent.
could mitsu be using the map sensor in the intake manifold to do an acel enrichment based on slight changes in pressure (vacuum\ positive psi) ? This may be a quicker and more direct way to offset slight load changes.
I thought every ECU had to have some kind of Accel Enrichment? Is the thinking that the EVO ECU must have it, but it just might not be the table we think it is? Or, is the thinking that the EVO has no Accel Enrichment table at all?
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
There is an acceleration enrichment routine in the EVO ROM, but this "acceleration enrichment" table has nothing to do with it. mixmastermatt explained some of what Bez had found.
Has anyone attempted to add this to their XML? Did you get it to work? Does it provide the expected Accel Enrichment functionality?
Originally Posted by Bez Bashni
But at the beginning stage U could use the patch I send before - but you need the accell enrichment to correct. I found the real acell enrichment tables and how it works in evo-I will use stock acell enrichment in my patch-so U can tune these tables right now.
add this to your xml-I spend ~1.5 hours finding the exact adresses 4 your definition..
<table name="Asynch_Acell_Enrichment" category="Fuel" address="1254" type="2D" level="1" scaling="uint16">
<table name="X" type="Static Y Axis" elements="5">
<data>pause_period</data>
<data>min_TPSdelta</data>
<data>Max_pulsewidth</data>
<data>idle_TPSRange</data>
<data>after_engine_start_addition</data>
</table>
</table>
<table name="Asynch_VS_TPSDELTA" category="Fuel" address="32b6" type="2D" level="1" scaling="uint8">
<table name="X" type="Static Y Axis" elements="9">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
</table>
</table>
<table name="Asynch_TPS(Rpm) Limit" category="Fuel" address="32c6" type="2D" level="1" scaling="WGDuty">
<table name="X" address="6c26" type="Y Axis" elements="10" scaling="RPM"/>
</table>
<table name="Asynch_Accel_vsRPM" category="Fuel" address="32e4" type="2D" level="1" scaling="uint8">
<table name="X" address="6c26" type="Y Axis" elements="10" scaling="RPM"/>
</table>
Heres mine examle of altering enrichment - left WAS -right - NOW (see .jpg)
Briefly
1 table
Pause period - TPS dynamics measurement cycle (shorter -faster) It measures TPS and copares it to OLD TPS value
min TPSDLTA - the minimum encrease of ADC value to recognise enrichment (TPS-OLDTPS) shoud be > TPSDELTA
Max Pulsewidth - total maxium enrichment pulsewidth
Idle tpsrange - the range withn wich the enrichment will work.
after engine start addition - the asynch PW constantly used within first ~5 seconds of engine started.
Asynch vs TPS - the amount of enrichment added for each point of tps difference.
Asynch_TPS(Rpm) Limit The TPS(RPM) above wich the enrichment will not be added
Asynch_Accel_vsRPM the general enrichment -Limits max total enrichment vs RPM - in newer ecu its an addition to some value)
these params exists on evo all ecus..The adressses could vary.
To log FPULSE2 (asynch injpulse) RAM:FFFF6D08 FPULSE2 i give U the ref 2 its adress 4 your ecu
But at the beginning stage U could use the patch I send before - but you need the accell enrichment to correct. I found the real acell enrichment tables and how it works in evo-I will use stock acell enrichment in my patch-so U can tune these tables right now.
add this to your xml-I spend ~1.5 hours finding the exact adresses 4 your definition..
<table name="Asynch_Acell_Enrichment" category="Fuel" address="1254" type="2D" level="1" scaling="uint16">
<table name="X" type="Static Y Axis" elements="5">
<data>pause_period</data>
<data>min_TPSdelta</data>
<data>Max_pulsewidth</data>
<data>idle_TPSRange</data>
<data>after_engine_start_addition</data>
</table>
</table>
<table name="Asynch_VS_TPSDELTA" category="Fuel" address="32b6" type="2D" level="1" scaling="uint8">
<table name="X" type="Static Y Axis" elements="9">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
</table>
</table>
<table name="Asynch_TPS(Rpm) Limit" category="Fuel" address="32c6" type="2D" level="1" scaling="WGDuty">
<table name="X" address="6c26" type="Y Axis" elements="10" scaling="RPM"/>
</table>
<table name="Asynch_Accel_vsRPM" category="Fuel" address="32e4" type="2D" level="1" scaling="uint8">
<table name="X" address="6c26" type="Y Axis" elements="10" scaling="RPM"/>
</table>
Heres mine examle of altering enrichment - left WAS -right - NOW (see .jpg)
Briefly
1 table
Pause period - TPS dynamics measurement cycle (shorter -faster) It measures TPS and copares it to OLD TPS value
min TPSDLTA - the minimum encrease of ADC value to recognise enrichment (TPS-OLDTPS) shoud be > TPSDELTA
Max Pulsewidth - total maxium enrichment pulsewidth
Idle tpsrange - the range withn wich the enrichment will work.
after engine start addition - the asynch PW constantly used within first ~5 seconds of engine started.
Asynch vs TPS - the amount of enrichment added for each point of tps difference.
Asynch_TPS(Rpm) Limit The TPS(RPM) above wich the enrichment will not be added
Asynch_Accel_vsRPM the general enrichment -Limits max total enrichment vs RPM - in newer ecu its an addition to some value)
these params exists on evo all ecus..The adressses could vary.
To log FPULSE2 (asynch injpulse) RAM:FFFF6D08 FPULSE2 i give U the ref 2 its adress 4 your ecu
Evolved Member
Joined: Apr 2008
Posts: 604
Likes: 0
From: Sydney, Australia
At least for my 80700010 ROM (Evo 7 GT-A) one of the labelled Accel Maps was actually a second boost limit map. Nothing at all to do with Accel. This ECU uses alot of different mapping for different gears and would be nothing like the Evo 8 and 9 roms that most here are using though.
Bez is a clever guy. His description is dead-on for how it works.
Bez is a clever guy. His description is dead-on for how it works.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Didn't see your post until just now. Bottom line is that this table we've been discussing has nothing to do with accel enrichment except for the secondary effect due to the reduction in barometric pressure when going WOT. I suppose that a car with a cone filter could have a tendency to run richer during accel because presumably there is less pressure drop at the MAF with a cone filter. I still have not yet worked out the overall magnitude of the barometric compensation though so we could be talking a very minor change in fueling during accel from the effect of a cone filter on baro.
I just stumbled upon this thread and I think this may have something to do with the odd sub 3000 rpm drive ability issues I see when rolling on moderate to full throttle (accelerating) @ 2200-2900 rpm only with the jdm map sensor installed. I know there are other unknown tables and/or code that needs to be changed for true proper implementation of the jdm map. for this reason I do not run it full time, only for logging boost when needed.
To be honest I am considering abandoning jdm map altogether for other means to do this.
To be honest I am considering abandoning jdm map altogether for other means to do this.
but barometric comp has it's own table or is that wrongly labeled as well?
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Any more info known about the "accel enrichment table"? Ever since adding my 850cc injectors I've gotten a fairly good black cloud from my car when I first get on the gas. I think my ECU is still adding IPW for the stock 560's which translates into way too much fuel considering my 850's.
Wow, never seen this thread, good info Fred. When I change the values in AE I see a similar AFR waveform just earlier when decreased. But this was on same gear. Would be nice some day to have one of the mitsu engineers chime in and tell us what they actually created here.
