The development files are stored both in the cloud repository and on the development PCs. So what are some of the advantages of using version control?įirst, it protects our codebase to ensure that we don’t lose any of our changes as we’re working. And the latest version of the file becomes the second commit.Īnyone looking at the repository can see what the changes were between the first and second commits.Īll PCs can then “Pull” the latest commit and continue developing from the updated file. If another developer has a change to make to the files, they can then “push” to the repository with their updated file. Other people working on my project can view and “clone” the repository to edit the files on their own PCs. Version control allows me to place, or “commit”, my file in a cloud storage area called a repository. Let’s start by looking at a simple example.

That gets a little bit tricky for us PLC programmers, who use graphical programming languages, but I’ll go into more detail on that later. Now, usually, people think of version control as tracking text based programming languages where their development files can be opened and read by a text editor, like Notepad. Let’s get started! At a high level, Version Control is how we track software development on both our local PCs and on an external server, which is typically the Cloud.

I’ll start by talking about what version control means for software development, and then I’ll dive into how you can apply it to your Siemens TIA Portal development workflow. Today I’m going to look at Siemens Version Control Interface, or “VCI” in TIA Portal. Hi and welcome! I’m Liz, co-founder of Outlier Automation, a Control Systems Integrator.

Simatic key installer