Easy way to clear SVM trouble code from MIB or Discover mul

[peter3man]

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

[dv52 (Australia)]

Jan 6, 2017 15:29:24 GMT peter3man said:

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

Peter: Hi. I'm guessing from your question that decryption algorithms are not something that you have used in the past - apology if I have misunderstood!

So, just as an introductory explanation, the XOR operator is a very rudimentary decryption tool that compares the binary string of two numbers. In the XOR process,  there are two "Input" numbers and an "Output" number (all "numbers" are in hexadecimal notation). The logical operator for the XOR process is what mathematicians call an "Exclusive OR", which means when the value of each Bit in the binary number for the two Inputs are the same, the XOR output is 0, otherwise the output of the XOR is 1. Yes, all very confusing, I agree - but here's an easy example that I hope helps to explain the XOR process:

Input 1 = HexD (or binary 1101)
Input 2 = HexB (or binary 1011)

If you look at the 2 x binary numbers and then you compare each of the Bits (by position), you can see that the values for the right-most-Bits and the left-most-Bits are the same (i.e. 1). All the other values in the Bit position are different for each number. Hence, if you apply the XOR algorithm to these numbers, you get the "Output" = 0110 ( or Hex6). It's that easy!!

The example is for Inputs with just one hex digit, but clearly the SVM algorithm uses Inputs with four hex digits -so, the XOR process is simply repeated four times!

I've not cleared SVM errors in the past, but I'm guessing that the instructions that you refer-to have given you the decryption key = 51666 in decimal (i.e. one of the "input" numbers for the XOR process). If you look at the example that you have quoted from the instructions:
 
i.e. 410a XOR C9D2 = 88d8

and you convert the encryption key 5166 to hexadecimal, you get hex C9D2!

So, I think that the instructions are telling you to use your current code 6AFD as "Input 1" and C9D2 (which is hexadecimal equivalent of 51666 in decimal) as "Input 2" and then apply the XOR conversion process - which should give you an Output = A32F ( see my calculations in the table below)

You can confirm my calculations by entering the values in the XOR converter HERE - or, if you are a nerd (like me- and proud of it!), you can do the conversion manually as per my table below, which is much more interesting (IMO)

Don

 

[peter3man]

Hi Don,

Thank you for the expectation, I think i am a bigger nerd than you anyway. HAHA.
I understand now what its means. Your calculation is right it works the fault code is gone. Thank you.
Only one question, have you ever see this on a Dicovery pro mib 1. It starded whit no navigate voice after a reset voice is back, but i have 4 collard arrows.
Maybe you now a solution. Hope to hear from you.
Nice day.
Peter 3man

Attachments:

[dv52 (Australia)]

Peter: great to hear that the error has cleared (and that you are a bigger nerd than me - difficult to believe!)

No - I have never seen the multiple arrows on a MIB SATNAV. It seems that the car doesn't know what direction it is traveling! Does the compass read correctly (i.e. North/East/South/West direction)? Have you tried resetting the MIB (i.e. hold down the OFF/ON button for more than 10 seconds)?

Don

[peter3man]

Hi Don,

I think that i am a bigger nerd than you believe me. I read all the stuff on this board. And i amazes me that you now so much about it.

Yes i have tried several times to reset the mib and every time it come's back.
It a quest for 3 months now for me. Aldo the strange thing about it is that voice an navigation works well. voice is right on time every time.
Is it something you can reset in the green Menu or is it in the canbus system.
I have 1 error in the canbus system witch not found out yet, See below.

Anyway thanks for al the good work on this board and you fast reply.

Greetzz from Amsterdam.
Peter 3man


VIN: WVWZZZAUZEW130472
Auto: Volkswagen Golf
Jaar: 2014
Motor: CJZA
Kilometerstand: 171057 KM

---------------------------------------------------------------
19 Diagnose-interface voor databus

Systeem omschrijving: GW MQB Mid
Software nummer: 5Q0907530L
Software versie: 1144
Hardware nummer: 5Q0907530E
Hardware versie: 124
Serienummer: 0000978812
ODX naam: EV_GatewLear
ODX versie: 009013
Long coding: 030100042B086400EF00064C080F00010001000000000000000000000000

