Last night I removed my AEM tru boost solenoid (I'm planning on replacing the stock BCS with it later). I'm having an issue where my WGDC will not exceed 78.43. Is this a configuration issue or a physical problem. I'm able to hit a 23 psi spike but the boost tapers something terrible (did this with the truboost) as well and I think I know why now. Any assistance would really be appreciated.

 

are all of your BWGDC tables tuned the same? I had a similar issue. I had set table #2 to my desired WGDC and left #1 and #3 set lower for safety. The problem was that I was running off of map #1 so my actual WGDC was capped at WGDC #1 (55%) + maximum + correction in TBEC table (+10%). Do you have another WGDC table set 58% duty?

 

All 3 are set the same. And no matter what I havent logged WGDC above 78.43 and it's always that number. I actually had different settings in BDEL but maxed out the Boost Desired engine load to try to get it to budge above 78.43 but it wont move above that. My boost cut is set at 275 but my loads are not getting that high. One thing I've noticed is that it seems to hit the target during the spike but then it just stays at 78.43

 

Have you even been able to log WGDC at 100%? Could you post your WGDC logging code?

 

No 78.43 is the max it's ever logged

Here's the code I have. I copied it from a thread on here. It would make sense that it was already 100%

<DataListItem DataLog="Y" Display="WGDC" LogReference="WGDC" RequestID="86" Eval="x*100/255" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="100" ChartMin="0" ChartMax="100" ScalingFactor="1" Notes="" />

Except for that terrible taper that I have of course. The boost looks just like it did with my Truboost but it controlled the spike a little better and I was able to get more boost if desired.

 

Ah. The formula is incorrect. Instead of x*100/255, use x/2. I think you might have gottend x*100/255 from one of my posts. Do you know which one?

 

Thanks mrfred! I'll give that a try.

I'm not sure which post I got it from. One of the threads dealing with logging WGDC and there were only a few.

Update: This was the problem. It's fixed. Thanks again mrfred!