Boost Tune - Only running base WGDC

[MattJackson86]

So I took my old K04 tune and started to tweak it for BT. Tune has not been touched in forever and at somepoint I must have made some changes so that the ECU will not deviate from my base WGDC, despite my ramp high being 10%. My "Boost Error Comp" has values in it too, but no matter what the WGDC just hits and stays right at the base value.

Any idea what tables I modified who knows how long ago to make the tune only use the base WGDC? This is a 100% boost based tune btw.

[someguy]

Have you checked the checkbox in the options for boost tuning? (I forget what it was called).

[2.0t03speed]

post the map

[MattJackson86]

Originally Posted by 2.0t03speed post the map

I will when I get home, I knew I should have initially. Got inpatient thinking about tuning while at work

Scratch that, see attached. Walked to car and offloaded it from the AP.

[ms6mil]

OP can you post a recent log? I just started looking through your map, the box is checked

[ms6mil]

There are a few things I would be concerned with in this map.

Tgt Throttle %


Your WGDC tables are not something I normally see on a GTX30 targeting only 21psi


Is there a reason why you have your Throt. Req. Load (High BAT) at 4.0




What are you referring to with your

base WGDC?

Have you tried loading an OTS map and building from there?


EDIT: I'm assuming you've already checked for any obvious signs of mechanical/hardware issues...

[MattJackson86]

Thank you for the great feedback! Couple logs attached from yesterday when wgdc was set to 75% (see attached map for the ones that match the logs). The earlier map is only slightly changed to see differences. As for the 4.0, I dont recall why This was based off a tune I made myself years ago and ran for years on my K04. It drove really great, I literally just took it and started to base a BT map for my GTX3071 off of it and see how it went. I believe the 4.0 and 5.0 loads were to prevent load cap issues. I understand that how you do things these days may have changed from when I did my initial tune on an earlier accesstuner version and before so much great info came out.

The 80% WGDC in the map I uploaded today is boosting way too high, hence why I need the 75% + error comp to work. My hotside was ported and and I have been working with Stratified on a pro tune and the consensus is that the hotside was over ported. I am just trying to see some data and play with it myself as I feel I have enough experience to tune a simple map myself, at least enough to confirm the hotside is a POS. I went pro tune cos they will know more of the obscure things to tune and make it better.

Maybe I will just start fresh from an ots map and see. Any suggestions on a good start map? Overall hardware is fine, minus the potential over port job. I was hoping to just take a known good map and see what happened on my gtx. While not optimal I would hope it would give me good data on my port issue.

Base wgdc I mean the main target wgdc table that I have set and you have screenshotted.

[ms6mil]

Originally Posted by MattJackson86 Thank you for the great feedback! Couple logs attached from yesterday when wgdc was set to 75% (see attached map for the ones that match the logs). The earlier map is only slightly changed to see differences. As for the 4.0, I dont recall why This was based off a tune I made myself years ago and ran for years on my K04. It drove really great, I literally just took it and started to base a BT map for my GTX3071 off of it and see how it went. I believe the 4.0 and 5.0 loads were to prevent load cap issues. I understand that how you do things these days may have changed from when I did my initial tune on an earlier accesstuner version and before so much great info came out. The 80% WGDC in the map I uploaded today is boosting way too high, hence why I need the 75% + error comp to work. My hotside was ported and and I have been working with Stratified on a pro tune and the consensus is that the hotside was over ported. I am just trying to see some data and play with it myself as I feel I have enough experience to tune a simple map myself, at least enough to confirm the hotside is a POS. I went pro tune cos they will know more of the obscure things to tune and make it better. Maybe I will just start fresh from an ots map and see. Any suggestions on a good start map? Overall hardware is fine, minus the potential over port job. I was hoping to just take a known good map and see what happened on my gtx. While not optimal I would hope it would give me good data on my port issue. Base wgdc I mean the main target wgdc table that I have set and you have screenshotted.

I would start with the OTS stage 2 boost/timing tables. Lower the WGDC tables to about 20% all the way across. You are overboosting because your WGDC are set pretty high. Set them lower and allow your error comp's and ramp's to bring them up to target. Allow the ECU to use BEC to add WGDC rather than pulling it.

Set your throttle tables back down to 80%, this will allow the throttle to modulate as needed. I believe that your 98% thrott. tgts and acc. ped. pos. have changed where it intersects with your boost targets. (maybe someone can explain that better)


Set all your Load tables, specifically your (High BAT) tables back to OTS.

Dynamics Tables: start with OTS and adjust the BEC and ramp as needed, if you are seeing Boost oscillation. Sometimes it may be too aggressive and you will see what your boost curve currently looks like.

I would pick any OTS stage 2 map from COBB since you will be scaling the maf to account for your SURE 3.25 MAF housing.

Download any of the curent available maps from COBB for your vehicle

and plug your MAF scalar....

3.25" (SURE) BETA

0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	2.10	2.39	2.72	3.07	3.44	3.86	4.31	4.84	5.39	5.94	6.70	7.46	8.23	8.93	10.06	10.83	11.67	12.63	13.68	14.76	15.98	17.32	18.67	20.14	22.11	23.38	24.63	25.89	27.15	29.02	31.02	33.08	35.27	37.56	39.95	42.46	45.07	47.75	50.55	53.45	56.46	59.58	62.84	66.19	69.69	72.17	74.63	77.11	80.85	84.64	88.54	92.52	96.60	100.80	105.11	109.57	119.93	124.94	130.09	135.36	140.79	146.31	151.94	157.62	163.45	169.42	175.54	181.79	188.22	194.83	201.60	208.64	215.93	223.41	231.08	238.94	246.97	255.21	263.63	272.25	281.06	290.01	299.14	308.48	318.03	327.75	337.69	347.86	358.23	368.83	379.66	390.71	401.99	413.49	425.22	437.18	449.41	461.85	474.55	487.49	500.67	514.11	527.82	541.77	555.99

I'm currently on my goverment computer so I can't look at the screen shots or your map right now so if I'm off, I'm sure someone will correct me.

[MattJackson86]

I'll take a look at the it's map and see what's different. I'm not over boosting at 75% and I do want the comp tables to pull the wgdc up to needed, but that's what's not working in my map. Just not sure what tables I neutered to stop error comp kicking in.

[Lex]

The issue here is this:

- The overported hotside requires a lot of WGDC to reach a decent amount of boost even on a 3port.
- Once you bring up the boost at 80% WGDC on a 3 port you are overworking the actuator to try and keep this large wastegate closed. So boost control becomes very touchy where it will easily spike at these WGDC levels.
- Because of this and especially during gear shifts you will end up with a spike that will trigger the WGDC to drop a few percentages. When the WGDC drops, the WG opens and boost takes a BIG dip of several PSI.

So you end up with a poor boost response, poor boost ramp, and overall something that is not only hard to tune, but very sensitive to weather and doesn't give you the crisp response and resiliency that you;d expect from the setup.

It is a good learning experience to try this for yourself Matt, and you will see that you will end up having to have very little dynamics in the wastegate to maintain boost and that will result in unpredictable boost response based on what RPM you go WOT at and even things like temperature changes.

[MattJackson86]

Originally Posted by Lex It is a good learning experience to try this for yourself Matt, and you will see that you will end up having to have very little dynamics in the wastegate to maintain boost and that will result in unpredictable boost response based on what RPM you go WOT at and even things like temperature changes.

Lex, and thats exactly my goal here. Just to see for myself and get a better understanding of the issue and whats going on. Not looking to tune (I have you for that!) but playing with it and better understanding the issue. Hence just looking to get my old map up and running again.