paracaidista2.7T
Newbie
Karma: +6/-0
 Offline
Posts: 21
|
 |
« Reply #60 on: September 11, 2011, 05:43:43 PM »
|
|
|
I used the method that Rick mentioned. I haven't had any TM issues with it for about 10k miles.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #61 on: September 11, 2011, 06:42:18 PM »
|
|
|
I spent some time over the weekend going through the assembler code that deals with KFMIRL and LDRXN. I had one branch instruction mislabeled which lead me to believe that KFMIRL limits LDRXN, when in actuality LDRXN limits KFMIRL. So what the FR says is correct, and I was wrong in this case. Glad we could have this argument though, cause in the process I found an error in my ECU disassembly.  I cleaned up the thread so that everything stays on topic and there is no misleading information. Also, I was right with what I was saying about KFMIRL being driven by the combustion efficiency. The axis for KFMIRL is driver requested torque percent scaled by ignition efficiency and lambda efficiency, so you can think of this as driver requested torque percent corrected for combustion efficiency. |
|
|
|
« Last Edit: September 13, 2011, 03:41:44 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #62 on: September 12, 2011, 09:52:51 AM »
|
|
|
Regarding timing oscillations, have you tried logging with knock control completely disabled?
I'm scared to do this on a WOT full boost run. What variables can I log that show knock corrections that aren't reflected in dwkrz*? wkr*? wkrm*? zkrvf*? 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. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #63 on: September 14, 2011, 03:14:36 PM »
|
|
|
Have you looked at turning off torque control of ignition angle via B_zwappl? I would try this before turning off KR.
Stupid question. How? Find and modify CWMDAPP bit 0? |
|
|
|
« Last Edit: September 14, 2011, 04:40:03 PM by nyet »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #64 on: September 14, 2011, 03:34:23 PM »
|
|
|
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
|
|
|
|
« Last Edit: September 14, 2011, 03:40:10 PM by nyet »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #65 on: September 14, 2011, 04:55:57 PM »
|
|
|
Hmm. In my case, it can't be zwsol, since my zwbas displays the crazy oscillations.  This leaves: zwgru,dzwzk,dzwbank(ZGRU) dzwwl(ZWWL) zswob(ZWOB) dwkr,wkrdy(KR) and the various calibration variables vszw, ZWAPPL, vstdzw which shouldn't apply. I believe zswob (overboost) doesn't apply. I believe dzwbank doesn't apply (depends on sy_zizwv? always 0?) I believe dzwzk doesn't apply (KFDZK is all zeros). I have logged dwkr, and that's not it (slow CF/KR) Which leaves dzwwl. I can log zwgru, but haven't yet I can log wkrdya, but haven't yet (I assume these are from trims and dont move fast enough to matter, unless we are moving back and forth between several of them) I don't have the locations for dzwwl, dzwzk or dzwbank yet. Comments?  |
|
|
|
« Last Edit: September 14, 2011, 10:29:58 PM by nyet »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #66 on: September 14, 2011, 06:06:18 PM »
|
|
|
Have you looked at turning off torque control of ignition angle via B_zwappl? I would try this before turning off KR.
Stupid question. How? Find and modify CWMDAPP bit 0? I think setting CWMDAPP (181BD) to 1 should do it. 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
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. Hmm. In my case, it can't be zwsol, since my zwbas displays the crazy oscillations. This leaves: zwgru,dzwzk,dzwbank(ZGRU) dzwwl(ZWWL) zswob(ZWOB) dwkr,wkrdy(KR) and the various calibration variables vszw, ZWAPPL, vstdzw which shouldn't apply. I believe zswob (overboost) doesn't apply. I believe dzwbank doesn't apply (depends on sy_zizwv? always 0?) I believe dzwwl (warmup) doesn't apply. I have logged dwkr, and that's not it (slow CF/KR) Really that only leaves dzwzk, but it looks like KFDZK is all zeros. I can log zwgru, but haven't yet I can log wkrdya, but haven't yet (I assume these are from trims and dont move fast enough to matter, unless we are moving back and forth between several of them) I don't have the locations for dzwzk or dzwbank yet. Comments? 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. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #67 on: September 14, 2011, 06:13:18 PM »
|
|
|
I think setting CWMDAPP (181BD) to 1 should do it.
Any possible side effects? If it works, can I just leave it set to 1? zwsol will affect zwbas_array.
so zwbasar_* is not zwbas in the FR? Do you have the ram location for zwbas handy? 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.
Agreed. This is my feeling at this point as well. |
|
|
|
« Last Edit: September 14, 2011, 06:15:08 PM by nyet »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #68 on: September 14, 2011, 06:36:41 PM »
|
|
|
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: 8D0907551M 002
etazws 0x380D96 Percent byte unsigned 0.5
dzws 0x380D95 Degrees byte signed 0.75
zwopt 0x380CB6 Degrees byte signed 0.75
zwsol 0x380D97 Degrees byte signed 0.75
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?) |
|
|
|
« Last Edit: September 14, 2011, 07:08:11 PM by nyet »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #69 on: September 14, 2011, 08:28:21 PM »
|
|
|
zwsol will affect zwbas_array.
so zwbasar_* is not zwbas in the FR? Do you have the ram location for zwbas handy? I misspoke, I was thinking zwappl. zwsol does not affect zwbas. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #70 on: September 14, 2011, 10:22:01 PM »
|
|
|
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 |
|
|
|
« Last Edit: September 14, 2011, 10:33:42 PM by nyet »
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #71 on: September 15, 2011, 02:20:06 AM »
|
|
|
Don't thunk zwwl is your issue. My guess is wkr
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #72 on: September 15, 2011, 07:31:18 AM »
|
|
|
Don't thunk zwwl is your issue. My guess is wkr
That would be obvious even in ECUx logs. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #73 on: September 15, 2011, 08:04:11 AM »
|
|
|
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 dzwwl also has a load dependant factor. It doesn't look like it would cause oscillations like that though. According to this function, we should be losing ~6 degrees up top? I have actually been meaning to start a thread about wkryda. I am getting adaptation via wkrdya through almost my entire log. The first time I hit positive map pressure the ECU pulls 1.5 degrees and it only advances to -0.75 by the end of a long log. I have not touched any of the KRAN maps. I really cannot see this causing the oscillations unless you did something weird to the KRAN maps. wkrdya can be disabled by setting TMDYNA to an temp unreachable by tmot. |
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #74 on: September 15, 2011, 11:49:56 AM »
|
|
|
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
|
|
|
|
|
Logged
|
|
|
|
|
