Project Files

So that a TwinCAT project is compatible with Source Control Management systems and supports work in teams, it is stored in several files. The following file extensions exist in the TwinCAT project:

File extension

Source Control Management

Merging permissible

Description

*.tsproj

yes

yes, use TwinCAT Project Compare

TwinCAT project file

*.plcproj

yes

yes, use TwinCAT Project Compare

TwinCAT PLC project file

*.tmc

yes

not permissible for PLC projects

TwinCAT module class (description file for a TcCom module)

*.tpy

no

-

This file serves only for compatibility with programs from other vendors.

*.xti

yes

yes, use TwinCAT Project Compare

In case of multiple file support, parts of the TwinCAT project file are stored with this extension.

*.TcTTO

yes

yes, use TwinCAT Project Compare

PLC task object

*.TcPOU

yes

yes, use TwinCAT Project Compare

PLC program organizational unit (POU)

*.TcDUT

yes

yes, use TwinCAT Project Compare

PLC data type

*.TcGVL

yes

yes, use TwinCAT Project Compare

PLC global variable list

*.TcVis

yes

Not currently supported

PLC visualization

*.TcVMO

yes

Not currently supported

PLC visualization manager

*.TcGTLO

yes

yes, use TwinCAT Project Compare

PLC global texts list

*.sln

no

-

This file is the solution file from Visual Studio (VS). It contains, among other data, a tag indicating the VS version used. If this is checked in, it makes working with different VS versions more difficult.

*.suo

no

 

This is the user options file for the VS project. It contains information on the selected platform, breakpoints, etc. and is user-specific. It is generated when a project is opened on a computer for the first time.

 

Note
TMC file is automatically re-generated

The description of the process image of a TcCom module is stored in the *.tmc file. If this is to be available directly after the checkout (fetching) of a project, even if the project had not previously been translated on one’s own computer, then the TMC file must be fetched with it (and thus checked in with the project beforehand). The TMC file is automatically re-generated after translating a PLC project. It is therefore NOT merged for PLC projects and from TwinCAT 3.1 version 4018 also no longer needs to be under Source Control administration!

 

Note
No manual merging of files

Manual merging of the files of a TwinCAT project is not generally recommended. The TwinCAT Compare Tool should be always used for this!