Signed TwinCAT user certificates for delivery without test mode
System requirements - Min. TwinCAT 3.1 Build 4024 |
With TwinCAT Build 4024, Beckhoff offers existing customers the issuing of a "TwinCAT 3 OEM user certificate", which can be used for signing TMX files created with TwinCAT 3 in C++.
- This certificate requires secure validation of the applicant data, since it is used in the Windows environment. TwinCAT 3 user certificates must therefore be officially ordered for validation of the address and contact data, and are only issued to existing Beckhoff customers.
- Order number: TC0008
- The issuing of this TwinCAT 3 user certificate is free of charge.
- Directory for saving the certificate: C:\TwinCAT\3.1\CustomConfig\Certificates
The TwinCAT 3 user certificate is not required for using the TwinCAT 3 TMX files The TwinCAT 3 user certificate is used exclusively for the one-time signing of the TMX files and is not required for the use of the TMX files signed with it. |
On which computers is the TwinCAT 3 user certificate TC0008 required? The TwinCAT 3 user certificate should be located exclusively on the engineering computer on which the TMX files are signed - i.e. NOT on each target system. |
Validity of the TwinCAT 3 user certificate
The validity of the TwinCAT 3 user certificate is limited to two years for security reasons.
What happens if the certificate has expired? You can no longer sign new TMX files. |
You can apply for a renewal of your certificate before the expiry of the two years (and even after that).
To extend a TwinCAT 3 user certificate, the same process applies as for requesting a new certificate. In this case, the certificate must also be ordered (the order numbers for a certificate extension are the same as for a new certificate request).
In contrast to a new certificate, you do not generate a new OEM Certificate Request File but send your existing certificate to the Beckhoff certificate section for renewal. Please notify us in the email that this is a certificate extension and not a new issue. Otherwise, the same criteria apply regarding the content of the email as for the application for a new certificate.
The existing certificate receives a new expiration date, is then re-signed and is valid for another 2 years.
The newly signed certificate is thus fully compatible with the original version.