Pages: [1] 2
Author Topic: LDRXN and LDRXNZK  (Read 22158 times)
e_pacman
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 38


« on: February 14, 2012, 10:16:47 AM »

Hi!
I think I have found these two tables in the software for my Seat Leon 1.8T Sport 2003, AUQ engine. They have a similar shape, but one has slightly higher values then the other.

What I'm looking for is basically for someone to confirm that I'm on the right track here, and if I am, maybe tell me which table is which. RPM axis can be found in the attached screenshot. My guess is that axis values should be devided by 4, which will render values between 1000 and 6520.

table1:
90   108.00   111.52   117.00   125.02   131.02   136.01   133.01   126.00   129.00   128.02   132.00   136.50   138.00   130.01   122.02


table2:
90.00      108.00   111.52   117.00   123.00   127.01   131.02   127.01   124.01   126.00   127.01   130.01   133.01   135.00   128.02   120.00
« Last Edit: February 14, 2012, 10:24:31 AM by e_pacman » Logged
masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #1 on: February 14, 2012, 10:42:17 AM »

I'd say first one is LDRXN and the second one LDRXNZK
Logged

e_pacman
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 38


« Reply #2 on: February 15, 2012, 12:22:36 AM »

Thanks! That's what I think as well. Then the XDF file I started from probably had them mixed up.
Logged
e_pacman
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 38


« Reply #3 on: February 16, 2012, 09:19:41 AM »

Just some more info for now: After doing some logging, I noticed that the requested load during a third gear, full throttle pull seems to follow the shape of the second table.
Logged
masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #4 on: February 16, 2012, 10:19:37 AM »

Just some more info for now: After doing some logging, I noticed that the requested load during a third gear, full throttle pull seems to follow the shape of the second table.

look at your knocks, if there are knocks encountered then it will follow LDRXNZK
Logged

e_pacman
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 38


« Reply #5 on: February 17, 2012, 12:11:35 AM »

Right, I'll try to remember to log those. I did however find an intrseting comment in another thread:

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.


So maybe the lower map actually is LDRXN.
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704


« Reply #6 on: February 26, 2012, 02:10:23 AM »

LDRXN is always the first map in the file
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #7 on: August 02, 2012, 01:02:57 PM »

I have discovered that firmware from 06A906032HS (VW Jetta AWP 180HP engine) has LDRXN > LDRXNZK. Other 1.8T firmwares like 06A906032HN (from AUQ 180HP) or even 8N0906018CB (from BAM 225 PS)  have LDRXN < LDRXNZK.

From 06A906032HS SW0006-0008:
LDRXN Maximalfuellung LDR (16x1)
(Motordrehzahl)/%
      U/min                                             
      1000.000   1480.000   1600.000   1720.000   1840.000   1920.000   2000.000   2520.000   3000.000   3520.000   4000.000   4520.000   5000.000   5520.000   6000.000   6520.000
-   0   90.0000   108.0000   111.5156   117.0000   125.0156   131.0156   136.0078   133.0078   126.0000   129.0000   128.0156   132.0000   136.5000   138.0000   130.0078   122.0156

LDRXNZK Maximalfuellung LDR bei Dauerklopfen (16x1)
(Motordrehzahl)/%

      U/min                                             
      1000.000   1480.000   1600.000   1720.000   1840.000   1920.000   2000.000   2520.000   3000.000   3520.000   4000.000   4520.000   5000.000   5520.000   6000.000   6520.000
-   0   90.0000   108.0000   111.5156   117.0000   125.0156   126.0000   128.0156   130.0078   124.7578   128.0156   127.0078   131.0156   137.0156   137.0156   126.0000   116.0156


Since in HS they have SW up to 0008 while on HN there is only SW 0002, maybe that was really bug and in VW they have found and fixed it in latest versions? Or maybe they swapped addresses of LDRXN and LDRXNZK? In any case please who can explain, what sense does it make to lower boost in normal situations (LDRXN) and increase it when it knocks?
« Last Edit: August 02, 2012, 01:08:12 PM by automan001 » Logged
userpike
Hero Member
*****

Karma: +22/-1
Offline Offline

Posts: 763


« Reply #8 on: August 02, 2012, 01:48:15 PM »

I have the HS with SW0007. What .xdf or .kp are you using for yours? Will you upload it please? The ones I have I'm not so sure is for SW 0007. Thanks!
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #9 on: August 31, 2012, 06:05:29 AM »

I have discovered that firmware from 06A906032HS (VW Jetta AWP 180HP engine) has LDRXN > LDRXNZK. Other 1.8T firmwares like 06A906032HN (from AUQ 180HP) or even 8N0906018CB (from BAM 225 PS)  have LDRXN < LDRXNZK.
Even more, AWP_HS.LDRXN=AUQ_HN.LDRXNZK=AUQ_SJ.LDRXNZK
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #10 on: June 19, 2013, 12:46:24 AM »

I have the HS with SW0007. What .xdf or .kp are you using for yours? Will you upload it please? The ones I have I'm not so sure is for SW 0007. Thanks!
Following equation is true for 1.8T map definitions:
AUQ HN1 = AWP HS6[7,8] = ARX HJ2
AUQ HN2 = ARX HJ3
So, if you need a definition for HS7, then just open HS7 binary and import HN1 maps pack. Or another way, vice versa, open HN1 binary with maps defined and then import your HS7 binary as new version. There are many definitions for HN1, for example in this thread http://nefariousmotorsports.com/forum/index.php?topic=576.15
Logged
userpike
Hero Member
*****

Karma: +22/-1
Offline Offline

Posts: 763


« Reply #11 on: June 19, 2013, 09:37:14 AM »

Following equation is true for 1.8T map definitions:
AUQ HN1 = AWP HS6[7,8] = ARX HJ2
AUQ HN2 = ARX HJ3
So, if you need a definition for HS7, then just open HS7 binary and import HN1 maps pack. Or another way, vice versa, open HN1 binary with maps defined and then import your HS7 binary as new version. There are many definitions for HN1, for example in this thread http://nefariousmotorsports.com/forum/index.php?topic=576.15

I have a fully defined HN .kp file I have been pulling maps off of and putting into an HS specific .kp file. Not all the maps line up but some are at different offsets. I have located the maps used for VVT in our engines and a lot others. I haven't made translations yet fully but I work on it in my spare time.
Argdubs .KP I believe only has maps that match the locations in the HN/HS/etc...for instance the VVT maps I found in my HS are at a different offset(164) than the HN but the basic load maps are @ the same addresses along with everything in Argdub's .kp. if you would like a copy lemme know. I will eventually post it up in the definition section but not till its finished I think.
Logged
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #12 on: June 20, 2013, 08:22:05 AM »

Hi Guys,

Did someone find out why LDRXNZK is less then LDRXN in stock many bin files?
Logged
vdubnation
Turboman
Global Moderator
Sr. Member
*****

Karma: +49/-2
Offline Offline

Posts: 433


« Reply #13 on: June 20, 2013, 08:26:53 AM »

Hi Guys,

Did someone find out why LDRXNZK is less then LDRXN in stock many bin files?

Its basically like a safety how much boost your going to run if knock occurs typically 15% lower than LDRXN alot of guys do 99 across the line.
Logged
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #14 on: June 20, 2013, 09:07:06 AM »

Its basically like a safety how much boost your going to run if knock occurs typically 15% lower than LDRXN alot of guys do 99 across the line.
But in most stock bin files LDRXN equally or less then LDRXNZK. it's the main question - why?
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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