|
phila_dot
|
 |
« Reply #30 on: November 05, 2011, 12:38:33 PM »
|
|
|
while i'm not sure this is the best way to fix the oscillations yet
dzweta has fixed them... you must tune the map, you can't just zero it or you will have other issues.
it is a percentage map for timing shift under zwsol.
after making progressive changes to only dzweta this is what happened to timing
You are not actually fixing the problem using this method. DZWETA is not the problem, etazws is. My guess is the root of the issue is in MDBAS. Edit: What "other" problems are you seeing when you zero out DZWETA? By zeroing it out you are isolating zwsol to zwopt (basically KFZWOP). |
|
|
|
« Last Edit: November 05, 2011, 01:23:23 PM by phila_dot »
|
Logged
|
|
|
|
|
judeisnotobscure
|
|
« Reply #31 on: November 05, 2011, 02:07:58 PM »
|
|
|
idle bounces and revs hang during shifts if u zero dzweta
I agree that this isn't a fix but a workaround. that's why i said it's not the best way to fix it.
|
|
|
|
|
Logged
|
I have a b5 s4
but i just want to dance.
|
|
|
|
phila_dot
|
|
« Reply #32 on: November 05, 2011, 02:37:34 PM »
|
|
|
idle bounces and revs hang during shifts if u zero dzweta
Yea... that makes sense. I wasn't thinking about everything that would bypass. |
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #33 on: November 22, 2011, 04:00:04 AM »
|
|
|
Just got a car in that's doing this, looking forward to having a play. You guys get anywhere?
Rick
|
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #34 on: November 22, 2011, 09:42:11 AM »
|
|
|
I didn't. The car mysteriously drops 6+ degrees of timing for a short moment without it being reflected in cylinder retardation column. I logged several ram variables and flags mentioned in this thread to no avail of any unusual activity.
Looking forward to your own findings.
|
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #35 on: November 22, 2011, 09:49:39 AM »
|
|
|
Did you look at thw wkrdy_n adaptation values for each cylinder?
Is the timing relatively smooth apart from the reduction?
Rick
|
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #36 on: November 22, 2011, 11:02:33 AM »
|
|
|
To illustrate, here is ecuX graph. I know I get torque intervention at least above 6k since I am boosting more than requested there, but the wild ride starts much sooner than that. Look at the severe timing dips and recoveries through the pull.
One notable thing to add is that I wasn't getting this behavior before when my MAF was running underscaled by about 20% and never hitting req load, at least in logs that is.
Now this got me thinking. Could be that if you OVERSCALE your MAF accidentally you always hit overload condition since internal ECU calculations for air intake show higher load than in reality?
|
|
|
|
« Last Edit: November 22, 2011, 11:16:53 AM by julex »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #37 on: November 22, 2011, 11:18:20 AM »
|
|
|
Log zwgru, dwkrz, wkrdy, zwbas, zwsol, zwist, and zwout.
Feel like a broken record here, but have you tried setting CWMDAPP to 1?
|
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #38 on: November 22, 2011, 11:30:11 AM »
|
|
|
Log zwgru, dwkrz, wkrdy, zwbas, zwsol, zwist, and zwout.
Feel like a broken record here, but have you tried setting CWMDAPP to 1?
zwgru - check dwkrz - I can only find dwkrz_0,dwkrz_1,dwkrz_2,dwkrz_3,dwkrz_4,dwkrz_5 - should I log this? wkrdy - check zwbas - what's the address and data type? zwsol - what's the address and data type? zwist - check zwout -check I haven't run with CWMDAPP set to 1 but could... just afraid to disable this. I'd rather try other approaches. By setting to "1", do you mean "FF" or "01" hex? Thanks. |
|
|
|
« Last Edit: November 22, 2011, 11:32:12 AM by julex »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #39 on: November 22, 2011, 11:47:15 AM »
|
|
|
zwbasar_0 , {} , 0x380D8B, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_1 , {} , 0x380D8C, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_2 , {} , 0x380D8D, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_3 , {} , 0x380D8E, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_4 , {} , 0x380D8F, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_5 , {} , 0x380D90, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwsol , {} , 0x380D97, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {}
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #40 on: November 22, 2011, 12:02:31 PM »
|
|
|
Log zwgru, dwkrz, wkrdy, zwbas, zwsol, zwist, and zwout.
Feel like a broken record here, but have you tried setting CWMDAPP to 1?
zwgru - check dwkrz - I can only find dwkrz_0,dwkrz_1,dwkrz_2,dwkrz_3,dwkrz_4,dwkrz_5 - should I log this? wkrdy - check zwbas - what's the address and data type? zwsol - what's the address and data type? zwist - check zwout -check I haven't run with CWMDAPP set to 1 but could... just afraid to disable this. I'd rather try other approaches. By setting to "1", do you mean "FF" or "01" hex? Thanks. Sorry. Dwkrz is a cylinder specific array, zwbas is a four member array that you should have, and use the wkrdy listed below. wkrdy 0xF9B4 byte unsigned degrees 0.75 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 Set CWMDAPP to 01. |
|
|
|
« Last Edit: November 22, 2011, 12:04:57 PM by phila_dot »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #41 on: November 22, 2011, 12:06:52 PM »
|
|
|
zwbasar_0 , {} , 0x380D8B, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_1 , {} , 0x380D8C, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_2 , {} , 0x380D8D, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_3 , {} , 0x380D8E, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_4 , {} , 0x380D8F, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwbasar_5 , {} , 0x380D90, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {Basiszündwinkelarray}
zwsol , {} , 0x380D97, 1, 0x0000, {°KW} , 1, 0, 0.75, 0, {}
Everything that I have looked at shows that zwbas is not cylinder specific and is only a four member array. http://nefariousmotorsports.com/forum/index.php/topic,1127.0title,.html |
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #42 on: November 22, 2011, 03:17:02 PM »
|
|
|
Let me know what you guys think.
There are quite a few drastic timing reductions in high rev range... I also exceed load quite a bit. Combined with the log, does that mean torque intervention?
I have NOT disabled it via CWMDAPP just yet. That will be tomorrow's logging session.
|
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #43 on: November 22, 2011, 03:55:04 PM »
|
|
|
Yep,
torque intervention is your issue. ZWGRU is nice and smooth, ZWSOL is causing the mess.
Rick
|
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #44 on: November 23, 2011, 06:09:05 AM »
|
|
|
Well on this car, oscilaltions were an easy fix, it was simply poorly calibrated torque model. I've attached the fixed screenshot. There are some knock corrections but they can be smoothed out.
What is interesting on this log, is that ZWBAS is higher than ZWGRU. Only addition I can think of is down to warmup which had well finished. Need to take a look at KR.
Rick
|
|
|
|
|
Logged
|
|
|
|
|
