Creation of versioned drivers

Each runtime object imported from an FMU into TwinCAT 3 automatically contains version information. This makes it possible to transfer several versions of the same model into TwinCAT runtime objects. These can then be instantiated version-selectively in TwinCAT.

Setting the version control

Under the tab General you can set for the entries Version source file and Version part for increment how the version control of the runtime modules should be done.

The basic version on which a version update is to be created is specified via Version source file. In the standard case $<LatestTMFile> is specified there. This searches for the last available version of the model on the local engineering PC and then uses this as the basis for the version increment. The version number consists of four digits, e.g. 1.0.3.2 or 2.12.123.14. Each digit can be incremented separately according to the scheme: <Major>.<Minor>.<Build>.<Revision>. If None is selected, no version update takes place and the last version on the engineering PC is overwritten.
Via DrvFileVersion you can specify a fixed version. To do this, enter the target version in the input field.