M580 Networking and Communication

M580 Networking & Communication WS
Bryan Suitor
Michael Trinca
Improving the understanding of Architectures
Confidential Property of Schneider Electric
Why this workshop?
Ethernet is the core of the ePAC.

• Flexibility – all ethernet communications
• Transparency via – DTMS and an ethernet backbone.
• Standardisation on more protocols
There is a cost .
• We require a better understanding of the offer
• We need a higher level of network understanding
The intent of this workshop is to explain the underlying communication protocols and Schneider
recommendations to help achieve a better success rate for implementation.
Confidential Property of Schneider Electric | Page 2

Agenda M580 CPU Rack Configuration
M580 ERIO Networks
Ask Questions at any time

M580 Peer to Peer Communications
M580 Device Communications
Summary
References
Exercises

M580 CPU Rack Configuration
Typical Questions
1. Difference between the BMEP584020 (EDIO) and the

BMEP584040 (EDIO/ERIO) ?
2. Why two IP addresses?
3. Isn’t this a switch?
4. Why only three NOC modules?
5. How many ethernet modules can I have?
6. What security settings do I need?

ERIO / EDIO versus EDIO CPUs
BME*58*040 BMEP58*020
ERIO EDIO
ERIO/EDIO EDIO PAC • CPU 125 EDIO devices scanned (3
• Configuration integrated into CPU program
PAC reserved EIP local slave)
• 31 ERIO (CRAs) Drops
• 32 devices in main ring to meet max 50 ms • ENOC 112 EDIO devices scanned
recovery time (16 reserved EIP local slave)
• DRS counts as 2 devices • RSTP recovery time max < 3 sec
• ETH 2 & 3 packets VLAN tagged • ETH 2 & 3 packets not VLAN tagged
• Max hops for ERIO 32 (switched device) • Use DRS or NOS in local rack to
extend # EDIO devices scanned
EDIO • No bandwidth restriction
• Separate device configuration • Max EDIO devices in main ring 38
• CPU 61 EDIO devices scanned (3 reserved EIP • Max hop main ring 40 including CPU
local slave) • Max hop NOS in local rack 40
• EDIO limited 5Mbps per EDIO ports (switched device) including CPU,
• Total EDIO traffic main ring 20 Mbps Ethernet backplane & NOS
• EDIO Devices connected to service ports CPU,
CRA Ethernet modules, DRS & NOS EDIO ports.
• Max hops for DRS EDIO subring 40 (switched
device) including DRS
• Max hop NOS in local rack or CRA rack 40
(switched device) including CPU or CRA, Ethernet
backplane & NOS
Is the M580 an ethernet switch?
Answer
Backplane is a dual bus rack with proprietary

X-BUSA port and a 4 or 8 port ethernet Enable or
switch Disable
Two pathways to the CPU, X-Bus and ethernet.

The CPU module uses a 5 port switch:
• Service port (port 1)
• Control or Device port (ports 2 & 3)
• Backplane port (port B)
• Internal connection to the CPU.
The same for the eNOC module.

Why two / four IP Addresses?
Answer:
NOTE: Hot Standby implications for

CPU & NOC \ Comms modules:
1. Primary address changes.

• Peer to Peer always communicate
with the master device.
2. IP Address A and IP Address B

remain with the CPU. Set by a
rotary switch on the back of the
CPU.
• ERIO / EDIO do not reconfigure
network.

Surely I can have two subnets?
Answer
Effectively the CPU has been allocated two IP addresses on the same subnet.
• For communications to the CPU target the CPU IP primary address.
• It is possible to use the ERIO / EDIO address to talk to the CPU.
• Both IP addresses are on the same subnet.
These are the one switch not separate ethernet switches.
To support a different subnet use a separate ethernet module.

