MELSECA: When primary server comes back online (dominant) the MELSECA driver on the standby server is not stopped (keeps the TCP connection alive) and the MELSECA driver on primary can no longer connect to the PLC and therefore the variable gets invalid

• Related Articles

• FAQ: Initialization of Internal variables (Network) in Dominant redundancy mode.

  When (re-)starting the dominant Server 1, regardless of their 'Remanence' configuration, internal variables with calculation in 'Network' are initialized first in the dominant Server 1 and only after synchronized with the running Server 2. Modules ...

• Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

  Time estimate: 45 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: 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] ...

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