Notices
ECU Flash

WGDC Log vs. Actual BCS Settings = Something Weird

Thread Tools
 
Search this Thread
 
Old Dec 10, 2009 | 05:56 PM
  #1  
Ted B's Avatar
Thread Starter
EvoM Guru
20 Year Member
Photogenic
Photoriffic
Liked
iTrader: (6)
 
Joined: Aug 2004
Posts: 6,334
Likes: 63
From: Birmingham, AL
WGDC Log vs. Actual BCS Settings = Something Weird

I was out today working on a base 93 octane map. Presently, I am using a GM 3-port in manual mode (have not yet implemented load or psi based control yet). What I am finding is that regardless of where I set WGD in the table, the log shows WGDC decreasing as rpm rises, and yes, boost tapers along with it (Omni MAP). I'm not sure why that would be the case. Now, I am assuming logged WGDC is determined from the ECU signal to the BCS. I would think that regardless of what is happening with the boost, the logged WGDC should be exactly what I specify in the table, but obviously, this is not the case (should be 75, not 58 at high rpm). What am I misunderstanding here?

Setup is in signature.

2nd gear WOT log and ECU Flash settings follow:



Reply
Old Dec 10, 2009 | 06:32 PM
  #2  
Ceddy's Avatar
Evolving Member
 
Joined: Apr 2008
Posts: 265
Likes: 1
From: Reading, PA
Unless am missing something, your WasteGate Duty Cycle is decreasing because you are surpassing your Desired Load.

Is LoadI?.. in your log, Load1Byte. Can't see full name.
Reply
Old Dec 10, 2009 | 06:40 PM
  #3  
Ted B's Avatar
Thread Starter
EvoM Guru
20 Year Member
Photogenic
Photoriffic
Liked
iTrader: (6)
 
Joined: Aug 2004
Posts: 6,334
Likes: 63
From: Birmingham, AL
"LoadM" on the log = 2-byte load (LoadMut2byte)

"159.4" is the max possible value in the "Boost Desired Engine..." table, and isn't a factor. But yes, I'd say that 418 load slightly exceeds that...
Reply
Old Dec 10, 2009 | 07:18 PM
  #4  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Since the rightside of your TBEC table is non-zero, you're not in manual mode. Your log shows that boost error is very high, so the ECU is pulling back WGDC. I'm actually surprised that it didn't pull back much more WGDC than what it did. You must still have the WGDC correction interval set to the stock value of 10. Zero the right side of the TBEC table, and the WGDC will exactly follow the baseline WGDC table.
Reply
Old Dec 10, 2009 | 07:24 PM
  #5  
Ted B's Avatar
Thread Starter
EvoM Guru
20 Year Member
Photogenic
Photoriffic
Liked
iTrader: (6)
 
Joined: Aug 2004
Posts: 6,334
Likes: 63
From: Birmingham, AL
Ok, that makes sense, thanks! Actually, I suspected that might have had something to do with it, and even made a map where the right side of the TBEC table is zeroed, but I wanted to consult you guys before I attempted it. I'll do that and drop the WGD values waaaay down.

As for the WGDC correction interval, where is that setting found, and what do you recommend? I ask because I am going to psi based control soon, so I am assuming that will be a factor.
Reply
Old Dec 10, 2009 | 07:39 PM
  #6  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by Ted B
Ok, that makes sense, thanks! Actually, I suspected that might have had something to do with it, and even made a map where the right side of the TBEC table is zeroed, but I wanted to consult you guys before I attempted it. I'll do that and drop the WGD values waaaay down.

As for the WGDC correction interval, where is that setting found, and what do you recommend? I ask because I am going to psi based control soon, so I am assuming that will be a factor.
Always good to start with low WGDC values. :-) The release version of the ECUFlash xmls only has a few ROMs with the correction interval listed. I think if you look in my psi-based boost control thread or my "boost control mods" thread, you'll find a definition for the correction interval (along with perhaps a few other goodies depending on your ROM).

I set my interval to 1. I forget exactly what that equates to in time, but my recollection is about 0.08 seconds.
Reply
Old Dec 11, 2009 | 12:38 AM
  #7  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by Ted B
"LoadM" on the log = 2-byte load (LoadMut2byte)

"159.4" is the max possible value in the "Boost Desired Engine..." table, and isn't a factor. But yes, I'd say that 418 load slightly exceeds that...
Just so you know, the Boost Desired Engine Load + Boost Load Offset = target load

So currently yours is 159.4 + 100 so 259.4 target load.

Since you are actually hitting 400+ load I would recommend setting your Boost Load Offset to 300 and your BDEL table to whatever equals the load.

So an example (going off that log you posted) would be Load Offset at 300 and BDEL @ 110 @ 6000 rpm which would be 410 target load.

I would also recommend setting your additive correction vs TPS at zero.

Make sense?

- Bryan
Reply
Old Dec 11, 2009 | 06:15 AM
  #8  
Ted B's Avatar
Thread Starter
EvoM Guru
20 Year Member
Photogenic
Photoriffic
Liked
iTrader: (6)
 
Joined: Aug 2004
Posts: 6,334
Likes: 63
From: Birmingham, AL
Yep, now I remember. That mechanism (BDEL+BLO=TL) completely slipped my mind. So many things to remember.

Anyway, I made the changes and dropped MAX WGD way down, and will start over.

Thanks!
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Ted B
Evo Engine / Turbo / Drivetrain
9
Aug 4, 2016 08:46 PM
Ted B
Evo Dyno Tuning / Results
120
Jul 26, 2014 07:08 AM
Ted B
Evo Engine / Turbo / Drivetrain
218
Feb 8, 2011 05:25 PM
Ted B
Evo How Tos / Installations
3
Jan 12, 2011 12:44 AM
Ted B
Evo How Tos / Installations
1
Feb 17, 2010 08:52 PM




All times are GMT -7. The time now is 07:53 AM.