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.

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.

Summary

When the 3S_V3 is used in redundant mode, the variables in the zenon runtime do not get invalid when the connection to the primary and secondary PLC is lost. The 3S_V3 also does not reestablish the connection to the primary or secondary plc when they are available again in the network. The variables of the 3S_V3 driver in the zenon runtime are always SPONT, although no communication is possible.

Description

When the 3S_V3 is used in redundant mode, the variables in the zenon runtime do not get invalid when the connection to the primary and secondary PLC is lost. The 3S_V3 also does not reestablish the connection to the primary or secondary plc when they are available again in the network. The variables of the 3S_V3 driver in the zenon runtime are always SPONT, although no communication is possible.

Solution

This issue has been addressed by no longer processing the statechange-callbacks directly but queueing them sequentially by the hardware thread.

Issue Number: 38986
Fixed on Date: 18.10.2017
Versions: 7.60 0 BUILD 42944 | 8.00 0 BUILD 46644

    • Related Articles

    • zenon Changesets Excel

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

    • zenon Changesets CSV

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...

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