Subsystemen:
Systeem omschrijving: J367-BDMHella
Software versie: 8042
Hardware versie: H03
Serienummer: 5742981303

Systeem omschrijving: E221__MFL-DC1
Software versie: 0038
Hardware versie: H15
Serienummer: 27130001448080013363
Long coding: 28FFFF

Fout codes:
U112600 - niet gedefinieerd regelapparaat Geen communicatie
permanent
Verleerteller: 153
Onbekende omgevingsgegevens:
Contact 15: aan
Voedingsspanning contact 30: 11.8 V
Prioriteit: 2
Date: 2016-12-12 11:00:28
Mileage: 170315 km
teller storingfrequentie: 1

[dv52 (Australia)]

Peter: My Dutch language skills are not good, but your Trouble code is U112600 - undefined control unit No communication. This suggests that the Gateway is expecting a control module that hasn't been included in the Gateway list. Other than the software update to the MIB, what other changes have you made to the car?


Don

[peter3man]

Hi Don - King of the VW


Thank you for helping me, And if you dont speak dutch a speak englisch. HAHah. Anyway Melborne is a long way from Amsterdam.



i bought this car in September 2016 and play a little whit the obdeleven tool. I think that i have made a change to something. I dont no what.

I have learn from that and now i write everything down on paper and check the obd history when a change something.

This i the only thing i can resolve.

Anyway hear from you.



Peter 3man



Below are the errors canbus 19





Long coding

Module: 19 Diagnose-interface for databus

Waardes:

EM_Ref_Spannungsmessung_Inaktiv:

Old value : YES

New value: No

Kilometerstand: 167113 km

Datum: 2016-09-21 13:15









Basis instellingen

Module: 19 Diagnose-interface voor databus

Naam: Restoring customizations of WakeUp-Monitor

Status:

Basisafstelling stopped

not active

Kilometerstand: 167195 km

Datum: 2016-09-22 13:18







Aanpassingen

Module: 19 Diagnose-interface voor databus

Naam: GW_Enable_CAN_Timeout_DTC

Waardes:

Actuator voor motor noise:

Old Value: Active

New value: Not active

Kilometerstand: 167195 km

Datum: 2016-09-22 13:54





Long coding

Module: 19 Diagnosis interface for data bus

Old Value:

030100002B086400EF00064C080F00010001000000000000000000000000

New value:

030100042B086400EF00064C080F00010001000000000000000000000000

Kilometerstand: 167353 km

Datum: 2016-09-26 10:21



I dont no how to change it whit OBDeleven





Aanpassingen

Module: 19 Diagnosis interface for data bus

Naam: List of built-in parts prescribed built-in

Waardes:

Media Player 1:

Old value: code

New Value: Note code

Kilometerstand: 167494 km

Datum: 2016-09-27 14:53



---------------------------------------------------------------

Aanpassingen

Module: 19 Diagnose-interface voor databus

Naam:List of built-in parts prescribed built-in

Media Player 1:

Oude waarde: not coded

Nieuwe waarde: code

Kilometerstand: 167400 km

Datum: 2016-09-26 15:35

[dv52 (Australia)]

^^^ Peter: Why did you change GW_Enable_CAN_Timeout_DTC ?

The code-string for the Gateway before and after the changes that you made are shown below:



The alteration was to change Byte 3, Bit 2. In doing this, you have disabled the Start Stop recuperation function on the Gateway. Why was this done?
Don

[peter3man]

Hi Don, il think that i have tested of it works. And than put it back.
I did this with the OBDeleven app. i put out and on.

 The code error is U112600 - not defined controller no communication (131692) this code is behind U112600. Mayby it make more sense of the eror


How can i code it back with a obdeleven device?


Peter 3man

[peter3man]

Hi Don,
 I cleared all the DTC's.  And so as you suggested i printed the history out, and search what i did wrong. I Cleared the multiple arrows from the MIB green menu. it was a wrong setting.

The U112600 trouble code, i search for 4 days. But i found out that i had added in the gateway menu the navigation button/program. In this navigation button/program you can never chance any thing.
i turned this on to get ride of the multiple arrows.
I did this with the OBDeleven app. So i removed this menu and yes the problem with U112600 is gone. i tested it again and turn the program on an the error code turned up.
So i understand now where the error came from. luckily i solved a the errors.

