m07500362 XXXXXXXX 0en

Manual
WAGO I/O System 750
750-362, 750-362/0000-0001
FC Modbus TCP; G4 (BootP)
Fieldbus Coupler Modbus TCP; Generation 4 (BootP)
Version 1.1.1
2 WAGO I/O System 750
750-362, 750-362/0000-0001 FC Modbus TCP; G4 (BootP)
© 2022 WAGO GmbH & Co. KG

All rights reserved.
WAGO GmbH & Co. KG
Hansastraße 27
D-32423 Minden
Phone: +49 (0) 571/8 87 – 0

Fax: +49 (0) 571/8 87 – 1 69
E-Mail: info@wago.com
Web: www.wago.com
Technical Support
Phone: +49 (0) 571/8 87 – 4 45 55

Fax: +49 (0) 571/8 87 – 84 45 55
E-Mail: support@wago.com
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: documentation@wago.com
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.
WAGO is a registered trademark of WAGO Verwaltungsgesellschaft mbH.
Manual
Version 1.1.1
WAGO I/O System 750 Table of Contents 3
Table of Contents
1 Notes about this Documentation ............................................................ 10
1.1 Validity of this Documentation................................................................ 10
1.2 Copyright................................................................................................ 10
1.3 Property rights........................................................................................ 11
1.4 Symbols ................................................................................................. 13
1.5 Number Notation .................................................................................... 15
1.6 Font Conventions ................................................................................... 15
2 Important Notes ........................................................................................ 16
2.1 Legal Bases ........................................................................................... 16
2.1.1 Subject to Changes ........................................................................... 16
2.1.2 Personnel Qualifications.................................................................... 16
2.1.3 Use of the 750 Series in Compliance with Underlying Provisions ..... 16
2.1.4 Technical Condition of Specified Devices ......................................... 17
2.1.4.1 Disposal ........................................................................................ 18
2.1.4.1.1 Electrical and Electronic Equipment ........................................ 18
2.1.4.1.2 Packaging ................................................................................ 19
2.2 Safety Advice (Precautions)................................................................... 20
2.3 Special Use Conditions for ETHERNET Devices .................................. 23
3 System Description .................................................................................. 24
3.1 Labeling ................................................................................................. 25
3.1.1 Labeling Symbols .............................................................................. 25
3.1.2 Manufacturing Number ...................................................................... 26
3.1.3 Hardware Address (MAC-ID) ............................................................ 27
3.1.4 Update Matrix .................................................................................... 27
3.2 Storage, Assembly and Transport ......................................................... 28
3.3 Assembly Guidelines/Standards ............................................................ 29
3.4 Power Supply ......................................................................................... 30
3.4.1 Overcurrent Protection ...................................................................... 30
3.4.2 Isolation ............................................................................................. 31
3.4.3 System Supply .................................................................................. 32
3.4.3.1 Connection ................................................................................... 32
3.4.3.2 Dimensioning ................................................................................ 34
3.4.4 Field Supply ...................................................................................... 36
3.4.4.1 Connection ................................................................................... 36
3.4.4.2 Fusing via Power Supply Module ................................................. 38
3.4.4.3 Fusing external ............................................................................. 41
3.4.5 Supplementary Power Supply Regulations ....................................... 43
3.4.6 Supply Example ................................................................................ 44
3.4.7 Power Supply Unit ............................................................................. 46
3.5 Grounding .............................................................................................. 47
3.5.1 Grounding the DIN Rail ..................................................................... 47
3.5.1.1 Framework Assembly ................................................................... 47
3.5.1.2 Insulated Assembly ...................................................................... 47
3.5.2 Grounding Function ........................................................................... 48
3.6 Shielding ................................................................................................ 49
3.6.1 General ............................................................................................. 49
Manual
Version 1.1.1
4 Table of Contents WAGO I/O System 750
3.6.2 Fieldbus Cables................................................................................. 49
3.6.3 Shielded Signal Lines ........................................................................ 50
3.6.4 WAGO Shield Connecting System .................................................... 50
4 Device Description ................................................................................... 51
4.1 View ....................................................................................................... 53
4.2 Connectors............................................................................................. 55
4.2.1 Device Supply ................................................................................... 55
4.2.2 Fieldbus Connection.......................................................................... 56
4.3 Display Elements ................................................................................... 57
4.4 Operating Elements ............................................................................... 58
4.4.1 Service Interface ............................................................................... 58
4.4.2 Address Selection Switch .................................................................. 59
4.5 Technical Data ....................................................................................... 60
4.5.1 Device Data ....................................................................................... 60
4.5.2 System Data ...................................................................................... 60
4.5.3 Supply ............................................................................................... 60
4.5.4 Fieldbus Modbus TCP ....................................................................... 61
4.5.5 Accessories ....................................................................................... 61
4.5.6 Connection Type ............................................................................... 61
4.5.7 Climatic Environmental Conditions.................................................... 62
4.5.8 Mechanical Strength.......................................................................... 63
4.5.9 Software Compatibility....................................................................... 63
4.6 Approvals ............................................................................................... 64
4.7 Standards and Guidelines...................................................................... 65
5 Mounting ................................................................................................... 66
5.1 Installation Position ................................................................................ 66
5.2 Overall Configuration ............................................................................. 66
5.3 Mounting onto Carrier Rail ..................................................................... 68
5.3.1 Carrier Rail Properties ....................................................................... 68
5.3.2 WAGO DIN Rails ............................................................................... 69
5.4 Spacing .................................................................................................. 69
5.5 Mounting Sequence ............................................................................... 70
5.6 Inserting and Removing Devices ........................................................... 71
5.6.1 Inserting the Fieldbus Coupler/Controller .......................................... 72
5.6.2 Removing the Fieldbus Coupler/Controller ....................................... 72
5.6.3 Inserting the I/O Module .................................................................... 73
5.6.4 Removing the I/O Module.................................................................. 74
6 Connect Devices....................................................................................... 75
6.1 Data Contacts/Local Bus ....................................................................... 75
6.2 Power Contacts/Field Supply ................................................................. 76
6.3 Connecting a Conductor to the CAGE CLAMP® .................................... 77
7 Function Description................................................................................ 78
7.1 Operating System .................................................................................. 78
7.2 Process Data Architecture ..................................................................... 79
7.2.1 Basic Structure .................................................................................. 79
7.2.2 Process Data MODBUS TCP ............................................................ 80
7.3 Data Exchange ...................................................................................... 81
Manual
Version 1.1.1
7.3.1 Memory Space .................................................................................. 82
7.3.2 Addressing ........................................................................................ 82
7.3.2.1 Addressing of I/O Modules ........................................................... 83
7.3.3 Data Exchange between MODBUS/TCP Master and I/O Modules ... 84
7.4 Logging .................................................................................................. 85
8 Commissioning......................................................................................... 87
8.1 Connecting Client PC and Fieldbus Nodes............................................ 88
8.2 Determining the IP Address of the PC ................................................... 88
8.3 Assigning the IP Address to the Fieldbus Node..................................... 89
8.3.1 Assigning IP Address via Address Selection Switch ......................... 89
8.3.2 Assigning IP Address via DHCP ....................................................... 91
8.3.2.1 Enable DHCP via "WAGO Ethernet Settings" (without existing IP
address)" ...................................................................................... 93
8.3.2.2 Enable DHCP via WBM (with existing IP address) ....................... 94
8.3.3 Assigning IP Address via “WAGO Ethernet Settings” ....................... 95
8.3.4 Assigning the IP Address via BootP .................................................. 97
8.3.4.1 Reasons for Failed IP Address Assignment ................................. 99
8.4 Apply IP address permanently (option “static“) .................................... 100
8.5 Testing the Function of the Fieldbus Node .......................................... 101
8.6 Preparing the Flash File System .......................................................... 102
8.7 Synchronizing the System Time .......................................................... 104
8.8 Restoring Factory Settings................................................................... 106
9 Configuring via the Web-Based Management System (WBM) ........... 107
9.1 WBM User Groups ............................................................................... 107
9.2 Open WBM .......................................................................................... 108
9.3 WBM Pages ......................................................................................... 109
9.4 Information ........................................................................................... 110
9.5 Administration ...................................................................................... 111
9.6 System Status ...................................................................................... 113
9.7 Clock .................................................................................................... 115
9.8 Miscellaneous ...................................................................................... 117
9.9 Storage Media...................................................................................... 118
9.10 Update ................................................................................................. 118
9.11 Ethernet ............................................................................................... 119
9.12 Protocols .............................................................................................. 123
9.13 SNMP................................................................................................... 124
9.13.1 SNMP v1/v2c .................................................................................. 125
9.13.2 SNMP V3 ........................................................................................ 126
9.14 SNTP ................................................................................................... 127
9.15 TCP/IP ................................................................................................. 128
9.16 Modbus ................................................................................................ 129
9.17 Modbus Mapping ................................................................................. 132
9.18 I/O Config ............................................................................................. 135
10 Diagnostics ............................................................................................. 136
10.1 LED Signaling ...................................................................................... 136
10.1.1 Evaluating Fieldbus Status .............................................................. 137
10.1.2 Evaluating Node Status – I/O LED (Blink Code Table) ................... 139
10.2 Fault Behavior ...................................................................................... 149
Manual
Version 1.1.1
10.2.1 Fieldbus Failure ............................................................................... 149
10.2.2 Local Bus Failure............................................................................. 149
11 Fieldbus Communication....................................................................... 151
11.1 Implemented Protocols ........................................................................ 151
11.1.1 Communication Protocols ............................................................... 151
11.1.1.1 IP (Internet Protocol) .................................................................. 151
11.1.1.2 TCP (Transmission Control Protocol) ......................................... 156
11.1.1.3 UDP (User Datagram Protocol) .................................................. 156
11.1.2 Configuration and Diagnostics Protocols ........................................ 157
11.1.2.1 BootP (Bootstrap Protocol) ......................................................... 157
11.1.2.2 DHCP (Dynamic Host Configuration Protocol) ........................... 158
11.1.2.3 HTTP (Hypertext Transfer Protocol) ........................................... 160
11.1.2.4 DNS (Domain Name Systems) ................................................... 160
11.1.2.5 SNTP-Client (Simple Network Time Protocol) ............................ 161
11.1.2.6 FTP-Server (File Transfer Protocol) ........................................... 161
11.1.2.7 SNMP (Simple Network Management Protocol)......................... 162
11.1.2.7.1 MIB II Description ................................................................... 163
11.1.2.7.2 Traps ...................................................................................... 164
11.1.2.8 Syslog Client ............................................................................... 164
11.1.2.8.1 Syslog Messages ................................................................... 166
11.1.2.8.2 Configuration .......................................................................... 166
11.1.3 Application Protocols ....................................................................... 167
11.2 Modbus Functions................................................................................ 168
11.2.1 General ........................................................................................... 168
11.2.2 Use of the MODBUS Functions....................................................... 171
11.2.3 Description of the MODBUS Functions ........................................... 172
11.2.3.1 Function Code FC1 (Read Coils) ............................................... 173
11.2.3.2 Function Code FC2 (Read Discrete Inputs)................................ 175
11.2.3.3 Function Code FC3 (Read Multiple Registers) ........................... 177
11.2.3.4 Function Code FC4 (Read Input Registers) ............................... 178
11.2.3.5 Function Code FC5 (Write Coil) ................................................. 179
11.2.3.6 Function Code FC6 (Write Single Register) ............................... 180
11.2.3.7 Function Code FC11 (Get Comm Event Counter) ...................... 181
11.2.3.8 Function Code FC15 (Write Multiple Coils) ................................ 182
11.2.3.9 Function Code FC16 (Write Multiple Registers) ......................... 184
11.2.3.10 Function Code FC22 (Mask Write Register) ............................... 185
11.2.3.11 Function Code FC23 (Read/Write Multiple Registers)................ 186
11.2.4 MODBUS Register Mapping ........................................................... 188
11.2.5 Modbus Registers ............................................................................ 191
11.2.5.1 Accessing Register Values ......................................................... 192
11.2.5.2 Modbus-Watchdog ..................................................................... 192
11.2.5.3 Modbus Watchdog Register ........................................................ 194
11.2.5.4 Diagnostic Registers ................................................................... 198
11.2.5.5 Configuration Registers .............................................................. 199
11.2.5.6 Constant Registers ..................................................................... 201
11.2.5.7 Firmware Information Registers ................................................. 203
12 I/O Modules ............................................................................................. 208
12.1 Overview .............................................................................................. 208
12.2 Process Data Architecture for Modbus-TCP ........................................ 209
Manual
Version 1.1.1
12.2.1 Digital Input Modules ....................................................................... 209
12.2.1.1 1 Channel Digital Input Module with Diagnostics ....................... 209
12.2.1.2 2 Channel Digital Input Modules ................................................. 210
12.2.1.3 2 Channel Digital Input Module with Diagnostics ....................... 210
12.2.1.4 2 Channel Digital Input Module with Diagnostics and Output
Process Data .............................................................................. 210
12.2.1.7 8 Channel Digital Input Module NAMUR with Diagnostics and
Output Process Data .................................................................. 211
12.2.1.8 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data .............................................................................. 213
12.2.2 16 Channel Digital Input Modules ................................................... 214
12.2.2.1 Digital Output Modules ............................................................... 215
12.2.2.2 1 Channel Digital Output Module with Input Process Data ......... 215
12.2.2.3 2 Channel Digital Output Modules .............................................. 215
12.2.2.4 2 Channel Digital Input Modules with Diagnostics and Input
Process Data .............................................................................. 216
12.2.2.5 4 Channel Digital Output Modules .............................................. 217
12.2.2.6 4 Channel Digital Output Modules with Diagnostics and Input
Process Data .............................................................................. 217
12.2.2.7 8 Channel Digital Output Module ................................................ 217
Process Data .............................................................................. 218
12.2.2.9 16 Channel Digital Output Modules ............................................ 218
12.2.2.10 8 Channel Digital Input/Output Modules ..................................... 219
12.2.3 Analog Input Modules ..................................................................... 220
12.2.3.1 1 Channel Analog Input Modules ............................................... 220
12.2.3.3 2 Channel Analog Input Modules HART ..................................... 221
12.2.3.6 3-Phase Power Measurement Module ....................................... 224
12.2.4 Analog Output Modules ................................................................... 226
12.2.4.1 2 Channel Analog Output Modules ............................................. 226
12.2.5 Specialty Modules ........................................................................... 227
12.2.5.1 Counter Modules ........................................................................ 228
12.2.5.2 Pulse Width Modules .................................................................. 230
12.2.5.3 Serial Interface Modules with Alternative Data Format............... 230
12.2.5.4 Serial Interface Modules with Standard Data Format ................. 231
12.2.5.5 Serial Interface Modules ............................................................. 231
12.2.5.6 Data Exchange Module .............................................................. 232
12.2.5.7 SSI Transmitter Interface Modules ............................................. 232
12.2.5.8 Incremental Encoder Interface Modules ..................................... 233
12.2.5.9 DC-Drive Controller .................................................................... 235
12.2.5.10 Stepper Controller ...................................................................... 236
12.2.5.11 RTC Module ............................................................................... 237
12.2.5.12 DALI/DSI Master Module ............................................................ 237
Manual
Version 1.1.1
12.2.5.13 DALI Multi-Master Module .......................................................... 238
12.2.5.14 LON® FTT Module ...................................................................... 241
12.2.5.15 EnOcean Radio Receiver ........................................................... 241
12.2.5.16 MP Bus Master Module .............................................................. 242
12.2.5.17 Bluetooth® RF-Transceiver ......................................................... 242
12.2.5.18 Vibration Velocity/Bearing Condition Monitoring VIB I/O ............ 243
12.2.5.19 Proportional Valve Module ......................................................... 244
12.2.5.20 M-Bus Master Module ................................................................ 245
12.2.5.21 IO-Link Master ............................................................................ 245
12.2.5.22 CAN Gateway ............................................................................. 246
12.2.5.23 Servo Stepper Controller ............................................................ 247
12.2.5.24 SMI Master Module .................................................................... 248
12.2.5.25 AS-interface Master Module ....................................................... 249
12.2.5.26 System Modules ......................................................................... 251
12.2.5.27 System Modules with Diagnostics .............................................. 251
12.2.5.28 Filter Module ............................................................................... 251
12.2.5.29 Binary Space Module ................................................................. 252
13 Application Examples ............................................................................ 253
13.1 Test of Modbus protocol and fieldbus nodes ....................................... 253
13.2 Visualization and Control using SCADA Software ............................... 253
14 Use in Hazardous Environments .......................................................... 256
14.1 Marking Configuration Examples ......................................................... 257
14.1.1 Marking for Europe According to ATEX and IECEx ........................ 257
14.1.2 Marking for the United States of America (NEC) and Canada (CEC)261
14.2 Installation Regulations ........................................................................ 264
14.2.1 Special Notes including Explosion Protection ................................. 264
14.2.2 Special Notes Regarding ANSI/ISA Ex ........................................... 266
15 Appendix ................................................................................................. 267
15.1 MIB II Groups ....................................................................................... 267
15.1.1 System Group ................................................................................. 267
15.1.2 Interface Group ............................................................................... 268
15.1.3 IP Group .......................................................................................... 270
15.1.4 IpRoute Table Group ....................................................................... 271
15.1.5 ICMP Group .................................................................................... 272
15.1.6 TCP Group ...................................................................................... 273
15.1.7 UDP Group ...................................................................................... 274
15.1.8 SNMP Group ................................................................................... 275
15.2 WAGO MIB Groups ............................................................................. 276
15.2.1 Company Group .............................................................................. 276
15.2.2 Product Group ................................................................................. 276
15.2.3 Versions Group ............................................................................... 277
15.2.4 Real-Time Clock Group ................................................................... 278
15.2.5 Ethernet Group ................................................................................ 279
15.2.6 Actual Error Group .......................................................................... 279
15.2.7 Http Group ....................................................................................... 280
15.2.8 Ftp Group ........................................................................................ 280
15.2.9 Sntp Group ...................................................................................... 281
15.2.10 Snmp Group .................................................................................... 281
Manual
Version 1.1.1
15.2.11 Snmp Trap String Group ................................................................. 283
15.2.12 Snmp User Trap String Group......................................................... 284
15.2.13 Plc Connection Group ..................................................................... 284
15.2.14 Modbus Group ................................................................................ 285
15.2.15 Process Image Group ..................................................................... 286
List of Figures .................................................................................................. 287
List of Tables .................................................................................................... 289
Manual
Version 1.1.1
10 Notes about this Documentation WAGO I/O System 750
1 Notes about this Documentation
Always retain this documentation!

This documentation is part of the product. Therefore, retain the documentation
during the entire service life of the product. Pass on the documentation to any
subsequent user. In addition, ensure that any supplement to this documentation
is included, if necessary.
1.1 Validity of this Documentation

This documentation is only applicable to the “FC Modbus TCP; G4 (BootP)” (750-
362, 750-362/0000-0001) and the variants listed in the table below.
Table 1: Variations
Oder number/
Designation
Variation
750-362 FC Modbus TCP; G4
750-362/0000-0001 FC Modbus TCP; G4; BootP
(Default setting: Boot/P is enabled, DHCP disabled)
The product “FC Modbus TCP; G4 (BootP)” (750-362, 750-362/0000-0001) 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 GmbH & Co. KG, Minden, Germany. Non-observance
will involve the right to assert damage claims.
Manual
Version 1.1.1
WAGO I/O System 750 Notes about this Documentation 11
1.3 Property rights

Third-party trademarks are used in this documentation. This section contains the
trademarks used. The “®” and “TM” symbols are omitted hereinafter.
• Adobe® and Acrobat® are registered trademarks of Adobe Systems Inc.
• AndroidTM is a trademark of Google LLC.
• Apple, the Apple logo, iPhone, iPad and iPod touch are registered
trademarks of Apple Inc. registered in the USA and other countries. “App
Store” is a service mark of Apple Inc.
• AS-Interface® is a registered trademark of the AS-International Association

e.V.
• BACnet® is a registered trademark of the American Society of Heating,

Refrigerating and Air Conditioning Engineers, Inc. (ASHRAE).
• Bluetooth® is a registered trademark of Bluetooth SIG, Inc.
• CiA® and CANopen® are registered trademarks of CAN in AUTOMATION –

International Users and Manufacturers Group e.V.
• CODESYS is a registered trademark of CODESYS Development GmbH.
• DALI is a registered trademark of the Digital Illumination Interface Alliance

(DiiA).
• EtherCAT® is a registered trademark and patented technology licensed by

Beckhoff Automation GmbH, Germany.
• ETHERNET/IP™ is a registered trademark of the Open DeviceNet Vendor

Association, Inc (ODVA).
• EnOcean® is a registered trademark of EnOcean GmbH.
• Google PlayTM is a registered trademark of Google Inc.
• IO-Link is a registered trademark of PROFIBUS Nutzerorganisation e.V.
• KNX® is a registered trademark of the KNX Association cvba.
• Linux® is a registered trademark of Linus Torvalds.
• LON® is a registered trademark of the Echelon Corporation.
• Modbus® is a registered trademark of Schneider Electric, licensed for

Modbus Organization, Inc.
• OPC UA is a registered trademark of the OPC Foundation.
Manual
Version 1.1.1
• PROFIBUS® is a registered trademark of the PROFIBUS
Nutzerorganisation e.V. (PNO).
• PROFINET® is a registered trademark of the PROFIBUS

Nutzerorganisation e.V. (PNO).
• QR Code is a registered trademark of DENSO WAVE INCORPORATED.
• Subversion® is a trademark of the Apache Software Foundation.
• Windows® is a registered trademark of Microsoft Corporation.
Manual
Version 1.1.1
1.4 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.1
Additional Information:
Refers to additional information which is not an integral part of this
documentation (e.g., the Internet).
Manual
Version 1.1.1
1.5 Number Notation

Table 2: Number Notation
Number Code Example Note
Decimal 100 Normal notation
Hexadecimal 0x64 C notation
Binary '100' In quotation marks, nibble separated
'0110.0100' with dots (.)
1.6 Font Conventions

Table 3: Font Conventions
Font Type Indicates
italic Names of paths and data files are marked in italic-type.
e.g.: C:\Program Files\WAGO Software
Menu 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
Input Designation of input or optional fields are marked in bold letters,
e.g.: Start of measurement range
“Value” Input or selective values are marked in inverted commas.
e.g.: Enter the value “4 mA” under Start of measurement range.
[Button] Pushbuttons in dialog boxes are marked with bold letters in square
brackets.
e.g.: [Input]
[Key] Keys are marked with bold letters in square brackets.
e.g.: [F5]
Manual
Version 1.1.1
16 Important Notes WAGO I/O System 750
2 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 GmbH & Co. KG reserves the right to provide for any alterations or
modifications. WAGO 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 WAGO I/O System 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
Fieldbus couplers, controllers and I/O modules of the modular WAGO I/O System
750 receive digital and analog signals from sensors and transmit them to
actuators or higher-level control systems. Using controllers, the signals can also
be (pre-) processed.
This product fulfills the requirements of protection type IP20 and is designed for
use in dry interior spaces. There is protection against finger injury and solid
impurities up to 12.5 mm diameter is assured; protection against water damage is
not ensured.
The product represents an open-type device. It may only be installed in
enclosures (tool-secured enclosures or operating rooms) which fulfil the listed
requirements specified in the safety instructions in chapter “Safety Advice
(Precautions)”. Use without additional protective measures in environments within
which dust, corrosive fumes, gases or ionized radiation can occur is considered
improper use.
The product is intended for installation in automation systems. It does not have
its own integrated separator. A suitable separator must therefore be created on
the plant side.
Manual
Version 1.1.1
WAGO I/O System 750 Important Notes 17
The operation of the product in residential areas without further measures is only
permitted if the product complies with the emission limits (interference emissions)
according to EN 61000-6-3.
Operating the product in home applications without further measures is only

permitted if it meets the emission limits (emissions of interference) according to
EN 61000-6-3. Please observe the installation regulations!
You will find the relevant information in the section “Device Description” >
“Standards and Guidelines” in the manual for the used product.
Appropriate housing (per 2014/34/EU) is required when operating the WAGO I/O
System 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.
The implementation of safety functions such as EMERGENCY STOP or safety

door monitoring must only be performed by the F I/O modules within the modular
WAGO I/O System 750. Only these safe F I/O modules ensure functional safety
in accordance with the latest international standards. WAGO's interference-free
output modules can be controlled by the safety function.
2.1.4 Technical Condition of Specified Devices

The devices to be supplied ex works are equipped with hardware and software
configurations, which meet the individual application requirements. These
modules contain no parts that can be serviced or repaired by the user. The
following actions will result in the exclusion of liability on the part of WAGO GmbH
& Co. KG:
• Repairs,
• Changes to the hardware or software that are not described in the
operating instructions,
• Improper use of the components.
Further details are given in the contractual agreements. Please send your
request for modified and new hardware or software configurations directly to
WAGO GmbH & Co. KG.
Manual
Version 1.1.1
2.1.4.1 Disposal
2.1.4.1.1 Electrical and Electronic Equipment
Electrical and electronic equipment may not be disposed of

with household waste. This also applies to products without
this symbol.
Electrical and electronic equipment contain materials and substances that can be
harmful to the environment and health. Electrical and electronic equipment must
be disposed of properly after use.
WEEE 2012/19/EU applies throughout Europe. Directives and laws may vary
nationally.
Environmentally friendly disposal benefits health and protects

the environment from harmful substances in electrical and
electronic equipment.
• Observe national and local regulations for the disposal of electrical and
• Clear any data stored on the electrical and electronic equipment.
• Remove any added battery or memory card in the electrical and

• Have the electrical and electronic equipment sent to your local

collection point.
Improper disposal of electrical and electronic equipment can be harmful to the

environment and human health.
Manual
Version 1.1.1
2.1.4.1.2 Packaging
Packaging contains materials that can be reused.

PPWD 94/62/EU and 2004/12/EU packaging guidelines apply throughout
Europe. Directives and laws may vary nationally.
Environmentally friendly disposal of the packaging protects the environment and

allows sustainable and efficient use of resources.
• Observe national and local regulations for the disposal of packaging.
• Dispose of packaging of all types that allows a high level of recovery,

reuse and recycling.
Improper disposal of packaging can be harmful to the environment and wastes

valuable resources.
Manual
Version 1.1.1
2.2 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 devices while energized!

All power sources to the device shall be switched off prior to performing any
installation, repair or maintenance work.
Install device in a suitable enclosure!

The device is an open system. Install the device in a suitable enclosure. This
enclosure must:
• Guarantee that the max. permissible degree of pollution is not exceeded.

• Offer adequate protection against contact.
• Prevent fire from spreading outside of the enclosure.
• Offer adequate protection against UV irradiation.
• Guarantee mechanical stability
• Restrict access to authorized personnel and may only be opened with tools
Ensure disconnect and overcurrent protection!

The device is intended for installation in automation technology systems.
Disconnect protection is not integrated. Connected systems must be protected by
a fuse.
Provide suitable disconnect and overcurrent protection on the system side!
Ensure a standard connection!

To minimize any hazardous situations resulting in personal injury or to avoid
failures in your system, the data and power supply lines shall be installed
according to standards, with careful attention given to ensuring the correct
terminal assignment. Always adhere to the EMC directives applicable to your
application.
Manual
Version 1.1.1
Power from SELV/PELV power supply only!

All field signals and field supplies connected to this fieldbus coupler/controller
(750-362, 750-362/0000-0001) must be powered from SELV/PELV power
supply(s)!
Inadequate wire cross sections can cause temperature increases!

To avoid increasing thermal risks, only use conductor cross-sections sufficient for
the required maximum load current. The conductor cross-sections specified in
the technical data refer exclusively to the mechanical connection capacity of the
clamping points.
Do not touch hot surfaces!

The surface of the housing can become hot during operation. If the device was
operated at high ambient temperatures, allow it to cool off before touching it.
Do not use in telecommunication circuits!

Only use devices equipped with ETHERNET or RJ-45 connectors in LANs.
Never connect these devices with telecommunication networks.
Ensure proper contact with the DIN-rail!

Proper electrical contact between the DIN-rail and device is necessary to
maintain the EMC characteristics and function of the device.
Replace defective or damaged devices!

Replace defective or damaged device/module (e.g., in the event of deformed
contacts).
Manual
Version 1.1.1
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.
Clean only with permitted materials!

Clean housing and soiled contacts with propanol.
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 may be destroyed by
electrostatic discharge when touched. Please observe the safety precautions
against electrostatic discharge per DIN EN 61340-5-1/-3. When handling the
devices, please ensure that environmental factors (personnel, work space and
packaging) are properly grounded.
Manual
Version 1.1.1
2.3 Special Use Conditions for ETHERNET Devices

If not otherwise specified, ETHERNET devices are intended for use on local
networks. Please note the following when using ETHERNET devices in your
system:
• Do not connect control components and control networks directly to an

open network such as the Internet or an office network. WAGO
recommends putting control components and control networks behind a
firewall.
• In the control components (e.g., for WAGO I/-CHECK and CODESYS)

close all ports and services not required by your application to minimize the
risk of cyber attacks and to enhance cyber security.
Only open ports and services during commissioning and/or configuration.
• Limit physical and electronic access to all automation components to

authorized personnel only.
• Change the default passwords before first use! This will reduce the risk of
unauthorized access to your system.
• Regularly change the passwords used! This will reduce the risk of
unauthorized access to your system.
• If remote access to control components and control networks is required,

use a Virtual Private Network (VPN).
• Regularly perform threat analyses. You can check whether the measures
taken meet your security requirements.
• Use “defense-in-depth” mechanisms in your system's security configuration

to restrict the access to and control of individual products and networks.
Manual
Version 1.1.1
24 System Description WAGO I/O System 750
3 System Description
The WAGO-I/O-SYSTEM 750 is a modular, fieldbus-independent input/output
system (I/O system). The configuration described here consists of a fieldbus
coupler/controller (1) and the modular I/O modules (2) for any signal shapes that
form the fieldbus node together. The end module (3) completes the node and is
required for correct operation of the fieldbus node.
Figure 1: Fieldbus Node (Example)
Fieldbus 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.
I/O modules for diverse digital and analog I/O signals as well as special functions
can be connected to the fieldbus coupler/controller. The communication between
the fieldbus coupler/controller and the I/O modules is carried out via a local bus.
The components of the WAGO I/O System 750 have clear termination points,
light emitting diodes for status display, plug-in mini WSB tags and group marker
cards for labeling.
The 1, 2 or 3 wire technology supplemented by a ground wire connection allows

for direct sensor or actuator wiring.
Manual
Version 1.1.1
WAGO I/O System 750 System Description 25
3.1 Labeling
The front labeling includes:
- Device designation
- Name of the display elements, connections and control elements
- Serial number with hardware and firmware version
The side labeling includes:

- Manufacturer's identification
- Connector pin assignment
- Serial number
- Approval information
3.1.1 Labeling Symbols

Some general information and the respective product approvals are shown in the
labeling as symbols.
Table 4: Labeling Symbols

Symbol Meaning Description
General Symbols
Manufacturer's identification Manufacturer name and address
Data matrix code One-to-one product identification

by means of UII
(Unique Item Identifier)
General warning label Read this manual carefully for
safe use and proper handling
ESD danger sign Avoid electrostatic discharge!

 See chapter
“Safety Advice (Precautions)”
WEEE label Note on disposal
See chapter
„Disposal“
Symbols of Approvals (Examples)

Conformity marking Approval information
 See chapter
“Approvals“
Korean Certificate
Ex approvals
Ship approvals
TÜV symbol
Manual
Version 1.1.1
3.1.2 Manufacturing Number

The serial number indicates the delivery status directly after production.
Figure 2: Marking Area for Serial Numbers
There are two serial numbers in two rows in the side marking. They are left of the
release tab. The first 10 positions in the longer row of the serial numbers contain
version and date identifications.
Example structure of the rows: 0114010101…
01 14 01 01 01 (additional positions)
WW YY FW -- HW FL -
Calendar Year Firmware Hardware Firmware Internal information
week version version loader
version
The row order can vary depending on the production year, only the longer row is
relevant. The back part of this and the shorter row contain internal administration
information from the manufacturer.
In addition, the serial number is printed on the front on the cover cap of the
service interface, so that it can also be read when installed.
Manual
Version 1.1.1
3.1.3 Hardware Address (MAC-ID)

Each FC Modbus TCP; G4 (BootP) has an internationally unambiguous physical
address, referred to as the MAC-ID (Media Access Control Identity).
As part of the labeling on the right side of this component, the MAC ID is printed
in the block diagram.
In addition, the MAC ID is located on the paper strip with two self-adhesive peel-
off strips on its left side.
The MAC ID has a fixed length of 6 bytes (48 bits) which are presented
hexadecimal. The first three bytes identify the manufacturer (e.g. 00:30 DE for
WAGO). The second 3 bytes comprise the unique serial number of the hardware.
3.1.4 Update Matrix

For products that can be updated, the side inscription has a prepared matrix in
which the current update data can be entered in columns.
The matrix has rows to enter the “FA” production or work order number and to
enter the “PD” production date and “AZ” item number.
Figure 3: Update Matrix from 2016
Table 5: Legend for Figure “Update Matrix from 2016”

Description
FA Production order number, 10-digit
PD KW = calendar week
YY = year
AZ FW = firmware index
HW = hardware index
FL = firmware loader index
For factory updates to a head station, the current production or work order
number is also printed on the cover cap of the service interface.
The original manufacturing information on the product housing remains

unchanged.
Manual
Version 1.1.1
3.2 Storage, Assembly and Transport

Whenever 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.1
3.3 Assembly Guidelines/Standards

• DIN 60204 Electrical equipment of machines
• DIN EN 50178 Electronic equipment for use in power installations

(replacement for VDE 0160)
• EN 60439 Low-voltage switchgear and controlgear assemblies
Manual
Version 1.1.1
3.4 Power Supply
3.4.1 Overcurrent Protection
Possible fire hazard due to insufficient overcurrent protection!

In the event of a fault, insufficient overcurrent protection can present a possible
fire hazard. In the event of a fault, excessive current flow in the components can
cause significant overheating. Therefore, you should always dimension the
overcurrent protection according to the anticipated power usage.
The system and field voltage of the WAGO-I/O-SYSTEMs 750 is supplied on the
head stations and bus supply modules.
For components that work with extra low voltage, only SELV/PELV voltage
sources should be used.
A single voltage source supplying multiple components must be designed

according to the component with the strictest electrical safety requirements.
For components which are only allowed to be supplied by SELV voltage sources,
these requirements are listed in the technical data.
Most components in the WAGO-I/O-SYSTEM 750 have no internal overcurrent

protection. Therefore, appropriate overcurrent production must always be
implemented externally for the power supply to these components, e.g. via fuses.
The maximum permissible current is listed in the technical data of the
components used.
System supply only with appropriate fuse protection!

Without overcurrent protection, the electronics can be damaged.
For 24 V system supply input voltage an external fuse, rated max. 2 A, slow
acting, min. 30 VDC shall be used.
Field supply only with appropriate fuse protection!

For 24V field supply input voltage an external fuse, rated max. 10 A, slow acting,
min. 30 VDC shall be used.
Manual
Version 1.1.1
3.4.2 Isolation
Within the fieldbus node, there are three electrically isolated potentials:
• Electrically isolated fieldbus interface via transformer
• Electronics of the fieldbus couplers/controllers and the I/O modules (local

bus)
• All I/O modules have an electrical isolation between the electronics (local
bus, logic) and the field electronics. Some digital and analog input modules
have each channel electrically isolated, please see catalog.
Figure 4: Isolation (Example)
Manual
Version 1.1.1
3.4.3 System Supply
3.4.3.1 Connection
The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply.

