nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 6, 2024 20:57:30 GMT
Hi, anyone who can help me? I changed the internal infoment unit with the composite media display bought used since I installed it. It gives me these errors that cannot be removed. Can you tell me if there is a way to remove them permanently? Thank you   |
|
|
|
Post by sprucepassatb8 on Feb 7, 2024 11:03:24 GMT
Hi, anyone who can help me? I changed the internal infoment unit with the composite media display bought used since I installed it. It gives me these errors that cannot be removed. Can you tell me if there is a way to remove them permanently? Thank you First u need to remove CP: Should be possible with some toolboxes or updating your infotaimentsystem. Second could be wrong coding for this unit! U have to code it right or have to try the old coding. The last one is some software failure, which is possible to remove with XOR-RechnerFirst things u need to know: ---> Installed SW train version ---> Installed SW MU Version ---> Partnumber Then we can go further. |
|
|
|
Post by ganimedes on Feb 7, 2024 11:33:34 GMT
.Hello
This error is totally normal if you have installed a new SECOND-HAND Infotaiment unit in your car.
That means that this unit was installed in another car at the factory, it has subsequently been hacked to eliminate Component Protection and be able to be used in another car.
For this reason it gives you that error, the component constellation (C.P.) of your car does not recognize it as original, everything will work perfectly, but this error cannot be eliminated, unless you recode it in an official Volkswagen service with ODIS, this software connects to Volkswagen servers in Germany.
The Process is delicate, since if the unit has been stolen, it will be reported, which will notify the police and can pose a problem.
If the unit you have installed is NEW, there will be no problem in recoding it for your car, but as I always tell you in an official Volkswagen service, and they are very skeptical about carrying out these recodings due to the problem it may pose for them, if the unit is not new and original.
As for the software error, it is very easy to eliminate it, there is a lot of information on the forum to do so; look it up, it's simple.
All the best.
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 11:44:27 GMT
.Hello
This error is totally normal if you have installed a new SECOND-HAND Infotaiment unit in your car.
That means that this unit was installed in another car at the factory, it has subsequently been hacked to eliminate Component Protection and be able to be used in another car.
For this reason it gives you that error, the component constellation (C.P.) of your car does not recognize it as original, everything will work perfectly, but this error cannot be eliminated, unless you recode it in an official Volkswagen service with ODIS, this software connects to Volkswagen servers in Germany.
The Process is delicate, since if the unit has been stolen, it will be reported, which will notify the police and can pose a problem.
If the unit you have installed is NEW, there will be no problem in recoding it for your car, but as I always tell you in an official Volkswagen service, and they are very skeptical about carrying out these recodings due to the problem it may pose for them, if the unit is not new and original.
As for the software error, it is very easy to eliminate it, there is a lot of information on the forum to do so; look it up, it's simple.
All the best.
thanks for your reply I bought the car radio used but I don't know where it came from, the guy who installed it told me that these errors were there but I didn't know how to remove them I had to go to VW anyway your explanation was excellent I'll just update the software thanks one thousand |
|
|
|
Post by sprucepassatb8 on Feb 7, 2024 11:56:05 GMT
.Hello
This error is totally normal if you have installed a new SECOND-HAND Infotaiment unit in your car.
That means that this unit was installed in another car at the factory, it has subsequently been hacked to eliminate Component Protection and be able to be used in another car.
For this reason it gives you that error, the component constellation (C.P.) of your car does not recognize it as original, everything will work perfectly, but this error cannot be eliminated, unless you recode it in an official Volkswagen service with ODIS, this software connects to Volkswagen servers in Germany.
The Process is delicate, since if the unit has been stolen, it will be reported, which will notify the police and can pose a problem.
If the unit you have installed is NEW, there will be no problem in recoding it for your car, but as I always tell you in an official Volkswagen service, and they are very skeptical about carrying out these recodings due to the problem it may pose for them, if the unit is not new and original.
As for the software error, it is very easy to eliminate it, there is a lot of information on the forum to do so; look it up, it's simple.
All the best.
thanks for your reply I bought the car radio used but I don't know where it came from, the guy who installed it told me that these errors were there but I didn't know how to remove them I had to go to VW anyway your explanation was excellent I'll just update the software thanks one thousand Look at my post! U don't have to go to VW Dealer  |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 12:14:04 GMT
thanks for your reply I bought the car radio used but I don't know where it came from, the guy who installed it told me that these errors were there but I didn't know how to remove them I had to go to VW anyway your explanation was excellent I'll just update the software thanks one thousand Look at my post! U don't have to go to VW Dealer ok I'll read carefully...I'm not very practical if you ever follow me. the only thing I did was change the key code with the xor calculation but the error goes away but it comes out |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 12:21:37 GMT
thanks for your reply I bought the car radio used but I don't know where it came from, the guy who installed it told me that these errors were there but I didn't know how to remove them I had to go to VW anyway your explanation was excellent I'll just update the software thanks one thousand Look at my post! U don't have to go to VW Dealer Ecco   |
|
|
|
Post by dv52 (Australia) on Feb 7, 2024 20:58:21 GMT
nicola : Hi. It's entirely your choice how you deal with the Component Protection error (you can take it to a dealer and pay for the minimum work-time for a master-tech to remove the CP error, or you can use the hack-tools mentioned previously) For the incorrectly coded error - you need to compare the long-code strings and the adaptation channels on both the old and the new MIB/MMI (what is the make/model of this car?). If you didn't make a record of the old MIB/MMI coding - temporarily refit the old module (it's easy to do this) and make a Backup. Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 21:01:25 GMT
nicola : Hi. It's entirely your choice how you deal with the Component Protection error (you can take it to a dealer and pay for the minimum work-time for a master-tech to remove the CP error, or you can use the hack-tools mentioned previously) For the incorrectly coded error - you need to compare the long-code strings and the adaptation channels on both the old and the new MIB/MMI (what is the make/model of this car?). If you didn't make a record of the old MIB/MMI coding - temporarily refit the old module (it's easy to do this) and make a Backup. Don Unfortunately I no longer have the old unit |
|
|
|
Post by dv52 (Australia) on Feb 7, 2024 21:08:04 GMT
hmm......... bummer!!
OK, then look through the records in History on your OBD11 account - hopefully there might be mention of the long-code value from a past interaction with the 5F module?
Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 21:19:08 GMT
hmm......... bummer!!
OK, then look through the records in History on your OBD11 account - hopefully there might be mention of the long-code value from a past interaction with the 5F module?
Don
Don, can you explain to me how I can send you the story? |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 21:28:45 GMT
OBDeleven registro cronologia auto
Data: 2024-02-07 22:14
NIV: WVWZZZAUZDP015921
Veicolo: Volkswagen Golf VII
Anno: 2013
Tipo di carrozzeria: 5-dr hatchback
Motore: CRBC
Chilometraggio: 145886 KM
---------------------------------------------------------------
Adattamento
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Nome: Startup_Screen_Sticker_HMI
Valori:
Startup_Screen_Sticker_HMI:
Vecchio valore: 0
Nuovo Valore: 2
Chilometraggio: 128245 km
Data: 2023-03-13 14:50
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 7
Nuovo Valore: 6
Chilometraggio: 128245 km
Data: 2023-03-13 12:43
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0507940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0506940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:43
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0540940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0507940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:41
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 64
Nuovo Valore: 7
Chilometraggio: 128245 km
Data: 2023-03-13 12:41
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F054C940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0540940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:36
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0504940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F054C940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:36
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0520940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0504940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:35
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0540940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0520940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:33
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0550940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0540940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:33
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0510940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0550940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:33
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0520940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0510940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:30
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0508940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0520940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:25
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0504940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0508940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:21
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731300FF0000006111000100080A001F0500940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0504940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:19
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_2_Car_Derivate:
Vecchio valore: 0
Nuovo Valore: 3
Chilometraggio: 128245 km
Data: 2023-03-13 12:04
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02731000FF0000006111000100080A001F0500940120000002
Nuovo Valore:
02731300FF0000006111000100080A001F0500940120000002
Chilometraggio: 128245 km
Data: 2023-03-13 12:04
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0106140100010057
Nuovo Valore:
02731000FF0000006111000100080A001F0500940120000002
Chilometraggio: 128190 km
Data: 2023-03-11 18:21
---------------------------------------------------------------
Adattamento
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Nome: Veicolo menu comandi
Valori:
menu_display_driving_school:
Vecchio valore: attivato
Nuovo Valore: non attivato
Chilometraggio: 121558 km
Data: 2022-10-26 18:56
---------------------------------------------------------------
Adattamento
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Nome: Veicolo lista funzioni CAN
Valori:
Driving_school:
Vecchio valore: disponibile
Nuovo Valore: non disponibile
Chilometraggio: 121558 km
Data: 2022-10-26 18:54
---------------------------------------------------------------
Adattamento
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Nome: Veicolo menu comandi
Valori:
menu_display_driving_school:
Vecchio valore: non attivato
Nuovo Valore: attivato
Chilometraggio: 121393 km
Data: 2022-10-23 09:54
---------------------------------------------------------------
Adattamento
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Nome: Veicolo lista funzioni CAN
Valori:
Driving_school:
Vecchio valore: non disponibile
Nuovo Valore: disponibile
Chilometraggio: 121393 km
Data: 2022-10-23 09:52
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 0
Nuovo Valore: 6
Chilometraggio: 102876 km
Data: 2021-08-27 12:34
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0100140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0106140100010057
Chilometraggio: 102876 km
Data: 2021-08-27 12:34
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 6
Nuovo Valore: 0
Chilometraggio: 101768 km
Data: 2021-08-06 19:08
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0106140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0100140100010057
Chilometraggio: 101768 km
Data: 2021-08-06 19:08
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 4
Nuovo Valore: 6
Chilometraggio: 101461 km
Data: 2021-07-30 22:09
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0104140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0106140100010057
Chilometraggio: 101461 km
Data: 2021-07-30 22:09
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 0
Nuovo Valore: 4
Chilometraggio: 101461 km
Data: 2021-07-30 22:08
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0100140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0104140100010057
Chilometraggio: 101461 km
Data: 2021-07-30 22:08
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0106140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0100140100010057
Chilometraggio: 101242 km
Data: 2021-07-25 11:20
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 6
Nuovo Valore: 0
Chilometraggio: 101242 km
Data: 2021-07-25 11:20
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 1
Nuovo Valore: 6
Chilometraggio: 100340 km
Data: 2021-07-06 23:17
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0101140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0106140100010057
Chilometraggio: 100340 km
Data: 2021-07-06 23:17
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 6
Nuovo Valore: 1
Chilometraggio: 100340 km
Data: 2021-07-06 23:16
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0106140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0101140100010057
Chilometraggio: 100340 km
Data: 2021-07-06 23:16
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Valori:
byte_18_Screenings:
Vecchio valore: 0
Nuovo Valore: 6
Chilometraggio: 100340 km
Data: 2021-07-06 20:40
---------------------------------------------------------------
Codifica completa
Unità di controllo: 5F Sistema elettronico per l'informazione 1
Vecchio valore:
02730001FF00000021110001000800001F0100140100010057
Nuovo Valore:
02730001FF00000021110001000800001F0106140100010057
Chilometraggio: 100340 km
Data: 2021-07-06 20:40
|
|
|
|
Post by dv52 (Australia) on Feb 7, 2024 23:25:49 GMT
Something doesn't make sense!!!
Here's a copy of the latest record from your History data showing the long-code string on what I assume is the OLD MIB on this car: --------------------------------------------------------------- Codifica completa Unità di controllo: 5F Sistema elettronico per l'informazione 1 Vecchio valore: 02731300FF0000006111000100080A001F0507940120000002 Nuovo Valore: 02731300FF0000006111000100080A001F0506940120000002 Chilometraggio: 128245 km Data: 2023-03-13 12:43 ---------------------------------------------------------------
Note the date for the above record is 2023-03-13. So this record is almost 12 months ago!!
However, you posted this in an earlier reply - which I assume is from the NEW MIB:
So, comparing the long-code strings: - New MIB = 02731300FF0000006111000100080A001F0506940120000002
- Old MIB = 02731300FF0000006111000100080A001F0506940120000002
EXACTLY THE SAME!!
I don't understand!!?
Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 7, 2024 23:56:05 GMT
there's no remedy?
|
|
|
|
Post by dv52 (Australia) on Feb 8, 2024 0:20:39 GMT
nicola : First-up, it's NOT my role on this forum to judge others - but I'm totally confused!! I can't answer any new questions if you don't answer my old questions first!! What has happened with this car? It's possible that you have replaced the ENTIRE long-code string from your old MIB into the new MIB - but I don't see this change in your History records. I can't help, if you don't want to explain the backstory for this new MIB and frankly, it doesn't matter to me if you won't answer my questions Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 8, 2024 7:05:19 GMT
what I can tell you about a year ago I wanted to change the old mib1 unit with an mib2 used by a guy who mounted it for me and I don't know he made some encodings that I haven't seen. From there these errors appeared and if possible I would like to eliminate them. I have sent you the entire history of the encodings carried out at f5 and the screenshots of the errors. That's all
|
|
|
|
Post by dv52 (Australia) on Feb 8, 2024 20:43:32 GMT
OK so I can only assume that the oldest hex5F entry (2021-07-06) in your History records applies for the OLD MIB.
Here is a comparison of the newest and oldest 5F long-code strings in your History records :
Name OLD NEW
Byte Hex Binary Hex Binary
00 02 00000010 02 00000010
01 73 01110011 73 01110011
02 00 00000000 13 00010011
03 01 00000001 00 00000000
04 FF 11111111 FF 11111111
05 00 00000000 00 00000000
06 00 00000000 00 00000000
07 00 00000000 00 00000000
08 21 00100001 61 01100001
09 11 00010001 11 00010001
10 00 00000000 00 00000000
11 01 00000001 01 00000001
12 00 00000000 00 00000000
13 08 00001000 08 00001000
14 00 00000000 0A 00001010
15 00 00000000 00 00000000
16 1F 00011111 1F 00011111
17 01 00000001 05 00000101
18 00 00000000 06 00000110
19 14 00010100 94 10010100
20 01 00000001 01 00000001
21 00 00000000 20 00100000
22 01 00000001 00 00000000
23 00 00000000 00 00000000
24 57 01010111 02 00000010
Remember that for Binary numbers, Bit 0 is the right-most digit and Bit 7 is the left-most digit
Maybe start by setting Byte 02 to the OLD value - then try clearing the error
Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 8, 2024 20:49:12 GMT
don I went into the total history and found the pina coding he did  |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 8, 2024 20:55:48 GMT
OK so I can only assume that the oldest hex5F entry (2021-07-06) in your History records applies for the OLD MIB.
Here is a comparison of the newest and oldest 5F long-code strings in your History records :
Name OLD NEW
Byte Hex Binary Hex Binary
00 02 00000010 02 00000010
01 73 01110011 73 01110011
02 00 00000000 13 00010011
03 01 00000001 00 00000000
04 FF 11111111 FF 11111111
05 00 00000000 00 00000000
06 00 00000000 00 00000000
07 00 00000000 00 00000000
08 21 00100001 61 01100001
09 11 00010001 11 00010001
10 00 00000000 00 00000000
11 01 00000001 01 00000001
12 00 00000000 00 00000000
13 08 00001000 08 00001000
14 00 00000000 0A 00001010
15 00 00000000 00 00000000
16 1F 00011111 1F 00011111
17 01 00000001 05 00000101
18 00 00000000 06 00000110
19 14 00010100 94 10010100
20 01 00000001 01 00000001
21 00 00000000 20 00100000
22 01 00000001 00 00000000
23 00 00000000 00 00000000
24 57 01010111 02 00000010
Remember that for Binary numbers, Bit 0 is the right-most digit and Bit 7 is the left-most digit
Maybe start by setting Byte 02 to the OLD value - then try clearing the error
Don
Don, I'm not sure what I should do, I'm not very practical, guide me more simply. Thank you |
|
|
|
Post by dv52 (Australia) on Feb 8, 2024 22:25:38 GMT
nicola : Yes, my table has already captured the value of the long-code changes in your last screenshot (dated 2023-03-13). Do this:
- Read THIS
- Ignition-ON, engine-OFF
- Plug-IN the OBD11 dongle and connect to Iphone
- Navigate to the Control Units screen
- scroll-down and select the 5F module
- Scroll-down and select Long coding
- Click-on 0/1 symbol (see picture below) until the Byte/Bit screen is selected
- Navigate to Byte 02
- Remove ticks from:After change NO ticks should appear on any Bits and Byte 02 = Hex 00
- Implement change
- Clear any faults that remain in 5F module
Don
|
|
|
|
Post by whataboutthis on Feb 8, 2024 22:37:36 GMT
Sorry don thought you had finished on this site.
1/ Go to control unit 5F and select Long Coding Then you will get this screen, now select number 1 at the top of the screen (defaults to 0) This will take you to Byte 00 (you can see the Byte number top left)
 Then using the Right hand Blue arrow at the bottom of the screen move to Byte 02 You will see the Value is 13, as per Don's instructions Firstly change this to 00, then try and clear the error. hope that helps
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 8, 2024 22:57:16 GMT
Sorry don thought you had finished on this site.
1/ Go to control unit 5F and select Long Coding Then you will get this screen, now select number 1 at the top of the screen (defaults to 0) This will take you to Byte 00 (you can see the Byte number top left)
Then using the Right hand Blue arrow at the bottom of the screen move to Byte 02 You will see the Value is 13, as per Don's instructions Firstly change this to 00, then try and clear the error. hope that helps
thanks I understood Don's instructions here now and night tomorrow morning I'll try to code hoping that the error will disappear |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 9, 2024 12:28:54 GMT
I did the coding but when I went back the ticks remained and if I tried to recode and remove the ticks it didn't work  |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 9, 2024 12:43:43 GMT
I forgot to tell you that before in the old mib1 I had the possibility in the menu to activate and deactivate the ESP. With this mib2 I no longer have the possibility to activate and deactivate it
|
|
|
|
Post by dv52 (Australia) on Feb 9, 2024 21:39:06 GMT
nicola : Hmm........ I think that maybe you made a "boo-boo" - which is a technical term for an error!! 
This is a copy of your screenshot:
Look at the first few numbers on the 2 x long-code strings in your picture: - Vecchio valore = 027313...................
- Nuovo Valre = 026013...................
Bytes are 2 x digit numbers (called "Hexadecimal pairs") and Byte numbering starts at Byte 00. This means for the values above: - Vecchio valore :
- Byte 00 = 02
- Byte 01 = 73
- Byte 02 = 13
- Nuovo Valore:
- Byte 00 = 02
- Byte 01 = 60
- Byte 02 = 13
So - it very much appears that Byte 01 was changed INSTEAD OF Byte 02 (which is actually the third-Byte in the long-code string - because Byte numbering starts with Byte 00)
Because of this new error - you need to un-do the change that was made and then alter the proper Byte 02 as per whataboutthis excellent instructions above.
To fix the new Byte 01 error - this is how to set-up the tick-marks for the Bits to revert the value back to Hex 73: - Bit 0 = tick
- Bit 1 = tick
- Bit 2 = no tick
- Bit 3 = no tick
- Bit 4 = tick
- Bit 5 = tick
- Bit 6 = tick
- Bit 7 = no tick
Hint: coding changes are very precise - double and triple (and quadruple) check ALL aspects BEFORE implementing the change. For long-code changes - this means: - confirm that you are changing the correct Byte number, and
- make sure that the set-up for the Bit tick-marks yield the correct new Hex value!!
Do NOT implement long-code changes unless these 2 x checks are correct on the 2nd line of the white box at the top of the OBD11 screen (see whataboutthis screenshots above)
Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 9, 2024 22:51:16 GMT
nicola : Hmm........ I think that maybe you made a "boo-boo" - which is a technical term for an error!!
This is a copy of your screenshot:
Look at the first few numbers on the 2 x long-code strings in your picture: - Vecchio valore = 027313...................
- Nuovo Valre = 026013...................
Bytes are 2 x digit numbers (called "Hexadecimal pairs") and Byte numbering starts at Byte 00. This means for the values above: - Vecchio valore :
- Byte 00 = 02
- Byte 01 = 73
- Byte 02 = 13
- Nuovo Valore:
- Byte 00 = 02
- Byte 01 = 60
- Byte 02 = 13
So - it very much appears that Byte 01 was changed INSTEAD OF Byte 02 (which is actually the third-Byte in the long-code string - because Byte numbering starts with Byte 00)
Because of this new error - you need to un-do the change that was made and then alter the proper Byte 02 as per whataboutthis excellent instructions above.
To fix the new Byte 01 error - this is how to set-up the tick-marks for the Bits to revert the value back to Hex 73: - Bit 0 = tick
- Bit 1 = tick
- Bit 2 = no tick
- Bit 3 = no tick
- Bit 4 = tick
- Bit 5 = tick
- Bit 6 = tick
- Bit 7 = no tick
Hint: coding changes are very precise - double and triple (and quadruple) check ALL aspects BEFORE implementing the change. For long-code changes - this means: - confirm that you are changing the correct Byte number, and
- make sure that the set-up for the Bit tick-marks yield the correct new Hex value!!
Do NOT implement long-code changes unless these 2 x checks are correct on the 2nd line of the white box at the top of the OBD11 screen (see whataboutthis screenshots above)
Don
ok Don I think we're there I did the coding of the bytes and bits the error is still there but I noticed that the coding I had on the old mib 1 there was a check on byte 3 which gave 1 before the letters FF |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 9, 2024 22:52:14 GMT
nicola : Hmm........ I think that maybe you made a "boo-boo" - which is a technical term for an error!!
This is a copy of your screenshot:
Look at the first few numbers on the 2 x long-code strings in your picture: - Vecchio valore = 027313...................
- Nuovo Valre = 026013...................
Bytes are 2 x digit numbers (called "Hexadecimal pairs") and Byte numbering starts at Byte 00. This means for the values above: - Vecchio valore :
- Byte 00 = 02
- Byte 01 = 73
- Byte 02 = 13
- Nuovo Valore:
- Byte 00 = 02
- Byte 01 = 60
- Byte 02 = 13
So - it very much appears that Byte 01 was changed INSTEAD OF Byte 02 (which is actually the third-Byte in the long-code string - because Byte numbering starts with Byte 00)
Because of this new error - you need to un-do the change that was made and then alter the proper Byte 02 as per whataboutthis excellent instructions above.
To fix the new Byte 01 error - this is how to set-up the tick-marks for the Bits to revert the value back to Hex 73: - Bit 0 = tick
- Bit 1 = tick
- Bit 2 = no tick
- Bit 3 = no tick
- Bit 4 = tick
- Bit 5 = tick
- Bit 6 = tick
- Bit 7 = no tick
Hint: coding changes are very precise - double and triple (and quadruple) check ALL aspects BEFORE implementing the change. For long-code changes - this means: - confirm that you are changing the correct Byte number, and
- make sure that the set-up for the Bit tick-marks yield the correct new Hex value!!
Do NOT implement long-code changes unless these 2 x checks are correct on the 2nd line of the white box at the top of the OBD11 screen (see whataboutthis screenshots above)
Don
Here you are  |
|
|
|
Post by dv52 (Australia) on Feb 10, 2024 0:17:21 GMT
nicola : Yes, well done - you now have the first 3 x bytes the same as your OLD MIB! As I said in my earlier reply, fixing this problem is a process of checking each individual Byte (one at a time) And also yes - Byte 3, Bit 0 was set on your OLD MIB - but it is not set on your new MIB (look at Byte 3 on my table). This Bit tells the MIB to use Europe region for SATNAV. But, the new MIB does NOT have SATNAV because the long-code switch that tells the MIB to use SATNAV (i.e. Byte 24, Bit 2) is NOT set (see my table above) - so if I'm correct, the current coding on the new MIB is OK.
However, if I'm wrong (i.e. if the new MIB does have SATNAV) and if you are in Europe - then change Byte 3, Bit 0 =1 and change Byte 24, Bit 2 =1
Don
|
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 10, 2024 7:31:30 GMT
nicola : Yes, well done - you now have the first 3 x bytes the same as your OLD MIB! As I said in my earlier reply, fixing this problem is a process of checking each individual Byte (one at a time) And also yes - Byte 3, Bit 0 was set on your OLD MIB - but it is not set on your new MIB (look at Byte 3 on my table). This Bit tells the MIB to use Europe region for SATNAV. But, the new MIB does NOT have SATNAV because the long-code switch that tells the MIB to use SATNAV (i.e. Byte 24, Bit 2) is NOT set (see my table above) - so if I'm correct, the current coding on the new MIB is OK.
However, if I'm wrong (i.e. if the new MIB does have SATNAV) and if you are in Europe - then change Byte 3, Bit 0 =1 and change Byte 24, Bit 2 =1
Don thanks Don, from what I'm understanding the coding is OK... yes in the new MIB you don't have the navi sat and I'm in Europe and I don't have to change anything anymore, is that the case? Don why doesn't the error go away? |
|
nicola
Junior Member
Posts: 69
Member is Online
|
Post by nicola on Feb 10, 2024 14:51:57 GMT
in your theory in byte 24 the bit must be 0 not having navi it may be here that the error is not removed  |
|
