# PP45 calibration **URL:** \ **Category:** HMI & Visualization\ **Tags:** power-panel, vc4\ **Created:** [March 12, 2025, 7:17am UTC](https://community.br-automation.com/t/pp45-calibration/6189 "2025-03-12T07:17:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Matjaz\_Kopac](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Matjaz\_Kopac](https://community.br-automation.com/u/Matjaz_Kopac)\ **Post date:** [March 12, 2025, 7:17am UTC](https://community.br-automation.com/t/pp45-calibration/6189/1 "2025-03-12T07:17:41Z")
Hello, Is it possible to calibrate touch panel PP45 if this option was not provided by developer? Thank you ---
**Author:** ![patrik.simcik](https://avatars.discourse-cdn.com/v4/letter/p/FF8800/32.png) [@patrik.simcik](https://community.br-automation.com/u/patrik.simcik)\ **Post date:** [March 12, 2025, 12:28pm UTC](https://community.br-automation.com/t/pp45-calibration/6189/2 "2025-03-12T12:28:59Z")
Hello @Matjaz_Kopac , Here is the possibility how to manually recalibrate the touchscreen. RUC/PVI Transfer: 1. Create a dummy project to calibrate the target 2. Connect to the target 3. Upload the “good” Calibration Data to the RUC (“vcdata.br” on older VC Versions, on newer versions the data is stored in “VisuHW.br”) 4. Start the Target with the Original project 5. Connect to the target and overwrite the vcdata.br or VisuHW.br file with the previously uploaded dummy one But if you/your customer observed a touch issue, it also could be that it is caused by the change in resistance and this hw problem you can usually not fix with the re-calibration anyhow. ---
**Author:** ![Matjaz\_Kopac](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Matjaz\_Kopac](https://community.br-automation.com/u/Matjaz_Kopac)\ **Post date:** [March 13, 2025, 8:34am UTC](https://community.br-automation.com/t/pp45-calibration/6189/3 "2025-03-13T08:34:10Z")
Hello, Thank you for this information. Two more questions regarding this procedure: - Just to confirm, if I understood correctly: When the calibration is done, file vcdata.br (or VisuHW.br) on the PLC is overwritten with new settings? - Do we need exactly the same version of AS as it was used for original application? ---
**Author:** ![patrik.simcik](https://avatars.discourse-cdn.com/v4/letter/p/FF8800/32.png) [@patrik.simcik](https://community.br-automation.com/u/patrik.simcik)\ **Post date:** [March 17, 2025, 12:20pm UTC](https://community.br-automation.com/t/pp45-calibration/6189/4 "2025-03-17T12:20:15Z")
Hello, Depending on the VC4 version, the calibration will be on different locations. Originally the calibration data was stored in the device´s internal flash memory. vcdata.dat for VC4 and user\_tcal.txt for VC3. If the calibration is done with a VC4 object, both files are created on drive B:, which is the drive letter for the internal memory. If its done with a VC3 object, just user\_tcal.txt is created. Since AS 2.6 the calibration data from VC4 objects are stored in the vcdata.br dataobject, which is located in the USRROM. Its possible to treat this module like a dataobject. With AS 2.6 and VC3 the file Tcal.dat is created on the CF in the folder RPSHD\VCDATA after calibration. Hence the calibration data are stored on the Compact Flash in both cases. In earlier versions (prior to VC 4.14.1) the calibration is being stored in a B&R Datamodule called “vcdata”, so you’d find it in Software Comparison view of Automation Studio under node “Data Objects”. In newer VC Runtime versions (beginning with VCRT 4.15.0), the name of the datamodule has been changed to be able to support more than 1 visualization on one target (e.g. for VNC server targets). The name consist now of the VC project name + “HW”, so if the name of the visu is “Vis”, then the calibration data object name is “VisHW”. If there is VC4, you can calibrate the screen with a different project using the same VC4 version then upload the vcdata.br and then download the calibration to the running target using Runtime Utility Center. ---
**Author:** ![system](https://europe1.discourse-cdn.com/brcommunity/original/1X/a202d64f0f03e22a662ed33fbbca6879f1efb794.jpeg) [@system](https://community.br-automation.com/u/system)\ **Post date:** [May 9, 2025, 12:42pm UTC](https://community.br-automation.com/t/pp45-calibration/6189/5 "2025-05-09T12:42:19Z")
---
**Author:** ![ZOUHAIIR](https://avatars.discourse-cdn.com/v4/letter/z/FF8800/32.png) [@ZOUHAIIR](https://community.br-automation.com/u/ZOUHAIIR)\ **Post date:** [May 26, 2025, 7:22am UTC](https://community.br-automation.com/t/pp45-calibration/6189/6 "2025-05-26T07:22:55Z")
J’ai rencontré le même un problème de calibrage avec un PP420 Le programme d’origine contient bien un bouton de calibrage mais il est impossible d’y accéder car l’écran tactile est totalement décalé Les données de calibrage sont créées et enregistrées dans un fichier nommé **vcdata.dat** Voici les solutions que j’ai trouvées : 1. Supprimer le fichier `vcdata.dat` situé sur la partition système.\*\* (⚠ Pensez à effectuer une sauvegarde complète de la carte au préalable à l’aide du Runtime Utility Center) Au redémarrage l’écran se recalibrera automatiquement. 2. Créer un programme de calibrage sur une carte vierge et effectuer le calibrage.\*\* Cela générera un fichier `vcdata.dat` sur cette carte. Il suffira ensuite de copier ce fichier et de le remplacer sur la carte d’origine