I had my car tuned by a local specialist, and the car runs great, but it throws a P17705 on every cold start, and I have to stop and start the engine after it has hit 80 degrees before the tune will work. The guy who did the tune is no longer available, so I am left on my own.

I know about the FVPDKLDUS setting/bug that should be set 5x1=0, and I was wondering if this is as easy as to open the bin file in TunerPro (with a XDF def file) and just edit what I show in the attached picture and save.

I have corrected the checksum with Me7sum, but I don't dare to flash my ECU until I know that I did this the right way.

me7check v1.12 (c) mki, 06/2004-05/2012
Checking file golfmin1.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4013.00//24b/Dst02o/210201//
-> Contents of ECUID data table:
   - '0261207436'         (SSECUHN)
   - '1037362287'         (SSECUSN)
   - '06A906032HJ '       (VAG part number)
   - '0002'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


-> No errors found. File is OK.   *********************

I have attached a picture of LKVDKNMN from my bin file - I am not sure what this do?

Can you explain?

Why do you say that this XDF does not match my Bin file?

Its a XDF for 06A906032HJ, and that is the same ECU as I have.

I was most interested in changing the FVPDKLDUS, and it seems the definition for this is correct:

<XDFTABLE uniqueid="0x0" flags="0x0">
    <title>FVPDKLDUS</title>
    <description>Untere Schwelle f&#252;r Leck vor Drosselklappe Erkennung im Leerlauf bei niedriger t</description>
    <CATEGORYMEM index="0" category="150" />
    <XDFAXIS id="x" uniqueid="0x0">
      <EMBEDDEDDATA mmedaddress="0x1F323" mmedelementsizebits="8" mmedmajorstridebits="8" />
      <units>Grad C</units>
      <indexcount>5</indexcount>
      <embedinfo type="1" />
      <datatype>0</datatype>
      <unittype>0</unittype>
      <DALINK index="0" />
      <MATH equation="0.750000 * X+ -48.000000">
        <VAR id="X" />
      </MATH>
    </XDFAXIS>
    <XDFAXIS id="y" uniqueid="0x0">
      <EMBEDDEDDATA mmedelementsizebits="16" mmedmajorstridebits="-32" />
      <units>-</units>
      <indexcount>1</indexcount>
      <decimalpl>0</decimalpl>
      <outputtype>2</outputtype>
      <datatype>0</datatype>
      <unittype>0</unittype>
      <DALINK index="0" />
      <LABEL index="0" value="" />
      <MATH equation="X">
        <VAR id="X" />
      </MATH>
    </XDFAXIS>
    <XDFAXIS id="z">
      <EMBEDDEDDATA mmedaddress="0x1F328" mmedelementsizebits="8" mmedrowcount="1" mmedcolcount="5" />
      <units>-</units>
      <decimalpl>4</decimalpl>
      <min>0.000000</min>
      <max>255.000000</max>
      <outputtype>1</outputtype>
      <MATH equation="0.007813 * X">
        <VAR id="X" />
      </MATH>
    </XDFAXIS>
  </XDFTABLE>

Axis values from your pictures are totally off.
Lkvdkmn also should be ~400 in stock file
Probably def for 0002 ver and yours 0003 or vice versa

But the question is:

Does this picture look ok, or is this also completely off?

All I want is to change FVPDKLDUS settings in my file to 0. The file is great as it is, but I get a P1705 error on cold start, and this makes me restart the car after it has hit 80 degrees celcius, and I have been doing that for over 5 years, and I want the error code to go away so I dont have to do this anymore.

I was thinking the exact same thing - that the order was not ascending, and this looked off to me.

Looking at the XDf file I see the following:

<EMBEDDEDDATA mmedaddress="0x1F323" mmedelementsizebits="8" mmedmajorstridebits="8" />
<EMBEDDEDDATA mmedaddress="0x1F328" mmedelementsizebits="8" mmedrowcount="1" mmedcolcount="5" />

I am guessing that if I find the correct adresses (0x1F323 --> 0x1F328 is wrong), then it will show the correct 5 settings.

I have checked kfmirl kfzw kfldimx, and they are also way off, and no ascending or descending order at all.

After checking more closely the XDF is off no matter what I look for, so it is not easy to find the correct addresses for FVPDKLDUS. I have tested the XDF against other bin files I have downloaded from this site, and I see that I can find the correct settings right away, but that doesn't help me much.

When I search for kfmirl kfzw kfldimx in my bin file all the settings are off, so the XDF files I have tested does not work with my file.

After trying to fix this for 5 years, I think I will give up. I have nothing to compare to, so it's like looking for a needle in the haystack I have asked every tuning company I know off, but nobody has been able to help, so I guess this was a longshot, but thanks for trying to help

Its funny. 5 minutes after I wrote that I gave up, I downloaded different XDF files, and one of them matched my bin file perfectly. This XDF file is for software 0002, and all the other XDF files I tested was written for software V 0003, and now I can finally make the changes I want.

I found the file on this forum, and this made me very happy. I have restarted my car for years after it has reached 80.25  degrees celius to have the tuning come alive, and now I will test and see if the changes will have any effect on this issue.

I see from other tuned files that FVPDKLDUS and LKVDKNMN are kept at original settings, and does anybody know why some tunes require change of these settings  and others dont?