Did anybody change the reference for the "Boost Limit" map when doing this mods? Yesterday I hit 305 2-byte load (limit set at 290) for more than 1 sec. and fuel cut didn´t occur. I´m thinking maybe the Boost Limit load reference is somewhat different and should be changed to the 2byte load reference.

 

My recollection is that the boost limiting load algorithm chooses between two different loads. I'd have to take another look and perhaps streamline it to use only 2-byte load ref.

 

If possible, that´d be great.

I found out what was causing my overboost situation: I recently installed the 3-port selenoid, and ran new silicone vacuum hoses to the turbo and wastegate. The one attached to the compressor nipple melted. Thankfully I had tuned and rescaled my maps to 320 load with conservative timing, so actually the pulls which got to very high loads (i might just have a record here... 345 on the stock 9.8 turbo) were almost without detonation. Weird thing is, fuel cut didn´t ever come in, and i didn´t even get a check engine light. Thankfully I had evoscan programmed alarms, otherwise things could have gotten a lot worse.

 

yeah boost limit could be upto 30 different from 2byte load...

i think boost limit uses baro+temp corrected load, which is upto 30 lower than 2byte..

 

Just to confirm:

is it possible to copy and paste the text into another map?

i am running JDM map and wanna start tuning boost with a 3 port BCS. this method seems pretty good and easy for me to do once i can copy and paste into my rom file and the evo 9base file.

BTW with the 3 port BCS i dont need a pill right?

 

You do NOT need a pill w/ the GM BCS! And yes you can copy/paste to your rom files/9base... BUT, you need to make sure that you make all changes from the location the program is in your comp. Also, Make a copy, so if you make a mistake, you can use the original! and if you have a shortcut on the desktop, once you have that done, also make copies for the files in your shortcut.

 

For anyone who is an idiot like me and always has trouble trying to add to the baseline boost tables in your head, I made a new scaling to use for just these 2 tables (alt table too).

Just replace the 7.4 in both calcs with whatever amount your boost adder is set to over nuetral pressure for your elevation. Since I'm at 14.3psi (a lowly ~630 ft above sea level) I used 21.7 for boost adder which should generally give me resolution up to 32psi.

Now I won't look like an idiot anymore when I forget to add things.

The only silly side effect is that your mininum boost will now be off... so instead of 0 you will have whatever your difference is (for me, 7.4). I noticed this number is not common only to the scaling I created, but also for WBAFR. Does anyone know how to get around this even though the min values are 0 for each? It seems that WBAFR can also go way above the max value set for it (32 also). Is this just a coincidence of the max range of the number related to the max value here?

 

Since 96420007 and 96420008 are deprecated in favor of 96420011, here are the values for 96420011:

<table name="Variable for Boost Control" category="Turbo" address="1f972" type="1D" level="1" scaling="Hex16"/>

<table name="SHLR->SHLL for EBC" category="Turbo" address="1f6ea" type="1D" level="1" scaling="Hex16"/>

<table name="Boost Error RAM Addr" category="Turbo" address="1f966" type="1D" level="1" scaling="Hex16"/>

<table name="Boost Error RAM Addr in Boost Error Table" category="Turbo" address="6b1a" type="1D" level="1" scaling="Hex16"/>

<table name="WGDC Correction interval #1" category="Turbo" address="1a54" type="1D" level="1" scaling="uint16"/>

<table name="Boost Error Correction" category="Turbo" address="4488" type="2D" level="1" scaling="OffsetWGDC">
<table name="Boost Error" elements="17" type="Y Axis" address="6b1e" elements="17" scaling="BoostErrorPsi"/>
</table>

<table name="Boost Adder" category="Turbo" address="1a70" type="1D" level="1" scaling="psia16"/>

<table name="Baseline Boost #1" category="Turbo" address="44f8" type="2D" level="1" scaling="psia8">
<table name="RPM" address="6af4" elements="16" type="Y Axis" scaling="RPM"/>
</table>

<table name="Baseline Boost #2" category="Turbo" address="450e" type="2D" level="1" scaling="psia8">
<table name="RPM" address="6af4" elements="16" type="Y Axis" scaling="RPM"/>
</table>

<table name="Baseline Boost #3 (BCLS)" category="Turbo" address="4524" type="2D" level="1" scaling="psia8">
<table name="RPM" address="6af4" elements="16" type="Y Axis" scaling="RPM"/>
</table>

<table name="Baseline Boost #4" category="Turbo" address="453a" type="2D" level="1" scaling="psia8">
<table name="RPM" address="6af4" elements="16" type="Y Axis" scaling="RPM"/>
</table>

Follow the rest of the instructions for 96420007/8.

 

I'll see if I can get an admin to raise the size limit on my first few posts in this thread as well so I can add these tables.

 

is there anyway to get psi based fuel cut? i would like to be able to re-enable this feature because now its disabled because im over 319 load most of the time in boost

 

OK, Dur moment. Functionally 7.4psi is the minimum boost I can request with this equation and number relation. This is essentially saying the bit is 0 and cannot go any lower, then evaluating it. I was just thinking backwards when I thought I was requesting 0 or 3lbs of boost, but not adding my base adder at the time.

Also, MrFred pointed out that the min/max are not related to values entered, but rather they set the range of input values to span the the full range of the color map.

 

Is there a way to do direct boost alt map switching on the Tephra 5.10 96530006 ROM? I already have direct boost running.

 

Yeah, just use alt maps WGDC and BDEL.

 

Isn't BDEL used for load-based boost control? I am set up for psi-based boost control on a 3-port. I use Baseline Boost, Boost error correction and max WGDC tables to control the boost profile.

 

Its all about scaling.

BDEL is for load based, if you have PSI based then BDEL becomes a Target Boost table.. the only thing that changes is the scaling on the table...

So for altmaps you can just change the scaling on the altmaps to match the scaling on your normal maps.. (and maybe rename the altmaps so u dont get confuseled)