3S_V3 crash after reload

3S_V3 crash after reload

Description

For a project running on the Service Engine, the PLC settings are changed in the Engineering Studio for the 3S_V3 driver. Afterwards  the Service Engine files are transferred. When reloading the project in the Service Engine, the driver crashes.

To avoid this error:

  • Update to the latest build of zenon 10 or 11.



Item ID: 254581
Version: 11.00 Build: 104641
Version: 10.00 Build: 103999
    • Related Articles

    • Checklist: Process closes unexpectedly (***Non-reproducible***)

      Time estimate: 45 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. Checklist usage: #. [Quick hints] ...
    • RT crash after reload - changes made in variables

      Summary Sometimes ServiceEngine crashes after reload if archive evacuation fails immediately before the reload Description Sometimes ServiceEngine crashes after reload if archive evacuation fails immediately before the reload Issue Number: 247623 ...
    • Checklist: Process closes unexpectedly (***Reproducible***)

      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. Checklist usage: #. [Quick hints] ...
    • The value (%v) in the dynamic limit text is not converted into the secondary unit

      Summary A dynamic limit text may be configured to display a variable´s value with the placeholder %v. It may further more be configured to display the variable´s measuring unit with the placeholder %u. If unit switch is enabled and the secondary unit ...
    • Sporadic crash in OPCUA process gateway on soft reload

      Description Occasionally the OPCUA Process Gateway closed unexpectedly on a soft reload. The issue has been addressed and the behavior is now as expected. To benefit from this fix: Update your zenon Software Platform to the latest build of zenon 12 ...