Help! WGDC not correcting on target boost???
#1
Newbie
Thread Starter
Join Date: Sep 2012
Location: Montreal, Quebec
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Help! WGDC not correcting on target boost???
Hi,
When I datalog, I can see that my boost is not correcting to reach the target.
I see the boost error but when I look at the WGDC Correction, it's always 0.
I'm using direct boost control with omnimap 4bar and grimmspeed boost controler.
Running 25psi tapering to 21psi at red line.
When I look in the global boost control setting map, I have found this that I'm not sure if it's well set(never touch it before):
- WGDC Correction table: the scaling is not set to OffsetWGDC but Percent255??
- Max total upward wgdc correction vs tps table: the value of wgdc correction are set to 0 everywhere??
Here's my boost error correction table and exemple of log.
My interval of correction is set to 1 for low and high gear.
Why do you think wastegate is not correcting guys?
When I datalog, I can see that my boost is not correcting to reach the target.
I see the boost error but when I look at the WGDC Correction, it's always 0.
I'm using direct boost control with omnimap 4bar and grimmspeed boost controler.
Running 25psi tapering to 21psi at red line.
When I look in the global boost control setting map, I have found this that I'm not sure if it's well set(never touch it before):
- WGDC Correction table: the scaling is not set to OffsetWGDC but Percent255??
- Max total upward wgdc correction vs tps table: the value of wgdc correction are set to 0 everywhere??
Here's my boost error correction table and exemple of log.
My interval of correction is set to 1 for low and high gear.
Why do you think wastegate is not correcting guys?
#6
Newbie
Thread Starter
Join Date: Sep 2012
Location: Montreal, Quebec
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
could someone check and compare this map edit of the boost error (mainly the offset wgdc line) if the parameter write are the same and his map
it's for an evo IX TephraMOD-88590715-v7 map.
Else, I will try to play with the value in all the table there's the wgdc correction in it to see if I have a value that is limiting me for the correction..
it's for an evo IX TephraMOD-88590715-v7 map.
Else, I will try to play with the value in all the table there's the wgdc correction in it to see if I have a value that is limiting me for the correction..
Trending Topics
#8
Newbie
Thread Starter
Join Date: Sep 2012
Location: Montreal, Quebec
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
#9
Newbie
Thread Starter
Join Date: Sep 2012
Location: Montreal, Quebec
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Problem found!!
It was the Max Total Upward WGDC Correction vs TPS Table that was the problem.
It was all set to 0 everywhere. I start changing it and everything is right.
With the correction done, I was overshooting the boost target each time with a spike before it correct on target. With testing, I have finish to make it work good with putting the WGDC correction interval to 3 instead of 1 and the table like this
From what I understand, I only want the boost to get corrected at full load because before full load, it can offset the wgdc curve and when it get to full boost, I overshoot a spike before another correction come to be on target...
What your total upward... table look likes guy when it's stock?? I don't why mine was all set to 0...
It was the Max Total Upward WGDC Correction vs TPS Table that was the problem.
It was all set to 0 everywhere. I start changing it and everything is right.
With the correction done, I was overshooting the boost target each time with a spike before it correct on target. With testing, I have finish to make it work good with putting the WGDC correction interval to 3 instead of 1 and the table like this
From what I understand, I only want the boost to get corrected at full load because before full load, it can offset the wgdc curve and when it get to full boost, I overshoot a spike before another correction come to be on target...
What your total upward... table look likes guy when it's stock?? I don't why mine was all set to 0...
#10
Evolved Member
iTrader: (5)
In the Tephra file mine was set to all zero except the 85 & 100, those were set to 10. I currently run all 0's in mine. Reason for that is the tendency to overshoot your boost targets, which is what it is doing for you now with the spike.
Last edited by ReaperX; Aug 2, 2013 at 08:19 PM.
#11
Newbie
Thread Starter
Join Date: Sep 2012
Location: Montreal, Quebec
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
With the wgdc correction set up around 3-4, now it's pretty good...(not perfect)
Because with out the correction, I often got my boost curve 25psi dropping for a 100rpm around 22psi getting up to 24 after or sometimes it's alright...
Because with out the correction, I often got my boost curve 25psi dropping for a 100rpm around 22psi getting up to 24 after or sometimes it's alright...
#12
Former Sponsor
iTrader: (12)
Some tuners zero it out because this will happen. Your turbo will be spooling and say -2psi before your target boost, the ECU will see boost error at -2psi and add WGDC, causing over boost. So people zero it or greatly reduce it so that it wont add WGDC and make boost spikes.
When you zero it, the correction only corrects downward, making sure you never over boost.
The following users liked this post:
sandman121383 (Aug 26, 2018)
Thread
Thread Starter
Forum
Replies
Last Post
Cbr1000love
General Engine Management / Tuning Forum
4
Apr 15, 2016 08:03 AM
barevolved
ECU Flash
10
Oct 12, 2012 09:19 PM