Creating subsequent SO instances of the same SOT consumes more and more time (1st=1sec // No150=15sec)

• Related Articles

• SOT : crash when creating a new SOT

  Description The creation of a new SOT via the Equipment Group led to an unexpected closure after a switch between projects. The issue has been addressed and the behavior is now as expected. To benefit from this fix: Update your zenon Software ...

• History of changes/Smart objects: A change in a property of the SOT (e.g. variable name) causes a change in all properties in the corresponding instances.

  Description Changing a property of a Smart Object Template (SOT) causes an entry to be made in the “History of Changes“ for all properties in the corresponding instances. This leads to a rapidly growing database with a lot of superfluous information. ...

• Starting and terminating of the zenon runtime when using over ten instances of the SNMPNG32 driver takes significantly much time.

  Summary When using more than ten instances of the SNMPNG32 driver the starting and terminating of the zenon runtime takes significantly much time. DescriptionWhen using more than ten instances of the SNMPNG32 driver the starting and terminating of ...

• FAQ: What is the time zone and time format used in zenon Software Platform products and what needs to be considered?

  When you ask someone what the time is, they'll usually be able to tell you. But when you ask them what date and time sunrise was yesterday in a different country on a different continent, in a different hemisphere it gets less easy. Terms like GMT ...

• Under specific circumstances two phase instances may become active after RT restart

  Summary In a batch control recipe if two phase instances of the same phase exist in a parallel, normally without an explicit force, only one phase is active at the same time. The other phase is waiting for the first phase to finish. However after a ...