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

Thank you so much @Hallahub, you helped me to enable it in my e-208 (a small typo in your message 2306 (alarm volumetric) 00 = (Yes)No 01 = (no) Yes).

I can’t change the value in 23D1 zone.

do you know if we can enable the pork assist option on e-208 ?

At first I’ve used diagbox to enable the alarm but I was having some issue since at that time the siren was not installed as I had to change it’s internal battery. When the diagbox token expired, I enabled it again using arduino console, 23D1 was not a problem for me.
Regarding park assist, we already spent some time about it in the previous pages, you can have a try only it your car is equipped with 12 sensors. In this case diagbox is mandatory to perform an auto coding of AAS and DAE. The rest of the ECUs such as NAC and BSI can be modified using arduino.
I’ve done this on my 208, but I don’t have the electric version, I hope this won’t cause any issue since as far as I remember Peugeot doesn’t offers park assist on electric cars.
 

I will try another time for the 23D1 zone.

yes I already asked for the park assist, and did some change on my 2008, but I haven’t diagbox and As you said without it it’s impossible (or very difficult). I only want to know if it’s possible on electric cars also or not.
 

@VLud, thanks for your help I resolved some issues :).

[QUOTE = "VLud, post: 2652298, member: 108646"] Make sure "Blackpanel" is enabled in 2126
[/ QUOTE]

- I tried this option but doesent work.

I have those new questions:
  • The steering wheel "back button" doesen't work
    s-l1600.jpg
  • The bip sounds about the rear and front parking sensors does not appear to be directional but it sounds on all speakers at same time. On my old smeg the bit happens on the respective speaker directions. I have 12 sensors in total.
  • The rear camera does not have the right picture framing, I already tried change it to 180degree and put other configurations on the 212A but it doesn't change anything. I have this:
    IMG_20200519_184149.jpg
  • Do you have any tip to enable the Tomtom Connected services like speedcams?
Thanks again for all greak work.
 

I have to check something for blackpanel (related to calib also)

  • No back button on 508 I with NAC so same: don't expect it to work with NAC
  • No idea
  • What is the issue ? 212A is for Visiopark 1 not 130°, no idea for 130° nor Wave2 at the moment.
  • No donor VIN to pay services = no services
 

What is the issue ? 212A is for Visiopark 1 not 130°, no idea for 130° nor Wave2 at the moment.

The rear camera resolution and frame is not like I had on smeg, it misses image on the top and the plate were less visible, its like the image frame is moved down and zoomed.

REgarding the parking sensor bips, there is any register I can play to try tune?
 

Bonjour à tous, j'ai une bonne nouvelle pour ceux qui ont des soucis de zone d'affichage de la caméra (au moins sur Wave3 ou Wave4)

J'ai enfin trouvé comment faire prendre en compte la zone 212A après avoir bidouillé pendant des heures ! (Car même un changement complet de calibration - sauf cas particulier lié à la zone 012A - ne suffit pas à vider le cache du NAC pour le Visiopark)

J'ai enfin un affichage correct de la caméra sur mon Wave3/4 SD :chinois:

Voici la méthode (à effectuer en mode console)

Prérequis : Calibration CUSTOM Wave4 - 012A = 01 = OLD VP1

Changement du paramètre en zone 012A Calibration_Fct_VP1_HW (00 = NEW VP1)
Code:
>764:664
:D91C:03:03
2E012A00
1103

Attendre le redémarrage

Remise en place du paramètre initial en zone 012A Calibration_Fct_VP1_HW (01 = OLD VP1)
Code:
>764:664
:D91C:03:03
2E012A01
1103

Attendre le redémarrage, la modification de la zone 212A est prise en compte et la vue change :bien:

Les redémarrages via 1103 ne sont pas obligatoires mais recommandés

Pour ceux qui ont un problème d'affichage sur un Wave2, il est possible d'essayer de mettre à jour le firmware du NAC après avoir modifié la zone 212A - plus contraignant pour simplement vider le cache du Visiopark -

----

Hello everyone, I have good news for those who have problems with the display area of the camera (at least on Wave3 or Wave4)

I finally figured out how to get 212A zone taken into account after "playing" for hours ! (Because even a complete change of calibration - except in particular cases linked to zone 012A - is not enough to empty the cache of the NAC for the Visiopark)

I finally have a correct display of the camera on my Wave3/4 SD :chinois:

Here is the method (to be done in console mode)

Prerequisites : Calibration CUSTOM Wave4 - 012A = 01 = OLD VP1

Parameter change in zone 012A Calibration_Fct_VP1_HW (00 = NEW VP1)
Code:
>764:664
2E012A00
1103

Wait for the reboot

Reinstallation of the initial parameter in zone 012A Calibration_Fct_VP1_HW (01 = OLD VP1)
Code:
>764:664
2E012A01
1103

Wait for the reboot, 212A zone modification is taken into account and the view changes :bien:

Reboots via 1103 might not be mandatory but are recommended.

For people having a display problem on a Wave2, it is possible to try to update the firmware of the NAC after modifying zone 212A - quite annoying way to flush the Visiopark cache -

