bad scaling definition for max downward WGDCC
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
bad scaling definition for max downward WGDCC
Hey Folks,
Just found out that the scaling definition that I used for the Max Downward WGDCC table is incorrect. Using the stock value is modified using the incorrect scaling large positive WGDCC values may result. Find the "OffsetWGDC" scaling in your evo9base.xml or evo7base.xml file and replace it with:
Just found out that the scaling definition that I used for the Max Downward WGDCC table is incorrect. Using the stock value is modified using the incorrect scaling large positive WGDCC values may result. Find the "OffsetWGDC" scaling in your evo9base.xml or evo7base.xml file and replace it with:
Code:
<scaling name="OffsetWGDC" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint16" endian="big"/>
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Code:
<scaling name="OffsetWGDC-8" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="OffsetWGDC-16" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint16" endian="big"/>
Trending Topics
We will need to keep the original Offset WGDC scaling too. If we change it...the Boost Error Correction table and MAF IAT WGDC table get messed up.
Oh what a can of worms this became.
Oh what a can of worms this became.
Code:
<scaling name="OffsetWGDC-8" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="OffsetWGDC-16" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint16" endian="big"/>
<table name="Max Total Upward WGDC Correction vs TPS" category="Turbo Boost Single Solenoid" type="2D" scaling="OffsetWGDC-8">
<table name="TPS" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
<table name="Max Total Downward WGDC Correction" category="Turbo Boost Single Solenoid" type="1D" level="3" scaling="OffsetWGDC-16"/>
<table name="Max Total Upward WGDC Correction vs TPS" address="3f10">
<table name="TPS" address="7284"/>
</table>
<table name="Max Total Downward WGDC Correction" address="1658"/>
Last edited by fostytou; Jan 4, 2010 at 11:55 AM.
9653:
PHP Code:
<scaling name="OffsetWGDC-8" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="OffsetWGDC-16" units="%WGDC Change" toexpr="(x-128)/2" frexpr="x*2+128" format="%.1f" min="-64" max="63.5" inc="0.1" storagetype="uint16" endian="big"/>
<table name="Max Total Upward WGDC Correction vs TPS" address="448a" category="Turbo Boost Single Solenoid" type="2D" scaling="OffsetWGDC-8">
<table name="TPS" address="6c2a" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
<table name="Max Total Downward WGDC Correction" address="1a58" category="Turbo Boost Single Solenoid" type="1D" level="3" scaling="OffsetWGDC-16"/>
Last edited by logic; Jan 5, 2010 at 06:58 AM.