I will thank you for your reply's.
Greeetzzz 
Peter 3man

[mdnav]

Hi!

I have recently bought the OBDeleven tool as I run a large retrofit store in Norway and think it is a much more handy tool than PC and VCDS. I have come across the SVM issue sometimes when updating SW or retrofitting MMI modules, but in these cases I have used the calculator from audienthusiast www.audienthusiasts.com/Application_SVMError.html but the MIB and MIBII platforms seems to have a different math behind the stored value in controller 5F, adaption: "Confirmation Of Installation Change" and how to calculate the new value.

I have read this thread a thousand times and tried to wrap my head around the math behind calculating the new value, but unfortunately I am a complete math noob and dont get this at all.

I have retrofitted a MIBII Main Unit in Audi Q7 4M and need to calculate new value to clear this error. Stored value is 441E


Can you guys please help me figure out what the new value would be and try and explain the math in simple ways and how to use the calculator for future similar issues:-)

Thanx!

Morgan Brorson Dahl - MDNAV

Jan 7, 2017 0:13:19 GMT dv52 (Australia) said:

Jan 6, 2017 15:29:24 GMT peter3man said:

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

Peter: Hi. I'm guessing from your question that decryption algorithms are not something that you have used in the past - apology if I have misunderstood!

So, just as an introductory explanation, the XOR operator is a very rudimentary decryption tool that compares the binary string of two numbers. In the XOR process,  there are two "Input" numbers and an "Output" number (all "numbers" are in hexadecimal notation). The logical operator for the XOR process is what mathematicians call an "Exclusive OR", which means when the value of each Bit in the binary number for the two Inputs are the same, the XOR output is 0, otherwise the output of the XOR is 1. Yes, all very confusing, I agree - but here's an easy example that I hope helps to explain the XOR process:

Input 1 = HexD (or binary 1101)
Input 2 = HexB (or binary 1011)

If you look at the 2 x binary numbers and then you compare each of the Bits (by position), you can see that the values for the right-most-Bits and the left-most-Bits are the same (i.e. 1). All the other values in the Bit position are different for each number. Hence, if you apply the XOR algorithm to these numbers, you get the "Output" = 0110 ( or Hex6). It's that easy!!

The example is for Inputs with just one hex digit, but clearly the SVM algorithm uses Inputs with four hex digits -so, the XOR process is simply repeated four times!

I've not cleared SVM errors in the past, but I'm guessing that the instructions that you refer-to have given you the decryption key = 51666 in decimal (i.e. one of the "input" numbers for the XOR process). If you look at the example that you have quoted from the instructions:
 
i.e. 410a XOR C9D2 = 88d8

and you convert the encryption key 5166 to hexadecimal, you get hex C9D2!

So, I think that the instructions are telling you to use your current code 6AFD as "Input 1" and C9D2 (which is hexadecimal equivalent of 51666 in decimal) as "Input 2" and then apply the XOR conversion process - which should give you an Output = A32F ( see my calculations in the table below)

You can confirm my calculations by entering the values in the XOR converter HERE - or, if you are a nerd (like me- and proud of it!), you can do the conversion manually as per my table below, which is much more interesting (IMO)

Don

 

[dv52 (Australia)]

Feb 20, 2017 0:49:58 GMT mdnav said:

Hi!

I have recently bought the OBDeleven tool as I run a large retrofit store in Norway and think it is a much more handy tool than PC and VCDS. I have come across the SVM issue sometimes when updating SW or retrofitting MMI modules, but in these cases I have used the calculator from audienthusiast www.audienthusiasts.com/Application_SVMError.html but the MIB and MIBII platforms seems to have a different math behind the stored value in controller 5F, adaption: "Confirmation Of Installation Change" and how to calculate the new value.

I have read this thread a thousand times and tried to wrap my head around the math behind calculating the new value, but unfortunately I am a complete math noob and dont get this at all.

I have retrofitted a MIBII Main Unit in Audi Q7 4M and need to calculate new value to clear this error. Stored value is 441E


Can you guys please help me figure out what the new value would be and try and explain the math in simple ways and how to use the calculator for future similar issues:-)

Thanx!

Morgan Brorson Dahl - MDNAV

Morgan: Hi and welcome to the wonderful world of numbers!!!