Surely I can have four subnets in hot standby?
Answer
In Hot standby we have four IP addresses all on the same subnet.
• For SCADA or Peer to Peer communications should use a separate NOC module to support a different
subnet, with the back plane disabled. In hot standby systems the NOC module will automatically change
IP address for the primary device.
• When we wish to talk directly to the controlling PLC we use the Primary address.
• To access the standby device we use the Standby address (primary address +1)
• These addresses swap when the primary CPU goes into standby mode.
• The peer device ie. SCADA or PLC uses the one address for the primary PLC.
• To manage the ERIO and maintain the 50ms recovery time we create a CPU A address and a CPU B
address (determined by the switch settings on the CPU).
• These addresses remain with the CPU module irrespective of its controlling status.
• Access to the CPU A & CPU B can be made by these IP addresses, however we are not aware until we
connect and interrogate the HSBY DDDT which is primary.

Why only three BMENOC0301 / BMENO0311 modules?
Answer
The first release of the BMENOC0301 / BMENOC0311 modules where found to have a
higher than expected current draw at elevated temperatures. To reduce impact on an
operating system the configuration is now limited to a maximum of 3 modules per CPU,
as precautionary measure.
Q1 2019 a new hardware version (PV>=10) BMENOC0301 / BMENOC0311 will be
available. Up to four of these units can be installed in a BMEP5840x0 (system) with
service patch.
Q3 2019 a new BMENOC0331 module will be available. Up to 6 of these can be used in
a BMEP585040 / BMEP6040 system.
BMENOC03x1.4 system supports:
• 3800 words Input and 3800 words Output
• Also allows upgrade of the CPU clock via the Bus-X backplane, using NTP.
• Supports 16 EIP slave connections and 112 EIP / Modbus TCP/IP EDIO device transactions
How Many ethernet modules can I have?
Answer
Depending on the CPU there can be up to six ethernet modules per rack.
• BMEP581020 / 20x0 – 2 modules
• BMEP5830x0 – 3 modules
• BMEP5840x40 – 4 modules
• BMEP585040 / BMEP586040 – 6 modules
Options include:
• BMXNGD0100 – Global data module, Real Time Publish Subscribe Protocol
• BMXNOR0200 – DNP3 & Modbus TCPIP module
• BMENOP0300 – IEC61850 & Modbus TCPIP module
• BMENOC0301/0311 – Modbus TCPIP / EIP module
• BMENOC0321 – Control Module Modbus TCPIP / EIP – with IP address forwarding
• BMENOC0331 – Advanced NOC (future release) Modbus TCPIP / EIP / OPC UA /

What security settings do I need?
Answer
Access list – by default if you enable this port 502 is

disabled. Make sure you turn port 502 on.
If off you will be able to ping the CPU but you cannot
connect via Unity Pro.
For any ERIO drops you must have DHCP, FTP, TFTP and
EIP enabled.
Initial settings are turn off security and then enable security
once complete disable anything that is not in use to
reduce the attack surface.
The function block “EthPort_Control_MX” can enable or
disable:
• FTP, TFTP, HTTP
• “Service_Control” bits, enable or disable the services.
M580 ERIO Networks

Summary
References
Exercises

M580 ERIO Networks
Typical Questions
1. What is so special about the ERIO network?

2. Can I use my Cisco switch in the ERIO network?
3. Why would I use the DRS?
4. How do I use the NOS module?
5. Special Hot standby connections.

What is so special about the ERIO network?
Answers
ERIO is effectively a proprietary network

Can I use third party switches in the ERIO network?
Answers
In a ERIO network the following are recommended & validated options:
1. Direct connection from CPU to CRA, using a in rack media converter as needed.
2. Use a Dual Ring Switch to connect devices or a sub ring of ERIO or EDIO devices.
3. Use NOS modules installed in the main CPU rack or in drop racks to add
connections.
4. Third party switches can be used in any network connection except the ERIO
network.
There have been cases of Cisco, Moxa switches used in the ERIO network.
It can work, no performance guarantee , limited support.

Why would I use a Dual Ring Switch?
Answers

How do I use a NOS module? (must have Ethernet Backplane)
Answers

Which Hot standby connections do I need?
Answers
Hot standby requires:
1. Synchronisation link – red
dash
2. Secondary pathway usually via
ERIO, however ...
• The NOS can be used to
complete the ERIO
connection. The CPU
manages the EDIO
network.
• NOC module with
Backplane port open
which manages the EDIO
network.

