[TUTO] Télécodage et calibration d'un NAC / RCC / CIROCCO / CMB_NUM SANS Diagbox via Arduino

Small update on my journey: it seems that 0 = enabled and 1 = disabled. And only then it makes sense. Very weird to me.
So I enabled (or disabled?) ACC in CVM3 and in BSI and I got an alert: fault of adaptive cruise control, on dashboard. So either I'm still missing some configuration, or it's simply not possible without radar on the 208.
I'm running out of ideas...

Small update on my journey: it seems that 0 = enabled and 1 = disabled. And only then it makes sense. Very weird to me.
So I enabled (or disabled ?) ACC in CVM3 and in BSI and I got an alert : fault of adaptive cruise control, on dashboard. So either I'm still missing some configuration, or it's simply not possible without radar on the 208.
I'm running out of ideas...
Any luck?
 

Hi,
I activated Park Assist in my 5008 II GT-Line 2019 4 days ago.
The activation condition is to have 12PDC = 6 PDC front + 6 PDC rear

My old values before coding:

1. AAS_UDS_G5:

>75D:65D
1003
222101
answer from arduino: 62 2101 A5
1001 (closes sessions)

2.BSI:

>752:652
1003
222300
answer from arduino: 62 2300 13
1001 (closes sessions)

3.DAE_BVH2:

>6B5:695
81
21A0
answer from arduino:: 61 A0 05C0 CD 0002000001
82 (closes sessions)

You can check your values via Arduino in the terminal.

If you want, I can write step by step how I activated it.

Secured Traceability
2E2901FD000000010101
You enter it in BSI right after the first coding change, I just entered it there. Not in DAE_BVH2 and AAS.
@onzar can you please share your values after the activation? Thanks
 

bonjour, dites-moi qui peut. la clé pour encoder cvm2 est seulement E2E5 ? ou y en a-t-il d'autre? caméra 9831721680-04 / D5.5 CEM01 . lors de l'encodage n'écrit pas la bonne clé
 

hello, tell me who can. the key to encode cvm2 is only E2E5? or are there others? camera 9831721680-04 /D5.5 CEM01. when encoding does not write the correct k

bonjour, dites-moi qui peut. la clé pour encoder cvm2 est seulement E2E5 ? ou y en a-t-il d'autre? caméra 9831721680-04 / D5.5 CEM01 . lors de l'encodage n'écrit pas la bonne clé
You need to send the commands correctly:
>74A:64A
1003
:E2E25:03:03
 


You need to send the commands correctly:
>74A:64A
1003
:E2E25:03:03
pas de problème dans toutes les zones et les blocs, mais avec cvm2 lit seulement, et en essayant de changer écrit que la clé n'est E2E5 pas correcte.
 

Bonsoir,
Je crois que je viens de comprendre le code 7F2737 !
7F2737 ERREUR : Required Time Delay Not Expired
Ça signifierait que le calculateur a été bloqué pour une période de XXX minutes, suite à un mauvais code de déblocage !
Mais dans la version où j'envoie 2703, je ne vois pas ce qui pourrait bloquer !
Dans la version où j'envoie : D1F5:03:03, si la clé n'était pas bonne, ça bloquerait : OK. MAIS je suis sûr de cette clé car j'ai un log d'écriture avec DB 7.62 sur CET AAS, avec une paire SEE/KEY qui correspond !
Je continue mes recherches...
comment avez-vous résolu ce problème? combien attendre? quelles sont les conditions pour fournir une voiture? j'ai toujours la même chose avec cvm2. tout est vrai pour tout le monde, et j'ai 7f2737
 


здравейте всички
Най-накрая успях да включа Park Assist в моя 5008 II 2019 и той работи :bounce:. Една седмица четене на целия форум на Arduino. Помогна ми и бих искал да благодаря на всички във форума за помощта и полезната информация. Много благодаря на @VLud за предоставянето на програмата на NAC / RCC / CIROCCO.

И прочетох за защитен код за проследяване 2E2901FD000000010101, но го забравих някъде, благодаря ви @1 6 D за вашето напомняне:ДОБРЕ:
Здравейте, можете ли да споделите всички стъпки за активиране на асистента за паркиране, имам 3008 със същия двигател и може би трябва да използвам същите стойности като вас. благодаря
 

