Hello after a long time.

I'm now a 1p cupra happy owner. I read its flash with MPPS some days ago and was preparing my definition (1P0907115C) from a well defined 1K0907115S from this forum. I'm totally open to share it once it's more or less ok.

Good. I come from me7 and I know pretty well the algorythm from the title. However, in MED9 it's more different than I would've expected... I guess it follows the same principle though:



At first sight, as LDORXN is lower than LDRXN (from rlmx_w), both go to the minimum selector and LDORXN (Absurdly low in my opinion, something like load 30) becomes plxs_w (by pressure transformation).

Obviously, this is not what happens without E_lde (overboost error).

So I assume the explanation is in the [IF] block working mode. For sure it has something to do with the arrow numeration, but I don't understand it's behaviour. I even tried to look at the begining of FR but nah... not clear enough.

Could someone explain to me how/why this works and wtf is LDORXN so stupid low?

Thanks a lot for your time mates

Ps: My presumption is that the latest option from the active [IF] becomes directly the last variable affected by any present [IF], no matter what's up/downwards. But even so, I couldn't find E_tnl so I don't know what it means. What's more, what should happen in the event of no E_xxx, aka, no errors? The [ELSE] from the only [IF] that has one? (then, ignoring LDPNB)

Not quite sure but this is my guess:

lets ignore E_tnl for the moment:

call the minimum of rlmx_w (corrected), ldrlts_w, ldrlms_w, and LDORXN some variable "foo"

Now, the purpose of that flip flop is to inhibit updating plxs_w from foo while B_ll

As long as B_ll is false or E_lde is true, plxs_w is updated by "foo" on the 50ms raster

As soon as B_ll goes true and E_lde goes false, the flip flop resets to false, NOT IF is triggered and plxs_w stops being updated by "foo", until E_lde becomes true again, and plxs_w starts getting updated by "foo" again.

Do the same for E_tnl, roughly, to add it back in with respect to the raster update.

I could be wrong, of course.

I think we understand more or less the same from the diagram...

This would've been a lot clearer if bosch used triggerable selectors (in my humble opinion) as they usually do in many other algorythms

And regarding LDORXN, from what I remember from me7, it is much higher there... Isn't it? But well, that's secondary

Thank you both guys

The description is in fact the same, but values are much lower:

So they just limited it harder.
What's so special? Nothing