Can I use more than one CPU in an ERIO network?
Answers
Flexibility - For users needing a few
remote I/O drops in an area already
managed by a separate M580 ERIO
network, a shared ring topology can
be used.
Cost-effectiveness – A shared ring

removes the need for an additional
PAC network with its associated
cabling and infrastructure expenses.
Power – Multiple, independent M580

PLC systems and their associated
drops can operate independently on
the same main ring.

More than One CPU in an ERIO network.
Rules to observe
• The maximum number of CPUs and CRAs on the shared network is still 32 (e.g. two HSBY systems sharing the ring use
four CPUs and can support up to 28 CRAs). Rules for number of devices on main and subrings for DRSs still hold as well.
• NOTE. Unity Pro enforces these limitations only at the PLC system level, so the designer needs to manage enforcement globally across
the shared network.
• The general rules for ring redundancy still hold:
• A DRS switch counts as two devices (CRA, CPU, DRS)
• A CPU and a CRA module each count as one
• Shared RIO system will maintain 50 ms recovery time if rules are followed
• Use different device IDs for every CRA across the shared network. DHCP/FDR will not work properly if two PAC systems try to
communicate with the same CRA.
• Use unique IP addresses for all of the devices on the shared network. Some auto-numbering takes place so check addresses across all
the systems to verify that there are no address conflicts
• Set the RSTP–CRP bridge priority to Root on one CPU and to Participant on all others. The redundancy status bit in the CPU DDT is
valid only for the system with its bridge priority designated Root.

More than One CPU in an ERIO network.
Bandwidth Checking
• The Ethernet RIO System Planning Guide indicates the following:
These limits still hold on a shared network architecture, but Unity Pro calculates bandwidth only at the individual PAC system level. We need
to know that all the systems on the shared ring comply.
To test the compliance of a potential shared network system, we propose the following:
1. In Unity Pro, configure one Hot Standby system that contains all the drops and all the EDIO used across all PLC systems in a
single Unity Pro project. Place EDIO devices on a BMENOC03x1 device.
2. If Unity Pro builds the system successfully, we can be confident that the shared ring system will be within bandwidth limits.
3. After the HSBY system-build completes successfully, the designer can move the various drops to the other systems on the shared
network.

M580 ERIO Networks

Summary
References

Typical Questions
1. What are my options for peer to peer communications?
2. What is IO scanning using Modbus TCP/IP?

3. What is Ethernet / IP implicit communications?
4. What is Global Data?
5. What are explicit communications?

Summary for Peer to Peer Service
Key Details Table
Considerations:
• the number of PACs to
share the data,
• the volume of data,
• the frequency of the data
transfer,
• the host system standalone
or hot standby
• when are changes to be
made to system – ie.
Online changes
Communication Options
Implicit communications
Global Data: Ethernet IP: Modbus TCPIP:
• Suitable for when data exchanges • Suitable for applications with • Suitable for applications with
less than 513 words fewer PACs and larger volumes many PACs and larger volumes
• Suitable for same data is to be of data. of data.
shared by multiple devices (max • Suitable for third party peer to • Suitable for communicating
64) peer communications eg. different data to multiple PACs.
• Cannot be used in hot standby Rockwell PAC where M580 is • Suitable for third party peer to
systems adaptor. peer communications eg.
• Restricted to Unity PLCs, M580, • The data being shared can vary Modbus TCPIP interface.
M340, Quantum, Premium between PACs. • Suitable for single small
• Specific BMXNGD0100 module • Good for when the data sizes exchanges
are fixed. • Good for exchanges where
individual data sizes vary
These options require stopping the PAC to make changes to the data exchange.

Communication Methods
Explicit Communications
Read_Var, Write_Var, Data_Exch:
• Requires multiple function blocks for exchange of large amounts of data sharing.
• Better performance occurs with CPU client connections instead of the BMENOC0301
connections.
• Does not require DTM configuration
• CPU scan time is impacted slightly more in this case.
• Therefore, explicit messaging is not as suitable for large amounts of data, to multiple devices as
implicit types of communication.
• Changes to the instructions can be performed online. Suitable for modifications to
continuous processes.
• Suited for reporting by exception. Or high latency networks – communications via radio.