comment avez-vous résolu ce problème? combien attendre? quelles sont les conditions pour fournir une voiture? j'ai toujours la même chose avec cvm2. tout est vrai pour tout le monde, et j'ai 7f2737
I got this same code when unlocking my ESP even though the unlock key was correct and the process was as follows.
When unlocking the unit, the error code was generated several times and after several seconds it changed to a different key when there were no more codes and the 7f2737 stopped appearing and it proceeded to send the key to write the zone.
This error code means that you have to wait a while for the zone to be unlocked and this happens when the 7F2737 stops appearing and changes to a different key.
Example:
>6AD:68D
1003
222101
:ABFB:03:03 Response when unlocking the unit
7F2737
7F2737
7F2737
7F2737
7F2737
6704
2E2101XXXXX
This is just an example to understand the process and it doesn't have to be your case but when it has happened to me I have only had to wait as indicated by the error code to proceed to write the zone.
I hope it is understood with the translation.

J'ai reçu ce même code lors du déverrouillage de mon ESP bien que la clé de déverrouillage était correcte et que le processus était le suivant.
Lors du déverrouillage de l'unité, il a généré le code d'erreur à plusieurs reprises et après plusieurs secondes, il a changé pour une clé différente lorsqu'il n'y avait plus de codes et que 7f2737 a cessé d'apparaître, il a ensuite envoyé la clé pour écrire la zone.
Ce code d'erreur signifie que vous devez attendre un certain temps pour que la zone soit déverrouillée et cela se produit lorsque 7F2737 cesse d'apparaître et passe à une clé différente.
Exemple:
>6AD:68D
1003
222101
:ABFB:03:03 Réponse lors du déverrouillage de l'unité
7F2737
7F2737
7F2737
7F2737
7F2737
6704
2E2101XXXXX
Ceci n'est qu'un exemple pour comprendre le processus et ce n'est pas nécessairement votre cas, mais quand cela m'est arrivé, je n'ai eu qu'à attendre comme indiqué par le code d'erreur pour procéder à l'écriture de la zone.
J'espère que c'est compris avec la traduction.
 
Dernière édition:

I got this same code when unlocking my ESP even though the unlock key was correct and the process was as follows.
When unlocking the unit, the error code was generated several times and after several seconds it changed to a different key when there were no more codes and the 7f2737 stopped appearing and it proceeded to send the key to write the zone.
This error code means that you have to wait a while for the zone to be unlocked and this happens when the 7F2737 stops appearing and changes to a different key.
Example:
>6AD:68D
1003
222101
:ABFB:03:03 Response when unlocking the unit
7F2737
7F2737
7F2737
7F2737
7F2737
6704
2E2101XXXXX
This is just an example to understand the process and it doesn't have to be your case but when it has happened to me I have only had to wait as indicated by the error code to proceed to write the zone.
I hope it is understood with the translation.

J'ai reçu ce même code lors du déverrouillage de mon ESP bien que la clé de déverrouillage était correcte et que le processus était le suivant.
Lors du déverrouillage de l'unité, il a généré le code d'erreur à plusieurs reprises et après plusieurs secondes, il a changé pour une clé différente lorsqu'il n'y avait plus de codes et que 7f2737 a cessé d'apparaître, il a ensuite envoyé la clé pour écrire la zone.
Ce code d'erreur signifie que vous devez attendre un certain temps pour que la zone soit déverrouillée et cela se produit lorsque 7F2737 cesse d'apparaître et passe à une clé différente.
Exemple:
>6AD:68D
1003
222101
:ABFB:03:03 Réponse lors du déverrouillage de l'unité
7F2737
7F2737
7F2737
7F2737
7F2737
6704
2E2101XXXXX
Ceci n'est qu'un exemple pour comprendre le processus et ce n'est pas nécessairement votre cas, mais quand cela m'est arrivé, je n'ai eu qu'à attendre comme indiqué par le code d'erreur pour procéder à l'écriture de la zone.
J'espère que c'est compris avec la traduction.
attendre et essayer tout le temps jusqu'à ce que vous réussissiez? ou attendre le temps, puis se connecter à la voiture et essayer?
 

