So true..

Can anyone answer my question above ?

Thanks

Hey adam,

Thanks for the insight, I agree, of course if I set a hard cut rev at 6800 and have set my rev limiter in other singles at 5000 there is no use, I won't reach it. But the question was more the other way around and for small gap.

But maybe first as you point out I should be sure I understood what physically means a hard rev cut...
So what I think is intended to do in a hard cut rev limiter is to cut the fuel at a certain rpm, so then rpm will a little drop beacause engine is cut, but if you keep pushing on throttle then it will go back up to the rpm where fuel is cut, and then go a little back dropping and then back up etc etc so it will make "rotototo"  

But my question is more for let's say a very short "gap" between the rev limiter defined in Nmax singles and the one we should put here in last column of KFTSRL, 50 rpm above or below for instance...

So if I have set my rev limiter to 6800 in the other singles of the tune (stock value), in KFTSRL if I put 6840rpm in last column and 6800 in column before maybe the car can still reach this 6840 rpm even if it is slightly above the rev limiter of 6800 ? Or it really will never reach any value above the rev limiter set to 6800 in stock software ? meaning it is really reactive then ?

My instinct would be that the best way is to set last column of KFTSRL to exactly the rev limiter of 6800 and column before to a value really close and below like 6760 rpm in my case to be sure to reach that and have the "cut" happen

Ok thanks adam, so just to be sure we are aligned, what I want is to cut spark before I cut fuel right ?
So in KFTSRL I can cut spark at 7100 for instance (2 last rows would be 7060 and 7100 for instance) and then I can set fuel cut in Nmax singles at 7200 rpm?

Or another example, if i take this image which was posted before :


I should have Nmax (fuel cut) set to a value >7080rpm ? let's say something around 7200 rpm in the singles Nmax?

Because you said in an old message on this thread :

So I thought fuel cut set by nmax should be = rpm spark cut set in KFTSRL ?

NMAX isn't straight fuel cut. There's a torque reduction process that is employed just prior to the hard limit which softens the effect of hard cut. That needs to be numbed to have proper fuel cut, otherwise just set all the NMAX limiters to a value above your greatest dwell RPM column. Be advised, spark cut is brutal on the engine and transmission.

Its two tables

Offenzeit fur funkenbandzundung

&

Schliebzeitkennfeld

Its in post 6...

FUBAOF set to 0
KFTSRL set like image if you want Revlimit @7200rpm

FR:

"Basically, spark band ignition shows the desired effect when the secondary ignition is within
of the smallest possible angular range. The optimal distance would be about 1 degree.
For this purpose, the open time FUBAOF must be chosen correspondingly small for the common coil ignition systems. This
can, however, lead to deterioration as some engines require the full spark duration.
Usual values ​​for a spark burning duration in which no significant HC increase is noticed are included
about 0.5ms. However, this value cannot be regarded as binding.
The open time is in various projects in which spark band ignition is already used
an order of magnitude in which the spark has long since swung out (2ms). The afterglow is only after
completely reloaded the coil. In this case the ignition would normally be caused by the first
Sparks are already too advanced to be supported by a second spark.
Nevertheless, an improvement of the cold start at extremely low temperatures is noticed in these projects
been. However, there is only an improvement if the first spark has not led to combustion
and the mixture ratios on the candle at the time of the first sparking are such that this one
Inflammation triggers."

after reading FUBAOF in FR. I keep thinking that it is not a good idea ... if someone has a coherent explanation of why set to 0, let them say it. Because in this post everyone is setting it to 0. It is not necessary for the hardcut and it is not good.

thanks for intervening.  and I think like you.  We are here to contribute and learn together.  not to disrespect us .... greetings

Of course you are. And with only 1 post, I bet you'll be back and contributing to the forum within minutes.