NefMoto

got a problem with RS4 cause it does not follow the LDRXN curve.

There is something like a wall at rlmax_w 204 but LDRXN is about 215.

KFLDIMIX is not the issue
Knock is not the issue

I think it has to be something like a min restriction an not a factor because I can raise the values in LDRXN up to whatever I want, it stays 204...  ???

 ldrlms_w  ldrlts_w  nmot_w            plsol        plsolr_w     pvdk      rl            rl_w      rlmax_w    rlsol_w  

126,703   269,578   4599,75       2350         814,063    2340         191,25   209,211   204,11   204,11

There is an entire function for this purpose!

Look at LDRLMX

Edit: i see you're on the right track, but those values aren't exactly legible

I can tell you that there's no mystery there.

Have you logged rlmx_w?

Log as much of the function as you can.

Looks like you've narrowed it down to knock (fldrrx_w), coolant temp (frxt), and IAT (frxta_w).

maybe no mystery but I see the unwanted result  :-\

no, unfortunately no rlmx_w...  but I have absolutely no knock retard  (dwkrz_0-5 = 0) in this area and my LDRXNZK is all 100

Your problem is most likely KFLDHBN.

That was my first reaction as well, but it looks like ldrlts_w is 269.5 above.

I thought about this if I make a mistake by understanding the values of KFLDHBN

but I can not identify the connection of KFLHBN and LDRXRN in my log seems to be high enough:

 ldrlts_w      nmot_w        plsol     plsolr_w      pvdk      rl        rl_w          rlmax_w       rlsol_w  
     rpm           mbar          mbar          mbar                     


268,406   4348,25    2370         836,484    2050         180,75   181,336   202,898   202,898

257,086   5795,75    990           0             2370         127,5   128,18   204,211   55,2422 (Wped = 0 after acceleration)

 ldrlts_w falls and  rlmax_w is rising and vice versa

Just set it to FF and test.... Easy ;)

KFLDHBN cannot limit rlmax_w it is simply high enough yet.

There must be another reason for this  :-\

If you don't post how high it is, and are sure that it's high enough, then you already seem to know all the answers, don't you?

Stop futzing around and post complete logs (and/or graphs from ecuxplot) and the contents of KFLDHBN

ldrlts_w (from KFLDHBN) is 269.5 which means that KFLDHBN can't be the problem.

I have posted it above. ldrlts_w

--------

why you calling it futzing?   :'(  I'm trying to solve it step by step.

So,

KFTARX - not the issue - cause 1,01 in temp area
KFTARXZK - not the issue cause 0,5 in all areas and no dwkrz_0-5 
so no negative frxta_w influence

KFFKRXTM - not the issue - cause only active above 116 deg C tmot
FKRXTOL - not the issue - cause all values 1 - so not active
so no negative frxt influence

KFFLLDE and KFFWLLDE and KFFLDEO and KFFSLDE - not the issue cause no dwkrz_0-5
so no negative fldrrx_w or fldrxo_w influence

And these values are factors so they would not result in a static rlmax_w value 204. They would influence the curve.

Next

KFLDHBN - far above LDRXN as you can see in ldrlts_w, so not the issue

LDPBN -  not the issue cause low under 204 (ldrlms_w) and not active

LDORXN - not the issue - if this map hits in it will restrict rlmax_w to 90-114

KFLDRXO - not the issue - cause in RS4 oem all 0 so not active and additional TLDOBAN all zero

So what else ??  ???

I think I have to log other values someday  :-\

Perhaps ASR is intervening?

That won't limit rlmax just rlsol.

You're going to have to log the other variables. What ECU?

I know ASR intervening from other cars - but then I see the ASR lamp flashing on dash

And you feel massive intervention from ASR if active, but it's not

rs4 - k

black, I have no problem exceeding that...

Send me the bin on e-mail...

What is the maximum value on %load axis used to specify optimum torque in the map KFMIOP? Load in LDRXN doesn't exceed this value.

You have that backwards.

Torque has no influence on rlmax, but rlmax has axis for KFMIOP.

---

 :)