mrfred

iTrader: (50)

Mr Turco asked a very good question here that resulted in several tables being found that could be useful in fine tuning the part throttle response of the boost control system. This new thread summarizes the discussion in the other thread.

The final definitions for the tables are:


USDM Evo 9 88590015

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="3f10" type="2D" level="1" scaling="DynamicBoost">
<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>


USDM Evo 8 96940011

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="3B14" type="2D" level="1" scaling="DynamicBoost">
<table name="TPS" address="6002" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>

<table name="Max WGDC vs Coolant Temp" category="Turbo" address="56D2" type="2D" level="1" scaling="WGDuty">
<table name="Coolant Temp" address="5eae" type="Y Axis" elements="8" scaling="Temp"/>
</table>

<table name="Min Load for Boost Control" category="Turbo" address="578a" type="2D" level="1" scaling="Load8">
<table name="RPM" address="596C" type="Y Axis" elements="16" scaling="RPM"/>
</table>


USDM Evo 8 96420007, 96420008

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="4478" type="2D" level="1" scaling="OffsetWGDC">
<table name="TPS" address="6b3a" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>

<table name="Min Load for Boost Control" category="Turbo Boost non-JDM" type="2D" scaling="Load8" address="62de">
<table name="RPM" type="Y Axis" elements="16" scaling="RPM" address="64a4"/>
</table>


USDM Evo 8 94170014, 94170015

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="4478" type="2D" level="1" scaling="OffsetWGDC">
<table name="TPS" address="69d8" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>


USDM Evo 8 94170008

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="4478" type="2D" level="1" scaling="OffsetWGDC">
<table name="TPS" address="6784" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>


EDM Evo 9 88840016/17

<scaling name="ThrottlePercentage" units="%" toexpr="x/255*100" frexpr="x*255/100" format="%.0f" min="0" max="100" inc="1" storagetype="uint16"/>

<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="3f34" type="2D" level="1" scaling="DynamicBoost">
<table name="TPS" address="738c" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>

<table name="Max WGDC vs Coolant Temp" category="Turbo" address="645a" type="2D" level="1" scaling="WGDuty">
<table name="Coolant Temp" address="7200" type="Y Axis" elements="8" scaling="Temp"/>
</table>

<table name="Min Load for Boost Control" category="Turbo" address="6542" type="2D" level="1" scaling="Load8">
<table name="RPM" address="6ca0" type="Y Axis" elements="16" scaling="RPM"/>
</table>


The first table sets a limit on the max possible total upward WGDC correction as a function of TPS. The max total possible total downward correction is -64% WGDCC.

The next table limits the WGDC as a function of coolant temp. This is only present in Evo 9 and later Evo 8 ROMS.

The last table sets the minimum load needed before the boost control system will operate. This is also only present in ROMs for late model Evos.

I can see several uses for these tables. One thing I may try is raising the min load so that the BCS is less likely to kick in during daily driving.

Sorry, I haven't translated these to all other ROMs yet. Hoping that some of the others on the board who are good at finding tables can work this out.

bnice01

iTrader: (4)

WOW good stuff MrFred

TouringBubble

iTrader: (2)

I'm liking the idea of that minimum load table ... that could have lots of uses ...

gear head

iTrader: (3)

Yes, these tables look very usefull.

mrfred, do you have any other roms worked out?

logic

iTrader: (2)

Bryan/razorlab: have you worked out the locations of this for 96940011 yet, by any chance?

logic

iTrader: (2)

Followup: for 96940011, looking through the prior thread, I see at least this (thanks to both Bryan and mrfred):

But, not "Max Total Upward WGDC Correction vs TPS" and "Max WGDC vs Coolant Temp". But for my purposes, I'm much more interested in MLBC anyway.

Numbers look right for the above table, so I'm a happy camper. Thanks, guys!

gear head

iTrader: (3)

^I was able to scrape up that info as well, just don't have the addresses for the other tables.

recompile

iTrader: (38)

For clarification, does "Max Total Upward WGDC Correction" with it's default values of 10 mean that your Max Actual WGDC can be as high as your table value + 10?

So, let's say I have my entire WGDC table set to 50... does this mean my max actual WGDC is 60, if the error correction is trying to push it that high?

Or, does it mean that you can only correct in increments as high as 10? So each error check can only add up to 10% of correction at most?

The reason I ask is, now that I'm using a low WGDC on the #65 pill, I've found that correction is pushing my WGDC too high at times... I'd like to prevent correction from EVER going higher than my Max WGDC table

TouringBubble

iTrader: (2)

Max upward correction defines the amount of correction that the TBEC table can apply to the WGDC curve. Stock is 10, so it your defined WGDC is 50 to cannot correct to a WGDC above 60. Change max correction to 20 and you can now see 70 WGDC.

the TBEC table with keep correcting and stacking values as needed until it hits the limit.

I'm pretty sure 100% duty is the max adn this setting will not change that.

recompile

iTrader: (38)

Thanks.

So if I zero out this table, I simply can't correct past the Max WGDC table, but correction should still work

TouringBubble

iTrader: (2)

if you 0 out that table, you will not correct upward past the max WGDC table. Correct.

In theory, you could correct down and then back up to meet the defined WGDC, but never pass it.

mrfred

iTrader: (50)

Yup.

SoCalRedLine

iTrader: (2)

wow... more fancy tables to look at. Thanks mrfred

honki24

iTrader: (23)

lol, ecu-based boost just got more complicated. I might just pony up for the HKS rather than go back to OE. Good job guys.

mrfred

iTrader: (50)

This table just being discussed today makes tuning the ECU-based boost somewhat easier. No more worry about shooting way past the BWGDC value.