¿Esperar e intentar todo el tiempo hasta tener éxito? ¿O esperar el tiempo y luego conectarlo al coche e intentarlo?
¿Esperar e intentar todo el tiempo hasta tener éxito? ¿O esperar el tiempo y luego conectarlo al coche e intentarlo?
You connect to the car with YAT and start coding. When you enter the unlock code for your ECU, it will generate the code 7F2737 several times. I can't tell you how many times, but after a while this error should stop appearing and change to a different code. Then the numbers will stop moving and you have 5 seconds to enter the area to write.
This has been my case for several ECUs that generated this error.

Vous vous connectez à la voiture avec YAT et commencez à coder lorsque vous entrez la clé de déverrouillage de votre calculateur, cela générera le code 7F2737 plusieurs fois, je ne sais pas combien de fois mais après un moment cette erreur doit cesser d'apparaître et passer à une autre code différent, ils arrêteront de déplacer les chiffres et vous aurez 5 secondes pour entrer dans la zone à écrire.
Cela a été mon cas pour plusieurs calculateurs qui ont généré cette erreur.
 
Dernière édition:
  • J'aime
Reactions: disel

Добрый вечер, уважаемые форумчане! Перечитал несколько раз форум и решил, что все смогу сделать сам, естественно с помощью всех наработок команды Влуд. Но, к сожалению, все идет не так хорошо. Собрать Ардуино было несложно и вроде все заработало с первого раза, читает и пишет, но подключить камеру заднего вида не удалось, поэтому решил поменять калибровку 9692809780 на ту, что из репозитория 308_T9-9692810980. . кал. Но каждый раз, когда калибровка доходила до 3 из 100, на этом все останавливалось и загрузка не продолжалась. Мне пришлось выйти из приложения PSA-Arduino-NAC.exe. После всех этих действий калибровка не изменилась, но экран стал темным и клавиши не реагируют на нажатия, и регулятор громкости тоже не реагирует. Сенсорный экран и кнопки на руле работают. Я понимаю, что нужно изменить калибровку FMUX Zone 010E, но не знаю какую настроить. У меня большая просьба, если у кого-нибудь есть моя калибровка 9692809780 для ПКР А2, машина 308 SW T2 - 2018 года, дизель, поделитесь пожалуйста. Извините за перевод, я использовал Google. СПАСИБО.
 

Pièces jointes

  • 2024-11-04 132220.jpg
    2024-11-04 132220.jpg
    84.7 Ko · Affichages: 26
  • 173071.jpg
    173071.jpg
    675.1 Ko · Affichages: 27
  • 17307.jpg
    17307.jpg
    804.4 Ko · Affichages: 21
Dernière édition:

Подключите машину к коду. Когда вы вводите код разблокировки вашего ЭБУ, несколько раз сгенерируйте Обратите внимание на код 7F2737. Так что у вас не будет проблем, у вас не будет проблем. Вы можете переключиться на короткий код. Имя привязано к кнопке, название 5 секунд, на бюджете Отправлено вам в регион Ваписи.
Как только вы его оставили, вы его найдете, и вы его найдете.

Используйте клавиатуру, код вашего автомобиля, свой автомобиль имеет код 7f2737, его нет, его нет (другой другой код, нет связи). Обратите внимание, что есть изменение, но оно будет через 5 дней. ребенок.
Этот калькулятор вы видите в этом видео.
большой! Я наконец-то разблокировал свой cvm2. Большое спасибо!!! можешь рассказать мне больше? какие зоны нужно изменить в машине, чтобы включить автоматический дальний свет? и чтобы в меню появился режим движения (автомат на панели)?
 

Hi! Since i installed and activated the CMV2 camera i gen "Communication Error with Rain/Light sensor" in BSI.
My car has auto wipers and lights, but there was no sensor in the windshield (or at least i assume so, the car had a crash in the past).
Now the wipers go intermittently on auto, even if it's not raining.
As CVM is sharing the wires with the sensor, should i also install this? or is it just a coding thing?


1730809401740.png
 
Dernière édition:

Hi! Since i installed and activated the CMV2 camera i gen "Communication Error with Rain/Light sensor" in BSI.
My car has auto wipers and lights, but there was no sensor in the windshield (or at least i assume so, the car had a crash in the past).
Now the wipers go intermittently on auto, even if it's not raining.
As CVM is sharing the wires with the sensor, should i also install this? or is it just a coding thing?


