New Team sync: Git history built right into CodeShuttle →

Your TIA project.
Finally versioned.

CodeShuttle is Git version control for Siemens TIA Portal: it turns blocks, data types, tag tables and HMI objects into readable text files and keeps both sides in sync. You see every change line by line, know who changed what and when, and can bring back any earlier state. No Git skills required – for TIA Portal V14 SP1 through V21.

Book a discovery call How it works

Free and with no obligation – or by email: codeshuttle@igrf.de

Nothing without your preview
No Git server required
Made in Germany

Abfuellanlage — CodeShuttle by IGRF mbH– ☐ ✕

V21AbfuellanlageConnected Switch instance

Folder: C:\Projekte\Abfuellanlage\CodeShuttle 2 devices History Compare Synchronise (5)

14 items found ·→ TIA→Folder: 4← Folder→TIA: 1

HMI_BedienpanelHMI4 items • 0 changedShow unchanged

PLC_AbfuellungPLCRack · 10 items • 5 changed Show unchanged

ITEMTIA PORTALDIRECTIONFOLDERSTATUS

Blocks 9 · 4 changed

fxAnlagendaten DB/ Anlagendaten/ AnlagendatenUnchangedDifferences

fxFoerderband SCL/ Foerderband/ FoerderbandReadyDifferences

fxMain SCL/ Main/ MainUnchangedDifferences

fxRezept SCL/ Rezept/ RezeptReadyDifferences

fxSkalierung SCL/ Skalierung/ SkalierungReadyDifferences

fxtypMotor UDT/ typMotor/ typMotorReadyDifferences

fxEingaenge TAG/ Eingaenge/ EingaengeUnchangedDifferences

Device details DEV/ DeviceDetailsFieldsXMLReadyDifferences

Log console36INFO08:18:35 · Preview ready: 14 item(s), T→F=4, F→T=1InfoWarningError

Commit created · c823c77Foerderband.scl · 08:27

Conflict detectedBoth sides changed – you decide

Collective F-signature unchangedchecked before and after the run

TIA Portal V14 SP1 – V21Every release of the last ten years

Siemens Solution PartnerIGRF mbH, Bremen, Germany

40+ years of automationBuilt by PLC engineers

Personal supportDirectly from the maker

The problem

Your automation know-how is locked in a black box.

TIA Portal stores projects in a binary format that no version control system can look into. What has been standard in software for twenty years is missing in PLC engineering – and that is expensive.

Projekt_v2_final_NEU.zap17

Versioning by folder copy

Dozens of project copies – and nobody knows for sure which one is current or what changed between two of them.

"Who touched that timer?"

No traceability

Changes are hard to prove after the fact – during troubleshooting, commissioning, service and liability questions.

"Last save wins"

Teamwork becomes a risk

When two engineers work on the same project, one ends up overwriting the other's work.

"What did it look like three weeks ago?"

No clean way back

Rolling a single block back to an earlier state costs hours – if it works at all.

And code reviews, pull requests or AI assistants? They need readable text – exactly what CodeShuttle delivers.

The solution

CodeShuttle shuttles your code between TIA and Git.

Through Siemens' official TIA Portal Openness interface – without touching your TIA installation. Three steps to a versioned PLC.

STEP 01

Connect

CodeShuttle finds every running TIA Portal instance on its own. Pick one, click "Connect" – the devices in your project are detected automatically.

V21 Abfuellanlage ● connected // 2 devices found: PLC_Abfuellung, HMI

STEP 02

Compare & sync

CodeShuttle compares the TIA project with the folder, proposes a direction per object and waits for your OK. Nothing is written before you confirm.

→ Foerderband.scl TIA → folder ← Rezept.scl folder → TIA ⚠ Main.scl conflict

STEP 03

Version

Every run creates a commit automatically – locally or in the shared team repository. Every state is documented and can be restored with one click.

c823c77 CodeShuttle sync: 1 to TIA a41f0e2 Initial CodeShuttle commit

9TIA Portal versions
from V14 SP1 to V21

0Git skills needed
to get started

100%control: nothing without
your confirmation

40+years of experience
in automation

Diff view

Every change visible. Line by line.

No more comparing block by block in two TIA instances. CodeShuttle shows the TIA side and the folder side next to each other – added, removed, changed.

Side by side or inline, optionally changes only with context
Resolve conflicts in place: "take TIA" or "take folder"
Your favourite tool: WinMerge, Beyond Compare, KDiff3 or VS Code are detected automatically

fxFoerderband SCL/ Foerderband/ FoerderbandReadyClose

Side by sideInline Changes only Context 3 + − 3 lines changed · 1 added · 1 removed Open in diff tool

TIA Portal · changed 30/09/2026 07:42

28BEGIN

29~ // Start sets, e-stop resets

30 IF #Start AND #Stopp AND #NotAus THEN

31 #Selbsthaltung := TRUE;

32 END_IF;

…

34 #Selbsthaltung := FALSE;

35 END_IF;

37− // write outputs every cycle

38 #Laeuft := #Selbsthaltung;

39 #Motor.Ein := #Selbsthaltung;

40 #Fertig := #Zaehler >= #Sollmenge;

41END_FUNCTION_BLOCK

Folder · changed just now

28BEGIN

29~ // Start sets, e-stop clears

30 IF #Start AND #Stopp AND #NotAus THEN

31 #Selbsthaltung := TRUE;

32 END_IF;

…

34 #Selbsthaltung := FALSE;

35 END_IF;

37 #Laeuft := #Selbsthaltung;

38 #Motor.Ein := #Selbsthaltung;

39 #Fertig := #Zaehler >= #Sollmenge;

40+ // batch done at setpoint

41END_FUNCTION_BLOCK

History

02.10.2026 08:27

CodeShuttle sync: 1 to TIA (Abfuellanlage)

Demo Projekteur · 1 file

01.10.2026 16:42

CodeShuttle sync: 3 to folder, 1 to TIA (Abfuellanlage)

M. Muster · 4 files

01.10.2026 16:41

Auto-backup before team sync

M. Muster · 2 files

30.09.2026 08:26

Initial CodeShuttle commit

Demo Projekteur · 16 files

PLC_Abfuellung/Programmbausteine/Foerderband.sclCompareRestore

Replace the current file "Foerderband.scl" in the sync folder with the state from this commit? The current state stays in the history.

Restore fileCancel

Version history

Who changed what, and when? Now you know.

Every sync is recorded as a commit automatically – with author, timestamp and affected files. Any earlier state is two clicks away.

Complete history of every block, right inside CodeShuttle
Restore with one click – the current state stays in the history
Team sync via network share or Git server (GitLab, GitHub, Azure DevOps …)

Team sync in detail

For the whole team

What CodeShuttle means for you.

Head of automation · management

Safety, evidence and predictable cost

Provable change history for acceptance, service and liability
Prepared for the 2027 Machinery Regulation – changes to control software documented
Know-how secured: the project state no longer depends on one laptop or one person
Parallel project work without a Multiuser server
Predictable: subscription from €45 per user per month, support and new TIA versions included

PLC programmers · engineers

Work like modern software developers

Real diffs instead of comparing block by block
Edit in the editor of your choice and bring it back into TIA with one click
Branches, reviews, pull requests with your Git tooling
AI-ready: readable SCL that code assistants can work with
Experiment freely – every earlier state can be restored

Features

Everything a serious workflow needs.

Bidirectional sync

TIA → folder and folder → TIA in one run, controllable per object.

Conflict detection

Both sides changed? CodeShuttle stops until you decide – nothing is silently overwritten.

Built-in diff view

Side by side or inline – or one click into your external diff tool.

Team sync with Git

Auto-commit after every run, pull/push to the team repository – Git is built in.

History & restore

Browse every commit, compare it and bring back individual files.

F-blocks & safety

F-FB, F-FC and F-DB from TIA V21 – F-changes never preselected, collective signature before/after.

PLC and HMI

Blocks in all six languages, UDTs, tables, WinCC screens, scripts and lists – WinCC Unified too.

Device details

IP addresses, order numbers, firmware and modules per device – documented automatically.

Compile before sync

Optionally, TIA compiles every device before CodeShuttle compares.

See all features

EU Machinery Regulation 2023/1230

From January 2027, evidence counts.

The new Machinery Regulation replaces the Machinery Directive and, for the first time, sets explicit requirements for safety-related software: it must be identifiable, protected against corruption, and interventions and software versions must be traceable. In engineering, CodeShuttle gives you a complete, provable change history of your PLC code.

What this means for you

–days

–weeks

–working days

until it applies on 14 January 2027

Compatibility

Fits your projects – the old ones too.

One tool for every TIA Portal version since V14 SP1. Several instances in parallel? No problem.

V14 SP1V15V15.1V16V17V18V19V20V21

PLC (STEP 7)

SCLSTLLADFBDGRAPHDBUDT Tag tables Watch & force tables F-FB · F-FC · F-DB (V21)

HMI (WinCC classic & Unified)

ScreensPop-upsSlide-insTemplates HMI tagsText & graphic lists VB scriptsConnectionsUnified scripts

Your tools

WinMergeBeyond CompareKDiff3VS Code GitLabGitHubAzure DevOpsGiteaNetwork share (UNC)

Investment

from€45per user
per month*

Less than one engineering hour a month – for a complete history of all your PLC code.

* Volume price from 10 users, net plus VAT. Offer for businesses only.

Included in the subscription

Personal support directly from the maker
All updates – right from within the app
New TIA Portal versions as they are released
Onboarding of your choice: self-paced or live training

Pricing & terms Request a quote

FAQ

The most common questions.

Do I need to change anything in my TIA Portal installation?

No. CodeShuttle uses the official TIA Portal Openness interface and installs nothing inside TIA Portal. Once, you add your Windows account to the "Siemens TIA Openness" group and allow CodeShuttle in TIA – the manual walks you through it step by step.

Do I need Git skills or a Git server?

No. Git is built into CodeShuttle. In "Local" mode, every sync creates a commit automatically – no server at all. For a team, a shared network folder is enough; a Git server (GitLab, GitHub, Azure DevOps …) is optional.

Can CodeShuttle break my TIA project?

CodeShuttle only writes what you confirmed in the preview. It deletes only when you explicitly choose to, conflicts block the run until you decide, and it never saves the TIA project itself – that stays your decision.

Do I need Siemens Multiuser Engineering?

No. With CodeShuttle every engineer works in their own project and merges changes through the shared Git repository – without a Multiuser server.

Does my project data leave the company?

No. CodeShuttle runs locally on your computer. Your project data only goes to the Git destination you choose yourself – such as your network share or your own Git server.

All questions & answers

Your TIA project.Finally versioned.