Short summary: Your process for the Audi is exactly the same as that of Peter's and if the link that you posted applies to your car (and I will explain later why it may not) the cypher on your Audi even has the same decryption key!

Longer answer: First I have to introduce the concept of a "base "(short for number base) because your Audi uses three of these.

Binary: this numbering system has a base 2, which means that there are 2 x numbers used - 0, 1

Decimal: this is the numbering system that you are familiar with and it has a base 10, which means that there are ten numbers used - 0, 1, 3.....9

Hexadecimal: this numbering system has a base 16, which means that there are sixteen "characters" used - 0, 1, 2 .....9, A, B, C.....F

Any number can be represented as a value in any of these 3 x numbering systems and it's possible to convert numbers into another system. For example Decimal 10 = Hexadecimal A = Binary 1010

So,. now that I have introduced these 3 x numbering system, let's look at the numbers for your project - there are three pertinent numbers as follows:

Decryption key: In my reply to Peter, I referred to the decryption key C9D2. Clearly this is not a decimal number, nor is it a binary number because it contains alphabetic characters - C9D2 is a hexadecimal number (base 16). The web contains numerous converters that will translate any number to any other number base, but:

 HexC9D2=Decimal 51,666 = Binary 1100100111010010 

Your Audi: Your screenshot and your post contains the number 441E. Again, it's obvious that this is not a decimal, or binary number (it contains alpha characters) - 441E is a hexadecimal number (base 16) and:

 Hex441E= decimal 17,438 = binary 0100010000011110

Audi webpage: The webpage in your link uses the number from the VCDS screen 24069. This is clearly a decimal number (it doesn't contain any alpha characters, so it's not hex and it contains numbers other than 0 & 1, so it isn't Binary):

 Decimal 24,069 = Hex5e05 = binary 0101111000000101

So, lets look at these numbers together in the same format (I've highlighted the number system that was originally identified in the source material and I've separated the numbers in your Audi into its own table to demonstrate how the decryption process is applied):

	Decimal	Hexadecimal	Binary
Your Audi.......	17,438	441E	0100010000011110

	Decimal	Hexadecimal	Binary
Decryption key	51,666	C9D2	1100100111010010
Audi webpage	24,069	5e05	0101111000000101
Xor	38,871	97d7	1001011111010111

In the last row of the second table, I've manually applied the mathematical function Xor in the Binary column. It's not difficult - just compare each digit from both binary numbers - if the two digits are the same, the Xor value is 0, if the two digits are different, the Xor value is 1. For example the left-most digits for the two numbers are different, therefore the left-most Xor digit is 1 - then repeat this same process with the other digits! Also in the last row, I've translated the Binary number into Decimal and Hexadecimal as shown

If you look at the Audi webpage in your link and you apply the decimal number in the 3rd screenshot (i.e. 24069) into the calculator at the bottom of the page (and press "calculate"), you get the number 38817 - exactly the same as my decimal value in the table above
 
So what's this all mean for your Audi?

Well here is the process (assuming your Audi uses the same decryption key as the Audi webpage in your link):

The thing to note is that your Audi uses hexadecimal numbers and the calculator on the webpage in your link uses decimal numbers -so:

1. In your screenshot, the number in your car is Hex441E, so first you need to convert the number into decimal (which is 17438 - see above).
   
2. Enter 17438 into the calculator at the bottom of the page in your link and press calculate - the answer is 36300, which is a decimal number
3. Convert decimal 36300 into hexadecimal (use any webpage converter) and you get hex8DCC
4. enter 8DCC into the new value box in your screen shot and press Doit!

Don

 

[Daniel (Germany)]

Wow, i'm impressed don. This is way to much for my little brain but now i know who i can ask for. One question what is svm trouble?

[dv52 (Australia)]

Feb 20, 2017 8:50:58 GMT Daniel (Germany) said:

Wow, i'm impressed don. This is way to much for my little brain but now i know who i can ask for. One question what is svm trouble?

Daniel:  This is just low level maths - I learnt it  many, many years ago @ uni and because I'm a self confessed nerd, that happens to like numbers, I remember it. Don't be impressed -I bet there's lots of stuff that you know, of which I'm totally ignorant!

As for SVM it's just an abbreviation for Software Version Management and it's a process that validates new software updates in the MIB unit

Don

[Daniel (Germany)]

Thanks don. Now i know what it is. I didnt know what svm was short for.

[mdnav]

Hi!

And thanx a lot for the warm welcome and fast reply:-)