Voir la pièce jointe 38833
You should have a light/rain sensor that can be mounted behind the support for the interior rearview mirror as this is independent of the CVM2. Check if you have it installed and that it is properly connected.

Vous devez disposer d'un capteur de lumière/pluie qui peut être monté derrière le support du rétroviseur intérieur car celui-ci est indépendant du CVM2, voyez si vous l'avez installé et qu'il est bien connecté
 

Bonsoir, chers utilisateurs du forum ! J'ai relu le forum plusieurs fois et j'ai décidé que je pouvais tout faire moi-même, naturellement avec l'aide de tous les développements de l'équipe Vlud. Mais malheureusement, tout ne va pas si bien. Ce n'était pas difficile d'assembler l'Arduino et tout semblait fonctionner du premier coup, il lit et écrit, mais je n'ai pas pu connecter la caméra de recul, j'ai donc décidé de changer le calibrage 9692809780 par celui du référentiel 308_T9-9692810980 . cal. Mais à chaque fois que la calibration atteignait 3 sur 100, tout s'arrêtait là et le téléchargement ne poursuivait pas. J'ai dû quitter l'application PSA-Arduino-NAC.exe. Après toutes ces étapes, le calibrage n'a pas changé, mais l'écran est devenu sombre et les touches ne répondent pas à l'appui, et le contrôle du volume ne répond pas non plus. L'écran tactile et les boutons du volant fonctionnent. Je comprends que je dois changer le calibrage du FMUX Zone 010E, mais je ne sais pas lequel régler. J'ai une grosse demande, si quelqu'un a mon calibrage 9692809780 pour RCC A2, voiture 308 SW T2 - 2018, diesel, merci de partager. Désolé pour la traduction, j'ai utilisé Google. MERCI.
Your screen has gone dark due to a failure when loading the calibration, load another calibration until one of the RCC ones works, it doesn't matter which one it is and which model it is. When you manage to load an RCC calibration, the screen will work again.
Try with the other one 308_T9-9692809680.cal. If that doesn't work either, try with any one from the repository, even if it's from another vehicle.
Another question, does the equipment allow you to read the parameters according to the current state?

Votre écran est devenu sombre en raison d'un échec lors du chargement de l'étalonnage, chargez un autre étalonnage jusqu'à ce que l'un des étalonnages RCC fonctionne pour vous, peu importe de quoi il s'agit et de quel modèle il s'agit. Lorsque vous parvenez à charger un étalonnage RCC, l'écran fonctionnera à nouveau.
Essayez-le avec l'autre 308_T9-9692809680.cal. Si cela ne fonctionne pas non plus, essayez-le avec n'importe quel référentiel, même s'il provient d'un autre véhicule.
Une autre question permet de déterminer comment l'équipement lit les paramètres.
 

You should have a light/rain sensor that can be mounted behind the support for the interior rearview mirror as this is independent of the CVM2. Check if you have it installed and that it is properly connected.

Vous devez disposer d'un capteur de lumière/pluie qui peut être monté derrière le support du rétroviseur intérieur car celui-ci est indépendant du CVM2, voyez si vous l'avez installé et qu'il est bien connecté

There is none. I had nothing around the interior rear view mirror before i installed the CVM. There was no wires in that area either.

Until now i thought this was the light & rain sensor (dont even know what it is anymore):
1730828726186.png
 

Hello/Salut @jeverds

I have a 2008II diesel, EAT8 MY2020 (Wave4 NAC/I-cockpit 3D/CVM3 most likely) where I was able to enable all the menus in NAC that need no BSI or other ECU configuration (i.e. i-cockpit amplify, additional themes, TPMS menu, Diagnostics menu, trip/fuel consumption menu). So far so good, but now I want to enable the grip control and the HBA and I'm thinking of using as a base for my "experiments" the codes shared by @Jlozde here but I need some guidance from someone that has done it already. From your experience, is it necessary to use YAT or other terminal supporting macros in order to pass the codes ? Do you by any chance have any clue on which coding should I use in order to enable HBA and Grip control on my car ?

Thanks in advance for your help.
Nikolas
 

