bad scaling definition for max downward WGDCC
It seems that we are missing the max downward WGDCC table in the xml defs for 96530706. Should we have it? If so what is the address?
We do have the max upward WGDCC table defined.
Thanks
We do have the max upward WGDCC table defined.
Thanks
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"/>
for 88590015:
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"/>
Was the "/" in the code intentionally left out above? ---> .....scaling="OffsetWGDC-8">
thanx
Last edited by ixbreaker; Jan 8, 2010 at 01:31 AM.
This is how the whole XML system is set up (a note to anyone that can't figure out where to put stuff). You can put a whole definition in each file, or you can do a referential system as Colby has set up (and probably the right way to do things). Anything that defines a non-rom-specific table goes in the evo xxx base file. Then a pointer for each rom ID points to this table with an address from the romID file. This cuts down on redundant code and *should* cut down on confusion.
^ Hey thanks man. You and everyone else are a great help!
I've running around with this problem chasing my tale with WGDCC for months becaues I change the original values. I did in fact get huge corrections and overboosted so much. The only way to get it to work was to make my TBEC all +/- 0.5. I thought my 3 port was super sensitive! everythings great now!
I've running around with this problem chasing my tale with WGDCC for months becaues I change the original values. I did in fact get huge corrections and overboosted so much. The only way to get it to work was to make my TBEC all +/- 0.5. I thought my 3 port was super sensitive! everythings great now!
Would this table being incorrectly defined cause issues such as massive overboosting followed by massive wastegate corrections to the point of misfiring? If so that's the problem I'm having right now, I turned things down for the winter and set my boost to 22psi when it was still a little warm out. Now I overboost to around 28psi again, and as soon as it shoots up my wastegate cuts pressure to about 16psi (according to my logs) and causes some major misfiring (feels like a fuel cut but is definitely not fuel cut).
Thread
Thread Starter
Forum
Replies
Last Post
scheides
ECU Flash
9
Dec 22, 2009 06:06 PM
