WGDC being pulled despite being well below boost/load targets

[MD1032]

Take a look and see if you have any ideas why. It's probably something obvious that I'm missing, but I can't figure it out. It's ever since it got cold that it started doing this. I keep increasing my load targets, but it just doesn't seem to give a shit. Maybe there's some load table I'm missing that it's running up against?

I attached my tune and a 4th gear log of it happening. I'm way below load/boost targets and logged WGDC is still only like 75%.

Gonna tag some people here:
@g00s3y; @sheston; @phate;

[phate]

Couple things:

You're at 80% IDC. Discussion here. Solution here. I don't think this is likely, as you are way below targets earlier in the rev range than where you're at 80% IDC.

Sometimes when using both sides of LEC and BEC together, they fight each other and end up doing nothing. You could try zeroing out one half of one table, or even one table altogether.

Are you sure that your car is using the 100% APP line from the tables as "full throttle"? I described this sort of thing and testing methods over here.

[MD1032]

Thank you! I will try the "Load Target Comp" fix first and see if that fixes it.

You're right, I'm not sure that it is referencing those last two rows in my table. I have less rows set to my "WOT" conditions now than I did then, but even then, I never had more than the bottom 4 rows (81% and up) set to my WOT conditions. I have many logs showing 100% WGDC from the summertime.

I did think about the LEC/BEC interference. I have been adjusting LEC non stop lately as the temperature changes and I think it is time to zero BEC and take it out of the equation. I'm basically only load tuning at this point anyway. The only time I check the boost targets table lately is to make sure it's above what I'm logging.

edit: Changing the Load Target Comp tables per the link above fixed the problem. I'll take a log on the way home. The difference is pretty obvious. I did enjoy the faster flashing speed with the new firmware btw.

[g00s3y]

I actually just started switching to a load tune about 2 weeks ago. I was having this exact problem past 5k, had no idea what it was. For me, it was this table;

Load Target Comp - Injector Base Offset (BETA)

I had it at 0%, which wasn't allowing IDC's to go past ~90. So it would just hold IDC's ~90, past 5k, and would start dropping wgdc. Switched it back to 20 (value i've found to be safe from reading other input on here, and what I had in my k04 tune, not sure why I switched it for the BNR), and all is good now.

[MD1032]

Agh! On my way home, it wasn't targeting 100% WGDC anymore like it was in the morning (I did a 4th gear pull in the morning (didn't log) and it was pegged at 100% from 5500 on.

Still, changing those values definitely did something. Obvious from how much more air I'm flowing, and how much higher IDC's are. And the car feels peppier in the top end.

BEC is getting zeroed and I'm also gonna push the boost limits up higher. I'm just gonna narrow LEC for now but leave it active. I will leave boost targeting checked for now as well.

I see what you mean Clint about it pulling WGDC throughout. Normally I would see the exact opposite. I am starting to wonder if the IAT comp table is interfering here. I would think my LEC/BEC tables combined would be enough to compensate for that table's subtractions though.

Those boost spikes are so annoying. Why the hell does the ECU take so long to realize that it's added too much WGDC?? At least this is one problem the BNR will probably solve.

[MD1032]

OK, now it's really solved for good.

I zeroed the BEC, LEC, IAT Comp tables one by one today and none of that did anything. Finally I copied the last row of my WGDC table down to the 3rd to last row (APP=87.50%) and saw an immediate change (from ~86 to ~92-94%). I then copied the last row down to the 4th to last row (APP=81.25%), and problem solved. Thanks @phate;!

You know the interesting thing is that as I was doing my pulls on the highway, I had the laptop open with tracing active in ATR, and I could see very clearly that it was referencing only the last two rows of the WGDC table (why I didn't originally suspect this as a problem). Apparently this is not truly the case. Clearly some kind of limitation of the tracing feature there.

I am still glad I made this thread because I found out about that IDC limitation in the process. For sure I am going to be pushing the IDC's very high when I get the BNR S3 tuned. Perhaps the methanol injection system I am planning to install sometime soon will be more important than I originally thought.