Pages: 1 ... 5 6 [7] 8 9 10
Author Topic: ARMD - antirukelfunktion and timing oscillations  (Read 107882 times)
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #90 on: July 30, 2012, 05:55:42 AM »

bit positions for

B_ar, Antiruckeleingriff aktiv, FD9C
B_dashv,Bedingung Dashpot verz"gert, FDA0
B_tvars, Bedingung Antiruckelfunktion dynamisch aktiv, FD9E
B_lsd, Bedingung: Pos. Lastschlagd,,mpfung aktiv, FDA2
B_fgr, Bedingung FGR (Tempomat) aktiv, FDA0
B_wk, Bedingung: Wandlerkupplung berbrckt, FD1A
B_argf, Bedingung Gangfenster Antiruckel, FD9C
B_tvarss, Bedingung Antiruckelfunktion station,,r aktiv, FD9E
B_iniar, Bedingung Initialisierung der AR-Funktion, FD9C
B_iniar1, Bedingung Initialisierung ARMD vorl,,ufig, FD9C
B_iniarv, Bedingung Initialisierung der Filterfunktion verz"gert, FD9C
B_kupgw, Bedingung Kupplung bet,,tigt bis erkannter Gangwechsel, FD9E
B_kuppl, Bedingung Kupplung bet,,tigt, FD56

and dmarv_w

also, not sure about the scaling for all of the 16 bit values, particularly dmar, ndar and fdar

enclosed is my full list that i am using above the stock ME7 ones.


I am almost done getting through ARMD. By far the most pain in the ass function I've worked on so far. I'll post up the entire function in *.ecu format within the next few days.

dmarv_w is not available for logging. It gets written to r6 only.
Logged
ibizacupra
Full Member
***

Karma: +4/-10
Offline Offline

Posts: 111


« Reply #91 on: August 01, 2012, 04:57:33 AM »

Success. I copied KIFZGHG, KFDMDADP, and KFDMDARO from F-box rs4.

No more ARMD intervention

What are these KIFZGHG, KFDMDADP, and KFDMDARO doing?

axis 1 to 6 and -4 to 50% on a 1.8t file I am looking at here..

Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #92 on: August 02, 2012, 12:54:47 PM »

The attached files contain all variables available for logging from functions MDZW, MDKOG, and ARMD.

These were created entirely by hand and only tested briefly at idle. Everything should be accurate, but post any errors that you may find. Some of the variables are undocumented, so I attempted to assign descriptive labels, but what makes sense to me may not make sense to anyone else. I am posting this without further testing first because I will not be available this weekend, but post any questions you have and I will try to answer them ASAP.

Note: You will need to either add these definitions to your *.ecu and *.cng or add the headings to the attached files. Also, as attached, all variables are commented out in the torque.cng file.

Edit: These files were created based on the M box.
« Last Edit: August 02, 2012, 01:03:44 PM by phila_dot » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12255


WWW
« Reply #93 on: August 02, 2012, 01:08:26 PM »

Phenomenal work! Thank you!

btw k and q box is next Smiley
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #94 on: August 02, 2012, 02:09:31 PM »

I just remembered, in an effort to determine the factor for dmrkh, I added dmrkh_w (known factor) and set both factors to 1. Next time I get on my computer, I will calculate it and correct the file I posted.
Logged
jibberjive
Hero Member
*****

Karma: +23/-2
Offline Offline

Posts: 536


« Reply #95 on: August 04, 2012, 03:23:51 PM »

Phenomenal work! Thank you!

btw k and q box is next Smiley
2nd!
Logged
masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #96 on: October 11, 2012, 04:59:33 PM »

The attached files contain all variables available for logging from functions MDZW, MDKOG, and ARMD.

These were created entirely by hand and only tested briefly at idle. Everything should be accurate, but post any errors that you may find. Some of the variables are undocumented, so I attempted to assign descriptive labels, but what makes sense to me may not make sense to anyone else. I am posting this without further testing first because I will not be available this weekend, but post any questions you have and I will try to answer them ASAP.

Note: You will need to either add these definitions to your *.ecu and *.cng or add the headings to the attached files. Also, as attached, all variables are commented out in the torque.cng file.

Edit: These files were created based on the M box.

wow... it would be so cool if setzi would update me7logger to autofind these on every bin...

Anyway, I don't know if someone said this already, but best way to disable ARMD function is by never letting it to start (B_ar = 0). Easiest way to do this is by setting TMAR = FF. I would recommend adding this to the wiki...

More info in armd-frgar subfunction Wink
Logged

nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12255


WWW
« Reply #97 on: October 12, 2012, 09:39:39 AM »

Disagree. I think the best way is to leave it intact except for full torque request line..

But we can agree to disagree Smiley

I'm not sure I want to make a recommendation. I dislike completely disabling functions unless there is no alternative..
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
bk56190
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 91


« Reply #98 on: May 20, 2013, 02:48:52 AM »

Hello,

I tried to disable ARMD intervention by setting the last row of KFDMDARO to 50 but no success :



 

Now, I'll copy KFDMDARO & KIFZGHG maps from TT 225 file on my TT 180 bin and log again...
« Last Edit: May 20, 2013, 02:56:41 AM by bk56190 » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12255


WWW
« Reply #99 on: May 20, 2013, 09:35:23 AM »

That doesn't look like ARMD intervention.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
s5fourdoor
Hero Member
*****

Karma: +33/-3
Offline Offline

Posts: 617


« Reply #100 on: May 20, 2013, 09:46:19 AM »

This is what Nye had on his Chinese K04 binary:
Logged
bk56190
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 91


« Reply #101 on: May 20, 2013, 10:45:02 AM »

That doesn't look like ARMD intervention.
So, what do you think about ?

On dyno (4th gear), I haven't these oscillations :


This is what Nye had on his Chinese K04 binary:

Thank you nehalem, I'll try these values if no success with TT 225 values.

 

Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12255


WWW
« Reply #102 on: May 20, 2013, 11:18:25 AM »

Guys, please log the appropriate ARMD variables before making arbitrary changes...

here are my addons to ME7L (mbox)

https://raw.github.com/nyetwurk/ME7L/master/ecus/extras.ecu

torque monitoring (from phila?)

https://raw.github.com/nyetwurk/ME7L/master/ecus/torque.ecu

Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704


« Reply #103 on: May 21, 2013, 12:48:16 AM »

They are very likely not oscillations, but the result of different cylinders being sent to zwout. 
Logged
prj
Hero Member
*****

Karma: +1067/-476
Offline Offline

Posts: 6004


« Reply #104 on: May 21, 2013, 12:50:48 AM »

Exactly, log zwsol/zwist/zwbas before concluding that there is intervention.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: 1 ... 5 6 [7] 8 9 10
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.026 seconds with 18 queries. (Pretty URLs adds 0s, 0q)