I am totally blown away at your math skills on this!!

I only got one issue. The web page from audienthusiasts I was refering to use MMI 3G as an example wich is slightly different from MIB. I doubt the 24069 decryption key is relevant for my Q7 retrfofit. From the audienthusiasts page adaption Channel 15 showing decryption key 24069 is for MMI 3G. Same function/procedure to calculate SVM on MIB is slightly different as the adaption setup is different. On MIB you can find the old value, wich is the one I understand you refer to as the decryption key under adaption channel option "Confirmation of installation change" as seen in the video example with Golf 7 using obdeleven tool. .

So in my case with the Audi Q7 with MIBII as far as I can understand the old value 441E is the decryption key for calculating new SVM value on MIB, similar to how 24069 is the decryption key for calculating new value in the example from audienthusiast page using a MMI 3G platform as example.

So if I am not misunderstanding this completely I dont see how the 24069 value from example with another car with MMI 3G can be related to my case with the Audi Q7 showing old value 441E to calculate new code?

Sorry if this might seem stupid to you but I am really, really a complete noob when it comes to math

Best regards

Morgan - MDNAV

 

Feb 20, 2017 7:03:21 GMT dv52 (Australia) said:

Feb 20, 2017 0:49:58 GMT mdnav said:

Hi!

I have recently bought the OBDeleven tool as I run a large retrofit store in Norway and think it is a much more handy tool than PC and VCDS. I have come across the SVM issue sometimes when updating SW or retrofitting MMI modules, but in these cases I have used the calculator from audienthusiast www.audienthusiasts.com/Application_SVMError.html but the MIB and MIBII platforms seems to have a different math behind the stored value in controller 5F, adaption: "Confirmation Of Installation Change" and how to calculate the new value.

I have read this thread a thousand times and tried to wrap my head around the math behind calculating the new value, but unfortunately I am a complete math noob and dont get this at all.

I have retrofitted a MIBII Main Unit in Audi Q7 4M and need to calculate new value to clear this error. Stored value is 441E


Can you guys please help me figure out what the new value would be and try and explain the math in simple ways and how to use the calculator for future similar issues:-)

Thanx!

Morgan Brorson Dahl - MDNAV

Morgan: Hi and welcome to the wonderful world of numbers!!!

Short summary: Your process for the Audi is exactly the same as that of Peter's and if the link that you posted applies to your car (and I will explain later why it may not) the cypher on your Audi even has the same decryption key!

Longer answer: First I have to introduce the concept of a "base "(short for number base) because your Audi uses three of these.

Binary: this numbering system has a base 2, which means that there are 2 x numbers used - 0, 1

Decimal: this is the numbering system that you are familiar with and it has a base 10, which means that there are ten numbers used - 0, 1, 3.....9

Hexadecimal: this numbering system has a base 16, which means that there are sixteen "characters" used - 0, 1, 2 .....9, A, B, C.....F

Any number can be represented as a value in any of these 3 x numbering systems and it's possible to convert numbers into another system. For example Decimal 10 = Hexadecimal A = Binary 1010

So,. now that I have introduced these 3 x numbering system, let's look at the numbers for your project - there are three pertinent numbers as follows:

Decryption key: In my reply to Peter, I referred to the decryption key C9D2. Clearly this is not a decimal number, nor is it a binary number because it contains alphabetic characters - C9D2 is a hexadecimal number (base 16). The web contains numerous converters that will translate any number to any other number base, but:

 HexC9D2=Decimal 51,666 = Binary 1100100111010010 

Your Audi: Your screenshot and your post contains the number 441E. Again, it's obvious that this is not a decimal, or binary number (it contains alpha characters) - 441E is a hexadecimal number (base 16) and:

 Hex441E= decimal 17,438 = binary 0100010000011110

