Pages: 1 [2]
Author Topic: LDRXN vs LDRXNZK sanity check  (Read 20342 times)
TTQS
Guest
« Reply #15 on: September 17, 2011, 11:28:04 AM »

I laugh at people that try to save money by using low octane gas. Modern torque based engine management will just use more fuel to try to give the driver the same "feel".

I can laugh too now, but I had to do the logging runs to convince myself that there was a substantial drop in output under WOT with lower octane fuel... A lot bigger than I was expecting. I dropped to standard octane for a while because, sadly, 95% of my driving is steady cruise.  Sad

Good discussion, but I'm still seeking that elusive answer as to why LDRXNZK is higher, not lower, in the 1.8T variants I've studied.

Doug
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #16 on: September 17, 2011, 11:29:52 AM »

Err. I thought giannis explained it perfectly.
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
TTQS
Guest
« Reply #17 on: September 17, 2011, 11:58:03 AM »

O.k., so the answer is that the knock control retards timing to deal with knock on the crank synchronous pathway as fredrik explains, but more boost is allowed to mitigate the loss of power by sparking later than would otherwise be required for peak cylinder pressure as Giannis suggests...

If that's the correct then I'm a happy man! Grin

If that's correct, why does the dumbass funktionsrahmen specify that LDRXNZK should be 15% lower than LDRXN?

Doug
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #18 on: September 17, 2011, 04:43:53 PM »

If that's correct, why does the dumbass funktionsrahmen specify that LDRXNZK should be 15% lower than LDRXN?

LOL. Good point. No clue.
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
rob.mwpropane
Sr. Member
****

Karma: +32/-0
Offline Offline

Posts: 370


WWW
« Reply #19 on: September 17, 2011, 10:15:07 PM »

Just a thought; I've had my cars software updated twice by Audi. This was well before I knew shit about "tunes", "chips", logging etc (some may argue that I still don't). If they were in fact updating it, I could only assume it was to run more efficiently than before. If this was the case, maybe they found a more efficient way to manipulate the maps? Again, just a theory....and in my defense I'm falling asleep at the keyboard, so this may read like nonsense in the am. Roll Eyes
Logged

This has nothing to do with cars but you can see my glorifying job at,

www.MWPropane.com
fredrik_a
Full Member
***

Karma: +25/-0
Offline Offline

Posts: 221


« Reply #20 on: September 18, 2011, 01:20:01 AM »

...

EDIT: I missed that the question for LDRXNZK being higher than LDRXN was already answered. It is indeed (at least for other EMS) to prevent that the driver feels an obvious loss of power.
« Last Edit: September 18, 2011, 01:26:25 AM by fredrik_a » Logged
TTQS
Guest
« Reply #21 on: September 18, 2011, 01:52:23 AM »

O.k., that's good enough for me. I've revised the 1.8T guide to read:

"Remarks for LDRXNZK: It is noted in module LDRLMX 3.100 that the values should be set about 15% lower than LDRXN which would be reasonable from an intuitive understanding; i.e. overall ignition advance is reduced during knock so maximum allowable cylinder charge should also be reduced. However, in these examples, the values in LDRXNZK are actually higher from around 2,300 to between 5,000 and 5,500 rpm. The only plausible explanation is that a slightly larger cylinder charge is allowed to counteract the sub-optimal peak cylinder pressure and consequential loss of torque that would result from sub-optimal ignition timing due to knock. Otherwise, the driver would feel a noticeable step-change in power during the onset of knock. If in doubt, don’t try to second-guess the OEM calibrator; follow the advice in the funktionsrahmen and set the values in LDRXNZK a bit lower than LDRXN."

Thanks guys.

One issue I had which I failed to mention in the original post was that if there was to be a 15% or so difference between the maps with no other power-loss compensation, then the driver would feel a noticeable step-change in power every time continuous knock was encountered. That didn't seem correct and which, in part, caused my confusion.

Doug
« Last Edit: September 18, 2011, 01:57:44 AM by TTQS » Logged
Giannis
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 176


« Reply #22 on: September 18, 2011, 08:52:48 AM »

Sorry for the off topic but can i ask something?when we say continious knock what does it mean? For how much time knocking must exist for to be considered by the ecu as continious?
Logged
e_pacman
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 38


« Reply #23 on: February 17, 2012, 12:10:00 AM »

In the 180 ps AUQ file LDRXN is lower everywhere than LDRXNZK. Mayby because of the power loss of ignition retarding during knock activity it has more boost to regain that loss and the driver can't feel the difference in power.

I just made the same discovery on my AUQ engine. Thought I had the tables mixed up at first, but when I log the requested engine load it clearly follows the shape of the lower one (LDRXN), and this was during cold conditions with 98 octane fuel.

Link to my thread for reference:
http://nefariousmotorsports.com/forum/index.php?topic=1534.msg14573#msg14573
« Last Edit: February 17, 2012, 12:13:37 AM by e_pacman » Logged
Pages: 1 [2]
  Print  
 
Jump to:  

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