When using 3S_V3 driver in redundant mode, a communication loss to the primary and secondary PLC will not lead to invalid bits in the runtime. When the primary and secondary PLC is available again, the 3S_V3 driver does not reestablish the connection and although the variables in the zenon runtime show the SPONT bit, no communication is possible.

• Related Articles

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

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

• Checklist: Smart Client cannot establish a reliable communication

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

• Bachmann M1 driver: Communication loss is not recognized at all when using callback mode

  Summary When switching the Bachmann M1 driver into "callback" mode it does not react on a communication loss. When having the driver not in callback mode it recognizes communication loss proper and does a reconnect when cable is plugged in again. ...