Greetings,

I have been tuning my S3 1.8T for a while now (roughly 2 years), and converted it from the standard K04-023 to BT.  The specs of the build are as follows:

S3 BAM

8N0906018BJ
0261207752
363001

RC 750 cc injectors at 3 bar
Walbro pump in-tank (issues at 1/4 tank but that's not the problem here)
Larger FMIC (Dual SMICs ditched)
MBC (N75 is currently broken, will be purchasing a new one shortly, I know MBC is trash).  The motor is still stock, internal wise, so the delayed spool is kind of a good thing at the moment.
Mostly Not Working WMI (ancient pump)

I had no issues dialing in the RCs, KRKTE, TVUB, KVB, FKKS, TEMIN/VA and KFMRES/KFMRESK and a few other maps helped those to be dialed in nicely.  I have scaled KFMIRL and KFMIOP correctly, with the 99% column at roughly 225 load, and the KFMIOP axis extended to 225, and interpolated correctly (Using PRJs sheet).  The MAF is underscaled with KFKHFM, and fuelling overscaled with FKKVS in the boost area.  I know that this isn't the best way of doing it, but it has worked well to 2 bar plus on a Mk4 GTI that I helped tune).  The underscale is relatively minor in this case at 10% .  I am running 1.5 - 1.55 bar, but even when I turn it down to 0.9 bar, the ECU will cut boost around 6500 rpm regardless of actual load or boost. 

It's really frustrating.  I will attach logs of both cases and in both cases the requested boost / timing drop off sharply, when boost doesn't follow requested (MBC) it will react with throttle cut.

It really seems like a type of torque intervention, and is really frustrating as I intend on forging the motor and running Ethanol and over 2 bar (30 psi) boost.  I have tuned a Mk4 GTI Big turbo to over 2 bar and it never had this reaction.

LDRXN (215)
LDRXNZK (LDRXN - 15%)
KFMIRL (Raised - but same issue with stock)
KFMIOP (Raised - but same issue with stock)
KFDLULS raised
KFMLDMX raised
KFLDHBN raised
ARMD adjusted
LDRXN requesting 215 under boost (reasonable for BT out of boost)
CWBGMSZS set to 0
FWFTBTRA adjusted
EGT maps raised slightly (EGT is in the DP so this is not really an issue)
VVT maps adjusted to turn off earlier under high load
TLDOBAN adjusted
KFWZ/2 adjusted
KFZWOP/2 adjusted (for new axis)
NMAX (7100)
NMAXOG (7100)
KFSZT/FTOMN/KFTSRL for HC Limiter

All then normal maps (KFZW/LAMFA/LAMFAWKR/KFLDBTS etc have been tuned for a reasonable fuelling request under boost, and it's fairly good).  I've also tweaked a number of other smaller maps for fine tuning various parts but nothing that should cause this issue.

I have tried maxing out KFMIZUFIL and KFMIZUOF (6000+ but to no effect) It looks like Level 2 torque intervention in anycase.  I've spent hours reading through nefmoto threads to try get an idea of why rlsol_w is taking such a massive dive after 6250-6500, as it's so boost/actual load/knock/fuelling/MAF independent. Is it perhaps an issue with this binary or the S3 load-path vs other 1.8Ts?

Any help would be greatly appreciated.

Regards,

Jono

Do not max out req boost. I do not know how many times I've said it, and there are copious warnings about it in the S4wiki tuning page.

Looks like RPM limiter to me, and keep in mind the valves will float at ~7300 rpm on stock valvetrain, so don't go nuts on it.
What you're doing with your boost request is pretty stupid though. You should not ask for more than 2450mbar ever without 5120 file. Although if you have a MBC (which is another stupid thing to do), then it doesn't matter too much.
What worries me more is that you have scaled stuff so much that req load is around 200, while actual load with boost on target is at 175. That means if something happens with boost control you are likely to blow the engine up, because it won't limit anything until around 2 bar.
Another thing is, that the rods on this engine are made of paper and you will bend them eventually at 1.5bar boost (BTDT).

I can sell you 5120 for this platform if you want it ... but it seems there are other things to take care of first.

I do understand, as DSLOFS is still stock, so the requested value is higher than the possible sensor value, which upsets the boost PID.  Where it cuts boost, the requested has dropped below the max though.  But the point has definitely been taken and I will revert MIRL/MIOP to stock and drop LDRXN as well so that it stays on or just below 2450 mbar request.

On further reading I suspect the issue is NMAXDV, as I am logging with the cluster fuse removed to get ME7L to work, and I have not raised NMAXDV from its stock value.  Removing the cluster fuse (as most know) divorces the ECU from the cluster and by association the VSS (Vehicle Speed Signal).

Cant do much w/o an actual log

log the rest of the load vars.

Can't diagnose requested load if you don't actually log the whole path.