Zenon logic crash - Astrazenca Project

Zenon logic crash - Astrazenca Project

Summary

Unexpected Logic Service crash when using shared memory. This has been fixed.

Description

If data types are incorrectly advised during the exchange between Service Engine and Logic Service via shared memory - for example Numeric variables on String variables - this led to a crash.

 

This crash is now prevented. However, data types must still not be mixed.

Recommendation: Make sure you use the correct data types when advising.

 

To benefit from this fix:

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

 



Item ID: 267865
Version: 12.00 Build: 162090

    • Related Articles

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

    • zenon logic runtime crash with C-compiled logic code

      Description After compiling the project in the Engineering Studio and starting the Service Engine the Logic Service crashed when it is started. The issue has been fixed and the behavior is now as expected. To benefit from this fix: Update your zenon ...

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

    • Compiler crashes when parsing a LD program

      Description zenon Logic is terminated unexpectedly when building an LD program. The cause is the handover of a two-dimensional array to a UDFB that expects a one-dimensional array as input. This cannot work and leads to an error. It is expected that ...

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