The power supply is provided via the fieldbus coupler/controller and, if necessary,
in addition via internal system supply modules 750-613. The power supply is
reverse voltage protected.
Do not use an incorrect voltage/frequency!

The use of an incorrect supply voltage or frequency can cause severe damage to
the components.
Figure 5: System Supply
Table 6: Legend for Figure “System Supply”

Pos. Description
1 System supply 24 VDC (−15% / +20%)
2 System supply 0 V
The fed-in 24 VDC supplies all internal system components, e.g. fieldbus
coupler/controller electronics, fieldbus interface and I/O modules via the local bus
(5 VDC system voltage). The 5 VDC system voltage is galvanically connected to
the 24 VDC supply voltage.
Manual
Version 1.1.1
System supply only with appropriate fuse protection!

For 24 V system supply input voltage an external fuse, rated max. 2 A, slow
acting, min. 30 VDC shall be used.
Figure 6: System Voltage (Example)
Only reset the system simultaneously for all supply modules!

Reset the system by switching the system supply simultaneously at all supply
modules (fieldbus coupler/controller and potential supply module with bus power
supply) off and on again.
Manual
Version 1.1.1
3.4.3.2 Dimensioning
Recommendation
A stable power supply cannot always be assumed. Therefore, you should use
regulated power supplies to ensure the quality of the supply voltage.
The supply capacity of the fieldbus coupler/controller or the internal system

supply module can be taken from the technical data of the components.
Table 7: Alignment
Internal current consumption*) Current consumption via system voltage
(5 V for electronics of I/O modules and
fieldbus coupler/controller).
Total current for I/O modules*) Available current for the I/O modules.
Provided by the bus power supply unit.
See fieldbus coupler/controller and internal
system supply module
*) See current catalog, manuals, Internet
Manual
Version 1.1.1
Example:
Calculating the current consumption on an example coupler
Internal current consumption 300 mA at 5 V

Residual current for bus modules 700 mA at 5 V
Sum I(5 V) total 1000 mA at 5 V
The internal current consumption is indicated in the technical data for each bus
terminal. In order to determine the total requirement, add together the values of
all I/O modules in the node.
Please note the aggregate current for I/O modules. It may be necessary to
supply potential!
When the sum of the internal current consumption for the I/O modules exceeds
their aggregate current, you must use a supply module with bus power supply.
Install it before the position where the permissible aggregate current would be
exceeded.
Example:
Calculating the total current on the example coupler
A node with an example coupler consists e. g. of the following I/O modules:

20 relay modules (750-517) and 10 digital input modules (750-405).
Internal current consumption 10 * 90 mA = 900 mA

20 * 2 mA = 40 mA
Sum 940 mA
In this example, the example coupler can provide 700 mA for the I/O modules.
This value is given in the associated data sheet ("Total current for I/O modules").
Consequently, an internal system supply module (750-613), e. g. in the middle of
the node, should be added.
Recommendation
Utilize the smartDESIGNER feature WAGO ProServe® software to configure
fieldbus node assembly. You can test the configuration via the integrated
plausibility check.
The maximum input current of the 24 V system supply is 500 mA. The exact
electrical consumption (I(V)) can be determined with the following formulas:
Manual
Version 1.1.1
Fieldbus coupler or controller

I(5 V) total = Sum of all the internal current consumption of the
connected I/O modules + internal current consumption of
the fieldbus coupler/controller
Internal system supply module
I(5 V) total = Sum of all the internal current consumption of the
connected I/O modules at internal system supply module
5V I(5 V) total
Input current I(24 V) = ×
24 V η
η = Efficiency of the power supply at nominal load 24 V
Activate all outputs when testing the current consumption!

If the electrical consumption of a power supply point for the 24 V system
supply exceeds 500 mA, then the cause may be an improperly
dimensioned node or a defect.
During the test, you must activate all outputs.
3.4.4 Field Supply
3.4.4.1 Connection
Sensors and actuators can be directly connected to the relevant channel of the
I/O module in 1, 2, 3 or 4 conductor connection technology. The I/O module
supplies power to the sensors and actuators. The input and output drivers of
some I/O modules require the field side supply voltage.
The power supply modules provide field side power (24 VDC). In this case it is a
passive power supply without protection equipment. Power supply modules are
available for different potentials, e.g. 24 VDC, 230 VAC or others.
Power supply modules with or without fuse holder and diagnostic capability are
available for the power supply of other field potentials (24 VDC,
0 … 230 VAC/DC, 120 VAC, 230 VAC). The power supply modules can also be
used to set up various potential groups. The connections are connected in pairs
to a power contact.
Manual
Version 1.1.1
Figure 7: Field Supply (Sensor/Actuator)
Table 8: Legend for Figure “Field Supply (Sensor/Actuator) for ECO Fieldbus Coupler”
Field supply
1 24 V (-15 % / +20 %)
2 0V
3 Optional ground potential (functional earth)
Power jumper contacts
4 Potential distribution to adjacent I/O modules
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.
The field-side power supply is automatically derived from the power jumper
contacts when snapping an I/O module.
The current load of the power contacts must not exceed 10 A on a continual
basis.
By inserting an additional power supply module, the field supply via the power
contacts is disrupted. From there a new power supply occurs which may also
contain a new voltage potential.
Manual
Version 1.1.1
Re-establish the ground connection when the connection to the power

jumper contacts is disrupted!
Some I/O 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 via power jumper contacts for subsequent I/O modules,
then you have to use a power supply module.
Note the data sheets of the I/O modules.
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
24 VDC to 230 VAC, 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.4.4.2 Fusing via Power Supply Module
Internal fusing of the field supply is possible for various field voltages via an
appropriate power supply module.
Table 9: Power Supply Modules

Order No. Field Voltage
750-601 24 V DC, Supply/Fuse
750-609 230 V AC, Supply/Fuse
750-610 24 V DC, Supply/Fuse/Diagnosis
750-611 230 V AC, Supply/Fuse/Diagnosis
750-606 Supply Module 24 V DC, 1,0 A, Ex i
750-625/000-001 Supply Module 24 V DC, 1,0 A, Ex i (without diagnostics)
Manual
Version 1.1.1
Figure 8: Supply Module with Fuse Carrier (Example 750-610)
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.
Manual
Version 1.1.1
In order to insert or change a fuse, or to switch off the voltage in succeeding I/O
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 9: Removing the Fuse Carrier
Lifting the cover to the side opens the fuse carrier.
Figure 10: Opening the Fuse Carrier
Figure 11: Changing the Fuse
After changing the fuse, the fuse carrier is pushed back into its original position.
Manual
Version 1.1.1
3.4.4.3 Fusing external
Field supply only with appropriate fuse protection!

For 24V field supply input voltage an external fuse, rated max. 10 A, slow acting,
min. shall be used.
The 24V input voltage for the field supply is provided with an external fuse with
max. 10 A slow acting, min. 30 VDC, to be secured.
For the external fusing, the fuse modules of the WAGO series 282, 2006, 281
and 2002 are suitable for this purpose.
Figure 12: Fuse Modules for Automotive Fuses, Series 282
Figure 13: Fuse Modules for Automotive Fuses, Series 2006
Figure 14: Fuse Modules with Pivotable Fuse Carrier, Series 281
Manual
Version 1.1.1
Figure 15: Fuse Modules with Pivotable Fuse Carrier, Series 2002
Manual
Version 1.1.1
3.4.5 Supplementary Power Supply Regulations

The WAGO-I/O-SYSTEM 750 can also be used in shipbuilding or offshore and
onshore areas of work (e. g. working platforms, loading plants). This is
demonstrated by complying with the standards of influential classification
companies such as Germanischer Lloyd and Lloyds Register.
Filter modules for 24 V supply are required for the certified operation of the
system.
Table 10: Filter Modules for 24 V Supply

Order No. Name Description
750-626 Supply Filter Filter module for system supply and field supply
(24 V, 0 V), i. e. for fieldbus coupler/controller and bus
power supply (750-613)
750-624 Supply Filter Filter module for the 24 V field supply
(750-602, 750-601, 750-610)
Therefore, the following power supply concept must be absolutely complied with.
Figure 16: Power Supply Concept
Use a supply module for equipotential bonding!

Use an additional 750-601/ 602/ 610 Supply Module behind the 750-626 Filter
Module if you want to use the lower power jumper contact for equipotential
bonding, e.g., between shielded connections and require an additional tap for this
potential.
Manual
Version 1.1.1
3.4.6 Supply Example

SupplSggggggggggggggggg
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.
Figure 17: Supply Example
Manual
Version 1.1.1
Table 11: Legend for Figure “Supply Example for Fieldbus Coupler/Controller”
Pos. Description
1 Power Supply on fieldbus coupler/controller via external Supply Module
2 Power Supply with optional ground
3 Internal System Supply Module
4 Separation Module recommended
5 Supply Module passive
6 Supply Module with fuse carrier/diagnostics
Manual
Version 1.1.1
3.4.7 Power Supply Unit

The WAGO-I/O-SYSTEM 750 requires a 24 VDC voltage (system supply).
Recommendation
A stable power supply cannot always be assumed everywhere. Therefore, you
should use regulated power supplies to ensure the quality of the supply voltage.
Buffer for system power supply!

The system power supply must be buffered to bridge power outages. As the
power demand depends on the respective node configuration, buffering is not
implemented internally.
To achieve power outages of 1 ms to 10 ms according to IEC61131-2, determine
the buffering appropriate for your node configuration and structure it as an
external circuit.
The power demand must be determined individually depending on the entry point
of the field supply. All loads through field devices and I/O modules must be taken
into account. The field supply also impacts the I/O modules because the input
and output drivers of some I/O modules require the voltage of the field supply.
System and field supply must be isolated!

The system supply and field supply must be isolated to ensure bus operation in
the event of short circuits on the actuator side.
Power supply units are available in the eShop.

You can find suitable power supply units, e. g. from the EPSITRON series, in the
eShop on www.wago.com.
Manual
Version 1.1.1
3.5 Grounding
3.5.1 Grounding the DIN Rail
3.5.1.1 Framework Assembly
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 electrical connection is established via the screw. Thus,
the carrier rail is grounded.
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.5.1.2 Insulated Assembly
Insulated assembly has been achieved when there is constructively no direct

ohmic contact between the cabinet frame or machine parts and the carrier rail.
Here, the earth ground must be set up via an electrical conductor in accordance
with valid national safety regulations.
Recommendation
The optimal setup is a metallic assembly plate with grounding connection which
is electrically conductive linked to 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 12: WAGO Ground Wire Terminals

Order No. Description
283-609 1-conductor ground (earth) terminal block make an automatic
contact to the carrier rail; conductor cross section:
0.2 mm² … 16 mm2
Note: Also order the end and intermediate plate (283-320).
Manual
Version 1.1.1
3.5.2 Grounding Function

The grounding function increases the resistance against electro-magnetic
interferences. Some components in the I/O system have a carrier rail contact that
dissipates electro-magnetic interferences to the carrier rail.
Figure 18: Carrier Rail Contact (Example)
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, see section “Mounting” > … > “Carrier
Rail Properties”.
The bottom CAGE CLAMP® connectors of the supply modules enable optional
connection of a field-side functional ground. This potential is made available to
the I/O module arranged on the right through the spring-loaded contact of the
three power contacts. Some I/O modules are equipped with a knife-edge contact
that taps this potential. This forms a potential group with regard to functional
ground with the I/O module arranged on the left.
Manual
Version 1.1.1
3.6 Shielding
3.6.1 General
Use of shielded cables reduces electromagnetic interference and thus increases
signal quality. Measurement errors, data transmission errors and interference
due to excessive voltage can be prevented.
Connect the cable shield to the ground potential!

Integrated shielding is mandatory to meet the technical specifications in regards
to measuring accuracy. Connect the cable shield and ground potential at the inlet
to the cabinet or housing. This allows induced interference to dissipate and to be
kept away from devices in the cabinet or housing.
Figure 19: Cable Shield at Ground Potential
Improve shielding performance by placing the shield over a large area!

Higher shielding performance is achieved via low-impedance connection
between shield and ground. For this purpose, connect the shield over a large
surface area, e.g., WAGO shield connecting system. This is especially
recommended for large-scale systems where equalizing current or high impulse-
type currents caused by atmospheric discharge may occur.
Keep data and signal lines away from sources of interference!

Route data and signal lines separately from all high voltage cables and other
sources of high electromagnetic emission (e.g., frequency converter or drives).
3.6.2 Fieldbus Cables

The shielding of fieldbus lines is described in the respective configuration
guidelines and standards of the fieldbus system. Information on this can be
provided by the corresponding fieldbus organization or specialist literature.
Manual
Version 1.1.1
3.6.3 Shielded Signal Lines
Use shielded signal lines!

Always use shielded signal lines for analog signals and I/O modules which are
equipped with shield clamps. Only then you can ensure that the accuracy and
interference immunity specified for the respective I/O module can be achieved
even in the presence of interference acting on the signal cable.
3.6.4 WAGO Shield Connecting System

The series 790 WAGO shield connecting system consists of shield clamping
saddles, busbars and various mounting carriers. These components can be used
to achieve many different configurations.
Figure 20: Examples of the WAGO Shield Connecting System
Figure 21: Application of the WAGO Shield Connecting System
Manual
Version 1.1.1
WAGO I/O System 750 Device Description 51
4 Device Description
The 750-362, 750-362/0000-0001 Fieldbus Coupler connects as the head station
of the node assembly the WAGO-I/O-SYSTEM 750 or 753 to the ETHERNET
fieldbus system.
This head station 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 head
station 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, static setting) can be given.
In the head station, all input signals from the sensors are combined. After
connecting the head station, the head station determines which I/O modules are
on the node and creates a local process image from theirs data. Analog and
specialty module data is sent via words and/or bytes; digital data is grouped bit-
by-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 head station.
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 head station 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 RJ-45 ETHERNET ports, which are
connected to the head station via an integrated ETHERNET switch. Both
ETHERNET ports independently support the following functions:
• 10BASE-T and 100BASE-TX

• Full and Half duplex
• Autonegotiation
• Auto-MDI(X)
Durch die Unterstützung von Autonegotiation und Auto-MDI/MDI-X ist keine

manuelle Konfiguration der Übertragungsrate notwendig und es können sowohl
Patch- als auch Crossover-Kabel verwendet werden.
Manual
Version 1.1.1
52 Device Description WAGO I/O System 750
By supporting of auto-negotiation and auto-MDI/MDI-X, no manual configuration
of the transmission rate is necessary and both patch and crossover cables can
be used.
In order to send process data via ETHERNET, the head station supports a series
of network protocols.
The Modbus TCP/UDP protocol is implemented for exchanging process data.

For the management and diagnosis of the system, the HTTP and SNMP
protocols are available.
For the data transfer via ETHERNET the FTP and SFTP are available.
For the automatic assignment of the IP address in the network, alternatively

DHCP or BootP can be used.
An internal server is available for Web-based applications.
HTML pages stored in the head station 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.1
4.1 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.
Figure 22: View FC Modbus TCP; G4
Manual
Version 1.1.1
Table 13: Legend for Figure “View”
Desig-
Pos. Meaning Details see Section
nation
LINK ACT
„Device Description“ >
1 1, 2, MS, Status LEDs Fieldbus
„Display Elements“
NS, I/O
Marking possibility on four miniature WSB
2 --- ---
markers
"Connect Devices" > "Data
3 --- Data contacts
Contacts/Local Bus"
"Mounting" >
4 --- Unlocking lug "Inserting and Removing
Devices"
"Device Description" >
5 --- Service interface (open flap)
"Operating Elements"
Fieldbus connection 2 x RJ-45 as 2-Port „Device Description“ >
6 X1, X2
ETHERNET Switch „Connectors“
CAGE CLAMP® Connections System "System Description"
7 -
Supply 0 VDC >"Voltage Supply"
CAGE CLAMP® Connections System Supply "System Description"
8 +
24 VDC >"Voltage Supply"
„Mounting“ > „Plugging and
9 --- Locking Disc
Removal of the Device“
"Device Description" >
10 --- Address Selection Switch
"Operating Elements"
Manual
Version 1.1.1
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 to the electrical potential of the

device.
Figure 23: Device Supply
Manual
Version 1.1.1
4.2.2 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 socket is arranged physically lower, allowing the coupler to fit in an 80 mm
high enclosure after plug connection.
Figure 24: RJ-45 Connector
Table 14: RJ-45 Connector and RJ-45 Connector Configuration

Contact Signal
1 TD + Transmit +
2 TD − Transmit −
3 RD + Receive +
4 free
5 free
6 RD − Receive −
7 free
8 free
Do not 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.1
4.3 Display Elements

The operating condition of the fieldbus 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 guides. In some
cases, the LEDs are multi-colored (red, green or orange).
Figure 25: Display Elements

+
For the diagnostics of the different ranges fieldbus and node, the LED’s can be
divided into groups:
Table 15: Display Elements Fieldbus Status

LED Color Meaning
LNK ACT 1 green indicates a connection to the physical network at port 1
LNK ACT 2 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 16: 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 state in the
section “Diagnostics” > … > “LED Signaling”.
Manual
Version 1.1.1
4.4 Operating Elements
4.4.1 Service Interface

The service interface is located behind the flap.
It is used for the communication with the WAGO I/O-CHECK and WAGO
Ethernet Settings.
Figure 26: Service Interface (Closed and Opened Flap)
Table 17: Legend for Figure “Service Interface (Closed and Opened Flap)”
Number Description
1 Open closed
2 View Service 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 connection to the 4-pin header under the cover flap can be realized via the
communication cables with the item numbers750-920 and 750-923 or via the
WAGO radio adapter with the item number 750-921.
Manual
Version 1.1.1
4.4.2 Address Selection Switch
Figure 27: Address Selection Switch (for example setting “0“)
The 8-pole DIP switch is used to select the protocol for setting the IP address
and as an address selection switch, to set the IP address.
The IP address is composed of a network component and a host component.
Network Host
192. 168. 1. 0 … 255
The network component is configurable and in delivery status 192.168.1.
The host component is set via the DIP switches of the address selection switch.
The coding with the DIP switches is bit-wise, starting with DIP switch 1 with the
least significant bit (20) to DIP switch 8 with the most significant bit (27),
corresponding to the values 0 to 255.
Table 18: Meaning of DIP Switch Positions

DIP Switch Value Meaning
Positions
(ON = 1)
The IP configuration set in the WBM on the
00000000 0 "Port" WBM page is used (default DHCP, but
(WBM) can be changed to BootP or EEPROM).
Host component by switch position
00000001… 1-254 Example of setting the DIP switch:
11111110 Host For the IP address 192.168.1.33, the 1st and
component 6th switches must be set: 20 (1st switch) + 25
(6th switch) = 33
255 The DHCP protocol is used to configure the IP
11111111
(DHCP) parameters.
Manual
Version 1.1.1
4.5 Technical Data
4.5.1 Device Data

Table 19: Technical Data - Device
Width 49.5 mm
High 96.8 mm
Length 71.9 mm
Length (from upper edge of DIN 35 64.7 mm
rail)
Weight 104.8 g
4.5.2 System Data

Table 20: Technical Data - System
Number of fieldbus nodes per master Limited by ETHERNET specification
Transmission medium Twisted Pair CAT 5e (S/UTP or S/STP)
Fieldbus coupler connection 2 x RJ-45
Max. cable length 100 m
Max. network length 2000 m
Baud rate 10/100 Mbit/s
Transmission performance Class D acc. to EN 50173
Protocols Modbus TCP/UDP, HTTP, HTTPS, BootP,
DHCP, DNS, SNTP, (S)FTP, SNMP
Max. number of socket links 15 Modbus TCP
Number of I/O modules 64
- with bus extension 250
Configuration via WBM, DIP Switch, WAGO Ethernet
Settings
Internal file system 1 GB
4.5.3 Supply
Table 4: Technical Data - Supply
Voltage Supply 24 V DC (-25% ... +30%)
Max. input current at 24 V DC. 280 mA
Power failure time acc. IEC 61131-2 Depending on external buffering
Efficiency of the power supply 90 %
Internal current consumption (5 V) 350 mA
Total current for I/O modules (5 V) 700 mA
Overvoltage category II
Isolation 500 V system/supply
Manual
Version 1.1.1
Buffer for system power supply!

The system power supply must be buffered to bridge power outages. As the
power demand depends on the respective node configuration, buffering is not
implemented internally.
To achieve power outages of 1 ms to 10 ms according to IEC61131-2, determine
the buffering appropriate for your node configuration and structure it as an
external circuit.
4.5.4 Fieldbus Modbus TCP

Table 5: Technical Data - Fieldbus Modbus TCP
Eingangsprozessabbild max 1020 words
Ausgangsprozessabbild max 1020 words
4.5.5 Accessories
Table 21: Technical data – Accessories
Miniature WSB Quick marking system
4.5.6 Connection Type

Table 22: Technical Data ‒ Field Wiring
Connection technology CAGE CLAMP®
Conductor cross-section, solid wire 0.08 mm² … 2.5 mm² / AWG 28 … 14
Conductor cross-section,
fine-stranded wire 0.25 mm² … 2.5 mm² / AWG 28 … 12
Strip length 8 mm … 9 mm / 0.33 in
Table 23: Technical Data – Data Contacts

Data contacts Slide contact, hard gold plated, self-
cleaning
Manual
Version 1.1.1
4.5.7 Climatic Environmental Conditions

Table 24: Technical Data – Climatic Environmental Conditions
Surrounding air temperature, operation 0 °C … 55 °C
Surrounding air temperature, storage −25 °C … +85 °C
Operating altitude 0 … 2000 m
Relative humidity Max. 5 % … 95 % without condensation
Pollution degree 2
Protection type IP20
Resistance to harmful substances Acc. to IEC 60068-2-42 and
IEC 60068-2-43
Maximum pollutant concentration at SO2 ≤ 25 ppm
relative humidity < 75 % H2S ≤ 10 ppm
Special conditions • Ensure that additional measures for
components are taken, which are
used in an environment involving:
– dust, caustic vapors or gases
– ionizing radiation
• The permissible temperature range
of the connecting cable must be
dimensioned based on the mounting
position and current intensity, as the
temperature of the terminal
connection can be up to 25 °K
above the maximum expected
surrounding air temperature (at
10 A).
Manual
Version 1.1.1
4.5.8 Mechanical Strength

Table 25: Technical Data – Mechanical Strength
Vibration resistance 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
Shock resistance 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.
Free fall Acc. IEC 60068-2-32
≤ 1 m (module in original packing)
4.5.9 Software Compatibility

Table 26: Technical Data – Software Compatibility
WAGO-I/O-CHECK 759-302
Commissioning software
starting from version 3.18.1.2
WAGO Ethernet Settings 759-316
Configuration software
starting from version 6.9.9.16
Manual
Version 1.1.1
4.6 Approvals
For current approvals, please go to: www.wago.com/<Item number>.
The following approvals have been granted to 750-362, 750-362/0000-0001

fieldbus coupler/controller:
Conformity Marking
Ordinary
UL61010-2-201
Locations
Korea Certification MSIP-REM-W43-PFC750
The following Ex approvals have been granted to 750-362, 750-362/0000-0001

Hazardous UL 121201 for Use in Hazardous Locations

Locations Cl I Div 2
TÜV 14 ATEX 148929 X

II 3 G Ex ec IIC T4 Gc
IECEx TUN 14.0035 X
Ex ec IIC T4 Gc
Brasilian- TUEV 12.1297 X

Ex Ex ec IIC T4 Gc
The following ship approvals have been granted to 750-362, 750-362/0000-0001

ABS (American Bureau of Shipping)
DNV GL
[Temperature: B, Humidity: B, Vibration: B, EMC: B, Enclosure: A]
PRS (Polski Rejestr Statków)
Manual
Version 1.1.1
4.7 Standards and Guidelines

750-362, 750-362/0000-0001 meets the following requirements on emission and
immunity of interference:
EMC CE-Immunity to interference EN 61000-6-2
EMC CE-Emission of interference EN 61000-6-3
EMC marine applications-Immunity

to interference acc. to DNV
EMC marine applications-Emission

of interference acc. to DNV
Manual
Version 1.1.1
66 Mounting WAGO I/O System 750
5 Mounting
5.1 Installation Position
Along with horizontal and vertical installation, all other installation positions are
allowed.
Use an end stop in the case of vertical mounting!

In the case of vertical assembly, an end stop has to be mounted as an additional
safeguard against slipping.
WAGO order no. 249-116 End stop for DIN 35 rail, 6 mm wide
WAGO order no. 249-117 End stop for DIN 35 rail, 10 mm wide
5.2 Overall Configuration

The maximum total length of a fieldbus node without fieldbus coupler/controller is
780 mm including end module. The width of the end module is 12 mm. When
assembled, the I/O modules have a maximum length of 768 mm.
Examples:
• 64 I/O modules with a 12 mm width can be connected to a fieldbus

coupler/controller.
• 32 I/O modules with a 24 mm width can be connected to a fieldbus

coupler/controller.
Exception:
The number of connected I/O modules also depends on the type of fieldbus
coupler/controller is used. For example, the maximum number of stackable I/O
modules on one PROFIBUS DP/V1 fieldbus coupler/controller is 63 with no
passive I/O modules and end module.
Observe maximum total length of a fieldbus node!

The maximum total length of a fieldbus node without fieldbus coupler/controller
and without using a 750-628 I/O Module (coupler module for internal data bus
extension) may not exceed 780 mm.
Also note the limitations of individual fieldbus couplers/controllers.
Manual
Version 1.1.1
WAGO I/O System 750 Mounting 67
Increase the total length using a coupler module for internal data bus
extension!
You can increase the total length of a fieldbus node by using a 750-628 I/O
Module (coupler module for internal data bus extension). For such a
configuration, attach a 750-627 I/O Module (end module for internal data bus
extension) after the last I/O module of a module assembly. Use an RJ-45 patch
cable to connect the I/O module to the coupler module for internal data bus
extension of another module block.
This allows you to segment a fieldbus node into a maximum of 11 blocks with
maximum of 10 I/O modules for internal data bus extension.
The maximum cable length between two blocks is five meters.
More information is available in the manuals for the 750-627 and 750-628 I/O
Modules.
Manual
Version 1.1.1
5.3 Mounting 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 60175 (DIN 35).
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 electro-

magnetic 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 I/O 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 metal 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.1
5.3.2 WAGO DIN Rails

WAGO carrier rails meet the electrical and mechanical requirements shown in the
table below.
Table 27: WAGO DIN Rails

Item No. Description
210-112 35 × 7.5; 1 mm; steel; bluish, tinned, chromed; slotted
210-113 35 × 7.5; 1 mm; steel; bluish, tinned, chromed; unslotted
210-197 35 × 15; 1.5 mm; steel; bluish, tinned, chromed; slotted
210-114 35 × 15; 1.5 mm; steel; bluish, tinned, chromed; unslotted
210-118 35 × 15; 2.3 mm; steel; bluish, tinned, chromed; unslotted
210-198 35 × 15; 2.3 mm; copper; unslotted
210-196 35 × 8.2; 1.6 mm; aluminum; unslotted
5.4 Spacing
The spacing between adjacent components, cable conduits, casing and frame
sides must be maintained for the complete fieldbus node.
Figure 28: 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.1
5.5 Mounting Sequence

Fieldbus couplers, controllers and I/O modules of the WAGO I/O System 750 are
snapped directly on a carrier rail in accordance with the European standard EN
60175 (DIN 35).
The reliable positioning and connection is made using a tongue and groove
system. Due to the automatic locking, the individual devices are securely seated
on the rail after installation.
Starting with the fieldbus coupler or controller, the I/O modules are mounted
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 I/O modules with power contacts (blade contacts) cannot be
linked to I/O modules with fewer power contacts.
Risk of injury due to sharp-edged blade contacts!

The blade contacts are sharp-edged. Handle the I/O module carefully to prevent
injury. Do not touch the blade contacts.
Insert I/O modules only from the proper direction!

All I/O modules feature grooves for power jumper contacts on the right side. For
some I/O modules, the grooves are closed on the top. Therefore, I/O modules
featuring a power jumper contact on the left side cannot be snapped from the
top. This mechanical coding helps to avoid configuration errors, which may
destroy the I/O modules. Therefore, insert I/O modules only from the right and
from the top.
Don't forget the bus end module!

Always plug a bus end module (e.g. 750-600) onto the end of the fieldbus node!
You must always use a bus end module at all fieldbus nodes with WAGO I/O
System 750 fieldbus couplers or controllers to guarantee proper data transfer.
Manual
Version 1.1.1
5.6 Inserting and Removing Devices
Do not work when devices are energized!

High voltage can cause electric shock or burns.
Switch off all power to the device prior to performing any installation, repair or
maintenance work.
Manual
Version 1.1.1
5.6.1 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.
Figure 29: Release Tab
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.1
5.6.3 Inserting the I/O Module

1. Position the I/O module so that the tongue and groove joints to the fieldbus
coupler or controller or to the previous or possibly subsequent I/O module
are
engaged.
Figure 30: Insert I/O Module (Example)
2. Press the I/O module into the assembly until the I/O module snaps into the
carrier rail.
Figure 31: Snap the I/O Module into Place (Example)
With the I/O module snapped in place, the electrical connections for the data
contacts and power jumper contacts (if any) to the fieldbus coupler or controller
or to the previous or possibly subsequent I/O module are established.
Manual
Version 1.1.1
5.6.4 Removing the I/O Module

1. Remove the I/O module from the assembly by pulling the release tab.
Figure 32: Removing the I/O Module (Example)
Electrical connections for data or power jumper contacts are disconnected when
removing the I/O module.
Manual
Version 1.1.1
WAGO I/O System 750 Connect Devices 75
6 Connect Devices
6.1 Data Contacts/Local Bus
Communication between the fieldbus coupler/controller and the I/O modules as
well as the system supply of the I/O modules is carried out via the local bus. The
contacting for the local bus consists of 6 data contacts, which are available as
self-cleaning gold spring contacts.
Figure 33: 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 devices are equipped with electronic components that may be destroyed by
electrostatic discharge. When handling the devices, ensure that the environment
(persons, workplace and packing) is well grounded. Avoid touching conductive
components, e.g. data contacts.
Manual
Version 1.1.1
76 Connect Devices WAGO I/O System 750
6.2 Power Contacts/Field Supply
Risk of injury due to sharp-edged blade contacts!

The blade contacts are sharp-edged. Handle the I/O module carefully to prevent
injury. Do not touch the blade contacts.
Self-cleaning power jumper contacts used to supply the field side are located on
the right side of most of the fieldbus couplers/controllers and on 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 34: 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 fieldbus node. You can test the configuration via the integrated
accuracy check.
Manual
Version 1.1.1
WAGO I/O System 750 Connect Devices 77
6.3 Connecting a Conductor to the CAGE CLAMP®

The WAGO CAGE CLAMP® connection is appropriate for solid, stranded and
finely stranded conductors.
Only connect one conductor to each CAGE CLAMP®!

Only one conductor may be connected to each CAGE CLAMP®.
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 feed-
through terminals.
1. For opening the CAGE CLAMP® insert the actuating tool into the opening
above the connection.
2. Insert the conductor into the corresponding connection opening.
3. For closing the CAGE CLAMP® simply remove the tool. The conductor is
now clamped firmly in place.
Figure 35: Connecting a Conductor to a CAGE CLAMP®
Manual
Version 1.1.1
78 Function Description WAGO I/O System 750
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.
Figure 36: Operating System
More information about the LED Signaling

Read the detailed description for the evaluation of the displayed LED state in the
Manual
Version 1.1.1
WAGO I/O System 750 Function Description 79
7.2 Process Data Architecture
7.2.1 Basic Structure

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 byte-
oriented I/O modules, which send data byte by byte. This group includes, for
example, counter modules and angle and distance measurement 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 physical 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.
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.
Manual
Version 1.1.1
Local bus extension with Coupler Module and End Module!

With the use of Bus Extension Coupler Module 750-628 and Bus Extension End
Module 750-627, it is possible to operate up to 250 I/O 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”.
7.2.2 Process Data MODBUS TCP

For some I/O modules (and their variations), the structure of the process data
depends on the fieldbus.
For the fieldbus controller with MODBUS, the process image is built up word-by-
word (with word alignment). The internal mapping method for data greater than
one byte conforms to Intel formats.
For the respective fieldbus-specific structure of the process values of any I/O
module within the 750 or 753 Series of the WAGO-I/O-SYSTEM, refer to Section
"Structure of Process Data for MODBUS/TCP".
Manual
Version 1.1.1
7.3 Data Exchange

With the fieldbus coupler, data is exchanged via the Modbus TCP or
Modbus UDP protocol.
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 defined number of simultaneous connections (socket connections) with other

network devices can be established to a fieldbus coupler:
• 3 connections for HTTP(S) (to read HTML pages from the coupler)
• 15 connections via Modbus TCP (to read or write input and output data of
the coupler)
• 10 connections for FTP
The maximum number of simultaneous connections can not be exceeded.

Existing connections must first be terminated before new ones can be set up.
The FC Modbus TCP; G4 (BootP) 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.
Manual
Version 1.1.1
7.3.1 Memory Space
Figure 37: Memory Areas and Data Exchange
The fieldbus 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 FC Modbus TCP; G4 (BootP) 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.2 Addressing
Module inputs and outputs in a fieldbus coupler are addressed internally as soon
as they 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.
Manual
Version 1.1.1
7.3.2.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
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.
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.
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 28: Data Width for I/O Modules

Data width > 1 byte (channel) Data width = 1 bit (channel)
Analog input modules Digital input modules
Analog output modules Digital output modules
Input modules for thermocouples Digital output modules with
diagnostics (2 bits/channel)
Input modules for resistor sensors Supply modules with fuse
carrier/diagnostics
Pulse width output modules Solid-state load relays
Interface modules Relay output modules
Up/down counters
I/O modules for angle and distance
measurement
Manual
Version 1.1.1
7.3.3 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 29: 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
Process data Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit
word 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte
High byte D1 Low byte D0
Output can be read back in by adding an offset of 200hex (0x0200) to the

MODBUS address.
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.
Figure 38: Data Exchange Between MODBUS Master and I/O Modules
Manual
Version 1.1.1
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.
Additional Information
A detailed description of the MODBUS addressing may be found in Chapter
"MODBUS Register Mapping".
7.4 Logging
For diagnostic purposes, a message protocol can be recorded in the form of a log
book via the head station.
The log messages can be sent to a syslog server or saved on the internal or, if
available, on an external file system (e g. memory card).
Rapid aging of the internal storage medium!

Note, when the log output is activated on the internal file system, excessive log
output leads to faster aging of the storage medium.
In addition, by lowering the log level this is also favored.
Therefore You should only use the log output in a targeted manner
(troubleshooting / support case) or use external / exchangeable storage media (if
supported by the device).
Sending and saving of log messages is done by selecting the respective log
level, which indicates the severity of the event (e.g. INFO, WARNING, ERROR).
The log level defines the threshold for the log outputs on the network "Network
log level" or for storage on the file system "File log level".
Example:
Log messages with the severity "INFO" are only recorded and displayed if at
least one of the two log level options is set to "INFO".
The online log works as a ring buffer and shows the last 256 log entries in
chronologically descending order.
For saving, the entries are downloaded in a single merged log file.
This log file in CSV format (comma-separated values) can be opened with a
normal text editor or imported and processed with a spreadsheet program (e g.
Microsoft Excel).
Manual
Version 1.1.1
The file name of the log file has the following structure:
Table 30: Log File Name Syntax

