Issue with zenon logic block name of a smart object at its instantiation

Issue with zenon logic block name of a smart object at its instantiation

Description

When instantiating a Smart Object, the block of a zenon Logic Project is not instantiated correctly. The name of the block does not match the rules in the instances and thus cannot be used as expected.

This behavior has been changed. Blocks are now instantiated correctly. 

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 10 or higher.

 



Item ID: 245139
Version: 10.00 Build: 113329

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

    • Smart Object: zenon logic Variables getting deactivated

      Description Smart Object Templates contain structure data types for zenon Logic. When changes are made to these templates, all structure elements in all instances of this template are inadvertently deactivated. These structure elements can not be ...

    • zenon logic: Unexpected complex data in expression

      In zenon version 8.20, it was possible to initiate and assign the function block in one line. This was not IEC compliant, therefore feature was removed in zenon 10. Now the error message "Unexpected complex data in expression" is logged when using ...

    • Smart Object Templates: Engineering Studio crashes when importing an XML file which contains an already existing function name in Smart Object

      Description The zenon Engineering Studio was closed unexpectedly when an XML file was imported that contained a function name that already existed in a Smart Object. The issue has been addressed and the behavior is now as expected. To benefit from ...