I used the method that Rick mentioned. I haven't had any TM issues with it for about 10k miles.

I believe if B_kr is not set (TMKR > tmot) then KRRA is completely shut down. I think your only option would be to log knock detection in KRKE.

Have you looked at turning off torque control of ignition angle via B_zwappl? I would try this before turning off KR.

Also, there are a few more torque intervention flags to test

B_NOZWE - Condition flag: no ignition angle intervention on the engine torque structure

B_ZWVS - Condition flag for fast external ignition angle intervention on the torque interface
seems to only be enabled for B_llrein (idle regulation), so this is probably not active.

B_ZWVZ - Condition flag for ignition angle intervention on the torque interface

I think setting CWMDAPP (181BD) to 1 should do it.


B_zwappl will neutralize this in ZUE and make the other bits you listed a non factor. I didn't see any way to manipulate the others easily.


zwsol will affect zwbas_array.

I have been looking at wkrdya because I am getting long term adaptation, but I don't think this could cause the problem.

I don't think it could be zwgru because all points are interpolated within and between the maps.

Basically, this leaves etazws and dzws

if (zwopt-dzws) < zwbas, then zwist will follow zwopt-dzws if zwappl=0.

Im still trying to decipher MDZW.

etazws = (mizsol - dmaufer)/(miopt*etazaist) if redist == 1
etazws = (mizsol - dmaufer)/miopt if redist == 0

which goes into DZWETA to generate dzws.

So. To get a SMALLER dzws, we need a LARGER etazws. If etazws is too small, we'll get a large dzws, which might make zwsol < zwbas.

If miopt is too big, or (mizsol-dmaufr) is too small, etazws will be too small

if dmaufr is too big, (mizsol-dmaufr) is too small.

So the possible causes are:

1) miopt too big
2) dmaufr too big
3) mizsol too small

sound right?

From tony, i have:


so I hope to get things figured out by logging those. Hopefully it will be enough, or I will also need to log mizsol, miopt, and dmaufr (and possibly etazaist?)

Ok. That means the source is either zwgru (which I can log) or dzwwl (which I can't log)

Turns out, dzwwl DEFINITELY looks suspect. Part of it is tmot dependent (KFZWWLRL) and part is tans dependent (FZWWKRLN, KFZWWLNM). The former is zero once we are up to temp, but the latter is most definitely non-zero.



What I dont get is that tans doesn't change much. Which really leaves wkrdya

That would be obvious even in ECUx logs.

We need to go back to basics here.  I haven't used Setzi's logger yet so not sure what variables are available/known, but this is how I would approach it.

Function ZUE gives the final output to hardware, zwout.

ZUE has various inputs which define the ignition angle.  They are:

Zwguru - basic ignition angle
Zwstt - Ignition angle during start
Dzwwl - delta ignition angle from warm-up
Wkrdy - ignition retard during dyn-function of knock control
Dwkrz - cyl.-spec. ignition-timing retardation with retardation for dynamics
Zwsol - desired ignition angle from torque intervention
B_nozwe - condition no ignition angle intervention of torque structure
Zwspae - retarded ignition angle
vszw - Ignition-timing correction by adjusting system
Zwappl - Applications interface ignition angle adjustment
cvzwzyl- device control value ignition

Now some of these are irrelevant, but the others need logging to see what they are outputting.  Once you find which is causing your fluctuation you can investigate that particular function.

Rick