Syntax Description
log_<MAC5:3>_<YYMMDDTHHMMSS>.csv
<MAC5:3> The last 3 digits of the MAC ID
(MAC-ID without OUI part)
<YYMMDDTHHMMSS> Date and time on the device
The fill level of the log memory can be limited by a limit value in%.
The maximum size results from the number and the maximum size of the log
files.
With a set value between 1% and 100%, the current fill level of the log memory is
monitored and a message is generated if the set limit value is exceeded (blink
code and log message).
If the value is set to 0%, the level is not monitored.
When the saved log files are deleted on the device, any warning regarding the fill
level of the log memory (blink code) is also reset.
To avoid data loss, the following points must be observed:
• The log files can only be called up via the WBM using the download
function [Download] and emptying using the delete function [Delete].
Direct access to the log directory "A:\log" or "S:\log" via FTP or SFTP as
well as the renaming of log files is not permitted and can lead to access
conflicts or inconsistent log information.
• No storage of user-specific files in the log directories "A:\log" or "S:\log".
The contents of the log directories “A:\log” or “S:\log” are not included in the
Backup & Restore function.
Manual
Version 1.1.1
WAGO I/O System 750 Commissioning 87
8 Commissioning
This section shows a step-by-step procedure for starting up exemplarily a WAGO
fieldbus node.
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 PC under Windows.
In principle, only a few steps are required for start-up.
To enable communication from your PC to the fieldbus coupler/controller over

network, both must be in the same network. This requires that you first determine
the IP address of the PC and then assign a corresponding IP address to the
fieldbus node. There are several options being available for IP address
assignment.
The description of these single work steps can be found in the corresponding
following chapters.
• Connecting PC and fieldbus node

• Determing IP address of the PC
• Assigning IP address to the fieldbus node
• Applying IP address permanently (option “static”)
Following the commissioning descriptions after which the fieldbus node is ready
for communication, the following topics are described:
• Preparing the Flash File System

• Synchronizing the System Time
• Restoring Factory Settings
Manual
Version 1.1.1
88 Commissioning WAGO I/O System 750
8.1 Connecting Client PC and Fieldbus Nodes

1. Mount the fieldbus node on the TS 35 carrier rail.
Follow the mounting instructions found in the “Mounting” chapter.
2. Connect the 24 V power supply to the supply terminals.
3. Connect the PC's ETHERNET interface to the head station's ETHERNET

interface (RJ-45) of your fieldbus node.
4. Turn the operating voltage on.
The head station is initialized. The head station determines the I/O module
configuration of the fieldbus node 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 node is operational.
If an error has occurred during initialization, it is red flashed with an error code by
the I/O LED.
If the I/O LED flashes 6 times (indicating error code 6) and then 4 times
(indicating error argument 4), this indicates that an IP address has not been
assigned yet.
8.2 Determining the IP Address of the PC

To determine the IP address of the PC (with Microsoft Windows operating
system) using the MS DOS prompt, proceed as follows:
1. Go via "Start"> "Search programs/files".
2. Enter the command "cmd" in the input field.
3. Choose at
(Windows 7): "cmd.exe" and
(Windows 10): "Command Prompt".
4. Press [Enter] key to confirm the entry.
The MS DOS prompt window opens.
5. In the MS DOS prompt window enter the command “ipconfig”.
6. Press [Enter] key to confirm the entry.
The IP address, subnet mask and the default gateway with the corresponding
parameters of the PC are displayed.
Manual
Version 1.1.1
8.3 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 7) is indicated by 'I/O' LED at the next power-on.
• Use address selection switch (DIP switch) to assign IP address

(manually).
• Automatic assignment of addresses via DHCP

(IP address via the fieldbus)
• Assigning IP Address via “WAGO Ethernet Settings”
(static IP address via the serial communication port or the ETHERNET
interface)
• Assigning IP Address via BootP
(IP address via the fieldbus)
8.3.1 Assigning IP Address via Address Selection Switch

Use the address selection switch to set the host ID, which is the last byte of the
IP address, with values between 1 and 254 binary coded.
The first three bytes of the IP address are specified by the fieldbus coupler/
controller. The fieldbus coupler/controller uses a static base IP address to assign
the IP address via the address selector switch.
The basic IP address can be changed via the Web-based management or
WAGO Ethernet settings (in the delivery state: 192.168.1.0).
The subnet mask and default gateway values are taken from the static settings
(as delivered: subnet mask = 255.255.255.0, default gateway = 0.0.0.0).
Example:
Base IP address: 192.168.1.0

Set DIP switch value: 50 (binary coded: 00110010)
Resulting IP address: 192.168.1.50
Manual
Version 1.1.1
Table 31: Address selection switch values (host ID)
Address selection switch Description
Address selection switch is enabled.
The host ID is set to a fixed value between 1 ... 254.
The IP address consists of the static base address
1 … 254
and the set host ID. The IP address set via the
current device configuration (DHCP, BootP, static) is
disabled.
Address selection switch is disabled.
0 The IP address set via the current device
configuration (DHCP, BootP, static) is used.
Address selection switch is disabled.
255
The IP address is obtained from a DHCP server.
More information about changing the static base address

You can also change the static base address currently saved in the fieldbus
coupler/controller as required. Proceed as described for example in the section
“Assigning IP Address via “WAGO Ethernet Settings””.
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).
Figure 39: Address Selection Switch, for Example the Value Setting “50” (21 + 24 + 25)
3. Restart the fieldbus node after adjusting the address selection switch to
apply the configuration changes.
Manual
Version 1.1.1
8.3.2 Assigning IP Address via DHCP
Set the address selection switch to 255 for assigning the IP address via
DHCP!
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.
In delivery state of the head station, the dynamic assignment of the IP address is
active by means of "Dynamic Host Configuration Protocol" (DHCP).
When the DHCP protocol is enabled the head station of fieldbus node expects
the DHCP server to be permanently available. If there is no DHCP server
available after a Power On reset, the network will remain inactive.
If DHCP is not active, it is necessary to enable DHCP, e. g. via "WAGO Ethernet

Settings" or via the WBM (see chapters "Enable DHCP via "WAGO Ethernet
Settings" (without existing IP address)" or "Enable DHCP via WBM (with existing
IP address)").
Then the IP address assignment with DHCP takes place automatically via a
DHCP server in the network.
If there is no DHCP server on your local PC, you can download a DHCP server
free of charge from the Internet and install it on your PC.
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.
Assign the DHCP server a fixed IP address and note common subnet!
Note that the DHCP server must have a fixed IP address and that the fieldbus
node and DHCP server must be in the same subnet.
After the IP address was assigned by means of DHCP, it can be determined via
the settings or outputs of the respective DHCP server, such as via the output of
"Open DHCP", for example.
Manual
Version 1.1.1
Via DHCP assigned IP addresses are only temporarily valid!

Note that an IP address assigned via DHCP is limited in time. If the DHCP server
is not available at the end of its useful life, the fieldbus node sets the IP address
free and then the fieldbus node is no longer accessible!
In order to use the IP address permanently, change it to “static” (see chapter

"Apply IP address permanently (option "static ")").
Manual
Version 1.1.1
8.3.2.1 Enable DHCP via "WAGO Ethernet Settings" (without existing IP

address)"
Note Software Compatibility!

Refer to the version of the software specified in "Software Compatibility" in the
Technical Data.
In the delivery state of the head station, the dynamic assignment of the IP
address is active by means of "Dynamic Host Configuration Protocol" (DHCP).
However, if DHCP is not active and you do not have access to your fieldbus node
via an IP address, you can enable DHCP via "WAGO Ethernet Settings" in the
Network tab.
WAGO communication cables or WAGO radio-link adapters can be used for data
communication via the serial service interface.
Do not connect Communication Cable when energized!

To prevent damage to the service interface, do not connect or disconnect
750-920 respectively 750-923 Communication Cable when energized! The
fieldbus coupler/controller must be de-energized!
1. Using a WAGO Communication cable 750-920 respectively 750-923,

connect your PC with the service interface of the head station of the
fieldbus node.
2. Start “WAGO Ethernet Settings” program.
3. Click on [Read] to read in and identify the connected fieldbus node.
4. Select the Network tab.
5. Select the option "DHCP" in the field Source.
6. Click on the [Write] button to apply the settings in the fieldbus node.
The fieldbus node then starts with the new IP address assigned via DHCP.
7. Then You can use the [Read] button to read out the currently assigned IP
address.
8. In order to use the IP address permanently, select on "TCP/IP" WBM page

