Add the following entry to the base.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="ThrottleVoltage16"/>
</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>

Then thank MrFred.

 

whoa, how did i miss these? are these in this thread?

Thanks!

Edit: so do you have info on how to tune these? Does this mean at 4.98v (100%) mean that it will only run 74% of my BWGDC?

 

Not sure if this table addresses what you are asking. This table only sets a limit on the max WGDC "correction" and not the max "WGDC" itself. Unfortunately, there is no TPS threshold for enabling the correction. Once the BCS control routine activates, it immediately tries to reach the target boost/load no matter what the TPS and can apply pretty large upward corrections (as limited by the WGDC "correction" vs TPS table) when cruising around at part throttle if the WGDC correction vs boost table is not setup properly.

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.

 

So if i do something like this:
Will this prevent it from ramping up the correction at part throttle?

So currently when i am cruising around the Boost Error is setting -3.087 but is adding 0 WGDC Corr. It isnt until about 80% TPS does it start to add WGDC Correction. It could be due to ramp and sample rate though.

 

There is definitely a piece of the puzzle missing. There should be some table or 1D value that says at what TPS the BCS system becomes enabled (and disabled).

For the moment, the table values that you show are a good start. A properly setup BCS system shouldn't need more than 10% correction to hold the target boost under WOT conditions. I'd probably be even more conservative at lower TPS values. Could try limiting it to 10% correction until about 3.75 V, and then ramp up the final two values to something like 20%.

 

You are right, it definitely isnt working because I am hitting my correction values i have set now unless your system works around this. I dont know how to do all this disassembly but I would love to see this table, or some 3d table work with the ecu controlled boost. I think it would really help part throttle boost ramp.

 

Couldn't sleep this morning, so I dug into the ROM code for a few hours. No WGDC correction is applied until the ECU goes into open loop. The "open loop load #1" table under the fuel section in ECUFlash definies the load vs rpm where the ECU goes open loop. I don't recommend changing the table as it plays a role in other operations of the ECU. But it at least tells you what controls when the boost control becomes enabled.

I think that limiting the max correction to something like 5-7% perhaps across the entire rpm range makes the most sense at this time for controlling boost at part throttle.

 

That makes perfect sense. It would definitely be nice to utilize this table and possible combine it with the BEC table. Thanks mrfred.

 

Turns out I was wrong about the boost control keying off the open loop load #1 table. The boost control system has its own table that establishes a minimum load for the boost control system to operate:

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

The values almost exactly duplicate the "open loop load #1" table though. Could be interesting to try tinkering with these values to see how it affects part throttle driveability. Probably most useful for keeping boost to a minimum during daily driving.

 

Got the address for 96940011 mrfred?

I know the RPM is 596c but the 6688 for Min load for boost control shows odd numbers

 

Are there any plans to integrate direct BC to Tephra's V5 Alt Map mod? It has the ability to switch bdel + bwdc maps. It would be awsome if it could do direct boost instead of bdel.

 

btw, something I just discovered after messing around is that if you change the "Max WGDC Correction vs TPS" "Y Axis" = "ThrottleVoltage16" to "ThrottlePercentage" it will show TPS % instead of Volts. Made it a little easier for my brain to compute visually.

So the Y axis looks like this:

0
13
25
38
50
63
75
88
100

instead of:

0
0.625
1.25
1.875
2.5
3.125
3.75
4.375
4.980

 

578a for you.

I must have missed the throttle percentage scaling. Definitely agree that its easier in percentage.

 

tephra is somewhere in the process of writing a completely new boost control subroutine that is actually a full PID controller. Will probably make its way into v6. :-)

In the mean time, if you do my direct boost control mods on his v5, it will be able to do map switching with the direct boost control method. Its a fortunate benefit of keeping the direct boost control mods very simple.

 

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):

https://www.evolutionm.net/forums/sh...09#post5437609