I have not done a full RPM pull, I will go get a log.

I was just working on getting my new injectors dialed in and wanted to get a decent AFR before doing a high RPM pull.

 

Sounds good, looks like you are taking a good approach to tuning.

 

[sigh] razorlab that was not very confidence inspiring. I don't like having one of "those" cars. mrfred, yes it was "interesting" that I didn't get fuel cut. I might just have to try to induce it via short delay and low boost limit values. I don't like not having that as a decent safety against disconnected hoses and accidental tuning errors.

What is annoying about keeping the upper TBEC zeroed out is I lose the WGDC increase during 1st and 2nd gear. grrr I might as well put my MBC back on or take the time (less than I've spent so far) to install my ProfecB. [sigh] I'd be tuning for timing and AFR by now.

well anyway I'll keep trying. I set the upper half to +1 in each cell to see what would happen on my drive to and from the train ... damn if the morning, cool, seemed much better but this afternoon, warm, I hit 1.6 again without any sign of drop off. I wasn't logging so I don't know what WGDC was doing. Likely won't get to do that until the weekend again but we'll see.

oh yeah and I'm gonna see if I can force a negative correction by setting BDEL way low. I want to prove that my ecu will even do it cause so far even the little negative correction I've seen has stayed above BDEL and I want to see it drop BELOW my BWGDC settings.

 

has anyone considered, and experimented with, the idea that the Boost Cut Delay Timer might relate as much to downward boost correction as it does to fuel cut?

 

My base tune from Vishnu had the delay time set to something like 130899490 ms, and at one point I was able to get nice up/down corrections in the WGDC. I still had the problem though of too much upward correction during spool-up. It would be nice to have a hard ceiling on the WGDC values.

 

Here is a 3rd gear pull (up a hill)

Here is my WGDC

 

sure .. go rain on my parade. I see how you are man. yeah a hard limit, or just a damn more responsive TBEC I wonder if any of the more accomplished ecu hackers are looking into that part of the code. all we really need is to find where the ECU determines if/when to make adjustments and, assuming there is a time factor, reduce it. even better if the up delay could be longer than the down delay. it would be a sweet hack and would make the ecu much more closed-loop like for boost control.

oh yeah and and and ... if they could figure out a way to tie it into the lean-spool code and use that "spool" condition as a way to increase the downward reaction time to catch the spike ... yeah yeah I know.

Hey mrfred didn't you say disabling lean spool really helped your spiking? what about hurting your spool though? I mean it IS there for a reason ...

just thinking outloud again ... if the spool upward correction is a problem, what about zero-ing out all upward values except say the -2 and -5 so that there is just enough upward correction to handle gear differences and actually prevent upward corrections when load is way below BDEL such as during spool?

I wonder, are the upward corrections additive? that is to say if you are in the -10 cell does it just add 6.5? or does it add 16.5?? that would make a difference in what I would set the -2 and -5 values.

and are we sure the "difference" is a % deviation or is straight difference? would just give me more detail on what to change those values on the left side to.

ok the wife wants Chik-Fil-A shakes and I can't deny her

 

here is my most recent settings. I'm hitting about 1.5 bar and taper down to 1.3 to redline. I zeroed out my upper TBEC table and lowered the bottom to -5.
I still need to raise my upper rpm MWGDC settings but I think I'm getting closer to my BDEL. So if I'm hitting my upper BDEL+BCLO target if I raise my upper TBEC table back up will I still stay within my target but hopefully pick up spool?
another question, I added the WGDC setting in my evoscan v0.99 it reads it on the screen but when I go to check the log after the run I can't get it to show?
ed

 

here is a screen from my 1st- 4th pull

 

Are you sure your BDEL + Offset aren't too high per each RPM?

What gear are you hitting 1.6?

 

Does anyone know what the impedance of the GM BCS is? Mitsu OEM BCS?

 

Yeah, I was also thinking about the possibility of changing the ROM code to get better control over boost. However, I thought it be good to first figure out why some people aren't having boost overshoot and others are.

You should try disabling lean spool to see for yourself what its like. With it disabled, it doesn't quite have that "urgent" spool-up feeling, but it still spools plenty fast. And actually, I like the engine response better with it disabled. It has a more predictable response. Daily driving is easier as well as anticipating the boost response when going WOT at lower rpms.

To answer your other question, the boost correction is additive. After making one correction, if the load still is below the target value, then it can more correction. So if you have a max upward correction of "1", then the ECU will keep adding 1+1+1+1... until the load reaches its target value.

You could try just limiting the max upward correction to "2". This will keep the WGDC from increasing too much with spool up but still allow some long term upward drift perhaps to compensate for lower gears. Hard to say though because the lower gears are gone in an instant.

But definitely try disabling lean spool too.

 

If it reads on screen, then its somewhere in the log.

 

You can see what I have them set at in my earlier post, they don't seem too high. I'm hitting 1.6 mostly in 4th. I can soetimes see it in 3rd if I go WOT at 4000-4500 but it quickly settles. and if I start at <3000 you get the 1st curve in that post which was with positive TBEC zeroed out.

Mr. Evo IX: my GM tested out to 26ohm and my stock tested at 32.5ohm

 

ok well that wil be the next thing I try, and then I think I'm gonna try some testing of TBEC to see what I get with only filling in the first two positive corrective values.