Your screen has gone dark due to a failure when loading the calibration, load another calibration until one of the RCC ones works, it doesn't matter which one it is and which model it is. When you manage to load an RCC calibration, the screen will work again.
Try with the other one 308_T9-9692809680.cal. If that doesn't work either, try with any one from the repository, even if it's from another vehicle.
Another question, does the equipment allow you to read the parameters according to the current state?
Good evening, Jeverds! Thank you for your reply. Yes, I can read the parameters of both Arduino and Digibox. I know that I need to try other calibrations, but I don't want to lose the configurations, or more precisely such functions as SAM (blind spot monitoring), AAS (parking assistance), MPD (measuring available space), Android Auto and others. Earlier in the forum I watched how people struggled with the inclusion of these functions in BSI, AAS. I thought that if the calibration number is higher than mine, then all these functions are already enabled a priori. Another option is to return the calibration using Digibox, but I really don't know yet how to do this safely. But in any case, thank you, I will try other calibrations.
 
Dernière édition:

Good evening, Jeverds! Thank you for your reply. Yes, I can read the parameters of both Arduino and Digibox. I know that I need to try other calibrations, but I don't want to lose the configurations, or more precisely such functions as SAM (blind spot monitoring), AAS (parking assistance), MPD (measuring available space), Android Auto and others. Earlier in the forum I watched how people struggled with the inclusion of these functions in BSI, AAS. I thought that if the calibration number is higher than mine, then all these functions are already enabled a priori. Another option is to return the calibration using Digibox, but I really don't know yet how to do this safely. But in any case, thank you, I will try other calibrations.
Try to backup your settings and then restore to your new calibration, you will keep everything the same unless the new calibration does not support some of your zones in which case you would have to delete that zone from the configuration file and load it again. The calibration of the NAC or RCC does not change anything in the BSI or other units. It will change the 010E zone if you use a calibration from another vehicle but you can always extract yours before touching anything with YAT and then write it back to your new calibration.
 
Dernière édition:

Hello/Salut @jeverds

I have a 2008II diesel, EAT8 MY2020 (Wave4 NAC/I-cockpit 3D/CVM3 most likely) where I was able to enable all the menus in NAC that need no BSI or other ECU configuration (i.e. i-cockpit amplify, additional themes, TPMS menu, Diagnostics menu, trip/fuel consumption menu). So far so good, but now I want to enable the grip control and the HBA and I'm thinking of using as a base for my "experiments" the codes shared by @Jlozde here but I need some guidance from someone that has done it already. From your experience, is it necessary to use YAT or other terminal supporting macros in order to pass the codes ? Do you by any chance have any clue on which coding should I use in order to enable HBA and Grip control on my car ?

Thanks in advance for your help.
Nikolas
It is imperative that you use YAT because it is the easiest way. The examples you provide are good for you to investigate what works or not for you, another thing you need to know is if your car uses a wheel or a button for the grip control and how it connects to the BSI for which you will need the diagrams for your car.
As for the values to modify in the zones or unlocking key, it will depend on the ESP and the type of control for the grip control that your car uses.
 

There is none. I had nothing around the interior rear view mirror before i installed the CVM. There was no wires in that area either.

Until now i thought this was the light & rain sensor (dont even know what it is anymore):
Voir la pièce jointe 38834
The sensor in the photo is for the air conditioner normally.
Before mounting CVM2 your car mounted another CVM
 
Dernière édition:
  • J'aime
Reactions: weirdcactus

Try to backup your settings and then restore to your new calibration, you will keep everything the same unless the new calibration does not support some of your zones in which case you would have to delete that zone from the configuration file and load it again. The calibration of the NAC or RCC does not change anything in the BSI or other units. It will change the 010E zone if you use a calibration from another vehicle but you can always extract yours before touching anything with YAT and then write it back to your new calibration.
Good day, Jeverds! Thank you again. Did I understand correctly that before loading a new calibration I should save my configuration? I did it, but it is not the factory one, I lost the factory one when I had to reinstall Windows, the hard drive had to be changed on the laptop. Therefore, the last one was saved, before installing the calibration. YAT never got used, I'll see how everything works. It may be necessary to make copies of the values in different zones before setting the calibration?
 

Hi @jeverds

thanks for your reply, I appreciate it.