the option “static" in the field Source and apply the settings for “IP
address”, “Subnet mask” and “Gateway” from the currently used settings.
9. Click on the [Write] button to apply the settings.
Manual
Version 1.1.1
8.3.2.2 Enable DHCP via WBM (with existing IP address)
In the delivery state of the head station, the dynamic assignment of the IP
address is active by means of "Dynamic Host Configuration Protocol" (DHCP).
However, if DHCP is not active and you do already have access to your fieldbus
node via an IP address, you can enable DHCP via WBM on "TCP/IP" WBM page.
1. Open the WBM (see chapter: "Configuring via the Web-Based

Management System (WBM)" >> "Open WBM").
2. Change to the WBM page "TCP / IP".
3. Activate the “DHCP“ option to assign a new IP address via DHCP.
4. Confirm the change with the [SUBMIT] button.
5. Select the WBM page "Administration".
6. Click the [SOFTWARE RESET] button to apply the changed setting.
Alternatively, you can restart the fieldbus node.
The fieldbus node then starts with the new IP address assigned via DHCP.
The connection to the browser is interrupted.
7. If you want to call the WBM again, you must use now the changed IP
address.
8. In order to use the IP address permanently, select in the WBM on "TCP/IP"

WBM page the option "IP configuration source: static" (see chapter "Apply
IP address permanently (option "static ")").
9. In order to use the IP address permanently, select on "TCP/IP" WBM page

the option “static" in the field Source and apply the settings for “IP
address”, “Subnet mask” and “Gateway” from the currently used settings.
10. Confirm the change with the [SUBMIT] button.
11. Click the [SOFTWARE RESET] button to apply the changed setting.
Manual
Version 1.1.1
Eine nähere Angabe von Jürgen erhal
8.3.3 Assigning IP Address via “WAGO Ethernet Settings”
Note Software Compatibility!

Refer to the version of the software specified in "Software Compatibility" in the
Technical Data.
This program is used to configure an IP address, to reset the fieldbus

coupler/controller parameters to the factory settings and to restore the Flash File
System in which the WBM pages of the fieldbus coupler/controller are stored.
"WAGO Ethernet Settings" can be used via the serial service interface or via the
ETHERNET interface.
For initial commissioning, however, the way via the serial service interface is
described here, because for access via the ETHERNET interface the currently
assigned IP address must already be known.
WAGO communication cables or WAGO radio-link adapters can be used for data
communication via the serial service interface.

To prevent damage to the service interface, do not connect or disconnect 750-
920 respectively 750-923 Communication Cable when energized! The fieldbus
coupler/controller must be de-energized!
Set the address selection switch to 0 for an IP assignment via software!

Set the address selection switch to “0” to disable the DIP switch.
1. Using a WAGO Communication cable 750-920 respectively 750-923,

connect your PC with the service interface of the head station of the
fieldbus node.
2. Start “WAGO Ethernet Settings” program.
3. Click on [Read] to read in and identify the connected fieldbus node.
4. Select the Network tab.

5. To assign a permanent address, select the option "Static configuration" in
the field Source.
Manual
Version 1.1.1
6. Enter the required IP Address and, if applicable, the address of the subnet
mask and gateway.
7. Click on the [Write] button to apply the settings in the fieldbus node.
8. You can now close "WAGO Ethernet Settings" or make other changes in
the Web-based Management System as required. To open the Web-based
Management System click on the button [Start WBM] on the right side.
Manual
Version 1.1.1
8.3.4 Assigning the IP Address via BootP

A BootP server 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.
Set the address selection switch to 0 for an IP assignment via software!

Set the address selection switch to “0” to disable the DIP switch.
By default, DHCP is active in the delivery state of the head station.
Therefor it is necessary to enable BootP for IP address assignment via BootP,

e. g. via "WAGO Ethernet Settings" or via the WBM (see analog the chapters
"Activate DHCP via "WAGO Ethernet Settings" (without existing IP address)" or
"Activate DHCP via WBM (with existing IP address)").
Then the IP address assignment with BootP takes place automatically via a
BootP server in the network.
If there is no BootP server on your local PC, you can download a BootP server
free of charge from the Internet and install it on your PC.
Assigning IP addresses using a BootP server can be carried out in any Windows
and Linux operating system. Any BootP server may be used.
IP address assignment is not possible via the router!

The IP address is assigned via patch cable, switches or hubs. Addresses cannot
be assigned via routers.
When the BootP protocol is enabled the head station of fieldbus node expects
the BootP server to be permanently available. If there is no BootP server
available after a Power On reset, the network will remain inactive.
In order to use the IP address permanently, change it to “static” (see chapter

"Apply IP address permanently (option "static ")").
Manual
Version 1.1.1
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 or e. g. in “WAGO
Ethernet Settings“ (Network tab, Source “BootP”).
3. To apply the new IP address, use e.g. a hardware reset to restart your
fieldbus node by interrupt the voltage supply for approx. 2 seconds.
4. Restart the fieldbus node.
The fieldbus node then starts with the new IP address assigned via BootP.
5. In order to use the IP address permanently, select in the WBM on "TCP/IP"

WBM page the option "IP configuration source: static" (see chapter "Apply
IP address permanently (option "static ")").
Manual
Version 1.1.1
8.3.4.1 Reasons for Failed IP Address Assignment
• The PC on whom the BootP server is running is not located in the network
as the fieldbus coupler/controller; i.e., the IP addresses do not match.
Example:
Sub net mask: 255.255.255.0
(default value for a fieldbus
coupler/
controller n)
PC‘s IP: 192.168.2.100
fieldbus coupler/controller‘s IP: 192.168.1.200
Due to the sub net mask, the first 3 digits of the IP addresses must match.
• PC and/or head station is/are not linked to the ETHERNET
Manual
Version 1.1.1
8.4 Apply IP address permanently (option “static“)
For permanent address assignment, the IP stored in the EEPROM must be

used!
To apply permanently the new IP address assigned via DHCP or BootP in the
fieldbus coupler/controller, the assigned or desired settings for IP address,
subnet mask and default gateway must be entered on the WBM “TCP/IP” page.
In addition the option "IP configuration source: static" must be activated.
Then, the IP address is stored in the EEPROM and used as static address.
You can enable the option “IP configuration source: static” in the Web-based
Management System.
1. Open the WBM (see chapter: "Configuring in the Web-Based Management

System (WBM)" >> "Open WBM").
2. Select the WBM page "TCP/IP".
3. Enter the assigned or desired settings for IP address, subnet mask and
default gateway in the fields "IP address", "Subnet mask" and "Default
gateway".
4. Enable the option “IP configuration source: "static".
At the same time, the use of the DHCP/BootP server is diabled.
5. Confirm your changes with button [SUBMIT].
6. Select the “Administration” WBM page.
7. Click on the button [Software Reset] at the bottom of the page in order for
the settings to take effect.
Alternatively restart the fieldbus node.
Then the fieldbus node starts with the configurations and the assigned IP
address, which were previously loaded into the EEPROM. The connection
to the browser is interrupted.
8. Now you must use the new IP address, if you want to access again on the
WBM of this fieldbus node via browser.
Manual
Version 1.1.1
8.5 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 PC and the fieldbus node.
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.
More information about LED signaling

The exact description for evaluating the LED signal displayed is available in the
Manual
Version 1.1.1
8.6 Preparing the Flash File System

The flash file system must be prepared in order to use the WBM of the fieldbus
coupler/controller of the fieldbus node 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/controller or it has been destroyed due to an error, you first must initialize
it manually to access it.

To prevent damage to the service interface, do not connect or disconnect 750-
920 respectively 750-923 Communication Cable when energized! The fieldbus
coupler/controller must be de-energized!
Resetting erases data!

Note that resetting 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 node.
2. Connect the communication cable 750-920 or 750-923 respectively the

Bluetooth® Adapter 750-921 to the service interface of the head station of
the fieldbus node and to your computer.
3. Switch on the supply voltage of the fieldbus node.

4. Start the “WAGO Ethernet Settings” program.
Manual
Version 1.1.1
5. In the top menu bar, select [Reset File System] to format the file system
and to extract the WBM pages of the flash file system.
Formatting and extracting is complete when the status window displays

"Resetting the file system successfully".
Restart the Fieldbus node after resetting file system!

Make a restart of the fieldbus node, so that the WBM pages can be displayed
after resetting file system.
Manual
Version 1.1.1
8.7 Synchronizing the System Time

The head station’s system time enables a date and time indication for files in the
flash file system.
System time will be reset when the fieldbus node is de-energized!

The head station 750-362, 750-362/0000-0001 does not have a real-time clock.
For this reason, the current system time will be reset when the fieldbus node is
de-energized!
After switching on the operating voltage, the system time starts at 01/01/2000,
00:00:00 a.m.
At start-up, synchronize the system time with the computer’s current time.
There are two options to synchronize the system time:
• Synchronize the system time using “WAGO Ethernet Settings”
• Set the system time using the Web Based Management System
Synchronize the system time using “WAGO Ethernet Settings”
Do not set time during a WAGO I/O-CHECK communication!

Note that setting the clock during a WAGO I/O-CHECK communication may
cause communication errors. Therefore set the time only if WAGO I/O-CHECK is
not yet started.

Manual
Version 1.1.1

4. Start the “WAGO Ethernet Settings” program.
5. Select the Date and Time tab.
6. Click on the [Apply] button.
Set the system time using the Web-based Management-System
1. Launch a Web browser (e.g., MS Internet Explorer or Mozilla) and enter in

the address bar the IP address you have assigned to your fieldbus node.
2. Click [Enter] to confirm.

The WBM start page is displayed.
3. Select “Clock” in the left navigation bar.
4. Enter your user name and password in the displayed query dialog box
(default: user = "admin", password = "wago" or: user = "user", password =
"user"). The WBM page "Clock" is displayed.
5. Set the current time and date values, as well as the time zone deviation in
the input fields, and select the desired option for the display and Daylight
Saving Time (DST).
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.
Manual
Version 1.1.1
8.8 Restoring Factory Settings

To restore the factory settings, proceed as follows:

4 Start the WAGO-ETHERNET-Settings program.
5. In the top menu bar, select [Factory Settings] 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.1
WAGO I/O System 750 Configuring via the Web-Based Management System (WBM) 107
9 Configuring via the Web-Based Management

System (WBM)
An integrated Web server can be used for configuration and administration of the
device. The HTML pages together, they are referred to as the Web-based
Management System (WBM).
The WBM pages saved internally provide current information about the
configuration and status of the device.
The configuration of the device can be changed via the special configuration
pages. Authentication is required for this.
Also HTML pages created by yourself can be save via the implemented file
system.
After changes to the configuration, a restart may be necessary!

In order for changed configuration settings to take effect, it may be necessary for
you to perform a system restart after your changes. This is then indicated in the
description text on the respective WBM pages.
9.1 WBM User Groups

For authentication, 3 different password-protected user authorization groups are
provided as standard:
Table 32: WBM User Groups

User Group Default Password Access Rights
admin wago Read/write access to all WBM pages as
well as passwords modification and
CODESYS application download, if this
is enabled for CODESYS (WBM page
"Administration"> "Security Settings">
"Enable CODESYS port authentication")
user user Read/write access to all WBM pages,
but no write authorization on WBM-page
"Administration"
guest guest Read only on WBM pages, no access
via (S)FTP.
Manual
Version 1.1.1
108 Configuring via the Web-Based Management System (WBM) WAGO I/O System 750
9.2 Open WBM

1. To open the WBM, launch a Web browser.
2. Enter the IP address of the fieldbus coupler/controller in the address bar.
3. Click [Enter] to confirm.

The start page of WBM loads.
4. Select the link to the desired WBM page in the left navigation bar.
The first time a configuration page is called, a login 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 WBM page is loaded.
6. Make the desired settings.
7. Click [SUBMIT] to confirm your changes or click [UNDO] to discard the

changes.
At the first confirmation via the [SUBMIT] button, a login dialog appears
again. Proceed as described under point 5.
8. To apply the settings, you may have to reboot afterwards if this is indicated
in the description text on the respective WBM page.
You restart the system using WBM page “Administration”, button
[SOFTWARE RESET].
Manual
Version 1.1.1
9.3 WBM Pages

You can access the available WBM pages via the links given in the navigation
bar on the left side.
The integrated configuration pages are following described.
Figure 40: Example for a WBM page structure (simplified representation)
Manual
Version 1.1.1
9.4 Information
The WBM page “Information” contains an overview of all important information
about your fieldbus coupler.
Table 33: WBM Page “Information”

Device details
Entry Default Value (example) Description
Product Fieldbus Coupler Produkt description
description Modbus TCP;
Generation 4 (BootP)
Order number 750-362, 750- Order number
362/0000-0001
Mac address 0030DEXXXXXX 0030DE000006 Hardware MAC address
Firmware kk.ff.bb(rr) 01.01.14(01) Firmware revision number
revision (kk = compatibility, ff = functionality,
bb = bugfix, rr = revision)
Firmware loader kk.ff.bb(rr) 01.03.01(03) Firmware loader revision number
revision (kk = compatibility, ff = functionality,
bb = bugfix, rr = revision)
Serial number ___ „“ Serial number of device
(manufacturer-specific identification
of device)
Serial number ___ „“ „Unique Item Identifier“ (world wide
(UII) unique identification of device)
Active Network Settings

IP address 0.0.0.0 172.29.233.123 IP address,
Type of IP address assignment
Subnet mask 255.255.255.0 255.0.0.0 Subnet mask
Default gateway 0.0.0.0 192.168.2.1 Gateway
Host name 0030DEXXXXXX 0030DE000000 Host name
Domain name ___ ___ Domain name (not assigned here)
Time server 0.0.0.0 0.0.0.0 Address of Time server
DNS server 1 0.0.0.0 0.0.0.0 Address of first DNS server
DNS server 2 0.0.0.0 0.0.0.0 Address of second DNS server
Module Status
State Modbus Disabled Disabled Status of Modbus Watchdog
Watchdog
Error Code 0 10 Error code
Error Argument 0 5 Error argument
Error Description no error Missmatch in Error description
CODESYS IO-
configuration
Manual
Version 1.1.1
9.5 Administration
Use the “Administration” WBM page to set configuration options for basic
administration purposes, such as boot behavior, authentication, and SSL
certificate.
These configuration options are stored in non-volatile memory when the

[SUBMIT] button is pressed. Changes to the configuration options take effect
after the next power-on cycle or software reset.
Changing the passwords requires administrator rights and software reset!

You can only change the passwords as an administrator with the user rights
"admin" and the associated password.
Press the [Software Reset] button to restart the software for the setting changes
to take effect.
Note password restrictions!

The following restriction is applied for passwords:
• Max. 32 characters inclusive special characters.
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 not changed the IP address and performed other settings; you can
restore the connection by refreshing the browser.
Table 34: WBM Page “Administration”

Security Settings
Entry Default Description
Enable password protection to access the
 Web interface
Enable web-server
authentication

Disable password protection to access the
 Web interface
Manual
Version 1.1.1
User Settings
User guest Select user permissions according to the default
user group ( see Chapter “WBM User Groups”).
Enable  The user selected under "User" is not active and
is unable to be used for authentication.

 The user selected under "User" is active and can
be used for authentication.
Password - Enter desired password (max. 32 characters
inclusive special characters).
Confirm Password - Enter desired password again to confirm.
*) The following default groups exist: User: admin Password: wago

User: user Password: user
User: guest Password: guest
SSL Certificates
Entry Button Status Description
(Example)
Select and load the file with the server
certificate and user key for secure Web
server communication (HTTPS protocol)onto
Server certificate
[UPLOAD] NO FILE the device.
incl. private key
The server certificate must be in *pem, *.cer
or *.crt format and contain the private key of
the device.
Select and load the file with the SSL root
Root certificate certificate onto the device.
[UPLOAD] NO FILE
(CA) The root certificate must be in *pem, *.cer or
*.crt format.
Upload and
- Ready Download and install status indicator
installation status
Installs the SSL server and/or root certificate
- [INSTALL] - previously loaded on the device and
replaces the existing SSL certificates.
Downloads the SSL root certificate stored in
- [DOWNLOAD] -
the device to the local PC.
Button Description
[SOFTWARE RESET] Restart the software.
[RESTORE SETTINGS] Reset the device to the delivery status.
Data will be deleted!

All user settings and user-specific files and an existing boot
application (only for controllers) are deleted.
Manual
Version 1.1.1
9.6 System Status

On the WBM "System Status" page, you can collect status information about the
system in log files, save it and make settings for it.
These configuration options are saved in non-volatile memory when the

[SUBMIT] button is pressed.
Changes to the configuration options take effect after the next power-up cycle or
software reset.
You can use the icons to customize the view of the sections with the log entries:
• [+] Expand
• [-] Minimize
• [] Update
Rapid aging of the internal storage medium!

Note, when the log output is activated on the internal file system, excessive log
output leads to faster aging of the storage medium.
In addition, by lowering the log level this is also favored.
Therefore You should only use the log output in a targeted manner
(troubleshooting / support case) or use external / exchangeable storage media (if
supported by the device).
Table 35: WBM Page “System Status”

Device details
Manual
Version 1.1.1
Log storage 80 (0 …100%, 0 = disable)
threshold [%] Defines the limit value for the fill level of the log memory in%.
Network log INFO (INFO, WARNING, ERROR, DEBUG)
level Specifies (together with the "File log level" option) the threshold for
the log outputs on the network.
This setting affects the log messages that are sent to the syslog
server.
File log level INFO (INFO, WARNING, ERROR, DEBUG)
Specifies (together with the "Network log level" option) the threshold
for the log outputs for storage on the file system.
This setting affects the log messages that are stored in log files.
Button Description
[DOWNLOAD] Downloads the saved log files as a single merged file (CSV format).
[DELETE] Deletes the log files stored on the device.
A possibly existing warning regarding the filling level of the log
memory is hereby reset (blink code).
System Log
Time (UTC); - 20210322T073715; Online logbook, shows the most
Severity; notice; recent log entries in chronologically
Facility; user; descending order.
Module; PARAM;
Description Configuration changed. ID = 3
System Load
Current CPU __% 17,3% Shows the current CPU utilization
load in %.
System Memory
Pool Name; - SYSMEM; Shows the current memory usage.
Pool Size; 33554432 The display shows the internal
Memory status of the memory pools in RAM.
Available; 31488620;
Tasks Waiting; 0;
Task Name -
System Tasks
Name; - DevDisc; Displays the current task
Priority; 3; configuration.
Preemptable; no; The display shows the internal
Time Slice; 0; status of the system tasks.
Stack Size; 10240;
Status suspend (event)
Manual
Version 1.1.1
9.7 Clock
On the WBM "Clock" page, you make settings for the internal system time. Enter
the current time and date here and select a time zone deviation, 12h or 24h
display and automatic daylight saving time as required.
At start-up, the system time has to be synchronized with the computer's current
time.
System time will be reset when the controller is de-energized!

The head station 750-362, 750-362/0000-0001 does not have a real-time clock.
For this reason, the current system time will be reset when the controller is de-
energized!
After switching on the operating voltage, the system time starts at 01/01/2000
00:00:00 a.m. and has to synchronize with the computer’s current time.
Use a WAGO RTC module for time synchronization!!

You can use a WAGO 750-640 RTC Module for your node to utilize the actual
encoded time (Real-time – RTC) in your higher-level control system.
Manual
Version 1.1.1
Table 36: WBM Page „Clock“
Clock Settings
Device local time Set current time
00:00:00 08:30:38
(HH:MM:SS)
Device local date Set current date
2000-01-01 2018-07-19
(YYYY-MM-DD)
Device time zone Set time zone offset from the
0:00 +1:00
(+/- HH:MM) Coordinated Universal Time (UTC)
  Enable 24-hour display
24h  Disable 24-hour display
Time display mode
  Enable 12-hour display
12h (AM/PM)  Disable 12-hour display
 Disable manual summer/winter
 time

off  Enable manual summer/winter
time
 Enable automatic Daylight
Saving Time (EU)
(last Sunday in March, clocks
are advanced from 02:00 AM to
 03:00 AM /
 last Sunday in October, clocks
EU
are set back
from 03:00 AM to 02:00 AM)
 Disable automatic Daylight
Saving Time (EU)
Automatic daylight Saving Time (US)
saving time (DST) (second Sunday in March,
clocks are advanced from
 02:00 AM to 03:00 AM /

US first Sunday in November, clocks
are set back
from 02:00 AM to 01:00 AM)
Saving Time (US)
Saving Time (AU)
(first Sunday in October, clocks
 are advanced from 02:00 AM to

AU 03:00 AM /
first Sunday in April, clocks are
set back from 03:00 AM to 02:00
AM)
Saving Time (AU)
Status display fort he current
DST current status not active not active
DST status
Manual
Version 1.1.1
9.8 Miscellaneous
On the Miscellaneous WBM page, you can set configuration options for various
features and compatibility options.
These configuration options are stored in non-volatile memory when the

[SUBMIT] button is pressed. Changes to the configuration options take effect
after the next power-on cycle or software reset.
Table 37: WBM Page “Miscellaneous”

Global Settings
Enables an automatic software reset to be conducted
 when a system error occurs
Autoreset on
fatal error

Disables an automatic software reset to be conducted

when a system error occurs
Automatically set the static IP address enabled.
For this configuration, the fieldbus coupler/
controller uses a statically configured IP address if the
 request via BootP fails. The time until the static IP
BootP request
 address is set is variable and usually takes approx. 90 s
before static IP
With the setting "DHCP" this function has no effect.
Automatically set the static IP address disabled.
 For this configuration, the IP address request via BootP
is repeated in the event of error.
Enables a fixed sampling interval of the local bus and
statically sets the pause time to 14 ms. As a result,
 possibly the sampling interval of the local bus is
extended and more computing power is available for the
Non-adaptive local PLC application.
bus interval

Enables the dynamic sampling interval of the local bus
(default). The pause time between two local bus cycles is
 dynamically adjusted. This shortens the sampling interval
of the local bus and less computing power is available for
the PLC application.
Indicates, that the bus extension (750-627/-628) is
Local bus extension  installed.
installed

 Indicates, that no bus extension is installed.
Manual
Version 1.1.1
9.9 Storage Media

Information about the available storage devices and active drives which are
currently mounted within the file system of the device is given on the “Storage
Media” WBM page.
This page will be refreshed every 5 s.
This size information for the storage devices listed below are specified in units of
1 kB with 1 kB = 1024 Byte.
Table 38: WBM page "Storage Media"

Local Disks
Entry Value (Example) Description
Drive Letter A Directory
Total Size [kB] 1050184 kB Total size of the file system
Used Size [kB] 295560 kB Used memory capacity
Free Size [kB] 754624 kB Free memory capacity
File System FAT File system (File Allocation Table)
9.10 Update
Use the “Update“ WBM page to update the firmware of the device. To do this, the
associated firmware image is first selected from the PC's local file system and
downloaded to the device. Afterwards, the update will be executed and the
device will be restarted automatically.
After the firmware update, the WBM pages will also be updated, self-created
HTML pages or settings will be remained save.
Stop fieldbus application and finish FTP connections before the update !
Please ensure, that the superordinate fieldbus application has been stopped and
possibly existing FTP connections has been finished before starting the update
process. When the software reset is beeing executed, the connection to the web-
based management will be lost and the web-page has to be reloaded.
Table 39: WBM Page “Update“

Firmware Selection / Upload
Entry Button Value Description
(example)
Use this button to select the firmware
Firmware image [UPLOAD] OK image file (*.bin) on your local file system
(PC) and upload this file onto the device.
Verification of Status display for the update.
Update Status - firmware image
is done
Manual
Version 1.1.1
9.11 Ethernet
Use the “Ethernet” WBM page to set the data transfer rate, the MAC address
filter settings and bandwidth limit for each of the two switch ports for data transfer
via Ethernet.
Table 40: WBM Page „Ethernet“

PHY Settings
Entry Default value Description
Enable port  Enable Port X1 or Port X2

 Disable Port X1 or Port X2
Enable auto-  Enable Autonegotiation for Port X1 or Port X2.
negotiation Automatically handling the best possible transmission
 mode and baud rate with the communication partner.
 Enable Autonegotiation for Port X1 or Port X2.
10 MBit Half Duplex 
10 MBit Full Duplex  Use a fixed transmission mode and baud rate for Port X1
100 MBit Half Duplex  or Port X2.
100 MBit Full Duplex 

Enable  Enable Auto-MDI/MDI-X for Port X1 or Port X2
Auto-MDI/MDI-X 
 Disable Auto-MDI/MDI-X for Port X1or Port X2
MDI  Transceiver of Port X1 or Port X2 sends on Tx

wire pair.
MDI-X   Port X1 or Port X2 sends an Rx wire pair.
Manual
Version 1.1.1
MAC Address Filter Settings
Enable filter  Activate MAC address filter.
Depending on the operating mode of the MAC
 address filter (whitelist / blacklist), the subsequently
entered MAC addresses are blocked or permitt.
 Deactivate MAC address filter.
Filter mode  Chose Whitelist.
Whitelist Only the following registered MAC addresses have
 network access to the fieldbus coupler/controller,
others are blocked
 Chose Blacklist.
Blacklist Only the following registered MAC addresses are
 blocked, others have network access to the fieldbus
coupler/controller.
Activate MAC address filter.
The WAGO devices with the MAC address
 00:30:EN:XX:XX:XX always have network access to
the fieldbus coupler/controller, independent of the
other settings of the MAC address filter.
Allow WAGO devices 
Deactivate MAC address filter.
Only devices whose MAC address is entered in the
 list have network access to the fieldbus coupler /
controller.
The settings of the MAC address filter apply.
MAC address 1 00:00:00:00: Filter for the first MAC address (hexadecimal).
00:00
MAC address 2 00:00:00:00: Filter for the second MAC address (hexadecimal).
00:00
MAC address 3 00:00:00:00: Filter for the third MAC address (hexadecimal).
00:00
MAC address 4 00:00:00:00: Filter for the fourth MAC address (hexadecimal).
00:00
MAC address 5 00:00:00:00: Filter for the fifth MAC address (hexadecimal).
00:00
Manual
Version 1.1.1
Switch Settings
 Enable “Fast Aging”
"Fast Aging" ensures that the cache for the MAC
addresses is cleared faster in the switch. This may
be required if a redundancy system (e.g., using a Jet-
Enable fast aging  Ring network or comparable technology) needs to be
set up.
 Disable “Fast Aging”.
The time to discard the cache entries is five minutes.
 Enable port mirroring
Port Mirroring is used for network diagnostics.
Enable port mirroring  Packets are mirrored from one port (mirror port) to
another (sniffer port).
 Disable port mirroring
Maximum packet size of a protocol, which can be
Ethernet MTU 1500 transferred without fragmentation ("Maximum
Transmission Unit" - MTU).
Port
1 2 internal
Input data rate limit The input limit rate limits network traffic when receiving.
No limit The rate is indicated in megabits or kilobits per second. If
the limit is exceeded, packets are lost.
Output data rate limit The output limit rate limits network traffic when sending.
No limit The rate is indicated in megabits or kilobits per second. If
the limit is exceeded, packets are lost.
 Activate broadcast storm protection. The maximum
Enable broadcast number of incoming broadcast telegrams is limited
storm protection
  and packets affected by the limitation are discarded.
 Broadcast storm protection disabled.
Sniffer Port   Select the sniffer port the mirror port should be mirrored to.
Select the mirror port which should be mirrored to the
Mirror Port    sniffer port.
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., 1452 for VPN) for ETHERNET
communication and the packets must be fragmented.
Setting the value is independent of the transmission mode selected.
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.
Manual
Version 1.1.1
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.1
9.12 Protocols
Use the “Protocols” WBM page to enable or disable ports for the services
available.
Close any ports and services that you do not need!

Unauthorized persons may gain access to your automation system through open
ports.
To reduce the risk of cyber attacks and, thus, enhance your cyber security, close
all ports and services in the control components (in particular Port 6626 for
WAGO I/O-CHECK, Port 2455 for CODESYS 2 and Port 11740 for e!COCKPIT)
not required by your application.
Only open ports and services during commissioning and/or configuration.
Table 41: WBM page „Protocols“

Protocol Settings
Entry Default Value Description
 Enable "File Transfer Protocol"
FTP (Port 21) 
 Disable "File Transfer Protocol"
 Enable "SSH File Transfer Protocol"
SFTP (Port 22) 
 Disable "SSH File Transfer Protocol"
80 Port number setting for HTTP (1 … 65535)
HTTP (Port __ )
 Disable "Hypertext Transfer Protocol"
  Enable “Hypertext Transfer Protocol over SSL-
encrypted connection”
 Disable “Hypertext Transfer Protocol over SSL-
HTTPS (Port 443)  encrypted connection”
 Enable "File Transfer Protocol"
 Enable "Simple Network Time Protocol"
SNTP (Port 123) 
 Disable "Simple Network Time Protocol"
 Enable "Simple Network Management Protocol"
SNMP (Port 161, 162) 
 Disable "Simple Network Management Protocol"
 Enable Modbus-UDP protocol
Modbus UDP (Port 502) 
 Disable Modbus-UDP protocol
 Enable Modbus-TCP protocol
Modbus TCP (Port 502) 
 Disable Modbus-TCP protocol
WAGO service protocol  Enable WAGO services
(Port 6626)

 Disable WAGO services
 Enable Syslog protocol (via UDP)
Syslog UDP (Port 514) 
 Disable Syslog protocol (via UDP)
Manual
Version 1.1.1
9.13 SNMP
On the HTML pages „SNMP“, you can perform the settings for the Simple
Network Management Protocol (SNMP v1/v2c and v3).
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 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.
Enable port 161 and 162 to use SNMP!

Enable ports 161 and 162 in the WBM in menu “port”, so that the fieldbus coupler
can be reached via SNMP. The port numbers cannot be modified.
Modify parameter via WBM or SNMP objects!

However, parameters that can be set on the WBM pages can also be changed
directly by the appropriate SNMP objects.
Additional information for SNMP, the Management Information Base (MIB) and
traps (event messages via SNMP) may be obtained from section “Fieldbus
Communication” > … > “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 coupler.
Manual
Version 1.1.1
9.13.1 SNMP v1/v2c

The SNMP version 1/2c represents a community message exchange. The
community name of the network community must thereby be specified.
Table 42: WBM Page “SNMP v1/v2”

SNMP Settings
Entry Value (Default) Description
FC Modbus TCP; Device description (sysDescription)
Description G4 (BootP) 750-362,
750-362/0000-0001
Physical location LOCAL Location of device (sysLocation)
Contact address support@wago.com E-mail contact address (sysContact)
SNMP v1/v2c Manager Settings

 Activating SNMP Version 1/2c
Enable protocol 
 Deactivating SNMP-Version 1/2c
Local community
public used community name
name
SNMP v1/v2c Trap Receiver 1 Settings

Trap receiver 0.0.0.0 IP address of 1. used SNMP manager
Community name public 1. Community name of the network community used
v1  v1  v2  Activating Traps Version 1
Trap version
v2  v1  v2  Activating Traps Version 2
SNMP v1/v2c Trap Receiver 2 Settings

Trap receiver 0.0.0.0 IP address of 2. used SNMP manager
Community name public 2. Community name of the network community used
v1  v1  v2  Activating Traps Version 1
Trap version
v2  v1  v2  Activating Traps Version 2
Manual
Version 1.1.1
9.13.2 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 fieldbus
coupler.
In SNMP v3, user data from SNMP messages can also be transmitted in
encoded form. This is why SNMP v3 is often used in safety-related networks.
Via this WBM page "SNMP V3" two independent SNMPV3 users can be defined
and activated (User 1 and User 2).
Table 43: WBM Page “SNMP V3”

SNMP v3 User 1 / 2 Settings
Entry Value Description
(Example)
 Activating user 1 or 2
Enable user activate 
 Deactivating user 1 or 2
No encryption of the
None  MD5  SHA1 
authentication
None 
Encryption of the
Authentication type MD5  None  MD5  SHA1 
authentication with MD5
SHA1  Encryption of the
None  MD5  SHA1 
authentication with SHA1
Enter the name, if the “Authentication type” MD5 or SHA1
Authentication name Security Name
has been selected
Authentication key Authentification Enter the password with at least 8 characters, if
(min. 8 characters) Key “Authentication type” MD5 or SHA1 has been selected
Privacy enable  Activate the DES encryption of the data
(DES)

 Deactivate the DES encryption of the data
Privacy key Enter the password of at least 8 characters in the
Privacy Key
(min. 8 characters) encryption with DES
Enable v3  Activate the notification traps of the SNMP version 3
notification/trap   Deactivate the notification traps of the SNMP version
enable 3
Notification receiver
192.168.1.10 IP address of the notification manager
(IP address)
Manual
Version 1.1.1
9.14 SNTP
On the WBM page “SNTP”, you can perform the settings for the “Simple Network
Time Protocol”.
The SNTP client supports configuration of static time servers. Two additional
servers may be assigned by dynamic network configuration (e. g. DHCP or
BootP). The selection of the active time server used to synchronize the current
time is done automatically by the SNTP client. The SNTP client queries all time
servers listed below and determines the most precise server to synchronize the
device clock with. This takes into account whether the respective time server can
be reached and how short the transmission distance between the time server and
the SNTP client is.
Table 44: WBM Page “SNTP”

SNMP Settings
Display the protocol status.
Protocol status enabled „enabled“ SNTP protocol ist activated.
„disabled“ SNTP protocol ist deactivated.
Hostname or IP address of the active time server,
Active time server de.pool.ntp.org
which is currently used to synchronize the time.
SNTP Client Settings

Server update
Polling interval for sychronizing the device clock with
interval [s] 3600
the active time server.
(60 … 65535 s)
Host name or IP address of the first user-defined time
First time server de.pool.ntp.org
server.
Host name or IP address of the second user-defined
Second time server 0.0.0.0
time server.
Additional time - List of up to 2 time servers dynamically allocated via
servers - BootP or DHCP.
Manual
Version 1.1.1
9.15 TCP/IP
You can configure network addressing and network identification on the “TCP/IP”
WBM page.
Set the DIP switch to “0” and enable static IP configuration source!
Before you change parameters on this page, set the DIP switch to value “0” and
enable the option “IP configuration source static”!
If these conditions are not met, the DIP switch settings are applied instead.
Table 45: WBM page „TCP/IP“

Network Settings (non-volatile)
Entry Default Value Value Description
(Example)
 Activate “Bootstrap Protocol“.
 BootP 
 Deactivate “Bootstrap Protocol“.
 Activate “Dynamic Host
Configuration Protocol“.
IP configuration  DHCP 
source  Deactivate “Dynamic Host
Configuration Protocol“
 Use IP address from EEPROM.
 static   Do not use IP address from
EEPROM.
IP address 0.0.0.0 192.168.1.180 Enter IP address.
Subnet mask 255.255.255.0 255.255.255.0 Enter subnet mask.
Default gateway 0.0.0.0 0.0.0.0 Enter gateway.
Host name 0030DEXXXX 0030DE000000 Enter host name.
XX
Domain name localdomain.co Enter domain name.
m
DNS server 1 0.0.0.0 0.0.0.0 Enter IP address of the first DNS server.
DNS server 2 0.0.0.0 0.0.0.0 Enter optional IP address of the second
DNS server.
DIP switch base IP 192.168.1 192.168.5 Network address for the configuration of
address the IP address with DIP switch.
Syslog UDP server 0.0.0.0 192.168.1.96 Host name or IP address of the Syslog
UDP server
IP Fragment TTL [s]
60 60 Life of a packet (Time to Live).
(max.255)
Manual
Version 1.1.1
9.16 Modbus
Use the “Modbus” WBM page to specify the settings for the Modbus protocol.
Table 46: WBM page “MODBUS”

Modbus UDP Multicast Address Setup
Enable multicast  Enable Multicast for Modbus UDP transmission.
addressing In addition to its own IP address, the fieldbus coupler
receives Modbus commands for the following registered
 MCAST addresses.
Multicast for Modbus UDP transmission is not enabled.
 The fieldbus coupler receives Modbus commands only
for the own IP address.
Do not reply to The reply to Modbus UDP multicast messages is
 deactivated.
Modbus UDP 
multicast The reply to Modbus UDP multicast messages is
messages  activated.
MCAST address Multicast address 1... 5, for the multicast will be enabled.
1 ... 5: 0.0.0.0 The valid address range is shown in the WBM.
Multiple assigned addresses are not valid.
Multicast function only active with a valid MCAST address!

The multicast function is only active with a valid MCAST address.
If you activate the "Enable Multicast" function, it is therefore necessary to
always enter an MCAST address that is not equal to 0.0.0.0. Otherwise, clicking
on the [SUBMIT] button automatically deactivates the function again.
If the "Enable Multicast" function is already enabled with valid addresses, then
you can no longer describe these MCAST address fields with invalid addresses,
because when clicking on the [SUBMIT] button, they are reset to the previously
valid addresses. The function "Enable Multicast" remains active.
Modbus Configuration Registers

Range Enabled
0x1029 – 0x1037   Enable Modbus configuration register range.
0x2040 – 0x2043   Disable Modbus configuration register range.
Manual
Version 1.1.1
Connection Watchdog
Connection timeout value 600 Monitoring period for TCP links.
(x 100 ms) After the completion of this period without any
subsequent data traffic, the TCP connection is
closed.
Modbus Watchdog
Status of Modbus watchdog disabled “disabled“ – Watchdog is disabled
“enabled [running]“ – Watchdog is activated,
Timeout monitoring is running
“enabled [expired]“ – Watchdog is activated,
Timeout occured
Watchdog type Standard  The watchdog can only be activated for the first time
by writing to register 0x1001 or 0x1003.
Alternative  The watchdog is activated for the first time with each
function code that is enabled in the coding mask
(watchdog trigger mask).
Watchdog timeout value 100 Monitoring period for Modbus links. After the
(x 100 ms) completion of this period without receiving a Modbus
telegram, the physical outputs are set to "0".
Close modbus socket after   The Modbus TCP connection remains
watchdog timeout opened when the watchdog timeout
has expired.
 The Modbus TCP connection is closed
when the watchdog timeout has expired.
Watchdog trigger mask 0xFFFF Coding mask for certain Modbus telegrams (Function
(FC1 to FC16) Code FC1 ... FC16)
Watchdog trigger mask 0xFFFF Coding mask for certain Modbus telegrams (Function
(FC17 to FC32) Code FC17 ... FC32)
Modbus Keepalive Timer Setup

Enable keepalive timer   The function Keepalive for Modbus-
TCP connection is disabled.
 The function Keepalive for Modbus-
TCP connection is enabled.
Connection idle time [s] 100 Maximum time in [s] that the Modbus-TCP
connection may be inactive before the Modbus
server starts sending keepalive requests (probes).
Probe interval [s] 20 Interval in [s] with which the Modbus server sends
keepalive requests (probes).
Number of probes: 5 Maximum number of unanswered keepalive requests
(probes) before the Modbus server closes the
connection.
Manual
Version 1.1.1
Modbus Miscellaneous
Priority class for Modbus- 0 Priority value (DSCP in IPv4-ToS) for sending
UDP (TOS/DCSP) Modbus packets.
Response delay for 0 Delay time in [ms] for sending Modubus TCP
Modbus-TCP [ms] response telegrams.
Manual
Version 1.1.1
9.17 Modbus Mapping

The WBM page “Modbus Mapping“ contains an overview of the current
Assignment of the Modbus registers for the I/O modules plugged into the local
bus as well as the general division of the register areas.
Table 47: WBM page “Modbus Mapping”

I/O Mapping
Modbus Register [word addresses]
I/O Module 1…n 1 Position of the I/O module on the local
bus, starting with 1 behind the front-end
station
Order Number 750-XXX 750-4xx WAGO item number of the I/O module
Input (RO) - 2.0 - 2.7 Address of the input data in format
<SR>[.<SO>] - <ER>[.<EO>], with:
<SR> = Start register address
<ER> = End register address
<SO> = Start bit offset inside the
start register
<EO> = End bit offset inside the
end register
The bit offset is only specified for digital
I/O modules
output (WO) - 2.0 - 2.7 Address of the output data in format
<SR>[.<SO>] - <ER>[.<EO>], with:
start register
end register
I/O modules
output (RW) - 514.0 - 514.7 Address of the read back output data in
format
<SR>[.<SO>] - <ER>[.<EO>], with:
start register
end register
I/O modules
I/O access - RO Read/write rights on the I/O module:
RO = Read only,
RW = Read and write
Manual
Version 1.1.1
Modbus Coils [bit addresses]
I/O Module 1…n 2 Position of the digital I/O module on the
local bus, starting with 1 behind the front-
end station
Order Number 750-XXX 750-5xx WAGO item number of the digital I/O
module
Input (RO) - 0-7 Bit address of the digital input data in
format
[<SO>] – [<EO>], with:
<SO> = Start bit offset
<EO> = End bit offset
output (WO) - 0-7 Bit address of the digital output data in
format
[<SO>] – [<EO>], with:
output (RW) - 512 - 519 Bit address of the read back digital output
data in format
[<SO>] – [<EO>], with:
I/O access - RW Read/write rights on the I/O module:
RO = Read only,
RW = Read and write
General Modbus Mapping

Input Register (FC3, FC4, FC23)
Modbus 0xXXXX – 0x0000 – 0x00FF Register address area of the associated
address 0xYYYY input data register
Description - physical input data Description of the content for the specified
register address range
Output Register (FC6, FC7, FC22, FC23)

Modbus 0xXXXX – 0x0000 – 0x00FF Register address area of the associated
address 0xYYYY output data register
Description - physical output Description of the content for the specified
data register address range
Digital Input (FC1, FC2)

Modbus 0xXXXX – 0x0000 – 0x01FF Coil address area of the associated digital
address 0xYYYY input data register
Description - physical input data Description of the content for the specified
coil address range
Manual
Version 1.1.1
Digital Output (FC5, FC15)
Modbus 0xXXXX – 0x0000 – 0x01FF Coil address area of the associated digital
address 0xYYYY output data register
Description - physical output Description of the content for the specified
data coil address range
Manual
Version 1.1.1
9.18 I/O Config

Click the link “I/O config” to view the number of modules that are connected to
your hardware.
The data in the second line are not relevant for the present fieldbus coupler,
because no I/O configuration will be load onto devices which have no runtime
system (PLC). Therefore you always find the value “0” for the number of modules
in the I/O configuration.
Table 48: WBM page „I/O Data“

Configuration summary
Number of modules on terminal bus 6 Number of I/O modules (hardware)
Number of modules in I/O 0 Number of I/O modules in the
configuration I/O configuration (not relevant).
Button Description
With this button, the current status of the I/O configuration on
[SAVE CONFIG]
the local bus is read in, displayed and stored on the device.
I/O Mapping
Position 1 Position of the I/O module in the hardware
Module 750-5xx Product number of the integrated I/O module
M001Ch1 M = module, 001 = position 1, Ch1 = channel 1
M001Ch2 M = module, 002 = position 2, Ch2 = channel 2
Type 8DO I/O module type, e.g. 8DO (8 Channel Digital Output Module)
Assigned Fieldbus 1 Mapping via fieldbus 1

Fieldbus
Manual
Version 1.1.1
136 Diagnostics WAGO I/O System 750
10 Diagnostics
10.1 LED Signaling
For on-site diagnostics, the fieldbus coupler has several LEDs that indicate the
operational status of the fieldbus coupler or the entire node (see following figure).
Figure 41: Display Elements
The diagnostics displays and their significance are explained in detail in the
following section.
The LEDs are assigned in groups to the various diagnostics areas:
Table 49: LED Assignment for Diagnostics

Diagnostics area LEDs
• LINK ACT Port 1
• LINK ACT Port 2
Fieldbus status
• MS
• NS
Node status • I/O
Manual
Version 1.1.1
WAGO I/O System 750 Diagnostics 137
10.1.1 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 used to
display the status of the system and the fieldbus connections.
Table 50: Fieldbus Diagnostics – Solution in Event of Error

LED Meaning Solution
Status
LINK ACT 1, 2
The fieldbus node is connected to the
green -
physical network.
green The fieldbus node sends and receives
-
flashing ETHERNET telegrams
The fieldbus node is not connected to
off 1. Check the fieldbus cable.
the physical network.
MS
green Normal operation -
1. Assign an IP address to the device (see
chapter "Commissioning").
2. If the status is still displayed, check
whether there is an Ethernet connection
(link on port X1 or X2) *
3. If the status is still displayed, check
whether, with dynamic IP address
green The system is not yet configures assignment, whether a BootP or DHCP
flashing (e.g no IP address assigned). server is available and accessible in the
network.
* If there is no link on both ports X1 and
X2, no IP address is assigned to the
network interface. It is therefore
considered "not configured" even if an
IP address was assigned in the device
settings.
1. Restart the device by turning the power
The system indicates a not supply off and on again.
red
remediable error 2. If the error still exists, please contact
the I/O support.
1. Check the display of the I/O LED (see
chapter "Evaluating Node Status – I/O
red The system indicates a remediable LED (Blink Code Table”).
flashing error 2. If the error cannot be localized via the
status of the I/O LED, please contact
the I/O support.
Manual
Version 1.1.1
off No system supply voltage 1. Check the supply voltage.
NS
At least one Modbus TCP connection
green -
is developed.
green
No Modbus TCP connection. -
flashing
The system indicates a double IP-
red 1. Use an IP address that is not used yet.
address in the network
At least one Modbus TCP connection 1. Restart the device by turning the power
red
announced a Timeout, where the supply off and on again.
flashing
controller functions as target. 2. Develop a new connection.
1. Assign to the system an IP address by
No IP address is assigned to the
off BootP, DHCP or the Ethernet Settings
system.
tool.
Manual
Version 1.1.1
10.1.2 Evaluating Node Status – I/O LED (Blink Code Table)

The communication status between fieldbus coupler/controller and the I/O
modules is indicated by the I/O LED.
Table 51: Node Status Diagnostics – Solution in Event of Error

LED Status Meaning Solution
I/O
green The fieldbus node is operating correctly. Normal operation.
Start of the firmware.
orange
1 … 2 seconds of rapid flashing indicates -
flashing
start-up.
Fieldbus coupler/controller hardware Replace the fieldbus coupler/controller.
red
defect
Flashing with approx. 10 Hz indicates the Note the following flashing sequence.
red
initialization of the local bus or a local bus
flashing
error.
Evaluate the flashing sequences based
Up to three successive flashing
red on the following blink code table.
sequences indicate local bus errors.
cyclical The blinking indicates an error message
There are short intervals between the
flashing comprised of an error code and error
sequences.
argument.
No data cycle on the local bus. The fieldbus coupler/controller supply is
off
off.
Device boot-up occurs after turning on the power supply. The I/O LED flashes
orange.
Then the local bus is initialized. This is indicated by flashing red at 10 Hz for
1 … 2 seconds.
After a trouble-free initialization, 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 flashing
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.1
Figure 42: Node Status – I/O LED Signaling
Figure 43: Error Message Coding
Example of a module error:
• The I/O LED starts the error display with the first flashing sequence
(approx. 10 Hz).
• After the first break, the second flashing 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 flashing sequence starts (approx. 1 Hz):
The I/O LED blinks twelve times.
Manual
Version 1.1.1
Error argument 12 means that the local 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.1
Table 52: 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
1. Turn off the power supply of the node.
internal buffer
2. Reduce the number of I/O modules.
1 memory for the
3. Turn on again the power supply of the node.
attached I/O
4. If the error persists, replace the head station.
modules.
1. Determine the faulty I/O module. First turn off the power
supply of the node.
2. Plug the end module into the middle of the node.
4. - LED continues to flash? -
Turn off the power supply of the node and plug the end
module into the middle of the first half of the node (toward
the head station).
I/O module(s) with - LED not flashing? -
2 Turn off the power supply of the node and plug the end
unknown data type
module into the middle of the second half of the node
(away from the head station).
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. Contact I/O support and inquire about a firmware update
for the head station.
Invalid check sum in 1. Turn off the power supply of the node.
3 the parameter area 2. Replace the head station.
of the head station. 3. Turn on again the power supply of the node.

Fault when writing in
4 2. Replace the head station.
the serial EEPROM.

Fault when reading
the serial EEPROM
The I/O module

configuration after
AUTORESET differs
from the 1. Restart the head station by turning the power supply off
6
configuration and on.
determined the last
time the head station
was powered up.
Invalid hardware- 1. Turn off the power supply of the node.

7 firmware 2. Replace the head station.
combination. 3. Turn on again the power supply of the node.

Timeout during serial
EEPROM access.
Manual
Version 1.1.1
Table 52: Blink code- table for the I/O LED signaling, error code 1
Error code 1: "Hardware and configuration error"
Argument

Head station
initialization error
10 ... 13 not used

Maximum number of
2. Reduce the number of corresponding modules to a valid
14 gateway or mailbox
number.
modules exceeded
Firmware loader was 1. Execute the last firmware update again.

15
loaded from backup. 2. If the error persists, contact I/O support.
Firmware was loaded 1. Execute the last firmware update again.

16
from backup. 2. If the error persists, contact I/O support.
Table 53: Blink Code Table for the I/O LED Signaling, Error Code 2
Error Code 2: „Process image exceeded“
Argument
1 Not used -
Maximum process 1. Turn off the power supply of the node.

2 image size 2. Reduce number of I/O modules.
exceeded 3. Turn on again the power supply of the node.
Process image
3 2. Remove unsupported I/O modules.
generation error
Configuration error
1. Check the configuration settings on the WBM page
4 detected for output
“System Status“.
of log files
Manual
Version 1.1.1
Error Code 3: „Protocoll error, local bus“
Argument
-- Are there power supply modules with the bus power supply
(750-613) in the node? ---
1. Check that these I/O modules are supplied correctly with
power.
2. Determine this by the state of the associated status LEDs.
--- Are all I/O modules connected correctly or are there
any 750-613 I/O modules in the node? ---
supply of the node.
Local bus 6. - LED continues to flash? -
communication Turn off the power supply of the node and plug the end
- defective, incorrect module into the middle of the first half of the node (toward
module not the head station).
identifiable - LED not flashing? -
10. If there is only one I/O module left on the head station and
the LED is flashing, either this I/O module or the head
station is defective.
11. Replace the faulty component.
Manual
Version 1.1.1
Error Code 4: „Physical error, local bus“
Argument
2. Plug in an I/O module with process data behind the head
station.
4. Observe the error argument signaled.
5. --- Is no error argument indicated in the I/O LED?---
Replace the head station.
--- Is an error argument indicated by the I/O LED? ---
supply of the node.
Local bus data
9. - LED continues to flash? -
transmission error or
- interruption of the
module into the middle of the first half of the node (toward
local bus at the head
the head station).
station
- LED not flashing? -
13. If there is only one I/O module left on the head station and
the LED is flashing, either this I/O module or the head
station is defective.
14. Replace the faulty component.
Interruption of the 1. Turn off the power supply for the node.
local bus behind the 2. Replace the (n+1) I/O module with process data or reduce
n*
nth I/O module with the number of I/O modules until the (n+1) I/O module.
process data. 3. Turn the power supply on.
* 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)
Error Code 5: „Initialization error, local bus“
Argument
Error in register 1. Turn off the power supply for the node.
communication 2. Replace the (n+1) I/O module with process data or reduce
n*
during local bus the number of I/O modules until the (n+1) I/O module.
initialization 3. Turn the power supply on.
* 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.1
Error Code 6: " Configuration error, node configuration"
Argument
1 Invalid MAC ID 2. Replace the head station.
1. Restart the head station by turning the power supply off and
Ethernet Hardware
2 on again.
2. If the error still exists, replace the head station.
TCP/IP initialization
3 on again.
error
Network configuration 1. Check the settings of DHCP/BootP server or if a static IP
4
error (no IP Address) address is used.
Application protocol
5 on again.
Maximum process
6 2. Reduce number of I/O modules.
image size exceeded
1. Change configuration. Use another IP address, which is not
Double IP address in yet present in network.
7
network 2. Restart the head station by turning the power supply off and
on again.

2. Reduce number of I/O modules.
Error when building
8 3. Restart the head station by turning the power supply off and
the process image
on again.
Error when mapping

9 the I/O modules to a 1. Check the file „io_config.xml“ on the head station.
fieldbus
Error Code 7: „Not supported I/O module“
Argument
1. Turn off the power supply for the node.
First not supported
2. Replace the (n+1) I/O module with process data or reduce
n I/O module at
the number of I/O modules until the (n+1) I/O module.
position n
3. Turn the power supply on.
Table 59: Blink Code Table for the I/O LED Signaling, Error Code 8 … 11
Error Code 8 … 11: - not used -
Argument
- Not used -
Manual
Version 1.1.1
Table 60: Blink code table for I/O LED signaling, error code 12
Error code 12 “System Error”
Error Error description Solution
Argument
1. Restart the fieldbus node by turning the power supply
General error of the
1 off and on again.
operating system
3. If the error still exists, please contact the I/O Support.
1. Reset the file system using “WAGO Ethernet Settings“,
button [Reset File System] in the menu above.
General error of the file
2 2. Restart the fieldbus node by turning the power supply
system
off and on again.
3. If the error still exists, please contact the I/O Support.
1. Reduce number of BACnet objects.
3 Insufficient RAM memory
2. Restart the access function.
Error code 13 – not used -
Argument
- Not used -
Error code 14 – not used -
Argument
- Not used -
Manual
Version 1.1.1
Table 63: Blink code - table for the I/O LED signaling, error code 15
Error code 15: "System meldungen"
Argument
Configuration error
1. Check the configuration settings on the WBM page
1 detected for the output of
"System Status".
the log files
Configured threshold
1. Delete the log memory or increase the threshold value
("Log storage threshold")
2 setting (“Log storage threshold”) on the WBM page
exceeded for the log
“System Status”.
storage
1. Close the log files that are opened via (S)FTP.

2. If you are using an external memory card as a log
Error while accessing the medium, remove the write protection.
3
log storage medium 3. When using an external memory card as the log
medium, check whether the error also occurs with a
different memory card.
1. Check whether the configured IP address is valid and

Error while sending can be reached (within the subnet).
4 messages to the syslog 2. Check whether the configured host name of the
server syslog server can be resolved (valid DNS
configuration).
1. Close the log files that are opened via (S)FTP.

2. If you are using an external memory card as a log
Error while accessing the medium, remove the write protection.
5
log files 3. When using an external memory card as the log
medium, check whether the error also occurs with a
different memory card.
Manual
Version 1.1.1
10.2 Fault Behavior

10.2.1 Fieldbus Failure
Irrespective of the fieldbus protocol used, faults on the ETHERNET bus can lead
to sporadic or permanent interruptions in the fieldbus communication.
This can show up e.g. through loss of telegrams, retransmissions or through a

complete link failure.
A fieldbus and thus a connection failure occurs if the set time-out time of the
watchdog has elapsed without being triggered by the higher-level controller.
The Modbus Watchdog monitors the Modbus communication running via the
Modbus protocol. If the Modbus watchdog has been configured and activated, a
fieldbus failure is indicated by the red I/O LED lighting up. All subsequent
Modbus TCP/IP requests are answered with the exception code 0x0004 (Slave
Device Failure).
Further Information
For detailed information on the Watchdog see Chapter "Modbus Functions" >…>
"Modbus Watchdog”.
10.2.2 Local Bus Failure

I/O LED indicates a local bus failure.
When a local bus failure occurs, the head station generates an error message
(error code and error argument) via the red-flashing I/O LED (see chapter
"Diagnostics" => "Evaluating Node Status - I/O LED (Blink Code Table)").
If the local bus completely fails, output modules switch to defined states, e.g.
"Off" or "0 V".
Example:
A fieldbus node consists of head station, five I/O modules with process data and
the end module.
The output of one digital output module is activated.
If the end module is removed of the fieldbus node during operation, the local bus
is interrupted. The output of the digital output module is automatically
deactivated and the I/O LED flashes red and indicates with it error message 4/5.
Manual
Version 1.1.1
The flashing code table provides for error code 4: "Physical error, local bus" with
error argument 5: "Interruption of the local bus behind the nth I/O module with
process data”.
If the end module is re-inserted into the fieldbus node, the local bus will restart
after a few seconds. After the initialization blink code is completely, the I/O LED
lights up again in a steady green and the transmission of the process data is
resumed. Also the output of the digital output module is re-activated.
If the local bus error is caused by a defective module, it must be replaced, as

described in the blink code table for error code 4 under "Solution".
Manual
Version 1.1.1
WAGO I/O System 750 Fieldbus Communication 151
11 Fieldbus Communication
Fieldbus communication between master application and a WAGO fieldbus
coupler/controller based on the ETHERNET standard normally occurs via a
fieldbus-specific application protocol.
Depending on the application, this can be e.g., MODBUS TCP/UDP, EtherNet/IP,

BACnet/IP, KNXnet/IP, PROFINET, sercos 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 64: 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.1
152 Fieldbus Communication WAGO I/O System 750
IP Addresses
To allow communication over the network each fieldbus node requires a 32 bit
Internet address (IP address).
IP Address must be unique!

For error free operation, the IP address must be unique within the network.
The same IP address may not be assigned twice.
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 65: Network Class A

e. g. 101 . 16 . 232 . 22
01100101 00010000 11101000 00010110
0 Net ID Host ID
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 66: Network Class B

e. g. 181 . 16 . 232 . 22
10110101 00010000 11101000 00010110
10 Net ID Host ID
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 67: Network Class C

e. g. 201 . 16 . 232 . 22
11000101 00010000 11101000 00010110
110 Net ID Host ID
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.1
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 68: Key Data Class A, B and C

Network Class Address range of Possible number of
the subnetwork Networks Hosts per
Network
Class A 0.XXX.XXX.XXX ... 128 Approx. 16 Million
127.XXX.XXX.XXX (27) (224)
Class B 128.000.XXX.XXX ... Approx. 16 Thousand Ca. 65 Thousand
191.255.XXX.XXX (214) (216)
Class C 192.000.000.XXX ... Approx. 2 Million 254
223.255.255.XXX (221) (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.
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).
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
dependent upon the number of subnets to be addressed and the number of
subscribers per subnet.
Manual
Version 1.1.1
Table 69: Example: Class B Address with Field for Subnet IDs
1 8 16 24 32
1 0 ... Network ID Subnet ID 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 70: Subnet Mask for Class A Network
255 .0 .0 .0
• Class B Subnet mask:

Table 71: Subnet Mask for Class B Network
255 .255 .0 .0
• Class C Subnet mask:

Table 72: Subnet Mask for Class C Network
255 .255 .255 .0
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 subnet mask. Only then the node
checks the node number and, if it corresponds, delivers the entire packet frame.
Table 73: Example for an IP Address from a Class B Network

IP address 172.16.233.200 '10101100 00010000 11101001 11001000'
Subnet mask 255.255.255.128 '11111111 11111111 11111111 10000000'
Net ID 172.16.0.0 '10101100 00010000 00000000 00000000'
Subnet ID 0.0.233.128 '00000000 00000000 11101001 10000000'
Host ID 0.0.0.72 '00000000 00000000 00000000 01001000'
Manual
Version 1.1.1
Specification of the network mask necessary!

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.
To communicate directly with each other, host and gateway must be on the same
subnet, that means the network ID must be the same.
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
Manual
Version 1.1.1
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.
11.1.1.2 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
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.
11.1.1.3 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.1
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 head station of the fieldbus node in a TCP/IP network.
The BootP protocol can be enabled in the WBM on "TCP/IP" WBM page (the
option "DHCP" is enabled by default).
The protocol communication consists of a client request from the head station
and a response from the BootP server. If no BootP server is available, in the
default configuration the head station will periodically send client requests at
irregular intervals until a server responds.
The protocol sends a broadcast request on port 67 (BootP server) containing the
hardware address (MAC ID) of the head station. The BootP server receives the
message. It contains a database in which MAC ID and IP addresses are
assigned to one another. If the MAC address is found, a broadcast response is
transmitted via the network. The head station “listens” at the specified Port 68 for
the response of the BootP server. Incoming packets contain information such as
the IP address and the MAC address of the head station. A head station
recognizes by the MAC address whether the message is intended for it and, if it
matches, transfers the sent IP address to its network interface.
In contrast to DHCP, the head station keeps the IP address with BootP, as long
as it is not switched off. This means that the head station can only receive a new
IP address after the next power on reset (or a software reset).
IP addresses can be assigned via BootP under Windows and Linux!

You can use BootP to assign an IP address under the Windows and Linux
operating systems.
More information about IP address assigning with BootP

The process for assigning addresses using BootP is described in detail in the
section “Commissioning”.
The head station supports the following options in addition to the default “IP
address” option:
Manual
Version 1.1.1
Table 74: 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.
[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.
[OPT12] Host name The name of the host is the unique name of a computer in a
network. The host name can contain up to 32 characters.
[OPT15] Domain name The name of the domain is the unique name of a network. The
domain name can contain up to 32 characters.
[OPT42] NTP server IP address of the Network Time Server. This address is only
accepted if the protocol "SNTP" is enabled via the WBM.
After the restart, a BootP request is sent to the BootP server with a predefined
number of repetitions. The interval between the repetitions (the timeout) is
variable and is calculated using a random algorithm. If the BootP server does not
respond to any of these requests, the head station does not have a valid IP
configuration. In this case, a blink code is displayed via the I/O LED (see chapter
"Diagnostics") and the BootP request is restarted after a short pause.
If the option “BootP request before static IP” is active (WBM page
“Miscellaneous”), the BootP request is not restarted after the first failure. Instead,
the head station uses the internal saved static configuration (WBM page
"TCP/IP").
11.1.2.2 DHCP (Dynamic Host Configuration Protocol)
The Dynamic Host Configuration Protocol (DHCP) allows you to assign an IP

address and other parameters to the head station of a fieldbus node in a TCP/IP
network.
The DHCP protocol can be activated in the WBM on the "TCP/IP" WBM page
(this option is already enabled by default).
DHCP is a further development of BootP. The difference between BootP and

DHCP is, among other things, that with DHCP the assignment of an IP address
configuration is limited in time (lease time). As with BootP, after the restart a
DHCP request is sent to the DHCP server with a predefined number of
repetitions. The interval between the repetitions (the timeout) is variable and is
calculated using a random algorithm. If the DHCP server does not respond to any
of these requests, the head-end station does not have a valid IP configuration. In
this case, a blink code is displayed via the I/O LED (see chapter "Diagnostics")
and the DHCP request is restarted after a short pause. If the head station has an
active IP address configuration, this must be renewed at cyclical intervals (lease
time). To do this, the head station sends requests to the DHCP server after half
the lease time has expired. If the head station does not receive a response, the
network configuration is discarded after the lease time has expired and a blink
code is displayed via the I/O LED.
Manual
Version 1.1.1
If there is no response from a server on a DHCP request, the request is repeated
continuously: first after 4 seconds, another after 8 seconds, the third after 16
seconds. After that follow more and more requests at longer intervals. If requests
remain without an answer, the network configuration is discarded after the lease
time has expired and a flash code is displayed via the I/O LED. Then the head
station no longer has a valid IP address (IP 0.0.0.0).
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 head station supports the following options in addition to the default “IP
address” option:
Manual
Version 1.1.1
Table 75: 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.
[OPT42] NTP server IP address of the Network Time Server. This address is only
accepted if the protocol "SNTP" is activated via the WBM.
[OPT51] Lease time The maximum duration in seconds (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.
The minimum lease time is 16 minutes.
[OPT58] Renewing time The renewing time indicates when the fieldbus coupler/controller
must renew the lease time. The renewing time should be
approximately half of the lease time.
[OPT59] Rebinding time The rebinding time indicates after what amount of time the
fieldbus coupler/controller must have received its new address.
The rebinding time should be approximately 7/8 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.1
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 SNTP-Client (Simple Network Time Protocol)
The SNTP client is used for synchronization of the time of day between a time
server (NTP and SNTP server Version 3 and 4 are supported) and the internal
system time in the (programmable) fieldbus coupler or controller. The protocol is
executed via a UDP port. Only unicast addressing is supported.
Configuration of the SNTP client
The configuration of the SNTP client is performed via the web-based

management system. The following parameters must be set:
Table 76: Meaning of the SNTP Parameters

Parameter Meaning
WBM page “TCP/IP”  “(S)NTP The address assignment can be made over an IP address.
Server”
The update time indicates the interval in seconds, in which the
WBM page “TCP/IP”  synchronization with the time server is to take place.
„SNTP Update Time (sec,
max. 65535) ”
To operate the ETHERNET couplers/controllers with SNTP in
WBM page “Clock”  various countries, you must specify a time zone. The time zone
“Timezone (+/- relative to GMT (Greenwich Mean time). A range of -12 to +14
hour:minute)” hours is acceptable.
It indicates whether the SNTP Client is to be activated or
WBM page “Port” deactivated.
“SNTP”
11.1.2.6 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 1 GB is available for the internal file system.
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.
Manual
Version 1.1.1
More Information about the implemented Protocols

You can find a list of the exact available implemented protocols in the section
“Technical Data” to the fieldbus coupler and/or controller.
11.1.2.7 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
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 safety-
related 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.
Manual
Version 1.1.1
11.1.2.7.1 MIB II Description
MIB II acc. to RFC1213 is divided into the following groups:
Table 77: MIB II Groups

Group Identifier
System Group 1.3.6.1.2.1.1
Interface Group 1.3.6.1.2.1.2
IP Group 1.3.6.1.2.1.4
IpRoute Table Group 1.3.6.1.2.1.4.21
ICMP Group 1.3.6.1.2.1.5
TCP Group 1.3.6.1.2.1.6
UDP Group 1.3.6.1.2.1.7
SNMP Group 1.3.6.1.2.1.11
Please find detailed information on these individual groups in section
“MIB II groups” of the manual appendix.
Manual
Version 1.1.1
11.1.2.7.2 Traps
Standard Traps
For specific events, the SNMP agent will independently send one of the following
messages without polling the manager.
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

Table 78: Standard Traps

TrapType/TrapNumber/OI Name Event
D of the provided value
TrapType = 0 ColdStart Restart the coupler/controller
TrapType = 1 WarmStart Reset via mode selector switch (only
for controller)
TrapType = 3 EthernetUp Network connection detected
TrapType = 4 AuthenticationFailure Unauthorized (abortive) MIB
access
TrapType = 6/ enterpriseSpecific Enterprise-specific messages and
ab Trap-Nummer 25 function poll in the PFC program
benutzerspezifisch starting with enterprise trap number 25
11.1.2.8 Syslog Client
The network protocol "syslog" (RFC5424) enables the transmission of event-

controlled log messages in an IP-based network. Communication takes place
according to the client-server principle, with a “syslog” client sending log
messages to a “syslog” server via TCP or UDP.
WAGO fieldbus couplers/controllers provide a "syslog" client that sends log

messages via UDP to a "syslog" server that can be configured by the user.
With the "syslog" protocol, a message consists of a short free text message with
additional information for classifying the log message.
Priority Selector (PRI)
The priority selector contains information about the source and the severity of a
log message. This allows log messages to be displayed or filtered on a "syslog"
server according to their urgency and origin.
Manual
Version 1.1.1
The facility field describes the source or the device component that triggered the
log message. Various values are predefined for this in RFC5124:
e.g. 0 = kernel, 1 = user, 4 = security.
The severity field describes the severity of a log message in the range from
0 to 7.
Examples: 0 = critical error, 3 = normal error, 4 = warning and 6 = information.
Header (HEADER)
The header of a "syslog" message contains the following information:
• Protocol version used (VERSION)

• Time stamp at which the log message was created (TIMESTAMP)
• Network name (FQDN) or the IP address of the device (HOSTNAME)
• Application that created the log message (APP-NAME)
• Process ID for the assignment of log messages (PROCID)
• Message ID for typing the log message (MSGID)
Structured Data (STRUCTURED-DATA)
Currently the WAGO fieldbus couplers/controllers do not support structured data.
Structured data is optional and enables the transmission of a list of name-value

pairs (e.g. JSON) within a "syslog" message.
Message Text (MSG)
The message text of a "syslog" message is free text in the "Unicode" or "UTF-8"
format.
Manual
Version 1.1.1
11.1.2.8.1 Syslog Messages
WAGO fieldbus couplers/controllers currently support the following "syslog"

messages:
Table 79: Supported Syslog Messages

Facility Severity Application (APP-NAME) Description
0 (Kernel) 4 (Warning) Core CPU utilization over 80%
0 (Kernel) 3 (Error) SEL (System Error Logger) An error has occurred
(see "Diagnostics" >> ... >> "Evaluating
Node Status - I/O LED (Blink Code
Table))
0 (Kernel) 3 (Error) SEL (System Error Logger) An error has been fixed
(see " Diagnostics" >> ... >> "Evaluating
Node Status - I/O LED (Blink Code
Table))
1 (User) 5 (Note) Parameter A parameter of the head station was
changed
1 (User) 5 (Note) Modbus Maximum number of Modbus TCP
connections exceeded
1 (User) 5 (Note) EIP (EtherNet/IP) Maximum number of EIP connections
exceeded
1 (User) 5 (Note) BAR (Backup & Restore) A backup image was successfully
created
1 (User) 5 (Note) BAR (Backup & Restore) A backup image was successfully
restored
4 (Security) 5 (Note) FTP Authentication via FTP was successful
4 (Security) 4 (Warning) FTP Authentication via FTP failed
4 (Security) 5 (Note) SSH Authentication via SSH was successful
4 (Security) 4 (Warning) SSH Authentication via SSH failed
4 (Security) 5 (Note) WBM (Web-based- Authentication via web server was
Management) successful
4 (Security) 4 (Warning) WBM (Web-based- Authentication via web server failed
Management)
11.1.2.8.2 Configuration
The configuration for the "syslog" client takes place via the web-based
management (see "Configuring via the Web-Based Management System
(WBM)"> "Protocols" and> "TCP/IP").
Manual
Version 1.1.1
11.1.3 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 fieldbus specific application protocols implemented in the fieldbus

coupler/controller are listed in the following chapters and some special details are
described.
Manual
Version 1.1.1
11.2 Modbus Functions

11.2.1 General
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 ex-
change 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 80: Modbus TCP Header

Byte 0 1 2 3 4 5 6 7 8…n
Identifier Protocol-identifier Length field Unit identifier Modbus Data
(entered by (is always 0) (High byte, low (Slave function
receiver) byte) address) code
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.1
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 81: Basic Data Types of MODBUS Protocol

Data type Length Description
Discrete inputs 1 bit Digital inputs
Coils 1 bit Digital outputs
Input register 16 bits Analog input data
Holding register 16 bits 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 82: List of the MODBUS Functions in the Fieldbus Coupler

Function code
Access to resources
Desig- Value Function Access method and description
(R=read/W=write)
nation (hex)
FC1 0x01 Read Coils Reading of several single input bits R: Process image
FC2 0x02 Read Discrete Reading of several input bits R: Process image
Inputs
FC3 0x03 Read Holding Reading of several input registers R: Process image,
Registers internal variables
FC4 0x04 Read Input Reading of several input registers R: Process image,
FC5 0x05 Write Single Writing of an individual output bit W: Process image
Coil
FC6 0x06 Write Single Writing of an individual output W: Process image,
Register register internal variables
FC11 0x0B Get Comm Communication event counter R: None
Event Counters
FC15 0x0F Write Multiple Writing of several output bits W: Process image
Coils
FC16 0x10 Write Multiple Writing of several output registers W: Process image,
FC22 0x16 Mask Write Writing of several bits of an W: Process image
Register individual output register by mask
FC23 0x17 Read/Write Reading and writing of several R/W: Process image
Multiple output registers
Registers
To execute a desired function, specify the respective function code and the
address of the selected input or output channel or of the register.
Manual
Version 1.1.1
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.1
11.2.2 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.
Figure 44: Use of the MODBUS Functions
Manual
Version 1.1.1
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 83: Exception Codes

Exception code Meaning
0x01 Illegal function
0x02 Illegal data address
0x03 Illegal data value
0x04 Slave device failure
0x05 Acknowledge
0x06 Server busy
0x08 Memory parity error
0x0A Gateway path unavailable
0x0B 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.1
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 84: Request of Function Code FC1

Byte Field name Example
Byte 0, 1 Transaction identifier 0x0000
Byte 2, 3 Protocol identifier 0x0000
Byte 4, 5 Length field 0x0006
Byte 6 Unit identifier 0x01 not used
Byte 7 MODBUS function code 0x01
Byte 8, 9 Reference number 0x0000
Byte 10, 11 Bit count 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 85: Response of Function Code FC1

...
Byte 8 Byte count 0x01
Byte 9 Bit values 0x12
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
Manual
Version 1.1.1
lowest value.
The assignment is thus made from 7 to 0 as follows:
Table 86: Assignment of Inputs

OFF OFF OFF ON OFF OFF ON OFF
Bit 0 0 0 1 0 0 1 0
Coil 7 6 5 4 3 2 1 0
Exception
Table 87: Exception of Function Code FC1

...
Byte 8 Exception code 0x01 or 0x02
Manual
Version 1.1.1
11.2.3.2 Function Code FC2 (Read Discrete Inputs)
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

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).

...
Byte 9 Bit values 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 90: Assignment of Inputs

OFF OFF OFF ON OFF OFF ON OFF
Bit 0 0 0 1 0 0 1 0
Coil 7 6 5 4 3 2 1 0
Manual
Version 1.1.1
Exception

...
Manual
Version 1.1.1
11.2.3.3 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.

Byte 10, 11 Word count 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.

...
Byte 9, 10 Value register 0 0x1234
The contents of register 0 are displayed by the value 0x1234 and the
contents of register 1 is 0x2345.
Exception

...
Manual
Version 1.1.1
11.2.3.4 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

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.

...
The contents of register 0 are shown by the value 0x1234 and the contents of
register 1 is 0x2345.
Exception

...
Manual
Version 1.1.1
11.2.3.5 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)

Byte 10 ON/OFF 0xFF
Byte 11 0x00
Response

...
Byte 10 Value 0xFF
Byte 11 0x00
Exception

...
Byte 8 Exception code 0x01, 0x02 or 0x03
Manual
Version 1.1.1
11.2.3.6 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

Byte 10, 11 Register value 0x1234
Response
The reply is an echo of the inquiry.

...
Byte 10, 11 Register value 0x1234
Exception

...
Manual
Version 1.1.1
11.2.3.7 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 104: Request of Function code FC11

Byte 7 MODBUS function code 0x0B
Response
The reply contains a 2-byte status word and a 2-byte event counter. The status
word only contains zeroes.

...
Byte 7 MODBUS function code 0x0B
Byte 8, 9 Status 0x0000
Byte 10, 11 Event count 0x0003
The event counter shows that 3 (0x0003) events were counted.
Exception
Table 106: Exception of Function Code FC 11

...
Manual
Version 1.1.1
11.2.3.8 Function Code FC15 (Write 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.

Byte 7 MODBUS function code 0x0F
Byte 13 Data byte1 0xA5
Byte 14 Data byte2 0xF0
Response

...
Manual
Version 1.1.1
Exception

...
Manual
Version 1.1.1
11.2.3.9 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

Byte 4, 5 Length field 0x000B
Byte 13, 14 Register value 1 0x1234
Byte 15, 16 Register value 2 0x2345
Response

...
Exception

...
Manual
Version 1.1.1
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

Byte 10, 11 AND mask 0x0000
Byte 12, 13 OR mask 0xAAAA
Response

...
Byte 10, 11 AND mask 0x0000
Byte 12, 13 OR mask 0xAAAA
Exception

...
Manual
Version 1.1.1
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. The write operation is performed before the read.
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.

Byte 4, 5 Length field 0x000D
Byte 8, 9 Reference number for read 0x0000
Byte 10, 11 Word count for read (1…125) 0x0002
Byte 12, 13 Reference number for write 0x0003
Byte 14, 15 Word count for write (1…100) 0x0001
Byte 16 Byte count (2 x word count for write) 0x02
Byte 17...(B+16) Register values (B = Byte count) 0x0123
Response

...
Byte 8 Byte count (2 x word count for read) 0x04
Byte 9...(B+1) Register values (B = Byte count) 0x0004 or 0x5678
Exception

...
Manual
Version 1.1.1
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.1
11.2.4 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 119: Register Access Reading (with FC3 and FC4)

MODBUS address IEC 61131 Memory range
[dec] [hex] address
0...255 0x0000...0x00FF %IW0...%IW255 Physical input area (1)
First 256 Words of physical input 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:
4096...12287 0x1000...0x2FFF - Configuration register (see Section
„Configuration Register“)
24576...25339 0x6000...0x62FB %IW256...%IW1020 Physical input area (2)
Additional 764 Words physical input data
25340...28671 0x62FC...0x6FFF - MODBUS exception:
28672...29435 0x7000...0x72FB %QW256...%QW1020 Physical output area (2)
Additional 764 Words physical output data
29436...65535 0x72FC...0xFFFF - MODBUS exception:
Manual
Version 1.1.1
Register Access Writing (with FC6 and FC16)
Table 120: Register Access Writing (with FC6 and FC16)

MODBUS address IEC 61131 Memory range
[dec] [hex] address
0...255 0x0000...0x00FF %QW0...%QW255
Physical output area (1)
256...511 0x0100...0x01FF - MODBUS exception:
512...767 0x0200...0x02FF %QW0...%QW255 Physical output area (1)
4096...12287 0x1000...0x2FFF - Configuration register (see Section
“Configuration Register”)
25340...28671 0x62FC...0x6FFF - MODBUS exception:
29436...65535 0x72FC...0xFFFF - MODBUS exception:
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.1
Bit Access Reading (with FC1 and FC2)
Table 121: Bit Access Reading (with FC1 and FC2)

MODBUS address Memory range Description
[dec] [hex]
0...511 0x0000...0x01FF Physical input area (1) First 512 digital inputs
512...1023 0x0200...0x03FF Physical output area (1) First 512 digital outputs
1024... 12287 0x0400...0x2FFF - MODBUS exception:
12288...13815 0x3000...0x35F7 MODBUS exception:
“Illegal data address
13816...16383 0x35F8...0x3FFF - MODBUS exception:
0x8000…0x85F7 Physical input area (2) Starts with the 513th and ends with the
2039th digital input
0x85F8…0x8FFF MODBUS exception:
0x9000…0x95F7 Physical output area (2) Starts with the 513th and ends with the
2039th digital output
0x95F8…0xFFFF MODBUS exception:
Bit Access Writing (with FC5 and FC15)
Table 122: Bit Access Writing (with FC5 and FC15)

MODBUS address Memory range Description
[dec] [hex]
0x85F8…0x8FFF MODBUS exception:
0x95F8…0xFFFF MODBUS exception:
Manual
Version 1.1.1
11.2.5 Modbus Registers

Table 123: Modbus Registers
Register Acces Length Description
address s (Word)
0x1000 R/W 1 Watchdog time read/write
0x1001 R/W 1…2 Watchdog coding mask 1…16
0x1002 R/W 1 Watchdog coding mask 17…32
0x1003 R/W 1 Watchdog trigger
0x1004 R 1 Minimum trigger time
0x1005 R/W 1 Watchdog stop (Write sequence 0xAAAA, 0x5555)
0x1006 R 1 Watchdog status
0x1007 R/W 1 Restart watchdog (Write sequence 0x1)
0x1008 R/W 1 Stop watchdog (Write sequence 0x55AA or 0xAA55)
0x1009 R/W 1 Modbus and HTTP close at watchdog time-out
0x100A R/W 1 Watchdog configuration
0x100B W 1 Save watchdog parameter ( Write sequence 0x55AA or 0xAA55)
0x1020 R 1…2 LED error code
0x1021 R 1 LED error argument
0x1022 R 1…4 Number of analog output data in the process image (in bits)
0x1023 R 1…3 Number of analog input data in the process image (in bits)
0x1024 R 1…2 Number of digital output data in the process image (in bits)
0x1025 R 1 Number of digital input data in the process image (in bits)
0x1029 R/W 1…9 Modbus TCP statistics (Write sequence 0x55AA or 0xAA55)
0x102A R 1 Number of TCP connections
0x102B W 1 KBUS Reset
0x1030 R/W 1 Configuration MODBUS/TCP time-out
0x1031 R 1…3 Read out the MAC-ID of the coupler/controller
0x1037 R/W 1 Modbus Response Delay (ms)
0x1038 1 Modbus TOS
0x1050 R 3 Diagnosis of the connected I/O modules
0x2000 R 1…9 Constant 0x0000
Manual
Version 1.1.1
0x2001 R 1…8 Constant 0xFFFF
0x2002 R 1…7 Constant 0x1234
0x2003 R 1…6 Constant 0xAAAA
0x2004 R 1…5 Constant 0x5555
0x2005 R 1…4 Constant 0x7FFF
0x2006 R 1…3 Constant 0x8000
0x2007 R 1…2 Constant 0x3FFF
0x2008 R 1 Constant 0x4000
0x2010 R 1 Firmware version
0x2011 R 1 Series code
0x2012 R 1 Coupler/controller code
0x2013 R 1 Firmware version major revision
0x2014 R 1 Firmware version minor revision
0x2020 R 1 … 16 Short description controller
0x2021 R 1…8 Compile time of the firmware
0x2022 R 1…8 Compile date of the firmware
0x2023 R 1 … 32 Indication of the firmware loader
0x2030 R 1 … 65 Description of the connected I/O modules (module 0…64)
0x2035 R/W 1 Process image settings
0x2036 R Fieldbus coupler/controller diagnostics
0x2040 W 1 Software reset (Write sequence 0x55AA or 0xAA55)
0x2043 W 1 Factory settings
11.2.5.1 Accessing Register Values
You can use any den 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 the Modbus watchdog and how to access both
the registers and their values.
11.2.5.2 Modbus-Watchdog
With the aid of the Modbus watchdog, it is possible to monitor whether

communication takes place with Modbus function codes with a specific regularity.
If the communication lapses for a given time, it is called a "time-out", which is
considered fieldbus failure. In general, the Modbus watchdog ensures that all
analog output modules in the fieldbus node are set to "0" and all digital output
modules are set to logical "Off". At the same time, the user is informed about the
time-outvia the WBM as well as via a status register (0x1006).
An internal timer is used to monitor the time-out. This timer is set to a certain
maximum time (register 0x1000) and started at the beginning of the monitoring. If
communication with a Modbus function code to be monitored occurs before
Manual
Version 1.1.1
reaching the maximum time, the timer starts again at "0". However, only the
function codes selected in the coding mask (0x1001) are monitored (respective
bit = '1'). All other function codes keep the timer running or, unlike the selected
function codes, do not restart the watchdog after a time-out.
The head station’s behavior after a time-outis defined by the initial choice of two
possible operating modes ("Standard"/"Alternative") and by an additional
parameter for the TCP interface (register 0x1009, "MODBUS and HTTP close for
Modbus Watchdog time-out“).
• Behavior 1 (lowest restriction):

After a Modbus watchdog time-out, all analog and digital output modules
are set to "0" or "Off", however, the Modbus watchdog is immediately
restarted the next time a function code is sent (provided the function code
in the coding mask (0x1001) is selected).
=> Select the operating mode "Alternative",

=> Set register 0x1009 to the value '0'.
When reading the status register (0x1006), the correct value is read first:
"2" = "Watchdog expired". Because this restarts the Modbus watchdog, the
next read would result in "1" = "watchdog active".
• Behavior 2 (medium restriction):

Further communication in relation to process data should be prevented.
Any attempt to access process data via Modbus function codes should be
answered with an error.
=> Select the operating mode "Standard" for this.
However, the Modbus TCP connection will still work to access the Modbus
configuration and status registers.
=> Set the register 0x1009 to the value '0'.
Access to the Modbus watchdog registers is still possible after a Modbus

watchdog time-out, although Modbus function codes are also sent in this
case.
For all other Modbus TCP/IP requests, the head station responds with the
exception code 0x0004 ("Slave Device Failure").
• Behavior 3 (highest restriction):

Further communication in relation to process data should be prevented.
Any attempt to access process data via Modbus function codes should be
answered with an error.
=> Select the operating mode "Standard" for this.
Manual
Version 1.1.1
In addition, the TCP connection should also be closed to prevent access to
the Modbus watchdog registers. For example thereby a restart of the
Modbus watchdog is not possible without a previous TCP reconnection.
=> Set the register 0x1009 to the value '1'.
After renewed TCP connection, in the "Standard" operating mode the

Modbus watchdog is still in the "expired" status and must be restarted
(register 0x1003 or 0x1007).
11.2.5.3 Modbus Watchdog Register
The watchdog registers can be addressed analogously with the described

Modbus function codes (read and write). Instead of the address of an I/O module
channel, the respective register address is therefor specified.
Table 124: Register Address 0x1000

Register address 0x1000 (4096dec)
Value Watchdog time, WS_TIME
Access Read/write
Default 0x0064
Description This register stores the watchdog timeout value as an unsigned 16 bit value. The
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.

Value Watchdog function coding mask, function code 1...16, WDFCM_1_16
Access Read/write
Default 0xFFFF
Description Using this mask, the function codes can be set to trigger the watchdog function.
The function code can be selected via a "1"
FC 1 Bit 0
FC 2 Bit 1
FC 3 Bit 2
FC 4 Bit 3
FC 5 Bit 4
...
FC 16 Bit 15
Changes to the register value can only be made if the watchdog is deactivated.
The bit pattern stored in the register defines the function codes that trigger the
watchdog. Some function codes are not supported. For those the watchdog will
not be triggered even if another Modbus device transmits one of them.
When switching the watchdog type from "Standard" to "Alternative", the coding
mask is reset to default value 0xFFFF.
Manual
Version 1.1.1
Value Watchdog function coding mask, function code 17...32, WD_FCM_17_32
Access Read/write
Default 0xFFFF
Description Same function as above, however, with the function codes 17 to 32.
FC 17 Bit 0
FC 18 Bit 1
...
FC 32 Bit 15
These codes are currently not supported, for this reason the default value should
not be changed. Changes to the register value can only be made if the watchdog
is deactivated. It is not possible to modify this value while the watchdog is running.

Value Watchdog trigger, WD_TRIGGER
Access Read/write
Standard 0x0000
Description This register is used for an alternative trigger method. The watchdog is triggered
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 after a Power-on.
For a restart the written value must necessarily be unequal the before written
value! A watchdog fault is reset and writing process data is possible again.

Register address 0x1004 (4100dez)
Value Minimum current trigger time, WD_AC_TRG_TIME
Access Read
Standard 0xFFFF
Description This register saves the minimum current watchdog trigger time. For user this
register is irrelevant.

Value Stop watchdog, WD_AC_STOP_MASK
Access Read/write
Standard 0x0000
Description The watchdog is stopped if here the value 0xAAAA is written first, followed by
0x5555. The watchdog fault reaction is blocked. A watchdog fault is reset and
writing on the process data is possible again.
Manual
Version 1.1.1
Value While watchdog is running, WD_RUNNING
Access Read
Standard 0x0000
Description Current watchdog status.
at 0x0000: Watchdog not active
at 0x0001: Watchdog active
at 0x0002: Watchdog exhausted.

Value Restart watchdog, WD_RESTART
Access Read/write
Standard 0x0000
Description This register restarts the watchdog timer after time out by writing a value of 0x1
into it. If the watchdog was stopped before the time out, it is not restarted.

Value Simply stop watchdog, WD_AC_STOP_SIMPLE
Access Read/write
Standard 0x0000
Description This register stops the watchdog by writing the value 0xAA55 or 0x55AA into 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

Value Close Modbus socket after watchdog timeout
Access Read/write
Standard 0x0000
Description 0: Modbus socket is not closed
1: Modbus socket is closed
Table 134: Register Address 0x100A

Register address 0x100A (4106dez)
Value Watchdog type Standard/Alternative
Access Read/write
Standard 0x0000
Description 0: Modbus watchdog type “Standard”
1: Modbus watchdog type “Alternative”
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.1
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 135: Starting Watchdog

FC FC16 FC15 FC14 FC13 FC12 FC11 FC10 FC9 FC8 FC7 FC6 FC5 FC4 FC3 FC2 FC1
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
bin 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0
hex 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 0xAA55 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 0xAA55 or 0x55AA into 0x1008
(Simply Stop Watchdog register, WD_AC_STOP_SIMPLE).
Table 136: Register Address 0x100B
Register address 0x100B (4107dez)
Value Save watchdog parameter
Access Write
Standard 0x0000
Description With writing of '0x55AA' or '0xAA55' in register 0x100B the registers 0x1000,
0x1001, 0x1002 are set on remanent.
Manual
Version 1.1.1
11.2.5.4 Diagnostic Registers
The following registers can be read to determine errors in the node:

Value LedErrCode
Access Read
Description Declaration of the error code

Value LedErrArg
Access Read
Description Declaration of the error argument
Manual
Version 1.1.1
11.2.5.5 Configuration Registers
The following registers contain configuration information of the connected

modules:

Value CnfLen.AnalogOut
Access Read
Description Number of word-based outputs registers in the process image in bits (divide by 16
to get the total number of analog words)

Value CnfLen.AnalogInp
Access Read
Description Number of word-based inputs registers in the process image in bits (divide by 16
to get the total number of analog words)

Value CnfLen.DigitalOut
Access Read
Description Number of digital output bits in the process image

Value CnfLen.DigitalInp
Access Read
Description Number of digital input bits in the process image

Register Address 0x1029 (4137dec) with 9 Words
Value MODBUS TCP statistics
Access Read/write
Description 1 word SlaveDeviceFailure  local bus error, fieldbus error by activated
watchdog
1 word BadProtocol  error in the MODBUS TCP header
1 word BadLength  Wrong telegram length
1 word BadFunction  Invalid function code
1 word BadAddress  Invalid register address
1 word BadData  Invalid value
1 word TooManyRegisters  Number of the registers which can be
worked on is too large, Read/Write 125/100
1 word TooManyBits  Number of the coils which can be worked on
is too large, Read/Write 2000/800
1 word ModTcpMessageCounter  Number of received MODBUS/TCP
requests
By writing 0xAA55 or 0x55AA the register is reset.
Manual
Version 1.1.1
Table 144: Register Address 0x102A
Register address 0x102A (4138dec) with a word count of 1
Value MODBUS/TCP connections
Access Read
Description Number of TCP connections
Table 145: Register Address 0x102B

Register Address 0x102B (4139dez) with a Word Count of up to 1
Value Local bus reset
Access Write
Description Writing of this register restarts the local bus

Register address 0x1030 (4144dec) with a word count of 1
Value Configuration MODBUS/TCP time-out
Access Read/write
Default 0x0258 (600 decimal)
Description This is the maximum number of milliseconds the fieldbus coupler will allow a
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.

Value Read the MAC-ID of the controller
Access Read
Description This register gives the MAC-ID, with a length of 3 words

Register address 0x1037 (4151dez) with a word count of 1
Value Configuration of Modbus Response Delay Time
Access Read/write
Default 0x0000
Description This register saves the value for the Modbus Response Delay Time for a Modbus
connection. The time base is 1 ms. On the Modbus TCP connection, the
response will be delayed by the inscribed time.

Register address 0x1038 (4152dez) with a word count of 1
Value Configuration of the priority value (DSCP in IPv4-ToS) for sending Modbus
packets.
Access Read/write
Default 0x0000
Description This register stores the priority value (DSCP in IPv4-ToS) for sending Modbus
packets. The range of values is 0 … 63.
Manual
Version 1.1.1
Value Diagnosis of the connected I/O modules
Access Read
Description Diagnosis of the connected I/O modules, length 3 words
Word 1: Number of the module
Word 2: Number of the channel
Word 3: Diagnosis
Mapping Diagnosis (Word 3)

Bit 0: Underrage
Bit 1: Overrange
Bit 2: User underrange
Bit 3: User overragne
Bit 4: Short circuit
Bit 5: Wire break
Bit 6: Collective failure
11.2.5.6 Constant Registers
The following registers contain constants, which can be used to test

communication with the master:

Value Zero, GP_ZERO
Access Read
Description Constant with zeros

Value Ones, GP_ONES
Access Read
Description Constant with ones
• –1 if this is declared as "signed int"
• MAXVALUE if it is declared as "unsigned int"

Value 1,2,3,4, GP_1234
Access Read
Description This constant value is used to test the Intel/Motorola format specifier. If the master
reads a value of 0x1234, then with Intel format is selected – this is the correct
format. If 0x3412 appears, Motorola format is selected.
Manual
Version 1.1.1
Value Mask 1, GP_AAAA
Access Read
Description This constant is used to verify that all bits are accessible to the fieldbus master.
This will be used together with register 0x2004.

Value Mask 1, GP_5555
Access Read
Description This constant is used to verify that all bits are accessible to the fieldbus master.
This will be used together with register 0x2003.

Value Maximum positive number, GP_MAX_POS
Access Read
Description Constant in order to control arithmetic.

Value Maximum negative number, GP_MAX_NEG
Access Read
Description Constant in order to control arithmetic

Value Maximum half positive number, GP_HALF_POS
Access Read

Value Maximum half negative number, GP_HALF_NEG
Access Read
Manual
Version 1.1.1
11.2.5.7 Firmware Information Registers
The following registers contain information on the firmware of the controller:

Value Revision, INFO_REVISION
Access Read
Description Firmware index, e.g. 0x0005 for version 5

Value Series code, INFO_SERIES
Access Read
Description WAGO serial number, e.g. 0x02EE (750 dec.) for WAGO-I/O-SYSTEM 750

Value Order number, INFO_ITEM
Access Read
Description First part of WAGO order number,
e.g. 0x0349 (841 dec.) for the controller 750-841 or 0x0155 (341 dec.) for the
coupler 750-341 etc.

Value Major sub item code, INFO_MAJOR
Access Read
Description Firmware version major revision

Value Minor sub item code, INFO_MINOR
Access Read
Description Firmware version minor revision

Register address 0x2020 (8224dec) with a word count of up to 16
Value Description, INFO_DESCRIPTION
Access Read
Description Information on the controller, 16 words
Manual
Version 1.1.1
Value Description, INFO_DESCRIPTION
Access Read
Description Time of the firmware version, 8 words

Value Description, INFO_DATE
Access Read
Description Date of the firmware version, 8 words

Value Description, INFO_LOADER_INFO
Access Read
Description Information to the programming of the firmware, 32 words
Manual
Version 1.1.1
Value Description of the connected I/O modules
Access Read module 0...64
Description Length 1...65 words
The node configuration can be specified in the 0x2030 register. The item number
of the I/O modules or fieldbus coupler/controller (without leading 750) is listed in
order. Each module is represented in a word. Because order 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
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Code 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1
Hex 8 4 0 1
2 Channel Digital Output Module = 0x8202
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Code 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0
Hex 8 2 0 2

Access Read modules 65...128
Description Length 1…64 words
order. Because order numbers cannot be read out of digital modules, a code is
displayed for them, as defined below:

Access Read modules 129...192
Manual
Version 1.1.1
Access Read modules 193 ... 255

Value Process image settings
Access Read/Write
Description For internal use only.
No access to I/O data when changes are made!

Note that this register is intended for internal use only.
Changes can mean that access to the I/O data is no longer
possible!
Manual
Version 1.1.1
Value Fieldbus coupler/controller diagnostics
Access Read
Description Register 0.0 Fieldbus error 0/1 0
allocation 0.1 Internal bus error 0/1 0
0.2 I/O module error 0/1 0
0.3 Fieldbus coupler/controller error 0/1 0
Register 1 Error code in the event of a configuration 0 - 65535
number error
Register 2 0.1=0 Bit length of Internal bus
number 0.1=1 Error code in the event of an internal bus 0 - 65535
error
Register 3 0.1=0 Number of I/O modules
number 0.1=1 I/O module number, at which the error
occurred
Register 4 Error code in the event of an internal bus
number error
Register 5 Internal bus command error Counter
number 6 Internal bus command error „Quality“
7 Internal bus command error „Quality-Overall“
Register 8 Internal bus timeout error Counter
number 9 Internal bus timeout error „Quality“
10 Internal bus timeout error „Quality-Overall“
Register 11 Internal bus input data error Counter
number 12 Internal bus input data error „Quality“
13 Internal bus input data error „Quality -Overall“
Register 14 Internal bus output data error Counter
number 15 Internal bus output data error „Quality“
16 Internal bus output data error „Quality-
Overall“

Value Implement a software reset
Access Write (Write sequence 0xAA55 or 0x55AA)
Description The fieldbus coupler/controller performs a restart by writing the values 0xAA55 or
0x55AA.

Value 0x55AA
Access Write
Description Factory settings
The default settings are applied after the next reset, e.g., software reset via
Modbus register address 0x2040.
Manual
Version 1.1.1
208 I/O Modules WAGO I/O System 750
12 I/O Modules
12.1 Overview
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
• Communication Modules, Supply and Segment Modules
• Function and Technology Modules
For detailed information on the I/O modules and the module variations, refer to
the manuals for the I/O modules.
You will find these manuals on the WAGO web pages under www.wago.com.
More Information about the WAGO I/O SYSTEM

Current information on the modular WAGO I/O SYSTEM is available in the
Internet under: www.wago.com.
Manual
Version 1.1.1
WAGO I/O System 750 I/O Modules 209
12.2 Process Data Architecture for Modbus-TCP

With some I/O modules, the structure of the process data is fieldbus specific.
Modbus-TCP 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/O-SYSTEM 750 and 753 I/O modules with Modbus-TCP.
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.
12.2.1 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 177: 1 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
Data bit
bit
DI 1
S1
Manual
Version 1.1.1
12.2.1.2 2 Channel Digital Input Modules
750-400, -401, -405, -406, -407, -410, -411, -412, -427, -438, (and all variations),
753-400, -401, -405, -406, -410, -411, -412, -427, -429
Table 178: 2 Channel Digital Input Modules

Input Process Image
Data bit Data bit
DI 2 DI 1
Channel 2 Channel 1
12.2.1.3 2 Channel Digital Input Module with Diagnostics
750-419, -421, -424, -425,

753-421, -424, -425
Table 179: 2 Channel Digital Input Module with Diagnostics

Input Process Image
Diagnostic Diagnostic Data bit Data bit
bit S 2 bit S 1 DI 2 DI 1
Channel 2 Channel 1 Channel 2 Channel 1
12.2.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 180: 2 Channel Digital Input Module with Diagnostics and Output Process Data
Input Process Image
Diagnostic bit Diagnostic bit Data bit Data bit
S2 S1 DI 2 DI 1
Output Process Image

Acknowledge- Acknowledge-
ment bit Q 2 ment bit Q 1 0 0
Channel 2 Channel 1
Manual
Version 1.1.1
750-402, -403, -408, -409, -414, -415, -422, -423, -428, -432, -433, -1420, -1421,
-1422, -1423
753-402, -403, -408, -409, -415, -422, -423, -428, -432, -433, -440

Input Process Image
Data bit Data bit Data bit Data bit
DI 4 DI 3 DI 2 DI 1
750-430, -431, -436, -437, -1415, -1416, -1417, -1418,

753-430, -431, -434, -436, -437

Input Process Image
Data bit DI Data bit Data bit Data bit Data bit Data bit Data bit Data bit
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
12.2.1.7 8 Channel Digital Input Module NAMUR with Diagnostics and Output
Process Data
750-439
The digital input module NAMUR provides via one logical channel 2 byte for the
input and output process image.
The signal state of NAMUR inputs DI1 … DI8 is transmitted to the fieldbus
coupler/controller via input data byte D0.
The fault conditions are transmitted via input data byte D1.
The channels 1 … 8 are switched on or off via the output data byte D1.
The output data byte D0 is reserved and always has the value “0“.
Manual
Version 1.1.1
Table 183: 8 Channel Digital Input Module NAMUR with Diagnostics and Output Process Data
Input Process Image
Input byte D0
Signal Signal Signal Signal Signal Signal Signal Signal
status status status status status status status status
DI 8 DI 7 DI 6 DI 5 DI 4 DI 3 DI 2 DI 1
Input byte D1
Wire break Wire break Wire break Wire break Wire break Wire break Wire break Wire break
/short /short /short /short /short /short /short /short
circuit circuit circuit circuit circuit circuit circuit circuit
Data bit Data bit Data bit Data bit Data bit Data bit Data bit Data bit

Output byte D0
0 0 0 0 0 0 0 0
Output byte D1
DI Off 8 DI Off 7 DI Off 6 DI Off 5 DI Off 4 DI Off 3 DI Off 2 DI Off 1
*) *) *) *) *) *) *) *)
*) 0: Channel ON
1: Channel OFF
Manual
Version 1.1.1
12.2.1.8 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data
750-1425
The digital input module PTC provides via one logical channel 2 byte for the input
and output process image.
The signal state of PTC inputs DI1 … DI8 is transmitted to the fieldbus
coupler/controller via input data byte D0.
The fault conditions are transmitted via input data byte D1.
The channels 1 … 8 are switched on or off via the output data byte D1.
The output data byte D0 is reserved and always has the value “0“.
Table 184: 8 Channel Digital Input Module PTC with Diagnostics and Output Process Data
Input Process Image
Input Byte D0
Signal Signal Signal Signal Signal Signal Signal Signal
status status status status status status status status
Input Byte D1
Wire break Wire break Wire break Wire break Wire break Wire break Wire break Wire break
/short /short /short /short /short /short /short /short
circuit circuit circuit circuit circuit circuit circuit circuit

