Introduction
A typical Modicon M580 system is designed and tested for simultaneous use of:
an Ethernet main local rack and the ability to extend to other local racks
RIO drops that support Ethernet and X Bus communications across the backplane
network option switch modules that attach RIO drops and distributed equipment to the M580 system
control network module that creates transparency between the device network and the control network
RIO and distributed equipment integrated on the same physical network
RIO and DIO sub-rings that communicate with the RIO main ring
third-party modules and devices
daisy-chain ring architectures provided by communication modules with dual Ethernet ports
An M580 system provides automatic network recovery of less than 50 ms and deterministic RIO performance.
An M580 system uses Modicon X80 I/O modules, many of which are used in an M340 system. The system also supports several Ethernet-based eX80 I/O modules, which can be installed on both the main local rack and main remote racks. M580 also supports Premium I/O modules installed on an extended local rack.
Typical M580 Architecture
This is a typical M580 architecture. It includes the enterprise, plant, process, and field levels of a manufacturing plant. An M580 simple RIO system is shown at the field level
| WARNING | |
|---|---|
UNEXPECTED EQUIPMENT BEHAVIOR
Failure to follow these instructions can result in death, serious injury, or equipment damage. | |
M580 Life Cycle
The life cycle of an M580 network includes these phases:
Phase |
Feature |
Description |
|---|---|---|
design phase |
standard |
reduce the learning and engineering time (use standard Ethernet technology, Modicon X80 common modules,and Control Expert software for device configuration |
open |
collaborate with third-party solutions |
|
flexible |
adapt the control architecture to the plant topology |
|
efficient |
design the solution without constraints |
|
operation phase |
transparent |
provide access to I/O modules and devices from the control network |
accessible |
change configuration without stopping the process, get diagnostic information from any location in the network, no switch required to create a complete M580 system |
|
renew phase |
sustainable |
preserve long-term investment, allow smooth migration |
M580 Simple RIO Example
This is an example of a typical M580 system that integrates RIO modules and distributed equipment in one Ethernet I/O device network:
1 An M580 CPU with Ethernet I/O scanner service on the local rack is connected to the RIO main ring. (For the Ethernet I/O scanner service, select a CPU with a commercial reference that ends in 40.)
2 A BMENOS0300 network option switch module on the local rack connects a DIO cloud to the RIO main ring.
3 A BMENOC0301/BMENOC0311 Ethernet communication module, connected to the CPU through the Ethernet backplane, manages distributed equipment on the device network.
4 A BMENOC0321 control network module on the local rack creates transparency between the device network and the control network.
5 A PC for port mirroring is connected to the service port of a BMECRA312•0 (e)X80 EIO adapter module.
6 A BMENOS0300 network option switch module on an RIO drop manages an RIO sub-ring.
7 A DIO cloud is connected to the service port of a BMECRA31210 eX80 performance EIO adapter module.
8 A BMENOS0300 network option switch module on an RIO drop connects a DIO sub-ring to the RIO main ring.