Versioned C++ Projects

Versioned TwinCAT C++ projects result in an architecture-dependent file when building.

• TMX files for Windows (x86 / x64) and TwinCAT/BSD® - these are loaded via the TwinCAT Loader. They must be signed by a TwinCAT user certificate.
• TME files for Beckhoff RT Linux^® are loaded by the operating system and do not need to be signed.

If a C++ project was created using the “Versioned C++ Project” template, the binaries are stored by Publish in the TwinCAT Engineering Repository (under TwinCAT 3.1 Build 4024: C:\TwinCAT\3.1\Repository and TwinCAT 3.1 Build 4026 C:\ProgramData\Beckhoff\TwinCAT\3.1\Repository) at a vendor- and version-specific location.

From here, modules are transferred to the target system, if they are needed:

• Windows with TwinCAT 3.1 Build 4024: C:\TwinCAT\3.1\Boot\Repository
• Windows with TwinCAT 3.1 Build 4026: C:\ProgramData\Beckhoff\TwinCAT\3.1\Boot\Repository
• TwinCAT/BSD^®: /usr/local/etc/TwinCAT/3.1/Boot/Repository
• Beckhoff RT Linux^®: /etc/TwinCAT/3.1/Boot/Repository

This can be either at the time of activation (Activate Configuration) or at the time of the Online Change.

Additionally, it is possible to create an archive for the transfer between engineering systems of the binary version of this project, which is configured by the project properties.