----

212A ProAce (0AE50BB803970708014A070802DB03EB08E30205080402060672800102C00000D000D0646400006464):
rnzbCMB.jpg

212A 308 Wave2 (0EF40BF30320070801E7070802C8026C065402560804020608028028021F0001FA0063646400006464):
lNaQ5Zq.jpg

212A C5 Aircross :bien: (0DFF0BF30367070801C2070802FF02BF06C202510804020807D0800102560000320000646400006464):
aVLB7a9.jpg

Hello Vlud, thank you for your incredible work on arduino and nac. Iv'e changed my screen on my peugeot 3008 to a 10" including a new nac wave 4 with a custom calibration. Everything is working great but the rear camera, which is not showing the correct image.
Iv'e been following your recent discovery with finding out how to write to the 212A zone to correct the camera.
I added the C5 calibration to the code as you provided using the following command:
Before entering the code I followed your guide on reinstalling the initial parameters in 212A
2E212A0DFF0BF30367070801C2070802FF02BF06C202510804020807D0800102560000320000646400006464
After writing this command I did:
2E012A01
And did a reboot
But upon restart of the nac I don't see any change of the camera view, iv'e tried your other calibrations as well, just to see if it changed anything on the image but nothing.

Do you have any idea on what might be wrong?
Thank you in advance for your help.
 

You didn't make the procedure correctly.

Simplier procedure without any reboot:
  • Change 212A value (by soft or console)
  • Read the current value 22012A, if 00 write 01 or if 01 write 00
Code:
:D91C:03:03
2E012AXX
  • Stop diagnostic session with 1001
  • Put the reverse gear (the image changed)
  • Rewrite the original value of 012A
  • Stop diagnostic session with 1001
  • Put the reverse gear (the image changed)
 
  • J'aime
Reactions: Francesco Ratta

You didn't make the procedure correctly.

Simplier procedure without any reboot:
  • Change 212A value (by soft or console)
  • Read the current value 22012A, if 00 write 01 or if 01 write 00
Code:
:D91C:03:03
2E012AXX
  • Stop diagnostic session with 1001
  • Put the reverse gear (the image changed)
  • Rewrite the original value of 012A
  • Stop diagnostic session with 1001
  • Put the reverse gear (the image changed)

So basically it’s the value of 22012A (00 or 01) that determines wether the nac accepts the values in 212A correct?

I will try the procedure and let you, and everyone else know how it went.
Thank you for your help, appreciating it a lot.
 
Dernière édition:

Changing the value of 012A to something else refreshes the 212A cache and changes the image, 012A settings also provide two different possible images for the same 212A.
 
  • J'aime
Reactions: Francesco Ratta

Changing the value of 012A to something else refreshes the 212A cache and changes the image, 012A settings also provide two different possible images for the same 212A.

That’s a great discovery!
I might be able to get access to a new 3008 face lifted with the 10” screen and wave 4.
In that way I can extract the parameters of 212A from that one and upload it to my Nac, and in theory then the image should be 100% correct right?
If that is the case, then I am willing to share the values with you guys here, I am sure there are other people like me, who changed their nac wave 2 to wave 4 with the 10” screen. :)
 



3008_RESTYLED-9694684380.cal

is already the official calibration for Wave4 10"

Thank you so much Vlud, I've been looking for a calibration for the restyled 3008, when I changed to the new wave4 I ended up with uploading a custom calibration to it, because the one you supplied here in this thread was for the wave 2 model.
You should add it to the list you have in the first page of this thread. :)

Thank you again, I will report back with the results of everything and maybe also some picture of the result. :)

Bon weekend :)
 

Changing the value of 012A to something else refreshes the 212A cache and changes the image, 012A settings also provide two different possible images for the same 212A.
Can this also be done in RCC A2? While trying to execute these instructions (... 2E012A01), I get a 7F2E31 reply. Is there any other known way to clear this cache? Please help.
 

Ok here’s the update from my 3008 which got upgraded from the old 8” screen with a wave 2 to a 10” with a wave 4.
I uploaded the calibration file and updated the 212A value with the new restyled one.
Did the steps as instructed by Vlud and the camera image is now fixed! :)
Thank you Vlud for the help.

I do have ONE last little problem, that I hope you can help with in some way.

Beside the camera problem, I also had problem with echoing when calling from the car.
I read before in the forum that this was due to a wrong calibration, and since I’ve been running a custom calibration I thought, it must be because the calibration is wrong.
So since Vlud just posted the calibration for the new restyled 3008, I was hoping that it would finally fix that problem as well.
But unfortunately that was not the case, the problem is still there.
So I got curious, and examined the file provided by Vlud and my custom calibration file, and they are identical. So I guess that this calibration is an adapted version but not the Real one extracted from a restyled 3008.

If I got access to a new 3008 restyled, what would it take to extract the calibration from that? I couldn’t seem to find the steps required with arduino to extract it from it.

What are your inputs? Do you think it will fix my problem if I get the “real” calibration?
In theory it should right?

Thank you in advance.
 



Bonjour à tous,