Audi webpage: The webpage in your link uses the number from the VCDS screen 24069. This is clearly a decimal number (it doesn't contain any alpha characters, so it's not hex and it contains numbers other than 0 & 1, so it isn't Binary):

 Decimal 24,069 = Hex5e05 = binary 0101111000000101

So, lets look at these numbers together in the same format (I've highlighted the number system that was originally identified in the source material and I've separated the numbers in your Audi into its own table to demonstrate how the decryption process is applied):

	Decimal	Hexadecimal	Binary
Your Audi.......	17,438	441E	0100010000011110

	Decimal	Hexadecimal	Binary
Decryption key	51,666	C9D2	1100100111010010
Audi webpage	24,069	5e05	0101111000000101
Xor	38,871	97d7	1001011111010111

In the last row of the second table, I've manually applied the mathematical function Xor in the Binary column. It's not difficult - just compare each digit from both binary numbers - if the two digits are the same, the Xor value is 0, if the two digits are different, the Xor value is 1. For example the left-most digits for the two numbers are different, therefore the left-most Xor digit is 1 - then repeat this same process with the other digits! Also in the last row, I've translated the Binary number into Decimal and Hexadecimal as shown

If you look at the Audi webpage in your link and you apply the decimal number in the 3rd screenshot (i.e. 24069) into the calculator at the bottom of the page (and press "calculate"), you get the number 38817 - exactly the same as my decimal value in the table above
 
So what's this all mean for your Audi?

Well here is the process (assuming your Audi uses the same decryption key as the Audi webpage in your link):

The thing to note is that your Audi uses hexadecimal numbers and the calculator on the webpage in your link uses decimal numbers -so:

1. In your screenshot, the number in your car is Hex441E, so first you need to convert the number into decimal (which is 17438 - see above).
   
2. Enter 17438 into the calculator at the bottom of the page in your link and press calculate - the answer is 36300, which is a decimal number
3. Convert decimal 36300 into hexadecimal (use any webpage converter) and you get hex8DCC
4. enter 8DCC into the new value box in your screen shot and press Doit!

Don

 

[dv52 (Australia)]

Mrgan: OK -bit of confusion but you are correct 24069 is not pertinent to your car at all. Don't apologize, this stuff can be daunting and this environment (i.e. a post on a forum) is not ideal to teach/learn number theory!

I think the main confusion is in your understanding of the decryption key . The decryption key is the code that is common to all cars and from what I can tell (from Peter's post and from the webpage link in your post) it is C9D2 - it's not 24069 and it's not hex441E. The decryption key is constant and it doesn't change for individual vehicles, however the decryption key is applied to a number that is unique to each car (it's actually unique to each MIB software update). So in your car, the individual code is hex441E and in the webpage link, the individual code was decimal 2409. But as I say, the individual code will be different for each vehicle.

The way that SVM works is that the same decryption key is applied to the unique code from each car to produce a unique number that is used to confirm the updated software. In your webpage link the decryption key's identity (i.e. C9D2) is hidden behind the algorithm that is activated when you press the "calculate" button. But I have proven that the decryption key value is C9D2 because the value that I calculate for the unique number in the car in the web-page is the same as the algorithm produces when you press the "calculate" button

So, perhaps the easiest way forward is to forget about 24069 and forget about the value of the decryption key - simply take your unique number hex441E and apply it in the way that I suggest to the 4 x steps at the end of my reply. If you have other vehicles that you want to also apply the technique, simply take its unique number (that you will get by viewing the screenshot in your post when you connect to the other car) and complete the same steps.

Don

[dv52 (Australia)]

Feb 20, 2017 21:15:26 GMT dv52 (Australia) said:

oops!!

[Tell]

Sorry to dig the thread up but I'm wondering what the definition of "new software updates". I got a Seat in the UK and they don't offer Mapcare. The unit is the Discover Pro type with the SSD. I enabled developers mode and read in the 2017-18 European Map up date via SWDL... more forced. Select all. They did have an F (on map) and Err against the other three categories... but it peculated away. You see the map for a short period then disappears with the message "The navigation data in the infotainment system is not valid. Please Check data". It navigates in voice only. Error codes in Obdeleven B201A00 and B126CF2. Checking software version management static and Database not enabled.

Is this a candidate for the SVM fix. I wasn't sure whether OBDEleven told you it needed to do this fix or whether you deduced it and just did it. I ran out of time looking at it before I took the car to the garage to sort out another issue and ask them to fix this. Information on SVM is a bit thin on the ground but I'm thinking perhaps it's an incremental fix for CP and changing the maps if you haven't got mapcare throws up this raspberry but then I didn't know how it presented itself. i.e. does introducing new maps into the system without mapcare count as a new software update ?.

My confirmation of installation change is 5349 so I think you work out the input code and it comes back with this code again ?. If this is the way to do it then the next map update I could try this way but I might be barking up the wrong tree. View ?.

I seemed to have worked out the value 9A9B but I didn't get to execute it.... not on this occasion but if it's the map fix it would be useful.

[slaw78]

Jan 6, 2017 15:29:24 GMT peter3man said:

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

[slaw78]

Hello everyone, I am new here. I have such a mistake in Vw Touran 2016 navi pro. Can anyone help me


5F Elektronika układów informacyjnych

Opis sytemu: MU-H-ND-EU
Numer oprogramowania: 3G0035020B
Wersja oprogramowania: 0317
Numer sterownika: 3G0035020
Wersja sterownika: H42
Numer seryjny: A598H0F7513582
Nazwa ODX: EV_MUHig4CGen2HBAS
Wersja ODX: 001001
Długie kodowanie: 02730801FF00000051111101008808031F0106D4012001009F

Kody błędów:
B201A00 - Sprawdzanie układu zarządzania wersją oprogramowania
Statycznie
Date: 2018-04-24 19:32:54
Mileage: 36598 km
Priorytet: 6
Licznik częstotliwości wystąpienia usterki: 1
Licznik cykli wyuczania: 43
Dynamiczne dane otoczenia: 02867A10024D4455563130312F4142542020202020

[slaw78]

May 6, 2018 9:13:50 GMT slaw78 said:

Jan 6, 2017 15:29:24 GMT peter3man said:

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

[slaw78]

May 6, 2018 9:46:28 GMT slaw78 said:

May 6, 2018 9:13:50 GMT slaw78 said:

[slaw78]

May 6, 2018 9:46:28 GMT slaw78 said:

May 6, 2018 9:13:50 GMT slaw78 said:

Only my key is not 410a but 2ff5

[slaw78]

May 6, 2018 9:13:50 GMT slaw78 said:

Jan 6, 2017 15:29:24 GMT peter3man said:

I Watch a video on a Easy way to clear SVM trouble code from MIB or Discover multimedia unit after sw update.

I don't understand the math. I have a 6afd code on my obdeleven screen.

Can you tell me how to do the math or where i can find any expectation of it.

Thanks

Peter





To remove SVM trouble code you need to modify value of adaptation "Confirmation of installation change".

Use this math to calculate new value: "original value" XOR 51666 = "New value"

i.e. 410a XOR C9D2 = 88d8

Only my key is not 410a but 2ff5

[slaw78]

May 6, 2018 9:52:01 GMT slaw78 said:

May 6, 2018 9:13:50 GMT slaw78 said:

Only my key is not 410a but 2ff5

Thanks Petet I substituted my code for this pattern and the problem was solved thanks

[spoon13]

Bonjour
je ne suis pas tres fort en math donc SVP AIDEZ MOI !!! Je ne comprends rien du tout
Vérification version logiciel 5F
Ma clé 40b9 si quelqu'un pouvait me donner le code merci d'avance

[dv52 (Australia)]

Jan 6, 2019 16:52:04 GMT spoon13 said:

Bonjour
je ne suis pas tres fort en math donc SVP AIDEZ MOI !!! Je ne comprends rien du tout
Vérification version logiciel 5F
Ma clé 40b9 si quelqu'un pouvait me donner le code merci d'avance

spoon: Apology, my French language skills are entirely non existent, but here's how to calculate your number - the answer is  896B

Don

[ofektal8]

His method really works, You just go to a Online XOR Calculatr and You will see two inputs, in one of them type C9D2 And in the second one type your current value.

And it will give you the code you need to use. The error disappeared right away, Thanks!

[spoon13]

Heyyyyyy résolu merci à vous deux DV52 et ofektal8 je suis vraiment contant de vos réponses j'ai appris grâce à vous comment faire le calcule
ps: je n'ait toujours pas de NAVIGATION car mon logiciel n'est pas bon
J'ai ce message
(donné de navigation non valide) j'ai la version 2018
Merci encore 🙏