STL-ETH1-Ethernet_UserManual_750

Manual
WAGO-I/O-SYSTEM 750
ETHERNET Fieldbus Coupler
750-352
10/100 Mbit/s; digital and analog Signals
Version 1.1.0
2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
© 2011 by WAGO Kontakttechnik GmbH & Co. KG
All rights reserved.
WAGO Kontakttechnik GmbH & Co. KG
Hansastraße 27
D-32423 Minden
Phone:
Fax:
+49 (0) 571/8 87 – 0
+49 (0) 571/8 87 – 1 69
E-Mail:
[email protected]
Web:
http://www.wago.com
Technical Support
Phone:
Fax:
+49 (0) 571/8 87 – 5 55
+49 (0) 571/8 87 – 85 55
E-Mail:
[email protected]
Every conceivable measure has been taken to ensure the accuracy and
completeness of this documentation. However, as errors can never be fully
excluded, we always appreciate any information or suggestions for improving the
documentation.
E-Mail:
[email protected]
We wish to point out that the software and hardware terms as well as the
trademarks of companies used and/or mentioned in the present manual are
generally protected by trademark or patent.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
3
Table of Contents
1
1.1
1.2
1.3
1.4
1.5
Notes about this Documentation............................................................... 10
Validity of this Documentation............................................................... 10
Copyright................................................................................................. 10
Symbols................................................................................................... 11
Number Notation..................................................................................... 13
Font Conventions .................................................................................... 13
2
Important Notes ......................................................................................... 14
2.1
Legal Bases ............................................................................................. 14
2.1.1
Subject to Changes ............................................................................. 14
2.1.2
Personnel Qualifications..................................................................... 14
2.1.3
Use of the 750 Series in Compliance with Underlying Provisions .... 14
Technical Condition of Specified Devices ......................................... 15
2.1.4
2.2
Safety Advice (Precautions).................................................................... 16
3
System Description..................................................................................... 18
3.1
Manufacturing Number ........................................................................... 19
3.2
Hardware Address (MAC ID) ................................................................. 19
3.3
Component Update.................................................................................. 20
3.4
Storage, Assembly and Transport ........................................................... 21
3.5
Assembly Guidelines/Standards.............................................................. 22
3.6
Power Supply .......................................................................................... 23
3.6.1
Isolation .............................................................................................. 23
3.6.2
System Supply .................................................................................... 24
3.6.2.1
Connection..................................................................................... 24
3.6.2.2
Alignment ...................................................................................... 25
3.6.3
Field Supply........................................................................................ 28
3.6.3.1
Connection..................................................................................... 28
3.6.3.2
Fusing ............................................................................................ 29
3.6.4
Supply Example.................................................................................. 33
Power Supply Unit ............................................................................. 34
3.6.5
3.7
Grounding ............................................................................................... 35
3.7.1
Grounding the DIN Rail ..................................................................... 35
3.7.1.1
Framework Assembly .................................................................... 35
3.7.1.2
Insulated Assembly........................................................................ 35
3.7.2
Grounding Function............................................................................ 36
3.7.3
Grounding Protection ......................................................................... 37
3.8
Shielding (Screening).............................................................................. 38
3.8.1
General ............................................................................................... 38
3.8.2
Bus Conductors .................................................................................. 38
3.8.3
Signal Conductors .............................................................................. 38
3.8.4
WAGO Shield (Screen) Connecting System...................................... 39
4
Device Description ..................................................................................... 40
4.1
View ........................................................................................................ 42
4.2
Connectors............................................................................................... 44
4.2.1
Device Supply .................................................................................... 44
4.2.2
Fieldbus Connection........................................................................... 45
Manual
Version 1.1.0
4
Table of Contents
4.3
4.4
4.4.1
4.4.2
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.5.7
4.5.8
4.5.9
4.5.10
4.6
4.7
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Display Elements .................................................................................... 46
Operating Elements ................................................................................. 47
Service Interface................................................................................. 47
Address Selection Switch ................................................................... 48
Technical Data ........................................................................................ 49
Device Data ........................................................................................ 49
System Data........................................................................................ 49
Safe electrical Isolation ...................................................................... 49
Degree of protection ........................................................................... 49
Supply................................................................................................. 50
Fieldbus MODBUS/TCP.................................................................... 50
Accessories ......................................................................................... 50
Wire Connection................................................................................. 50
Climatic Environmental Conditions ................................................... 51
Mechanical strength............................................................................ 51
Approvals ................................................................................................ 52
Standards and Guidelines........................................................................ 53
5
Assembly ..................................................................................................... 54
5.1
Installation Position................................................................................. 54
5.2
Total Extension ....................................................................................... 54
5.3
Assembly onto Carrier Rail..................................................................... 56
5.3.1
Carrier Rail Properties........................................................................ 56
5.3.2
WAGO DIN Rail................................................................................ 57
5.4
Spacing.................................................................................................... 57
5.5
Assembly Sequence ................................................................................ 58
5.6
Inserting and Removing Devices ............................................................ 59
5.6.1
Inserting the Fieldbus Coupler/Controller.......................................... 60
5.6.2
Removing the Fieldbus Coupler/Controller ....................................... 60
5.6.3
Inserting I/O Module .......................................................................... 61
5.6.4
Removing the I/O Module.................................................................. 62
6
6.1
6.2
6.3
Connect Devices ......................................................................................... 63
Data Contacts/Internal Bus ..................................................................... 63
Power Contacts/Field Supply.................................................................. 64
Connecting a conductor to the CAGE CLAMP® .................................... 65
7
Function Description ................................................................................. 66
7.1
Operating System .................................................................................... 66
7.2
Process Data Architecture ....................................................................... 67
7.3
Data Exchange ........................................................................................ 69
7.3.1
Addressing.......................................................................................... 70
7.3.1.1
Addressing of I/O Modules ........................................................... 70
7.3.1.2
Address Ranges ............................................................................. 71
7.3.2
Data Exchange between MODBUS/TCP Master and I/O Modules... 72
7.3.2.1
Data Exchange between EtherNet/IP Master and I/O Modules .... 73
8
Commissioning ........................................................................................... 75
Connecting Client PC and Fieldbus Nodes ............................................. 76
8.1
8.2
Allocating the IP Address to the Fieldbus Node ..................................... 76
8.2.1
Assigning IP Address via Address Selection Switch ......................... 76
Assigning IP Address via DHCP........................................................ 78
8.2.2
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
5
8.2.2.1
Enable DHCP................................................................................. 79
8.2.2.2
Disabling DHCP ............................................................................ 79
Assigning the IP Address with a BootP Server .................................. 81
8.2.3
8.2.3.1
Note MAC ID ................................................................................ 83
Determining IP addresses .............................................................. 84
8.2.3.2
8.2.3.3
Assigning the IP address and Enable BootP.................................. 85
8.2.3.4
Disabling BootP............................................................................. 85
Reasons for Failed IP Address Assignment................................... 88
8.2.3.5
8.3
Testing the Function of the Fieldbus Node ............................................. 89
8.4
Preparing the Flash File System.............................................................. 90
8.5
Restoring Factory Settings ...................................................................... 92
9
Configuring via the Web-Based Management System (WBM)............. 93
9.1
Information.............................................................................................. 94
9.2
Ethernet ................................................................................................... 96
9.3
TCP/IP..................................................................................................... 99
9.4
Port ........................................................................................................ 101
9.5
SNMP.................................................................................................... 103
9.5.1
SNMP V1/V2c.................................................................................. 104
9.5.2
SNMP V3 ......................................................................................... 106
9.6
Watchdog .............................................................................................. 108
9.7
Security ................................................................................................. 110
9.8
Features ................................................................................................. 113
9.9
I/O Config ............................................................................................. 114
10 Diagnostics ................................................................................................ 115
10.1
LED Signaling....................................................................................... 115
10.1.1
Evaluating Fieldbus Status ............................................................... 116
Evaluating Node Status - I/O LED (Blink Code Table)................... 117
10.1.2
10.2
Fault Behavior....................................................................................... 124
10.2.1
Loss of Fieldbus ............................................................................... 124
10.2.2
Internal Data Bus Failure.................................................................. 125
11 Fieldbus Communication ........................................................................ 126
11.1
Implemented Protocols.......................................................................... 126
11.1.1
Communication Protocols ................................................................ 126
11.1.1.1
IP (Internet Protocol) ................................................................... 126
11.1.1.2
TCP (Transmission Control Protocol) ......................................... 131
11.1.1.3
UDP (User Datagram Protocol)................................................... 131
11.1.2
Configuration and Diagnostics Protocols......................................... 132
11.1.2.1
BootP (Bootstrap Protocol).......................................................... 132
DHCP (Dynamic Host Configuration Protocol).......................... 134
11.1.2.2
11.1.2.3
HTTP (Hypertext Transfer Protocol)........................................... 136
11.1.2.4
DNS (Domain Name Systems) .................................................... 136
11.1.2.5
FTP-Server (File Transfer Protocol)............................................ 137
11.1.2.6
SNMP (Simple Network Management Protocol) ........................ 137
11.1.2.6.1
MIB II Description.................................................................. 138
11.1.2.6.2
Traps........................................................................................ 139
11.1.3
Application Protocols ....................................................................... 140
11.2
MODBUS Functions............................................................................. 141
11.2.1
General ............................................................................................. 141
Manual
Version 1.1.0
6
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.2
Use of the MODBUS Functions....................................................... 144
11.2.3
Description of the MODBUS Functions .......................................... 145
Function Code FC1 (Read Coils) ................................................ 146
11.2.3.1
11.2.3.2
Function Code FC2 (Read Input Discretes)................................. 148
Function Code FC3 (Read Multiple Registers) ........................... 150
11.2.3.3
11.2.3.4
Function Code FC4 (Read Input Registers)................................. 151
Function Code FC5 (Write Coil) ................................................. 152
11.2.3.5
Function Code FC6 (Write Single Register) ............................... 153
11.2.3.6
11.2.3.7
Function Code FC11 (Get Comm Event Counter) ...................... 154
11.2.3.8
Function Code FC15 (Force Multiple Coils)............................... 155
11.2.3.9
Function Code FC16 (Write Multiple Registers) ........................ 157
Function Code FC22 (Mask Write Register).............................. 158
11.2.3.10
11.2.3.11
Function Code FC23 (Read/Write Multiple Registers) ............... 159
11.2.4
MODBUS Register Mapping ........................................................... 161
11.2.5
MODBUS Registers ......................................................................... 164
11.2.5.1
Accessing Register Values .......................................................... 165
11.2.5.2
Watchdog Registers ..................................................................... 165
11.2.5.3
Diagnostic Registers .................................................................... 170
11.2.5.4
Configuration Registers ............................................................... 171
11.2.5.5
Firmware Information Registers.................................................. 176
11.2.5.6
Constant Registers ....................................................................... 178
11.3
EtherNet/IP (Ethernet/Industrial Protocol) ........................................... 180
11.3.1
General ............................................................................................. 180
11.3.2
Protocol overview in the OSI model ................................................ 181
11.3.3
Characteristics of the EtherNet/IP Protocol Software ...................... 182
11.3.4
EDS File ........................................................................................... 182
11.3.5
Object Model .................................................................................... 183
11.3.5.1
General......................................................................................... 183
11.3.5.2
Class Overview............................................................................ 184
11.3.5.3
Explanation of the Table Headings in the Object Descriptions... 186
11.3.5.4
Identity (01 hex) ............................................................................ 186
11.3.5.5
Message Router (02 hex) ............................................................... 188
11.3.5.6
Assembly Object (04 hex) ............................................................. 189
11.3.5.7
Connection (05 hex)....................................................................... 192
11.3.5.8
Connection Manager (06 hex)........................................................ 192
11.3.5.9
Port Class (F4 hex) ........................................................................ 192
11.3.5.10
TCP/IP Interface (F5 hex) ............................................................. 194
11.3.5.11
Ethernet Link (F6 hex) .................................................................. 196
11.3.5.12
Coupler/Controller Configuration (64 hex) ................................... 202
11.3.5.13
Discrete Input Point (65 hex)......................................................... 203
11.3.5.14
Discrete Input Point Extended 1 (69 hex) ..................................... 203
11.3.5.15
Discrete Input Point Extended 2 (6D hex)..................................... 204
11.3.5.16
Discrete Input Point Extended 3 (71 hex) ..................................... 205
11.3.5.17
Discrete Output Point (66 hex) ...................................................... 205
11.3.5.18
Discrete Output Point Extended 1 (6A hex) .................................. 206
11.3.5.19
Discrete Output Point Extended 2 (6E hex) .................................. 207
11.3.5.20
Discrete Output Point Extended 3 (72 hex)................................... 207
11.3.5.21
Analog Input Point (67 hex) .......................................................... 208
11.3.5.22
Analog Input Point Extended 1 (6B hex) ...................................... 209
11.3.5.23
Analog Input Point Extended 2 (6F hex)....................................... 209
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.5.24
11.3.5.25
11.3.5.26
11.3.5.27
11.3.5.28
11.3.5.29
11.3.5.30
Table of Contents
7
Analog Input Point Extended 3 (73 hex) ....................................... 210
Analog Output Point (68 hex) ....................................................... 211
Analog Output Point Extended 1 (6C hex).................................... 211
Analog Output Point Extended 2 (70 hex) .................................... 212
Analog Output Point Extended 3 (74 hex) .................................... 213
Module Configuration (80 hex) ..................................................... 214
Module Configuration Extended (81 hex)..................................... 215
12 I/O Modules .............................................................................................. 216
12.1
Overview ............................................................................................... 216
12.2
Process Data Architecture for MODBUS/TCP..................................... 217
12.2.1
Digital Input Modules....................................................................... 218
1 Channel Digital Input Module with Diagnostics ...................... 218
12.2.1.1
12.2.1.2
2 Channel Digital Input Modules ................................................ 218
2 Channel Digital Input Module with Diagnostics ...................... 218
12.2.1.3
12.2.1.4
2 Channel Digital Input Module with Diagnostics and Output
Process Data................................................................................. 219
12.2.1.5
4 Channel Digital Input Modules ................................................ 219
12.2.1.6
8 Channel Digital Input Modules ................................................ 219
16 Channel Digital Input Modules .............................................. 220
12.2.1.7
12.2.2
Digital Output Modules.................................................................... 221
12.2.2.1
1 Channel Digital Output Module with Input Process Data ........ 221
2 Channel Digital Output Modules.............................................. 221
12.2.2.2
12.2.2.3
2 Channel Digital Input Modules with Diagnostics and Input
Process Data................................................................................. 222
12.2.2.4
4 Channel Digital Output Modules.............................................. 223
12.2.2.5
4 Channel Digital Output Modules with Diagnostics and Input
Process Data................................................................................. 223
8 Channel Digital Output Module ............................................... 223
12.2.2.6
12.2.2.7
8 Channel Digital Output Modules with Diagnostics and Input
Process Data................................................................................. 224
12.2.2.8
16 Channel Digital Output Modules............................................ 224
8 Channel Digital Input/Output Modules .................................... 225
12.2.2.9
Analog Input Modules...................................................................... 226
12.2.3
12.2.3.1
1 Channel Analog Input Modules................................................ 226
12.2.3.2
2 Channel Analog Input Modules................................................ 226
12.2.3.3
4 Channel Analog Input Modules................................................ 227
12.2.4
Analog Output Modules ................................................................... 228
12.2.4.1
2 Channel Analog Output Modules ............................................. 228
4 Channel Analog Output Modules ............................................. 228
12.2.4.2
12.2.5
Specialty Modules ............................................................................ 229
12.2.5.1
Counter Modules ......................................................................... 229
12.2.5.2
Pulse Width Modules................................................................... 231
12.2.5.3
Serial Interface Modules with alternative Data Format............... 231
12.2.5.4
Serial Interface Modules with Standard Data Format ................. 232
12.2.5.5
Data Exchange Module................................................................ 232
12.2.5.6
SSI Transmitter Interface Modules.............................................. 232
12.2.5.7
Incremental Encoder Interface Modules...................................... 233
12.2.5.8
DC-Drive Controller.................................................................... 235
12.2.5.9
Stepper Controller........................................................................ 236
12.2.5.10
RTC Module ................................................................................ 237
Manual
Version 1.1.0
8
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.5.11
DALI/DSI Master Module........................................................... 237
12.2.5.12
EnOcean Radio Receiver............................................................. 238
MP Bus Master Module............................................................... 238
12.2.5.13
12.2.5.14
Bluetooth® RF-Transceiver.......................................................... 239
12.2.5.15
Vibration Velocity/Bearing Condition Monitoring VIB I/O ....... 240
12.2.5.16
AS-interface Master Module ....................................................... 240
12.2.6
System Modules ............................................................................... 242
System Modules with Diagnostics............................................... 242
12.2.6.1
12.2.6.2
Binary Space Module .................................................................. 242
12.3
Process Data Architecture for EtherNet/IP ........................................... 243
12.3.1
Digital Input Modules....................................................................... 244
1 Channel Digital Input Module with Diagnostics ...................... 244
12.3.1.1
12.3.1.2
2 Channel Digital Input Modules ................................................ 244
2 Channel Digital Input Module with Diagnostics ...................... 245
12.3.1.3
12.3.1.4
2 Channel Digital Input Module with Diagnostics and Output
Process Data................................................................................. 245
12.3.1.5
4 Channel Digital Input Modules ................................................ 246
12.3.1.6
8 Channel Digital Input Modules ................................................ 246
16 Channel Digital Input Modules .............................................. 246
12.3.1.7
12.3.2
Digital Output Modules.................................................................... 247
12.3.2.1
1 Channel Digital Output Module with Input Process Data ........ 247
2 Channel Digital Output Modules.............................................. 248
12.3.2.2
12.3.2.3
2 Channel Digital Input Modules with Diagnostics and Input
Process Data................................................................................. 248
12.3.2.4
4 Channel Digital Output Modules.............................................. 249
12.3.2.5
4 Channel Digital Output Modules with Diagnostics and Input
Process Data................................................................................. 249
8 Channel Digital Output Module ............................................... 250
12.3.2.6
12.3.2.7
8 Channel Digital Output Modules with Diagnostics and Input
Process Data................................................................................. 250
12.3.2.8
16 Channel Digital Output Modules............................................ 251
8 Channel Digital Input/Output Modules .................................... 251
12.3.2.9
Analog Input Modules...................................................................... 252
12.3.3
12.3.3.1
1 Channel Analog Input Modules................................................ 252
12.3.3.2
2 Channel Analog Input Modules................................................ 253
12.3.3.3
4 Channel Analog Input Modules................................................ 253
Analog Output Modules ................................................................... 254
12.3.4
2 Channel Analog Output Modules ............................................. 254
12.3.4.1
12.3.4.2
4 Channel Analog Output Modules ............................................. 254
12.3.5
Specialty Modules ............................................................................ 255
12.3.5.1
Counter Modules ......................................................................... 255
12.3.5.2
Pulse Width Modules................................................................... 257
12.3.5.3
Serial Interface Modules with alternative Data Format............... 257
12.3.5.4
Serial Interface Modules with Standard Data Format ................. 258
12.3.5.5
Data Exchange Module................................................................ 259
12.3.5.6
SSI Transmitter Interface Modules.............................................. 259
12.3.5.7
Incremental Encoder Interface Modules...................................... 260
12.3.5.8
DC-Drive Controller.................................................................... 262
12.3.5.9
Steppercontroller.......................................................................... 263
12.3.5.10
RTC Module ................................................................................ 264
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
9
12.3.5.11
DALI/DSI Master Module........................................................... 265
12.3.5.12
EnOcean Radio Receiver............................................................. 265
MP Bus Master Module............................................................... 266
12.3.5.13
12.3.5.14
Bluetooth® RF-Transceiver.......................................................... 266
12.3.5.15
Vibration Velocity/Bearing Condition Monitoring VIB I/O ....... 267
12.3.5.16
AS-interface Master Module ....................................................... 268
12.3.6
System Modules ............................................................................... 269
System Modules with Diagnostics............................................... 269
12.3.6.1
12.3.6.2
Binary Space Module .................................................................. 269
13 Application Examples.............................................................................. 270
Test of MODBUS protocol and fieldbus nodes .................................... 270
13.1
13.2
Visualization and Control using SCADA Software.............................. 270
14 Use in Hazardous Environments ............................................................ 273
14.1
Identification ......................................................................................... 274
For Europe according to CENELEC and IEC.................................. 274
14.1.1
14.1.2
For America according to NEC 500................................................. 277
14.2
Installation Regulations......................................................................... 278
14.2.1
Special Conditions for Safe Operation of the ATEX and IEC Ex (acc.
DEMKO 08 ATEX 142851X and IECEx PTB 07.0064)................. 279
14.2.2
Special Conditions for Safe Operation of the Ex i (acc. TÜV 07
ATEX 554086 X) ............................................................................. 280
14.2.3
Special Conditions for the Safe Operation of the IEC Ex i (acc. TUN
09.0001 X)........................................................................................ 281
14.2.4
ANSI/ISA 12.12.01 .......................................................................... 282
List of Figures .................................................................................................... 283
List of Tables...................................................................................................... 285
Manual
Version 1.1.0
10
1
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Notes about this Documentation
Keep this documentation!
The operating instructions are part of the product and shall be kept for the entire
lifetime of the device. They shall be transferred to each subsequent owner or user
of the device. Care must also be taken to ensure that any supplement to these
instructions are included, if applicable.
1.1
Validity of this Documentation
This documentation is only applicable to the device:
"ETHERNET Fieldbus Coupler" 750-352 of the WAGO-I/O-SYSTEM 750
series.
The ETHERNET Fieldbus Coupler 750-352 shall only be installed and operated
according to the instructions in this manual and the system description for the
WAGO-I/O-SYSTEM 750.
Consider power layout of the WAGO-I/O-SYSTEM 750!
In addition to these operating instructions, you will also need the system
description for the WAGO-I/O-SYSTEM 750, which can be downloaded at
www.wago.com. There, you can obtain important information including
information on electrical isolation, system power and supply specifications.
1.2
Copyright
This Manual, including all figures and illustrations, is copyright-protected. Any
further use of this Manual by third parties that violate pertinent copyright
provisions is prohibited. Reproduction, translation, electronic and phototechnical
filing/archiving (e.g., photocopying) as well as any amendments require the
written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden, Germany.
Non-observance will involve the right to assert damage claims.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
1.3
Table of Contents
11
Symbols
Personal Injury!
Indicates a high-risk, imminently hazardous situation which, if not avoided, will
result in death or serious injury.
Personal Injury Caused by Electric Current!
Indicates a high-risk, imminently hazardous situation which, if not avoided, will
result in death or serious injury.
Personal Injury!
Indicates a moderate-risk, potentially hazardous situation which, if not avoided,
could result in death or serious injury.
Personal Injury!
Indicates a low-risk, potentially hazardous situation which, if not avoided, may
result in minor or moderate injury.
Damage to Property!
Indicates a potentially hazardous situation which, if not avoided, may result in
damage to property.
Damage to Property Caused by Electrostatic Discharge (ESD)!
Indicates a potentially hazardous situation which, if not avoided, may result in
damage to property.
Important Note!
Indicates a potential malfunction which, if not avoided, however, will not result in
damage to property.
Manual
Version 1.1.0
12
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Additional Information:
Refers to additional information which is not an integral part of this
documentation (e.g., the Internet).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
1.4
Table of Contents
13
Number Notation
Table 1: Number Notation
Number code
Decimal
Hexadecimal
Binary
1.5
Example
100
0x64
'100'
'0110.0100'
Note
Normal notation
C notation
In quotation marks, nibble separated with
dots (.)
Font Conventions
Table 2: Font Conventions
Font type
italic
Menu
>
Input
“Value”
[Button]
[Key]
Manual
Version 1.1.0
Indicates
Names of paths and data files are marked in italic-type.
e.g.: C:\Programme\WAGO-I/O-CHECK
Menu items are marked in bold letters.
e.g.: Save
A greater-than sign between two names means the selection of a
menu item from a menu.
e.g.: File > New
Designation of input or optional fields are marked in bold letters,
e.g.: Start of measurement range
Input or selective values are marked in inverted commas.
e.g.: Enter the value “4 mA” under Start of measurement range.
Pushbuttons in dialog boxes are marked with bold letters in square
brackets.
e.g.: [Input]
Keys are marked with bold letters in square brackets.
e.g.: [F5]
14
Table of Contents
2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Important Notes
This section includes an overall summary of the most important safety
requirements and notes that are mentioned in each individual section. To protect
your health and prevent damage to devices as well, it is imperative to read and
carefully follow the safety guidelines.
2.1
Legal Bases
2.1.1
Subject to Changes
WAGO Kontakttechnik GmbH & Co. KG reserves the right to provide for any
alterations or modifications that serve to increase the efficiency of technical
progress. WAGO Kontakttechnik GmbH & Co. KG owns all rights arising from
the granting of patents or from the legal protection of utility patents. Third-party
products are always mentioned without any reference to patent rights. Thus, the
existence of such rights cannot be excluded.
2.1.2
Personnel Qualifications
All sequences implemented on Series 750 devices may only be carried out by
electrical specialists with sufficient knowledge in automation. The specialists
must be familiar with the current norms and guidelines for the devices and
automated environments.
All changes to the coupler or controller should always be carried out by qualified
personnel with sufficient skills in PLC programming.
2.1.3
Use of the 750 Series in Compliance with Underlying
Provisions
Couplers, controllers and I/O modules found in the modular WAGO-I/OSYSTEM 750 receive digital and analog signals from sensors and transmit them
to the actuators or higher-level control systems. Using programmable controllers,
the signals can also be (pre-)processed.
The components have been developed for use in an environment that meets the
IP20 protection class criteria. Protection against finger injury and solid impurities
up to 12.5 mm diameter is assured; protection against water damage is not
ensured. Unless otherwise specified, operation of the components in wet and
dusty environments is prohibited.
Appropriate housing (per 94/9/EG) is required when operating the WAGO-I/OSYSTEM 750 in hazardous environments. Please note that a prototype test
certificate must be obtained that confirms the correct installation of the system in
a housing or switch cabinet.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
2.1.4
Table of Contents
15
Technical Condition of Specified Devices
The components to be supplied Ex Works, are equipped with hardware and
software configurations, which meet the individual application requirements.
WAGO Kontakttechnik GmbH & Co. KG will be exempted from any liability in
case of changes in hardware or software as well as to non-compliant usage of
components.
Please send your request for modified and new hardware or software
configurations directly to WAGO Kontakttechnik GmbH & Co. KG.
Manual
Version 1.1.0
16
2.2
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Safety Advice (Precautions)
For installing and operating purposes of the relevant device to your system the
following safety precautions shall be observed:
Do not work on components while energized!
All power sources to the device shall be switched off prior to performing any
installation, repair or maintenance work.
Installation only in appropriate housings, cabinets or in electrical operation
rooms!
The WAGO-I/O-SYSTEM 750 and its components are an open system. As such,
install the system and its components exclusively in appropriate housings,
cabinets or in electrical operation rooms. Allow access to such equipment and
fixtures to authorized, qualified staff only by means of specific keys or tools.
Replace defective or damaged devices!
Replace defective or damaged device/module (e.g., in the event of deformed
contacts), since the long-term functionality of fieldbus station involved can no
longer be ensured.
Protect the components against materials having seeping and insulating
properties!
The components are not resistant to materials having seeping and insulating
properties such as: aerosols, silicones and triglycerides (found in some hand
creams). If you cannot exclude that such materials will appear in the component
environment, then install the components in an enclosure being resistant to the
above-mentioned materials. Clean tools and materials are imperative for handling
devices/modules.
Cleaning only with permitted materials!
Clean soiled contacts using oil-free compressed air or with ethyl alcohol and
leather cloths.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
17
Do not use any contact spray!
Do not use any contact spray. The spray may impair contact area functionality in
connection with contamination.
Do not reverse the polarity of connection lines!
Avoid reverse polarity of data and power supply lines, as this may damage the
devices involved.
Avoid electrostatic discharge!
The devices are equipped with electronic components that you may destroy by
electrostatic discharge when you touch. Pay attention while handling the devices
to good grounding of the environment (persons, job and packing).
Manual
Version 1.1.0
18
3
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
System Description
The WAGO-I/O-SYSTEM 750 is a modular, fieldbus independent I/O system. It
is comprised of a fieldbus coupler/controller (1) and connected fieldbus modules
(2) for any type of signal. Together, these make up the fieldbus node. The end
module (3) completes the node.
Figure 1: Fieldbus node
Couplers/controllers are available for different fieldbus systems.
The ECO coupler contains the fieldbus interface, electronics and a power supply
for the system. The fieldbus interface forms the physical interface to the relevant
fieldbus. The electronics process the data of the bus modules and make it
available for the fieldbus communication.
Bus modules for diverse digital and analog I/O functions as well as special
functions can be connected to the coupler/controller. The communication between
the coupler/controller and the bus modules is carried out via an internal bus.
The WAGO-I/O-SYSTEM 750 has a clear port level with LEDs for status
indication, insertable mini WSB markers and pullout group marker carriers.
The 3 wire technology supplemented by a ground wire connection allows for
direct sensor/actuator wiring.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.1
Table of Contents
19
Manufacturing Number
The manufacturing number indicates the delivery status directly after production.
This number is part of the lateral marking on the component. In addition the
manufacturing number is also printed on the cover of the configuration and
programming interface of the fieldbus coupler or controller.
01
PROFIBUS DP 12 MBd /DPV1
Hansastr. 27
D-32423 Minden
72072
GL
NO
DS
SW
HW
FWL
0 1 0 3 0 0 0 2 0 3 - B 0 60 0 60 0 60
24V DC
AWG 28-14
55°C max ambient
LISTED 22ZA AND 22XM
ITEM-NO.:750-333
Power Supply
Field
II 3 GD
DEMKO 02 ATEX132273 X
EEx nA II T4
Manufacturing number
03
00
02
03
+
24 V
0V
Power Supply
Electronic
PATENTS PENDING
-B000000
Calendar Year Software Hardware Firmware Internal
week
version version
loader
number
version
Figure 2: Example of a manufacturing number
The manufacturing number consists of the production week and year, the software
version (if available), the hardware version of the component, the firmware loader
(if available) and further internal information for WAGO Kontakttechnik GmbH
& Co. KG.
3.2
Hardware Address (MAC ID)
Each ETHERNET Fieldbus Coupler has a unique and internationally
unambiguous physical address, referred to as the MAC-ID (Media Access Control
Identity). This is located on the rear of the controller and on a self-adhesive tearoff label on the side of the controller. The MAC ID has a set length of 6 bytes (48
bits) (hexadecimal). The first three bytes identify the manufacturer (e.g. 00:30 DE
for WAGO). The second 3 bytes indicate the consecutive serial number for the
hardware.
Manual
Version 1.1.0
20
3.3
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Component Update
For the case of an Update of one component, the lateral marking on each
component contains a prepared matrix.
This matrix makes columns available for altogether three updates to the entry of
the current update data, like production order number (NO; starting from calendar
week 13/2004), update date (DS), software version (SW), hardware version (HW)
and the firmware loader version (FWL, if available).
Current Version data for
Production Order
Number
Datestamp
1. Update
NO
DS
SW
Hardware index
HW
Firmware loader index FWL
2. Update
3. Update
 only starting from
calendar week 13/2004
Software index
 only for coupler/controller
If the update of a component took place, the current version data are registered
into the columns of the matrix.
Additionally with the update of a fieldbus coupler or controller also the cover of
the configuration and programming interface of the coupler or controller is printed
on with the current manufacturing and production order number.
The original manufacturing data on the housing of the component remain thereby.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.4
Table of Contents
21
Storage, Assembly and Transport
Wherever possible, the components are to be stored in their original packaging.
Likewise, the original packaging provides optimal protection during transport.
When assembling or repacking the components, the contacts must not be soiled or
damaged. The components must be stored and transported in appropriate
containers/packaging. Thereby, the ESD information is to be regarded.
Manual
Version 1.1.0
22
3.5
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Assembly Guidelines/Standards
DIN 60204
Electrical equipping of machines
DIN EN 50178 Equipping of high-voltage systems with electronic components
(replacement for VDE 0160)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.6
Power Supply
3.6.1
Isolation
Table of Contents
23
Within the fieldbus node, there are three electrically isolated potentials:
•
electrically isolated fieldbus interface via transformer
•
Electronics of the couplers/controllers and the bus modules (internal bus)
•
All bus modules have an electrical isolation between the electronics
(internal bus, logic) and the field electronics. Some digital and analog input
modules have each channel electrically isolated, please see catalog.
Potential of the system supply
Electrical isolation
to the field level
T 6,3 A
250 V
per module
per channel
Elektronic
Fieldbus
Interface
DC
DC
Potential
Fieldbus interface
Potentials
in the field level
Figure 3: Isolation
Note
Ensure protective conductor function is present (via ring feeding if
required)!
Pay attention, that the ground wire connection must be present in each group. In
order that all protective conductor functions are maintained under all
circumstances, it is recommended that a ground wire be connected at the
beginning and the end of a potential group (ring format, please see chapter
“Grounding” > “Grounding Protection”, Ring Feeding). Thus, if a bus module
comes loose from a composite during servicing, then the protective conductor
connection is still guaranteed for all connected field devices.
When you use a joint power supply unit for the 24 V system supply and the 24 V
field supply, the electrical isolation between the internal bus and the field level is
eliminated for the potential group.
Manual
Version 1.1.0
24
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.6.2
System Supply
3.6.2.1
Connection
The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply
(-15 % or +20 %). The power supply is provided via the coupler/controller and, if
necessary, in addition via the internal system supply modules (750-613). The
voltage supply is reverse voltage protected.
NOTICE
Do not use an incorrect voltage/frequency!
The use of an incorrect supply voltage or frequency can cause severe damage to
the component.
A
C
B
D
24V 0V
System
24 V (-15 % / +20 %)
0V
+ +
- -
750-613
Figure 4: System supply
The fed DC 24 V supplies all internal system components, e.g. coupler/controller
electronics, fieldbus interface and bus modules via the internal bus (5 V system
voltage). The 5 V system voltage is electrically connected to the 24 V system
supply.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
25
750-613
DC 5 V
0V
DC
DC
Electronic
Fieldbus
Interface
DC
DC
DC 24 V
(-15% / + 20%)
Figure 5: System voltage
Note
Only reset the system simultaneously for all supply modules!
Resetting the system by switching on and off the system supply, must take place
simultaneously for all supply modules (coupler/controller and 750 613).
3.6.2.2
Alignment
Note
Recommendation
A stable network supply cannot be taken for granted always and everywhere.
Therefore, regulated power supply units should be used in order to guarantee the
quality of the supply voltage.
The supply capacity of the coupler/controller or the internal system supply
module (750-613) can be taken from the technical data of the components.
Table 3: Alignment
Current consumption via system voltage:
5 V for electronics of bus modules and coupler/controller
Available current for the bus modules. Provided by the bus
power supply unit. See coupler/controller and internal
system supply module (750-613)
*) See current catalog, manuals, Internet
Internal current
consumption*)
Residual current
for bus terminals*)
Manual
Version 1.1.0
26
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Example:
Calculating the current consumption on a 750-343 PROFIBUS DP ECO
Coupler:
Internal current consumption
Residual current for bus modules
Sum I(5 V) total
350 mA at 5 V
650 mA at 5 V
1000 mA at 5V
The internal current consumption is indicated in the technical data for each bus
terminal. In order to determine the overall requirement, add together the values of
all bus modules in the node.
Note
Observe total current of I/O modules, re-feed the potential if required!
If the sum of the internal current consumption exceeds the residual current for bus
modules, then an internal system supply module (750-613) must be placed before
the module where the permissible residual current was exceeded.
Example:
Calculating the total current on an ECO Coupler:
A node with a PROFIBUS DP ECO coupler 750-343 consists of:
10 relay modules (750-517) and 20 digital input modules (750-405).
Internal current consumption
Sum
10 * 90 mA = 900 mA
20 * 2 mA = 40 mA
940 mA
The PROFIBUS DP ECO coupler 750-343 can provide 650 mA for the bus
modules. Consequently, an internal system supply module (750-613), e. g. in the
middle of the node, should be added.
Note
Recommendation
You can configure with the WAGO ProServe® Software smartDESIGNER, the
assembly of a fieldbus node. You can test the configuration via the integrated
accuracy check.
The maximum input current of the 24 V system supply is 500 mA. The exact
electrical consumption (I(24 V)) can be determined with the following formulas:
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
27
Coupler or controller
I(5 V) total = Sum of all the internal current consumption of the connected
bus modules + internal current consumption
coupler/controller
Internal system supply module 750-613
I(5 V) total = Sum of all the internal current consumption of the connected
bus modules at internal system supply module
Input current I(24 V) =
5V
I
* (5 V) total
24 V
η
η = Efficiency of the power supply at nominal load 24 V
Note
Activate all outputs when testing the current consumption!
If the electrical consumption of the power supply point for the 24 V system
supply exceeds 500 mA, then the cause may be an improperly aligned node
or a defect.
During the test, you must activate all outputs, in particular those of the relay
modules.
Manual
Version 1.1.0
28
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.6.3
Field Supply
3.6.3.1
Connection
Sensors and actuators can be directly connected to the relevant channel of the bus
module in 1/4 conductor connection technology. The bus module supplies power
to the sensors and actuators. The input and output drivers of some bus modules
require the field side supply voltage.
For the field side power, a power supply module is necessary.
Likewise, with the aid of the power supply modules, various potentials can be set
up. The connections are linked in pairs with a power contact.
A
A
C
B
B
D
+ +
Further Supply
modules
- DC 24 V
- AC/DC 0-230 V
- AC 120 V
- AC 230 V
- Fuse
- Diagnosis
Field supply
A
C
B
D
+ +
24 V
(-15 % / + 20 %)
- -
- 0V
Protective
conductor
750-602
750-602
Power jumper
contacts
Potential distribution to
adjacent I/O modules
Figure 6: Field supply (sensor/actuator)
Note
In exceptional instances, I/O modules can be directly connected to the field
supply!
The 24 V field supply can be connected also directly to a bus module, if the
connection points are not needed for the peripheral device supply. In this case, the
connection points need the connection to the power jumper contacts.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
29
Note
Re-establish the ground connection when the connection to the power jumper
contacts is disrupted!
Some bus modules have no or very few power contacts (depending on the I/O
function). Due to this, the passing through of the relevant potential is disrupted. If
you require a field supply for subsequent bus modules, then you must use a power
supply module.
Note the data sheets of the bus modules.
Note
Use a spacer module when setting up a node with different potentials!
In the case of a node setup with different potentials, e.g. the alteration from
DC 24 V to AC 230 V, you should use a spacer module. The optical separation of
the potentials acts as a warning to heed caution in the case of wiring and
maintenance works. Thus, you can prevent the results of wiring errors.
3.6.3.2
Fusing
Internal fusing of the field supply is possible for various field voltages via an
appropriate power supply module.
Table 4: Power supply modules
Item No.
750-601
750-609
750-615
750-610
750-611
Manual
Version 1.1.0
Field Voltage
24 V DC, Supply/Fuse
230 V AC, Supply/Fuse
120 V AC, Supply/Fuse
24 V DC, Supply/Fuse/Diagnosis
230 V AC, Supply/Fuse/Diagnosis
30
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Figure 7: Supply module with fuse carrier (Example 750-610)
NOTICE
Observe the maximum power dissipation and, if required, UL requirements!
In the case of power supply modules with fuse holders, you must only use fuses
with a maximum dissipation of 1.6 W (IEC 127).
For UL approved systems only use UL approved fuses.
In order to insert or change a fuse, or to switch off the voltage in succeeding bus
modules, the fuse holder may be pulled out. In order to do this, use a screwdriver
for example, to reach into one of the slits (one on both sides) and pull out the
holder.
Figure 8: Removing the fuse carrier
Lifting the cover to the side opens the fuse carrier.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Figure 9: Opening the fuse carrier
Figure 10: Change fuse
After changing the fuse, the fuse carrier is pushed back into its original position.
Manual
Version 1.1.0
31
32
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Alternatively, fusing can be done externally. The fuse modules of the WAGO
series 281 and 282 are suitable for this purpose.
Figure 11: Fuse modules for automotive fuses, series 282
Figure 12: Fuse modules for automotive fuses, series 2006
Figure 13: Fuse modules with pivotable fuse carrier, series 281
Figure 14: Fuse modules with pivotable fuse carrier, series 2002
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.6.4
Table of Contents
33
Supply Example
SupplSggggggggggggggggg
Note
The system supply and the field supply shall be separated!
You should separate the system supply and the field supply in order to ensure bus
operation in the event of a short-circuit on the actuator side.
L1
L2
L3
N
PE
b)
a)
750-612
750-410
750-401
750-613
2)
1)
750-616
1) d)
c)
750-612
750-512
750-512
750-513
750-616
750-610
750-552
750-630
750-600
2)
Shield (screen) bus
10 A
Main ground bus
System
Supply
230V
1) Separation module
recommended
2) Ring-feeding
recommended
24V
Field
Supply
230V
24V
Field
Supply
10 A
Figure 15: Supply example
Manual
Version 1.1.0
a) Power Supply
on coupler via
external
Supply Module
b) Internal System
Supply Module
c) Supply Module
passive
d) Supply Module
with fuse carrier/
diagnostics
34
Table of Contents
3.6.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Power Supply Unit
The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply with
a maximum deviation of -15 % or +20 %.
Note
Recommendation
A stable network supply cannot be taken for granted always and everywhere.
Therefore, you should use regulated power supply units in order to guarantee the
quality of the supply voltage.
A buffer (200 µF per 1 A current load) should be provided for brief voltage dips.
Note
Power failure time is not acc. to IEC61131-2!
Note that the power failure time in a node with maximal components is not 10 ms,
according to the defaults of the IEC61131-2 standard.
The electrical requirement for the field supply is to be determined individually for
each power supply point. Thereby all loads through the field devices and bus
modules should be considered. The field supply as well influences the bus
modules, as the inputs and outputs of some bus modules require the voltage of the
field supply.
Note
System and field supply shall be isolated from the power supply!
You should isolate the system supply and the field supply from the power
supplies in order to ensure bus operation in the event of short circuits on the
actuator side.
Table 5: WAGO Power Supply Unit
WAGO Power Description
Supply Unit
787-612
Primary switched mode;
DC 24 V; 2,5 A Input nominal voltage AC 230 V
787-622
Primary switched mode;
DC 24 V; 5 A Input nominal voltage AC 230 V
787-632
Primary switched mode;
DC 24 V; 10 A Input nominal voltage AC 230/115 V
Rail-mounted modules with universal mounting carrier
288-809
AC 115 V/DC 24 V; 0,5 A
288-810
AC 230 V/DC 24 V; 0,5 A
288-812
AC 230 V/DC 24 V; 2 A
288-813
AC 115 V/DC 24 V; 2 A
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.7
Grounding
3.7.1
Grounding the DIN Rail
3.7.1.1
Framework Assembly
Table of Contents
35
When setting up the framework, the carrier rail must be screwed together with the
electrically conducting cabinet or housing frame. The framework or the housing
must be grounded. The electronic connection is established via the screw. Thus,
the carrier rail is grounded.
DANGER
Ensure sufficient grounding is provided!
You must take care to ensure the flawless electrical connection between the
carrier rail and the frame or housing in order to guarantee sufficient grounding.
3.7.1.2
Insulated Assembly
Insulated assembly has been achieved when there is constructively no direct
conduction connection between the cabinet frame or machine parts and the carrier
rail. Here the earth ground must be set up via an electrical conductor accordingly
valid national safety regulations.
Note
Recommendation
The optimal setup is a metallic assembly plate with grounding connection with an
electrical conductive link with the carrier rail.
The separate grounding of the carrier rail can be easily set up with the aid of the
WAGO ground wire terminals.
Table 6: WAGO ground wire terminals
Item No.
283-609
Manual
Version 1.1.0
Description
1-conductor ground (earth) terminal block make an automatic contact
to the carrier rail; conductor cross section: 0.2 -16 mm2
Note: Also order the end and intermediate plate (283-320).
36
Table of Contents
3.7.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Grounding Function
The grounding function increases the resistance against disturbances from electromagnetic interferences. Some components in the I/O system have a carrier rail
contact that dissipates electro-magnetic disturbances to the carrier rail.
Figure 16: Carrier rail contact
DANGER
Ensure sufficient grounding is provided!
You must take care to ensure the direct electrical connection between the carrier
rail contact and the carrier rail.
The carrier rail must be grounded.
For information on carrier rail properties, please see chapter “Carrier Rail
Properties”, page 56.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.7.3
Table of Contents
37
Grounding Protection
For the field side, the ground wire is connected to the lowest connection terminals
of the power supply module. The ground connection is then connected to the next
module via the Power Jumper Contact (PJC). If the bus module has the lower
power jumper contact, then the ground wire connection of the field devices can be
directly connected to the lower connection terminals of the bus module.
Note
Re-establish the ground connection when the connection to the power jumper
contacts is disrupted!
Should the ground conductor connection of the power jumper contacts within the
node become disrupted, e. g. due to a 4-channel bus terminal, the ground
connection will need to be re-established.
The ring feeding of the grounding potential will increase the system safety. When
one bus module is removed from the group, the grounding connection will remain
intact.
The ring feeding method has the grounding conductor connected to the beginning
and end of each potential group.
Figure 17: Ring-feeding
Note
Observe grounding protection regulations!
You must observe the regulations relating to the place of assembly as well as the
national regulations for maintenance and inspection of the grounding protection.
Manual
Version 1.1.0
38
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.8
Shielding (Screening)
3.8.1
General
The shielding of the data and signal conductors reduces electromagnetic
interferences thereby increasing the signal quality. Measurement errors, data
transmission errors and even disturbances caused by overvoltage can be avoided.
Note
Lay the shielding throughout the entrance and over a wide area!
Constant shielding is absolutely required in order to ensure the technical
specifications in terms of the measurement accuracy.
The cable shield should be potential. With this, incoming disturbances can be
easily diverted.
You should place shielding over the entrance of the cabinet or housing in order to
already repel disturbances at the entrance.
Note
Lay high-voltage cables separately!
Separate the data and signal conductors from all high-voltage cables.
3.8.2
Bus Conductors
The shielding of the bus conductor is described in the relevant assembly
guidelines and standards of the bus system.
3.8.3
Signal Conductors
Bus modules for most analog signals along with many of the interface bus
modules include a connection for the shield.
Note
Improve shield performance by placing the shield over a large area!
For a better shield performance, you should place the shield previously over a
large area. The WAGO shield connection system is suggested for such an
application. This suggestion is especially applicable if the equipment can have
even current or high impulse formed currents running through (for example
initiated by atmospheric discharge).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
3.8.4
Table of Contents
WAGO Shield (Screen) Connecting System
The WAGO Shield Connecting system includes a shield clamping saddle, a
collection of rails and a variety of mounting feet. Together these allow many
different possibilities. See catalog W4 volume 3 chapter 10.
Figure 18: Example WAGO Shield (Screen) Connecting System
Figure 19: Application of the WAGO Shield (Screen) Connecting System
Manual
Version 1.1.0
39
40
4
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Device Description
The 750-352 Fieldbus Coupler connects the WAGO-I/O-SYSTEM 750 or 753 to
the ETHERNET fieldbus system.
This coupler can be used for applications in machine and plant construction as
well as in the process industry and building technology.
Equipped with two RJ-45 ports, which both work as 2-channel switches, the
Fieldbus coupler enables easy and cost-effective cabling such as linear bus
topology for which no additional external switches or hubs are required.
With the DIP switch the last byte of the IP address, as well as the assignment of
the IP address (DHCP, BootP, firm setting) can be given.
In the Fieldbus Coupler, all input signals from the sensors are combined. After
connecting the Fieldbus Coupler, the Fieldbus Coupler determines which I/O
modules are on the node and creates a local process image from these. Analog and
specialty module data is sent via words and/or bytes; digital data is grouped bitby-bit.
The local process image is divided into two data zones containing the data
received and the data to be sent.
The data of the analog modules is mapped first into the process image. The
modules are mapped in the order of their physical position after the Coupler.
The bits of the digital modules are combined into words and then mapped after the
analog ones in the process image. If the number of digital I/Os is greater than 16
bits, the Fieldbus Coupler automatically begins a new word.
All sensor input signals are grouped in the coupler (slave) and transferred to the
higher-order controller (master) via the fieldbus. Process data linking is performed
in the higher-order controller. The higher-order controller puts out the resulting
data to the actuators via the bus and the node.
The fieldbus connection consists of two ports (RJ-45). An ETHERNET switch
integrated in the fieldbus coupler operates in the store and forward mode.
Both ports support:
•
10BASE-T / 100BASE-TX
•
Full / Half duplex
•
Autonegotiation
•
Auto-MDI(X)
In order to send process data via ETHERNET, the Coupler supports a series of
network protocols.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
41
The MODBUS/TCP(UDP) protocol and the ETHERNET/IP protocol are
implemented for exchanging process data.
The two communication protocols can be used optional or together.
For the management and diagnosis of the system, the HTTP, SNTP and SNMP
protocols are available.
For the data transfer via ETHERNET the FTP is available.
For the automatic assignment of the IP address in the network, kann alternatively
DHCP or BootP can be used.
An internal server is available for Web-based applications.
HTML pages stored in the Fieldbus Coupler allow access to information about the
configuration, the status and the I/O data of the fieldbus node via Web browsers.
It is also possible to store individual HTML pages using the implemented file
system, store custom HTML pages.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
View
The view below shows the different parts of the device:
•
•
•
•
The fieldbus connection is within the lower range on the left side.
Over the fieldbus connection is a power supply unit for the system supply.
LEDs for bus communication, error messages and diagnostics are within the
upper range on the right side.
Down right the service interface is to be found.
1
2
8
13
ON
12
11
10
9
24V
X3
0V
ETHERNET
LINK 1
ACT
LINK 2
ACT
3
MS
NS
0: WBM
255: DHCP
I/O
750-352
1
1 2 3 4 5 6 7 8
4.1
Table of Contents
ON
42
4
X
1
5
6
9
X
2
7
8
Figure 20: View ETHERNET TCP/IP Fieldbus Coupler
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 7: Legend to the View ETHERNET TCP/IP Fieldbus Coupler
DesignaNo.
Meaning
tion
LINK
ACT 1, 2,
1
Status LEDs Fieldbus
MS, NS,
I/O
Manual
Version 1.1.0
2
---
Marking possibility on four miniature WSB
markers
3
---
Data Contacts
4
---
Unlocking Lug
5
---
Service Interface (open flap)
6
X1, X2
10
-
11
+
9
10
Table of Contents
43
Details see Chapter:
„Device Description“ >
„Display Elements“
--"Connect Devices" > "Data
Contacts/Internal Bus"
"Assembly" >
"Inserting and Removing
Devices"
"Device Description" >
"Operating Elements"
Fieldbus connection 2 x RJ-45 as 2-Port
ETHERNET Switch
„Device Description“ >
„Connectors“
CAGE CLAMP® Connections Field Supply
DC 0 V
CAGE CLAMP® Connections Field Supply
DC 24 V
"System Description"
>"Voltage Supply"
"System Description"
>"Voltage Supply"
---
Locking Disc
„Assembly“ > „Plugging
and Removal of the Device“
---
Address Selection Switch
"Device Description" >
"Operating Elements"
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.2
Connectors
4.2.1
Device Supply
The device is powered via terminal blocks with CAGE CLAMP® connections.
The device supply generates the necessary voltage to power the electronics of the
device and the internal electronics of the connected I/O modules.
The fieldbus interface is galvanically separated from the electrical potential of the
device via the transducer.
24 V
0V
24 V
10 nF
DC
I/O
Modules
DC
ELECTRONIC
FIELDBUS INTERFACE
0V
ELECTRONIC
FIELDBUS
INTERFACE
44
10 nF
750-352
Figure 21: Device Supply
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.2.2
Table of Contents
45
Fieldbus Connection
The connection to the fieldbus is made via two RJ-45 plugs, which are connected
to the fieldbus controller via an integrated switch.
The integrated switch works in store-and-forward operation and for each port,
supports the transmission speeds 10/100 Mbit as well as the transmission
modes full and half-duplex and autonegotiation.
The wiring of these plugs corresponds to the specifications
for 100BaseTX, which prescribes a category 5 twisted pair cable as the
connecting cable. Cable types S-UTP (Screened Unshielded Twisted Pair) and
STP (Shielded Twisted Pair) with a maximum segment length of 100 m
(approximately 328.08 feet) can be used.
The RJ-45 socket is physically lower, allowing the coupler to fit in an 80 mm high
enclosure once connected.
Table 8: RJ-45 Connector and RJ-45 Connector Configuration
View
8
7
6
5
4
3
2
1
Figure 22:
RJ-45-Connector
Contact
Signal
1
2
3
4
5
6
7
8
TD +
TD RD +
RD -
Transmit +
Transmit Receive +
free
free
Receive free
free
Not for use in telecommunication circuits!
Only use devices equipped with ETHERNET or RJ-45 connectors in LANs.
Never connect these devices with telecommunication networks.
Manual
Version 1.1.0
46
4.3
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Display Elements
The operating condition of the coupler or the node is displayed with the help of
illuminated indicators in the form of light-emitting diodes (LEDs).
The LED information is routed to the top of the case by light fibres. In some
cases, these are multi-colored (red/green or red/green/orange).
ETHERNET
LINK 1
ACT
LINK 2
ACT
MS
NS
I/O
Figure 23: Display Elements
+
For the diagnostics of the different ranges fieldbus and node, the LED’s can be
divided into groups:
Table 9: Display Elements Fieldbus Status
LED
Color
Meaning
LINK
ACT 1
LINK
ACT 2
green
indicates a connection to the physical network at port 1
green
indicates a connection to the physical network at port 2
MS
red/green
indicates the status of the node
NS
red/green
indicates the network status
+
Table 10: Display Elements Node Status
LED
Color
Meaning
I/O
red/green/
indicates the operation of the node and signals via a blink code faults
orange
encountered
More information about the LED Signaling
Read the detailed description for the evaluation of the displayed LED-Signals in
the chapter "Diagnostics" > "LED Signaling".
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.4
Operating Elements
4.4.1
Service Interface
Table of Contents
47
The Service Interface is to find behind the flap.
The configuration interface is used for the communication with the WAGO-I/OCHECK and for downloading firmware.
1
2
Figure 24: Service Interface for the configuration (closed and opened flap)
Table 11: Service Interface
Number
1
2
Description
Flap opened
Configuration Interface
Device must be de-energized!
To prevent damage to the device, unplug and plug in the communication cable
only when the device is de-energized!
The 750-920 Communication Cable is connected to the 4-pole header.
Manual
Version 1.1.0
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Address Selection Switch
1 2 3 4 5 6 7 8
4.4.2
ON
48
Figure 25: Address Selection Switch
The configuration of the IP address via the address selection switch takes place
when you set the host ID (last digit of the IP address).
The coding of the host ID is bit by bit and begins with address selection switch 1
for bit 0 (LSB) and ends with address selection switch 8 for bit 7 (MSB).
The base address used depends on the IP address currently saved in the coupler.
With the original factory settings, the IP address is configured to the value 0.0.0.0.
by default. In this case, the static base address 192.168.1.X is used.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.5
Technical Data
4.5.1
Device Data
Table of Contents
49
Table 12: Technical Data - Device
Width
50 mm
High (from upper edge of DIN 35 rail) 65* mm (*from upper edge of DIN 35
rail)
Length
97 mm
Weight
110 g
4.5.2
System Data
Table 13: Technical Data - System
Number of fieldbus nodes per master
Transmission medium
Fieldbus coupler connection
Transmission performance
Baud rate
max. length of fieldbus segment
Protocols
Max. number of socket links
Number of I/O modules
- with bus extension
Configuration
4.5.3
Limited by ETHERNET specification
Twisted Pair CAT 5e (S/UTP or S/STP)
2 x RJ-45
Class D acc. to EN 50173
10/100 Mbit/s
100 m
MODBUS/TCP (UDP), EtherNet/IP,
HTTP, BootP, DHCP, DNS, FTP, SNMP
3 HTTP, 15 MODBUS/TCP, 10 FTP,
2 SNMP, 128 for Ethernet/IP
64
250
via PC
Safe electrical Isolation
Table 2: Technical Data – Safe electrical Isolation
Air and creepage distance
Degree of pollution
acc. to IEC 61131-2
4.5.4
Acc. to IEC 60664-1
2
Degree of protection
Table 3: Technical Data - Degree of protection
Degree of protection
Manual
Version 1.1.0
IP 20
50
Table of Contents
4.5.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Supply
Table 4: Technical Data - Supply
Voltage Supply
Input currentmax. (24 V)
Efficiency of the power supply
Internal current consumption (5 V)
Total current for I/O modules (5 V)
Isolation
4.5.6
DC 24 V (-25% ... +30%)
280 mA
90 %
450 mA
700 mA
500 V system/supply
Fieldbus MODBUS/TCP
Table 5: Technical Data - Fieldbus MODBUS/TCP
Eingangsprozessabbild max
Ausgangsprozessabbild max
4.5.7
1020 words
1020 words
Accessories
Table 14: Technical data – Accessories
Miniature WSB Quick marking system
4.5.8
Wire Connection
Table 15: Technical Data Wire Connection
Wire connection
Cross section
Stripped lengths
Voltage drop at Imax.
Data contacts
CAGE CLAMP®
0.08 mm² ... 1.5 mm² / AWG 28-16
5 ... 6 mm / 0.22 in
< 1 V/64 modules
slide contact, hard gold plated
1.5 µm, self-cleaning
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.5.9
Table of Contents
51
Climatic Environmental Conditions
Table 16: Technical Data - Climatic environmental conditions
Operating temperature range
Storage temperature range
Relative humidity
Resistance to harmful substances
Maximum pollutant concentration at
relative humidity < 75%
Special conditions
4.5.10
0 °C ... 55 °C
-25 °C ... +85 °C
95 % without condensation
Acc. to IEC 60068-2-42 and
IEC 60068-2-43
SO2  25 ppm
H2S  10 ppm
Ensure that additional measures for
components are
taken, which are used in an environment
involving:
– dust, caustic vapors or gases
– ionization radiation
Mechanical strength
Table 17: Technical data – Mechanical strength
Vibration resistance
Shock resistance
Free fall
Manual
Version 1.1.0
acc. to IEC 60068-2-6
Comment to the vibration resistance:
a) Type of oscillation:
sweep with a rate of change of 1 octave per minute
10 Hz  f < 57 Hz, const. Amplitude 0,075 mm
57 Hz  f < 150 Hz, const. Acceleration 1 g
b) Period of oscillation:
10 sweep per axis in each of the 3 vertical axes
acc. to IEC 60068-2-27
Comment to the shock resistance:
a) Type of impulse: half sinusoidal
b) Intensity of impulse:
15 g peak value, 11 ms maintenance time
c) Route of impulse:
3 impulses in each pos. And neg. direction of the 3
vertical axes of the test object, this means 18 impulses
in all
acc. IEC 60068-2-32
≤ 1m (module in original packing)
52
4.6
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Approvals
More Information about Approvals
Detailed references to the approvals are listed in the document "Overview
Approvals WAGO-I/O-SYSTEM 750", which you can find on the DVD
“AUTOMATION Tools and Docs” (Item-No.: 0888-0412) or via the internet
under: www.wago.com  Service  Documentation  WAGO-I/O-SYSTEM
750  System Description.
The following approvals have been granted to 750-352 fieldbus
coupler/controller:
CULUS
(UL508)
The following approvals are pending for 750-352 fieldbus coupler/controller:
Conformity Marking
The following ship approvals are pending for 750-352 fieldbus coupler/controller:
GL (Germanischer Lloyd)
Cat. A, B, C, D (EMC 1)
For more information about the ship approvals:
Note the "Supplementary Power Supply Regulations" chapter for the ship
approvals.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4.7
Table of Contents
53
Standards and Guidelines
750-352 meets the following requirements on emission and immunity of
interference:
EMC CE-Immunity to interference
acc. to EN 61000-6-2: 2005
EMC CE-Emission of interference
acc. to EN 61000-6-3: 2007
750-352 meets the following requirements on emission and immunity of
interference:
EMC marine applications-Immunity
to interference
acc. to Germanischer Lloyd (2003)
EMC marine applications-Emission
of interference
acc. to Germanischer Lloyd (2003)
Manual
Version 1.1.0
54
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
5
Assembly
5.1
Installation Position
Along with horizontal and vertical installation, all other installation positions are
allowed.
Note
Use an end stop in the case of vertical assembly!
In the case of vertical assembly, an end stop has to be mounted as an additional
safeguard against slipping.
WAGO item 249-116
End stop for DIN 35 rail, 6 mm wide
WAGO item 249-117
End stop for DIN 35 rail, 10 mm wide
5.2
Total Extension
The length of the module assembly (including one end module of 12mm width)
that can be connected to the 750-352 is 780 mm. When assembled, the I/O
modules have a maximum length of 768 mm.
Examples:
•
64 I/O modules of 12 mm width can be connected to one coupler/controller.
•
32 I/O modules of 24 mm width can be connected to one coupler/controller.
Exception:
The number of connected I/O modules also depends on which type of
coupler/controller is used. For example, the maximum number of I/O modules
that can be connected to a PROFIBUS coupler/controller is 63 without end
module.
NOTICE
Observe maximum total length of a node!
The maximum total length of a node without a 750-352 must not exceed 780 mm.
Furthermore, you must observe restrictions made on certain types of
couplers/controllers (e.g. for PROFIBUS).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
55
Note
Increase total length using a WAGO internal data bus extension module!
Using an internal data bus extension module from WAGO, you can increase the
total length of the fieldbus node. In this type of configuration, you must connect a
750-627 Bus Extension End Module to the last module of the node.
You then connect the 750-627 module to the 750-628 Coupler Module of the next
I/O module assembly via RJ-45 cable.
You can connect up to 10 internal data bus extension coupler modules 750-628 to
an internal data bus extension end module 750-627. In this manner, you can
logically connect up to 10 module assemblies to a 750-352, dividing a fieldbus
node into 11 assemblies maximum.
The maximum cable length between two assemblies is 5 meters. For additional
information, refer to the "750-627/-628 Modules" manual. The total cable length
for a fieldbus node is 70 meters.
Manual
Version 1.1.0
56
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
5.3
Assembly onto Carrier Rail
5.3.1
Carrier Rail Properties
All system components can be snapped directly onto a carrier rail in accordance
with the European standard EN 50022 (DIN 35).
NOTICE
Do not use any third-party carrier rails without approval by WAGO!
WAGO Kontakttechnik GmbH & Co. KG supplies standardized carrier rails that
are optimal for use with the I/O system. If other carrier rails are used, then a
technical inspection and approval of the rail by WAGO Kontakttechnik GmbH &
Co. KG should take place.
Carrier rails have different mechanical and electrical properties. For the optimal
system setup on a carrier rail, certain guidelines must be observed:
•
The material must be non-corrosive.
•
Most components have a contact to the carrier rail to ground electromagnetic disturbances. In order to avoid corrosion, this tin-plated carrier rail
contact must not form a galvanic cell with the material of the carrier rail
which generates a differential voltage above 0.5 V (saline solution of 0.3 %
at 20°C).
•
The carrier rail must optimally support the EMC measures integrated into
the system and the shielding of the bus module connections.
•
A sufficiently stable carrier rail should be selected and, if necessary, several
mounting points (every 20 cm) should be used in order to prevent bending
and twisting (torsion).
•
The geometry of the carrier rail must not be altered in order to secure the
safe hold of the components. In particular, when shortening or mounting the
carrier rail, it must not be crushed or bent.
•
The base of the I/O components extends into the profile of the carrier rail.
For carrier rails with a height of 7.5 mm, mounting points are to be riveted
under the node in the carrier rail (slotted head captive screws or blind
rivets).
•
The medal springs on the bottom of the housing must have low-impedance
contact with the DIN rail (wide contact surface is possible).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
5.3.2
Table of Contents
57
WAGO DIN Rail
WAGO carrier rails meet the electrical and mechanical requirements shown in the
table below.
Table 18: WAGO DIN Rail
Item Number
210-113 /-112
210-114 /-197
210-118
210-198
210-196
5.4
Description
35 x 7,5;
1 mm;
35 x 15; 1,5 mm;
35 x 15; 2,3 mm;
35 x 15; 2,3 mm;
35 x 7,5;
1 mm;
steel yellow chromated; slotted/unslotted
steel yellow chromated; slotted/unslotted
steel yellow chromated; unslotted
copper; unslotted
aluminum; unslotted
Spacing
The spacing between adjacent components, cable conduits, casing and frame sides
must be maintained for the complete fieldbus node.
Figure 26: Spacing
The spacing creates room for heat transfer, installation or wiring. The spacing to
cable conduits also prevents conducted electromagnetic interferences from
influencing the operation.
Manual
Version 1.1.0
58
5.5
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Assembly Sequence
All system components can be snapped directly on a carrier rail in accordance
with the European standard EN 50022 (DIN 35).
The reliable positioning and connection is made using a tongue and groove
system. Due to the automatic locking, the individual components are securely
seated on the rail after installation.
Starting with the coupler/controller, the bus modules are assembled adjacent to
each other according to the project design. Errors in the design of the node in
terms of the potential groups (connection via the power contacts) are recognized,
as the bus modules with power contacts (male contacts) cannot be linked to bus
modules with fewer power contacts.
Risk of injury due to sharp-edged male contacts!
The male contacts are sharp-edged. Handle the module carefully to prevent injury.
Connect the I/O modules in the required order!
Never plug bus modules from the direction of the end terminal. A ground wire
power contact, which is inserted into a terminal without contacts, e.g. a 4-channel
digital input module, has a decreased air and creepage distance to the neighboring
contact in the example DI4.
Assemble the I/O modules in rows only if the grooves are open!
Please take into consideration that some bus modules have no or only a few power
jumper contacts. The design of some modules does not allow them to be
physically assembled in rows, as the grooves for the male contacts are closed at
the top.
Don't forget the bus end module!
Always plug a bus end module 750-600 onto the end of the fieldbus node! You
must always use a bus end module at all fieldbus nodes with the WAGO I/O
System 750 fieldbus couplers/controllers to guarantee proper data transfer.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
5.6
Table of Contents
59
Inserting and Removing Devices
Use caution when interrupting the PE!
Make sure that people or equipment are not placed at risk when removing an I/O
module and the associated PE interruption. To prevent interruptions, provide ring
feeding of the ground conductor, see section "Grounding/Ground Conductor" in
manual "System Description WAGO-I/O-SYSTEM 750".
Perform work on devices only if the system is de-energized!
Working on devices when the system is energized can damage the devices.
Therefore, turn off the power supply before working on the devices.
Manual
Version 1.1.0
60
Table of Contents
5.6.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Inserting the Fieldbus Coupler/Controller
1.
When replacing the fieldbus coupler/controller for an already available
fieldbus coupler/controller, position the new fieldbus coupler/controller so
that the tongue and groove joints to the subsequent I/O module are engaged.
2.
Snap the fieldbus coupler/controller onto the carrier rail.
3.
Use a screwdriver blade to turn the locking disc until the nose of the locking
disc engages behind the carrier rail (see the following figure). This prevents
the fieldbus coupler/controller from canting on the carrier rail.
With the fieldbus coupler/controller snapped in place, the electrical connections
for the data contacts and power contacts (if any) to the possible subsequent I/O
module are established.
Locking
disc
Release
lug
fix
loosen
Figure 27: Unlocking lug
5.6.2
Removing the Fieldbus Coupler/Controller
1.
Use a screwdriver blade to turn the locking disc until the nose of the locking
disc no longer engages behind the carrier rail.
2.
Remove the fieldbus coupler/controller from the assembly by pulling the
release tab.
Electrical connections for data or power contacts to adjacent I/O modules are
disconnected when removing the fieldbus coupler/controller.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
5.6.3
Table of Contents
61
Inserting I/O Module
1.
Position the I/O module so that the tongue and groove joints to the fieldbus
coupler/controller or to the previous or possibly subsequent I/O module are
engaged.
Figure 28: Insert I/O module
2.
Press the I/O module into the assembly until the I/O module snaps into the
carrier rail.
Figure 29: Snap the I/O module into place
With the I/O module snapped in place, the electrical connections for the data
contacts and power contacts (if any) to the fieldbus coupler/controller or to the
previous or possibly subsequent I/O module are established.
Manual
Version 1.1.0
62
Table of Contents
5.6.4
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Removing the I/O Module
1.
Remove the I/O module from the assembly by pulling the release tab.
Figure 30: Removing the I/O module
Electrical connections for data or power contacts are disconnected when removing
the I/O module.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
6
Connect Devices
6.1
Data Contacts/Internal Bus
Table of Contents
63
Communication between the coupler/controller and the bus modules as well as the
system supply of the bus modules is carried out via the internal bus. It is
comprised of 6 data contacts, which are available as self-cleaning gold spring
contacts.
Figure 31: Data contacts
Do not place the I/O modules on the gold spring contacts!
Do not place the I/O modules on the gold spring contacts in order to avoid soiling
or scratching!
Ensure that the environment is well grounded!
The modules are equipped with electronic components that may be destroyed by
electrostatic discharge. When handling the modules, ensure that the environment
(persons, workplace and packing) is well grounded. Avoid touching conductive
components, e.g. data contacts.
Manual
Version 1.1.0
64
6.2
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Power Contacts/Field Supply
Risk of injury due to sharp-edged male contacts!
The male contacts are sharp-edged. Handle the module carefully to prevent injury.
Self-cleaning power jumper contacts used to supply the field side are located on
the right side of both couplers/controllers and some of the I/O modules. These
contacts come as touch-proof spring contacts. As fitting counterparts the I/O
modules have male contacts on the left side.
Figure 32: Example for the arrangement of power contacts
Field bus node configuration and test via smartDESIGNER
With the WAGO ProServe® Software smartDESIGNER, you can configure the
structure of a field bus node. You can test the configuration via the integrated
accuracy check.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
6.3
Table of Contents
65
Connecting a conductor to the CAGE CLAMP®
The WAGO CAGE CLAMP® connection is appropriate for solid, stranded and
finely stranded conductors.
Note
Only connect one conductor to each CAGE CLAMP® connection!
Only one conductor may be connected to each CAGE CLAMP® connection.
Do not connect more than one conductor at one single connection!
If more than one conductor must be routed to one connection, these must be
connected in an up-circuit wiring assembly, for example using WAGO feedthrough terminals.
Exception:
If it is unavoidable to jointly connect 2 conductors, then you must use a ferrule to
join the wires together. The following ferrules can be used:
Length
8 mm
Nominal cross section max.
1 mm2 for 2 conductors with 0.5 mm2 each
WAGO Product
216-103 or products with comparable properties.
1.
To open the CAGE CLAMP® insert the actuating tool into the opening
above the connection.
2.
Insert the conductor into the corresponding connection opening.
3.
To close the CAGE CLAMP® simply remove the tool - the conductor is
then clamped firmly in place.
Figure 33: Connecting a conductor to a CAGE CLAMP®
Manual
Version 1.1.0
66
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
7
Function Description
7.1
Operating System
After master configuration and electrical installation of the fieldbus station, the
system is operative.
The coupler begins running up after switching on the power supply or after a
reset.
Upon initialization, the fieldbus coupler determines the I/O modules and
configuration. The 'I/O' LED flashes red. After a trouble-free start-up, the coupler
enters “Fieldbus start” mode and the 'I/O' LED lights up green.
In the event of a failure, the 'I/O' LED will blink continuously. Detailed error
messages are indicated by blinking codes; an error is indicated cyclically by up to
3 blinking sequences.
Switching on the
supply voltage
Initialization,
Determination of the I/O modules
and the configuration
‘I/O’ LED is blinking red
Test o.k.?
No
Yes
Fieldbus coupler is
in operating mode
Stop
‘I/O’ LED indicates
the blink code
‘I/O’ LED is shining green
‘I/O’ LED is blinking red
Figure 34: Operating System
More information about the LED Signaling
Read the detailed description for the evaluation of the displayed LED-Signals in
the chapter "Diagnostics" > "LED Signaling".
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
7.2
Table of Contents
67
Process Data Architecture
After switching on the supply voltage, the fieldbus coupler identifies all I/O
modules connected with the node that send or receive data (data width/bit width >
0). In the maximum total extension the node can consist of a mixed arrangement
of a maximum of 64 analog and digital I/O modules, connected on the fieldbus
coupler.
The data of the digital I/O modules are bit-oriented; i.e., digital data are sent bit by
bit. The data of the analog I/O modules are byte-oriented; i.e., analog data are sent
byte by byte. The term “Analog I/O modules” represents the group of byteoriented I/O modules, which send data byte by byte. This group includes, e.g.
counter modules, I/O modules for angle and distance measurement, and
communication modules.
Table 19: Data width of the I/O Modules
Data width = 1 bit per Channel
Digital input modules
Digital output modules
Digital output modules with
diagnostics
Power supply modules with
diagnostics
Solid State Relay
Relais output modules
Up/Down Counter
I/O modules for angle and
distance measurement
Data width  1 word per Channel
Analog input modules
Analog output modules
Analog input modules for Thermocouples
Analog input modules for RTDs
Pulse width output modules
Interface modules
The fieldbus coupler stores the process data in the process images. The fieldbus
coupler works with a process output data image (PIO) and a process input data
image (PII).
The PIO is filled of the fieldbus master with the process output data. The PII is
filled of the fieldbus coupler with the process input data.
Into the input and output process image the data of the I/O modules are stored in
the sequence of its position after the fieldbus coupler in the individual process
image.
First, all the byte-oriented I/O modules are stored in the process image, then the
bit-oriented I/O modules. The bits of the digital I/O modules are grouped into
bytes. If the amount of digital I/O information exceeds 8 bits, the fieldbus coupler
automatically starts a new byte.
Manual
Version 1.1.0
68
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Avoid equipment damages due to addressing errors!
To avoid equipment damages within the field range, you must consider that,
depending on the specific position of an I/O module in the fieldbus node, the
process data of all previous byte or bit-oriented modules must be taken into
account to determine its location in the process data map.
Consider the Process Data size for each module!
Observe the number of input and output bits or bytes for the individual I/O
modules.
Expandable with Module Bus Extension Coupler and End Module!
With the use of the WAGO Module Bus Extension Coupler Module 750-628 and
the End Module 750-627, it is possible to operate up to 250 modules on the
device.
For some I/O modules and their different versions, the structure of the process
data depends on the fieldbus.
Additional information about the fieldbus specific process image
For the fieldbus-specific process image of any WAGO-I/O-Module, please refer
to the section “Structure of the Process Data”.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
7.3
Table of Contents
69
Data Exchange
With the fieldbus coupler, data is exchanged either via the MODBUS/TCP
protocol or via Ethernet/IP.
MODBUS/TCP works according to the master/slave principle. The master
controller can be a PC or a PLC.
The fieldbus couplers of the WAGO-I/O-SYSTEM 750 are slave devices.
The master requests communication. This request can be directed to certain nodes
by addressing. The nodes receive the request and, depending on the request type,
send a reply to the master.
A coupler can set up a defined number of simultaneous connections (socket
connections) to other network subscribers:
•
3 connections for HTTP (to read HTML pages from the coupler)
•
15 connections via MODBUS/TCP (to read or write input and output data of
the coupler)
•
128 connections for Ethernet IP
•
10 connections for FTP
•
2 connections for SNMP
The maximum number of simultaneous connections can not be exceeded. Existing
connections must first be terminated before new ones can be set up. The
ETHERNET Fieldbus Coupler is essentially equipped with two interfaces for data
exchange:
•
•
the interface to the fieldbus (Master)
the interface to the I/O modules.
Data exchange takes place between the fieldbus master and the I/O modules.
If MODBUS is used as the fieldbus, the MODBUS master accesses the date using
the MODBUS functions implemented in the fieldbus coupler; Ethernet/IP, in
contrast, uses an object model for data access.
Manual
Version 1.1.0
70
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
fieldbus coupler
memory area
for input data
word 0
I/O modules
1
input
modules
fieldbus
master
word 255
memory area
for output data
word 0
2
output
modules
I
O
word 255
A Figure 35: Memory areas and data exchange
The coupler process image contains the physical data for the bus modules.
These have a value of 0 ... 255 and word 512 ... 1275.
1
The input module data can be read by the CPU and by the fieldbus side.
2
Likewise, data can be written to the output modules from the CPU and the
fieldbus side.
In addition, all output data is mirrored in the ETHERNET Fieldbus Coupler to a
memory area with the address offset 0x0200 and 0x1000. This allows output
values to be read back in by adding 0x0200 or 0x1000 to the MODBUS address.
7.3.1
Addressing
Module inputs and outputs in a fieldbus coupler are addressed internally as soon
as hey are started. The order in which the connected modules are addressed
depends on the type of module that is connected (input module, output module).
The process image is formed from these addresses.
The physical arrangement of the I/O modules in the fieldbus node is arbitrary.
7.3.1.1
Addressing of I/O Modules
Addressing first references complex modules (modules that occupy several bytes)
in accordance with their physical order downstream of the fieldbus
coupler/controller; i.e., they occupy addresses starting from word 0.
Following these is the data for the remaining modules, compiled in bytes
(modules that occupy less than one byte). In this process, byte by byte is filled
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
71
with this data in the physical order. As soon a complete byte is occupied by the bit
oriented modules, the process begins automatically with the next byte.
Note
Hardware changes can result in changes of the process image!
I f the hardware configuration is changed and/or expanded; this may result in a
new process image structure. In this case, the process data addresses also change.
If adding modules, the process data of all previous modules has to be taken into
account.
Note
Observe process data quantity!
For the number of input and output bits or bytes of the individual IO modules
please refer to the corresponding description of the IO modules.
Table 20: Data with for I/O modules
Data width ≥ 1 word (channel)
Analog input modules
Analog output modules
Input modules for thermocouples
Input modules for resistor sensors
Pulse width output modules
Interface modules
Up/down counters
I/O modules for angle and distance
measurement
7.3.1.2
Data width = 1 bit (channel)
Digital input modules
Digital output modules
Digital output modules with
diagnostics (2 bits/channel)
Supply modules with fuse
carrier/diagnostics
Solid-state load relays
Relay output modules
Address Ranges
Subdivision of the address ranges for word-by-word addressing in accordance
with IEC-61131-3:
Manual
Version 1.1.0
72
Table of Contents
7.3.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Data Exchange between MODBUS/TCP Master and I/O
Modules
Data exchange between the MODBUS/TCP Master and the I/O modules is
conducted using the MODBUS functions implemented in the controller by means
of bit-by-bit or word-by-word reading and writing routines.
There are 4 different types of process data in the controller:
•
•
•
•
Input words
Output words
Input bits
Output bits
Access by word to the digital I/O modules is carried out in accordance with the
following table:
Table 21: Allocation of digital inputs and outputs to process data words in accordance with the
Intel format
Digital inputs/
16. 15. 14. 13. 12. 11. 10. 9. 8. 7. 6. 5. 4. 3. 2. 1.
outputs
Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit
Process data
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
word
Byte
High byte D1
Low byte D0
Output can be read back in by adding an offset of 200hex (0x0200) to the
MODBUS address.
Note
Data > 256 words can be read back by using the cumulative offset!
All output data greater than 256 words and, therefore located in the memory range
0x6000 to 0x62FC, can be read back by adding an offset of 1000hex (0x1000) to
the MODBUS address.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
73
MODBUS master
0x0000
0x6000 0x0000
(0x0200)
PIO
PII
0x00FF
0x6000
(0x7000)
00x0FF
0x62FC (0x02FF)
0x62FC
(0x72FC)
Outputs
Inputs
I/O modules
PII = Process Input
Image
PIO = Process Output
Image
Programmable Fieldbus Controller
Figure 36: Data exchange between MODBUS Master and I/O modules
Register functions start at address 0x1000. These functions can be addressed in a
similar manner with the MODBUS function codes that are implemented
(read/write).
The specific register address is then specified instead of the address for a module
channel.
Information
Additional Information
A detailed description of the MODBUS addressing may be found in Chapter
"MODBUS Register Mapping“.
7.3.2.1
Data Exchange between EtherNet/IP Master and I/O Modules
The data exchange between Ethernet/IP master and the I/O modules is
objectoriented. Each node on the network is depicted as a collection of objects.
The "assembly" object specifies the structure of the objects for the data
transmission. With the assembly object, data (e.g. I/O data) can be combined into
blocks (mapped) and sent via a single message connection. Thanks to this
mapping, less access to the network is necessary.
There is a distinction between input and output assemblies.
An input assembly reads in data from the application via the network or produces
data on the network.
An output assembly writes data to the application or consumes data from the
network.
In the fieldbus coupler/controller, various assembly instances are already
preprogrammed (static assembly).
Manual
Version 1.1.0
74
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
After the input voltage is applied, the assembly object combines 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 it or read and write using
I/O connections.
The mapping of the data depends on the assembly instance of the static assembly
selected.
Information
Additional Information:
The assembly instances for the static assembly are described in the section
"Ethernet/IP".
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8
Table of Contents
75
Commissioning
This chapter shows a step-by-step procedure for starting up exemplariliy a
WAGO fieldbus node.
Note
Good example!
This description is just an example and only serves to describe the procedure for a
local start-up of a single fieldbus node with a non-networked computer under
Windows.
Two work steps are required for start-up. The description of these work steps can
be found in the corresponding following sections.
•
Connecting client PC and fieldbus nodes
•
Assigning the IP address to the fieldbus node
The IP address must occur in the network only once!
For error-free network communication, note that the assigned IP address must
occur only once in the network!
In the event of an error, the error message "IP address configuration error" (error
code 6 - error argument 6) is indicated by 'I/O' LED at the next power-on.
There are various ways to assign the IP address.
The various options are described in the following sections individually.
Following the commissioning descriptions after which the fieldbus node is ready
for communication, the following topics are described:
•
Preparing the Flash File System
•
Restoring factory settings
Manual
Version 1.1.0
76
Table of Contents
8.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Connecting Client PC and Fieldbus Nodes
1. Mount the fieldbus node on the TS 35 carrier rail.
Follow the assembly instructions found in the "Assembly" chapter.
2. Connect the 24V power supply to the supply terminals.
3. Connect the PC's Ethernet interface to the fieldbus coupler's Ethernet
interface.
4. Turn the operating voltage on.
The fieldbus coupler is initialized. The coupler determines the I/O module
configuration and creates a process image.
During start-up, the I/O LED (red) flashes.
If the I/O LED lights up green after a brief period, the fieldbus coupler is
operational.
If an error has occurred during startup, a fault code is flashed on the I/O LED.
If the I/O LED flashes 6 times (indicating error code 6) and then 4 times
(indicating error argument 4), an IP address has not been assigned yet.
8.2
Allocating the IP Address to the Fieldbus Node
•
Use address selection switch (DIP switch) to assign IP address (manually).
•
Automatic assignment of addresses via DHCP
•
8.2.1
Assigning IP Address via BootP server
Assigning IP Address via Address Selection Switch
Use the address selection switch to set the host ID, i.e., the last byte ("X") of the
IP address saved in the fieldbus coupler with values between 1 and 254 binary
coded.
Example:
IP address saved in the fieldbus coupler:
Set DIP switch value:
Resulting IP address:
192.168.7.33
50 (binary coded: 00110010)
192.168.7.50
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
77
Note
Host ID 1 - 254 via address selection switch freely adjustable!
Use the address selection switch to set the last byte ("X") of the IP address to a
value between 1 and 254. The DIP switch is then enabled and the IP address is
composed of the base address stored in the fieldbus coupler and the host ID set on
the DIP switch.
The IP address make via the Web-based Management System is disabled.
Note
Address selection switch values 0 and 255 are predefined, address selection
switch disabled!
If you use the address selection switch to set the value 0 or 255, the address
selection switch is disabled and the setting configured in the fieldbus coupler is
used.
With the value 0, the settings of the Web based Management System apply.
If you set the value 255, the configuration via DHCP is activated.
The base address used consists of the first three bytes of the IP address. This
always depends on the IP address currently saved in the fieldbus coupler.
If there is still no static IP address in the fieldbus coupler, the default value
192.168.1.X defined by the firmware as the base address is used when setting the
DIP switch to 1 - 254.
The address selection switch setting then overwrites the value of the host ID "X".
Information
More information about changing the static base address
You can also change the base address currently saved in the fieldbus coupler as
required.
Proceed as described in the following section "Assigning IP Address via Web
Server".
1.
To configure the IP address via the address selection switch by setting the
host ID (last position of the IP address) to a value that does not equal 0/255,
first convert the host ID to the binary representation.
For example, host ID 50 results in a binary code of 00110010.
2.
Set the bits in sequence using the 8 address switches. Start with address
switch 1 to set bit 0 (LSB) and end with address switch 8 for bit 7 (MSB).
Manual
Version 1.1.0
78
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8
7
6
5
4
3
2
1
ON
0
0
1
1
0
0
1
0
OFF
Figure 37: Address selection switch
3.
8.2.2
Restart the fieldbus coupler after adjusting the address selection switch to
apply the configuration changes.
Assigning IP Address via DHCP
If you want to use DHCP to assign the IP address, it happens automatically via a
DHCP server on the network.
Note
Total network failure when there are two DHCP servers in the network!
To prevent network failure, never connect a PC, on which a DHCP server is
installed, to a global network. In larger networks, there is usually a DHCP server
already that can cause collisions and subsequent network failure.
Note
There must be a DHCP server in the network for further configuration!
Install a DHCP server on your client PC in the local network if not already
available. You can download a DHCP server free of charge on the Internet, e.g.,
http://windowspedia.de/dhcp-server_download/.
Note
Assign the client PC a fixed IP address and note common subnet!
Note that the client PC, on which the DHCP server is listed, must have a fixed IP
address and that the fieldbus node and client PC must be in the same subnet.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
79
The following steps are included:
•
•
8.2.2.1
Enable DHCP
Disable DHCP
Enable DHCP
Set the address selection switch to 255 for active software configuration!
Set the address selection switch to 255 to disable the DIP switch and to enable
DHCP.
Restart the fieldbus node after adjusting the address selection switch to apply the
configuration changes.
Note
DHCP must be enabled on the Web pages (for this, address selection switch
must be on 0)!
Note that DHCP must be enabled on the internal Web pages of the WBM, HTML
page "Port configuration".
An IP address is automatically assigned after restarting the fieldbus node.
8.2.2.2
Disabling DHCP
DHCP must be disabled to assign the address permanently!
To apply the new IP address permanently in the fieldbus coupler, DHCP must be
disabled.
This prevents the fieldbus coupler from receiving a new DHCP request.
You can disable DHCP in two ways:
•
•
Disable DHCP via the address selection switch.
Disable DHCP in the Web-based Management System.
Disable DHCP via the address selection switch.
Manual
Version 1.1.0
80
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Note
Do not set the address selection switch to 0/255 again!
Do not switch the address selection switch to 0/255 again because doing so
automatically enables DHCP and disables the DIP switch.
1.
Use the address selection switch to set a value between 1 and 254. The
address saved in the fieldbus coupler is then valid (with changed host ID =
DIP switch).
(Example: If the address 10.127.3.15 was saved in the fieldbus coupler and
you set the switch to 50 (binary coded 00110010), for example, the fieldbus
coupler then has the address 10.127.3.50.)
2.
Restart the fieldbus coupler after adjusting the address selection switch to
apply the configuration changes.
Disable DHCP in the Web-based Management System
Set the address selection switch to 0 for active software configuration!
Set the address selection switch to 0 to disable address selection via DIP switch or
DHCP.
1.
Launch a Web browser (e.g., MS Internet Explorer or Mozilla) and enter the
IP address you have assigned your fieldbus node in the address bar.
2.
Click [Enter] to confirm.
The start page of the Web based Management System loads.
3.
Select "Port" in the left menu bar.
4.
Enter your user name and password in the inquiry screen (default: user =
"admin", password = "wago" or user = "user", password = "user").
The HTML page "Port configuration" loads:
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
81
Figure 38: WBM page "Port"
8.2.3
5.
Disable DHCP by selecting the option “BootP” or “use IP fom
EEPROM”.
6.
Click on [SUBMIT] to apply the changes in your fieldbus node.
7.
Restart the fieldbus node to apply the settings of the Web interface.
Assigning the IP Address with a BootP Server
A BootP server or PLC program can be used to assign a fixed IP address.
Assigning the IP address using a BootP server depends on the respective BootP
program. Handling is described in the respective manual for the program or in the
respective integrated help texts.
Manual
Version 1.1.0
82
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Set the address selection switch to 0 for active software configuration!
Set the address selection switch to 0 to disable the DIP switch and to enable the
software configuration via BootP.
Restart the fieldbus node after adjusting the address selection switch to apply the
configuration changes.
IP address assignment is not possible via the router!
The IP address is assigned via patch cable, switches, hubs, or via direct link using
a crossover cable. Addresses can not be allocated via router.
BootP must be enabled on the Web pages!
Note that BootP must be enabled on the internal Web pages of the WBM, HTML
page "Port configuration".
BootP is enabled by default when delivered.
Information
Additional Information
Assigning IP addresses using the WAGO-BootP server can be carried out in any
Windows and Linux operating system. Any other BootP servers may also be used,
besides the WAGO-BootP server.
The following steps are included:
•
•
•
•
Note MAC ID
Note IP address
Assigning the IP address and enable BootP
Disable BootP
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8.2.3.1
Table of Contents
83
Note MAC ID
1.
Write down the couplers’s MAC address (see label or peel-off strip).
If the fieldbus is already installed, turn off the operating voltage of the
fieldbus coupler, then take the fieldbus coupler out of the assembly of your
fieldbus node and note the MAC ID of your fieldbus coupler.
The MAC ID is applied to the back of the fieldbus coupler or on the selfadhesive peel-off strip on the side of the fieldbus coupler.
MAC ID of the fieldbus coupler: 0 0 : 3 0 : D E : _ _ : _ _ : _ _
2.
Plug the fieldbus coupler into the assembly of the fieldbus node.
3.
Use the fieldbus cable to connect the fieldbus connection of your
mechanically and electrically assembled fieldbus node to an open interface
on your computer.
The client PC must be equipped with a network card for this connection.
The controller transfer rate then depends on the network card of your client
PC.
4.
Start the client that assumes the function of the master and BootP server.
5.
Switch on the power at the coupler (DC 24 V power supply unit).
The fieldbus coupler is initialized. The coupler determines the I/O module
configuration and creates a process image.
During start-up, the I/O LED (red) flashes.
If the I/O LED lights up green after a brief period, the fieldbus coupler is
operational.
If an error occurs during start-up indicated by the I/O LED flashing red, evaluate
the error code and argument and resolve the error.
Information
More information about LED signaling
The exact description for evaluating the LED signal displayed is available in the
section "Diagnostics", "LED Signaling".
Error code 6, followed by error argument 4, is indicated by the I/O LED after
coupler start-up with 6 red error code flashes, followed by four red flashes of the
error argument. This indicates that an IP address has not yet been assigned.
Manual
Version 1.1.0
84
Table of Contents
8.2.3.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Determining IP addresses
1.
If the client PC is already integrated into an IP network, you can determine
the client PC's IP address by clicking on Control Panel from the Start
Menu / Settings.
2.
Double-click on the Network icon.
The network dialog window appears.
For Windows NT:
•
•
Select the Protocols tab
Mark the entry TCP/IP protocol
For Windows 2000/XP:
•
•
•
Select Network and Dial-Up Connections
In the dialog window that then appears, right click on LAN Connection
and open the Properties link.
Mark the entry Internet Protocol (TCP/IP)
Note
Reinstall TCP/IP components if required!
If the "Internet Protocol TCP/IP" entry is missing, install the corresponding
TCP/IP components and reboot your computer.
You will need the installation CD for Windows NT, 2000 or XP.
3.
Then click on the Properties... button
4.
The IP address, subnet mask and, where required, the client PC's gateway
address appear in the Properties window. Note these values:
Client PC IP address:
Subnet mask:
Gateway:
5.
___ . ___ . ___ . ___
___ . ___ . ___ . ___
___ . ___ . ___ . ___
Now select the desired IP address for your fieldbus node.
Note
Assign the client PC a fixed IP address and note common subnet!
Note that the client PC, on which the BootP server is listed, must have a fixed IP
address and that the fieldbus node and client PC must be in the same subnet.
6.
Note the IP address you have selected:
Fieldbus node IP address:
___ . ___ . ___ . ___
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8.2.3.3
8.2.3.4
Table of Contents
85
Assigning the IP address and Enable BootP
1.
Based on the handling, which depends on the BootP program set, assign the
required IP address for your fieldbus node.
2.
Enable the query/response mechanism of the BootP protocol based on the
handling, which depends on the BootP program set.
3.
To apply the new IP address, use a hardware reset to restart your fieldbus
node (interrupt the voltage supply for approx. 2 seconds).
Disabling BootP
When the BootP protocol is activated the coupler expects the BootP server to be
permanently available. If there is no BootP server available after a PowerOn reset,
the network will remain inactive.
You must then deactivate the BootP protocol so that the coupler uses the
configurated IP address from the EEPROM; this does away with the need for the
BootP server to be permanently available.
BootP must be disabled to assign the address permanently!
To apply the new IP address permanently in the fieldbus coupler, BootP must be
disabled.
This prevents the fieldbus coupler from receiving a new BootP request.
No loss if the IP Address with deactivated BootP Protocol!
If the BootP protocol is deactivated after addresses have been assigned, the stored
IP address is retained, even after an extended loss of power, or when the
controller is removed
You can disable in the Web-based Management System.
Disable BootP in the Web-based Management System
1.
Open the Web browser on your client (such as the Microsoft Internet
Explorer) to have the HTML pages displayed.
2.
Enter the IP address for your fieldbus node in the address line of the
browser and press [Return].
Manual
Version 1.1.0
86
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
A dialog window then appears with a password prompt. This is provided for
secure access and entails three different user groups: admin, guest and user.
3.
As Administrator, enter the user name: "admin" and the password "wago".
A start page is then displayed in the browser window with information about your
fieldbus coupler. You can navigate to other information using the hyperlinks in
the left navigation bar.
Figure 39: WBM page "Information"
Disable the proxy server to display the web-based Management-System!
If these pages are not displayed for local access to the fieldbus nodes, you must
define in the Web browser properties that, as an exception, no proxy server are to
be used for the node IP address.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
87
The coupler IP can be changed in the network by the DHCP server!
If BootP is not deactivated and an ISDN/DSL router is installed in the network
(factory default setting with DHCP server activated) addresses will be assigned
automatically from the address range for the ISDN/DSL router after a loss of
power (loss of 24 V DC power to coupler). As a result, all couplers will be
assigned new IP addresses!
4.
In the left navigation bar click on Port to open the HTML page for selecting
a protocol.
Figure 40: WBM page "Port"
You are shown a list of all the protocols supported by the coupler.
5.
Select the option "DHCP" or "use IP from EEPROM".
You have now deactivated the BootP protocol.
You can also deactivate any other protocols that you no longer need in the same
manner, or select desired protocols and activate them explicitly.
Manual
Version 1.1.0
88
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Since communication for each protocol takes place via different ports, you can
have several protocols activated simultaneously; communication takes place via
these protocols.
The protocol settings are then saved and the coupler is ready for operation.
8.2.3.5
Reasons for Failed IP Address Assignment
•
The controller MAC address does not correspond to the entry given in the
"bootstrap.txt" file.
•
The client on whom the BootP server is running is not located in the same
subnet as the controller; i.e., the IP addresses do not match
Example: Client IP: 192.168.0.10 and controller IP: 10.1.254.5
•
Client and/or controller is/are not linked to the ETHERNET
•
Poor signal quality (use switches or hubs)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8.3
Table of Contents
89
Testing the Function of the Fieldbus Node
1.
To ensure that the IP address is correct and to test communication with the
fieldbus node, first turn off the operating voltage of the fieldbus node.
2.
Create a non-serial connection between your client PC and the fieldbus
node.
The fieldbus coupler is initialized. The coupler determines the I/O module
configuration and creates a process image.
During start-up, the I/O LED (red) flashes.
If the I/O LED lights up green after a brief period, the fieldbus coupler is
operational.
If an error occurs during start-up indicated by the I/O LED flashing red, evaluate
the error code and argument and resolve the error.
Information
More information about LED signaling
The exact description for evaluating the LED signal displayed is available in the
section "Diagnostics", "LED Signaling".
3.
To test the coupler’s newly assigned I/P address, start a DOS window by
clicking on the Start menu item Programs/MS-DOS Prompt.
4.
In the DOS window, enter the command: "ping " followed by the IP address
of your coupler in the following format:
ping [space] XXX . XXX . XXX . XXX (=IP address)
Figure 41: Example for the Function test of a Fieldbus Node
5.
When the [Enter] key has been pressed, your PC will receive a query from
the coupler, which will then be displayed in the DOS window.
If the error message: "Timeout" appears, please compare your entries again
to the allocated IP address and check all connections.
6.
When the test has been performed successfully, you can close the DOS
prompt.
The fieldbus node is now ready for communication.
Manual
Version 1.1.0
90
8.4
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Preparing the Flash File System
The flash file system must be prepared in order to use the Web interface of the
fieldbus coupler to make all configurations.
The flash file system is already prepared when delivered.
However, if the flash file system has not been initialized on your fieldbus coupler
or it has been destroyed due to an error, you must first extract it to the flash
memory to access it.
Do not connect 750-920 Communication Cable when energized!
To prevent damage to the communications interface, do not connect or disconnect
750-920 Communication Cable when energized! The fieldbus coupler must be deenergized!
Formatting erases data!
Note that formatting erases all data and configurations.
Only use this function when the flash file system has not been initialized yet or
has been destroyed due to an error.
1.
Switch off the supply voltage of the fieldbus coupler.
2.
Connect the communication cable 750-920 to the configuration interface of
the fieldbus coupler and to a vacant serial port on your computer.
3.
Switch on the supply voltage of the fieldbus coupler.
The fieldbus coupler is initialized. The coupler determines the I/O module
configuration and creates a process image.
During start-up, the I/O LED (red) flashes.
If the I/O LED lights up green after a brief period, the fieldbus coupler is
operational.
If an error occurs during start-up indicated by the I/O LED flashing red, evaluate
the error code and argument and resolve the error.
Information
More information about LED signaling
The exact description for evaluating the LED signal displayed is available in the
section "Diagnostics", "LED Signaling".
4.
Start the WAGO-ETHERNET-Settings program.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
91
5.
In the top menu bar, select Format to format the file system.
Formatting is complete when the status window displays "Formatting flash
disk successfully done".
6.
In the top menu bar, select Extract to extract the Web pages of the flash file
system.
This process takes a few seconds and is complete when the status window
displays "Extracting files successfully done."
Note
Restart the Fieldbus coupler/controller after [Format]/[Extract]!
Make a restart of the fieldbus coupler/controller, so that the Web pages can be
displayed after a Format/Extract.
Manual
Version 1.1.0
92
8.5
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Restoring Factory Settings
To restore the factory settings, proceed as follows:
1.
Switch off the supply voltage of the fieldbus coupler.
2.
Connect the communication cable 750-920 to the configuration interface of
the fieldbus coupler and to a vacant serial port on your computer.
3.
Switch on the supply voltage of the fieldbus coupler.
4
Start the WAGO-ETHERNET-Settings program.
5.
In the top menu bar, select Default and click [Yes] to confirm.
A restart of the fieldbus node is implemented automatically. The start takes place
with the default settings.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
9
Table of Contents
93
Configuring via the Web-Based Management
System (WBM)
An internal file system and an integrated Web server can be used for
configuration and administration of the system. Together, they are referred to as
the Web-Based Management System (WBM).
The HTML pages saved internally provide you with information about the
configuration and status of the fieldbus node. In addition, you can also change the
configuration of the device here.
You can also save HTML pages created yourself via the implemented file system.
Note
Always restart after making changes to the configuration!
The system must always be restarted for the changed configuration settings to
take effect.
1.
To open the WBM, launch a Web browser (e.g., Microsoft Internet Explorer
or Mozilla Firefox).
2.
Enter the IP address of the fieldbus coupler/controller in the address bar
(192.168.1.1 by default or as previously configured).
3.
Click [Enter] to confirm.
The start page of WBM loads.
4.
Select the link to the desired HTML page in the left navigation bar.
A query dialog appears.
5.
Enter your user name and password in the query dialog (default: user =
"admin", password = "wago" or user = "user", password = "user").
The corresponding HTML page is loaded.
6.
Make the desired settings.
7.
Press [SUBMIT] to confirm your changes or press [UNDO] to discard the
changes.
8.
Restart the system to apply the settings.
Manual
Version 1.1.0
94
9.1
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Information
The default start page of the WBM "Information" contains an overview of all
important information about your fieldbus coupler/controller.
Figure 42: WBM page "Information"
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 22: WBM page "Information"
Coupler details
Entry
Default
Order number
750-352/000-000
Mac address
0030DEXXXXXX
Firmware
kk.ff.bb (rr)
revision
Manual
Version 1.1.0
Table of Contents
95
Value (example)
750-352/000-000
0030DE000006
01.01.09 (00)
Description
Item number
Hardware MAC address
Firmware revision number
(kk = compatibility, ff =
functionality, bb = bugfix, rr =
revision)
Actual network settings
Entry
Default
IP address
192.168.1.1
Value (example)
192.168.1.80
Subnet mask
Gateway
Hostname
Domainname
255.255.255.0
0.0.0.0
___
___
255.255.255.240
192.168.1.251
___
___
Description
IP address,
Type of IP address assignment
Subnet mask
Gateway
Host name (not assigned here)
Domain name (not assigned here)
DNS server 1
DNS server 2
Module status
Entry
State Modbus
Watchdog
Error code
Error argument
Error description
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Address of first DNS server
Address of second DNS server
Default
Disabled
Value (example)
Disabled
Description
Status of Modbus Watchdog
0
10
0
5
Coupler running, OK Mismatch in
CoDeSys IOconfiguration
Error code
Error argument
Error description
96
9.2
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Ethernet
Use the "Ethernet" HTML page to set the data transfer rate and bandwidth limit
for each of the two switch ports for data transfer via Ethernet.
Figure 43: WBM page "Ethernet"
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 23: WBM page "Ethernet"
Phy Configuration
Entry
Default
Enable Port

Enable autonegotiation

10 MBit Half Duplex
10 MBit Full Duplex
100 MBit Half Duplex
100 MBit Full Duplex




97
Description
 Enable Port 1/Port 2
 Disable Port 1/Port 2
 Enable Autonegotiation
Automatically set the best possible transmission
speed with "Enable Autonegotiation".
 Enable Autonegotiation
Select half or full duplex for the ETHERNET to
configure a fixed transmission speed 10 or 100 MBit
Misc. Configuration
Entry
Input Limit Rate
Output Limit Rate
Port
1 2
Description
internal
No Limit
No Limit
The Input Limit Rate limits network traffic when
receiving. The rate is indicated in megabytes or
kilobytes per second. If the limit is exceeded, packets
are lost.
The Output Limit Rate limits network traffic when
sending. The rate is indicated in megabytes or kilobytes
per second. If the limit is exceeded, packets are lost.
 Broadcast Protection limits the number of
BC protection
Ethernet MTU
 
1500
broadcast telegrams per unit of time. If protection
is on, the broadcast packets are limited at 100
Mbit to 8 packets per 10 ms and at 10 Mbit to 8
packets per 100 ms. If the limit is exceeded,
packets are lost.
 Broadcast Protection disabled.
Maximum packet size of a protocol, which can be
transferred without fragmentation ("Maximum
Transmission Unit" - MTU)
Note
Set the MTU value for fragmentation only!
Only set the value for MTU, i.e., the maximum packet size between client and
server, if you are using a tunnel protocol (e.g., VPN) for ETHERNET
communication and the packets must be fragmented.
Setting the value is independent of the transmission mode selected.
Manual
Version 1.1.0
98
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Configure ETHERNET transmission mode correctly!
A fault configuration of the ETHERNET transmission mode may result in a lost
connection, poor network performance or faulty performance of the fieldbus
coupler/controller.
All ETHERNET ports cannot be disabled!
Both ETHERNET ports can be switched off. If both ports are disabled and you
press [SUBMIT], the selection is not applied and the previous values are restored.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
9.3
Table of Contents
99
TCP/IP
You can configure network addressing and network identification on the
"TCP/IP" HTML page.
Set the DIP switch to "0" and enable "use IP from EEPROM"!
Before you change parameters on this page, set the DIP switch to zero and on the
"Port configuration" WBM page, set the "use IP from EEPROM" option!
If these conditions are not met, the DIP switch settings are applied instead.
Figure 44: WBM page "TCP/IP"
Manual
Version 1.1.0
100
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 24: WBM page „TCP/IP“
Configuration Data
Entry
Default
IP address
Subnet mask
Gateway
Host name
Domain name
DNS Server1
DNS Server2
Switch IP-Address
Value
(example)
192.168.1.0
192.168.1.200
255.255.255.0 255.255.255.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
192.168.1
192.168.5
Description
Enter IP address
Enter subnet mask
Enter gateway
Enter host name
Enter domain name
Enter IP address of the first DNS server
Enter optional IP address of the second
DNS server
Network address for the configuration of
the IP address with DIP switch
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
9.4
Table of Contents
Port
Use the "Port" HTML page to enable or disable services available via the IP
protocol.
Figure 45: WBM page "Port"
Manual
Version 1.1.0
101
102
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 25: WBM page "Port"
Port Settings
Entry
Entry
FTP (Port 21)
Enabled

HTTP (Port 80)
Enabled

SNMP (Port 161, 162)
Enabled

Ethernet IP (TCP-Port 44818,
UDP-Port 2222)
Enabled

Modbus UDP (Port 502)
Enabled

Modbus TCP (Port 502)
Enabled

WAGO Services (Port 6626)
Enabled

BootP (Port 68)
Enabled

DHCP (Port 68)
Enabled

Entry
 activating "File Transfer Protocol"
 deactivating "File Transfer Protocol"
 activating "Hypertext Transfer Protocol"
 deactivating "Hypertext Transfer Protocol"
 activating "Simple Network Management

Protocol"
deactivating "Simple Network Management
Protocol"
activating ETHERNET/IP protocol
deactivating ETHERNET/IP protocol
activating MODBUS/UDP protocol
deactivating MODBUS/UDP protocol
activating MODBUS/TCP protocol
deactivating MODBUS/TCP protocol
activating WAGO services
de activating WAGO services








 activating "Boots Trap Protocol"
 deactivating "Boots Trap Protocol"
 activating "Dynamic Host Configuration
Protocol"
 deactivating "Dynamic Host Configuration
Protocol"
use IP from EEPROM
Enabled

 activating use of IP address from EEPROM
 deactivating use of IP address from
EEPROM
Alternative IP address assignment!
You can only select the DHCP, BootP and "use IP from EEPROM" settings as an
alternative!
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
9.5
Table of Contents
103
SNMP
On the HTML page "SNMP", you can perform the settings for the Simple
Network Management Protocol.
SNMP is a standard for device management within a TCP/IP network. The Simple
Network Management Protocol (SNMP) is responsible for transporting the control
data that allows the exchange of management information, the status and statistic
data between individual network components and a management system.
The fieldbus coupler/controller supports SNMP in versions 1, 2c and 3.
The SNMP of the ETHERNET TCP/IP coupler includes the general MIB
according to RFC1213 (MIB II).
SNMP is processed via port 161. The port number for SNMP traps (agent
messages) is 162.
Note
Enable port 161 and 162 to use SNMP!
Enable ports 161 and 162 in the WBM in menu "port", so that the fieldbus
coupler/controller can be reached via SNMP. The port numbers cannot be
modified.
Note
Modify parameter via WBM or SNMP objects!
However, parameters that can be set on the html pages can also be changed
directly by the appropriate SNMP objects.
Information
Additional Information:
Additional information for SNMP, the Management Information Base (MIB) and
traps (event messages via SNMP) may be obtained from chapter "Fieldbus
communications" > "Communications protocols" > "SNMP (Simple Network
Management Protocol)".
Note that the settings for SNMPV1/V2c and SNMPV3 are separate from each
other: The different SNMP versions can be activated or used in parallel or
individually on a fieldbus controller.
Manual
Version 1.1.0
104
Table of Contents
9.5.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
SNMP V1/V2c
The SNMP version 1/2c represents a community message exchange. The
community name of the network community must thereby be specified.
Figure 46: WBM page "SNMP"
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 26: WBM page "SNMP"
SNMP Configuration
Entry
Value (Default)
Name of device
750-352
ETHERNET
Description
Fieldbus Coupler
750-352
Physical location
LOCAL
Contact
[email protected]
Table of Contents
105
Description
Device name (sysName)
Device description (sysDescription)
Location of device (sysLocation)
E-mail contact address (sysContact)
SNMP v1/v2 Manager Configuration
Entry
Value (Default) Description
 Activating SNMP Version 1/2c
SNMP
Protocol Enable

V1/V2c
 Deactivating SNMP-Version 1/2c
Used community name
Local Community
public
Name
SNMP v1/v2 Trap Receiver Configuration
Entry
Value (Default) Description
Trap Receiver 1
0.0.0.0
IP address of 1. used SNMP manager
Community Name 1 public
1. Community name of the network community used
Activating Traps Version 1
 V1  V2 
V1
Trap Version
V2
 V1  V2 
Activating Traps Version 2
Trap Receiver 2
0.0.0.0
IP address of 2. used SNMP manager
Community Name 2 public
2. Community name of the network community used
Activating Traps Version 1
 V1  V2 
V1
Trap Version
V2
 V1  V2 
Activating Traps Version 2
Manual
Version 1.1.0
106
Table of Contents
9.5.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
SNMP V3
In SNMP version 3, exchanging messages is user-related. Each device, that knows
the passwords set via WBM, may read or write values from the controller. In
SNMPv3, user data from SNMP messages can also be transmitted in encoded
form. This is why SNMPv3 is often used in safetyrelated networks.
Figure 47: WBM page "SNMP V3"
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
SNMP v3 (user based)
Entry
Value
(Example)
1. User / 2. User
activate
Description


Authentification
Type
None
MD5
SHA1
Security
Authentification
Name
Security Name
Authentification Key
Privacy Enable
Privacy Key
Notification/
Trap enable
Notification
Receiver IP
107


 Activating user 1 or 2
 Deactivating user 1 or 2
No encryption of the
authentication
Encryption of the
None  MD5  SHA1 
authentication with MD5
Encryption of the
None  MD5  SHA1 
authentication with SHA1
None  MD5  SHA1 
Enter the name, if the "authentification type“ MD5 or
SHA1 has been selected
Authentification Enter the password with at least 8 characters, if
Key
"authentification type“ MD5 or SHA1 has been selected
 Activate the DES encryption of the data
DES

 Deactivate the DES encryption of the data
Enter the password of at least 8 characters in the
Privacy Key
encryption with DES
 Activate the notification traps of the SNMP version 3
V3
  Deactivate the notification traps of the SNMP version
3
192.168.1.10
IP address of the notification manager
Two independent SNMPv3 users can be defined and activated via the html page
(user 1 and user 2).
Manual
Version 1.1.0
108
9.6
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Watchdog
Click the link "Watchdog" to go to a Web site where you can specify the settings
for the connection and MODBUS watchdog.
Figure 48: WBM page „Watchdog“
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 27: WBM page "Watchdog"
Connection watchdog
Entry
Default
Connection Timeout Value 600
(100 ms)
Modbus Watchdog
Entry
State Modbus Watchdog
Watchdog Type
Watchdog Timeout Value
(100 ms)
Watchdog Trigger Mask
(F 1 to F16)
Watchdog Trigger Mask
(F17 to F32)
Manual
Version 1.1.0
Default
Disabled
109
Description
Monitoring period for TCP links.
After the completion of this period without any
subsequent data traffic, the TCP connection is
closed.
Description
Enabled – Watchdog is activated
Disabled – Watchdog is disabled
Standard  The set coding mask (watchdog trigger mask) is
evaluated to determine whether the watchdog time is
reset.
Alternative  The watchdog time is reset by any Modbus/TCP
telegram.
100
Monitoring period for Modbus links. After the
completion of this period without receiving a
Modbus telegram, the physical outputs are set to "0".
0xFFFF
Coding mask for certain Modbus telegrams
(Function Code FC1 ... FC16)
0xFFFF
Coding mask for certain Modbus telegrams
(Function Code FC17 ... FC32)
110
9.7
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Security
Use the "Security" HTML page with passwords to set up read and/or write access
for various user groups to protect against configuration changes.
Note
Passwords can only be changed by "admin" and after software reset!
The "admin" user and associated password are required to change passwords.
Press the [Software Reset] button to restart the software for the setting changes to
take effect.
Note
Note password restrictions!
The following restrictions apply for passwords:
• Max. 16 characters
• Letters and numbers only
• No special characters or umlauts
Renew access after software reset!
If you initiate a software reset on this page, then the fieldbus coupler/controller
starts with the configurations previously loaded into the EEPROM and the
connection to the browser is interrupted.
If you changed the IP address previously, you have to use the changed IP address
to access the device from the browser.
You have have not changed the IP address and performed other settings, you can
restor the connection by refreshing the browser.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Figure 49: WBM page "Security"
Manual
Version 1.1.0
Table of Contents
111
112
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 28: WBM page "Security"
Webserver Security
Entry
Default
Webserver authentification
enabled

Webserver and FTP User configuration *)
Entry
Default
User
guest
Password
guest
Confirm password
*) The following default groups exist:
Description
Enable password protection to access the Web
 interface
Disable password protection to access the
 Web interface
Description
Select admin, guest or user
Enter password
Enter password again to confirm
User: admin
User: guest
User: user
Password: wago
Password: guest
Password: user
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
9.8
Table of Contents
113
Features
Use the "Features" HTML page to enable or disable additional functions.
Figure 50: WBM page "Features"
Table 29: WBM page "Features"
Additional functions
Entry
Default
Manual
Version 1.1.0
Autoreset on
system error

BootP Request
before Static-IP

Description
enables an automatic software reset to be conducted
 when a system error occurs
disables an automatic software reset to be conducted
 when a system error occurs
Automatically set the static IP address enabled.
this configuration, the fieldbus coupler/
 For
controller uses a statically configured IP address if the
request via BootP fails.
Automatically set the static IP address disabled.
 For this configuration, the IP address request via BootP
is repeated in the event of error.
114
9.9
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
I/O Config
Click the link "I/O config" to view the configuration and/or write access
privileges for the outputs of your fieldbus node.
The node structure created using the "WAGO-I/O-PRO CAA I/O Configurator"
hardware configuration tool is displayed in the window. If no modules are shown
in this window, no hardware configuration and, thus, no allocation of write access
privileges have been assigned. In this case, the handling defined at the Web site
"PLC" by the function "I/O configuration - Compatible handling for eaconfig.xml" will be applied to assign the write privileges for all outputs either to
the standard fieldbus, or to the PLC.
Figure 51: WBM page "IO config"
Information
Additional Information
For more detailed information about the WAGO-I/O-PRO CAA I/O Configurator,
refer to the Section "Startup of Fieldbus Node".
Table 30: WBM page "I/O configuration"
Configuration details
Entry
Value (Example)
Number of modules on terminalbus 5
Number of modules in I/O
5
configuration
Description
Number of I/O modules (hardware)
Number of I/O modules in the hardware
configuration of the I/O Configurator (see
the following note)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
10
Diagnostics
10.1
LED Signaling
Table of Contents
For on-site diagnostics, the fieldbus coupler has several LEDs that indicate the
operational status of the coupler or the entire node (see following figure).
ETHERNET
LINK 1
ACT
LINK 2
ACT
MS
NS
I/O
Figure 52: Display Elements
The diagnostics displays and their significance are explained in detail in the
following chapter.
The LEDs are assigned in groups to the various diagnostics areas:
Table 31: LED assignment for diagnostics
Diagnostics area
LEDs
Fieldbus status
Node status
Manual
Version 1.1.0
•
•
•
•
LINK ACT Port 1
LINK ACT Port 2
MS
NS
• I/O
115
116
Table of Contents
10.1.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Evaluating Fieldbus Status
The health of the ETHERNET Fieldbus is signaled through the top LED group
('LINK ACT 1, 2', 'MS', und 'NS').
The two-colored LEDs ‘MS’ (module status) and ‘NS’ (network status) are solely
used by the Ethernet/IP protocol. These two LEDs conform to the Ethernet/IP
specifications.
Table 32: Fieldbus diagnostics – solution in event of error
LED
Meaning
Solution
Status
LINK ACT 1, 2
The fieldbus node is connected to
green
the physical network.
green
The fieldbus node sends and
flashing
receives Ethernet telegrams
The fieldbus node is not
off
1. Check the fieldbus cable.
connected to the physical
network.
MS
green
Normal operation
green
The system is not yet configures
flashing
1. Restart the device by turning the
The system indicates a not
power supply off and on again.
red
remediable error
2. If the error still exists, please
contact the I/O support.
red/green
Self test
flashing
off
No system supply voltage
1. Check the supply voltage.
NS
green
grün
flashing
red
red
flashing
red/green
flashing
off
At least one connection
(MODBUS/TCP or Ethernet/IP)
is developed (also connection to
the Message rout applies)
No connection (MODBUS/TCP
or Ethernet/IP).
The system indicates a double IPaddress in the network
At least one connection
(MODBUS/TCP or Ethernet/IP)
announced a Timeout, where the
controller functions as target.
-
1. Use an IP address that is not used
yet.
1. Restart the device by turning the
power supply off and on again.
2. Develop a new connection.
Self test
-
No IP address is assigned to the
system.
1. Assign to the system an IP address
for example by BootP or DHCP.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
10.1.2
Table of Contents
117
Evaluating Node Status - I/O LED (Blink Code Table)
The communication status between fieldbus coupler/controller is indicated by the
I/O LED.
Table 33: Node status diagnostics – solution in event of error
LED Status Meaning
Solution
I/O
green
The fieldbus node is operating correctly.
Normal operation.
orange
The internal data bus is initialized, 1-2 seflashing
conds of rapid flashing indicate start-up.
red
Controller hardware defect
Replace the fieldbus coupler/controller.
red
General internal bus error
Note the following blinking sequence.
flashing
Evaluate the blinking sequences based
Up to three successive blinking
red
on the following blink code table.
sequences indicate internal data bus
cyclical
The blinking indicates an error message
errors. There are short intervals between
flashing
comprised of an error code and error
the sequences.
argument.
No data cycle on the internal bus.
The fieldbus coupler/controller supply
off
is off.
Device boot-up occurs after turning on the power supply. The I/O LED is orange.
After a trouble-free start-up, the I/O LED is green.
In the event of an error, the I/O LED continues to blink red. Blink codes indicate
detailed error messages. An error is indicated cyclically by up to 3 blinking
sequences.
After elimination of the error, restart the node by turning the power supply of the
device off and on again.
Manual
Version 1.1.0
118
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Switching on
the power supply
Start-up
‘I/O’ LED is blinking (red)
Test o.k.?
No
Yes
‘I/O’ LED
1st flash sequence (red)
(Introduction of the error indication)
1st break
‘I/O’ LED
2nd flash sequence (red)
Error code
(Number of flash cycles)
2nd break
‘I/O’-LED is shining (green)
‘I/O’ LED
3rd flash sequence (red)
Error argument
(Number of flash cycles)
ready for operation
Figure 53: Node status - I/O LED signaling
1st flash sequence
Break
2nd flash sequence
Break
3rd flash sequence
(ca. 10 Hz)
(ca. 1 Hz)
(Introduction of the
error indication)
Error code x
Error argument y
(x = Number of flash cycles)
(y = Number of flash cycles)
(ca. 1 Hz)
Figure 54: Error message coding
Example of a module error:
•
The I/O LED starts the error display with the first blinking sequence
(approx. 10 Hz).
•
After the first break, the second blinking sequence starts (approx. 1 Hz):
The I/O LED blinks four times.
Error code 4 indicates "data error internal data bus".
•
After the second break, the third blinking sequence starts (approx. 1 Hz):
The I/O LED blinks twelve times.
Error argument 12 means that the internal data bus is interrupted behind the
twelfth I/O module.
The thirteenth I/O module is either defective or has been pulled out of the
assembly.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
119
Table 34: Blink code- table for the 'I/O' LED signaling, error code 1
Error code 1: "Hardware and configuration error"
Error
Error Description
Solution
Argument
Overflow of the
internal buffer
memory for the
attached I/O
modules.
1. Turn off the power for the node.
2. Reduce the number of I/O modules and turn the power
supply on again.
3. If the error persists, replace the fieldbus coupler.
2
I/O module(s) with
unknown data type
1. Determine the faulty I/O module by first turning off the
power supply..
2. Plug the end module into the middle of the node.
3. Turn the power supply on again.
4. - LED continues to flash? Turn off the power supply and plug the end module into
the middle of the first half of the node (toward the
fieldbus controller).
- LED not flashing? Turn off the power and plug the end module into the
middle of the second half of the node (away from the
fieldbus controller).
5. Turn the power supply on again.
6. Repeat the procedure described in step 4 while halving
the step size until the faulty I/O module is detected.
7. Replace the faulty I/O module.
8. Inquire about a firmware update for the fieldbus coupler.
3
Invalid check sum in 1. Turn off the power supply for the node.
the parameter area of 2. Replace the fieldbus coupler and turn the power supply
the fieldbus coupler.
on again.
4
1. Turn off the power supply for the node.
Fault when writing in
2. Replace the fieldbus coupler and turn the power supply
the serial EEPROM.
on again.
5
Fault when reading
the serial EEPROM
6
The I/O module
configuration after
AUTORESET
differs from the
1. Restart the fieldbus coupler by turning the power supply
configuration
off and on.
determined the last
time the fieldbus
coupler was powered
up.
7
Invalid hardwarefirmware
combination.
1
Manual
Version 1.1.0
1. Turn off the power supply for the node.
2. Replace the fieldbus coupler and turn the power supply
on again.
1. Turn off the power supply for the node.
2. Replace the fieldbus coupler and turn the power supply
on again.
120
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 34: Blink code- table for the 'I/O' LED signaling, error code 1
Error code 1: "Hardware and configuration error"
Error
Error Description
Solution
Argument
8
Timeout during
serial EEPROM
access.
1. Turn off the power supply for the node.
2. Replace the fieldbus coupler and turn the power supply
on again.
9
Bus controller
initialization error
1. Turn off the power supply for the node.
2. Replace the fieldbus coupler and turn the power supply
on again.
10 ... 13
14
not used
Maximum number of 1. Turn off the power for the node.
gateway or mailbox 2. Reduce the number of corresponding modules to a valid
modules exceeded
number.
Table 35: Blink code table for the 'I/O' LED signaling, error code 2
Error code 2: -not usedError
Error Description
Solution
Argument
-
Not used
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
121
Table 36: Blink code table for the 'I/O' LED signaling, error code 3
Error code 3: "Protocol error, internal bus"
Error
Error Description
Solution
Argument
- Are passive power supply modules (750-613) located in the
node? 1. Check that these modules are supplied correctly with
power.
2. Determine this by the state of the associated status LEDs.
-
Manual
Version 1.1.0
Internal data bus
communication is
faulty, defective
module cannot be
identified.
- Are all modules connected correctly or are there any 750613 Modules in the node? 1. Determine the faulty I/O module by turning off the power
supply..
2. Plug the end module into the middle of the node.
3. Turn the power supply on again.
4. - LED continues to flash? Turn off the power supply and plug the end module into
the middle of the first half of the node (toward the
fieldbus coupler).
- LED not flashing? Turn off the power and plug the end module into the
middle of the second half of the node (away from the
fieldbus coupler).
5. Turn the power supply on again.
6. Repeat the procedure described in step 4 while halving
the step size until the faulty I/O module is detected.
7. Replace the faulty I/O module.
8. Inquire about a firmware update for the fieldbus coupler.
122
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 37: Blink code table for the 'I/O' LED signaling, error code 4
Error code 4: "Physical error, internal bus"
Error
Error Description
Solution
Argument
1. Turn off the power supply to the node.
2. Plug in an end module behind the fieldbus coupler.
3. Turn the power supply on.
4. Observe the error argument signaled.
- Is no error argument indicated by the I/O LED? 5. Replace the fieldbus coupler.
- Is an error argument indicated by the I/O LED? 5. Identify the faulty I/O module by turning off the power
supply.
6. Plug the end module into the middle of the node.
Internal bus data
7. Turn the power supply on again.
transmission error or
8. - LED continues to flash? interruption of the
Turn off the power and plug the end module into the
internal data bus at
middle of the first half of the node (toward the fieldbus
the fieldbus coupler
coupler).
- LED not flashing? Turn off the power and plug the end module into the
middle of the second half of the node (away from the
fieldbus coupler).
9. Turn the power supply on again.
10. Repeat the procedure described in step 6 while halving
the step size until the faulty I/O module is detected.
11. Replace the faulty I/O module.
12. If there is only one I/O module on the fieldbus coupler
and the LED is flashing, either the I/O module or fieldbus
coupler is defective. Replace the defective component.
Interruption of the
internal data bus
1. Turn off the power supply to the node.
2. Replace the (n+1) I/O module containing process data.
behind the nth bus
n*
module with process 3. Turn the power supply on.
data
* The number of light pulses (n) indicates the position of the I/O module.
I/O modules without data are not counted (e.g., supply modules without diagnostics)
Table 38: Blink code table for the 'I/O' LED signaling, error code 5
Error code 5: "Initialization error, internal bus"
Error
Error Description
Solution
Argument
Error in register
1. Turn off the power supply to the node.
communication
2. Replace the (n+1) I/O module containing process data.
n*
during internal bus
3. Turn the power supply on.
initialization
* The number of light pulses (n) indicates the position of the I/O module.
I/O modules without data are not counted (e.g., supply modules without diagnostics)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
123
Table 39: Blink code- table for the I/O LED signaling, error code 6
Error code 6: "Fieldbus specific errors"
Error
Error description
Solution
Argument
1. Turn off the power supply of the node.
Invalid MACID
2. Exchange fieldbus coupler.
1
3. Turn the power supply on again.
1. Restart the fieldbus coupler by turning the power
Ethernet Hardware
supply off and on again.
2
initialization error
2. If the error still exists, exchange the fieldbus coupler.
1. Restart the fieldbus coupler by turning the power
TCP/IP initialization
supply off and on again.
3
error
2. If the error still exists, exchange the bus coupler.
Network configuration 1. Check the settings of BootP server.
4
error (no IP Address)
1. Restart the fieldbus coupler by turning the power
Application protocol
supply off and on again.
5
initialization error
2. If the error still exists, exchange the bus coupler.
Process image is too
1. Turn off the power supply of the node.
6
large
2. Reduce number of I/O modules
1. Change configuration. Use another IP address, which is
Double IP address in
not yet present in network.
7
network
2. Restart the fieldbus coupler by turning the power
supply off and on again.
1. Turn off the power supply of the node.
2. Reduce number of I/O modules
Error when building
3. Restart the fieldbus coupler by turning the power
8
the process image
supply off and on again.
4. If the error still exists, exchange the bus coupler.
9
Manual
Version 1.1.0
Error with mapping
between bus modules
and fieldbus
1. Check EA-Config.xml file on the fieldbus coupler
124
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
10.2
Fault Behavior
10.2.1
Loss of Fieldbus
A fieldbus and, hence, a link failure is recognized when the set reaction time for
the watchdog expires without initiation by the higher-order control system. This
may occur, for example, when the Master is switched off, or when there is a
disruption in the bus cable. An error at the Master can also result in a fieldbus
failure. No connection via ETHERNET.
The MODBUS watchdog monitors the ongoing MODBUS communication via
MODBUS protocol. A fieldbus failure is signaled by the red "I/O" LED lighting
up, provided the MODBUS watchdog has been configured and activated.
Fieldbus monitoring independently of a certain protocol is possible using the
function block 'FBUS_ERROR_INFORMATION' in the library "Mod_com.lib".
This checks the physical connection between modules and the controller and
assumes evaluation of the watchdog register in the control system program. The
I/O bus remains operational and the process images are retained. The control
system program can also be processed independently.
FBUS_ERROR_INFORMATION
FBUS_ERROR
ERROR
Figure 55: Function block for determining loss of fieldbus, independently of protocol
'FBUS_ERROR' (BOOL)
= FALSE
= TRUE
= no fault
= loss of field bus
'ERROR' (WORD)
=0
=1
= no fault
= loss of field bus
The node can be put into a safe status in the event of a fieldbus failure with the aid
of these function block outputs and an appropriately programmed control system
program.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
125
Information
Loss of fieldbus detection through MODBUS protocol:
For detailed information about the watchdog register, refer to Section "MODBUS
Functions", in particular Section "Watchdog (Fieldbus failure)".
Protocol-independent detection of loss of fieldbus:
The library 'Mod_com.lib' with function block
'FBUS_ERROR_INFORMATION' is normally included in the setup for the
WAGO-I/O-PRO CAA. You can integrate the library via register "Resources" at
the bottom on the left of the workspace. Click Insert and then Other libraries.
The Mod_com.lib is located in folder C:\Programme\ WAGO Software\CoDeSys
V2.3\Targets\WAGO\Libraries\32_Bit
10.2.2
Internal Data Bus Failure
'I/O' LED indicates an internal bus failure.
• 'I/O' LED flashed red:
When an internal data bus failure occurs, the fieldbus coupler generates an error
message (error code and error argument).
An internal data bus failure occurs, for example, if an I/O module is removed.
If the error occurs during operation, the output modules operate as they do during
an internal data bus stop.
If the internal data bus error is resolved, the coupler starts up after turning the
power off and on similar to that of a normal start-up. The process data is
transmitted again and the outputs of the node are set accordingly.
If the 'KBUS_ERROR_INFORMATION' function block is evaluated in the
control program, then the 'ERROR','BITLEN', 'TERMINALS' and
'FAILADDRESS' output values are relevant.
'ERROR'
= FALSE
('BITLEN'
'TERMINALS'
= No fault
= Bit length of the internal bus shift register
= Number of I/O modules)
'ERROR'
= TRUE
('BITLEN'
'TERMINALS'
'FAILADRESS'
= Internal Bus Error
=0
= 0)
= Position of the I/O module after which the
internal bus interruption arose, similar to the
flashed error argument of the I/O LED
Manual
Version 1.1.0
126
Table of Contents
11
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Fieldbus Communication
Fieldbus communication between master application and a WAGO fieldbus
coupler/controller based on the ETHERNET standard normally occurs via an
implemented fieldbus-specific application protocol.
Depending on the application, this can be e.g., MODBUS/TCP (UDP),
EtherNet/IP, BACnet/IP, KNXnet/IP, PROFINET, SERCOS III or other.
In addition to the ETHERNET standard and the fieldbus-specific application
protocol, there are also other communications protocols important for reliable
communication and data transmission and other related protocols for configuring
and diagnosing the system implemented in the WAGO fieldbus coupler/controller
based on ETHERNET.
These protocols are explained in more detail in the other sections.
11.1
Implemented Protocols
11.1.1
Communication Protocols
11.1.1.1
IP (Internet Protocol)
The Internet protocol divides datagrams into segments and is responsible for their
transmission from one network subscriber to another. The stations involved may
be connected to the same network or to different physical networks which are
linked together by routers.
Routers are able to select various paths (network transmission paths) through
connected networks, and bypass congestion and individual network failures.
However, as individual paths may be selected which are shorter than other paths,
datagrams may overtake each other, causing the sequence of the data packets to be
incorrect.
Therefore, it is necessary to use a higher-level protocol, for example, TCP to
guarantee correct transmission.
IP Packet
In addition to the data units to be transported, the IP data packets contain a range
of address information and additional information in the packet header.
Table 40: IP Packet
IP Header
IP Data
The most important information in the IP header is the IP address of the
transmitter and the receiver and the transport protocol used.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
127
IP Addresses
To allow communication over the network each fieldbus node requires a 32 bit
Internet address (IP address).
Note
IP Address must be unique!
For error free operation, the IP address must be unique within the network.
As shown below there are various address classes with net identification (net ID)
and subscriber identification (subscriber ID) of varying lengths. The net ID
defines the network in which the subscriber is located. The subscriber ID
identifies a particular subscriber within this network.
Networks are divided into various network classes for addressing purposes:
• Class A: (Net ID: Byte 1, Host ID: Byte 2… Byte 4)
Table 41: Network Class A
e. g.
101 .
16
.
232
.
22
01100101
00010000
11101000
00010110
Net ID
Host ID
0
The highest bit in Class A networks is always ‘0’. This means the highest byte can
be in a range of’0 0000000’ to ‘0 1111111’.
Therefore, the address range of a Class A network in the first byte is always
between 0 and 127.
• Class B: (Net ID: Byte 1 … Byte 2, Host ID: Byte 3… Byte 4)
Table 42: Network Class B
e. g.
181
10110101
.
16
.
232
.
22
00010000
11101000
00010110
Net ID
Host ID
10
The highest bits in Class B networks are always ’10’. This means the highest byte
can be in a range of’10 000000’ to ‘10 111111’.
Therefore, the address range of Class B networks in the first byte is always
between 128 and 191.
• Class C: (Net ID: Byte 1 … Byte 3, Host ID: Byte 4)
Table 43: Network Class C
e. g.
16
.
232
.
22
00010000
11101000
00010110
Net ID
Host ID
110
The highest bits in Class C networks are always ‘110’. This means the highest
byte can be in a range of’110 00000’ to ‘110 11111’.
Manual
Version 1.1.0
201
11000101
.
128
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Therefore, the address range of Class C networks in the first byte is always
between 192 and 223.
• Additional network classes (D, E): are only used for special tasks.
Key Data
Table 44: Key Data Class A, B and C
Network Class
Class A
Class B
Class C
Address range of
the subnetwork
Possible number of
Networks
Hosts per
Network
1.XXX.XXX.XXX ...
127
126.XXX.XXX.XXX
(27)
128.000.XXX.XXX ... Approx. 16 Thousand
191.255.XXX.XXX
(214)
192.000.000.XXX ...
Approx. 2 Million
223.255.255.XXX
(221)
Approx. 16 Million
(224)
Ca. 65 Thousand
(216)
254
(28)
Each WAGO ETHERNET fieldbus coupler or controller can be easily assigned an
IP address via the implemented BootP protocol. For small internal networks we
recommend selecting a network address from Class C.
Note
Do not set IP addresses to 0.0.0.0 or 255.255.255.255!
Never set all bits to equal 0 or 1 in one byte (byte = 0 or 255). These are reserved
for special functions and may not be allocated. Therefore, the address 10.0.10.10
may not be used due to the 0 in the second byte.
If a network is to be directly connected to the Internet, only registered,
internationally unique IP addresses allocated by a central registration service may
be used. These are available from InterNIC (International Network Information
Center).
Note
Internet access only by the authorized network administrator!
Direct connection to the Internet should only be performed by an authorized
network administrator and is therefore not described in this manual.
Subnets
To allow routing within large networks a convention was introduced in the
specification RFC 950. Part of the Internet address, the subscriber ID is divided
up again into a subnetwork number and the station number of the node. With the
aid of the network number it is possible to branch into internal subnetworks
within the partial network, but the entire network is physically connected together.
The size and position of the subnetwork ID are not defined; however, the size is
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
129
dependent upon the number of subnets to be addressed and the number of
subscribers per subnet.
Table 45: Class B Address with Field for Subnet IDs
1
1 0
8
...
16
Network ID
24
Subnet ID
32
Host ID
Subnet Mask
A subnet mask was introduced to encode the subnets in the Internet. This involves
a bit mask, which is used to mask out or select specific bits of the IP address. The
mask defines the subscriber ID bits used for subnet coding, which denote the ID
of the subscriber. The entire IP address range theoretically lies between 0.0.0.0
and 255.255.255.255. Each 0 and 255 from the IP address range are reserved for
the subnet mask.
The standard masks depending upon the respective network class are as follows:
•
Class A Subnet mask:
Table 46: Subnet mask for Class A network
255
•
.0
.0
.0
.0
.0
.255
.0
Class B Subnet mask:
Table 47: Subnet mask for Class B network
255
•
.255
Class C Subnet mask:
Table 48: Subnet mask for Class C network
255
.255
Depending on the subnet division the subnet masks may, however, contain other
values beyond 0 and 255, such as 255.255.255.128 or 255.255.255.248.
Your network administrator allocates the subnet mask number to you.
Together with the IP address, this number determines which network your PC and
your node belongs to.
The recipient node, which is located on a subnet initially, calculates the correct
network number from its own IP address and the subnet mask.
Only then does it check the node number and delivers the entire packet frame, if it
corresponds.
Table 49: Example for an IP address from a Class B network
172.16.233.200
10101100 00010000 11101001 11001000
IP address
255.255.255.128
11111111 11111111 11111111 10000000
Subnet mask
172.16.0.0
10101100 00010000 00000000 00000000
Net ID
0.0.233.128
00000000 00000000 11101001 10000000
Subnet ID
0.0.0.72
00000000 00000000 00000000 01001000
Host ID
Manual
Version 1.1.0
130
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Note
Specification of the network mask necessarily!
Specify the network mask defined by the administrator in the same way as the IP
address when installing the network protocol.
Gateway
The subnets of the Internet are normally connected via gateways. The function of
these gateways is to forward packets to other networks or subnets.
This means that in addition to the IP address and network mask for each network
card, it is necessary to specify the correct IP address of the standard gateway for a
PC or fieldbus node connected to the Internet. You should also be able to obtain
this IP address from your network administrator.
The IP function is limited to the local subnet if this address is not specified.
RAW IP
Raw IP manages without protocols such as PPP (point-to-point protocol). With
RAW IP, the TCP/IP packets are directly exchanged without handshaking, thus
enabling the connection to be established more quickly.
However, the connection must beforehand have been configured with a fixed IP
address. The advantages of RAW IP are high data transfer rate and good stability.
IP Multicast
Multicast refers to a method of transmission from a point to a group, which is a
point-to-multipoint transfer or multipoint connection. The advantage of multicast
is that messages are simultaneously transferred to several users or closed user
groups via one address.
IP multicasting at the Internet level is realized with the help of the Internet Group
Message Protocol IGMP; neighboring routers use this protocol to inform each
other on membership to the group.
For distribution of multicast packets in the sub-network, IP assumes that the
datalink layer supports multicasting. In the case of Ethernet, you can provide a
packet with a multicast address in order to send the packet to several recipients
with a single send operation. Here, the common medium enables packets to be
sent simultaneously to several recipients. The stations do not have to inform each
other on who belongs to a specific multicast address – every station physically
receives every packet. The resolution of IP address to Ethernet address is solved
by the use of algorithms, IP multicast addresses are embedded in Ethernet
multicast addresses.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.1.1.2
Table of Contents
131
TCP (Transmission Control Protocol)
As the layer above the Internet protocol, TCP (Transmission Control Protocol)
guarantees the secure transport of data through the network.
TCP enables two subscribers to establish a connection for the duration of the data
transmission. Communication takes place in full-duplex mode (i.e., transmission
between two subscribers in both directions simultaneously).
TCP provides the transmitted message with a 16-bit checksum and each data
packet with a sequence number.
The receiver checks that the packet has been correctly received on the basis of the
checksum and then sets off the sequence number. The result is known as the
acknowledgement number and is returned with the next self-sent packet as an
acknowledgement.
This ensures that the lost TCP packets are detected and resent, if necessary, in the
correct sequence.
TCP Data Packet
The packet header of a TCP data packet is comprised of at least 20 bytes and
contains, among others, the application port number of the transmitter and the
receiver, the sequence number and the acknowledgement number.
The resulting TCP packet is used in the data unit area of an IP packet to create a
TCP/IP packet.
TCP Port Numbers
11.1.1.3
TCP can, in addition to the IP address (network and subscriber address), respond
to a specific application (service) on the addressed subscriber. For this the
applications located on a subscriber, such as a web server, FTP server and others
are addressed via different port numbers. Well-known applications are assigned
fixed ports to which each application can refer when a connection is built up
(Examples: Telnet Port number: 23, http Port number: 80).
A complete list of "standardized services" is contained in the RFC 1700 (1994)
specifications.
UDP (User Datagram Protocol)
The UDP protocol, like the TCP protocol, is responsible for the transport of data.
Unlike the TCP protocol, UDP is not connection-orientated; meaning that there
are no control mechanisms for the data exchange between transmitter and
receiver. The advantage of this protocol is the efficiency of the transmitted data
and the resulting higher processing speed.
Manual
Version 1.1.0
132
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.1.2
Configuration and Diagnostics Protocols
11.1.2.1
BootP (Bootstrap Protocol)
The "Bootstrap Protocol" (BootP) can be used to assign an IP address and other
parameters to the fieldbus coupler/controller in a TCP/IP network. Subnet masks
and gateways can also be transferred using this protocol. Protocol communication
is comprised of a client request from the fieldbus coupler or controller and a
server response from the PC.
A broadcast request is transmitted to Port 67 (BootP server) via the protocol that
contains the hardware address (MAC ID) for the fieldbus coupler or controller.
The BootP server then receives this message. The server contains a database in
which the MAC ID and IP addresses are assigned to one another. When a MAC
address is found a broadcast reply is transmitted via the network.
The fieldbus coupler/controller "listens" at the specified Port 68 for a response
from the BootP server. Incoming packets contain information such as the IP
address and the MAC address for the fieldbus coupler/controller. A fieldbus
coupler/controller recognizes by the MAC address that the message is intended
for that particular fieldbus coupler/controller and accepts the transmitted IP
address into its network.
Note
IP addresses can be assigned via BootP under Windows and Linux!
You can use WAGO-BootP-Server to assign an IP address under the Windows
and Linux operating systems. You can also use any other BootP server besides
WAGO-BootP-Server. You can also use any other BootP server besides the
WAGO-BootP-Server.
Information
More information about WAGO-BootP-Server
The process for assigning addresses using WAGO-BootP-Server is described in
detail in the section "Commissioning Fieldbus Node".
The BootP Client assists in the dynamic configuration of the network parameters:
The ETHERNET TCP/IP fieldbus controller has a BootP client that supports the
following options in addition to the default "IP address" option:
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
133
Table 50: BootP options
Option
Meaning
[OPT1] Subnet mask
32-bit address mask that displays which bits of the IP address
identify the network and which identify the network stations.
Time difference between the local time and the UTC (Universal
Time Coordinated).
IP address of the router that permits access to other networks.
IP address of the name servers that converts a name into an IP
address. Up to 2 DNS servers can be configured.
The name of the host is the unique name of a computer in a
network. The host name can contain up to 32 characters.
The name of the domain is the unique name of a network. The
domain name can contain up to 32 characters.
IP address of the Network Time Server. When assigning an NTP
server, the SNTP client is automatically enabled in the coupler.
[OPT2] Time zone
[OPT3] Gateway
[OPT6] DNS server
[OPT12] Host name
[OPT15] Domain name
[OPT42] NTP server
The "Features" WBM page can also be used to select the "BootP Request before
static IP" option. After the restart, 5 BootP queries are sent. If there is no response
to any of these queries, the fieldbus coupler/controller tries to configure itself with
the IP parameters saved in the EEPROM.
The network parameters (IP address, etc.) are stored in the EEPROM when using
the Bootstrap protocol to configure the node.
Note
BootP configuration is saved in the EEPROM!
Please note that the network configuration is stored in the EEPROM when using
BootP in contrast to configuration via DHCP.
By default, BootP is activated in the fieldbus coupler/controller.
When BootP is activated, the fieldbus coupler/controller expects the BootP server
to be permanently available.
If there is no BootP server available after a PowerOn reset, the network will
remain inactive.
To operate the fieldbus coupler/controller with the IP configuration stored in the
EEPROM, you must deactivate the BootP protocol after configuration.
The Web-based management system is used to deactivate the BootP protocol on
the respective fieldbus coupler/controller-internal HTML page under the "Port"
link.
If BootP is deactivated, the fieldbus coupler/controller uses the parameters saved
in the EEPROM when booting next.
If there is an error in the saved parameters, the I/O LED reports a blink code and
configuration via BootP is turned on automatically.
Manual
Version 1.1.0
134
Table of Contents
11.1.2.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
DHCP (Dynamic Host Configuration Protocol)
The fieldbus coupler/controller internal HTML page opened via the "Port" link
provides the option to configure the network using the data saved in the EEPROM
or via DHCP instead of via the BootP protocol.
DHCP (Dynamic Host Configuration Protocol) is a further development of BootP
and is backwards compatible with BootP.
Both BOOTP and DHCP assign an IP address to the fieldbus node (Client) when
starting; the sequence is the same as for BootP.
For configuration of the network parameters via DHCP, the fieldbus
coupler/controller sends a client request to the DHCP server e.g., on the connected
PC.
A broadcast request is transmitted to Port 67 (DHCP server) via the protocol that
contains the hardware address (MAC ID) for the fieldbus coupler/controller.
The DHCP server then receives this message. The server contains a database in
which the MAC ID and IP addresses are assigned to one another. When a MAC
address is found a broadcast reply is transmitted via the network.
The fieldbus coupler/controller "listens" at the specified Port 68 for a response
from the DHCP server. Incoming packets contain information such as the IP
address and the MAC address for the fieldbus coupler/controller. A fieldbus
coupler/controller recognizes by the MAC address that the message is intended
for that particular fieldbus coupler/controller and accepts the transmitted IP
address into its network.
If there is no reply, the inquiry is sent again after 4 seconds, 8 seconds and 16
seconds.
If all inquiries receive no reply, a blink code is reported via the I/O LED. The
parameters cannot be applied from the EEPROM.
Note
DHCP configuration is not saved in the EEPROM!
Please note that the network configuration is not stored in the EEPROM when
using DHCP in contrast to configuration via BootP.
The difference between BOOTP and DHCP is that both use different assignment
methods and that configuration with DHCP is time limited. The DHCP client
always has to update the configuration after the time has elapsed. Normally, the
same parameters are continuously confirmed by the server.
The difference between BOOTP and DHCP is that both use different assignment
methods. BOOTP can be used to assign a fixed IP address for each client where
the addresses and their reservation are permanently saved in the BOOTP server
database.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
135
Because of this time dependency, DHCP is also used to dynamically assign
available IP addresses through client leases (lease time after which the client
requests a new address) where each DHCP client address is saved temporarily in
the server database.
In addition, DHCP clients do not require a system restart to rebind or renew
configuration with the DHCP server. Instead, clients automatically enter a
rebinding state at set timed intervals to renew their leased address allocation with
the DHCP server. This process occurs in the background and is transparent to the
user.
There are three different operating modes for a DHCP server:
•
Manual assignment
In this mode, the IP addresses are permanently assigned on the DHCP server
to specific MAC addresses. The addresses are assigned to the MAC address
for an indefinite period.
Manual assignments are used primarily to ensure that the DHCP client can
be reached under a fixed IP address.
•
Automatic assignment
For automatic assignment, a range of IP addresses is assigned on the DHCP
server.
If the address was assigned from this range once to a DHCP client, then it
belongs to the client for an indefinite period as the assigned IP address is
also bound to the MAC address.
•
Dynamic assignment
This process is similar to automatic assignment, but the DHCP server has a
statement in its configuration file that specifies how long a certain IP
address may be "leased" to a client before the client must log into the server
again and request an "extension".
If the client does not log in, the address is released and can be reassigned to
another (or the same) client. The time defined by the administrator is called
Lease Time.
Some DHCP servers also assign IP addresses based on the MAC address,
i.e., a client receives the same IP address as before after longer network
absence and elapse of the Lease Time (unless the IP address has been
assigned otherwise in the mean time).
DHCP is used to dynamically configure the network parameters.
The ETHERNET TCP/IP fieldbus controller has a DHCP client that supports the
following options in addition to the default "IP address" option:
Manual
Version 1.1.0
136
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 51: Meaning of DHCP options
Option
Meaning
[OPT1] Subnet mask
32-bit address mask that displays which bits of the IP address
identify the network and which identify the network stations.
[OPT2] Time zone
Time difference between the local time and the UTC (Universal
Time Coordinated).
[OPT3] Gateway
IP address of the router that permits access to other networks.
[OPT6] DNS server
IP address of the name servers that converts a name into an IP
address. Up to 2 DNS servers can be configured.
[OPT15] Domain name *)
The name of the domain is the unique name of a network. The
domain name can contain up to 32 characters.
IP address of the Network Time Server. When assigning an NTP
server, the SNTP client is automatically enabled in the coupler.
[OPT42] NTP server
The maximum duration (i.e., how long the fieldbus
coupler/controller maintains the assigned IP address) can be
defined here. The maximum lease time for the fieldbus controller
is 48 days. This is due to the internal timer resolution.
[OPT51] Lease time
The renewing time indicates when the fieldbus coupler/controller
must renew the lease time. The rebinding time should be
approximately 7/8 of the lease time.
[OPT58] Renewing time
The rebinding time indicates after what amount of time the
fieldbus coupler/controller must have received its new address.
[OPT59] Rebinding time
The renewing time should be approximately half of the lease
time.
)
* In contrast to BootP, the DHCP client does not support assignment of the host name.
11.1.2.3
HTTP (Hypertext Transfer Protocol)
HTTP is a protocol used by WWW (World Wide Web) servers for the forwarding
of hypermedia, texts, images, audiodata, etc.
Today, HTTP forms the basis of the Internet and is also based on requests and
responses in the same way as the BootP protocol.
The HTTP server implemented in the (programmable) fieldbus coupler or
controller is used for viewing the HTML pages saved in the coupler/controller.
The HTML pages provide information about the coupler/controller (state,
configuration), the network and the process image.
On some HTML pages, (programmable) fieldbus coupler or controller settings
can also be defined and altered via the web-based management system (e.g.
whether IP configuration of the coupler/controller is to be performed via the
DHCP protocol, the BootP protocol or from the data stored in the EEPROM).
The HTTP server uses port number 80.
11.1.2.4
DNS (Domain Name Systems)
The DNS client enables conversion of logical Internet names such as
www.wago.com into the appropriate decimal IP address represented with
separator stops, via a DNS server. Reverse conversion is also possible.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
137
The addresses of the DNS server are configured via DHCP, BootP or web-based
management. Up to 2 DNS servers can be specified. The host identification can be
achieved with two functions, an internal host table is not supported.
11.1.2.5
FTP-Server (File Transfer Protocol)
The file transfer protocol (FTP) enables files to be exchanged between different
network stations regardless of operating system.
In the case of the ETHERNET coupler/controller, FTP is used to store and read
the HTML pages created by the user, the IEC61131 program and the IEC61131
source code in the (programmable) fieldbus coupler or controller.
A total memory of 2 MB is available for the file system.
Note
Cycles for flash limited to 1 million!
Up to 1 million write cycles per sector are allowed when writing the flash for the
file system. The file system supports "Wear-Leveling", so that the same sectors
are not always written to.
Information
More Information about the implemented Protocols
You can find a list of the exact available implemented protocols in the chapter
"Technical Data" to the fieldbus coupler and/or controller.
11.1.2.6
SNMP (Simple Network Management Protocol)
The Simple Network Management Protocol (SNMP) is responsible for
transporting the control data that allows the exchange of management information
as well as status and statistic data between individual network components and a
management system.
An SNMP management workstation polls the SNMP agents to obtain information
on the relevant devices.
SNMP is supported in versions 1/2c and some fieldbus couplers/controllers in
version 3.
This represents a community message exchange in SNMP versions 1 and 2c. The
community name of the network community must thereby be specified.
In SNMP version 3, exchanging messages is user-related. Each device, that knows
the passwords set via WBM, may read or write values from the controller. In
SNMPv3, user data from SNMP messages can also be transmitted in encoded
Manual
Version 1.1.0
138
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
form. This way, both requested values and values to be written cannot be easily
decoded by others via ETHERNET. This is why SNMPv3 is often used in safetyrelated networks.
The device data, that can be accessed or modified by an SNMP agent, is called
SNMP object. The sets of SNMP objects are stored in a logical database called
Management Information Base (MIB); this is why these objects are typically
known as "MIB objects".
The SNMP of the ETHERNET controller includes both the general MIB acc. to
RFC1213 (MIB II) and a special WAGO MIB.
SNMP is processed via port 161. The port number for SNMP traps (agent
messages) is 161. Both ports must be enabled to use SNMP.
11.1.2.6.1 MIB II Description
MIB II acc. to RFC1213 is divided into the following groups:
Table 52: MIB II groups
Group
System Group
Interface Group
IP Group
IpRoute Table Group
ICMP Group
TCP Group
UDP Group
SNMP Group
Identifier
1.3.6.1.2.1.1
1.3.6.1.2.1.2
1.3.6.1.2.1.4
1.3.6.1.2.1.4.21
1.3.6.1.2.1.5
1.3.6.1.2.1.6
1.3.6.1.2.1.7
1.3.6.1.2.1.11
Information
Additional Information:
Please find detailed information on these individual groups in section
"MIB II groups" of the manual appendix..
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
139
11.1.2.6.2 Traps
Standard Traps
For specific events, the SNMP agent will independently send one of the following
messages without polling the manager.
Note
Enable event messages (traps) in the WBM!
Initially enable the event messages in the WBM in menu "SNMP“ under "Trap
Enable“. Traps in version 1, 2c and 3 may be activated separately.
The following messages are triggered automatically as traps (SNMPv1) by the
fieldbus coupler/controller:
Table 53: Standard Traps
TrapType/TrapNumber/
OID of the provided value
TrapType = 0
TrapType = 1
TrapType = 3
TrapType = 4
TrapType = 6/
ab Trap-Nummer 25
benutzerspezifisch
Manual
Version 1.1.0
Name
Event
ColdStart
WarmStart
EthernetUp
AuthenticationFailure
Restart the coupler/controller
Reset via service switch
Network connection detected
Unauthorized (abortive) MIB
access
Enterprise-specific messages and
function poll in the PFC program
starting with enterprise trap number 25
enterpriseSpecific
140
Table of Contents
11.1.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Application Protocols
If fieldbus specific application protocols are implemented, then the appropriate
fieldbus specific communication is possible with the respective coupler/controller.
Thus the user is able to have a simple access from the respective fieldbus on the
fieldbus node.
The implemented fieldbus specific application protocols these protocols are
individual described in the following chapters.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
11.2
MODBUS Functions
11.2.1
General
141
MODBUS is a manufacturer-independent, open fieldbus standard for diverse
applications in manufacturing and process automation.
The MODBUS protocol is implemented according to the current Internet Draft of
the IETF (Internet Engineering Task Force) and performs the following functions:
•
Transmission of the process image
•
Transmission of the fieldbus variables
•
Transmission of different settings and information on the coupler/controller
The data transmission in the fieldside takes place via TCP and via UDP.
The MODBUS/TCP protocol is a variation of the MODBUS protocol, which was
optimized for communication via TCP/IP connections.
This protocol was designed for data exchange in the field level (i.e. for the exchange of I/O data in the process image).
All data packets are sent via a TCP connection with the port number 502.
MODBUS/TCP segment
The general MODBUS/TCP header is as follows:
Table 54: MODBUS/TCP header
Byte
0
1
Identifier
(entered by
receiver)
2
3
Protocolidentifier
(is always 0)
4
5
6
Length field Unit identifier
(High byte, low
(Slave
byte)
address)
7
8…n
MODBUS
function
code
Data
Information
Additional Information
The structure of a datagram is specific for the individual function. Refer to the
descriptions of the MODBUS Function codes.
For the MODBUS protocol 15 connections are made available over TCP. Thus it
allows digital and analog output data to be directly read out at a fieldbus node and
special functions to be executed by way of simple MODBUS function codes from
15 stations simultaneously.
For this purpose a set of MODBUS functions from the Open MODBUS/TCP
specification is realized.
Manual
Version 1.1.0
142
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Information
More information
More information on the “Open MODBUS/TCP specification” you can find in the
Internet: www.modbus.org .
Therefore the MODBUS protocol based essentially on the following basic data
types:
Table 55: Basic data types of MODBUS protocol
Data type
Discrete Inputs
Coils
Input Register
Holding Register
Length
1 Bit
1 Bit
16 Bit
16 Bit
Description
Digital inputs
Digital outputs
Analog input data
Analog output data
For each basic data type one or more function codes are defined.
These functions allow digital or analog input and output data, and internal
variables to be set or directly read out of the fieldbus node.
Table 56: List of the MODBUS Functions in the Fieldbus Coupler
Function code
Function
Access method and description
0x01
Read Coils
Reading of several single input bits
FC1
0x02
Read Input
Reading of several input bits
FC2
Discretes
0x03
Read Multiple Reading of several input registers
FC3
Registers
0x04
Read Input
Reading of several input registers
FC4
Registers
0x05
Write Coil
Writing of an individual output bit
FC5
0x06
Write Single
Writing of an individual output
FC6
Register
register
Get Comm
Communication event counter
FC11 0x0B
Event Counters
Force Multiple Writing of several output bits
FC15 0x0F
Coils
Write Multiple Writing of several output registers
FC16 0x10
Registers
Mask Write
FC22 0x16
Register
Read/Write
Reading and writing of several
FC23 0x17
Registers
output registers
Access to resources
R: Process image
R: Process image
R:
Process image,
internal variables
Process image,
internal variables
Process image
Process image,
internal variables
None
W:
Process image
W:
Process image,
internal variables
Process image
R:
R:
W:
W:
W:
R/W: Process image
To execute a desired function, specify the respective function code and the
address of the selected input or output data.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
143
Note
Note the number system when addressing!
The examples listed use the hexadecimal system (i.e.: 0x000) as their numerical
format. Addressing begins with 0. The format and beginning of the addressing
may vary according to the software and the control system. All addresses then
need to be converted accordingly.
Manual
Version 1.1.0
Table of Contents
Use of the MODBUS Functions
The example below uses a graphical view of a fieldbus node to show which
MODBUS functions can be used to access data of the process image.
DO AO AO
DI DI AI AI DI AI DI DI AI
Ethernet
ON
LINK
TxD/RxD
ERROR
I/O
750-342
11.2.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
W AGO ßI /O ßSY STE M
144
Eingangsklemmen 750- 400 400 467 467 400 467 400 400 467
FC 3 (Read Multiple Registers)
FC 4 (Read Input Registers)
Ausgangsklemmen 750- 501 550 550
FC 6 (Write Single Register)
FC 16 (Write Multiple Registers)
MODBUS-Adressen
1
Word2
Word1
Word2
Word1
Word2
Word2
0x0000
0x0001
0x0002
0x0003
0x0004
0x0005
0x0006
0x0007
Word2
Word1
Word2
MODBUS-Adressen
1
3
Word2
Word1
Word2
0x0000 / 0x0200
0x0001 / 0x0201
0x0002 / 0x0202
0x0003 / 0x0203
0x0004 /
0x0204
Highbyte
Word2
Word1
Word2
Word2
Word1
Word2
Lowbyte
FC 3 (Read Multiple Registers)
FC 4 (Read Input Registers)
3
0x0008
MODBUS-Adressen
Highbyte
Lowbyte
FC 1 (Read Coils)
FC 2 (Read Input Discretes)
1
0x0200
0x0201
0x0202
0x0203
3
0x0204
Word2
Word1
Word2
Word2
Word1
Word2
Highbyte
Lowbyte
MODBUSAdressen
2
0x0000
0x0001
0x0002
0x0003
0x0004
0x0005
0x0006
0x0007
0x0008
0x0009
FC 5 (Write Coil)
FC 15 (Force Multiple Coils)
MODBUS-Adressen
0x0000 / 0x0200
2
0x0001 / 0x0201
FC 1 (Read Coils)
FC 2 (Read Input Discretes)
MODBUS-Adressen
2
0x0200
0x0201
Figure 56: Use of the MODBUS Functions
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
145
Note
Use register functions to access analog signals and coil functions to access
binary signals!
It is recommended that analog data be accessed with register functions  and
digital data with coil functions . If reading or writing access to binary signals is
performed via register functions , an address shift may occur as soon as further
analog modules are operated on the coupler/controller.
11.2.3
Description of the MODBUS Functions
All MODBUS functions are executed as follows:
1.
A MODBUS TCP master (e.g., a PC) makes a request to the WAGO
fieldbus node using a specific function code based on the desired operation..
2.
The WAGO fieldbus node receives the datagram and then responds to the
master with the proper data, which is based on the master’s request.
If the WAGO fieldbus node receives an incorrect request, it sends an error
datagram (Exception) to the master.
The exception code contained in the exception has the following meaning:
Table 57: Exception odes
Exception code
0x01
0x02
0x03
0x04
0x05
0x06
0x08
0x0A
0x0B
Meaning
Illegal function
Illegal data address
Illegal data value
Slave device failure
Acknowledge
Server busy
Memory parity error
Gateway path unavailable
Gateway target device failed to respond
The following chapters describe the datagram architecture of request, response
and exception with examples for each function code.
Manual
Version 1.1.0
146
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Note
Reading and writing of outputs via FC1 to FC4 is also possible by adding an
offset!
In the case of the read functions (FC1 ... FC4) the outputs can be additionally
written and read back by adding an offset of 200hex (0x0200) to the MODBUS
addresses in the range of [0hex ... FFhex] and an offset of 1000hex (0x01000) to the
MODBUS addresses in the range of [6000hex ... 62FChex].
11.2.3.1
Function Code FC1 (Read Coils)
This function reads the status of the input and output bits (coils) in a slave device.
Request
The request specifies the reference number (starting address) and the bit count to
read.
Example: Read output bits 0 to 7.
Table 58: Request of Function code FC1
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Bit count
Example
0x0000
0x0000
0x0006
0x01 not used
0x01
0x0000
0x0008
Response
The current values of the response bits are packed in the data field. A binary 1
corresponds to the ON status and a 0 to the OFF status. The lowest value bit of the
first data byte contains the first bit of the request. The others follow in ascending
order. If the number of inputs is not a multiple of 8, the remaining bits of the last
data byte are filled with zeroes (truncated).
Table 59: Response of Function code FC1
Byte
...
Byte 7
Byte 8
Byte 9
Field name
Example
MODBUS function code
Byte count
Bit values
0x01
0x01
0x12
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
147
The status of the inputs 7 to 0 is shown as byte value 0x12 or binary 0001 0010.
Input 7 is the bit having the highest significance of this byte and input 0 the lowest
value.
The assignment is thus made from 7 to 0 as follows:
Table 60: Assignment of inputs
Bit
Coil
OFF OFF OFF ON
0
0
0
1
7
6
5
4
OFF OFF ON OFF
0
0
1
0
3
2
1
0
Exception
Table 61: Exception of Function code FC1
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x81
0x01 or 0x02
148
Table of Contents
11.2.3.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Function Code FC2 (Read Input Discretes)
This function reads the input bits from a slave device.
Request
The request specifies the reference number (starting address) and the bit count to
be read.
Example: Read input bits 0 to 7
Table 62: Request of Function code FC2
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Bit count
Example
0x0000
0x0000
0x0006
0x01 not used
0x02
0x0000
0x0008
Response
The current value of the requested bits are packed into the data field. A binary 1
corresponds to the ON status and a 0 the OFF status. The lowest value bit of the
first data byte contains the first bit of the inquiry. The others follow in an
ascending order. If the number of inputs is not a multiple of 8, the remaining bits
of the last data byte are filled with zeroes (truncated).
Table 63: Response of Function code FC2
Byte
...
Byte 7
Byte 8
Byte 9
Field name
Example
MODBUS function code
Byte count
Bit values
0x02
0x01
0x12
The status of the inputs 7 to 0 is shown as a byte value 0x12 or binary 0001 0010.
Input 7 is the bit having the highest significance of this byte and input 0 the lowest
value. The assignment is thus made from 7 to 0 as follows:
Table 64: Assignment of inputs
OFF OFF OFF
ON
OFF OFF
Bit
0
0
0
1
0
Coil
7
6
5
4
3
ON
OFF
0
1
0
2
1
0
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Exception
Table 65: Exception of Function code FC2
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x82
0x01 or 0x02
149
150
Table of Contents
11.2.3.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Function Code FC3 (Read Multiple Registers)
This function reads the contents of holding registers from a slave device in word
format.
Request
The request specifies the reference number (start register) and the word count
(register quantity) of the registers to be read. The reference number of the request
is zero based, therefore, the first register starts at address 0.
Example: Read registers 0 and 1.
Table 66: Request of Function code FC3
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Word count
Example
0x0000
0x0000
0x0006
0x01 not used
0x03
0x0000
0x0002
Response
The reply register data is packed as 2 bytes per register. The first byte contains the
higher value bits, the second the lower values.
Table 67: Response of Function code FC3
Byte
...
Byte 7
Byte 8
Byte 9, 10
Byte 11, 12
Field name
Example
MODBUS function code
Byte count
Value register 0
Value register 1
0x03
0x04
0x1234
0x2345
The contents of register 0 are displayed by the value 0x1234 and the contents of
register 1 is 0x2345.
Exception
Table 68: Exception of Function code FC3
Byte
...
Byte 7
Byte 8
Field name
Example
MODBUS function code
Exception code
0x83
0x01 or 0x02
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.3.4
Table of Contents
151
Function Code FC4 (Read Input Registers)
This function reads contents of input registers from the slave device in word
format.
Request
The request specifies a reference number (start register) and the word count
(register quantity) of the registers to be read. The reference number of the request
is zero based, therefore, the first register starts at address 0.
Example: Read registers 0 and 1
Table 69: Request of Function code FC4
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Word count
Example
0x0000
0x0000
0x0006
0x01 not used
0x04
0x0000
0x0002
Response
The register data of the response is packed as 2 bytes per register. The first byte
has the higher value bits, the second the lower values.
Table 70: Response of Function code FC4
Byte
...
Byte 7
Byte 8
Byte 9, 10
Byte 11, 12
Field name
Example
MODBUS function code
Byte count
Value register 0
Value register 1
0x04
0x04
0x1234
0x2345
The contents of register 0 are shown by the value 0x1234 and the contents of
register 1 is 0x2345.
Exception
Table 71: Exception of Function code FC4
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x84
0x01 or 0x02
152
Table of Contents
11.2.3.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Function Code FC5 (Write Coil)
This function writes a single output bit to the slave device.
Request
The request specifies the reference number (output address) of output bit to be
written. The reference number of the request is zero based; therefore, the first coil
starts at address 0.
Example: Turn ON the second output bit (address 1)
Table 72: Request of Function code FC5
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10
Byte 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
ON/OFF
Example
0x0000
0x0000
0x0006
0x01 not used
0x05
0x0001
0xFF
0x00
Response
Table 73: Response of Function code FC5
Byte
...
Byte 7
Byte 8, 9
Byte 10
Byte 11
Field name
Example
MODBUS function code
Reference number
Value
0x05
0x0001
0xFF
0x00
Exception
Table 74: Exception of Function code FC5
Byte
...
Byte 7
Byte 8
Field name
Example
MODBUS function code
Exception code
0x85
0x01, 0x02 or 0x03
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.3.6
Table of Contents
153
Function Code FC6 (Write Single Register)
This function writes the value of one single output register to a slave device in
word format.
Request
The request specifies the reference number (register address) of the first output
word to be written. The value to be written is specified in the “Register Value”
field. The reference number of the request is zero based; therefore, the first
register starts at address 0.
Example: Write a value of 0x1234 to the second output register
Table 75: Request of Function code FC6
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Register value
Example
0x0000
0x0000
0x0006
0x01 not used
0x06
0x0001
0x1234
Response
The reply is an echo of the inquiry.
Table 76: Response of Function code FC6
Byte
...
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Example
MODBUS function code
Reference number
Register value
0x06
0x0001
0x1234
Exception
Table 77: Exception of Function code FC6
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x85
0x01 or 0x02
154
Table of Contents
11.2.3.7
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Function Code FC11 (Get Comm Event Counter)
This function returns a status word and an event counter from the slave device’s
communication event counter. By reading the current count before and after a
series of messages, a master can determine whether the messages were handled
normally by the slave.
Following each successful new processing, the counter counts up. This counting
process is not performed in the case of exception replies, poll commands or
counter inquiries.
Request
Table 78: Request of Function code FC11
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Example
0x0000
0x0000
0x0002
0x01 not used
0x0B
Response
The reply contains a 2-byte status word and a 2-byte event counter. The status
word only contains zeroes.
Table 79: Response of Function code FC11
Byte
...
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Example
MODBUS function code
Status
Event count
0x0B
0x0000
0x0003
The event counter shows that 3 (0x0003) events were counted.
Exception
Table 80: Exception of Function code FC 11
Byte
...
Byte 7
Byte 8
Field name
Example
MODBUS function code
Exception code
0x85
0x01 or 0x02
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.3.8
Table of Contents
155
Function Code FC15 (Force Multiple Coils)
This function sets a sequence of output bits to 1 or 0 in a slave device. The
maximum number is 256 bits.
Request
The request message specifies the reference number (first coil in the sequence),
the bit count (number of bits to be written), and the output data. The output coils
are zero-based; therefore, the first output point is 0.
In this example 16 bits are set, starting with the address 0. The request contains 2
bytes with the value 0xA5F0, or 1010 0101 1111 0000 in binary format.
The first data byte transmits the value of 0xA5 to the addresses 7 to 0, whereby 0
is the lowest value bit. The next byte transmits 0xF0 to the addresses 15 to 8,
whereby the lowest value bit is 8.
Table 81: Request of Function code FC15
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Byte 12
Byte 13
Byte 14
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Bit count
Byte count
Data byte1
Data byte2
Example
0x0000
0x0000
0x0009
0x01 not used
0x0F
0x0000
0x0010
0x02
0xA5
0xF0
Response
Table 82: Response of Function code FC15
Byte
...
Byte 7
Byte 8, 9
Byte 10, 11
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Reference number
Bit count
0x0F
0x0000
0x0010
156
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Exception
Table 83: Exception of Function code FC15
Byte
...
Byte 7
Byte 8
Field name
Example
MODBUS function code
Exception code
0x8F
0x01 or 0x02
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.3.9
Table of Contents
157
Function Code FC16 (Write Multiple Registers)
This function writes a sequence of registers in a slave device in word format.
Request
The Request specifies the reference number (starting register), the word count
(number of registers to write), and the register data . The data is sent as 2 bytes
per register. The registers are zero-based; therefore, the first output is at address 0.
Example: Set data in registers 0 and 1
Table 84: Request of Function code FC16
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Byte 12
Byte 13, 14
Byte 15, 16
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
Word count
Byte count
Register value 1
Register value 2
Example
0x0000
0x0000
0x000B
0x01 not used
0x10
0x0000
0x0002
0x04
0x1234
0x2345
Response
Table 85: Response of Function code FC16
Byte
...
Byte 7
Byte 8, 9
Byte 10, 11
Field name
Example
MODBUS function code
Reference number
Word count
0x10
0x0000
0x0002
Exception
Table 86: Exception of Function code FC16
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x85
0x01 or 0x02
158
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.3.10 Function Code FC22 (Mask Write Register)
This function manipulates individual bits within a register using a combination of
an AND mask, an OR mask, and the register’s current content.
Request
Table 87: Request of Function code FC22
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Byte 12, 13
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number
AND mask
OR mask
Example
0x0000
0x0000
0x0002
0x01 not used
0x16
0x0000
0x0000
0xAAAA
Response
Table 88: Response of Function code FC22
Byte
...
Byte 7
Byte 8, 9
Byte 10, 11
Byte 12, 13
Field name
Example
MODBUS function code
Reference number
AND mask
OR mask
0x10
0x0000
0x0000
0xAAAA
Exception
Table 89: Exception of Function code FC22
Byte
...
Byte 7
Byte 8
Field name
Example
MODBUS function code
Exception code
0x85
0x01 or 0x02
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
159
11.2.3.11 Function Code FC23 (Read/Write Multiple Registers)
This function performs a combination of a read and write operation in a single
request. The function can write the new data to a group registers, and then return
the data of a different group.
Request
The reference numbers (addresses) are zero-based in the request message;
therefore, the first register is at address 0.
The request message specifies the registers to read and write. The data is sent as 2
bytes per register.
Example: The data in register 3 is set to value 0x0123, and values 0x0004 and
0x5678 are read out of the two registers 0 and 1.
Table 90: Request of Function code FC23
Byte
Byte 0, 1
Byte 2, 3
Byte 4, 5
Byte 6
Byte 7
Byte 8, 9
Byte 10, 11
Byte 12, 13
Byte 14, 15
Byte 16
Byte 17...(B+16)
Field name
Transaction identifier
Protocol identifier
Length field
Unit identifier
MODBUS function code
Reference number for read
Word count for read (1…125)
Reference number for write
Word count for write (1…100)
Byte count (2 x word count for write)
Register values (B = Byte count)
Example
0x0000
0x0000
0x000F
0x01 not used
0x17
0x0000
0x0002
0x0003
0x0001
0x02
0x0123
Response
Table 91: Response of Function code FC23
Byte
...
Byte 7
Byte 8
Byte 9...(B+8)
Field name
Example
MODBUS function code
Byte count (2 x word count for read)
Register values (B = Byte count)
0x17
0x04
0x0004 or 0x5678
Exception
Table 92: Exception of Function code FC23
Byte
...
Byte 7
Byte 8
Manual
Version 1.1.0
Field name
Example
MODBUS function code
Exception code
0x97
0x01 or 0x02
160
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Note
Note that if the register ranges overlap, the results are undefined!
If register areas for read and write overlap, the results are undefined.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.4
Table of Contents
161
MODBUS Register Mapping
The following tables display the MODBUS addressing and the internal variables.
Via the register services the states of the complex and digital I/O modules can be
determined or changed.
Register Access Reading (with FC3 and FC4)
Table 93: Register Access Reading (with FC3 and FC4)
MODBUS address
[dec]
[hex]
0...255
0x0000...0x00FF
256...511
0x0100...0x01FF
512...767
0x0200...0x02FF
768...4095
0x0300...0x0FFF
4096...12287 0x1000...0x2FFF
12288...24575 0x3000...0x5FFF
24576...25339 0x6000...0x62FB
25340...28671 0x62FC...0x6FFF
28672...29435 0x7000...0x72FB
29436...65535 0x72FC...0xFFFF
Manual
Version 1.1.0
IEC 61131
address
%IW0...%IW255
Memory range
Physical input area (1)
First 256 Words of physical input data
MODBUS exception:
“Illegal data address”
%QW0...%QW255 Physical output area (1)
First 256 Words of physical output data
MODBUS exception:
“Illegal data address”
Configuration register (see Section
„Configuration Register“)
MODBUS exception:
“Illegal data address”
%IW256...%IW1020 Physical input area (2)
Additional 764 Words physical input data
MODBUS exception:
“Illegal data address”
%QW256...%QW1020 Physical output area (2)
Additional 764 Words physical output data
MODBUS exception:
“Illegal data address”
162
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Register Access Writing (with FC6 and FC16)
Table 94: Register Access Writing (with FC6 and FC16)
MODBUS address
[dec]
[hex]
0...255
0x0000...0x00FF
IEC 61131
address
Memory range
%QW0...%QW255
Physical output area (1)
First 256 Words of physical output data
256...511
0x0100...0x01FF
MODBUS exception:
“Illegal data address”
512...767
0x0200...0x02FF
%QW0...%QW255 Physical output area (1)
First 256 Words of physical output data
768...4095 0x0300...0x0FFF
MODBUS exception:
“Illegal data address”
4096...12287 0x1000...0x2FFF
Configuration register (see Section
“Configuration Register”)
12288...24575 0x3000...0x5FFF
MODBUS exception:
“Illegal data address”
24576...25339 0x6000...0x62FB %QW256...%QW1020 Physical output area (2)
Additional 764 Words physical output data
25340...28671 0x62FC...0x6FFF
MODBUS exception:
“Illegal data address”
28672...29435 0x7000...0x72FB %QW256...%QW1020 Physical output area (2)
Additional 764 Words physical output data
29436...65535 0x72FC...0xFFFF
MODBUS exception:
“Illegal data address”
The digital MODBUS services (coil services) are bit accesses, with which only
the states of digital I/O modules can be determined or changed. Complex I/O
modules are not attainable with these services and so they are ignored. Because of
this the addressing of the digital channels begins again with 0, so that the
MODBUS address is always identical to the channel number, (i.e. the digital input
no. 47 has the MODBUS address "46").
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
163
Bit Access Reading (with FC1 and FC2)
Table 95: Bit Access Reading (with FC1 and FC2)
MODBUS address
[dec]
[hex]
0...511
0x0000...0x01FF
512...1023
0x0200...0x03FF
1024... 12287 0x0400...0x2FFF
12288...13815 0x3000...0x35F7
13816...16383 0x35F8...0x3FFF
16384...17911 0x4000...0x45F7
17912...32767 0x45F8...0x7FFF
0x8000…0x85F7
0x85F8…0x8FFF
0x9000…0x95F7
0x95F8…0xFFFF
Memory range
Description
Physical input area (1) First 512 digital inputs
Physical output area (1) First 512 digital outputs
MODBUS exception:
“Illegal data address”
MODBUS exception:
“Illegal data address
MODBUS exception:
“Illegal data address”
MODBUS exception:
“Illegal data address
MODBUS exception:
“Illegal data address”
Physical input area (2) Starts with the 513th and ends with the
2039th digital input
MODBUS exception:
“Illegal data address”
Physical output area (2) Starts with the 513th and ends with the
2039th digital output
MODBUS exception:
“Illegal data address”
Bit Access Writing (with FC5 and FC15)
Table 96: Bit Access Writing (with FC5 and FC15)
MODBUS address
[dec]
[hex]
0...511
0x0000...0x01FF
512...1023
0x0200...0x03FF
1024...12287 0x0400...0x2FFF
12288...13815 0x3000...0x35F7
13816...16383 0x35F8...0x3FFF
16384...17911 0x4000...0x45F7
17912...32767 0x45F8...0x7FFF
0x8000…0x85F7
0x85F8…0x8FFF
0x9000…0x95F7
0x95F8…0xFFFF
Manual
Version 1.1.0
Memory range
Description
Physical output area (1) First 512 digital outputs
Physical output area (1) First 512 digital outputs
MODBUS exception:
“Illegal data address”
MODBUS exception:
“Illegal data address
MODBUS exception:
“Illegal data address”
MODBUS exception:
“Illegal data address
MODBUS exception:
“Illegal data address”
Physical output area (2) Starts with the 513th and ends with the
2039th digital output
MODBUS exception:
“Illegal data address”
Physical output area (2) Starts with the 513th and ends with the
2039th digital output
MODBUS exception:
“Illegal data address”
164
Table of Contents
11.2.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
MODBUS Registers
Table 97: MODBUS registers
Register Access Length
address
(Word)
0x1000
R/W
1
0x1001
R/W
1
0x1002
R/W
1
0x1003
R/W
1
0x1004
R
1
0x1005
R/W
1
0x1006
R
1
0x1007
R/W
1
0x1008
R/W
1
0x1009
R/W
1
0x100A R/W
1
0x100B W
1
0x1020
R
1…2
0x1021
R
1
0x1022
R
1…4
0x1023
R
1…3
0x1024
R
1…2
0x1025
R
1…4
0x1028
R/W
1
0x1029
R
9
0x102A R
1
Watchdog time read/write
Watchdog coding mask 1…16
Watchdog coding mask 17…32
Watchdog trigger
Minimum trigger time
Watchdog stop (Write sequence 0xAAAA, 0x5555)
Watchdog status
Restart watchdog (Write sequence 0x1)
Stop watchdog (Write sequence 0x55AA or 0xAA55)
MODBUS and HTTP close at watchdog time-out
Watchdog configuration
Save watchdog parameter
LED error code
LED error argument
Number of analog output data in the process image (in bits)
Number of analog input data in the process image (in bits)
Number of digital output data in the process image (in bits)
Number of digital input data in the process image (in bits)
Boot configuration
MODBUS/TCP statistics
Number of TCP connections
0x102B
W
1
KBUS Reset
0x1030
0x1031
R/W
R
1
3
Configuration MODBUS/TCP time-out
Read out the MAC-ID of the coupler/controller
0x1037
R/W
1
Modbus Response Delay (ms)
0x1050
R
3
Diagnosis of the connected I/O modules
0x2000
0x2001
0x2002
0x2003
0x2004
0x2005
0x2006
0x2007
0x2008
0x2010
0x2011
0x2012
0x2013
0x2014
R
R
R
R
R
R
R
R
R
R
R
R
R
R
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Constant 0x0000
Constant 0xFFFF
Constant 0x1234
Constant 0xAAAA
Constant 0x5555
Constant 0x7FFF
Constant 0x8000
Constant 0x3FFF
Constant 0x4000
Firmware version
Series code
Coupler/controller code
Firmware version major revision
Firmware version minor revision
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
165
Table 98: MODBUS registers (Continuation)
Register Access Length Description
address
(Word)
0x2020
R
16
Short description controller
0x2021
R
8
Compile time of the firmware
0x2022
R
8
Compile date of the firmware
0x2023
R
32
Indication of the firmware loader
0x2030
R
65
Description of the connected I/O modules (module 0…64)
0x2031
R
64
Description of the connected I/O modules (module 65…128)
0x2032
R
64
Description of the connected I/O modules (module 129…192)
0x2033
R
63
Description of the connected I/O modules (module 193…255)
0x2040
W
1
Software reset (Write sequence 0x55AA or 0xAA55)
0x2041
W
1
Format flash disk
0x2042
W
1
Extract HTML sides from the firmware
0x2043
W
1
Factory settings
11.2.5.1
Accessing Register Values
You can use any MODBUS application to access (read from or write to) register
values. Both commercial (e.g., "Modscan") and free programs (from
http://www.modbus.org/tech.php) are available.
The following sections describe how to access both the registers and their values.
11.2.5.2
Watchdog Registers
The watchdog monitors the data transfer between the fieldbus master and the
controller. Every time the controller receives a specific request (as define in the
watchdog setup registers) from the master, the watchdog timer in the controller
resets.
In the case of fault free communication, the watchdog timer does not reach its end
value. After each successful data transfer, the timer is reset.
If the watchdog times out, a fieldbus failure has occurred. In this case, the
fieldbus controller answers all following MODBUS TCP/IP requests with the
exception code 0x0004 (Slave Device Failure).
In the controller special registers are used to setup the watchdog by the master
(Register addresses 0x1000 to 0x1008).
By default, the watchdog is not enabled when you turn the controller on. To
activate it, the first step is to set/verify the desired time-out value of the Watchdog
Time register (0x1000). Second, the function code mask must be specified in the
mask register (0x1001), which defines the function code(s) that will reset the
timer. Finally, the Watchdog-Trigger register (0x1003) must be changed to a nonzero value to start the timer.
Manual
Version 1.1.0
166
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Reading the Minimum Trigger time (Register 0x1004) reveals whether a
watchdog fault occurred. If this time value is 0, a fieldbus failure is assumed.
The timer of watchdog can manually be reset, if it is not timed out, by writing a
value of 0x1 to the Restart Watchdog register (0x1007).
After the watchdog is started, it can be stopped by the user via the Watchdog Stop
register (0x1005) or the Simply Stop Watchdog register (0x1008).
The watchdog registers can be addressed in the same way as described with the
MODBUS read and write function codes. Specify the respective register address
in place of the reference number.
Table 99: Register address 0x1000
Register address 0x1000 (4096dec)
Watchdog time, WS_TIME
Value
Read/write
Access
0x0064
Default
This register stores the watchdog timeout value as an unsigned 16 bit value. The
Description
default value is 0. Setting this value will not trigger the watchdog. However, a
non zero value must be stored in this register before the watchdog can be
triggered. The time value is stored in multiples of 100ms (e.g., 0x0009 is .9
seconds). It is not possible to modify this value while the watchdog is running.
Table 100: Register address 0x1001
Register address 0x1001 (4097dec)
Watchdog function coding mask, function code 1...16, WDFCM_1_16
Value
Read/write
Access
0xFFFF
Default
Using this mask, the function codes can be set to trigger the watchdog function.
Description
The function code can be selected via a "1"
FC 1 Bit 0
FC 2 Bit 1
FC 3 Bit 0 or 1
FC 4 Bit 2
FC 5 Bit 0 or 2
FC 6 Bit 1 or 2
etc.
The watchdog function is started if a value is not equal to zero. If only codes
from non-supported functions are entered in the mask, the watchdog will not
start. An existing fault is reset and writing into the process illustration is possible.
Also here changes cannot be made while the watchdog is running. When the
watchdog is enabled, no code is generated to rewrite the current data value.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
167
Table 101: Register address 0x1002
Register address 0x1002 (4098dec)
Watchdog function coding mask, function code 17...32, WD_FCM_17_32
Value
Read/write
Access
0xFFFF
Default
Same function as above, however, with the function codes 17 to 32. These codes
Description
are currently not supported, for this reason the default value should not be
changed. It is not possible to modify this value while the watchdog is running.
Table 102: Register address 0x1003
Register address 0x1003 (4099dez)
Watchdog Trigger, WD_TRIGGER
Value
Read/write
Access
0x0000
Standard
This register is used for an alternative trigger method. The watchdog is triggered
Description
by writing different values in this register. Values following each other must
differ in size. Writing of a value not equal to zero starts the watchdog. A
watchdog fault is reset and writing process data is possible again.
Table 103: Register address 0x1004
Register address 0x1004 (4100dez)
Minimum current trigger time, WD_AC_TRG_TIME
Value
Read/write
Access
0xFFFF
Standard
This register saves the minimum current watchdog trigger time. If the watchdog
Description
is triggered, the saved value is compared with the current value. If the current
value is smaller than the saved value, this is replaced by the current value. The
unit is 100 ms/digit. The saved value is changed by writing new values, which
does not affect the watchdog. 0x000 is not permissible.
Table 104: Register address 0x1005
Register address 0x1005 (4101dez)
Stop watchdog, WD_AC_STOP_MASK
Value
Read/write
Access
0x0000
Standard
The watchdog is stopped if here the value 0xAAAA is written first, followed by
Description
0x5555. The watchdog fault reaction is blocked. A watchdog fault is reset and
writing on the process data is possible again.
Table 105: Register address 0x1006
Register address 0x1006 (4102dez)
While watchdog is running, WD_RUNNING
Value
Read
Access
0x0000
Standard
Current watchdog status.
Description
at 0x0000: Watchdog not active
at 0x0001: Watchdog active
at 0x0002: Watchdog exhausted.
Manual
Version 1.1.0
168
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 106: Register address 0x1007
Register address 0x1007 (4103dez)
Restart watchdog, WD_RESTART
Value
Read/write
Access
0x0001
Standard
This register restarts the watchdog timer by writing a value of 0x1 into it.
Description
If the watchdog was stopped before the overrun, it is not restarted.
Table 107: Register address 0x1008
Register address 0x1008 (4104dez)
Simply stop watchdog, WD_AC_STOP_SIMPLE
Value
Read/write
Access
0x0000
Standard
This register stops the watchdog by writing the value 0x0AA55 or 0X55AA into
Description
it. The watchdog timeout fault is deactivated and it is possible to write in the
watchdog register again. If there is an existing watchdog fault, it is reset
Table 108: Register address 0x1009
Register address 0x1009 (4105dez)
Close MODBUS socket after watchdog timeout
Value
Read/write
Access
0: MODBUS socket is not closed
Description
1: MODBUS socket is closed
Table 109: Register address 0x100A
Register address 0x100A (4106dez)
Alternative watchdog
Value
Read/write
Access
0x0000
Standard
This register provides an alternate way to activate the watchdog timer.
Description
Procedure: Write a time value in register 0x1000; then write a 0x0001 into
register 0x100A. With the first MODBUS request, the watchdog is started. The
watchdog timer is reset with each MODBUS/TCP instruction. If the watchdog
times out, all outputs are set to zero. The outputs will become operational again,
after communications are re-established.
Register 0x00A is non-volatile, including register 0x1000.
It is not possible to modify the time value in register 0x1000 while the watchdog
is running.
The length of each register is 1 word; i.e., with each access only one word can be
written or read. Following are two examples of how to set the value for a time
overrun:
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
169
Setting the watchdog for a timeout of more than 1 second:
1.
Write 0x000A in the register for time overrun (0x1000).
Register 0x1000 works with a multiple of 100 ms;
1 s = 1000 ms; 1000 ms / 100 ms = 10dec = Ahex)
2.
Use the function code 5 to write 0x0010 (=2(5-1)) in the coding mask
(register 0x1001).
Table 110: Starting Watchdog
FC FC16 FC15 FC14 FC13 FC12 FC11 FC10
9
Bit 15 14 13 12 11 10
0
0
0
0
0
0
bin 0
0
0
hex
FC9
FC8
FC7
FC6
FC5
FC4
FC3
FC2
FC1
8
0
7
0
6
0
5
0
4
1
3
0
2
0
1
0
0
0
1
0
Function code 5 (writing a digital output bit) continuously triggers the watchdog
to restart the watchdog timer again and again within the specified time. If time
between requests exceeds 1 second, a watchdog timeout error occurs.
3.
To stop the watchdog, write the value 0x0AA55 or 0X55AA into 0x1008
(Simply Stop Watchdog register, WD_AC_STOP_SIMPLE).
Setting the watchdog for a timeout of 10 minutes or more:
1.
Write 0x1770 (= 10*60*1000 ms / 100 ms) in the register for time overrun
(0x1000).
(Register 0x1000 works with a multiple of 100 ms;
10 min = 600,000 ms; 600,000 ms / 100 ms = 6000dec = 1770hex)
2.
Write 0x0001 in the watchdog trigger register (0x1003) to start the
watchdog.
3.
Write different values (e.g., counter values 0x0000, 0x0001) in the
watchdog to trigger register (0x1003).
Values following each other must differ in size. Writing of a value not equal to
zero starts the watchdog. Watchdog faults are reset and writing process data is
possible again.
4.
To stop the watchdog, write the value 0x0AA55 or 0X55AA into 0x1008
(Simply Stop Watchdog register, WD_AC_STOP_SIMPLE).
Table 111: Register address 0x100B
Register address 0x100B (4107dez)
Save watchdog parameter
Value
Write
Access
0x0000
Standard
With writing of '0x55AA' or '0xAA55' in register 0x100B the registers 0x1000,
Description
0x1001, 0x1002 are set on remanent.
Manual
Version 1.1.0
170
Table of Contents
11.2.5.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Diagnostic Registers
The following registers can be read to determine errors in the node:
Table 112: Register address 0x1020
Register address 0x1020 (4128dec)
LedErrCode
Value
Read
Access
Declaration of the Error code
Description
Table 113: Register address 0x1021
Register address 0x1021 (4129dec)
LedErrArg
Value
Read
Access
Declaration of the Error argument
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.2.5.4
Table of Contents
171
Configuration Registers
The following registers contain configuration information of the connected
modules:
Table 114: Register address 0x1022
Register address 0x1022 (4130dec)
CnfLen.AnalogOut
Value
Read
Access
Number of word-based outputs registers in the process image in bits (divide by
Description
16 to get the total number of analog words)
Table 115: Register address 0x1023
Register address 0x1023 (4131dec)
CnfLen.AnalogInp
Value
Read
Access
Number of word-based inputs registers in the process image in bits (divide by 16
Description
to get the total number of analog words)
Table 116: Register address 0x1024
Register address 0x1024 (4132dec)
CnfLen.DigitalOut
Value
Read
Access
Number of digital output bits in the process image
Description
Table 117: Register address 0x1025
Register address 0x1025 (4133dec)
CnfLen.DigitalInp
Value
Read
Access
Number of digital input bits in the process image
Description
Table 118: Register address 0x1028
Register address 0x1028 (4136dec)
Boot options
Value
Read/write
Access
Boot configuration:
Description
1: BootP
2: DHCP
4: EEPROM
Manual
Version 1.1.0
172
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 119: Register address 0x1029
Register address 0x1029 (4137dec) with 9 words
MODBUS TCP statistics
Value
Read/write
Access
 internal bus error, fieldbus error by
1 word SlaveDeviceFailure
Description
activated watchdog
 error in the MODBUS TCP header
1 word BadProtocol
 Wrong telegram length
1 word BadLength
 Invalid function code
1 word BadFunction
 Invalid register address
1 word BadAddress
 Invalid value
1 word BadData
 Number of the registers which can be
1 word TooManyRegisters
worked on is too large, Read/Write 125/100
 Number of the coils which can be worked
1 word TooManyBits
on is too large, Read/Write 2000/800
1 word ModTcpMessageCounter  Number of received MODBUS/TCP
requests
With Writing 0xAA55 or 0x55AA in the register will reset this data area.
Table 120: Register address 0x102A
Register address 0x102A (4138dec) with a word count of 1
MODBUS/TCP Connections
Value
Read
Access
Number of TCP connections
Description
Table 121: Register address 0x102B
Register address 0x102B (4139dez) with a word count of up to 1
KBUS reset
Value
Write
Access
Writing of this register restarts the internal bus
Description
Table 122: Register address 0x1030
Register address 0x1030 (4144dec) with a word count of 1
Configuration MODBUS/TCP Time-out
Value
Read/write
Access
0x0258 (600 decimal)
Default
This is the maximum number of milliseconds the fieldbus coupler will allow a
Description
MODBUS/TCP connection to stay open without receiving a MODBUS request.
Upon time-out, idle connection will be closed. Outputs remain in last state.
Default value is 600 ms (60 seconds), the time base is 100 ms, the minimal value
is 100 ms. If the value is set to ‘0’, the timeout is disabled. On this connection,
the watchdog is triggered with a request.
Table 123: Register address 0x1031
Register address 0x1031 (4145dec) with a word count of 3
Read the MAC-ID of the controller
Value
Read
Access
This register gives the MAC-ID, with a length of 3 words
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
173
Table 1: Register address 0x1037
Register address 0x1031 (4151dez) with a word count of 3
Configuration of Modbus Response Delay Time
Value
Read/write
Access
0x0000
Default
This register saves the value for the Modbus Response Delay Time for a Modbus
Description
connection. The time base is 1 ms. On the Modbus TCP connection, the
response will be delayed by the inscribed time.
Table 124: Register address 0x1050
Register address 0x1050 (4176dec) with a word count of 3
Diagnosis of the connected I/O modules
Value
Read
Access
Diagnosis of the connected I/O modules, length 3 words
Description
Word 1: Number of the module
Word 2: Number of the channel
Word 3: Diagnosis
Table 125: Register address 0x2030
Register address 0x2030 (8240dec) with a word count of up to 65
Description of the connected I/O modules
Value
Read module 0...64
Access
Length 1...65 words
Description
These 65 registers identify the controller and the first 64 modules present in a
node. Each module is represented in a word. Because item numbers cannot be
read out of digital modules, a code is displayed for them, as defined below:
Bit position 0

Input module
Bit position 1

Output module
Bit position 2…7

Not used
Bit position 8…14

Module size in bits
Bit position 15

Designation digital module
Examples:
4 Channel Digital Input Module = 0x8401
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Code 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1
8
4
0
1
Hex
2 Channel Digital Output Module = 0x8202
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Code 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0
8
2
0
2
Hex
Manual
Version 1.1.0
174
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 126: Register address 0x2031
Register address 0x2031 (8241dec) with a word count of up to 64
Description of the connected I/O modules
Value
Read modules 65...128
Access
Length 1-64 words
Description
These 64 registers identify the 2nd block of I/O modules present (modules 65 to
128). Each module is represented in a word. Because item numbers cannot be
read out of digital modules, a code is displayed for them, as defined below:
Bit position 0

Input module
Bit position 1

Output module
Bit position 2…7

Not used
Bit position 8…14

Module size in bits
Bit position 15

Designation digital module
Table 127: Register address 0x2032
Register address 0x2032 (8242dec) with a word count of up to 64
Description of the connected I/O modules
Value
Read modules 129...192
Access
Length 1…64 words
Description
These 64 registers identify the 3rd block of I/O modules present (modules 129 to
192). Each module is represented in a word. Because item numbers cannot be
read out of digital modules, a code is displayed for them, as defined below:
Bit position 0

Input module
Bit position 1

Output module
Bit position 2…7

Not used
Bit position 8…14

Module size in bits
Bit position 15

Designation digital module
Table 128: Register address 0x2033
Register address 0x2033 (8243dec) with a word count of up to 65
Description of the connected I/O modules
Value
Read modules 193 ... 255
Access
Length 1-63 words
Description
These 63 registers identify the 4th block of I/O modules present (modules 193 to
255). Each module is represented in a word. Because item numbers cannot be
read out of digital modules, a code is displayed for them, as defined below:
Bit position 0

Input module
Bit position 1

Output module
Bit position 2…7

Not used
Bit position 8…14

Module size in bits
Bit position 15

Designation digital module
Table 129: Register address 0x2040
Register address 0x2040 (8256dec)
Implement a software reset
Value
Write (Write sequence 0xAA55 or 0x55AA)
Access
With Writing 0xAA55 or 0x55AA the register will be reset.
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
175
Table 130: Register address 0x2041
Register address 0x2041 (8257dez)
Flash Format
Value
Write (Write sequence 0xAA55 or 0x55AA)
Access
The file system Flash is again formatted.
Description
Table 131: Register address 0x2042
Register address 0x2042 (8258dez)
Extract data files
Value
Write (Write sequence 0xAA55 or 0x55AA)
Access
The standard files (HTML pages) of the Coupler/Controller are extracted and
Description
written into the Flash.
Table 132: Register address 0x2043
Register address 0x2043 (8259dez)
0x55AA
Value
Write
Access
Factory Settings
Description
Manual
Version 1.1.0
176
Table of Contents
11.2.5.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Firmware Information Registers
The following registers contain information on the firmware of the controller:
Table 133: Register address 0x2010
Register address 0x2010 (8208dec) with a word count of 1
Revision, INFO_REVISION
Value
Read
Access
Firmware index, e.g. 0005 for version 5
Description
Table 134: Register address 0x2011
Register address 0x2011 (8209dec) with a word count of 1
Series code, INFO_SERIES
Value
Read
Access
WAGO serial number, e.g. 0750 for WAGO-I/O-SYSTEM 750
Description
Table 135: Register address 0x2012
Register address 0x2012 (8210dec) with a word count of 1
Item number, INFO_ITEM
Value
Read
Access
WAGO item number,
Description
e.g. 841 for the controller 750-841 or 341 for the coupler 750-341 etc.
Table 136: Register address 0x2013
Register address 0x2013 (8211dec) with a word count of 1
Major sub item code, INFO_MAJOR
Value
Read
Access
Firmware version Major Revision
Description
Table 137: Register address 0x2014
Register address 0x2014 (8212dec) with a word count of 1
Minor sub item code, INFO_MINOR
Value
Read
Access
Firmware version Minor Revision
Description
Table 138: Register address 0x2020
Register address 0x2020 (8224dec) with a word count of up to 16
Description, INFO_DESCRIPTION
Value
Read
Access
Information on the controller, 16 words
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 139: Register address 0x2021
Register address 0x2021 (8225dec) with a word count of up to 8
Description, INFO_DESCRIPTION
Value
Read
Access
Time of the firmware version, 8 words
Description
Table 140: Register address 0x2022
Register address 0x2022 (8226dec) with a word count of up to 8
Description, INFO_DATE
Value
Read
Access
Date of the firmware version, 8 words
Description
Table 141: Register address 0x2023
Register address 0x2023 (8227dec) with a word count of up to 32
Description, INFO_LOADER_INFO
Value
Read
Access
Information to the programming of the firmware, 32 words
Description
Manual
Version 1.1.0
177
178
Table of Contents
11.2.5.6
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Constant Registers
The following registers contain constants, which can be used to test
communication with the master:
Table 142: Register address 0x2000
Register address 0x2000 (8192dec)
Zero, GP_ZERO
Value
Read
Access
Constant with zeros
Description
Table 143: Register address 0x2001
Register address 0x2001 (8193dec)
Ones, GP_ONES
Value
Read
Access
Constant with ones
Description
• –1 if this is declared as "signed int"
• MAXVALUE if it is declared as "unsigned int"
Table 144: Register address 0x2002
Register address 0x2002 (8194dec)
1,2,3,4, GP_1234
Value
Read
Access
This constant value is used to test the Intel/Motorola format specifier. If the
Description
master reads a value of 0x1234, then with Intel format is selected – this is the
correct format. If 0x3412 appears, Motorola format is selected.
Table 145: Register address 0x2003
Register address 0x2003 (8195dec)
Mask 1, GP_AAAA
Value
Read
Access
This constant is used to verify that all bits are accessible to the fieldbus master.
Description
This will be used together with register 0x2004.
Table 146: Register address 0x2004
Register address 0x2004 (8196dec)
Mask 1, GP_5555
Value
Read
Access
This constant is used to verify that all bits are accessible to the fieldbus master.
Description
This will be used together with register 0x2003.
Table 147: Register address 0x2005
Register address 0x2005 (8197dec)
Maximum positive number, GP_MAX_POS
Value
Read
Access
Constant in order to control arithmetic.
Description
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 148: Register address 0x2006
Register address 0x2006 (8198dec)
Maximum negative number, GP_MAX_NEG
Value
Read
Access
Constant in order to control arithmetic
Description
Table 149: Register address 0x2007
Register address 0x2007 (8199dec)
Maximum half positive number, GP_HALF_POS
Value
Read
Access
Constant in order to control arithmetic
Description
Table 150: Register address 0x2008
Register address 0x2008 (8200dec)
Maximum half negative number, GP_HALF_NEG
Value
Read
Access
Constant in order to control arithmetic
Description
Manual
Version 1.1.0
Table of Contents
179
180
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3
EtherNet/IP (Ethernet/Industrial Protocol)
11.3.1
General
EtherNet/IP stands for Ethernet Industrial Protocol and defines an open industry
standard that extends the classic Ethernet with an industrial protocol. This
standard was jointly developed by ControlNet International (CI) and the Open
DeviceNet Vendor Association (ODVA) with the help of the Industrial Ethernet
Association (IEA).
This communication system enables devices to exchange time-critical 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 is based on the TCP/IP protocol family and consequently uses the
bottom 4 layers of the OSI layer model in unaltered form so that all standard
Ethernet communication modules such as PC interface cards, cables, connectors,
hubs and switches can also be used with EtherNet/IP.
Positioned above the transport layer is the encapsulation protocol, which enables
use of the Control & Information Protocol (CIP) on TCP/IP and UDP/IP.
CIP, as a major network independent standard, is already used with ControlNet
and DeviceNet. Therefore, converting from one of these protocols to EtherNet/IP
is easy to do. Data exchange takes place with the help of an object model.
In this way, ControlNet, DeviceNet and EtherNet/IP have the same application
protocol and can therefore jointly use device profiles and object libraries. These
objects enable plug-and-play interoperability between complex devices of
different manufacturers.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.2
Table of Contents
181
Protocol overview in the OSI model
In order to clarify the interrelationships between DeviceNet, ControlNet and
EtherNet/IP, the following diagram presents the associated ISO/OSI reference
model.
Table 151: ISO/OSI reference model
Object Library
(Communications, Applications, Time
Synchronization)
Safety Object
Library
6
Presentation
Layer
Data Management Services
Explicit and I/O Messages
Safety Services and
Messages
5
Session
Layer
TCP/UDP
3
Network
Layer
Internet
Protocol
2
Data Link
Layer
CompoNet
Network and Transport
ControlNet
Network
and
Transport
DeviceNet
Network and
Transport
Ethernet
CSMA/CD
CompoNet
Time Slot
ControlNet
CTDMA
CAN
CSMA/NBA
Ethernet
CompoNet
ControlNet
DeviceNet
Network Adaptations of CIP
4
Transport
Layer
1
Physical
Layer
Manual
Version 1.1.0
Connection Management, Routing
Comon Industrial Protocol (CIP)
7
Application
Layer
182
Table of Contents
11.3.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Characteristics of the EtherNet/IP Protocol Software
The Ethernet/IP product classes are divided into 4 levels with each level
containing a particular functionality. Each higher level in turn possesses at least
the functionality of a lower level. The fieldbus coupler supports levels 1 and 2 of
the Ethernet/IP product classes, which immediately build on each other.
11.3.4
Level 2
Level 2: Level 1 + I/O Messages Server
Level 1
Level 1: Explicit 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)
EDS File
The "Electronic Data Sheets" file (EDS file for short) contains the characteristics
of the fieldbus coupler/controller and information regarding its communication
capabilities. The EDS file required for Ethernet/IP operation is imported and
installed by the corresponding configuration software.
Note
Downloading the EDS file!
You can download the EDS file in the download area of the WAGO web site:
http://www.wago.com  Service  Downloads  AUTOMATION
Information
Information about installing the EDS file
When installing the EDS file, refer to the information provided in the
documentation of the configuration software, which you are using.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.5
Object Model
11.3.5.1
General
Table of Contents
183
For network communication, Ethernet/IP utilizes an object model in which all
functions and data of a device are described.
Each node in the network is depicted as a collection of objects.
The object model contains terms that are defined as follows:
Object:
An object is an abstract representation of individual, related components within a
device. It is determined by its data or attributes, its outwardly applied functions or
services, and by its defined behavior.
Class:
A class describes a series of objects which all represent the same type of system
components. A class is the generalization of an object. All objects in a class are
identical as regards form and behavior, but can comprise differing attribute
values.
Instance:
An instance describes a specific and physical occurrence of an object. The terms
"object," "instance" and "object instance" all refer to a specific instance. Different
instances of a class have the same services, the same behavior and the same
variables (attributes). However, you can have different variable values.
For example, Finland is an instance of the "Land" object class.
Variable:
The variables (attributes) describe an externally visible characteristic or the
function of an object. Typical attributes include configuration or status
information.
For example, the ASCII name of an object or the repetition frequency of a
periodic object is output.
Service:
A service is a function supported by an object and/or an object class. CIP defines
a group of common services that are applied to the attributes. These services
execute specified actions.
Example: Reading variables.
Behavior:
The behavior specifies how an object functions. The functions result from various
occurrences, which are determined by the object, e.g. receiving service requests,
recording internal errors or the sequence of timers.
Manual
Version 1.1.0
184
Table of Contents
11.3.5.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Class Overview
CIP classes are included in the CIP specification of ODVA. They describe the
properties (Volume 1, "Common Industrial Protocol") of Ethernet and CAN
independent of their physical interface. The physical interface is described in a
separate specification. For Ethernet/IP, this is Volume 2 ("Ethernet/IP Adaptation
of CIP"), which describes the adaption of Ethernet /IP to CIP.
For this purpose, WAGO uses classes 01hex, 02hex, 04hex, 05hex, 06hex and F4hex,
which are described in Volume 1 ("Common Industrial Protocol").
Classes F5hex and F6hex are supported from Volume 2 ("Ethernet/IP Adaptation of
CIP").
WAGO-specific classes listed in the overview table below are also available.
All CIP Common classes listed and the WAGO-specific classes listed below that
are described in detail in the following individual sections after a brief explanation
of the table headings in the object descriptions.
Table 152: CIP common class
Class
01 hex
02 hex
04 hex
05 hex
06 hex
F5 hex
F6 hex
Name
Identity
Message Router
Assembly
Connection
Connection Manager
TCP/IP Interface Object
Ethernet Link Object
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 153: WAGO specific classes
Class
64 hex
65 hex
66 hex
67 hex
68 hex
69 hex
6A hex
6B hex
6C hex
6D hex
6E hex
6F hex
70 hex
71 hex
72 hex
73 hex
74 hex
80 hex
81 hex
Manual
Version 1.1.0
Name
Coupler/Controller Configuration Object
Discrete Input Point
Discrete Output Point
Analog Input Point
Analog Output Point
Discrete Input Point Extended 1
Discrete Output Point Extended 1
Analog Input Point Extended 1
Analog Output Point Extended 1
Discrete Input Point Extended 2
Discrete Output Point Extended 2
Analog Input Point Extended 2
Analog Output Point Extended 2
Discrete Input Point Extended 3
Discrete Output Point Extended 3
Analog Input Point Extended 3
Analog Output Point Extended 3
Module Configuration
Module Configuration Extended 1
185
186
Table of Contents
11.3.5.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Explanation of the Table Headings in the Object Descriptions
Table 154: Explanation of the table headings in the object descriptions
Table heading
Description
Attribute ID
Access
Integer value which is assigned to the corresponded attribute
Set:
The attribute can be accessed by means of Set_Attribute services.
Note
Response also possible with Get_Attribute service!
All the set attributes can also be accessed by means of
Get_Attribute services.
NV
Get:
The attribute can be accessed by means of Get_Attribute services.
Get_Attribute_All:
Delivers content of all attributes.
Set_Attribute_Single:
Modifies an attribute value.
Reset:
Performs a restart.
0: Restart
1: Restart and restoration of factory settings
NV (non volatile):
The attribute is permanently stored in the controller.
V (volatile):
The attribute is not permanently stored in the controller.
Note
Name
Data type
Description
Default value
11.3.5.4
Without specifying, the attribute is not saved!
If this column is missing, all attributes have the type V
(volatile).
Designation of the attribute
Designation of the CIP data type of the attribute
Short description for the Attribute
Factory settings
Identity (01 hex)
The "Identity" class provides general information about the fieldbus
coupler/controller that clearly identifies it.
Instance 0 (Class Attributes)
Table 155: Identity (01 hex) – Class
Attribute ID Access Name
1
Get
Revision
2
Get
Max Instance
3
Get
Max ID number of
class attributes
4
Get
Max ID number of
instance attribute
Data type
UINT
UINT
UINT
UINT
Description
Revision of this object
Maximum instance
Maximum number of
class attributes
Maximum number of
instance attributes
Default value
1 (0x0001)
1 (0x0001)
0 (0x0000)
0 (0x0000)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
187
Instance 1
Table 156: Identity (01 hex) – Instance 1
Attribute ID Access Name
1
Get
Vendor ID
Default value
40 (0x0028)
2
Get
12 (0x000C)
3
Get
4
Get
5
Get
6
7
Get
Get
Data type Description
UINT
Manufacturer
identification
Device Type
UINT
General type
designation of
the product
Product Code
UINT
Designation
of the
coupler/
controller
Revision
STRUCT Revision of
of:
the identity
objects
Major Revision UINT
Minor Revision UINT
Status
WORD
Current status
of the device
Serial Number
Product Name
UINT
SHORT_
STRING
z. B. 841 (0x0349),
873 (0x0369), 341(0x0155) etc.
Depending on the firmware
Bit 0
Assignment to a
master
Bit 1 = 0 reserved
Bit 2
(configured)
=0
Configuration is
unchanged
=1
Configuration is
different to the
manufacturers
parameters
Bit 3 = 0 reserved
Bit 4-7 Extended Device
Status
=0010 at least one faulted I/O
connection
=0011 no I/O connection
established
Bit 8-11 not used
Bit 12- reserved
15 =0
Serial number The last 4 digits of MAC ID
Product name
Common Services
Table 157: Identity (01 hex) – Common service
Service code Service available Service name
Class Instance
01 hex
Yes
Yes
Get_Attribute_All
05 hex
No
Yes
Reset
0E hex
Manual
Version 1.1.0
No
Yes
Description
Supplies contents of all attributes
Implements the reset service
Service parameter
0: Emulates a Power On reset
1: Emulates a Power On reset and reestablishes factory settings
Get_Attribute_Single Supplies contents of the appropriate attribute
188
Table of Contents
11.3.5.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Message Router (02 hex)
The "Message Router Object" provides connection points (in the form of classes
or instances), which can use a client for addressing services (reading, writing).
These messages can be transmitted both when connected and when unconnected
from the client to the fieldbus coupler.
Instance 0 (Class Attributes)
Table 158: Message router (02 hex) – Class
Attribute ID Access Name
1
Get
Revision
2
Get
Number of Attributes
3
Get
Number of Services
4
Get
Max ID Number of
Class Attributes
5
Get
Max ID Number of
Instance Attributes
Data type
UINT
UINT
UINT
UINT
UINT
Description
Revision of this object
Number of attributes
Number of services
Maximum number of class
attributes
Maximum number of
instance attributes
Default value
1 (0x0001)
0 (0x0000)
0 (0x0000)
0 (0x0000)
0 (0x0000)
Note
Get_Attribute_All service can only be used!
The class attributes are only accessible with the Get_Attribute_All service.
Instance 1
Table 159: Message router (02 hex) – Instance 1
Attribute ID Access Name
Data type
1
Get
ObjectList
STRUCT of:
Number
UINT
Classes
2
Get
UINT
NumberAvailable UINT
Description
Number of
implemente
d classes
Implemente
d classes
Maximum
number of
different
connections
Default value
40 (0x0028)
01 00 02 00 04 00 06 00 F4
00 F5 00 F6 00 64 00 65
0066 0067 00 68 00 69 00
6A 00 6B 00 6C 00 6D 00
6E 00 6F 00 70 00 71 00 72
00 73 00 74 00 80 00 81 00
A0 00 A1 00 A2 00 A6 00
A7 00 AA 00 AB 00 A3 00
A4 00 A5 00 A8 00 A9 00
AC 00 AD 00
128 (0x0080)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
189
Common Services
Table 160: Message router (02 hex) – Common service
Service code Service available Service-Name
Description
Class
Instance
01 hex
Yes
No
Get_Attribute_All
Supplies contents of all attributes
0E hex
No
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.6
Assembly Object (04 hex)
By means of the assembly classes, even several diverse objects can be combined.
These could be, for example, input and output data, status and control information
or diagnostic information. WAGO uses the manufacturer-specific instances in
order to provide these objects for you in various arrangements. This gives you an
efficient way to exchange process data. The following is a description of the
individual static assembly instances with their contents and arrangements.
Static Assembly Instances – Overview
Table 161: Static assembly instances – Overview
Instance
Description
Instance 101 (65 hex) for analog and digital output data
Instance 102 (66 hex) for digital output data
Instance 103 (67 hex) for analog output data
Instance 104 (68 hex) for analog and digital input data and status
Instance 105 (69 hex) for digital input data and status
Instance 106 (6A hex) for analog input data and status
Instance 107 (6B hex) for analog and digital input data
Instance 108 (6C hex) for digital input data
Instance 109 (6D hex) for analog input data
Instance 0 (Class Attributes)
Table 162: Assembly (04 hex) – Class
Attribute ID Access Name
Data type
1
Get
Revision UINT
Description
Revision of this object
Default value
2 (0x0002)
Instance 101 (65hex)
This assembly instance contains analog and digital output data.
Table 163: Static assembly instances – Instance 101 (65 hex)
Attribute ID Access Name Data type
Description
3
Get/Set Data
ARRAY of BYTE Reference on the process
image: analog and digital
output data
Manual
Version 1.1.0
Default value
-
190
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Instance 102 (66hex)
This assembly instance contains digital output data only.
Table 164: Static assembly instances – Instance 102 (66 hex)
Attribute ID Access Name Data type
Description
3
Get/Set Data
ARRAY of BYTE Reference on the process
image: only digital output
data
Default value
-
Instance 103 (67hex)
This assembly instance contains analog output data only.
Table 165: Static assembly instances – Instance 103 (67 hex)
Attribute ID Access Name Data type
Description
3
Get/Set Data
ARRAY of BYTE Reference of the process
image: only analog output
data
Default value
-
Instance 104 (68hex)
This assembly instance contains analog and digital input data and the status only.
Table 166: Static assembly instances – Instance 104 (68 hex)
Attribute ID Access Name
Data type
Description
3
Get
Data
ARRAY of BYTE Reference of the process
image: analog and digital
input data + Status
Default value
-
Instance 105 (69hex)
This assembly instance contains digital input data and the status only.
Table 167: Static assembly instances – Instance 105 (69 hex)
Attribute ID Access Name
Data type
Description
Default value
3
Get
Data
ARRAY of BYTE Reference of the process
image: only digital input data
+ Status
Instance 106 (6Ahex)
This assembly instance contains analog input data and the status only.
Table 168: Static assembly instances – Instance 106 (6A hex)
Attribute ID Access Name
Data type
Description
Default value
3
Get
Data
ARRAY of BYTE Reference of the process
image: only analog input data
+ Status
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
191
Instance 107 (6Bhex)
This assembly instance contains analog and digital input data.
Table 169: Static assembly instances – Instance 107 (6B hex)
Attribute ID Access Name
Data type
Description
3
Get
Data
ARRAY of BYTE Reference of the process
image: analog and digital
input data
Default value
-
Instance 108 (6Chex)
This assembly instance contains digital input data.
Table 170: Static assembly instances – Instance 108 (6C hex)
Attribute ID Access Name
Data type
Description
Default value
3
Get
Data
ARRAY of BYTE Reference of the process
image: only digital input data
Instance 109 (6Dhex)
This assembly instance contains analog input data.
Table 171: Static assembly instances – Instance 109 (6C hex)
Attribute ID Access Name
Data type
Description
Default value
3
Get
Data
ARRAY of BYTE Reference of the process
image: only analog input data
Instance 198 (C6 hex) “Input Only”
This instance is used to establish a connection when no outputs are to be
addressed or when inputs, which are already being used in an exclusive owner
connection, are to be interrogated. The data length of this instance is always zero.
This instance can only be used in the “consumed path” (seen from the slave
device).
Instance 199 (C7 hex) “Listen only”
This instance is used to establish a connection based on an existing exclusive
owner connection. The new connection also has the same transmission parameters
as the exclusive owner connection. When the exclusive owner connection is
cleared, this connection, too, is automatically cleared. The data length of this
instance is always zero.
This instance can only be used in the “consumed path” (from the point of view of
the slave device).
Manual
Version 1.1.0
192
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Common Service
Table 172: Static assembly instances – Common service
Service code Service available Service name
Description
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
The software inspects the writing of attribute 3 of assembly instances 101, 102
and 103. If the limit value has been exceeded, it is identified and, if necessary,
corrected. However, a write request is not rejected. This means that if less data is
received than expected, only this data is written. If more data is received than
expected, the received data at the upper limit is deleted. In the case of explicit
messages, however, a defined CIP is generated even though the data has been
written.
11.3.5.7
Connection (05 hex)
Because the connections are established and terminated via the connection
manager, the class and instance attributes of this class are not visible.
11.3.5.8
Connection Manager (06 hex)
The "Connection Manager Object" provides the internal resources that are
required for the input and output data and explicit messages. In addition, the
administration of this resource is an assignment of the "Connection Manager
Object".
For each connection (input and output data or explicit), another instance of the
connection class is created. The connection parameters are extracted from the
"Forward Open" service, which is responsible for establishing a connection.
The following services are supported for the first instance:
•
Forward_Open
•
Unconnected_Send
•
Forward_Close
No class and instance attributes are visible.
11.3.5.9
Port Class (F4 hex)
The "Port Class Object" specifies the existing CIP ports on the fieldbus
coupler/coupler. There is one instance for each CIP port.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
193
Instance 0 (Class Attributes)
Table 173: Port class (F4 hex) – Class
Attribute ID Access Name
1
Get
Revision
2
Get
Max Instance
3
Get
Num Instances
8
Get
Entry Port
9
Get
All Ports
Data type
UINT
UINT
UINT
UINT
Array of
Struct
UINT
Description
Revision of this object
Max. number of instances
Number of current ports
Instance of the port object
where the request arrived.
Array with instance attributes
1 and 2 of all instances
Default value
1 (0x0001)
1 (0x0001)
1 (0x0001)
1 (0x0001)
0 (0x0000)
0 (0x0000)
4 (0x0004)
2 (0x0002)
Instance 1
Table 174: Port class (F4 hex) – Instance 1
Attribute ID Access NV Name
1
Get
V Port Type
2
Get
V Port Number
Data type Description
UINT
UINT
CIP port number
3
UINT
Get
V
Port Object
Padded
EPATH
4
Get
V
7
Get
V
Port Name
SHORT_
STRING
Node Address Padded
EPATH
Number of 16 bit
words in the
following path
Object, which
manages this port
Port name
Port segment (IP
address)
Default value
4 (0x0004)
2 (0x0002)
(EtherNet/IP)
2 (0x0002)
0x20 0xF5
0x24 0x01
(equals TCP/IP
Interface Object)
“”
Depends on IP address
Common Services
Table 175: Port class (F4 hex) – Common service
Service code Service available Service-Name
Description
Class Instance
01 hex
Yes
Yes
Get_Attribute_All
Supplies contents of all attributes
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate attribute
Manual
Version 1.1.0
194
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.5.10 TCP/IP Interface (F5 hex)
The "TCP/IP Interface Object" provides for the configuration of the TCP/IP
network interface of a fieldbus coupler/controller. Examples of configurable
objects include the IP address, the network mask and the gateway address of the
fieldbus coupler/controller.
The underlying physical communications interface that is connected with the
TCP/IP interface object can be any interface supported by the TCP/IP protocol.
Examples of components that can be connected to a TCP/IP interface object
include the following: an Ethernet interface 802.3, an ATM (Asynchronous
Transfer Mode) interface or a serial interface for protocols such as PPP (Point-toPoint Protocol).
The TCP/IP interface object provides an attribute, which is identified by the linkspecific object for the connected physical communications interface. The linkspecific object should typically provide link-specific counters as well as any linkspecific configuration attributes.
Each device must support exactly one instance of the TCP/IP interface object for
each TCP/IP-compatible communications interface. A request for access to the
first instance of the TCP/IP interface object must always refer to the instance
connected with the interface, which is used to submit the request.
Instance 0 (Class Attributes)
Table 176: TCP/IP interface (F5hex) – Class
Attribute
Access Name
Data type
ID
1
Get
Revision
UINT
2
Get
Max Instance
UINT
3
Get
Num Instances UINT
Description
Revision of this object
Max. number of instances
Number of the current
instanced connections
Default
value
1 (0x0001)
1 (0x0001)
1 (0x0001)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
195
Instance 1
Table 177: TCP/IP interface (F5hex) – Instance 1
Attribute ID Access NV Name
Data type Description
1
2
Get
Get
3
Set
4
Get
V
V
Status
DWORD
Configuration DWORD
Capability
NV Configuration DWORD
Control
V
Physical Link STRUCT
Object
of
Path size
UINT
Path
5
6
Set
Set
NV Interface
Configuration
IP Address
Network
Mask
Gateway
Address
Name Server
Name Server
2
Domain
Name
NV Host Name
Padded
EPATH
Default
value
0x00000017
Interface state
Interface flags for possible
kinds of configuration
Specifies, how the device gets 0x00000011
is TCP/IP configuration after
the first Power On
Number of 16 Bit words in
the following path
Logical path, which points to
the physical Link object
0x0002
0x20 0xF6
0x24 0x03
(equates to
the Ethernet
Link Object)
STRUCT
of
UDINT
UDINT
IP address
Net work mask
UDINT
IP address of default gateway 0
UDINT
0
STRING
IP address of the primary
name of the server
IP address of the secondary
name of the server
Default domain name
STRING
Device name
“”
UDINT
0
0
0
“”
Common Services
Table 178: TCP/IP interface (F5hex) – Common service
Service code Service available Service name
Class Instance
01 hex
Yes
Yes
Get_Attribute_All
0E hex
Yes
Yes
Get_Attribute_Single
10 hex
No
Yes
Set_Attribute_Single
Manual
Version 1.1.0
Description
Supplies contents of all attributes
Supplies contents of the appropriate attribute
Modifies an attribute value
196
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.5.11 Ethernet Link (F6 hex)
The "Ethernet Link Object" contains link-specific counter and status information
for an Ethernet 802.3 communications interface. Each device must support exactly
one instance of the Ethernet Link Object for each Ethernet IEEE 802.3
communications interface on the module. An Ethernet link object instance for an
internal interface can also be used for the devices, e.g. an internal port with an
integrated switch.
Instance 0 (Class Attributes)
Table 179: Ethernet link (F5hex) – Class
Attribute ID Access Name
1
Get
Revision
2
Get
Max Instance
3
Get
Num Instances
Data type
UINT
UDINT
UDINT
Description
Revision of this object
Max. number of instances
Number of the current
instanced connections
Default value
3 (0x0003)
3 (0x0003)
3 (0x0003)
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
197
Instance 1
Table 180: Ethernet link (F6 hex) – Instance 1
Attribute ID Access Name
Data type Description
1
Get
Interface Speed
UDINT
Transfer rate
Manual
Version 1.1.0
2
Get
Interface Flags
3
Get
6
Set
Physical Address ARRAY
of 6
UINTs
Interface Control STRUCT
of:
Control Bits
WORD
7
Get
Forced Interface
Speed
Interface Type
8
Get
Interface Status
DWORD
UINT
USINT
USINT
Default value
10 (0x0A) or
100 (0x64)
Interface configuration Value is dependent
and status information upon Ethernet
Bit 0: Link status
connection.
Bit 1: Half/full lduplex
Bit 2…4: Detection
status
Bit 5: Manual settings
require reset
Bit 6: Local hardware
error
Bit 7…31: Reserved
MAC layer address
MAC ID of the
device
Configuration of the
physical interface
Interface configuration 0x0001
bits
Bit 0: Automatic
detection
Bit 1: Default duplex
mode
Bit 2…15: Reserved
Preset interface speed 10 (0x000A) or
100 (0x0064)
Interface type
2 (0x02) – Twisted
Value 0: Unknown
Pair
Value 1: Internal
interface; e.g., in the
case of an integrated
switch
Value 2: Twisted pair
(e.g. 100Base-TX).
Value 3: fiber glass
(e.g. 100Base-FX).
Value 4…256:
Reserved
Interface status
Value 0: Unknown
Value 1: Interface
active and ready to
send/receive.
Value 2: Interface
deactivated.
Value 3: Interface is
testing
Wert 4…256:
Reserved
198
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 180: Ethernet link (F6 hex) – Instance 1
Attribute ID Access Name
Data type Description
Default value
9
Get/
Admin Status
USINT
Admin status:
1 (0x01)
Set
Value 0: Reserved
Value 1: Interface
active
Value 2: Interface
deactivated. Is this the
only CIP interface, a
request for
deactivation will be
receipted with error
code 0x09
Value 3…256:
Reserved
10
Get
Interface Label
SHORT_ Name of the interface “Port 1“
STRING
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
199
Instance 2 – Port 2
Table 181: Ethernet link (F6 hex) – Instance 2
Attribute ID Access Name
Data type Description
1
Get
Interface Speed
UDINT
Transfer rate
Manual
Version 1.1.0
2
Get
Interface Flags
3
Get
6
Set
Physical Address ARRAY
of 6
UINTs
Interface Control STRUCT
of:
Control Bits
WORD
7
Get
Forced Interface
Speed
Interface Type
8
Get
Interface Status
DWORD
UINT
USINT
USINT
Default value
10 (0x0000000A) or
100 (0x00000064)
Interface configuration Value is dependent
and status information upon Ethernet
Bit 0: Link status
connection.
Bit 1: Half/full lduplex
Bit 2…4: Detection
status
Bit 5: Manual settings
require reset
Bit 6: Local hardware
error
Bit 7…31: Reserved
MAC layer address
MAC-ID des
Fieldbus couplers/
controllers
Configuration of the
physical interface
Interface configuration 0x0001
bits
Bit 0: Automatic
detection
Bit 1: Default duplex
mode
Bit 2…15: Reserved
Preset interface speed 10 (0x000A) or
100 (0x0064)
Interface type
2 (0x02) – Twisted
Value 0: Unknown
Pair
Value 1: Internal
interface; e.g., in the
case of an integrated
switch
Value 2: Twisted pair
(e.g. 100Base-TX).
Value 3: fiber glass
(e.g. 100Base-FX).
Value 4…256:
Reserved
Interface status
Value 0: Unknown
Value 1: Interface
active and ready to
send/receive.
Value 2: Interface
deactivated.
Value 3: Interface is
testing
Wert 4…256:
Reserved
200
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 181: Ethernet link (F6 hex) – Instance 2
Attribute ID Access Name
Data type Description
Default value
9
Get/
Admin Status
USINT
Admin status:
1 (0x01)
Set
Value 0: Reserved
Value 1: Interface
active
Value 2: Interface
deactivated. Is this the
only CIP interface, a
request for
deactivation will be
receipted with error
code 0x09
Value 3…256:
Reserved
10
Get
Interface Label
SHORT_ Name of the interface “Port 2“
STRING
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
201
Instance 3 – Internal Port 3
Table 182: Ethernet link (F6 hex) – Instance 3
Attribute ID Access Name
Data type
1
Get
Interface Speed
UDINT
2
Get
Interface Flags
DWORD
3
Get
6
Set
Physical Address ARRAY of 6
UINTs
Interface Control STRUCT of:
Description
Transfer rate
Interface
configuration and
status information
MAC layer address
Configuration of the
physical interface
Interface
configuration bits
Control Bits
WORD
UINT
Baud rate
UINT
Interface type
UINT
UINT
SHORT_
STRING
Interface status
Admin status
Name of the
interface
7
Get
Forced Interface
Speed
Interface Type
8
9
10
Get
Get
Get
Interface Status
Admin Status
Interface Label
Default value
100 (0x64)
3 (0x03) – Link
active (Bit 0),
Full duplex (Bit 1)
MAC ID of the
device
3 (0x03) – Link
active (Bit 0),
Full duplex (Bit 1)
100 (0x64)
1 (0x01) – internal
Port
1 (0x01) – active
1 (0x01) – active
„Internal Port 3“
Common Services
Table 183: Ethernet link (F6 hex) – Common service
Service code Service available Service-Name
Class Instance
01 hex
Yes
Yes
Get_Attribute_All
0E hex
Yes
Yes
Get_Attribute_Single
10 hex
No
Yes
Set_Attribute_Single
Description
Supplies contents of all attributes
Supplies contents of the appropriate attribute
Modifies an attribute value
Note
Changes with service ”Set_Attribute_Single“ not directly effective!
Attributes (particularly the attributes 6 and 9) which were changed over the
service “Set_Attribute_Single“, become only effective after the next Power-OnReset of the controller.
Manual
Version 1.1.0
202
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
11.3.5.12 Coupler/Controller Configuration (64 hex)
The fieldbus coupler configuration class allows reading and configuration of some
important fieldbus/controller process parameters. The following listings explain in
details all supported instances and attributes.
Instance 0 (Class Attributes)
Table 184: Coupler/Controller configuration (64 hex) – Class
Attribute ID Access Name
Data type Description
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance UINT
Max. number of instances
Default value
1 (0x0001)
1 (0x0001)
Instance 1
Table 185: Coupler/Controller configuration (64 hex) – Instance 1
Attribute ID Access NV Name
Data type Description
5 (0x05)
Get
V
ProcessState USINT
6 (0x06)
Get
V
DNS_i_
Trmnldia
7 (0x07)
Get
V
8 (0x08)
Get
9 (0x09)
Get
10 (0x0A)
Get
11 (0x0B)
Set
CnfLen.
AnalogOut
V CnfLen.
AnalogInp
V CnfLen.
DigitalOut
V CnfLen.
DigitalInp
NV Bk_Fault_
Reaction
UINT
UINT
UINT
UINT
UINT
USINT
State of coupler/controller, error
mask:
Bit 0: Internal bus error
Bit 3: Module diagnostics (0x08)
Bit 7: Fieldbus error (0x80)
Module diagnostics:
Bit 0..7: Module number
Bit 8..14: Module channel
Bit 15: 0/1 Error, repair/arisen
Number of I/O bits for the analog
output
Number of I/O bits for the analog
input
Number of I/O bits for the digital
output
Number of I/O bits for the digital
input
Fieldbus error reaction
0: stop local I/O cycles
1: set all output to 0
2: no error reaction
3: no error reaction
4: PFC task takes over control of
the outputs (apply to controllers)
12..26
Reserved for compatibility to DeviceNet
(0x0C...0x1A)
40..43
Reserved for compatibility to DeviceNet
(0x28...0x2B)
45 (0x2D)
Get
V Bk_Led_Err UINT
I/O LED error code
_Code
46 (0x2E)
Get
V Bk_Led_Err UINT
I/O LED error argument
_Arg
Default
value
0
0
1
0
0
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
120 (0x78)
Set
NV Bk_Header
CfgOT
UINT
121(0x79)
Set
NV Bk_Header
CfgTO
UINT
Indicates whether the
RUN/IDLE header is used
originator  target direction
0: is used
1: is not used
Indicates whether the
RUN/IDLE header is used
originator  target direction
0: is used
1: is not used
203
0x0000
0x0001
Common Service
Table 186: Coupler/Controller configuration (64 hex) – Common service
Service code Service available Service name
Description
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.13 Discrete Input Point (65 hex)
This class allows the reading of data of a particular digital input point.
Instance 0 (Class-Attributes)
Table 187: Discrete input point (65 hex) – Class
Attribute ID Access Name
Data type Description
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default value
1 (0x0001)
-
Instance 1 ... 255 (Digital output value 1 up to 255)
Table 188: Discrete input point (65 hex) – Instance 1...255
Attribute ID Access Name
Data type Description
1
Get
DipObj_Value BYTE
Digital output (only Bit 0 is
valid)
Default value
-
Common Services
Table 189: Discrete input point (65 hex) – Common service
Service code Service available Service name
Description
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate attribute
11.3.5.14 Discrete Input Point Extended 1 (69 hex)
The extension of the "Discrete Input Point" class enables the reading of data from
a fieldbus node that contains over 255 digital input points (DIPs). The instance
Manual
Version 1.1.0
204
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
scope of the "Discrete Input Point Extended 1" class covers DIPs from 256 to 510
in the fieldbus node.
Instance 0 (Class Attributes)
Table 190: Discrete Input Point Extended 1(69 hex,) – Class
Attribute ID Access Name
Data type Description
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance UINT
Max. number of instances
Default value
1 (0x0001)
-
Instance 256 ... 510 (Digital input value 256 up to 510)
Table 191: Discrete output point (66 hex) – Instance 256...510
Attribute ID Access Name
Data type Description
1
Get
DipObj_Value BYTE
Digital input
(only Bit 0 is valid)
Default value
-
Common Services
Table 192: Discrete Input Point Extended 1 (69 hex) – Common service
Service
Service available
Service-name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.15 Discrete Input Point Extended 2 (6D hex)
The extension of the "Discrete Input Point" class enables the reading of data from
a fieldbus node that contains over 510 digital input points (DIPs). The instance
scope of the "Discrete Input Point Extended 2" class covers DIPs from 511 to 765
in the fieldbus node.
Instance 0 (Class Attributes)
Table 193: Discrete Input Point Extended 2 (6D hex) – Class
Attribute ID Access Name
Data type Description
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default value
1 (0x0001)
-
Instance 511 ... 765 (Digital input value 511 up to 765)
Table 194: Analog input point (67 hex) – Instance 1
Attribute ID Access Name
Data type Description
1
Get
AipObj_Value
ARRAY Analog input
of BYTE
2
Get
AipObj_Value_Length USINT
Length of the input data
AipObj_Value (in byte)
Default value
-
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
205
Common Services
Table 195: Analog input point (67 hex) – Common service
Service code Service available Service name
Description
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate attribute
11.3.5.16 Discrete Input Point Extended 3 (71 hex)
The extension of the "Discrete Input Point" class enables the reading of data from
a fieldbus node that contains over 765 digital input points (DIPs). The instance
scope of the "Discrete Input Point Extended 3" class covers DIPs from 766 to
1020 in the fieldbus node.
Instance 0 (Class-Attributes)
Table 196: Discrete Input Point Extended 3 (71 hex) – Class
Attribute ID Access Name
Data type Description
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default value
1 (0x0001)
-
Instance 766 ... 1020 (Digital input value 766 up to 1020)
Table 197: Discrete Input Point Extended 3 (71 hex) – Instance 766...1020
Attribute
Access Name
Data type Description
ID
1
Get
DipObj_Value BYTE
Digital input
(only Bit 0 is valid)
Default value
-
Common Services
Table 198: Discrete Input Point Extended 3 (71 hex) – Common service
Service
Service available
Service-Name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.17 Discrete Output Point (66 hex)
This class enables data exchange for a particular digital output point.
Instance 0 (Class Attributes)
Table 199: Discrete Output Point (66 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Manual
Version 1.1.0
Default
value
1 (0x0001)
-
206
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Instance 1 ... 255 (Digital output value 1 up to 255)
Table 200: Discrete Output Point (66 hex) – Instance 1...255
Attribute
Access Name
Data type Description
ID
1
Get
DopObj_Value BYTE
Digital Output
(only Bit 0 valid)
Default
value
-
Common Services
Table 201: Discrete Output Point (66 hex) – Common service
Service
Service available
Service-Name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.18 Discrete Output Point Extended 1 (6A hex)
The extension of the "Discrete Output Point" class enables the exchange of data
from a fieldbus node that contains over 255 digital output points (DOPs). The
instance scope of the "Discrete Output Point Extended 1" class covers DOPs from
256 to 510 in the fieldbus node.
Instance 0 (Class Attributes)
Table 202: Discrete Output Point Extended 1 (6A hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 256 ... 510 (Digital output value 256 up to 510)
Table 203: Discrete Output Point Extended 1 (6A hex) – Instance 256...510
Attribute
Access Name
Data type Description
ID
1
Get
DopObj_Value BYTE
Digital Output
(only Bit 0 valid)
Default
value
-
Common Services
Table 204: Discrete Output Point Extended 1 (6A hex) – Common service
Service
Service available
Service-Name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
207
11.3.5.19 Discrete Output Point Extended 2 (6E hex)
The extension of the "Discrete Output Point" class enables the exchange of data
from a fieldbus node that contains over 510 digital output points (DOPs). This
instance cope of the "Discrete Output Point Extended 1" class covers the DOPs
from 511 to 765 in the fieldbus node.
Instance 0 (Class Attributes)
Table 205: Discrete Output Point Extended 2 (6E hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 511 ... 765 (Digital output value 511 up to 765)
Table 206: Discrete Output Point Extended 2 (6E hex) – Instance 511...765
Attribute
Access Name
Data type Description
ID
1
Get
DopObj_Value BYTE
Digital Output
(only Bit 0 valid)
Default
value
-
Common Services
Table 207: Discrete Output Point Extended 2 (6E hex) – Common service
Service
Service available
Service-Name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.20 Discrete Output Point Extended 3 (72 hex)
The extension of the "Discrete Output Point" class enables the exchange of data
from a fieldbus node that contains over 765 digital output points (DOPs). The
instance scope of the "Discrete Output Point Extended 2" class covers DOPs from
766 to 1020 in the fieldbus node.
Instance 0 (Class Attributes)
Table 208: Discrete Output Point Extended 3 (72 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Manual
Version 1.1.0
Default
value
1 (0x0001)
-
208
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Instance 766 ... 1020 (Digital Output value 766 up to 1020)
Table 209: Discrete Output Point Extended 3 (72 hex) – Instance 766...1020
Attribute
Access Name
Data type Description
ID
1
Get
DopObj_Value BYTE
Digital Output
(only Bit 0 valid)
Default
value
-
Common Services
Table 210: Discrete Output Point Extended 2 (6E hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.21 Analog Input Point (67 hex)
This class enables the reading of data of a particular analog input point (AIP). An
analog input point is part of an analog input module.
Instance 0 (Class Attributes)
Table 211: Analog Input Point (67 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 1 ... 255 (Analog input 1 up to 255)
Table 212: Analog Input Point (67 hex) – Instance 1 ... 255
Attribute
Access Name
Data type Description
ID
1
Get
AipObj_Value ARRAY Analog Input
of BYTE
2
Get
AipObj_Value_ USINT
Length of the output data
Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 213: Analog Input Point (67 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
209
11.3.5.22 Analog Input Point Extended 1 (6B hex)
The extension of the "Analog Input Point" class enables the reading of data from a
fieldbus node that contains over 255 analog outputs (AIPs). The instance scope of
the "Analog Input Point Extended 1" class covers AIPs from 256 to 510 in the
fieldbus node.
Instance 0 (Class Attributes)
Table 214: Analog Input Point Extended 1 (6B hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 256 ... 510 (Analog Input value 256 up to 510)
Table 215: Analog Input Point Extended 1 (6B hex) – Instance 256 ... 510
Attribute
Access Name
Data type Description
ID
1
Get
AipObj_Value ARRAY Analog Input
of BYTE
2
Get
AipObj_Value_ USINT
Length of the output data
Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 216: Analog Input Point Extended 1 (6B hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.23 Analog Input Point Extended 2 (6F hex)
The extension of the "Analog Input Point" class enables the reading of data from a
fieldbus node that contains over 510 analog outputs (AIPs). The instance scope of
the "Analog Input Point Extended 2" class covers AIPs from 511 to 765 in the
fieldbus node.
Instance 0 (Class Attributes)
Table 217: Analog Input Point Extended 2 (6F hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Manual
Version 1.1.0
Default
value
1 (0x0001)
-
210
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Instance 511 ... 765 (Analog Input 511 up to 765)
Table 218: Analog Input Point Extended 2 (6F hex) – Instance 511 ... 765
Attribute
Access Name
Data type Description
ID
1
Get
AipObj_Value ARRAY Analog Input
of BYTE
2
Get
AipObj_Value_ USINT
Length of the output data
Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 219: Analog Input Point Extended 2 (6F hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.24 Analog Input Point Extended 3 (73 hex)
The extension of the "Analog Input Point" class enables the reading of data from a
fieldbus node that contains over 765 analog outputs (AIPs). The instance scope of
the "Analog Input Point Extended 3" class covers AIPs from 766 to 1020 in the
fieldbus node.
Instance 0 (Class Attributes)
Table 220: Analog Input Point Extended 3 (73 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 766 ... 1020 (Analog input value 766 up to 1020)
Table 221: Analog Input Point Extended 3 (73 hex) – Instance 766 ... 1020
Attribute
Access Name
Data type Description
ID
1
Get
AipObj_Value ARRAY Analog Input
of BYTE
2
Get
AipObj_Value_ USINT
Length of the output data
Length
AopObj_Value (in byte)
Default
value
-
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
211
Common Services
Table 222: Analog Input Point Extended 3 (73 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
11.3.5.25 Analog Output Point (68 hex)
This class enables the reading of data of a particular analog output point (AOP).
An analog output point is part of an analog output module.
Instance 0 (Class Attributes)
Table 223: Analog Output Point (68 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 1 ... 255 (Analog output value 1 up to 255)
Table 224: Analog Output Point (68 hex) – Instance 1...255
Attribute
Access Name
Data type Description
ID
1
Get
AopObj_Value ARRAY Analog Output
of BYTE
2
Get
AopObj_Value USINT
Length of the output data
_Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 225: Analog Output Point (68 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.26 Analog Output Point Extended 1 (6C hex)
The extension of the "Analog Output Point" class enables the exchange of data
from a fieldbus node that contains over 255 analog output points (AOPs). The
instance scope of the "Discrete Output Point Extended 1" class covers AOPs from
256 to 510 in the fieldbus node.
Manual
Version 1.1.0
212
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Instance 0 (Class Attributes)
Table 226: Analog Output Point Extended 1 (6C hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 256 ... 510 (Analog output value 256 up to 510)
Table 227: Analog Output Point Extended 1 (6C hex) – Instance 256...510
Attribute
Access Name
Data type Description
ID
1
Get
AopObj_Value ARRAY Analog Output
of BYTE
2
Get
AopObj_Value USINT
Length of the output data
_Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 228: Analog Output Point Extended 1 (6C hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.27 Analog Output Point Extended 2 (70 hex)
The extension of the "Analog Output Point" class enables the exchange of data
from a fieldbus node that contains over 510 analog output points (AOPs). The
instance scope of the "Discrete Output Point Extended 2" class covers AOPs from
511 to 765 in the fieldbus node.
Instance 0 (Class Attributes)
Table 229: Analog Output Point Extended 2 (70 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
213
Instance 511 ... 765 (Analog output value 511 up to 765)
Table 230: Analog Output Point Extended 2 (70 hex) – Instance 511...765
Attribute
Access Name
Data type Description
ID
1
Get
AopObj_Value ARRAY Analog Output
of BYTE
2
Get
AopObj_Value USINT
Length of the output data
_Length
AopObj_Value (in byte)
Default
value
-
Common Services
Table 231: Analog Output Point Extended 2 (70 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.28 Analog Output Point Extended 3 (74 hex)
The extension of the "Analog Output Point" class enables the exchange of data
from a fieldbus node that contains over 765 analog output points (AOPs). The
instance scope of the "Discrete Output Point Extended 3" class covers AOPs from
766 to 1020 in the fieldbus node.
Instance 0 (Class Attributes)
Table 232: Analog Output Point Extended 3 (74 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 766 ... 1020 (Analog output value 766 up to 1020)
Table 233: Analog Output Point Extended 3 (74 hex) – Instance 766...1020
Attribute
Access Name
Data type Description
ID
1
Get
AopObj_Value ARRAY Analog Output
of BYTE
2
Get
AopObj_Value USINT
Length of the output data
_Length
AopObj_Value (in byte)
Manual
Version 1.1.0
Default
value
-
214
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Common Services
Table 234: Analog Output Point Extended 3 (74 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
10 hex
No
Yes
Set_Attribute_Single Modifies an attribute value
11.3.5.29 Module Configuration (80 hex)
Instance 0 (Class Attributes)
Table 235: Module Configuration (80 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 1 … 255 (Clamp 0 up to 254)
Table 236: Module Configuration (80 hex) – Instance 1...255
Attribute
Access Name
Data type Description
Default
ID
value
1
Get
ModulDescription WORD
Description of connected
modules (module 0 =
coupler/controller)
Bit 0:
Module has inputs
Bit 1:
Module has outputs
Bit 8-14: Data width internally in
bit 15: 0/1 Analog/digital
module
For analog modules, bits 0-14
identify the module type, e.g.,
401 for module 750-401
Common Services
Table 237: Module Configuration (80 hex) – Common service
Service
Service available
Service name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
215
11.3.5.30 Module Configuration Extended (81 hex)
The same as "Module Configuration (80 hex)" but with a description of module
255.
Instance 0 (Class Attributes)
Table 238: Module Configuration Extended (81 hex) – Class
Attribute
Access Name
Data type Description
ID
1
Get
Revision
UINT
Revision of this object
2
Get
Max Instance
UINT
Max. number of instances
Default
value
1 (0x0001)
-
Instance 256 (Clamp 255)
Table 239: Module Configuration Extended (81 hex) – Instance 256
Attribute
Access Name
Data type Description
Default
ID
value
1
Get
ModulDescription WORD
Description of connected
modules (module 0 =
coupler/controller)
Bit 0:
Module has inputs
Bit 1:
Module has outputs
Bit 8-14: Data width internally in
Bit 15: 0/1 Analog/digital
module
For analog modules, bits 0-14
identify the module type, e.g.,
401 for module 750-401
Common Services
Table 240: Module Configuration Extended (81 hex) – Common service
Service
Service available
Service-Name
Description
code
Class Instance
0E hex
Yes
Yes
Get_Attribute_Single Supplies contents of the appropriate
attribute
Manual
Version 1.1.0
216
Table of Contents
12
I/O Modules
12.1
Overview
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
For modular applications with the WAGO-I/O-SYSTEM 750, different types of
I/O modules are available
•
Digital Input Modules
•
Digital Output Modules
•
Analog Input Modules
•
Analog Output Modules
•
Special Modules
•
System Modules
For detailed information on the I/O modules and the module variations, please
refer to the manuals for the I/O modules.
You will find these manuals on DVD ROM "AUTOMATION Tools and Docs"
(Item-no.: 0888-0412) or on the WAGO web pages under www.wago.com 
Service  Download  Documentation.
Information
More Information about the WAGO-I/O-SYSTEM
Current information on the modular WAGO-I/O-SYSTEM is available in the
Internet under: http://www.wago.com
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2
Table of Contents
217
Process Data Architecture for MODBUS/TCP
With some I/O modules, the structure of the process data is fieldbus specific.
In the case of a fieldbus coupler with MODBUS/TCP, the process image uses a
word structure (with word alignment). The internal mapping method for data
greater than one byte conforms to the Intel format.
The following section describes the process image for various WAGO-I/OSYSTEM 750 and 753 I/O modules when using a fieldbus coupler with
MODBUS/TCP.
NOTICE
Equipment damage due to incorrect address!
Depending on the specific position of an I/O module in the fieldbus node, the
process data of all previous byte or bit-oriented modules must be taken into
account to determine its location in the process data map.
Manual
Version 1.1.0
218
Table of Contents
12.2.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Digital Input Modules
Digital input modules supply one bit of data per channel to specify the signal state
for the corresponding channel. These bits are mapped into the Input Process
Image.
Some digital modules have an additional diagnostic bit per channel in the Input
Process Image. The diagnostic bit is used for detecting faults that occur (e.g., wire
breaks and/or short circuits).
When analog input modules are also present in the node, the digital data is always
appended after the analog data in the Input Process Image, grouped into bytes.
12.2.1.1
1 Channel Digital Input Module with Diagnostics
750-435
Table 241: 1 Channel Digital Input Module with Diagnostics
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
12.2.1.2
Bit 2
Bit 1
Diagnostic
bit
S1
Bit 0
Data bit
DI 1
2 Channel Digital Input Modules
750-400, -401, -405, -406, -410, -411, -412, -427, -438, (and all variations),
753-400, -401, -405, -406, -410, -411, -412, -427
Table 242: 2 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
12.2.1.3
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
DI 2
DI 1
Channel 2 Channel 1
2 Channel Digital Input Module with Diagnostics
750-419, -421, -424, -425,
753-421, -424, -425
Table 243: 2 Channel Digital Input Module with Diagnostics
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Data bit
Data bit
bit S 2
bit S 1
DI 2
DI 1
Channel 2 Channel 1 Channel 2 Channel 1
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.1.4
Table of Contents
219
2 Channel Digital Input Module with Diagnostics and Output Process
Data
750-418,
753-418
The digital input module supplies a diagnostic and acknowledge bit for each input
channel. If a fault condition occurs, the diagnostic bit is set. After the fault
condition is cleared, an acknowledge bit must be set to re-activate the input. The
diagnostic data and input data bit is mapped in the Input Process Image, while the
acknowledge bit is in the Output Process Image.
Table 244: 2 Channel Digital Input Module with Diagnostics and Output Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Data bit Data bit
bit S 2
bit S 1
DI 2
DI 1
Channel 2 Channel 1 Channel 2 Channel 1
Output Process Image
Bit 7
Bit 6
Bit 5
12.2.1.5
Bit 4
Bit 3
Bit 2
Acknowledge- Acknowledgement bit Q 2
ment bit Q 1
Channel 2
Channel 1
Bit 1
Bit 0
0
0
4 Channel Digital Input Modules
750-402, -403, -408, -409, -414, -415, -422, -423, -428, -432, -433, -1420, -1421,
-1422
753-402, -403, -408, -409, -415, -422, -423, -428, -432, -433, -440
Table 245: 4 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
12.2.1.6
Bit 3
Data bit
DI 4
Channel 4
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
DI 3
DI 2
DI 1
Channel 3 Channel 2 Channel 1
8 Channel Digital Input Modules
750-430, -431, -436, -437, -1415, -1416, -1417
753-430, -431, -434
Table 246: 8 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
DI 8
DI 7
DI 6
DI 5
DI 4
DI 3
DI 2
DI 1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
Manual
Version 1.1.0
220
Table of Contents
12.2.1.7
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
16 Channel Digital Input Modules
750-1400, -1402, -1405, -1406, -1407
Table 247: 16 Channel Digital Input Modules
Input Process Image
Bit 15 Bit 14Bit 13Bit 12Bit 11Bit 10Bit 9 Bit 8 Bit 7 Bit 6
Data Data Data Data Data Data Data Data Data Data
bit bit DI bit
bit
bit bit bit bit bit bit
DI 16 DI 15 DI 14 DI 13 DI 12 DI 11 DI 10 DI 9 8 DI 7
Chann Chan Chan Chan Chan Chan Chann Chan Chan Chan
el 16 nel 15 nel 14 nel 13 nel 12 nel 11 el 10 nel 9 nel 8 nel 7
Bit 5
Data
bit
DI 6
Chan
nel 6
Bit 4
Data
bit
DI 5
Chan
nel 5
Bit 3
Data
bit
DI 4
Chan
nel 4
Bit 2
Data
bit
DI 3
Chan
nel 3
Bit 1
Data
bit
DI 2
Chan
nel 2
Bit 0
Data
bit
DI 1
Chan
nel 1
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.2
Table of Contents
221
Digital Output Modules
Digital output modules use one bit of data per channel to control the output of the
corresponding channel. These bits are mapped into the Output Process Image.
Some digital modules have an additional diagnostic bit per channel in the Input
Process Image. The diagnostic bit is used for detecting faults that occur (e.g., wire
breaks and/or short circuits). For modules with diagnostic bit is set, also the data
bits have to be evaluated.
When analog output modules are also present in the node, the digital image data is
always appended after the analog data in the Output Process Image, grouped into
bytes.
12.2.2.1
1 Channel Digital Output Module with Input Process Data
750-523
The digital output modules deliver 1 bit via a process value Bit in the output
process image, which is illustrated in the input process image. This status image
shows "manual mode".
Table 248: 1 Channel Digital Output Module with Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
not used
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
not used
12.2.2.2
Bit 0
Status bit
“Manual
Operation“
Bit 0
controls
DO 1
Channel 1
2 Channel Digital Output Modules
750-501, -502, -509, -512, -513, -514, -517, -535, (and all variations),
753-501, -502, -509, -512, -513, -514, -517
Table 249: 2 Channel Digital Output Modules
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Manual
Version 1.1.0
Bit 3
Bit 2
Bit 1
Bit 0
controls
controls
DO 2
DO 1
Channel 2 Channel 1
222
Table of Contents
12.2.2.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
2 Channel Digital Input Modules with Diagnostics and Input Process
Data
750-507 (-508), -522,
753-507
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 250: 2 Channel Digital Input Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic
bit S 2
bit S 1
Channel 2 Channel 1
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
DO 2
Channel 2
Bit 0
controls
DO 1
Channel 1
750-506,
753-506
The digital output module has 2-bits of diagnostic information for each output
channel. The 2-bit diagnostic information can then be decoded to determine the
exact fault condition of the module (i.e., overload, a short circuit, or a broken
wire). The 4-bits of diagnostic data are mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 251: 2 Channel Digital Input Modules with Diagnostics and Input Process Data 75x-506
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic
bit S 3
bit S 2
bit S 1
bit S 0
Channel 2 Channel 2 Channel 1 Channel 1
Diagnostic bits S1/S0, S3/S2: = ‘00’
standard mode
Diagnostic bits S1/S0, S3/S2: = ‘01’
no connected load/short circuit against +24 V
Diagnostic bits S1/S0, S3/S2: = ‘10’
Short circuit to ground/overload
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
not used
not used
Bit 1
controls
DO 2
Channel 2
Bit 0
controls
DO 1
Channel 1
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.2.4
Table of Contents
223
4 Channel Digital Output Modules
750-504, -516, -519, -531,
753-504, -516, -531, -540
Table 252: 4 Channel Digital Output Modules
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
12.2.2.5
Bit 3
Bit 2
Bit 1
controls
controls
controls
DO 4
DO 3
DO 2
Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
4 Channel Digital Output Modules with Diagnostics and Input
Process Data
750-532
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 253: 4 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic
bit
bit
bit
bit
S4
S3
S2
S1
Channel 4 Channel 3 Channel 2 Channel 1
Diagnostic bit S = ‘0’
no Error
Diagnostic bit S = ‘1’
overload, short circuit, or broken wire
Output Process Image
Bit 7
Bit 6
12.2.2.6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
DO 4
DO 3
DO 2
Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
Table 254: 8 Channel Digital Output Module
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
8 Channel Digital Output Module
750-530, -536, -1515, -1516
753-530, -534
Manual
Version 1.1.0
224
Table of Contents
12.2.2.7
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
8 Channel Digital Output Modules with Diagnostics and Input
Process Data
750-537
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 255: 8 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic
bit
bit
bit
bit
bit
bit
bit
bit
S8
S7
S6
S5
S4
S3
S2
S1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
Diagnostic bit S = ‘0’
no Error
Diagnostic bit S = ‘1’
overload, short circuit, or broken wire
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
12.2.2.8
Bit 0
controls
DO 1
Channel 1
16 Channel Digital Output Modules
750-1500, -1501, -1504, -1505
Table 256: 16 Channel Digital Output Modules
Output Process Image
Bit 15 Bit 14Bit 13Bit 12Bit 11Bit 10Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
control control control control control
control control control control control control control control control
controls
controls
s
s
s
s
s
s
s
s
s
s
s DO
s
s
s
DO 16
DO 10
DO 15 14 DO 13 DO 12 DO 11
DO 9 DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 DO 1
Channel
Channel
Channe Channe Channe Channe Channe
Channe Channe Channe Channe Channe Channe Channe Channe Channe
16
10
l1
l2
l3
l4
l 11
l5
l 12
l6
l 13
l7
l 14
l8
l 15
l9
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.2.9
Table of Contents
225
8 Channel Digital Input/Output Modules
750-1502, -1506
Table 257: 8 Channel Digital Input/Output Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
DI 8
DI 7
DI 6
DI 5
DI 4
DI 3
DI 2
DI 1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
Manual
Version 1.1.0
Bit 0
controls
DO 1
Channel 1
226
Table of Contents
12.2.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Analog Input Modules
The hardware of an analog input module has 16 bits of measured analog data per
channel and 8 bits of control/status.
However, the coupler/controller with MODBUS/TCP does not have access to the
8 control/status bits.
Therefore, the coupler/controller with MODBUS/TCP can only access the 16 bits
of analog data per channel, which are grouped as words and mapped in Intel
format in the Input Process Image.
When digital input modules are also present in the node, the analog input data is
always mapped into the Input Process Image in front of the digital data.
Information to the structure of the Control/Status byte
For detailed information about the structure of a particular module’s control/status
byte, please refer to that module’s manual. Manuals for each module can be found
on the Internet under: http://www.wago.com.
12.2.3.1
1 Channel Analog Input Modules
750-491, (and all variations)
Table 258: 1 Channel Analog Input Modules
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
12.2.3.2
Description
Measured Value UD
Measured Value Uref
2 Channel Analog Input Modules
750-452, -454, -456, -461, -462, -465, -466, -467, -469, -472, -474, -475, 476, 477, -478, -479, -480, -481, -483, -485, -492, (and all variations),
753-452, -454, -456, -461, -465, -466, -467, -469, -472, -474, -475, 476, -477,
478, -479, -483, -492, (and all variations)
Table 259: 2 Channel Analog Input Modules
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
Description
Measured Value Channel 1
Measured Value Channel 2
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.3.3
Table of Contents
227
4 Channel Analog Input Modules
750-453, -455, -457, -459, -460, -468, (and all variations),
753-453, -455, -457, -459
Table 260: 4 Channel Analog Input Modules
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
2
D5
D4
3
D7
D6
Manual
Version 1.1.0
Description
Measured Value Channel 1
Measured Value Channel 2
Measured Value Channel 3
Measured Value Channel 4
228
Table of Contents
12.2.4
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Analog Output Modules
The hardware of an analog output module has 16 bits of measured analog data per
channel and 8 bits of control/status. However, the coupler/controller with
MODBUS/TCP does not have access to the 8 control/status bits. Therefore, the
coupler/controller with MODBUS/TCP can only access the 16 bits of analog data
per channel, which are grouped as words and mapped in Intel format in the Output
Process Image.
When digital output modules are also present in the node, the analog output data
is always mapped into the Output Process Image in front of the digital data.
Information to the structure of the Control/Status byte
For detailed information about the structure of a particular module’s control/status
byte, please refer to that module’s manual. Manuals for each module can be found
on the Internet under: http://www.wago.com.
12.2.4.1
2 Channel Analog Output Modules
750-550, -552, -554, -556, -560, -562, 563, -585, (and all variations),
753-550, -552, -554, -556
Table 261: 2 Channel Analog Output Modules
Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
12.2.4.2
Description
Output Value Channel 1
Output Value Channel 2
4 Channel Analog Output Modules
750-553, -555, -557, -559,
753-553, -555, -557, -559
Table 262: 4 Channel Analog Output Modules
Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
2
D5
D4
3
D7
D6
Description
Output Value Channel 1
Output Value Channel 2
Output Value Channel 3
Output Value Channel 4
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.5
Table of Contents
229
Specialty Modules
WAGO has a host of Specialty I/O modules that perform various functions. With
individual modules beside the data bytes also the control/status byte is mapped in
the process image.
The control/status byte is required for the bidirectional data exchange of the
module with the higher-ranking control system. The control byte is transmitted
from the control system to the module and the status byte from the module to the
control system.
This allows, for example, setting of a counter with the control byte or displaying
of overshooting or undershooting of the range with the status byte.
The control/status byte always is in the process image in the Low byte.
Information
Information to the structure of the Control/Status byte
For detailed information about the structure of a particular module’s control/status
byte, please refer to that module’s manual. Manuals for each module can be found
on the Internet under: http://www.wago.com.
12.2.5.1
Counter Modules
750-404, (and all variations except of /000-005),
753-404, (and variation /000-003)
The above Counter Modules have a total of 5 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 1 byte of control/status).
The counter value is supplied as 32 bits. The following tables illustrate the Input
and Output Process Image, which has a total of 3 words mapped into each image.
Word alignment is applied.
Table 263: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003)
Input Process Image
Byte Destination
Offset
Description
High Byte
Low Byte
0
S
Status byte
1
D1
D0
Counter value
2
D3
D2
Output Process Image
Offset
0
1
2
Manual
Version 1.1.0
Byte Destination
High Byte
D1
D3
Low Byte
C
D0
D2
Description
Control byte
Counter setting value
230
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
750-404/000-005
The above Counter Modules have a total of 5 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 1 byte of control/ status).
The two counter values are supplied as 16 bits. The following tables illustrate the
Input and Output Process Image, which has a total of 3 words mapped into each
image. Word alignment is applied.
Table 264: Counter Modules 750-404/000-005
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
S
1
D1
D0
2
D3
D2
Description
Status byte
Counter Value of Counter 1
Counter Value of Counter 2
Output Process Image
Offset
0
1
2
Byte Destination
High Byte
Low Byte
C
D1
D0
D3
D2
Description
Control byte
Counter Setting Value of Counter 1
Counter Setting Value of Counter 2
750-638,
753-638
The above Counter Modules have a total of 6 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 2 bytes of control/status).
The two counter values are supplied as 16 bits. The following tables illustrate the
Input and Output Process Image, which has a total of 4 words mapped into each
image. Word alignment is applied.
Table 265: Counter Modules 750-638, 753-638
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
S0
1
D1
D0
2
S1
3
D3
D2
Description
Status byte von Counter 1
Counter Value von Counter 1
Status byte von Counter 2
Counter Value von Counter 2
Output Process Image
Offset
0
1
2
3
Byte Destination
High Byte
Low Byte
C0
D1
D0
C1
D3
D2
Description
Control byte von Counter 1
Counter Setting Value von Counter 1
Control byte von Counter 2
Counter Setting Value von Counter 2
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.5.2
Table of Contents
231
Pulse Width Modules
750-511, (and all variations /xxx-xxx)
The above Pulse Width modules have a total of 6 bytes of user data in both the
Input and Output Process Image (4 bytes of channel data and 2 bytes of control/
status). The two channel values are supplied as 16 bits. Each channel has its own
control/status byte. The following table illustrates the Input and Output Process
Image, which has a total of 4 words mapped into each image. Word alignment is
applied.
Table 266: Pulse Width Modules 750-511, /xxx-xxx
Input and Output Process
Byte Destination
Offset
High Byte
Low Byte
0
C0/S0
1
D1
D0
2
C1/S1
3
D3
D2
12.2.5.3
Description
Control/Status byte of Channel 1
Data Value of Channel 1
Control/Status byte of Channel 2
Data Value of Channel 2
Serial Interface Modules with alternative Data Format
750-650, (and the variations /000-002, -004, -006, -009, -010, -011, -012, -013),
750-651, (and the variations /000-001, -002, -003),
750-653, (and the variations /000-002, -007),
753-650, -653
Note
The process image of the / 003-000-variants depends on the parameterized
operating mode!
With the freely parametrizable variations /003 000 of the serial interface modules,
the desired operation mode can be set. Dependent on it, the process image of these
modules is then the same, as from the appropriate variation.
The above Serial Interface Modules with alternative data format have a total of 4
bytes of user data in both the Input and Output Process Image (3 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 2 words mapped into each image.
Word alignment is applied.
Table 267: Serial Interface Modules with alternative Data Format
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
Manual
Version 1.1.0
0
D0
C/S
1
D2
D1
Description
Control/status
byte
Data bytes
Data byte
232
Table of Contents
12.2.5.4
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Serial Interface Modules with Standard Data Format
750-650/000-001, -014, -015, -016
750-653/000-001, -006
The above Serial Interface Modules with Standard Data Format have a total of 6
bytes of user data in both the Input and Output Process Image (5 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 3 words mapped into each image.
Word alignment is applied.
Table 268: Serial Interface Modules with Standard Data Format
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
12.2.5.5
0
D0
C/S
1
2
D2
D4
D1
D3
Description
Data byte
Control/status
byte
Data bytes
Data Exchange Module
750-654, (and the variation /000-001)
The Data Exchange modules have a total of 4 bytes of user data in both the Input
and Output Process Image. The following tables illustrate the Input and Output
Process Image, which has a total of 2 words mapped into each image.
Word alignment is applied.
Table 269: Data Exchange Module
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
12.2.5.6
Description
Data bytes
SSI Transmitter Interface Modules
750-630 (and all variations)
Note
The process image of the / 003-000-variants depends on the parameterized
operating mode!
The operating mode of the configurable /003-000 I/O module versions can be set.
Based on the operating mode, the process image of these I/O modules is then the
same as that of the respective version.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
233
The above SSI Transmitter Interface modules have a total of 4 bytes of user data
in the Input Process Image, which has 2 words mapped into the image.
Word alignment is applied.
Table 270: SSI Transmitter Interface Modules
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D1
D0
1
D3
D2
12.2.5.7
Description
Data bytes
Incremental Encoder Interface Modules
750-631/000-004, -010, -011
The above Incremental Encoder Interface modules have 5 bytes of input data and
3 bytes of output data. The following tables illustrate the Input and Output Process
Image, which have 4 words into each image. Word alignment is applied.
Table 271: Incremental Encoder Interface Modules 750-631/000-004, --010, -011
Input Process Image
Byte Destination
Offset
Description
High Byte
Low Byte
0
S
not used
Status byte
1
D1
D0
Counter word
2
not used
3
D4
D3
Latch word
Output Process Image
Offset
0
1
2
3
Byte Destination
High Byte
Low Byte
C
D1
D0
-
Description
not used
Control byte
Counter setting word
not used
not used
750-634
The above Incremental Encoder Interface module has 5 bytes of input data (6
bytes in cycle duration measurement mode) and 3 bytes of output data. The
following tables illustrate the Input and Output Process Image, which has 4 words
mapped into each image. Word alignment is applied.
Manual
Version 1.1.0
234
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 272: Incremental Encoder Interface Modules 750-634
Input Process Image
Byte Destination
Offset
Description
High Byte
Low Byte
0
S
not used
Status byte
1
D1
D0
Counter word
2
(D2) *)
not used
(Periodic time)
3
D4
D3
Latch word
*)
If cycle duration measurement mode is enabled in the control byte, the cycle duration is
given as a 24-bit value that is stored in D2 together with D3/D4.
Output Process Image
Offset
0
1
2
3
Byte Destination
High Byte
Low Byte
C
D1
D0
-
Description
not used
Control byte
Counter setting word
not used
750-637
The above Incremental Encoder Interface Module has a total of 6 bytes of user
data in both the Input and Output Process Image (4 bytes of encoder data and 2
bytes of control/status). The following table illustrates the Input and Output
Process Image, which have 4 words mapped into each image. Word alignment is
applied.
Table 273: Incremental Encoder Interface Modules 750-637
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
C0/S0
1
D1
D0
2
C1/S1
3
D3
D2
Description
Control/Status byte of Channel 1
Data Value of Channel 1
Control/Status byte of Channel 2
Data Value of Channel 2
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
235
750-635,
753-635
The above Digital Pulse Interface module has a total of 4 bytes of user data in
both the Input and Output Process Image (3 bytes of module data and 1 byte of
control/status). The following table illustrates the Input and Output Process
Image, which have 2 words mapped into each image. Word alignment is applied.
Table 274: Digital Pulse Interface Modules 750-635
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
12.2.5.8
0
D0
C0/S0
1
D2
D1
Description
Control/status
byte
Data bytes
Data byte
DC-Drive Controller
750-636
The DC-Drive Controller maps 6 bytes into both the input and output process
image. The data sent and received are stored in up to 4 input and output bytes
(D0 ... D3). Two control bytes (C0, C1) and two status bytes (S0/S1) are used to
control the I/O module and the drive.
In addition to the position data in the input process image (D0 … D3), it is
possible to display extended status information (S2 … S5). Then the three control
bytes (C1 … C3) and status bytes (S1 … S3) are used to control the data flow.
Bit 3 of control byte C1 (C1.3) is used to switch between the process data and the
extended status bytes in the input process image (Extended Info_ON). Bit 3 of
status byte S1 (S1.3) is used to acknowledge the switching process.
Table 275: DC-Drive Controller 750-636
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
S1
S0
*)
**)
Manual
Version 1.1.0
1
D1*) / S3**)
D0*) / S2**)
2
D3*) / S5**)
D2*) / S4**)
ExtendedInfo_ON = ‘0’.
ExtendedInfo_ON = ‘1’.
Description
Status byte S1
Status byte S0
Actual position*) Actual position
/ Extended status (LSB) / Extended
byte S3**)
status byte S2**)
Actual position
Actual position*)
(MSB) /
/ Extended status
Extended status
byte S4**)
byte S3**)
236
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Output Process Image
Offset
0
12.2.5.9
Byte Destination
High Byte
Low Byte
C1
C0
1
D1
D0
2
D3
D2
Description
Control byte C1 Control byte C0
Setpoint position Setpoint position
(LSB)
Setpoint position Setpoint position
(MSB)
Stepper Controller
750-670
The Stepper controller RS422 / 24 V / 20 mA 750-670 provides the fieldbus
coupler 12 bytes input and output process image via 1 logical channel. The data to
be sent and received are stored in up to 7 output bytes (D0 … D6) and 7 input
bytes (D0 … D6), depending on the operating mode.
Output byte D0 and input byte D0 are reserved and have no function assigned.
One I/O module control and status byte (C0, S0) and 3 application control and
status bytes (C1 ... C3, S1 ... S3) provide the control of the data flow.
Switching between the two process images is conducted through bit 5 in the
control byte (C0 (C0.5). Activation of the mailbox is acknowledged by bit 5 of the
status byte S0 (S0.5).
Table 276: Stepper Controller RS 422 / 24 V / 20 mA 750-670
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
reserved
S0
1
D1
D0
2
D3
D2
3
D5
D4
4
5
*)
**)
S3
D6
S1
S2
Cyclic process image (Mailbox disabled)
Mailbox process image (Mailbox activated)
Description
reserved
Status byte S0
Process data*) / Mailbox**)
Status byte S3
Status byte S1
Process data*) /
reserved**)
Status byte S2
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
237
Output Process Image
Byte Destination
High Byte
Low Byte
reserved
C0
D1
D0
D3
D2
D5
D4
Offset
0
1
2
3
4
5
*)
**)
C3
D6
C1
C2
Cyclic process image (Mailbox disabled)
Mailbox process image (Mailbox activated)
Description
reserved
Control byte C0
Process data*) / Mailbox**)
Process data*) /
reserved**)
Control byte C1 Control byte C2
Control byte C3
12.2.5.10 RTC Module
750-640
The RTC Module has a total of 6 bytes of user data in both the Input and Output
Process Image (4 bytes of module data and 1 byte of control/status and 1 byte ID
for command). The following table illustrates the Input and Output Process
Image, which have 3 words mapped into each image. Word alignment is applied.
Table 277: RTC Module 750-640
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
ID
C/S
1
2
D1
D3
D0
D2
Description
Command byte
Control/status
byte
Data bytes
12.2.5.11 DALI/DSI Master Module
750-641
The DALI/DSI Master module has a total of 6 bytes of user data in both the Input
and Output Process Image (5 bytes of module data and 1 byte of control/status).
The following tables illustrate the Input and Output Process Image, which have 3
words mapped into each image. Word alignment is applied.
Table 278: DALI/DSI Master module 750-641
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D0
S
1
D2
D1
2
D4
D3
Manual
Version 1.1.0
Description
DALI Response
Status byte
Message 3
DALI Address
Message 1
Message 2
238
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Output Process Image
Offset
Byte Destination
High Byte
Low Byte
0
D0
C
1
2
D2
D4
D1
D3
Description
DALI command,
DSI dimming value
Parameter 2
Command extension
Control byte
DALI Address
Parameter 1
12.2.5.12 EnOcean Radio Receiver
750-642
The EnOcean radio receiver has a total of 4 bytes of user data in both the Input
and Output Process Image (3 bytes of module data and 1 byte of control/status).
The following tables illustrate the Input and Output Process Image, which have 2
words mapped into each image. Word alignment is applied.
Table 279: EnOcean Radio Receiver 750-642
Input Process Image
Byte Destination
Offset
High Byte
Low Byte
0
D0
S
1
D2
D1
Description
Data byte
Status byte
Data bytes
Output Process Image
Offset
0
1
Byte Destination
High Byte
Low Byte
C
-
Description
not used
Control byte
not used
12.2.5.13 MP Bus Master Module
750-643
The MP Bus Master Module has a total of 8 bytes of user data in both the Input
and Output Process Image (6 bytes of module data and 2 bytes of control/status).
The following table illustrates the Input and Output Process Image, which have 4
words mapped into each image. Word alignment is applied.
Table 280: MP Bus Master Module 750-643
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
0
C1/S1
C0/S0
1
2
3
D1
D3
D5
D0
D2
D4
Description
extended
Control/
Status byte
Control/status
byte
Data bytes
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
239
12.2.5.14 Bluetooth® RF-Transceiver
750-644
The size of the process image for the Bluetooth® module can be adjusted to 12, 24
or 48 bytes.
It consists of a control byte (input) or status byte (output); an empty byte; an
overlayable mailbox with a size of 6, 12 or 18 bytes (mode 2); and the Bluetooth®
process data with a size of 4 to 46 bytes.
Thus, each Bluetooth® module uses between 12 and 48 bytes in the process image.
The sizes of the input and output process images are always the same.
The first byte contains the control/status byte; the second contains an empty byte.
Process data attach to this directly when the mailbox is hidden. When the mailbox
is visible, the first 6, 12 or 18 bytes of process data are overlaid by the mailbox
data, depending on their size. Bytes in the area behind the optionally visible
mailbox contain basic process data. The internal structure of the Bluetooth®
process data can be found in the documentation for the Bluetooth® 750-644 RF
Transceiver.
The mailbox and the process image sizes are set with the startup tool WAGO-I/OCHECK.
Table 281: Bluetooth® RF-Transceiver 750-644
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
Manual
Version 1.1.0
0
-
C0/S0
1
2
3
...
max.
23
D1
D3
D5
...
D0
D2
D4
...
D45
D44
Description
not used
Control/status
byte
Mailbox (0, 3, 6 or 9 words) and
Process data (2-23 words)
240
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.2.5.15 Vibration Velocity/Bearing Condition Monitoring VIB I/O
750-645
The Vibration Velocity/Bearing Condition Monitoring VIB I/O has a total of 12
bytes of user data in both the Input and Output Process Image (8 bytes of module
data and 4 bytes of control/status). The following table illustrates the Input and
Output Process Image, which have 8 words mapped into each image.
Word alignment is applied.
Table 282: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645
Input and Output Process Image
Byte Destination
Offset
Description
High Byte
Low Byte
Control/status byte
0
C0/S0
not used
(log. Channel 1,
Sensor input 1)
Data bytes
1
D1
D0
(log. Channel 1, Sensor input 1)
Control/status byte
2
C1/S1
not used
(log. Channel 2,
Sensor input 2)
Data bytes
3
D3
D2
(log. Channel 2, Sensor input 2)
Control/status byte
4
C2/S2
not used
(log. Channel 3,
Sensor input 1)
Data bytes
5
D5
D4
(log. Channel 3, Sensor input 3)
Control/status byte
6
C3/S3
not used
(log. Channel 4,
Sensor input 2)
Data bytes
7
D7
D6
(log. Channel 4, Sensor input 2)
12.2.5.16 AS-interface Master Module
750-655
The length of the process image of the AS-interface master module can be set to
fixed sizes of 12, 20, 24, 32, 40 or 48 bytes.
It consists of a control or status byte, a mailbox with a size of 0, 6, 10, 12 or 18
bytes and the AS-interface process data, which can range from 0 to 32 bytes.
The AS-interface master module has a total of 6 to maximally 24 words data in
both the Input and Output Process Image. Word alignment is applied.
The first Input and output word, which is assigned to an AS-interface master
module, contains the status / control byte and one empty byte.
Subsequently the mailbox data are mapped, when the mailbox is permanently
superimposed (Mode 1).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
241
In the operating mode with suppressible mailbox (Mode 2), the mailbox and the
cyclical process data are mapped next.
The following words contain the remaining process dat.
The mailbox and the process image sizes are set with the startup tool WAGO-I/OCHECK.
Table 283: AS-interface Master module 750-655
Input and Output Process Image
Byte Destination
Offset
High Byte
Low Byte
Manual
Version 1.1.0
0
-
C0/S0
1
2
3
...
max.
23
D1
D3
D5
...
D0
D2
D4
...
D45
D44
Description
not used
Control/status
byte
Mailbox (0, 3, 5, 6 or 9 words)/
Process data (0-16 words)
242
Table of Contents
12.2.6
System Modules
12.2.6.1
System Modules with Diagnostics
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
750-610, -611
The modules provide 2 bits of diagnostics in the Input Process Image for
monitoring of the internal power supply.
Table 284: System Modules with Diagnostics 750-610, -611
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
12.2.6.2
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic
bit S 2
bit S 1
Fuse
Fuse
Binary Space Module
750-622
The Binary Space Modules behave alternatively like 2 channel digital input
modules or output modules and seize depending upon the selected settings 1, 2, 3
or 4 bits per channel. According to this, 2, 4, 6 or 8 bits are occupied then either in
the process input or the process output image.
Table 285: Binary Space Module 750-622 (with behavior like 2 channel digital input)
Input and Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
(Data bit
(Data bit
(Data bit
(Data bit
(Data bit
(Data bit
Data bit
DI 8)
DI 7)
DI 6)
DI 5)
DI 4)
DI 3)
DI 2
Bit 0
Data bit
DI 1
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3
Table of Contents
Process Data Architecture for EtherNet/IP
With some I/O modules, the structure of the process data is fieldbus specific.
In the case of a fieldbus controller with EtherNet/IP, the process image uses a
word structure (with word alignment). The internal mapping method for data
greater than one byte conforms to the Intel format.
The following section describes the process image for various WAGO-I/OSYSTEM 750 and 753 I/O modules when using a fieldbus coupler with
EtherNet/IP.
NOTICE
Equipment damage due to incorrect address!
Depending on the specific position of an I/O module in the fieldbus node, the
process data of all previous byte or bit-oriented modules must be taken into
account to determine its location in the process data map.
Manual
Version 1.1.0
243
244
Table of Contents
12.3.1
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Digital Input Modules
Digital input modules supply one bit of data per channel to specify the signal state
for the corresponding channel. These bits are mapped into the Input Process
Image.
Some digital I/O modules have an additional diagnostic bit per channel in the
input process image. The diagnostic bit detects faults (e.g., wire breakage,
overloads and/or short circuits). For some I/O modules, the data bits also have be
evaluated with the set diagnostic bit.
When analog input modules are also present in the node, the digital data is always
appended after the analog data in the Input Process Image, grouped into bytes.
1 sub index is assigned for each 8 bit.
Each input channel seizes one Instance in the Discrete Input Point Object (Class
0x65).
12.3.1.1
1 Channel Digital Input Module with Diagnostics
750-435
Table 286: 1 Channel Digital Input Module with Diagnostics
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Diagnostic
bit
S1
Bit 0
Data bit
DI 1
The input modules seize 2 Instances in Class (0x65).
12.3.1.2
2 Channel Digital Input Modules
750-400, -401, -405, -406, -410, -411, -412, -427, -438, (and all variations),
753-400, -401, -405, -406, -410, -411, -412, -427
Table 287: 2 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
DI 2
DI 1
Channel 2 Channel 1
The input modules seize 2 Instances in Class (0x65).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.1.3
Table of Contents
245
2 Channel Digital Input Module with Diagnostics
750-419, -421, -424, -425,
753-421, -424, -425
Table 288: 2 Channel Digital Input Module with Diagnostics
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Data bit
Data bit
bit S 2
bit S 1
DI 2
DI 1
Channel 2 Channel 1 Channel 2 Channel 1
The input modules seize 4 Instances in Class (0x65).
12.3.1.4
2 Channel Digital Input Module with Diagnostics and Output Process
Data
750-418,
753-418
The digital input module supplies a diagnostic and acknowledge bit for each input
channel. If a fault condition occurs, the diagnostic bit is set. After the fault
condition is cleared, an acknowledge bit must be set to re-activate the input. The
diagnostic data and input data bit is mapped in the Input Process Image, while the
acknowledge bit is in the Output Process Image.
Table 289: 2 Channel Digital Input Module with Diagnostics and Output Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Data bit Data bit
bit S 2
bit S 1
DI 2
DI 1
Channel 2 Channel 1 Channel 2 Channel 1
The input modules seize 4 Instances in Class (0x65).
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Acknowledge- Acknowledgement bit Q 2
ment bit Q 1
Channel 2
Channel 1
And the input modules seize 4 Instances in Class (0x66).
Manual
Version 1.1.0
Bit 1
Bit 0
0
0
246
Table of Contents
12.3.1.5
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
4 Channel Digital Input Modules
750-402, -403, -408, -409, -414, -415, -422, -423, -428, -432, -433, -1420, -1421,
-1422
753-402, -403, -408, -409, -415, -422, -423, -428, -432, -433, -440
Table 290: 4 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Data bit
DI 4
Channel 4
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
DI 3
DI 2
DI 1
Channel 3 Channel 2 Channel 1
The input modules seize 4 Instances in Class (0x65).
12.3.1.6
8 Channel Digital Input Modules
750-430, -431, -436, -437, -1415, -1416, -1417
753-430, -431, -434
Table 291: 8 Channel Digital Input Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
DI 8
DI 7
DI 6
DI 5
DI 4
DI 3
DI 2
DI 1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
The input modules seize 8 Instances in Class (0x65).
12.3.1.7
16 Channel Digital Input Modules
750-1400, -1402, -1405, -1406, -1407
Table 292: 16 Channel Digital Input Modules
Input Process Image
Bit 15 Bit 14Bit 13Bit 12Bit 11Bit 10Bit 9 Bit 8 Bit 7 Bit 6
Data Data Data Data Data Data Data Data Data Data
bit bit DI bit
bit
bit bit bit bit bit bit
DI 16 DI 15 DI 14 DI 13 DI 12 DI 11 DI 10 DI 9 8 DI 7
Chann Chan Chan Chan Chan Chan Chann Chan Chan Chan
el 16 nel 15 nel 14 nel 13 nel 12 nel 11 el 10 nel 9 nel 8 nel 7
Bit 5
Data
bit
DI 6
Chan
nel 6
Bit 4
Data
bit
DI 5
Chan
nel 5
Bit 3
Data
bit
DI 4
Chan
nel 4
Bit 2
Data
bit
DI 3
Chan
nel 3
Bit 1
Data
bit
DI 2
Chan
nel 2
Bit 0
Data
bit
DI 1
Chan
nel 1
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.2
Table of Contents
247
Digital Output Modules
Digital output modules use one bit of data per channel to control the output of the
corresponding channel. These bits are mapped into the Output Process Image.
Some digital modules have an additional diagnostic bit per channel in the Input
Process Image. The diagnostic bit is used for detecting faults that occur (e.g., wire
breaks and/or short circuits). With some I/O modules, with set diagnostic bit,
additionally the data bits must be evaluated.
When analog output modules are also present in the node, the digital image data is
always appended after the analog data in the Output Process Image, grouped into
bytes.
For each 8 bits a subindex is occupied.
Each output channel occupies one instance in the Discrete Output Point Object
(Class 0x 66).
12.3.2.1
1 Channel Digital Output Module with Input Process Data
750-523
The digital output modules deliver 1 bit via a process value Bit in the output
process image, which is illustrated in the input process image. This status image
shows "manual mode".
Table 293: 1 Channel Digital Output Module with Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
not used
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
not used
And the output modules seize 2 Instances in Class (0x66).
Manual
Version 1.1.0
Bit 0
Status bit
“Manual
Operation“
Bit 0
controls
DO 1
Channel 1
248
Table of Contents
12.3.2.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
2 Channel Digital Output Modules
750-501, -502, -509, -512, -513, -514, -517, -535, (and all variations),
753-501, -502, -509, -512, -513, -514, -517
Table 294: 2 Channel Digital Output Modules
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
controls
controls
DO 2
DO 1
Channel 2 Channel 1
The output modules seize 2 Instances in Class (0x66).
12.3.2.3
2 Channel Digital Input Modules with Diagnostics and Input Process
Data
750-507 (-508), -522,
753-507
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 295: 2 Channel Digital Input Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic
bit S 2
bit S 1
Channel 2 Channel 1
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
DO 2
Channel 2
Bit 0
controls
DO 1
Channel 1
And the output modules seize 2 Instances in Class (0x66).
750-506,
753-506
The digital output module has 2-bits of diagnostic information for each output
channel. The 2-bit diagnostic information can then be decoded to determine the
exact fault condition of the module (i.e., overload, a short circuit, or a broken
wire). The 4-bits of diagnostic data are mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
249
Table 296: 2 Channel Digital Input Modules with Diagnostics and Input Process Data 75x-506
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic
bit S 3
bit S 2
bit S 1
bit S 0
Channel 2 Channel 2 Channel 1 Channel 1
Diagnostic bits S1/S0, S3/S2: = ‘00’
standard mode
Diagnostic bits S1/S0, S3/S2: = ‘01’
no connected load/short circuit against +24 V
Diagnostic bits S1/S0, S3/S2: = ‘10’
Short circuit to ground/overload
The output modules seize 4 Instances in Class (0x65).
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
DO 2
Channel 2
Bit 0
controls
DO 1
Channel 1
not used
not used
Bit 3
Bit 2
Bit 1
controls
controls
controls
DO 4
DO 3
DO 2
Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
And the output modules seize 4 Instances in Class (0x66).
12.3.2.4
4 Channel Digital Output Modules
750-504, -516, -519, -531,
753-504, -516, -531, -540
Table 297: 4 Channel Digital Output Modules
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
The output modules seize 4 Instances in Class (0x66).
12.3.2.5
4 Channel Digital Output Modules with Diagnostics and Input
Process Data
750-532
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 298: 4 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic
bit
bit
bit
bit
S4
S3
S2
S1
Channel 4 Channel 3 Channel 2 Channel 1
Diagnostic bit S = ‘0’
no Error
Diagnostic bit S = ‘1’
overload, short circuit, or broken wire
The output modules seize 4 Instances in Class (0x65).
Manual
Version 1.1.0
250
Table of Contents
Output Process Image
Bit 7
Bit 6
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
DO 4
DO 3
DO 2
Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
And the output modules seize 4 Instances in Class (0x66).
12.3.2.6
8 Channel Digital Output Module
750-530, -536, -1515, -1516
753-530, -534
Table 299: 8 Channel Digital Output Module
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
The output modules seize 8 Instances in Class (0x66).
12.3.2.7
8 Channel Digital Output Modules with Diagnostics and Input
Process Data
750-537
The digital output modules have a diagnostic bit for each output channel. When an
output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 300: 8 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic
bit
bit
bit
bit
bit
bit
bit
bit
S8
S7
S6
S5
S4
S3
S2
S1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
Diagnostic bit S = ‘0’
no Error
Diagnostic bit S = ‘1’
overload, short circuit, or broken wire
The output modules seize 8 Instances in Class (0x65).
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
Bit 0
controls
DO 1
Channel 1
And the output modules seize 8 Instances in Class (0x66).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.2.8
Table of Contents
251
16 Channel Digital Output Modules
750-1500, -1501, -1504, -1505
Table 301: 16 Channel Digital Output Modules
Output Process Image
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9
Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
controls controls controls controls controls controls controls controls controls controls controls controls controls controls controls controls
DO 16 DO 15 DO 14 DO 13 DO 12 DO 11 DO 10 DO 9 DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 DO 1
Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
The output modules seize 16 Instances in Class (0x66).
12.3.2.9
8 Channel Digital Input/Output Modules
750-1502, -1506
Table 302: 8 Channel Digital Input/Output Modules
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
Data bit
DI 8
DI 7
DI 6
DI 5
DI 4
DI 3
DI 2
DI 1
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1
The input/output modules seize 8 Instances in Class (0x65).
Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
controls
controls
controls
controls
controls
controls
controls
DO 8
DO 7
DO 6
DO 5
DO 4
DO 3
DO 2
Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2
The input/output modules seize 8 Instances in Class (0x66).
Manual
Version 1.1.0
Bit 0
controls
DO 1
Channel 1
252
Table of Contents
12.3.3
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Analog Input Modules
The hardware of an analog input module has 16 bits of measured analog data per
channel and 8 bits of control/status.
However, the coupler/controller with EtherNet/IP does not have access to the 8
control/status bits.
Therefore, the coupler/controller with MODBUS/TCP can only access the 16 bits
of analog data per channel, which are grouped as words and mapped in Intel
format in the Input Process Image.
When digital input modules are also present in the node, the analog input data is
always mapped into the Input Process Image in front of the digital data.
Each input channel seizes one Instance in the Analog Input Point Object (Class
0x67).
Note
Information for the control/status byte development
Please refer to the corresponding description of the I/O modules for the structure
of the control/status bytes. You can find a manual with the relevant I/O module
description on the WAGO home page: at: http://www.wago.com .
12.3.3.1
1 Channel Analog Input Modules
750-491, (and all variations)
Table 303: 1 Channel Analog Input Modules
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
Description
Measured Value UD
Measured Value Uref
The input modules represent 2x2 bytes and seize 2 Instances in Class (0x67).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.3.2
Table of Contents
253
2 Channel Analog Input Modules
750-452, -454, -456, -461, -462, -465, -466, -467, -469, -472, -474, -475, 476, 477, -478, -479, -480, -481, -483, -485, -492, (and all variations),
753-452, -454, -456, -461, -465, -466, -467, -469, -472, -474, -475, 476, -477,
478, -479, -483, -492, (and all variations)
Table 304: 2 Channel Analog Input Modules
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
Description
Measured Value Channel 1
Measured Value Channel 2
The input modules represent 2x2 bytes and seize 2 Instances in Class (0x67).
12.3.3.3
4 Channel Analog Input Modules
750-453, -455, -457, -459, -460, -468, (and all variations),
753-453, -455, -457, -459
Table 305: 4 Channel Analog Input Modules
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
n+2
D5
D4
n+3
D7
D6
Description
Measured Value Channel 1
Measured Value Channel 2
Measured Value Channel 3
Measured Value Channel 4
The input modules represent 4x2 bytes and seize 4 Instances in Class (0x67).
Manual
Version 1.1.0
254
Table of Contents
12.3.4
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Analog Output Modules
The hardware of an analog output module has 16 bits of measured analog data per
channel and 8 bits of control/status. However, the coupler/controller with
EtherNet/IP does not have access to the 8 control/status bits. Therefore, the
coupler/controller with EtherNet/IP can only access the 16 bits of analog data per
channel, which are grouped as words and mapped in Intel format in the Output
Process Image.
When digital output modules are also present in the node, the analog output data
is always mapped into the Output Process Image in front of the digital data.
Each output channel seizes one Instance in the Analog Output Point Object (Class
0x68).
Information
Information to the structure of the Control/Status byte
For detailed information about the structure of a particular module’s control/status
byte, please refer to that module’s manual. Manuals for each module can be found
on the Internet under: http://www.wago.com.
12.3.4.1
2 Channel Analog Output Modules
750-550, -552, -554, -556, -560, -562, 563, -585, (and all variations),
753-550, -552, -554, -556
Table 306: 2 Channel Analog Output Modules
Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
Description
Output Value Channel 1
Output Value Channel 2
The output modules represent 2x2 bytes and seize 2 Instances in Class (0x68).
12.3.4.2
4 Channel Analog Output Modules
750-553, -555, -557, -559,
753-553, -555, -557, -559
Table 307: 4 Channel Analog Output Modules
Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
n+2
D5
D4
n+3
D7
D6
Description
Output Value Channel 1
Output Value Channel 2
Output Value Channel 3
Output Value Channel 4
The output modules represent 4x2 bytes and seize 4 Instances in Class (0x68).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.5
Table of Contents
255
Specialty Modules
WAGO has a host of Specialty I/O modules that perform various functions. With
individual modules beside the data bytes also the control/status byte is mapped in
the process image. The control/status byte is required for the bidirectional data
exchange of the module with the higher-ranking control system. The control byte
is transmitted from the control system to the module and the status byte from the
module to the control system.
This allows, for example, setting of a counter with the control byte or displaying
of overshooting or undershooting of the range with the status byte.
The control/status byte always lies in the low byte for the fieldbus
coupler/controller with Ethernet/IP.
Information
Information to the structure of the Control/Status byte
For detailed information about the structure of a particular module’s control/status
byte, please refer to that module’s manual. Manuals for each module can be found
on the Internet under: http://www.wago.com.
The Specialty Modules represent as analog modules.
For this, the process input data of the Specialty Modules seize one Instance per
channel in the Analog Input Point Object (Class 0x67) and the process output data
seize one Instance seize one Instance in the Analog Input Point Object (Class
0x67) per channel in the Analog Output Point Object (Class 0x68).
12.3.5.1
Counter Modules
750-404, (and all variations except of /000-005),
753-404, (and variation /000-003)
The above Counter Modules have a total of 5 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 1 byte of control/status).
The counter value is supplied as 32 bits. The following tables illustrate the Input
and Output Process Image, which has a total of 3 words mapped into each image.
Word alignment is applied.
Table 308: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003)
Input Process Image
Byte Destination
Instance
Description
High Byte
Low Byte
S
Status byte
n
D1
D0
Counter value
D3
D2
The specialty modules represent 1x6 bytes input data and seize 1 Instance in Class
(0x67).
Manual
Version 1.1.0
256
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
C
D1
D0
D3
D2
Description
Control byte
Counter setting value
And the specialty modules represent 1x6 bytes output data and seize 1 Instance in
Class (0x68).
750-404/000-005
The above Counter Modules have a total of 5 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 1 byte of control/ status).
The two counter values are supplied as 16 bits. The following tables illustrate the
Input and Output Process Image, which has a total of 3 words mapped into each
image. Word alignment is applied.
Table 309: Counter Modules 750-404/000-005
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
S
n
D1
D0
D3
D2
Description
Status byte
Counter Value of Counter 1
Counter Value of Counter 2
The specialty modules represent 2x3 bytes input data and seize 2 Instances in
Class (0x67).
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
C
D1
D0
D3
D2
Description
Control byte
Counter Setting Value of Counter 1
Counter Setting Value of Counter 2
And the specialty modules represent 1x6 bytes output data and seize 1 Instance in
Class (0x68).
750-638,
753-638
The above Counter Modules have a total of 6 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 2 bytes of control/status).
The two counter values are supplied as 16 bits. The following tables illustrate the
Input and Output Process Image, which has a total of 4 words mapped into each
image. Word alignment is applied.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 310: Counter Modules 750-638, 753-638
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
S0
n
D1
D0
S1
n+1
D3
D2
257
Description
Status byte von Counter 1
Counter Value von Counter 1
Status byte von Counter 2
Counter Value von Counter 2
The specialty modules represent 2x3 bytes input data and seize 2 Instances in
Class (0x67).
Output Process Image
Instance
n
n+1
Byte Destination
High Byte
Low Byte
C0
D1
D0
C1
D3
D2
Description
Control byte von Counter 1
Counter Setting Value von Counter 1
Control byte von Counter 2
Counter Setting Value von Counter 2
And the specialty modules represent 2x3 bytes output data and seize 2 Instances
in Class (0x68).
12.3.5.2
Pulse Width Modules
750-511, (and all variations /xxx-xxx)
The above Pulse Width modules have a total of 6 bytes of user data in both the
Input and Output Process Image (4 bytes of channel data and 2 bytes of control/
status). The two channel values are supplied as 16 bits. Each channel has its own
control/status byte. The following table illustrates the Input and Output Process
Image, which has a total of 4 words mapped into each image. Word alignment is
applied.
Table 311: Pulse Width Modules 750-511, /xxx-xxx
Input and Output Process
Byte Destination
Instance
High Byte
Low Byte
C0/S0
n
D1
D0
n+1
D3
D2
Description
Control/Status byte of Channel 1
Data Value of Channel 1
Control/Status byte of Channel 2
Data Value of Channel 2
The specialty modules represent 2x3 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
12.3.5.3
Serial Interface Modules with alternative Data Format
750-650, (and the variations /000-002, -004, -006, -009, -010, -011, -012, -013),
750-651, (and the variations /000-002, -003),
750-653, (and the variations /000-002, -007),
753-650, -653
Manual
Version 1.1.0
258
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Note
The process image of the / 003-000-variants depends on the parameterized
operating mode!
With the freely parametrizable variations /003 000 of the serial interface modules,
the desired operation mode can be set. Dependent on it, the process image of these
modules is then the same, as from the appropriate variation.
The above Serial Interface Modules with alternative data format have a total of 4
bytes of user data in both the Input and Output Process Image (3 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 2 words mapped into each image.
Word alignment is applied.
Table 312: Serial Interface Modules with alternative Data Format
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D0
C/S
n+1
D2
D1
Description
Control/status
byte
Data bytes
Data byte
The specialty modules represent 2x2 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
12.3.5.4
Serial Interface Modules with Standard Data Format
750-650/000-001, -014, -015, -016
750-651/000-001
750-653/000-001, -006
The above Serial Interface Modules with Standard Data Format have a total of 6
bytes of user data in both the Input and Output Process Image (5 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 3 words mapped into each image.
Word alignment is applied.
Table 313: Serial Interface Modules with Standard Data Format
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D0
C/S
D2
D4
D1
D3
Description
Data byte
Control/status
byte
Data bytes
The specialty modules represent 1x6 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.5.5
Table of Contents
259
Data Exchange Module
750-654, (and the variation /000-001)
The Data Exchange modules have a total of 4 bytes of user data in both the Input
and Output Process Image. The following tables illustrate the Input and Output
Process Image, which has a total of 2 words mapped into each image.
Word alignment is applied.
Table 314: Data Exchange Module
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
Description
Data bytes
The specialty modules represent 2x2 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
12.3.5.6
SSI Transmitter Interface Modules
750-630, (and all variations)
Note
The process image of the / 003-000-variants depends on the parameterized
operating mode!
The operating mode of the configurable /003-000 I/O module versions can be set.
Based on the operating mode, the process image of these I/O modules is then the
same as that of the respective version.
The above SSI Transmitter Interface modules have a total of 4 bytes of user data
in the Input Process Image, which has 2 words mapped into the image.
Word alignment is applied.
Table 315: SSI Transmitter Interface Modules
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D1
D0
n+1
D3
D2
Description
Data bytes
The specialty modules represent 2x2 bytes input data and seize 2 Instances in
Class (0x67).
Manual
Version 1.1.0
260
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
750-630/000-004, -005, -007
In the input process image, SSI transmitter interface modules with status occupy 5
usable bytes, 4 data bytes, and 1 additional status byte. A total of 3 words are
assigned in the process image via word alignment.
Table 316: SSI Transmitter Interface I/O Modules with an Alternative Data Format
Input Process Image
Byte Destination
Instance
Description
High Byte
High Byte
S
not used
Status byte
n
D1
D0
Data bytes
D3
D2
The specialty modules represent 1x6 bytes and seize 1 Instance in Class (0x67).
12.3.5.7
Incremental Encoder Interface Modules
750-631/000-004, -010, -011
The above Incremental Encoder Interface modules have 5 bytes of input data and
3 bytes of output data. The following tables illustrate the Input and Output Process
Image, which have 4 words into each image. Word alignment is applied.
Table 317: Incremental Encoder Interface Modules 750-631/000-004, -010, -011
Input Process Image
Byte Destination
Instance
Description
High Byte
Low Byte
S
not used
Status byte
D1
D0
Counter word
n
not used
D4
D3
Latch word
The specialty modules represent 1x6 bytes input data and seize 1 Instance in Class
(0x67).
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
C
D1
D0
-
Description
Control byte of counter 1
Counter setting value of counter 1
not used
not used
And the specialty modules represent 1x6 bytes output data and seize 1
Instance in Class (0x68).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
261
750-634
The above Incremental Encoder Interface module has 5 bytes of input data (6
bytes in cycle duration measurement mode) and 3 bytes of output data. The
following tables illustrate the Input and Output Process Image, which has 4 words
mapped into each image. Word alignment is applied.
Table 318: Incremental Encoder Interface Modules 750-634
Input Process Image
Byte Destination
Instance
Description
High Byte
Low Byte
S
not used
Status byte
D1
D0
Counter word
n
(D2) *)
not used
(Periodic time)
D4
D3
Latch word
*)
If cycle duration measurement mode is enabled in the control byte, the cycle duration is
given as a 24-bit value that is stored in D2 together with D3/D4.
The specialty modules represent 1x6 bytes input data and seize 1 Instance in Class
(0x67).
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
C
D1
D0
-
Description
not used
Control byte
Counter setting word
not used
And the specialty modules represent 1x6 bytes output data and seize 1 Instance in
Class (0x68).
750-637
The above Incremental Encoder Interface Module has a total of 6 bytes of user
data in both the Input and Output Process Image (4 bytes of encoder data and 2
bytes of control/status). The following table illustrates the Input and Output
Process Image, which have 4 words mapped into each image. Word alignment is
applied.
Table 319: Incremental Encoder Interface Modules 750-637
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
C0/S0
n
D1
D0
C1/S1
n+1
D3
D2
Description
Control/Status byte of Channel 1
Data Value of Channel 1
Control/Status byte of Channel 2
Data Value of Channel 2
The specialty modules represent 2x3 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
Manual
Version 1.1.0
262
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
750-635,
753-635
The above Digital Pulse Interface module has a total of 4 bytes of user data in
both the Input and Output Process Image (3 bytes of module data and 1 byte of
control/status). The following table illustrates the Input and Output Process
Image, which have 2 words mapped into each image. Word alignment is applied.
Table 320: Incremental Encoder Interface Modules 750-635, 750-635
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D0
C0/S0
D2
D1
Description
Control/status
byte
Data bytes
Data byte
The specialty modules represent 1x4 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
12.3.5.8
DC-Drive Controller
750-636
The DC-Drive Controller maps 6 bytes into both the input and output process
image. The data sent and received are stored in up to 4 input and output bytes
(D0 ... D3). Two control bytes (C0, C1) and two status bytes (S0/S1) are used to
control the I/O module and the drive.
In addition to the position data in the input process image (D0 … D3), it is
possible to display extended status information (S2 … S5). Then the three control
bytes (C1 … C3) and status bytes (S1 … S3) are used to control the data flow.
Bit 3 of control byte C1 (C1.3) is used to switch between the process data and the
extended status bytes in the input process image (Extended Info_ON). Bit 3 of
status byte S1 (S1.3) is used to acknowledge the switching process.
Table 321: DC-Drive Controller 750-636
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
S1
S0
D1*) / S3**)
D0*) / S2**)
D3*) / S5**)
D2*) / S4**)
n
*)
**)
Description
Status byte S1
Status byte S0
Actual position*) Actual position
/ Extended status (LSB) / Extended
byte S3**)
status byte S2**)
Actual position
Actual position*)
(MSB) /
/ Extended status
Extended status
byte S4**)
byte S3**)
ExtendedInfo_ON = ‘0’.
ExtendedInfo_ON = ‘1’.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
263
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
C1
C0
D1
D0
D3
D2
Description
Control byte C1 Control byte C0
Setpoint position Setpoint position
(LSB)
Setpoint position Setpoint position
(MSB)
The specialty modules represent 1x6 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
12.3.5.9
Steppercontroller
750-670
The Steppercontroller RS422 / 24 V / 20 mA 750-670 provides the fieldbus
coupler 12 bytes input and output process image via 1 logical channel. The data to
be sent and received are stored in up to 7 output bytes (D0 … D6) and 7 input
bytes (D0 … D6), depending on the operating mode.
Output byte D0 and input byte D0 are reserved and have no function assigned.
One I/O module control and status byte (C0, S0) and 3 application control and
status bytes (C1 ... C3, S1 ... S3) provide the control of the data flow.
Switching between the two process images is conducted through bit 5 in the
control byte (C0 (C0.5). Activation of the mailbox is acknowledged by bit 5 of the
status byte S0 (S0.5).
Table 322: Steppercontroller RS 422 / 24 V / 20 mA 750-670
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
reserved
S0
D1
D0
D3
D2
n
D5
D4
S3
*)
**)
Manual
Version 1.1.0
D6
S1
S2
Cyclic process image (Mailbox disabled)
Mailbox process image (Mailbox activated)
Description
reserved
Status byte S0
Process data*) / Mailbox**)
Status byte S3
Status byte S1
Process data*) /
reserved**)
Status byte S2
264
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
reserved
C0
D1
D0
D3
D2
D5
D4
C3
D6
C1
C2
Cyclic process image (Mailbox disabled)
Mailbox process image (Mailbox activated)
*)
**)
Description
reserved
Control byte C0
Process data*) / Mailbox**)
Process data*) /
reserved**)
Control byte C1 Control byte C2
Control byte C3
The specialty modules represent 1x12 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
12.3.5.10 RTC Module
750-640
The RTC Module has a total of 6 bytes of user data in both the Input and Output
Process Image (4 bytes of module data and 1 byte of control/status and 1 byte ID
for command). The following table illustrates the Input and Output Process
Image, which have 3 words mapped into each image. Word alignment is applied.
Table 323: RTC Module 750-640
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
ID
C/S
D1
D3
D0
D2
Description
Command byte
Control/status
byte
Data bytes
The specialty modules represent 1x6 bytes input data and seize 1 Instance in Class
(0x67).and seize 1 Instance in Class (0x68).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
265
12.3.5.11 DALI/DSI Master Module
750-641
The DALI/DSI Master module has a total of 6 bytes of user data in both the Input
and Output Process Image (5 bytes of module data and 1 byte of control/status).
The following tables illustrate the Input and Output Process Image, which have 3
words mapped into each image. Word alignment is applied.
Table 324: DALI/DSI Master module 750-641
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
D0
S
n
D2
D1
D4
D3
Description
DALI Response
Status byte
Message 3
DALI Address
Message 1
Message 2
The specialty modules represent 1x6 bytes input data and seize 1
Instance in Class (0x67).
Output Process Image
Instance
n
Byte Destination
High Byte
Low Byte
D0
C
D2
D4
D1
D3
Description
DALI command,
DSI dimming value
Parameter 2
Command extension
Control byte
DALI Address
Parameter 1
And the specialty modules represent 1x6 bytes output data and seize 1
Instance in Class (0x68).
12.3.5.12 EnOcean Radio Receiver
750-642
The EnOcean radio receiver has a total of 4 bytes of user data in both the Input
and Output Process Image (3 bytes of module data and 1 byte of control/status).
The following tables illustrate the Input and Output Process Image, which have 2
words mapped into each image. Word alignment is applied.
Table 325: EnOcean Radio Receiver 750-642
Input Process Image
Byte Destination
Instance
High Byte
Low Byte
n
D0
S
n+1
D2
D1
Description
Data byte
Status byte
Data bytes
Output Process Image
Instance
n
n+1
Byte Destination
High Byte
Low Byte
C
-
Description
not used
Control byte
not used
The specialty modules represent 2x2 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
Manual
Version 1.1.0
266
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.5.13 MP Bus Master Module
750-643
The MP Bus Master Module has a total of 8 bytes of user data in both the Input
and Output Process Image (6 bytes of module data and 2 bytes of control/status).
The following table illustrates the Input and Output Process Image, which have 4
words mapped into each image. Word alignment is applied.
Table 326: MP Bus Master Module 750-643
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
C1/S1
C0/S0
D1
D3
D5
D0
D2
D4
Description
extended
Control/
Status byte
Control/status
byte
Data bytes
The specialty modules represent 1x8 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
12.3.5.14 Bluetooth® RF-Transceiver
750-644
The size of the process image for the Bluetooth® module can be adjusted to 12, 24
or 48 bytes.
It consists of a control byte (input) or status byte (output); an empty byte; an
overlayable mailbox with a size of 6, 12 or 18 bytes (mode 2); and the Bluetooth®
process data with a size of 4 to 46 bytes.
Thus, each Bluetooth® module uses between 12 and 48 bytes in the process image.
The sizes of the input and output process images are always the same.
The first byte contains the control/status byte; the second contains an empty byte.
Process data attach to this directly when the mailbox is hidden. When the mailbox
is visible, the first 6, 12 or 18 bytes of process data are overlaid by the mailbox
data, depending on their size. Bytes in the area behind the optionally visible
mailbox contain basic process data. The internal structure of the Bluetooth®
process data can be found in the documentation for the Bluetooth® 750-644 RF
Transceiver.
The mailbox and the process image sizes are set with the startup tool WAGO-I/OCHECK.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Table 327: Bluetooth® RF-Transceiver 750-644
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
-
C0/S0
D1
D3
D5
...
D45
D0
D2
D4
...
D44
267
Description
not used
Control/status
byte
Mailbox (0, 3, 6 or 9 words) and
Process data (2-23 words)
The 750-644 constitutes a special module, whose process data (12, 24 or 48 bytes)
occupy on instances in classes 0x67 and 0x68.
12.3.5.15 Vibration Velocity/Bearing Condition Monitoring VIB I/O
750-645
The Vibration Velocity/Bearing Condition Monitoring VIB I/O has a total of 12
bytes of user data in both the Input and Output Process Image (8 bytes of module
data and 4 bytes of control/status). The following table illustrates the Input and
Output Process Image, which have 8 words mapped into each image.
Word alignment is applied.
Table 328: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645
Input and Output Process Image
Byte Destination
Instance
Description
High Byte
Low Byte
Control/status byte
C0/S0
not used
(log. Channel 1, Sensor input 1)
n
Data bytes
D1
D0
(log. Channel 1, Sensor input 1)
Control/status byte
C1/S1
not used
(log. Channel 2, Sensor input 2)
n+1
Data bytes
D3
D2
(log. Channel 2, Sensor input 2)
Control/status byte
C2/S2
not used
(log. Channel 3, Sensor input 1)
n+2
Data bytes
D5
D4
(log. Channel 3, Sensor input 3)
Control/status byte
C3/S3
not used
(log. Channel 4, Sensor input 2)
n+3
Data bytes
D7
D6
(log. Channel 4, Sensor input 2)
The specialty modules represent 4x3 bytes input and output data and seize 4
Instances in Class (0x67) and 4 Instances in Class (0x68).
Manual
Version 1.1.0
268
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.5.16 AS-interface Master Module
750-655
The length of the process image of the AS-interface master module can be set to
fixed sizes of 12, 20, 24, 32, 40 or 48 bytes.
It consists of a control or status byte, a mailbox with a size of 0, 6, 10, 12 or 18
bytes and the AS-interface process data, which can range from 0 to 32 bytes.
The AS-interface master module has a total of 6 to maximally 24 words data in
both the Input and Output Process Image. Word alignment is applied.
The first Input and output word, which is assigned to an AS-interface master
module, contains the status / control byte and one empty byte.
Subsequently the mailbox data are mapped, when the mailbox is permanently
superimposed (Mode 1).
In the operating mode with suppressible mailbox (Mode 2), the mailbox and the
cyclical process data are mapped next.
The following words contain the remaining process dat.
The mailbox and the process image sizes are set with the startup tool WAGO-I/OCHECK.
Table 329: AS-interface Master module 750-655
Input and Output Process Image
Byte Destination
Instance
High Byte
Low Byte
n
-
C0/S0
D1
D3
D5
...
D45
D0
D2
D4
...
D44
Description
not used
Control/status
byte
Mailbox (0, 3, 5, 6 or 9 words)/
Process data (0-16 words)
The specialty modules represent 1x 12...48 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
12.3.6
System Modules
12.3.6.1
System Modules with Diagnostics
Table of Contents
269
750-610, -611
The modules provide 2 bits of diagnostics in the Input Process Image for
monitoring of the internal power supply.
Table 330: System Modules with Diagnostics 750-610, -611
Input Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnostic Diagnostic
bit S 2
bit S 1
Fuse
Fuse
The system modules seize 2 Instances in Class (0x65).
12.3.6.2
Binary Space Module
750-622
The Binary Space Modules behave alternatively like 2 channel digital input
modules or output modules and seize depending upon the selected settings 1, 2, 3
or 4 bits per channel. According to this, 2, 4, 6 or 8 bits are occupied then either in
the process input or the process output image.
Table 331: Binary Space Module 750-622 (with behavior like 2 channel digital input)
Input and Output Process Image
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
(Data bit
(Data bit
(Data bit
(Data bit
(Data bit
(Data bit
Data bit
DI 8)
DI 7)
DI 6)
DI 5)
DI 4)
DI 3)
DI 2
Bit 0
Data bit
DI 1
The Binary Space Modules seize 2, 4, 6 or 8 Instances in class (0x65) or in Class
(0x66).
Manual
Version 1.1.0
270
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
13
Application Examples
13.1
Test of MODBUS protocol and fieldbus nodes
You require a MODBUS master to test the function of your fieldbus node. For
this purpose, various manufacturers offer a range of PC applications that you can,
in part, download from the Internet as free of charge demo versions.
One of the programs which is particularly suitable to test your ETHERNET
TCP/IP fieldbus node, is for instance ModScan from Win-Tech.
Information
Additional Information
A free of charge demo version from ModScan32 and further utilities from WinTech can be found in the Internet under:
http://www.win-tech.com/html/demos.htm
ModScan32 is a Windows application that works as a MODBUS master.
This program allows you to access the data points of your connected ETHERNET
TCP/IP fieldbus node and to proceed with the desired changes.
Information
Additional Information
For a description example relating to the software operation, refer to:
http://www.win-tech.com/html/modscan32.htm
13.2
Visualization and Control using SCADA Software
This chapter is intended to give insight into how the WAGO ETHERNET fieldbus
coupler/controller can be used for process visualization and control using standard
user software.
There is a wide range of process visualization programs, called SCADA Software,
from various manufacturers.
Information
Additional Information
For a selection of SCADA products, look under i.e.:
http://www.abpubs.demon.co.uk/scadasites.htm
SCADA is the abbreviation for Supervisory Control and Data Acquisition.
It is a user-orientated tool used as a production information system in the areas of
automation technology, process control and production monitoring.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
271
The use of SCADA systems includes the areas of visualization and monitoring,
data access, trend recording, event and alarm processing, process analysis and
targeted intervention in a process (control).
The WAGO ETHERNET fieldbus node provides the required process input and
output values.
Note
SCADA software has to provide a MODBUS device driver and support
MODBUS/TCP functions!
When choosing suitable SCADA software, ensure that it provides a MODBUS
device driver and supports the MODBUS/TCP functions in the coupler.
Visualization programs with MODBUS device drivers are available from i.e.
Wonderware, National Instruments, Think&Do or KEPware Inc., some of which
are available on the Internet as demo versions.
The operation of these programs is very specific.
However, a few essential steps are described to illustrate the way an application
can be developed using a WAGO ETHERNET fieldbus node and SCADA
software in principle:
1.
Load the MODBUS ETHERNET driver and select MODBUS ETHERNET
2.
Enter the IP address for addressing the fieldbus node
At this point, some programs allow the user to give the node an alias name, i.e. to
call the node "Measuring data". The node can then be addressed with this name.
3.
Create a graphic object, such as a switch (digital) or a potentiometer
(analog)
This object is displayed on the work area.
4.
Link the object to the desired data point on the node by entering the
following data:
•
•
•
Node address (IP address or alias name)
The desired MODBUS function codes (register/bit read/write)
The MODBUS address of the selected channel
Entry is program specific.
Depending on the user software the MODBUS addressing of a bus module can be
represented with up to 5 digits.
Manual
Version 1.1.0
272
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Example of the MODBUS Addressing
In the case of SCADA Software Lookout from National Instruments the
MODBUS function codes are used with a 6 digit coding, whereby the first digit
represents the MODBUS table (0, 1, 3 or 4) and implicit the function code (see
following table):
Table 332: MODBUS table and function codes
MODBUS table
MODBUS function code
0
FC1 or
Reading of input bits or
FC15
writing of several output bits
1
FC2
Reading of several input bits
3
FC4 or
Reading of several input registers or
FC 16
writing of several output registers
4
FC3
Reading of several input registers
The following five digits specify the channel number (beginning with 1) of the
consecutively numbered digital or analog input and/or output channels.
Examples:
•
•
Reading/writing the first digital input:
Reading/writing the second analog input:
i.e. 0 0000 1
i.e. 3 0000 2
Application Example:
Thus, the digital input channel 2 of the above node "Measuring data" can be read
out with the input: "Measuring data. 0 0000 2".
Exemplary node "Measuring data"
Adapt the addressing of the SCADA
software to the process image of the node
ETHERNET TCP/IP
Hub
MODBUS protocol
ETHERNET
adapter
Figure 57: Example SCADA software with MODBUS driver
Information
Additional Information
Please refer to the respective SCADA product manual for a detailed description of
the particular software operation.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
14
Table of Contents
273
Use in Hazardous Environments
The WAGO-I/O-SYSTEM 750 (electrical equipment) is designed for use in
Zone 2 hazardous areas.
The following sections include both the general identification of components
(devices) and the installation regulations to be observed. The individual
subsections of the "Installation Regulations" section must be taken into account if
the I/O module has the required approval or is subject to the range of application
of the ATEX directive.
Manual
Version 1.1.0
274
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
14.1
Identification
14.1.1
For Europe according to CENELEC and IEC
Figure 58: Example for lateral labeling of bus modules
Figure 59: Printing on text detail in accordance with CENELEC and IEC
Table 333: Description of Printing on
Printing on Text
DEMKO 08 ATEX 142851 X
IECEx PTB 07.0064X
I M2 / II 3 GD
Ex nA
IIC
T4
Description
Approval body and/or number of the examination
certificate
Explosion protection group and Unit category
Type of ignition and extended identification
Explosion protection group
Temperature class
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table of Contents
Figure 60: Example of side marking of Ex i and IEC Ex i approved I/O modules
Figure 61: Inscription text detail acc. CENELEC and IEC
Manual
Version 1.1.0
275
276
Table of Contents
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 334: Description of the inscription
Inscription text
TÜV 07 ATEX 554086 X
TUN 09.0001X
Dust
II
3(1)D
Ex
tD
[iaD]
A22
IP6X
T 135°C
Mining
I
(M2)
[Ex ia]
I
Gases
II
3(1)G
Ex
nA
[ia]
IIC
T4
Description
Approving authority or
certificate numbers
Device group: All except mining
Device category: Zone 22 device (Zone 20 subunit)
Explosion protection mark
Protection by enclosure
Approved in accordance with "Dust intrinsic safety"
standard
Surface temperature determined according to
Procedure A, use in Zone 22
Dust-tight (totally protected against dust)
Max. surface temp. of the enclosure (no dust bin)
Device group: Mining
Device category: High degree of safety
Explosion protection: Mark with category of type of
protection intrinsic safety: Even safe when two
errors occur
Device group: Mining
Device group: All except mining
Device category: Zone 2 device (Zone 0 subunit)
Explosion protection mark
Type of protection: Non-sparking operating
equipment
Category of type of protection intrinsic safety: Even
safe when two errors occur
Explosion Group
Temperature class: Max. surface temperature 135°C
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
14.1.2
Table of Contents
For America according to NEC 500
Figure 62: Example for lateral labeling of bus modules
Figure 63: Printing on text detail in accordance with NEC
Table 335: Description of Printing on
Printing on Text
CL 1
DIV 2
Grp. ABCD
Optemp code T4
Manual
Version 1.1.0
Description
Explosion protection group (condition of use
category)
Area of application (zone)
Explosion group (gas group)
Temperature class
277
278
Table of Contents
14.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Installation Regulations
In the Federal Republic of Germany, various national regulations for the
installation in explosive areas must be taken into consideration. The basis for this
forms the working reliability regulation, which is the national conversion of the
European guideline 99/92/E6. They are complemented by the installation
regulation EN 60079-14. The following are excerpts from additional VDE
regulations:
Table 336: VDE Installation Regulations in Germany
DIN VDE 0100 Installation in power plants with rated voltages up to 1000 V
DIN VDE 0101 Installation in power plants with rated voltages above 1 kV
DIN VDE 0800 Installation and operation in telecommunication plants including
information processing equipment
DIN VDE 0185 lightning protection systems
The USA and Canada have their own regulations. The following are excerpts
from these regulations:
Table 337: Installation Regulations in USA and Canada
NFPA 70
National Electrical Code Art. 500 Hazardous Locations
ANSI/ISA-RP 12.6-1987 Recommended Practice
C22.1
Canadian Electrical Code
Notice the following points
When using the WAGO-I/O SYSTEM 750 (electrical operation) with Ex
approval, the following points are mandatory:
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
14.2.1
Table of Contents
279
Special Conditions for Safe Operation of the ATEX and IEC
Ex (acc. DEMKO 08 ATEX 142851X and IECEx PTB 07.0064)
The fieldbus-independent I/O modules of the WAGO-I/O-SYSTEMs 750-.../...-...
Must be installed in an environment with degree of pollution 2 or better. In the
final application, the I/O modules must be mounted in an enclosure with IP 54
degree of protection at a minimum with the following exceptions:
-
I/O modules 750-440, 750-609 and 750-611 must be installed in an IP 64
minimum enclosure.
I/O module 750-540 must be installed in an IP 64 minimum enclosure for
230 V AC applications.
I/O module 750-440 may be used up to max. 120 V AC.
When used in the presence of combustible dust, all devices and the enclosure shall
be fully tested and assessed in compliance with the requirements of IEC 612410:2004 and IEC 61241-1:2004.
I/O modules fieldbus plugs or fuses may only be installed, added, removed or
replaced when the system and field supply is switched off or the area exhibits no
explosive atmosphere.
DIP switches, coding switches and potentiometers that are connected to the I/O
module may only be operated if an explosive atmosphere can be ruled out.
I/O module 750-642 may only be used in conjunction with antenna 758-910 with
a max. cable length of 2.5 m.
To exceed the rated voltage no more than 40%, the supply connections must have
transient protection.
The permissible ambient temperature range is 0 °C to +55 °C.
Manual
Version 1.1.0
280
Table of Contents
14.2.2
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Special Conditions for Safe Operation of the Ex i (acc. TÜV
07 ATEX 554086 X)
1.
For operation as a Category 3 Device (in Zone 2 or 22), the WAGO-I/OSYSTEM 750-*** must be mounted in an enclosure that fulfills the
requirements of the directive 94/9/EG and the relevant standards (see
designation) EN 60079-0, EN 60079-11, EN 60079-15, EN 61241-0 and EN
61241-1. For operation as a Group I Category M2 device, the device must
be mounted in a housing that ensures adequate protection according to both
EN 60079-0 and EN 60079-1, while meeting IP64 protection. A declaration
of conformity according to appendix X of directive 94/9/EG must confirm
the correct installation of the devices above in the enclosure or switchgear
cabinet.
2.
If the interface circuits are operated without the fieldbus coupler station of
type 750-3../...-... (DEMKO 08 ATEX 142851 X), then measures must be
taken outside of the device so that the rated voltage will not be exceeded by
more than 40% due to temporary faults.
3.
DIP switches, coding switches and potentiometers that are connected to the
module may only be operated if an explosive atmosphere can be ruled out.
4.
Non-intrinsically safe circuits may only be connected and disconnected for
installation, maintenance and repair. Explosive atmosphere and installation,
maintenance or repair occurring simultaneously must be ruled out.
5.
For types 750-606, 750-625/000-001, 750-487/003-000, 750-484, the
following must be taken into account: The interface circuits must be limited
to overvoltage category I/II/III (electrical circuits without power
supply/electrical circuits with power supply) as defined in EN 60664-1.
6.
For type 750-601, the following must be taken into account: The fuse must
not be removed or replaced while the device is running.
7.
The permissible ambient temperature range is 0 °C ≤ Ta ≤ +55 °C.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
14.2.3
Table of Contents
281
Special Conditions for the Safe Operation of the IEC Ex i
(acc. TUN 09.0001 X)
1.
For operation as a Dc or Gc device (in Zone 2 or 22), the WAGO-I/OSYSTEM 750-*** must be mounted in an enclosure that fulfills the
requirements for a device of the relevant standards (see designation) IEC
60079-0, IEC 60079-11, IEC 60079-15, IEC 61241-0 and IEC 61241-1. For
operation as a Group I Category M2 device, the device must be mounted in
a housing that ensures adequate protection according to both EN 60079-0
and EN 60079-1, while meeting IP64 protection. A declaration of
conformity must confirm compliance with these requirements and correct
installation of the devices above in the enclosure or switchgear cabinet by
an Ex certification authority.
2.
Outside the device, measures must be taken so that the rated voltage will not
be exceeded by more than 40% due to temporary faults.
3.
DIP switches, coding switches and potentiometers that are connected to the
module may only be operated if an explosive atmosphere can be ruled out.
4.
Non-intrinsically safe circuits may only be connected and disconnected for
installation, maintenance and repair. Explosive atmosphere and installation,
maintenance or repair occurring simultaneously must be ruled out.
5.
For types 750-606, 750-625/000-001, 750-487/003-000, 750-484, the
following must be taken into account: The interface circuits must be limited
to overvoltage category I/II/III (electrical circuits without power
supply/electrical circuits with power supply) as defined in EN 60664-1.
6.
For type 750-601, the following must be taken into account: The fuse must
not be removed or replaced while the device is running.
7.
The permissible ambient temperature range is 0 °C ≤ Ta ≤ +55 °C.
Manual
Version 1.1.0
282
Table of Contents
14.2.4
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
ANSI/ISA 12.12.01
This equipment is suitable for use in Class I, Division 2, Groups A, B, C, D or
non-hazardous locations only.
NOTICE
Explosion hazard!
Explosion hazard - substitution of components may impair suitability for Class I,
Div. 2.
NOTICE
Disconnect device when power is off and only in a non-hazardous area!
Do not disconnect equipment unless power has been switched off or the area is
known to be non-hazardous.
When a fuse is provided, the following marking shall be provided:
”A switch suitable for the location where the equipment is installed shall be
provided to remove the power from the fuse”.
The switch need not be integrated in the equipment.
For devices with Ethernet connectors:
”Only for use in LAN, not for connection to telecommunication circuits”.
NOTICE
Use only with antenna module 758-910!
Use Module 750-642 only with antenna module 758-910.
Additional Information
Proof of certification is available on request. Also take note of the information
given on the module technical information sheet. The Instruction Manual,
containing these special conditions for safe use, must be readily available to the
user.
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
List of Figures
283
List of Figures
Figure 1: Fieldbus node......................................................................................... 18
Figure 2: Example of a manufacturing number..................................................... 19
Figure 3: Isolation ................................................................................................. 23
Figure 4: System supply ........................................................................................ 24
Figure 5: System voltage....................................................................................... 25
Figure 6: Field supply (sensor/actuator)................................................................ 28
Figure 7: Supply module with fuse carrier (Example 750-610)............................ 30
Figure 8: Removing the fuse carrier...................................................................... 30
Figure 9: Opening the fuse carrier......................................................................... 31
Figure 10: Change fuse.......................................................................................... 31
Figure 11: Fuse modules for automotive fuses, series 282 ................................... 32
Figure 12: Fuse modules for automotive fuses, series 2006 ................................. 32
Figure 13: Fuse modules with pivotable fuse carrier, series 281 .......................... 32
Figure 14: Fuse modules with pivotable fuse carrier, series 2002 ........................ 32
Figure 15: Supply example.................................................................................... 33
Figure 16: Carrier rail contact ............................................................................... 36
Figure 17: Ring-feeding ........................................................................................ 37
Figure 18: Example WAGO Shield (Screen) Connecting System........................ 39
Figure 19: Application of the WAGO Shield (Screen) Connecting System......... 39
Figure 20: View ETHERNET TCP/IP Fieldbus Coupler ..................................... 42
Figure 21: Device Supply...................................................................................... 44
Figure 22: RJ-45-Connector.................................................................................. 45
Figure 23: Display Elements ................................................................................. 46
Figure 24: Service Interface for the configuration (closed and opened flap)........ 47
Figure 25: Address Selection Switch .................................................................... 48
Figure 26: Spacing................................................................................................. 57
Figure 27: Unlocking lug ...................................................................................... 60
Figure 28: Insert I/O module ................................................................................. 61
Figure 29: Snap the I/O module into place............................................................ 61
Figure 30: Removing the I/O module.................................................................... 62
Figure 31: Data contacts........................................................................................ 63
Figure 32: Example for the arrangement of power contacts ................................. 64
Figure 33: Connecting a conductor to a CAGE CLAMP® .................................... 65
Figure 34: Operating System................................................................................. 66
A Figure 35: Memory areas and data exchange .................................................... 70
Figure 36: Data exchange between MODBUS Master and I/O modules.............. 73
Figure 37: Address selection switch...................................................................... 78
Figure 38: WBM page "Port"................................................................................ 81
Figure 39: WBM page "Information" ................................................................... 86
Figure 40: WBM page "Port"................................................................................ 87
Figure 41: Example for the Function test of a Fieldbus Node .............................. 89
Figure 42: WBM page "Information" ................................................................... 94
Figure 43: WBM page "Ethernet" ......................................................................... 96
Figure 44: WBM page "TCP/IP"........................................................................... 99
Figure 45: WBM page "Port".............................................................................. 101
Figure 46: WBM page "SNMP".......................................................................... 104
Figure 47: WBM page "SNMP V3".................................................................... 106
Figure 48: WBM page „Watchdog“.................................................................... 108
Manual
Version 1.1.0
284
List of Figures
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Figure 49: WBM page "Security" ....................................................................... 111
Figure 50: WBM page "Features" ....................................................................... 113
Figure 51: WBM page "IO config" ..................................................................... 114
Figure 52: Display Elements ............................................................................... 115
Figure 53: Node status - I/O LED signaling........................................................ 118
Figure 54: Error message coding......................................................................... 118
Figure 55: Function block for determining loss of fieldbus, independently of
protocol ...................................................................................................... 124
Figure 56: Use of the MODBUS Functions ........................................................ 144
Figure 57: Example SCADA software with MODBUS driver ........................... 272
Figure 58: Example for lateral labeling of bus modules ..................................... 274
Figure 59: Printing on text detail in accordance with CENELEC and IEC ........ 274
Figure 60: Example of side marking of Ex i and IEC Ex i approved I/O modules
.................................................................................................................... 275
Figure 61: Inscription text detail acc. CENELEC and IEC................................. 275
Figure 62: Example for lateral labeling of bus modules ..................................... 277
Figure 63: Printing on text detail in accordance with NEC ................................ 277
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
List of Tables
285
List of Tables
Table 1: Number Notation..................................................................................... 13
Table 2: Font Conventions .................................................................................... 13
Table 3: Alignment................................................................................................ 25
Table 4: Power supply modules ............................................................................ 29
Table 5: WAGO Power Supply Unit..................................................................... 34
Table 6: WAGO ground wire terminals ................................................................ 35
Table 7: Legend to the View ETHERNET TCP/IP Fieldbus Coupler.................. 43
Table 8: RJ-45 Connector and RJ-45 Connector Configuration ........................... 45
Table 9: Display Elements Fieldbus Status........................................................... 46
Table 10: Display Elements Node Status .............................................................. 46
Table 11: Service Interface.................................................................................... 47
Table 12: Technical Data - Device........................................................................ 49
Table 13: Technical Data - System ....................................................................... 49
Table 14: Technical data – Accessories ............................................................... 50
Table 15: Technical Data Wire Connection .......................................................... 50
Table 16: Technical Data - Climatic environmental conditions........................... 51
Table 17: Technical data – Mechanical strength................................................... 51
Table 18: WAGO DIN Rail................................................................................... 57
Table 19: Data width of the I/O Modules.............................................................. 67
Table 20: Data with for I/O modules..................................................................... 71
Table 21: Allocation of digital inputs and outputs to process data words in
accordance with the...................................................................................... 72
Table 22: WBM page "Information"..................................................................... 95
Table 23: WBM page "Ethernet" .......................................................................... 97
Table 24: WBM page „TCP/IP“.......................................................................... 100
Table 25: WBM page "Port" ............................................................................... 102
Table 26: WBM page "SNMP" ........................................................................... 105
Table 27: WBM page "Watchdog"...................................................................... 109
Table 28: WBM page "Security"......................................................................... 112
Table 29: WBM page "Features" ........................................................................ 113
Table 30: WBM page "I/O configuration" .......................................................... 114
Table 31: LED assignment for diagnostics ......................................................... 115
Table 32: Fieldbus diagnostics – solution in event of error ................................ 116
Table 33: Node status diagnostics – solution in event of error ........................... 117
Table 34: Blink code- table for the 'I/O' LED signaling, error code 1 ................ 119
Table 35: Blink code table for the 'I/O' LED signaling, error code 2 ................. 120
Table 36: Blink code table for the 'I/O' LED signaling, error code 3 ................. 121
Table 37: Blink code table for the 'I/O' LED signaling, error code 4 ................. 122
Table 38: Blink code table for the 'I/O' LED signaling, error code 5 ................. 122
Table 39: Blink code- table for the I/O LED signaling, error code 6.................. 123
Table 40: IP Packet.............................................................................................. 126
Table 41: Network Class A ................................................................................. 127
Table 42: Network Class B ................................................................................. 127
Table 43: Network Class C ................................................................................. 127
Table 44: Key Data Class A, B and C................................................................. 128
Table 45: Class B Address with Field for Subnet IDs ........................................ 129
Table 46: Subnet mask for Class A network....................................................... 129
Table 47: Subnet mask for Class B network ....................................................... 129
Manual
Version 1.1.0
286
List of Tables
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 48: Subnet mask for Class C network ....................................................... 129
Table 49: Example for an IP address from a Class B network............................ 129
Table 50: BootP options ...................................................................................... 133
Table 51: Meaning of DHCP options.................................................................. 136
Table 52: MIB II groups...................................................................................... 138
Table 53: Standard Traps .................................................................................... 139
Table 54: MODBUS/TCP header........................................................................ 141
Table 55: Basic data types of MODBUS protocol .............................................. 142
Table 56: List of the MODBUS Functions in the Fieldbus Coupler................... 142
Table 57: Exception odes .................................................................................... 145
Table 58: Request of Function code FC1........................................................... 146
Table 59: Response of Function code FC1 ......................................................... 146
Table 60: Assignment of inputs........................................................................... 147
Table 61: Exception of Function code FC1......................................................... 147
Table 62: Request of Function code FC2............................................................ 148
Table 63: Response of Function code FC2 ......................................................... 148
Table 64: Assignment of inputs........................................................................... 148
Table 65: Exception of Function code FC2......................................................... 149
Table 66: Request of Function code FC3............................................................ 150
Table 67: Response of Function code FC3 ......................................................... 150
Table 68: Exception of Function code FC3......................................................... 150
Table 69: Request of Function code FC4............................................................ 151
Table 70: Response of Function code FC4 ......................................................... 151
Table 71: Exception of Function code FC4......................................................... 151
Table 72: Request of Function code FC5............................................................ 152
Table 73: Response of Function code FC5 ......................................................... 152
Table 74: Exception of Function code FC5......................................................... 152
Table 75: Request of Function code FC6............................................................ 153
Table 76: Response of Function code FC6 ......................................................... 153
Table 77: Exception of Function code FC6......................................................... 153
Table 78: Request of Function code FC11.......................................................... 154
Table 79: Response of Function code FC11 ....................................................... 154
Table 80: Exception of Function code FC 11...................................................... 154
Table 81: Request of Function code FC15.......................................................... 155
Table 82: Response of Function code FC15 ....................................................... 155
Table 83: Exception of Function code FC15....................................................... 156
Table 84: Request of Function code FC16.......................................................... 157
Table 85: Response of Function code FC16 ....................................................... 157
Table 86: Exception of Function code FC16....................................................... 157
Table 87: Request of Function code FC22.......................................................... 158
Table 88: Response of Function code FC22 ....................................................... 158
Table 89: Exception of Function code FC22....................................................... 158
Table 90: Request of Function code FC23.......................................................... 159
Table 91: Response of Function code FC23 ....................................................... 159
Table 92: Exception of Function code FC23....................................................... 159
Table 93: Register Access Reading (with FC3 and FC4) ................................... 161
Table 94: Register Access Writing (with FC6 and FC16) .................................. 162
Table 95: Bit Access Reading (with FC1 and FC2)............................................ 163
Table 96: Bit Access Writing (with FC5 and FC15)........................................... 163
Table 97: MODBUS registers ............................................................................. 164
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
List of Tables
287
Table 98: MODBUS registers (Continuation)..................................................... 165
Table 99: Register address 0x1000 ..................................................................... 166
Table 100: Register address 0x1001 ................................................................... 166
Table 101: Register address 0x1002 ................................................................... 167
Table 102: Register address 0x1003 ................................................................... 167
Table 103: Register address 0x1004 ................................................................... 167
Table 104: Register address 0x1005 ................................................................... 167
Table 105: Register address 0x1006 ................................................................... 167
Table 106: Register address 0x1007 ................................................................... 168
Table 107: Register address 0x1008 ................................................................... 168
Table 108: Register address 0x1009 ................................................................... 168
Table 109: Register address 0x100A................................................................... 168
Table 110: Starting Watchdog............................................................................. 169
Table 111: Register address 0x100B................................................................... 169
Table 112: Register address 0x1020 ................................................................... 170
Table 113: Register address 0x1021 ................................................................... 170
Table 114: Register address 0x1022 ................................................................... 171
Table 115: Register address 0x1023 ................................................................... 171
Table 116: Register address 0x1024 ................................................................... 171
Table 117: Register address 0x1025 ................................................................... 171
Table 118: Register address 0x1028 ................................................................... 171
Table 119: Register address 0x1029 ................................................................... 172
Table 120: Register address 0x102A................................................................... 172
Table 121: Register address 0x102B................................................................... 172
Table 122: Register address 0x1030 ................................................................... 172
Table 123: Register address 0x1031 ................................................................... 172
Table 124: Register address 0x1050 ................................................................... 173
Table 125: Register address 0x2030 ................................................................... 173
Table 126: Register address 0x2031 ................................................................... 174
Table 127: Register address 0x2032 ................................................................... 174
Table 128: Register address 0x2033 ................................................................... 174
Table 129: Register address 0x2040 ................................................................... 174
Table 130: Register address 0x2041 ................................................................... 175
Table 131: Register address 0x2042 ................................................................... 175
Table 132: Register address 0x2043 ................................................................... 175
Table 133: Register address 0x2010 ................................................................... 176
Table 134: Register address 0x2011 ................................................................... 176
Table 135: Register address 0x2012 ................................................................... 176
Table 136: Register address 0x2013 ................................................................... 176
Table 137: Register address 0x2014 ................................................................... 176
Table 138: Register address 0x2020 ................................................................... 176
Table 139: Register address 0x2021 ................................................................... 177
Table 140: Register address 0x2022 ................................................................... 177
Table 141: Register address 0x2023 ................................................................... 177
Table 142: Register address 0x2000 ................................................................... 178
Table 143: Register address 0x2001 ................................................................... 178
Table 144: Register address 0x2002 ................................................................... 178
Table 145: Register address 0x2003 ................................................................... 178
Table 146: Register address 0x2004 ................................................................... 178
Table 147: Register address 0x2005 ................................................................... 178
Manual
Version 1.1.0
288
List of Tables
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 148: Register address 0x2006 ................................................................... 179
Table 149: Register address 0x2007 ................................................................... 179
Table 150: Register address 0x2008 ................................................................... 179
Table 151: ISO/OSI reference model................................................................. 181
Table 152: CIP common class............................................................................. 184
Table 153: WAGO specific classes..................................................................... 185
Table 154: Explanation of the table headings in the object descriptions ............ 186
Table 155: Identity (01 hex) – Class ..................................................................... 186
Table 156: Identity (01 hex) – Instance 1 ............................................................. 187
Table 157: Identity (01 hex) – Common service................................................... 187
Table 158: Message router (02 hex) – Class ......................................................... 188
Table 159: Message router (02 hex) – Instance 1 ................................................. 188
Table 160: Message router (02 hex) – Common service ...................................... 189
Table 161: Static assembly instances – Overview .............................................. 189
Table 162: Assembly (04 hex) – Class.................................................................. 189
Table 163: Static assembly instances – Instance 101 (65 hex).............................. 189
Table 164: Static assembly instances – Instance 102 (66 hex).............................. 190
Table 165: Static assembly instances – Instance 103 (67 hex).............................. 190
Table 166: Static assembly instances – Instance 104 (68 hex).............................. 190
Table 167: Static assembly instances – Instance 105 (69 hex).............................. 190
Table 168: Static assembly instances – Instance 106 (6A hex)............................. 190
Table 169: Static assembly instances – Instance 107 (6B hex) ............................. 191
Table 170: Static assembly instances – Instance 108 (6C hex) ............................. 191
Table 171: Static assembly instances – Instance 109 (6C hex) ............................. 191
Table 172: Static assembly instances – Common service................................... 192
Table 173: Port class (F4 hex) – Class.................................................................. 193
Table 174: Port class (F4 hex) – Instance 1 .......................................................... 193
Table 175: Port class (F4 hex) – Common service ............................................... 193
Table 176: TCP/IP interface (F5hex) – Class ....................................................... 194
Table 177: TCP/IP interface (F5hex) – Instance 1................................................ 195
Table 178: TCP/IP interface (F5hex) – Common service..................................... 195
Table 179: Ethernet link (F5hex) – Class.............................................................. 196
Table 180: Ethernet link (F6 hex) – Instance 1..................................................... 197
Table 181: Ethernet link (F6 hex) – Instance 2..................................................... 199
Table 182: Ethernet link (F6 hex) – Instance 3..................................................... 201
Table 183: Ethernet link (F6 hex) – Common service .......................................... 201
Table 184: Coupler/Controller configuration (64 hex) – Class............................. 202
Table 185: Coupler/Controller configuration (64 hex) – Instance 1 ..................... 202
Table 186: Coupler/Controller configuration (64 hex) – Common service .......... 203
Table 187: Discrete input point (65 hex) – Class.................................................. 203
Table 188: Discrete input point (65 hex) – Instance 1...255 ................................. 203
Table 189: Discrete input point (65 hex) – Common service ............................... 203
Table 190: Discrete Input Point Extended 1(69 hex,) – Class ............................ 204
Table 191: Discrete output point (66 hex) – Instance 256...510 ........................... 204
Table 192: Discrete Input Point Extended 1 (69 hex) – Common service............ 204
Table 193: Discrete Input Point Extended 2 (6D hex) – Class ........................... 204
Table 194: Analog input point (67 hex) – Instance 1............................................ 204
Table 195: Analog input point (67 hex) – Common service................................. 205
Table 196: Discrete Input Point Extended 3 (71 hex) – Class ............................ 205
Table 197: Discrete Input Point Extended 3 (71 hex) – Instance 766...1020........ 205
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
List of Tables
289
Table 198: Discrete Input Point Extended 3 (71 hex) – Common service............ 205
Table 199: Discrete Output Point (66 hex) – Class............................................. 205
Table 200: Discrete Output Point (66 hex) – Instance 1...255 .............................. 206
Table 201: Discrete Output Point (66 hex) – Common service ............................ 206
Table 202: Discrete Output Point Extended 1 (6A hex) – Class........................... 206
Table 203: Discrete Output Point Extended 1 (6A hex) – Instance 256...510 ...... 206
Table 204: Discrete Output Point Extended 1 (6A hex) – Common service ........ 206
Table 205: Discrete Output Point Extended 2 (6E hex) – Class ........................... 207
Table 206: Discrete Output Point Extended 2 (6E hex) – Instance 511...765 ...... 207
Table 207: Discrete Output Point Extended 2 (6E hex) – Common service........ 207
Table 208: Discrete Output Point Extended 3 (72 hex) – Class............................ 207
Table 209: Discrete Output Point Extended 3 (72 hex) – Instance 766...1020 ..... 208
Table 210: Discrete Output Point Extended 2 (6E hex) – Common service........ 208
Table 211: Analog Input Point (67 hex) – Class................................................... 208
Table 212: Analog Input Point (67 hex) – Instance 1 ... 255 ................................ 208
Table 213: Analog Input Point (67 hex) – Common service ................................ 208
Table 214: Analog Input Point Extended 1 (6B hex) – Class ............................... 209
Table 215: Analog Input Point Extended 1 (6B hex) – Instance 256 ... 510 ........ 209
Table 216: Analog Input Point Extended 1 (6B hex) – Common service............. 209
Table 217: Analog Input Point Extended 2 (6F hex) – Class................................ 209
Table 218: Analog Input Point Extended 2 (6F hex) – Instance 511 ... 765 ......... 210
Table 219: Analog Input Point Extended 2 (6F hex) – Common service ............. 210
Table 220: Analog Input Point Extended 3 (73 hex) – Class................................ 210
Table 221: Analog Input Point Extended 3 (73 hex) – Instance 766 ... 1020 ....... 210
Table 222: Analog Input Point Extended 3 (73 hex) – Common service ............. 211
Table 223: Analog Output Point (68 hex) – Class ................................................ 211
Table 224: Analog Output Point (68 hex) – Instance 1...255................................ 211
Table 225: Analog Output Point (68 hex) – Common service.............................. 211
Table 226: Analog Output Point Extended 1 (6C hex) – Class ............................ 212
Table 227: Analog Output Point Extended 1 (6C hex) – Instance 256...510........ 212
Table 228: Analog Output Point Extended 1 (6C hex) – Common service.......... 212
Table 229: Analog Output Point Extended 2 (70 hex) – Class ............................. 212
Table 230: Analog Output Point Extended 2 (70 hex) – Instance 511...765 ....... 213
Table 231: Analog Output Point Extended 2 (70 hex) – Common service........... 213
Table 232: Analog Output Point Extended 3 (74 hex) – Class ............................. 213
Table 233: Analog Output Point Extended 3 (74 hex) – Instance 766...1020 ...... 213
Table 234: Analog Output Point Extended 3 (74 hex) – Common service........... 214
Table 235: Module Configuration (80 hex) – Class.............................................. 214
Table 236: Module Configuration (80 hex) – Instance 1...255 ............................. 214
Table 237: Module Configuration (80 hex) – Common service ........................... 214
Table 238: Module Configuration Extended (81 hex) – Class.............................. 215
Table 239: Module Configuration Extended (81 hex) – Instance 256.................. 215
Table 240: Module Configuration Extended (81 hex) – Common service ........... 215
Table 241: 1 Channel Digital Input Module with Diagnostics ........................... 218
Table 242: 2 Channel Digital Input Modules...................................................... 218
Table 243: 2 Channel Digital Input Module with Diagnostics ........................... 218
Table 244: 2 Channel Digital Input Module with Diagnostics and Output Process
Data ............................................................................................................ 219
Table 245: 4 Channel Digital Input Modules...................................................... 219
Table 246: 8 Channel Digital Input Modules...................................................... 219
Manual
Version 1.1.0
290
List of Tables
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 247: 16 Channel Digital Input Modules.................................................... 220
Table 248: 1 Channel Digital Output Module with Input Process Data ............. 221
Table 249: 2 Channel Digital Output Modules ................................................... 221
Table 250: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data ............................................................................................................ 222
Table 251: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data 75x-506.............................................................................................. 222
Table 252: 4 Channel Digital Output Modules ................................................... 223
Table 253: 4 Channel Digital Output Modules with Diagnostics and Input Process
Data ............................................................................................................ 223
Table 254: 8 Channel Digital Output Module..................................................... 223
Table 255: 8 Channel Digital Output Modules with Diagnostics and Input Process
Data ............................................................................................................ 224
Table 256: 16 Channel Digital Output Modules ................................................. 224
Table 257: 8 Channel Digital Input/Output Modules.......................................... 225
Table 258: 1 Channel Analog Input Modules ..................................................... 226
Table 259: 2 Channel Analog Input Modules ..................................................... 226
Table 260: 4 Channel Analog Input Modules ..................................................... 227
Table 261: 2 Channel Analog Output Modules................................................... 228
Table 262: 4 Channel Analog Output Modules................................................... 228
Table 263: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003) ............................................................. 229
Table 264: Counter Modules 750-404/000-005 .................................................. 230
Table 265: Counter Modules 750-638, 753-638 ................................................. 230
Table 266: Pulse Width Modules 750-511, /xxx-xxx ......................................... 231
Table 267: Serial Interface Modules with alternative Data Format .................... 231
Table 268: Serial Interface Modules with Standard Data Format....................... 232
Table 269: Data Exchange Module ..................................................................... 232
Table 270: SSI Transmitter Interface Modules ................................................... 233
Table 271: Incremental Encoder Interface Modules 750-631/000-004, --010, -011
.................................................................................................................... 233
Table 272: Incremental Encoder Interface Modules 750-634............................. 234
Table 273: Incremental Encoder Interface Modules 750-637............................. 234
Table 274: Digital Pulse Interface Modules 750-635 ......................................... 235
Table 275: DC-Drive Controller 750-636 ........................................................... 235
Table 276: Stepper Controller RS 422 / 24 V / 20 mA 750-670......................... 236
Table 277: RTC Module 750-640 ....................................................................... 237
Table 278: DALI/DSI Master module 750-641 .................................................. 237
Table 279: EnOcean Radio Receiver 750-642 .................................................... 238
Table 280: MP Bus Master Module 750-643...................................................... 238
Table 281: Bluetooth® RF-Transceiver 750-644................................................. 239
Table 282: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645
.................................................................................................................... 240
Table 283: AS-interface Master module 750-655............................................... 241
Table 284: System Modules with Diagnostics 750-610, -611 ............................ 242
Table 285: Binary Space Module 750-622 (with behavior like 2 channel digital
input) .......................................................................................................... 242
Table 286: 1 Channel Digital Input Module with Diagnostics ........................... 244
Table 287: 2 Channel Digital Input Modules...................................................... 244
Table 288: 2 Channel Digital Input Module with Diagnostics ........................... 245
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
List of Tables
291
Table 289: 2 Channel Digital Input Module with Diagnostics and Output Process
Data ............................................................................................................ 245
Table 290: 4 Channel Digital Input Modules...................................................... 246
Table 291: 8 Channel Digital Input Modules...................................................... 246
Table 292: 16 Channel Digital Input Modules.................................................... 246
Table 293: 1 Channel Digital Output Module with Input Process Data ............. 247
Table 294: 2 Channel Digital Output Modules ................................................... 248
Table 295: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data ............................................................................................................ 248
Table 296: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data 75x-506.............................................................................................. 249
Table 297: 4 Channel Digital Output Modules ................................................... 249
Table 298: 4 Channel Digital Output Modules with Diagnostics and Input Process
Data ............................................................................................................ 249
Table 299: 8 Channel Digital Output Module..................................................... 250
Table 300: 8 Channel Digital Output Modules with Diagnostics and Input Process
Data ............................................................................................................ 250
Table 301: 16 Channel Digital Output Modules ................................................. 251
Table 302: 8 Channel Digital Input/Output Modules.......................................... 251
Table 303: 1 Channel Analog Input Modules ..................................................... 252
Table 304: 2 Channel Analog Input Modules ..................................................... 253
Table 305: 4 Channel Analog Input Modules ..................................................... 253
Table 306: 2 Channel Analog Output Modules................................................... 254
Table 307: 4 Channel Analog Output Modules................................................... 254
Table 308: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003) ............................................................. 255
Table 309: Counter Modules 750-404/000-005 .................................................. 256
Table 310: Counter Modules 750-638, 753-638 ................................................. 257
Table 311: Pulse Width Modules 750-511, /xxx-xxx ......................................... 257
Table 312: Serial Interface Modules with alternative Data Format .................... 258
Table 313: Serial Interface Modules with Standard Data Format....................... 258
Table 314: Data Exchange Module ..................................................................... 259
Table 315: SSI Transmitter Interface Modules ................................................... 259
Table 316: SSI Transmitter Interface I/O Modules with an Alternative Data
Format ........................................................................................................ 260
Table 317: Incremental Encoder Interface Modules 750-631/000-004, -010, -011
.................................................................................................................... 260
Table 318: Incremental Encoder Interface Modules 750-634............................. 261
Table 319: Incremental Encoder Interface Modules 750-637............................. 261
Table 320: Incremental Encoder Interface Modules 750-635, 750-635 ............. 262
Table 321: DC-Drive Controller 750-636 ........................................................... 262
Table 322: Steppercontroller RS 422 / 24 V / 20 mA 750-670........................... 263
Table 323: RTC Module 750-640 ....................................................................... 264
Table 324: DALI/DSI Master module 750-641 .................................................. 265
Table 325: EnOcean Radio Receiver 750-642 .................................................... 265
Table 326: MP Bus Master Module 750-643...................................................... 266
Table 327: Bluetooth® RF-Transceiver 750-644................................................. 267
Table 328: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645
.................................................................................................................... 267
Table 329: AS-interface Master module 750-655............................................... 268
Manual
Version 1.1.0
292
List of Tables
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Table 330: System Modules with Diagnostics 750-610, -611 ............................ 269
Table 331: Binary Space Module 750-622 (with behavior like 2 channel digital
input) .......................................................................................................... 269
Table 332: MODBUS table and function codes.................................................. 272
Table 333: Description of Printing on................................................................. 274
Table 334: Description of the inscription............................................................ 276
Table 335: Description of Printing on................................................................. 277
Table 336: VDE Installation Regulations in Germany ....................................... 278
Table 337: Installation Regulations in USA and Canada.................................... 278
Manual
Version 1.1.0
WAGO-I/O-SYSTEM 750
750-352 ETHERNET Fieldbus Coupler
Manual
Version 1.1.0
List of Tables
293
WAGO Kontakttechnik GmbH & Co. KG
Postfach 2880
•
D-32385 Minden
Hansastraße 27
•
D-32423 Minden
Phone:
+49/5 71/8 87 – 0
Fax:
+49/5 71/8 87 – 1 69
E-Mail:
[email protected]
Internet:
http://www.wago.com