Je vais prochainement rejoindre la grande famille des possesseurs de SMEG qui passent au NAC.
Pour ma part ce sera sur une DS4 que j'ai depuis près d'un mois.

Merci à Vlud et à tous les contributeurs pour leur boulot incroyable.

J'ai parcouru (c'était long !) les 95 pages du topic mais n'ai pas trouvé de réponse à ma question (concernant la carte CAN-BUS et la résistance de 120 Ohm).

J'ai vu à plusieurs reprises et sur plusieurs modèles de cartes des personnes qui ajoutent la résistance sur les 2 PIN "CAN H" et "CAN L" mais qui utilisent malgré tout le port DB9.
J'avoue que je n'arrive pas à comprendre pourquoi. Est-ce obligatoire ?

Pour ma part j'envisage d'utiliser des connecteurs dupont et de souder une résistance entre mes 2 fils (ma prise OBD2 est sans connecteur au bout, juste les fils) pour éviter d'avoir à monter un connecteur DB9.

Est-ce que ça va fonctionner en me piquant directement sur les 2 PIN ?
Autre question, est-ce qu'une résistance 1/4w convient ?

La carte que j'ai commandé est la même que celle ci-dessous (photo de Jordan63 qui a d'ailleurs soudé la résistance mais utilisé le port DB9).

Merci à tous.
full

20210216_131124.2083
 

Bonjour Xs21

La résistance n'est pas obligatoire, mais recommandé, avec la même carte j'ai directement connecté les 2 fils sur "CAN H" et "CAN L" au dessus sans passé par le port DB9 et sans mettre la résistance et pour mon cas ça a quand même marché

Il faudrait déjà tester sans, et si ça ne marche pas, il faudra ressayer avec une résistance .
 

Hello @Xs21
I also have the same Keyestudio CAN-Bus shield and it works perfectly.
I ordered the DB9 connector with the screw terminal and the prefabricated OBD plug with 30 cm cable.
This is the most stable solution for me. Definitely much better than putting blank wires in the car OBD terminal. It will cost you less than 5€ (links below).
The 120 Ohm resistor is really needed for stable connection. I screwed it directly to the DB9 plug together with the wires from OBD.
No soldering needed :)
Note that the DB9 layout is completely different as on the picture in the tutorial - CAN-L is pin 2 and CAN-H is pin 7.

https://fr.aliexpress.com/item/1005001479655952.html?spm=a2g0s.9042311.0.0.27424c4dOZzmvT
https://fr.aliexpress.com/item/32676383706.html?spm=a2g0s.9042311.0.0.27424c4dOZzmvT

20211129_154912.jpg
.
20211129_155100.jpg
 


  • The bip sounds about the rear and front parking sensors does not appear to be directional but it sounds on all speakers at same time. On my old smeg the bit happens on the respective speaker directions. I have 12 sensors in total
 

Il faut mettre 4 avants 4 arrières les 4 autres servent aux capteurs d'angles morts. Ja aïs le même problème et depuis tout remarche comme avant par zone..[/QUOTE]
 


Hallahub, where do you find such info? Where could I get smth like that for a whole BSI?

Yes I enabled it myself, those are the zones of BSI:
  • 2305 (alarm mounting type) 00 = factory alarm 01= aftermarket
  • 2306 (alarm volumetric) 00 = Yes 01 = no
  • 2309 (alarm type) 00 = no alarm 01 = standard alarm 02= belgium alarm and so on
  • 23D1 (anti rising function) 00=no 01 = yes
  • 240E (alarm architecture) I don’t know what is
  • 23B6 (presence of alarm ecu over LIN) 00 = no 01 = yes
  • 23B7 (siren presence over LIN) 00 = no 01 = yes
  • 2365 (thatcham mode) 00=no 01 = yes
 


Hello, I have uploaded to my RCC A2 the calibration file 308_T9-9692810980.cal from the first page of this topic (and from GitHub). It seems inappropriate. The volume knob and the buttons next to the screen do not work. There is, however, a new menu (The menu looks like in 208) that appears after touching with three fingers. VisioPark1 also does not work despite running in zones 2105. Is the correct file available or what am I doing wrong? and only one language is available.
 
Dernière édition:

Hello, I have uploaded to my RCC A2 the calibration file 308_T9-9692810980.cal from the first page of this topic (and from GitHub). It seems inappropriate. The volume knob and the buttons next to the screen do not work. There is, however, a new menu (The menu looks like in 208) that appears after touching with three fingers. VisioPark1 also does not work despite running in zones 2105. Is the correct file available or what am I doing wrong? and only one language is available.


Hello, the configuration file must also be changed in addition to the calibration file adapted to your car
 

Hello, the configuration file must also be changed in addition to the calibration file adapted to your car
Thanks for the answer. After uploading the .cal file, I did a parameter restore from the .nac file. Is there anything else I should upload or set because the effect is as described.
 

@marop : Instead of saying calibrations / configurations are wrong you forgot to say that you made your own mess with a custom calibration (peugeotklub.pl)

RCCs don't have the same zones (calibration), as told earlier : ONLY W3/4 NACs can be fixed for now.