|
nyet
|
 |
« Reply #75 on: September 15, 2011, 12:17:26 PM »
|
|
|
Rick, exactly the approach I am taking, except I don't have all the variable locations I need.
I've narrowed it down to wkrdy and dzwwl
By logging zwgru and wkryda i should be able to definitively figure out which.
Alternatively, bumping TMDYNA might help illuminate things.
Phila: I am definitely NOT always losing 5-6 degrees that i can tell, which is a bit of a mystery. I won't be able to solve that until I can log dzwwl directly. ETA: my IAT is generally max 50-60C, so i should be losing only 0.75-2.25 degrees.. definitely plausible.
Also, if you look at rl axis of FZWWLRLN you'll see it stops at 90 (iirc), so we are far past the rl dependent part in the region of logs I'm looking at. ETA: at 90+ load, FZWWLRLN is 1.0...
EDIT: my KRANH/KRALH are not stock in this file. they are 80 and 2.25 respectively (stock is 120 and 3.75). My understanding was those affect wrk[az], not wkrdy.
|
|
|
|
« Last Edit: September 15, 2011, 12:55:15 PM by nyet »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #76 on: September 15, 2011, 12:33:51 PM »
|
|
|
Function ZUE gives the final output to hardware, zwout.
The fluctuations are visible in zwbas, so I believe the only two possible sources are wkrdy and dzwwl; the rest of your list are zero or post zwbas (that I can tell)... PLEASE tell me if you spot something to the contrary  Dzwwl - delta ignition angle from warm-up
As a side note, initially, I dismissed dzwwl because of this terminology. What threw me is that dzwwl still has an effect AFTER warm-up. The lesson is "don't rule out maps just because of their name" |
|
|
|
« Last Edit: September 15, 2011, 12:45:53 PM by nyet »
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #77 on: September 15, 2011, 01:39:01 PM »
|
|
|
Ok, if it's evident in zwbas it's nothing to do with torque monitoring as zwbas is an input to calculation of torque.
Zwbas is created in ZUE, it is is the product of zwgru and zwappl.
I think we can disregard zwappl, so for clarity it depends only on zwgru.
I'm not sure how you conclude zwgru is dependant on wkrdy - wkrdy isn't an input to zwgru is it?
Rick
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +131/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #78 on: September 15, 2011, 02:06:31 PM »
|
|
|
Once you find which is causing your fluctuation you can investigate that particular function.
This is exactly how I tuned my car with my RAM based data logger. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #79 on: September 15, 2011, 02:30:22 PM »
|
|
|
I'm not sure how you conclude zwgru is dependant on wkrdy - wkrdy isn't an input to zwgru is it?
It's not. dwkrz and wkrdy are output from KR and added to zwgru as part of zwbas. |
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #80 on: September 15, 2011, 03:10:40 PM »
|
|
|
Yea,
so really those need logging.
Rick
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #81 on: September 15, 2011, 05:43:58 PM »
|
|
|
I can't log wkrdy, but I do have zwgru and zwsol now  Definite progress on TWO(!) types of timing interference: 1) dzws gets big enough such that zwsol < zwbas, so sometimes zwout follows zwsol, NOT zwbas!!!! I believe my IOP needs some work.. 2) zwgru is rock solid. dwkrz is steady (not show in graph). zwbas is not. so there is definite wkrdy activity. I need to bug tony/setzi to get me locations for wrkdy and associated variables, unless some of you guys have them handy. I am also going to put KRANH/KRALH back to stock (they affect wkrdy hysteresis NOT dwkrz, like i thought!), then experiment with TMDYNA, which hopefully won't disable dwkrz, just wkrdy. Thoughts? |
|
|
|
« Last Edit: September 15, 2011, 06:11:03 PM by nyet »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #82 on: September 15, 2011, 07:07:29 PM »
|
|
|
I need to bug tony/setzi to get me locations for wrkdy and associated variables, unless some of you guys have them handy. I am also going to put KRANH/KRALH back to stock (they affect wkrdy hysteresis NOT dwkrz, like i thought!), then experiment with TMDYNA, which hopefully won't disable dwkrz, just wkrdy.
Thoughts?
You can log wkrdya_*. |
|
|
|
« Last Edit: September 15, 2011, 07:36:26 PM by phila_dot »
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #83 on: September 16, 2011, 03:06:55 AM »
|
|
|
Great work Nyet.
You'll probably be wanting to log variables the input to wrkdy too.
Rick
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #84 on: September 16, 2011, 10:57:58 AM »
|
|
|
You can log wkrdya_*.
Yea, but those are just the adaptations (starting points).... i need wkrdy, B_mf/zaldy The good news is I can probably disable it easily with DYAFVS = 0, while still keeping wkrdya. ETA: Oh, no thats bad. That ABREGELUNG - restoration of negative wkrdya_* towards 0. Hmm. Odd. That means wkrdy -> wkrdy_a in a single step on a certain B_rkldya/B_rkldyv |
|
|
|
« Last Edit: September 16, 2011, 11:00:56 AM by nyet »
|
Logged
|
|
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +131/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #86 on: September 16, 2011, 11:43:24 AM »
|
|
|
I will try and get you the addresses of wkrdy and B_mf/zaldy this afternoon.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #87 on: September 16, 2011, 11:49:36 AM »
|
|
|
I will try and get you the addresses of wkrdy and B_mf/zaldy this afternoon.
Thanks, as usual, tony! BTW B_mf/zaldy might not be as useful as B_krldy[av] Hell, I'm starting to think this might be a wild goose chase; I see no indication that wkrdy should be moving around terribly quickly. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +131/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #88 on: September 16, 2011, 03:51:31 PM »
|
|
|
wkrdy 0xF9B4 byte unsigned degrees 0.75
I wasn't able to find B_mf, zaldy, or B_krldy because none of then are closely coupled to a map lookup.
|
|
|
|
« Last Edit: September 16, 2011, 03:53:10 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #89 on: September 16, 2011, 04:14:08 PM »
|
|
|
Thanks tony! I'll have more logs up time permitting.
|
|
|
|
|
Logged
|
|
|
|
|
