TB, the load error goes positive in several locations which tells me that the ECU thinks the target load is lower than the target load you have programmed. Something is wrong somewhere in your ROM settings. I saw something in one of your earlier posts about the "min temp for full boost" setting. That is an incorrect table definition. Its really a WGDC setting. Did you change that value?

 

Fair enough. Just wanted to be sure

 

Thats exactly what I'm seeing too ...

I did change Min Temp for Full Boost Control. It's at 78 I believe. But I'm pretty sure it hadn't changed since the issue started. Let me double check that ... thanks for the input.

 

0x6EED is the target load used by the ECU. Put 0x6EED into one of your MUT table entries, and you can log the target load that the ECU is trying to acheive.

 

What EvoScan formula do I need to use for that 0x6EEd value? Just "x?"

Okay, I did a few logs this morning and at least I'm pretty happy with the TBEC now ... I think the spike will be better controlled when the ECU gets to aiming at the correct target again. I changed the Min Temp for Full Boost Control values from 74 (apparently I did change it recently) to 80, which is a value I've used successfully before. I believe 82 is the stock value. Below are the results ... not much changed from last night ...





It looks like the target boost from 3750 to 4500 is close to the correct target and then it gets further off as revs increase.

 

Oops. Small mistake. 0x6EED is only the BDEL used by the ECU. Scaling is x*5/8. The ECU does not store the target load (BDEL + BCLO) in a RAM variable.

The stock value for the min temperature for full boost is 85. Since the table definition is completely wrong, it would be better to use the stock value until we get a better handle on what this setting is.

 

Will do ... any thought on why the incorrect load target seems to be getting closer to desired load over time? Could this be related to the battery disconnect?

 

Definitely wouldn't be related to the battery disconnect. Let's see what BDEL you log after setting the "min temp for full boost" back to stock, and then we'll go from there.

 

Alright ... but I've been running <85 for like 6 months and haven't had an issue ...

 

New log ... MTfFBC set to "85"



Same issue.

 

Try logging 0x6EED. That should provide some useful info.

 

If you move your target load to what it is currently hitting, i wonder if what it actually hits will move down as well.

 

Based on the way it is acting it would move down.

There is the chance that some sort of cap is being placed on either the BDEL or the BCLO ... if that were the case then it might not fall below the actual target if the target were lowered. This doesn't seem to be the case though.

 

Nope that was a stupid idea, edited out.
MB

 

TB, your first post in this thread shows the variable for boost control as being FFFF6B42. Is that still the case?