Questions about GM 3 Port Tuning
Questions about GM 3 Port Tuning
I am trying to find out the following about the GM 3 Port tuning:
1. What WGDC Correction Interval do you guys use? With the pill I use number 1. But the GM 3 port is much faster. Should I use a slower correction interval?
2. As a general rule of thumb, how much lower should the WGDC tables be with the GM 3 port vs. a #65 pill? Is 10% lower a good strating point?
3. What TBEC values are you using in the TBEC table?
Thanks
1. What WGDC Correction Interval do you guys use? With the pill I use number 1. But the GM 3 port is much faster. Should I use a slower correction interval?
2. As a general rule of thumb, how much lower should the WGDC tables be with the GM 3 port vs. a #65 pill? Is 10% lower a good strating point?
3. What TBEC values are you using in the TBEC table?
Thanks
Last edited by nj1266; Apr 8, 2008 at 11:50 AM.
I had oscillation problems at 1. I'm actually using 3 for mine. 3 ms is so much faster than the turbo can respond it doesn't matter.
I pulled my WGDC to 40% across the board and inched it up until I got what I wanted. Set all the positive correction factors to zero (leave the negative ones) and see if you can get close to the boost curve you want. Then add in the positive factors. Once you add the positive stuff in you may start seeing oscillation. Tweak the WGDC to get rid of as much WGDC correction as you can and any oscillation should go away.
I pulled my WGDC to 40% across the board and inched it up until I got what I wanted. Set all the positive correction factors to zero (leave the negative ones) and see if you can get close to the boost curve you want. Then add in the positive factors. Once you add the positive stuff in you may start seeing oscillation. Tweak the WGDC to get rid of as much WGDC correction as you can and any oscillation should go away.
Hey Naji, I havent figured out where this WGDC Correction table is, but im running whatever it is stock, and it changes very quickly. Much more responsive than the stock BCS.
can anyone link me up to a thread, or let me know the address of the WGDCC table?
OOOOOHHH.... duh... thats the first table in the Turbo section. "Boost Solenoid" or something...lol. duh...
https://www.evolutionm.net/forums/sh...=288408&page=3
/post
this is what i came up with. Its the stockish boost curve on teh WGDC side, adn it doesnt overshoot the BDEL. If you add back in the boost adding on the TBEC, it will bost 20psi in 3rd-5th.
can anyone link me up to a thread, or let me know the address of the WGDCC table?
OOOOOHHH.... duh... thats the first table in the Turbo section. "Boost Solenoid" or something...lol. duh...
https://www.evolutionm.net/forums/sh...=288408&page=3
/post
this is what i came up with. Its the stockish boost curve on teh WGDC side, adn it doesnt overshoot the BDEL. If you add back in the boost adding on the TBEC, it will bost 20psi in 3rd-5th.
Last edited by SoCalRedLine; Apr 8, 2008 at 11:53 AM.
I had oscillation problems at 1. I'm actually using 3 for mine. 3 ms is so much faster than the turbo can respond it doesn't matter.
I pulled my WGDC to 40% across the board and inched it up until I got what I wanted. Set all the positive correction factors to zero (leave the negative ones) and see if you can get close to the boost curve you want. Then add in the positive factors. Once you add the positive stuff in you may start seeing oscillation. Tweak the WGDC to get rid of as much WGDC correction as you can and any oscillation should go away.
I pulled my WGDC to 40% across the board and inched it up until I got what I wanted. Set all the positive correction factors to zero (leave the negative ones) and see if you can get close to the boost curve you want. Then add in the positive factors. Once you add the positive stuff in you may start seeing oscillation. Tweak the WGDC to get rid of as much WGDC correction as you can and any oscillation should go away.
Trending Topics
Then why the F do they put (ms) next to it in ECU flash?
I'm guessing its processor loops then? It only looks at boost error every x number of times it gets to that point in the code.
Either way, 1 was too fast for my car. I got a repeatable 3-4 psi oscillation. Changed it to 3 and it works beautifully.
I'm guessing its processor loops then? It only looks at boost error every x number of times it gets to that point in the code.
Either way, 1 was too fast for my car. I got a repeatable 3-4 psi oscillation. Changed it to 3 and it works beautifully.
NJ, for now i run a baseline WGDC that hits boost where i want it and then use TBEC to help prevent overshoot and have very minimal if any under correction. I dont mind having a winter and summer BWGDC though. I will eventually be fine tuning it but i have used small, 1-2% for correction where boost is +- 1-2psi off
Then why the F do they put (ms) next to it in ECU flash?
I'm guessing its processor loops then? It only looks at boost error every x number of times it gets to that point in the code.
Either way, 1 was too fast for my car. I got a repeatable 3-4 psi oscillation. Changed it to 3 and it works beautifully.
I'm guessing its processor loops then? It only looks at boost error every x number of times it gets to that point in the code.
Either way, 1 was too fast for my car. I got a repeatable 3-4 psi oscillation. Changed it to 3 and it works beautifully.
I usually set the correction interval to 4 for the GMBCS
I usually see about 10% or so less WGDC needed, depending on flow mods.
The error correction table I use usually ends up something like this:
0
0.5
1
2
1
0.5
0
0
0
0
0
-0.5
-1
-1.5
-3.5
-5.5
-7.5
I usually see about 10% or so less WGDC needed, depending on flow mods.
The error correction table I use usually ends up something like this:
0
0.5
1
2
1
0.5
0
0
0
0
0
-0.5
-1
-1.5
-3.5
-5.5
-7.5






