Without any changes to the TBEC, target load, or BWGDC tables, the most probable effect is that boost will run lower. Might run the same. Will not run higher.

 

so do you leave the WGDC correction interval #2 at 10? and only make adjustments to the #1 ?
ed

 

Thanks TouringBubble and mrfred. I will try it as is anyway. Can always set them back to stock if I don't like what it does. Weekend is looking busy so may have to try this tommorow .

 

mrfred, can you comment on my two things in my post at the top of the page.

accident, look at my settings at the top of the page. also, yes only change delay #.

Anybody that wants a good starting point for a TBEC table, look at my settings above. With those settings, adjustments were perfect, weather they were big or small adjustments.

 

But your settings are for the use of the GM 3-port solenoid, correct?

 

I just got mine set where it's usable. I used lower TBEC values (+/-3 maximum) and actually used a 4 for the delay timer. Anything below 4 was causing over correction. My boost is fairly solid in 3rd and 4th ... I didn't try second. The spike is significant in 3rd, but I get no knock so it's not an issue.

 

For the dip, can you post a log showing what the load error is doing?

Table #3 is only for when the vehicle speed exceeds the boost limiting vehicle speed. Table #2 never gets called into action by the ROM (even though the table exists). So, I'm pretty sure that Table #1 is all that matters.

 

IS that for the BDEL and MWGDC tables??

 

I added the line to my evoscan and when the "load error" box is checked evoscan doesn't want to record. any idea what could be wrong?
ed

 

I was going to bring that up as well ... I was not able to log load error last night. EvoScan .99 doesn't like the line of code Mrfred gives in the first post. Un-checking the load error box let EvoScan run fine, so the problem is definitely in that line.

Mrfred, could you double check the Evoscan data item code?

 

I posted up a revised data item in the first post. EvoScan 0.99 has some problems with certain formulas, so I used a more simple formula. I'm on business travel right now, so I can't verify though.

 

Both. I hope the next version of ECUFlash stops using the term "MWGDC". BWGDC is more appropriate.

 

Thanks for the updated code!

For informative purposes, here are my settings ...





(4th Gear)

As you can see, I've purposely set the BWGDC values lower than my desired load to compensate for temperature changes. When the weather cools off (it's been over 100* for some time now) the error correction table should have to work less to meet the desired load. This should aid in reducing overboost in cooler weather.

 

wow...what octane is that?

 

TB, I can see in your chart that the WGDC is getting pumped up during spool. This is what's causing the boost overshoot. I think you might be better off using a BWGDC curve that gets you as close as possible to your desired load without any WGDC corrections. Then zero out the -20 correction and let the WGDC correction routine fine tune.

At high rpm, it appears that the boost control system is maxed out and cannot reach your desired load. It might be better to pull the BDEL down there to match the max load that you can acheive. This will again prevent the WGDC from getting unnecessarily pumped up.

One thing that may work for better automated fine tuning of the WGDC might be to using a "rising rate" on the TBEC table. Something like:

-20 0
-10 10
-8 6
-6 3
-4 2
-3 1
-2 0.5
-1 0
0 0
1 0
2 -0.5
3 -1
4 -2
6 -3
8 -6
10 -10
20 -20

This way, the corections are very small when the error is small, but then become rapidly much larger as the error becomes larger.