Issue
Examples of MODICON M580 ePAC Networking Architectures
Product Line
Unity
Environment
Windows 10
Resolution
The following examples are selected for presentation based on criteria which attempts to address
some of the most likely needs for Ethernet Connectivity of MODICON M580 ePAC Systems into an
End User's Ethernet Networking Infrastructure.
Examples of MODICON M580 ePAC Networking Architectures
Product Line
Unity
Environment
Windows 10
Resolution
The following examples are selected for presentation based on criteria which attempts to address
some of the most likely needs for Ethernet Connectivity of MODICON M580 ePAC Systems into an
End User's Ethernet Networking Infrastructure.
There are many needs that should be evaluated before committing to connectivity methods, these
include:
include:
1. Standardized and Minimized Part Numbers vs. Lowest Cost2. System likelihood to expand or require additional communication requirements3. Remote Management (Network Transparency) of an entire M580 ePAC system (HART, Drives, etc.)4. SCADA (Control) Network connection Speed (100 MB vs. 1 GB) and Throughput Management5. Redundant SCADA (Control) Network connectivity6. Owner of the Infrastructure (IT vs. Controls Engineering) and the IT Proficiency Level of the Owner
It is highly recommended to consult with your Schneider Electric Technical Sales Consultant to validate Quantum and M580 Ethernet IO Network Architectures.
This Legend is applicable to all of the examples that follow:
This first example is strictly applicable to systems that will only include 'BMX' Part Numbers
(excluding the CPU). If System Expansion at the Control Network Level is possible, including,
adding EIO Drops or 'BME' or 'PME' Modules, then this example cannot be used. The minimum
number of IP Addresses required on the Control Network by the M580 ePACs is 7 (eDIO Device count=0).
(excluding the CPU). If System Expansion at the Control Network Level is possible, including,
adding EIO Drops or 'BME' or 'PME' Modules, then this example cannot be used. The minimum
number of IP Addresses required on the Control Network by the M580 ePACs is 7 (eDIO Device count=0).
This example will potentially include 318 IP Addresses on the Control Network for the M580 ePACs
and their eDIO Devices.
and their eDIO Devices.
This second example removes the limitation of only including 'BMX' Part Numbers, but has Device
Access and System Management limitations. The minimum number of IP Addresses required on the
Control Network by the M580 ePACs is 6 (eDIO Device count=0, eDIO at BMECRA excluded).
Access and System Management limitations. The minimum number of IP Addresses required on the
Control Network by the M580 ePACs is 6 (eDIO Device count=0, eDIO at BMECRA excluded).
This example will potentially include 304 IP Addresses on the Control Network for the M580 ePACs
and their eDIO Devices.
and their eDIO Devices.
The third example demonstrates an alternative method of Securing and providing Total System
Management for an M580 System. The minimum number of IP Addresses required on the Control
Network by the M580 ePACs (as shown) is 11 (eDIO Device count=0, eDIO at BMECRA excluded).
The addition of HART Analog modules to the far right system will increase this minimum count by
1 IP Address per HART Module. This example will potentially include 374 IP Addresses on the Control
Network for the M580 ePACs and their eDIO Devices.
1 IP Address per HART Module. This example will potentially include 374 IP Addresses on the Control
Network for the M580 ePACs and their eDIO Devices.
發佈於: 施耐德電機Taiwan
