You are currently viewing the content available in Vietnam. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.
Issue
Environment
Resolution
here is the list of steps to go through :
FAQ Applicable Conditions (Optional)
Both CPU linked via peer to peer must be version SV3.20 or later
- 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
- yes
- 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