What is IOScanning?
Key Points
• Modbus Function Codes 3 (read), 16 (write) or 23 (read / write)
• M580 both Modbus Server & Modbus Client
• Repetition rate 5 – 60000 ms, nominal period between two successive Modbus queries transmitted
by IO Scanner Client
• Actual Repetition rate – IO scanner will only transmit after receipt of previous response and when the
next repetition rate is due. If response takes longer than nominal period it waits until the next repetition
is due.
• Maximum 125 words read & 120 words write per Message (size 256 bytes).
• A new connection for each transaction line
• Maximum payload per module
• BMENOC0301, BMENOC0311 3.8 kw input / 3.8 kw output – 112 transactions lines
• BMENOC0321 – 1.8 kw input 1.8 kw output - 52 transaction lines
• BMEP58*020 – 2048 w input 2048 words output – 125 transactions lines
• BMEP58*040 – 1024 w input 1024 words output – 61 transactions lines
What is Ethernet IP implicit communications?
Key Points
• M580 can act as both Ethernet IP Adaptor (Target) or IP Scanner (Originator)
• Use specific DTMs for each Adaptor, sizes of assembly must match at both Adaptor and Scanner
• Repetition rate 5 – 65535 ms, nominal period between two successive Adaptor unicasts
• Maximum 505 bytes input assembly & 509 bytes output assembly ENIP Message (size 512 bytes).
• A new connection for each assembly, IGMP filtering is recommended on all network switches
• Once a configuration is implemented by DTM you must read and write the total data structure you
cannot perform a partial data extraction.
• Maximum payload per module
• BMENOC0301, BMENOC0311 3.8 kwords input / 3.8 kw output – 16 adaptor instances
• BMENOC0321 – 1.8 kw input 1.8 kw output - 12 adaptor instances
• BMEP58*020 – 2048 w input 2048 words output – 3 adaptor instances
• BMEP58*040 – 1024 w input 1024 words output – 3 adaptor instances
What is Global Data?
Key Points
• Real time publish Subscribe protocol (RTPS)
• Uses IP Multicast technology IP address
group range 224.0.0.0 to 239.255.255.255
• Optimum performance when used with
switches configured with GMRP protocol.
• Group size 64 participants
• Maximum subscription is 2048 words per
participant
• Publish 1 variable maximum size 512 words
• Distribution period 10ms to 15000ms in 10ms
increments
• This offer is more for legacy sites upgrading
to M580
What are Explicit communications?
Key Points
• Focus on Modbus
• Each communication function block is queued and sent at the end of the scan. Maximum
execution rate is equal to the scan time of the CPU.
• Read operation (FC 3) 125 words maximum, Write operation (FC 16) 123 words maximum
• Fine details:
1. Client Actions
– Maximum EF blocks active per scan for the CPU is based on the module client connection capacity.
– Maximum number of 20 client unique device (single IP) connections available per scan.
– Several EF blocks (up to client capacity maximum) can be active if they target an IP address which has a
connection.
2. Server Response.
– Must also consider the ability of the server to respond
– %SW90 is used to increase the number of server connections acted upon in one scan

Key Points
• Read_Var, Write_Var, Data_Exch:
1. Client Actions
– Maximum EF blocks active per scan
for the CPU is based on the module
client connection capacity.
– Maximum number of 20 client
unique device (single IP)
connections available per scan.
– Several EF blocks (up to client
capacity maximum) can be active if
they target an IP address which has
a connection.

Key Points
• Fine details:
2. Server Response.
– From table 1 there is a maximum
number of concurrent connections.
– %SW90 enables an increase in the
number of responses handled per scan.
(For BMEP584040 = Max 40)
Per PLC Scan this is a total of:
– CPU IP address responses (Max 24 for
BMECPU584040)
– Communications modules server
requests. (Max 16 for BMENOC0301
module).
– Number of communications modules
(see next page)
– USB programming communications
(Max 4 for CPU)

Key Points
• Fine details:
‒ Number of modules
3. Does not require
DTMs
4. Changes can be
made online.
5. Good for slow
responding networks.

M580 ERIO Networks

Summary
References

Typical Questions
1. What issues are there with DTMs?

