IOT2050 - Logic redundancy: after few minutes passive Logic becomes accidentially active

• Related Articles

• stratonNG driver loses status information of variables which are not BEV Buffering active after Server and IoT (Logic Server) network breakdown

  Description The stratonNG driver lost the status information of variables which were not BEV buffered after a network breakdown between the Server and the IoT (Logic Server). The issue has been addressed and the status information is now transmitted ...

• Checklist: The Logic Service to Service Engine connection does not work

  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. Screenshot and followed ...

• In "IOT2050 docker" LOGIC Service redundancy can not be set

  Description In the IOT2050 Docker it was not possible to set the Logic service redundancy. The issue has been addressed and the redundancy can be used now. To benefit from this fix: Update your zenon Software Platform to the latest build of zenon 15 ...

• zenon Logic shows unexpected behaviour after several redundancy switches.

  Summary After several redundancy switches, the zenon Logic runtime shows unexpected behaviour. DescriptionAfter several redundancy switches, the zenon Logic runtime shows unexpected behaviour. Solution This issue has been addressed by not accessing ...

• FAQ: How to address Logic service cycle overflows?

  In some cases, Logic Service may not respect the configured cycle time of the Logic application. When this happens consider the following: Check Windows Event Logs - System Event ID = 37: The speed of processor x in group y is being limited by system ...