Ignoring spoolup-assist, WGbase tells the ECU how much boost (above atmospheric pressure) it should expect see from just the actuator and with no solenoid mediation at all. The ECU attempts to assist in making up the difference between WGbase and the target boost while avoiding overshooting the target. So if WGbase is set up as high as the target level then ECU thinks it doesn't need to do anything at all. When WGbase is lower than the target then WGsens is used as a scale factor in calculating WG%. When WGbase and WGsens are set correctly then boost should rise to the target by the time rpm reaches WGrpm. Once boost does reach the target (+/- 15kPa) then the ECU will start tracking ... i.e. it stops calculating WG% based on WGbase and WGsens and instead begins applying corrections to the current WG% value in an attempt to keep the boost as close as possible to the target. But whenever boost is more than 15kPa higher or lower than the target then the ECU reverts to the simpler WG%=WGsens*[(target-WGbase)/WGbase] calculation. Keep in mind that WGbase is atmospheric pressure + actuator pressure so it will change as atmospheric pressure changes. The keypad displays the sum but the map entry contains only the actuator pressure. This is a rather simplistic model that assumes the actuator pressure remains fairly constant as a function of engine rpm and it relies on the tracking mode to regulate boost when that's not really true. The +/- gain control zones control how much correction the ECU applies to WG% in tracking mode when boost wanders away from the target. Your log looks better than I was expecting for that funky actuator!
----- Original Message ----- From: "Rob Ebersol" <[email protected]> To: "Ray Ayala" <[email protected]> Sent: Friday, March 06, 2009 7:36 AM Subject: Re: Link EBC questions >I have been. You're right, that's the biggest indicator of what is going >on. I've been focused on getting what I believe is a proper action/curve >from the results, but looking at my tune from the prior actuator. What >happened last night is that raising the WGbase eventually led to no WG% at >all (never reaching target. That's with WGrpm at 4600 and WGsns at various >settings up to max. WG% is at 98 right up until close loop start - as it >should be. As closed loop nears, the boost curve decreases it's rate of >rise. > > Here's a log from last night which has a usable WG% curve- similar to > what I started with on the old actuator. > http://ebersol.com/FE3/logs/DL93052215.TXT.zip > > > > On Mar 6, 2009, at 9:37 AM, Ray Ayala wrote: > >> In order to remove the actuator effects from your view of how the >> software processing results change when you alter a setting, look at WG% >> instead of boost. > _______________________________________________ Miatapower mailing list [email protected] http://list.miatapower.net/cgi-bin/mailman/listinfo/miatapower
