Any word on the the boost error issue?

Boost error registers the same the entire time? Is this an ECU Flash V7 setting, or a EVOScan setting issue? I am running the 0715 APPauldd spec. Other than this, all good so far for me. I will be testing the GearFIX Patch tommorow.

Thanks again for all you do T.

 

well see if the gear fix fixes the boost error...

if not let me know and we will examine that problem

 

Yes! Gear logs fine, and gear-based-boost-control works just fine (as it did at 96530706 V7), and I can tell 94170715 drives much smoother!

Thank you, Tephra!

But unfortunately, boost error and WGDC correction logging problem is still there. (Boost error logs -0.001 for first 5 minutes then stuck at -3.7825 (minimum value of Omni 4bar setting), and WGDC correction is 0 for all the time (even when the boost is more than the target value and the WGDC is lowered))

Although our max WGDC vs Coolant temp table looks weird, WGDC remained 0 until coolant temp reaches 55 celcius degree, then it goes to 100%.

But it seems WGDC remains 100% even when it is below the BCS activation rpm which is set to 2250rpm. (100% WGDC below this load is set to 170 kPa, I guess this function overrides BCS activation rpm table.)

I am glad that gear based boost control now works!

 

Tephra, I am assuming this is an activate/deactivate switch? Like choosing load based or psi based, and only effects the gear based boost?

No dice for me on the Boost Error either...
I couldnt check the Boost per gear, for I over shot my boost during spool, due to the boost error showing that I was down on boost, so the WGDC tries to increase, causing misfire... I backed off.
So in summary, WGDC and Boost Error Correction tables are working, but boost error is getting the wrong info.

ace33joe, whats your target boost? I have mine set at 21.5 and am spooling to 23+, and then WGDC tries to hold it due to the boost error.

 

Ok, after careful look at the log, I guess Raceghost, you are right, I think boost error correction does not work here. Deviation from WGDC table is probably from MAF IAT correction.

I guess I was too excited to see the gear logs fine, and WGDC follows the gear-based tables.

 

Tephra,

I had an observation today as I was looking to see if I had forgot to copy something, or change a setting.

In stock ROM 0015, MUT 4-0 is 0x8091,
In your patched V.5 rom, MUT 4-0 is 0x8417
In the new V7 Rom, my MUT 4-0 look like yours, as well as 4-1,2,3.
Each of these roms have changed values in the 4-0 through 4-3 locations.
I am assuming that you have used thes MUT locations as variables depending on the version of ROM/MAP utilizing.

Is there any chance that one of these locations is the correct memory spot for the boost error sub routine. I am just throwing it out there....

Just seemed weird that I can't find these locations anywhere in this forum with a listing on why they would be changed. So that would illiminate me changing those address in your V5.

EDIT: I found them referencing the the 1 byte load. But not all those locations are mentioned.

Thanks again for you help.

Oh also another side note: Has anyone else scaled there Timing and Fuel maps for more resolution than the default scaling in the BIG maps? Supprisingly, my car loves the resolution difference of 10. 0 - 320 in increments of 10.

EDIT: Its working to a point. The Boost Error keeps constant at a -3 boost.. So your WGDCC tables trys to add WGDC to get that -3 to a 0. In this case, because the boost error never changes, the WGDCC just keeps adding and addding. This becomes a problem quick for you can overspool. Lucky, my tables are set to blow that WG wide open at 23 so it won't hold much over that. I will say though, I do have a flat boost curve. Spikes 24, holds 23-22 redline. This of course was before I realized the issue last night.

 

what is your boost error requestid?

 

<DataListItem DataLog="N" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.029551*x-3.78251" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

<DataListItem DataLog="N" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

Boost Error : 8A
WGDC Correction : 8B

 

I see your MUT8A points to 0xFFFF8027...

Is that correct for your ROM - ie is that what MrFred said to use?

 

Yes, and MUT8B is 0x8cd9

 

to save me some time, can you find me the thread/post he refers too?

 

I'm confused... thread/post?

 

well the stock V7 rom just comes with regular boost control...

mrfred's mod will add either load or direct psi based boost.

i am pretty sure you need todo that mod to get loaderror?

 

mrfred's direct boost control how-to:

https://www.evolutionm.net/forums/ec...t-control.html

mrfred's boost control mod how-to: (load based)

https://www.evolutionm.net/forums/ec...trol-mods.html

Is this what you meant, tephra?

 

yup

ok so the MUT's are correct as per MrFreds instructions

what about
as per https://www.evolutionm.net/forums/4719861-post2.html