NefMoto

So far im practicing my skills and want to add LC and DSG farts ability in oldie me7

LC

At the stock routine LC me7 just closes the TB with miges_w request from dsg
Luckily DSG gives feedback when it starts the LC ( id440.7.0 which me7 recognises as b_motaus) and when nmot >= LC_nmot (b_ges, migs_can)
So i divide LC logic in two paths:
1. if(b_motaus & !b_ges) means DSG detect LC mode and rpm starts to rise. In map names i mark it with *active
2. if(b_motaus & b_ges) means its LC mode and nmot reaches desired rpms - DSG request reduction, maps calling *Reduction

kfzwActive - intercepts zwgru so no any corrections
kfzwReduction
fuelCutoffCylsActive - number of cylinders to shut off by generating evz_austot mask
fuelCutoffCylsReduction

enableFuelCut - active fuelcut control
enableTsrldynCut - active spark control

tsrldynDelay - delay between zeroeng tsrldyn, runs at 10ms raster

miges_add - addition to miges ( slow path - throttle cut)
miges_min - min value of miges after addition

requestBoost - plsol at LC
requestLamfa - lamfaw at LC

*****

First testing shows some mistakes in code (miges overflow and lamfaw fault) but in general it works

Questions here -
What preferrable settings should i take as a starting point?
Should i fill miges_w with FFs to eliminate throttle control at all?
And so on?



DSG FARTS

What exactly behind the loud and nice DSG farts?
only zwmn doesnt give it and i believe something with the spark cut should be done
i had nice farts when one spark coil goes bad lol

simply routine like if(b_ges) then tsrldyn=0 gives too loud bang with jerking schalt
ive got an idea to implement cutoff mask to spark coils but unable to find routine with p2.0 - p2.3 outputs in ecu yet

Nice.
I tried to make some farts with changed some timing maps, but, doesn't have them.
I have me7.5 with dq250 and 018h bam.

Tier 2 of being a blindly copy-cat

DSG keeps migs_can reduction even if nmot falls below launch control rpm setting in DSG
So i had to implement new variable LC_nmot which stores nmot when its firstly hit reduction rpm and use it as a flag to hit reduction in my routine, basically its target LC rpm

Also evz_austot > 0  triggered b_bevab and lambda follows LASOAB so another hook placed here to keep fueling at desired in all conditions


Next thing here is the throttle cut, i have to fix ve model for now but anyway even if its a peaks here, i dont want to throttle control sooo... set ps_w = pvdkds_w at LC ?

The sound you are referring to is selective cut.

Basically if you are hitting zwmin (and you should be, and zwmin should not be ridiculously low so you get huge egt spike), you need to start cutting cylinders by using redsol.
And the redsol pattern makes also quite a big difference.

This is also the logic used during OEM launch control.

Ok ive succesfully tested LC with fadeout but im using own fadeout routine bc im stupid af and didnt realize there was redsol..

Also i have made simple routine with evz_austot of cutting 1 cyl at shifts. sounds nice for sure but its jerking at mid loads so im very interested in some kind of torque reduction implemented in MDRED but this translation are not clear for me and it seems that its only for nmax / asr interventions ?


MDRED


Is there a way to enable cyl fadeout without custom code?
and if no is it enough to feed redsol with 1 cyl cut or its better to somehow determine reduction stage? (lets say nmot x rl as input and redsol as output and checking conditions for hitting zwmin )?
Im i right about slow intervention? If yes - i believe something should be done to prevent it when using conservative zwmin
Im asking bc i dont have a car for now and limited with remote testing, i know how to make this stuff but i need to know the principles

First is to dump your own routine.
Second, I don't know if ME7 has capability to apply cylinder cut in case of increasing fast path torque request or if it just cuts throttle, if it can't do it with timing. I never tested this.

If it does not have it, then you will have to write a lot of logic with torque control. You can't just cut a cylinder randomly, because ignition is still late.
I don't know if it already calculates the torque correctly when a cylinder is cut or not. If it does, then that's half the job done at least, but you might have to hook into that calculation to do prediction, so that the ignition angle can be restored to what is correct.

