Well, I already saw that from the code a while back, but experience tells me that things are not always what they seem and checking is better. More so that there were contradictory claims about this earlier...

i have forged Fiat bravo with big turbo if you are interested for testing LC/NLS code 


Great Job for that ecus ....

B_kr and B_dmdstop off the top of my head.

Stage 1 I assume you mean totally stock hardware. In that case (what I intend to try once I get to it):

MDMAXNMOT (also MDMAXNMOB if you have overboost activated), raise it, can be actually arbitrarily, because KFLDBHN should be the map keeping your turbo safe. If your resulting torque goes over KLMIMAX(_UM) then increase these two, but I don't think the stock KFLDBHN would allow it. Once you figure out what torque line you get it would be nice to tap MDMAXNMOT down to it (for elegance). And do something with with KFPED(X) if the pedal response is not what you expect. I don't think there is anything else to it, but I am yet to see myself. (Well, OK, on 150/155 hp ECUs you may run out of injectors too, but then it's AFR measuring time, not mapping, no map will help you get more out of them).

Great job !!!

OK, so first of all many thanks to Teo for testing this out (as it turned out, the first test code had a benign bug ).

This is a basic procedure, LC rpm hard cut and time limited NLS cut, as in the patch to be found in the Wiki for ME7.1 (or was it ME7.5). Only I fixed it around a bit, and this one disables dmd and kr, oh, and it also has configurable hysteresis margins for the RPM thresholds. I attach the factory bin of what Teo tested, a S19 patch, xdf definition with LC/NLS parameters, patched bin for the lazy ones, and my ASM source (don't bother trying to find the tool that compiles it, only I have it, the code is only for reviewing, please tell me if you see bugs) if you want to match to another bin.

Two next extensions on the list, RPM shift light through MIL (this I already sorted out), and dynamic setting up of LC/NLS RPM thresholds through the cruise control stalk. Here I need feedback, I got a bit stuck conceptually:

My initial plan was: cc into on mode (also makes LC/NLS disabled), and then when holding cc+ register the rpm (highest seen) for LC, and when holding cc- register rpm for NLS. But for this to make sense there has to be a way to reset it and I run out of cc buttons. There is the resume button, but, here is the thing, there are two types of ME7.9.10 (as far as I can tell), one that has cc stalk connected directly to the ECU (and then all buttons / states are always readable), the other one gets this from the cluster through CAN and the cluster already filters out some things, in particular the ECU does not receive resume presses when stationary (or +/- presses without cc being on).

So I need another logic for this. Possibly: cc on for setup / LC/NLS disable, then (no other buttons) register RPMs for LC (as long as they are above some sensible limit, like 2500 rpm), with cc+ register RPMs for NLS, cc- reset both. What do you think? To me it seems overly complicated, but I cannot come up with something simpler. There is also the option to read the sport / power steering state, but this would make it even a bigger clusterfuck. Help me out here to come up with something sensible.

Everything is optional, including the cruise control setup and sport mode (but, you probably do have sport mode, through the city power steering mode, that's how it works on my Grande).

But, I am almost certain that for you it's a no-go for another reason, the clone MPPS (that's what I remember you have, right?) can only flash data region on this ECU (at least the version I have seen), and you have to be able to flash the complete file. Also, if you still have the cat-converter in the car, that would probably get killed by this feature.

Well post your bin then (can be factory, no need to share tunes) and we will see what can be done. I am now working on a more proper version of this, with retard, gear dependant RPM levels for NLS, and turbo DC, it will take me a while though.

I'd be also interested to know what you did, tune wise, to disable the CAT (I can guess, but checking with somebody that have done it and tested is better).