2. What are the limitations for Implicit communications?
3. EDIO / RSTP Info / Hops etc

What are the issues with using DTMs?
Answers
Limitations:
• For General Modbus DTM refined details cannot be easily
duplicated.
• When using HART IO modules must consider IO as well as
manage the HART Ethernet / IP DTM.
• DTMs versions
• Store a copy of third party DTMs as well as the Unity project for
installing on other PCs.
• Generated DTMs from EDS is the order of creation and the use
of different versions
• Selectively install required DTMs. Unused DTMs are installed
in the Unity Catalog and reduce performance and consume
memory.

ERIO / EDIO versus EDIO CPUs
ERIO/EDIO ERIO EDIO PAC EDIO

PAC • ETH 2 & 3 packets VLAN tagged • ETH 2 & 3 packets not VLAN tagged
• 31 ERIO (CRAs) Drops • CPU 125 EDIO devices scanned
• 32 devices in main ring to meet max 50 ms (3 reserved EIP local slave)
recovery time • ENOC 112 EDIO devices scanned
• DRS counts as 2 devices (16 reserved EIP local slave)
• Max hops for ERIO 32 (switched device) • Use DRS or NOS in local rack to
extend # EDIO devices scanned
EDIO
• No bandwidth restriction
• CPU 61 EDIO devices scanned (3 reserved EIP • RSTP recovery time max < 3 sec
local slave) • Max EDIO devices in main ring 38
• VLAN tag needs to be removed for EDIO devices • Max hop main ring 40 including
• EDIO Devices connected to service ports CPU, CPU
CRA Ethernet modules, DRS & NOS EDIO ports. • Max hop NOS in local rack 40
• EDIO limited 5Mbps per EDIO ports including NOS
• Total EDIO traffic main ring 20 Mbps
• Max hops for DRS EDIO subring 40 (switched
device) including DRS
• Max hop NOS in local rack or CRA rack 40
(switched device) including CPU or CRA, Ethernet
backplane & NOS
M580 System Hop count example
3 DIO loops – each loop has
EDIO device #9 a maximum hop count of 39
… 9 Hops to EDIO device #9 1 ERIO loop – maximum hop
count 31
EDIO device #7
… 7 Hops to EDIO device #7
10 ERIO Drops
4 Hops to ERIO device #4
…
ERIO device #4
…
What are the limitations for Implicit communications?
Answers

M580 ERIO Networks

Summary
References
Exercises

Summary
General M580 CPU details

Summary
Peer to Peer
Protocol option summary
1. Many to many devices:

• Modbus TCPIP
• Ethernet IP
• Global Data
2. One to many devices:
• Modbus TCPIP
• Ethernet IP
• Global Data
3. Data concentrator:
• Modbus TCPIP
• Ethernet IP
4. One to one:
• Modbus TCPIP
• Ethernet IP
• Explicit messaging
M580 ERIO Networks

Summary
References

References
All files will be available on box folder …
1. TVDA - How Can I Implement M580 Peer to Peer Communications_V1.00

2. TVDA: How can I … Implement Ethernet Distributed I/O in an M580 Modular
Architecture?
3. Modicon M580 BMENOC0301/0311 Ethernet Communications Module Installation
and Configuration Guide
4. Modicon M580 Hardware Reference Manual

M580 ERIO Networks

Summary
References
Exercises

Exercise - Preparation
● Configure the ethernet port “VMNet0” on the PC VM to have the following IP Addresses
192.168.100.100+x, 192.168.111.100+x (use the advanced setting)192.168 where x is
your station number and you have a subnet mask of 255.255.255.0
● For example if you are station 9:
●The IP addresses of your laptop will be 192.168.100.109,
192.168.111.109
Confidential property of Schneider Electric 47

