- •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 • 73
Data Exchange
3.1.5.6 Data Exchange between Master and PLC Functionality (CPU)
The fieldbus master and the PLC functionality of the controller regard the data in a different manner.
Variable data created by the fieldbus master reaches the PFC as input variables. Data created in the PFC is sent to the fieldbus master through output variables.
In the PFC, the controller can access the MODBUS TCP PFC variable data from word address 256 to 511 (double word address 128-255, byte address 512-1023) and the Ethernet IP PFC variable data from word address 1276 to 1531 (double word address 638-765, byte address 2552-3063).
3.1.5.6.1 Example MODBUS TCP Master and PLC functionality (CPU)
Data Access by the MODBUS TCP Master
With MODBUS TCP, the fieldbus master can access controller data as words or bits.
When accessing the first 256 words of memory from the Fieldbus port (physical I/O modules), the I/O modules start with the address 0 for both bit and word access.
When accessing data from the starting memory address of 256, the bit and word addresses follow the sequence below:
4096 for bit 0 in word 256
4097 for bit 1 in word 256
...
8191 for bit 15 in word 511.
The bit number can be calculated from the following formula:
BitNo = (Word * 16) + Bitno_in_Word
Data Access by the PLC Functionality
When accessing the same data from both a PLC and Fieldbus master, the following memory address conventions should be understood:
A 16 bit IEC 61131-3 variable uses the same addressing as the MODBUS word format.
An IEC 61131-3 boolean variable (1 bit) uses a “WORD.BIT” notation for addressing, which is different from MODBUS’s bit notation.
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
74 • Fieldbus Controller 750-841
Data Exchange
The “WORD.BIT” notation is composed of the boolean’s word address and bit number in the word, separated by a dot. The Word and Bit values are zero based (e.g., %IX0.0 is the first possible digital input).
Example:
MODBUS bit number 19 => bit addressing in PLC <Wordno>.<Bitno> = 1.2
The PLC functionality of the PFC can also access the data as Bytes and
DoubleWords.
The byte addresses are computed according to the following formula:
High-Byte Address = Word address*2
Low-Byte Address = (Word address*2) + 1
The double word address is computed according to the following formula: Double word address = High word address/2 (rounded off)
or = Low word address/2
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
