The S7TIA driver performs poorly with AGLink.dll v5.1.0.2

The S7TIA driver performs poorly with AGLink.dll v5.1.0.2

Summary

When using AGLink.dll v5.1.0.2 the S7TIA driver performs poorly.

Description

When using AGLink.dll v5.1.0.2 the S7TIA driver performs poorly.

Solution

This issue has been addressed by updating the AGLink.dll to v 5.1.0.9

Issue Number: 37156
Fixed on Date: 5.10.2016
Versions: 7.20 0 BUILD 32414 | 7.50 0 BUILD 31997
    • Related Articles

    • Support of TIA V18

      TIA V18 is supported by the S7-1200/1500 (S7TIA.exe) driver from zenon 10/11/12 with build higher than 157700. All older versions of zenon are not supporting TIA V18. To confirm the support of TIA18 check in the installation directory of zenon if the ...
    • 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 ...
    • 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] ...
    • Communication Reset after one hour for the TIA driver with firmware 3.0

      Description If the TIA driver is operated with firmware 3.x, the PLC performs a reset in the Service Engine after one hour of operation. Communication is interrupted and restarted. This reset always occurs again after one hour. This behavior has been ...
    • TIA Driver crashes after starting communication to the PLC with a specific project

      Description The TIA driver crashed, if an import has been done from a PLC project (or the project has been started in the Runtime or the Service Engine) in a build that used AGLink in version 6.0.2.0. To fix this issue the AGLink version has been ...