TwinCAT
Versioned C++ projects are stored as binary in a TMX file (TwinCAT Module Executeable).
For the implementation of TwinCAT 3 C++ modules, this compiled, executable TMX file must be signed with a TwinCAT user certificate if it is to be loaded by the TwinCAT Runtime.
Signing
TwinCAT TMX files can only be loaded after a successful signing.
Note | |
Signing on 32-bit and 64-bit systems In contrast to the operating system signing, TwinCAT signing is intended for both 32-bit and 64-bit systems. Thus, the test mode is also assumed for a test signing on 32-bit systems. |
For signing a TMX file, a TwinCAT user certificate is required, which is configured accordingly in the project for signing.
Test signing
The user certificate can be created locally in TwinCAT. As long as it is not countersigned by Beckhoff, it is necessary to activate the test mode, as described here.
As soon as the TwinCAT user certificate has been countersigned by Beckhoff, the test mode can be dispensed with accordingly. It can be deactivated in the same way as it is activated.