Industrial Ethernet Presentation
Industrial Ethernet is the term used to represent the industrial protocols that use the standard Ethernet physical layer and standard Ethernet protocols.
On an Industrial Ethernet network, you can connect:
oindustrial devices (industrial protocols)
onon-industrial devices (other Ethernet protocols)
For more information, refer to Industrial Ethernet User Guide.
Industrial Ethernet Architecture
This figure presents a typical Industrial Ethernet architecture:
This architecture is configurable with EcoStruxure Machine Expert.
Industrial Ethernet Description
|
M262 Logic/Motion Controller |
|
|---|---|
|
Features |
Description |
|
Topology |
Daisy chain and Star via switches |
|
Bandwidth |
10/100 Mbit/s for Ethernet 1 port 10/100/1000 Mbit/s for Ethernet 2 port |
|
EtherNet/IP Scanner |
|
|
Performance |
Up to 64(1) EtherNet/IP target devices managed by the logic controller, monitored within a timeslot of 20 ms |
|
Number of connections |
0...64(1) |
|
Number of input words |
0...15360 |
|
Number of output words |
0...15360 |
|
I/O communications |
EtherNet/IP Scanner service Function block for configuration and data transfer |
|
Originator/Target |
|
|
Modbus TCP IOScanner |
|
|
Performance |
Up to 64 Modbus TCP slave devices managed by the logic controller, monitored within a timeslot of 64 ms. |
|
Number of connections |
0...64(1) |
|
Number of input words |
0...8000 |
|
Number of output words |
0...8000 |
|
I/O communications |
Modbus TCP IOScanner service Function block for data transfer |
|
Master/Slave |
|
|
Sercos |
|
|
Performance |
Refer to Performance Overview. |
|
Other services |
FDT/DTM/EDS management |
|
FDR (Fast Device Replacement) |
|
|
DHCP server |
|
|
Security management (refer to Security Parameters and Firewall Configuration) |
|
|
Modbus TCP server |
|
|
Modbus TCP client |
|
|
EtherNet/IP adapter (controller as a target on EtherNet/IP) |
|
|
EtherNet/IP Originator |
|
|
Modbus TCP server (controller as a slave on Modbus TCP) |
|
|
Web server |
|
|
FTP server |
|
|
SNMP |
|
|
IEC VAR ACCESS |
|
|
Additional features |
You can mix the Ethernet/IP and Modbus TCP server devices: o96 on TM262L10MESE8T and TM262M15MESS8T o128 on TM262L20MESE8T, TM262M25MESS8T and TM262M35MESS8T. Devices can be directly accessed for configuration, monitoring, and management purposes. Network transparency between control network and device network (controller can be used as a gateway). NOTE: Using the controller as a gateway can impact the performance of the controller. |
|
(1) 0...6 on Ethernet_1 port of TM262M•. |
|
EtherNet/IP is the implementation of the CIP protocol over standard Ethernet.
The EtherNet/IP protocol uses an Originator/Target architecture for data exchange.
Originators are devices that initiate data exchanges with Target devices on the network. This applies to both I/O communications and service messaging. This is the equivalent of the role of a client in a Modbus network.
Targets are devices that respond to data requests generated by Originators. This applies to both I/O communications and service messaging. This is the equivalent of the role of a server in a Modbus network.
EtherNet/IP Adapter is an end-device in an EtherNet/IP network. I/O blocks and drives can be EtherNet/IP Adapter devices.
The communication between an EtherNet/IP Originator and Target is accomplished using an EtherNet/IP connection.
The Modbus TCP protocol uses a Client/Server architecture for data exchange.
The Modbus TCP explicit (non-cyclic) data exchanges are managed by the application.
Modbus TCP implicit (cyclic) data exchanges are managed by the Modbus TCP IOScanner. The Modbus TCP IOScanner is a service based on Ethernet that polls slave devices continuously to exchange data, status, and diagnostic information. This process monitors inputs and controls outputs of slave devices.
Clients are devices that initiate data exchange with other devices on the network. This applies to both I/O communications and service messaging.
Servers are devices that address any data requests generated by a Client. This applies to both I/O communications and service messaging.
The communication between the Modbus TCP IOScanner and the slave device is accomplished using Modbus TCP channels.
For more information on Sercos standard and configuration, refer to Overview of the Sercos Standard.
The protocol manager must be present on the Ethernet_1 (ETH1) and Ethernet_2 (ETH2) nodes of the device tree to activate these functions and services:
oEtherNet/IP Scanner
oGeneric TCP/UDP Manager
oModbus TCP IO Scanner
When a Protocol manager is defined on an interface, this interface address must be Fixed. The post-configuration defined for this interface is not applied, if any.
The protocol manager is available by default under the Ethernet_1 (ETH1) and Ethernet_2 (ETH2) nodes. It is automatically added when a slave device is added on the Ethernet_1 (ETH1) or Ethernet_2 (ETH2) node.
To manually add the a function or service to the Ethernet_1 (ETH1) or Ethernet_2 (ETH2), select the protocol manager in the Hardware Catalog and drag and drop it on one of the highlighted nodes.
For more information on adding a device to your project, refer to:
• Using the Drag-and-drop Method
• Using the Contextual Menu or Plus Button
The Sercos fieldbus must be present on the Ethernet_1 (ETH1) to activate the Sercos Master. It is automatically added when a slave device is added on the Ethernet_1 (ETH1) node.
To manually add Sercos Master to the Ethernet_1 (ETH1), select Sercos Master in the Hardware Catalog and drag and drop it on one of the highlighted nodes.
For more information on adding a device to your project, refer to:
• Using the Drag-and-drop Method
• Using the Contextual Menu or Plus Button
