Can someone explain to me the boost target engine load table?

I thought that the combined value of a cell + the offset = targeted load.

I have it set to accommodate the load ranges which are experienced with 28psi, but it seems like it falls intermittently, then comes back up again (Almost like it's correcting it for a second). Example - progresses to 25psi, then backs down to 22, then on its way to 28 again.

How can this be if the load ranges are not conflicting with the boost target engine load table and boost limit tables at any time?

This is on a 3 port and the reactive boost table in the WOT range are steady values and not causing the issue.


Please help.. I'm starting to wonder if this is a mechanical problem of some sort now..

 

Bump

 

You are correct in that the cell + offset value = target load. Target load is just that though, a target. Logging would show what's happening but my guess is that your WGDC ramp up is too aggressive, meaning it over shoots it's target early on, and then over corrects on the WGDC correction table and drops the WGDC value too much, dropping you below your targeted load. The maps then compensate the other way and eventually you hit target. The 3 port is very sensitive to change so I would only drop a couple of points at a time anywhere you try to correct the WGDC map and log again.
You can also adjust the correction table to reduce WGDC less aggressively for small over shoots as well (although keep the largest drops for massive boost over shoots as this will protect your engine)

 

Well I run 100 value usually on my reactive until 3000 rpm, which then goes to 70, and then from 3500 and on it stays around 58.

I don't think the reactive table is causing the problem because it's making the corrections when they are all the same value (58).

I've attached a log, let me know what you think. It's showing that it's making a lot of correction, but I'm not sure why because it's hitting target load and the reactive table is almost all the same value.

EDIT: NVM.. It won't let me attach a .CSV

 

When tuning my 3 port (and for other changes) I turned positive error correction (under boost target) to 0 and negative error correction to 0 for overboost under +4.7 load. I then used a 2,250rpm launch in 3rd and a 2,500rpm launch in 4th to tune up my high & low WGDC maps to get as close as possible to my target values. I logged, adjusted the WGDC in a certain RPM range (2000rpm - 3500rpm had the most time spent on them) up or down a few points, flashed then logged again and compared.

Once there I added values back into error correction both for over and underboost. Targets then went out as a single change early on in the ramp up changed the curve on the rest of the map so a bit of patience and a fair number of logs and flashes brought my map to the point where it was launching from my test rpms consistently. At this point adjusting your load targets in the lower rpms can assist, alongside WGDC changes, something that took me a dozen flashes and some hair tearing to figure out

Final stage was (I have an SST and use RaxPatch - thanks Rich) to then adjust my map to have consistent positive correction (+6WGDC on both high and low) to make use of the upshift boost management (drops the WGDC correction when it senses a drop in rpm, meaning boost drops slightly when shifting = less stress on gearbox)

My point of all this is that it is worth spending time logging and slowly adjusting your maps to reduce error correction. If error correction consistently kicks in then your reactive WGDC maps are not set to properly hit the targets you are after. I would log load, rpm, WGDC, WGDC_correction and at the first point that the correction kicks in alter the values in that area up or down a couple of points, using the view function to get the graph to ensure it's a consistent slope. The reactive WGDC is what is determining the boost level, the load is what you want and the error correction tries to fine tune the result to meet the load target.

For what it's worth I reckon if you drop values from 2,500rpm down from 100 to 90 maybe and slope down from there you'll see an improvement