Output Byte D0
0 0 0 0 0 0 0 0
Output Byte D1
DI Off 8 DI Off 7 DI Off 6 DI Off 5 DI Off 4 DI Off 3 DI Off 2 DI Off 1
*) *) *) *) *) *) *) *)
*) 0: Channel ON
1: Channel OFF
Manual
Version 1.1.1
12.2.2 16 Channel Digital Input Modules

750-1400, -1402, -1405, -1406, -1407

Input Process Image
Input Byte D0
Input Byte D1
Channel Channel Channel Channel Channel Channel Channel Channel
16 15 4 13 12 11 10 9
Manual
Version 1.1.1
12.2.2.1 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.2 1 Channel Digital Output Module with Input Process Data
750-523
The digital output module delivers 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 186: 1 Channel Digital Output Module with Input Process Data
Input Process Image
Status bit
not used “Manual
Operation“

controls
not used DO 1
Channel 1
12.2.2.3 2 Channel Digital Output Modules
750-501, -502, -509, -512, -513, -514, -517, -535, -538, (and all variations),
753-501, -502, -509, -512, -513, -514, -517
Table 187: 2 Channel Digital Output Modules

controls controls
DO 2 DO 1
Channel 2 Channel 1
Manual
Version 1.1.1
12.2.2.4 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 188: 2 Channel Digital Input Modules with Diagnostics and Input Process Data
Input Process Image
Diagnostic Diagnostic
bit S 2 bit S 1
Channel 2 Channel 1

