Introduction
You can connect a device network to the control network through the service port on an M580 CPU.
Do not connect the service port to the device network unless in some specific conditions described in Modicon M580, Open Ethernet Network, System Planning Guide.
The service port may not provide full performance and features that the Device Network ports on the CPU provide. Connecting the service port, either directly or through a switch/hub, to the device network may affect system performance.
You may connect additional devices to the device network using a BM•CRA312•0 EIO adapter module.
If Ethernet transparency is needed between a device network and the control network, make the connection with a switch as shown in the following figure.
If Ethernet transparency is not needed, use a BMENOC0301/11 Ethernet communication module and configure the module in isolated mode.
Connect an M580 system to a control network through the service port of the CPU to support monitoring and communication with the device network:
1 The M580 CPU is connected to the main ring. The CPU manages RIO drops within the device network.
2 The service port of the CPU is connected to a control network.
3 This BMENOC0301/11 module (with the Ethernet backplane connection enabled) manages an isolated DIO cloud.
4 RIO drops are connected to the main ring through BM•CRA312•0 X80 EIO adapter modules.
| WARNING | |
|---|---|
RISK OF UNEXPECTED EQUIPMENT BEHAVIOR In a system with multiple RIO networks, do not assign
the same device name to more than one device. Assigning different
network devices the same device name can lead to a conflict when a
device receives its configuration and IP address from a DHCP server. Failure to follow these instructions can result in death, serious injury, or equipment damage. | |
In a system with multiple RIO networks, each with its own DHCP server, assigning the same device name to equipment on different RIO networks can cause a conflict when DHCP servers assign device configurations - including IP addresses.
For example, if communications adapter on an RIO drop (DROP_1) is configured via its rotary switch with the name BMECRA001 and a second communications adapter on another RIO drop (also named DROP_1) is configured with the same name (BMECRA001), there is a potential conflict. As a consequence, a DHCP server can send a device configuration and IP address assignment to the wrong drop.