well, as far as I know my car has ESP90 (some posts above a user with the same car as mine confirmed it), as for the unlocking keys, it's all in @VLud Git despite that I see there are some discrepancies using them but anyway, I believe it's all a matter of synchronization (a small delay in command input can cause such issues that's why YAT is a must as you confirmed).

My car has the button depicted in the attached image and I think that @Jlozde has provided the commands for each type of button/wheel concerning the Grip control. Is it possible for you to check and double confirm my allegations ? I mean, two pairs of eyes (and brains) are always preferable in such kind of things
:)

iu
 

Hi @jeverds

thanks for your reply, I appreciate it.

well, as far as I know my car has ESP90 (some posts above a user with the same car as mine confirmed it), as for the unlocking keys, it's all in @VLud Git despite that I see there are some discrepancies using them but anyway, I believe it's all a matter of synchronization (a small delay in command input can cause such issues that's why YAT is a must as you confirmed).

My car has the button depicted in the attached image and I think that @Jlozde has provided the commands for each type of button/wheel concerning the Grip control. Is it possible for you to check and double confirm my allegations ? I mean, two pairs of eyes (and brains) are always preferable in such kind of things
:)

iu
As for the unlocking key, you'll have to try. My car has ESP90 and I had to use the ESP81 key.
As for the button, it's correct that in the example files you have both types of buttons (wheel and push button).
Now all you need is the diagram to connect it to the BSI and modify the other areas to activate the push button, if your car doesn't have the original installation.
 

Good day, Jeverds! Thank you again. Did I understand correctly that before loading a new calibration I should save my configuration? I did it, but it is not the factory one, I lost the factory one when I had to reinstall Windows, the hard drive had to be changed on the laptop. Therefore, the last one was saved, before installing the calibration. YAT never got used, I'll see how everything works. It may be necessary to make copies of the values in different zones before setting the calibration?
Don't complicate things because it's very simple. Get a backup of what you have right now. Look for a calibration that recovers the unit and if the settings are not as before, enter them manually or load a configuration from those in the repository to start.
Even if you tried to change the calibration, it still has the same one inside the unit but with an error, so if you want to get the 010E zone (which is in case you have to use the calibration of another vehicle and the buttons don't work for you) you can do it with YAT and then apply it to another calibration in case none of those that correspond to your car model work for you. The copy of the configuration should be the same since you haven't changed the calibration. Example for zone 010E, I have a NAC WAVE 4 HD in a vehicle that used RCC 1 and as there is no NAC WAVE4 calibration for this model I used another one and configured it to my needs but before changing the RCC I obtained zone 010E and then loaded it with YAT in my NAC WAVE4. There is also a WEB page to create your 010E zone to suit your needs.
If you have only tried to load a calibration once over the original and the error occurred you should not have any problems recovering it.
 
Dernière édition:

As for the unlocking key, you'll have to try. My car has ESP90 and I had to use the ESP81 key.
As for the button, it's correct that in the example files you have both types of buttons (wheel and push button).
Now all you need is the diagram to connect it to the BSI and modify the other areas to activate the push button, if your car doesn't have the original installation.
Thanks again for your reply @jeverds

just to clarify, I didn't retrofit anything to my car. Everything is there from the factory. I just need to try different codings till I find the one that enables the Grip and HBA.
 

Don't complicate things because it's very simple. Get a backup of what you have right now. Look for a calibration that recovers the unit and if the settings are not as before, enter them manually or load a configuration from those in the repository to start.
If you have only tried to load a calibration once over the original and the error occurred you should not have any problems recovering it.
Ok, thanks for the info. I am indeed overcomplicating things. But I need time to figure out YAT, so I will try with Arduino.exe. In fact, I tried to load this calibration 3 times. Now the 010E zone is empty, without parameters. I thought to try to generate data using this program https://afululu.com/PSA/010E/ and upload it to the RCC, Thanks again
 

Good evening, dear Jeverds! Yesterday and today I tried to install various RCC calibrations, but the same result "ERROR. Calibration file invalid". I don't understand what's going on, everything seems to work, but I can't install the calibration. The file extension is correct - .cal. What should I do?
 

Pièces jointes

  • 509.jpg
    509.jpg
    691.4 Ko · Affichages: 23
  • 546.jpg
    546.jpg
    711.4 Ko · Affichages: 25