controls controls
DO 2 DO 1
Channel 2 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,
Table 189: 2 Channel Digital Input Modules with Diagnostics and Input Process Data 75x-506
Input Process Image
Diagnostic Diagnostic Diagnostic Diagnostic
bit S 3 bit S 2 bit S 1 bit S 0
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

controls controls
not used not used DO 2 DO 1
Channel 2 Channel 1
Manual
Version 1.1.1
750-504, -515, -516, -519, -531,

753-504, -516, -531, -540

controls controls controls controls
DO 4 DO 3 DO 2 DO 1

Process Data
750-532, -539
Table 191: 4 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Diagnostic Diagnostic Diagnostic
Diagnostic bit
bit bit bit
S1
S4 S3 S2
Channel 1
Channel 4 Channel 3 Channel 2
Diagnostic bit S = ‘0’ no Error
Diagnostic bit S = ‘1’ overload, short circuit, or broken wire

controls controls controls controls
DO 4 DO 3 DO 2 DO 1
12.2.2.7 8 Channel Digital Output Module
750-530, -536, -1515, -1516,

753-530, -534, 536
Table 192: 8 Channel Digital Output Module

controls controls controls controls controls controls controls controls
DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 DO 1
Manual
Version 1.1.1

Process Data
750-537,
753-537
Table 193: 8 Channel Digital Output Modules with Diagnostics and Input Process Data
Input Process Image
Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic
bit bit bit bit bit bit bit bit
S8 S7 S6 S5 S4 S3 S2 S1
Diagnostic bit S = ‘0’ no Error
Diagnostic bit S = ‘1’ overload, short circuit, or broken wire

750-1500, -1501, -1504, -1505

Output Byte D0
Output Byte D1
Channel Channel Channel Channel Channel Channel Channel Channel
16 15 14 13 12 11 10 9
Manual
Version 1.1.1
12.2.2.10 8 Channel Digital Input/Output Modules
750-1502, -1506
Table 195: 8 Channel Digital Input/Output Modules

Input Process Image
Data bit DI Data bit Data bit Data bit Data bit Data bit Data bit Data bit
8 DI 7 DI 6 DI 5 DI 4 DI 3 DI 2 DI 1

Manual
Version 1.1.1
12.2.3 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 on the structure of control and status bytes

For detailed information on the structure of a particular I/O module’s
control/status bytes, please refer to that module’s manual. Manuals for each
module can be found on the Internet at www.wago.com.
12.2.3.1 1 Channel Analog Input Modules
750-491, (and all variations)
Table 196: 1 Channel Analog Input Modules

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0 Measured Value UD
1 D3 D2 Measured Value Uref
750-452, -454, -456, -461, -462, -464 (2-Channel Operation) -465, -466, -467,
-469, -470, -472, -473, -474, -475, 476, -477, -478, -479, -480, -481, -483, -485,
-487, -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)

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0 Measured Value Channel 1
Manual
Version 1.1.1
12.2.3.3 2 Channel Analog Input Modules HART
750-482, -484, (and all variations),

753-482
The HART I/O module provides two different process images depending on the
set operating mode.
For the pure analog values 4 mA ... 20 mA, the HART I/O module transmits 16 bit
measured values per channel as an analog input module, which are mapped by
word.
In operating mode "6 Byte Mailbox", the HART I/O module provides the fieldbus
coupler / controller with a 12-byte input and output process image via a logical
channel. For the control/status byte and the dummy byte, an acyclic channel
(mailbox) for the process value communication is embedded in the process
image, which occupies 6 bytes of data. This is followed by the measured values
for channels 1 and 2.
HART commands are executed via the WAGO-IEC function blocks of the
"WagoLibHart_0x.lib" library. The data is tunneled to the application via the
mailbox and decoded by means of the library, so that the evaluation and
processing takes place directly at the application level.
The operating mode is set using the WAGO-I / O-CHECK commissioning tool.
Manual
Version 1.1.1
Table 198: 2-Channel Analog Input Modules HART
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Table 199:: 2 Channel Analog Input Modules HART + 6 bytes Mailbox

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 Internal Use S0 Internal used Status byte
1 MBX_RES MBX_RES
2 MBX_RES MBX_RES Response data from mailbox
3 MBX_RES MBX_RES

Byte Destination
Offset Description
High Byte Low Byte
0 - C0 Control byte
1 MBX_REQ MBX_REQ
2 MBX_REQ MBX_REQ Request data from mailbox
3 MBX_REQ MBX_REQ
4 - -
Not used
5 - -
750-450, -453, -455, -457, -459, -460, -463, -464 (4-Channel Operation), -468,
-471, -468, (and all variations),
753-453, -455, -457, -459

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Manual
Version 1.1.1
750-451, 750-458, 750-496, 750-497

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Manual
Version 1.1.1
12.2.3.6 3-Phase Power Measurement Module
750-493
The above Analog Input Modules have a total of 9 bytes of user data in both the
Input and Output Process Image (6 bytes of data and 3 bytes of control/status).
The following tables illustrate the Input and Output Process Image, which has a
total of 6 words mapped into each image.
Word alignment is applied.
Table 202: 3-Phase Power Measurement Module

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S0 Status byte 0
1 D1 D0 Input data word 1

Byte Destination
Offset Description
High Byte Low Byte
0 - C0 Control byte 0
1 D1 D0 Output data word 1
Manual
Version 1.1.1
750-494, -495, (and all variations)
The 3-Phase Power Measurement Modules 750-494, -495, (and all variations)
have a total of 24 bytes of user data in both the Input and Output Process Image
(16 bytes of data and 8 bytes of control/status).
Table 203: 3-Phase Power Measurement Modules 750-494, -495, (and all variations)
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 S1 S0 Status word
1 S3 S2 Extended status word 1
4 D1 D0
Process value 1
5 D3 D2
6 D5 D4
Process value 2
7 D7 D6
8 D9 D8
Process value 3
9 D11 D10
10 D13 D12
Process value 4
11 D15 D14

Byte Destination
Offset Description
High Byte Low Byte
0 S1 S0 Control word
1 S3 S2 Extended control word 1
4 - -
-
5 - -
6 - -
-
7 - -
8 - -
-
9 - -
10 - -
-
11 - -
Manual
Version 1.1.1
12.2.4 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 on the structure of control and status bytes

For detailed information on the structure of a particular I/O module’s
control/status bytes, please refer to that module’s manual. Manuals for each
module can be found on the Internet at www.wago.com.
12.2.4.1 2 Channel Analog Output Modules
750-550, -552, -554, -556, -560, -562, 563, -585, -586, (and all variations),
753-550, -552, -554, -556
Table 204: 2 Channel Analog Output Modules

Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0 Output Value Channel 1
750-553, -555, -557, -559,

753-553, -555, -557, -559

Byte Destination
Offset Description
High Byte Low Byte
Manual
Version 1.1.1
750-597

Byte Destination
Offset Description
High Byte Low Byte
12.2.5 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 about 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: www.wago.com.
Manual
Version 1.1.1
12.2.5.1 Counter Modules
750-404, (and all variations except of /000-005),

753-404, -404/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 207: Counter Modules 750-404, (and all variations except of /000-005),
753-404, -404/000-003
Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 - S Status byte
1 D1 D0
Counter value
2 D3 D2

Byte Designation
Offset Description
High Byte Low Byte
0 - C Control byte
1 D1 D0
Counter setting value
2 D3 D2
750-404/000-005,
753-404/000-005
and Output Process Image (4 bytes of counter data and 1 byte of control/ status).
The two counter values are 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 208: Counter Modules 750-404/000-005, 753-404/000-005

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 - S Status byte
1 D1 D0 Counter Value of Counter 1

Byte Designation
Offset Description
High Byte Low Byte
0 - C Control byte
1 D1 D0 Counter Setting Value of Counter 1
Manual
Version 1.1.1
750-633
The above Counter Module has 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 following tables illustrate the Input and Output Process Image, which has a
total of 3 words mapped into each image. Word alignment is applied.
The meaning of the output data depends on the set operating mode:
1 Up counter with enable input
2 Up/down counter with U/D input
3 Frequency counter
4 Gate time counter
Table 209: Counter Modules 750-633

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 - S Status byte
1 D1 D0
Counter Value
2 D3 D2

Byte Designation
Offset Description
High Byte Low Byte
0 - C Control byte
Counter Setting Value 1,2)
1 D1 D0 watchdog time 3)
reserved 4)
Counter Setting Value 1,2)
2 D3 D2 reserved 3)
reserved 4)
1,2)
Up counter with enable input, Up /down counter with U / D input
3)
Frequency counter
4)
Gate time counter
750-638,
753-638
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 210: Counter Modules 750-638, 753-638

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 - S0 Status byte of Counter 1
2 - S1 Status byte of Counter 2
Manual
Version 1.1.1
Byte Designation
Offset Description
High Byte Low Byte
0 - C0 Control byte of Counter 1
2 - C1 Control byte of Counter 2
12.2.5.2 Pulse Width Modules
750-511, (and all variations),

753-511
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 211: Pulse Width Modules 750-511, /xxx-xxx, 753-511

Input and Output Process
Byte Designation
Offset Description
High Byte Low Byte
0 - C0/S0 Control/Status byte of Channel 1
1 D1 D0 Data Value of Channel 1
12.2.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-001, -002, -003),
750-653, (and the variations /000-002, -007),
753-650, -653
The process image of the / 003-000-variants depends on the parameterized

operating mode!
With the freely parameterizable variations /003 000 of the serial interface
modules, the desired operating 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
Manual
Version 1.1.1
Output Process Image, which have a total of 2 words mapped into each image.
Table 212: Serial Interface Modules with Alternative Data Format

Input and Output Process Image
Byte Designation
Offset Description
High Byte Low Byte
Control/status
0 D0 C/S Data byte
byte
1 D2 D1 Data bytes
12.2.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.
Table 213: Serial Interface Modules with Standard Data Format

Byte Designation
Offset Description
High Byte Low Byte
Control/status
0 D0 C/S Data byte
byte
1 D2 D1
Data bytes
2 D4 D3
12.2.5.5 Serial Interface Modules
750-652,
753-652
The size of the process image for the Serial Interface Module can be adjusted to
12, 24 or 48 bytes.
It consists of two status bytes (input) or control bytes (output) and the process
data with a size of 6 to 46 bytes.
Thus, each Serial Interface Module uses between 8 and 48 bytes in the process
image. The sizes of the input and output process images are always the same.
The process image sizes are set with the startup tool WAGO-I/O-CHECK.
Manual
Version 1.1.1
Table 214: Serial Interface Modules 750-652, 753-652
Process Byte Designation
image Offset Description
High Byte Low Byte
size
Control/Status byte Control/Status byte
0 C1/S1 C0/S0
C1/S1 C0/S0
8 bytes 1 D1 D0
2 D3 D2
3 D5 D4
4 D7 D6
24 bytes* … Prozess data (6-46 bytes)
11 D21 D20
12 D23 D22
48 bytes …
23 D45 D44
*) Factory setting
12.2.5.6 Data Exchange Module
750-654, -654/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.
Table 215: Data Exchange Module 750-654, -654/000-001

Byte Designation
Offset Description
High Byte Low Byte
0 D1 D0
Data bytes
1 D3 D2
12.2.5.7 SSI Transmitter Interface Modules
750-630, and the variations /000-001, -002, -006, -008, -009, -011, -012, -013
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.
Manual
Version 1.1.1
Table 216: SSI Transmitter Interface Modules
Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 D1 D0
Data bytes
1 D3 D2
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 217: SSI Transmitter Interface I/O Modules with an Alternative Data Format (/000-004, -005, -
007)
Input Process Image
Byte Destination
Offset Description
High Byte High Byte
0 - S not used Status byte
1 D1 D0
Data bytes
2 D3 D2
12.2.5.8 Incremental Encoder Interface Modules
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 218: Incremental Encoder Interface Modules 750-631/000-004, --010, -011

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
1 D1 D0 Counter word
2 - - not used
3 D4 D3 Latch word

Byte Designation
Offset Description
High Byte Low Byte
0 - C not used Control byte
1 D1 D0 Counter setting word
2 - - not used
3 - - not used
Manual
Version 1.1.1
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 219: Incremental Encoder Interface Modules 750-634

Input Process Image
Byte Designation
Offset Description
High Byte Low 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.

Byte Designation
Offset Description
High Byte Low Byte
1 D1 D0 Counter setting word
2 - -
not used
3 - -
750-637, (and all variations)
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 220: Incremental Encoder Interface Modules 750-637, (and all variations)
Byte Designation
Offset Description
High Byte Low Byte
Manual
Version 1.1.1
Digital Pulse Interface module
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 221: Digital Pulse Interface Modules 750-635, 753-635

Byte Designation
Offset Description
High Byte Low Byte
Control/status
0 D0 C0/S0 Data byte
byte
1 D2 D1 Data bytes
12.2.5.9 DC-Drive Controller
750-636, -636/000-700, -636/000-800
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 222: DC-Drive Controller 750-636, -636/000-700, -636/000-800

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 S1 S0 Status byte S1 Status byte S0
Actual position*) / Actual position
1 D1*) / S3**) D0*) / S2**) Extended status (LSB) / Extended
byte S3**) status byte S2**)
Actual position Actual position*) /
2 D3*) / S5**) D2*) / S4**) (MSB) / Extended Extended status
status byte S3**) byte S4**)
*) ExtendedInfo_ON = ‘0’.
**) ExtendedInfo_ON = ‘1’.
Manual
Version 1.1.1
Byte Designation
Offset Description
High Byte Low Byte
0 C1 C0 Control byte C1 Control byte C0
Setpoint position Setpoint position
1 D1 D0
(LSB)
Setpoint position Setpoint position
2 D3 D2
(MSB)
12.2.5.10 Stepper Controller
750-670, -671, -672
The Stepper controller provides the fieldbus coupler/controller 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 223: Stepper Controller 750-670, -671, -672

Byte Designation
Offset Description
High Byte Low Byte
Control/Status byte
0 Reserviert C0/S0 reserved
C0/S0
1 D1 D0
2 D3 D2 Process data*) / Mailbox**)
3 D5 D4
Control/Status byte Process data*) /
4 S3 D6
C3/S3 reserved**)
Control/Status byte Control/Status byte
5 C1/S1 C2/S2
C1/S1 C2/S2
*) Cyclic process image (Mailbox disabled)
**) Mailbox process image (Mailbox activated)
Manual
Version 1.1.1
12.2.5.11 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 224: RTC Module 750-640

Byte Designation
Offset Description
High Byte Low Byte
Control/status
0 ID C/S Command byte
byte
1 D1 D0
Data bytes
2 D3 D2
12.2.5.12 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 225: DALI/DSI Master Module 750-641

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 D0 S DALI Response Status byte
1 D2 D1 Message 3 DALI Address
2 D4 D3 Message 1 Message 2

Byte Designation
Offset Description
High Byte Low Byte
DALI command,
0 D0 C Control byte
DSI dimming value
1 D2 D1 Parameter 2 DALI Address
2 D4 D3 Command extension Parameter 1
Manual
Version 1.1.1
12.2.5.13 DALI Multi-Master Module
753-647
The DALI Multi-Master module occupies a total of 24 bytes in the input and
output range of the process image.
The DALI Multi-Master module can be operated in "Easy" mode (default) and
"Full" mode. "Easy" mode is used to transmit simply binary signals for lighting
control. Configuration or programming via DALI master module is unnecessary in
"Easy" mode.
Changes to individual bits of the process image are converted directly into DALI
commands for a pre-configured DALI network. 22 bytes of the 24-byte process
image can be used directly for switching of electronic ballasts (ECG), groups or
scenes in "Easy" mode. Switching commands are transmitted via DALI and group
addresses, where each DALI and each group address is represented by a 2-bit
pair.
In full mode, the 24 bytes of the process image are used to tunnel a protocol
using a mailbox interface. The process image consists of 1 byte for control /
status and 23 bytes for the acyclic data.
The structure of the process data is described in detail in the following tables.
Table 226: DALI Multi-Master Module 753-647 in the "Easy" Mode

Input Process Image
Byte Designation
Offset Note
High Byte Low Byte
res. Status, activate broadcast
Bit 0: 1-/2-button mode
0 - S
Bit 2: Broadcast status ON/OFF
Bit 1,3-7: -
1 DA4…DA7 DA0…DA3 Bit pair for DALI address DA0:
2 DA12…DA15 DA8…DA11 Bit 1: Bit set = ON
3 DA20…DA23 DA16…DA19 Bit not set = OFF
4 DA28…DA31 DA24…DA27 Bit 2: Bit set = Error
5 DA36…DA39 DA32…DA35 Bit not set = No error
6 DA44…DA47 DA40…DA43 Bit pairs DA1 … DA63 similar to DA0.
7 DA52…DA55 DA48…DA51
8 DA60…DA63 DA56…DA59
Bit pair for DALI group address GA0:
9 GA4…GA7 GA0…GA3 Bit 1: Bit set = ON
Bit not set = OFF
Bit 2: Bit set = Error
10 GA12…GA15 GA8…GA11 Bit not set = No error
Bit pairs GA1 … GA15 similar to GA0.
11 - - Not used
DA = DALI address
GA = Group address
Manual
Version 1.1.1
Byte Designation
Offset Note
High Byte Low Byte
res. Bit 0: Broadcast ON
Bit 1: Broadcast OFF
Bit 2: (1 button operation):
- short: Broadcast ON/OFF
- long: Broadcast dimming
brighter/darker
Bit 2: (2 buttons operation):
- long: Broadcast dimming brighter
0 - C
Bit 3: (1 button operation):
Broadcast ON/OFF
Bit 3: (2 buttons operation):
- long: Broadcast dimming darker
Bit 4: Watchdog toggling (starting
from FW06 of the DALI Multi-
Master)
Bit 5…7: reserved
1 DA4…DA7 DA0…DA3 Bit pair for DALI address:
2 DA12…DA15 DA8…DA11 Bit 1 (1 button operation):
3 DA20…DA23 DA16…DA19 - short: DA switch ON/OFF
- long: dimming brighter/darker
4 DA28…DA31 DA24…DA27
Bit 1 (2 buttons operation):
5 DA36…DA39 DA32…DA35 - short: DA switch ON
6 DA44…DA47 DA40…DA43 - long: dimming brighter
7 DA52…DA55 DA48…DA51 Bit 2 (1 button operation):
DA switch ON/OFF
8 DA60…DA63 DA56…DA59
- short: DA switch OFF
- long: dimming darker
9 GA4…GA7 GA0…GA3 Bit pair for DALI group address:
Bit 1 (1 button operation):
- short: GA switch ON/OFF
- long: dimming brighter/darker
- short: GA switch ON
10 GA12…GA15 GA8…GA11 - long: dimming brighter
Bit 2 (1 button operation):
GA switch ON/OFF
- short: GA switch OFF
- long: dimming darker
11 Bit 8…15 Bit 0…7 Switch scene 0…15
DA = DALI address
GA = Group address
Manual
Version 1.1.1
Table 227: DALI Multi-Master Module 753-647 in the "Full" Mode
Byte Designation
Offset Note
High Byte Low Byte
0 MBX_C/S C0/S0 Mailbox control/status byte control/status byte
1 MBX1 MBX0
2 MBX3 MBX2
3 MBX5 MBX4
4 MBX7 MBX6
5 MBX9 MBX8
6 MBX11 MBX10 Mailbox
7 MBX13 MBX12
8 MBX15 MBX14
9 MBX17 MBX16
10 MBX19 MBX18
11 MBX21 MBX20
Manual
Version 1.1.1
12.2.5.14 LON® FTT Module
753-648
The process image of the LON® FTT module consists of a control/status byte and
23 bytes of bidirectional communication data that is processed by the WAGO-I/O-
PRO function block "LON_01.lib". This function block is essential for the function
of the LON® FTT module and provides a user interface on the control side.
Table 228: LON® FTT Module 753-648

Byte Designation
Offset Note
High Byte Low Byte
0 MBX_C/S C0/S0 Mailbox control/status byte control/status byte
1 MBX1 MBX0
2 MBX3 MBX2
3 MBX5 MBX4
4 MBX7 MBX6
5 MBX9 MBX8
6 MBX11 MBX10 Mailbox
7 MBX13 MBX12
8 MBX15 MBX14
9 MBX17 MBX16
10 MBX19 MBX18
11 MBX21 MBX20
12.2.5.15 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
Table 229: EnOcean Radio Receiver 750-642

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 D0 S Data byte Status byte
1 D2 D1 Data bytes

Byte Destination
Offset Description
High Byte Low Byte
1 - - not used
Manual
Version 1.1.1
12.2.5.16 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
Table 230: MP Bus Master Module 750-643

Byte Destination
Offset Description
High Byte Low Byte
Extended
Control/status
0 C1/S1 C0/S0 Control/
byte
Status byte
1 D1 D0
2 D3 D2 Data bytes
3 D5 D4
12.2.5.17 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 one control byte (input) or status byte (output); an empty byte; an
overlay able 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/O-CHECK.
Manual
Version 1.1.1
Table 231: Bluetooth® RF-Transceiver 750-644
Process Byte Destination
High Byte Low Byte
size
Control/status
0 - C0/S0 not used
byte
12 bytes 1 D1 D0
… … …
5 D9 D8
6 D11 D10
Mailbox (0, 6, 12 or 18 words)/
24 bytes … … …
Process data (4 … 46 words)
11 D21 D20
12 D23 D22
48 bytes*) ... ... ...
23 D45 D44
*) Factory Setting
12.2.5.18 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.
Table 232: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645

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
Sensor input 2)
Data bytes
3 D3 D2
Control/status byte
Sensor input 1)
Data bytes
5 D5 D4
Control/status byte
Sensor input 2)
Data bytes
7 D7 D6
Manual
Version 1.1.1
12.2.5.19 Proportional Valve Module
750-632, -632/000-100
The size of the process image of the proportional valve modules depends on the
set operating mode. The operating mode with one valve occupies has a total of 6
data bytes in both the Input and Output Process Image, and the operating mode
with two valves occupies has a total of 12 data bytes in both the Input and Output
Process Image. The following tables illustrate the Input and Output Process
Images, which have 3 words mapped into each image for operating mode with
one valve and 6 words for operating mode with two valves. Word alignment is
applied.
Table 233: Proportional valve module operating mode with one valve 750-632, 753-632/000-100
Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 MBX_ST S0 Mailbox Status byte Status byte S0
1 V1 MBX_DATA Status byte V1 Mailbox
2 V1_ACTUAL_H V1_ACTUAL_L Process data

Byte Designation
Offset Description
High Byte Low Byte
0 MBX_CTRL C0 Mailbox control byteControl byte C0
1 V1 MBX_DATA Control byte V1 Mailbox
2 V1_ SETPOINTVALUE_H V1_SETPOINTVALUE_L Process data
Table 234: Proportional valve module operating mode with two valves 750-632, 753-632/000-100
Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 MBX_ST S0 Mailbox Status byte Status byte S0
1 MBX_DATA2 MBX_DATA1
Mailbox
3 V2 V1 Status byte V2 Status byte V1
4 V1_ACTUAL_H V1_ACTUAL_L
Process data
5 V2_ACTUAL_H V2_ACTUAL_L

Byte Designation
Offset Description
High Byte Low Byte
Mailbox control
0 MBX_CTRL C0 Control byte C0
byte
Mailbox
3 V2 V1 Control byte V2 Control byte V1
4 V1_ SETPOINTVALUE_H V1_SETPOINTVALUE_L
Process data
5 V2_ SETPOINTVALUE_H V2_SETPOINTVALUE_L
Manual
Version 1.1.1
12.2.5.20 M-Bus Master Module
753-649
The M-Bus master 753-649 has a cyclic 24 byte process image for the local bus
in both the Input and Output Process Image.
In addition to the control/status byte and the empty byte, an acyclic channel that
occupies 22 bytes of data is embedded in the process image for the process
communication.
For data access, the WAGO-IEC function blocks are available of the library
„MBUS_649_01.lib“.
The input and output data exchange is event-driven.
Table 235: M-BUS Master Module 753-649

Byte Designation
Offset Description
High Byte Low Byte
0 - C0/S0 Not used Control/Status byte
1 MBX0 MBX_C/S Mailbox Mailbox Control/Status byte
2 MBX2 MBX1
3 MBX4 MBX3
4 MBX6 MBX5
5 MBX8 MBX7
6 MBX10 MBX9
Mailbox
7 MBX12 MBX11
8 MBX14 MBX13
9 MBX16 MBX15
10 MBX18 MBX17
11 MBX20 MBX19
12.2.5.21 IO-Link Master
750-657
The process image size of the IO-Link master can be adjusted to the devices
(switches, IO-Link compatible devices, etc.) attached to the IO-Link ports.
Process image sizes of 4, 6, 8, 10, 12, 16, 20 or 24 bytes can be set.
As process data is exchanged, the process image has a fixed structure of a
control/status byte, Mailbox bytes and SIO byte regardless of the current
configuration.
The mailbox starts in the process image with an offset of 1 (after the control /
status byte) and occupies at least 2 bytes (FC0, MB0). The mailbox size can be
set to a maximum of x bytes (x = total PA size - 1 SIO byte - 1 control / status
byte) to configure the IO-Link master.
Depending on the set mailbox size, another data storage area is available behind
the SIO byte in which cyclical process data can be transferred from IO-Link
devices.
The mailbox and the process image sizes are set with the startup tool WAGO-
I/O-CHECK.
Manual
Version 1.1.1
Table 236: IO-Link Master 750-657
image Offset Descrition
High Byte Low Byte
size
Control/
0 FC0 C0/S0 Acyclic channel
4 bytes Status byte
1 SIO MB0 SIO byte Mailbox byte
6 bytes 2 D1 D0
8 bytes 3 D3 D2
10 bytes 4 D5 D4
12 bytes 5 D7 D6
6 D9 D8 Mailbox (0 … 20 bytes)/
16 bytes Process data (0 … 20 bytes)
7 D11 D10
8 D13 D12
20 bytes
9 D15 D14
10 D17 D16
24 bytes*
11 D19 D18
*) Factory Setting
12.2.5.22 CAN Gateway
750-658
The process image size of the CAN Gateway can be set in the specified sizes of
8, 12, 16, 20, 24, 32, 40 or 48 bytes.
The CAN Gateway has an acyclic communication channel (Mailbox) in the
process image.
This is used to transmit configuration, parameterization and diagnostic data.
The length of the first acyclic channel can be set between 2 and a maximum of
x bytes (x = total PA size - 3). This is followed by the CAN user data area, where
CAN telegrams are transmitted via the "Mailbox 2.0" communication mechanism
in the operating modes "Sniffer Mode" and "Transparent Mode". In the operating
mode "Mapped Mode", in this area transmitted and received CAN telegrams can
be mapped to the process image without using any protocoll.
The operating mode and also the mailbox and the process image sizes are set
with the startup tool WAGO-I/O-CHECK.
Table 237: CAN Gateway 750-658

image Offset Descrition
High Byte Low Byte
size
Control/
0 C/D_MBX C0/S0 Config/Diag Mailbox
Status byte
1 C/D_MBX / CAN_X C/D_MBX Config/Diag Mailbox
8 bytes
(1 … 44 bytes)/
2 C/D_MBX / CAN_X C/D_MBX / CAN_X
CAN user data Mailbox
3 C/D_MBX / CAN_X C/D_MBX / CAN_X (5 … 45 bytes) **)
4 C/D_MBX / CAN_X C/D_MBX / CAN_X bzw.
12 bytes Toggle-Byte +CAN-Nutzdaten
(4 44 B t ) ***)
Manual
Version 1.1.1
16 bytes
20 bytes
24 bytes *
32 bytes …
40 bytes …
48 bytes
23 CAN_X CAN_X
*) Factory Setting
**) Operating mode „Sniffer Mode“ and operating mode „Transparent Mode“
***) Operating mode „Mapped Mode“
12.2.5.23 Servo Stepper Controller
750-673
The stepper servo provides the fieldbus coupler / controller with a 12-byte input
and output process image via 1 logical channel.
The data to be sent and received is stored in up to 7 output bytes (D0 ... D6) and
7 input bytes (D0 ... D6) depending on the operating mode. The output byte D0
and the input byte D0 are reserved and without function.
A local bus control and status byte (C0, S0) as well as 3 control and status bytes
for the application (C1 ... C3, S1 ... S3) are used to control the data flow.
The changeover between both process images takes place via bit 5 in control
byte C0 (C0.5). Bit 5 of the status byte S0 (S0.5) acknowledges the activation of
the mailbox.
Table 238: Servo Stepper Controller 750-673

Byte Designation
Offset Description
High Byte Low Byte
Control/status byte
0 reserved C0/S0 reserved
C0/S0
1 D1 D0
2 D3 D2 Process data*) / Mailbox**)
3 D5 D4
Control/status byte Process data*) /
4 C3/S3 D6
C3/S3 reserved**)
Control/status byte Control/status byte
5 C1/S1 C2/S2
C1/S1 C2/S2
*) Cyclic process image (Mailbox deactivated)
**) Mailbox process image (Mailbox activated)
Manual
Version 1.1.1
12.2.5.24 SMI Master Module
753-1630, -1631
The 753-1630 I/O module has a cyclic 12 byte process image for the local bus in
both the Input and Output Process Image.
Process data communication with the SMI master module is conducted in
fieldbus coupler mode via a cyclic process image and in Full mode via the
Mailbox 2.0 protocol.
Byte 0 of the process image contains the control/status byte and byte 1 the
extended control/status byte. Depending on the control/status byte, bytes 2 to 11
contain data from Mailbox 2.0 or the cyclic process image.
The changeover between Mailbox 2.0 and the cyclic process image takes place
via bit 5 in control byte C0 (C0.5). Bit 5 of the status byte S0 (S0.5)
acknowledges the activation of the mailbox.
Tabelle 239:SMI Master Module 753-1630, -1631 in Fieldbus Coupler Mode

Input Process Image
Byte Designation
Offset Description
High Byte Low Byte
0 S1 S0 Extended status byte Status byte
1 - -
Not used
2 - -
3 D5 D4 Reflection of the group mask bit 0…15
4 D7 D6 Response to the command
5 D9 D8 Shutter actual position Slat actual position

Byte Designation
Offset Description
High Byte Low Byte
0 C1 C0 Extended control byte Control byte
2-button operation 2-button operation
upwards upwards
1 D1 D0 Bit 0: Address 8 Bit 0: Address 0
… … … …
Bit 7: Address 15 Bit 7: Address 7
2-button operation 2-button operation
downwards downwards
2 D3 D2 Bit 0: Address 8 Bit 0: Address 0
… … … …
Bit 7: Address 15 Bit 7: Address 7
3 D5 D4 Group mask bit 0...15
4 D7 D6 Commands
5 D9 D8 Shutter target position Slat target position
Table 240: SMI Master Module 753-1630, -1631 in „Full Mode“

