When importing variables from the S7TIA driver, the imported variables in zenon have an incorrect name or adressing

• Related Articles

• TIA driver crashes after importing and overwriting existing variables from the TIA project

  Description The driver was closed unexpectedly after a project was loaded and already existing variables were imported from the TIA project and overwritten. The issue has been addressed and the behavior is now as expected. To benefit from this fix: ...

• S7TIA: Variables cannot be imported from TIA project when CPU name contains dots (.)

  Summary All Version do not resolve dots (.) as part of CPU-name properly. This leads to problem with importing variables from TIA-projects or pre-compiled projects. With the current bugfix CPU-names containing dots are quoted to recognise it and to ...

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• When importing variables either from the PLC or from a XML symbol file of the 3S_V3 driver, variables with a name consisting of more than 128 characters shall not be imported.

  Summary Variables of the 3S_V3 driver with a name consisting of more than 128 characters shall not be imported from a PLC or from a XML symbol file. DescriptionVariables of the 3S_V3 driver with a name consisting of more than 128 characters shall not ...

• Checklist: Communication to TwinCat via BeckhoffNG driver

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...