- •Important Comments
- •Legal Principles
- •Copyright
- •Personnel Qualification
- •Intended Use
- •Symbols
- •Font Conventions
- •Number Notation
- •Scope
- •Important Comments for Starting up
- •Abbreviation
- •The WAGO-I/O-SYSTEM 750
- •Technical Data
- •Manufacturing Number
- •Storage, Assembly and Transport
- •Mechanical Setup
- •Installation Position
- •Total Expansion
- •Assembly onto Carrier Rail
- •Carrier rail properties
- •WAGO DIN Rail
- •Spacing
- •Plugging and Removal of the Components
- •Assembly Sequence
- •Internal Bus / Data Contacts
- •Power Contacts
- •Wire connection
- •Power Supply
- •Isolation
- •System Supply
- •Connection
- •Alignment
- •Field Supply
- •Connection
- •Fusing
- •Supplementary power supply regulations
- •Supply example
- •Power Supply Unit
- •Grounding
- •Grounding the DIN Rail
- •Framework Assembly
- •Insulated Assembly
- •Grounding Function
- •Grounding Protection
- •Shielding (Screening)
- •General
- •Bus Conductors
- •Signal Conductors
- •WAGO Shield (Screen) Connecting System
- •Assembly Guidelines / Standards
- •Fieldbus Controller
- •Fieldbus Controller 750-841
- •Description
- •Hardware
- •View
- •Device Supply
- •Fieldbus Connection
- •Display Elements
- •Configuration and Programming Interface
- •Operating Mode Switch
- •Hardware Address (MAC-ID)
- •Operating System
- •Start-up
- •PLC Cycle
- •Process Image
- •Example of a Process Input Image
- •Example of a Process Output Image
- •Fieldbus specific Process Data Architecture for MODBUS/TCP
- •Digital Input Modules
- •Digital Output Modules
- •Analog Input Modules
- •Analog Output Modules
- •Specialty Modules
- •Data Exchange
- •Memory Areas
- •Addressing
- •Addressing the I/O Modules
- •Address Range
- •Absolute Addresses
- •Data Exchange between MODBUS TCP Master and I/O Modules
- •Data Exchange between Ethernet IP Master and I/O Modules
- •Data Exchange between PLC Functionality (CPU) and I/O Modules
- •Data Exchange between Master and PLC Functionality (CPU)
- •Example MODBUS TCP Master and PLC functionality (CPU)
- •Comparison of MODBUS TCP Addresses and IEC 61131-3 Addresses
- •Starting up an ETHERNET TCP/IP fieldbus node
- •Connecting PC and Fieldbus Node
- •Determining IP Addresses
- •Allocating the IP Address to the Fieldbus Node
- •Testing the Function of the Fieldbus Node
- •Deactivating the BootP Protocol
- •Programming the PFC with WAGO-I/O-PRO CAA
- •WAGO-I/O-PRO CAA library elements for ETHERNET
- •IEC 61131-3-Program transfer
- •Transmission via the Serial Interface
- •Transmission by the Fieldbus
- •Information on the web-based management system
- •LED Display
- •Blink code
- •Fieldbus status
- •Node status
- •Fault Message via Blink Code from the I/O-LED
- •Supply voltage status
- •Fault behavior
- •Fieldbus failure
- •Internal bus fault
- •Technical Data
- •I/O Modules
- •General
- •Digital Input Modules
- •Digital Output Modules
- •Analog Intput Modules
- •Analog Output Modules
- •Counter Modules
- •ETHERNET
- •General
- •Network Architecture – Principles and Regulations
- •Transmission Media
- •Network Topologies
- •Coupler Modules
- •Important Terms
- •Network Communication
- •Protocol layer model
- •Communication Protocols
- •ETHERNET
- •Channel access method
- •IP-Protocol
- •IP Multicast
- •TCP Protocol
- •Application Protocols
- •MODBUS
- •Ethernet/IP
- •BootP (Bootstrap Protocol)
- •HTTP (HyperText Transfer Protocol)
- •DHCP (Dynamic Host Configuration Protocol)
- •DNS (Domain Name Systems)
- •SNTP-Client (Simple Network Time Protocol)
- •FTP-Server (File Transfer Protocol)
- •SNMP V1 (Simple Network Management Protocol)
- •Configuration of SNMP
- •Description of MIB II
- •IpNetToMediaTable
- •Traps
- •SMTP (Simple Mail Transfer Protocol)
- •MODBUS Functions
- •General
- •Use of the MODBUS Functions
- •Description of the MODBUS Functions
- •Function Code FC1 (Read Coils)
- •Function Code FC2 (Read Input Discretes)
- •Function Code FC3 (Read multiple registers)
- •Function code FC4 (Read input registers)
- •Function Code FC5 (Write Coil)
- •Function Code FC6 (Write single register)
- •Function Code FC11 (Get comm event counter)
- •Function Code FC15 (Force Multiple Coils)
- •Function Code FC16 (Write multiple registers)
- •Function Code FC22 (Mask Write Register)
- •Function Code FC23 (Read/Write multiple registers)
- •MODBUS Register Mapping
- •Internal Variables
- •Description of the internal variables
- •Watchdog (Fieldbus failure)
- •Watchdog Register:
- •Diagnostic Functions
- •Configuration Functions
- •Firmware Information
- •Constant Registers
- •Ethernet/IP (Ethernet/Industrial Protocol)
- •General
- •Characteristics of the Ethernet/IP Protocol Software
- •Object model
- •General
- •Classes
- •CIP Common Classes
- •Static Assembly Instances
- •Application examples
- •Test of MODBUS protocol and fieldbus nodes
- •Visualization and control using SCADA software
- •Use in Hazardous Environments
- •Foreword
- •Protective measures
- •Classification meeting CENELEC and IEC
- •Divisions
- •Explosion protection group
- •Unit categories
- •Temperature classes
- •Types of ignition protection
- •Classifications meeting the NEC 500
- •Divisions
- •Explosion protection groups
- •Temperature classes
- •Identification
- •For Europe
- •For America
- •Installation regulations
172 • Ethernet/IP (Ethernet/Industrial Protocol)
General
7 Ethernet/IP (Ethernet/Industrial Protocol)
7.1 General
Ethernet/IP is a communication system that enables devices to exchange timecritical application data in an industrial environment. The spectrum of devices ranges from simple I/O devices (e.g., sensors) through to complex controllers (e.g., robots).
Ethernet/IP uses CIP (Control and Information Protocol), which is implemented on the fourth layer in the ISO/OSI reference model (transport layer), and is also used by DeviceNet and ControlNet. Therefore, converting from one of these protocols to Ethernet/IP is easy to do.
Ethernet/IP uses the standard Ethernet and TCP/IP technology (IEEE 802.3) to transmit the CIP communication packets.
In order to clarify the interrelationships between DeviceNet, ControlNet and Ethernet/IP, the following diagram presents the associated ISO/OSI reference model.
|
|
Application device profiles |
|
|
|
|
|
(e.g. positioning controllers, semi-conductors, pneumatic valves) |
|
||||
7 |
Application |
CIP application object library |
|
|
||
|
layer |
|
CIP |
|||
|
|
|
|
|
||
6 |
Presentation |
CIP data management services |
|
|||
|
|
|||||
|
layer |
(explicit messages, I/O messages) |
|
|
||
5 |
Session |
CIP message routing, connection management |
|
|||
|
layer |
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 |
Transport |
DeviceNet or ControlNet |
|
Encapsulation |
|
|
|
layer |
|
protocol |
|
||
|
transport |
|
|
|||
|
|
|
|
|
|
|
3 |
Network |
(transmission control, |
|
TCP |
UDP |
|
|
layer |
addressing) |
|
IP |
|
ETHERNET/IP |
|
|
|
|
|||
|
|
|
|
|
||
2 Data Link |
CAN (CSMA/NBA) or |
|
Ethernet |
|||
|
|
|||||
|
layer |
ControlNet (CTDMA) |
|
(CSMA/CD) |
|
|
1 |
Physical |
DeviceNet or ControlNet |
|
Ethernet |
|
|
|
layer |
physical interface |
|
physical interface |
|
|
|
|
|
|
|
|
|
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
Ethernet/IP (Ethernet/Industrial Protocol) • 173
Characteristics of the Ethernet/IP Protocol Software
7.2 Characteristics of the Ethernet/IP Protocol Software
Level 1 |
Level 1: |
Explicit Messages Server |
Level 2 |
Level 2: |
Level 1 + I/O Messages Server |
•Unconnected Message Manager (UCMM) Client and Server
•128 Encapsulation Protocol sessions
•128 Class 3 or Class 1 Connections combined
Class 3 connection – explicit messages (connection oriented, client and server) Class 1 connection – I/O messages (connection oriented, client and server)
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP