Page 3 of 3

Re: Not hitting load targets

Posted: September 6th, 2019, 5:27 pm
by mituc
The MAF cal I've sent him should fix that, among other things. But we will see...

Re: Not hitting load targets

Posted: September 6th, 2019, 8:41 pm
by Enki
The .9v 2.0 g/s thing is a genwon issue and I normally cut the calibration off like that myself. Has there been any discussion of this from anyone on the code side, Mituc? Is it being looked into or are we just SOL?

Re: Not hitting load targets

Posted: September 7th, 2019, 10:51 pm
by mituc
Enki wrote:Has there been any discussion of this from anyone on the code side, Mituc? Is it being looked into or are we just SOL?
I've sent Ugnius a private message pointing to this thread. He seems to have read it. Not sure if he is looking into it, if he's on vacation or has other priorities...

Re: Not hitting load targets

Posted: September 13th, 2019, 6:40 pm
by Enki
:(

Re: Not hitting load targets

Posted: September 14th, 2019, 4:00 am
by Dolfius
@Enki & @JohnnyT are you guys running big turbos or k04s?

What year model is your car @JohnnyT?

Re: Not hitting load targets

Posted: September 15th, 2019, 7:05 am
by JohnnyT
I'm getting mine figured out. Still working on mafcal but I think it was just me not setting the table correctly. I'll let you know when I get past the mafcal. Mines an 07 speed3 and I'm running a Precision Turbo 5862 journal bearing. Just a little bigger then the ko4 lol.

Re: Not hitting load targets

Posted: September 16th, 2019, 10:44 am
by Enki
09 MS3 with an EFR 7163.
I know there are ECU revisions between genwons, specifically for my year, as even ATR has a different version for it compared to 07-08:

Re: Not hitting load targets

Posted: October 26th, 2019, 5:01 pm
by Enki
Still not even an acknowledgement of this topic?

Re: Not hitting load targets

Posted: July 3rd, 2020, 10:59 pm
by EmPeEs6
Just want to confirm that I also have this weird APP issue on my Gen1 MS3: actual load is almost exactly stuck to the desired values in the APP = 93.75 row of the APP req. load table under WOT conditions (instead of using the values for APP=100, although an APP value of 100 is logged during wot runs), which means that the acutal APP value has its max at about 95% and not 100% (and no, I didn't map actual APP 100 to a reported one of 95 ;-) ).
It was a very frustrating way until I finally find this out since there were a lot of potential reasons for not reaching the "realistic" target load (high temps, wgdc corrections too low or high, other limiter tables etc.).