Yeah, that is how I understand it is supposed to work. The "Max" WGDC is more like a "Base" WGDC according to this idea. There is also something of a delay before the ECU applies the adjustment. If I recall correctly, it was mrfred who suggested that it was about 0.4 sec of delay. He had some nice graphs showing all of this in another thread.

 

I think that its more of an integration time than a "delay".

It is definitely a "baseline" WGDC. If it were a max WGDC no one would be having problems with the overshoot. :-)

 

I have a question:

I log WGDC and I get 49 @ 3500 rpm, but the MWGDC is 54.5 @ 3500 rpm. Why is there a difference between the two?

Load is 248.7 and target load is 259.4. TBEC is stock. The boost logged is around 22 psi. Should I attempt to make the WGDC and MWGDC the SAME? How do I do that?

 

I'd have to see the entire log to see what's going on.

 

I know as of now most people are changing the wastegate duty cycle tables to adjust the boost, I am not sure if this has been discussed, but has anyone just tried to set wastegate duty cycle to 100 all the way thru the rpm band up til redline and then just adjust the load offset and the boost desired engine load the way it is done from factory? If so how did that work out, I am thinking of tuning mines like that to test it because i cannot get the gm solenoid to keep boost stable day to day. With the factory solenoid and the pills at least boost would stay stable but with the gm i can change settings and get 21psi, then the next day i wont go no further than 18psi although nothing has changed and the weather outside is about the same as the day before (hot and muggy)

 

Attached the log and the boost tables. I want to know why is the MWGDC different from the one that is logged? How do I make them the same if possible?

https://www.evolutionm.net/forums/at...1&d=1184468238

 

The reason why the factory uses 100% in the WGDC has to do with the size of the pill. Before I traded in my Evo 8, I flashed the ECU back to stock but kepts the #65 pill that I was running in the boost line. I did a couple of logs and saw a peak Load of 290 with Evoscan LoadCalc. I also saw a bunch of knock along with it since the timing was stock.

 

The link to your log didn't work. The simple way to make the WGDC match the baseline WGDC (its not a max WGDC) is to zero out the correction table. I'm guessing that you are looking for a better answer than that though. If you can fix the link to your log, then I can check it out.

 

I fixed the link. I am talking about MWGDC. It is the table in the ROM that say MWGDC. I want to know why the MWGDC numbers in the ROM are different than the one logged in the log. And I want to know if we can make them the same.

 

TBEC adjustment is accumulative. It will keep adjusting up and up (or down). That means you have to look at the WGDC & load 500 rpm's back (If you're logging in 3rd gear, you are aren't you?) You should also take an average of your load across 500 rpm's from 3500-4000 rpm. I believe the TBEC is actually a percentage, as it doesn't correspond directly with load.

In this example, you need to look at your load at 3500rpm and WGDC. Too high or too low at 3500 rpm will also affect 4000 rpm. Also, remember that load does not equal boost. As your rpm's climb higher, load will drop as boost remains constant.

 

Again, TBEC adjustments are cumulative. You need to log the WGDC and see at what point the TBEC kicked in. You need to tune your boost from left to right. Values at MWGDC act as both a curve and a starting point. Once TBEC kicks in, it'll keep that offset for the remainder of the MWGDC setting, until TBEC adjusts it again. Say at 3500rpm, TBEC kicks in and adds 5 to your MWGDC. If the rest of your BDEL + BCLO are in line, it'll offset the rest of your MWGDC by +5.

 

That depends on where and when TBEC adjusted your WGDC setting. Ideally you don't want TBEC to adjust WGDC during the part where you're actually boosting anything significant. It'll probably adjust WGDC when you haven't built up boost yet, or are still spooling.

 

Are the rest of your MWGDC & BDEL maps the same as this one?

 

I've been trying this with a completely stock BCS setup to try to get rid of a 270+ load spike I am getting. From my observations the problem with this approach seems to be the .4+ it takes for the ECU to see a spike and then allowing TBEC to step in and correct it by lowering the WGDC. If your getting very quick sharp spikes it seems the better way to deal with this is to directly lower WGDC.

 

The table in ECUFlash that says MWGDC is not actually max WGDC. The table is mis-labeled (as are a few others). Its really a baseline WGDC that the ECU can move up or down depending on whether the actual load is above/below the target load. How much it gets moved up/down depends on the values you insert into the TBEC correction table.

I plotted your data. The recorded load is matching quite well to the target load. The reason that the WGDC is running below your BWGDC values is because that's what's needed for the load to be at the target load. You can change the values in your BWGDC table to the WGDC values recorded in your run.

I think part of the problem that you're having is that Logworks has this funky thing where it plots the same value many times over. I suspect that this block data is hiding the true shape of the load curve in the lower rpm range.