Max WGDC Correction vs TPS table
#1
Max WGDC Correction vs TPS table
mrfred found a table and labeled it: "Max WGDC Correction vs TPS":
Add the following entry to the Evo9base.xml file:
<scaling name="ThrottleVoltage16" units="V" toexpr="x*5/256" frexpr="x*256/5" format="%.2f" min="0" max="5" inc="0.05" storagetype="uint16" endian="little"/>
then this in 88590015.xml
<table name="Max WGDC Correction vs TPS" category="Turbo" address="3f10" type="2D" level="1" scaling="WGDuty">
<table name="TPS" address="7284" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
His idea of the function of this table was that if the BWGDC was set at a certain % that the ECU could change,via correction, the BWGDC up to whatever precentage was in this table, at the TPS value. An example he gave was: "The 74% is actually 74% WGDC and not 74% of the BWGDC value. So if the BWGDC is set at say 15% across the entire RPM range and you are at WOT, then the ECU could change the WGDC up to as much as 15% + 74% = 89% WGDC"
Anyway, I figured I would mess around with the table quickly today on a Evo 9. After what I saw, I think this table does something other than what we think!
I bought the values down in the Max WGDC Correction vs TPS table and the BWGDC and thus boost also came down. Load was on target before I change the Max WGDC Correction vs TPS values, so no correction was taking place. It brought the boost down by approx 7psi in some parts of the curve!
I'm beginning to think it's a global boost curve setting of some type now.
Here is a log:
The lower value plots are using the table on the right. The higher value plots are using the table on the left. As you can see, lowering the % in this table also brought the BWGDC down over the whole curve, more than 40%! Of course, since the BWGDC was down, so was boost and load.
For some reason I forgot to log Error Correction and Load correction for these runs. I'll do some logging on my personal car with these on so we can get more data.
Add the following entry to the Evo9base.xml file:
<scaling name="ThrottleVoltage16" units="V" toexpr="x*5/256" frexpr="x*256/5" format="%.2f" min="0" max="5" inc="0.05" storagetype="uint16" endian="little"/>
then this in 88590015.xml
<table name="Max WGDC Correction vs TPS" category="Turbo" address="3f10" type="2D" level="1" scaling="WGDuty">
<table name="TPS" address="7284" type="Y Axis" elements="9" scaling="ThrottlePercentage"/>
</table>
His idea of the function of this table was that if the BWGDC was set at a certain % that the ECU could change,via correction, the BWGDC up to whatever precentage was in this table, at the TPS value. An example he gave was: "The 74% is actually 74% WGDC and not 74% of the BWGDC value. So if the BWGDC is set at say 15% across the entire RPM range and you are at WOT, then the ECU could change the WGDC up to as much as 15% + 74% = 89% WGDC"
Anyway, I figured I would mess around with the table quickly today on a Evo 9. After what I saw, I think this table does something other than what we think!
I bought the values down in the Max WGDC Correction vs TPS table and the BWGDC and thus boost also came down. Load was on target before I change the Max WGDC Correction vs TPS values, so no correction was taking place. It brought the boost down by approx 7psi in some parts of the curve!
I'm beginning to think it's a global boost curve setting of some type now.
Here is a log:
The lower value plots are using the table on the right. The higher value plots are using the table on the left. As you can see, lowering the % in this table also brought the BWGDC down over the whole curve, more than 40%! Of course, since the BWGDC was down, so was boost and load.
For some reason I forgot to log Error Correction and Load correction for these runs. I'll do some logging on my personal car with these on so we can get more data.
#2
Evolved Member
iTrader: (6)
Join Date: Jul 2005
Location: Charleston, SC
Posts: 1,228
Likes: 0
Received 0 Likes
on
0 Posts
Man, all these boost control tables. I am almost done with my new tune for the FIC1050's, and was going to run my vacuum lines to the 3-port this weekend, and start playing around with it. Yeesh. (I know this is for a IX, not a VIII)
With so much going on in just simply controlling a wastegate bleed solenoid, is there some sort of patch that someone could generate for a simple RPM based target psi value based off the map sensor, instead of all the other tables?
With so much going on in just simply controlling a wastegate bleed solenoid, is there some sort of patch that someone could generate for a simple RPM based target psi value based off the map sensor, instead of all the other tables?
#4
EvoM Staff Alumni
iTrader: (16)
So it looks like we need to look into this table a bit more. I would like to see your correction before and after though. I may try to get logs myself. I would really like to see this stuff working as it could really help part throttle boost. Edit: also log TPS.
good stuff bryan.
good stuff bryan.
Last edited by MR Turco; Mar 20, 2008 at 06:31 AM.
#7
Evolved Member
iTrader: (7)
So it looks like we need to look into this table a bit more. I would like to see your correction before and after though. I may try to get logs myself. I would really like to see this stuff working as it could really help part throttle boost. Edit: also log TPS.
good stuff bryan.
good stuff bryan.
I agree, I think what we need is something that reduces WGDC at partial throttle. That'll improve driveability. I wonder if boost error correction stays activated still though.
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post