|
Post by vwjap on Feb 1, 2021 16:56:13 GMT
Go into the module, then faults, then I think you can clear from there (been a while tho)
|
|
|
Post by vwjap on Feb 2, 2021 9:14:10 GMT
.
|
|
|
Post by mlamaiz on Feb 2, 2021 9:21:07 GMT
Thanks. I know how to clear "faults". You said clear "codes", I thought that it meant something else.
|
|
|
Post by vwjap on Feb 2, 2021 11:55:08 GMT
Ah ok sorry, well they are fault codes 😂
|
|
|
Post by mlamaiz on Feb 2, 2021 15:03:26 GMT
I have just cleared the fault codes 10 times and they did not go away! Any other suggestions?
|
|
|
Post by Carmaffia on Feb 2, 2021 17:42:15 GMT
Somebody got this working on ios? Tried different radio's, changed code and then save. But the wheel keeps turning for ages and does not confirm. When i recheck the old code is still active. So the error stays... Leave it. Used Odis to clear this code. It's not working on OBD11 under Ios.
|
|
|
Post by mlamaiz on Feb 22, 2021 10:12:35 GMT
For the people that got the same issue as me, the only way to remove the SVM fault code is to re-install/update the software of the MIB unit again. The needed version number will be generated. The fault code can be then removed like it's described in this topic.
|
|
|
Post by scubamrtin on Jun 18, 2021 15:10:48 GMT
Help,
I’ve done a software update to my taracco unit and also a map update and have a couple of fault codes that don’t seem to want to go away.
I’ve got the B126CF2 navigation database not enabled B201A00 version management
I’ve looked at the many posts and checked the confirmation of changes which gives current value of key BD9A if I’ve read the posts correctly the code I should enter is 7448 as the new key. When I do this it says writing and never changes I’ve left it for 10 minutes but nothing. I’m using iOS.
What am I doing wrong?
|
|
|
Post by vogash on Aug 21, 2021 16:05:56 GMT
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: - 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).
- 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
- Convert decimal 36300 into hexadecimal (use any webpage converter) and you get hex8DCC
- enter 8DCC into the new value box in your screen shot and press Doit!
Don
Hi, I red all thread, all almost clear, except 2 things. 1. How/where can I see Decryption key in OBD11? 2. The value from Audi page 24609, in OBD11 I find it in Adoptation>Confirmation of installation change, right(in my case is 224D)? Assuming as you wrote decryption key is C9D2 I did the following. Opened calculator, switch to Programmer mode and Entered my current value 224D I got binary number Did XOR of two binary numbers and get my HEX new value EB9F Enter security code. However after entering new value and pressing accept, it automatically reverts back Any clue?
|
|
|
Post by vwjap on Aug 21, 2021 21:07:11 GMT
Clear the faults then look for errors again
|
|
|
Post by vogash on Aug 22, 2021 17:31:43 GMT
yep, it worked, I missed information that value in OBD11 will not changed, but behind the since yes.
|
|
|
Post by ramasjang on Jan 12, 2022 16:42:52 GMT
Hi dv52 (Australia) Octavia 2019 here.... Can you help with a new code for fault code B201A00? My key value under Confirmation of installation change is 6DA2
|
|
|
Post by vwjap on Jan 12, 2022 17:41:30 GMT
A470
Not sure if it’s fixed but I thought there was problems doing it on iOS
|
|
|
Post by crxgator on Feb 9, 2022 23:43:46 GMT
|
|
|
Post by vwjap on Feb 10, 2022 9:31:47 GMT
Seconds, but iOS is all over the place when doing this, android is much more stable
Plus it’s not really a error, it doesn’t cause any problems, I know a Vw tech and he says they never clear it in the workshop, then they can see if they’ve done any work to the unit, like the security update that happened a few years ago
|
|
|
Post by grigcris on May 11, 2022 13:04:50 GMT
Hello everyone. I have a golf 7 manufactured in 2015 with MIB1 Discovery Media with the following error: Address 5F: Information Electr. (J794) Labels:| 5G0-035-MIB-STD1.clb Part No SW: 5G0 035 846 A HW: 5G0 035 846 A Component: MU-S-N-ER 041 0430 Serial number: V1F00508142993 Coding: 02730001FF00000011110001000800001F0000840100010045 Shop #: WSC 00028 028 00066 ASAM Dataset: EV_MUStd4CPASE 002039 ROD: EV_MUStd4CPASE_VW37.rod VCID: 275D4E9B5EED1DB3A2-8072 Display and control head 1 for information electronics: Subsystem 1 - Part No SW: 5G0 919 605 D HW: 5G0 919 605 D Component: ABT_Std_Nav H60 0030 Serial number: VWZ8Z9PS402RQL Data carrier: Subsystem 2 - Part No SW: 5G0 919 866 BD HW: ----------- Component: ECE 2020/21 --- 0094 Serial number: -------------------- 1 Fault Found: 1589 - invalid data record B2005 00 [009] - - [New feature! Extended UDS fault detail is only supported by current gen. interfaces] Confirmed - Tested Since Memory Clear Freeze Frame: Fault Status: 00000001 Fault Priority: 2 Fault Frequency: 1 Reset counter: 167 Mileage: 180478 km Date: 2022.05.10 Time: 14:05:50 i tried to insert the correct code given by the hex calculator mib-helper.com/im-so-xory/ with VCDS but, after the confirmation of writting the new code, i have again the old code memorised and the error is still present.. Today i ordered OBDeleven dongle and i will try to do it again with OBDEleven. Did that happened to anyone? How did you solve it? Many thanks
|
|
|
Post by dv52 (Australia) on May 11, 2022 20:39:58 GMT
hmm........ I'm unsure why you believe that the particular error in your VCDS report above is a fault that can be fixed by SVM? It's not - your error is caused by something else!
And, yes - when you enter the new correct SVM code and it is accepted, the value that is displayed by the channel is the "old code". Don
|
|
falcon
Junior Member
Posts: 57
|
Post by falcon on May 12, 2022 10:43:22 GMT
grigcris I once read this error in connection with the activation of VIM using the carlyappapp adapter. Disabling and reactivating VIM using OBD-eleven helped there. Did you try something there? Furthermore. MIB 1 devices are limited in many functions. i.e. many activations only became possible with MIB 2 or later.
|
|
|
Post by vwjap on May 12, 2022 18:48:48 GMT
Changing a lot of things bring up the SVM error, even a firmware updat
|
|
|
Post by grigcris on May 13, 2022 19:16:21 GMT
Thanks for taking time to answer me. I didn't attempted to activate VIM .. Don, can you be more specific ? I really have no idea what to check more... This is the only error i have on the car
|
|
|
Post by vwjap on May 13, 2022 20:37:03 GMT
B2005 This fault usually means there's a bug in the factory firmware, parameter related data in the control unit is incorrect or parameter data is missing because the module has not been configured via SVM with a direct connection to VW/Audi headquarters.
|
|
|
Post by grigcris on May 16, 2022 6:24:54 GMT
.... meaning i can't do anything (with VCDS dongle) to solve it, without a visit to VW service. Unfortunatelly they have huge prices here for these software related issues.
many thanks everyone.
|
|
|
Post by vwjap on May 17, 2022 10:30:42 GMT
That error could’ve been there from new, or a service update, does it cause any problems with the car? Or do you just want it cleared to cure your ocd/ make things look tidier?
|
|
|
Post by grigcris on May 17, 2022 12:43:32 GMT
Hello it's not bothering me and it's just there when you scan with vcds. i just wanted to get rid of it..
It appeared after the previous owner played with a caristaappapp dongle many thanks
|
|
falcon
Junior Member
Posts: 57
|
Post by falcon on May 17, 2022 15:46:52 GMT
So someone worked with a carlyapp adapter after all. Do you know what the previous owner changed? possibly undo these codings again with VCDS or obdeleven by hand re-coding (see my post above about VIM). This procedure may also help with other encodings with carlyapp. good luck.
|
|
|
Post by grigcris on May 17, 2022 16:14:27 GMT
i don't know what he has tried... I already tried your VIM ideea but no luck. I think that the only solution is to rewrite the original software again. problem is how to get it and how to write it... thanks again
|
|
|
Post by freshslo on Nov 26, 2022 23:32:24 GMT
Do you maybe know xor number for Lamborghini Urus. I have installation change code: 362d. But if i calculate thru method above i get ffff which doesn't work.
|
|
|
Post by dv52 (Australia) on Nov 27, 2022 22:13:41 GMT
Of course the answer is FFFF !
That's because your code 362D is a very special hex number -it's what mathematicians (I'm not one of these) call the "1's complement" of the cypher key that's used in the XOR function. As stated in earlier posts, the cypher key for cars in this part of the forum is C2D9 C9D2.
Maybe a better way of understanding just how special your code is - is by converting these two numbers into Binary, like this: - 36 2D = 00110110 00101101
- C9 D2 = 11001001 11010010
Notice for the Binary values that for each individual digit position between the hex numbers, every digit is the opposite (i.e. for each position in the Binary value - whenever there is a "1" in one number there is a "0" in the other number and vice-a-versa).
So, XOR(362D,C9D2) = 1111111 11111111) = FFFF!!!
Now, I guess there is a finite probability that your code is a legitimate candidate as a hex value for the XOR calculation for SVM - but I'm very surprised to see the 1's compliment of the cypher key used in this fashion!!
I'm guessing of course and I'm not sure what it means - but I suspect that this special number has been chosen deliberately for your car!! Maybe 362D is the actual cypher key for a Lamborghini Urus (again, a total guess)?
Don
PS: Interesting fact about "1's compliment" numbers in hex - it's the remainder value when subtracting! For example, the max hex value is F and the decimal equivalent of F = 15. So, with the 2 x numbers above 3 62D & C 9D2, take the highlighted digits 6 +9 = F. The same answer happens for each of the other digit positions- I love numbers
|
|
falcon
Junior Member
Posts: 57
|
Post by falcon on Nov 28, 2022 19:22:02 GMT
Hi dv52.
Have you possibly mixed up the characters in the cipher key? In the upper part of the last post you write C2D9, then in the explanation of C9D2? Which one is the right one?
|
|
|
Post by dv52 (Australia) on Nov 28, 2022 20:28:06 GMT
falcon : oops my bad - now fixed. Thanks! Don
|
|