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 Tool. | TwinCAT project file |
*.plcproj | Yes | Yes, use TwinCAT Project Compare Tool. | TwinCAT PLC project file |
*.tmc | Yes | Not permissible for PLC projects. | TwinCAT module class (description file for a TcCom module) |
*.tpr | Yes | Yes | File contains the refactoring information for standalone PLC projects |
*.tpy | No | - | This file serves only for compatibility with programs from other vendors. |
*.xti | Yes | Yes, use TwinCAT Project Compare Tool. | In case of multiple file support, parts of the TwinCAT project file are stored with this extension. |
*.TcTTO | Yes | Yes, use TwinCAT Project Compare Tool. | PLC task object |
*.TcPOU | Yes | Yes, use TwinCAT Project Compare Tool. | PLC program organization unit (POU) |
*.TcDUT | Yes | Yes, use TwinCAT Project Compare Tool | PLC data type |
*.TcGVL | Yes | Yes, use TwinCAT Project Compare Tool. | 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 Tool. | 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. |
 | TMC file is regenerated automatically 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 compiled 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 compiling 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 Management! |
| Do not merge files manually In general we do not recommend manual merging of the files of a TwinCAT project.
|