Why does the communication with a Siemens TIA PLC with TIA 20 and firmware 4.0 fail under specific circumcstances?

• Related Articles

• 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 ...

• 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 ...

• 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] ...

• FAQ: How can I monitor and react on the communication status of my devices with zenon?

  Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...

• 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 ...