Project delivery
Once the development of a PLC project is completed and before the project is delivered, we recommend checking the following steps and, if they make sense in relation to the project, to perform them.
Command/step | Where to find it | Purpose | Further information |
|---|---|---|---|
Activating the "Pin Version" option | TwinCAT 3 project > Double-click the SYSTEM node > "General" tab | On opening the project, the TwinCAT 3 Engineering version defined in the project is automatically used if it exists on the engineering computer. For the avoidance of source code changes - when activating/logging in later - that could be triggered by the use of a different engineering version | TE1000 XAE\ Technologies\ Remote Manager\ TwinCAT integration\ Pin Version project setting |
Setting the compiler version of the PLC application project to the "newest" | PLC project > Right-click the PLC project object > Select the "Properties" command > Open the "Compile" category > Set the "Compiler version" setting to "newest" | The compiler version used for application projects is then automatically the one that matches the engineering version that is loaded in the Remote Manager (see point 1: Pin Version). This is the intended method of use of the compiler version. | |
Setting the PLC library references to a fixed version (no use of "always newest"/"*") | PLC project For all library/placeholder references simultaneously with just one command: > Right-click the References node > Select the command "Use effective version"
or for individual or several libraries/placeholders (by multiple selection): > Right-click a library reference underneath the References node > Select the command "Use effective version"
or for individual libraries/placeholders: > Mark the library reference underneath the References node > Select a fixed version in the Properties window
or for individual placeholders: > Right-click the References node > Open the placeholder dialog > Select a fixed version in the "Library" column | For the avoidance of an Online Change query - when logging in later - that would be triggered by the automatic use of a newer library version if a library reference to "always newest"/"*" is triggered and a newer library version is available in the library repository for this library | |
Checking the settings of the target archive Note: | PLC project > Double-click the PLC project > "Settings" tab | For the avoidance of the inadvertent passing-on of the project sources or libraries due to saving on the target system
|
For standard machines, the use/activation of the following options is usually helpful.
In addition, the two options are necessary if a complete machine update is to be carried out at file level.
Option | Where to find it | Purpose | Further information |
|---|---|---|---|
Option "Use relative NetIds" in the route settings | TwinCAT 3 project > Expand the SYSTEM node > Double-click the Route node > "NetId Management" tab | If the option "Use relative NetIds" is activated, then the first four digits correspond to the project NetId of a placeholder and are set according to the actual NetId of the target system. This allows a project or a configuration to be used on another, identical target system without manual adaptation of the project NetId. Example:
| TE1000 XAE\ System\ System node\ System sub-node\ Routes and TE1000 XAE\ System\ Machine update at file level\ Execute complete machine update |
Option "Virtual device names" in the adapter settings of all network and USB devices | TwinCAT 3 project > Expand the I/O node > Expand the Device node > Double-click the device, e.g. the EtherCAT Master > "Adapter" tab | If the option "Virtual device names" is activated, then the spoken name or display name is used as a reference to the device. The system then uses the device name, not the MAC address. | TE1000 XAE\ I/O\ EtherCAT\ EtherCAT Master\ Adapter and TE1000 XAE\ System\ Machine update at file level\ Execute complete machine update |