Byte Designation
Offset Description
High Byte Low Byte
Manual
Version 1.1.1
Extended
0 S1/C1 S0/C0 Control/Status byte
Control/Status byte
1 MBX0 MBX_C/S Mailbox Mailbox Control/Status byte
2 MBX2 MBX1
3 MBX4 MBX3
4 MBX6 MBX5
5 MBX8 MBX7
6 MBX10 MBX9
Mailbox
7 MBX12 MBX11
8 MBX14 MBX13
9 MBX16 MBX15
10 MBX18 MBX17
11 MBX20 MBX19
12.2.5.25 AS-interface Master Module
750-655,
753-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 46 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/O-CHECK.
Table 241: AS-interface Master Module 750-655, 753-655

High Byte Low Byte
size
Control-/
0 - C0/S0 Not used
Status byte
12 bytes 1 D1 D0
…
5 D9 D8 Mailbox (0, 6, 10, 12 or 18 bytes)/
6 D11 D10 Process data (0-46 bytes)
20 bytes …
9 D17 D16
Manual
Version 1.1.1
10 D19 D18
24 bytes *
11 D21 D20
12 D23 D22
32 bytes …
15 D29 D28
16 D31 D30
40 bytes …
19 D37 D36
12 D39 D38
48 bytes …
23 D45 D44
*) Factory Setting
Manual
Version 1.1.1
12.2.5.26 System Modules
12.2.5.27 System Modules with Diagnostics
750-606
The modules provide 2 bits of diagnostics in the Input Process Image for
monitoring of the internal power supply.
Table 242: System Modules with Diagnostics 750-606, -611

Input Process Image
Diagnostics Diagnostics
bit S_out bit S_in
750-610, -611
The modules provide 2 bits of diagnostics in the Input Process Image for
monitoring of the internal power supply.
Table 243: System Modules with Diagnostics 750-610, -611

Input Process Image
Diagnostics Diagnostics
bit S 2 bit S 1
Fuse Fuse
12.2.5.28 Filter Module
750-624/020-002, -626/020-002
The Filter Module 750-624/020-002 and 750-626/020-002 equipped with surge

suppression for the field side power supply have a total of 8 bits in both the Input
and Output Process Image.
Table 244: Filter Modules 750-624/020-002, 750-626/020-002

Input Process Image
0V_MA 0V_PA 24V_MA 24V_PA not used PWR_DIAG not used VAL

