Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Remove Software Version Management Error

  1. #1
    Verified VCDS User
    Join Date
    Sep 2019
    Location
    UK
    Posts
    14
    Post Thanks / Like

    Remove Software Version Management Error

    I recently replaced the MIB unit in my 2015 Audi S3 with an MIB2 unit. One of the errors being flagged up is 1555 - Check Software Version Management. I believe this to do with the changes and it's the system wanting a check done for any updates. I tried to follow the process at http://www.audienthusiasts.com/Appli..._SVMError.html but his screenshots are from an older version of VCDS and the adaptions screen for the 5F module is different from what I see on the latest version of VCDS. He has a field to enter a channel number, all I get is a drop down list of items to choose from.

    Is there a guide I can follow that is more relevant to the newer versions of VCDS?

  2. #2
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    25,068
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by sparkymark75 View Post
    Is there a guide I can follow that is more relevant to the newer versions of VCDS?
    This is not something that changed in VCDS, but rather the control modules. See: UDS vs. non-UDS.

    Is it this car?

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  3. #3
    Verified VCDS User golfi_vend's Avatar
    Join Date
    Apr 2014
    Location
    Tartu, Estonia
    Posts
    2,011
    Post Thanks / Like
    Take adaption value:Confirmation of installation change(or similar, typing from head here) and use that value with XOR calculation C9 D2 and insert new value separated with space.
    I am a VW Freak - Le WV Freaks OR Come visit me at my work with ODIS concerns - FORSS ODIS GeKo/FaZit access for VW/AUDI/Škoda
    The world is my oyster...

  4. Likes sparkymark75, DV52, Uwe, PetrolDave, Dana liked this post
  5. #4
    Verified VCDS User
    Join Date
    Sep 2019
    Location
    UK
    Posts
    14
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post
    This is not something that changed in VCDS, but rather the control modules. See: UDS vs. non-UDS.

    Is it this car?

    -Uwe-
    It is that car yes. That scan was from the end of last year before I started tinkering with it.

  6. #5
    Verified VCDS User Spacewalker's Avatar
    Join Date
    Jun 2014
    Location
    Poland
    Posts
    751
    Post Thanks / Like
    One time I got a unit when value:Confirmation of installation change was 00 00
    so o way to calculate XOR

    But i use other device what force that and problem gone
    HOT HOT HOT VW Touran 2005 with ACC HOT HOT HOT

  7. #6
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    sparky: Hi. As golfi_vend says - go to the module @ address hex5F - then go to adaptations - then search for IDE02502-Confirmation of installation change.

    The value for this channel will a 4 x digit hexadecimal number. To clear the error you will need to input this number into an "exclusive or" calculator together with the cypher-key C9 D2.

    If you are not familiar with this process - simply post-up the channel value here and I'm sure that a forum colleague will do the calculation for you (or you could find an on-line calculator - or even better, you could do the calculation manually - it's fun ).

    Once the exclusive-or calculation is done, you simply need to enter the value calculated back into the channel setting

    But I'm more interested in how you managed the Component Protection error that would have resulted from the retro-fit. Was the new MIB unit hacked? Can you post-up a current, unedited copy of the auto-scan for the vehicle -please?

    Don
    Last edited by DV52; 09-11-2019 at 07:21 PM.
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  8. Likes Uwe, PetrolDave, sparkymark75, Dana, jyoung8607 liked this post
  9. #7
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    Quote Originally Posted by Spacewalker View Post
    One time I got a unit when value:Confirmation of installation change was 00 00
    so o way to calculate XOR

    But i use other device what force that and problem gone
    Spacewalker: Interesting situation - I would have thought that if the channel value was hex00 00, the exclusive-or calculation would have given the answer C9 D2 (i.e. the same value as the cypher-key) and that this answer would have worked to clear the SVM error.

    In logic - there is no reason why entering the cypher-key value into the adaptation channel in this situation shouldn't work. Can you remember what value you eventually used?

    Don

    Don
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  10. #8
    Verified VCDS User Spacewalker's Avatar
    Join Date
    Jun 2014
    Location
    Poland
    Posts
    751
    Post Thanks / Like
    yes, very
    anyway - I was try write C9 D2 , failed ...... 00 00 , failed
    then other device made it

    One guy told me that some time when you go to that adaptation show 00 00 , but when you start looking there few more time , it will show new value
    HOT HOT HOT VW Touran 2005 with ACC HOT HOT HOT

  11. Likes DV52, Dana liked this post
  12. #9
    Verified VCDS User
    Join Date
    Sep 2019
    Location
    UK
    Posts
    14
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    sparky: Hi. As golfi_vend says - go to the module @ address hex5F - then go to adaptations - then search for IDE02502-Confirmation of installation change.

    The value for this channel will a 4 x digit hexadecimal number. To clear the error you will need to input this number into an "exclusive or" calculator together with the cypher-key C9 D2.

    If you are not familiar with this process - simply post-up the channel value here and I'm sure that a forum colleague will do the calculation for you (or you could find an on-line calculator - or even better, you could do the calculation manually - it's fun ).

    Once the exclusive-or calculation is done, you simply need to enter the value calculated back into the channel setting

    But I'm more interested in how you managed the Component Protection error that would have resulted from the retro-fit. Was the new MIB unit hacked? Can you post-up a current, unedited copy of the auto-scan for the vehicle -please?

    Don
    Will give this a go on my lunch break at work. If I happen to "calculate" the wrong code and enter it, will it reject it or will it accept it and keep showing the error?

    The MIB2 unit is hacked as I believe that's the only way to get an MIB2 unit in a car that never had it.

  13. #10
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    Quote Originally Posted by sparkymark75 View Post
    If I happen to "calculate" the wrong code and enter it, will it reject it or will it accept it and keep showing the error?
    sparky: it's been a while since I have done this process - and an even longer time since I have entered the wrong number (I like hexadecimal arithmetic - it's much more interesting than boring decimal counting). I'm fairly certain that the adaptation channel will accept any legitimate hex-number that's 4 x digits. But of course if it's the wrong number - the SVM error doesn't clear.

    But my suggestion is - don't miscalculate.

    To confirm the calculation- use the cypher-key as the first number in the X-OR calculator - then do the calculation again and use the cypher-key as the second number. The two answers must be the same!

    Quote Originally Posted by sparkymark75 View Post
    The MIB2 unit is hacked as I believe that's the only way to get an MIB2 unit in a car that never had it.
    hmm...... not really - there's always the official VW process for dealing with CP errors which involves going to a dealer with FAZIT connection facilities back to VW HQ. Probably cost an amount approaching the annual budget of a small African nation - but it is an alternative for the "hack" process



    Don
    Last edited by DV52; 09-12-2019 at 05:16 AM.
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  14. Likes Uwe, downtime liked this post

Posting Permissions

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