[3D Integration] Triggering limit values don't always led to correspondent highlighting on 3D models present in multiple zenon screens

[3D Integration] Triggering limit values don't always led to correspondent highlighting on 3D models present in multiple zenon screens

Description

In 3D Integration, the violation of limit values is not always indicated in the corresponding 3D models if they are used in several zenon screens.

This bug has been fixed. Limit value violations are displayed in all linked models.

To benefit from this fix:

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


Item ID: 269512
Version: 14.00 Build: 237866
Version: 14.00 Build: 239777

    • Related Articles

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

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

    • [3D Integration] Limit-violations are not reflected in the 3D Model

      Summary In 3D Integration, limit violations in the 3D model are not taken into account. This has been fixed. Description Limit violations are not displayed in the 3D model if they occurred before the screen with the affected model was opened. The ...

    • Command Processing Screen doesn´t resolve Dynamic Limit Value Text

      Description Dynamic limit texts are displayed correctly in Dynamic Elements and CEL. But in Command Processing screens, Dynamic Limit Texts values are not resolved. This behavior has been changed: Placeholders for Dynamic Limit Texts are also ...

    • MELSECA: (BLOCKWRITE=1) Writing any negative values always returns -1

      Summary Writing a recipe using the MELSECA driver with activated BLOCKWRITE: Negative values are always set to -1 regardless of the value. This has been fixed. Description BLOCKWRITE has been activated for MELSECA with this entry in the project.ini: ...