Also, if you are just cutting a cylinder every time (and make sure to do it through redsol so a pattern is applied based on firing order, otherwise it's shit) then it's 100% going to be jerky as fuck, because most of the time cutting a cylinder cuts over 25% torque on a 4 cylinder, and this is way too much for low load shifts.

Got it, thx for the input thats brilliant info

me7 divides migs_can for 2 paths: migs_w (directly from canbus and its fast path) and miges_w (slow path via throttle - only applied when b_ges from canbus is true)
migs_w used at shifts and b_ges triggered throttle cut at LC to holds rpms at steady state in stock routine

So no throttle interventions when shifts even at pretty conservative zwmin (although throttle cuts are here in stock but for different reason)

For now i have redneu triggered when misol > mizwmn its working from stock routine but b_mdee false and redsol came only when b_sa i believe its from hysteresys or redzem.. or i can force it anyway that part are pretty good in stock

As for torque calc - it seem there is etazaist and its factor to miist_w so thats looking good (bosch doesnt got a rocket science here - its just a factor of REDMX - if you cut 2 of 4 cyls, you got 0.5 factor to miist)

*5 min job goes wild here*

Yep... :D
But it seems with a little bit of help you now understand how it works, so now it is about modding it a little to do what you want.

Btw, for launch control, you can easily just write your own routine and make it kick in a little before the gearbox limiter.
The way I did rolling antilag was to dynamically force NMAX and then I simply made two maps - one that has nmot_w - current NMAX on axis, and the output is redsol (e.g. cut 1 cylinder 100 rpm before, 2 cylinders at 0 rpm from target, 3 cylinders -100 rpm etc). And second map is simply KFZW style with an ignition offset. You can do a similar thing with launch control...

Well this is a little simplified...

I did a similar thing, but more complex:
When LC conditions are met (b_br & b_motaus) it using 8x1 map (nmot) with ign angle override (about 0..-3 deg to build boost), plsol and lamsoni (iirc - target lambda) fixed values, miges are ignored due to DSG wants to operate with TB and 8x1 map (nmot) with output of number of cylinders to cut (filled with 1 near LC region and made a brrrrrrt sound which every man loves so much tbh)

When DSG triggers b_ges it means nmot reached DSG LC nmot, thus are nailed as LC_nmot in ram so i dont need to set it manually
And if nmot > LC_nmot routine uses more agressive cyl cut 8x1 map so nmot floating around LC_nmot

OEM on newer cars closes the throttle a little too. Not much to create lag, but enough that it never needs to cut more than 1-2 cylinders and has reasonable ignition timing.

Yikes! It works :)

Ive tried force b_mdee and generally it works but sometimes it cuts 2 cyls at low loads even if misol are slightly lower than mizwmn, idk about reasons.. etazaist 75% when cutting one gives only 60% miist with +3 ign and DSG required about 20% at shifts which only possible at -12 deg with 2 cyl cut so IRL/IOP needs to be lowered to shown lowered relative moment or its just poor calculation from stock.. duno

Anyway i decided to made my own stupid and simple logic here - i have a KFZWMNGS_drive _sport _tip for ignition angle at shifts (with momentenreduktion ofc)
And introduced REDSOL_drive _sport _tip maps for number of cut cyls

So i manually compensate zwmn with redsol and now its time to find best combinations at different areas and job done, with initial settings shown at attachment it works pretty hot and not jerking at all but i see miist(60%) > misol(24%) at shifts. Is it badly for DSG? Does it raise sync window in that case?
This tune has an issues with ps_w and rl calculation so i need to make things clear and see how it goes

Seems that only ZW reduction are the best for performance (idk if short EGT spike are hurt something ??) and high zwmn + redsol for show-off in mid-load range

Should i touch AFR at shifts? What if make an extra enrichment at 100-200 ms shifts?

Somehow i cannot edit attachments so here is another funny pic

As for LC its also works fine with redsol, ill hope to get some video soon

prj, thanks again for your time and especially for giant impact of nefmoto community by sharing priceless info
I see bunch of haters here from time to time wanting feed em with free solutions but for truly learning person much more important is to know where to find answers if you stuck and develop own solution and thats the key to knowledge  ::)

About EGT spike - it depends how high it goes.
If it goes only a little ok. But this is what the ZWMIN is for, to limit the max EGT spike, actually on newer ECU's there is exactly what you describe KFZWMNGS - minimum ignition during shift. It's already there stock, exactly for the same reason.

