Can the service port of the M580 be used to communicate between multiple M580s on the same network.
Issue:
Can the service port of the M580 be used to communicate between multiple M580s on the same network.
Product Line:
M580, Control Expert, Unity Pro
Resolution:
The SERVICE ports of the M580 system are NOT intended to be connected together through the CONTROL network. Do NOT connect, directly, or through a switch, two or more SERVICE ports from different M580 systems. This applies on all service ports: CPU, CRA and DRS.
The reason for this is that the SERVICE ports are in the same subnet as the DEVICE network. At startup, and during some configuration sequences, some broadcast messaging could flood parts of the system. A message broadcast from any CRA is forwarded on the service port, and would go further if it was connected on another M580.
For M580 Hot Standby controllers (BMEH58••••), Schneider Electric documentation explicitly states that the service ports of the two controllers in the Hot Standby pair must not be connected together, either directly or through a common Layer-2 network.
For standalone M580 controllers managing Ethernet RIO drops through BM•CRA312•0 adapters, connections of separate M580 systems should not be placed in the same broadcast domain when doing so could interconnect their device networks. CRA device names are derived from the adapters’ rotary-switch settings and may be duplicated across independent systems. In addition, each M580 system may provide DHCP/FDR services to its configured adapters. Interconnecting the networks could therefore expose a CRA to duplicate device identifiers or competing DHCP/FDR responses, potentially resulting in an incorrect address or configuration assignment, failure of a drop to establish communication, or interruption of I/O communication.
For standalone M580 controllers that are not managing ERIO drops, connecting multiple CPU service ports to the same switched network is not inherently prohibited, provided the network is loop-free, all IP addresses are unique, and the service-port network does not create an additional Layer-2 path into or between the controllers’ device networks. The service ports do not support RSTP and therefore must not be used as ring ports or as part of a redundant Layer-2 path.
If this FAQ did not solve your issue, you can chat with us at chat with us or e-mail us at customer.services@se.com to create a case with our Technical Support Team.
If you are not located in North America, please contact your local Customer Care Center for assistance: