how-to: ECU-based direct boost control
#331
He shoots he SCORES! Exactly what i thought, thanks again mrfred, you are teh man.
#332
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
This table can be used in a couple ways. The most obvious way is to tweak the WGDCC values in the table. Another useful way is to very specifically tweak the TPS where upward correction is allowed to begin. This would be done by rescaling the TPS values. So instead of:
The values could be, for instance,:
And remember that, for instance, the ECU will linearly interpolate the Max Correction value from 0 to 10 as the TPS goes from 75 to 93 (in this example), so the max correction would feather up more slowly than for the stock value.
Code:
TPS% Max Corr 0 0 13 0 25 0 38 0 50 0 63 0 75 0 88 10 100 10
Code:
TPS% Max Corr 0 0 13 0 25 0 38 0 50 0 63 0 75 0 93 10 100 10
#333
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
New summary for USDM Evo 9 88590015:
So in summary, here are three additional tables that could be useful in tuning the boost control system (for the USDM Evo 9 88590015.xml):
<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="3f10" type="2D" level="1" scaling="OffsetWGDC">
<table name="TPS" address="7284" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
<table name="Max WGDC vs Coolant Temp" category="Turbo" address="65d0" type="2D" level="1" scaling="WGDuty">
<table name="Coolant Temp" address="70f8" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="Min Load for Boost Control" category="Turbo" address="6688" type="2D" level="1" scaling="Load8">
<table name="RPM" address="6b98" type="Y Axis" elements="16" scaling="RPM"/>
</table>
Note that the "OffsetWGDC" scaling in the "Max Total WGDC Correction vs TPS" definition is one of my custom ones that is included in the "direct boost control" instructions. People not running my direct boost control setup can use "DynamicBoost" scaling instead.
There is actually another unpublished 1D table that defines the minimum temperature for the boost control system to operate. (The published one it ECUFlash is wrong.) Its a bit redundant since its purpose overlaps with the "Max WGDC vs Coolant Temp" table, but I'm sure the Evo engineers had a reason for the redundancy. :-)
So in summary, here are three additional tables that could be useful in tuning the boost control system (for the USDM Evo 9 88590015.xml):
<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="3f10" type="2D" level="1" scaling="OffsetWGDC">
<table name="TPS" address="7284" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
<table name="Max WGDC vs Coolant Temp" category="Turbo" address="65d0" type="2D" level="1" scaling="WGDuty">
<table name="Coolant Temp" address="70f8" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="Min Load for Boost Control" category="Turbo" address="6688" type="2D" level="1" scaling="Load8">
<table name="RPM" address="6b98" type="Y Axis" elements="16" scaling="RPM"/>
</table>
Note that the "OffsetWGDC" scaling in the "Max Total WGDC Correction vs TPS" definition is one of my custom ones that is included in the "direct boost control" instructions. People not running my direct boost control setup can use "DynamicBoost" scaling instead.
There is actually another unpublished 1D table that defines the minimum temperature for the boost control system to operate. (The published one it ECUFlash is wrong.) Its a bit redundant since its purpose overlaps with the "Max WGDC vs Coolant Temp" table, but I'm sure the Evo engineers had a reason for the redundancy. :-)
#338
There is actually another unpublished 1D table that defines the minimum temperature for the boost control system to operate. (The published one it ECUFlash is wrong.) Its a bit redundant since its purpose overlaps with the "Max WGDC vs Coolant Temp" table, but I'm sure the Evo engineers had a reason for the redundancy. :-)
Code:
<table name="Min Temp for Full Boost Control" address="1e26"/>
Last edited by fostytou; Mar 25, 2008 at 11:33 AM.
#345
alright mrfred should be my last question LOL.
for tephra v5 all you have to do for the alternate boost if using direct boost control, is to change the scaling from load8 to psia8?
I also changed the name to "Alternate Baseline Boost".
for tephra v5 all you have to do for the alternate boost if using direct boost control, is to change the scaling from load8 to psia8?
I also changed the name to "Alternate Baseline Boost".