CPU error whlie using PM583 ETH redundant configuration with cm597
In My System i am using PM583 ETH redundant configuration With CM597 as a ethernet coupler for both CPU A and CPU B, and i have a two ethernet switches for network redundency. i have used onboard ETH ports for UDP data exchange with crossover cable, i have connected one cable from ETH1 port of CPU A Coupler to Switch1 and another cable from ETH1 port of CPU B coupler to switch 2 , third cable from ETH2 port of CPU A Coupler to switch 2, fourth cable from ETH2 port CPU B Coupler to switch1(please fid attached picture reference).
When i Attach Third or Fourth cable to ETH2 PORT of CPU A or ETH2 PORT Of CPU B coupler(cm597), the both cpu are suddenly going to stop mode or when i insert cpu ethernet cable in switch after insertion of four eth cables of couplers of CPU A&B and i am getting following errors
Error 1: E2 003 , D1 009,D2 001, D3 031,D4 001.
Error 2:E4 054, D1 011,D2 009, D3 031,D4 031.
Error 3:E4 020, D1 009 ,D2 000, D3 002, D4 002.
Error 4:E4 007, D1 011, D2 003,D3 001, D4 003.
IP Adresses of CPU A is 172.16.4.152 and its coupler cm597 adresses is 172.16.4.154.
IP Adresses of CPU B is 172.16.4.156 and its coupler cm597 adresses is 172.16.4.158.
please help me to resolve this problem and suggest me that how we can assign two different ip address to plc's like 172.16.4.20 & 172.20.4.12 on redundant configuration.
The issue is mostly due to a network loop causing a network surge.The network storm is overwhelming the CPUs and this is probably what is causing the CPUs to stop.
Based on the IP addresses specified by you, I am assuming that you are either using CHMI or 800xA as SCADA.
Though the network architecture specifies NIC bridging,I would suggest not to use any form of bridging or network teaming to achieve redundancy. To achieve ethernet redundancy in the client server network, follow the Network Configuration manual to correctly build redundant networks using implicit addressing and rnrp.
I have implemented the same architecture in several sites.As per ABB support , the firmware on the CM597 (from around 2017) does support redundant ethernet connectivity (compatibility with STP/RSTP or via implementation of STP/RSTP at the firmware level) as described in the network architecture.
Please go through the below link for more info,
1) Delete the UDP Data exchange protocol appended to the CM597, since you are already using the onboard ETH ports for data synchronisation
2) The use of crossover ethernet cable was earlier a compulsory requirement.However, with current generation of AC500 PLCs, straight cable can also be used as datasync cable.I have tested the same and we have been using straight cables since quite some time.