The 3S_32 driver does not communicate with a PLC in the zenon runtime.

• Related Articles

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

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

• Service Engine: S7TIA Driver - crashes on reconnect PLC

  Description The Service Engine has a connection to a S7TIA PLC. If the Service Engine loses the connection and the variables get the status "invalid", the S7TIA Driver is terminated unexpectedly after reconnecting. This error has been fixed. To ...

• The iLON100 driver does not communicate in the zenon runtime.

  Summary No Communication is possible in the zenon runtime with the iLON100 driver. DescriptionNo Communication is possible in the zenon runtime with the iLON100 driver. Solution This issue has been addressed by improving the communication behaviour ...

• Setting values for DINT/UDINT variables of the S7_NT Driver from zenon runtime to PLC leads to value 0 in both zenon runtime and plc.

  Summary Setting values for DINT/UDINT variables of the S7_NT Driver from zenon runtime to PLC leads to value 0 in both zenon runtime and plc. This behaviour occurs when the following prerequisites are given: S7-Project created in Step 7 v. 55 ...