{}

Search FAQs

{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}

How to migrate a Safety application for Modicon M580 / EcoStrucxure Control Expert with a Safe Peer to Peer communication from ECE<15.0 to ECE>=15.0 and a CPU FW >= 3.20

Issue
  • Modicon M580 Safety with EcoStrucxure Control Expert V15 implements a new safety time management principle no more based on NTP services.
  • New peer to peer communication EFB are provided to replace legacy ones.
  • Compiling an earlier application containing legacy EFBs will lead to compilation errors.

Environment
  • ECE>=15.0 and CPU FW >= 3.20

Resolution
here is the list of steps to go through :
  • Set the application level to 3.20
  • Suppress in the logic each instance of S_SYST_CLOCK_MX
  • Replace in the logic each instance of the S_RD_ETH_MX FB with the S_RD_ETH_MX2 FB.
  • Replace in the logic each instance of the S_WR_ETH_MX FB with the S_WR_ETH_MX2 FB.
  • Create and connect the CONTROL_DATA to each of the S_RD_ ETH_MX2 / S_WR_ ETH_MX2 FB
  • Add the communication transfer of the CONTROL_DATA from Receiver PAC to Sender PAC
  • Do you want to delete all unused SAFE variables?
    • yes
      • Purge all unused variables in the Safety Data Editor, in the Function Blocks folder
      • Purge unused Type in the Derived FB Types Editor
    • no
      • Delete manually all S_RD_ETH_MX & S_WR_ETH_MX variables, in the Function Blocks folder
      • Delete manually all S_RD_ETH_MX & S_WR_ETH_MX FB types, in the Derived FB Types Editor
  • Purge unused Types in the Types Library Manager  – in the <Application> view of the types

FAQ Applicable Conditions (Optional)
Both CPU linked via peer to peer must be version SV3.20 or later

Did this answer your question?

Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.