Exercise – Unity Pro V13.1
● Open Unity Pro and configure an M580 CPU which satisfies the following requests..
1. Configure a BMEP584040S CPU with IP address (8 Slot Ethernet Rack)
● 192.168.11.1, SM 255.255.0.0 (this is your primary address).
● 192.168.11.2 this will be your A address .
● Change the project properties from “project” to “Texpert 2018 SLC1”
● Save the project as “Network 1.001.STU”.
2. Use Unity Pro to configure as many BMENOC03*1.4 modules as the software allows. How many modules can you configure?
● Answer:
3. Now change the configuration, you need 4 ethernet modules how can you do this?
(hint: use 1 x BMENOP0300 and some of the following BMXNOR0200, BMXNGD0100,).
● Which of these modules support Modbus TCP/IP?
● Answer:
4. Configure the BMENOP module to support Modbus TCPIP.

● Enable the Data dictionary under the Tools \ Project Settings \ PLC embedded Data
● Select the module for slot 4.
● Open the module and create an IP address of 192.168.111.49.
● Create a module name “Texpert” in the project box and validate the changes.

Exercise – Unity Pro V13.1 (Continued…)
● Open Unity Pro and configure an M580 CPU which satisfies the following requests..
4. Step 4 continued ….
● The IEC61850 configuration button should change to green so you can open the configuration tool. Create a new project and
select the default options
● On the “texpert \ General” tab page leave the Goose Publish \ Auto Enable, IEC61850 client and the IEC61850 server tick boxes
unchecked.
● Change the “General” Tab drop down to the “General \ Communication Settings” tab and open the “Switch” tab, and enable the
backplane port.
● Apply changes, Close the configuration tool and Save all settings. “Update application”. “Rebuild all” the complete project,
making sure there are no errors.
● Save the project as “Network 1.04.STU”.
5. Can you find a means to disable the CPU backplane port in CPU ethernet settings?
●Answer:
6. Configure a single BMENOC0311.4 module in slot 5, with an IP address:
● 192.167.13.1, SM: 255.255.0.0.
● Via the DTM Browser and the Switch settings for the NOC module. Enable the backplane port.
7. Connect the PC via ethernet cable to the CPU control port (port 2 or 3), can you ping the NOC module?
● Answer:
8. Configure the service port on the CPU to mirror the traffic on the backplane port and the control ports.
9. Save the project as “Network 1.10.STU”

Exercise 2.1 – 2.3
1. Open Unity Pro and configure an M580 CPU. Now design a
project in unity which satisfies the following requests..
1. Open the project “Network 1.010.STU”.
2. Change the master task properties for the Process logic:
● Run in periodic mode at 20ms intervals.
● Configure ERIO X80 Drop 1.
– BMEXBP0800, BMXCPS3020, BMECRA31210, BMXDRA0805 or
BMXDRA1605 relay module in slot 3
● Open the master task properties and change to 20ms Periodic….
● When the application is built, connect via USB to the PLC and
download the application to the CPU.
● Start and run the application.
● Reconnect to the PLC CPU service port using the ethernet cable
● Save the project as “Network 2.03.stu”.
● Work with a neighbour and ask the neighbour to put a BMECRA31210
module in their rack.
● Configure the module switch settings and test operation, by turning
on and off one or more relay outputs

Exercise 2.4
Wireshark
4. Use Wireshark to monitor ERIO and backplane traffic.
● Open the Wireshark application.
● Select menu options “Capture \ Options”
● Verify that “VMNet0” is selected and confirm there is traffic activity.
● Enable promiscuous mode on all interfaces
● Start capture
● The following page has a list of useful filter options, to help you with the following tasks.

Exercise 2.4
Wireshark – Filter details
Key filters used in this application are:
● enip – for selection of Ethernet / IP traffic
● !enip – for omission of Ethernet / IP traffic, the “!” is used to invert the answer.
● arp – for selection of ARP traffic
● ip.src == 192.168.20.13 – for selection of traffic originating from ip address 192.168.20.13.
● !ip.src == 192.168.20.11 – for omission of traffic from this address.
● ip.len < 190 – used to select traffic which has a packet length less than 190.
● && - used to AND two conditions together to ensure the result satisfied both sets of criteria.
● || - used to OR two or more conditions so the result is one or the other condition or both.
● () – parentheses are used to group expressions together and enforce solving the conditions
within the parentheses set before executing external commands.
● Ip.src == 192.168.20.17 && enip && ip.len > 190 – was used to select ethernet/IP traffic from
(ip address 192.168.20.17). The packet length in this test was always 206.
● icmp – used to detect ping traffic.

.
Exercise 2.5
Wireshark – IO graph details
This tool is used to display the traffic in
graphical form. Selection of the tool and a
typical screen with filters defined are shown
below.
For testing purposes, the settings shown in
Figure 13 are worth noting.
•Apply filters as mentioned in previous
pages.
•Set the display interval to 100ms – longer
time intervals provide an overview of activity
but mask finer spike activity.
•Use the mouse zoom function to investigate
disturbances.
•Use Shift Y / Y to adjust the scale resolution
and up / down or left right arrows to centre
the graph.

5. Wireshark filtering and analysis
● Enter the “arp” filter. Which devices are not connected? Answer:
● Alter the filter to include the ethernet IP traffic “enip || arp”
● Stop the capture.
● Open the “Statistics \ IO Graph” (see previous page)
● Add a graph filter with a pink trace to identify enip traffic which is sourced from the CPU.
● Add a graph filter with a blue trace to identify enip traffic which is sourced from the CRA module.
● Select the mouse zoom mode and expand the Time axis so you can see the traces.
● You may need to zoom out of the Y axis to see both traces.
● How often is each enip traffic updating in “packets per 100ms”? Answer:
● What is the update rate settings from the CRA module configuration?
● What is the scan time of the CPU?
● Save the capture for future reference.
● Save the IO Graph for future reference.
6. Connect to either port 2 or 3 of the CPU and perform the same test.
● Do you see any enip traffic?
● Why is this the case?
● This is the reason to ensure you do not connect EDIO to the ERIO network..
Exercise 2.7
7. Setting a unique identifier for CRA modules.
When sharing:
● the same ERIO network amongst two or more CPUs, or
● connecting the service port or the CPU to another CPU.
the “network identifier” must be unique for each BM*CRA312*0 module.
●To do this: 1. Open the Ethernet network, 2. Modify the extension number to a unique value in this case 009.

● Open Unity Pro and configure an M580 CPU. Now design a project in unity which satisfies the following
requests..
1. Work with your neighbour to configure one of the three options for communications.
2. Open the project “Network 2.03.STU”.
3. Open the DTM browser:
4. Right mouse click on the BMECPUP584040S module and add the “BMENOC0311 Revision 2.2” DTM.
5. Label the DTM “SLC1_eNOC0311_s05” where we are talking to SLC1 NOC module in slot 05.
6. Double click on the new device in the DTM browser.
7. Select Local Slave 1 – Exclusive owner
8. Change the input size and output size from 128 to 8. Press “OK”
9. Open the BMENOC0311 module in the DTM browser.

Exercise 3.10
● Configure Ethernet IP DTMs..
10. Scroll down to the Device List and click on
the new DTM “SLC1_eNOC0311_s05”
● Change the Import mode to “Manual”
● Modify the IP address of new DTM
instance to match the IP address of
BMENOC0311 module …
192.168.13.1. Now press “Apply”
● Open the “Items” list and configure as
shown in the diagram steps 1 – 8,
● Select the “Output” tab (9)
● Repeat the steps 1 to 8 for the
“Output” tab calling the array the
“Out_Array”
● Press “OK”
● Rebuild the project, once successful
save it as “Network 3. 10.STU”

Exercise 3.11
Ethernet / IP communications
Configure Ethernet IP DTMs..
11. At the neighbour’s PLC, ensure the
BMENOC0311 slave 1 is configured with
the same parameters:
‒ Double Click on the “eNOC0311_s05”
DTM in the DTM browser.
‒ Double Click on the “Local Slave 1” in the
configuration menu.
‒ Change the Assembly Outputs to “8”
bytes
‒ Change the Assembly Inputs to “8” bytes
‒ Press “Apply”
‒ Define the items as shown in steps 1 – 9,
‒ Perform the same changes for the
outputs (10), as per steps 1-9 as shown
in the diagram.
‒ Select “OK”
‒ Rebuild all, save the changes as
“Network 3-11.STU” and download to the
PLC.
Exercise 3.12
Ethernet / IP communications
Test the application..
12. Open the “Data Editor” and select:
‒ “eNOC0311_s05_LS1” variable,
‒ “SLC1_eNOC0311_s05” variable
‒ Copy these to the animation table.
‒ Expand the variables
‒ Select Modify the variables.
‒ Enter numbers in the output arrays and
verify the corresponding input arrays
show the same value.

Exercise 4.1
1. Using the DTM Audit Tool.
Open the Unity Pro “C:\Users\Public\Documents\Schneider Electric\Unity Pro\Extras\ DTM Audit Tool:” folder..
● Run the “DTMAuditToolUI.exe” application.
● “Choose a file” – selecting the target project application you wish to assess.
● Then press “Run”

Exercise 1.2 - Answer

Exercise Answers
● 1.3 – NOR, NOP support Modbus TCPIP, NGD module does not support Modbus TCP/IP
● 1.5 – You cannot disable the CPU backplane port
● 1.7 – you should be able to ping the NOC module in slot 5 even if it is on a different subnet.
● 2.5 - 62ms mast task process update from CRA to CPU, 10ms update from Safe IO to CPU
● 2.5 - 62ms mast task process update from CPU to CRA, 22ms update from SAFE CPU to CRA
● 2.6 - we will not see any ENIP traffic on the control ports as the traffic is tagged to VLAN1 and the
wireshark is unable to pick this up.

M580 Networking and Communication

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

M580 Networking and Communication

Загружено:

Авторское право:

Доступные форматы

M580 Networking & Communication WS

Ethernet is the core of the ePAC.

Confidential Property of Schneider Electric | Page 2

M580 ERIO Networks

Ask Questions at any time

M580 Device Communications

Confidential Property of Schneider Electric | Page 3

1. Difference between the BMEP584020 (EDIO) and the

Confidential Property of Schneider Electric | Page 4

Backplane is a dual bus rack with proprietary

Two pathways to the CPU, X-Bus and ethernet.

The same for the eNOC module.

Confidential Property of Schneider Electric | Page 6

NOTE: Hot Standby implications for

1. Primary address changes.

2. IP Address A and IP Address B

Confidential Property of Schneider Electric | Page 7

Confidential Property of Schneider Electric | Page 8

Confidential Property of Schneider Electric | Page 9

Confidential Property of Schneider Electric | Page 11

Access list – by default if you enable this port 502 is

M580 ERIO Networks

Ask Questions at any time

M580 Device Communications

Confidential Property of Schneider Electric | Page 13

1. What is so special about the ERIO network?

Confidential Property of Schneider Electric | Page 14

ERIO is effectively a proprietary network

It can work, no performance guarantee , limited support.

Confidential Property of Schneider Electric | Page 16

Confidential Property of Schneider Electric | Page 17

Confidential Property of Schneider Electric | Page 18

Confidential Property of Schneider Electric | Page 19

Cost-effectiveness – A shared ring

Power – Multiple, independent M580

Confidential Property of Schneider Electric | Page 20

• The general rules for ring redundancy still hold:

• A DRS switch counts as two devices (CRA, CPU, DRS)

• A CPU and a CRA module each count as one

Confidential Property of Schneider Electric | Page 21

Confidential Property of Schneider Electric | Page 22

M580 ERIO Networks

Ask Questions at any time

M580 Device Communications

Confidential Property of Schneider Electric | Page 23

1. What are my options for peer to peer communications?

2. What is IO scanning using Modbus TCP/IP?

Confidential Property of Schneider Electric | Page 24

Confidential Property of Schneider Electric | Page 26

Confidential Property of Schneider Electric | Page 27

Confidential Property of Schneider Electric | Page 31

Confidential Property of Schneider Electric | Page 32

Confidential Property of Schneider Electric | Page 33

Confidential Property of Schneider Electric | Page 34

M580 ERIO Networks

Ask Questions at any time

M580 Device Communications

Confidential Property of Schneider Electric | Page 35

1. What issues are there with DTMs?

Confidential Property of Schneider Electric | Page 36

Confidential Property of Schneider Electric | Page 37

ERIO/EDIO ERIO EDIO PAC EDIO

… 7 Hops to EDIO device #7

Confidential Property of Schneider Electric | Page 40