]> 2026-05-26T15:08:20+02:00 Placing a TwinCAT3 Machine Under Source Control 0 en Draft Changing the directory structure to allow a PC used for PLC code editing to sync with the source code version control system Medium 30 minute(s) <div class="icon-instructions caution-icon"> <div class="icon-instructions-icon"><i class="fa fa-exclamation-triangle"></i></div> <div class="icon-instructions-text">...Note - This dokit is now obsolete - the sourcetree system has been replaced by the internal one in TcXAEShell</div> </div> Click [https://stuga.dokit.app/wiki/Changing_Version_Control_to_Visual_Studio here] for the latest procedure 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 because 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 [https://www.atlassian.com/git/tutorials/what-is-version-control Click here] for an introduction to version control using Git This tutorial is a step by step guide to setting up an existing machine or diagnostic PC to a standard uses on all Stuga machines to enable quick, easy and stress free version control. false en Installing_SourceTree_Version_Control_Software_Annotation_2020-02-01_125845.jpg none See this tutorial for backing up (archiving) a TwinCAT3 project 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 <br/> Remove the version numbers at the end In the Project folder for the machine, delete tc3Multi and PLC_Reset folder <div class="icon-instructions info-icon"> <div class="icon-instructions-icon"><i class="fa fa-info-circle"></i></div> <div class="icon-instructions-text">...These folders now reside in the versionControl folder</div> </div><br/> This will get the latest file versions from the cloud of tcMulti and PLC_Reset and copy into PLC_Reset and tc3Multi folders #Open the machine's standard Visual Studio project file #Right click on tc3Multi_and select Change Project #Navigate to the versionControl folder\tc3Multi #Select Use Original Project Location #Repeat for PLC_Reset <div class="icon-instructions pin-icon"> <div class="icon-instructions-icon"><i class="fa fa-thumb-tack"></i></div> <div class="icon-instructions-text">...Following this method will keep the io links in the project</div> </div><br/> See this [https://stuga.dokit.app/wiki/Installing_SourceTree_Version_Control_Software tutorial] for installation instructions <br/> Backup the Old Project Install Sourcetree on the PC Clone the tcMulti repository Pull the latest tcMulti Projects Change the PLC Projects to versionControl Rename tcMulti and PLC_Reset Check the IO Links still Exist Activate Configuration Delete the Old PLC Projects Sourcetree version control 2022-03-21T10:07:19Z 2459659.9217477 Placing a TwinCAT3 Machine Under Source Control 0 false false 0 0 0 1 plainlist 3 [[:Dokit:DocOptions]] [[DokitEPIEnable::yes]] Placing a TwinCAT3 Machine Under Source Control# QUERYee7a61aae48f1c3f91d8e4d7736360be