Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: 2017 NMS Passat with Byte 18 problem

  1. #21
    Verified VCDS User
    Join Date
    Feb 2019
    Location
    Iraq
    Posts
    16
    Post Thanks / Like
    if the code of byte 18 is masked behind 00 so how can I know the original code ???
    also should I reflash the controller or not ?

  2. #22
    Verified VCDS User TBAx's Avatar
    Join Date
    Dec 2016
    Location
    DE
    Posts
    585
    Post Thanks / Like
    You simply can't. The EEPROM parameters masked by 00 are overwritten as soon, as you change the value there to something else. Reflashing to another version would not help, as this does not affect this specific part of the EEPROM.

  3. Likes Uwe liked this post
  4. #23
    Verified VCDS User PetrolDave's Avatar
    Join Date
    Dec 2014
    Location
    South Molton, UK
    Posts
    3,192
    Post Thanks / Like
    Quote Originally Posted by Bakhtiyar View Post
    if the code of byte 18 is masked behind 00 so how can I know the original code ???
    The simple rule is that if byte 18 is 00 then modifying byte 18 is a seriously bad idea - because you don't know what the hidden code is, which means you can't go back to it.

  5. Likes Uwe liked this post
  6. #24
    Verified VCDS User
    Join Date
    Feb 2019
    Location
    Iraq
    Posts
    16
    Post Thanks / Like
    Hi Ms Dana

    Could you please give an advice for Byte 18 as I sent it to you before and how can I change to its original code ?

    thanks

  7. #25
    Ross-Tech Employee Dana's Avatar
    Join Date
    Jan 2014
    Location
    United States
    Posts
    4,086
    Post Thanks / Like
    Hello,

    Per your PM, providing it was in reference to to this car, my only suggestion would have been Long Coding Helper option:

    A0,Lighting: VW Passat (A3/NMS/VW411) North American Region (NAR)

    The other NMS options are China (CHN) so I'm not very confident they would work for your car but you may want to try them since A0 didn't help. If you don't receive any other suggestions here I suppose it couldn't hurt to try nearby options such as A1, A2, etc.

  8. Likes Uwe liked this post
  9. #26
    Verified VCDS User
    Join Date
    Dec 2016
    Location
    Amsterdam
    Posts
    532
    Post Thanks / Like
    Quote Originally Posted by PetrolDave View Post
    The simple rule is that if byte 18 is 00 then modifying byte 18 is a seriously bad idea - because you don't know what the hidden code is, which means you can't go back to it.
    As far as I know, if the value is 00 it means the light configuration is 'custom', as in: its not one of the preset configurations. Changing it to a preset still changes the light configuration only you cannot go back by changing bytes alone.
    Current:
    2018 Tiguan AD Highline 2.0 BiTDI 240hp > Stage 1+ 328hp
    2016 Polo 6C Highline 1.0 TSI 105hp

  10. #27
    Ross-Tech Employee Dana's Avatar
    Join Date
    Jan 2014
    Location
    United States
    Posts
    4,086
    Post Thanks / Like
    Hi Tommy,

    The vast majority that are masked by 00's can be resolved by entering the proper value (providing that value is known) to restore all lighting. In this case I don't know what his would be. This car is very similar to a NAR NMS but that coding didn't work.

    There however were some RoW market models where pre-ODIS required a GFF parameter test plan and current day ODIS does something similar because there wasn't an actual coding value (between HEX 01 and FF) that would fix them. If memory serves those were the late production 2009 (technically MY 2010) Skoda Octavias with PQ35 BCMs and that type would fall into your custom explanation if someone tinkered with it.

  11. Likes Uwe liked this post
  12. #28
    Verified VCDS User
    Join Date
    Dec 2016
    Location
    Amsterdam
    Posts
    532
    Post Thanks / Like
    Quote Originally Posted by Dana View Post
    Hi Tommy,

    The vast majority that are masked by 00's can be resolved by entering the proper value (providing that value is known) to restore all lighting. In this case I don't know what his would be. This car is very similar to a NAR NMS but that coding didn't work.

    There however were some RoW market models where pre-ODIS required a GFF parameter test plan and current day ODIS does something similar because there wasn't an actual coding value (between HEX 01 and FF) that would fix them. If memory serves those were the late production 2009 (technically MY 2010) Skoda Octavias with PQ35 BCMs and that type would fall into your custom explanation if someone tinkered with it.
    Learned something new, thanks for the explaination!
    Current:
    2018 Tiguan AD Highline 2.0 BiTDI 240hp > Stage 1+ 328hp
    2016 Polo 6C Highline 1.0 TSI 105hp

Posting Permissions

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