Changing the directory structure to allow a PC used for PLC code editing to sync with the source code version control system
Auteur Gareth Green | Dernière modification 21/03/2022 par Gareth Green en cours de rédaction ⧼frevu-button-review-label⧽
Pas encore d'image
Changing the directory structure to allow a PC used for PLC code editing to sync with the source code version control system
For many years, the source code for the PLCs has resided on the G:\drive and then a copy on each and every one of the PCs used to edit the code, so at least one on each machine. This is a recipe for disaster because maintaining all the copies and version numbers is incredibly difficult and adds a lot of time overhead to fixes and changes. This has worked becasue there has been only one developer, but this is set to change in future as more programmers will be trained and tracking versions becomes more difficult
From 2020, the PLC code version control has been improved by using an industry standard source control system called "Git" along with "BitBucket" to store the PLC code in the cloud. The program "SourceTree" is used to commit, push and pull the changes
Click here for an introduction to version control using Git
See this tutorial for backing up (archiving) a TwinCAT3 project
See this tutorial for installation instructions
Clone the online repository to a new local directory c:\TwinCAT\stuga\versionControl
Check success by navigating to the folder - there should be 2 folders
PLC_Reset
tc3Multi
This will get the latest file versions from the cloud of tcMulti and PLC_Reset and copy into PLC_Reset and tc3Multi
en none 0 Draft
Vous avez entré un nom de page invalide, avec un ou plusieurs caractères suivants :
< > @ ~ : * € £ ` + = / \ | [ ] { } ; ? #