not used not used not used not used not used not used not used GFT
Manual
Version 1.1.1
12.2.5.29 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 245: Binary Space Module 750-622 (with Behavior like 2 Channel Digital Input)
(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
Manual
Version 1.1.1
WAGO I/O System 750 Application Examples 253
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.
A free of charge demo version from ModScan32 and further utilities from Win-
Tech 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.
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.
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.
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.
Manual
Version 1.1.1
254 Application Examples WAGO I/O System 750
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.1
WAGO I/O System 750 Application Examples 255
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 246: 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: i.e. 0 0000 1

• Reading/writing the second analog input: 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 45: Example SCADA Software with Modbus Driver
Please refer to the respective SCADA product manual for a detailed description
of the particular software operation.
Manual
Version 1.1.1
256 Use in Hazardous Environments WAGO I/O System 750
14 Use in Hazardous Environments

The WAGO I/O System 750 (electrical equipment) is designed for use in Zone 2
hazardous areas and shall be used in accordance with the marking and
installation regulations.
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.1
WAGO I/O System 750 Use in Hazardous Environments 257
14.1 Marking Configuration Examples
14.1.1 Marking for Europe According to ATEX and IECEx
Figure 46: Marking Example According to ATEX and IECEx
Figure 47: Text Detail – Marking Example According to ATEX and IECEx
Manual
Version 1.1.1
Table 247: Description of Marking Example According to ATEX and IECEx
Marking Description
TUEV 07 ATEX 554086 X Approving authority resp. certificate numbers
IECEx TUN 09.0001 X
Dust
II Equipment group: All except mining
3D Category 3 (Zone 22)
Ex Explosion protection mark
tc Type of protection: Protection by enclosure
IIIC Explosion group of dust
T135°C Max. surface temperature of the enclosure
(without a dust layer)
Dc Equipment protection level (EPL)
Mining
I Equipment group: Mining
M2 Category: High level of protection
d Type of protection: Flameproof enclosure
I Explosion group for electrical equipment for
mines susceptible to firedamp
Mb Equipment protection level (EPL)
Gases
3G Category 3 (Zone 2)
nA Type of protection: Non-sparking equipment
IIC Explosion group of gas and vapours
T4 Temperature class: Max. surface temperature
135 °C
Gc Equipment protection level (EPL)
Manual
Version 1.1.1
Figure 48: Marking Example for Approved I/O Module Ex i According to ATEX and IECEx
Figure 49: Text Detail – Marking Example for Approved I/O ModuleEx i According to ATEX and
IECEx
Manual
Version 1.1.1
Table 248: Description of Marking Example for Approved I/O Module Ex I According to ATEX and
IECEx
Marking Description
TUEV 12 ATEX 106032 X Approving authority resp. certificate numbers
IECEx TUN 12 0039 X
Dust
3 (1) D Category 3 (Zone 22) equipment containing a safety
device for a category 1 (Zone 20) equipment
tc Type of protection: Protection by enclosure
[ia Da] Type of protection and equipment protection level
(EPL): Associated apparatus with intrinsic safety
circuits for use in Zone 20
IIIC Explosion group of dust
T135°C Max. surface temperature of the enclosure
(without a dust layer)
Dc Equipment protection level (EPL)
Mining
I Equipment Group: Mining
M2 (M1) Category: High level of protection with electrical
circuits which present a very high level of protection
d Type of protection: Flameproof enclosure
[ia Ma] Type of protection and equipment protection level
electrical circuits
I Explosion group for electrical equipment for mines
susceptible to firedamp
Mb Equipment protection level (EPL)
Gases
3 (1) G Category 3 (Zone 2) equipment containing a safety
device for a category 1 (Zone 0) equipment
ec Equipment protection by increased safety “e”
[ia Ga] Type of protection and equipment protection level
circuits for use in Zone 0
IIC Explosion group of gas and vapours
T4 Temperature class: Max. surface temperature
135 °C
Manual
Version 1.1.1
14.1.2 Marking for the United States of America (NEC) and Canada
(CEC)
Figure 50: Marking Example According to NEC
Figure 51: Text Detail – Marking Example According to NEC 500
Table 249: Description of Marking Example According to NEC 500

Marking Description
CL I Explosion protection (gas group)
DIV 2 Area of application
Grp. A B C D Explosion group (gas group)
op temp code T4 Temperature class
Manual
Version 1.1.1
Figure 52: Text Detail – Marking Example for Approved I/O Module Ex i According to NEC 505
Table 250: Description of Marking Example for Approved I/O Module Ex i According to NEC 505
Marking Description
CI I, Explosion protection group
Zn 2 Area of application
AEx Explosion protection mark
nA Type of protection
[ia Ga] Type of protection and equipment protection
level (EPL): Associated apparatus with intrinsic
safety circuits for use in Zone 20
IIC Group
T4 Temperature class
Figure 53: Text Detail – Marking Example for Approved I/O Module Ex i According to NEC 506
Table 251: Description of Marking Example for Approved I/O Module Ex i According to NEC 506
Marking Description
CI I, Explosion protection group
Zn 2 Area of application
AEx Explosion protection mark
[ia IIIC] Type of protection and equipment protection
IIC Group
Manual
Version 1.1.1
Figure 54: Text Detail – Marking Example for Approved I/O Module Ex i According to CEC 18
attachment J
Table 252: Description of Marking Example for Approved I/O Module Ex i According to CEC 18
attachment J
Marking Description
Dust
[ia IIIC] Type of protection and equipment protection
IIC Group
X Symbol used to denote specific conditions of use
Gases
[ia Ga] Type of protection and equipment protection
IIC Group
X Symbol used to denote specific conditions of use
Manual
Version 1.1.1
14.2 Installation Regulations

For the installation and operation of electrical equipment in hazardous areas, the
valid national and international rules and regulations which are applicable at the
installation location must be carefully followed.
14.2.1 Special Notes including Explosion Protection

The following warning notices are to be posted in the immediately proximity of the
WAGO I/O System 750 (hereinafter “product”):
WARNING – DO NOT REMOVE OR REPLACE FUSED WHILE ENERGIZED!
WARNING – DO NOT DISCONNECT WHILE ENERGIZED!
WARNING – ONLY DISCONNECT IN A NON-HAZARDOUS AREA!
Before using the components, check whether the intended application is

permitted in accordance with the respective printing. Pay attention to any
changes to the printing when replacing components.
The product is an open system. As such, the product must only be installed in
appropriate enclosures or electrical operation rooms to which the following
applies:
• Can only be opened using a tool or key
• Inside pollution degree 1 or 2
• In operation, internal air temperature within the range of 0 °C ≤ Ta ≤ +55 °C

or −20 °C ≤ Ta ≤ +60 °C for components with extension number …/025-xxx
or −40 °C ≤ Ta ≤ +70 °C for components with extension number …/040-xxx
• Minimum degree of protection: min. IP54 (acc. to EN/IEC 60529)
• For use in Zone 2 (Gc), compliance with the applicable requirements of the
standards EN/IEC/ABNT NBR IEC 60079-0, -7, -11, -15
• For use in Zone 22 (Dc), compliance with the applicable requirements of

the standards EN/IEC/ABNT NBR IEC 60079-0, -7, -11, -15 and -31
• For use in mining (Mb), minimum degree of protection IP64 (acc. EN/IEC
60529) and adequate protection acc. EN/IEC/ABNT NBR IEC 60079-0 and
-1
• Depending on zoning and device category, correct installation and

compliance with requirements must be assessed and certified by a “Notified
Body” (ExNB) if necessary!
Manual
Version 1.1.1
Explosive atmosphere occurring simultaneously with assembly, installation or
repair work must be ruled out. Among other things, these include the following
activities
• Insertion and removal of components
• Connecting or disconnecting from fieldbus, antenna, D-Sub, ETHERNET or

USB connections, DVI ports, memory cards, configuration and
programming interfaces in general and service interface in particular:
• Operating DIP switches, coding switches or potentiometers
• Replacing fuses
Wiring (connecting or disconnecting) of non-intrinsically safe circuits is only

permitted in the following cases
• The circuit is disconnected from the power supply.
• The area is known to be non-hazardous.
Outside the device, suitable measures must be taken so that the rated voltage is
not exceeded by more than 40 % due to transient faults (e.g., when powering the
field supply).
Product components intended for intrinsically safe applications may only be

powered by 750-606 or 750-625/000-001 bus supply modules.
Only field devices whose power supply corresponds to overvoltage category I or

II may be connected to these components.
Manual
Version 1.1.1
14.2.2 Special Notes Regarding ANSI/ISA Ex

For ANSI/ISA Ex acc. to UL File E198726, the following additional requirements
apply:
• Use in Class I, Division 2, Group A, B, C, D or non-hazardous areas only
• ETHERNET connections are used exclusively for connecting to computer

networks (LANs) and may not be connected to telephone networks or
telecommunication cables
• WARNING – The radio receiver module 750-642 may only be used to

connect to external antenna 758-910!
• WARNING – Product components with fuses must not be fitted into circuits
subject to overloads!
These include, e.g., motor circuits.
• WARNING – When installing I/O module 750-538, “Control Drawing No.

750538” in the manual must be strictly observed!
Proof of certification is available on request.
Also take note of the information given on the operating and assembly
instructions.
The manual, containing these special conditions for safe use, must be readily
available to the user.
Manual
Version 1.1.1
WAGO I/O System 750 Appendix 267
15 Appendix
15.1 MIB II Groups
15.1.1 System Group
The system group contains general information about the coupler/controller.
Table 253: MIB II – System Group

Identifier Entry Access Description
1.3.6.1.2.1.1.1 sysDescr R This entry contains the device identification. The
object has a fixed code (e.g., "WAGO 750-841")
1.3.6.1.2.1.1.2 sysObjectID R This entry contains the manufacturer's authorization
identification.
1.3.6.1.2.1.1.3 sysUpTime R This entry contains the time (in hundredths of a
second) since the management unit has been last
reset.
1.3.6.1.2.1.1.4 sysContakt R/W This entry contains the identification and contact
information for the system contact person.
1.3.6.1.2.1.1.5 sysName R/W This entry contains the administration-assigned
device name.
1.3.6.1.2.1.1.6 sysLocation R/W This entry contains the node’s physical location.
1.3.6.1.2.1.1.7 sysServices R This entry designates the quantity of services that this
coupler/controller contains.
Manual
Version 1.1.1
268 Appendix WAGO I/O System 750
15.1.2 Interface Group

The interface group contains information and statistics about the device interface.
A device interface describes the Ethernet interface of a coupler/controller and

provides status information on the physical Ethernet ports as well as on the
internal loopback interface.
Table 254: MIB II – Interface Group

1.3.6.1.2.1.2.1 ifNumber R Number of network interfaces in this system
1.3.6.1.2.1.2.2 ifTable - List of network interfaces
1.3.6.1.2.1.2.2.1 ifEntry - Network interface entry
1.3.6.1.2.1.2.2.1.1 ifIndex R This entry contains a unique value for each
interface
1.3.6.1.2.1.2.2.1.2 ifDescr R This entry contains the name of the
manufacturer, the product name, and the
version of the hardware interface:
e.g., "WAGO Kontakttechnik GmbH 750-841:
Rev 1.0"
1.3.6.1.2.1.2.2.1.3 ifType R This entry describes the type of interface.
ETHERNET CSMA/CD =6
Software Loopback = 24
1.3.6.1.2.1.2.2.1.4 ifMtu R This entry specifies the largest transfer unit;
i.e., the maximum telegram length that can be
transferred via this interface.
1.3.6.1.2.1.2.2.1.5 ifSpeed R This entry indicates the interface speed in bits

per second.
1.3.6.1.2.1.2.2.1.6 ifPhysAddress R This entry indicates the physical address of
the interface. For example, for Ethernet, this
entry contains a MAC ID.
1.3.6.1.2.1.2.2.1.7 ifAdmin-Status R/W This entry specifies the desired state of the
interfaces. Possible values are:
up(1): Ready for operation for
transmission and reception
down(2): Interface is switched off
testing(3): Interface is in test mode
1.3.6.1.2.1.2.2.1.8. ifOperStatus R This entry indicates the current operational
state of the interface.
1.3.6.1.2.1.2.2.1.9. ifLastChange R This entry indicates the value of the
sysUpTime when the state was last changed.
1.3.6.1.2.1.2.2.1.10 ifInOctets R This entry gives the total number of bytes
received via interface.
1.3.6.1.2.1.2.2.1.11 ifInUcastPkts R This entry indicates the number of received
unicast packets delivered to a higher layer.
1.3.6.1.2.1.2.2.1.12 ifInNUcastPkts R This entry indicates the number of received
broad and multicast packets delivered to a
higher layer.
1.3.6.1.2.1.2.2.1.13 ifInDiscards R This entry indicates the number of packets
that were discarded even though no errors
had been detected.
1.3.6.1.2.1.2.2.1.14 ifInErrors R This entry indicates the number of received
packets that contained errors preventing them
from being deliverable to a higher layer.
Manual
Version 1.1.1
Table 254: MIB II – Interface Group
1.3.6.1.2.1.2.2.1.15 IfInUnknown- R This entry indicates the number of received
Protos packets sent to an unknown or unsupported
port number.
1.3.6.1.2.1.2.2.1.16 ifOutOctets R This entry gives the total number of bytes sent
via interface.
1.3.6.1.2.1.2.2.1.17 ifOutUcastPkts R This entry contains the number of outgoing
unicast packets delivered to a higher layer.
1.3.6.1.2.1.2.2.1.18 ifOutNUcastPkts R This entry indicates the number of outgoing
broad and multicast packets delivered to a
higher layer.
1.3.6.1.2.1.2.2.1.19 ifOutDiscards R This entry indicates the number of packets
that were discarded even though no errors
had been detected.
1.3.6.1.2.1.2.2.1.20 ifOutErrors R This entry indicates the number of packets
that could not be transmitted because of
errors.
Manual
Version 1.1.1
15.1.3 IP Group
The IP group contains information about IP communication.
Table 255: MIB II – IP Group

1.3.6.1.2.1.4.1 ipForwarding R/W 1: Host is a router; 2: Host is not a router
1.3.6.1.2.1.4.2 ipDefaultTTL R/W Default value for the Time-To-Live field of each
IP frame.
1.3.6.1.2.1.4.3 ipInReceives R Number of received IP frames, including those
received in error.
1.3.6.1.2.1.4.4 ipInHdrErrors R Number of received IP frames with header
errors.
.3.6.1.2.1.4.5 ipInAddrErrors R Number of received IP frames with a
misdirected IP address.
1.3.6.1.2.1.4.6 ipForwDatagrams R Number of received IP frames passed on
(routed)
1.3.6.1.2.1.4.7 ipUnknownProtos R Number of received IP frames with an unknown
protocol type.
1.3.6.1.2.1.4.8 ipInDiscards R Number of received IP frames rejected
although no disturbance was present.
1.3.6.1.2.1.4.9 ipInDelivers R Number of received IP frames passed on a
higher protocol layer.
1.3.6.1.2.1.4.10 ipOutRequests R Number of sent IP frames
1.3.6.1.2.1.4.11 ipOutDiscards R Number of rejected IP Frames that should have
been sent.
1.3.6.1.2.1.4.12 ipOutNoRoutes R Number of sent IP frames rejected because of
incorrect routing information.
1.3.6.1.2.1.4.13 ipReasmTimeout R Minimum time duration until an IP frame is re-
assembled.
1.3.6.1.2.1.4.14 ipReasmReqds R Minimum number of the IP fragments for
building up and passing on.
1.3.6.1.2.1.4.15 ipReasmOKs R Number of IP frames re-assembled
successfully.
1.3.6.1.2.1.4.16 ipReasmFails R Number of IP frames not re-assembled
successfully.
1.3.6.1.2.1.4.17 ipFragOKs R Number of IP frames fragmented and passed
on.
1.3.6.1.2.1.4.18 ipFragFails R Number of IP frames that should have been
fragmented but could not be, because their
don't fragment bit was set in the header.
1.3.6.1.2.1.4.19 ipFragCreates R Number of generated IP fragment frames
1.3.6.1.2.1.4.20 ipAddrTable - Table of all local IP addresses of the
coupler/controller.
1.3.6.1.2.1.4.20.1 ipAddrEntry - Address information for an entry
1.3.6.1.2.1.4.20.1.1 ipAdEntAddr R The IP address corresponding to the entry’s
address information
1.3.6.1.2.1.4.20.1.2 ipAdEntIfIndex R Index of the interface
1.3.6.1.2.1.4.20.1.3 ipAdEntNetMask R The entry's associated subnet mask
1.3.6.1.2.1.4.20.1.4 ipAdEntBcastAddr R Value of the last significant bit in the IP
broadcast address
1.3.6.1.2.1.4.20.1.5 IpAdEntReasm- R The size of the longest IP telegram that can be
MaxSize defragmented (reassembled) again.
1.3.6.1.2.1.4.23 ipRoutingDiscards R Number of deleted routing entries
Manual
Version 1.1.1
15.1.4 IpRoute Table Group

The IP route table contains information about the routing table in the
coupler/controller.
Table 256: MIB II – IpRoute Table Group

1.3.6.1.2.1.4.21 ipRouteTable - IP routing table
1.3.6.1.2.1.4.21.1 ipRouteEntry - A routing entry for a particular destination
1.3.6.1.2.1.4.21.1.1 ipRouteDest R/W This entry indicates the destination address of
the routing entry
1.3.6.1.2.1.4.21.1.2 ipRouteIfIndex R/W This entry indicates the index of the interface,
which is the next route destination
1.3.6.1.2.1.4.21.1.3 ipRouteMetric1 R/W The primary route to the target system
1.3.6.1.2.1.4.21.1.4 ipRouteMetric2 R/W An alternative route to the target system
.3.6.1.2.1.4.21.1.7 ipRouteNextHop R/W The IP address of the next route section
1.3.6.1.2.1.4.21.1.8 ipRouteType R/W The route type
1.3.6.1.2.1.4.21.1.9 ipRouteProto R Routing mechanism via which the route is
developed
1.3.6.1.2.1.4.21.1.10 ipRouteAge R/W Number of seconds since then the route was
last renewed/examined
1.3.6.1.2.1.4.21.1.11 ipRouteMask R/W This entry contents the subnet mask for this
entry
1.3.6.1.2.1.4.21.1.13 ipRouteInfo R/W A reference to a special MIB
Manual
Version 1.1.1
15.1.5 ICMP Group

Table 257: MIB II – ICMP Group
1.3.6.1.2.1.5.1 icmpInMsgs R Number of received ICMP messages
1.3.6.1.2.1.5.2 icmpInErrors R Number of received ICMP errors containing
ICMP-specific errors
1.3.6.1.2.1.5.3 icmpInDestUnreachs R Number of received ICMP destination
unreachable messages
1.3.6.1.2.1.5.4 icmpInTimeExcds R Number of received ICMP time exceeded
messages
1.3.6.1.2.1.5.5 icmpInParmProbs R Number of received ICMP parameter problem
messages
1.3.6.1.2.1.5.6 icmpInSrcQuenchs R Number of received ICMP source quench
messages
1.3.6.1.2.1.5.7 icmpInRedirects R Number of received ICMP redirect messages
1.3.6.1.2.1.5.8 icmpInEchos R Number of received ICMP echo request
messages (Ping)
1.3.6.1.2.1.5.9 icmpInEchoReps R Number of received ICMP echo reply messages
(Ping)
1.3.6.1.2.1.5.10 icmpInTimestamps R Number of received ICMP timestamp request
messages
1.3.6.1.2.1.5.11 icmpInTimestampReps R Number of received ICMP timestamp reply
messages
1.3.6.1.2.1.5.12 icmpInAddrMasks R Number of received ICMP address mask request
messages
1.3.6.1.2.1.5.13 icmpInAddrMaskReps R Number of received ICMP address mask reply
messages
1.3.6.1.2.1.5.14 icmpOutMsgs R Number of sent ICMP messages
1.3.6.1.2.1.5.15 icmpOutErrors R Number of sent ICMP messages that could not
be sent due to errors
1.3.6.1.2.1.5.16 icmpOutDestUnreachs R Number of sent ICMP destination unreachable
messages
1.3.6.1.2.1.5.17 icmpOutTimeExcds R Number of sent ICMP time exceeded messages
1.3.6.1.2.1.5.18 icmpOutParmProbs R Number of sent ICMP parameter problem
messages
1.3.6.1.2.1.5.19 icmpOutSrcQuenchs R Number of sent ICMP source quench messages
1.3.6.1.2.1.5.20 icmpOutRedirects R Number of sent ICMP redirection messages
1.3.6.1.2.1.5.21 icmpOutEchos R Number of sent ICMP echo request messages
1.3.6.1.2.1.5.22 icmpOutEchoReps R Number of sent ICMP echo reply messages
1.3.6.1.2.1.5.23 icmpOutTimestamps R Number of sent ICMP timestamp request
messages
1.3.6.1.2.1.5.24 icmpOutTimestampReps R Number of sent ICMP timestamp reply messages
1.3.6.1.2.1.5.25 icmpOutAddrMasks R Number of sent ICMP address mask request
messages
1.3.6.1.2.1.5.26 icmpOutAddrMaskReps R Number of sent ICMP address mask reply
messages
Manual
Version 1.1.1
15.1.6 TCP Group

Table 258: MIB II – TCP Group
1.3.6.1.2.1.6.1 tcpRtoAlgorithm R Retransmission time: 1 = other,
2 = constant, 3 = RSRE, 4 = VANJ
1.3.6.1.2.1.6.2 tcpRtoMin R Minimum value for the retransmission timer
1.3.6.1.2.1.6.3 tcpRtoMax R Maximum value for the retransmission
timer
1.3.6.1.2.1.6.4 tcpMaxConn R Number of maximum TCP connections that
can exist simultaneously
1.3.6.1.2.1.6.5 tcpActiveOpens R Number of existing active TCP connections
1.3.6.1.2.1.6.6 tcpPassiveOpens R Number of existing passive TCP
connections
1.3.6.1.2.1.6.7 tcpAttemptFails R Number of failed connection attempts
1.3.6.1.2.1.6.8 tcpEstabResets R Number of connection resets
1.3.6.1.2.1.6.9 tcpCurrEstab R The number of TCP connections for which
the current state is either Established or
Close-Wait
1.3.6.1.2.1.6.10 tcpInSegs R Number of received TCP frames including
the error frames
1.3.6.1.2.1.6.11 tcpOutSegs R Number of correctly sent TCP frames with
data
1.3.6.1.2.1.6.12 tcpRetransSegs R Number of sent TCP frames retransmitted
because of errors
1.3.6.1.2.1.6.13 tcpConnTable - For each existing connection, a table entry
is created
1.3.6.1.2.1.6.13.1 tcpConnEntry - Table entry for connection
1.3.6.1.2.1.6.13.1.1 tcpConnState R This entry indicates the status of the TCP
connection
1.3.6.1.2.1.6.13.1.2 tcpConnLocalAddress R The entry contains the IP address for the
connection. For a server, this entry is
constant 0.0.0.0
1.3.6.1.2.1.6.13.1.3 tcpConnLocalPort R The entry indicates the port number of the
TCP connection.
1.3.6.1.2.1.6.13.1.4 tcpConnRemAddress R The entry contains the remote IP address
of the TCP connection.
1.3.6.1.2.1.6.13.1.5 tcpConnRemPort R The entry contains the remote port of the
TCP connection.
1.3.6.1.2.1.6.14 tcpInErrs R Number of received incorrect TCP frames
1.3.6.1.2.1.6.15 tcpOutRsts R Number of sent TCP frames with set RST
flag
Manual
Version 1.1.1
15.1.7 UDP Group

Table 259: MIB II – UDP Group
1.3.6.1.2.1.7.1 udpInDatagrams R Number of received UDP frames that could be
passed on to the appropriate applications
1.3.6.1.2.1.7.2 udpNoPorts R Number of received UDP frames that could not
be passed on to the appropriate applications
(port unreachable)
1.3.6.1.2.1.7.3 udpInErrors R Number of received UDP frames that could not
be passed on to the appropriate applications for
other reasons.
1.3.6.1.2.1.7.4 udpOutDatagrams R Number of sent UDP frames
1.3.6.1.2.1.7.5 udpTable - A table entry is created for each application that
received UDP frames
1.3.6.1.2.1.7.5.1 udpEntry - Table entry for an application that received an
UDP frame
1.3.6.1.2.1.7.5.1.1 udpLocalAddress R IP address of the local UDP server
1.3.6.1.2.1.7.5.1.2 udpLocalPort R Port number of the local UDP server
Manual
Version 1.1.1
15.1.8 SNMP Group

Table 260: MIB II – SNMP Group
1.3.6.1.2.1.11.1 snmpInPkts R Number of received SNMP frames
1.3.6.1.2.1.11.2 snmpOutPkts R Number of sent SNMP frames
1.3.6.1.2.1.11.3 snmpInBadVersions R Number of received SNMP frames with an invalid
version number
1.3.6.1.2.1.11.4 snmpInBadCommunity- R Number of received SNMP frames with an invalid
Names community
1.3.6.1.2.1.11.5 snmpInBadCommunity R Number of received SNMP frames whose
Uses community did not have sufficient authorization for
the actions that it tried to execute
1.3.6.1.2.1.11.6 snmpInASNParseErrs R Number of received SNMP frames with an
incorrect structure
1.3.6.1.2.1.11.8 snmpInTooBigs R Number of received SNMP frames that
acknowledged the result too Big
1.3.6.1.2.1.11.9 snmpInNoSuchNames R Number of received SNMP frames that
acknowledged the result noSuchName
1.3.6.1.2.1.11.10 snmpInBadValues R Number of received SNMP frames that
acknowledged the result bad value
1.3.6.1.2.1.11.11 snmpInReadOnlys R Number of received SNMP frames that
acknowledged the result readOnly
1.3.6.1.2.1.11.12 snmpInGenErrs R Number of received SNMP frames that
acknowledged the result genError
1.3.6.1.2.1.11.13 snmpInTotalReqVars R Number of received SNMP frames with valid GET
or GET-NEXT requests
1.3.6.1.2.1.11.14 snmpInTotalSetVars R Number of received SNMP frames with valid SET
requests
1.3.6.1.2.1.11.15 snmpInGetRequests R Number of GET requests received and processed
1.3.6.1.2.1.11.16 snmpInGetNexts R Number of GET-NEXT requests received and
processed
1.3.6.1.2.1.11.17 snmpInSetRequests R Number of SET requests received and processed
1.3.6.1.2.1.11.18 snmpInGetResponses R Number of received GET responses
1.3.6.1.2.1.11.19 snmpInTraps R Number of received traps
1.3.6.1.2.1.11.20 snmpOutTooBigs R Number of sent SNMP frames that contained the
result too Big
1.3.6.1.2.1.11.21 snmpOutNoSuchNames R Number of sent SNMP frames that contained the
result noSuchName
1.3.6.1.2.1.11.22 snmpOutBadValues R Number of sent SNMP frames that contained the
result bad value
1.3.6.1.2.1.11.24 SnmpOutGenErrs R Number of sent SNMP frames that contained the
result genErrs
1.3.6.1.2.1.11.25 snmpOutGetRequests R Number of GET requests sent
1.3.6.1.2.1.11.26 SnmpOutGetNexts R Number of GET NEXT requests sent
1.3.6.1.2.1.11.27 snmpOutSetRequests R Number of SET requests sent
1.3.6.1.2.1.11.28 snmpOutGetResponses R Number of GET responses sent
1.3.6.1.2.1.11.29 snmpOutTraps R Number of traps sent
1.3.6.1.2.1.11.30 snmpEnableAuthenTraps R/W Authentification failure traps(1 = on, 2 = off )
Manual
Version 1.1.1
15.2 WAGO MIB Groups

15.2.1 Company Group
The company group contains general information about the company WAGO
Kontakttechnik GmbH & Co. KG.
Table 261: WAGO MIB – Company Group

1.3.6.1.4.1.13576.1.1 wagoName R Company’s registered name
Default value: "WAGO Kontakttechnik
GmbH & Co. KG"
1.3.6.1.4.1.13576.1.2 wagoDescrition R Description of company
Default value: "WAGO Kontakttechnik
GmbH & Co. KG, Hansastr. 27,
D-32423 Minden"
1.3.6.1.4.1.13576.1.3 wagoURL R URL for company web site
Default value: "www.wago.com"
15.2.2 Product Group

The product group contains information about the product.
Table 262: WAGO MIB – Product Group

1.3.6.1.4.1.13576.10.1.1 wioArticleName R Name of article
Default value: "750-xxx/000-000"
1.3.6.1.4.1.13576.10.1.2 wioArticleDescription R Description of article
Default value: "WAGO Ethernet
(10/100MBit) FBC"
1.3.6.1.4.1.13576.10.1.3 wioSerialNumber R Serial number of article
Default value: "SNxxxxxxxx-Txxxxxx-
mac|0030DExxxxxx"
1.3.6.1.4.1.13576.10.1.4 wioMacAddress R MAC address of article
Default value: "0030DExxxxxx"
1.3.6.1.4.1.13576.10.1.5 wioURLDatasheet R URL to datasheet of article
Default value: "http://www.wago.com/
wagoweb/documentation/navigate/nm
0dc__e.htm#ethernet"
1.3.6.1.4.1.13576.10.1.6 wioURLManual R URL to manual of article
Default value: "http://www.wago.com/
wagoweb/documentation/navigate/nm
0dc__e.htm#ethernet"
Manual
Version 1.1.1
1.3.6.1.4.1.13576.10.1.7 wioDeviceClass R Device class
10 = controller
20 = coupler
30 = switch
40 = display
50 = sensor
60 = actuator
1.3.6.1.4.1.13576.10.1.8 wioDeviceGroup R Device group
10 = Serie 750
20 = Serie 758
30 = Serie 767
40 = Serie 762 PERSPECTO
15.2.3 Versions Group

The version group contains information about the hardware/software versions
used in the fieldbus coupler.
Table 263: WAGO MIB – Versions Group

1.3.6.1.4.1.13576.10.1.10.1 wioFirmwareIndex R Index of firmware version
1.3.6.1.4.1.13576.10.1.10.2 wioHardwareIndex R Index of hardware version
1.3.6.1.4.1.13576.10.1.10.3 wioFwlIndex R Index of software version from
firmware loader
1.3.6.1.4.1.13576.10.1.10.4 wioFirmwareVersion R Complete firmware string
Manual
Version 1.1.1
15.2.4 Real-Time Clock Group

The real-time clock group contains information about the system’s real-time
clock.
Table 264: WAGO MIB – Real Time Clock Group

1.3.6.1.4.1.13576.10.1.11.1 wioRtcDateTime R/W Date/time of coupler in UTC as
string. For writing date/time use
the following string time 11:22:33
date 13-1-2007
Default value: "time xx:xx:xx date
xx-xx-xxxx (UTC)"
1.3.6.1.4.1.13576.10.1.11.2 wioRtcTime R/W Date/time of coupler in UTC as
integer in seconds from 1970-01-
01
Default value: “0”
1.3.6.1.4.1.13576.10.1.11.3 wioTimezone R/W "Actual time zone of article in
hours (-12 - +12)
1.3.6.1.4.1.13576.10.1.11.4 wioRtcHourMode R Hour mode
0 = 12h mode
1 = 24h mode
1.3.6.1.4.1.13576.10.1.11.5 wioRtcBatteryStatus R RTC battery status:
0 = ok
1 = battery empty
1.3.6.1.4.1.13576.10.1.11.6 wioRtcDayLightSaving R/W Time offset of 1 hour:
0 = not offset
1 = offset 1 hour (DayLightSaving)
Manual
Version 1.1.1
15.2.5 Ethernet Group

The Ethernet group contains the settings for the fieldbus coupler on the
ETHERNET.
Table 265: WAGO MIB – Ethernet Group

1.3.6.1.4.1.13576.10.1.12.1 wioEthernetMode R/W IP configuration of ETHERNET
connection:
0 = fix Ip address
1 = dynamic IP address over Bootp
2 = dynamic IP address over DHCP
1.3.6.1.4.1.13576.10.1.12.2 wioIp R/W Actual IP address of coupler
1.3.6.1.4.1.13576.10.1.12.3 wioSubnetMask R/W Actual subnet mask of coupler
1.3.6.1.4.1.13576.10.1.12.4 wioGateway R/W Actual gateway IP of coupler
1.3.6.1.4.1.13576.10.1.12.5 wioHostname R/W Actual host name of coupler
1.3.6.1.4.1.13576.10.1.12.6 wioDomainName R/W Actual domain name of coupler
1.3.6.1.4.1.13576.10.1.12.7 wioDnsServer1 R/W IP address of first DNS server
1.3.6.1.4.1.13576.10.1.12.8 wioDnsServer2 R/W IP address of second DNS server
15.2.6 Actual Error Group

The actual error group contains information about the last system status/error
status.
Table 266: WAGO MIB – Actual Error Group

1.3.6.1.4.1.13576.10.1.20.1 wioErrorGroup R Error group of last error
1.3.6.1.4.1.13576.10.1.20.2 wioErrorCode R Error code of last error
1.3.6.1.4.1.13576.10.1.20.3 wioErrorArgument R Error argument of last error
1.3.6.1.4.1.13576.10.1.20.4 wioErrorDescription R Error description string
Manual
Version 1.1.1
15.2.7 Http Group

The Http group contains information and settings for the coupler's Web server.
Table 267: WAGO MIB – Http Group

1.3.6.1.4.1.13576.10.1.40.1. wioHttpEnable R/W Enable/disable the port of the
1 webserver:
0 = port of webserver disable
1 = port of webserver enable
Default value: { 1 }
1.3.6.1.4.1.13576.10.1.40.1. wioHttpAuthen- R/W Enable/disable the authentication on the
2 ticationEnable websides:
0 = authentication disabled
1 = authentication enable
1.3.6.1.4.1.13576.10.1.40.1. wioHttpPort R/W Port of the http web server
3 Default value: { 80 }
15.2.8 Ftp Group

The Ftp group contains information and settings for the coupler's Ftp server.
Table 268: WAGO MIB – Ftp Group

1.3.6.1.4.1.13576.10.1.40.2. wioFtpEnable R/W Enable/disable the port of the ftp server
1 0 = port of ftp server disable
1 = port of ftp server enable
Manual
Version 1.1.1
15.2.9 Sntp Group

The Sntp group contains information and settings for the coupler's Sntp server.
Table 269: WAGO MIB – Sntp Group

1.3.6.1.4.1.13576.10.1.40.3. wioSntpEnable R/W Enable/disable the port of the SNTP
1 server
0 = port of SNTP server disable
1 = port of SNTP server enable
1.3.6.1.4.1.13576.10.1.40.3. wioSntpServer- R/W IP address of SNTP server
2 Address Default value: { 0 }
1.3.6.1.4.1.13576.10.1.40.3. wioSntpClient- R/W Interval to pool SNTP manager
3 Intervall Default value: { 0 }
1.3.6.1.4.1.13576.10.1.40.3. wioSntpClient- R/W Timeout to corrupt SNTP answer
4 Timeout Default value: { 2000 }
1.3.6.1.4.1.13576.10.1.40.3. wioSntpClient- R/W Time offset of 1 hour:
5 DayLightSaving 0 = not offset
1 = offset 1 hour (DayLightSaving)
15.2.10 Snmp Group

The Snmp group contains information and settings for the coupler's SNMP agent.
Table 270: WAGO MIB – Snmp Group

1.3.6.1.4.1.13576.10.1.40.4.1 wioSnmpEnable R/W Enable/disable the port of the SNMP
server
0 = port of SNMP server disable
1 = port of SNMP server enable
1.3.6.1.4.1.13576.10.1.40.4.2.1 wioSnmp1- R/W Enable/disable first SNMPv1/v2c
ProtocolEnable agent
1.3.6.1.4.1.13576.10.1.40.4.2.2 wioSnmp1- R/W IP address of first SNMP server
ManagerIp Default value: { 'C0A80101'h }
1.3.6.1.4.1.13576.10.1.40.4.2.3 wioSnmp1- R/W Community identification string for
Community SNMPv1/v2c
Default value: { "public" }
1.3.6.1.4.1.13576.10.1.40.4.2.4 wioSnmp1Trap- R/W Enable/disable SNMPv1 traps to first
V1enable SNMP server
1.3.6.1.4.1.13576.10.1.40.4.2.5 wioSnmp1Trap- R/W Enable/disable SNMPv2c traps to
V2enable first SNMP server
Manual
Version 1.1.1
1.3.6.1.4.1.13576.10.1.40.4.2.6 wioSnmp2- R/W Enable/disable first SNMPv1/v2c
ProtocolEnable agent
1.3.6.1.4.1.13576.10.1.40.4.2.7 wioSnmp2- R/W IP address of second SNMP server
ManagerIp Default value: { '00000000'h }
1.3.6.1.4.1.13576.10.1.40.4.2.8 wioSnmp2- R/W Community identification string for
Community SNMPv1/v2c
Default value: { "public" }
1.3.6.1.4.1.13576.10.1.40.4.2.9 wioSnmp2Trap- R/W Enable/disable SNMPv1 traps to first
V1enable SNMP server
1.3.6.1.4.1.13576.10.1.40.4.2.10 wioSnmp2Trap- R/W Enable/disable SNMPv2c traps to
V2enable first SNMP server
1.3.6.1.4.1.13576.10.1.40.4.3.1 wioSnmp1User- R/W Enable/disable first SNMPv3 user
Enable Default value: { 1 }
1.3.6.1.4.1.13576.10.1.40.4.3.2 wioSnmp1- R/W Athentication typ for first SNMPv3
Authentication- user:
Typ 0 = no Authentication
1 = MD5 Authentication
2 = SHA1 Authentication
1.3.6.1.4.1.13576.10.1.40.4.3.3 wioSnmp1- R/W Authentication name for first
Authentication- SNMPv3 user
Name Default value: { "SecurityName" }
1.3.6.1.4.1.13576.10.1.40.4.3.4 wioSnmp1- R/W Authentication key for first SNMPv3
Authentication- user
Key Default value: {"AuthenticationKey "}
1.3.6.1.4.1.13576.10.1.40.4.3.5 wioSnmp1- R/W Disable/enable data encryption for
PrivacyEnable first SNMPv3 user::
0 = no Encryption
1 = DES Encryption
1.3.6.1.4.1.13576.10.1.40.4.3.6 wioSnmp1- R/W Privacy key for SNMPv3 for first
PrivacyKey SNMPv3 user
Default value: { "PrivacyKey" }
1.3.6.1.4.1.13576.10.1.40.4.3.7 wioSnmp1- R/W Enable/disable notification (SNMPv3
Notification- traps) with SNMPv3 user
1.3.6.1.4.1.13576.10.1.40.4.3.8 wioSnmp1- R/W Receiver IP address for notification
Notification- (SNMPv3 traps) with SNMPv3 user
ReceiverIP Default value: { 'C0A80101'h }
1.3.6.1.4.1.13576.10.1.40.4.3.9 wioSnmp2User- R/W Enable/disable second SNMPv3 user
1.3.6.1.4.1.13576.10.1.40.4.3.10 wioSnmp2- R/W Authentication typ for second
Authentication- SNMPv3 user:
Typ 0 = no authentication
1 = MD5 authentication
2 = SHA1 authentication
1.3.6.1.4.1.13576.10.1.40.4.3.11 wioSnmp2- R/W Authentication name for second
Name Default value: { "SecurityName" }
1.3.6.1.4.1.13576.10.1.40.4.3.12 wioSnmp2- R/W Authentication key for second
Key Default value: {"AuthenticationKey"}
Manual
Version 1.1.1
1.3.6.1.4.1.13576.10.1.40.4.3.13 wioSnmp2- R/W Privacy key for SNMPv3 for second
PrivacyEnable SNMPv3 user
1.3.6.1.4.1.13576.10.1.40.4.3.14 wioSnmp2- R/W Privacy key for SNMPv3 for second
PrivacyKey SNMPv3 user
Default value: { "PrivacyKey" }
1.3.6.1.4.1.13576.10.1.40.4.3.15 wioSnmp2- R/W Enable/disable notification (SNMPv3
Notification- traps) with SNMPv3 user
1.3.6.1.4.1.13576.10.1.40.4.3.16 wioSnmp2- R/W Receiver IP address for notification
Notification- (SNMPv3 traps) with SNMPv3 user
ReceiverIP Default value: { '00000000'h }
15.2.11 Snmp Trap String Group

The Snmp trap string group contains strings that are attached to the
manufacturer-specific traps.
Table 271: WAGO MIB – Snmp Trap String Group

1.3.6.1.4.1.13576.10.1.40.4.4.1 wioTrapKbus- R/W String for 1st SNMP trap
Error Default value: { "Kbus Error" }
1.3.6.1.4.1.13576.10.1.40.4.4.2 wioTrapPlcStart R/W String for 2nd SNMP trap
Default value: { "Plc Start" }
1.3.6.1.4.1.13576.10.1.40.4.4.3 wioTrapPlcStop R/W String for 3rd SNMP trap
Default value: { "Plc Stop" }
1.3.6.1.4.1.13576.10.1.40.4.4.4 wioTrapPlc- R/W String for 4th SNMP trap
Reset Default value: { "Plc Reset" }
1.3.6.1.4.1.13576.10.1.40.4.4.5 wioTrapPlcSoft- R/W String for 5th SNMP trap
wareWatchdog Default value: { "Plc Software
Watchdog" }
DivideByZero Default value: {"Plc Divide By Zero"}
OnlineChange Default value: {"Plc Online Change"}
Download Default value: { "Plc Download
Programm" }
Login Default value: { "Plc Login" }
Logout Default value: {"Plc Logout"}
Manual
Version 1.1.1
15.2.12 Snmp User Trap String Group

The Snmp user trap string group contains strings that can be attached to user-
specific traps. These strings can be changed via SNMP or Wago_SNMP.lib in
CODESYS.
Table 272: WAGO MIB – Snmp User Trap String Group

1.3.6.1.4.1.13576.10.1.40.4.5.1 wioUserTrapMsg1 R/W String for 1st SNMP trap
1.3.6.1.4.1.13576.10.1.40.4.5.2 wioUserTrapMsg2 R/W String for 2nd SNMP trap
1.3.6.1.4.1.13576.10.1.40.4.5.3 wioUserTrapMsg3 R/W String for 3rd SNMP trap
1.3.6.1.4.1.13576.10.1.40.4.5.4 wioUserTrapMsg4 R/W String for 4th SNMP trap
15.2.13 Plc Connection Group

Activate or deactivate the connection to CODESYS with the Plc connection
group.
Table 273: WAGO MIB – Plc Connection Group

1.3.6.1.4.1.13576.10.1.40.5.1 wioCODESYSEnabl R/W Enable/disable the port of the
e CODESYS server
0 = port of CODESYS server
disable
1 = port of CODESYS server
enable
Manual
Version 1.1.1
15.2.14 Modbus Group

The Modbus group contains information and settings about the coupler's modbus
server.
Table 274: WAGO MIB – Modbus Group

1.3.6.1.4.1.13576.10.1.40.6.1 wioModbusTcp- R/W Enable/disable the port of the Modbus
Enable TCP server
0 = port of Modbus TCP server disable
1 = port of Modbus TCP server enable
1.3.6.1.4.1.13576.10.1.40.6.2 wioModbusUdb- R/W Enable/disable the port of the Modbus
Enable UDP server
0 = port of Modbus UDP server disable
1 = port of Modbus UDP server enable
1.3.6.1.4.1.13576.10.1.40.6.3 wioMax- R/W The maximal count of modbus
Connections connections
1.3.6.1.4.1.13576.10.1.40.6.4 wioConnection- R/W Timeout of the modbus connection
Timeout Default value: { 600 }
1.3.6.1.4.1.13576.10.1.40.6.5 wioModbus- R/W Mode of the modbus watchdog
WatchdogMode Default value: { 0 }
1.3.6.1.4.1.13576.10.1.40.6.6 wioModbus- R/W Timeout of the modbus watchdog
WatchdogTime Default value: { 100 }
1.3.6.1.4.1.13576.10.1.40.6.7 wioFreeModbus- R/W Unused and free modbus connections
Sockets Default value: { 15 }
1.3.6.1.4.1.13576.10.1.40.6.8 wioModbus- -
ConnectionTable
1.3.6.1.4.1.13576.10.1.40.6.8.1 wioModbus- -
ConnectionEntry
1.3.6.1.4.1.13576.10.1.40.6.8.1.1 wioModbus- R/W Index of modbus connection
ConnectionIndex
1.3.6.1.4.1.13576.10.1.40.6.8.1.2 wioModbus- R/W IP address of modbus connection
ConnectionIp
1.3.6.1.4.1.13576.10.1.40.6.8.1.3 wioModbus- R/W Port of modbus connection
ConnectionPort
Manual
Version 1.1.1
15.2.15 Process Image Group

The process image group contains a list of information about the terminals
connected to the fielbus coupler.
Table 275: WAGO MIB – Process Image Group

1.3.6.1.4.1.13576.10.1.50.1 wioModulCount R Count of modules
1.3.6.1.4.1.13576.10.1.50.2 wioAnalogOutLength R Length of analog output process datas
1.3.6.1.4.1.13576.10.1.50.3 wioAnalogInLength R Length of analog input process datas
1.3.6.1.4.1.13576.10.1.50.4 wioDigitalOutLength R Length of digital output process datas
1.3.6.1.4.1.13576.10.1.50.5 wioDigitalInLength R Length of digital input process datas
1.3.6.1.4.1.13576.10.1.50.6 wioDigitalOutOffset R Offset of digital output process datas
1.3.6.1.4.1.13576.10.1.50.7 wioDigitalInOffset R Offset of digital input process datas
1.3.6.1.4.1.13576.10.1.50.8 wioModuleTable -
1.3.6.1.4.1.13576.10.1.50.8.1 wioModuleEntry -
1.3.6.1.4.1.13576.10.1.50.8.1.1 wioModuleNumber R Number of module slot
1.3.6.1.4.1.13576.10.1.50.8.1.2 wioModuleName R Name of module
1.3.6.1.4.1.13576.10.1.50.8.1.3 wioModuleType R Type of module
1.3.6.1.4.1.13576.10.1.50.8.1.4 wioModuleCount R Count of module
1.3.6.1.4.1.13576.10.1.50.8.1.5 wioModule- R Module in alternative format
AlternativeFormat
1.3.6.1.4.1.13576.10.1.50.8.1.6 wioModuleAnalog- R Length of analog output data of module
OutLength (Bit)
1.3.6.1.4.1.13576.10.1.50.8.1.7 wioModuleAnalog- R Length of analog input data of module
InLength (Bit)
1.3.6.1.4.1.13576.10.1.50.8.1.8 wioModuleDigital- R Length of digital output data of module
OutLength (Bit)
1.3.6.1.4.1.13576.10.1.50.8.1.9 wioModuleDigital- R Length of digital input data of module
InLength (Bit)
Manual
Version 1.1.1
WAGO I/O System 750 List of Figures 287
List of Figures
Figure 1: Fieldbus Node (Example) ..................................................................... 24
Figure 2: Marking Area for Serial Numbers ......................................................... 26
Figure 3: Update Matrix from 2016 ...................................................................... 27
Figure 4: Isolation (Example) ............................................................................... 31
Figure 5: System Supply ...................................................................................... 32
Figure 6: System Voltage (Example) ................................................................... 33
Figure 7: Field Supply (Sensor/Actuator) ............................................................. 37
Figure 8: Supply Module with Fuse Carrier (Example 750-610) .......................... 39
Figure 9: Removing the Fuse Carrier .................................................................. 40
Figure 10: Opening the Fuse Carrier ................................................................... 40
Figure 11: Changing the Fuse ............................................................................. 40
Figure 12: Fuse Modules for Automotive Fuses, Series 282 ............................... 41
Figure 13: Fuse Modules for Automotive Fuses, Series 2006 ............................. 41
Figure 14: Fuse Modules with Pivotable Fuse Carrier, Series 281 ...................... 41
Figure 15: Fuse Modules with Pivotable Fuse Carrier, Series 2002 .................... 42
Figure 16: Power Supply Concept ....................................................................... 43
Figure 17: Supply Example .................................................................................. 44
Figure 18: Carrier Rail Contact (Example) ........................................................... 48
Figure 19: Cable Shield at Ground Potential ....................................................... 49
Figure 20: Examples of the WAGO Shield Connecting System .......................... 50
Figure 21: Application of the WAGO Shield Connecting System ........................ 50
Figure 22: View FC Modbus TCP; G4 ................................................................. 53
Figure 23: Device Supply ..................................................................................... 55
Figure 24: RJ-45 Connector ................................................................................ 56
Figure 25: Display Elements ................................................................................ 57
Figure 26: Service Interface (Closed and Opened Flap) ..................................... 58
Figure 27: Address Selection Switch (for example setting “0“) ............................ 59
Figure 28: Spacing ............................................................................................... 69
Figure 29: Release Tab ....................................................................................... 72
Figure 30: Insert I/O Module (Example) ............................................................... 73
Figure 31: Snap the I/O Module into Place (Example) ........................................ 73
Figure 32: Removing the I/O Module (Example) ................................................. 74
Figure 33: Data Contacts ..................................................................................... 75
Figure 34: Example for the Arrangement of Power Contacts .............................. 76
Figure 35: Connecting a Conductor to a CAGE CLAMP®.................................... 77
Figure 36: Operating System ............................................................................... 78
Figure 37: Memory Areas and Data Exchange .................................................... 82
Figure 38: Data Exchange Between MODBUS Master and I/O Modules ............ 84
Figure 39: Address Selection Switch, for Example the Value Setting “50” (21 + 24
+ 25) ............................................................................................................90
Figure 40: Example for a WBM page structure (simplified representation) ....... 109
Figure 41: Display Elements .............................................................................. 136
Figure 42: Node Status – I/O LED Signaling ..................................................... 140
Figure 43: Error Message Coding ...................................................................... 140
Figure 44: Use of the MODBUS Functions ........................................................ 171
Figure 45: Example SCADA Software with Modbus Driver ................................ 255
Figure 46: Marking Example According to ATEX and IECEx ............................ 257
Manual
Version 1.1.1
288 List of Figures WAGO I/O System 750
Figure 47: Text Detail – Marking Example According to ATEX and IECEx ....... 257
Figure 48: Marking Example for Approved I/O Module Ex i According to ATEX
and IECEx ................................................................................................ 259
Figure 49: Text Detail – Marking Example for Approved I/O ModuleEx i According
to ATEX and IECEx .................................................................................. 259
Figure 50: Marking Example According to NEC ................................................ 261
Figure 51: Text Detail – Marking Example According to NEC 500 .................... 261
Figure 52: Text Detail – Marking Example for Approved I/O Module Ex i
According to NEC 505 .............................................................................. 262
According to NEC 506 .............................................................................. 262
According to CEC 18 attachment J .......................................................... 263
Manual
Version 1.1.1
WAGO I/O System 750 List of Tables 289
List of Tables
Table 1: Variations ............................................................................................... 10
Table 2: Number Notation .................................................................................... 15
Table 3: Font Conventions ................................................................................... 15
Table 4: Labeling Symbols .................................................................................. 25
Table 5: Legend for Figure “Update Matrix from 2016” ....................................... 27
Table 6: Legend for Figure “System Supply” ....................................................... 32
Table 7: Alignment ............................................................................................... 34
Table 8: Legend for Figure “Field Supply (Sensor/Actuator) for ECO Fieldbus
Coupler” ......................................................................................................37
Table 9: Power Supply Modules .......................................................................... 38
Table 10: Filter Modules for 24 V Supply ............................................................. 43
Table 11: Legend for Figure “Supply Example for Fieldbus Coupler/Controller” . 45
Table 12: WAGO Ground Wire Terminals ........................................................... 47
Table 13: Legend for Figure “View” ..................................................................... 54
Table 14: RJ-45 Connector and RJ-45 Connector Configuration ........................ 56
Table 15: Display Elements Fieldbus Status ....................................................... 57
Table 16: Display Elements Node Status ............................................................ 57
Table 17: Legend for Figure “Service Interface (Closed and Opened Flap)” ....... 58
Table 18: Meaning of DIP Switch Positions ......................................................... 59
Table 19: Technical Data - Device ....................................................................... 60
Table 20: Technical Data - System ...................................................................... 60
Table 21: Technical data – Accessories ............................................................. 61
Table 22: Technical Data ‒ Field Wiring .............................................................. 61
Table 23: Technical Data – Data Contacts .......................................................... 61
Table 24: Technical Data – Climatic Environmental Conditions .......................... 62
Table 25: Technical Data – Mechanical Strength ................................................ 63
Table 26: Technical Data – Software Compatibility ............................................. 63
Table 27: WAGO DIN Rails ................................................................................. 69
Table 28: Data Width for I/O Modules ................................................................. 83
Table 29: Allocation of Digital Inputs and Outputs to Process Data Words in
Accordance with the ................................................................................... 84
Table 30: Log File Name Syntax ......................................................................... 86
Table 31: Address selection switch values (host ID) ........................................... 90
Table 32: WBM User Groups ............................................................................. 107
Table 33: WBM Page “Information” ................................................................... 110
Table 34: WBM Page “Administration” .............................................................. 111
Table 35: WBM Page “System Status” .............................................................. 113
Table 36: WBM Page „Clock“ ............................................................................ 116
Table 37: WBM Page “Miscellaneous” .............................................................. 117
Table 38: WBM page "Storage Media" .............................................................. 118
Table 39: WBM Page “Update“ .......................................................................... 118
Table 40: WBM Page „Ethernet“ ........................................................................ 119
Table 41: WBM page „Protocols“ ....................................................................... 123
Table 42: WBM Page “SNMP v1/v2” ................................................................. 125
Table 43: WBM Page “SNMP V3” ..................................................................... 126
Table 44: WBM Page “SNTP” ............................................................................ 127
Table 45: WBM page „TCP/IP“ .......................................................................... 128
Manual
Version 1.1.1
290 List of Tables WAGO I/O System 750
Table 46: WBM page “MODBUS” ...................................................................... 129
Table 47: WBM page “Modbus Mapping” .......................................................... 132
Table 48: WBM page „I/O Data“ ........................................................................ 135
Table 49: LED Assignment for Diagnostics ....................................................... 136
Table 50: Fieldbus Diagnostics – Solution in Event of Error .............................. 137
Table 51: Node Status Diagnostics – Solution in Event of Error ....................... 139
Table 52: Blink code- table for the I/O LED signaling, error code 1 ................... 142
Table 53: Blink Code Table for the I/O LED Signaling, Error Code 2 ................ 143
Table 59: Blink Code Table for the I/O LED Signaling, Error Code 8 … 11....... 146
Table 60: Blink code table for I/O LED signaling, error code 12 ........................ 147
Table 63: Blink code - table for the I/O LED signaling, error code 15 ................ 148
Table 64: IP Packet ........................................................................................... 151
Table 65: Network Class A ................................................................................ 152
Table 66: Network Class B ................................................................................ 152
Table 67: Network Class C ................................................................................ 152
Table 68: Key Data Class A, B and C ................................................................ 153
Table 69: Example: Class B Address with Field for Subnet IDs ........................ 154
Table 70: Subnet Mask for Class A Network ..................................................... 154
Table 71: Subnet Mask for Class B Network ..................................................... 154
Table 72: Subnet Mask for Class C Network ..................................................... 154
Table 73: Example for an IP Address from a Class B Network ......................... 154
Table 74: BootP Options .................................................................................... 158
Table 75: Meaning of DHCP Options ................................................................ 160
Table 76: Meaning of the SNTP Parameters ..................................................... 161
Table 77: MIB II Groups ..................................................................................... 163
Table 78: Standard Traps .................................................................................. 164
Table 79: Supported Syslog Messages ............................................................. 166
Table 80: Modbus TCP Header ......................................................................... 168
Table 81: Basic Data Types of MODBUS Protocol ............................................ 169
Table 82: List of the MODBUS Functions in the Fieldbus Coupler .................... 169
Table 83: Exception Codes ................................................................................ 172
Table 84: Request of Function Code FC1 ........................................................ 173
Table 85: Response of Function Code FC1 ...................................................... 173
Table 86: Assignment of Inputs ......................................................................... 174
Table 87: Exception of Function Code FC1 ....................................................... 174
Table 88: Request of Function Code FC2 ......................................................... 175
Table 90: Assignment of Inputs ......................................................................... 175
Manual
Version 1.1.1
Table 100: Exception of Function Code FC5 ..................................................... 179
Table 101: Request of Function Code FC6 ....................................................... 180
Table 102: Response of Function Code FC6 .................................................... 180
Table 103: Exception of Function Code FC6 ..................................................... 180
Table 104: Request of Function code FC11 ...................................................... 181
Table 105: Response of Function Code FC11 .................................................. 181
Table 106: Exception of Function Code FC 11 .................................................. 181
Table 107: Request of Function Code FC15 ..................................................... 182
Table 109: Exception of Function Code FC15 ................................................... 183
Table 119: Register Access Reading (with FC3 and FC4) ................................ 188
Table 120: Register Access Writing (with FC6 and FC16) ................................ 189
Table 121: Bit Access Reading (with FC1 and FC2) ......................................... 190
Table 122: Bit Access Writing (with FC5 and FC15).......................................... 190
Table 123: Modbus Registers ........................................................................... 191
Table 124: Register Address 0x1000 ................................................................ 194
Table 134: Register Address 0x100A ................................................................ 196
Table 135: Starting Watchdog ........................................................................... 197
Table 136: Register Address 0x100B ................................................................ 197
Table 144: Register Address 0x102A ................................................................ 200
Table 145: Register Address 0x102B ................................................................ 200
Manual
Version 1.1.1
Table 177: 1 Channel Digital Input Module with Diagnostics ............................. 209
Table 178: 2 Channel Digital Input Modules ...................................................... 210
Table 179: 2 Channel Digital Input Module with Diagnostics ............................. 210
Table 180: 2 Channel Digital Input Module with Diagnostics and Output Process
Data ..........................................................................................................210
Table 183: 8 Channel Digital Input Module NAMUR with Diagnostics and Output
Process Data ............................................................................................ 212
Table 184: 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data ............................................................................................ 213
Table 185: 16 Channel Digital Input Modules .................................................... 214
Table 186: 1 Channel Digital Output Module with Input Process Data .............. 215
Table 187: 2 Channel Digital Output Modules ................................................... 215
Table 188: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data ..........................................................................................................216
Table 189: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data 75x-506 ............................................................................................ 216
Table 190: 4 Channel Digital Output Modules ................................................... 217
Manual
Version 1.1.1
Table 191: 4 Channel Digital Output Modules with Diagnostics and Input Process
Data ..........................................................................................................217
Table 192: 8 Channel Digital Output Module ..................................................... 217
Table 193: 8 Channel Digital Output Modules with Diagnostics and Input Process
Data ..........................................................................................................218
Table 194: 16 Channel Digital Output Modules ................................................. 218
Table 195: 8 Channel Digital Input/Output Modules .......................................... 219
Table 196: 1 Channel Analog Input Modules ..................................................... 220
Table 198: 2-Channel Analog Input Modules HART .......................................... 222
Table 199:: 2 Channel Analog Input Modules HART + 6 bytes Mailbox ............ 222
Table 202: 3-Phase Power Measurement Module ............................................ 224
Table 203: 3-Phase Power Measurement Modules 750-494, -495, (and all
variations) ................................................................................................. 225
Table 204: 2 Channel Analog Output Modules .................................................. 226
Table 207: Counter Modules 750-404, (and all variations except of /000-005),
753-404, -404/000-003 ............................................................................. 228
Table 208: Counter Modules 750-404/000-005, 753-404/000-005 .................... 228
Table 209: Counter Modules 750-633 ............................................................... 229
Table 210: Counter Modules 750-638, 753-638 ................................................ 229
Table 211: Pulse Width Modules 750-511, /xxx-xxx, 753-511 ........................... 230
Table 212: Serial Interface Modules with Alternative Data Format .................... 231
Table 213: Serial Interface Modules with Standard Data Format ...................... 231
Table 214: Serial Interface Modules 750-652, 753-652 ..................................... 232
Table 215: Data Exchange Module 750-654, -654/000-001 .............................. 232
Table 216: SSI Transmitter Interface Modules .................................................. 233
Table 217: SSI Transmitter Interface I/O Modules with an Alternative Data Format
(/000-004, -005, -007)............................................................................... 233
Table 218: Incremental Encoder Interface Modules 750-631/000-004, --010, -
011............................................................................................................233
Table 219: Incremental Encoder Interface Modules 750-634 ............................ 234
Table 220: Incremental Encoder Interface Modules 750-637, (and all variations)
..................................................................................................................234
Table 221: Digital Pulse Interface Modules 750-635, 753-635 .......................... 235
Table 222: DC-Drive Controller 750-636, -636/000-700, -636/000-800 ............ 235
Table 223: Stepper Controller 750-670, -671, -672 ........................................... 236
Table 224: RTC Module 750-640 ...................................................................... 237
Table 225: DALI/DSI Master Module 750-641 ................................................... 237
Table 226: DALI Multi-Master Module 753-647 in the "Easy" Mode .................. 238
Table 227: DALI Multi-Master Module 753-647 in the "Full" Mode .................... 240
Table 228: LON® FTT Module 753-648 ............................................................. 241
Table 229: EnOcean Radio Receiver 750-642 .................................................. 241
Table 230: MP Bus Master Module 750-643 ..................................................... 242
Table 231: Bluetooth® RF-Transceiver 750-644 ................................................ 243
Table 232: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645 ... 243
Manual
Version 1.1.1
Table 233: Proportional valve module operating mode with one valve 750-632,
753-632/000-100 ...................................................................................... 244
Table 234: Proportional valve module operating mode with two valves 750-632,
753-632/000-100 ...................................................................................... 244
Table 235: M-BUS Master Module 753-649 ...................................................... 245
Table 236: IO-Link Master 750-657 ................................................................... 246
Table 237: CAN Gateway 750-658 .................................................................... 246
Table 238: Servo Stepper Controller 750-673 ................................................... 247
Tabelle 239:SMI Master Module 753-1630, -1631 in Fieldbus Coupler Mode... 248
Table 240: SMI Master Module 753-1630, -1631 in „Full Mode“ ....................... 248
Table 241: AS-interface Master Module 750-655, 753-655 ............................... 249
Table 242: System Modules with Diagnostics 750-606, -611 ............................ 251
Table 243: System Modules with Diagnostics 750-610, -611 ............................ 251
Table 244: Filter Modules 750-624/020-002, 750-626/020-002 ........................ 251
Table 245: Binary Space Module 750-622 (with Behavior like 2 Channel Digital
Input) ........................................................................................................252
Table 246: Modbus Table and Function Codes ................................................. 255
Table 247: Description of Marking Example According to ATEX and IECEx..... 258
Table 248: Description of Marking Example for Approved I/O Module Ex I
According to ATEX and IECEx ................................................................. 260
Table 249: Description of Marking Example According to NEC 500.................. 261
Table 250: Description of Marking Example for Approved I/O Module Ex i
According to NEC 505 .............................................................................. 262
According to NEC 506 .............................................................................. 262
According to CEC 18 attachment J .......................................................... 263
Table 253: MIB II – System Group .................................................................... 267
Table 254: MIB II – Interface Group .................................................................. 268
Table 255: MIB II – IP Group ............................................................................. 270
Table 256: MIB II – IpRoute Table Group .......................................................... 271
Table 257: MIB II – ICMP Group ....................................................................... 272
Table 258: MIB II – TCP Group ......................................................................... 273
Table 259: MIB II – UDP Group ......................................................................... 274
Table 260: MIB II – SNMP Group ...................................................................... 275
Table 261: WAGO MIB – Company Group ........................................................ 276
Table 262: WAGO MIB – Product Group ........................................................... 276
Table 263: WAGO MIB – Versions Group ......................................................... 277
Table 264: WAGO MIB – Real Time Clock Group ............................................. 278
Table 265: WAGO MIB – Ethernet Group ......................................................... 279
Table 266: WAGO MIB – Actual Error Group .................................................... 279
Table 267: WAGO MIB – Http Group ................................................................ 280
Table 268: WAGO MIB – Ftp Group .................................................................. 280
Table 269: WAGO MIB – Sntp Group ................................................................ 281
Table 270: WAGO MIB – Snmp Group .............................................................. 281
Table 271: WAGO MIB – Snmp Trap String Group ........................................... 283
Table 272: WAGO MIB – Snmp User Trap String Group .................................. 284
Table 273: WAGO MIB – Plc Connection Group ............................................... 284
Table 274: WAGO MIB – Modbus Group .......................................................... 285
Table 275: WAGO MIB – Process Image Group ............................................... 286
Manual
Version 1.1.1
Manual
Version 1.1.1
WAGO GmbH & Co. KG
Postfach 2880 • D - 32385 Minden
Hansastraße 27 • D - 32423 Minden
Phone: +49 571 887 – 0
Fax: +49 571 887 – 844169
E-Mail: info@wago.com
Internet: www.wago.com

m07500362 XXXXXXXX 0en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

m07500362 XXXXXXXX 0en

Uploaded by

Copyright:

Available Formats

Manual

WAGO I/O System 750

© 2022 WAGO GmbH & Co. KG

WAGO GmbH & Co. KG

Phone: +49 (0) 571/8 87 – 0

Phone: +49 (0) 571/8 87 – 4 45 55

WAGO is a registered trademark of WAGO Verwaltungsgesellschaft mbH.

1 Notes about this Documentation

Always retain this documentation!

1.1 Validity of this Documentation

The product “FC Modbus TCP; G4 (BootP)” (750-362, 750-362/0000-0001) shall

Consider power layout of the WAGO I/O System 750!

1.3 Property rights

• Adobe® and Acrobat® are registered trademarks of Adobe Systems Inc.

• AndroidTM is a trademark of Google LLC.

• AS-Interface® is a registered trademark of the AS-International Association

• BACnet® is a registered trademark of the American Society of Heating,

• Bluetooth® is a registered trademark of Bluetooth SIG, Inc.

• CiA® and CANopen® are registered trademarks of CAN in AUTOMATION –

• CODESYS is a registered trademark of CODESYS Development GmbH.

• DALI is a registered trademark of the Digital Illumination Interface Alliance

• EtherCAT® is a registered trademark and patented technology licensed by

• ETHERNET/IP™ is a registered trademark of the Open DeviceNet Vendor

• EnOcean® is a registered trademark of EnOcean GmbH.

• Google PlayTM is a registered trademark of Google Inc.

• IO-Link is a registered trademark of PROFIBUS Nutzerorganisation e.V.

• KNX® is a registered trademark of the KNX Association cvba.

• Linux® is a registered trademark of Linus Torvalds.

• LON® is a registered trademark of the Echelon Corporation.

• Modbus® is a registered trademark of Schneider Electric, licensed for

• OPC UA is a registered trademark of the OPC Foundation.

• PROFINET® is a registered trademark of the PROFIBUS

• QR Code is a registered trademark of DENSO WAVE INCORPORATED.

• Subversion® is a trademark of the Apache Software Foundation.

• Windows® is a registered trademark of Microsoft Corporation.

Personal Injury Caused by Electric Current!

Damage to Property Caused by Electrostatic Discharge (ESD)!

1.5 Number Notation

1.6 Font Conventions

2.1 Legal Bases

2.1.1 Subject to Changes

2.1.2 Personnel Qualifications

2.1.3 Use of the 750 Series in Compliance with Underlying

Operating the product in home applications without further measures is only

The implementation of safety functions such as EMERGENCY STOP or safety

2.1.4 Technical Condition of Specified Devices

2.1.4.1.1 Electrical and Electronic Equipment

Electrical and electronic equipment may not be disposed of

Environmentally friendly disposal benefits health and protects

• Clear any data stored on the electrical and electronic equipment.

• Remove any added battery or memory card in the electrical and

• Have the electrical and electronic equipment sent to your local

Improper disposal of electrical and electronic equipment can be harmful to the

Packaging contains materials that can be reused.

Environmentally friendly disposal of the packaging protects the environment and

• Observe national and local regulations for the disposal of packaging.

• Dispose of packaging of all types that allows a high level of recovery,

Improper disposal of packaging can be harmful to the environment and wastes

2.2 Safety Advice (Precautions)

Do not work on devices while energized!

Install device in a suitable enclosure!

• Guarantee that the max. permissible degree of pollution is not exceeded.

Ensure disconnect and overcurrent protection!