translation error in zenon 7.60 and zenon 8.00

translation error in zenon 7.60 and zenon 8.00

Description

In the French language version of zenon, the string "Nouveau projet %OEM917" is displayed instead of "Nouveau projet zenon Logic". This translation error has been fixed. The correct expression "Nouveau projet zenon Logic" is displayed again.

To benefit from this fix:

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


Item ID: 181634
Version: 11.00 Build: 111398

    • Related Articles

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

    • Service Engine: S7TIA Driver - crashes on reconnect PLC

      Description The Service Engine has a connection to a S7TIA PLC. If the Service Engine loses the connection and the variables get the status "invalid", the S7TIA Driver is terminated unexpectedly after reconnecting. This error has been fixed. To ...

    • RDA Archives are not created after the Server is shut down in a redundant system

      Summary Server 2 (or 1) does not generate RDA archives in a redundant system. This has been fixed. Description In a redundant system, the server where Service Engine was started second, the RDA variables are not advised automatically. In consequence, ...

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

    • Checklist: VBA code compilation error

      Time estimate:   15 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. Error still occurs after ...