|
littco
|
 |
« Reply #105 on: January 31, 2013, 04:15:24 PM »
|
|
|
My ARMD interventions are over!
Solution:
1) inspect xdf pack. If KFDMDARO is at 0x1DE1C, change it to 0x1DE7C
2) alter KFDMDARO at column "50" (% of torque engine is generationg, this is NOT load!) and put in 100% for all gears, or however you feel it should be appropriate.
Page 638 diagram explains how it works. Input dmarv_w is compared to output of several tables and appropriate bits are set. KFDMDARO gets %torque (x-axis) and gear (y-axis) and resulting threshold is returned. If dmarv_w is larger than table value, you get intervention in torque % amount via fast path timing change.
Setting a cell to 100 causes the condition to be no longer valid and rpm deviation is ignored.
Can I just check your not setting KFDMDADP? To 100. I ask as I have 4 KFDMDARO maps 0-1-2-3.. 3 are the same and 1 is very slightly different.. I'll try setting them all to 100 on the 50 line... Also I set DMARMX to 1 across the map. |
|
|
|
« Last Edit: January 31, 2013, 04:28:16 PM by littco »
|
Logged
|
|
|
|
|
julex
|
|
« Reply #106 on: January 31, 2013, 04:38:53 PM »
|
|
|
Can I just check your not setting KFDMDADP? To 100.
I ask as I have 4 KFDMDARO maps 0-1-2-3.. 3 are the same and 1 is very slightly different..
I'll try setting them all to 100 on the 50 line...
Also I set DMARMX to 1 across the map.
I don't have the PDF in front of me but for kfdmdadp to be active for comparison, b_dashv or whatever the bit is must be which is not in my case. Having said that, I set kfdmdadp to 100 too as I don't attenuation with neither increasing nor falling while being over 50% torque request. I know the kfdmdadp alone doesnt work as to date everyone had bad set pack with kfdmdaro actually pointing to kfdmdadp map location and changes weren't in effect when going wot. |
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #107 on: January 31, 2013, 05:04:41 PM »
|
|
|
SGA06MDUB is not correctly defined based on this information.
The axis reads: 3, 4, 5, 6, 255, 6
Should read: 1, 2, 3, 4, 5, 6
right?
DMARMX as defined here is defaulted to 0.00 for the entire table. Is this correct?
Finally: Please confirm:
KFDMDADP: 0x1DE1C 6x8
KFDMDARO: 0x1DE7C 6x8
KFDMDAROS: 0x1DEDC 6x8
All three share the two axis you showed before.
If I get some clarity on all of this, and of course I'll continue researching, then I have a good XDF for the community ready to go / fully updated.
|
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #108 on: January 31, 2013, 05:09:39 PM »
|
|
|
SGA06MDUB is not correctly defined based on this information.
The axis reads: 3, 4, 5, 6, 255, 6
Should read: 1, 2, 3, 4, 5, 6
right?
DMARMX as defined here is defaulted to 0.00 for the entire table. Is this correct?
Finally: Please confirm:
KFDMDADP: 0x1DE1C 6x8
KFDMDARO: 0x1DE7C 6x8
KFDMDAROS: 0x1DEDC 6x8
All three share the two axis you showed before.
If I get some clarity on all of this, and of course I'll continue researching, then I have a good XDF for the community ready to go / fully updated.
Yes SGA06MDUB should be 1-2-3-4-5-6 relating to gangi Dmarmx in my case goes from 1.17 @-9 to 2.89 @110, its not linear though, more weight to higher temps. I've set this to 1.17 from the whole table. The other 3 do share the same axis, gangi and  |
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #109 on: January 31, 2013, 05:11:08 PM »
|
|
|
Yes SGA06MDUB should be 1-2-3-4-5-6 relating to gangi
can you clarify the address / details on your working SGA06MDUB? |
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #110 on: January 31, 2013, 05:15:19 PM »
|
|
|
Dmarmx in my case goes from 1.17 @-9 to 2.89 @110, its not linear though, more weight to higher temps. I've set this to 1.17 from the whole table.
Can you please clarify your details on DMARMX too? |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #111 on: January 31, 2013, 05:58:15 PM »
|
|
|
It's all in my post on the previous page...
The gangi axis doesn't exist...the stutzstellen variable is created from gangi and then just used to calculate the map location. Just label it in your definition.
As for axis length, it's identified in the hex just before the axis.
|
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #112 on: January 31, 2013, 06:52:12 PM »
|
|
|
OK, well give what was shown before, here is the XDF:
DMARMX and SGA06MDUB require fixing.
SGA06MDUB is just an axis, so it just shows the axis values wrong, that's simply ugly, but non consequential.
DMARMX is totally wrong. Somebody should take a screen shot of their exact settings in tuner-pro, because there isn't enough information as described so far.
|
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #113 on: January 31, 2013, 06:56:33 PM »
|
|
|
Here is the entire DMARMX setup. Please tell me what's wrong so I can correct this for the XDF.
|
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #114 on: January 31, 2013, 07:05:11 PM »
|
|
|
SGA06MDUB is repaired. The address is 0x1A603 not 0x1A605.
Just need a response on correct changes for DMARMX.
|
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #115 on: January 31, 2013, 07:16:30 PM »
|
|
|
How does this look for DMARMX? Is this correct? Randomly searched up and down from wrong address.
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #116 on: January 31, 2013, 08:51:09 PM »
|
|
|
How does this look for DMARMX? Is this correct? Randomly searched up and down from wrong address.
Nope, first one's correct. 0x19B9D It's all zero. I would do one row and six columns though. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #117 on: January 31, 2013, 08:55:47 PM »
|
|
|
SGA06MDUB is repaired. The address is 0x1A603 not 0x1A605.
Just need a response on correct changes for DMARMX.
This axis doesn't exist. The gangi axis doesn't exist...the stutzstellen variable is created from gangi and then just used to calculate the map location. Just label it in your definition.
I just use external (manual) for the label source and punch in the values. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #118 on: January 31, 2013, 10:17:05 PM »
|
|
|
1) inspect xdf pack. If KFDMDARO is at 0x1DE1C, change it to 0x1DE7C
Interesting. I've always had the right value. Not sure where the wrong value came from "KFDMDADP","0x1de1c","Upper threshold for torque intervention under dashpot","8x6","16 Bit (LoHi)","-","%","%","-","0.001526","0.003052","1.0","1.001056","20.002808","0x290","0x3334" "KFDMDARO","0x1de7c","Upper threshold for torque intervention","8x6","16 Bit (LoHi)","-","%","%","-","0.001526","0.003052","1.0","1.001056","20.002808","0x290","0x3334" |
|
|
|
|
Logged
|
|
|
|
|
marcellus
|
|
« Reply #119 on: January 31, 2013, 10:20:31 PM »
|
|
|
Interesting. I've always had the right value. Not sure where the wrong value came from
"KFDMDADP","0x1de1c","Upper threshold for torque intervention under dashpot","8x6","16 Bit (LoHi)","-","%","%","-","0.001526","0.003052","1.0","1.001056","20.002808","0x290","0x3334"
"KFDMDARO","0x1de7c","Upper threshold for torque intervention","8x6","16 Bit (LoHi)","-","%","%","-","0.001526","0.003052","1.0","1.001056","20.002808","0x290","0x3334"
I got my XDF when NYET posted it and all my locations are right. |
|
|
|
|
Logged
|
|
|
|
|
