LOL

to activate the lanch mode I wanted to raise the rpm value nmax 4000rpm, and then put vmax in stationary mode at 40km, and the right way?

You first need to match the code to your software version, the bins / patches I provided earlier won't work (and they will screw up your ECU almost for certain). Otherwise the default parameter values should be more or less sane and usable for first tests.

I got a message that a version with retard also works, but there is some fine tuning and additional tests for NLS needed. Result so far:

https://youtu.be/WPlf6sJ-Xm8

Teo will report on it when he tests more, the retard you see on the video is 6 degrees ATDC.

On a different note, just came back from my desk, doing some physical work with the casing I f-ed up my bench ECU :/ Not sure what could have happened, will triple check all connections, but it seems like a search for another reasonably priced one. If anyone has one floating around, let me know.

Had some fun today doing my first attempts at stage 1 tune for my 120hp tjet. Successful so far, I got the ECU to raise boost until reaching KFLDBHN without ill effects. Would post logs, but proper ones are yet to be done pending fixing of my logging software which had a very bad day on two different devices (incomplete logs, unable to connect, all kinds of crap).

I have to hand it to Mr. prj about his endless comments here and there about repeatability of results on road (which I never doubted, but now got to experience it in the Bosch context). And I am not even talking about power indications, just getting the same actual/requested/max torque figures in logs between pulls is impossible.

To be continued...

I didn't follow the complete thread or checked your code but i use 2 different variables for lc and nls since dsg gearboxes do not like big retardation values however i choose to cut spark as well directly from szout_w.Unless you are willing to use this code on automatic gearboxes your method using the same variable is fine.

Further more i regulate the boost and maximum requested load to keep the ecu sane while you are on lc.

As prj wrote an rpm dependand lc is the ultimate case as per Med17.1.62 ttrs/rs3 2.5 but that is not always enough.
I have found several ways to cut spark on different ecus but the dwell times serves me well on late m7 and med9 without any issues so feel free to test. if you regulate boost you can use higher retardation values.

I use zwgru on my st10f based ecu but the ignition array is also a choice.

So the logs from my first stage 1 tune attempts. This is essentially only raising MDMAXNMOB (I have the extra boost only in sport mode) to hit KFLDHBN. (Note that in the actual logs there is all kinds of data that is not actually being logged (Zeitronix is disconnected), just dummy values, and also the conversion for requested torque is off by factor of 2, it should be 120% during full throttle pulls, not 60%, need to fix my software).

But my point, look at the pictures, what a crappy stock boost controller, prj already warned me about this and slickkon has continuing problems with it too, I just found it hard to believe that a stock setup can also cause trouble. On the picture this is the first time (out of 5-6 pulls or so) that the boost overshot so much (typically it was hitting only ~230kpa, this time good 240) the throttle had to cut it, nevertheless. If you look at the normal run (this is stock calibration), it also overshoots strongly, but not as much. And I can promise you from my foot feelings from the past, that even on stock pulls there happens to be a very feelable torque dip telling me there is a throttle cut too occasionally. And the DC does not seem to care to do anything. I need to find the parameter that defines the allowable overshot (I know it is somewhere), because I do not intend to tune this boost controller, not for a stock stage 1 tune.

(I also have a 2nd gear pull till red line, all is good there, no overshot, no throttle cuts, but 2nd gear pulls are worthless).