Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Long Coding Advice for Passat B8 Instruments Control Module 17

  1. #11
    Verified VCDS User
    Join Date
    May 2017
    Location
    Finland
    Posts
    1,823
    Post Thanks / Like
    NETech is right. Byte 5 bit 4 PLA is for PLA2.0 and that needs to be unchecked with PLA3.0.

    PLA3.0 bit is byte 13 bit 0 as NETech wrote.

    So uncheck byte5 BIT 4 and check byte 13 bit 0.

    If you use the experimental coding option it shows you the labels for byte 13 as well. Normal label file does not have the explanation for that byte.

    This is a correct coding for your instrument cluster
    Code:
    27A401186788000801886B0B1001000000000000

  2. #12
    Verified VCDS User
    Join Date
    Mar 2020
    Location
    Australia
    Posts
    16
    Post Thanks / Like
    Quote Originally Posted by NEtech View Post
    Are you 100% sure, that the kufatec dongle changed coding in [17] Byte 5 Bit 4 ?
    Is it kufatec product Item no. 41780-1 you have installed ?
    What manual coding/change with a tester, is explained in kufatec instructions

    Out of 246 Control units I have in Autoscan files with Part Number SW: 3G0 920 7xx, none have this bit active.

    As Dana wrote, I would try to remove Byte 5 Bit 4, then Bus rest etc.
    Is the DTC gone ?

    You can also test coding in [17], Byte 13 Bit 0
    Hi NETech, I am not sure that what the Kufatec dongle changed with the coding, I will go through my backup of coding prior to the dongle being used to try to work that out. I can certainly change the Byte 5 Bit 4 and see if a) the DTC is gone and b) that the Park Assist/Pilot from Kufatec still works and report back. I will have a look at Byte 13 Bit 0.

    Thanks for your input I appreciate it.

    Andrew

  3. #13
    Verified VCDS User
    Join Date
    Mar 2020
    Location
    Australia
    Posts
    16
    Post Thanks / Like
    I have now sent Kufatec at their request my VCDS scan and the Dongle Code KTC File. Hopefully they will be able to confirm what the correct coding is from the dongle and if that needs any further adjustment.

  4. #14
    Verified VCDS User
    Join Date
    Mar 2020
    Location
    Australia
    Posts
    16
    Post Thanks / Like
    Problem solved, Kufatec analysed my scan and their dongle code and concluded the same as advised here the key CHANGE being Byte 13 Bit 0 must be activated.
    Address 17: Instruments (J285) Labels:| 5G0-920-XXX-17.clb-SRI3
    Part No SW: 3G0 920 751 A HW: 3G0 920 751 A
    Component: KOMBI 301 6421
    Coding: 27A401186788000801886B0B1001000000000000
    Shop #: WSC 04174 123 61029
    ASAM Dataset: EV_DashBoardVDDMQBAB 009046
    ROD: EV_DashBoardVDDMQBAB_009_VW37.rod
    VCID: 2313E9B0AB5FE2E36E0-8076

    No fault code found.

  5. #15
    Verified VCDS User
    Join Date
    May 2017
    Location
    Finland
    Posts
    1,823
    Post Thanks / Like
    NEtech and I told you so already. Didn't you see that I posted you a working code earlier and what NEtech wrote?

  6. Likes PetrolDave, Uwe, Fredrick Awuor, jhnbssll liked this post

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •