- •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
Fieldbus Controller 750-841 • 69
Data Exchange
Addressing Example:
Address calculation (depending upon the word address):
Bit address: |
word address .0 to .15 |
|
Byte address: |
1. |
Byte: 2 x word address |
|
2. |
Byte: 2 x word address + 1 |
Dword address: |
word address (even numbers) / 2 |
|
|
or |
word address (uneven numbers) / 2, rounded off |
3.1.5.3 Data Exchange between MODBUS TCP Master and I/O Modules
The data exchange between the MODBUS TCP master and the I/O modules is made via the Ethernet Fieldbus port using MODBUS TCP read and write commands.
The controller handles four different types of process data with MODBUS TCP:
•Input words
•Output words
•Input bits
•Output bits
The relationship between bits and words are defined in the table below:
Digital inputs/outputs |
16. |
15. |
14. |
13. |
12. |
11. |
10. |
9. |
8. |
7. |
6. |
5. |
4. |
3. |
2. |
1. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
Prozess data word |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
Bit |
|
15 |
14 |
13 |
12 |
11 |
10 |
9 |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
||
|
|||||||||||||||||
Byte |
High-Byte |
|
|
|
|
|
|
Low-Byte |
|
|
|
|
|
|
|||
D1 |
|
|
|
|
|
|
|
D0 |
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
Table 3.9: Allocation of Digital Inputs/Outputs to Process Data Word in Intel Format
WAGO-I/O-SYSTEM 750
ETHERNET TCP/IP
70 • Fieldbus Controller 750-841
Data Exchange
Adding an offset of 0x0200 to the MODBUS output address lets you read back output data.
Note
For MODBUS mapping, all output data over 256 words resides in the memory area 0x6000 to 0x62FC, and can be read back with an offset of 1000hex (0x1000) added onto the MODBUS address.
|
MODBUS master |
||
0x0000 |
0x6000 |
0x0000 |
0x6000 |
|
|
(0x0200) |
(0x7000) |
|
PII |
|
PIO |
|
|
00x0FF |
0x62FC |
0x00FF |
0x62FC(0x02FF) |
(0x72FC) |
|
Inputs |
|
|
Outputs |
|
I/O modules |
|
|
|
|
|
PII = Process Input |
|
|
|
Image |
|
|
|
PIO = Process Output |
|
|
|
Image |
Programmable Fieldbus Controller
Fig. 3-9: Data exchange between MODBUS master and I/O modules |
g015045e |
The MODBUS register assignments allow for a Fieldbus Master to read and write data from the controller. The register mapping for IEC 61131.1 varies from the MODBUS assignments. Please refer to section 3.1.5.6.2 for a comparison of MODBUS TCP and IEC 61131.1 address mapping.
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
Fieldbus Controller 750-841 • 71
Data Exchange
3.1.5.4 Data Exchange between Ethernet IP Master and I/O Modules
Data exchange between the Ethernet IP master and the I/O modules is object oriented. Each node in the network is represented as a collection of objects. The “assembly” object defines the structure of objects for data transfer. With the assembly object, data (e.g. I/O data) can be grouped into blocks (mapped) and sent via a single communication link. As a result of this mapping technique, fewer access operations to the network are required.
Input and output assemblies have different functions.
An input assembly reads data from the application over the network or produces data on the network.
Where as, an output assembly writes data to the application or consumes data from the network.
Various assembly instances are permanently pre-programmed in the fieldbus controller (static assembly).
After switching on the power supply, the assembly object maps data from the process image. As soon as a connection is established, the master can address the data with "class", "instance" and "attribute" and access or read and/or write the data via I/O links.
The mapping of the data depends on the chosen assembly instance of the static assembly.
Further information
The assembly instances for the static assembly are described in the section
7.3.2.6 "Assembly (04 hex)".
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
72 • Fieldbus Controller 750-841
Data Exchange
3.1.5.5 Data Exchange between PLC Functionality (CPU) and I/O Modules
Through absolute addresses, the PLC functionality of the controller can directly address the I/O module data.
The PFC addresses the input data with absolute addresses. The data can then be processed, internally in the controller, through the IEC 61131-3 program, whereby the flags are filed in a permanent memory area. Following this, the linking results can be directly written in the output data via absolute addressing.
Inputs |
|
|
Outputs |
|
I/O modules |
750-4xx....6xx |
|
%IW0 |
%IW512 |
%QW0 |
%QW512 |
|
PII |
|
PIO |
%IW255 |
%IW1275 |
%QW255 |
%QW1275 |
Inputs |
|
|
Outputs |
PLC functionality (CPU) |
|||
|
|
|
PII = Process Input |
|
|
|
Image |
|
|
|
PIO = Process Output |
|
|
|
Image |
Programmable Fieldbus Controller
Fig. 3-10: Data exchange between PLC functionality (CPU) and I/O modules 15043e
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