When you have already a very highly tuned car running on EGT limit then sudden -10 deg ignition can create some problems, in those cases it is a good idea to force it to cut some cylinders. The cutout of the cylinders also cools them, so now the -10 deg is suddenly not a problem anymore.
It does not make the car slower, because throttle stays 100% open and boost stays where it needs to be.

AFR during shift - if you still have EGT problems you can dump a little sure. But if you can solve it with good balancing of ignition angle and cylinder cutting then no need.

So the results
Long shiftings for test purpose with +3 deg zwmn and 1 cyl cutout
https://youtu.be/xgnvEQXXbhE

LC with 3 cyl cutout
https://youtube.com/shorts/RexLzrRRqEQ

For LC close throttle a little bit, it will sound much nicer.
You can set NMAX when LC active to the target and start cutting some cyls 150 rpm before it is hit.
For example 1 cyl 150 rpm before, 2 cyls 50 rpm before, 3 cyls 50 rpm after, 4 cyls 150 rpm after.

I don't know to develope in  IDA, but i make many things with analogy with other files....other things....(please don't comment here)
I saw in golf 5 dsg file, this map KLREDNMXDid we have it in our me7.5 018h or 032hf?
I have the problem , feel like throttle cut (shoots when dsg change gears) on my 1.8t with dsg from 3 years.
I don;t know if they are from ignition cut, or fuel cut or throttle cut.
Other thing what is different from golf 5 is CREDSTU.
Maybe if this help.....please let me know.

Hello
Can someone help me too, please.
It is a great request if you could help me
I would also like to do dsg farts on a 1.8T with DSG.
06A906032HF
Thank you

+1 always helpful if you ask the right questions


The "cutout" is the way to go make the LC sound like a modern car, correct? Did you play abit more to finetune the sound? Do your farts work under wot and high load?

There is a map with load x rpm with number of cutout cylinders and kfzwmngs for minimun advance during shift so its a plenty room for tune shifting time and some kind of sound (and probably cutout mask) but unfortunatelly im far away from those project cars and didnt had a chance to hear it personally  ::)
Yes its works at wot

I think its basic fart, not a tiger roars like AMGs

Hello,

I've sent you a couple PM's regarding this, I have an audi tt APX that i've converted to wideband using HJ ecu, It's been dyno tuned to 250WHP running around 1.5 bar of boost, recently i've swapped to dq250 from a passat 6 2.0tdi and did the TCU tune to suit the shift points etc, also converted to MK60 ABS with ESP from a 4motion car.

Could you help me with the DSG mode multimap and the LC/DSG farts?
I'm one of a few in my country with a dsg swapped 1.8t, all the other cars are owned by my friend who helped me with the swap, we're both trying to get the tunes down so the functionality is as close to a factory equipped dsg car can be, he has an Ibiza with around 450 WHP and launch control would help him alot to spool the big turbo since he does drag racing.

Any help is appreciated, thanks.

Bringing this old topic back. Can we talk more about the cylinder shutoff pattern? I am dealing with ECU with no redsol in AEVAB. Instead, it's sending a bitmask which gets OR'd with abmm, so unfortunately, I can't see what happend to evz_aus when redsol > 0 like it's possible on MED17.5. I am trying to understand what happens to abmm when the redsol stays the same throughout the intervention. Do I understand it correctly that the same pattern calculated once when the change in redsol was detected gets applied throughout the whole intervention? I.e., if evrbgn_one was 1, then it will cut cyl 1 during the whole time of intervention? Or am I mistaken and after 2 turns of the crank, it will blank cylinder 2 and so will it continue?
I'm not getting any kind of a "dsg fart" sound whatsoever even with 2 or 3 out of 6 cylinders shutoff.

Okay, I think I got one of my questions answered - I can't hear the "fart" because cylinder cutoff time is just too short. Had to tweak the code to force the ECU to stop transferring torque intervention from the fast path (schnell? pfad) to the air path (Luft(?) pfad), otherwise it would start to close the throttle almost immediately depending on the size of the torque intervention. Plus, of course, ASR is kicking in very quickly and cylinders are cut off for a very short time. Now I can get them to cut off for about 0.2-0.3 seconds, the sound is not a "canonical" "fart", though. Sounds more like as if the engine stops for a brief moment and then resumes. Must be the cutoff pattern and perhaps the exhaust system damping the resonance(s).