m07508214-00000000-0en

Manual
WAGO I/O System 750
750-8214
PFC200; G2; 2ETH RS CAN
Controller PFC200; 2nd Generation; 2 x ETHERNET,
RS-232/-485, CAN, CANopen
Version 1.9.0, valid from FW Version 03.10.08(22)

2 WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
© 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: [email protected]
Web: www.wago.com
Technical Support
Phone: +49 (0) 571/8 87 – 4 45 55

Fax: +49 (0) 571/8 87 – 84 45 55
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.
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
WAGO I/O System 750 Table of Contents 3
750-8214 PFC200; G2; 2ETH RS CAN
Table of Contents
1 Notes about this Documentation ........................................................... 15
1.1 Validity of this Documentation............................................................... 15
1.2 Copyright .............................................................................................. 15
1.3 Property rights ...................................................................................... 16
1.4 Symbols ............................................................................................... 18
1.5 Number Notation .................................................................................. 20
1.6 Font Conventions ................................................................................. 20
2 Important Notes ...................................................................................... 21
2.1 Legal Bases.......................................................................................... 21
2.1.1 Subject to Changes .......................................................................... 21
2.1.2 Personnel Qualifications .................................................................. 21
2.1.3 Use of the 750 Series in Compliance with Underlying Provisions ..... 21
2.1.3.1 Improper Use............................................................................... 22
2.1.3.2 Warranty and Liability .................................................................. 22
2.1.3.3 Obligations of Installers/Operators............................................... 23
2.2 Safety Advice (Precautions) ................................................................. 24
2.3 Licensing Terms of the Software Package Used................................... 28
2.4 Special Use Conditions for ETHERNET Devices .................................. 28
3 Overview .................................................................................................. 30
4 Properties ................................................................................................ 33
4.1 Hardware Description ........................................................................... 33
4.1.1 View ................................................................................................. 33
4.1.2 Labeling ........................................................................................... 35
4.1.2.1 Production Code.......................................................................... 35
4.1.3 Connectors ...................................................................................... 36
4.1.3.1 Wiring Level................................................................................. 36
4.1.3.2 Service Interface ......................................................................... 37
4.1.3.3 Network Connectors .................................................................... 38
4.1.3.4 CANopen..................................................................................... 39
4.1.3.5 Communication Interface ............................................................. 41
4.1.3.5.1 Operating as an RS-232 Interface........................................... 42
4.1.3.5.2 Operating as an RS-485 Interface........................................... 43
4.1.4 System Contacts .............................................................................. 44
4.1.4.1 Data Contacts.............................................................................. 44
4.1.4.2 Power Jumper Contacts .............................................................. 45
4.1.5 Display Elements ............................................................................. 46
4.1.5.1 Power Supply LEDs..................................................................... 46
4.1.5.2 System/Fieldbus LEDs ................................................................ 47
4.1.5.3 Network Connector LEDs ............................................................ 48
4.1.5.4 Memory Card Slot LED ................................................................ 49
4.1.6 Operating Elements ......................................................................... 50
4.1.6.1 Operating Mode Switch ............................................................... 50
4.1.6.2 Reset Button................................................................................ 51
4.1.7 Memory Card Slot ............................................................................ 52
4.2 Schematic Diagram .............................................................................. 53
Manual
4 Table of Contents WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
4.3 Technical Data ..................................................................................... 54
4.3.1 Mechanical Data .............................................................................. 54
4.3.2 System Data .................................................................................... 54
4.3.3 Power Supply ................................................................................... 54
4.3.4 Clock ................................................................................................ 55
4.3.5 Programming ................................................................................... 55
4.3.6 Local Bus ......................................................................................... 55
4.3.7 ETHERNET ..................................................................................... 56
4.3.8 CANopen ......................................................................................... 56
4.3.9 Communication Interface ................................................................. 56
4.3.10 Connection Type .............................................................................. 57
4.3.11 Climatic Environmental Conditions ................................................... 57
4.4 Approvals ............................................................................................. 58
4.5 Standards and Guidelines .................................................................... 60
5 Function Description .............................................................................. 61
5.1 Network ................................................................................................ 61
5.1.1 Interface Configuration ..................................................................... 61
5.1.1.1 Operation in Switch Mode............................................................ 61
5.1.1.2 Operation with Separate Network Interfaces................................ 62
5.1.1.3 MAC ID and IP Address Assignment Examples ........................... 63
5.1.2 Network Security .............................................................................. 64
5.1.2.1 Users and Passwords.................................................................. 64
5.1.2.1.1 Services and Users ................................................................. 64
5.1.2.1.2 WBM User Group.................................................................... 65
5.1.2.1.3 Linux User Group .................................................................... 66
5.1.2.1.4 SNMP User Group .................................................................. 66
5.1.2.2 Web Protocols for WBM Access .................................................. 67
5.1.2.2.1 TLS Encryption ....................................................................... 67
5.1.2.3 Root Certificates .......................................................................... 69
5.1.3 Network Configuration...................................................................... 70
5.1.3.1 Host Name/Domain Name ........................................................... 70
5.1.3.2 Routing ........................................................................................ 70
5.1.4 Network Services ............................................................................. 74
5.1.4.1 DHCP-Client ................................................................................ 74
5.1.4.2 DHCP Server............................................................................... 74
5.1.4.3 DNS Server ................................................................................. 76
5.1.5 Cloud Connectivity Functionality ...................................................... 77
5.1.5.1 Components of the Cloud Connectivity Software Package .......... 78
5.2 Memory Card Function ......................................................................... 79
5.2.1 Formatting........................................................................................ 79
5.2.2 Data Backup .................................................................................... 81
5.2.2.1 Backup Function.......................................................................... 81
5.2.2.2 Restore Function ......................................................................... 82
5.2.3 Inserting a Memory Card during Operation ...................................... 84
5.2.4 Removing the Memory Card during Operation ................................. 84
5.2.5 Setting the Home Directory for the Runtime System ........................ 85
5.2.6 Load Boot Project ............................................................................ 85
5.3 Licensed Software Components ........................................................... 87
6 Mounting .................................................................................................. 88
Manual
750-8214 PFC200; G2; 2ETH RS CAN
6.1 Installation Position............................................................................... 88
6.2 Overall Configuration ............................................................................ 88
6.3 Mounting onto Carrier Rail .................................................................... 90
6.3.1 Carrier Rail Properties...................................................................... 90
6.3.2 WAGO DIN Rails ............................................................................. 91
6.4 Spacing ................................................................................................ 91
6.5 Mounting Sequence.............................................................................. 92
6.6 Inserting Devices .................................................................................. 93
6.6.1 Inserting the Controller ..................................................................... 93
7 Connect Devices ..................................................................................... 94
7.1 Connecting a Conductor to the CAGE CLAMP® ................................... 94
7.2 Power Supply Concept ......................................................................... 95
7.2.1 Overcurrent Protection ..................................................................... 95
7.2.2 Supplementary Power Supply Regulations ...................................... 96
8 Commissioning ....................................................................................... 97
8.1 Switching On the Controller .................................................................. 97
8.2 Determining the IP Address of the Host PC .......................................... 99
8.3 Setting an IP Address ......................................................................... 100
8.3.1 Assigning an IP Address using DHCP ............................................ 101
8.3.2 Changing an IP Address Using the “CBM” Configuration Tool and a
Terminal Program .......................................................................... 102
8.3.3 Changing an IP Address using “WAGO Ethernet Settings” ............ 105
8.3.4 Temporarily Setting Fixed IP Addresses ....................................... 107
8.4 Testing the Network Connection ......................................................... 108
8.5 Changing Passwords .......................................................................... 109
8.6 Shutdown/Restart ............................................................................... 110
8.7 Initiating Reset Functions ................................................................... 111
8.7.1 Warm Start Reset .......................................................................... 111
8.7.1.1 CODESYS V2 Runtime System................................................. 111
8.7.1.2 e!RUNTIME Runtime System .................................................... 111
8.7.2 Cold Start Reset............................................................................. 111
8.7.2.1 CODESYS V2 Runtime System................................................. 111
8.7.2.2 e!RUNTIME Runtime System .................................................... 111
8.7.3 Software Reset .............................................................................. 112
8.7.4 Controller Reset ............................................................................. 112
8.8 Configuration ...................................................................................... 114
8.8.1 Configuration via Web-Based-Management (WBM) ....................... 115
8.8.1.1 WBM User Administration.......................................................... 117
8.8.1.2 General Information about the Page .......................................... 121
8.8.2 Configuration via Console-Based-Management-Tool (CBM) using a
Terminal Program .......................................................................... 123
8.8.2.1 CBM Menu Structure Overview ................................................. 125
8.8.3 Configuration using “WAGO Ethernet Settings”.............................. 128
8.8.3.1 Identification Tab ....................................................................... 130
8.8.3.2 Network Tab .............................................................................. 131
8.8.3.3 PLC Tab .................................................................................... 133
8.8.3.4 Status Tab ................................................................................. 134
9 Run-time System CODESYS 2.3........................................................... 135
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.1 Installing the CODESYS 2.3 Programming System ............................ 135
9.2 First Program with CODESYS 2.3 ...................................................... 135
9.2.1 Start the CODESYS Programming System .................................... 135
9.2.2 Creating a Project and Selecting a Target System ......................... 135
9.2.3 Creating the PLC Configuration ..................................................... 137
9.2.4 Editing the Program Function Block ............................................... 144
9.2.5 Loading and Running the PLC Program in the Fieldbus Controller
(ETHERNET) ................................................................................. 146
9.2.6 Creating a Boot Project .................................................................. 148
9.3 Syntax of Logical Addresses .............................................................. 148
9.4 Creating Tasks ................................................................................... 149
9.4.1 Cyclic Tasks ................................................................................... 152
9.4.2 Freewheeling Tasks ....................................................................... 153
9.4.3 Debugging an IEC Program ........................................................... 154
9.5 System Events ................................................................................... 158
9.5.1 Creating an Event Handler ............................................................. 160
9.6 Process Images .................................................................................. 163
9.6.1 Process Images for I/O Modules Connected to the Controller ........ 165
9.6.2 Process Image for Slaves Connected to the Fieldbus .................... 166
9.7 Access to Process Images of the Input and Output Data via CODESYS
2.3 ...................................................................................................... 166
9.8 Addressing Example ........................................................................... 168
9.9 Local Bus Synchronization ................................................................. 170
9.9.1 Case 1: CODESYS Task Interval Set Smaller than the Local Bus
Cycle .............................................................................................. 170
9.9.2 Case 2: CODESYS Task Interval Smaller than Twice the Local Bus
Cycle .............................................................................................. 171
9.9.3 Case 3: CODESYS Task Interval Greater than Twice the Local Bus
Cycle .............................................................................................. 172
9.9.4 Case 4: CODESYS Task Interval Greater than 10 ms.................... 173
9.9.5 Local Bus (KBus) Settings ............................................................. 174
9.9.5.1 Effect of Update Mode on CODESYS Tasks ............................. 175
9.9.5.1.1 Asynchronous Update Mode ................................................. 175
9.9.5.1.2 Synchronous Update Mode ................................................... 175
9.10 Memory Settings in CODESYS........................................................... 176
9.10.1 Program Memory ........................................................................... 176
9.10.2 Data Memory and Function Block Limitation .................................. 178
9.10.3 Remanent Memory ........................................................................ 179
9.11 General Target System Settings ......................................................... 180
9.12 CODESYS Visualization ..................................................................... 180
9.12.1 Limits of CODESYS Visualization .................................................. 183
9.12.2 Eliminating Errors in CODESYS Web Visualization ........................ 185
9.12.3 FAQs about CODESYS Web Visualization .................................... 186
10 e!RUNTIME Runtime Environment ....................................................... 188
10.1 General Notes .................................................................................... 188
10.2 CODESYS V3 Priorities ...................................................................... 189
10.3 Memory Spaces under e!RUNTIME.................................................... 190
10.3.1 Program and Data Memory ............................................................ 190
10.3.2 Function Block Limitation ............................................................... 190
Manual
750-8214 PFC200; G2; 2ETH RS CAN
10.3.3 Remanent Memory ........................................................................ 190
11 Modbus – CODESYS V2........................................................................ 191
11.1 General .............................................................................................. 191
11.2 Features ............................................................................................. 191
11.3 Configuration ...................................................................................... 192
11.3.1 Modbus Settings ............................................................................ 193
11.3.2 Modbus TCP Settings .................................................................... 194
11.3.3 Modbus UDP Settings .................................................................... 194
11.3.4 Modbus RTU Settings .................................................................... 194
11.4 Data Exchange ................................................................................... 197
11.4.1 Process Image ............................................................................... 198
11.4.2 Flag Area ....................................................................................... 199
11.4.3 Modbus Registers .......................................................................... 200
11.4.4 Modbus Mapping ........................................................................... 200
11.4.4.1 Modbus Mapping for Write Bit Services FC1, FC2 ..................... 200
11.4.4.2 Modbus Mapping for Write Bit Services FC5, FC15 ................... 201
11.4.4.3 Modbus Mapping for Read Register Services FC3, FC4, FC23 . 202
11.4.4.4 Modbus Mapping for Write Register Services FC6, FC16, FC22,
FC23 ......................................................................................... 204
11.5 WAGO Modbus Registers .................................................................. 206
11.5.1 Process Image Properties .............................................................. 207
11.5.1.1 Register 0x1022 – Number of Registers in the Modbus Input
Process Image .......................................................................... 207
11.5.1.2 Register 0x1023 – Number of Registers in the Modbus Output
Process Image .......................................................................... 207
11.5.1.3 Register 0x1024 – Number of Bits in the Modbus Input Process
Image ........................................................................................ 207
11.5.1.4 Register 0x1025 – Number of Bits in the Modbus Output Process
Image ........................................................................................ 207
11.5.2 Network Configuration.................................................................... 208
11.5.2.1 Register 0x1028 – IP Configuration ........................................... 208
11.5.2.2 Register 0x102A – Number of Established TCP Connections .... 208
11.5.2.3 Register 0x1030 – Modbus TCP Socket Timeout ...................... 208
11.5.2.4 Register 0x1031 – MAC Address for ETHERNET-Interface 1 (eth0)208
11.5.2.5 Register 0x1037 - Modbus TCP Response Delay ...................... 208
11.5.3 PLC Status Register ...................................................................... 209
11.5.4 Modbus Watchdog ......................................................................... 209
11.5.4.1 Register 0x1100 – Watchdog Command ................................... 211
11.5.4.2 Register 0x1101 – Watchdog Status ......................................... 213
11.5.4.3 Register 0x1102 – Watchdog Timeout ....................................... 213
11.5.4.4 Register 0x1103 – Watchdog Config ......................................... 213
11.5.5 Register 0x1104 – Watchdog Operation Mode ............................... 214
11.5.6 Modbus Constants Registers ......................................................... 215
11.5.6.1 Electronic Nameplate ................................................................ 215
11.5.6.2 Register 0x2010 – Revision (Firmware Index) ........................... 215
11.5.6.3 Register 0x2011 – Series Designator ........................................ 215
11.5.6.4 Register 0x2012 – Device ID ..................................................... 215
11.5.6.5 Register 0x2013 – Major Firmware Version ............................... 216
11.5.6.6 Register 0x2014 – Minor Firmware Version ............................... 216
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5.6.7 Register 0x2015 – MBS Version ................................................ 216
11.6 Diagnostics ......................................................................................... 217
11.6.1 Diagnostics for the Modbus Master ................................................ 217
11.6.2 Diagnostics for the Runtime System .............................................. 217
11.6.3 Diagnostics for the Error Server ..................................................... 217
12 Modbus – e!RUNTIME ........................................................................... 220
12.1 Modbus Address Overview ................................................................. 220
12.2 Modbus Registers............................................................................... 221
12.2.1 Modbus Watchdog ......................................................................... 223
12.2.1.1 Register 0xFA00 – Watchdog Command................................... 225
12.2.1.2 Register 0xFA01 – Watchdog Timeout ...................................... 226
12.2.1.3 Register 0xFA02 – Watchdog Status ......................................... 226
12.2.1.4 Register 0xFA03 – Watchdog Config ......................................... 227
12.2.1.5 Modbus TCP Connection Watchdog Register............................ 228
12.2.2 Status Registers............................................................................. 229
12.2.2.1 PLC Status Register .................................................................. 229
12.2.3 Electronic Nameplate ..................................................................... 229
12.2.3.1 Order Number ........................................................................... 229
12.2.3.2 Firmware Version ...................................................................... 229
12.2.3.3 Hardware Version ...................................................................... 229
12.2.3.4 Firmware Loader/Boot Loader ................................................... 229
12.2.4 Modbus Process Image Version .................................................... 229
12.2.5 Modbus Process Image Registers.................................................. 229
12.2.6 Constant Registers ........................................................................ 230
12.2.7 Live Register .................................................................................. 230
12.3 Estimating the Modbus Master CPU Load .......................................... 231
13 CANopen Master and Slave .................................................................. 232
13.1 Object Directory .................................................................................. 232
13.2 Communications Profile ...................................................................... 233
13.2.1 Master Configuration ...................................................................... 237
13.3 Data Exchange ................................................................................... 239
13.3.1 Controller Communication Objects ................................................. 239
13.3.2 Fieldbus-Specific Addressing ......................................................... 239
13.3.3 Examples for the Definition of PFC Fieldbus Variables .................. 243
13.3.3.1 CODESYS Access to PFC Variables ......................................... 243
13.3.3.2 Maximum Indices ...................................................................... 244
13.3.4 CANopen Master Control Configuration ......................................... 246
13.3.4.1 Selecting the Master .................................................................. 246
13.3.4.2 Setting the Master Parameters .................................................. 247
13.3.4.3 Adding Slaves ........................................................................... 249
13.3.4.4 Configuring the Slave PDOs ...................................................... 256
13.3.4.5 Configuring the Service Data Objects ........................................ 259
13.3.5 CANopen Slave Control Configuration ........................................... 262
13.3.5.1 CANopen Variables Configuration ............................................. 263
13.3.5.2 Configuring of CANopen Parameters ........................................ 264
13.4 Fieldbus Coupler Diagnostics ............................................................. 265
13.4.1 BusDiag.lib..................................................................................... 265
13.4.1.1 Creating Diagnostics in CODESYS 2.3...................................... 266
13.4.1.2 Calling the Diagnostics Function Block ...................................... 268
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.4.1.3 Performing Bus Diagnostics Using DiagGetBusState() .............. 269
13.4.1.4 Performing Subscriber Diagnostics Using DiagGetState() ......... 271
13.4.1.5 Evaluating the CANopen Diagnostics (Emergency Messages) .. 273
13.4.2 WagoCANopenDiag.lib .................................................................. 275
13.5 Data Exchange between Simple CAN Subscribers and PFC200 in the
CANopen Network .............................................................................. 276
13.6 Data Exchange between CAN Subscribers and the PFC200 in a CAN
Layer2 Network .................................................................................. 279
14 Diagnostics............................................................................................ 280
14.1 Operating and Status Messages ......................................................... 280
14.1.1 Power Supply LEDs ....................................................................... 280
14.1.1.1 A LED ........................................................................................ 280
14.1.1.2 B LED ........................................................................................ 280
14.1.2 System/Fieldbus LEDs ................................................................... 281
14.1.2.1 SYS LED ................................................................................... 281
14.1.2.2 RUN LED .................................................................................. 284
14.1.2.3 I/O LED ..................................................................................... 286
14.1.2.4 MS LED ..................................................................................... 287
14.1.2.5 CAN LED................................................................................... 288
14.1.3 Network Connection LEDs ............................................................. 289
14.1.3.1 LNK LED ................................................................................... 289
14.1.3.2 ACT LED ................................................................................... 289
14.1.4 Memory Card Slot LED .................................................................. 290
14.2 Diagnostics Messages via Flashing Sequences ................................. 291
14.2.1 Flashing Sequences ...................................................................... 291
14.2.2 Example of a Diagnostics Message Indicated by a Flashing
Sequence....................................................................................... 292
14.2.3 Meaning of Blink Codes and Procedures for Troubleshooting ........ 293
14.2.4 Meaning of Blink Codes and Procedures for Troubleshooting ........ 299
15 Service ................................................................................................... 300
15.1 Inserting and Removing the Memory Card.......................................... 300
15.1.1 Inserting the Memory Card ............................................................. 300
15.1.2 Removing the Memory Card .......................................................... 300
15.2 Firmware Changes ............................................................................. 302
15.2.1 Use e!COCKPIT to Update/Downgrade the Firmware .................... 303
15.2.2 Use WAGOupload to Update/Downgrade the Firmware ................. 304
15.2.3 Perform Firmware Update/Downgrade ........................................... 305
15.3 Updating Root Certificates .................................................................. 306
16 Removal ................................................................................................. 307
16.1 Removing Devices.............................................................................. 307
16.1.1 Removing the Controller ................................................................ 307
17 Disposal ................................................................................................. 308
17.1 Electrical and electronic equipment .................................................... 308
17.2 Packaging........................................................................................... 308
18 Use in Hazardous Environments ......................................................... 310
18.1 Marking Configuration Examples ........................................................ 311
18.1.1 Marking for Europe According to ATEX and IECEx ........................ 311
Manual
750-8214 PFC200; G2; 2ETH RS CAN
18.1.2 Marking for the United States of America (NEC) and Canada (CEC)315
18.2 Installation Regulations....................................................................... 318
18.2.1 Special Notes including Explosion Protection ................................. 318
18.2.2 Special Notes Regarding ANSI/ISA Ex .......................................... 320
19 Appendix ............................................................................................... 321
19.1 Configuration Dialogs ......................................................................... 321
19.1.1 Web-Based-Management (WBM) .................................................. 321
19.1.1.1 “Information” Tab ....................................................................... 321
19.1.1.1.1 “Device Status” Page ............................................................ 321
19.1.1.1.2 “Vendor Information” Page .................................................... 323
19.1.1.1.3 “PLC Runtime Information” Page .......................................... 324
19.1.1.1.4 “WAGO Software License Agreement” Page ........................ 326
19.1.1.1.5 “Open Source Licenses” Page .............................................. 327
19.1.1.1.6 “WBM Third Party License Information” Page ....................... 328
19.1.1.1.7 “Trademarks Information” Page ............................................ 329
19.1.1.1.8 “WBM Version” Page ............................................................ 330
19.1.1.2 “Configuration” Tab.................................................................... 331
19.1.1.2.1 “PLC Runtime Configuration” Page ....................................... 331
19.1.1.2.2 “TCP/IP Configuration” Page ................................................ 334
19.1.1.2.3 “Ethernet Configuration” Page............................................... 336
19.1.1.2.4 Configuration of Host and Domain Name” Page ................... 339
19.1.1.2.5 “Routing” Page...................................................................... 341
19.1.1.2.6 “Clock Settings” Page ........................................................... 346
19.1.1.2.7 “Configuration of Serial Interface RS232/RS485” Page ......... 348
19.1.1.2.8 “Configuration of Service Interface” Page ............................. 349
19.1.1.2.9 “Create Bootable Image” Page.............................................. 350
19.1.1.2.10 “Firmware Backup” Page ...................................................... 351
19.1.1.2.11 “Firmware Restore” Page ...................................................... 353
19.1.1.2.12 “Active System” Page ........................................................... 355
19.1.1.2.13 “Mass Storage” Page ............................................................ 356
19.1.1.2.14 “Software Uploads” Page ...................................................... 357
19.1.1.2.15 “Configuration of Network Services” Page ............................ 358
19.1.1.2.16 “Configuration of NTP Client” Page ....................................... 360
19.1.1.2.17 “PLC Runtime Services” Page .............................................. 361
19.1.1.2.18 “SSH Server Settings” Page ................................................. 363
19.1.1.2.19 “DHCP Server Configuration” Page ...................................... 364
19.1.1.2.20 “Configuration of DNS Server” Page ..................................... 365
19.1.1.2.21 “Status overview” Page ......................................................... 366
19.1.1.2.22 “Configuration of Connection <n>” Page ............................... 367
19.1.1.2.23 “Configuration of General SNMP Parameters” Page ............. 373
19.1.1.2.24 “Configuration of SNMP v1/v2c Parameters” Page ............... 374
19.1.1.2.25 “Configuration of SNMP v3 Users” Page ............................... 376
19.1.1.2.26 Page “Docker® Settings” ....................................................... 378
19.1.1.2.27 “WBM User Configuration” Page ........................................... 379
19.1.1.3 “Fieldbus” Tab ........................................................................... 380
19.1.1.3.1 “OPC UA Status” Page ......................................................... 380
19.1.1.3.2 “OPC UA Configuration” Page .............................................. 381
19.1.1.3.3 “OPC UA Information Model” Page ....................................... 384
19.1.1.3.4 “OPC UA Server Certificates” Page ...................................... 385
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.5 OPC UA Client Certificates” Page ......................................... 387
19.1.1.3.6 “MODBUS Services Configuration” Page .............................. 389
19.1.1.3.7 “BACnet Status” Page ........................................................... 390
19.1.1.3.8 “BACnet Configuration” Page ................................................ 391
19.1.1.3.9 “BACnet Storage Location” Page .......................................... 393
19.1.1.3.10 “BACnet Files” Page ............................................................. 395
19.1.1.4 “Security” Tab ............................................................................ 396
19.1.1.4.1 “OpenVPN / IPsec Configuration” Page ................................ 396
19.1.1.4.2 “General Firewall Configuration” Page .................................. 398
19.1.1.4.3 “Interface Configuration” Page .............................................. 399
19.1.1.4.4 “Configuration of MAC Address Filter” Page ......................... 400
19.1.1.4.5 “Configuration of User Filter” Page ........................................ 402
19.1.1.4.6 “Certificates” Page ................................................................ 404
19.1.1.4.7 “Boot mode configuration” Page............................................ 405
19.1.1.4.8 “Security Settings” Page ....................................................... 406
19.1.1.4.9 “Advanced Intrusion Detection Environment (AIDE)” Page ... 407
19.1.1.4.10 “WAGO Device Access” Page............................................... 409
19.1.1.5 “Diagnostic” Tab ........................................................................ 410
19.1.1.5.1 “Diagnostic Information” Page ............................................... 410
19.1.2 Console-Based-Management (CBM) ............................................. 411
19.1.2.1 “Information” Menu .................................................................... 411
19.1.2.1.1 “Information” > “Controller Details” Submenu ........................ 411
19.1.2.1.2 “Information” > “Network Details” Submenu .......................... 412
19.1.2.2 “PLC Runtime” Menu ................................................................. 413
19.1.2.2.1 “PLC Runtime” > “Information” Submenu .............................. 413
19.1.2.2.2 “Information” > “Runtime Version” Submenu ......................... 414
19.1.2.2.3 “Information” > “Webserver Version” Submenu ..................... 414
19.1.2.2.4 “Information” > “State” Submenu ........................................... 414
19.1.2.2.5 “Information” > “Number of Tasks” Submenu ........................ 415
19.1.2.2.6 “Information” > “Project Details” Submenu ............................ 415
19.1.2.2.7 “Information” > “Tasks” Submenu.......................................... 415
19.1.2.2.8 “Tasks” > “Task n” Submenu ................................................. 416
19.1.2.2.9 “PLC Runtime” > “General Configuration” Submenu ............. 416
19.1.2.2.10 “General Configuration” > “PLC Runtime Version” Submenu 417
19.1.2.2.11 “General Configuration” > “Home Dir On SD Card” Submenu417
19.1.2.2.12 “PLC Runtime” > “WebVisu” Submenu.................................. 418
19.1.2.3 “Networking” Menu .................................................................... 419
19.1.2.3.1 “Networking” > “Host/Domain Name” Submenu .................... 419
19.1.2.3.2 “Host/Domain Name” > “Hostname” Submenu ...................... 420
19.1.2.3.3 “Host/Domain Name” > “Domain Name” Submenu ............... 420
19.1.2.3.4 “Networking” > “TCP/IP” Submenu........................................ 420
19.1.2.3.5 “TCP/IP” > “IP Address” Submenu ........................................ 421
19.1.2.3.6 “IP Address” > “Xn“ Submenu ............................................... 421
19.1.2.3.7 “TCP/IP” > “Default Gateway” Submenu ............................... 422
19.1.2.3.8 “Default Gateway” > “Default Gateway n” Submenu.............. 422
19.1.2.3.9 “TCP/IP” > “DNS Server” Submenu ...................................... 423
19.1.2.3.10 “Networking” > “Ethernet” Submenu ...................................... 423
19.1.2.3.11 “Ethernet” > “Switch Configuration” Submenu ....................... 424
19.1.2.3.12 “Ethernet” > “Ethernet Ports” Submenu ................................. 424
19.1.2.3.13 “Ethernet Ports” > “Interface Xn” Submenu ........................... 425
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4 “Firewall” Menu .......................................................................... 426
19.1.2.4.1 “Firewall” > “General Configuration” Submenu ...................... 427
19.1.2.4.2 “General Configuration” > “Interface xxx” Submenu .............. 428
19.1.2.4.3 “Firewall” > “MAC Address Filter” Submenu .......................... 430
19.1.2.4.4 “MAC Address Filter” > “MAC address filter whitelist” Submenu431
19.1.2.4.5 “MAC address filter whitelist” > “Add new / No (n)” Submenu 431
19.1.2.4.6 “Firewall” > “User Filter” Submenu ........................................ 432
19.1.2.4.7 “User Filter” > “Add New / No (n)” Submenu ......................... 433
19.1.2.5 “Clock” Menu ............................................................................. 434
19.1.2.6 “Administration” Menu ............................................................... 435
19.1.2.6.1 “Administration” > “Users” Submenu ..................................... 436
19.1.2.6.2 “Administration” > “Create Image” Submenu ......................... 436
19.1.2.7 “Package Server” Menu ............................................................. 437
19.1.2.7.1 “Package Server” > “Firmware Backup” Submenu ................ 437
19.1.2.7.2 “Firmware Backup” > “Auto Update Feature” Submenu ........ 438
19.1.2.7.3 “Firmware Backup” > “Destination” Submenu........................ 438
19.1.2.7.4 “Package Server” > “Firmware Restore” Submenu ............... 439
19.1.2.7.5 “Firmware Restore” > “Select Package” Submenu ................ 439
19.1.2.7.6 “Package Server” > “System Partition” Submenu .................. 440
19.1.2.8 “Mass Storage” Menu ................................................................ 441
19.1.2.8.1 “Mass Storage” > “SD Card” Submenu ................................. 441
19.1.2.9 “Software Uploads” Menu .......................................................... 442
19.1.2.10 “Ports and Services” Menu ........................................................ 443
19.1.2.10.1 “Ports and Services” > “Telnet” Submenu ............................. 444
19.1.2.10.2 “Ports and Services” > “FTP” Submenu ................................ 444
19.1.2.10.3 “Ports and Services” > “FTPS” Submenu .............................. 445
19.1.2.10.4 “Ports and Services” > “HTTP” Submenu .............................. 445
19.1.2.10.5 “Ports and Services” > “HTTPS” Submenu ........................... 446
19.1.2.10.6 “Ports and Services” > “NTP” Submenu ................................ 446
19.1.2.10.7 “Ports and Services” > “SSH” Submenu ................................ 447
19.1.2.10.8 “Ports and Services” > “TFTP” Submenu .............................. 447
19.1.2.10.9 “Ports and Services” > “DHCPD” Submenu .......................... 448
19.1.2.10.10 “DHCPD” > “Xn” Submenu .................................................... 448
19.1.2.10.11 “Ports and Services” > “DNS” Submenu................................ 449
19.1.2.10.12 “Ports and Services” > “IOCHECK PORT” Submenu ............ 450
19.1.2.10.13 “Ports and Services” > “Modbus TCP” Submenu .................. 450
19.1.2.10.14 “Ports and Services” > “Modbus UDP” Submenu .................. 451
19.1.2.10.15 “Ports and Services” > “OPC UA” Submenu ......................... 451
19.1.2.10.16 “…” > “Firewall Status” Submenu .......................................... 452
19.1.2.10.17 “Ports and Services” > “PLC Runtime Services” Submenu.... 453
19.1.2.10.18 “PLC Runtime Services” > “CODESYS 2” Submenu ............. 454
19.1.2.10.19 “PLC Runtime Services” > “e!RUNTIME” Submenu .............. 455
19.1.2.11 “SNMP” Menu............................................................................ 456
19.1.2.11.1 “SNMP” > “General SNMP Configuration” Submenu ............. 456
19.1.2.11.2 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu 457
19.1.2.11.3 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration”
Submenu .............................................................................. 457
19.1.2.11.4 “SNMP” > “SNMP v3 Configuration” Submenu...................... 458
19.1.2.11.5 “SNMP” > “(Secure)SNMP firewalling” Submenu .................. 459
19.2 Process Data Architecture .................................................................. 460
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.2.1 Digital Input Modules...................................................................... 461
19.2.1.1 1 Channel Digital Input Module with Diagnostics ....................... 461
19.2.1.2 2 Channel Digital Input Modules ................................................ 461
19.2.1.3 2 Channel Digital Input Module with Diagnostics ....................... 461
19.2.1.4 2 Channel Digital Input Module with Diagnostics and Output
Process Data ............................................................................. 462
19.2.1.7 8 Channel Digital Input Module NAMUR with Diagnostics and
Output Process Data ................................................................. 463
19.2.1.8 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data ............................................................................. 464
19.2.1.9 16 Channel Digital Input Modules .............................................. 465
19.2.2 Digital Output Modules ................................................................... 466
19.2.2.1 1 Channel Digital Output Module with Input Process Data ......... 466
19.2.2.2 2 Channel Digital Output Modules ............................................. 466
19.2.2.3 2 Channel Digital Input Modules with Diagnostics and Input
Process Data ............................................................................. 467
19.2.2.4 4 Channel Digital Output Modules ............................................. 468
19.2.2.5 4 Channel Digital Output Modules with Diagnostics and Input
Process Data ............................................................................. 468
19.2.2.6 8 Channel Digital Output Module ............................................... 468
Process Data ............................................................................. 469
19.2.2.8 16 Channel Digital Output Modules ........................................... 469
19.2.2.9 8 Channel Digital Input/Output Modules .................................... 470
19.2.3 Analog Input Modules .................................................................... 471
19.2.3.1 1 Channel Analog Input Modules ............................................... 471
19.2.3.3 2 Channel Analog Input Modules HART .................................... 472
19.2.3.6 3-Phase Power Measurement Module ....................................... 475
19.2.4 Analog Output Modules.................................................................. 477
19.2.4.1 2 Channel Analog Output Modules ............................................ 477
19.2.4.2 4 Channel Analog Output Modules ............................................ 477
19.2.5 Specialty Modules .......................................................................... 478
19.2.5.1 Counter Modules ....................................................................... 478
19.2.5.2 Pulse Width Modules ................................................................. 481
19.2.5.3 Serial Interface Modules with Alternative Data Format .............. 481
19.2.5.4 Serial Interface Modules with Standard Data Format ................. 482
19.2.5.5 Serial Interface Modules ............................................................ 482
19.2.5.6 Data Exchange Module ............................................................. 483
19.2.5.7 SSI Transmitter Interface Modules ............................................ 483
19.2.5.8 Incremental Encoder Interface Modules .................................... 484
19.2.5.9 DC-Drive Controller ................................................................... 486
19.2.5.10 Stepper Controller ..................................................................... 487
19.2.5.11 RTC Module .............................................................................. 488
19.2.5.12 DALI/DSI Master Module ........................................................... 488
19.2.5.13 DALI Multi-Master Module ......................................................... 489
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.2.5.14 LON® FTT Module ..................................................................... 492
19.2.5.15 EnOcean Radio Receiver .......................................................... 492
19.2.5.16 MP Bus Master Module ............................................................. 493
19.2.5.17 Bluetooth® RF-Transceiver ........................................................ 493
19.2.5.18 Vibration Velocity/Bearing Condition Monitoring VIB I/O ............ 494
19.2.5.19 KNX/EIB/TP1 Module ................................................................ 495
19.2.5.20 AS-interface Master Module ...................................................... 495
19.2.6 System Modules ............................................................................ 497
19.2.6.1 System Modules with Diagnostics ............................................. 497
19.2.6.2 Filter Module.............................................................................. 497
19.2.6.3 Binary Space Module ................................................................ 497
19.3 CODESYS V2 Libraries ...................................................................... 499
19.3.1 General Libraries ........................................................................... 499
19.3.1.1 CODESYS System Libraries ..................................................... 499
19.3.1.2 SysLibCom.lib ........................................................................... 500
19.3.1.3 SysLibFile.lib ............................................................................. 500
19.3.1.4 SysLibFileAsync.lib.................................................................... 501
19.3.1.5 SysLibRtc.lib.............................................................................. 502
19.3.1.6 BusDiag.lib ................................................................................ 503
19.3.1.7 mod_com.lib .............................................................................. 503
19.3.1.8 SerComm.lib.............................................................................. 503
19.3.1.9 WagoConfigToolLIB.lib .............................................................. 504
19.3.1.10 WagoLibCpuUsage.lib ............................................................... 521
19.3.1.11 WagoLibDiagnosticIDs.lib .......................................................... 522
19.3.1.12 WagoLibLed.lib.......................................................................... 522
19.3.1.13 WagoLibNetSnmp.lib ................................................................. 522
19.3.1.14 WagoLibNetSnmpManager.lib ................................................... 522
19.3.1.15 WagoLibSSL.lib ......................................................................... 523
19.3.1.16 WagoLibTerminalDiag.lib........................................................... 523
19.3.2 Libraries for a CANopen and CANLayer2 Link ............................... 524
19.3.2.1 WagoCANLayer2_02.lib ............................................................ 524
19.3.2.2 WagoCANopen_02.lib ............................................................... 524
19.3.2.3 WagoCANopenDiag.lib .............................................................. 525
List of Figures ................................................................................................ 526
List of Tables .................................................................................................. 530
Manual
WAGO I/O System 750 Notes about this Documentation 15
750-8214 PFC200; G2; 2ETH RS CAN
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 “PFC200; G2; 2ETH RS CAN”
controller (750-8214).
This documentation is only applicable from FW Version 03.10.08(22).
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
16 Notes about this Documentation WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
• 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
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
Additional Information:
Refers to additional information which is not an integral part of this
documentation (e.g., the Internet).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
1.5 Number Notation

Table 1: 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 2: 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
WAGO I/O System 750 Important Notes 21
750-8214 PFC200; G2; 2ETH RS CAN
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
22 Important Notes WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
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.3.1 Improper Use
Improper use of the product is not permitted. Specifically, improper use occurs in
the following cases:
• Non-observance of the intended use.
• Use without protective measures in an environment in which moisture, salt

water, salt spray mist, dust, corrosive fumes, gases, direct sunlight or
ionizing radiation can occur.
• Use of the product in areas with special risk that require flawless
continuous operation and in which failure or operation of the product can
result in an imminent risk to life, limb or health or cause serious damage to
property or the environment (such as the operation of nuclear power plants,
weapon systems , aircraft and motor vehicles).
2.1.3.2 Warranty and Liability
The terms set forth in the General Business & Contractual Conditions apply to
deliveries and services of WAGO GmbH & Co. KG, and the WAGO Software
License Contract applies to software products and products with integrated
software. Both are available at www.wago.com. In particular, the warranty is void
if:
• The product is improperly used.
• The deficiency (hardware and software configurations) is due to special

instructions.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
• The hardware or software has been modified by the user or a third party.
Individual agreements always have priority.
2.1.3.3 Obligations of Installers/Operators
The installers and operators bear responsibility for the safety of an installation or
a system assembled with the products. The installer/operator is responsible for
proper installation and safety of the system. All laws, standards, guidelines, local
regulations and accepted technology standards and practices applicable at the
time of installation, and the instructions in the the products’ Instructions for Use,
must be complied with. In addition, the Installation regulations specified by
Approvals must be observed. In the event of non-compliance, the products may
not be operated within the scope of the approval.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
Power from SELV/PELV power supply only!

All field signals and field supplies connected to the controller „PFC200; G2; 2ETH
RS CAN“ (750-8214) 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.
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.
Do not exceed maximum values via power contacts!

The maximum current that can flow through the power jumper contacts is 10 A.
The power jumper contacts can be damaged and the permissible operating
temperature can be exceeded by higher current values.
When configuring the system, do not exceed the permissible maximum current
value. If there is a higher power requirement, you must use an additional supply
module to provide the field voltage.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Do not exceed the maximum total current for I/O modules (5 VDC) via data
contacts!
The maximum permissible total current for internal system supply of the I/O
modules may not be exceeded. The permissible total current is specified in the
technical data of the head station and power supply. The data contacts for
internal system supply can be damaged and the permissible operating
temperature can be exceeded by higher values.
When configuring the system, do not exceed the permissible total current. If there
is a higher power requirement, you must use an additional supply to provide the
system voltage (5 VDC)!
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).
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.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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.
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
750-8214 PFC200; G2; 2ETH RS CAN
2.3 Licensing Terms of the Software Package Used

The firmware for the “PFC200; G2; 2ETH RS CAN” controller (750-8214)
contains open-source software.
The licence conditions of the software packages are stored in the controller in
text form. They can be accessed via the WBM page “Legal Information” > “Open
Source Software.”
You can obtain the source code with licensing terms of the open-source software
from WAGO GmbH & Co. KG on request. Send your request to
[email protected] with the subject “Controller Board Support Package.”
2.4 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.
• Please note the risks of using cloud services!

If you use third-party cloud services, sensitive data is transferred to the
cloud service provider at one's own responsibility. External access may
result in manipulated data and/or unwanted control commands affecting the
Manual
750-8214 PFC200; G2; 2ETH RS CAN
performance of your control system.
Use encryption methods to protect your data and observe the information
provided by the Federal Office for Information Security – “Cloud: Risks and
Security Tips”.
Observe comparable publications of the competent, public institutions of
your country.
Manual
30 Overview WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
3 Overview
The controller 750-8214(PFC200; G2; 2ETH RS CAN) is an automation device
that can perform control tasks of a PLC. It is suitable for mounting on a DIN rail
and stands out on account of its various interfaces.
This controller can be used for applications in mechanical and systems

engineering, in the processing industry and in building technology.
You can connect all available I/O modules of the WAGO-I/O-SYSTEM 750 (750
and 753 Series) to the controller, enabling it to internally process analog and
digital signals from the automation environment, or to supply these signals to
other devices via one of the available interfaces.
Automation tasks can be executed in all IEC 61131-3-compatible languages with

the WAGO-I/O-PRO or e!COCKPIT programming system, depending on the
runtime system set (CODESYS V2 or e!RUNTIME).
The implementation of the task processing in the runtime system for Linux® has
been optimized with real-time extensions in order to provide maximum
performance for automation tasks. Web visualization is also provided as
visualization in addition to the development environment.
Under CODESYS V2, the controller provides 16 MB of program memory (flash),

64 MB of data memory (RAM) as well as 128 kB of retentive memory (retain and
flag variables in an integrated NVRAM) for IEC-61131-3 programming in
CODESYS applications.
Under e!RUNTIME, the controller provides 32 MB of program memory (flash),
128 MB of data memory (RAM) as well as 128 kB of retentive memory (retain and
flag variables in an integrated NVRAM) for IEC-61131-3 programming in
CODESYS applications.
The controller has a slot for an SD card. The SD card can be used to transfer
device parameters, boot projects and other files from one controller to another.
The SD card can be accessed via FTP as an additional drive.
Memory card is not included in the scope of delivery!

Note, the controller is delivered without memory card.
To use a memory card, you must order one separately. The controller can also
be operated without memory card expansion, the use of a memory card is
optional.
</dg_
Manual
WAGO I/O System 750 Overview 31
750-8214 PFC200; G2; 2ETH RS CAN
Only use recommended memory cards!

Use only the SD memory cards available from WAGO (item No. 758-879/000-
001 and 758-879/000-2108) as these are suitable for industrial applications
subjected to environmental extremes and for use in this device.
Compatibility with other commercially available storage media cannot be
guaranteed.
</dg_
Two ETHERNET interfaces and the integrated, configurable switch enable wiring
in all necessary configurations with one common network where both ports share
a common IP address or with two separate networks where each port has its own
IP address.
The physical interfaces (ports) are assigned via logical bridges and can be e.g.,
configured via the WBM.
Both of these interfaces support:
• 10BASE-T / 100BASE-TX
• Full/Half duplex
• Autonegotiation
• Auto-MDI(X) (automatic uplink and crossover switching)
The following fieldbus circuits are implemented for exchange of process data:
• Modbus TCP Master/Slave
• Modbus UDP Master/Slave
• Modbus RTU Master/Slave (via RS-232 or RS-485)
• CANopen Master/Slave
In the controller, all input signals from the sensors are combined. After
connecting the controller, all of the I/O modules on the bus node are detected
and a local process image is created from these. Analog and specialty module
data is sent via words and/or bytes; digital data is sent bit by bit.
No direct access from fieldbus to the process image for I/O modules!
Any data that is required from the I/O module process image must be explicitly
mapped in the CODESYS program to the data in the fieldbus process image and
vice versa! Direct access is not possible!
Manual
32 Overview WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
The fieldbus configuration can be defined with the WAGO-I/O-PRO or
e!COCKPIT controller configuration, depending on the set runtime system
(CODESYS V2 or e!RUNTIME).
A Web-based management system (WBM) is also available as a configuration

aid. This system includes various dynamic HTML pages from which, among other
things, information about configuration and the status of the controller can be
called up. The WBM is already stored in the device and is presented and
operated using a web browser. You can also save your own HTML pages in the
implemented file system, or call up programs directly.
In the controller's initial state, the installed firmware is based on Linux®, with
special real-time extensions of the RT-Preempt patch. In addition, the following
application programs are also installed on the controller, along with a number of
different auxiliary programs:
• a SNMP server/client
• a FTP server, a FTPS server (explicit connections only)
• a SSH server/client
• a Web server
• a NTP client
• a BootP and DHCP client
• a DHCP server
• a DNS server
• a CODESYS Runtime Environment (CODESYS V2 or e!RUNTIME,

selectable)
Based on IEC-61131-3 programming, data processing takes place on site in the

controller. The logical process results can be output directly to the actuators or
transmitted via a connected fieldbus to the higher level controller.
Manual
WAGO I/O System 750 Properties 33
750-8214 PFC200; G2; 2ETH RS CAN
4 Properties
4.1 Hardware Description
4.1.1 View
Figure 1: View
Table 3: Legend for Figure “View”

Item Description See section
1 Marking options (Mini WSB) ---
“Display Elements” > “Power
2 LED indicators – power pupply
Supply Indicating Elements”
“Connectors” > “Data
3 Data contacts
Contacts/Local Bus”
CAGE CLAMP® connectors for power “Connectors” > “CAGE
4
supply CLAMP® connectors”
5 Slot for memory card “Slot for Memory Card”
“Connectors” > “Power
Power contacts for power supply of
6 Jumper Contacts/Field
down-circuit I/O modules
Supply”
“Mounting” > “Inserting
Devices”
7 Releasing strap
“Removal” > “Removing
Devices”
Manual
34 Properties WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
“Connectors” > “Service

8 Service Interface (behind the flap)
Interface”
“Operating elements” >
9 Mode selector switch
“Operating Mode Switch”
“Connectors” > “Network
10 ETHERNET connectors – X1, X2
connectors”
“Mounting” > “Inserting
Devices”
11 Safe locking feature
“Removal” > “Removing
Devices”
12 Fieldbus connector – CANopen – X4 “Connecors” > “CANopen”
“Connectors” >
13 Communication interface – X3
“Communication Interface”
“Display Elements” >
14 LED indicators – system “Fieldbus/System Indicating
Elements”
“Operating Elements” >
15 Reset button (in hole)
“Reset Button”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.2 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
4.1.2.1 Production Code
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.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3 Connectors
4.1.3.1 Wiring Level
Figure 3: CAGE CLAMP® connections
Table 4: Legend for figure “CAGE CLAMP® connections”

Contact Description Description
1 24 V System power supply voltage +24 V
2 + Field-side power supply voltage UV
3 - Field-side power supply voltage 0 V
4 Ground Field-side power supply voltage, ground
5 0V System power supply voltage 0 V
6 + Field-side power supply voltage UV
7 - Field-side power supply voltage 0 V
8 Ground Field-side power supply voltage, ground
</dg_
Observe supplementary power supply regulations for use in shipbuilding!

Observe supplementary power supply regulations for shipbuilding and the supply
voltage in Section “Connect Devices” > … > “Supplementary Power Supply
Regulations”!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.2 Service Interface
The service interface is located behind the flap.
The Service interface is used for communication with WAGO-I/O-CHECK and

“WAGO Ethernet Settings”.
Figure 4: Service Interface (Closed and Open Flap)
Table 5: Service Interface

Number Description
1 Open flap
2 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
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.3 Network Connectors
Figure 5: Network Connections – X1, X2
Table 6: Legend for Figure “Network Connections – X1, X2”

Contact Signal Description
1 TD + Transmit Data +
2 TD − Transmit Data −
3 RD + Receive Data +
4 NC Not assigned
5 NC Not assigned
6 RD − Receive Data −
7 NC Not assigned
8 NC Not assigned
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.4 CANopen
Figure 6: CANopen – X4 Fieldbus Connection
Table 7: Legend for Figure “CANopen – X4 Fieldbus Connection”

Contact Signal Description
1 - Not used
2 CAN_L CAN Signal Low
3 GND Ground
4 - Not used
5 Drain Shield Shield termination
6 - Not used
7 CAN_H CAN Signal High
8 - Not used
9 CAN_V+ Not used
DC/DC converters and optocouplers in the fieldbus interface provide electrical

isolation between the CANopen bus system and the electronics.
The cable shield must be applied to the CAN shield. This is terminated to ground
in devices with 1 MΩ (DIN rail contact). A low-impedance connection of the
shielding to ground is possible only from the outside (e.g., by a supply module).
We recommend using central ground contacts for the entire CANopen bus line
shielding.
To minimize reflection at the end of the line, the CANopen line must be
terminated at both ends by a cable termination.
Attention - bus termination!

The CANopen bus segment must be terminated at both ends!
No more than 2 terminations per bus segment may be used!
Terminations may not be used in stub and branch lines!
Operation without proper termination of the CANopen network may result in
transmission errors.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Observe permissible resistor power loss!

For normal operation, 1/4 Watt resistors are sufficient. In the event of a short
circuit (24 V power supply to a bus line), the resistor is subjected to a power loss
of (short-circuit output current from transceiver * power supply voltage). The
resistor must be designed to withstand this power loss level.
Figure 7: CANopen Standard Bus Termination
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.5 Communication Interface
Figure 8: RS-232/RS-485 – Communication Interface – X3
Table 8: Legend for Figure “RS-232/RS-485 – Communication Interface – X3”

RS-232 (DCE) RS-485
Contact
Signal Description Signal Description
1 NC Not assigned NC Not assigned
2 RxD (out) Receive Data NC Not assigned
3 TxD (in) Transmit Data A (Tx/Rx+) Transmit/receive data +
5 FB_GND Ground FB_GND Ground
6 NC Not assigned FB_5V Power Supply
7 RTS (in) Request to Send NC Not assigned
8 CTS (out) Clear to Send B (Tx/Rx−) Transmit/receive data −
Enclosure Shield Shielding Shield Shielding
If the communication interface is opened as an RS-232 interface, the controller

represents data communication equipment (DCE). The RxD and CTS signals are
sent to the communication partner (out), and the TxD and RTS signals are
received by the communication partner (in).
Incorrect parameterization can damage the communication partners!

The voltage levels are −12 V and +12 V for RS-232, and −5 V and +5 V for
RS-485.
If the controller interfaces differ from those of the communication partners
(RS-232 <> RS-485 or RS-485 <> RS-232), this may damage the interface of the
communication partner.
Therefore, always ensure that the controller interface matches those of its
communication partners when configuring these items!
DC/DC converters and optocouplers in the fieldbus interface electrically isolate

the fieldbus system and the electronics.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.5.1 Operating as an RS-232 Interface

Kommuni kati onsansc hlus s
Depending on the device type DTE (Data Terminal Equipment, e.g., PC) or DCE
(Data Communication Equipment, e.g., PFC, modem), the RS-232 signals have
different data directions.
Table 9: Function of RS-232 Signals for DTE/DCE

Data Direction
Contact Signal
DTE DCE
2 RxD Input Output
3 TxD Output Input
5 FB_GND --- ---
7 RTS Output Input
8 CTS Input Output
For a DTE-to-DCE connection, the signals are connected directly (1:1).
Figure 9: Termination with DTE-DCE Connection (1:1)
For a DCE-to-DCE connection, the signal connections are crossed (cross-over).
Figure 10: Termination with DCE-DCE Connection (Cross-Over)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.3.5.2 Operating as an RS-485 Interface
To minimize reflection at the end of the line, the RS-485 line must be terminated
at both ends by a cable termination. If required, one pull-up or pull-down resistor
may be used. These resistors ensure a defined level on the bus when no
subscriber is active, i.e., when all subscribers are in “Tri-state”.
Attention — bus termination!

The RS-485 bus must be terminated at both ends!
No more than two terminations per bus segment may be used!
Terminations may not be used in stub and branch lines!
Drop cables must be kept as short as possible!
Operation without proper termination of the RS-485 network may result in
transmission errors.
Figure 11: RS-485 Bus Termination
Transmission error with ineligible RS-485 configuration!

For baud rates lower than 115200 baud, configure the RS-485 interface with two
stop bits and enabled parity (even or odd) to avoid transmission errors.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.4 System Contacts
4.1.4.1 Data Contacts
Communication between the controller and the I/O modules and system power
supply for the I/O modules is provided via the local bus, which consists of 6 data
contacts designed as self-cleaning gold spring contacts.
Figure 12: 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!
Pay attention to potential equalization from the environment!

The devices are equipped with electronic components that may be destroyed by
electrostatic discharge. When handling the devices, please ensure that
environmental factors (personnel, work space and packaging) are properly
equalized. Do not touch any conducting parts, e.g., data contacts.
Do not exceed the maximum total current for I/O modules (5 VDC) via data
contacts!
The maximum permissible total current for internal system supply of the I/O
modules may not be exceeded. The permissible total current is specified in the
technical data of the head station and power supply. The data contacts for
internal system supply can be damaged and the permissible operating
temperature can be exceeded by higher values.
When configuring the system, do not exceed the permissible total current. If there
is a higher power requirement, you must use an additional supply to provide the
system voltage (5 VDC)!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.4.2 Power Jumper Contacts
The controller 750-8214is equipped with 3 self-cleaning power contacts for

transferring of the field-side power supply to down-circuit I/O modules. These
contacts are designed as spring contacts.
Figure 13: Power Jumper Contacts
Table 10: Legend for Figure “Power Jumper Contacts”

Contact Type Function
Potential transmission (UV)
1 Spring contact
for field supply
Potential transmission (0 V)
2 Spring contact
for field supply
Potential transmission (ground)
3 Spring contact
for 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.
Do not exceed maximum values via power contacts!

The maximum current that can flow through the power jumper contacts is 10 A.
The power jumper contacts can be damaged and the permissible operating
temperature can be exceeded by higher current values.
When configuring the system, do not exceed the permissible maximum current
value. If there is a higher power requirement, you must use an additional supply
module to provide the field voltage.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.5 Display Elements
4.1.5.1 Power Supply LEDs
Figure 14: Power Supply Indicating Elements
Table 11: Legend for Figure “Power Supply Indicating Elements”

Designation Color Description
A Green/off Status of system power supply voltage
B Green/off Status of field-side power supply voltage
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.5.2 System/Fieldbus LEDs
Figure 15: Indicating elements for fieldbus/system
Table 12: Legend for Figure “Fieldbus/System Indicating Elements”

Red/Green/
SYS System status
Orange/Off
Red/Green/
RUN PLC program status
Orange/Off
Red/Green/
I/O Local bus status
Orange/Off
Red/Green/
MS Module status
Orange/Off
Red/Green/
NS Without function
Orange/Off
Red/Green/
CAN CANopen status
Orange/Off
User LED 6, programmable using function
Red/Green/
U6 blocks from the WAGO libraries to control the
Orange/Off
LEDs
Red/Green/
Orange/Off
LEDs
Red/Green/
Orange/Off
LEDs
Red/Green/
Orange/Off
LEDs
Red/Green/
Orange/Off
LEDs
Red/Green/
Orange/Off
LEDs
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.5.3 Network Connector LEDs
Figure 16: Indicating Elements, RJ-45 Jacks
Table 13: Legend for Figure “Indicating Elements, RJ-45 Jacks”

LNK Green/Off ETHERNET connection status
ACT Yellow/Off ETHERNET data exchange
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.5.4 Memory Card Slot LED
Figure 17: Indicating Elements, Memory Card Slot
Table 14: Legend for Figure “Indicating Elements, Memory Card Slot”
SD Yellow/Off Memory card status
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.6 Operating Elements
4.1.6.1 Operating Mode Switch
Figure 18: Mode Selector Switch
The function of the mode selector switch depends on the activated runtime
system (CODESYS V2 or e!RUNTIME).
The following functions apply to the CODESYS V2 runtime system:

</dg_
Table 15: Mode Selector Switch

Item Activation Function
Normal mode
RUN Latching
CODESYS V2 application runs.
Stop
STOP Latching
CODESYS V2 application stopped.
Reset warm start or
Reset cold start
RESET Spring-return
(based on the duration of activation, see Section
“Starting” > “Initiating Reset Functions”)
</dg_
Other functions can also be initiated using the reset button.
The following functions apply to the e!RUNTIME runtime system:

</dg_
Table 16: Mode Selector Switch

Position Actuation Function
Normal operation
RUN Latching
e!RUNTIME applications running.
Stop
STOP Latching
All e!RUNTIME applications have stopped.
Reset warm start or
Reset cold start
RESET Spring-return
(depending on length of actuation, see Section
“Starting” > “Initiating Reset Functions”)
</dg_
Other functions can also be initiated using the reset button.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.6.2 Reset Button
Figure 19: Reset Button
The Reset button is installed behind drilling to prevent operating errors. It is a

shortstroke button with a low actuating force of 1.1 N … 2.1 N (110 gf … 210 gf).
The button can be actuated using a suitable object (e.g., pen).
You can initiate different functions using the Reset button depending on the
position of the mode selector:
• Temporarily set a fixed IP address (“Fixed IP Address” mode, see section

“Commissioning” > “Setting an IP Address” > “Temporarily Setting a Fixed
IP Address”)
• Perform a software reset (restart, see section “Commissioning” > “Initiating

Reset Functions” > “Software Reset”)
• Restore factory setting (factory reset, see section “Service” > “Firmware
Changes” > “Factory Reset”)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.1.7 Memory Card Slot
Figure 20: Slot for SD Memory Card
The slot for the SD memory card is located on the front of the housing. The
memory card is locked in the enclosure by a push/push mechanism. Inserting
and removing the memory card is described in the Section “Service” > “Inserting
and Removing the Memory Card.”
The memory card is protected by a cover flap. The cover cap is sealable.
Memory card is not included in the scope of delivery!

Note, the controller is delivered without memory card.
To use a memory card, you must order one separately. The controller can also
be operated without memory card expansion, the use of a memory card is
optional.
</dg_

guaranteed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.2 Schematic Diagram
Figure 21: Schematic diagram
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.3 Technical Data
4.3.1 Mechanical Data

Table 17: Technical Data – Mechanical Data
Width 112 mm / 4.409 inch
Height 100 mm / 3.937 inch
Depth 71.9 mm / 2.831 inch
Depth from upper edge of DIN-rail 64.7 mm / 2.547 inch
Weight 256.9 g
4.3.2 System Data

</dg_
Table 18: Technical Data – System Data

CPU Cortex A8, 1 GHz
Operating System Real-time Linux® with RT Preemption
Patch
Memory card slot Push-push mechanism,
sealable cover lid
Type of memory card SD and SDHC up to 32 Gbytes
(All guaranteed properties are valid only
in connection with the WAGO memory
cards 758-879/000-001 and
758-879/000-2108.)
4.3.3 Power Supply

Table 19: Technical Data – Power Supply
Power supply 24 VDC (-25 % … +30 %)
Max. input current (24 V) 550 mA
Power failure time acc. IEC 61131-2 Depending on external buffering
Total current for I/O modules (5V) 1700 mA
Isolation 500 V system/supply
Buffer for system power supply!

The system power supply and, if necessary, the field 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.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.3.4 Clock
</dg_
Table 20: Technical Data – Clock

Drift - system clock (25 °C) 20 ppm
Drift - RTC (25 °C) 3 ppm
Buffer time RTC (25 °C) 30 days
4.3.5 Programming
Table 21: Technical Data – Programming
Programming CODESYS V2 WAGO-I/O-PRO V2.3
e!RUNTIME e!COCKPIT
IEC 61131-3 LD, FBD, ST, FC
CODESYS V2 memory configuration
Program memory (Flash) 16 MByte
Data memory (RAM) 64 MByte
Non-volatile memory (NVRAM, 128 kByte
Retain + Flags)
e!RUNTIME memory configuration
Program memory (flash) 32 MByte
Data memory (RAM) 128 MByte
Non-volatile memory (NVRAM, 128 kByte
Retain + Flags)
Retain variables max. CODESYS V2 10,000
e!RUNTIME Not specified
4.3.6 Local Bus

Table 22: Technical Data – Local Bus
Number of I/O modules (per node) 64
with bus extension 250
Input and output CODESYS V2 1,000 words
process image (max.) e!RUNTIME Not specified
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.3.7 ETHERNET
Table 23: Technical Data – ETHERNET
ETHERNET 2 x RJ-45 (switched or separated mode)
Transmission medium Twisted Pair S-UTP, 100 Ω, Cat 5,
100 m maximum cable length
Baud rate 10/100 Mbit/s; 10Base-T/100Base-TX
Protocols DHCP, DNS, SNTP, FTP, FTPS (only
explicit connections), SNMP, HTTP,
HTTPS, SSH, Modbus (TCP, UDP)
Modbus input and CODESYS V2 1,000 words,
output process image, also with Modbus access to the flag
max. area (see Section "Modbus" > … >
"Flag Area")
e!RUNTIME 32,000 words
4.3.8 CANopen
Table 24: Technical Data – CANopen
CANopen input and output process 2000 words
image max.
4.3.9 Communication Interface

Table 25: Technical Data – Communication Interface
Interface 1 x serial interface per TIA/EIA 232 and
TIA/EIA 485 (switchable), 9-pole D-sub
female connector
Protocols WAGO Service Communication,
Linux console as well as application-
specific protocols (Modbus RTU, etc.)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.3.10 Connection Type

Table 26: Technical Data – Field Wiring
Connection technology CAGE CLAMP®
Conductor cross-section 0.08 mm² … 2.5 mm², AWG 28 … 14
Strip length 8 mm … 9 mm / 0.33 in
Table 27: Technical Data – Power Jumper Contacts

Power jumper contacts Spring contact, self-cleaning
Table 28: Technical Data – Data Contacts

Data contacts Slide contact, hard gold plated, self-
cleaning
4.3.11 Climatic Environmental Conditions

Table 29: Technical Data – Climatic Environmental Conditions
Surrounding air temperature, operation 0 … 55 °C
Surrounding air temperature, storage −25 … +85 °C
Relative humidity without condensation 5 … 95 % without condensation
Operating altitude above sea level
without temperature derating 0 … 2000 m
with temperature derating 2000 … 5000 m: 0,5 K per 100 m
max. 5000 m
Pollution degree 2
Overvoltage category II
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
750-8214 PFC200; G2; 2ETH RS CAN
4.4 Approvals
For current approvals, please go to: www.wago.com/<Item number>.
The following approvals have been granted to the “PFC200; G2; 2ETH RS CAN”
controller (750-8214):
Conformity Marking
Ordinary
UL61010-2-201
Locations
Korea Certification MSIP-REM-W43-PFC750
The following Ex approvals have been granted to the “PFC200; G2; 2ETH RS
CAN” controller (750-8214):
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
2020312310000213
Ex nA IIC T4 Gc
EAC RU C-DE.AM02.B.00163/19
2Ex e IIC T4 Gc X
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The following ship approvals have been granted to the “PFC200; G2; 2ETH RS
CAN” controller (750-8214):
ABS (American Bureau of Shipping)
BV (Bureau Veritas)
DNV GL
[Temperature: B, Humidity: B, Vibration: B, EMC: B, Enclosure: (*)]
(*) Required protection according to the rules shall be provided upon
installation on board.
LR (Lloyd’s Register) Env. 1, 2, 3, 4
PRS (Polski Rejestr Statków)
RINA (Registro Italiano Navale)
For more information about the ship approvals:

Note the “Supplementary Power Supply Regulations” section for the ship
approvals.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4.5 Standards and Guidelines

The “PFC200; G2; 2ETH RS CAN” controller (750-8214) fulfills the following
standards and regulations:
Electrical Equipment For UL61010-1

Measurement, Control, and Laboratory
Use; Part 1: General Requirements
Electrical Equipment For CAN/CSA C22.2 No. 61010-1-12

Measurement, Control, and Laboratory
Use; Part 1: General Requirements
The “PFC200; G2; 2ETH RS CAN” controller (750-8214) fulfills the following
safety standards:
Safety requirements for electrical UL61010-2-201

equipment for measurement,
control and laboratory use
Part 2-201: Particular requirements
for control equipment
Safety requirements for electrical CAN/CSA-IEC 61010-2-201:14

equipment for measurement,
control and laboratory use
Part 2-201: Particular requirements
for control equipment
The “PFC200; G2; 2ETH RS CAN” controller (750-8214) fulfills the following EMC
standards:
EMC CE-Immunity to interference EN 61000-6-2
EMC CE-Emission of interference EN 61000-6-3
Manual
WAGO I/O System 750 Function Description 61
750-8214 PFC200; G2; 2ETH RS CAN
5 Function Description
</dg_
5.1 Network
5.1.1 Interface Configuration

The X1 and X2 network interfaces of the controller are connected with an
integrated configurable 3-port switch, in which the third port is connected to the
CPU.
The two interfaces and configurable switch enable wiring for:
• One common network where both ports share a common IP address.
• Two separate networks where each port has its own IP address.
The physical interfaces (ports) are assigned via logical bridges and can be e.g.,
configured via the WBM.
Figure 22: Example of Interface Assignment via WBM
For network interfaces X1 … X<n>, fixed IP addresses can be set temporarily

(“Fix IP Address” mode). The setting is carried out with the Reset button (see
Section “Commissioning” > … > “Temporarily Setting Fixed IP Addresses”).
Setting a fixed IP address has no effect on the mode previously set.
5.1.1.1 Operation in Switch Mode
For operation in Switch mode, the TCP/IP settings such as the IP address or
subnet mask apply to both X1 and X2.
When switching to Switch mode, the X1 settings are applied as a new common
configuration for X1 and X2.
The device is then no longer accessible via the IP address previously set for X2.
This must be taken into account for CODESYS applications that use X2 for
communication.
Manual
62 Function Description WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
5.1.1.2 Operation with Separate Network Interfaces
When operating with separate network interfaces, both ETHERNET interfaces

can be configured and used separately.
When switching to operating with separate interfaces, interface X2 is initialized

with the setting values last valid for it. The connections on the X1 interface
persist.
When operating with separate interfaces and fixed IP address, the device can still
be accessed via the interface X2 via the regular IP address.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.1.3 MAC ID and IP Address Assignment Examples
One common network with one common IP address for both ports
Figure 23: One Bridge with Two Ports
Table 30: MAC ID and IP Address Assignment for One Bridge with Two Ports
Bridge MAC ID IP Addr. Port MAC ID Port MAC ID
1 01 1 X1 02 X2 03
Two separate networks where each port has its own IP address
Figure 24: Two Bridges with One/One Ports
Table 31: MAC ID and IP Address Assignment for Two Bridges with One/One Ports
Bridge MAC ID IP Addr. Port MAC ID Port MAC ID
1 01 1 X1 01
2 02 2 X2 02
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.2 Network Security
5.1.2.1 Users and Passwords
Several groups of users are provided in the controller which can be used for
various services.
Default passwords are set for all users. We strongly recommend changing these
passwords on startup!
Change passwords
Default passwords are documented in these instructions and therefore do not
offer adequate protection! Change the passwords to meet your particular needs.
5.1.2.1.1 Services and Users
All password-protected services and their associated users are listed in the
following table.
Table 32: Services and Users

Users
Linux
Service SNMP
root admin user
Web Based Management (WBM) X X X
Linux console X X X
Console Based Management (CBM) X
CODESYS X
Telnet X X X
FTP X X X
FTPS X X X
SSH X X X
SNMP X
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.2.1.2 WBM User Group
The WBM uses part of the Linux users.
Table 33: WBM Users

Users Permissions Default Password
root All (administrator) wago
admin All (administrator) wago
user Supported to a limited extent user
guest Display only ---
General Rights of WBM Users

The WBM users “root”, “admin” and “user” have rights beyond the WBM to
configure the system and install software.
Change passwords
More information is available in the Section “WBM User Administration”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.2.1.3 Linux User Group
The Linux user group includes the actual users of the operating system, which is
likewise used by most services.
Table 34: Linux Users

User Special Feature Home Directory Default Password
root Super user /root wago
admin CODESYS user /home/admin wago
user Normal user /home/user user
You can configure passwords for these users via a terminal connection.
Change passwords
Note password length!

For CODESYS, the password length must be greater than or equal to 1 character
and less than 60 characters!
5.1.2.1.4 SNMP User Group
The SNMP service manages its own users. In its initial state, no users are stored
in the system.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.2.2 Web Protocols for WBM Access
The HTTP and HTTPS web protocols can be used to access the WBM pages for
the controller. HTTPS is preferred because it uses the SSL/TLS protocol. The
SSL/TLS protocol ensures secure communication through encryption and
authentication
The default setting for the controller allows strong encryption, but uses only
simple authentication methods. As authentication for any secure communication
channel plays a central role, it is strongly recommended that you use secure
authentication. The security certificate saved on the controller is the basis for
authentication. The default location for the security certificate is:
/etc/lighttpd/https-cert.pem
As delivered, the controller uses a generic security certificate based on x509. To

allow secure authentication, you must replace the generic security certificate with
a security certificate specific for the individual device.
5.1.2.2.1 TLS Encryption
When an HTTPS connection is established, the Web browser and Webserver

negotiate what TLS version and what cryptographic method are to be used.
The “TLS Configuration” group of the WBM page “Security” can be used to switch
the cryptographic methods allowed for HTTPS and the TLS versions that can be
used.
The settings “Strong” and “Standard” are possible.

If “Strong” is set, the Webserver only allows TLS Version 1.2 and strong
algorithms.
Older software and older operating systems may not support TLS 1.2 and
encryption algorithms.
If “Standard” is set, TLS 1.0, TLS 1.1 and TLS 1.2 are allowed, as well as
cryptographic methods that are no longer considered secure.
BSI Technical Guidelines TR-02102

The rules for the “Strong” setting are based on technical guidelines TR-02102 of
the German Federal Office for Information Security.
You can find the guidelines on the Internet at: https://www.bsi.bund.de >
“Publications” > “Technical Guidelines.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
BSI Guidelines on Migration to TLS 1.2

The German Federal Office for Information Security guidelines on migration to
TLS 1.2 contain “compatibility matrices” that show what software is comparable
with TLS 1.2.
You can find the guidelines on the Internet at: https://www.bsi.bund.de > “Topics”
> “Standards and Criteria” > “Minimum Standards“.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.2.3 Root Certificates
For communication encrypted with TLS, root certificates are used to verify the
authenticity of the communication partner.
A root certificate, which is signed by a certificate authority, serves to verify the
validity of all certificates issued by this certificate authority.
The root certificates stored on the controller (root CA bundle) form the basis for
authentication of services hosted on the Internet (e.g., email providers and cloud
services).
The standard storage location for the root certificates is /etc/ssl/certs/ca-

certificates.crt.
This file contains the certificates provided by Mozilla. A list of the included root
certificates and their respective validity periods can be requested from the
following address:
https://hg.mozilla.org/releases/mozilla-release/raw-
file/79f079284141/security/nss/lib/ckfw/builtins/certdata.txt
The root certificates can be updated on the controller by updating the file
/etc/ssl/certs/ca-certificates.crt (see section “Service” > “Updating Root
Certificates”).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
5.1.3 Network Configuration
5.1.3.1 Host Name/Domain Name
Without a host name configuration, the controller is assigned a default name

which includes the last three values of the controller's MAC address, e.g.,
“PFCx00-A1A2A3.” This name is valid for as long as a host name was not
configured, or host name was not supplied to the controller via DHCP (for
configuration of the controller see Section “Startup” > “Configuring”). When the
host name is set, a host name supplied by a DHCP response is immediately
active and displaces the configured or default host name.
For multiple network interfaces with DHCP, the hostname is taken from the
network interface (bridge or Wwan) with the highest priority. The priority is
specified alphanumerically by the name of the network interface. Thus, Bridge1
has the highest priority, followed by Bridge2, Bridge3, ..., Wwan0.
If only the configured name is to be valid, the network administrator must adjust
the configuration of the active DHCP server so that no host names are
transferred in the DHCP response.
The default host name or the configured name is active again if the network
interfaces are set to static IP addresses or if a host name is not received via the
DHCP response.
A similar mechanism is used for a domain name as for the host name. The
difference is that a default domain name is not set. As long as a domain name is
not configured or supplied by DHCP, the domain name is empty.
5.1.3.2 Routing
As part of the TCP/IP configuration, the controller allows you to configure static
routes, IP masquerading and port forwarding. Default gateways are configured
via static routes, since default gateways are a special case of static routes.
A network station transmits to a gateway all network data packets for systems
outside of its local network. This gateway is responsible for the appropriate
routing of the data packets so that they reach the target system. To allow access
to different target systems, it may be necessary to configure multiple gateways.
This is configured by adding routing entries.
A routing entry consists of the following information:
• Destination address,
• Destination mask,
• Gateway address,
• Gateway metric.
• Interface
Manual
750-8214 PFC200; G2; 2ETH RS CAN
On the basis of the target system configuration, consisting of the destination
address and destination mask, a decision is made about which gateway a
network data packet should be forwarded to. The target system can be specified
through an individual IP address or an IP address range. For a network data
packet to forward, the routing entry with the most specific destination address
and destination mask entries is always selected. The default gateway
corresponds to the least specific routing entry. All network data packets such that
no specific routing entry exists for their destination address and destination mask
are sent to this default gateway.
Default gateway:
Default gateways, also called default routes, are always set in connection with
the IP configuration.
Each default gateway has a metric that is unique among all default gateways.
Bridge <n> has the metric 19+<n>.
A default gateway can also be defined via the routing configuration, e.g., to
define an individual metric. The value “default” must be set for “Destination
Address” and the value “0.0.0.0” for Destination Mask.
Route:
If an IP address or IP address range is entered in the “Destination Address” field,
then all network data packets that are directed to the network address or network
address range are sent to the gateway address corresponding to the entry.
Alternatively, a bridge, a modem or a VPN interface can be specified in the
“Interface” field, via which all data packets that are directed to the destination
address are routed. Specifying an interface is optional. However, either a
gateway address, an interface or both must be specified.
If the IP address of the gateway is outside the IP address space that the
controller can reach, the associated route is not enabled. This also applies to
routes in which an interface is specified, which e.g., is not enabled in the current
bridge configuration.
A metric is assigned to each routing entry. If multiple routing entries are

configured for the same destination address and destination mask, the metric
specifies how the routing entries are prioritized. In this case, routing entries with a
lower value for the metric are preferred over routing entries with a higher metric
value. The metric value of the configured routing entries can be specified for the
controller.
Besides the manually configurable routes, default gateways can also be set via
DHCP replies. A unique metric is assigned to all default gateways assigned by
DHCP.
The metric is assigned starting at 10 and depends on the network interface via
which the DHCP response was received. The metric is assigned in ascending
order based on the alphanumeric sorting of the network interface names (e.g.,
br0, br1, … wwan0).
Metric example:
A controller obtains its IP configuration via a DHCP server and receives both the
Manual
750-8214 PFC200; G2; 2ETH RS CAN
IP address and the network mask 192.168.1.10/24. Furthermore, a gateway with
IP address 192.168.1.2 and metric value 20 is set up on the controller. Therefore,
when no specific routing entry exists for the target address of network data
packets, the controller sends them to gateway 192.168.1.2. Besides the IP
address and network mask, the DHCP server is now instructed to allocate a
default gateway of 192.168.1.1. The controller gives this default gateway a metric
value of 10. Therefore, the default gateway received via DHCP is preferred over
the manually configured gateway.
The routing entries are used to specify which gateways the network data packets
are sent. If the controller is running in switched mode and only has one network
interface, all network traffic passes through this network interface. If the controller
is running in separated mode or contains a modem, it has more than one network
interface. Therefore, it is possible for a network data packet to arrive at the
controller on one network interface and depart on a different network interface.
This forwarding between different network interfaces must be explicitly enabled; it
is disabled when the controller is delivered. To enable the forwarding, “Enabled”
must be enabled in the “IP Forwarding through multiple interfaces” group. In this
case, the controller can function as a router.
For forwarding network communication through a router, it is necessary to note

that corresponding routing entries must be provided not only for the router, but
also for the respective endpoints of the communication. The routing entries of the
endpoints must ensure that the desired network data packets are sent via the
router, both when the connection is established and with the replies.
Host route example:

A host route is a route to an individual host. In the following example, a route to a
host with IP address 192.168.1.2 is to be specified. The route passes through a
gateway that can be reached via address 10.0.1.3. To configure a host route to
the destination host on a controller connected to the gateway, the following
settings must be made:
Destination Address: 192.168.1.2 IP address of the destination host

Destination Mask: 255.255.255.255 Subnet mask of an individual host
Gateway Address: 10.0.1.3 IP address of the gateway
Gateway Metric 20 Route priority
Network route example:

A network route is a route to a subnet, which can contain multiple hosts. In the
following example, a route to a subnet should be specified with network address
192.168.1.0. The route passes through a gateway that can be reached via
address 10.0.1.3. To configure a network route to the destination network on a
controller connected to the gateway, the following settings must be made:
Destination Address: 192.168.1.0 IP address of the destination network

Destination Mask: 255.255.255.0 Subnet mask of the destination network
Gateway Address: 10.0.1.3 IP address of the gateway
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Example of a route via an interface:
In the following example, a route to a host with IP address “192.168.1.2” is to be
specified. The route runs via the br1 interface, which corresponds to Bridge 2. To
configure a host route to the target host via Bridge 2 on a controller with an
activated Bridge 2, the following settings must be made.
Destination address: 192.168.1.2 IP address of the target host

Destination mask: 255.255.255.255 Subnet mask of an individual host
Interface br1 Interface through which the packet is to
be routed
Besides configuration of static routes, the controller also supports IP

masquerading. This can be enabled for selected network interfaces of the
controller. Network data packets that depart the controller through a network
interface for which IP masquerading has been enabled are given the IP address
of the network interface as their sender address. If network data packets are
forwarded through the controller, the network behind the controller is
encapsulated under a single address.
Furthermore, the controller permits configuration of port forwarding entries. For

port forwarding, the destination address and, if relevant, destination port of a
network data packet that arrived at the controller via a previously configured
network interface are overwritten. This makes it possible to forward network data
packets through the controller to other addresses and ports. Forwarding can be
configured for the TCP or UDP protocols.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.4 Network Services
5.1.4.1 DHCP-Client
The controller can get network parameters from an external DHCP master via the
DHCP Client service.
The following parameters can be obtained:
• IP address
• SubNet mask
• Router/gateway
• Hostname
• Domain
• DNS server
• NTP server
For the IP address, SubNet mask and router/gateway parameters, the entries are
stored per ETHERNET port.
For multiple network interfaces with DHCP, the hostname is taken from the
network interface (bridge or Wwan) with the highest priority. The priority is
specified alphanumerically by the name of the network interface. Thus, Bridge1
has the highest priority, followed by Bridge2, Bridge3, ..., Wwan0.
5.1.4.2 DHCP Server
The controller provides the DHCP server service for the automatic configuration
of IP addresses of network stations on the same subnet.
Generally, only one DHCP server can be active on a subnet at one time.
The following can be set for the DHCP server:
• The service itself (active/not active)
• The range of dynamically assigned IP addresses
• The lease time of the dynamically assigned IP addresses
• A list with static assignments of IP addresses to MAC addresses
In “switched” mode, these settings are possible for both interfaces together and
in “separated” mode for each interface separately.
The settings are made, for example, in the WBM via the “DHCP Configuration”
page.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The DHCP server also passes other parameters in addition to the IP address.
The following table shows the complete list.
Table 35: List of Parameters Transmitted via DHCP

Parameters Explanation
IP address An IP address from the range of permitted address; the
range can be configured in the WBM.
The DHCP server determines the IP address to be passed
to the requesting network subscriber (client) from the MAC
address of the network subscriber and the range of
addresses to be assigned. As long as the configured
address range does not change and no bottlenecks occur
when assigning IP addresses, the DHCP server
continuously reassigns the same IP addresses to
requesting network subscribers.
When a subscriber connects to the network, for whose
MAC address a fixed IP address has been configured in the
WBM, this address is passed to it. Such a fixed IP address
can also be outside the range of freely-assignable IP
addresses.
A hostname can also be specified instead of the MAC
address for identifying the requesting network subscriber.
Subnet mask The subnet mask configured in the network settings of the
DHCP server for the local network concerned is passed.
The subnet mask and IP address determine the range of
valid IP addresses on the local network.
Broadcast address IP address with which an IP packet can be sent to all
network subscribers on the subnet at the same time
Lease time Determines the validity period of the DHCP parameters
passed to a network subscriber:
Per protocol, the network subscriber is required to request
the network settings again after half the period of validity.
The lease time is configured in the WBM.
Host name The network name is passed to the network subscriber.
The network subscriber normally sends its own name with
its request for the IP address. It is then used by the DHCP
server in its response.
Name server The DHCP server passes its own IP address as the DNS
name server to the network subscriber.
Default gateway The DHCP server passes its own IP address as the default
gateway to the network subscriber.
The default gateway is required to communication with
subscribers outside the local network.
Not all parameters can be set in the WBM. If you want to set other values for the
existing parameters or want to pass other parameters via DHCP, the DHCP
server must be manually configured. For the controller, the DHCP server service
is handled by the program "dnsmasq".
Manual
750-8214 PFC200; G2; 2ETH RS CAN
From a Linux® command line, an editor must be used to change the file
“/etc/dnsmasq.d/dnsmasq_default.conf” to set the configuration.
5.1.4.3 DNS Server
The controller offers the DNS server service for the automatic assignment of
hostnames to IP addresses of network stations.
The DNS server takes over the names and IP addresses of local network stations
from the DHCP server. This DNS server routes requests for non-local names,
such as from the Internet, to higher-level DNS servers if configured and
accessible.
The following settings are possible for the DNS server:
• The service itself (enabled/disabled)
• Access type to the assignments

The requests are buffered in “Proxy” mode (throughput optimized).
In Relay mode the requests are routed directly to higher-level name
servers.
• A list with up to 15 static assignments of IP addresses to hostnames

If only the hostname is used, the configured or default domain is added to
the hostname automatically to ensure FQDN name resolution.
The settings are made, e.g., in the WBM, via the “Configuration of DNS Service”
page.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.1.5 Cloud Connectivity Functionality

With the cloud connectivity functionality and an IEC library, the controller is
available as a gateway for Internet-of-Things (IoT) applications. This means the
controller can collect the data from all the connected devices, access the Internet
via the built-in Ethernet interface or the mobile communications module and send
the data to the cloud.
You can specify the cloud service to use: Microsoft Azure, Amazon Web Services
and IBM Cloud are available.
Figure 25: Connecting the Controller to a Cloud Service (Example)
Data is transmitted from the controller to the cloud service as JSON files. The
connection can be encrypted with TLS; see the section “Functional Description” >
… > “TLS Encryption.”
You can find the settings that must be configured in the controller in order to use
the cloud connectivity functionality in the section “Start-Up” > … > “Configuration
Using Web-Based Management.
The communication parameters are configured in the WBM; the data to

exchange between the cloud and controller is configured with the libraries for
e!COCKPIT or CODESYS 2.3.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Please note the risks of using cloud services!

If you use third-party cloud services, sensitive data is transferred to the cloud
service provider at one's own responsibility. External access may result in
manipulated data and/or unwanted control commands affecting the performance
of your control system.
Use encryption methods to protect your data and observe the information
provided by the Federal Office for Information Security – “Cloud: Risks and
Security Tips”.
Observe comparable publications of the competent, public institutions of your
country.
Observe the additional documentation!

You can find a detailed description of the cloud connectivity software package
with a controller and information on PLC programming in Application Note
A500920 in the Downloads area: www.wago.com.
Observe the necessary data protection and security settings!

Before using the cloud connectivity functionality, consult the corresponding
handbook and familiarize yourself with data protection and security issues.
You will find this in the Downloads area at www.wago.com.
5.1.5.1 Components of the Cloud Connectivity Software Package
Table 36: Components of the Cloud Connectivity Software Package

Components Description
e!COCKPIT: IEC libraries to create the PLC application; function
WagoAppCloud blocks make it possible to exchange data between
the PLC and cloud service. The data transmission
CODESYS 2.3:
variables are definable.
WagoLibCloud
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.2 Memory Card Function

</dg_

guaranteed.
The memory card is optional and serves as an additional memory area in

addition to the internal memory or drive in the controller. The user program, user
data, source code of the project or device settings can be saved to the memory
card, and thus already existing project data and programs can be copied to one
or more controllers.
Deactivate write protection!

In order to be able to write data to the memory card, you must deactivate the
write protection using the small push switch for the write protection setting. This
switch is on one of the long sides of the memory card.
If the memory card is inserted, this is incorporated under /media/sd in the

directory structure of the file system inside the controller. This means that the
memory card can be addressed like a removable medium on a PC.
The function of the memory card in normal operation and possible faults that may
occur when the memory card is used are described in the following sections for
different operating modes.
5.2.1 Formatting
Note the pre-formatting of the memory card!

Please note that memory cards ≤ 2 GB are often formatted with the “FAT16” file
system type and can generate up to 512 entries in the root directory. For over
512 entries create these in a subdirectory or format the memory card with
“FAT32” or “NTFS.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Memory card access from CODESYS only possible with FAT16, FAT32 or
NTFS!
If the CODESYS user “admin” (see the section “Network” > “Network Security” >
“Users and Passwords” > “Services and Users“) is supposed to be able to access
files created on the memory card, the memory card must be formatted with
FAT16, FAT32 or NTFS.
If the Linux® file system formats EXT2 or EXT3 are used, “root” rights are
required for data access. Therefore, access via CODESYS is not possible.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.2.2 Data Backup

The controller has a backup function and a restore function.
In the WBM, the required settings can be made in the “Configuration” tab on the
“Package Server” > “Firmware Backup” or “Firmware Restore” pages and the
functions can be executed.
Settings can also be made in the CBM menu “Package Server” > “Firmware
Backup” or “Firmware Restore”.
The storage medium (internal memory or SD card) and, if applicable, the storage
location on the network can be set.
The data to be backed up and restored can also be selected:
• the CODESYS project (“PLC Runtime project,” boot project)

• the device settings (“Settings”)
• the controller operating system and the root file system (“System”)
• all of the above (“All,” only visible if not saved on the network)
Note the firmware version!

Restoring the controller operating system (“System” selection) is only permissible
and possible if the firmware versions at the backup and restore times are
identical.
If necessary, skip restoring the controller operating system, or match the
firmware version of the controller to the firmware version of the backup time
beforehand.
5.2.2.1 Backup Function
The backup function enables the data of the internal memory and device settings
to be saved on the memory card during operation.
The backup function can be called up the WBM page “Firmware Backup” in the
“Configuration” tab, selection “Package Server” > “Firmware Backup” or in the
CBM menu “Package Server” > “Firmware Backup”.
The network or the inserted memory card can be selected as the target medium.
The files of the internal drive are stored on the target medium in the directory
media/sd/copy and in the corresponding subdirectories.
The information that is not present as files on the controller is stored in XML
format in the directory media/sd/settings/.
If the memory card is selected as the target medium, the LED above the memory
card slot flashes yellow during the save operation.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The device settings and files of the internal drive are then saved on the target
medium.
The controller has an automatic update function. If this function is activated on a

memory card before the data backup and a controller is booted from this memory
card, this data is restored automatically on the internal memory of the controller.
Only one package may be copied to the network!

If you have specified “Network” as the storage location, only one package may
be selected for each storing process.
No backup of the memory card!

Backup from the memory card to the internal flash memory is not possible.
Account for backup time

Generation of backup files can take several minutes. Stop the CODESYS
program before you start the backup procedure to help shorten the time required.
5.2.2.2 Restore Function
The restore function is used to load the data and device settings from the
memory card to the internal memory during operation.
The restore function can be called up the WBM page “Firmware Restore” in the
“Configuration” tab, selection “Package Server” > “Firmware Restore” or in the
CBM menu “Package Server” > “Firmware Restore”.
The network or, if it is inserted, the memory card can be selected as the source
medium.
If the memory card is selected as the source medium, the LED above the
memory card slot flashes yellow during the load operation.
When loading the data, the files are copied from the directory media/sd/copy/ of
the source medium to the appropriate directories on the internal memory.
The device has an active and an inactive root partition. The system backup is
stored on the inactive partition. Startup is then performed from the newly written
partition. If the startup process can be completed, the new partition is switched to
active. Otherwise, booting is performed again from the old active partition during
the next boot process.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The boot project is loaded automatically and the settings automatically activated
after a restart. The “Home directory on memory card enabled” setting determines
whether the boot project of the internal drive or the memory card is loaded. This
setting can be called up on the WBM page “PLC Runtime Configuration” in the
“Configuration” tab, selection “PLC Runtime”.
File size must not exceed the size of the internal drive!
Note that the amount of data in the media/sd/copy/ directory must not exceed the
total size of the internal drive.
Restoration only possible from internal memory!

If the device was booted from the memory card, the firmware cannot be restored.
Reset by restore
A reset is performed when the system or settings are restored by CODESYS!
Connection loss through restore

If the restore changes the parameters of the ETHERNET connection, the WBM
may then no longer be able to open a connection to the device. You must call the
WBM again by entering the correct IP address of the device in the address line.
Note the restore time!

The restore process takes approx. 2 … 3 minutes.
After the restore process, the controller is restarted and is then ready for use
again.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.2.3 Inserting a Memory Card during Operation

The fieldbus nodes and the PLC program are running.
Insert a memory card during ongoing operation.
During normal operation, the memory card is incorporated into the file system of
the controller as a drive.
No automatic copy procedures are triggered.
The LED above the memory card flashes yellow during the access.
The memory card is then ready for operation and available under /media/sd.
5.2.4 Removing the Memory Card during Operation

The fieldbus node and the PLC program are in operation and the memory card is
plugged in.
Remove the memory card during ongoing operation.
Data can be lost during writing!

Note that if you pull the memory card out during a write procedure, data will be
lost.
The LED above the memory card flashes yellow during the attempted access.
The controller then works without a memory card.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.2.5 Setting the Home Directory for the Runtime System

The home directory for the runtime system is located in the controller's internal
memory by default. An existing boot project may be saved in the home directory.
You can use the WBM to move the home directory for the runtime system to the
memory card, e.g., to make more memory available for a large boot project or
other files.
This setting can be activated using the check box “Home directory on memory
card enabled” on the WBM page “PLC Runtime”. Click the [Submit] button to
apply the setting, which takes effect after the next restart.
No files are applied from the old to the new home directory.
After moving the directory, a project must be loaded and a boot project created.
It should be noted that the memory card may not be removed under any
circumstances as long as the home directory is there. If an application is running,
system safety can be endangered by an uncontrolled controller crash.
Switching the home directory has no effect if the controller was botted from a
memory card. The configuration state is saved, but only takes effect if the content
of the memory card is copied to the internal memory.
5.2.6 Load Boot Project

If a boot project exists, it may be loaded, depending on the home directory setting
for the runtime system. The following table shows the possible results:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 37: Loading a Boot Project
“Home
Boot Project Memory Card
Directory on
Stored in with Boot Boot Project is
Memory Card
Internal Flash Project Loaded ...
Enabled”
Memory Inserted
Checked
No No, no boot project exists
No
Yes No, no boot project exists
No No, no boot project exists in the
No
Yes internal flash memory
Yes Yes, from memory card
No Yes, from internal flash memory
No, invalid combination, since
no no boot project is allowed to
(Yes) invalid
exist in the internal flash
memory for this setting
Yes
No Yes, from internal flash memory
No, invalid combination, since
Yes no boot project is allowed to
(Yes) invalid
exist in the internal flash
memory for this setting
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5.3 Licensed Software Components

The e!RUNTIME runtime system software components that are subject to license
verification (runtime licenses) are available for 2nd generation controllers (750-
821x/xxx-xxx).
The e!COCKPIT software can be used for licensing. You can find corresponding
instructions in the documentation of e!COCKPIT.
A license key is required for productive use without time restriction of a software
component that is subject to licensing. Full use of the software component is
possible even without a license key for 30 days. This trial period only includes the
days of actual use. Access without a license key is no longer possible after the
trial period.
The license status (“Evaluation period not yet expired” or “Evaluation period has
expired”) is displayed by the controller via the SYS LED.
When loading a program with licensed components, e!COCKPIT displays the

number of days remaining.
Manual
88 Mounting WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
6 Mounting
6.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
6.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
WAGO I/O System 750 Mounting 89
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
6.3 Mounting onto Carrier Rail

6.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
750-8214 PFC200; G2; 2ETH RS CAN
6.3.2 WAGO DIN Rails

WAGO carrier rails meet the electrical and mechanical requirements shown in the
table below.
Table 38: 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
Observe the mounting distance of the DIN rail when the load is increased!
With increased vibration and shock load, mount the DIN rail at a mounting
distance of max. 60 mm.
6.4 Spacing
The spacing between adjacent components, cable conduits, casing and frame
sides must be maintained for the complete fieldbus node.
Figure 26: Spacing
The spacing creates room for heat transfer, installation or wiring. The spacing to
cable conduits also prevents conducted electromagnetic interferences from
influencing the operation.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
6.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.

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
750-8214 PFC200; G2; 2ETH RS CAN
6.6 Inserting 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.
6.6.1 Inserting the Controller

1. When replacing the controller for an already available controller, position
the new controller so that the tongue and groove joints to the subsequent
I/O module are engaged.
2. Snap the 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 controller from canting on the carrier rail.
With the 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 27: Release Tab of Controller (Example)
Manual
94 Connect Devices WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
7 Connect Devices
7.1 Connecting a Conductor to the CAGE CLAMP®
The WAGO CAGE CLAMP® connection is appropriate for solid, stranded and
finely stranded conductors.
Select conductor cross sections as required for current load!

The current consumed for field-side supply may not exceed 10 A. The wire cross
sections must be sufficient for the maximum current load for all of the I/O
modules to be supplied with power.
Only connect one conductor to each CAGE CLAMP® connection!

Only one conductor may be connected to each CAGE CLAMP® connection.
Do not connect more than one conductor at one single connection!
If more than one conductor must be routed to one connection, these must be
connected in an up-circuit wiring assembly, for example using WAGO feed-
through terminals.
1. To open the CAGE CLAMP® insert the actuating tool into the opening
above the connection.
2. Insert the conductor into the corresponding connection opening.
3. To close the CAGE CLAMP® simply remove the tool - the conductor is then
clamped firmly in place.
Figure 28: Connecting a Conductor to a CAGE CLAMP®
Manual
WAGO I/O System 750 Connect Devices 95
750-8214 PFC200; G2; 2ETH RS CAN
7.2 Power Supply Concept
7.2.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!

If you implement the overcurrent protection for the system supply with a fuse, a
fuse, max. 2 A, slow-acting, should be used.
Field supply only with appropriate fuse protection!

If you alternatively implement the overcurrent protection for the field supply with
an external fuse, a 10 A fuse should be used.
Manual
96 Connect Devices WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
7.2.2 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 39: 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 29: 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
WAGO I/O System 750 Commissioning 97
750-8214 PFC200; G2; 2ETH RS CAN
8 Commissioning
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.
8.1 Switching On the Controller

Before switching on the controller ensure that you
• have properly installed the controller

(see section “Installation”),
• have connected all required data cables (see section “Connections”) to the
corresponding interfaces and have secured the connectors by their
attached locking screws,
• have connected the electronics and field-side power supply

(see section “Connections”),
• have mounted the end module

(see Section “Installation”),
• have performed appropriate potential equalization at your machine/system

(see System Description for 750-xxx) and
• have performed shielding properly (see System Description for 750-xxx).
To switch on both the controller and the connected I/O modules, switch on your
power supply unit.
Starting of the controller is indicated by a brief orange flashing of all LEDs. After a
few seconds the SYS LED will indicate successful boot-up of the controller.
The CODESYS 2.3 runtime system or e!RUNTIME is started at the same time.
Once the entire system has been successfully started, the SYS and I/O LEDs
light up green.
If there is an executable IEC 61131-3 program stored and running on the

controller, the RUN LED will light up green.
Manual
98 Commissioning WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
If no executable program is stored on the controller, or the mode selector switch
is set to STOP, this is likewise indicated by the RUN LED (see Section
“Diagnostics”> … > “Fieldbus/System Indication Elements”).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.2 Determining the IP Address of the Host PC

To ensure that the host PC can communicate with the controller via ETHERNET,
both devices must be located in the same subnet.
To determine the IP address of the host PC (with the Microsoft Windows®

operating system) using the MS DOS prompt, proceed as follows:
1. Open the MS DOS prompt window.

To do this, enter the command “cmd” in the input field under Start >
Execute… > Open: (Windows® XP) or Start > Search programs/files
(Windows® 7) and then click [OK] or press [Enter].
2. In the MS DOS prompt enter the command “ipconfig” and then press
[Enter].
3. The IP address, subnet mask and standard gateway, including the

appropriate parameters, are displayed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.3 Setting an IP Address

In the controller’s initial state, the following IP addresses are active for the
ETHERNET interface (Port X1 and Port X2):
Table 40: Default IP Addresses for ETHERNET Interfaces

ETHERNET Interface Default Setting
X1/X2 Dynamic assignment of IP address using DHCP
(switched mode) (“Dynamic Host Configuration Protocol”)
Adapt IP addressing to your specific system structure to ensure that the PC and
the controller can communicate with one another using one of the available
configuration tools (see section “Configuration”).
Example for incorporating the controller (192.168.2.17) into an existing

network:
• The IP address of the host PC is 192.168.1.2.
• The controller and host PC must be in the same subnet (regardless of the
IP address of the host PC).
• With a subnet mast of 255.255.255.0, the first three digits of the IP address
of the host PC and controller must match so that they are located in the
same subnet.
Table 41: Network Mask 255.255.255.0

Host PC Subnet Address Range for the Controller
192.168.1.2 192.168.1.1 or 192.168.1.3 … 192.168.1.254
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.3.1 Assigning an IP Address using DHCP

The Controller can obtain dynamic IP addresses from a server (DHCP/BootP).
In contrast to fixed IP addresses, dynamically assigned addresses are not stored
permanently. Therefore, a BootP or DHCP server must be available each time
the controller is restarted.
If an IP address has been assigned by means of DHCP (default setting), it can be

determined through the settings and the output of the specific DHCP server.
In the example figure shown here, the corresponding output of “Open DHCP” is
presented.
Figure 30: “Open DHCP”, Example Figure
In conjunction with the DNS server associated with DHCP, the device can be
reached using its host name.
This name consists of the prefix “PFCx00-“ and the last six places of the MAC
address (in the example shown here: “00:30:DE:FF:00:5A”). The MAC address of
the device can be printed on the label on the side of the device.
The host name of the device in the example shown here is thus “PFC200-
FF005A”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.3.2 Changing an IP Address Using the “CBM” Configuration

Tool and a Terminal Program
You can also assign a new IP address to the ETHERNET interfaces X1 and X2
using the “CBM” configuration tool provided on the Linux® console. More
information about “CBM” is given in the Section “Configuration.”
1. Connect a PC to the ETHERNET interface X1 of the controller using an

SSH terminal program.
2. Start the terminal program.
3. Select “SSH” as the connection type, and enter the IP address of the
controller and port 22 as the connection parameters.
Alternatively, you can also connect the controller via a serial interface:
1. Connect a PC to the X3 serial interface of the controller using a terminal

program.
3. Select “Serial” as the connection type and enter a baud rate of 115200
bauds as the connection parameter. The settings for data bits, stop bits and
parity do not need to be adjusted.
4. Log in to the Linux® system as a “super user.”

The user name and the password are provided in the Section “Users and
Passwords” > “Linux® User Group.”
5. Start the configuration tool by entering the command “cbm” (case sensitive)
on the command line and then press [Enter].
Figure 31: CBM main menu (example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
6. In the Main menu use the keyboard (arrow keys or numeric keypad) to
move to and select Networking and then press [Enter].
Figure 32: CBM – Selecting “Networking”
7. In the Networking menu select TCP/IP and press [Enter].
Figure 33: CBM – Selecting “TCP/IP”
8. In the menu TCP/IP select IP Address and press [Enter].
Figure 34: CBM – Selecting “IP address”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9. In the menu TCP/IP Configuration select IP Address and press [Enter].
Figure 35: CBM – Selecting the IP Address
10. In the menu Change IP Address enter the new IP address and confirm by
clicking [OK]. If you want to return to the main menu without making
changes, click [Abort].
Figure 36: CBM – Entering a New IP Address
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.3.3 Changing an IP Address using “WAGO Ethernet Settings”

The Microsoft Windows® application “WAGO Ethernet Settings” is a software
used to identify the controller and configure network settings.
Observe the software version!

To configure the controller use at least Version 6.4.1.1 dated 2015-06-29 of
“WAGO Ethernet Settings”!
You can use WAGO communication cables or WAGO radio adapters or even the
IP network for data communication.
1. Switch off the power supply to the controller.
2. Connect the 750-920 communication cable to the Service interface on the

controller and to a serial interface of your PC.
3. Switch the power supply to the controller on again.
4. Start the “WAGO Ethernet Settings” program.
Figure 37: “WAGO Ethernet Settings” – Starting Screen (Example)
5. Click [Read] to read in and identify the connected controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
6. Select the “Network” tab:
Figure 38: “WAGO Ethernet Settings” – “Network” Tab
7. To assign a fixed address, select “Static configuration” on the “Source” line

under “Input”. DHCP is normally activated as the default setting.
8. In the column “Input” enter the required IP address and, if applicable, the
address of the subnet mask and of the gateway.
9. Click on [Write] to accept the address in the controller. (If necessary,

“WAGO Ethernet Settings” will restart your controller. This action may
require about 30 seconds.)
10. You can now close “WAGO Ethernet Settings”, or make other changes
directly in the Web-based Management system as required. To do this,
click on [Run WBM] at the right in the window.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
8.3.4 Temporarily Setting Fixed IP Addresses

This process temporarily sets the IP addresses for the network interfaces
X1 … X<n> to fixed IP addresses.
For each bridge used, the assigned interfaces are assigned their own address,
whereby bridge 1 receives the IP address “192.168.1.17”, bridge 2 the IP
address “192.168.2.17” and so on.
No reset is performed.
To set temporary fixed IP addresses, proceed as follows:
1. Set the mode selector switch to STOP and
2. Press and hold the Reset button (RST) for longer than 8 seconds.
Execution of the setting is signaled by the “SYS” LED flashing orange.
If you make changes to the IP configuration of a bridge after activating the

temporary IP addresses, the new settings are permanently adopted and applied
immediately. The configured bridge exits the temporary IP address mode. The
other bridges keep the temporarily set IP address until restart / reset.
To cancel this setting, proceed as follows:
• Perform a software reset or
• Switch off the controller and then switch it back on.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.4 Testing the Network Connection

Carry out a ping network function to check whether you can reach the controller
at the IP address you have assigned in the network.
1. Open the MS DOS prompt window.

To do this, enter the command “cmd” in the input field under Start >
Execute… > Open: (Windows® XP) or Start > Search programs/files
(Windows® 7) and then click [OK] or press [Enter].
2. In the MS DOS window, enter the command “ping” and the IP address of
the controller (for example, ping 192.168.1.17)and then press [Enter].
Host entries in the ARP table!

It may also be useful to delete the current host entries in the ARP table with the
command “arp -d *” before executing the “ping” command (as administrator in
Windows® 7). This ensures that older entries will not impair the success of the
“ping” command.
3. Your PC sends out a query that is answered by the controller. This reply
appears in the MS DOS prompt window. If the error message “Timeout”
appears, the controller has not responded properly. You then need to check
your network settings.
Figure 39: Example of a Function Test
4. If the test is completed successfully, close the MS DOS window.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.5 Changing Passwords
Change standard passwords

The standard passwords are documented in these instructions and therefore do
not offer adequate protection! Change the passwords to meet your particular
needs!
To increase security all passwords should contain a combination of lower case

letters (a … z), upper case letters (A … Z), numbers (0 … 9), spaces and special
characters: (]!"#$%&'()*+,./:;<=>?@[\^_`{|}~-). Passwords should not contain
generally known names, dates of birth and other information that is easy to
guess.
Change the standard passwords before commissioning the controller.

Standard passwords are issued for the user groups “WBM Users” and “Linux®
Users.”
The table in the Section “Function Description” > ... > “Users and Passwords” >
“WBM Users Group” shows the standard passwords for the WBM users. Proceed
as follows to change these passwords:
1. Connect the controller to a PC via one of the network interfaces (X1, X2).
2. Start a web browser program on the PC and call up the WBM of the
controller (see Section “Commissioning” > … > “Configuration via Web-
Based-Management (WBM)”).
3. Log in on the controller as “admin” user with the standard password.
4. Change the password for all users on the WBM “Configuration of the users
for the WBM” page.
5. Select each user and enter a new password and confirm it.
The table in the Section “Functional Description” > ... > “Users and Passwords” >
“Linux® Users Group” shows the standard passwords for the Linux® users.
Proceed as follows to change these passwords:
1. Connect the controller to a PC via the network interfaces X1.
2. Start a terminal program on the PC (see Section “Commissioning” > … >

“Configuration via Console-Based-Management-Tool (CBM) using a
Terminal Program”).
3. Log in on the controller as user “root” with the standard password.
4. Change the password for all users with the “passwd root,” “passwd admin”
and “passwd user” commands.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
8.6 Shutdown/Restart
Switch off the power supply to shut down the controller.
To perform a controller restart, press the Reset button as described in the

Section “Triggering Reset Functions” > “Software Reset (Restart).”
Alternatively, you can switch off the controller and switch it back on again.
Do not power cycle the controller after changing any parameters!

Some parameter changes require a controller restart for the changes to apply.
Saving changes takes time.
Do not power cycle the controller to perform a restart, i.e., changes may be lost
by shutting down the controller too soon.
Only restart the controller using the software reboot function. This ensures that
all memory operations are completed correctly and completely.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.7 Initiating Reset Functions

</dg_
You can initiate various reset functions using the mode selector switch and the
Reset button (RST).
8.7.1 Warm Start Reset

The warm start reset function depends on the activated runtime system
8.7.1.1 CODESYS V2 Runtime System

</dg_
The CODESYS V2 application is reset on a warm start reset. This corresponds to

the WAGO I/O PRO IDE “Reset” command.
</dg_
To perform a warm start reset, set the mode selector switch to "Reset" and hold it
there for two to seven seconds.
Execution of the reset is signaled by the red “RUN LED” briefly going out when
the mode selector switch is released.
8.7.1.2 e!RUNTIME Runtime System
All e!RUNTIME applications are reset with a warm start reset. All global data is
set to its initialization values. This corresponds to the e!COCKPIT IDE “Reset
warm” command.
</dg_
To perform a warm start reset, set the mode selector switch to "Reset" and hold it
there for two to seven seconds.
Execution of the reset is signaled by the red “RUN LED” briefly going out when
the mode selector switch is released.
8.7.2 Cold Start Reset

The cold start reset function depends on the activated runtime system
8.7.2.1 CODESYS V2 Runtime System

</dg_
On a cold start reset the CODESYS V2 application is reset and the memory
containing the retain variables is cleared.
This corresponds to the WAGO I/O PRO IDE “Reset (Cold)” command.
</dg_
To perform a cold start reset, set the mode selector switch to “Reset” and hold it
there for more than seven seconds.
Execution of the reset is signaled after seven seconds by the “RUN” LED going
out for an extended period. You can then release the mode selector switch.
8.7.2.2 e!RUNTIME Runtime System

</dg_
Manual
750-8214 PFC200; G2; 2ETH RS CAN
All e!RUNTIME applications are reset with a cold start reset. All global data and
the retain variables are set to their initialization values.
This corresponds to the e!COCKPIT IDE “Reset Cold” command.
</dg_
To perform a cold start reset, set the mode selector switch to “Reset” and hold it
there for more than seven seconds.
Execution of the reset is signaled after seven seconds by the “RUN” LED going
out for an extended period. You can then release the mode selector switch.
8.7.3 Software Reset

</dg_
The controller is restarted on a software reset.
To perform a software reset, set the mode selector switch to RUN or STOP and
then press the Reset button (RST) for one to eight seconds.
Reset completion is indicated by a brief orange flashing of all LEDs. After a few
seconds the SYS LED will indicate successful boot-up of the controller.
8.7.4 Controller Reset
Do not switch the controller off!

The controller can be damaged by interrupting the controller reset process.
Do not switch the controller off during the controller reset process, and do not
disconnect the power supply!
Parameters and passwords are overwritten!

Parameters and passwords for the Linux® and WBM users of the controller are
overwritten by a controller reset.
Stored boot projects are deleted, including existing web visualizations.
Subsequently installed firmware functions are not overwritten.
Software licenses are retained.
The inactive system is not changed by the reset.
If you have any questions, contact WAGO Support.
The controller is restarted after the controller reset.

Proceed as follows to reset the controller:
1. Press the Reset button (RST).
2. Set the mode selector switch to the “RESET” position.
3. Press and hold both buttons until the “SYS” LED alternately flashes
red/green after approx. 8 seconds.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4. When the “SYS” LED flashes red/green alternately, release the mode
selector switch and Reset button.
Do not interrupt the reset process!

If you release the Reset button (RST) too early, then the controller restarts
without performing the controller reset.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8 Configuration
Check firmware version and update if required!

At the beginning of initial configuration check to ensure that you have the latest
firmware version for the controller.
The firmware version installed on the controller is given on the WBM page
“Status Information”, or in the CBM menu “Information” under “Controller Details”.
Perform an update to install the latest firmware version.
To do this, follow the instructions given in section “Service” > “Firmware
Changes” > “Perform Firmware Upgrade”.
The following methods are available for configuring the controller:
• Access to the Web-based management system via the PC using a web

browser (section “Configuration Using Web-Based Management [WBM]”)
• Access to the “Console-Based Management” tool via the PC using a

terminal program (section “Configuration Using a Terminal Program
[CBM]”)
• Access via the CODESYS PLC program using the CODESYS V2 library
WagoConfigToolLIB.lib (section “Appendix” > “WagoConfigToolLIB.lib”) or
the e!RUNTIME library “WagoAppConfigTool.lib”
• Access via the PC using “WAGO Ethernet Settings” (section “Configuration

Using ‘WAGO Ethernet Settings’”).
The CBM is basically for the initial configuration and startup of the controller.
Therefore, it only provides a subset of the WBM parameters. For example,
parameters that cannot be displayed in a terminal window in a reasonable way
and are not necessary for initial startup are not displayed. You can find the
explanations of the parameters starting with the section “‘Information’ Page.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.1 Configuration via Web-Based-Management (WBM)

The HTML pages (from here on referred to as “pages”) of the Web-Based
Management are used to configure the controller. Proceed as follows to access
the WBM using a web browser:
1. Connect the controller to the ETHERNET network via the ETHERNET

interface X1.
2. Start a Web browser on your PC.
3. Enter “https://” followed by the controller's IP address and “/wbm-ng” in the

address line of your web browser, e.g., “https://192.168.1.17/wbm-ng”.
Note that the PC and the controller must be located within the same subnet
(see Section “Setting an IP Address”).
If you do not know the IP address and cannot determine it, switch the
controller temporarily to the pre-set address “192.168.1.17” (“Fixed IP
address” mode, see Section “Commissioning” > … > “Temporarily Setting a
Fixed IP Address”).
Take usage by the CODESYS program into account

If the controller is at capacity due to a CODESYS program, this may result in
slower processing in the WBM. As a result, timeout errors are sometimes
reported in some circumstances. It is therefore important to stop the CODESYS
application prior to performing complicated configurations using WBM.
 When the connection has been established, a login window opens.
Figure 40: Entering Authentication
4. Enter the username and password.
5. Click the [Login] button.
6. If you only want to log in as a guest, click the [Guest] button.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
 Depending on the user selected, the navigation bar and the tabs of the
WBM are displayed.
If you have disabled cookies in your web browser, you can continue to use the
WBM as long as you move directly inside it. However, if you fully reload the
website (e.g., with [F5]), you must log in again since the web browser is then not
able to store the data of your login session.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.1.1 WBM User Administration
To allow settings to be made only by a select number of users, limit access to

WBM functions through User Administration.
Change passwords
If you do not change these passwords, a warning will appear each time you call
up a website after logging in.
Figure 41: Password Reminder
Table 42:User Settings in the Default State

Users Permissions Default Password
root All (administrator) wago
admin All (administrator) wago
user Supported to a limited extent user
guest Display only ---

The WBM users “root”, “admin” and “user” have rights beyond the WBM to
configure the system and install software.
User administration for controller applications is configured separately.
Access rights for the WBM pages are shown in the table below.
The “root” user has the same rights as the “admin” user and is therefore not listed
separately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 43: Access Rights for WBM Pages
Tab/Navigation WBM Page Title User
Information
Device Status Device Status guest
Vendor Information Vendor Information guest
PLC Runtime PLC Runtime Information guest
Legal Information
WAGO Licenses WAGO Software License Agreement guest
Open Source Open Source Licenses user
Licenses
WBM Licenses WBM Third Party License Information user
Trademarks Trademarks Information guest
Information
WBM Version WBM Version Info guest
Configuration
PLC Runtime PLC Runtime Configuration user
Networking
TCP/IP TCP/IP Configuration user
Configuration
Ethernet Ethernet Configuration user
Configuration
Host/Domain Configuration of Host and Domain Name user
Name
Routing Routing user
Clock Clock Settings user
Administration
Serial Interface Configuration of Serial Interface admin
RS232/RS485
Service Interface Configuration of Service Interface admin
Create Image Create bootable Image admin
Package Server
Firmware Firmware Backup admin
Backup
Firmware Firmware Restore admin
Restore
Active System Active System admin
Mass Storage Mass Storage admin
Software Uploads Software Uploads admin
Ports and Services
Network Configuration of Network Services admin
Services
NTP Client Configuration of NTP Client admin
PLC Runtime PLC Runtime Services admin
Services
SSH SSH Server Settings admin
Manual
750-8214 PFC200; G2; 2ETH RS CAN
TFTP TFTP Server admin
DHCP Server DHCP Server Configuration admin
DNS Configuration of DNS Service user
Cloud Connectivity
Status Overview admin
Connection 1 Configuration admin
Connection 2 Configuration admin
SNMP
General Configuration of general SNMP parameters admin
Configuration
SNMP v1/v2c Configuration of SNMP v1/v2c parameters admin
SNMP v3 Configuration of SNMP v3 Users admin
Docker Docker Settings admin
Users WBM User Configuration admin
Fieldbus
OPC UA
Status OPC UA Status admin
Configuration OPC UA Configuration admin
Information OPC UA Information Model admin
Model
Server OPC UA Server Certificates admin
Certificates
Client OPC UA Client Certificates admin
Certificates
Modbus Modbus Services Configuration user
BACnet
Status BACnet Status admin
Configuration BACnet Configuration admin
Storage Location BACnet Storage Location admin
Files BACnet Files admin
Security
OpenVPN / IPsec OpenVPN / IPsec Configuration admin
Firewall
General General Firewall Configuration admin
Configuration
Interface Interface Configuration admin
Configuration
MAC Address Configuration of MAC Address Filter admin
Filter
User Filter Configuration of User Filter admin
Certificates Certificates admin
Boot Mode Boot mode configuration admin
TLS Security Settings admin
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Integrity Advanced Intrusion Detection Environment admin
(AIDE)
WAGO Device WAGO Device Access admin
Access
Diagnostic Diagnostic Information guest
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.1.2 General Information about the Page
The IP address of the active device is displayed in the entry line of the browser
window.
The WBM pages are only displayed after logging in. To log in, enter your
username and password in the login window and click the [Login] button.
Figure 42: WBM Browser Window (Example)
The tabs for the various WBM areas and the [Reboot] and [Logout] buttons are
displayed in the header of the browser window. The [Reboot] button only
appears if you are logged in as an administrator.
If not all tabs can be displayed in the selected width of the window, a tab with
ellipsis (...) is displayed instead of the tabs that cannot be displayed. This allows
you to select the tabs (not shown) using a pull-down menu.
Figure 43: WBM Header with Tabs that Cannot be Displayed (Example)
The navigation tree is shown on the left of the browser window. The content of
the navigation tree depends on the selected tab.
You can use this navigation tree to go to the individual pages and, where
provided, subpages included in these pages.
The current device status is displayed in the status bar.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 44: WBM Status Bar (Example)
• Date and Time - Local date and local time and on the device
• Setting of the mode selector switch
• LED status of the Device:

All LEDs are graphically represented and are labeled with their particular
designation (e.g., SYS, RUN, …). The following colors are possible:
- gray: LED is off.

- full color (green, red, yellow, orange): The LED is activated in the
particular color.
- half color:
The LED is flashing in the corresponding color. The other half of the
surface is then either gray or also colored. The latter case indicates that
the LED is flashing sequentially in different colors.
A tooltip containing more detailed information opens as long as the cursor

is positioned over an LED. The text that is displayed also contains the
message that put the LED into its current status. The time of the message
is also shown.
The states displayed in the WBM will not always correspond at the precise
time to those on the controller. Data has a runtime during transmission and
can only be queried at a certain interval. The time period between two
queries is 30 seconds.

A description of the WBM pages and the respective parameters can be found in
the appendix in Section “Configuration Dialogs” > “Web-Based Management
(WBM)”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.2 Configuration via Console-Based-Management-Tool (CBM)

using a Terminal Program
The Console-Based Management Tool (CBM) is basically used for the initial
configuration and startup of the controller via a terminal program.
Therefore, it only provides a subset of the controller parameters. For example,
parameters that cannot be displayed in a terminal window in a reasonable way
and are not necessary for initial startup are not displayed.
1. Connect a PC to the ETHERNET interface X1 of the controller using an

SSH terminal program.
3. Select “SSH” as the connection type, and enter the IP address of the
controller and port 22 as the connection parameters.
Alternatively, you can also connect the controller via a serial interface:
1. Connect a PC to the X3 serial interface of the controller using a terminal

program.
3. Select “Serial” as the connection type and enter a baud rate of 115200
bauds as the connection parameter. The settings for data bits, stop bits and
parity do not need to be adjusted.
4. Log in to the Linux® system as a “super user.”

The user name and the password are provided in the Section “Users and
Passwords” > “Linux® User Group.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5. Start the configuration tool by entering the command “cbm” (case sensitive)
on the command line and then press [Enter].
Figure 45: CBM main menu (example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.2.1 CBM Menu Structure Overview
Table 44: CBM Menu Structure

Menu Hierarchy
0. Quit
1. Information
0. Back to Main Menu
1. Controller Details
2. Network Details
2. PLC Runtime
1. Information
2. General Configuration
3. WebVisu
3. Networking
1. Host-/Domain Name
2. TCP/IP
0. Back to Networking Menu
1. IP Address
2. Default Gateway
3. DNS Server
3. Ethernet
0. Back to Networking Menu
1. Switch Configuration
2. Ethernet Ports
0. Back to Ethernet Menu
1. Interface X1
2. Interface X2
4. Firewall
2. MAC Address Filter
3. User Filter
5. Clock
1. Date on device (local)
2. Time on device (local)
3. Time on device (UTC)
4. Clock Display Mode
5. Timezone
6. TZ-String
6. Administration
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 44: CBM Menu Structure
Menu Hierarchy
1. Users
2. Create Image
3. Owner of Serial Interface
4. Reboot Controller
7. Package Server
1. Firmware Backup
2. Firmware Restore
3. System Partition
8. Mass Storage
1. Internal Flash (active partition)
9. Software Uploads
1. Update Script
10. Ports and Services
1. Telnet
2. FTP
3. FTPS
4. HTTP
5. HTTPS
6. NTP
7. SSH
8. TFTP
9. DHCPD
10. DNS
11. IOCHECK PORT
12. Modbus TCP
13. Modbus UDP
14. PLC Runtime Services
11. SNMP
1. General SNMP Configuration
2. SNMP v1/v2c Manager Configuration
3. SNMP v1/v2c Trap Receiver Configuration
4. SNMP v3 Configuration
5. SNMP firewalling
6. Secure SNMP firewalling
Manual
750-8214 PFC200; G2; 2ETH RS CAN

A description of the CBM menus and the respective parameters can be found in
the appendix in Section “Configuration Dialogs” > “Console-Based Management
(CBM)”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
8.8.3 Configuration using “WAGO Ethernet Settings”

The “WAGO Ethernet Settings” program enables you to read system information
about your controller, make network settings and enable/disable the Web server.
Observe the software version!

To configure the controller, use at least Version 6.4.1.1 dated 2015-06-29 or
newer of “WAGO Ethernet Settings”!
You must select the corresponding interface after launching the “WAGO
ETHERNET Settings”.
A connection can be established via the service interface using communication

cable 750-920, Bluetooth® Adapter 750-921, configuration cable 750-923 or 750-
923/000-001 or via the ETHERNET interfaces.
Figure 46: “WAGO Ethernet Settings” – Start Screen
For this, click “Settings” and then “Communication”.
In the “Communication settings” window that then opens, adapt the settings to
your needs.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 47: “WAGO Ethernet Settings” – Communication Link
Once you have configured “WAGO Ethernet Settings” and have clicked [Apply],
connection to the controller is established automatically.
If “WAGO Ethernet Settings” has already been started with the correct
parameters, you can establish connection to the controller by clicking [Read].
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.3.1 Identification Tab
An overview of the connected device is given here.
Besides some fixed values — e.g., item No., MAC address and firmware version
— the currently used IP address and the configuration method are also shown
here.
Figure 48: “WAGO Ethernet Settings” – Identification Tab (Example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.3.2 Network Tab
This tab is used to configure network settings.
Values can be changed in the “Input” column, while the parameters in use are
shown in the “Currently in use” column.
Figure 49: “WAGO Ethernet Settings” – Network Tab
Address Source
Specify how the controller will determine its IP address: Static, via DHCP or via
BootP.
IP address, subnet mask, gateway

Specify the specific network parameters for static configuration.
Restricted setting for default gateways!

Only the default gateway 1 can be set via “WAGO Ethernet Settings.”
The default gateway 2 can only be set in the WBM!
Preferred DNS server, alternative DNS server

Enter the IP address (when required) for an accessible DNS server when
identifying network names.
Time server
Specify the IP address for a time server if setting the controller's system time via
NTP.
Hostname
The host name of the controller is displayed here. In the controller's initial state,
this name is composed of the string “PFCx00” and the last three bytes of the
Manual
750-8214 PFC200; G2; 2ETH RS CAN
MAC address.
This standard value is also used whenever the chosen name in the “Input”
column is deleted.
Domain name
The current domain name is displayed here. This setting can be automatically
overwritten with dynamic configurations, e.g., DHCP.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.3.3 PLC Tab
Figure 50: “WAGO Ethernet Settings” – Protocol Tab
Here you can select the runtime system.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8.8.3.4 Status Tab
Figure 51: “WAGO Ethernet Settings” – Status Tab
General information about the controller status is displayed here.
Manual
WAGO I/O System 750 Run-time System CODESYS 2.3 135
750-8214 PFC200; G2; 2ETH RS CAN
9 Run-time System CODESYS 2.3

9.1 Installing the CODESYS 2.3 Programming System
The WAGO target files must also be included for the installation of CODESYS.
These contain all device-specific information for the WAGO 750/758 product
series.
Proceed as described below to install the CODESYS 2.3 programming software

on a personal computer.
1. Insert the “WAGO-I/O-PRO” CD into your computer drive.
2. To install the programming system, follow the instructions that appear on

your screen. A successful installation is indicated by a CODESYS icon on
your desktop.
9.2 First Program with CODESYS 2.3

This section uses an example to explain the relevant steps required for the
creation of a CODESYS project. It is intended as a set of quick start instructions
and does not address the full functional range of CODESYS 2.3.
Additional information
For a detailed description of the full range of functions, refer to the “Manual for
PLC Programming using CODESYS 2.3” manual available on the “WAGO-I/O-
PRO” (759-911) CD.
9.2.1 Start the CODESYS Programming System

Start CODESYS by double clicking on the CODESYS pictogram on your desktop
using the Start menu in your operating system. To do this, click on the “Start”
button and choose Programs >
WAGO Software > CODESYS > CODESYS V2.3.
9.2.2 Creating a Project and Selecting a Target System
Note the maximum length of the project name and element identifier!
The maximum length of the project name, element identifier and other file names
in the project cannot exceed 80 characters!
Longer names or identifiers can lead to errors in the program flow or in the
display.
Manual
136 Run-time System CODESYS 2.3 WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
1. In the menu bar click on File and select New. The “Target system settings”
window then opens. Here, all available target systems that can be
programmed with CODESYS 2.3 are listed.
2. Open the selection box in the “Target system settings” window and select
the fieldbus controller you are using. In the example shown here this is the
PFC200 CS 2ETH RS “WAGO_750-8202”.
Figure 52: Target System Settings (1)
3. Click on [OK]. The “Target system settings” configuration window then

opens.
Figure 53: Target System Settings (2)
4. To accept the default configuration for the fieldbus controller click [OK].
The “New component” window opens.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5. In this “New component” window create a new program function block. In
the example shown here, the new function block “PLC_PRG” is created in
the “ST” programming language.
Figure 54: Creating a New Function Block
6. Click on [OK] to create the project. The programming interface opens.
Figure 55: Programming Interface With the PLC_PRG Program Module
9.2.3 Creating the PLC Configuration
Procedure for Creating the PLC Configuration

The procedure explained in this section describes the PLC configuration for the
I/O modules connected to the controller.
Information about the controller function for any fieldbuses connected to the
system is given in the section on the specific fieldbus.
The PLC configuration is used to configure the fieldbus controller, along with the
connected I/O modules and to declare variables for accessing the inputs and
outputs of the I/O modules.
1. Click on the “Resources” tab.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 56: “Resources” Tab
2. In the left window double-click on “PLC configuration”. The PLC

configuration for the controller opens.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
3. Right-click on the entry “K-Bus[FIX]” and then select “Edit” in the contextual
menu. The “configuration” dialog window then opens.
Figure 57: Control Configuration – Edit
4. There are three options for accepting the topology for the I/O modules
connected to the fieldbus controller. The simplest way is to scan in the
topology using WAGO-I/O-CHECK.
To do this, click on the “Start WAGO-I/O-CHECK and scan” button.
Figure 58: “Start WAGO-I/O-CHECK and Scan” Button
Ensure proper installation of WAGO-I/O-CHECK!

This function requires that the latest version of WAGO-I/O-CHECK be installed
and the IP address set under “Online > Communication parameters”, as
otherwise communication will not be possible.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
5. WAGO-I/O-CHECK is started.
Figure 59: WAGO-I/O-CHECK – Starting Screen
6. To connect to the controller and read in the module configuration, click

[Identify].
7. If this action is successful click [Save] and exit WAGO-I/O-CHECK.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
8. The detected I/O modules then appear in the configuration window.
Passive I/O Modules

Remember that passive I/O modules, such as a power supply module
(750-602/xxx-xxx) or end module (750-600/xxx-xxx) will not be shown in the I/O
configurator.
Figure 60: I/O Configurator Empty
9. You can use the [Add] button to add new I/O modules to manually define
or change the configuration.
Figure 61: “Add I/O Modules” Button
Manual
750-8214 PFC200; G2; 2ETH RS CAN
10. You can select a module in the new “Module selection” window that then
appears.
Figure 62: “Module Selection” Window
11. You can change the position of an I/O module by marking it and then using
the arrow buttons at the right edge of the window to move it up or down.
Figure 63: I/O Configurator with Defined I/O Modules
12. Use [Import configuration from file] to add a configuration imported

previously using WAGO-I/O-CHECK.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13. To close the I/O Configurator, click [OK].
14. The individual inputs and outputs of the selected I/O module are displayed
in the right half of the configuration window.
Here, you can declare a dedicated variable in the “Name” column for each
input and output, e.g., “Output_1”, “Output_2”, “Input_1”, “Input_2”.
Figure 64: Variable declaration
15. The added I/O modules appear in the control configuration under
“K-Bus[FIX]” with their associated fixed addresses and, where applicable,
their previously set variable name.
Figure 65: Control Configuration: I/O Modules with Their Associated Addresses
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.2.4 Editing the Program Function Block

To edit the PLC_PRG program function block, go to the “Function block” tab and
double-click on the PLC_PRG program module.
Figure 66: Program Function Block
The following example illustrates the editing of the program function block. To do
this, an input is assigned to an output:
1. Press [F2] to open the Input assistant, or right click and select “Input
assistant” from the contextual menu.
Figure 67: Input Assistant for Selecting Variables
2. Under “Global variables” select the previously declared variable “Output_1”

and click [OK] to add it.
3. Enter the allocation “=” behind the variable name.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4. Repeat Step 2 for the “Input_1” variable.
Figure 68: Example of an Allocation
5. To compile, click on Project > Compile all in the menu bar.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.2.5 Loading and Running the PLC Program in the Fieldbus

Controller (ETHERNET)
Requirement:
- The simulation is deactivated (Online > Simulation).
- The PC is linked to the controller via ETHERNET. Refer to Section “Device

Description” > …> “ETHERNET – X1, X2 Network Connection”.
Proceed as follows:
1. In the menu bar click on Online and select Communication parameters

…. The “Communication Parameters” window opens.
2. To select a communication link, click on [New …] in the “Communication

Parameters” window. A window opens in which you can define a
communication link.
Figure 69: Creating a Communication Link – Step 1
Manual
750-8214 PFC200; G2; 2ETH RS CAN
3. In the “Name” field enter a designation for your fieldbus controller and then
click on “Tcp/Ip (Level 2 Route)”. Then click [OK].
4. In the “Communication Parameters” window enter the IP address of your

fieldbus controller in the “Address” field and then press Enter. To close
the window, click on [OK].
To select an already created controller, select it in the left window and then
click on [OK].
5. Transfer the PLC program by clicking on Online in the menu bar and select
Login.
6. Ensure that the Run/Stop switch for the fieldbus controller is set to “Run”.
7. Start the PLC program by clicking on Online > Start in the menu bar.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.2.6 Creating a Boot Project

Create a boot project to ensure that the PLC program starts automatically again
after a fieldbus controller restart. In the menu bar select Online > Create boot
project. You must be logged in to CODESYS to use this function.
Automatic loading of the boot project

In addition, you can load the boot project automatically when starting the
fieldbus controller. Click on the “Resources” tab and open “Target system
settings”. Select the “General” tab and “Load boot project automatically”.
If a boot project (DEFAULT.PRG and DEFAULT.CHK) is present under

/home/codesys and the “Run/Stop” switch of the fieldbus controller is set to
“Run”, the fieldbus controller automatically starts with the processing of the PLC
program. The PLC program is not started if the switch is set to “Stop”.
If a PLC program is running in the fieldbus controller, a PLC task starts with the
reading of the fieldbus data (only with fieldbus controllers and fieldbus
connection), the integrated input and output data and the I/O modules. The
output data changed in the PLC program is updated after the PLC task is
processed. A change in operating mode (“Stop/Run”) is only carried out at the
end of a PLC task. The cycle time includes the time from the start of the PLC
program to the next start. If a larger loop is programmed within a PLC program,
the task time is prolonged accordingly. The inputs and outputs are updated
during processing. These updates only take place at the end of a PLC task.
9.3 Syntax of Logical Addresses

Access to individual memory elements according to IEC 61131-3 is possible
using only the following special symbols:
Table 45: Syntax of Logical Addresses

Item Prefix Description Notes:
1 % Starts the absolute address -
2 I Input
Q Output
M Flag
3 X Single bit Data width
B- Byte (8 bits)
W Word (16 bits)
D Double word (32 bits)
4 Address
Two examples:
Addressing by word %QW27 (28th word)

Addressing by bit %IX1.9 (10th bit in word 2)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Enter the character string of the absolute address without empty spaces. The first
bit of a word has an address of 0.
9.4 Creating Tasks

Set the time response and the priority of individual tasks in the task configuration.
Watchdog
In an application program without task configuration, there is no watchdog that
monitors the cycle time of the application program (PLC_PRG).
Create a task as follows:
1. Open the task configuration by double-clicking on the “Task configuration”

module in the “Resources” tab.
Figure 72: Task Configuration
2. To create a task right-click on “Task configuration” and in the contextual

menu select “Attach task”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
3. To assign a new name to the task (e.g. PLC_Prog), click on “New Task”.
Then select the type of task. In this example, this is the “cyclic” type.
Observe the cycle time!

The minimum cycle time for I/O-based tasks is 2 milliseconds (ms)!
Figure 73: Changing Task Names 1
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4. Add the program module PLC_PRG that you have just created (see
Section “Editing the Program Modules”). To do this, right-clock on the
“Clock” symbol and in the contextual menu select “Attach program call-up”.
Then, click the [...] button and [OK].
Figure 74: Call-up to Add to the Program Module
5. Compile the example program by selecting Project > Rebuild all in the
context menu.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.4.1 Cyclic Tasks

You can assign a priority for each task in order to establish the task processing
sequence.
Figure 75: Cyclic Task
Order of Task Processing

The priorities given below do not specifiy the order of task processing. The tasks
start in an arbitrary order.
Priority 0 … 5:
Important arithmetic operations and synchronized access to I/O module process
images are to be carried out as tasks with the highest priorities 0 … 5. These
tasks are processed fully according to priority and correspond to Linux® RT
priorities
-79 through -74.
Priority 6 … 20:
Real-time access, such as access to ETHERNET and the file system, to fieldbus
data and to the RS-232 interface (when available) are to be carried out as tasks
with average priorities 6 … 20. These tasks are processed fully according to
priority and correspond to Linux® RT priorities -40 through -26.
Priority 21 … 31:
Applications such as long-lasting arithmetic operations and non-real-time-
relevant access to ETHERNET and the file system, to fieldbus data and the RS-
232 interface (when provided) are to be carried out as tasks with the lowest
priorities 21 … 31. No prioritiy distinction is made between tasks of priorities 21
Manual
750-8214 PFC200; G2; 2ETH RS CAN
… 31. These tasks all receive the same computing time from the operating
system (“Completely Fair Scheduler” procedure).
9.4.2 Freewheeling Tasks

So-called freewheeling tasks are not processed in cycles. Their processing
depends solely on the current capacity of the system. The input field “Priority
(0 … 31)” is provided for freewheeling tasks without a function. These tasks are
handled as tasks with priority 21 … 31.
Figure 76: Freewheeling Task
PLC-PRG as Freewheeling Task without Task Configuration

If you do not perform any task configuration, the program PLC_PRG is carried
out with the lowest priority at an interval of 10 ms. The runtime of “freewheeling
tasks” is not monitored by a CODESYS watchdog.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.4.3 Debugging an IEC Program

If the IEC program is debugged with breakpoints, the behavior on actuation of the
mode selector switch is defined as follows:
Provided that a task is not located on a breakpoint, RUN and STOP from the user
interface (IDE) and from the mode selector switch (BAS) always have an effect
on all tasks (case 1 and case 2).
Figure 77: Debugging (Case 1)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
If the mode selector switch and the STOP function of the user interface are used
simultaneously, the mode selector switch has priority (case 3 and case 4).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
As soon as a task is located at a breakpoint, only all other tasks can be controlled
with the mode selector switch.
Exception: If the mode selector switch is on STOP, the debug task is also no
longer processed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
If a task is at a breakpoint and the connection to the IDE is broken (e.g., by
logging out), all breakpoints are deleted.
The debug task stays at the current position until the next time the mode selector
switch is switched from STOP to RUN. In this case, the task continues to run
from the current position (case 7).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.5 System Events

Event tasks can be used in the CODESYS task configuration in addition to
cyclical tasks. Event tasks call up certain events in the device.
To activate events and define a program to be called up, open the window “Task
configuration” in the “Resources” tab in the CODESYS development
environment.
Figure 84: CODESYS – System Events
Do not set debug points in the event handlers!

Debug points in event handlers can lead to unforeseeable errors and must
therefore not be set!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The following events can be activated:
Table 46: Events

Name Description
start The event is called directly after the user program starts.
stop The event is called directly after the user program stops.
before_reset The event is called directly before the user program is
reset.
after_reset The event is called directly after the user program is
reset.
shutdown The event is called directly before the user program is
shutdown.
excpt_watchdog The event is called if a task watchdog is recognized.
excpt_access_violation The event is called if a memory access error to an
invalid memory area is recognized. (incorrect pointer,
invalid array index, invalid data descriptor)
excpt_dividebyzero The event is called if a division by zero is recognized.
after_reading_inputs The event is triggered after reading all of the inputs
independent of the user program.
before_writing_outputs The event is triggered before writing all of the outputs
independent of the user program.
debug_loop This event is triggered at every task call, if a breakpoint
was reached in this task and the processing of this task
is therefore blocked.
online_change This event is called up after initialization of the program
on an online change.
before_download This event is always called up before a download from
the IDE to the device takes place.
Application stops on a non-defined event handler!

If “excpt” events occur in the system and an event handler has not been defined,
the application goes into the “Stop” status.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.5.1 Creating an Event Handler

The example here is provided to illustrate how to define and use an event
handler. The event handler “excpt_dividebyzero” is used in this example.
First, a program is generated in the PLC_PRG- module which provokes division

by 0.
Figure 85: CODESYS Program Provokes Division by “0”
After this, the system event “excpt_dividebyzero” is activated in the Task

Configurator and the name of the event handler to be generated is entered in the
column “Called POU”.
Figure 86: CODESYS – Creating and Activating an Event Handler
To generate the event handler, click [Generate CALLBACK_DIV_BY_ZERO

function block].
A new function having the defined name then appears in the “Function blocks”
tab.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 87: CODESYS – New Module has been Generated
Handling for the event that has occurred is now programmed in this new function.
In the example here, the event is documented in a global variable.
Figure 88: CODESYS – Enter the Event in a Global Variable
The newly created project is now supported and can be loaded to the controller.
After startup, the value of the “Events” variable changes only when counter “i”
reaches the value 0, meaning that division by 0 has been performed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 89: CODESYS – Variable Contents Prior to Division by “0”
Figure 90: CODESYS – Variable Contents After Division by “0” and Call-up of the Event Handler
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.6 Process Images

A process image is a memory area in which the process data is stored in a
defined sequence and consists of the I/O modules attached to the local bus, the
PFC variables, the bit memory address area and the slaves attached to the
fieldbus.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 91: Process Image
The process image areas for PROFIBUS® slave, CANopen master/slave and
PROFIBUS® master are only available if the corresponding fieldbus interface is
implemented. Otherwise, the areas are not used.
Figure 92: Flag Area
9.6.1 Process Images for I/O Modules Connected to the

Controller
After starting the fieldbus controller, it automatically detects all connected I/O
modules.
The analog input and output data is stored first word by word in the process
image. Subsequent to this, come the digital input and output data bits combined
to form words.
The size and structure of the process image for the I/O modules connected to the
system are described in the appendix.
I/O Module Data Width

The data width of an I/O module is between 0 and 48 bytes.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
I/O Module Process Data

Check the I/O module process data whenever you add or remove the modules
to/from the fieldbus controller. Changing the I/O module topology results in an
adjustment of the process image, as the process data addresses also change.
9.6.2 Process Image for Slaves Connected to the Fieldbus

The size and structure of the process image for the slaves connected to the
system are described in the section for the specific fieldbus.
9.7 Access to Process Images of the Input and Output

Data via CODESYS 2.3
The following tables describe the possibilities with which you can access the
address ranges of the process image for the inputs and outputs connected to the
local bus.
Table 47: Access to the Process Images of the Input and Output Data – Local Bus
Memory Area Description Access Logical Address Space
via PLC
Local bus input Map of the local input modules Read Word %IW0 to %IW999
process image (I/O module 1 to 64*) in the RAM
Byte %IB0 to %IB1999
Local bus output Map of the local output modules Read/ Word %QW0 to %QW999
process image (I/O module 1 to 64*) in the RAM Write
Byte %QB0 to %QB1999
* The use of up to 250 I/O modules is possible with the WAGO local bus extension modules.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 48: Access to the Process Images of the Input and Output Data – Modbus
Memory area Description Access via Logical Address Space
PLC
Word
Modbus input variables, %IW1000 to %IW1999
Read
addressed by word via Modbus Byte
Modbus input
%IB2000 to %IB3999
process image
Bit
Modbus input variables,
Read %IX1000.0 …%IX1000.15 to
addressed by bit via Modbus
%IX1384.0 … %IX1384.15
Word
Modbus output variables, Read/ %QW1000 to %QW1999
addressed by word via Modbus Write Byte
Modbus output %QB2000 to %QB3999
process image Bit
Modbus output variables, Read/ %QX1000.0 …
addressed by bit via Modbus Write %QX1000.15 to %QX1384.0
… %QX1384.15
Table 49: Access to the Process Images of the Input and Output Data – PROFIBUS
PLC
PROFIBUS input PROFIBUS input variables Read Word
process image %IW2000 to %IW2499
Byte
%IB4000 to %IB4999
PROFIBUS PROFIBUS output variables Read/ Word
output process Write %QW2000 to %QW2499
image Byte
%QB4000 to %QB4999
Table 50: Access to the Process Images of the Input and Output Data – CANopen
PLC
CANopen input CANopen master or CANopen Read Word
process image slave input variables %IW3000 to %IW4999
Byte
%IB6000 to %IB9999
CANopen output CANopen master or CANopen Read/ Word
process image slave output variables Write %QW3000 to %QW4999
Byte
%QB6000 to %QB9999
Table 51: Access to the Process Images of the Input and Output Data – PROFIBUS
PLC
PROFIBUS input PROFIBUS input variables Read Word
process image %IW5000 to %IW7499
Byte
%IB10000 to %IB14999
PROFIBUS PROFIBUS output variables Read/ Word
output process Write %QW5000 to %QW7499
image Byte
%QB10000 to %QB14999
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 52: Access to the Process Images of the Input and Output Data – Flags
Memory Area Description Access via Logical Address Space
PLC
Total of 128 kB remanent Read/ %MW0 to
memory (65536 words). Write %MW65535
104 kB addressed by word via Read/ Word (Modbus)
Modbus (53248 words) Write %MW0 to %MW3327
Flag variables
Bit (Modbus)
6.5 kB addressed by bit via Read/ %MX0.0 … %MX0.15 to
Modbus (3328 words). Write %MX3327.0 …
%MX3327.15
Retain memory addressed by Read/ -
Retain variables
symbols in the NVRAM: 128 kB Write
* The use of up to 250 I/O modules is possible with the WAGO local bus extension modules.
The total size of the memory for flag and retain variables is 128 kB (131060
bytes). The size of these two sections can be customized as required, provided
the total (permissible) size is not exceeded.
If you are using bit-oriented addressing, remember that the basic address is
word-based. The bits are addressed from 0 to 15.
9.8 Addressing Example

The following addressing example clarifies the access to the process image:
Table 53: Arrangement of the I/O Modules for the Addressing Example
Fieldbus controller 750- 750- 750- 750- 750- 750- 750- 750-
400 554 402 504 454 650 468 600
1 2 3 4 5 6 7 8
Table 54: Addressing Example

I/O module Input data Output data Description
Type C*
2DI, 24 V, 3 ms:
1 %IX8.0 1. Digital input module with a data width of 2
bits. As the analog input modules already
750-400
occupy the first 8 words of the input process
2 %IX8.1 image, the 2 bits occupy the lowest-value bits
of the 8th word.
2AO, 4 – 20 mA:
1 %QW0
1. Analog output module with a data width of 2
750-554
words. This module occupies the first 2 words
2 %QW1
in the output process image.
1 %IX8.2 4DI, 24 V:
2. Digital input module with a data width of 4
2 %IX8.3
750-402 bits. These are added to the 2 bits of the 750-
3 %IX8.4 400 module and stored in the 8th word of the
4 %IX8.5 input process image.
1 %QX4.0 4DO, 24 V:
750-504 1. Digital output module with a data width of 4
2 %QX4.1 bits. As the analog output module already
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 54: Addressing Example
I/O module Input data Output data Description
Type C*
3 %QX4.2 occupies the first 4 words of the output

process image, the 4 bits occupy the lowest-
4 %QX4.3 value bits of the 4th word.
2AI, 4 – 20 mA:
1 %IW0
1. Analog input module with a data width of 2
750-454
words. This module occupies the first 2 words
2 %IW1
in the input process image.
%IW2 RS-232, C 9600/8/N/1:
%IW3 The serial interface module is an analog input
750-650 1 and output module, which displays 2 words
%QW2 both in the input process image and in the
%QW3 output process image.
1 %IW4 4AI, 0 – 10 V S.E:

2. Analog input module with a data width of 4
2 %IW5 words. As the 750-454 and 750-650 analog
750-468 input and output modules already occupy the
3 %IW6 first 4 words of the input process image, the 4
words of this I/O module are added behind the
4 %IW7 others.
End module
750-600 The passive 750-600 end module does not
transmit any data.
Analog input and output modules
Digital input and output modules
*C: Number of the input/output
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.9 Local Bus Synchronization

The local bus cycle and the CODESYS task cycle are optimally automatically
synchronized: This depends on the number of I/O modules connected and the
fastest CODESYS task cycle set in the fieldbus controller. The synchronization
cases described below can therefore take place.
In this section, CODESYS task denotes only tasks within CODESYS that contain
an access to the local bus. Tasks that do not access the local bus are not
synchronized in the same way as described below. For this, see section
“Creating Tasks.”
9.9.1 Case 1: CODESYS Task Interval Set Smaller than the Local
Bus Cycle
Execution of the CODESYS tasks is synchronized with the local bus cycle time.
The CODESYS task is processed in parallel to the local bus cycle. The
CODESYS task interval is extended to the local bus cycle time. This is necessary
so that each CODESYS task is started with new input data from the local bus and
the output values are also set at the module after each CODESYS task.
Figure 93: Local Bus Synchronization (Case 1)
CTI: CODESYS Task Interval

CT: CODESYS Task that accesses the I/O modules via the local bus
LBZ: Local Bus Cycle
Example:
CODESYS task interval (CTI): 100 µs
Local bus cycle (LBZ): 2000 µs
Result: Matching of the CODESYS task interval to the local bus cycle of 2000
µs.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.9.2 Case 2: CODESYS Task Interval Smaller than Twice the

Local Bus Cycle
Execution of the local bus is synchronized with the set CODESYS task interval.
At the end of the CODESYS task, the local bus cycle starts, which is processed
synchronously with the fastest CODESYS task. This ensures that when starting
each CODESYS Task, current input data are available from the local bus and the
output values of each CODESYS task are also output to the I/O modules.

Example:
Result: Execution of the local bus cycle every 2500 µs.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.9.3 Case 3: CODESYS Task Interval Greater than Twice the

Local Bus Cycle
The I/O data from the local bus are refreshed once prior to the CODESYS task
and once after the CODESYS task.
Prior to processing the CODESYS task, the local bus cycle is executed, which
provides the current input data for the CODESYS task. After execution of the
CODESYS task, an additional local bus cycle is started, which provides the
output data to the I/O modules.
This ensures that at the start of every CODESYS task, current input data are
available from the local bus and the output data from each CODESYS task are
quickly output to the I/O modules. This prevents processing of local bus cycles
that would unnecessarily use a great deal of computing time on the CPU.

Example:
Result: Execution of the local bus cycle 2000 µs prior to the CODESYS task and
once directly after the CODESYS task.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.9.4 Case 4: CODESYS Task Interval Greater than 10 ms

Synchronization takes place as in case 3; however, the output modules would be
reset to their default state after 100 ms without a local bus cycle. This reliably
prevents the execution of a local bus cycle after at least every 10 ms.
The I/O data from the local bus are refreshed once before the CODESYS task
and once after the CODESYS task and an additional local bus cycle is also
executed every 10 ms.

CT: CODESYS task that accesses the I/O modules via the local bus
LBZ: Local bus cycle
Example:
Result: Execution of the local bus cycle 2000 µs prior to the CODESYS task,
once directly after the CODESYS task and 10 ms after the previous local bus
cycle.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.9.5 Local Bus (KBus) Settings
Figure 97: Local Bus (KBus) Settings
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 55: Local Bus (KBus) Settings
Parameter Explanation
The update mode is used to configure how the local bus process
data is to be updated (refreshed).
In the asynchronous update mode process data
Asynchronous
Update mode are refreshed in cycles at a definable interval.
In the synchronous update mode the process
Synchronous* data are synchronized with the most rapid
CODESYS task that accesses the local bus.
The update interval for the local bus is set by the cycle time. This
setting is effective only in the asynchronous mode.
KBus cycle
1000 µs Minimum value 1 millisecond
time *
10000 µs Default value 10 milliseconds
50000 µs Maximum value 50 milliseconds
This value indicates the priority for the local bus thread. This
setting is effective only in the asynchronous mode.
KBus thread This priority is equivalent to the priority of the cyclic CODESYS
priority tasks (see section “Cyclic Tasks”).
0* Highest priority
15 Lowest priority
PLC stop Specifies the response of the local bus outputs when the PLC
behavior application stops.
Hold last value The output states are retained.
Set to zero* Outputs are set to zero.
*
Default setting
9.9.5.1 Effect of Update Mode on CODESYS Tasks
9.9.5.1.1 Asynchronous Update Mode
In the asynchronous update mode there is no direct influence on CODESYS task

behavior.
Local bus “freeze” on priority conflicts!

In the asynchronous update mode there is a risk of the local bus “freezing”, as
the local bus thread operates at the same priority as the IEC tasks. The local
bus thread must therefore use a priority higher than that of the IEC task to
prevent this from occurring.
9.9.5.1.2 Synchronous Update Mode
In the synchronous update mode the runtime behavior of CODESYS tasks can
be influenced by the local bus. The minimum task interval that can then be
Manual
750-8214 PFC200; G2; 2ETH RS CAN
achieved depends on the duration of a local bus cycle. The duration of a local
bus cycle, on the other hand, is based on the I/O modules connected to the bus.
As a rule of thumb: The shorter the local bus structure, the shorter the cycle time
and digital modules are faster than analog or complex ones.
In the event of a local bus error, the CODESYS tasks are blocked until the error
is rectified, i.e., when a local bus cycle has been successfully executed again.
No call-up of local bus status when local bus errors are present!
If a local bus error has occurred, it is not possible to call up the bus status using
KBUS_ERROR_INFORMATION (mod_com.lib) while in the synchronous update
mode.
9.10 Memory Settings in CODESYS

The list below illustrates the standard memory allocation of the controller:
• Program memory: 16 Mbyte (max.)

• Data memory: 64 Mbytes
• Input data: 64 kbytes
• Output data: 64 kbytes
• Flags: 24 kbytes
• Retain: 104 kbytes
• Function block limitation: 12 * 4096 bytes = 48 kbytes
9.10.1 Program Memory

The program memory (also code memory) cannot be configured and is limited to
a maximum of 16 Mbytes. The memory space actually available is based on the
scope of installed applications.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 98: Program Memory (Example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.10.2 Data Memory and Function Block Limitation

The data memory is set for 64 Mbytes in the controller's initial state.
This set value has already been requested in the system after a successful
program download and can be fully utilized.
Together with the data memory to be used by the application, memory is required
for the individual program function blocks in the system.
The size of the administration space is calculated from the function block
limitation * 12 (i.e., normally 4096 * 12).
The actual size of the main memory required in the system for data is the sum of
global data memory and function block limitation memory.
This value should not exceed the value specified for “Size of entire data
memory.”
Figure 99: Data Memory and Function Block Limitation (Example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.10.3 Remanent Memory

A total of 128 kbytes of remanent memory is available for the IEC-61131
application.
The remanent section is subdivided into the flag area (memory) and the retain
area.
Figure 100: Remanent Main Memory (Example)
The breakdown of the flag and retain variables can be customized as required.
Observe general conditions!

The sum of Memory + Retain must not exceed the maximum value of 128 kbytes
(0x20000).
A maximum of 10,000 retain variables can be created.
Figure 101: Flag and Retain Memory (Example)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.11 General Target System Settings
Figure 102: General Target System Settings
No change to the settings is necessary on the “General” tab.
The “Update unused I/Os” box can be checked for initial startup. Enabling this
results in a higher CPU load and possibly a significant effect on task processing.
</dg_
9.12 CODESYS Visualization

CODESYS Web visualization is based on Java technology. All Java programs
require a Java runtime environment (JRE), which must be installed on the host
PC along with a web browser. An applet is stored in the file system of a Web
server and is accessible to web browsers via an HTML page.
You create all visualization types (HMI and Web visualization) with the same
CODESYS graphic editor. Select the visualization type in the “Target system
settings” window. A description file in XML format is generated from the
information for each of these pages. You can find these files in the subfolder
“visu” of the CODESYS installation path. The HTML home page “webvisu.htm”
and the Java archive “webvisu.jar” in the applet (webvisu.class) are also saved
there in a compressed format.
Once you have selected a visualization type, the following steps must be
performed to execute the technique:
1. Click the “Resources” tab and open the “Target system settings.” Specify
whether you wish to have visualization displayed as a “Web visualization”
using a web browser.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 103: Selecting the Visualization Technique in the Target System Settings
Manual
750-8214 PFC200; G2; 2ETH RS CAN
2. Generate a start page for the visualization. Right-click the “Visualization”
folder in the “Visualization” tab. Select Add object ... from the contextual
menu. The “New visualization” dialog box opens.
Figure 104: Creating the PLC_VISU Starting Visualization
3. In the “New visualization” dialog window, enter the name PLC_VISU for the
start visualization. This page is then displayed as the start page upon
system startup.
4. Activate the CODESYS Web server in the WBM on the “Ports and Services
– CODESYS Services” page in the “CODESYS Webserver” group.
5. Activate the http service in the WBM on the “Ports and Services – Network
Services” page in the “HTTP” group.
If you transfer the PLC program to the controller (Online > Login) and start the
program (Online > Start), enter one of the following lines in the address line of
the web browser for online visualization:
- “https://<IP address of the controller>/webvisu”, preferred method (http can

also be used instead of https)
- “https://<IP address of the controller>”, if the default Web server in the

WBM has been set to“WebVisu” (http can also be used instead of https)
- “http://<IP address of the controller>:8080/webvisu.htm”
You can also have Web visualization displayed via the WBM (see Section
“`CODESYS - WebVisu´” Page).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Frequently Asked Questions

Additional information (FAQs) on CODESYS Web visualization is also provided
in the Section “Frequently Asked Questions about CODESYS Web Visualization”
and in the online Help function for CODESYS 2.3.
9.12.1 Limits of CODESYS Visualization

The controller supports the “WebVisu” visualization type integrated into
CODESYS. Technological limitations can be caused by the visualization type
used.
Compared to “HMI”, Web visualization on the controller is performed within

significantly narrower physical limits. Whereas “HMI” can access almost unlimited
resources on a desktop PC, the following limitations must be observed when
using Web visualization:
Adapting to the File System
The overall size of the PLC program, visualization files, bitmaps, log files,
configuration files, etc. must fit into the file system.
Process Data Memory
Web visualization uses its own protocol for exchanging process data between
applet and control.
The controller transfers process data with ASCII coding. The pipe symbol (“|”) is
used to separate two process values. Therefore, the space requirement for a
process data variable in the process data memory is dependent not only on the
data type, but also on the process value itself. Thus, a variable of the “WORD”
type occupies between one byte for the values 0 through 9 and five bytes for
values from 10000 and greater. The selected format (ASCII + |) only permits a
rough estimate of the space requirement for the individual process data in the
process data buffer. If the size of the ASCII coded process data is exceeded,
Web visualization no longer works as expected.
Computer Performance/Processor Time
The controller is based on a real-time operating system. This means that high-
priority processes (e.g., PLC program) interrupt or block lower priority processes.
The Web server responsible for Web visualization is among these lower priority
processes.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Processor Time
Make sure when configuring tasks, that there is sufficient processor time
available for all processes.
Network Load
The controller's CPU processes both the PLC program and network traffic.
ETHERNET communication demands that each received telegram is processed,
regardless of whether it is intended for the controller or not.
A significant reduction of the network load can be achieved by using switches

instead of hubs.
There is no measure against broadcast telegrams that can be used on the

controller, however. These can only be curtailed by the sender, or blocked with
configurable switches that have a broadcast limitation. A network monitor such as
“wireshark” (www.wireshark.com) provides an overview of the current load in your
network.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.12.2 Eliminating Errors in CODESYS Web Visualization

If you are experiencing problems when working with the CODESYS Web
visualization, use the following table to find the solution. If you cannot eliminate
the problem, please contact WAGO support.
Table 56: Errors and Remedies

Error Solution
Internet Explorer reports Close all Internet Explorer windows and restart. If the error persists, this
the error “APPLET NOT indicates a missing or damaged file.
INITIATED” Using FTP, check if the entire Java archive “webvisu.jar” is available in
the “/PLC” folder of the controller. The original file can be found in the
installation path of CODESYS (usually under C:\Programme\WAGO
Software\CODESYS V2.3\Visu\webvisu.jar).
If necessary, replace the damaged file using FTP or force the download
of all files in CODESYS with Purge All > Compile All > Log in.
Web visualization is not Have you installed the JRE? Check the firewall settings, e.g., if port 8080
displayed is open.
Web visualization The call-up intervals selected in the task configuration are too small. As a
“freezes”. result, the Web server of the controller — which is executed with a low
Web visualization stops priority — does not receive sufficient computer time, if any at all.
after an extended period
of time. If no (explicit) task configuration has been provided, the PLC_PRG is
(implicitly) executed as a free running task with Priority 1. This
significantly limits the Web server’s computing time. Always provide a
task configuration when using Web visualization. In doing so, the call-up
interval should not exceed three times the average execution time.
When determining the execution time, ensure that the PLC program has
reached a “steady state.” When determining the execution time, ensure
that the PLC program is not “steady state.”
Web visualization Not all files may fit into the controller's file system. Delete any unneeded
cannot be loaded into data (e.g., via FTP).
the controller
Bitmap is not displayed If the name of an image file contains umlauts, the Web server cannot
interpret these image names.
Java console reports: The JRE does not find the entry point for the class “webvisu.class” in the
“Class not found” Java archive “WebVisu.jar”. The Java archive is probably incomplete.
Delete “WebVisu.jar” from the Java cache and/or deactivate the cache.
In this case, the controller requests the archive (applet) again. If the
problem persists, reload the project into the controller.
Web visualization is Process data communication has failed.
static, all process values If Web visualization is operated over a proxy server, then a SOCKS
are “0” proxy is also necessary for process data exchange in addition to the
actual HTTP proxy.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
9.12.3 FAQs about CODESYS Web Visualization

How can I optimize the applet for special screen resolutions?
In order to optimize the Web visualization for display on a device with a fixed
resolution, proceed as follows:
In the “Target system settings”, enter the pixel width and height in the tab
“Visualization”. When the visualization is created, the visible area is highlighted in
gray. However, the actual pixel width and height of the Web visualization is
defined by the attributes “Height” and “Width” of the HTML APPLET tag in the
“webvisu.htm” file. Do not forget to also adapt these parameters to the existing
resolution.
Which JRE should I use?
Java2 standard edition Version 1.5.0 (J2SE1.5.0_06) or higher is recommended.

This is available free of charge at www.oracle.com.
Microsoft's MSJVM3810 was also tested. For PDAs, there are runtime
environments available from other manufacturers (JamaicaVM, CrEme, etc.).
Please consider that for the Web visualization, these solutions can behave
differently within their scope of services (e.g., stability) than those mentioned
above.
Should the Java Cache be used?
This depends on the situation. After a standard installation, the cache is enabled.
If the cache is enabled, the JRE uses it to store applets and Java archives. If the
Web visualization is called up a second time, it requires considerably less time to
start because the applet (approx. 250 kb) does not need to be reloaded via the
network, but is already available in the cache. This is especially useful when
network connections are slow.
Note:
The Java archives may not be completely transferred into the cache due to
network failures. In this case, the cache must be cleared manually or disabled.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Why does the visualization element “TREND” in the Web visualization only
work “Online”?
The following settings must be selected for visualization projects: Resources tab
> Target system settings.
Activate “Web visualization” and “Trend data recording within control”. Otherwise,
the trend data is stored on the hard drive of the CODESYS development PC.
This makes a permanent connection between the controller and the CODESYS
gateway necessary. If this connection is interrupted, this may lead to the
controller behaving unpredictably.
In the TREND configuration dialog, you can choose between “Online” and
“History” operating modes. The controller only supports the “Online” operating
mode for visualization projects since it is not possible to configure the maximum
size (quota) of the trend files (*.trd). Uncontrolled expansion of trend files can
lead to unpredictable controller behavior.
In most cases, the use of the “HISTOGRAM” visualization element is the better
choice, as this gives full control over the time and number of measurements and
thus the amount of memory required.
What needs to be observed when the visualization element “ALARM

TABLE” is used in the Web visualization?
The status of this component is best described as “Add-On”, i.e., an extra that is
free of charge and not warrantied.
The following settings must be selected for visualization projects: Resources tab
> Target system settings.
Activate “Web visualization” (checkmark) and “Alarm handling within control”.
Otherwise, the alarm data is processed on the CODESYS development PC. This
makes a permanent connection between the controller and the CODESYS
gateway necessary. If this connection is interrupted, this may lead to the
controller behaving unpredictably.
Manual
188 e!RUNTIME Runtime Environment WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
10 e!RUNTIME Runtime Environment

10.1 General Notes
Additional Information
Information on the installation and startup of e!COCKPIT is provided in the
corresponding manual.
Information on programming is provided in the CODESYS 3 documentation.
Manual
WAGO I/O System 750 e!RUNTIME Runtime Environment 189
750-8214 PFC200; G2; 2ETH RS CAN
10.2 CODESYS V3 Priorities

A list of priorities implemented for the controller is provided below as
supplementary information to the CODESYS 3 documentation.
Table 57: CODESYS V3 Priorities

Linux® IEC
Scheduler Task Remark
Priority Priority
Local bus or
-95 … -86 Local bus (-88)
fieldbus - HIGH
Task registers changes
to the mode selector
Mode selector switch and changes
-85
switch monitoring the state of the PLC
application. (start, stop,
reset warm/cold)
CODESYS Execution of the
-83
watchdog watchdog functions
For real-time tasks
Preemptive which must not be
Cyclic and event-
scheduling -55 … -53 1 … 3 influenced in execution
controlled IEC task
- by external interfaces
Real-time (e.g., fieldbus).
range CAN (-52 … -51)
PROFIBUS (-49
Local bus or
-52 … -43 … -45)
fieldbus - MID
Modbus® slave/master
(-43)
For real-time tasks
which must not
Cyclic and event-
-42 … -32 4 … 14 influence fieldbus
controlled IEC task
communication during
execution.
Local bus or
-13 … -4
fieldbus – LOW
Communication with
CODESYS the CODESYS
Fair
communication development
scheduling Back-
environment
- ground
Cyclic, event-
None real- (20)
controlled and Incl. standard priority of
time range 15
freewheeling IEC the visualization task
task
Manual
190 e!RUNTIME Runtime Environment WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
10.3 Memory Spaces under e!RUNTIME

The memory spaces in the controller under e!RUNTIME have the following sizes:
• Program memory: 32 Mbytes

• Data memory: 128 Mbytes
• Input data: 64 kbytes
• Output data: 64 kbytes
• Flags: 24 kbytes
• Retain: 104 kbytes
• Function block limitation: 12 * 4096 bytes = 48 kbytes
10.3.1 Program and Data Memory

The program memory (also code memory) has a maximum size of 32 MB.
The data memory has a maximum size of 128 MB.
Both areas are separate from each other and are requested when downloading
to the system depending on the scope of the program. If the size limit is
exceeded, it is displayed as an error.
10.3.2 Function Block Limitation

Together with the data memory to be used by the application, memory is required
for the individual program function blocks in the system.
The size of the administration space is calculated from the function block
limitation * 12 (i.e., 4096 Byte * 12).
The actual size of the main memory required in the system for data is the sum of
global program and data memory and function block limitation memory.
10.3.3 Remanent Memory

A total of 128 kbytes of remanent memory is available for the IEC-61131
application.
The remanent section is subdivided into the flag area (memory) and the retain
area.
Figure 105: Remanent Main Memory
Manual
WAGO I/O System 750 Modbus – CODESYS V2 191
750-8214 PFC200; G2; 2ETH RS CAN
11 Modbus – CODESYS V2
</dg_
11.1 General
Modbus is a non-vendor-specific, open fieldbus standard for a wide range of
applications in production and process automation. The Modbus communications
protocol is based on a master/slave or client/server architecture that uses
function codes for execution of individual Modbus services, which have reading
or writing access to individual or multiple elements of the Modbus data model
simultaneously.
11.2 Features
The Modbus slave implemented in the PFC200 has the following features:
• 3 modes: Modbus TCP, Modbus UDP and Modbus RTU, which can be run
independently of one another simultaneously
• Each mode can be configured
• 10 supported Modbus services (Function Codes): FC1 to FC6, FC15,

FC16, FC22, FC23
• Data exchange via 1000 registers in each of the local Modbus process
images
• 768-byte sector that can be addressed by bits in each local Modbus

process image
• Access to a 104 kB flag sector (total of 53248 registers/words, with 3328

addressable bits)
• 28 Information and configuration registers
• Up to 1000 TCP connections
• Modbus communications monitoring using programmable watchdogs
• Configurable response on PLC stop
• Configurable response on disruption of Modbus communication
Manual
192 Modbus – CODESYS V2 WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
11.3 Configuration
All of the Modbus operating modes are configured using the CODESYS PLC
configuration.
Figure 106: CODESYS PLC Configuration - Modbus Settings
The Modbus slave configuration is composed of four basic parameter groups:
• Modbus settings,
• Modbus TCP settings,
• Modbus UDP settings,
• Modbus RTU settings.
A detailed description of all the parameter groups is given in the following

sections.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.3.1 Modbus Settings

The “Modbus settings” group contains the following configuration parameters.
Table 58: Modbus Settings

PLC stop Response of the Modbus slave when the controller has halted
behavior (controller in STOP state)
No data No data exchange possible. Modbus requests will
exchange always be answered by the exception response
“ILLEGAL FUNCTION” (0x81).
Switch to Data exchange possible. Substitute values (0)
substitute are provided for Modbus read requests and the
*
value values accepted unchanged in the local Modbus
process image for write requests, without passing
these on to the controller.
Hold last value Data exchange possible. The last frozen values
are provided for Modbus read requests and the
values accepted unchanged in the Modbus
process image for write requests, without passing
these on to the controller.
Fieldbus error Response of the Modbus slave to detected fieldbus errors
response (interruption of communication).
No data No data exchange possible.
exchange
Switch to Data exchange possible. Substitute values (0)
substitute are supplied from the Modbus process image for
*
value PLC read functions; for write access the values
are accepted unchanged in the Modbus process
image without passing them on to the Modbus
master.
Hold last value Data exchange possible. The previously frozen
values are supplied from the Modbus process
image for PLC read functions; for write access
the values are accepted unchanged in the
Modbus process image without passing them on
to the Modbus master.
*
Default setting
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.3.2 Modbus TCP Settings

The “Modbus TCP Settings” contains the following configuration parameters for
the “Modbus TCP” mode:
Table 59: Modbus TCP Settings

TCP mode Enable for the Modbus TCP mode
Off Operation not permitted
*
Active Operation possible
TCP port Port number for the TCP link
1 Minimum port number
*
502 Modbus default port
65535 Maximum port number
TCP Timeout Time-out for a TCP link
1 100 ms (1 × 100 ms)
*
600 60 seconds (600 × 100ms)
65535 1 h 49 min 13 s 500 ms (65535 × 100 ms)
*
Default setting
11.3.3 Modbus UDP Settings

The “Modbus UDP Settings” group contains the following configuration
parameters for the “Modbus UDP” mode:
Table 60: Modbus UDP Settings

UDP mode Enable for the Modbus UDP mode
Off Operation not permitted
*
UDP port Port number for the UDP link
1 Minimum port number
502* Modbus default port
65535 Maximum port number
*
Default setting
11.3.4 Modbus RTU Settings

The “Modbus RTU Settings” group contains the following configuration
parameters for the “Modbus RTU” mode:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 61: Modbus RTU Settings
RTU mode Enable for the Modbus RTU mode
Off* Operation not permitted
Device ID Device ID (device address) for the tty device
1* min. device ID
247 max. device ID
Maximum Response timeout for a request in [ms]
response time 2000 min. response time = 2 seconds. If this value is
set lower than 2 seconds, it will be corrected
internally to 2 seconds.
*
5000 Default = 5 seconds
4294967295 max. response time > 71 hours.
Interface Device name
“dev/…” Name of the tty in the string
“dev/ttyO0” *
Standard tty
Baud rate Communication baud rate
1200 baud 1200 baud min. transmission speed
2400 baud 2400 baud
4800 baud 4800 baud
9600 baud 9600 baud
19200 baud 19200 baud
38400 baud 38400 baud
57600 baud 57600 baud
*
115200 baud 115200 baud, max. transmission speed
Stop bits Number of stop bits
1 stop bit* 1 stop bit in the frame; must be used when even
or odd parity has been selected.
2 stop bits 2 stop bits in the frame; must be used when
“None” has been selected for parity.
Parity Parity check
None No parity check performed; 2 stop bits must be
selected in the configuration for this setting.
*
Even Even parity
Odd Odd parity
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 61: Modbus RTU Settings
Flow control Data flow control (Supported only for the setting “RS-232” for the
physical interface.)
None* No data flow control
RTS/CTS Hardware flow control
Physical Mode for the physical interface
interface RS-232* RS-232 is used as the physical interface.
RS-485 RS-485 is used as the physical interface.
*
Default setting
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
11.4 Data Exchange

Modbus data exchange is performed in cycles or acyclically using Modbus
services. The type and number of usable Modbus services depends on the area
that is addressed. There are generally four Modbus-relevant address areas in the
PFC200:
• Modbus input process image (Modbus Input) – is an area in the PIO (PIO
= Output Process Image), in which data from the PLC is provided in cycles
exclusively for Modbus Read services.
• Modbus output process image (Modbus Output) – is an area in the PII

(PII = Input Process Image), in which Modbus Write services provide data
for cyclic reading by the PLC. Modbus Read services are also acceptable in
this area.
• Modbus flag area – is an area, in which both Modbus Read and Write
services can be executed.
• Modbus register – is an area, in which the WAGO specific information and

configuration registers are contained. Only Modbus register services may
be executed in this area.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.1 Process Image

The main data interfaces between the PLC and the Modbus slave are the local
Modbus process images in the PLC address area based on IEC 61131. The
Modbus input process image (Modbus Input) is in the PIO and the Modbus output
process image (Modbus Output) in the PII. Data memory blocks of 2 kB (1000
registers/word) are available for each local Modbus input and output process
image. The first 768 bytes of each of these data blocks are also provided for
executing bit services.
Figure 107: Modbus Process Image
As no direct access to the I/O modules is provided by the fieldbus, data can be
exchanged via this interface between the PLC and Modbus for processing in the
control system (PLC). Using this data in the individual I/O modules connected to
the PLC can then be performed by the application.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.2 Flag Area

Modbus can also exchange data and fieldbus variables with the PLC via the flag
area. Caution is urged, however, when using data and/or variables in this area
that is accessed by both Modbus and the PLC. This “conflicting” access is not
protected from either side and could result in data inconsistency.
Figure 108: Flag Area
The figure shows the maximum addressable flag area with a size of 104 kB.
The actual addressable flag area depends on the current memory arrangement in
the target system settings in CODESYS.
The default setting is 24 kB.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.3 Modbus Registers

WAGO specific registers are implemented in the last Modbus-relevant address
area; this simplifies the reading of certain system and Modbus information, as
well as configuration.
The Modbus address area reserved for these registers ranging from the Modbus
starting address of 4096 (0x1000) up to the Modbus end address of 12287
(0x2FFF), without any allocation to the IEC 61131 address area. These registers
can be queried using the register read services FC3, FC4 and FC23 and with the
register write services FC6, FC16 and FC23. A detailed description of the
individual registers is given in the section “WAGO Modbus Registers”.
11.4.4 Modbus Mapping

11.4.4.1 Modbus Mapping for Write Bit Services FC1, FC2
The table below outlines the mapping for the Modbus-reading, bit-oriented
services:
• FC1 – Read Single Coil,
• FC2 – Read Discrete Inputs.
Table 62: Modbus Mapping for Read Bit Services FC1, FC2
Modbus Address IEC 61131 Description
(hexadecimal values Address
in parentheses)
0 … 6143 %IX1000.0 … Modbus Output:
(0x0000 … 0x17FF) %IX1383.15 6144 PFC input bit variables in the first
384 registers/words (768 bytes) of the
2kB Modbus output process image in the
PII.
Note: In this area, the read bit services
return the content from the bit-addressed
PII.
6144 … 12287 %QX1000.0 … Modbus Input:
(0x1800 … 0x2FFF) %QX1383.15 6144 PFC output bit variables in the first
384 registers/words (768 bytes) of the 2
kB Modbus-input process image in the
PIO.
12288 … 65535 %MX0.0 … Maximum bit-addressable flag area:
(0x3000 … 0xFFFF) %MX3327.15 53248 bit flags (6.5 kB);
the actual addressable flag area
depends on the current memory
arrangement in CODESYS.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.4.2 Modbus Mapping for Write Bit Services FC5, FC15
The table below outlines the mapping for the Modbus-writing, bit-oriented
services:
• FC5 – Write Single Coil
• FC15 – Write Multiple Coils
Table 63: Modbus Mapping for Write Bit Services FC5, FC15
in parentheses)
0 … 6143 %IX1000.0 … Modbus Output:
(0x0000 … 0x17FF) %IX1383.15 6144 PFC input bit variables in the first
384 registers/words (768 bytes) of the
2kB Modbus output process image in the
PII.
6144 … 12287 %QX1000.0 … Modbus Output:
(0x1800 … 0x2FFF) %QX1383.15 Modbus-only area for bit-oriented write
access.
Bit-based write services for this area are
acknowledged by the Modbus slave with
the Modbus exception code “ILLEGAL
DATA ADDRESS” (0x02).
12288 … 65535 %MX0.0 … Maximum bit-addressable flag area:
(0x3000 … 0xFFFF) %MX3327.15 53248 bit flags (6.5 kB);
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.4.3 Modbus Mapping for Read Register Services FC3, FC4, FC23
The table below outlines the mapping for the Modbus-reading, register-oriented
services:
• FC3 – Read Holding Registers,
• FC4 – Read Input Registers,
• FC23 – Read/Write Multiple Registers
Table 64: Modbus Mapping for Read Register Services FC3, FC4, FC23
in parentheses)
0 … 999 %IW1000 … Modbus Output:
(0x0000 … 0x03E7) %IW1999 1000 PFC input registers/words in the
2 kB Modbus output process image in
the PII.
Note: In this area, the read register
services return the content from the PII.
1000 … 1999 %QW1000 … Modbus Input:
(0x03E8 … 0x07CF) %QW1999 1000 PFC output registers/words in the
2 kB Modbus input process image in the
PIO.
Note on FC23:
Only the Read portion of this service can
be executed.
2000 … 4095 Inhibited to Modbus-only area for
(0x07D0 … 0x0FFF) register-oriented read access. Register-
based read services for this area are
4096 … 12287 No IEC 61131 Information and configuration registers:
(0x1000 … 0x2FFF) address Not all Modbus addresses in this range
are valid.
Valid Modbus addresses are described
in the Section “WAGO Modbus
Registers”.
Access to invalid addresses are
Note on FC23:
The Write portion of this service can only
be executed for registers that data can
be written to.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 64: Modbus Mapping for Read Register Services FC3, FC4, FC23
in parentheses)
12288 … 65535 %MW0 … Maximum addressable flag area:
(0x3000 … 0xFFFF) %MW53247 53248 register/word flags (104 kB);
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.4.4.4 Modbus Mapping for Write Register Services FC6, FC16, FC22, FC23
The table below outlines the mapping for Modbus-writing, register-oriented

services.
• FC6 – Write Single Register,
• FC16 – Write Multiple Registers,
• FC22 – Mask Write Register, not for information and configuration registers
• FC23 – Read/Write Multiple Registers.
Table 65: Modbus Mapping for Write Register Services FC6, FC16, FC22, FC23
in parentheses)
0 … 999 %IW1000 … Modbus Output:
(0x0000 … 0x03E7) %IW1999 1000 PFC input registers/words in the
2 kB Modbus output process image in
the PII.
1000 … 1999 No access to: Modbus Output:
(0x03E8 … 0x07CF) %QW1000 … Inhibited Modbus area for register-
%QW1999 oriented write access.
Register-oriented write services in this

area are acknowledged by the Modbus
slave with the Modbus exception code
“ILLEGAL DATA ADDRESS” (0x02).
2000 … 4095 Inhibited Modbus area for register-
(0x07D0 … 0x0FFF) oriented write access.
Register-oriented write services in this

area are acknowledged by the Modbus
slave with the Modbus exception code
“ILLEGAL DATA ADDRESS” (0x02).
4096 … 12287 No IEC 61131 Information and Configuration Registers:
(0x1000 … 0x2FFF) address Not all Modbus addresses in this area
are valid and not all registers can be
FC6, FC16, FC23 written to.
only, Valid Modbus addresses are described
not FC22 in the Section “WAGO Modbus
Registers”.
Access to invalid addresses are
Manual
750-8214 PFC200; G2; 2ETH RS CAN
in parentheses)
12288 … 65535 %MW0 … Maximum addressable flag area:
(0x3000 … 0xFFFF) %MW53247 53248 register/word flags (104 kB);
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5 WAGO Modbus Registers

System and Modbus data can be read and some Modbus parameters configured
using the WAGO Modbus registers. The following table lists all of the WAGO
Modbus registers.
Table 66: WAGO Modbus Registers

Modbus Address Data Length
Access Description
Dec. Hex. in Words
4130 0x1022 1 ro Number of registers in the
Modbus input process image in
the PAA
4131 0x1023 1 ro Number of registers in the
Modbus output process image in
the PAE
4132 0x1024 1 ro Number of bits in the Modbus
input process image in the PAA
4133 0x1025 1 ro Number of bits in the Modbus
output process image in the PAE
4136 0x1028 1 ro IP configuration: BootP(1),

DHCP(2) or permanently coded
IP address(4)
4138 0x102A 1 ro Number of established TCP
connections
4144 0x1030 1 r/w Modbus TCP Timeout (Changes

apply only to new connections)
4145 0x1031 3 ro MAC ID of the ETHERNET
interface (eth0)
4151 0x1037 1 r/w Modbus TCP response delay
4160 0x1040 1 ro PLC status
4352 0x1100 1 wo Watchdog command

4353 0x1101 1 ro Watchdog status
4354 0x1102 1 rw Watchdog timeout (configuration
register)
4355 0x1103 1 rw Watchdog config (configuration
register)
4356 0x1104 1 rw Watchdog operation mode
(configuration register)
8192 0x2000 1 ro 0x0000 (constant)

8193 0x2001 1 ro 0xFFFF (constant)
8194 0x2002 1 ro 0x1234 (constant)
8195 0x2003 1 ro 0xAAAA (constant)
8196 0x2004 1 ro 0x5555 (constant)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Access Description
Dec. Hex. in Words
8197 0x2005 1 ro 0x7FFF (constant)
8198 0x2006 1 ro 0x8000 (constant)
8199 0x2007 1 ro 0x3FFF (constant)
8200 0x2008 1 ro 0x4000 (constant)
8208 0x2010 1 ro Revision (firmware index)

8209 0x2011 1 ro Series code
8210 0x2012 1 ro Device code
8211 0x2013 1 ro Major firmware version
8212 0x2014 1 ro Minor firmware version
8213 0x2015 1 ro MBS version
The WAGO Modbus registers are described in more details in the following
sections.
11.5.1 Process Image Properties

11.5.1.1 Register 0x1022 – Number of Registers in the Modbus Input Process
Image
This register contains the number of registers available in the Modbus input
process image (Modbus input).
11.5.1.2 Register 0x1023 – Number of Registers in the Modbus Output

Process Image
This register contains the number of registers available in the Modbus output
process image (Modbus output).
11.5.1.3 Register 0x1024 – Number of Bits in the Modbus Input Process Image
This register contains the number of bits available in the Modbus input process
image (Modbus input).
11.5.1.4 Register 0x1025 – Number of Bits in the Modbus Output Process

Image
This register contains the number of bits available in the Modbus output process
image (Modbus output).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5.2 Network Configuration

11.5.2.1 Register 0x1028 – IP Configuration
This register contains information about the set IP configuration.

Possible values:
1 = BootP
2 = DHCP
4 = Fixed IP address
11.5.2.2 Register 0x102A – Number of Established TCP Connections
This register supplies the number of established TCP connections.

The maximum number of Modbus TCP connections is 1000.
11.5.2.3 Register 0x1030 – Modbus TCP Socket Timeout
This register contains the timeout value for the TCP sockets.
This value is given in units of 100ms (ticks). A new value is accepted only for new
connections which have not yet been established. In the event of any changes,
the already established connections will continue to operate using the previously
set timeout value.
11.5.2.4 Register 0x1031 – MAC Address for ETHERNET-Interface 1 (eth0)
This register provides the MAC address for the first ETHERNET interface (eth0).
MAC may also provide a partial result.
11.5.2.5 Register 0x1037 - Modbus TCP Response Delay
This register saves the value of the Modbus response delay.

This value is specified in ms units. The maximum delay is 32 ms, default value is
0 ms (no delay).
Transmission of the response to a Modbus request is delayed from the time of
processing (read and/or write register values) by the time set. In the meantime,
incoming requests can only be processed when the previous response is sent.
For Modbus UDP, this applies to all requests and for Modbus TCP, for each
connection. The actual length of time between a Modbus request and the
associated response depends on the number of parallel requests overall system
utilization; it is always greater than the response delay set. Changes to the
response delay become effective immediately for each subsequent request.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5.3 PLC Status Register

Register 0x1040 provides the status (state) that the controller is currently in.
Possible values:
1 = PLC running − PLC status is RUNNING.

2 = PLC stopped − PLC status is STOPPED.
11.5.4 Modbus Watchdog

The Modbus watchdog monitors in the Modbus slave the ongoing Modbus
communication with the Modbus master. All valid Modbus requests of a Modbus
master from all the services supported by the Modbus slave are trigger events
(see chapter “Modbus Mapping”). This does not apply to the Explicit Trigger
mode and the access to the register 0x1101 (Watchdog Status), which can be
configured via the 0x1103 (Watchdog Config) register.
If no trigger occurs during the watchdog within the timeout time set in the 0x1102
register (Watchdog Timeout), the “Watchdog Timeout” response is initiated. The
closing of all Modbus TCP connections can be configured as a response, see
register 0x1103 (Watchdog Config).
The Modbus watchdog supports two different functions

STANDARD_WATCHDOG and ALTERNATIVE_WATCHDOG. The operation
mode can be selected via the register 0x1104 (Watchdog Operation Mode).
The following diagrams show the possible states of the Modbus watchdog and
status transitions for the particular operation mode.
Figure 109: State Diagram, STANDARD_WATCHDOG Operation Mode
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 110: State Diagram, ALTERNATIVE_WATCHDOG Operation Mode
The state diagram for the ALTERNATIVE_WATCHDOG operation mode shows

that the watchdog is always active as soon as a timeout time > 0 is set in the
register 0x1102 (Watchdog Timeout). The writing of commands in the register
0x1100 (Watchdog Command) is limited in this operation mode. Only the
WATCHDOG_START command is permitted as a possible trigger. The only
possibilities to deactivate or stop the watchdog in ALTERNATIVE_WATCHDOG
mode are the setting of the timeout register to 0 after the timeout has elapsed
and the switching back to the STANDARD_WATCHDOG operation mode.
The following diagram shows the possible state transitions when operation
modes are switched.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 111: State Diagram, Switchover Operation Mode
11.5.4.1 Register 0x1100 – Watchdog Command
This register receives commands for the Modbus watchdog. It cannot be read,
i.e. it is not possible to read out the last command written.
The following commands are accepted depending on watchdog status:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 67: Watchdog Commands
Value Name Explanation
0x5555 WATCHDOG_ Starts the configured watchdog;
START in the WATCHDOG_UNCONFIGURED state if
no timeout is configured, the response is an
ILLEGAL_DATA_VALUE (0x03) exception. In
the WATCHDOG_EXPIRED state and the
STANDARD_WATCHDOG operation mode the
response is an ILLEGAL_FUNCTION (0x01)
exception. The watchdog must in this case be
reset first with the command
WATCHDOG_RESET to the
WATCHDOG_STOPPED state. In all other
cases the watchdog is restarted and the
WATCHDOG_RUNNING state is set.
0x55AA WATCHDOG_ Stops the running watchdog;
STOP in the WATCHDOG_UNCONFIGURED state,
the response is an ILLEGAL_DATA_
VALUE (0x03) exception if no timeout time is
set. In the WATCHDOG_EXPIRED state and
the STANDARD_WATCHDOG operation mode
the response is an ILLEGAL_FUNCTION (0x01)
exception. In this case the watchdog must first
be reset with the WATCHDOG_
RESET command to the WATCHDOG_
STOPPED state. In operation mode
ALTERNATIVE_WATCHDOG the response is
an ILLEGAL_DATA_
VALUE (0x03) exception. The command is not
generally permitted in this operation mode. In all
other cases, the watchdog is stopped
successfully and the WATCHDOG_
STOPPED state is set. In the
WATCHDOG_STOPPED state, a stop
command received several times in a row does
not have any impact on the behavior of the
watchdog and is therefore not acknowledged
with an error response.
0xAAAA WATCHDOG_ Resets the expired watchdog;
RESET the watchdog is reset in the
WATCHDOG_EXPIRED state and
STANDARD_WATCHDOG operation mode.
The watchdog is then in the
cases the response is an ILLEGAL_
DATA_VALUE (0x03) exception.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5.4.2 Register 0x1101 – Watchdog Status
This register provides the current state of the Modbus watchdog.

The following states are possible:
Table 68: Watchdog Status

0xFFFF WATCHDOG_ The Modbus watchdog is not configured, the
UNCONFIGURED “Watchdog Timeout” register (0x1102) contains
the value 0. This state can only be closed by
setting a timeout > 0.
0x0000 WATCHDOG_ The watchdog is configured, the “Watchdog
STOPPED Timeout” register (0x1102) contains a value >0.
In the STANDARD_WATCHDOG operation
mode the watchdog can be activated in this
state by the WATCHDOG_START command.
This state cannot be reached in the
ALTERNATIVE_WATCHDOG operation mode
since the watchdog is started automatically
here.
0x0001 WATCHDOG_ The Modbus watchdog is active, i.e. configured
RUNNING and started. The set timeout has not yet
expired.
0x0002 WATCHDOG_ The timeout set in register 0x1102 (Watchdog
EXPIRED Timeout) has expired. In the
STANDARD_WATCHDOG operation mode, the
watchdog in this state must be reset to the
WATCHDOG_STOPPED state with the
WATCHDOG_RESET command. In the
ALTERNATIVE_WATCHDOG operation mode,
the watchdog is automatically restarted with the
next trigger.
11.5.4.3 Register 0x1102 – Watchdog Timeout
This register contains the value for the watchdog timeout. The step width is
100 ms and the maximum value is 65535 (corresponds to 6553.5 s). The default
value is 0. In this case the watchdog cannot be started and will have the
WATCHDOG_UNCONFIGURED state.
The register can be read and written in the states

WATCHDOG_UNCONFIGURED, WATCHDOG_STOPPED and
WATCHDOG_EXPIRED. However, if the watchdog is active
(WATCHDOG_RUNNING state), this register can only be read. The response to
a write operation is an ILLEGAL_FUNCTION (0x01) exception.
11.5.4.4 Register 0x1103 – Watchdog Config
This register contains the configuration parameters for the watchdog. The
register is organized in bits, see following table.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
WATCHDOG_UNCONFIGURED, WATCHDOG_STOPPED and
WATCHDOG_EXPIRED. However, if the watchdog is active
(WATCHDOG_RUNNING state), this register can only be read. The response to
a write operation is an ILLEGAL_FUNCTION (0x01) exception.
Table 69: Watchdog Configuration

Bit Name/Bit Identifier Explanation
0 EXPLICIT_ Activates the Explicit Trigger mode
TRIGGER_ONLY 0* All valid Modbus requests are considered as
watchdog triggers. The only exception is the
access to the register 0x1101 (Watchdog Status).
1 Only the writing of register 0x1100 (Watchdog
Command) with the value 0x5555
(WATCHDOG_START) is considered as a
watchdog trigger. The access to the register
0x1101 (Watchdog Status) is also an exception
here.
1 TRIGGER_ON_ Activates the watchdog trigger by (read) access to
STATUS_REG register 0x1101 (Watchdog Status)
0* The reading of the watchdog status is not
considered as a watchdog trigger.
1 The reading of the watchdog status triggers the
watchdog.
2 CLOSE_ALL_TCP_ Activates the closing of all Modbus TCP connections
CONNECTIONS with the expiry of the timeout (transition to
WATCHDOG_EXPIRED state)
0 Existing Modbus TCP connections remain open.
1* All existing Modbus TCP connections are closed.
* Default setting
The individual options are activated when the specific bit, or bit combination, is
set.
11.5.5 Register 0x1104 – Watchdog Operation Mode

This register contains the value for the watchdog operation mode.
The register can be both read and written irrespective of the watchdog status.
The following operation modes are possible:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 70: Watchdog Operation Modes
0x0000 STANDARD_ “Standard Watchdog” operation mode;
WATCHDOG the watchdog must be controlled explicitly via
commands (see register 0x1100 Watchdog
Command).
0x0001 ALTERNATIVE_ “Alternative Watchdog” operation mode;
WATCHDOG the watchdog is activated immediately with a
timeout > 0 s in register 0x1102 (Watchdog
Timeout). Each trigger restarts both the running
as well as the expired watchdog. In this
operation mode the registers 0x1102
(Watchdog Timeout) and 0x1103 (Watchdog
Config) are also saved retentively with the
operation mode itself. After a device restart, the
“Alternative Watchdog” operation mode is
retained with the same configuration as before
and is therefore immediately active again when
the timeout is set.
11.5.6 Modbus Constants Registers

Registers 0x2000 … 0x2008 provide constants based on the table “WAGO
Modbus Registers”. It is possible to read all of the constants, or a consecutive
portion of them at once.
11.5.6.1 Electronic Nameplate
Registers 0x2010 to 0x2015 contain information from the electronic nameplate. It

is possible to read the entire nameplate or a consecutive portion of it all at once.
11.5.6.2 Register 0x2010 – Revision (Firmware Index)
This register provides the consecutive revision index (firmware index) for the
controller.
Example: 5 for Version 5.
11.5.6.3 Register 0x2011 – Series Designator
This register provides the designation (ID) for the WAGO series (Series Code) for
the controller.
Example: 750 for WAGO I/O SYSTEM 750.
11.5.6.4 Register 0x2012 – Device ID
This register provides the device ID (WAGO Item No.) of the controller.
Example: 8206.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.5.6.5 Register 0x2013 – Major Firmware Version
This register provides the major part for the firmware version.
11.5.6.6 Register 0x2014 – Minor Firmware Version
This register provides the minor part for the firmware version.
11.5.6.7 Register 0x2015 – MBS Version
This register provides the version of the Modbus slave library. The high byte
contains the major version number and the low byte, the minor version number.
Example:
0x010A => Major version number = 1, Minor version number = 10.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
11.6 Diagnostics
11.6.1 Diagnostics for the Modbus Master
The status of the PLC, or of the control system, can be queried by the Modbus
master by reading the WAGO specific register 0x1040 – “PLC Status” using
Modbus services FC3 (Read Holding Registers) or FC4 (Read Input Registers).
The WAGO specific register 0x1040 – “PLC Status” is explained in the Section
“PLC Status Registers”.
The status of the Modbus Watchdog can be requested using a register service
(FC3 or FC4) with a query to the WAGO specific register 0x1101 – “Watchdog
Status Register”. Information about this is given in the Section “Modbus
Watchdog”.
The Modbus service “Get Communication Event Counter” (FC11) is not

supported in the current Modbus slave Version V1.0.
11.6.2 Diagnostics for the Runtime System

Diagnostics for the Modbus slaves can be executed by integrating the CODESYS
library “BusDiag.lib” via the runtime system. The required function block,
“DiagGetBusState() indicates the status of the fieldbus (here Modbus) and is
located in this library. Details about this function block are provided both in this
document and in the online Help function for CODESYS.
11.6.3 Diagnostics for the Error Server

The Modbus slave also supports the error service implemented in the PFC and
generates diagnostic messages, which are stored permanently (in a file), or
temporarily (in the RAM) and can be displayed directly via the WBM client. The
following diagnoses are generated by the Modbus slave:
Table 71: Diagnostics for the Error Server

Diagnostics Diagnostic text Method of Explanation
ID saving
0x00090000 Modbus Slave Temporary Modbus slave library has been
library loaded successfully loaded.
0x00090001 Modbus Slave Temporary Modbus slave library has been
library closed successfully unloaded.
0x00090002 Modbus Slave Temporary Modbus slave successfully
TCP started started in TCP mode.
0x00090003 Modbus Slave Permanent Starting the Modbus slave in
TCP start failed the TCP mode failed.
0x00090004 Modbus Slave Temporary Modbus slave TCP mode
TCP terminated successfully terminated.
UDP started started in UDP mode.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
ID saving
UDP start failed UDP mode failed.
0x00090007 Modbus Slave Temporary Modbus slave UDP mode
UDP terminated successfully terminated.
RTU started started in the RTU mode.
RTU start failed RTU mode failed.
0x0009000A Modbus Slave Temporary Modbus slave RTU mode
RTU terminated successfully terminated.
0x0009000B Modbus Slave Temporary Modbus slave data exchange
data exchange started.
started by PLC
0x0009000C Modbus Slave Temporary Modbus slave data exchange
data exchange stopped.
stopped by PLC
0x0009000F Modbus Slave Permanent Monitoring time for controller
PLC watchdog (PLC) expired.
timer expired
0x00090100 Modbus Slave Permanent Modbus slave configuration
common failed.
configuration
failed.
0x00090101 Modbus Slave Temporary Modbus slave TCP
TCP configured configuration completed
successfully. successfully.
0x00090102 Modbus Slave Permanent Modbus slave TCP
TCP configuration configuration failed.
failed.
0x00090103 Modbus Slave Temporary Modbus slave UDP
UDP configured configuration completed
successfully successfully.
0x00090104 Modbus Slave Permanent Modbus slave UDP
UDP configuration configuration failed.
failed.
0x00090105 Modbus Slave Temporary Modbus slave RTU
RTU configured configuration completed
successfully. successfully.
0x00090106 Modbus Slave Permanent Modbus slave RTU
RTU configuration configuration failed.
failed
0x00090107 Port for Modbus Permanent Serial port for Modbus slave
Slave RTU RTU configuration already
operation not free. occupied.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
ID saving
0x00090108 Modbus Slave Permanent Modbus slave RTU
RTU configuration configuration for the RS-485
in RS-485 mode mode has failed.
failed.
0x00090200 Modbus Slave Temporary Modbus watchdog activated.
Watchdog
activated.
0x00090201 Modbus Slave Temporary Modbus watchdog
Watchdog deactivated.
deactivated.
0x00090202 Modbus Slave Permanent Modbus watchdog monitoring
Watchdog Timer time expired.
expired.
0x00090203 Modbus Slave has Permanent All Modbus TCP connections
terminated all terminated due to timeout.
established TCP
connections.
0x00090300 Modbus Slave: Permanent Request for system resources
obtaining system by the Modbus slave has
resource failed failed.
0x00090301 Modbus Slave: Permanent Access to system resources
processing system by the Modbus slave has
resource failed. failed.
Manual
220 Modbus – e!RUNTIME WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
12 Modbus – e!RUNTIME
12.1 Modbus Address Overview
Figure 112: Modbus Address Overview
Manual
WAGO I/O System 750 Modbus – e!RUNTIME 221
750-8214 PFC200; G2; 2ETH RS CAN
12.2 Modbus Registers

Access Description
Dec. Hex. in Words
Watchdog Configuration Registers
64,000 0xFA00 1 w Watchdog command register
64,001 0xFA01 1 rw Watchdog timeout register
64,002 0xFA02 1 ro Watchdog status register
64,003 0xFA03 1 rw Watchdog config register
Modbus TCP connection
64,004 0xFA04 1 rw
watchdog register
Status Registers
LED flash code I/O-LED
64,010 0xFA0A 1 ro
(sequence 1 of 3)
64,011 0xFA0B 1 ro
(sequence 2 of 3)
64,012 0xFA0C 1 ro
(sequence 3 of 3)
64,013 0xFA0D 1 ro PLC State : 1 = Stop; 2 = Run
Electronic Type Label
Order number, e.g.,
64,016 0xFA10 4 ro
0750810100400001
64,020 0xFA14 1 ro Firmware status
64,021 0xFA15 1 ro Hardware version
64,022 0xFA16 1 ro Firmware loader
Process Image Version
Version of the Modbus process
64,023 0xFA17 1 ro
image
Network Configuration
64,032 0xFA20 3 ro MAC-ID 1
Process Image Registers
Number of input registers, analog
64,064 0xFA40 1 ro and digital (total size of the
Modbus IN space) 0x7D00
Number of input registers, analog
64,065 0xFA41 1 ro
0x7D00
Number of input registers, digital
64,066 0xFA42 1 ro
0x8000
Number of output registers,
64,067 0xFA43 1 ro analog and digital (total size of
the Modbus OUT space) 0x7D00
64,068 0xFA44 1 ro
analog 0x7D00
64,069 0xFA45 1 ro
digital 0x8000
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Access Description
Dec. Hex. in Words
Constants Registers
64,160 0xFAA0 1 ro Constant 0x1234
64,161 0xFAA1 1 ro Constant 0xAAAA
64,162 0xFAA2 1 ro Constant 0x5555
64,250 0xFAFA 1 ro Live register
The WAGO Modbus registers are described in more details in the following
sections.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.1 Modbus Watchdog

The Modbus watchdog monitors in the Modbus slave the ongoing Modbus
communication with the Modbus master. All valid Modbus requests of a Modbus
master from all the services supported by the Modbus slave are trigger events
(see chapter “Modbus Mapping”). Exceptions here are the Explicit Trigger mode
and the access to the register 0xFA02 (Watchdog Status), which can be
configured via the register 0xFA03 (Watchdog Config).
The “Watchdog Timeout” response is initiated if no trigger occurs within the

timeout set in the register 0xFA01 (Watchdog Timeout) with the watchdog
running. The closing of all Modbus TCP connections can be configured as a
response, see register 0xFA03 (Watchdog Config).
The Modbus watchdog supports two different operation modes

ADVANCED_WATCHDOG and SIMPLE_WATCHDOG. The operation mode can
be selected via Bit 7 in the register 0xFA03 (Watchdog Config).
The following diagrams show the possible states of the Modbus watchdog and
status transitions for the particular operation mode.
Figure 113: State Diagram, ADVANCED_WATCHDOG Operation Mode
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 114: State Diagram, SIMPLE_WATCHDOG Operation Mode
The state diagram for the SIMPLE_WATCHDOG operation mode shows that the
watchdog is always active as soon as a timeout > 0 is set in the register 0xFA01
(Watchdog Timeout). The writing of commands in the register 0xFA00 (Watchdog
Command) is restricted in this operation mode. Only the WATCHDOG_START
command is permitted as a possible trigger. The only possibility to deactivate and
stop the watchdog in operation mode SIMPLE_WATCHDOG, is the switching
back to the operation mode ADVANCED_WATCHDOG.
The following diagram shows the possible state transitions when operation
modes are switched.
Figure 115: State Diagram, Switching Operation Modes
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.1.1 Register 0xFA00 – Watchdog Command
This register receives commands for the Modbus watchdog. It cannot be read,
i.e. it is not possible to read out the last command written.
The following commands are accepted depending on watchdog status:
Table 73: Watchdog Commands

0x5555 WATCHDOG_ Starts the configured watchdog;
START in the WATCHDOG_UNCONFIGURED state if
no timeout is configured, the response is an
ILLEGAL_DATA_VALUE (0x03) exception. The
same exception is returned even if the
watchdog has expired
(WATCHDOG_EXPIRED) in the ADVANCED_
WATCHDOG operation mode. The watchdog
must in this case be reset first with the
command WATCHDOG_RESET to the
cases the watchdog is restarted and the
WATCHDOG_RUNNING state is set.
0x55AA WATCHDOG_ Stops the running watchdog;
STOP in the WATCHDOG_UNCONFIGURED state,
the response is an ILLEGAL_DATA_
VALUE (0x03) exception if no timeout time is
set. The same exception is returned even if the
watchdog has expired
(WATCHDOG_EXPIRED) in the ADVANCED_
WATCHDOG operation mode. The watchdog
must in this case be reset first with the
command WATCHDOG_RESET to the
WATCHDOG_STOPPED state. In the SIMPLE_
WATCHDOG operation mode the response is
an ILLEGAL_DATA_VALUE (0x03) exception.
The command is not generally permitted in this
operation mode. In all other cases, the
watchdog is stopped and the
WATCHDOG_STOPPED state is set. In the
WATCHDOG_STOPPED state a stop
command received several times in a row does
not have any impact on the behavior of the
watchdog and is therefore not acknowledged
with an error response.
0xAAAA WATCHDOG_ Resets the expired watchdog;
RESET in the WATCHDOG_EXPIRED state the
ADVANCED_WATCHDOG operation mode
resets the watchdog. The watchdog is then in
the WATCHDOG_STOPPED state. In all other
cases the response is an ILLEGAL_
DATA_VALUE (0x03) exception.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.1.2 Register 0xFA01 – Watchdog Timeout
This register contains the value for the watchdog timeout. The step width is 1 ms
and the maximum value is 65535 (corresponds to 65.535 s). The default value is
0. In this case the watchdog cannot be started and will have the
WATCHDOG_UNCONFIGURED state.

WATCHDOG_UNCONFIGURED and WATCHDOG_STOPPED. However, if the
watchdog is active or expired (WATCHDOG_RUNNING and
WATCHDOG_EXPIRED state), only read access to this register is possible. The
response to a write operation is an ILLEGAL_FUNCTION (0x01) exception.
12.2.1.3 Register 0xFA02 – Watchdog Status
This register provides the current state of the Modbus watchdog.

The following states are possible:
Table 74: Watchdog Status

0xFFFF WATCHDOG_ The Modbus watchdog is not configured, i.e.,
UNCONFIGURED register 0xFA01 (Watchdog Timeout) contains
the value 0. Only the setting of a timeout > 0 s
can close this state.
0x0000 WATCHDOG_ The Modbus watchdog is configured, the
STOPPED register 0xFA01 (Watchdog Timeout) contains a
value >0. In the ADVANCED_WATCHDOG
operation mode, the watchdog can be activated
in this state with the WATCHDOG_START
command. In the SIMPLE_WATCHDOG
operation mode, this state cannot be accessed
since the watchdog is automatically started.
0x0001 WATCHDOG_ The Modbus watchdog is active, i.e. configured
RUNNING and started. The set timeout has not yet
expired.
0x0002 WATCHDOG_ The timeout set in register 0xFA01 (Watchdog
EXPIRED Timeout) has expired. In the
ADVANCED_WATCHDOG operation mode, the
watchdog in this state must be reset to the
WATCHDOG_STOPPED state with the
WATCHDOG_RESET command. In the
SIMPLE_WATCHDOG operation mode, the
watchdog is automatically restarted with the
next trigger.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.1.4 Register 0xFA03 – Watchdog Config
This register contains the configuration parameters for the watchdog. The
register is organized in bits, see following table.
The register can be read and written irrespective of the watchdog state in the
SIMPLE_WATCHDOG operation mode.
However, in the ADVANCED_WATCHDOG operation mode, the register can only
be read and written in the WATCHDOG_UNCONFIGURED and
WATCHDOG_STOPPED states.
If the watchdog is active (WATCHDOG_RUNNING or WATCHDOG_EXPIRED
state), only a read access is permissible. The response to a write request in this
case is an ILLEGAL_FUNCTION (0x01) exception.
Table 75: Watchdog Configuration

Bit Name/Bit Identifier Explanation
0 EXPLICIT_ Activates the Explicit Trigger mode
TRIGGER_ONLY 0* All valid Modbus requests are considered as
watchdog triggers. Access to register 0xFA02
(Watchdog Status) is the only exception.
1 Only the writing of register 0xFA00 (Watchdog
Command) with the value 0x5555
(WATCHDOG_START) is considered as the
watchdog trigger. The exception is also here the
access to the register 0xFA02 (Watchdog
Status).
1 TRIGGER_ON_ Activates the watchdog trigger by (read)
STATUS_REG access to register 0xFA02 (Watchdog Status)
0* The reading of the watchdog status is not
considered as a watchdog trigger.
1 The reading of the watchdog status triggers the
watchdog.
2 CLOSE_ALL_TCP_ Activates the closing of all Modbus TCP connections
CONNECTIONS with the expiry of the timeout (transition to
WATCHDOG_EXPIRED state)
0 Existing Modbus TCP connections remain open.
1* All existing Modbus TCP connections are closed.
7 SELECT_ Determines the watchdog operation mode
ADVANCED_ 0* Advanced Mode: The watchdog must be
SIMPLE_MODE controlled explicitly via commands (see register
0xFA00 Watchdog Command).
1 Simple Mode: The watchdog is activated directly
with a timeout > 0 in register 0xFA01 (Watchdog
Timeout). Each trigger restarts the running as
well as the expired watchdog. The watchdog can
only be stopped by switching to Advanced mode.
*Default setting
The individual options are activated if the relevant bit or bit combination is set.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.1.5 Modbus TCP Connection Watchdog Register
The 0xFA04 register contains the time for the Modbus TCP connection
watchdog. Time base is 10 ms. This enables the time to be set up to 655350 ms.
If the register contains a value > 0 s when a new TCP connection from a Modbus
master is accepted, the watchdog for this connection is started. Later changes to
the register have no effect on the monitoring of existing connections. If the
watchdog is started and no telegram is received from the connected Modbus
master within the set time, this connection is closed from one side with a reset.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.2 Status Registers

12.2.2.1 PLC Status Register
The register 0xFA0D supplies the current status of the controller.

Possible values:
1 = PLC Stop - PLC is in STOP status.

2 = PLC Run - PLC is in RUN status
12.2.3 Electronic Nameplate

Registers 0xFA10–0xFA17 contain information from the electronic nameplate. It
is possible to read the entire nameplate or a consecutive portion of it all at once.
12.2.3.1 Order Number
The registers 0xFA10–0xFA13 contain the WAGO order number of the controller.
Example: 0750-8202/0025-0001.
0xFA10 = 0750,
0xFA11 = 8202,
0xFA12 = 0025,
0xFA13 = 0001
12.2.3.2 Firmware Version
The register 0xFA14 contains the firmware version of the controller.
12.2.3.3 Hardware Version
The register 0xFA15 contains the hardware version of the controller.
12.2.3.4 Firmware Loader/Boot Loader
The register 0xFA16 contains the firmware loader/boot loader version of the
controller.
12.2.4 Modbus Process Image Version

The register 0xFA17 contains the Modbus process image version of the
controller.
12.2.5 Modbus Process Image Registers

The registers 0xFA40–0xFA45 contain size information for the process image
spaces of the controller for bit and register accesses.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.2.6 Constant Registers

Registers 0xFAA0 … 0xFAA2 provide constants based on the “WAGO Modbus
Registers” table. It is possible to read all of the constants, or a consecutive
portion of them at once.
0xFAA0 = 0x1234,
0xFAA1 = 0xAAAA,
0xFAA2 = 0x5555
12.2.7 Live Register

The register 0xFAFA can only be read and contains a counter that is incremented
with each cycle of a task of the runtime environment with read and write access
to the Modbus process data.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
12.3 Estimating the Modbus Master CPU Load

Due to the real-time characteristics of the Linux kernel used, many data points
can generate many context changes.
For a one-off update (transmitting and receiving of a function code), a CPU time
of approx. 800 µs can be assumed.
The CPU load (cpu_load) in percent can be estimated from the cycle time (t_z)
for a query with the following rule of thumb:
cpu_load = 800 µs / t_z * 100
A cycle time of 100 ms thus results in a CPU load of 0.8%.

A maximum load of approx. 20% can be generated per connection, as this is
limited by the network protocol. To minimize the CPU load:
- The cycle time must be as high as possible.
- As many data points as possible must be combined in a query.
- The minimum query interval can be increased (default value: 0 ms).
Manual
232 CANopen Master and Slave WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
13 CANopen Master and Slave

</dg_
Based on IEC 61131-3 programming, data processing occurs on site in the

controller. The process results can be output directly to the actuators, or
transmitted via the bus.
Process data is exchanged with PDOs and SDOs. The controller supports 512
TX PDOs and 512 RX PDOs and SDOs to send process data via the CANopen
fieldbus.
In the local process image, a range of 4000 bytes serves as each input and
output range for data exchange via the CANopen interface. This range is situated
between the addresses 6000 to 9999. Direct access to the I/O modules via the
fieldbus is not provided.
All entries of the object directory can be mapped as required to the RX PDOs and
TX PDOs. The complete input and output process image can be transmitted via
SDOs.
13.1 Object Directory

All communication objects and all user objects are compiled in the object
directory. The figure below provides a rough overview of this:
Table 76: Overview of Addresses in the Object Directory

Index Range Use
0000 Not used
0001-009F Data types
00A0-0FFF Reserved (addresses used for other services)
1000-1FFF Communication profile
2000-5FFF Vendor-specific range
6000-9FFF Up to eight standardized device profiles
A000-AFFF Process images from IEC 61131 devices
B000-BFFF Process images from CANopen gateways acc. CiA 302-7
C000-FFFF Reserved
The objects, which are made available by the controller, are described below.
Manual
WAGO I/O System 750 CANopen Master and Slave 233
750-8214 PFC200; G2; 2ETH RS CAN
13.2 Communications Profile

0x1000 Device Type
The stack responds on the bus as the DS-405 device (IEC 61131-3
programmable device), regardless of being configured as the master or slave. As
direct access to the I/O modules via the bus is prohibited, the bits for information
about inputs and outputs are 0.
Entry 0x000191 = DS 405 for master and slave
0x1001 Error Register
This entry contains an 8-bit item of information about the error status. At present,
bit 4 is used specifically for communication and bit 5 for the device profile. Bit 0 is
set for each error.
0x1003 Pre-defined Error Field
This entry contains the list of accumulated errors which were signaled in error
register 0x1001. Sub-index 0 contains the number of entries. If a new error
occurs, it is added to sub-index 1 and all existing errors are moved down one
sub-index. A maximum of 20 error entries is supported. If more than 20 errors
occur, the error at sub-index 20 is overwritten. By writing a “0” into sub-index 0,
the complete error memory is deleted.
Standard values: 0 in all entries
0x1005 COB IB Sync
This objects defines the COB ID for the synchronization message.
Default: 0x80
0x1006 Communication Cycle Period
The duration of the synchronization cycle given in µs, or 0 for cyclic

synchronization. Internal resolution is 1 ms. If this value is 0, SYNC monitoring
does not occur.
Default: 0
0x1008 Manufacturer Device Name
This object specifies the device name.
Entry: Item No. for the PFC200, e.g., “750-8206”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
0x1009 Manufacturer Hardware Version
Entry: “V 1.0” or higher
0x100A Manufacturer Software Version
Entry: “V 1.00” or higher
0x100C Node Guarding Time
The object specifies the “Guarding Time” in milliseconds. An NMT master

requests the state of the NMT slave in a cyclical manner. The time between two
requests is the “Guarding Time.”
Default: 0 (Node guarding disabled)
0x100D Life Time Factor
The “Life Time Factor” is part of the node guarding protocol. The NMT slave
checks whether it was queried within the node lifetime (guarding time multiplied
by the lifetime factor). If not, the slave must assume that the NMT master is no
longer in normal operation; it then initiates a “life guarding event”.
Default: 0 (Node guarding off)
0x1012h COB-ID Time Stamp Object
The time stamp object enables every device's clock on the bus to be
synchronized. The ID for this object is indicated here. Although the
synchronization signal is not evaluated by the runtime, it may be used with library
functions.
Default: 0x100 (Time Stamp Consumer)
0x1014h Emergency COB ID
An emergency message is transmitted in the event of CANopen device errors.

The ID for this object is indicated here.
Default: 0x80 + Device ID
0x1015h Emergency Inhibit Time
This object specifies the minimum time that must elapse before another
emergency object is sent. An entry equal to zero disables delayed sending. One
time unit amounts to 100µs.
Default: 0
Manual
750-8214 PFC200; G2; 2ETH RS CAN
0x1016h Consumer Heartbeat Time
This entry can be used for monitoring of other devices on the bus. A check is
made to determine whether each module defined in this object has generated a
heartbeat within the set time. If the set time has been exceeded, a heartbeat
event is triggered. The "Heartbeat Time" is entered in milliseconds. If the time is
0, monitoring is deactivated. The number of devices to be monitored is entered in
index 0, the heartbeat time is entered in ms in the bottom 16 bits and the ID of
the bus device in the 8 bits above that.
Default:
Index 0: 0 (currently still 127 = Number of possible entries)
All other entries are 0 (this function is not yet supported by the CAN master in
Firmware 1.0).
0x1017h Producer Heartbeat Time
This object defines the time (in milliseconds) between two transmitted heartbeat
messages. No heartbeat is sent if the time is set to 0.
Default: 0
0x1200, 0x1201 Server SDO Parameter Channels
The communication parameters for an SDO as the server are entered here. Two
server SDO channels are supported.
0x1280 … 0x128E Client SDO Parameter Channels
The communication parameters for an SDO transfer as the client are entered
here. 16 client SDO channels are supported.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
0x1018h Identity
This object specifies the device being used. The manufacturer ID contains a
unique number for each vendor. WAGO has been assigned an ID of 33. The
device description reflects the family of products used.
The Rev. No. contains a specific CANopen behavior. The Major Rev. No.
contains the CANopen functionality. If the functionality is changed, the Major
Rev. No. is increased. You can use the Minor Rev. No. to distinguish between
different versions with the same CANopen behavior.
Sub-index 0 No. of entries: 4
Sub-index 1 vendor ID: 33
Sub-index 2 product_code: e.g., 8206 for 750-8206
Sub-index 3 revision_number: 0x00010001 or higher
Sub-index 4 serial_number: corresponds to the last 4 bytes of the MAC

address.
0x1029h Error Behavior
This object defines how the slave responds in the event of an error.
Sub-index 0 No. of entries: 1
Sub-Index 1 Communication Error:
1 No change (Standard)
0 Change from operational to preoperational
2 Change to stop
0x1F51 Program Control
The status of the PLC can be read out using this object. Writing is prohibited.
Entries: 0 = Stop 1 = Run 2 = Reset 3 = Clear
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.2.1 Master Configuration

These objects are only available at the bus end when the master has been
configured.
0x102A NMT Inhibit Time
This object indicates the minimum time that must elapse before another NMT
telegram is sent. An entry equal to zero deactivates delayed sending. One unit of
time is 100 µs.
Default: 0
0x1F80 NMT Start-up
This object contains the configuration bits for the master status. If automatic
startup is deactivated, the master can be started by writing of 0x1F to this object.
0x1F81 … 0x1F8A Slave Configuration
The configured slaves are entered in these lists. All of the entries are checked
when the master is started and transferred to the slaves.
0x1F81 NMT Slave-Assignment
Subindex 0: 128 = Number of possible entries
Subindex 1 … 128: Bit 0: Slave present
Bit 2: Slave required for start
Bit 3: Slave reset performed on start
Bit 8 … 15: Guard Retry Factor
Bit 16 … 31: Guard Time
Subindex 128: Total network (write only)
0x1F82 Request-NMT
Sub-Index 0: 127 = Number of possible entries
Sub-Index = Master Node ID NMT state of the master
0x1F84 Device Type Identification
Sub-Index 1 … 127: Slave device type
Manual
750-8214 PFC200; G2; 2ETH RS CAN
0x1F85 Vendor Identification
Sub-Index 1 … 127: Slave device type (not used by default)
0x1F86 Product Code
0x1F87 Revision number
0x1F88 Serial Number
0x1F89 Boot Time
Time in ms between the start of slaves and operational readiness of all slaves.
Default: 0 = deactivated
0x1F8A Restore Configuration
Sub-Index 1 … 127: Bit 0 = 1 Send restore configuration to slave on start
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3 Data Exchange

Process data exchange occurs via the communication objects with the CANopen
fieldbus controller.
Each object consists of a CAN telegram with a maximum of 8 bytes process data
and a COB (Communication Object Identifier) ID that is unique within the
network.
These communication objects transmit data, trigger events, signal error statuses,
etc.
The parameters required for the communication objects, as well as CANopen

device parameters and data are stored in an object directory.
13.3.1 Controller Communication Objects

The PFC200 supports the following communication objects:
512 Tx-PDOs for process data exchange from input data of the fieldbus node
512 Rx-PDOs for process data exchange from output data of the fieldbus node
Synchronization objects (SYNC) for network synchronization
Emergency objects (EMCY)
Network management objects
- Module Control Protocols
- Error Control Protocols
- Boot-up Protocol
13.3.2 Fieldbus-Specific Addressing

The CODESYS variable for the CAN bus (%QB6000 … %QB9999 and %IB6000
… %IB9999) are mapped to an object directory after configuring the CAN
interface as a master or slave (initialization). A CANopen fieldbus device uses the
16-bit indices and 8-bit sub-indices of the object directory to address data via
PDOs or SDOs and to access the data. The position of the data in the process
image is therefore not directly significant for the CANopen user at the fieldbus
end.
The variables entered into the object directory are distinguished by data type
(Integer8, Unsigned8, Boolean, Integer16, etc.) and by input/output. Access via
PDOs can be either for reading or writing. Direct access via SDO can be read-
only.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
As CANopen does not transfer data by bits, the variable data is combined from a
Boolean data type to bytes and assigned to the corresponding index; Boolean
input variable data is assigned to index 0xA080, Boolean output variable data to
index 0xA500.
Variable data that has a data width of 1 byte or more is assigned to the
corresponding indices in a similar manner.
Observe the direction of data flow!

The IEC 61131-3 input variables are defined from the perspective of the CAN
bus. These are output variables from the perspective of the PFC. Accordingly,
the IEC 61131-3 output variables are input variables for the PFC.
This table provides an overview of the indices of “IEC 61131-3” variables.
Table 77: Indexing of “IEC 61131-3” Variable Data in the Object Directory
IEC 61131-3 Output IEC 61131-3 Input Variables
Data Type Variables
Index
Integer8 0xA000 0xA480
Unsigned8 0xA040 0xA4C0
Boolean 0xA080 0xA500
Integer16 0xA0C0 0xA540
Unsigned16 0xA100 0xA580
Integer24 0xA140 0xA5C0
Float32 0xA240 0xA6C0
Integer48 0xA340 0xA7C0
Integer64 0xA400 0xA880
Unsigned64 0xA440 0xA8C0
Using the associated indices for data types with a data width of 1 byte (Integer8,
Unsigned8 and Boolean), read-only byte-by-byte access is possible from the
fieldbus to data in the controller memory.
The sub-index is utilized to select a specific byte.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
In contrast, when the indices for larger data blocks are used, several bytes can
be accessed simultaneously.
For example, the described PFC output variable data can be accessed in a word-
by-word manner using the index for Integer16 (0xA0C0) or for Unsigned16
(0xA100), three bytes can be accessed using index 0xA140 for Integer24, etc.
Example:
The first three bytes of the PFC output data for the data type integer or unsigned
are accessed from the fieldbus:
Table 78: Fieldbus Access to PFC Output Data

Reading with Index Sub-
Access PFC Output Data
(Integer / Unsigned) Index
By byte Byte 6000 (0xA000 / 0xA040) 1
(with Integer8 / Byte 6001 (0xA000 / 0xA040) 2
Unsigned8) Byte 6002 (0xA000 / 0xA040) 3
By word Word 3000 (Byte 6000/6001) (0xA0C0 / 0xA100) 1
(with Integer16 /
Word 3001 (Byte 6002/6003) (0xA0C0 / 0xA100) 2
Unsigned16)
3 bytes Bytes 6000 … 6002 (0xA140 / 0xA180) 1
(with Integer24 /
Unsigned24)
The following tables give an overview of addressing data with different data
widths.
In this case, the corresponding indexing is assigned to the memory space for
fieldbus variables (byte 6000 to byte 9999) as a function of the data width.
The indexing indicated in the tables continues up to the respective maximum

index and sub-index.
Observe the direction of data flow!

The PFC output variables are defined from the perspective of the controller; from
the perspective of the CAN fieldbus these are input variables. Accordingly, the
PFC input variables for IEC 61131-3 access are output variables for the fieldbus.
Thus: IEC 61131-3 input variable = PFC output variable
PFC input variable = IEC 61131-3 input variable.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Figure 116: Correlation Between “IEC 61131-3” Variables and PFC Variables
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.3 Examples for the Definition of PFC Fieldbus Variables

The examples below show the allocation of several definitions for PFC variables
with different data types to the associated object directory entries.
13.3.3.1 CODESYS Access to PFC Variables
Table 79: Examples for CODESYS Access to PFC Variables

Data Type PFC Input Variables PFC Output Variables
of PFC Definition based on Index/sub- Definition based on Index/sub-
Variables IEC 61131-3 index IEC 61131-3 index
Unsigned8 InByte0 AT 0xA4C0/1 OutByte0 AT 0xA040 /1
%IB6000: BYTE; %QB6000: BYTE;
InByte0 AT 0xA4C0/2 OutByte0 AT 0xA040 /2
%IB6001: BYTE; %QB6001: BYTE;
Integer16 InInt0 AT 0xA540 /1 OutInt0 AT 0xA0C0/1
%IW3000: INT; %QW3000: INT;
InInt1 AT 0xA540 /2 OutInt1 AT 0xA0C0/2
%IW3001: INT; %QW3001: INT;
Unsigned16 InWord0 AT 0xA580 /1 OutWord0 AT 0xA100 /1
%IW3000: WORD; %QW3000:
WORD;
InWord0 AT 0xA580 /2 OutWord0 AT 0xA100 /2
%IW3001: WORD; %QW3001:
WORD;
Unsigned32 InDWord0 AT 0xA680 /1 OutDWord0 AT 0xA200 /1
%ID1500: %QD1500:
DWORD; DWORD;
InDWord0 AT 0xA680 /2 OutDWord0 AT 0xA200 /2
%ID1501: %QD1501:
DWORD; DWORD;
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.3.2 Maximum Indices
The maximum indices and sub-indices are yielded from the memory size of the
fieldbus controller at 4000 bytes and the corresponding data width for the data
types.
The table below provides an overview of the maximum indices and sub-indices of
the IEC 61131-3 variables.
Table 80: Maximum Indices and Sub-Indices for “IEC 61131-3” Variables
IEC 61131-3 Input Variables IEC 61131-3 Output Variables
Data Type
Max. index Max. sub-index Max. index Max. sub-index
Integer8 0xA00F 0xFF 0xA487 0xFF
Unsigned8 0xA04F 0xFF 0xA4C7 0xFF
Boolean 0xA08F 0xFF 0xA507 0xFF
Integer16 0xA0C7 0xFF 0xA543 0xFF
Unsigned16 0xA107 0xFF 0xA583 0xFF
Integer24 0xA145 0x55 0xA5C0 0x55
Unsigned24 0xA185 0x55 0xA600 0x55
Integer32 0xA1C3 0xFF 0xA643 0xFF
Unsigned32 0xA203 0xFF 0xA683 0xFF
Float32 0xA243 0xFF 0xA6C3 0xFF
Integer40 0xA2C3 0x33 0xA743 0x33
Unsigned48 0xA302 0xAA 0xA780 0xAA
Integer48 0xA342 0xAA 0xA7C0 0xAA
Integer56 0xA3C2 0x49 0xA842 0x49
Integer64 0xA401 0xFF 0xA880 0xFF
Unsigned64 0xA441 0xFF 0xA8C0 0xFF
Example:
514 bytes of output variables are addressed by word by the data type
Unsigned16.
Addressing of 257 data words then occurs with:
- Index 0xA580, sub-index 1 to 255

- Index 0xA581, sub-index 1 and 2.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 81: Example of “IEC 61131-3” Output Variables
Index Sub-Index Contents Description
0xA580 1 D1 *) 1st output variable block
2 D2 *) 2nd output variable block
... ... ...
*)
255 D255 255th output variable block
0xA581 1 D256 *) 256th output variable block
2 D257 *) 257th output variable block
*)
D1 = Data word output variable 1, D255 = Data word output variable 255, etc.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
13.3.4 CANopen Master Control Configuration
Note Calling up the addresses or the symbolic name of the inputs and
outputs
Addresses or symbolic names of the inputs and outputs have to be called
up explicitly, otherwise the process image is not updated. Alternatively, you
can also create an array of max. 240 bytes at the memory addresses
IB%6000 or QB%6000. This array has to be called up in the PLC program.
An application must be configured in CODESYS before it can access the

connected CAN network.
13.3.4.1 Selecting the Master
To add the CANopen Master to the control configuration, right-click “COS

unused[Slot]” and select “Replace element -> CANopen Master”.
Figure 117: Adding the CANopen Master
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.4.2 Setting the Master Parameters
No input should be made on the Basic parameters tab.
Figure 118: Basic Parameters Tab (Master)
Table 82: Description of Basic Parameters (Master)

Module id
Node id
Input address Parameters that use the runtime system CODESYS.
Output address
Diagnostic address
Comment Input field for comments.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Normally, you must only check the baud rate on the CAN parameters tab.
Figure 119: CAN Parameters Tab (Master)
Table 83: Description of the CAN Parameters (Master)

Baud rate Specify the baud rate that will apply to the transfer
on the CAN bus (default setting: 125000 baud).
Com. Cycle Period (µsec) Specify the time interval (in µsec) that the
synchronization notification will be sent by the
controller. Smallest time interval: 1000 µsec
Sync. Window Length Not currently implemented.
(µsec)
Sync. COB-ID You can enable or disable sending of
synchronization notification by the controller.
Default setting: COB ID 128 (0x80).
Node ID Station address (node ID) of the controller on the
CAN bus.
Start automatically When you mark this check box, the controller
automatically sets the CAN master and slaves to the
“Operational” based on the defined parameters.
If you do not mark this check box, starting can be
performed using the CIA405NMT library command.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 83: Description of the CAN Parameters (Master)
Support ... DSP 301 If you mark this check box, modular CAN slaves as
well as additional extensions adhering to the
DSP301 V3.01 and DSP 306 standards are
supported by the control configuration.
Heartbeat Master If the “Heartbeat Generation” option is enabled, the
CAN device transmits heartbeats in ms intervals
specified in “Heartbeat Producer Time”. Heartbeat
consumption is not currently implemented.
In the “Module parameters” tab you can define the start and stop behavior of the
master.
Figure 120: Module Parameters Tab (Master)
Table 84: Description of the Module Parameters (Master)

Scan all node IDs on boot All permissible node IDs are scanned at the start if
this option is set. EMC messages are received from
this node if a node is present.
Goto Preoperational on If this option is set, the master switches to the
PLC stop “Operational” state if the CODESYS runtime is in the
“Run” state.
If the runtime switches to the “Stop” state, the
master switches to the “Preoperational” state.
13.3.4.3 Adding Slaves
To select one (or several) CANopen slaves, right-click on the CANopen master
and select “Attach subelements”. In this example, the 750-337 was selected as
the slave.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
EDS Files
The EDS files for current components of the WAGO-I/O-SYSTEM are integrated
in the target files for the controller. The associated EDS files are required for
incorporation of non-WAGO devices. For this, click “Tools” > “Add configuration
file” in the menu bar.
Only use the supplied EDS files for CODESYS 2.3!

The EDS files for the PFC200 CANopen slave, which are supplied in the target
files for the controller, can only be used if the CODESYS 2.3 runtime system is
used on the controller!
Figure 121: Adding a CANopen Slave
Manual
750-8214 PFC200; G2; 2ETH RS CAN
No input must be made on the Basic parameters tab.
Figure 122: Basic Parameters Tab (Slave)
Table 85: Description of Basic Parameters (Slave)

Module ID Recognition of the slave.
Node ID Node number of the slave used in the CODESYS
runtime environment.
Input address Starting address for the input data:
The address space always begins at %IB 6000 and
is assigned automatically.
Output address Starting address for the output data:
The address space always begins at %QB 6000 and
is assigned automatically.
Diagnostic address Memory area for internal diagnostic processing.
Comment Input field for comments.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Normally, you must only check the Node ID on the CAN parameters tab.
Figure 123: CAN Parameters Tab (Slave)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 86: Description of the CAN Parameters (Slave)
General
Node ID The node ID (1–126) is the station address under
which the controller communicates with the slave on
the CAN network.
Write DCF Currently not implemented.
Generate all SDOs When this check box is marked, SDOs are
generated for all objects in the EDS file.
In addition, the corresponding options must be
activated. If the node-guarding objects are to be
written, for example, the checkbox for the “Node-
Guarding” option must also be marked.
If the checkbox is not marked, SDOs are only
generated for the objects in which the default values
deviate from the EDS file.
Reset node If you activate this option, the slave is reset by the
controller (receives a “reset node”) before the
configuration is sent to the slave.
This function is not currently implemented.
Mapping SDOs Activate or deactivate each of the three SDO ranges
of the slave configuration here.
Comm SDOs Mapping SDOs:
Objects 0x1600 … 0x1620
Objects 0x1A00 … 0x1A20
Comm SDOs:
Basic SDOs Objects 0x1400 … 0c1420
Objects 0x1800 … 0x1820
Basic SDOs:
Objects 0x100C … 0x1017
Node Guard
Node-Guarding With Node-Guarding enabled, the slave monitors the
PFC for any potential disruption of fieldbus
communication.
Guard COB ID Default setting: 0x700 + Node ID.
Guard Time (ms) Under“Guard Time” specify the interval at which the
PFC expects to receive “Confirmation” from the
slave.
Lifetime factor In the field “Lifetime factor” (>= 2) specify the
multiplier for the “Guard time”.
If the time yielded from “Guard time” x "Lifetime
factor” “Node lifetime”) has expired, the slave is
brought into the predefined state.
This function is deactivated by “0”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 86: Description of the CAN Parameters (Slave)
Heartbeat Settings
Activate heartbeat If the “Heartbeat Generation” option is enabled, the
generation CAN device transmits heartbeats in ms intervals
Heartbeat producer time specified in “Heartbeat Producer Time”.
(ms) This function is disabled by “0”.
Activate heartbeat If the “Heartbeat Consumption” option is enabled,

consumption the CAN device monitors the heartbeat of the
master. Only “Heartbeat” or “Node-Guarding” can be
used for monitoring.
Emergency Telegram
Emergency If you mark this checkbox, the slave sends error and
status messages that are stored as emergency
messages to the diagnostic address in the flag area.
These error and status messages are read out using
“BusDiag.lib”.
If you do not mark this checkbox, SDO 0x1014 is not

transmitted to the slave. The default setting for the
slave would then still apply.
COB-ID Default: Node ID + 0x80
Communication Cycle
Cycle
These functions are currently not implemented.
Period (µsec)
Click [Info …] to display the parameters “FileInfo” and “DeviceInfo” from the EDS
file.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
You can now select the installed input and output modules in the CAN module
selection tab. In the example shown here, one 8-bit input and output module
each.
Figure 124: CAN Module Selection Tab
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.4.4 Configuring the Slave PDOs
Now, configure the receiving PDOs for the slave (output from the perspective of
the controller) and the send PDOs. The PDOs for the module have already been
created by the Configurator. The eight bits have been placed in the first PDO.
Figure 125: PDO Mapping Tab
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 87: Receiving and Sending Description for PDO Mapping
Insert PDO Depending on the I/O modules selected for the
CANopen slave, the corresponding CANopen
objects appear on the “Receive PDO Mapping”
(PFC  slave) and “Send PDO Mapping” (slave 
PFC) tabs. Using these tabs, you can change the
“Default Mapping” described in the EDS file.
Click on the button [Add PDO] to match the PDOs

to the I/O module topology. The PDO properties
window opens for defining certain properties for the
PDO. More information about this is provided under
“Properties”.
In order to assign one of the PDOs an object from

the left window, mark both the corresponding object
and the corresponding PDO and then click [>>].
Then the object will be added below the PDOs in the
right window. The first 64 digital and the first 12
analog inputs and outputs are then assigned
automatically to the PDOs 1–4.
Remove Click [Remove] to remove the item currently marked
in the right window from the configuration.
Features A dialog box with information about the PDO
properties opens (see next page).
Further configuration of the PDOs is also possible using the “Properties” button.
Figure 126: PDO Properties Window
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 88: Description of the PDO Properties Window
COB-ID CAN Identifier
Inhibit Time (* 100 µs) Here, specify the time span of a PDO to reduce
communication incidence; this is the time that must
pass before it can be sent again. This value is not
used for synchronous transmission. This value is
insignificant for a receive PDO.
Transmission Type Here, select the transmission mode for the PDO:
acyclic-synchronous:
(transmission type 0)
The PDO is transmitted synchronously, but not
periodically. For receive PDOs, the transmission
types 0–240 are handled the same way.
cyclic-synchronous:
(transmission type 1–240)
The PDO is transmitted synchronously, whereby
“Number of Syncs” specifies the number of
synchronization messages that lie between two
transmissions of the PDO. For receive PDOs, the
transmission types 0–240 are handled the same
way.
synchronous - only RTR:

The PDO is updated after a synchronization
message, but not sent. It is only transmitted with an
explicit inquiry “Remote Transmission Request” (not
implemented).
asynchronous - only RTR:

The PDO is only updated and transmitted with an
explicit inquiry “Remote Transmission Request” (not
implemented).
asynchronous-vendor-specific:
The PDO is only transmitted after particular events.
asynchronous-device-profile-specific:
The PDO is only transmitted after specific events.
Number of Syncs Depending on the “transmission type,” this field can
be edited to enter the number of synchronization
messages from 1–240. This value is insignificant for
a receive PDO.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 88: Description of the PDO Properties Window
Event Time Depending on the “transmission type”, enter the time
span (in ms) that should elapse between two
transmissions of the PDO. This value is insignificant
for a receive PDO.
13.3.4.5 Configuring the Service Data Objects
Service data objects can also be configured in addition to the configuration

performed on the previous tabs.
Figure 127: Service Data Objects Tab
All objects of the EDS file are listed here, which range from index 0x2000 to
0x9FFF and can be described.
For each object, the index, name, value, type and default are specified.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The value of the objects can be changed. To do this, mark the field in question in
the “Value” column and overwrite the value with your input, then press [Enter].
On initialization of the CAN bus, the set values will be transmitted to the slaves
as SDOs.
An example here is the activation of sending PDOs on a change in analog

values, which is normally deactivated:
Figure 128: Adapting SDOs
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The starting parameters for the slave can now be set on the “Module parameters”
tab.
Figure 129: “Module Parameters” Tab (Slave)
Table 89: Description of the Module Parameters (Slave)

EnableCANopenStartup Yes (default):
During the boot-up phase of the CANopen network,
all basic SDO frames are sent to the selected
CANopen slave.
No:
With this setting, no SDO frames are sent to the
CANopen slave.
EnableNMTStartNode Yes (default):
During the boot-up phase of the CANopen network,
the NMT command “Start remote node” is sent to
the selected CANopen slave (communication
connection is established).
No:
With this setting, no start command is transmitted.
The CANopen slave can be started at any time
using the “Start remote node” command.
Note: to do this, deactivate the parameter “Start
automatically”:
MandantorySlave If this option is set, the master only switches to the
“Operational” state if this slave is present.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.5 CANopen Slave Control Configuration

An application must be configured in CODESYS before it can access the
connected CAN network.
To add the CANopen slave to the control configuration, right-click “COS

unused[Slot]” and select “Replace element -> CANopen slave”.
Figure 130: Attaching a CANopen Slave
Right-click on CANopen Slave and select “Edit” to configure the slave.
Figure 131: Configuring a CANopen Slave
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.5.1 CANopen Variables Configuration
Figure 132: Configuration of the CANopen Slave Variables
CANopen variables can be added by clicking the [+] (Add) button. After this, you
must specify the data type and communication direction (I/O type).
Table 90: Description of the CANopen Slave Variables Window

Name You can edit the name for the variable or for its bits.
Address Output of the CODESYS address in the input or output area,
based on data type.
Data Type The following data types may be used:
BOOL, BYTE ,WORD, DWORD, SINT, INT, DINT, USINT,

UINT, UDINT, REAL, BYTE(Array)
The byte array can be extended by adding bytes until the

required size is achieved. The maximum length of the array
is eight bytes.
Comment Input field for a comment
I/O type Input or output
Fieldbus access Output of the address offset in bytes, relative to the
beginning of the CAN data range
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.3.5.2 Configuring of CANopen Parameters
Figure 133: Configuration of CANopen Slave Parameters
Table 91: Description of CANopen Slave Settings

Baud rate Specify the baud rate to apply for the transfer on the CAN
bus
(default setting: 125000 baud).
Node ID PFC's Node ID on the CAN bus.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
13.4 Fieldbus Coupler Diagnostics

This section requires substantial knowledge of the CODESYS programming tool.
It only describes the procedure to create diagnostics using the fieldbus master.
Configured slaves (e.g., a fieldbus coupler or a fieldbus controller) are required

for diagnostics in fieldbus networks.
The DiagGetBusState() and DiagGetState() function blocks are available from

the BusDiag.lib library and the CANopenDiag() function block from the
WagoCANopenDiag.lib.
13.4.1 BusDiag.lib
The following function blocks from the BusDiag.lib library are required in order to
evaluate the diagnostics:
• DiagGetBusState() for bus diagnostics

This function module provides general information on every connected slave
(e.g. number of slaves).
• DiagGetState() for subscriber diagnostics

This function block provides detailed information on each slave (e.g.
information on diagnostics).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.4.1.1 Creating Diagnostics in CODESYS 2.3
In order to execute bus diagnostics or subscriber diagnostics for the slaves, it is

necessary to integrate the BusDiag.lib library into CODESYS. This library
contains the necessary function blocks DiagGetBusState() for bus diagnostics
and DiagGetState() for subscriber diagnostics.
Integrate the BusDiag.lib library into CODESYS as described below:
1. Click the “Resources” tab.
Figure 134: “Resources” Tab
2. In the left column, double-click “Library Manager.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
3. In the menu bar, click on Insert > Additional library. The “Open” dialog
window then opens. Select the “BusDiag.lib” and click [Open] to add it to
the project.
Figure 135: “Open” Dialog Window
4. In the menu bar, click on the “Module” icon (the box symbol).
Figure 136: Module Icon in the Menu Bar; FUP Programming Language
5. Press [F2] on your keyboard. The “Input Assistant” dialog window opens.
Click on the option “Standard function blocks” and select the function block
DiagGetBusState().
6. Create an instance of the function block DiagGetBusState(). Enter a name

above the function block.
In the example shown here this is “GeneralBusInformation.”
Figure 137: Instance of the Function Block DiagGetBusState() in FUP
Manual
750-8214 PFC200; G2; 2ETH RS CAN
• DRIVERNAME:
The DRIVERNAME input parameter does not need to be indicated for the
controller.
• DEVICENUMBER:
The DEVICENUMBER is device-specific, and the variable “DeviceNumber”
must be adapted accordingly based on the information given in the section
“Appendix” > … > “BusDiag.lib.”
7. Call the function block DiagGetBusState() for the slave diagnostics from the
library BusDiag.lib.
8. Create an instance of the function block DiagGetState().

Shown in this example is “DiagnosticsNode.”
Figure 138: Function Block DiagGetState() in FUP
In this example, both function blocks are called during the program sequence. To
avoid prolonging the cycle times during the program sequence, set the input
“ENABLE” for DiagGetState() to “TRUE” only when performing diagnostic
operations.
13.4.1.2 Calling the Diagnostics Function Block
Call the function block as shown in the following figure.
Figure 139: Off-line View of Variable Window in CODESYS
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.4.1.3 Performing Bus Diagnostics Using DiagGetBusState()
To perform bus diagnostics, proceed as follows:
1. Log into CODESYS. To do this, click in the menu bar on Online > Login.
The variable window then displays information on the variables (online
view).
2. To start the PLC program, click on Online > Start in the menu bar. Starting
calls the function block DiagGetBusState(), and the diagnostic information
is output to the array EXTENDEDINFO.
In the online view of the variable window, the EXTENDEDINFO array provides
information on the status of the slave. An entry is reserved in the array for every
slave. The slave address is assigned to the array index. In this example, the
slaves with station addresses 2 and 5 store the diagnostic information. If the
device is configured as a slave, only the information for its own address is
available.
Display of diagnostic information

The diagnostic information is only displayed for the duration of one program
cycle. If the diagnostic information should be available for longer, a suitable
program must be written.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Array
0: No slaves or non-configured slaves

≠ 0: Configured slaves
Figure 140: Online View of Variable Window (Top Window) in FUP
3. The binary code facilitates the evaluation of the individual diagnostic bits.
The diagnostic information from the EXTENDEDINFO array can be
displayed in binary code. To do this, right click in the variable window and
select binary.
 Station address 4 of the controller
 Three least significant bits
 Station address 2 of the slave
 Station address 5 of the slave
Figure 141: Example of Diagnostics
4. Compare the three least significant bits of the diagnostic information of the
slaves with station addresses 2 and 5 to the bits from the following table:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 92: Diagnostic Information Bits
Bit 2 Bit 1 Bit 0
1 0 1 0 1 0
Diagnostic No diagnostic Slave is active. Slave is Slave installed. Slave not
information is information is inactive. installed.
present at the present at the
slave. slave.
• The slave with station address 2 supplies the value 011. This means that
the slave is installed and active.
• The slave with station address 5 supplies the value 111. This means that
the slave is installed and active and that error information is available for
this slave. Subscriber diagnostics must be performed to evaluate this error
information. Refer to section “Performing Subscriber Diagnostics Using
DiagGetState()” for more information about this.
Diagnostic information
When READY = TRUE, the STATE provides information on the current bus
status with one of the following values:
BUSOK: All configured slaves are exchanging data with the DP Master.
BUSFAULT: One or more configured slaves are not exchanging data with the DP
master
BUSNOTCOMMUNICATION: All configured slaves are not exchanging data with
the DP master.
13.4.1.4 Performing Subscriber Diagnostics Using DiagGetState()
If the bus diagnostics have revealed that an I/O module contains diagnostic
information, then perform subscriber diagnostics on the corresponding slave.
Proceed as follows:
1. Call the function block DiagGetState() by setting the input ENABLE to

“True.”
2.Specify the slave that provides the diagnostic information at the input variable
BUSMEMBERID. In this example it is the slave with fieldbus address 5.
Figure 142: DiagGetState() Diagnostic Call
Manual
750-8214 PFC200; G2; 2ETH RS CAN
• DRIVERNAME:
The DRIVERNAME input parameter does not need to be indicated for the
controller.
• DEVICENUMBER:
The DEVICENUMBER is device-specific, and the variable “DeviceNumber”
must be adapted accordingly based on the information given in the section
“Appendix” > … > “BusDiag.lib.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.4.1.5 Evaluating the CANopen Diagnostics (Emergency Messages)
The array elements [0] to [3] listed in the illustration below are reserved for the
CANopen status information in bytes. The emergency messages of the slaves
are stored starting with array element [4].
 Byte 1
 Byte 2 Range for CANopen status
information
 ...
Range for slave emergency

messages
Figure 143: Online View of the EXTENDEDINFO Array in Binary Representation
The CANopen status information and the slaves’ emergency messages are
described on the following pages.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Description of the Function Block’s Diagnostic Information
DiagGetState.EXTENDEDINFO for CANopen
The EXTENDEDINFO array contains the following status information:
Byte 0
Bit 0: Slave entered
Bit 1: Slave entered and configured
Bit 2: Slave configuration invalid
Bit 3: Diagnosis: Emergency event active
Bit 4: Slave status “Operational”
Bit 5: Slave status “Stop”
Bit 6: Slave status “Preoperational”
Bit 7: Configuration structure incorrect (from master)
Byte 1
Bit 0: Configuration structure not valid for slave.
Bit 1: Slave device detection error
Byte 2
Bit 0: An emergency message is present in the list.
Byte 3
Not used
Byte 4 … 11
Last emergency message in the list
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.4.2 WagoCANopenDiag.lib
This library provides a function block for the user-friendly monitoring of CANopen
nodes. The diagnostics and EMCY messages are provided in plain text.
Additional information is given in the description of the WagoCANopenDiag.lib.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
</dg_
13.5 Data Exchange between Simple CAN Subscribers

and PFC200 in the CANopen Network
The EDS file “Generic CAN device”, which has been reduced to the essentials,
has been created to simplify the control configuration for adding CAN Layer2
device. The EDS file contains 16 send and receive PDOs, each of which has
8x1-byte entries. You only have to deactivate the configuration and monitoring
telegrams typical of CANopen for these subscribers.

The EDS files for the CAN2 Layer2 device, which are supplied in the target files
for the controller, can only be used if the CODESYS 2.3 runtime system is used
on the controller!
You can also execute the control configuration with any EDS file for CANopen.
1. To add the CANopen Master to the control configuration, right-click “COS

unused[Slot]” and select “Replace element -> CANopen Master”.
Figure 144: Attaching the CANopen Master
Manual
750-8214 PFC200; G2; 2ETH RS CAN
2. In the “CAN Parameters” tab, select the required baud rate.
Figure 145: Setting the Baud Rate
3. To add a slave, right-click CANopen Master[SLOT] and select Attach

sub-element > Generic CAN Device (EDS) … in the contextual menu.
Figure 146: EDS File “Generic CAN Device”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
4. Open the Module parameters tab of the slave. For communication with
simple CAN Layer2 devices, deactivate transmission of the configuration to
the slave with EnableCANopenStartup (= “No”).
Figure 147: “Module Parameters” Tab
5. Open the CAN parameters tab of the slave. Deactivate the parameters
CommSDO, MappingSDO, Basic SDO and Nodeguarding.
Figure 148: “CAN Parameters“ Tab
6. You can now use the commands of the CAN Layer2 library (see Section
“CODESYS Libraries” > … > “WagoCANLayer2_01.lib”) to access the
devices.
To configure the CAN frames for CAN Layer2 devices, refer to the Section
“CANopen Master and Slaves” > … > “Configuring the slave PDOs”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
13.6 Data Exchange between CAN Subscribers and the

PFC200 in a CAN Layer2 Network
If there are only CAN Layer2 devices in the network, the CANopen functions are
not necessary. A separate device has been defined that provides only the CAN
Layer2 basic functions.

The EDS files for the CAN2 Layer2 device, which are supplied in the target files
for the controller, can only be used if the CODESYS 2.3 runtime system is used
on the controller!
1. To add the CAN Layer2 device to the control configuration, right-click “COS
unused[Slot]” and select “Replace element -> CAN Layer2 Device”.
Figure 149: Attaching the CAN Layer2 Device
2. The CAN interface can now be opened with the function blocks from the
WagoCANLayer2_02.lib, the CAN LED set and the data exchanged.
Manual
280 Diagnostics WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
14 Diagnostics
14.1 Operating and Status Messages
The following tables contain descriptions of all operating and status messages for
the controller which are indicated by LEDs.
14.1.1 Power Supply LEDs
Figure 150: Power Supply Indicating Elements
14.1.1.1 A LED
The A LED (system power supply) indicates following diagnostics:
Table 93: System Power Supply Diagnistics

Status Explanation Solution
Green 24V system power supply ---
voltage present
Off No 24V system power Switch on the power
supply voltage present supply. Check the supply
voltage.
14.1.1.2 B LED
The B LED (field-side power supply) indicates following diagnostics:
Table 94: Field-Side Supply Diagnostics

Green 24V field-side supply ---
voltage present
Off No 24V field-side supply Switch on the power
voltage present supply. Check the supply
voltage.
Manual
WAGO I/O System 750 Diagnostics 281
750-8214 PFC200; G2; 2ETH RS CAN
14.1.2 System/Fieldbus LEDs
Figure 151: Indicating elements for fieldbus/system
14.1.2.1 SYS LED
The SYS LED indication depends on the runtime system enabled (CODESYS V2
or e!RUNTIME).
The following indications apply to the CODESYS V2 runtime system:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 95: Diagnostics via SYS LED
Status Explanation Remedy
Green Ready to operate - ---
System start
completed without
errors
Orange Device is in ---
startup/boot process
and the RST button is
not pressed.
Load above threshold Try to reduce the load on the system:
value 1 - Change the CODESYS program.
The system is at full - End any fieldbus communication that
capacity; real-time is not essential, or reconfigure the
response can no fieldbuses.
longer be guaranteed. - Remove any non-critical tasks from
the RT area.
- Select a longer cycle time for IEC
tasks.
Orange flashing “Fix IP Address” Connect to the device via the standard
mode, address (192.168.1.17) or restart the
temporary setting device to restore the original value set.
until the next reboot
Red Load above threshold Try to reduce the load on the system:
value 2 - Change the CODESYS program.
The system is - End any fieldbus communication that
overloaded; real-time is not essential, or reconfigure the
response can no fieldbuses.
longer be guaranteed. - Remove any non-critical tasks from
the RT area.
tasks.
Green/red Firmware update ---
flashing mode
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The following indications apply to the e!RUNTIME runtime system:
Table 96: Diagnostics via SYS LED

Green Ready to operate - ---
System start
completed without
errors
Orange Device is in ---
startup/boot process
and the RST button is
not pressed.
Orange flashing “Fix IP Address” Connect to the device via the standard
mode, address (192.168.1.17) or restart the
temporary setting device to restore the original value set.
until the next reboot
Green/red Firmware update ---
flashing mode
Orange/red No license; The libraries or device functions affected
flashing evaluation period not are shown in e!COCKPIT.
yet expired Activate the associated licenses before
the evaluation period ends, or remove
the libraries or device functions from
your application.
The device has unrestricted functionality
until the evaluation period ends.
Red flashing No license; The libraries or device functions affected
evaluation period has are shown in e!COCKPIT.
expired Activate the associated licenses
promptly, or remove the libraries or
device functions from your application.
Otherwise, the application can no longer
be started after being downloaded again
or started as a boot application after the
device is restarted.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.2.2 RUN LED
The RUN LED indication depends on the runtime system enabled (CODESYS V2
or e!RUNTIME).
The following indications apply to the CODESYS V2 runtime system:
Table 97: Diagnostics RUN LED

Green PLC program has the ---
status “Run”.
Green flashing PLC program at a Resume the program in the linked IDE
debug point. (Integrated Development Environment)
using “Single step” or “Start”. If the
connection has been interrupted, set the
Run/Stop switch to “Stop” and then back
to “Run” to enable the program to
continue.
Green/red PLC is at a debug Set the Run/Stop switch to “Run” to
flashing point and the enable the program to continue.
Run/Stop switch has
been set to “Stop”.
Red No PLC-program Load the PLC program.
loaded or PLC Set the Run/Stop switch to “Run” to start
program has the the current program.
status “Stop”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
The following indications apply to the e!RUNTIME runtime system:
Table 98: RUN LED Diagnostics

Green Applications loaded ---
and all in the “RUN”
status
Green flashing No application and Load an application or boot project.
now boot project
loaded
Red Applications loaded Set the mode selector switch to “RUN” to
and all in the “STOP” start the application.
status
Green/red At least one Start the stopped application.
flashing application in the
“RUN” status and one
in the ”STOP” status
Red, Warm start reset ---
goes out briefly completed
Red, Cold start reset ---
goes out longer completed
Red, flashing At least one Start the application with a reset via the
application after in the mode selector switch or in the connected
“STOP” status after IDE.
exception (e.g., If the application cannot be started,
memory access error) restart the controller.
Contact WAGO Support if the error
occurs again.
Orange/green Load above threshold Try to reduce the load on the system:
flashing value 1 - Change the CODESYS program.
- End any fieldbus communication that
is not essential, or reconfigure the
fieldbuses.
- Remove any non-critical tasks from
the RT area.
tasks.
Orange Runtime system in Resume the application in the connected
debug state IDE with single step or start.
(breakpoint, single Remove the breakpoint if necessary.
step, individual cycle) If the connection has been interrupted,
set the mode selector switch to “STOP”
and then back to “RUN” to enable the
application to continue
OFF No runtime system Enable a runtime system, e.g., via the
loaded WBM.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.2.3 I/O LED
The I/O LED indicates following diagnostics:
Table 99: Diagnostics I/O LED

Green Data cycle on the local ---
bus, normal operating
status.
Orange flashing Startup phase; the local Wait until initialization has
bus is being initialized. been completed.
The startup phase is
indicated by rapid flashing
for about 1 ... 2 seconds.
Red A hardware fault is Contact WAGO Support.
present.
Red flashing An error which may be First, try to eliminate the
(2 Hz) able to be eliminated is error by switching the
present. device (power supply) off
and then back on.
Check the entire node
structure for any errors.
If you cannot eliminate the
error, contact WAGO
Support.
Red flashing A local bus error is An explanation of the
(flashing sequence) present. flashing sequence is
given in the section
“Diagnostics Messages
via Flashing Sequences”.
Off A library was not loaded, Restart the device.
or a library function was If you cannot eliminate the
not called up. error, contact WAGO
Support.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.2.4 MS LED
The MS LED indicates following diagnostics:
Table 100: MS-LED Diagnostics

Off No error ---
Red flashing A configuration error An explanation of the flashing sequence
(flashing exists. is given in the section “Diagnostics via
sequence) Flashing Sequences.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.2.5 CAN LED
The CAN LED indicates following diagnostics:
Table 101: Diagnostics CAN LED

Off The CAN interface has ---
not been configured
Alternating red 50 ms / Configuration in progress ---
green 50 ms
Alternating red 200 ms / Configuration invalid Check the configuration in
green 200 ms the CODESYS
Configurator.
Green 200 ms / off 800 The CANopen interface ---
ms has the status “Stop”.
Green 200 ms / off 200 The CANopen interface ---
ms has the status
“Preoperational”.
Green The CANopen interface ---
has the status
“Operational”.
Red The CANopen interface Check the bus
has the status “Bus Off” connections and the baud
(short-circuit or other rate.
major fault).
Error in the status “Preoperational”
1* red flashing / 2 * green “Bus Warning Level” Check the wiring for the
flashing exceeded. CAN bus.
2* red flashing / 2 * green “Guarding Error”, slave Check the slaves and the
flashing incorrectly configured or configuration.
not available.
3* red flashing / 2 * green “Sync Error” Change the time interval
flashing for the synchronization
message.
Error in the status “Operational”
1* red flashing / green “Bus Warning Level” Check the wiring for the
800 ms on exceeded. CAN bus.
2* red flashing / green “Guarding Error” Check the slaves and the
800 ms on configuration.
3* red flashing / green “Sync Error” Change the time interval
800 ms on for the synchronization
message.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.3 Network Connection LEDs
Figure 152: Indicating Elements, RJ-45 Jacks
14.1.3.1 LNK LED
The LNK LED indicates following diagnostics:
Table 102: LNK-LED Diagnostics

Off 10 Mbit/s ---
Green 100 Mbit/s ---
14.1.3.2 ACT LED
The ACT LED indicates following diagnostics:
Table 103: ACT-LED Diagnostics

Off No network Check network connections and network
communication via settings.
port
Yellow flashing Network ---
communication via
port
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.1.4 Memory Card Slot LED
Figure 153: Indicating Elements, Memory Card Slot
The memory card slot LED indicates following diagnostics:
Table 104: Diagnostics via Memory Card Slot LED

Off No memory card ---
access
Yellow Memory card access ---
Yellow flashing
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.2 Diagnostics Messages via Flashing Sequences
14.2.1 Flashing Sequences

A diagnosis (fault/error) is always displayed as three flashing sequences in a
cyclic manner:
1. The first flashing sequence (flickering) initiates reporting of the fault/error.
2. After a short break (approx. 1 second), the second flashing sequence

starts. The number of blink pulses indicates the error code, which
describes the type of error involved.
3. After a further break the third flashing sequence is initiated. The number of
blink pulses indicates the error argument, which provides an additional
description of the error, e.g., which of the I/O modules connected to the
controller exhibits an error.
Figure 154: Flashing Sequence Process Diagram
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.2.2 Example of a Diagnostics Message Indicated by a Flashing

Sequence
The example below illustrates the representation of a diagnostics message via a
flashing sequence. The I/O LED indicates a data error on the local bus. The data
error is caused by the removal of an I/O module located at the 6th position of the
bus node.
Initiation of the Start Phase
1. The I/O LED flashes for 1 cycle at about 10 Hz (10 flashes/second).
2. This is followed by a pause of about one second.
Error Code 4: Data Error in the Local Bus
3. The I/O LED flashes for 4 cycles of about 1Hz.
4. This is followed by a pause of about 1 second.
Error Argument 5: I/O Module at the 6th Slot
5. The I/O LED flashes for 5 cycles at 1 Hz.

This indicates that a disruption has occurred at the local bus downcircuit of
the 5th I/O module.
6. The blink code starts flickering when the start phase is initiated again. If
there is only one error, this process is repeated.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.2.3 Meaning of Blink Codes and Procedures for

Troubleshooting
This section describes the diagnostics presented as blink codes via the I/O LEDs.
If the diagnostics cannot be cleared by the measured specified for them, contact
WAGO support. Be ready to explain to them the blink code that is displayed.
Phone: +49 571 887 44 55 5

Fax: +49 571 887 84 45 55
E-mail: [email protected]
Table 105: Overview of Error Codes, I/O LED

Error code Explanation
1 Hardware and configuration error
2 Configuration error
3 Local bus protocol error
4 Physical error on the local bus
5 Local bus initialization error
6 Not used
7 Not supported I/O module
8 Not used
9 CPU exception error
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 106: Error Code 1, Explanation of Blink Codes and Procedures for Troubleshooting
Error
Cause Remedy
Argument
Invalid parameter - Switch off the power to the controller
- checksum for local and replace it.
bus interface - Then switch the power back on.
Internal buffer
overflow (max. - Switch off the power to the
amount of data controller.
1
exceeded) during - Reduce the number of I/O modules.
inline code - Switch the power back on.
generation.
- Update the controller firmware. If this
error persists, there is an error in the
I/O module. Identify the error as
follows:
- Switch off the power supply.
- Place the end module in the middle
of the I/O modules connected to the
system.
- Switch the power back on.
- If the I/O flashes red switch off the
Data type of the I/O power supply again and place the
2 module(s) is not end module in the middle of the first
supported half of the I/O modules (toward the
controller).
- If the LED is no longer flashing,
switch off the power supply and
place the end module in the middle
of the second half of the I/O modules
(away from the controller).
- Repeat this procedure until you
establish which I/O module is
defective. Then replace that module.
Unknown module - Switch off the power to the controller
3 type of the flash and replace it.
program memory - Then switch the power back on.
Error occurred while - Switch off the power to the controller
4 writing to the flash and replace it.
memory - Then switch the power back on.
Error occurred while
5
erasing a flash sector
The I/O module - Restart the controller by first
configuration after a switching off the power supply and
6 local bus reset differs then switching it back on, or
from the one after the by pressing the Reset button on the
last controller startup. controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Error
Cause Remedy
Argument
Error occurred while - Switch off the power to the controller
7 writing to the serial and replace it.
EEPROM - Then switch the power back on.
Invalid hardware/
8
firmware combination
Invalid checksum in
9
the serial EEPROM
Fault when initializing
10
the serial EEPROM.
- Switch off the power supply to the
Error occurred while
controller and reduce the number of
11 reading from the
I/O modules.
serial EEPROM
- Then switch the power back on.
Time to access the - Switch off the power to the controller
12 serial EEPROM and replace it.
exceeded - Then switch the power back on.
- Switch off the power to the
Maximum number of controller.
14 gateway or mailbox - Reduce the number of gateway or
modules exceeded. mailbox modules.
Maximum number of
controller.
16 I/O modules
- Reduce the number of I/O modules.
exceeded
Error
Cause Remedy
Argument
Maximum size of the
controller.
2 process image
- Reduce the number of I/O modules.
exceeded
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Error
Cause Solution
Argument
If a power supply module (e.g., 750-602)
is connected to the controller, ensure
that this module functions properly (see
Section “LED Signaling”). If the supply
module does not exhibit any errors/faults,
the I/O module is defective. Identify the
defective I/O module as follows:
- Switch off the power supply.

- Place the end module in the middle
of the I/O modules connected to the
system.
- If the I/O LED continues to flash red
switch off the power supply again
and place the end module in the
Local bus communication
middle of the first half of the I/O
-- error; defective I/O module
modules (toward the controller).
cannot be identified
If only one I/O module is left and the LED
continues to flash, either this module or
the controller local bus interface is
defective. Replace the defective module
or the controller.
- If the LED is no longer flashing,

switch off the power supply and
place the end module in the middle
of the second half of the I/O modules
(away from the controller).
- Repeat this procedure until you
establish which I/O module is
defective. Then replace that module.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Error
Cause Solution
Argument
- Switch off the power to the controller.
Maximum permissible
- Reduce the number of I/O modules
-- number of I/O modules
to an acceptable value.
exceeded.
- Replace the (n+1)th process data
module.
Local bus disruption after
n* the nth process data
module.
I/O modules that do not provide any data
are ignored (e.g., supply module without
diagnostics).
Error
Cause Solution
Argument
- Replace the (n+1)th process data
module.
Register communication
n* error during local bus
initialization
I/O modules that do not provide any data
are ignored (e.g., supply module without
diagnostics).
Error
Cause Solution
Argument
- Replace the nth I/O module
First unsupported I/O containing process data or reduce
n
module in place of n. the number of modules to the
number of n-1.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Error
Cause Remedy
Argument
Invalid program Malfunction of the program sequence:
1
statement - Contact WAGO Support.
Malfunction of the program sequence:
2 Stack overflow
- Contact WAGO Support.
3 Stack underflow
4 Invalid event (NMI)
For CODESYS V2 applications:
For e!RUNTIME applications:
- Check the system load by IEC tasks
Local bus watchdog with priorities 1 ... 14 in the runtime
5
has triggered. system (see Section “e!RUNTIME”
Runtime Environment >
“CODESYS V3 Priorities”).
For C applications:
- Check the time monitoring settings.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
14.2.4 Meaning of Blink Codes and Procedures for

Troubleshooting
This section describes the diagnostics presented as blink codes via the MS
LEDs.
If the diagnostics cannot be cleared by the measured specified for them, contact
WAGO support. Be ready to explain to them the blink code that is displayed.
Phone: +49 571 887 44 55 5

Fax: +49 571 887 84 45 55
E-mail: [email protected]
Table 113: Overview of MS-LED Error Codes

Error Code Explanation
1 Configuration error
Error
Cause Remedy
Argument
- Check the information of the
Error when connected I/O modules in the
synchronizing the CODESYS controller configuration.
5 controller - Adjust this to match the I/O module
configuration with the that is actually inserted.
local bus - Recompile the project.
- Reload the project into the controller.
Manual
300 Service WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
15 Service
15.1 Inserting and Removing the Memory Card
</dg_
15.1.1 Inserting the Memory Card

1. Use an actuating tool or a screwdriver to open the transparent cover flap by
flipping it upwards. The point where to position the tool is marked with an
arrow.
2. Hold the memory card so that the contacts are visible on the right and the
diagonal edge is at the top, as depicted in the figure below.
3. Insert the memory card in this position into the slot provided for it.
4. Push the memory card all the way in. When you let go, the memory card
will move back a little and then snap in place (push-push mechanism).
5. Close the cover flap by flipping it down and pushing it in until it snaps into
place.
6. You can seal the closed flap through the hole in the enclosure next to the
flap.
Figure 155: Inserting the Memory Card

</dg_
15.1.2 Removing the Memory Card

1. First, remove any seal that may be in place.
2. Use an actuating tool or a screwdriver to open the transparent cover flap by

flipping it upwards. The point where to position the tool is marked with an
arrow.
3. To remove the memory card you must first push it slightly into the slot
(push-push mechanism). This releases the mechanical locking mechanism.
4. As soon as you let go of the memory card, the memory card is pushed out
a bit and you can remove it.
5. Remove the memory card.
Manual
WAGO I/O System 750 Service 301
750-8214 PFC200; G2; 2ETH RS CAN
6. Close the cover flap by flipping it down and pushing it in until it snaps into
place.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
15.2 Firmware Changes
Do not switch the controller off!

The controller can be damaged by interrupting the factory reset process.
Do not switch the controller off during the factory reset process, and do not
disconnect the power supply!
Obtain documentation appropriate for the firmware target version!

A firmware change can modify, remove or add controller properties and
functions. As a result, described properties or functions of the controller may not
be available or available properties or functions may not be described in the
documentation.
Therefore, use only documentation appropriate for the target firmware after a
firmware change.
If you have any questions, feel free to contact our WAGO Support.
Note the firmware version

For devices with a factory installation of a firmware >= FW 05, a simple
downgrade to a version <= FW 04 is not possible!
Use a special downgrade image.
You can update the firmware in two different ways using:
• e!COCKPIT
• WAGOupload
• Memory card and WBM
Manual
750-8214 PFC200; G2; 2ETH RS CAN
15.2.1 Use e!COCKPIT to Update/Downgrade the Firmware

1. Launch e!COCKPIT.
2. Create a new project or open an existing project.
3. Add at least one controller to your e!COCKPIT project either by scanning

the network or going to the device catalog and entering the IP address of
your controller in the settings dialog.
Your controller is now displayed in the Device View of the project.
4. Select the displayed controller and click “Apply Selection” in the “SCAN”
tab.
5. Click [Add] in the dialog.
6. Then click [Replace Firmware]. in the “DEVICE” tab.
The “Replace Firmware” dialog opens.
7. In the “Replace Firmware” dialog, select the required firmware under

“Available firmware on the PC” or click the “Select File” entry and select the
* .wup firmware file for the required firmware.
8. Click [Replace Firmware] to transfer the firmware to the controller.
9. Wait until the operation ends with a status message and only then click
[OK] to close the window.
The newly installed firmware is now available on your controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
15.2.2 Use WAGOupload to Update/Downgrade the Firmware

1. Launch WAGOupload.
2. Click the [Update Firmware] action.
3. In the “Select Target Controllers” dialog, enter the IP address of your

controller in the “Transfer via TCP/IP” option.
4. Click [Find Controller].
Your controller is now displayed in the list.
5. Select the displayed controller and click [Next].
6. In the “Select Update File” dialog, select the *.wup firmware file for the
required firmware.
7. Click [Next].
8. Click [Next] to confirm the summary.
9. Wait until the operation ends with a status message and only then click
[Exit] to close the window.
The newly installed firmware is now available on your controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
15.2.3 Perform Firmware Update/Downgrade

Proceed as follows if you want to update the controller to a later firmware version
or to downgrade the controller to an earlier firmware version:
1. Copy the firmware image (*.img file) of the required firmware to the memory
card using a suitable PC tool.
2. Save your application and the controller settings.
3. Switch off the controller.
4. Insert the memory card with the new firmware image into the memory card
slot. Use a special downgrade image if necessary (see above).
5. Switch on the controller.
6. After booting the controller, launch the WBM “Create Boot Image” page
(you may have to temporarily change the IP address).
7. Create a new boot image on the internal memory.
8. Switch off the controller after completing the process.
9. Remove the memory card.
10. Switch on the controller.
The controller can now be started with the new firmware version.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
15.3 Updating Root Certificates

If you want to update the root certificates on the controller, proceed as follows:
1. Download the current root CA bundle from https://curl.haxx.se/ca to your

PC.
2. Rename the file “ca-certificates.crt.”
3. Transfer the file to the /etc/ssl/certs directory on the controller with an SFTP
or FTP client.
4. Restart the controller. To do so, use the reboot function in WBM or CBM.
Manual
WAGO I/O System 750 Removal 307
750-8214 PFC200; G2; 2ETH RS CAN
16 Removal

16.1 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.
16.1.1 Removing the 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 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 controller.
Figure 156: Release Tab of Controller (Example)
Do not take the controller enclosure apart!

The enclosure sections are firmly joined. The feed-in section with the CAGE
CLAMP® connections cannot be separated from the other enclosure section.
Manual
308 Disposal WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
17 Disposal
17.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.
17.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.
Manual
WAGO I/O System 750 Disposal 309
750-8214 PFC200; G2; 2ETH RS CAN
• 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
310 Use in Hazardous Environments WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
18 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
WAGO I/O System 750 Use in Hazardous Environments 311
750-8214 PFC200; G2; 2ETH RS CAN
18.1 Marking Configuration Examples
18.1.1 Marking for Europe According to ATEX and IECEx
Figure 157: Marking Example According to ATEX and IECEx
Figure 158: Text Detail – Marking Example According to ATEX and IECEx
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 115: 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
750-8214 PFC200; G2; 2ETH RS CAN
Figure 159: Marking Example for Approved I/O Module Ex i According to ATEX and IECEx
Figure 160: Text Detail – Marking Example for Approved I/O ModuleEx i According to ATEX and
IECEx
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 116: 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
750-8214 PFC200; G2; 2ETH RS CAN
18.1.2 Marking for the United States of America (NEC) and Canada
(CEC)
Figure 161: Marking Example According to NEC
Figure 162: Text Detail – Marking Example According to NEC 500
Table 117: 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
750-8214 PFC200; G2; 2ETH RS CAN
Figure 163: Text Detail – Marking Example for Approved I/O Module Ex i According to NEC 505
Table 118: 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 164: Text Detail – Marking Example for Approved I/O Module Ex i According to NEC 506
Table 119: 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
750-8214 PFC200; G2; 2ETH RS CAN
Figure 165: Text Detail – Marking Example for Approved I/O Module Ex i According to CEC 18
attachment J
Table 120: 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
750-8214 PFC200; G2; 2ETH RS CAN
18.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.
18.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
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
18.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!
Additional Information
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
WAGO I/O System 750 Appendix 321
750-8214 PFC200; G2; 2ETH RS CAN
19 Appendix
19.1 Configuration Dialogs
19.1.1 Web-Based-Management (WBM)
19.1.1.1 “Information” Tab
19.1.1.1.1 “Device Status” Page
The “Device Status” page shows information about product identification and the
most important network properties.
“Device Details” Group
This group shows information about product identification.
Table 121: WBM “Device Status” Page – “Device Details” Group

Product Description Product Designation
Order Number Product Item Number
Serial Unique Product Serial Number
Notification that the CODESYS runtime system is
License Information
available
Firmware Revision Firmware Version
Manual
322 Appendix WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
“Network TCP/IP Details” Group
The network and interface properties of the product are displayed in this group.
Table 122: WBM “Device Status” Page – “Network TCP/IP Details” Group
Parameter Meaning
Bridge currently configured;
Bridge <n> the properties are displayed in a separate area for
each configured bridge.
MAC address used for product identification and
MAC Address
addressing
Current reference type of the IP address
None No IP allocation method is selected; this
occurs, for example, if a bridge was
added due to changes to the bridge
configuration.
Select a source in the Configuration tab
on the Networking > TCP/IP
Configuration page.
IP Source static IP Static IP address assignment
dhcp Dynamic IP address assignment via
DHCP
bootp Dynamic IP address assignment via
BootP (if BootP is supported)
external The IP address may be assigned by the
fieldbus application; this occurs e.g., if
the IP address is controlled by the
application.
IP Address Current product IP address
Subnet Mask Current product subnet mask
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.2 “Vendor Information” Page
You can find the manufacturer and address on the “Vendor Information” page.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.3 “PLC Runtime Information” Page
All information about the enabled runtime system and PLC program created in
the programming software is provided on the “PLC Runtime Information” page.
You will also find a link here to open WebVisu.
“Runtime” Group
Table 123: WBM “PLC Runtime Information” Page – “Runtime” Group

The version of the currently enabled runtime system
is shown.
Version If the runtime system is disabled, “None” is
displayed and the subsequent fields of this group
are hidden.
This shows the version number of the Webserver.
This field appears if the controller supports the
Webserver Version
CODESYS V2 runtime system and CODESYS V2 is
set as the runtime system.
The PLC operating state is displayed.
State set as the runtime system.
STOP PLC program is not executed.
RUN PLC program is executed.
The number of tasks in the PLC program is shown.
Number of Tasks
set as the runtime system.
“WebVisu” Group
You will find a link that you can use to open WebVisu.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Project Details” Group
This group appears if the controller supports the CODESYS V2 runtime system
and CODESYS V2 is set as the runtime system.
Table 124: WBM “PLC Runtime Information” Page – “Project Details” Group
Date The last save date of the project is displayed.
The project information that the programmer has
Title
entered in the PLC program is displayed here (in the
programming software under Project > Project
Version
Information ...).
The information only appears in an executed PLC
Author
program.
Descriptive texts up to 1024 characters long are
Description
given under “Description.”
Checksum The calculated checksum of the project is displayed.
“Task <n>” Group(s)
One dedicated group is displayed for each task when the PLC program is
executed. As a rule, only the group title is displayed with the task number, the
task name and the task ID.
This group(s) appear(s) if the controller supports the CODESYS V2 runtime

system and CODESYS V2 is set as the runtime system.
Table 125: WBM “PLC Runtime Information” Page – “Task n” Group(s)

Cycle count Number of task cycles since the system start
Cycle time (µsec) Currently measured task cycle time for the task
Minimum task cycle time for the task since the
Cycle time min (µsec)
system start
Maximum task cycle time for the task since the
Cycle time max (µsec)
system start
Cycle time avg (µsec) Average task cycle time since the system start
Status Task status (e.g., RUN, STOP)
Mode Task execution mode (e.g., in cycles)
Priority Set task priority
Interval (msec) Set task interval
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.4 “WAGO Software License Agreement” Page
The “WAGO Software License Agreement” page lists the license terms for the
WAGO software used in the product.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.5 “Open Source Licenses” Page
The license conditions for the open source software used for the product are
listed in alphabetical order on the “Open Source Licenses” page.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.6 “WBM Third Party License Information” Page
On the “WBM Third Party License Information” page, you can find the license text
of the open source licenses that apply to the WBM itself.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.7 “Trademarks Information” Page
On the “Trademarks Information” page you will find a list of property and
trademark rights.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.1.8 “WBM Version” Page
On the “WBM Version” page, you can find the version information for the various
sections (“Plug-ins”) that the WBM contains. This information may be useful for
support if an error is found in the WBM.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2 “Configuration” Tab
19.1.1.2.1 “PLC Runtime Configuration” Page
On the "PLC Runtime Configuration" page, you will find the settings for the boot
project created with the programming software and the settings for the web
visualization created in the runtime system.
“General PLC Runtime Configuration” Group
Table 126: WBM “PLC Runtime Configuration” Page – “General PLC Runtime Configuration” Group
Parameter Meaning
Select here the PLC runtime system to be enabled.
None No runtime system is enabled.

CODESYS V2 runtime system is
enabled.
CODESYS 2 This value only appears if the
PLC runtime version controller supports the
CODESYS V2 runtime system.
e!RUNTIME runtime system is
enabled.
e!RUNTIME This value only appears if the
controller supports the
e!RUNTIME runtime system.
Define if the home directory for the runtime system
should be moved to the memory card.
Home directory on memory The home directory is stored in
Disabled
card enabled the internal memory.
The home directory is moved to
Enabled
the memory card.
All data is deleted when switching the runtime system!

The runtime system’s home directory is completely deleted when switching the
runtime system!
Only the first partition can be used as the Home directory!

Only the first partition of a memory card can be accessed at /media/sd and used
as the home directory.
Click [Submit] to apply the change. The runtime system change is effective
immediately.
The home directory change only takes effect after the product restarts. For this
purpose, use the WBM reboot function. Do not switch off the product too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Webserver Configuration” Group
Table 127: WBM “PLC Runtime Configuration” Page – “Webserver Configuration” Group
Parameter Meaning
This displays the status (enabled/disabled) of the
CODESYS V2 Webserver CODESYS V2 Webserver.
State This field only appears if the controller supports the
This indicates the status (enabled/disabled) of the
e!RUNTIME Webserver e!RUNTIME Webserver.
State This field only appears if the controller supports the
e!RUNTIME runtime system.
Choose here whether the Web-based Management
or web visualization of the runtime system should be
displayed when only entering the IP address of the
controller.
Default Webserver
Web-Based The Web-based Management is
Management displayed.
WebVisu The web visualization of the runtime
system is displayed.
Click [Submit] to apply the change. The change takes effect immediately.
In its default setting, the WBM is called up when only entering the IP address.
To update the display after switching, enter the IP address again in the address
line of the Web browser.
To display the web visualization, the Webserver must be enabled (in WBM under
“Ports and Services” -> “PLC Runtime Services”) and there must be a suitably
configured application.
Regardless of the default Webserver setting, the WBM can be called up at any
time with “https://<IP address>/wbm” and the Web visualization with “https://<IP
address>/webvisu”.
Possible error messages when calling up the web visualization

The “500 − Internal Server Error” message indicates that the Webserver is not
enabled.
A page with the header “WebVisu not available” means that no application has
been loaded in the product using web visualization.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.2 “TCP/IP Configuration” Page
The TCP/IP settings for the ETHERNET interfaces are shown on the “TCP/IP
configuration” page.
“TCP/IP Configuration” Group
The properties are displayed in a separate area for each configured bridge.
Table 128: WBM “TCP/IP Configuration” Page – “TCP/IP Configuration” Group

Parameter Meaning
Network Details Bridge <n> Settings for the bridge currently configured
Current IP Address This displays the current IP address.
Current Subnet Mask This displays current subnet mask.
The IP address of the current default gateway is
Current Default Gateway
displayed.
You can specify whether to use a static or dynamic
IP address.
IP Source Static IP Static IP addressing
DHCP Dynamic IP addressing via DHCP
BootP Dynamic IP addressing via BootP
Enter a static IP address. This is enabled if “Static
IP Address
IP” is enabled in the IP Source field.
Enter the subnet mask. This is enabled if “Static IP”
Subnet Mask
is enabled in the IP Source field.
Default Gateway Enter the IP address of the default gateway here.
Click the [Submit] button to apply a change. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“DNS Server” Group
Table 129: WBM “TCP/IP Configuration” Page – “DNS Server” Group

The active DNS servers are displayed.
Up to 3 active DNS servers can be used.
Active The index reflects the query order.
The first DNS server assigned via DHCP is given
the highest priority.
The DNS servers assigned if necessary by DHCP
(or BootP) are displayed. If no DNS server has been
Assigned by DHCP
assigned by DHCP (or BootP), “No DNS Servers
assigned by DHCP” is displayed.
The addresses of the defined DNS servers are
Assigned by user displayed. If no server has been entered, “No DNS
Servers configured” is displayed.
Add additional DNS server addresses.
You can enter as many addresses as you like, but a
maximum of three entries are used.
New Server IP
The entries actually used result from an alternating
combination of the “Assigned by DHCP” and
”Assigned by user” lists.
Click the [Delete] button to delete the selected DNS server. The change takes
effect immediately.
Click the [Add] button to add the entered DNS server. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.3 “Ethernet Configuration” Page
The settings for ETHERNET are located on the “Ethernet Configuration” page.
“Bridge Configuration” Group
Table 130: WBM “Ethernet Configuration” Page – “Bridge Configuration” Group

Parameter Meaning
Assign the physical ports X1… X <n> to a logical
bridge.
Bridge 1 … <n> To do so, click the respective option button. The
assignment is marked in color.
A port can only be assigned to one bridge at a time.
Click the [Submit] button to apply the change. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Switch Configuration” Group
This group only appears if parameter configuration is supported.
Table 131: WBM “Ethernet Configuration” Page – “Switch Configuration” Group

Enable or disable mirroring of the data traffic
between the ports.
Both ETHERNET ports are operating
None
normally.
Port Mirror
The entire data traffic between X1 and
X1
the PFC system is mirrored at port X2.
The entire data traffic between X2 and
X2
the PFC system is mirrored at port X1.
You can set the broadcast limit for protection against
overloads.
Disabled No broadcast packet limit
Broadcast Protection
Limits incoming broadcast packets to
1 % … 5 % the selected percentage of the total
possible data throughput (10/100 Mbit)
You can set the basic limitation of the incoming data
traffic.
Rate Limit Disabled No limitation of the incoming data traffic
64 kbps … Limits the incoming data traffic to the
99 mbps entered value
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Ethernet Interface Configuration” Group
Table 132: WBM “Ethernet Configuration” Page – “Ethernet Interface Configuration” Group
Parameter Meaning
A separate area is displayed for each interface in
Interface X<n>
the controller.
Enabled You can enable or disable the interface.
MAC Learning You can disable or enable “MAC Learning”.
Select the transmission speed and the transmission
method.
The drop-down menu is generated depending on the
Speed/Duplex device and interface.
When “Autonegotiation” is selected, the connection
modalities are negotiated automatically between the
peer devices.
Click [Submit] to apply changes. The changes take effect immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.4 Configuration of Host and Domain Name” Page
The settings for the hostname and domain are displayed on the “Configuration of
Host/Domain Name” page.
“Hostname” Group
Table 133: WBM “Configuration of Host and Domain Name” Page – “Hostname” Group
If you have selected dynamic assignment of an IP
Currently used address via DHCP, the name of the host currently
being used is displayed.
Enter the product hostname here; it is then used if
the network interface is changed to a static IP
Configured
address or if no hostname is assigned per DHCP
response.
Click the [Submit] button to apply a change.
Click the [Clear] button to reset the input field.
The change takes effect immediately.
If the controller has been assigned a host name via DHCP, it is given preference
and the manually configured host name is not used.
To accept the manually configured host name, the configuration of the DHCP
server may have to be reduced by assigning the host name.
“Domain Name” Group
Table 134: WBM “Configuration of Host and Domain Name” Page – “Domain Name” Group
If you have selected dynamic assignment of an IP
Currently used address via DHCP, the name of the domain
currently being used is displayed.
Enter the product domain name here; it is then used
if the network interface is changed to a static IP
Configured
address or if no domain name is assigned per
DHCP response.
Click the [Clear] button to reset the input field.
The change takes effect immediately.
If the controller has been assigned a domain name via DHCP, it is given
preference and the manually configured domain name is not used.
To accept the manually configured domain name, the configuration of the DHCP
server may have to be reduced by assigning the domain name.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.5 “Routing” Page
On the “Routing” page you can find settings and information on the routing
between the network interfaces.
“IP Forwarding through multiple interfaces” Group
Table 135: WBM “Routing” Page – “IP Forwarding through multiple interfaces” Group
Specify whether forwarding of IP data packets is
allowed between different network interfaces.
If the box is not checked, the settings under “Static
Routes” are used, without allowing IP data packets
that arrive at the controller on one network interface
Enabled
to leave the controller on different network interface.
If the box is checked, IP packets can be forwarded
between the interfaces.
Other settings may be necessary on this WBM
page.
Click the [Submit] button to apply the change. The changes take effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Custom Routes” Group
Each configured static route has its own area in the display. If no static routes
have been entered, “(no custom routes)” is displayed.
Table 136: WBM “Routing” Page – “Custom Routes“ Group

Specify whether the selected route should be used.
Enabled Disabled The route is not used.
Enabled The route is used.
Specify whether any network devices or only a
specific network device or device pool should be
accessible.
Any network devices can be
Destination Address Default
reached.
Only a specific network device
Network address or device from the specified
address pool can be reached.
Enter the subnet mask of the device.
Destination Mask If “default” is entered for Destination Address, the
value “0.0.0.0” must be entered.
Enter the address of the gateway.
If the “Interface” input field is empty, an entry is
Gateway Address
required here. If a value is entered in the “Interface”
input field, the input here is optional.
Set the number used as the metric.
When there are multiple routes with the same
destination address and destination mask, the
metric specifies the gateway to which network data
Gateway Metric
packets are first sent. Priority is given to routes with
a lower value for the metric.
The lowest value is 0.
The highest value is 2³² - 1 = 4294967295.
Enter an interface via which the packets sent to the
destination address are routed. Bridges (br0-br3) as
well as modems (wwan0) or VPN interface names
can be used.
Interface
If the “Gateway Address” input field is empty, an
entry is required here. If a value is entered in the
“Gateway Address” input field, the input here is
optional.
Click the [Submit] button to apply the changes. The changes take effect
immediately.
To add a new route, click the [Add] button. The change takes effect immediately.
Click the [Delete] button to delete an existing route. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Dynamic Routes” Group
All default gateways received via DHCP are displayed.

Default gateways configured via DHCP are given the metric value 10, which
means that they are normally used before the statically configured default
gateways.
Each dynamic route has its own area in the display. If no dynamic routes are
received via DHCP, “(no dynamic route)” appears.
“IP-Masquerading” Group
Each entry has its own area in the display.
Table 137: WBM “Routing” Page – “IP-Masquerading” Group

Specify whether IP masquerading should be used.
Enabled Disabled IP masquerading is not used.
Enabled IP masquerading is used.
You can select the specified name of a network
Interface interface. Alternatively, selecting “other” allows you
to specify any network interface name.
immediately.
Click the [Add] button to add a new entry. The change takes effect immediately.
Click the [Delete] button to delete an existing entry. The change takes effect
immediately.
An entry is only transferred to the system if “Enabled” is enabled in the “General

Routing Configuration” group. This allows you to configure a default setting that is
not applied until the general switch-on.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Port-Forwarding” Group
Each entry has its own area in the display.
Table 138: WBM “Routing” Page – “Port Forwarding” Group

Specify whether port forwarding should be used.
Enabled Disabled Port forwarding is not used.
Enabled Port forwarding is used.
You can select the specified name of a network
Interface interface. Alternatively, selecting “other” allows you
to specify any network interface name.
Enter the port here on which the product receives
Port
network data packets to be forwarded.
You can select the protocol to be used for the port
Protocol forwarding. The options are TCP, UDP or both
protocols.
Specify the network address of the destination
Destination Address device. This address replaces the original
destination address of the network data packet.
Specify the port number of the destination device.
Destination Port This value replaces the original destination port of
the network data packet.
immediately.
Click the [Add] button to add a new entry. The change takes effect immediately.
Click the [Delete] button to delete an existing entry. The change takes effect
immediately.
An entry is only transferred to the system if “Enabled” is enabled in the “General

Routing Configuration” group. This allows you to configure a default setting that is
not applied until the general switch-on.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.6 “Clock Settings” Page
The date and time settings are displayed on the “Clock Settings” page.
“Timezone and Format” Group
Table 139: WBM “Clock Settings” Page – “Timezone and Format” Group
Select the appropriate time zone for your location.
Default setting:
AST/ADT “Atlantic Standard Time,” Halifax
“Eastern Standard Time,” New York,
EST/EDT
Toronto
“Central Standard Time,” Chicago,
CST/CDT
Winnipeg
“Mountain Standard Time,” Denver,
MST/MDT
Edmonton
Timezone “Pacific Standard Time”, Los Angeles,
PST/PDT
Whitehouse
“Greenwich Mean Time”, GB, P, IRL,
GMT/BST
IS, …
“Central European Time,” B, DK, D,
CET/CEST
F, I, CRO, NL, …
“Eastern European Time,” BUL, FI,
EET/EEST
GR, TR, …
CST “China Standard Time”
JST “Japan/Korea Standard Time”
For time zones that cannot be selected with the
“Time Zone” parameter, enter the name of the time
zone or the country or city applicable to you.
TZ string
You can determine a valid name for the time zone
here:
http://www.timeanddate.com/time/map/
For switching between 12-hour and 24-hour time
Time Format
display
immediately.
“UTC Time and Date” Group
Table 140: WBM “Clock Settings” Page – “UTC Time and Date” Group
UTC Date Set the date.
UTC Time Set GMT time.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Local Time and Date” Group
Table 141: WBM “Clock Settings” Page – “Local Time and Date” Group
Local Date Set the date.
Local Time Set the local time.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.7 “Configuration of Serial Interface RS232/RS485” Page
The settings for the serial interface are shown on the “Configuration of Serial
Interface RS232/485” page.
“Serial Interface assigned to” Group
The application that the serial interface is currently assigned to is displayed.
“Assign Owner of Serial Interface” Group
You can specify the application that the serial interface is to assigned after the
next controller reboot.
Table 142: WBM “Configuration of Serial Interface RS232” Page – “Assign Owner of Serial Interface”
Group
Specify that the serial interface is assigned to the
Linux® Console
Linux® console.
Specify that the serial interface is not to be assigned
Unassigned (usage by
to any application and is available, so that the
applications, libraries,
CODESYS program, for example, can access it via
CODESYS)
function blocks.
Remove RS-485 devices before switching to “Linux Console”!

Connected RS-485 devices can be damaged when switching to “Linux Console”.
Remove these devices before switching!
Click [Change Owner] to apply the change. The change only takes effect once
the controller restarts. For this purpose, use the WBM reboot function. Do not
shut down the controller too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.8 “Configuration of Service Interface” Page
The settings for the service interface are shown on the “Configuration of the
Service Interface” page.
“Service Interface assigned to” Group
The application that the service interface is currently assigned to is displayed.
“Assign Owner of Service Interface” Group
You can specify the application to which the service interface is assigned after
the next controller reboot.
Table 143: WBM “Configuration of Service Interface” Page – “Assign Owner of Service Interface”
Group
Specify that the service interface is used for the
WAGO Service
WAGO Service communication or runtime system
Communication
communication.
Specify that the service interface is assigned to the
Linux Console
Linux® console.
Specify that the service interface is not to be
Unassigned (usage by
assigned to any application and is available, so that
applications, libraries,
the CODESYS program, for example, can access it
CODESYS)
via function blocks.
Click [Submit] to apply the change. The change only takes effect once the
controller restarts. For this purpose, use the WBM reboot function. Do not shut
down the controller too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.9 “Create Bootable Image” Page
You can create a bootable image on the “Create Bootable Image” page.
“Create bootable image from boot device” Group
Once the destination has been determined and output, it is then checked and the
results of this check are displayed below the settings:
Table 144: WBM “Create Bootable Image” Page – “Create bootable image from active partition”
Group
Parameters Meaning
The medium from which the boot was made is
Boot Device
displayed.
Depending on which medium has been booted, the
following destination is available for selection after
boot-up for the image to be generated:
Destination System was booted Target partition for
from “bootable image”
Memory Card  Internal Flash
Internal memory  Memory Card
- Free space on target device:

If the available memory space is less than 5% a warning is displayed. You
can still start the copy process despite the warning. If the available space is
too low, a corresponding message is displayed and copying cannot be
started.
- Device being used by CODESYS:

If the device is being used by CODESYS, a warning is displayed. Although
it is not recommended, you can still start the copying procedure despite this
warning.
Click [Start Copy] to start the copying procedure. If the outcome of the test is
positive, copying begins immediately. If errors have been detected, a
corresponding message is displayed and copying is not started. If warnings have
been issued, these are displayed again and you must then confirm that you still
wish to continue.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.10 “Firmware Backup” Page
You can find the controller data backup settings on the “Firmware Backup” page.
“Firmware Backup” Group
Table 145: WBM “Firmware Backup” Page – “Firmware Backup” Group

The storage medium from which the device was
Boot Device
booted is displayed here.
Select the storage location for the backup here.
The data is written to the memory
card.
This selection only appears if a
Memory Card
memory card is inserted and the
Destination
device has not been booted from
the memory card.
The data is saved in the file system
Network and then made available as a
download on the PC.
If you want to save the PLC runtime project, select
PLC runtime project
this checkbox.
If you want to save the device settings, select this
Settings
checkbox.
If you want to back up the operating system of the
System
device and the root file system, select this checkbox.
If you want to save the data in encrypted form,
Encryption
select this button.
Enter the encryption password here.
Encryption passphrase This input field only appears if the “Encryption”
checkbox is selected.
Enter the encryption password again here to check
it.
Confirm passphrase
This input field only appears if the “Encryption”

identical.
beforehand.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Only one package may be copied to the network!

If you have specified “Network” as the storage location, only one package may
be selected for each storing process.
No backup of the memory card!

Backup from the memory card to the internal flash memory is not possible.
Account for backup time!

Generation of backup files can take several minutes. Stop the CODESYS
program before you start the backup procedure to help shorten the time required.
Click the [Create Backup] button to start the backup operation.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.11 “Firmware Restore” Page
The settings for restoring the controller data are shown on the “Firmware
Restore” page.
“Firmware Restore” Group
Table 146: WBM “Firmware Restore” Page – “Firmware Restore” Group

Select the data source for the restore here.
The data is read from the memory
card.
This selection is only enabled if a
Memory Card
Source memory card is inserted and the
device has not been booted from
the memory card.
The data is uploaded from the PC
Network
and restored.
Boot Device
Enter the name of the backup file for the CODESYS
project here.
PLC runtime project
The input field only appears if the network is
selected as the data source.
Enter the name of the backup file for the settings
here.
Settings
Enter the name of the backup file for the system
data and the root file system here.
System
If you have backed up the data in encrypted form,
Decryption
select this checkbox.
Enter the encryption password here.
Decryption passphrase This input field only appears if the “Decryption”

identical.
beforehand.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
File size must not exceed the size of the internal drive!
Note that the amount of data in the media/sd/copy/ directory must not exceed the
total size of the internal drive.
Restoration only possible from internal memory!

If the device was booted from the memory card, the firmware cannot be restored.
Reset by restore
A reset is performed when the system or settings are restored by CODESYS!
Connection loss through restore

If the restore changes the parameters of the ETHERNET connection, the WBM
may then no longer be able to open a connection to the device. You must call the
WBM again by entering the correct IP address of the device in the address line.
Note the restore time!

The restore process takes approx. 2 … 3 minutes.
After the restore process, the controller is restarted and is then ready for use
again.
Click the [Restore] button to start the restore operation.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.12 “Active System” Page
The settings for specifying the partition from which the system is started are
shown on the “Active System” page.
“Boot Device” Group
Table 147: WBM “Active System” Page – “Boot Device” Group

Boot Device
“System <n> (Internal Flash)” Groups
Table 148: WBM “Active System” Page – “System <n> (Internal Flash)” Group
Active This shows whether the system is active.
This shows whether the system should be active
Configured
after the next reboot.
The system status is displayed here.
good The system is valid and can be used.
State
The system is not valid and cannot be
bad
used.
Click the respective [Activate] button to start the required system at the next
reboot.
Provide a bootable system!

A functional firmware backup must be available on the boot system!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.13 “Mass Storage” Page
The “Mass Storage” page displays information and settings for the storage
media.
The group title contains the designation for the storage media (“Memory Card” or
“Internal Flash”) and, if this storage medium is also the active partition, the text
“Active Partition”.
“Devices” Group
An area with information on the storage medium is displayed for each storage
medium found.
Table 149: WBM “Mass Storage” Page – “Devices” Group

<Device> The storage medium is displayed.
This shows whether the device has booted from this
Boot device
storage medium.
Volume name The name of the storage medium is displayed.
“Create new Filesystem on Memory Card” Group
Table 150: WBM “Mass Storage” Page – “Create new Filesystem on Memory Card” Group
Parameter Meaning
You can select the format in which the filesystem
should be created on the memory card.
Filesystem type The filesystem is created in Ext4 format.
Ext4
The files are not readable under Windows!
FAT The filesystem is created in FAT format.
Specify the name for the storage medium when
Label
formatted.
Data is deleted!
Any data stored in the storage medium is deleted during formatting!
To format the specified storage medium, click [Start].
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.14 “Software Uploads” Page
On “Software Upload” page, you can install software packages on the product
from your PC.
Table 151: WBM “Software Uploads” Page – “Upload New Software” Group
Software file The file name of your selected software package is
displayed, as long as you have not yet transferred it
to the product.
If you have not yet selected a package, “Choose ipk
file...” appears. Click the input field and select a file
with a software package on your PC.
To install the package, click [Install].
The file with the software package is deleted from the device again after the
installation process. If this is not possible due to a processing error, it is deleted
no later than the next time the product restarts.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.15 “Configuration of Network Services” Page
The settings for various services are shown on the “Configuration of Network
Services” page.
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 increase cyber security, close all
ports and services not required by your application in the control components
(e.g., port 6626 for WAGO-I/O-CHECK, port 2455 for CODESYS V2 and port
11740 for e!COCKPIT).
“FTP” Group
Table 152: WBM “Configuration of Network Services” Page – “FTP” Group

Enable/disable the FTP service.
Service active
This service is disabled by default.
immediately.
“FTPES (explicit FTPS)” Group
Table 153: WBM “Configuration of Network Services” Page – “FTPS (explicit FTPS)” Group
Enable/disable the FTPS service.
Service active
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“HTTP” Group
Table 154: WBM “Configuration of Network Services” Page – “HTTP” Group

Enable/disable the HTTP service.
Service active
immediately.
Disconnection abort on disabling

If the HTTP service is disabled, the connection to the product may be interrupted.
In that case, reopen the page.
“HTTPS” Group
Table 155: WBM “Configuration of Network Services” Page – “HTTPS” Group

Service active
HTTPS service.
“I/O-CHECK” Group
Table 156: WBM “Configuration of Network Services” Page – “I/O-CHECK“ Group

Service active Enable/disable the WAGO-I/O-CHECK service.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.16 “Configuration of NTP Client” Page
The settings for the NTP service are shown on the “Configuration of NTP Client”
page.
“NTP Client Configuration” Group
Table 157: WBM “Configuration of NTP Client” Page – “NTP Client Configuration” Group
Service enabled Enable/disabled time update.
Update interval (sec) Specify the update interval of the time server.
Enter here the IP addresses of up to 4 time servers.
Time server No. 1 is queried first. If no data is
Time Server <n>
accessible via this server, time server No. 2 is
queried, etc.
The NTP servers assigned if necessary by DHCP
Additionally assigned (or BootP) are displayed. If no NTP server has been
(DHCP) assigned by DHCP (or BootP), “(No additional
servers assigned)” is displayed.
To update the time regardless of interval, click the [Update Time] button.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.17 “PLC Runtime Services” Page
The settings for various services of the runtime systems are displayed on the
“PLC Runtime Services” page.
“CODESYS V2” Group
This group only appears if the controller supports the CODESYS V2 runtime
system.
Table 158: WBM “PLC Runtime Services” Page – “CODESYS V2” Group
CODESYS 2 State
Enable or disable the CODESYS V2 Webserver for
Webserver enabled
the CODESYS web visualization.
Enable or disable the communication between the
Communication enabled CODESYS V2 runtime system and the
CODESYS V2 programming system.
Enter here the port number for communication with
Communication Port
the CODESYS V2 programming system. The default
Number
value is 2455.
Define here whether port authentication is enabled.
If this is enabled, the password specified under
Port authentication enabled
“General Configuration” must be entered when
logging in via CODESYS V2 IDE.
Click the [Submit] button to apply the change.

The change in authentication takes effect after the next restart.
All other changes take effect immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“e!RUNTIME” Group
This group only appears if the controller supports the e!RUNTIME runtime
system.
Table 159: WBM “PLC Runtime Services” Page – “e!RUNTIME” Group

This displays the status of the e!RUNTIME system
e!RUNTIME State
(enabled/disabled).
Enable or disable the Webserver for the
Webserver enabled
e!RUNTIME web visualization.
Enter here whether a login is required for connecting
Port authentication enabled to the device. The user name is admin and the
password specified at “General Configuration.”
Click the [Submit] button to apply the change.

The change in authentication takes effect after the next restart.
All other changes take effect immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.18 “SSH Server Settings” Page
The settings for the SSH service are shown on the “SSH Server Settings” page.
“SSH Server” Group
Table 160: WBM “SSH Server Settings” Page – “SSH Server” Group
Service active You can enable/disable the SSH server.
Port Number Enter the port number.
Allow root login You can enable or inhibit root access.
Allow password login Enable or disable the password query function.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.19 “DHCP Server Configuration” Page
The “DHCP Server Configuration” page displays the DHCP service settings.
“DHCP Server Configuration Bridge <n>” Group
Table 161: WBM “DHCP Server Configuration” Page – “DHCP Configuration Bridge <n>” Group
Enable or disable the DHCP service for the interface
Service active
X<n>.
Enter the start value of the available IP address
Start IP for Range
range.
Enter the end value of the available IP address
End IP for Range
range.
Specify the lease time here in seconds. 120 minutes
Lease time (min)
are entered by default.
This displays the static assignments of MAC IDs to
Static Hosts IP addresses. If no assignment was defined, “No
static hosts configured” is displayed.
You can add static MAC addresses or host names
Add Static Host
and IP addresses.
Enter a new static assignment, e.g.,
“01:02:03:04:05:06=192.168.1.20” or
MAC Address or Hostname
“hostname=192.168.1.20”.
You can enter 15 assignments or host names.
Enter the IP address.
Ip Address
You can enter 15 IP addresses.
immediately.
To accept a new assignment click the [Add] button. The change takes effect
immediately.
Click [Delete] to delete an existing assignment. The change takes effect

immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.20 “Configuration of DNS Server” Page
The “Configuration of DNS Server” page displays the DNS service settings.
“DNS Server” Group
Table 162: WBM “Configuration of DNS Server” Page – “DNS Server” Group
Service active You can enable/disable the DNS server service.
Select the operating mode of the DNS server.
Requests are buffered to optimize
Mode Proxy
throughput.
Relay All requests are routed directly.
This displays the names for IP addresses. If no
Static Hosts assignment was defined, “No static hosts
configured” is displayed.
You can add static IP addresses and host names
Add Static Host
below.
Enter a new static assignment,
IP Address e.g., “192.168.1.20:hostname”.
You can enter 10 assignments.
Hostname Enter a host name.
immediately.
To accept a new assignment click the [Add] button. The change takes effect
immediately.
Click [Delete] to delete an existing assignment. The change takes effect

immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.21 “Status overview” Page
On the “Status overview” page, you can find information about cloud access.
“Service” Group
Table 163: WBM “Status Overview” Page – “Service” Group

Version The cloud plug-in version is displayed.
“Connection <n>” Group
A group is displayed for each cloud access.
Table 164: WBM “Status Overview” Page – “Connection <n>” Group

The status of the cloud connectivity application is
Operation
displayed.
This shows how many data collections have been
Data from PLC Runtime registered on the IEC application side for transfer to
the cloud.
The status of the connection to the cloud service is
Cloud Connection
shown.
This shows the current heartbeat interval setting in
Heartbeat
seconds.
Telemetry Data This indicates whether transfer of data is enabled or
Transmission disabled.
Cache fill level This shows the fill level of the memory cache for
(QoS 1 and 2) outgoing messages as a percentage.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.22 “Configuration of Connection <n>” Page
You can find settings and information for cloud access on the “Configuration of
Connection <n>” page.
A page is displayed for each cloud access.
“Configuration” Group
The parameters indicated depend on the cloud platform setting and, if applicable,
on other settings in this group.
The dependencies are shown in a separate table.
Table 165: WBM “Configuration of Connection <n>” Page – “Configuration” Group

You can enable/disable the cloud connectivity
Enabled
function.
Cloud platform Select the cloud platform.
Enter the host name or IP address for the selected
Hostname
cloud platform.
Enter the port here to which a connection is to be
established.
Port number
Typical values are 8883 for encrypted connections
and 1883 for unencrypted connections.
Device ID Enter the device ID for the selected cloud platform.
Client ID Enter the client ID for the selected cloud platform.
Select the authentication method.
Authentication Possible settings are “Shared Key Access” or “X.509
Certificate”.
Enter the activation key for the selected cloud
Activation Key
platform.
Specify whether clean session should be enabled
during the connection to the cloud service. If clean
Clean Session session is enabled, the information and messages
on this connection are not stored persistently on the
cloud service.
You can specify whether TLS encryption should be
TLS used for the connection to the cloud platform.
Amazon Web Services (AWS) always uses TLS.
Enter the path here to the file encoded in PEM
format that contains the trusted CA certificate to use
to establish an encrypted connection. The default
CA file
value is the CA certificate /etc/ssl/certs/ca-
certificates.crt that is already installed on the
controller.
Enter the user name for cloud service
Users
authentication.
Password Enter the password for cloud service authentication.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Enter the path here to the file encoded in PEM
Certification file
format that is used for cloud service authentication.
Enter the path to the file encoded in PEM format that
Key file contains the private key for cloud service
authentication.
Here, you can specify whether the connection to the
cloud platform is to be set up using the Websocket
protocol via Port 443.
Use websockets
If this checkbox is not selected, the connection to
the cloud platform is set up using the MQTT protocol
via Port 8883.
Proxy Type Select which type of proxy should be used.
HTTP Proxy Host Enter the host name or IP address of the proxy.
HTTP Proxy Port Enter the port number of the proxy.
HTTP Proxy User Enter the name of the proxy user.
HTTP Proxy Password Enter the password for the proxy user.
Here, you can set whether the data is to be
Use compression
compressed using GZIP compression.
Data Protocol Here you can select the data protocol.
Specify in which memory the cache for the data
telegrams should be created.
Cache mode This selection field is only enabled if a correctly
formatted SD card is inserted (more information is
available in Application Note A500920).
You can specify whether a last will message should
Last Will
be enabled/disabled.
You can specify the topic under which the last will
(Last Will) Topic
messages should be sent.
You can enter the message you wish to use as the
(Last Will) Message
last will message.
You can specify the “Quality of Service” (QoS) of the
(Last Will) QoS
last will message.
Here, you can set whether the previous last-will
(Last Will) Retain message sent under a topic from the broker is to be
handled as a retained message.
Specify whether a device info message should be
generated that informs the cloud service of the basic
Device info
configuration of the controller (more information is
available in the Application Note A500920).
Specify whether device state messages should be
generated that inform the cloud service about
Device status changes in the mode selector switch and the LEDs
(more information is available in the Application
Note A500920).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Specify whether the integrated standard commands
should be supported (list of standard commands is
Standard commands available in the Application Note A500920).
If the checkbox is disabled, only the commands
defined in the IEC program are supported.
You have the option of creating your own property
for the individual MQTT messages to the Azure
cloud.
This parameter is optional; i.e., if the field is left
blank, this property is not sent.
The following placeholders are available to create
Application property this property:
template • <m>: Message type
• <p>: Protocol version
• <d>: Device ID
Examples:
• MyKey=HelloWorld_<m>
• TestKey=<m>/<p>/<d>
• DeviceId=<d>
The changes only take effect after the controller restarts. For this purpose, use
the WBM reboot function. Do not shut down the controller too early!
The following tables show the dependencies of the selection and input fields as
well as the possible settings.
Table 166: Display of the Selection and Input Fields Depending on the Selected Cloud Platform
Cloud Platform
Web Services
AnyCloud
Services
Amazon
SAP IoT
WAGO
Cloud
Cloud
MQTT
Azure
Selection or Input Field

IBM
Enabled X X X X X X
Cloud platform X X X X X X
Hostname X X X X X X
Port number X X (X) X
Device ID X X
Client ID X X X X
Authentication X
Activation Key X X2
Clean Session X (X) (X) X
TLS X X (X) X
CA file X X X X
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 166: Display of the Selection and Input Fields Depending on the Selected Cloud Platform
Cloud Platform
Web Services
AnyCloud
Services
Amazon
SAP IoT
WAGO
Cloud
Cloud
MQTT
Azure
IBM
User X X
Password X X
Certification file X2 X X X
Key file X2 X X X
Use websockets X X1
Proxy Type X4 X4
HTTP Proxy Host X5 X5
HTTP Proxy Port X5 X5
HTTP Proxy User X5 X5
HTTP Proxy Password X5 X5
Data Protocol X X X X (X)
Use compression X X1 X1
Cache mode X X X X X X
Last Will X X X X
Last Will Topic X3 X3 X3 X3
Last Will Message X3 X3 X3 X3
Last Will QoS X3 X3 X3 X3
Last Will Retain X3 X3 (X3) X3
Device info X1 X1 X1 X1
Device status X1 X1 X1 X1
Standard commands X1 X1 X1
Application property template X1
X: Visible and enabled
(X): Visible, but disabled
X1: Visible and enabled, depending on the selected data protocol
X2: Visible and enabled, depending on the selected authentication
X3: Visible and enabled when “Last Will” is switched on
(X3): Visible, but disabled when “Last Will” is switched on
X4: Enabled if “Use websockets” is switched on.
X5: Visible and enabled if “Use websockets” is switched on and if “HTTP” is
set as the “Proxy Type”.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 167: Choice of Data Protocol Depending on the Selected Cloud Platform
Cloud Platform
Web Services
AnyCloud
Services
Amazon
SAP IoT
WAGO
Cloud
Cloud
MQTT
Azure
Data Protocol
IBM
WAGO Protocol X X X X
WAGO Protocol 1.5 X X X X
Native MQTT X X X (X)
Sparkplug payload B X X X
X: Selection possible
(X): Fixed setting
Table 168: Display of the Selection and Input Fields Depending on the Selected Data Protocol
Data Protocol
Protocol 1.5
Sparkplug
payload B
Protocol
WAGO
WAGO
Native
MQTT
Client ID X X X X
Use compression X X X
Device info X X
Device status X X
Standard commands X X
Application property template X X
Table 169: Choice of Cache Mode Depending on the Selected Data Protocol
Data Protocol
Protocol 1.5
Sparkplug
payload B
Protocol
WAGO
WAGO
Native
MQTT
Cache Mode
RAM X X X (X)
SD-Card X1 X1 X1
X: Selection possible
X1: Selection only possible if “Compression” is not switched on
(X): Fixed setting
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 170: Display of the Selection and Input Fields Depending on the Selected Authentication
Authentication
Certificate
Access
Shared
X.509
Key
Activation Key X
Certification file X
Key file X
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.23 “Configuration of General SNMP Parameters” Page
The general settings for SNMP are given on the “Configuration of General SNMP
Parameters” page.
“General SNMP Configuration” Group
Table 171: WBM “Configuration of General SNMP Parameters” Page – “General SNMP
Configuration” Group
Service active Activate/deactivate the SNMP service.
Name of device Enter here the device name (sysName).
Description Enter here the device description (sysDescription).
Physical location Enter here the location of the device (sysLocation).
Contact Enter here the email contact address (sysContact).
Object ID Enter here the object ID (sysOID).
Click the [Submit] button to apply the changes. The changes only take effect
after restarting the controller. For this purpose, use the WBM reboot function. Do
not shut down the controller too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.24 “Configuration of SNMP v1/v2c Parameters” Page
The general settings for SNMP v1/v2c are shown on the “Configuration of SNMP
v1/v2c Parameters” page.
“SNMP v1/v2c Manager Configuration” Group
Table 172: WBM “Configuration of SNMP v1/v2c Parameters” Page – “SNMP v1/v2c Manager
Configuration” Group
It is displayed the SNMP protocol for v1/v2c is
Protocol enabled enabled. The local community name is deleted when
the protocol is disabled.
Specify the community name for the SNMP
manager configuration. The community name can
establish relationships between SNMP managers
and agents who are respectively referred to as
“Community” and who control identification and
Local Community Name access between SNMP participants.
The community name can be up to 32 characters
long and must not include spaces.
To use the SNMP protocol, a valid community name
must always be specified. The default community
name is “public.”
after the controller restarts. For this purpose, use the WBM reboot function. Do
not shut down the controller too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“Actually configured Trap Receivers” Group
Table 173: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Actually Configured Trap
Receivers” Group
Parameters Meaning
Each configured trap receiver has its own area in the display. If no trap receiver
has been configured, “(no trap receivers configured)” is displayed.
The IP address for the trap receiver (management
IP Address
station) is displayed.
This displays the community name for the trap
Community Name receiver configuration. The community name can be
evaluated by the trap receiver.
This displays the SNMP version, via which the traps
Version are sent: v1 or v2c (traps higher than v3 are
displayed in a separate form).
Add new Trap Receiver In this area, you can enter a new trap receiver.
Specify the IP address for the new trap receiver
IP Address
(management station).
Specify the community name for the new trap
receiver configuration. The community name can be
Community Name evaluated by the trap receiver.
The community name can be up to 32 characters
long and must not include spaces.
Specify the SNMP version that will send the traps:
Version v1 or v2c (traps higher than v3 are configured in a
separate form).
Click the corresponding [Delete] button to delete an existing trap receiver.
Click the [Add] button to add a new trap receiver.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.25 “Configuration of SNMP v3 Users” Page
The general settings for SNMP v3 are shown on the “Configuration of SNMP v3
Users” page.
“Actually configured v3 Users” Group
Table 174: WBM “Configuration of SNMP v3” Page – “Actually configured v3 Users” Group
Parameters Meaning
Each configured v3 user has its own area in the
User <n> display. If no v3 user has been configured, “(no trap
receivers configured)” is displayed.
Security Authentication
The user name is displayed.
Name
The authentication type for the SNMP v3 packets is
displayed.
Authentication Type
Possible values:
- Use no authentication (“None”)
- Message Digest 5 (“MD5”)
- Secure Hash Algorithm (“SHA”)
Authentication Key The authentication key is displayed.
The encryption algorithm for the SNMP message is
displayed.
Privacy
Possible values:
- No encryption (“None”)
- Data Encryption Standard (“DES”)
- Advanced Encryption Standard (“AES”)
The key for encryption of the SNMP message is
Privacy Key displayed. If nothing is displayed, the “authentication
key” is automatically used.
The IP address of a trap receiver for v3 traps is
Notification Receiver IP displayed. If no v3 traps are to be sent for this user,
this field remains blank.
In this area, you can enter a new v3 user. You can
Add new v3 User
create up to 10 users.
Enter the user name. This name must be unique; a
pre-existing user name is not accepted when
Security Authentication entered. The name must be min. 8 and max. 32
Name characters long and contain lower case letters
(a … z), upper case letters (A … Z), numbers
(0 … 9), special characters !()*~'.-_ but no spaces.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 174: WBM “Configuration of SNMP v3” Page – “Actually configured v3 Users” Group
Parameters Meaning
Specify the authentication type for the SNMP v3
packets.
Authentication Type
Possible values:
- Use no authentication (“None”)
- Message Digest 5 (“MD5”)
- Secure Hash Algorithm (“SHA”)
Specify the authentication key. The key must be
min. 8 and max. 32 characters long and contain
Authentication Key (min. 8
lower case letters (a … z), upper case letters
char.)
(A … Z), numbers (0 … 9), special characters !()*~'.-
_ but no spaces.
Specify the encryption algorithm for the SNMP
message.
Privacy
Possible values:
- No encryption (“None”)
- Data Encryption Standard (“DES”)
- Advanced Encryption Standard (“AES”)
Enter the key for encryption of the SNMP message.
If nothing is specified here, the “authentication key”
is automatically used. The key must be min. 8 and
Privacy Key (min. 8 char.)
max. 32 characters long and contain lower case
letters (a … z), upper case letters (A … Z), numbers
(0 … 9), special characters !()*~'.-_ but no spaces.
Specify an IP address for a trap receiver for v3
Notification Receiver IP traps. If no v3 traps are to be sent for this user, this
field remains blank.
Click the respective [Delete] button to delete an existing user.
Click [Add] to add a new user.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.26 Page “Docker® Settings”
On the page “Docker® Settings”, see the settings for the "Docker®" service.
Group “Docker® Status”
Table 175: WBM Page “Docker® Settings” – group “Docker® Status”

Parameter Meaning
If you want to install the “Docker®” service, check
Service Installed
this box.
If you want to enable the “Docker®” service, check
Service Active
this box.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.2.27 “WBM User Configuration” Page
The settings for user administration are displayed on the “WBM User
Configuration” page.
“Change Password” Group
Changing Passwords
The initial passwords as delivered are documented in this manual and therefore
do not provide sufficient protection. Change the passwords to meet your
particular needs!
Table 176: WBM “WBM User Configuration” Page – “Change Password” Group
Old Password Enter the current password here for authentication.
Enter the new password here.
Permitted characters for the password are the
New Password following ASCII characters: a … z, A … Z, 0 … 9,
blank spaces and special characters:
!?%+=()_ #"-/`<>*;,:.
Confirm Password Enter the new password again here for confirmation.
immediately.
Note the permitted characters for WBM passwords!

If passwords with invalid characters are set for the WBM outside the WBM (e.g.,
from a USB keyboard), access to the pages directly on the display is no longer
possible because only permitted characters are available from the virtual
keyboard.

The WBM users “admin” and “user” have rights beyond the WBM to configure the
system and install software.
User administration for controller applications is configured and managed

separately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3 “Fieldbus” Tab
19.1.1.3.1 “OPC UA Status” Page
You can find the status information on the OPC UA service on the “OPC UA
Status” page.
“OPC UA Server” Group
Table 177: WBM “OPC UA Status” Page – “OPC UA Server” Group

The current status (enabled / disabled) of the
State
WAGO OPC UA server is displayed.
The installed version of the WAGO OPC UA Server
Version
is displayed here.
Any existing OPC UA server license is displayed.
License Some features of the WAGO OPC UA server require
a paid special license.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.2 “OPC UA Configuration” Page
The settings for the OPC UA service are shown on the “OPC UA Configuration”
page.
“General OPC UA Server Configuration” Group
Table 178: WBM “OPC UA Configuration” Page – “General OPC UA Server Configuration” Group
Service enabled Enable or disable the WAGO OPC UA Server here.
Enter the configuration names the controller
Ctrl Configuration name
contains in the PLC Open Device Set.
Select the log level. The following values can be set:
Info / Debug / Warning / Error.
With log level “Error,” only error messages are read
Log level out; with log level “Info,” status messages are read
out too. The specific log level selection affects
server reaction time. Therefore, select the lowest
level necessary; e.g., “Debug” for in-depth analyses.
Access rights to the data provided by the server are
set here.
Unlimited anonymous An unregistered user can view, read
Enabled
access and write all variables.
Complete access to the data requires
Disabled
user logon with the appropriate rights.
Click the [Submit] button to apply the changes.
Group “OPC UA Endpoint URL”
Table 179: WBM page “OPC UA Configuration” – group “OPC UA Endpoint URL”
Parameter Meaning
Select the endpoint URL of the OPC UA server. The
Interface
hostname or a bridge or IP address is possible.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“OPC UA Endpoints” Group
Table 180: WBM “OPC UA Configuration” Page – “OPC UA Endpoints” Group

Parameter Meaning
Enable or disable the OPC UA endpoint “None”.
Security Policy - None This allows an unsecured connection to the OPC UA
server to be established.
Enable or disable the “Basic128Rsa15” security
Security Policy - policy.
Basic128Rsa15 Note:
This policy is no longer classified as secure.
The “Basic256Sha256” security policy allows a
Security Policy -
secure connection to be established with the OPC
Basic256Sha256
UA server.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“OPC UA Security Settings” Group
Table 181: WBM Page “OPC UA Configuration” – “OPC UA Security Settings” Group
The verification is enabled or disabled here.
A connection to all clients is
Enabled
Trust all clients permitted.  No security!
Connection is only allowed to clients
Disabled
with secure certificates.
The URI check can be enable or disable here.
A disabled URI check enables connection to an
URI Check Application
OPC server even if the URI on the server URI is
different from the URI in the certificates.
The time can be enabled or disabled here.
Certificates may have an expiration date. This date
Error Certificate Time is checked against the current usage time on the
device. The check cannot be run successfully if the
time is incorrectly set on the device.
The time stamp check can be enabled or disabled
here.
CA certificates contain a validity time stamp from the
Certificate Issuer Time
manufacturer. This stamp is used when checking
Invalid
the time on the server hardware. If the time setting
on the server hardware is incorrect or is missing
entirely, the certificate may be indicated as invalid.
The accessibility check of the saving location for
withdrawn certificates can be enabled or disabled
here.
Certificate Revocation
Each certificate can have a location for withdrawn
Unknown
certificates. If network problems or other causes
prevent access to the specified location, the
certificate is not accepted.
The accessibility check of the storage location for
withdrawn certificates can be enabled or disabled
here.
Certificate Issuer
Each certificate of a certification location (CA
Revocation Unknown
certificate) can contain an entry for the withdrawn
certificate saving location. If the location cannot be
reached, the server will refuse the certificate.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.3 “OPC UA Information Model” Page
You can find the settings for the OPC UA information module on the “OPC UA
Information Model” page.
The page is only visible on products that support software components that are
subject to a license check (runtime licenses).
“OPC UA Server Information Model” Group
Table 182: WBM “OPC UA Information Model” Page – “OPC UA Server Information Model” Group
Parameter Meaning
Enable or disable the OPC UA Server information
Feature enabled
model.
Select an XML description file for the information
model to be used.
The WAGO OPC UA Mapping Editor can be used to
create the XML description file.
informationmodel.xml
Using a specific information model requires an
extended OPC UA license!
Current information on the currently available OPC
UA licenses can be found on the WAGO Web site.
To transfer the selected description file to the controller, click the [Upload]
button.
To delete the installed description file from the controller, click the [Delete]
button. After deletion, the default PLC Open information model is used again.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.4 “OPC UA Server Certificates” Page
The “OPC UA Server Certificates” provides options to install or delete OPC UA

server certificates and keys.
“OPC UA Server Own Certificate” Group
Table 183: WBM Page “OPC UA Server Certificates” – “OPC UA Server Own Certificate” Group
Parameter Meaning
The certificate currently used by the server is
<certificate name>
displayed. If no certificate is being used, “No
e.g., “certificate.der”
certificates existing” is displayed.
To delete the certificate, click the [Delete] button. The change applies
immediately.
To select a certificate file on the PC, click the Choose file … selection field.
To transfer the selected certificate file to the product, click the [Upload] button.
The change applies immediately.
“OPC UA Server Private Keys” Group
Table 184: WBM Page “OPC UA Server Certificates” – “OPC UA Server Private Keys” Group
Parameter Meaning
<private key name> The key currently used is displayed. If not key has
e.g., “key.pem” been loaded, “No private keys existing” is displayed.
To delete the key, click the [Delete] button. The change applies immediately.
To select a key file on the PC, click the Choose file … selection field.
To transfer the selected key file to the product, click the [Upload] button. The
change applies immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“OPC UA Server Trusted / Rejected Certificates” Group
Table 185: WBM Page “OPC UA Server Certificates” – “OPC UA Server Trusted / Rejected
Certificates” Group
Parameter Meaning
The certificates of clients marked as trustworthy are
Trusted listed in this area. If not certificate exists, “No
This area lists the certificates of OPC UA devices
that have not yet been classified as trustworthy or
Rejected that have been marked as “Rejected”. If not
certificate exists, “No certificates existing” is
displayed.
To move a certificate from the “Trusted” area to the “Rejected” area, click the
[Reject] button. The change applies immediately.
To delete a certificate, click the [Delete] button. The change applies immediately.
The change applies immediately. The loaded certificate is first listed in the
“Rejected” area.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.5 OPC UA Client Certificates” Page
On the “OPC UA Client Certificates” page, you find options to install or delete
OPC UA client certificates and keys.
“OPC UA Client Own Certificate” Group
Table 186: WBM Page “OPC UA Client Certificates” – “OPC UA Client Own Certificate” Group
Parameter Meaning
The certificate currently used by the client is
<certificate name>
displayed. If no certificate is being used, “No
e.g., “certificate.der”
To delete the certificate, click the [Delete] button. The change applies
immediately.
The change applies immediately.
“OPC UA Client Private Keys” Group
Table 187: WBM Page “OPC UA Client Certificates” – “OPC UA Client Private Keys” Group
Parameter Meaning
<private key name> The key currently used is displayed. If not key has
e.g., “key.pem” been loaded, “No private keys existing” is displayed.
To delete the key, click the [Delete] button. The change applies immediately.
To select a key file on the PC, click the Choose file … selection field.
To transfer the selected key file to the product, click the [Upload] button. The
change applies immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“OPC UA Client Trusted / Rejected Certificates” Group
Table 188: WBM Page “OPC UA Client Certificates” – “OPC UA Client Trusted / Rejected
Certificates” Group
Parameter Meaning
Trusted that the client trusts. If not certificate exists, “No
that have not yet been classified as trustworthy or
Rejected that have been marked as “Rejected”. If not
certificate exists, “No certificates existing” is
displayed.
To move a certificate from the “Trusted” area to the “Rejected” area, click the
[Reject] button. The change applies immediately.
To delete a certificate, click the [Delete] button. The change applies immediately.
The change applies immediately. The loaded certificate is first listed in the
“Rejected” area.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.6 “MODBUS Services Configuration” Page
The “Modbus Services Configuration” page displays the settings for various
Modbus® services. The groups only appear if the e!RUNTIME system is
enabled. Otherwise an information text is displayed.
“Modbus TCP Slave” Group
Table 189: WBM “Modbus Services Configuration” Page – “Modbus TCP” Group
Service active Disable or enable the Modbus/TCP service.
Click the [Submit] button to apply the changes. The change takes effect
immediately.
“Modbus UDP Slave” Group
Table 190: WBM “Modbus Services Configuration” Page – “Modbus UDP” Group
Service active Disable/enable the Modbus UDP service.
Click the [Submit] button to apply the changes. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.7 “BACnet Status” Page
The “BACnet Status” page displays BACnet fieldbus and BACnet license specific
information about your controller.
“BACnet Information” Group
Table 191: WBM Page “BACnet Status” – “BACnet Information” Group

Parameter Meaning
This group shows whether the BACnet fieldbus is
State
enabled or disabled.
Status Info The status of the BACnet fieldbus is displayed.
The current device ID of the controller is displayed

Device-ID
here.
“BACnet License” Group
Table 192: WBM Page “BACnet Status” – “BACnet License” Group

Parameter Meaning
Type The type of license is indicated here.
The number of possible BACnet objects allowed by

User Objects
this license is displayed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.8 “BACnet Configuration” Page
You can make special settings for the BACnet fieldbus on this page.
Click the [Submit] button to apply a setting.

Changes made to the BACnet configuration are not applied until after a restart.
Use the WBM Reboot function to restart the stack/controller. Click the [Restart]
button to restart the runtime. Do not shut down the controller too early!
“BACnet Service” Group
You can enable/disable the fieldbus in this group.
The “Service active” parameter must be enabled (default setting) for the BACnet
fieldbus protocol to be used.
On a runtime restart a security message is displayed in a pop-up window asking

if you really want to perform a restart.
Table 193: WBM Page “BACnet Configuration” – “BACnet Settings” Group

Parameter Meaning
Service active Enable/disable the BACnet fieldbus.
Runtime restart
Use this button to restart the runtime.
[Restart]
“BACnet Settings” Group
The basic settings for the fieldbus are given in this group.
Table 194: WBM Page “BACnet Configuration” – “BACnet Settings” Group

Parameter Meaning
Port number Set the port for BACnet fieldbus communication.
Here, you can specify the intervals at which the

Who-Is online interval time controller transmits queries to the fieldbus about
(sec) which other subscribers are online (minimum: 60
seconds).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“BACnet Data Reset” Group
In this group you can select the data to be deleted or reset on the next restart.
Table 195: WBM Page “BACnet Configuration” – “BACnet Data Reset” Group
Parameter Meaning
Persistent BACnet data is deleted on the next
Delete Persistence Data
restart.
Reset all BACnet Data and The factory default settings for BACnet-specific
Settings to Default settings and data is restored on the next restart.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.9 “BACnet Storage Location” Page
You can specify settings for saving of BACnet-specific parameters on this page.
Changes are applied without having to restart.
“BACnet Persistence” Group
This group lets you select the storage location (SD card/internal flash) for the
persistence data.
If the persistence settings are changed, a pop-up window warns that data loss
may occur until the next persistence is completed.
Table 196: WBM Page “BACnet Storage Location” – “BACnet Persistence” Group
Parameter Meaning
You can select the storage location for the
persistence data.
Selection is possible only when both storage options
are available.
Data will be stored in the controller's
Internal-Flash
internal memory.
Storage location
Data will be stored on the SD card.
If “SD card” has been selected and
the card is no longer inserted, this
SD-Card
option is no longer enabled and only
the “internal flash” option can be
selected.
“BACnet Trendlog” Group
trend log data.
Table 197: WBM Page “BACnet Storage Location” – “BACnet Trendlog” Group
Parameter Meaning
You can select the storage location for the trend log
data.
are available.
Internal-Flash
internal memory.
Storage location
SD-Card
selected.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“BACnet Eventlog” Group
event log data.
Table 198: WBM Page “BACnet Storage Location” – “BACnet Eventlog” Group
Parameter Meaning
Select the storage location for the event log data
here.
are available.
Internal-Flash
internal memory.
Storage location
SD-Card
selected.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.3.10 “BACnet Files” Page
You can exchange an override file in the controller on this page.
“BACnet override.xml” Group
Table 199: WBM Page “BACnet Files” – “BACnet override.xml” Group

Parameter Meaning
Choose file… Select the desired file on the controller or PC here.
Use this button to transfer the selected file from the
[Upload]
PC to the controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4 “Security” Tab
19.1.1.4.1 “OpenVPN / IPsec Configuration” Page
The “OpenVPN / IPsec Configuration” page displays the settings for OpenVPN
and IPsec.
“OpenVPN” Group
Table 200: WBM “OpenVPN / IPsec Configuration” Page – “OpenVPN” Group

The current status of the OpenVPN service is
displayed.
Current State
stopped The service is disabled.
running The service is enabled.
OpenVPN enabled Enable or disable the OpenVPN service.
Select an OpenVPN configuration file to be
openvpn.config
transferred from PC to product or vice versa.
To select a file on the PC, click the Choose file … selection field.
To transfer the selected file from the PC to the product, click [Upload] button.
To transfer a file from product to PC, click the [Download] button.
The changes only take effect after the product restarts. For this purpose, use the
WBM reboot function. Do not switch off the product too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“IPsec” Group
Table 201: WBM “OpenVPN / IPsec Configuration” Page – “IPsec” Group

The current status of the IPsec service is displayed.
Current State stopped The service is disabled.
running The service is enabled.
IPsec enabled Enable or disable the IPsec service.
Select an IPsec configuration file to be transferred
ipsec.conf
from PC to product or vice versa.
Select an IPsec configuration file to be transferred
ipsec.secrets
from PC to product or vice versa.
To transfer the selected file from the PC to the product, click [Upload] button.
To transfer a file from product to PC, click the [Download] button.
The changes only take effect after the product restarts. For this purpose, use the
WBM reboot function. Do not switch off the product too early!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.2 “General Firewall Configuration” Page
The “General Firewall Configuration” page displays the global firewall settings.
“Global Firewall Parameter” Group
Table 202: WBM “General Firewall Configuration” Page – “Global Firewall Parameter” Group
Enables/disables the complete functionality of the
firewall. This setting has the highest priority. If the
firewall is disabled, all other settings have no direct
effect. The configuration of the other parameters is
possible nevertheless so that you can set the
Firewall enabled entirely firewall parameters correctly before you enable the
firewall.
This setting is independent of the “Filter enabled”
setting in the “MAC address filter state bridge <n>”
group on the “MAC address filter state bridge <n>”
page.
ICMP echo broadcast Enable or disable the “ICMP echo broadcast”
protection protection.
Max. UDP connections per You can specify the maximum number of UDP
second connections per second.
Max. TCP connections per You can specify the maximum number of TCP
second connections per second.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.3 “Interface Configuration” Page
The individual interfaces for the firewall settings are displayed on the “Interface
Configuration” page.
“Firewall Configuration Bridge <n> / VPN / WAN” Group
A separate group is displayed for each configured bridge.

The settings in this group are based on the firewall configuration on the IP level.
Table 203: WBM “Interface Configuration” Page – “Firewall Configuration Bridge <n> / VPN / WAN”
Group
Firewall enabled for Enable or disable the firewall for the respective
Interface bridge.
Enable or disable the “ICMP echo” protection for the
ICMP echo protection
respective bridge.
You can specify the maximum number of “ICMP
ICMP echo limit per second pings” per second.
“0” = “Disabled”
ICMP burst limit
echo bursts” per second.
(0 = disabled)
FTP/FTPES
FTPS (implicit)
HTTP
HTTPS
I/O-CHECK
PLC Runtime
PLC WebVisu – Enable or disable the
direct link (port 8080) firewall for the
SSH respective service.
BootP/DHCP The services
Service enabled themselves must be
DNS
enabled or disabled
Modbus TCP separately on the
Modbus UDP “Ports and Services”
SNMP page.
OPC UA
BACnet (Port 47808)
PROFINET IO
DNP3 (port 20000)
IEC60870-5-104 (port 2404)
IEC61850 (port 102)
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.4 “Configuration of MAC Address Filter” Page
The “Configuration of MAC address filter” page displays the firewall configuration
on the ETHERNET level.
The “MAC Address Filter Whitelist” contains a default entry with the following
values:
MAC address: 00:30:DE:00:00:00

MAC mask: ff:ff:ff:00:00:00
If you enable the default entry, this already allows communication between
different WAGO devices in the network.
Enable the MAC address filter before activation!

Before activating the MAC address filter, you must enter and activate your own
MAC address in the “MAC Address Filter Whitelist.”
Otherwise you cannot access the device via the ETHERNET. This also applies to
other services that are used by your device, e.g., the IP configuration via DHCP.
If the “MAC Address Filter Whitelist” does not contain the MAC address of your
DHCP server, your device will lose its IP settings after the next refresh cycle and
is then no longer accessible.
If the “MAC Address Filter Whitelist” does not contain an entry, the activation of
the filter is prevented.
If at least one enabled address is entered, you will receive an appropriate
warning before activation, which you have to acknowledge.
The check described above is only performed in the WBM but not in the CBM!
“Global MAC address filter state” Group
Table 204: WBM “Configuration of MAC Address Filter” Page – “Global MAC address filter state”
Group
Filter enabled Enable or disable the global MAC address filter.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
“MAC address filter state Bridge <n>” Group
A separate group is displayed for each configured bridge.
Table 205: WBM “Configuration of MAC Address Filter” Page – “MAC address filter state Bridge <n>”
Group
Enable or disable here the MAC address filter for the
specific bridge.
Filter enabled This setting is independent of the “Firewall enabled
entirely” setting on the General Firewall
Configuration page.
immediately.
“MAC address filter whitelist” Group
Each list entry has its own area in the display.
Table 206: WBM “Configuration of MAC Address Filter” Page – “MAC address filter whitelist” Group
MAC address Displays the MAC address of the relevant list entry.
This displays the MAC mask of the relevant list
MAC mask
entry.
Filter enabled Enable or disable the filter for the relevant list entry.
Add filter to whitelist Create a new list entry.
Enter here the MAC address for a new list entry.
MAC address
You can enter 10 filters.
MAC mask Enter the MAC mask for the new list entry.
Filter enabled Enable or disable the filter for the new list entry.
immediately.
Click the appropriate [Delete] button to remove an existing list entry. The change
takes effect immediately.
Click [Add] to accept a new list entry. You can enter 10 filters. The change takes
effect immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.5 “Configuration of User Filter” Page
The “Configuration of User Filter” page displays the settings for custom firewall
filters.
“User filter” Group
Each configured filter has its own area in the display.
Table 207: WBM “Configuration of User Filter” Page – “User Filter” Group
Parameters Meaning
This displays whether the network participant is
Policy
permitted or excluded by the filter.
The source IP address for the respective filter is
Source IP address
displayed.
This displays the source netmask for the respective
Source Netmask
filter.
The source port number for the respective filter is
Source Port
displayed.
The destination IP address for the respective filter is
Destination IP address
displayed.
The destination netmask for the respective filter is
Destination Netmask
displayed.
The destination port number for the respective filter
Destination Port
is displayed.
The permitted protocols for the respective filter is
Protocol
displayed.
The permitted interfaces for the respective filter are
Input interface
displayed.
You can create up to 10 filters.
You only have to enter values in the fields that are to
Add new user filter
be set for the filter. At least one value must be
entered, all other fields can remain empty.
Select here whether the network devices is to be
allowed or excluded by the filter.
Policy
Allow The network device is permitted.
Drop The network device is excluded.
Source IP address Enter here the source IP address for the new filter.
Enter here the source network mask for the new
Source netmask
filter.
Source port Enter here the source port address for the new filter.
Enter here the destination IP address for the new
Destination IP address
filter.
Enter here the destination network mask for the new
Destination subnet mask
filter.
Enter here the destination port address for the new
Destination port
filter.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 207: WBM “Configuration of User Filter” Page – “User Filter” Group
Parameters Meaning
Enter here the protocols for the new filter.
TCP/ The TCP service and UDP service are
Protocol UDP filtered.
TCP The TCP service is filtered.
UDP The UDP service is filtered.
Enter here the interfaces for the new filter.
Any All interfaces are filtered.
The interfaces assigned for bridge <n> are
Input interface Bridge
filtered. Only the configured bridges are
<n>
displayed.
VPN The VPN interface is filtered.
Click [Add] to apply the new filter. The change takes effect immediately.
Click the [Delete] button to delete an existing filter. The change takes effect
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.6 “Certificates” Page
On the “Certificates” page, you will find options to install or delete certificates and
keys.
“Installed Certificates” Group
Table 208: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate List” Group
The loaded certificates are displayed. If no
<certificate name> certificate has been loaded. “No certificates existing”
is displayed.
To transfer the selected file PC to the product, click the [Upload] button. The
changes take effect immediately.
The certificates are stored in the directory “/etc/certificates/” and the keys in the
directory “/etc/certificates/keys/”.
Click [Delete] to delete an entry. The changes take effect immediately.
“Installed Private Keys” Group
Table 209: WBM “Configuration of OpenVPN and IPsec” Page – “Private Key List” Group
Parameters Meaning
The loaded keys are displayed. If no key has been
<private key name>
loaded, “No private keys existing” is displayed.
To transfer the selected file PC to the product, click the [Upload] button. The
changes take effect immediately.
The certificates are stored in the directory “/etc/certificates/” and the keys in the
directory “/etc/certificates/keys/”.
Click [Delete] to delete an entry. The changes take effect immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.7 “Boot mode configuration” Page
See the “Boot mode configuration” page for boot option settings.
“Force internal boot” Group
Table 210: WBM Page “Boot mode configuration” – “Force internal boot” Group
Parameter Meaning
You set the boot option for the product.
Memory card or You can boot from the internal
Boot mode internal flash flash or from the memory card.
Internal flash You can only boot from the internal
only flash.
If you force booting from the internal flash, the device can no longer be
booted from the memory card!
If a connection via ETHERNET is no longer possible due to problems or incorrect
configuration, you have the option of making the product accessible again via the
service interface and “WAGO Ethernet Settings”.
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.8 “Security Settings” Page
The network security settings are found on the “Security Settings” page.
“TLS Configuration” Group
Table 211: “Security Settings” WBM Page – “TLS Configuration” Group

You can set what TLS versions and cryptographic
methods are allowed for HTTPS.
The Webserver allows TLS 1.0,
TLS 1.1 and TLS 1.2, as well as
Standard
cryptographic methods that are no
TLS Configuration
longer considered secure.
The Webserver only allows TLS
Version 1.2 and strong algorithms.
Strong
Older software and older operating
systems may not support TLS 1.2.
immediately.
BSI TR-02102 Technical Guidelines

The rules for the “Strong” setting are based on the TR-02102 technical guidelines
of the German Federal Office for Information Security (BSI).
You can find the guidelines on the Internet at: https://www.bsi.bund.de >
“Publications” > “Technical Guidelines.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.9 “Advanced Intrusion Detection Environment (AIDE)” Page
The network security settings are available on the “Advanced Intrusion Detection
Environment (AIDE)” page.
“Run AIDE check at startup” Group
Table 212: WBM “Advanced Intrusion Detection Environment (AIDE)” Page – “Run AIDE check at
startup” Group
Here, you can activate/deactivate the “AIDE check”
Service active
when the controller is started.
when the controller restarts.
“Refresh Options” group
Table 213: WBM “Advanced Intrusion Detection Environment (AIDE)” Page – “Control AIDE and
show log” Group
Select here the action to be executed.
readlog The log data are displayed.
The database is initialized and filled with
init
the current values.
Select Action The current values are compared against
check
the values stored in the database.
The current values are compared with the
update values stored in the database and the
database then updated.
Activate display of only the last n messages. You
Read only the last n also specify the number of messages to be
displayed.
Select the checkbox to enable cyclic refresh.
Enter the cycle time in seconds in which a cyclic
Automatic refresh interval
refresh is performed. The label of the button
(sec)
(“Refresh”/“Start“/“Stop”) changes depending on
status.
Click [Refresh] to update the display. The button is only displayed if the cyclic
refresh is not enabled.
To enable cyclic refresh, click the [Start] button. The button is only displayed if
cyclic refresh is enabled and has not yet started.
To stop cyclic refresh again, click the [Stop] button. The button only appears if
cyclic refresh is enabled.
The cyclical refresh is performed for as long as the “Advanced Intrusion

Detection Environment (AIDE)” page is open. If you change the WBM page, the
Manual
750-8214 PFC200; G2; 2ETH RS CAN
update is stopped until you call up the “Advanced Intrusion Detection
Environment (AIDE)” page again.
The messages are displayed below the settings.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.4.10 “WAGO Device Access” Page
On the “WAGO Device Access” page you will find settings for authentication
when scanning the node.
Beta Status
In the present firmware version, the “WAGO Device Access” functionality is still in
beta!
“Unauthenticated Requests” Group
Table 214: WBM Page “WAGO Device Access” – “Unauthenticated Requests” Group
Parameter Meaning
You set whether the node can be scanned without
authentication.
In the default setting, authentication is switched off.
Allow unauthenticated
To increase the security level, you can enforce
Device Scan
authentication for node scanning.
In the current beta status, only head stations but no
I/O modules are recognized when scanning!
immediately.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.1.5 “Diagnostic” Tab
19.1.1.5.1 “Diagnostic Information” Page
The settings for displaying diagnostic messages are shown on the “Diagnostic
Information” page.
Table 215: WBM “Diagnostic Information” Page

Parameters Meaning
Activate display of only the last n messages. You
Read only the last also specify the number of messages to be
displayed.
Select the checkbox to enable cyclic refresh.
Enter the cycle time in seconds in which a cyclic
Automatic refresh interval
refresh is performed. The label of the button
(sec)
(“Refresh”/“Start“/“Stop”) changes depending on
status.
Select the source of the diagnostic messages.
The drop-down list depends on the user who is
logged in.
Source
user Default diagnostic messages only
Default diagnostic messages and all log
admin
files in the folder /var/log/*
To refresh the display or to enable cyclic refresh, click the [Refresh] button. This
button is only displayed if the cyclic refresh is not enabled.
To enable cyclic refresh, click the [Start] button. The button is only displayed if
cyclic refresh is enabled and has not yet started.
To stop cyclic refresh again, click the [Stop] button. The button only appears if
cyclic refresh is enabled.
The cyclical refresh is performed for as long as the “Diagnostic Information” page
is open. If you change the WBM page, the refresh is stopped until you call up the
“Diagnostic Information” page again.
The messages are displayed below the settings.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2 Console-Based-Management (CBM)
19.1.2.1 “Information” Menu
This menu contains other submenus with information on the controller and
network.
Table 216: “Information” Menu

Menu Item Explanation
0. Back to … Back to the higher-level menu
1. Controller Details Opens a submenu with controller properties
Opens a submenu with controller network and
2. Network Details
interface properties
To make a selection, choose the appropriate menu item.

To return to the higher-level menu, press [Q].
19.1.2.1.1 “Information” > “Controller Details” Submenu
In this submenu, the controller properties are displayed.
Table 217: “Information” > “Controller Details” Submenu

Product Description Controller identification
Order Number Item number of the controller
Notification that the CODESYS runtime system is
License Information
available
Firmware Revision Firmware status
To return to the higher-level menu, press [Q] or [Return].
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.1.2 “Information” > “Network Details” Submenu
In this submenu, the network and interface properties of the controller are
displayed.
If the EHERNET interfaces are operated in “Switched” mode, a common table

(“X1/X2”) is displayed for both connections.
If the EHERNET interfaces are operated in “Separated” mode, an individual table
(“X1” / “X2”) is displayed for each connection.
Table 218: “Information” > “Network Details” Submenu

Status of the ETHERNET interface
State
(enabled/disabled)
Mac Address MAC address identifies and addresses the controller
Current IP address of the controller and (in brackets)
IP Address
the reference type (static/bootp/dhcp)
Subnet Mask Current subnet mask of the controller
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2 “PLC Runtime” Menu
This menu contains other submenus with information and settings for the runtime
system.
Table 219: “PLC Runtime” Menu

Opens a submenu with information on the runtime
1. Information
system
Opens a submenu with settings for the runtime
system
Opens a submenu with settings for the Web
3. WebVisu
visualization

19.1.2.2.1 “PLC Runtime” > “Information” Submenu
This submenu contains other submenus with information on the runtime system
and PLC program.
Menu items 2 … 6 only appear if CODESYS V2 is set as the runtime system.
Table 220: “PLC Runtime” > “Information” Submenu

1. Runtime Version Opens a submenu to display the runtime version
2. Webserver Version Opens a submenu to display the Webserver version
Opens a submenu to display the PLC operating
3. State
state
Opens a submenu to display the number of tasks in
4. Number of Tasks
the PLC program
Opens a submenu to display the PLC program
5. Project Details
project information
Opens a submenu to display the tasks in the PLC
6. Tasks
program

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2.2 “Information” > “Runtime Version” Submenu
In this submenu, the runtime version is displayed.
Table 221: “PLC Runtime” > “Information” > “Runtime Version” Submenu
The version of the currently enabled runtime system
Version is shown. If the runtime system is disabled, “None”
is displayed.
19.1.2.2.3 “Information” > “Webserver Version” Submenu
In this submenu, the Webserver version is displayed.

The submenu only appears when CODESYS V2 is enabled as the runtime
system.
Table 222: “PLC Runtime” > “Information” > “Webserver Version” Submenu
Version The Webserver version is displayed.
19.1.2.2.4 “Information” > “State” Submenu
In this submenu, the PLC operating state is displayed.

system.
Table 223: “PLC Runtime” > “Information” > “State” Submenu

The PLC operating state is shown.
State STOP PLC program is not executed.
RUN PLC program is executed.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2.5 “Information” > “Number of Tasks” Submenu
In this submenu, the number of tasks in the PLC program are displayed.
system.
Table 224: “PLC Runtime” > “Information” > “Number of Tasks” Submenu
Number of Tasks The number of tasks in the PLC program is shown.
19.1.2.2.6 “Information” > “Project Details” Submenu
In this submenu, project information from the PLC program is displayed.

system and the program is executed.
Table 225: “PLC Runtime” > “Information” > “Project Details” Submenu
Date Display of project information that the programmer
Title entered in the PLC program (in the programming
software under Project > Project Information ...)
Version
Descriptive text with up to 1024 characters is
Author displayed under “Description”.
Description
19.1.2.2.7 “Information” > “Tasks” Submenu
In this submenu, tasks from the PLC program are displayed. An entry is
generated for each task.
system.
Table 226: “PLC Runtime” > “Information” > “Tasks” Submenu

Opens a submenu with information on the selected
n. Task n
task

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2.8 “Tasks” > “Task n” Submenu
In this submenu, information on the selected task is displayed.

system.
Table 227: “PLC Runtime” > “Information” > “Tasks” > “Task n” Submenu
Cycle count Number of task cycles since the system start
Cycle time (µsec) Currently measured task cycle time for the task
Minimum task cycle time for the task since the
Cycle time min (µsec)
system start
Maximum task cycle time for the task since the
Cycle time max (µsec)
system start
Cycle time avg (µsec) Average task cycle time since the system start
Status Task status (e.g., RUN, STOP)
Mode Task execution mode (e.g., in cycles)
Priority Set task priority
Interval (msec) Set task interval
19.1.2.2.9 “PLC Runtime” > “General Configuration” Submenu
This submenu contains other submenus with general settings for the runtime
system.
Table 228: “PLC Runtime” > “General Configuration” Submenu

Opens a submenu for the CODESYS runtime
1. PLC Runtime Version
system settings
2. Home Dir On SD Card Opens a submenu for the home directory settings

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2.10 “General Configuration” > “PLC Runtime Version” Submenu
In this submenu, select which PLC runtime system is enabled.
Table 229: “PLC Runtime” > “General Configuration” > “PLC Runtime Version” Submenu
1. None No runtime system is enabled.
2. CODESYS 2 The CODESYS V2 runtime system is enabled.
3. e!RUNTIME The e!RUNTIME runtime system is enabled.
All data is deleted when switching the runtime system!

The runtime system’s home directory is completely deleted when switching the
runtime system!

19.1.2.2.11 “General Configuration” > “Home Dir On SD Card” Submenu
In this submenu, define if the home directory for the runtime system should be
moved to the memory card.
Table 230: “PLC Runtime” > “General Configuration” > “Home Dir On SD Card” Submenu
1. Enable The home directory is moved to the memory card.
2. Disable The home directory is stored in the internal memory.
Insert a memory card before switching the home directory!

When moving the home directory to the memory card, insert a memory card
formatted to support file system. Only the first partition of a memory card can be
accessed at /media/sd and can be used as the home directory.
Perform a reset before switching the home directory!

Stop IEC-61131 applications in use before switching the home directory of the
runtime system.
Restore the device to its initial state using the “Reset” function. Any boot project
is deleted.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.2.12 “PLC Runtime” > “WebVisu” Submenu
This submenu contains information and settings for the Web visualization.
Table 231: “PLC Runtime” > “WebVisu” Submenu

Menu Item Submenu Item / Explanation
1. CODESYS 2 Webserver The status of the CODESYS V2 Webserver is
State displayed.
2. e!RUNTIME Webserver The status of the e!RUNTIME Webserver is
State displayed.
Choose here whether the Web-based Management
or web visualization of the runtime system should be
displayed when only entering the IP address of the
controller.
3. Default Webserver
1. Web-based
The Web-based Management is
Managem
displayed.
ent
2. CODESYS The web visualization of the runtime
WebVisu system is displayed.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3 “Networking” Menu
This menu contains other submenus with settings for the network configuration.
Table 232: “Networking” Menu

Opens a submenu with setting options for the
1. Host/Domain Name
general TCP/IP parameters
Opens a submenu with TCP/IP settings for the
2. TCP/IP
ETHERNET interfaces
Opens a submenu with settings for the ETHERNET
3. Ethernet
configuration

19.1.2.3.1 “Networking” > “Host/Domain Name” Submenu
This submenu contains the “Hostname” and “Domain Name” submenu with
setting options for the general TCP/IP parameters.
Table 233: “Networking” > “Host/Domain Name” Submenu

Opens a submenu with the hostname settings
1. Hostname In addition to the menu item, the configured and
current hostname are displayed.
Opens a submenu hostname settings
2. Domain Name In addition to the menu item, the configured and
current domain name are displayed.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.2 “Host/Domain Name” > “Hostname” Submenu
In this submenu, you can set the hostname of the controller.
Table 234: “Networking” > “Hostname” Submenu

Enter here the hostname of the controller to be used
if the network interface is changed to a static IP
Enter new Hostname
address or if no hostname is transmitted with a
DHCP response.
Click [<OK>] to apply the entry.

Click [<Abort>] to discard the entry.
19.1.2.3.3 “Host/Domain Name” > “Domain Name” Submenu
In this submenu, you can set the domain name of the controller.
Table 235: “Networking” > “Host/Domain Name” > “Domain Name” Submenu
Enter the domain name.
Enter new Domain Name
The default entry is “localdomain.lan”.

19.1.2.3.4 “Networking” > “TCP/IP” Submenu
This submenu contains other submenus with the TCP/IP settings for the
ETHERNET interfaces.
Table 236: “Networking” > “TCP/IP” Submenu

Opens a submenu with settings for the IP
1. IP Address
address(es)
Opens a submenu with settings for the default
2. Default Gateway
gateway
Opens a submenu with settings for the DNS
3. DNS Server
server(s)

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.5 “TCP/IP” > “IP Address” Submenu
This submenu contains other submenus with settings for the ETHERNET
interfaces.
The submenu only appears if the controller is operated in “Separated” mode.

If the controller is operated in “Switched” mode, then the “IP Address” > “X1”
submenu is displayed directly.
Table 237: “Networking” > “IP Address” Submenu

1. X1 Opens a submenu with settings for the X1 interface
2. X2 Opens a submenu with settings for the X2 interface

19.1.2.3.6 “IP Address” > “Xn“ Submenu
This submenu contains the settings for the selected interface.
Table 238: “Networking” > “TCP/IP” > “IP Address” Submenu > “Xn”
Select a static or dynamic IP address.
Static IP addressing
1. Type of IP Address When selecting static addressing, the
1. Static IP
Configuration IP address and subnet mask are then
retrieved.
2. DHCP Dynamic IP addressing
3. BootP Dynamic IP addressing
2. IP Address Enter here a static IP address.
3. Subnet Mask Enter the subnet mask.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.7 “TCP/IP” > “Default Gateway” Submenu
This submenu contains other submenus with settings for the default gateway.
Table 239: “Networking” > “TCP/IP” > “Default Gateway” Submenu

Opens a submenu with settings for default gateway
1
1. Default Gateway 1
In addition to the menu item, the current status of
the gateway is displayed.
Opens a submenu with settings for default gateway
2
2. Default Gateway 2
In addition to the menu item, the current status of
the gateway is displayed.

19.1.2.3.8 “Default Gateway” > “Default Gateway n” Submenu
This submenu contains the settings for the selected gateway.
Table 240: “Networking” > “TCP/IP” > “Default Gateway” > “Default Gateway n” Submenu
Set here whether the selected default gateway is to
be used.
1. State 0. Back to … Back to the higher-level menu
1. Disabled The default gateway is not used.
2. Enabled The default gateway is used.
2. Gateway IP Address Enter the address of the default gateway.
Set here a number as the metric.
3. Gateway Metric The default value for the metric is 20, the lowest
value is 0, the highest value is 4.294.967.295.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.9 “TCP/IP” > “DNS Server” Submenu
This submenu contains the settings for the DNS server.
Table 241: “Networking” > “TCP/IP” > “DNS Server” Submenu

The addresses of the defined DNS servers are
displayed. Other submenus are available for the
server entered.
n. DNS Server n
You can change the selected DNS
1. Edit
server address.
You can delete the selected DNS
2. Delete
server address.
(n+1). Add new DNS Add additional DNS server addresses.
Server You can enter 10 addresses.

19.1.2.3.10 “Networking” > “Ethernet” Submenu
configuration.
Table 242: “Networking” > “Ethernet” Submenu

Opens a submenu with settings for the Switch
1. Switch Configuration
Configuration
Opens a submenu with settings for the ETHERNET
2. Ethernet Ports
interfaces

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.11 “Ethernet” > “Switch Configuration” Submenu
This submenu contains the settings for the Switch configuration.
Table 243: “Networking” > “Ethernet” > “Switch Configuration” Submenu

Submenu Submenu Item / Explanation
Enable or disable the switch.
Each interface is operated with its
1. Network interfaces 1. Separated
own IP address.
Both interfaces are operated with one
2. Switched
IP address.

19.1.2.3.12 “Ethernet” > “Ethernet Ports” Submenu
interfaces.
Table 244: “Networking” > “Ethernet” > “Ethernet Ports” Submenu

1. Interface X1 Opens a submenu with settings for the X1 interface
2. Interface X2 Opens a submenu with settings for the X2 interface

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.3.13 “Ethernet Ports” > “Interface Xn” Submenu
This submenu contains the settings for the selected ETHERNET interface.
Table 245: “Networking” > “Ethernet” > “Ethernet Ports” > “Interface Xn” Submenu
Submenu Submenu Item / Explanation
Set here whether the selected port is to be used.
1. Port
1. Disabled The port is not used.
2. Enabled The port is used.
Set here whether the Autonegotiation function is
enabled for the selected port.
2. Autonegotiation 0. Back to … Back to the higher-level menu
1. Disabled Autonegotiation is disabled.
2. Enabled Autonegotiation is enabled.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4 “Firewall” Menu
This menu contains other submenus for the firewall functionality settings.
Table 246: “Firewall” Menu

1. General Configuration Opens a submenu with general firewall settings
2. MAC Address Filter Opens a submenu with MAC address filter settings
3. User Filter Opens a submenu with user filter settings

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.1 “Firewall” > “General Configuration” Submenu
This submenu contains the general settings for the firewall.
Table 247: “Firewall” > “General Configuration” Submenu

Enables/disables the complete functionality of the
firewall.
1. Firewall enabled entirely 0. Back to … Back to the higher-level menu
1. Enable Firewall is enabled.
2. Disable Firewall is disabled.
Enable or disable the “ICMP echo broadcast”
protection.
2. ICMP echo broadcast
“ICMP echo broadcast” protection is
protection 1. Enable
enabled.
“ICMP echo broadcast” protection is
2. Disable
disabled.
You can specify the maximum number of UDP
3. Max UDP connections
connections per second.
per second
You can specify the maximum number of TCP
4. Max TCP connections
connections per second.
per second
5. Interface VPN
6. Interface WAN Opens a submenu with firewall settings on the IP
7. Interface X1 level for the selected interface
8. Interface X2

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.2 “General Configuration” > “Interface xxx” Submenu
This submenu contains the firewall settings on the IP level for the selected
interface.
Table 248: “Firewall” > “General Configuration” > “Interface xxx” Submenu
Enable or disable the firewall for the selected
interface.
1. Interface state The firewall for the selected interface
1. Open
is disabled.
The firewall for the selected interface
2. Filtered
is enabled.
Enable or disable the “ICMP echo” protection for the
respective interface.
2. ICMP Policy The “ICMP echo” protection is
1. Accept
disabled.
The “ICMP echo” protection is
2. Drop
enabled.
3. ICMP Limit pings” per second.
4. ICMP Burst echo bursts” per second.
5. Telnet
6. FTP
7. FTPS
8. HTTP
9. HTTPS
10. I/O-CHECK
11. PLC Runtime Enable or disable the firewall for the respective
service.
12. PLC WebVisu –
The services themselves must be enabled or
direct link (port 8080)
disabled separately on the “Ports and Services”
13. SSH page.
14. TFTP
15. BootP/DHCP
16. DNS
17. Modbus TCP
18. Modbus UDP
19. SNMP

Manual
750-8214 PFC200; G2; 2ETH RS CAN
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.3 “Firewall” > “MAC Address Filter” Submenu
This submenu contains the settings for the MAC address filter.
Table 249: “Firewall” > “MAC Address Filter” Submenu

Enable or disable the global MAC address filter.
1. Global MAC address The global MAC address filter is
1. Filtered
filter state enabled.
The global MAC address filter is
2. Open
disabled.
2. MAC address filter Opens a submenu to edit the MAC address filter
whitelist whitelist
Enable or disable the MAC address filter for the X1
interface.
3. MAC address filter state
The MAC address filter for the X1
X1 1. Open
interface is disabled.
2. Filtered
interface is enabled.
Enable or disable the MAC address filter for the X2
interface.
4. MAC address filter state
X2 1. Open
interface is disabled.
2. Filtered
interface is enabled.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.4 “MAC Address Filter” > “MAC address filter whitelist” Submenu
This submenu displays all available filter entries.
Table 250: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” Submenu
Opens a submenu to add a new filter entry
1. Add new
You can enter 10 filters.
Displays the previous page of the list (if more than
2. Previous page
one page is filled)
Displays the next page of the list (if more than one
3. Next Page
page is filled)
(n + 3.) No (n): Opens a submenu to edit an existing filter entry

19.1.2.4.5 “MAC address filter whitelist” > “Add new / No (n)” Submenu
In this submenu, you can create, change or delete filter entries.
Table 251: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” > “Add new / No (n)”
Submenu
1. MAC address Enter the MAC address.
2. MAC mask Enter the MAC mask.
Enable or disable the filter.
3. Filter state
1. on The filter is enabled.
2. off The filter is disabled.
To apply the changes for the selected filter entry,
4. accept
choose this menu item.
To delete the selected filter entry, choose this menu
5. delete
item.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.6 “Firewall” > “User Filter” Submenu
This submenu displays all available filter entries.
Table 252: “Firewall” > “User Filter” Submenu

1. Add new Opens a submenu to add a new filter entry
Displays the previous page of the list (if more than
2. Previous page
one page is filled)
Displays the next page of the list (if more than one
3. Next Page
page is filled)
(n + 3.) No (n): Opens a submenu to edit an existing filter entry

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.4.7 “User Filter” > “Add New / No (n)” Submenu
In this submenu, you can create, change or delete filter entries.
Table 253: “Firewall” > “User Filter” > “Add New / No (n)” Submenu
Select here whether the network devices is to be
allowed or excluded by the filter.
1. Policy 0. Back to … Back to the higher-level menu
1. Allow The network device is permitted.
2. Drop The network device is excluded.
2. Source IP address Enter the source IP address.
3. Source netmask Enter the source network mask.
4. Source port Enter the source port number.
5. Destination IP address Enter the destination IP address.
6. Destination netmask Enter here the destination netmask.
7. destination port Enter the destination port number.
Select the permitted protocols.
8. protocol 1. tcp The TCP protocol is permitted.
2. udp The UDP protocol is permitted.
3. tcp & udp Both protocols are permitted.
Select the permitted interfaces.
1. all All interfaces are permitted.
9. interface 2. VPN The VPN interface is permitted.
3. WAN The WAN interface is permitted.
4. X1 The X1 interface is permitted.
5. X2 The X2 interface is permitted.
Enable or disable the filter.
10. state
1. on The filter is enabled.
2. off The filter is disabled.
To apply the changes for the selected filter entry,
11. accept
choose this menu item.
To delete the selected filter entry, choose this menu
12. delete
item.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.5 “Clock” Menu
This menu contains other submenus for the date and time settings.
Table 254: “Clock” Menu

1. Date on device (local) Set date.
2. Time on device (local) Set local time.
3. Time on device (UTC) Set GMT time.
Select the display format for the time.
The time is displayed in 24-hour
4. Clock Display Mode 1. 24 hours
format.
The time is displayed in 12-hour
2. 12 hours
format.
Specify the appropriate time zone for your location.
Basic setting:
1. AST/ADT “Atlantic Standard Time,” Halifax
“Eastern Standard Time,” New York,
2. EST/EDT
Toronto
“Central Standard Time,” Chicago,
3. CST/CDT
Winnipeg
4. MST/ “Mountain Standard Time,” Denver,
MDT Edmonton
5. Timezone
“Pacific Standard Time”, Los Angeles,
5. PST/PDT
Whitehouse
Greenwich Mean Time,“ GB, P, IRL,
6. GMT/BST
IS, …
7. CET/ “Central European Time,” B, DK, D,
CEST F, I, CRO, NL, …
8. EET/ “East European Time,” BUL, FI, GR,
EEST TR, …
9. CST “China Standard Time”
10. JST “Japan/Korea Standard Time”
Enter the name of your time zone or country and
6. TZ String town if the time zone is not available for selection
using the “Timezone” parameter.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.6 “Administration” Menu
This menu contains settings for controller administration.
Table 255: “Administration” Menu

Opens a submenu with settings for the user
1. Users
passwords
2. Create Image Opens a submenu for creating a bootable image
Select the serial interface assignment.
1. Linux The serial interface is assigned to the
3. Owner of Serial Interface Console Linux® console.
The serial interface is not assigned
2. Un-
and is available for applications or
assigned
CODESYS.
Restart the controller following a security challenge.
4. Reboot Controller 0. Back to … Back to the higher-level menu
1. Reboot Restarts the controller

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.6.1 “Administration” > “Users” Submenu
This submenu contains settings for the user passwords.
Table 256: “Administration” > “Users” Submenu

1. user Enter a new password for the “user” user.
2. admin Enter a new password for the “admin” user.

19.1.2.6.2 “Administration” > “Create Image” Submenu
This submenu contains the selection for creating the image.
In addition to the menu item for the enabled storage medium, the current status is
displayed.
Table 257: “Administration” > “Create Image” Submenu

To create an image on the memory card, select this
menu item. Enter the reserved memory size in
1. SD Card another step.
This menu item only appears if the memory card is
inserted.
To create an image on the internal memory, select
2. Internal Flash
this menu item.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.7 “Package Server” Menu
This menu contains other submenus with functions for firmware backup and
restore, as well as information and setting options for the current system partition.
Table 258: “Package Server” Menu

Opens a submenu with functions for the firmware
1. Firmware Backup
backup
Opens a submenu with functions for the firmware
2. Firmware Restore
restore
Opens a submenu with information and setting
3. System Partition
options for the current system partition

19.1.2.7.1 “Package Server” > “Firmware Backup” Submenu
This submenu contains a selection option for the data to be saved.
The submenu only appears if a memory card is inserted that does not contain a
bootable system. Otherwise, a message is displayed.
Table 259: “Package Server” > “Firmware Backup” Menu

1. All All data is saved.
2. PLC Runtime project The PLC runtime project is saved.
3. Settings The controller settings are saved.
4. System The controller operating system is saved.

You are taken to the following submenu after making the selection.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.7.2 “Firmware Backup” > “Auto Update Feature” Submenu
This submenu contains a setting option for the Auto Update function.
The submenu only appears if the data for the firmware backup has been
selected.
Table 260: “Package Server” > “Firmware Backup” > “Auto Update Feature” Menu
The Auto Update function is OFF for the selected
1. No
data.
The Auto Update function is ON for the selected
2. Yes
data.

19.1.2.7.3 “Firmware Backup” > “Destination” Submenu
This submenu contains a selection option for the backup destination drive.
Table 261: “Package Server” > “Firmware Backup” > “Auto Update Feature” Menu
1. SD Card The selected data is copied to the memory card.

The copy progress is displayed during the backup process.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.7.4 “Package Server” > “Firmware Restore” Submenu
This submenu contains a selection option for the restore source drive.
In addition to the enabled partition, the current status is displayed.
Table 262: “Package Server” > “Firmware Restore” Menu

1. SD Card The data is copied from the memory card.
2. Internal Flash The data is copied from the internal memory.

19.1.2.7.5 “Firmware Restore” > “Select Package” Submenu
This submenu contains a selection option for the data to be restored.
Table 263: “Package Server” > “Firmware Restore” > “Select Package” Menu
1. PLC Runtime project The PLC runtime project is loaded.
2. Settings The controller settings are loaded.
3. System The controller operating system is loaded.
The controller operating system and settings are
4. System + Setting
loaded.
5. All All data is loaded.

The copy progress is displayed during the restore process.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.7.6 “Package Server” > “System Partition” Submenu
This submenu contains information and setting options for the current system
partition.
Table 264: “Package Server” > “System Partition” Submenu

1. Current active partition The partition currently in use is displayed.
2. Set inactive NAND Select this menu item to start the system from a
partition active different partition at the next controller reboot.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.8 “Mass Storage” Menu
This menu contains information on the internal flash memory and, if inserted, on
the external memory card.
In addition to the menu item, the status is displayed for the enabled partition.
Table 265: “Mass Storage” Menu

Opens a submenu with information on the memory
card and its formatting
1. SD Card
This menu item only appears if a memory card is
inserted in the controller.
Opens a submenu with information on the internal
2. Internal Flash
flash memory

19.1.2.8.1 “Mass Storage” > “SD Card” Submenu
This submenu contains information on the external memory card and its
formatting.
This submenu only appears if a memory card is inserted in the controller.
Table 266: “Mass Storage” > “SD Card” Menu

1. Show information Displays information on the memory card
To format the memory card in FAT format, select
2. FAT format medium
this menu item. Then specify a volume name.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.9 “Software Uploads” Menu
This menu contains choices and settings for the device update.
You can select fieldbus software, program licenses and update scripts, for
example, for transfer from a PC to the controller.
You can also enable transmitted packages or delete from the controller.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10 “Ports and Services” Menu
This submenu contains other submenus with settings for the respective services.
Table 267: “Ports and Services” Menu

Opens a submenu with settings for the Telnet
1. Telnet
service
2. FTP Opens a submenu with settings for the FTP service
Opens a submenu with settings for the FTPS
3. FTPS
service
Opens a submenu with settings for the HTTP
4. HTTP
service
Opens a submenu with settings for the HTTPS
5. HTTPS
service
6. NTP Opens a submenu with settings for the NTP service
7. SSH Opens a submenu with settings for the SSH server
8. TFTP Opens a submenu with settings for the TFTP server
Opens a submenu with settings for the DHCPD
9. DHCPD
service
10. DNS Opens a submenu with settings for the DNS service
Opens a submenu with settings for the WAGO-I/O-
11. IOCHECK PORT
CHECK port
Opens a submenu with settings for the Modbus TCP
12. Modbus TCP
service
Opens a submenu with settings for the Modbus UDP
13. Modbus UDP
service
Opens a submenu with settings for the OPC UA
14. OPC UA
service
Opens a submenu with settings for the PLC runtime
15. PLC Runtime Services
system services

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.1 “Ports and Services” > “Telnet” Submenu
This submenu contains the settings for the Telnet service.
Table 268: “Ports and Services” > “Telnet” Submenu

Enable/disable the Telnet service.
1. State
1. Enable The Telnet service is enabled.
2. Disable The Telnet service is disabled.
Opens a submenu with firewall settings for the this
2. Firewall status
service for the interfaces

19.1.2.10.2 “Ports and Services” > “FTP” Submenu
This submenu contains the settings for the FTP service.
Table 269: “Ports and Services” > “FTP” Submenu

Enable/disable the FTP service.
1. State
1. Enable The FTP service is enabled.
2. Disable The FTP service is disabled.
2. Firewall status

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.3 “Ports and Services” > “FTPS” Submenu
This submenu contains the settings for the FTPS service.
Table 270: “Ports and Services” > “FTPS” Submenu

Enable/disable the FTPS service.
1. State
1. Enable The FTPS service is enabled.
2. Disable The FTPS service is disabled.
2. Firewall status

19.1.2.10.4 “Ports and Services” > “HTTP” Submenu
This submenu contains the settings for the HTTP service.
Table 271: “Ports and Services” > “HTTP” Submenu

Enable/disable the HTTP service.
1. State
1. Enable The HTTP service is enabled.
2. Disable The HTTP service is disabled.
2. Firewall status

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.5 “Ports and Services” > “HTTPS” Submenu
This submenu contains the settings for the HTTPS service.
Table 272: “Ports and Services” > “HTTPS” Submenu

Enable/disable the HTTPS service.
1. State
1. Enable The HTTPS service is enabled.
2. Disable The HTTPS service is disabled.
2. Firewall status

19.1.2.10.6 “Ports and Services” > “NTP” Submenu
This submenu contains the settings for the NTP service.
Table 273: “Ports and Services” > “NTP” Submenu

Enable/disable the NTP service.
1. State
1. Enable The NTP service is enabled.
2. Disable The NTP service is disabled.
2. Port Enter the port number of the NTP server.
3. Time Server 1
Enter here the IP addresses of up to 4 time servers.
4. Time Server 2 Time server No. 1 is requested first of all. If no data
5. Time Server 3 can be accessed via time server No. 1, time server
No. 2 is requested.
6. Time Server 4
7. Update Time Specify here the update interval of the time server.
To update the time immediately, irrespective of the
8. Issue immediate update
update interval, select this menu item.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.7 “Ports and Services” > “SSH” Submenu
This submenu contains the settings for the SSH service.
Table 274: “Ports and Services” > “SSH” Submenu

You can enable/disable the SSH server.
1. State
1. Enable The SSH server is enabled.
2. Disable The SSH server is disabled.
2. Port Enter the port number.
You can enable or inhibit root access.
3. Allow root login
1. Enable Root access is permitted.
2. Disable Root access is not permitted.
Enable or disable the password query function.
4. Allow password login
1. Enable Password query is enabled.
2. Disable Password query is disabled.
5. Status of firewalling

19.1.2.10.8 “Ports and Services” > “TFTP” Submenu
This submenu contains the settings for the TFTP service.
Table 275: “Ports and Services” > “TFTP” Submenu

Enable or disable the TFTP server.
1. State
1. Enable The TFTP server is enabled.
2. Disable The TFTP server is disabled.
Specify here the path for downloading the server
2. Transfer Directory
directory.
3. Status of firewalling

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.9 “Ports and Services” > “DHCPD” Submenu
This submenu contains the settings for the DHCPD service.
Table 276: “Ports and Services” > “DHCPD” Submenu

1. DHCPD firewalling
2. X1 Opens a submenu with the DHCPD settings for the
3. X2 selected interface

19.1.2.10.10 “DHCPD” > “Xn” Submenu
This submenu contains the settings for the DHCPD service for the selected
interface.
Table 277: “Ports and Services” > “DHCPD” > “Xn” Submenu
Enable/disable the DHCPD service for the Xn
interface.
1. State 0. Back to … Back to the higher-level menu
1. Enable The DHCPD service is enabled.
2. Disable The DHCPD service is disabled.
2. Range Enter a range of available IP addresses.
Specify the lease time here in seconds. 120
3. Lease Time (min)
seconds are entered by default.
Enter a new static assignment of MAC ID to IP
address,
4. Add static hostname e.g., “01:02:03:04:05:06=192.168.1.20” or
“hostname=192.168.1.20”.
This displays the static assignments.
(5 + n). Static Host (n) Opens a submenu to change the
1. Edit
selected assignment
2. Delete Deletes the selected assignment

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.11 “Ports and Services” > “DNS” Submenu
This submenu contains the settings for the DNS service.
Table 278: “Ports and Services” > “DNS” Submenu

Enable/disable the DNS service.
1. State
1. Enable The DNS service is enabled.
2. Disable The DNS service is disabled.
Select the operating mode of the DNS server.
2. Mode The requests are buffered to optimize
1. Proxy
throughput.
2. Relay All requests are routed directly.
3. Firewall status
Enter a new static assignment of IP address to
hostname,
4. Add static hostname
e.g., “192.168.1.20:hostname”.
This displays the static assignments.
(5 + n). Static Host (n) Opens a submenu to change the
1. Edit
selected assignment
2. Delete Deletes the selected assignment

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.12 “Ports and Services” > “IOCHECK PORT” Submenu
This submenu contains settings for the WAGO-I/O-CHECK port.
Table 279: “Ports and Services” > “IOCHECK PORT” Submenu

Enable/disable the WAGO-I/O-CHECK port.
The WAGO-I/O-CHECK port is
1. State 1. Enable
enabled.
The WAGO-I/O-CHECK port is
2. Disable
disabled.
2. Firewall status

19.1.2.10.13 “Ports and Services” > “Modbus TCP” Submenu
This submenu contains the settings for the Modbus TCP service.
Table 280: “Ports and Services” > “Modbus TCP” Submenu

Disable or enable the Modbus TCP service.
1. State
1. Enable The Modbus TCP service is enabled.
2. Disable The Modbus TCP service is disabled.
2. Firewall status

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.14 “Ports and Services” > “Modbus UDP” Submenu
This submenu contains the settings for the Modbus UDP service.
Table 281: “Ports and Services” > “Modbus UDP” Submenu

Disable/enable the Modbus UDP service.
1. State
1. Enable The Modbus UDP service is enabled.
2. Disable The Modbus UDP service is disabled.
2. Firewall status

19.1.2.10.15 “Ports and Services” > “OPC UA” Submenu
This submenu contains the settings for the OPC UA service.
Table 282: “Ports and Services” > “OPC UA” Submenu

Disable/enable the OPC UA service.
1. State
1. Enable The OPC UA service is enabled.
2. Disable The OPC UA service is disabled.
2. Firewall status

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.16 “…” > “Firewall Status” Submenu
This submenu contains firewall settings for the selected service.
Table 283: “Ports and Services” > “Firewall Status” Submenu

Enable or disable the firewall for the VPN interface
and respective service.
1. VPN Data traffic via the VPN interface is
1. open
permitted.
Data traffic via the VPN interface is
2. close
not permitted.
Enable or disable the firewall for the WAN interface
2. WAN Data traffic via the WAN interface is
1. open
permitted.
Data traffic via the WAN interface is
2. close
not permitted.
Enable or disable the firewall for the X1 interface
3. X1 Data traffic via the X1 interface is
1. open
permitted.
Data traffic via the X1 interface is not
2. close
permitted.
1. open
permitted.
2. close
permitted.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.17 “Ports and Services” > “PLC Runtime Services” Submenu
This submenu contains the settings for the PLC runtime system services.
Table 284: “Ports and Services” > “PLC Runtime Services” Submenu
1. General Configuration Enter the password for port authentication.
Opens a submenu with service settings for
2. CODESYS 2
CODESYS V2
Opens a submenu with service settings for
3. e!RUNTIME
e!RUNTIME
4. Change CODESYS
Runtime firewalling
settings
5. Change CODESYS
WebVisu firewalling
settings

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.18 “PLC Runtime Services” > “CODESYS 2” Submenu
This submenu contains the settings for the CODESYS V2 service.
Table 285: “Ports and Services” > “PLC Runtime Services” > “CODESYS 2” Submenu
Enable or disable the Webserver for the CODESYS
web visualization.
1. Webserver
enable/disable
1. Enable The Webserver is enabled.
2. Disable The Webserver is disabled.
Enable or disable the communication between the
CODESYS V2 runtime system and the
2. Communication CODESYS V2 programming system.
enable/disable 0. Back to … Back to the higher-level menu
1. Enable Communication is enabled.
2. Disable Communication is disabled.
Enter here the port number for communication with
3. Communication Port
the CODESYS V2 programming system. The default
Number
value is 2455.
to the device.
4. Port Authentication
enable/disable
1. Enable Authentication via login is required.
2. Disable Authentication is not required.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.10.19 “PLC Runtime Services” > “e!RUNTIME” Submenu
This submenu contains the settings for the e!RUNTIME service.
Table 286: “Ports and Services” > “PLC Runtime Services” > “e!RUNTIME” Submenu
Enable or disable the Webserver for the
e!RUNTIME web visualization.
1. Webserver
enable/disable
1. Enable The Webserver is enabled.
2. Disable The Webserver is disabled.
to the device.
2. Port Authentication
enable/disable
1. Enable Authentication via login is required.
2. Disable Authentication is not required.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.11 “SNMP” Menu
This menu contains other submenus with the SNMP settings.
Table 287: “SNMP” Menu

1. General SNMP
Opens a submenu with general SNMP settings
Configuration
2. SNMP v1/v2c Manager Opens a submenu with settings for the SNMP
Configuration v1/v2c Manager
3. SNMP v1/v2c Trap Opens a submenu with settings for the SNMP
Receiver Configuration v1/v2c trap receivers
Opens a submenu with settings for the SNMP v3
4. SNMP v3 Configuration
configuration
5. SNMP firewalling
Opens a submenu with firewall settings for SNMP
6. Secure SNMP firewalling

19.1.2.11.1 “SNMP” > “General SNMP Configuration” Submenu
This submenu contains the general SNMP settings.
Table 288: “SNMP” > “General SNMP Configuration” Submenu

Parameters Submenu Item / Explanation
Enable or disable the SNMP service.
1. SNMP status
1. Enable The SNMP service is enabled.
2. Disable The SNMP service is disabled.
2. Name of device Enter here the device name (sysName).
3. Description Enter here the device description (sysDescription).
4. Physical location Enter here the location of the device (sysLocation).
5. Contact Enter here the email contact address (sysContact).

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.11.2 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu
This submenu contains the SNMP v1/v2c Manager settings.
Table 289: “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu

Parameters Submenu Item / Explanation
Enable or disable the SNMP v1/v2c protocol.
The SNMP v1/v2c protocol is
1. Protocol state 1. Enable
enabled.
The SNMP v1/v2c protocol is
2. Disable
disabled.
Specify here the community name for the SNMP
2. Local community name manager configuration (max. 32 characters, no
spaces).

19.1.2.11.3 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu
This submenu contains settings for the v1/v2c trap receivers.
Table 290: “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu
(n). Trap Receiver (n)
v1/v2c trap receiver to delete the trap receiver
Opens a series of submenus to create a new v1/v2c
trap receiver
You can enter 10 trap receivers.
The following entries/selections are possible:
(n + 1). Add new Trap • IP address of the new trap receiver
Receiver (management station)
• Community name for the new trap receiver
configuration (max. 32 characters, no spaces)
• SNMP version via which the traps are sent
(v1/v2c)

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.11.4 “SNMP” > “SNMP v3 Configuration” Submenu
This submenu contains settings for SNMP v3.
Table 291: “SNMP” > “SNMP v3 Configuration” Submenu

(n). Username
v3 user and to delete the user
Opens a series of submenus to create a new v3
user
You can enter 10 users.
The following entries/selections are possible:
• Authentication name (The name can have a
min. 8 and max. 32 characters and may contain
lower case letters (a … z), upper case letters
(A … Z), numbers (0 … 9), special characters
!()*~'.-_ but no spaces.)
• Authentication type (None/MD5/SHA)
• Authentication key (The key can have a min. 8
(n + 1). Add new v3 User
and max. 32 characters and may contain lower
case letters (a … z), upper case letters (A … Z),
numbers (0 … 9), special characters !()*~'.-_ but
no spaces.)
• Privacy type (None/DES/AES)
• Privacy key (The key can have a min. 8 and
max. 32 characters and may contain lower case
letters (a … z), upper case letters (A … Z),
numbers (0 … 9), special characters !()*~'.-_ but
no spaces.)
• IP address for a trap receiver for v3 traps

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.1.2.11.5 “SNMP” > “(Secure)SNMP firewalling” Submenu
These submenus contain the SNMP firewall settings.
Table 292: “SNMP” > “(Secure )SNMP firewalling” Submenu

Enable or disable the firewall for the VPN interface
1. VPN Data traffic via the VPN interface is
1. open
permitted.
Data traffic via the VPN interface is
2. close
not permitted.
Enable or disable the firewall for the WAN interface
2. WAN Data traffic via the WAN interface is
1. open
permitted.
Data traffic via the WAN interface is
2. close
not permitted.
1. open
permitted.
2. close
permitted.
1. open
permitted.
2. close
permitted.

Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.2 Process Data Architecture

The process image for the I/O modules on the local bus is built up word-by-word
in the controller (with word alignment). The internal mapping method for data
greater than one byte conforms to Intel formats.
The following section describes the representation for WAGO-I/O SYSTEM 750
(750 and 753 Series) I/O modules in the process image, as well as the
configuration of the process values.
Equipment damage due to incorrect address!

To prevent any damage to the device in the field you must always take the
process data for all previous byte or bit-oriented I/O modules into account when
addressing an I/O module at any position in the fieldbus node.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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.
19.2.1.1 1 Channel Digital Input Module with Diagnostics
750-435
Table 293: 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
19.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 294: 2 Channel Digital Input Modules

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

753-421, -424, -425
Table 295: 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
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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 296: 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
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
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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“.
Table 299: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.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 300: 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
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
19.2.2 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.
19.2.2.1 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 302: 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
19.2.2.2 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 303: 2 Channel Digital Output Modules

controls controls
DO 2 DO 1
Channel 2 Channel 1
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.2.2.3 2 Channel Digital Input Modules with Diagnostics and Input Process
Data
750-507 (-508), -522,

753-507
The digital output modules have a diagnostic bit for each output channel. When
an output fault condition occurs (i.e., overload, short circuit, or broken wire), a
diagnostic bit is set. The diagnostic data is mapped into the Input Process Image,
while the output control bits are in the Output Process Image.
Table 304: 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 305: 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
750-8214 PFC200; G2; 2ETH RS CAN
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 307: 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
19.2.2.6 8 Channel Digital Output Module
750-530, -536, -1515, -1516,

753-530, -534, 536
Table 308: 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
750-8214 PFC200; G2; 2ETH RS CAN

Process Data
750-537,
753-537
Table 309: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.2.2.9 8 Channel Digital Input/Output Modules
750-1502, -1506
Table 311: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.2.3 Analog Input Modules

The analog input modules provide 16-bit measured data and 8 control/status bits
per channel.
The controller only uses the 8 control/status bits internally for

configuration/parameterization (e.g., via WAGO-I/O-CHECK).
Therefore, only the 16-bit measurement values for each channel are in Intel
format and are mapped by word in the input process image for the controller.
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.
19.2.3.1 1 Channel Analog Input Modules
750-491, (and all variations)
Table 312: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.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
750-8214 PFC200; G2; 2ETH RS CAN
Table 314: 2-Channel Analog Input Modules HART
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Table 315:: 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
750-8214 PFC200; G2; 2ETH RS CAN
750-451, 750-458, 750-496, 750-497

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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 318: 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
750-8214 PFC200; G2; 2ETH RS CAN
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 319: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.2.4 Analog Output Modules

The analog output modules provide 16-bit output values and 8 control/status bits
per channel.
The controller only uses the 8 control/status bits internally for

configuration/parameterization (e.g., via WAGO-I/O-CHECK).
Therefore, only the 16-bit measurement values for each channel are in Intel
format and are mapped by word in the output process image for the controller.
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.
19.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 320: 2 Channel Analog Output Modules

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

753-553, -555, -557, -559
Table 321: 4 Channel Analog Output Modules

Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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.
19.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 322: 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
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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 323: 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
750-8214 PFC200; G2; 2ETH RS CAN
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 324: 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 325: 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
750-8214 PFC200; G2; 2ETH RS CAN
Byte Designation
Offset Description
High Byte Low Byte
0 - C0 Control byte of Counter 1
2 - C1 Control byte of Counter 2
19.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 326: 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
19.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
750-8214 PFC200; G2; 2ETH RS CAN
Output Process Image, which have a total of 2 words mapped into each image.
Table 327: 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
19.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 328: 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
19.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
750-8214 PFC200; G2; 2ETH RS CAN
Table 329: 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
19.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 330: Data Exchange Module 750-654, -654/000-001

Byte Designation
Offset Description
High Byte Low Byte
0 D1 D0
Data bytes
1 D3 D2
19.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
750-8214 PFC200; G2; 2ETH RS CAN
Table 331: 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 332: 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
19.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 333: 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
750-8214 PFC200; G2; 2ETH RS CAN
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 334: 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 335: Incremental Encoder Interface Modules 750-637, (and all variations)
Byte Designation
Offset Description
High Byte Low Byte
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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 336: 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
19.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 337: 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
750-8214 PFC200; G2; 2ETH RS CAN
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)
19.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 338: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.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 339: 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
19.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 340: 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
DALI / DSI Master can only be used with CODESYS 2!

The DALI/DSI master module is only supported by the runtime system
CODESYS 2. The runtime system e!Runtime does not support the DALI/DSI
master module!
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.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 341: 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
750-8214 PFC200; G2; 2ETH RS CAN
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
750-8214 PFC200; G2; 2ETH RS CAN
Table 342: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.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 343: 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
19.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 344: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.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 345: 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
19.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
750-8214 PFC200; G2; 2ETH RS CAN
Table 346: 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
19.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 347: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.2.5.19 KNX/EIB/TP1 Module
753-646
The KNX/TP1 module appears in router and device mode with a total of 24-byte
user data within the input and output area of the process image, 20 data bytes
and 2 control/status bytes. Even though the additional bytes S1 or C1 are
transferred as data bytes, they are used as extended status and control bytes.
The opcode is used for the read/write command of data and the triggering of
specific functions of the KNX/EIB/TP1 module. Word-alignment is used to assign
12 words in the process image. Access to the process image is not possible in
router mode. Telegrams can only be tunneled.
In device mode, access to the KNX data can only be performed via special
function blocks of the IEC application. Configuration using the ETS engineering
tool software is required for KNX.
Table 348: KNX/EIB/TP1 Module 753-646

Byte Destination
Offset Description
High Byte Low Byte
0 - C0/S0 not used Control/Status byte
extended
1 C1/S1 OP Control/Status Opcode
byte
2 D1 D0 Data byte 1 Data byte 0
19.2.5.20 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.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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 349: AS-interface Master Module 750-655, 753-655

Process Byte Designation
High Byte Low Byte
size
Control-/
0 - C0/S0 Not used
Status byte
12 bytes 1 D1 D0
…
5 D9 D8
6 D11 D10
20 bytes …
9 D17 D16
10 D19 D18
24 bytes *
11 D21 D20
Mailbox (0, 6, 10, 12 or 18 bytes)/
12 D23 D22
Process data (0-46 bytes)
32 bytes …
15 D29 D28
16 D31 D30
40 bytes …
19 D37 D36
12 D39 D38
48 bytes …
23 D45 D44
*) Factory Setting
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.2.6 System Modules
19.2.6.1 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 350: 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 351: System Modules with Diagnostics 750-610, -611

Input Process Image
Diagnostics Diagnostics
bit S 2 bit S 1
Fuse Fuse
19.2.6.2 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 352: 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
19.2.6.3 Binary Space Module
750-622
Manual
750-8214 PFC200; G2; 2ETH RS CAN
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 353: 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
750-8214 PFC200; G2; 2ETH RS CAN
19.3 CODESYS V2 Libraries

Additional functions for the controller 750-8214are provided using libraries.
19.3.1 General Libraries

This section contains general CODESYS libraries supported by the controller
750-8214.
19.3.1.1 CODESYS System Libraries
All of the functions of the CODESYS system libraries listed below are supported.
Table 354: CODESYS System Libraries

Library Function C/IEC 61131
Analyzation.lib Analysis of boolean expressions C and IEC 61131
AnalyzationNew.lib Analysis of boolean expressions C and IEC 61131
Iecsfc.lib Provision of implicit variables in the IEC 61131
SFC (sequential function chart)
NetVarUdp_LIB_V23.lib Implementation for network IEC 61131
variables
Standard.LIB Offers various standard functions C
SysLibAlarmTrend.lib Supports alarm and trend tasks IEC 61131
SysLibCallback.lib For installing call-back handlers C
and event handlers
SysLibDir.lib For accessing directories C
SysLibDirect.lib Access to variables using indices C
SysLibEvent.lib Handling of events in the system C
SysLibFileStream.lib File handling using ANSI-C C
functions
SysLibGetAddress.lib Returns addresses and the size of C
memory segments
SysLibIecTasks.lib Administration of IEC tasks C
SysLibMem.lib Memory administration C
SysLibPlcCtrl.lib Control of the PLC from outside C
the PLC program
SysLibProjectInfo.lib Reading out of information about C
the CODESYS project
SysLibSem.lib Handling of semaphores C
SysLibSockets.lib Socket handling C
SysLibSocketsAsync.lib Socket handling, asynchronous C
SysLibStr.lib String functions C
SysLibTasks.lib Administration of tasks C
SysLibTime.lib Administration of real-time clock C
SysLibVisu.lib Dynamic visualization C
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 354: CODESYS System Libraries
Library Function C/IEC 61131
SysTaskInfo.lib Evaluation of task information in IEC 61131
the Online mode
Util.lib Various logical operations IEC 61131
Util_no_Real.lib Various logical operations IEC 61131
Additional information about the libraries is given in the online Help function for
CODESYS-IDE.
</dg_
19.3.1.2 SysLibCom.lib
The controller 750-8214supports the following function blocks of the

“SysLibCom.lib” library:
- SysComClose
- SysComGetVersion2300
- SysComOpen
- SysComRead
- SysComSetSettings
- SysComSetSettingsEx
- SysComWrite
Observe restrictions on the settings for stop bits!

The setting “1.5 stop bits” is not supported by controller750-8214.
Additional information about this is given in the online Help function for
CODESYS-IDE.
19.3.1.3 SysLibFile.lib

“SysLibFile.lib” library:
- SysFileClose
- SysFileCopy
- SysFileDelete
- SysFileEOF
- SysFileGetPos
- SysFileGetSize
- SysFileGetTime
- SysFileOpen
- SysFileRead
- SysFileRename
- SysFileSetPos
- SysFileWrite
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Ensure that files are saved!

Files are not reliably saved on the data medium until you call up the
“SysFileClose” function block!
CODESYS-IDE.
Notes on the parameters of the function blocks
File and directory names distinguish between upper and lower case!
“test.txt”≠ “TEST.TXT”≠ “Test.txt”
The separator for directories is: “/.”
The file system supports:
- Absolute paths, (e.g., “/media/sd/test.txt”)

- Relative paths (e.g., “testpath/test.txt”)
- Macros (e.g., “HOME://”, “CARD://”, “TMP://”)
Table 355: Possible Macros for File Access

Macro Booting from Internal Memory Booting from Memory Card
HOME:// “/home/codesys/” “/home/codesys/”
(internal NAND memory) (memory card)
CARD:// “/media/sd/” “/home/codesys/”
(nemory card) (memory card)
TMP:// “/tmp/codesys/” “/tmp/codesys/”
(internal RAM memory) (internal RAM memory)
19.3.1.4 SysLibFileAsync.lib

“SysLibFileAsync.lib” library:
- SysFileCloseAsync
- SysFileCopyAsync
- SysFileDeleteAsync
- SysFileEOFAsync
- SysFileGetPosAsync
- SysFileGetSizeAsync
- SysFileGetTimeAsync
- SysFileOpenAsync
- SysFileReadAsync
- SysFileRenameAsync
- SysFileSetPosAsync
Manual
750-8214 PFC200; G2; 2ETH RS CAN
- SysFileWriteAsync
Ensure that files are saved!

Files are not reliably saved to the data medium until you call up the
“SysFileCloseAsync” function block.
CODESYS-IDE.
Notes on the parameters of the function blocks
File and directory names distinguish between upper and lower case!
“test.txt”≠ “TEST.TXT”≠ “Test.txt”
The separator for directories is: “/.”
The file system supports:
- Absolute paths, (e.g., “/media/sd/test.txt”)

- Relative paths (e.g., “testpath/test.txt”)
- Macros (e.g., “HOME://”, “CARD://”, “TMP://”)
Table 356: Possible Macros for File Access

Macro Booting from Internal Memory Booting from Memory Card
HOME:// “/home/codesys/” “/home/codesys/”
(internal NAND memory) (memory card)
CARD:// “/media/sd/” “/home/codesys/”
(nemory card) (memory card)
TMP:// “/tmp/codesys/” “/tmp/codesys/”
(internal RAM memory) (internal RAM memory)
19.3.1.5 SysLibRtc.lib

“SysLibRtc.lib” library:
- SysRtcGetHourMode
- SysRtcGetTime
- SysRtcSetTime
CODESYS-IDE.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.3.1.6 BusDiag.lib
The controller 750-8214 supports the following function blocks of the

“BusDiag.lib” library:
- DiagGetBusState
- DiagGetState
The document containing a description of this library and the function blocks it
includes is available for download on the Internet at www.wago.com.
The values for the input variables “DEVICENUMBER” of the “DiagGetBusState”

and “DiagGetState” functions are based on the particular device and bus system
and are as follows for the controller “PFC200; G2; 2ETH RS CAN” (750-8214):
Table 357: Input Variable “DEVICENUMBER”

Bus System Value
Local bus 0
Modbus 1
CANopen 2
19.3.1.7 mod_com.lib

“mod_com.lib” library:
- ADD_PI_INFORMATION
- CRC16
- FBUS_ERROR_INFORMATION
- GET_DIGITAL_INPUT_OFFSET
- GET_DIGITAL_OUTPUT_OFFSET
- KBUS_ERROR_INFORMATION
- MOD_COM_VERSION
- PI_INFORMATION
- SET_DIGITAL_INPUT_OFFSET
- SET_DIGITAL_OUTPUT_OFFSET
- SLAVE_ADDRESS
19.3.1.8 SerComm.lib

“SerComm.lib” library:
- SERCOMM
- SERCOMM_VERSION
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.3.1.9 WagoConfigToolLIB.lib
The following table shows call-ups that allow you to configure and parameterize
the controller from the PLC program or Linux® via the “ConfigToolFB” function
block (see parameter “stCallString”). In addition to WBM and the CBM, this is
another variant to configure the controller for operational requirements.
The configuration directory for this under Linux® is: /etc/config-tools/
Figure 166: Graphical Representation of the “ConfigToolFB” Function Block
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 358: Description of the Configuration Scripts for “Information”
Parameters Status Call-Up Output/Input Effective
Controller Details: Identifies various information about the controller
Product get_coupler_details
read Product description Immediately
Description product-description
get_coupler_details
Order Number read Item number of the controller Immediately
order-number
Firmware get_coupler_details Firmware version of the
read Immediately
Revision firmware-revision controller
Licence get_coupler_details
read CODESYS license details Immediately
Information license-information
Network Details X1: Identifies the parameters currently used for the ETHERNET interface
X1/X2 in “switched” mode or for the ETHERNET interface X1 in “separated” mode
Status of the interface.
get_actual_eth_config Possible return values:
State read Immediately
X1 state - enabled
- disabled
get_actual_eth_config
Mac Address read MAC address Immediately
X1 mac-address
IP Address read Current IP address Immediately
X1 ip-address
Subnet Mask read Current subnet mask Immediately
X1 subnet-mask
Path via which the interface
receives its IP address;
Configuration get_actual_eth_config Possible return values:
read Immediately
type X1 config-type - dhcp
- static
- bootp
Connection status;
get_actual_eth_config Possible return values:
Cable state read Immediately
X1 cable-state - connected
- disconnected
Default gateway currently
get_actual_eth_config used for interface X1
Default-gateway read Immediately
X1 default-gateway (e.g., if a default gateway was
entered via a DHCP server)
Network Details X2: Identifies the parameters currently used for the ETHERNET interface X2
in “separated” mode
See “Network Details X1”. When calling these up, replace “X1” with “X2” (in “separated” mode only).
</dg_
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 359: Description of the Configuration Scripts for “CODESYS”
Parameters Status Call Output/Input Effecti
ve
Information
CODESYS get_coupler_details
Version of the CODESYS Immedia
Webserver read codesys-Webserver-
Webserver tely
Version version
Project Details
get_rts_info Immedia
Date read
project date tely
Title read
project title tely
Display of the project information
Version read specified in CODESYS (Menu >
project version tely
Project > Project Information)
Author read
project author tely
Description read
project description tely
CODESYS State
get_rts_info Display of the CODESYS status Immedia
State read
state (RUN or STOP) tely
Home Directory (Boot Project Location)
Storage logation for the home
directory.
Possible return values:
get_runtime_config
read - enabled: The home directory
homedir-on-sdcard
is on the SD card.
- disabled: The home directory
Home Directory
is on the boot medium. After
(Boot Project
Storage logation for the home restart
Location)
directory.
config_runtime Possible entries for the value are:
write homedir-on- - enabled: Put the home
sdcard=<Wert> directory on the SD card.
- disabled: The home directory
is on the boot medium.
Memory location for a boot
project of the runtime application
get_runtime_config
read - HOME:// (saving on internal
boot-project
memory)
Boot project - CARD:// (saving on the After
location memory card) restart
Possible entries for <value>:
- HOME:// (saving on internal
config_runtime boot-
write memory)
project=<value>
- CARD:// (saving on the
memory card)
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 360: Description of the Configuration Scripts for “Networking - Host/Domain Name”
ve
Host Name
Display of the host name.
The return value is blank when
get_coupler_details Immedia
read /etc/hostname is empty.
hostname tely
Host Name For details see the parameter
“Actual Hostname.”
change_hostname Changing the host name. Immedia
write
hostname=<String> Input a host name for <String>. tely
The actual host name (if
Actual get_coupler_details /etc/hostname is empty, a unique Immedia
read
Hostname actual-hostname host name is generated from the tely
MAC address)
Domain Name
get_coupler_details
read Display of domain name
domain-name Immedia
Domain name
change_hostname Change the domain name. Enter tely
write
dnsdomain=<String> the domain name for <String>.
Table 361: Description of the Configuration Scripts for “Networking - TCP/IP”

ve
IP Address X1: Determines the IP parameters of the ETHERNET interfaces X1/X2 in
“switched” mode and the ETHERNET interface X1 in “separated” mode
Path via which the interface
receives its IP address
get_eth_config Possible return values are:
read
X1 config-type - static (set statically)
- dhcp (per DHC)
Type of IP
- bootp (per BootP) Immedia
address
Enable process, via which the tely
configuration
config_interfaces interface receives its IP address
interface=X1 Possible entries for <Value> are:
write
config-type=<Value> - static (set statically)
state=enabled - dhcp (per DHC)
- bootp (per BootP)
get_eth_config Address set for using a static IP
read
X1 ip-address address (static IP).
Change IP address for static IP
Immedia
IP address config_interfaces <Value> must have an IP address
tely
write interface=X1 with the format
ip-address=<Value> “Number.Number.Number.Numbe
r.”
get_eth_config Subnet mask set for using a static
read
X1 subnet-mask IP address (static IP)
Change subnet mask for static IP
Immedia
Subnet Mask config_interfaces addresses. <Value> must have
tely
write interface=X1 an IP address with the format
subnet-mask=<Value> “Number.Number.Number.Numbe
r.”
IP Address X2: Determines the parameters currently used for the ETHERNET interface X2 in
“separated” mode
See “IP Address X1.” When calling these up, replace X1 with X2 (only permissible in “separated”
mode).
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 361: Description of the Configuration Scripts for “Networking - TCP/IP”
ve
Default Gateway 1
Current status of the default
gateway 1.
get_default_gateway_
read Possible return values:
config number=1 state
Default - enabled Immedia
Gateway - disabled tely
config_default_gateway Possible entries for <Value>:
write number=1 - enabled
state=<stateval> - disabled
get_default_gateway_ Current IP address of the
read
config number=1 value configured default gateway 1
Enter the IP address of the
Default Immedia
default gateway 1 here.
Gateway config_default_gateway tely
write <gw> is an IP address with the
number=1 value=<gw>
format “Number.Number.Number.
Number.”
Current metric (cost factor) of the
get_default_gateway_
read default gateway 1
config number=1 metric
The default value is “20.”
Default Immedia
Enter the metric of the default
Gateway tely
config_default_gateway gateway 1 here.
write
number=1 metric=<n> <n> is a number between “0” and
“4.294.967.295.”
Default Gateway 2
See “Default Gateway 1.” When calling the gateway number, replace 1 with 2.
DNS Server 1
DNS server address with the
read get_dns_server 1
consecutive number 1
Set the address of the DNS
edit_dns_server
server with 1 as the consecutive
dns-server-nr=1
write/ number.
change=change Immedia
DNS Server 1 change <Value> is an IP address with the
dns-server- tely
format “Number.Number.Number.
name=<Value>
Number.”
edit_dns_server
write/ Delete the DNS server with the
dns-server-nr=1
delete consecutive number 1.
delete=delete
DNS Server 2 … n
See “DNS Server 1.” When calling, adjust the server number (2 … n).
Add DNS Server
Add additional DNS addresses
edit_dns_server here.
Immedia
Add DNS server write add=add dns-server- <Value> is an IP address with the
tely
name=<Value> format “Number.Number.Number.
Number.”
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 362: Description of the Configuration Scripts for “Networking - ETHERNET”
Switch Configuration
Query the switch
configuration:
read get_dsa_mode Possible return values:
- 0 = „switched“ mode
Interface Mode - 1 = „separated“ mode Immediately
Set the switch configuration:
set_dsa_mode -v Possible entries for <value>:
write
<value> - 0 = „switched“ mode
- 1 = „separated“ mode
Interface X1
Query the port state:
get_eth_config Possible return values:
read
X1 state - enabled
- disabled
Port State Immediately
config_ethernet port=X1
Activate port: enabled
state=enabled
write
config_ethernet port=X1
Deactivate port: disabled
state=disabled
Query the status of the
autonegotiation function:
get_eth_config
X1 autoneg
- enabled
- disabled
config_ethernet port=X1 Activate the autonegotiation
autoneg=on function: on
Deactivate the autonegotiation
function: off
Autonegotiation Note: You must also indicate Immediately
the speed and duplex value
config_ethernet port=X1 when you deactivate the
write
autoneg=off autonegotiation function.
speed=<value> Possible entries for speed:
duplex=<value> - 10M
- 100M
Possible entries for duplex:
- half
- full
get_eth_config
read Display of ETHERNET speed
X1 speed
get_eth_config
read Display of the Duplex mode
X1 duplex
Change the ETHERNET
Speed and speed and the Duplex mode. Immediately
Duplex Settings config_ethernet port=X1 Possible entries for speed:
autoneg=off - 10M
write
speed=<value> - 100M
duplex=<value> Possible entries for duplex:
- half
- full
Interface X2
See “Interface X1”. When calling these up, replace “X1” with “X2”.
</dg_
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 363: Description of the Configuration Scripts for “NTP”
ve
Configuration Data
Query the status of the NTP
server
get_ntp_config
read Possible return values are:
state
- enabled Immedia
State
- disabled tely
Possible entries for <Value>:
config_sntp
write - enabled
state=<Value>
- disabled
get_ntp_config Port number of the NTP server
read
port Immedia
Port
config_sntp Enter the port number for tely
write
port=<Value> <Value>.
Query the IP address of the time
get_ntp_config
read server: N = 1 … 4 for querying
time-server-<N>
one of 4 time servers.
Enter the IP address of 4 time
Immedia
Time Server servers
config_sntp tely
<N> can be a value from 1 to 4.
write time-server-
<Value> is an IP address with the
<N>=<Value>
format “Number. Number.
Number. Number.”
Query the time in seconds
get_ntp_config
read between two requests to the time
Update Time update-time Immedia
server.
(seconds) tely
config_sntp Specify the time-server's query
write
update-time=<Value> cycle (in s) for <Value>.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 364: Description of the Configuration Scripts for “Clock”
Clock
Time and Date
get_clock_data
read Local time and date
date-local
Date on device,
config_clock Immediately
local Change date. The format for
write type=local
<date> is: DD.MM.YYYY
date=<Datum>
get_clock_data
read Time/UTC
time-utc
Time on device,
Change time, based on UTC Immediately
UTC config_clock
write time. The format for <time> is:
type=utc time=<Time>
hh:mm:ss xx
get_clock_data
read Time/local time
time-local
Time on device,
Change time, based on local Immediately
local config_clock
write time. The format for <time> is:
type=local time=<Time>
hh:mm:ss xx
Presentation format either as
12 or 24-hour format:
get_clock_data
display-mode
- 12-hour-format
12-Hour- - 24-hour-format
Immediately
Format Set the presentation format
config_clock _ for the time.
write display_mode Possible entries for <Value>:
display-mode=<value> - 12-hour-format
- 24-hour-format
Time Zone
Currently set time zone –
get_clock_data
read original TZ string as stored in
tz-string
the operating system.
TZ-String Change TZ string directly. Immediately
config_timezone Example of <String>:
write
tz-string=<String> CET-1CEST,
M3.5.0/2,M10.5.0/3
Table 365: Description of the Configuration Scripts for "Administration"

ve
Administration
Configuration of Serial Interface
User of the serial interface
get_coupler_details Possible return values are:
read
RS232-owner - Linux
Configuration of - None immedia
serial interface User of the serial interface tely
config_RS232 Possible entries for <value> are:
write
owner=<value> - Linux
- None
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 365: Description of the Configuration Scripts for "Administration"
ve
Configuration of Service Interface
User of the serial interface.
Active: Current value
Configured: Value set, but not
applied by a reboot
Possible return values are:
get_service_interface_ immedia
read - service (WAGO-I/O-CHECK,
config mode tely
WAGO-I/O-PRO,
Configuration of
e!COCKPIT)
Service
- linux (Linux® console)
Interface
- free (unused, free for
application)
User of the serial interface.
config_service_interface after
write - service
_config mode=<value> Restart
- linux
- free
Reboot Controller
immedia
- write start_reboot Restart the controller.
tely
</dg_
Table 366: Description of Configuration Scripts for “Package Server”

Parameters Status Call-Up Output/Input Valid
Firmware Update
Specifies the medium for the
Medium for get_filesystem_data Right
read active partition
active partition active-partition-medium away
(sd-card, internal-flash-emmc).
Generates a backup of the
selected packet on the specified
medium.
Parameter:
<Value1> = 1, if the “Settings”
package is to be selected.
firmware_backup
<Value2> = 1, if the “CODESYS
package-
Project” package is to be
settings=<Value1>
selected.
package-
<Value3> = 1, if the “System”
Create codesys=<Value2>
package is to be selected. Right
firmware write package-
<Value4> = target medium for away
backup system=<Value3>
saving the backup. (sd-card,
device-
network)
medium=<Value4>
<Value5> = 1, if “Auto Update”
auto-update=<Value5>
function is to be activated.
download-dir=<Value6>
<Value6> = target directory for
backup file, if “network” is
selected as target medium.
Parameters, which are not to be
set (1) can either be set to 0 or
omitted completely.
</dg_
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 367: Description of Configuration Scripts for “Ports and Services” – “Network Services
Network Services
Telnet
Read the status of the Telnet
server.
get_port_state
telnet
- enabled Right
Telnet Port
- disabled away
config_port Possible entries for <Value>:
write port=telnet - enabled
state=<Value> - disabled
FTP
Read the status of the FTP
server.
config_ssl
ftp-status
- enabled Right
FTP Port
- disabled away
Possible entries for <Value>:
config_port
write - enabled
port=ftp state=<Value>
- disabled
FTPS
Read the status of the FTPS port.
read config_ssl ftps-status
- enabled
- disabled Right
FTPS Port
Activate/Deactivate FTPS. away
config_port port=ftps Possible entries for <Value>:
write
state=<Value> - enabled
- disabled
HTTP
Read the status of the HTTP port.
read config_ssl http-status
- enabled
- disabled Right
HTTP Port
Activate/Deactivate HTTP. away
config_port port=http Possible entries for <Value>:
write
- disabled
HTTPS
Read the status of the HTTPS
port.
read config_ssl https-status Possible return values:
- enabled
Right
HTTPS Port - disabled
away
Activate/Deactivate HTTPS.
config_port port=https Possible entries for <Value>:
write
- disabled
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 368: Description of Configuration Scripts for “Ports and Services” – “PLC Runtime Services”
ve
General Settings
Version of the enabled PLC
runtime
get_runtime_config Possible return values:
read
running-version - 0 = no runtime enabled
- 2 = CODESYS V2 enabled
- 3 = e!RUNTIME enabled
PLC runtime Setting and, if necessary, Immedia
version stopping of the previous runtime tely
version and starting of required
config_runtime runtime- version
write
version=<value> Possible entries for <value>:
- 0 = do not enable runtime
- 2 = enable CODESYS V2
- 3 = enable e!RUNTIME
Calling web page when only
entering the IP address in the
web browser
get_runtime_config
default-webpage
- WBM (web based
Default web Immedia
management)
page tely
- Webvisu (web visualization)
config_runtime default- - WBM (web based
write
webpage=<value> management)
- Webvisu (web visualization)
config_linux_user
Change user=admin new-
Change the PLC runtime access Immedia
authentication write password=<value>
password tely
password confirm-
password=<value>
Manual
750-8214 PFC200; G2; 2ETH RS CAN
ve
CODESYS V2 Settings
Read status of the runtime-
get_runtime_config cfg- specific Webserver
read version=2 Webserver- Possible return values:
state - enabled
CODESYS2
- disabled Immedia
Webserver
Enable/disable runtime-specific tely
State
config_runtime cfg- Webserver
write version=2 Webserver- Possible entries for <value>:
state=<value> - enabled
- disabled
Read status of the port
authentication for communication
between the CODESYS V2 PC
get_runtime_config cfg-
read software and the controller
CODESYS2 version=2 authentication
Possible return values: Immedia
Port
- enabled tely
Authentication
- disabled
config_runtime cfg- Possible entries for <value>:
write version=2 - enabled
authentication=<value> - disabled
Read status of the port for
communication between the
CODESYS V2 PC software and
get_runtime_config
read the controller
service-state
CODESYS2 Possible return values: Immedia
Service State - enabled tely
- disabled
config_runtime service-
write - enabled
state=<value>
- disabled
Read value of set network port
get_runtime_config for communication between PC
read
CODESYS2 comm-port and controller
Immedia
Communication Default value is 2455
tely
Port Change port number
config_runtime comm-
write Enter the TCP/IP port number for
port=<value>
<value>.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
ve
e!Runtime Settings
Read status of the runtime-
get_runtime_config cfg- specific Webserver
read version=3 Webserver- Possible return values
state - enabled
e!RUNTIME
- disabled Immedia
Webserver
Enable/disable runtime-specific tely
State
config_runtime cfg- Webserver
write version=3 Webserver- Possible entries for <value>:
state=<value> - enabled
- disabled
Read status of the port
authentication for communication
between the e!COCKPIT PC
get_runtime_config cfg-
read software and the controller
e!RUNTIME version=3 authentication
Possible return values: Immedia
Port
- enabled tely
Authentication
- disabled
config_runtime cfg- Possible entries for <value>:
write version=3 - enabled
authentication= <value> - disabled
</dg_
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 369: Description of Configuration Scripts for “Ports and Services” – “SSH/TFTP”
SSH
SSH Server
Read the status of the SSH port.
read get_ssh_config state
- enabled
- disabled
Indicates whether logon as root is
permitted.
get_ssh_config root-
access-state
- enabled
- disabled
Indicates whether authentication
by password (instead of PKI key
get_ssh_config files) is permitted.
read
password-request-state Possible return values:
- enabled
- disabled
get_ssh_config port- Right
SSH read Specifies the SSH port
number away
Activate/Deactivate SSH service.
config_ssh Possible entries for <Value>:
write
- disabled
config_ssh port-
write Set the SSH port
number=<Value>
Permit/Prohibit logon as root.
config_ssh root-access- Possible entries for <Value>:
write
state-value=<Value> - enabled
- disabled
Permit/Prohibit authentication by
config_ssh password- password.
write request-state- Possible entries for <Value>:
value=<Value> - enabled
- disabled
TFTP
TFTP Server
Read the status of the TFTP port.
read get_tftp_config state
- enabled
- disabled
get_tftp_config
read Read the TFTP main directory.
download-dir Right
TFTP
Activate/Deactivate TFTP port. away
config_tftp Possible entries for <Value>:
write
- disabled
config_tftp download-
write Set the TFTP main directory.
dir=<Value>
<
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 370: Description of Configuration Scripts for “SNMP”
General SNMP information parameters
get_snmp_data Specifies the SNMP parameter Right
read
device-name “sysName”. away
Name of device Change the SNMP parameter
config_snmp After
write “sysName”
device-name=<Value> * restart
(<Value> = string).
get_snmp_data Specifies the SNMP parameter Right
read
description “sysDescr”. away
Description Change the SNMP parameter
config_snmp After
write “sysDescr”
description=<Value> restart
(<Value> = string). *
get_snmp_data Specifies the SNMP Right
read
physical-location “sysLocation” parameter. away
Physical
config_snmp Change the SNMP parameter
location After
write physical- “sysLocation”
* restart
location=<Value> (<Value> = string).
get_snmp_data Specifies the SNMP “sysContact” Right
read
contact parameter. away
Contact Change the SNMP parameter
config_snmp After
write “sysContact”
contact=<Value> restart
(<Value> = string).
* When entering values, the blank characters must be filled by either “+” or “%20”. If this is not
done, the input is not recognized as a coherent string.

SNMP Manager configuration for v1 and v2c
Outputs the status of the SNMP
protocol for v1/v2c as a string.
get_snmp_data Right
Protocol status read Possible return values:
v1-v2c-state away
- enabled
- disabled
Local
get_snmp_data Specifies the community name Right
Community read
v1-v2c-community-name set for v1/v2c/ away
Name
Activates/deactivates the v1/v2c
protocol (<Value1> = enabled or
disabled) and assigns a
community name. (<Value2> =
string without spaces, min. 1,
max. 32 characters).
config_snmp
Protocol
v1-v2c-state=<Value1> After
Status/Commu write Note:
v1-v2c-community- restart
nity Name No community name is required
name=<Value2>
for deactivation.
Activation is only possible by
entering a community name. A
community name can only be
saved when the protocol is
activated.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
SNMP Trap Receiver Configuration for v1 and v2c
Any number of trap receivers can be configured. A trap receiver that has been set up is always
active; the data set must be completely deleted to deactivate it.
Specifies the IP address of the
trap receiver that the controller is
to send the v1 or v2 traps to.
The <number> parameter

enables consecutive reading of
get_snmp_data
IP address of a related data from the individually Right
read v1-v2c-trap-receiver-
trap receiver configured trap receiver for a away
address <Nummer>
short period of time (without
interim changing of the data).
This is a consecutive number that
is not connected to the data. If
the number is not included, the
data of the first receiver are read.
Specifies the community name
get_snmp_data that the SNMP agent of the
Community v1-v2c-trap-receiver- controller sends in the Trap Right
read
Name community-name Header. away
<Nummer> Parameter <number> see section
“IP Address of a Trap Receiver”.
Specifies the SNMP version (“v1”
or “v2c”) via which the SNMP
get_snmp_data
agent sends the traps to the Right
Trap version read v1-v2c-trap-receiver-
associated trap receiver address. away
version <Nummer>
Parameter <number> see section
“IP Address of a Trap Receiver”.
Create a new trap receiver
(value1=add) or delete an
already configured trap receiver
(value1=delete).
Other parameters:
<Value2> = IP address
config_snmp
(number.number.number.number
v1-v2c-trap-receiver-
) that the controller is to send the
edit=<Value1>
traps to.
Creating/ <Value3>: Community string
address=<Value2> After
deleting a trap write (string), which the controller
v1-v2c-trap-receiver- restart
receiver enters in the trap header.
community-
<Value4>: SNMP version, via
name=<Value3>
which the traps are sent (v1 or
v2c).
version=<Value4>
Note:
All parameters must also be
entered when deleting a trap
receiver, as this is the only
means to uniquely identify the
data set.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Configuration of SNMP v3
Any number of SNMP v3 users can be created. A user that has been set up is always active; the
complete data set must be deleted to deactivate a user.
Specifies the user name for the
v3 user.
The <number> parameter
enables consecutive reading of
the related data from the
get_snmp_data individually configured trap
Authentication Right
read v3-auth-name receiver for a short period of time
Name away
<Nummer> (without interim changing of the
data). This is a consecutive
number that is not connected to
the data. If the number is not
included, the data of the first user
are read.
Specifies the type of encryption
that the v3 user uses (none,
Authentication get_snmp_data Right
read MD5, or SHA).
encryption type v3-auth-type <Number> away
Parameter <number> see
“Authentication Name”.
Specifies the key string for
Authentication get_snmp_data authentication. Right
read
key v3-auth-key <Nummer> Parameter <number> see away
Specifies the type of privacy
encryption for the v3 user (none,
Privacy get_snmp_data Right
read DES, or AES).
encryption type v3-privacy <number> away
Specifies the key string for
privacy. If nothing is entered, the
get_snmp_data
SNMP agent uses the Right
Privacy key read v3-privacy-key
“Authentication Key”. away
<number>
IP address of an SNMP manager
that the agent traps for this v3
get_snmp_data user are sent to. If nothing is
Trap receiver Right
read v3-notification-receiver entered here, no traps are sent
address away
<number> for this user.
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Creating a new v3 user.
This must be a new, unique user
name.
Parameters:
User name (<Value1> = string,
min. 8 and max. 32 characters,
lower case letters (a … z), upper
case letters (A … Z), numbers
(0 … 9), special characters !()*~'.-
_ but no spaces)
Encryption method. (<Value2> =
none, MD5 or SHA).
config_snmp Key string for authentication,
v3-edit=add (<Value3> = String, min. 8 and
v3-auth-name=<Value1> max. 32 characters, lower case
v3-auth-type=<Value2> letters (a … z), upper case letters
Add new v3- v3-auth-key=<Value3> (A … Z), numbers (0 … 9), After
write
User v3-privacy=<Value4> special characters !()*~'.-_ but no restart
v3-privacy- spaces)
key=<Value5> Privacy encryption method
v3-notification- (<Value4> = none, DES or AES).
receiver=<Value6> Privacy key string (<Value5> =
String, min. 8 and max. 32
characters, lower case letters
(a … z), upper case letters
(A … Z), numbers (0 … 9),
special characters !()*~'.-_ but no
spaces), can also be blank; in
this case the authentication key
will be used. The IP address of a
trap receiver is transmitted as the
notification receiver (<Value6> =
number.number.number.number)
This parameter is not required if
no v3 traps are to be sent.
Deleting a v3 user that has been
set up.
Because the doubled allocation
config_snmp
of the same user name is After
Delete v3 user write v3-edit=delete
prevented when creating a user, restart
v3-auth-name=<Value>
the name is sufficient to uniquely
identify a data set (<Value> =
string).
19.3.1.10 WagoLibCpuUsage.lib

“WagoLibCpuUsage.lib” library:
- CPU_Usage
The document containing the description of the library and the function block it
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.3.1.11 WagoLibDiagnosticIDs.lib

“WagoLibDiagnosticIDs.lib” library:
- DIAGNOSTIC_SEND_ID
- DIAGNOSTIC_SET_TEXT_FOR_ID
19.3.1.12 WagoLibLed.lib

“WagoLibLed.lib” library:
- LED_SET_STATIC
- LED_SET_BLINK
- LED_SET_FLASH
- LED_SET_ERROR
- LED_RESET_ERROR
- LED_RESET_ALL_ERRORS
- LED_GET_STATE
- LED_GET_STATE_ASYNC
19.3.1.13 WagoLibNetSnmp.lib

“WagoLibNetSnmp.lib” library:
- snmpGetValueCustomOID_INT32
- snmpGetValueCustomOID_STRING
- snmpGetValueCustomOID_UINT32
- snmpRegisterCustomOID_INT32
- snmpRegisterCustomOID_STRING
- snmpRegisterCustomOID_UINT32
- snmpSetValueCustomOID_INT32
- snmpSetValueCustomOID_STRING
- snmpSetValueCustomOID_UINT32
19.3.1.14 WagoLibNetSnmpManager.lib

“WagoLibNetSnmpManager.lib” libraries:
Manual
750-8214 PFC200; G2; 2ETH RS CAN
- SNMPM_DINT_TO_TLV
- SNMPM_UDINT_TO_TLV
- SNMPM_STRING_TO_TLV
- SNMPM_TLV_TO_DINT
- SNMPM_TLV_TO_UDINT
- SNMPM_TLV_TO_STRING
- SNMPM_GET
- SNMPM_GET_V3
- SNMPM_SET
- SNMPM_SET_V3
19.3.1.15 WagoLibSSL.lib

“WagoLibSSL.lib” library:
- SSL_CTX
- SSL_CTX_load_verify_locations
- SSL_CTX_sess_set_cache_size
- SSL_CTX_set_client_CA_list
- SSL_CTX_set_method
- SSL_CTX_use_certificate_file
- SSL_CTX_use_PrivateKey_file
- SSL_free
- SSL_get_error
- SSL_Hndshk_Accept
- SSL_Hndshk_Connect
- SSL_load_client_CA_file
- SSL_read
- SSL_shutdown
- SSL_write
19.3.1.16 WagoLibTerminalDiag.lib

“WagoLibTerminalDiag.lib” library:
- GET_TERMINALDIAG
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.3.2 Libraries for a CANopen and CANLayer2 Link

This section contains libraries supported by the controller 750-8214 for linking
with CANopen and CANLayer2.
19.3.2.1 WagoCANLayer2_02.lib

“WagoCANLayer2_02.lib” library:
- CAN_CLOSE
- CAN_ERROR_INFO
- CAN_LAYER2_VERSION
- CAN_OPEN
- CAN_RESET
- CAN_RX_11BIT_FRAME
- CAN_RX_29BIT_FRAME
- CAN_SET_LED
- CAN_TX_11BIT_FRAME
- CAN_TX_29BIT_FRAME
19.3.2.2 WagoCANopen_02.lib
The controller 750-8214supports the following functions blocks of the

“WagoCANopen_02.lib” library:
- CIA405_GET_KERNEL_STATE
- CIA405_GET_LOCAL_NODE_ID
- CIA405_RECV_EMCY
- CIA405_RECV_EMCY_DEV
- CIA405_GET_STATE
- CIA405_RECV_EMCY_DEV
- CIA405_NMT
- CANOPEN_VERSION
- NMT_GUARD_ERROR
- NMT_GUARD_ERROR_DEV
- CIA405_SDO_WRITE4
- CIA405_SDO_READ4
- CIA405_SDO_WRITEXX
- CIA405_SDO_READXX
Manual
750-8214 PFC200; G2; 2ETH RS CAN
19.3.2.3 WagoCANopenDiag.lib
The controller 750-8214 supports the following function blocks of the

“WagoCANopenDiag.lib” library:
- CANOPEN_DIAG
Manual
526 List of Figures WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
List of Figures
Figure 1: View ....................................................................................................33
Figure 2: Marking Area for Serial Numbers ........................................................35
Figure 3: CAGE CLAMP® connections ...............................................................36
Figure 4: Service Interface (Closed and Open Flap) ...........................................37
Figure 5: Network Connections – X1, X2 ............................................................38
Figure 6: CANopen – X4 Fieldbus Connection ...................................................39
Figure 7: CANopen Standard Bus Termination...................................................40
Figure 8: RS-232/RS-485 – Communication Interface – X3................................41
Figure 9: Termination with DTE-DCE Connection (1:1) ......................................42
Figure 10: Termination with DCE-DCE Connection (Cross-Over) .......................42
Figure 11: RS-485 Bus Termination ...................................................................43
Figure 12: Data Contacts ...................................................................................44
Figure 13: Power Jumper Contacts ....................................................................45
Figure 14: Power Supply Indicating Elements ....................................................46
Figure 15: Indicating elements for fieldbus/system .............................................47
Figure 16: Indicating Elements, RJ-45 Jacks......................................................48
Figure 17: Indicating Elements, Memory Card Slot .............................................49
Figure 18: Mode Selector Switch ........................................................................50
Figure 19: Reset Button .....................................................................................51
Figure 20: Slot for SD Memory Card ..................................................................52
Figure 21: Schematic diagram............................................................................53
Figure 22: Example of Interface Assignment via WBM .......................................61
Figure 23: One Bridge with Two Ports ................................................................63
Figure 24: Two Bridges with One/One Ports ......................................................63
Figure 25: Connecting the Controller to a Cloud Service (Example) ...................77
Figure 26: Spacing .............................................................................................91
Figure 27: Release Tab of Controller (Example).................................................93
Figure 28: Connecting a Conductor to a CAGE CLAMP® ...................................94
Figure 29: Power Supply Concept ......................................................................96
Figure 30: “Open DHCP”, Example Figure .......................................................101
Figure 31: CBM main menu (example) .............................................................102
Figure 32: CBM – Selecting “Networking”.........................................................103
Figure 33: CBM – Selecting “TCP/IP” ...............................................................103
Figure 34: CBM – Selecting “IP address” .........................................................103
Figure 35: CBM – Selecting the IP Address .....................................................104
Figure 36: CBM – Entering a New IP Address ..................................................104
Figure 37: “WAGO Ethernet Settings” – Starting Screen (Example) .................105
Figure 38: “WAGO Ethernet Settings” – “Network” Tab ....................................106
Figure 39: Example of a Function Test .............................................................108
Figure 40: Entering Authentication ...................................................................115
Figure 41: Password Reminder ........................................................................117
Figure 42: WBM Browser Window (Example) ...................................................121
Figure 43: WBM Header with Tabs that Cannot be Displayed (Example) .........121
Figure 44: WBM Status Bar (Example) .............................................................122
Figure 45: CBM main menu (example) .............................................................124
Figure 46: “WAGO Ethernet Settings” – Start Screen .......................................128
Figure 47: “WAGO Ethernet Settings” – Communication Link ..........................129
Manual
WAGO I/O System 750 List of Figures 527
750-8214 PFC200; G2; 2ETH RS CAN
Figure 48: “WAGO Ethernet Settings” – Identification Tab (Example) ..............130
Figure 49: “WAGO Ethernet Settings” – Network Tab ......................................131
Figure 50: “WAGO Ethernet Settings” – Protocol Tab ......................................133
Figure 51: “WAGO Ethernet Settings” – Status Tab .........................................134
Figure 52: Target System Settings (1) ..............................................................136
Figure 53: Target System Settings (2) ..............................................................136
Figure 54: Creating a New Function Block .......................................................137
Figure 55: Programming Interface With the PLC_PRG Program Module..........137
Figure 56: “Resources” Tab..............................................................................138
Figure 57: Control Configuration – Edit ............................................................139
Figure 58: “Start WAGO-I/O-CHECK and Scan” Button ...................................139
Figure 59: WAGO-I/O-CHECK – Starting Screen .............................................140
Figure 60: I/O Configurator Empty ....................................................................141
Figure 61: “Add I/O Modules” Button ................................................................141
Figure 62: “Module Selection” Window .............................................................142
Figure 63: I/O Configurator with Defined I/O Modules ......................................142
Figure 64: Variable declaration.........................................................................143
Figure 65: Control Configuration: I/O Modules with Their Associated Addresses
................................................................................................................143
Figure 66: Program Function Block ..................................................................144
Figure 67: Input Assistant for Selecting Variables ............................................144
Figure 68: Example of an Allocation .................................................................145
Figure 69: Creating a Communication Link – Step 1 ........................................146
Figure 72: Task Configuration ..........................................................................149
Figure 73: Changing Task Names 1 .................................................................150
Figure 74: Call-up to Add to the Program Module .............................................151
Figure 75: Cyclic Task ......................................................................................152
Figure 76: Freewheeling Task ..........................................................................153
Figure 77: Debugging (Case 1) ........................................................................154
Figure 84: CODESYS – System Events ...........................................................158
Figure 85: CODESYS Program Provokes Division by “0” .................................160
Figure 86: CODESYS – Creating and Activating an Event Handler ..................160
Figure 87: CODESYS – New Module has been Generated ..............................161
Figure 88: CODESYS – Enter the Event in a Global Variable ...........................161
Figure 89: CODESYS – Variable Contents Prior to Division by “0” ...................162
Figure 90: CODESYS – Variable Contents After Division by “0” and Call-up of the
Event Handler .........................................................................................162
Figure 91: Process Image ................................................................................165
Figure 92: Flag Area ........................................................................................165
Figure 93: Local Bus Synchronization (Case 1) ................................................170
Manual
528 List of Figures WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
Figure 97: Local Bus (KBus) Settings ...............................................................174
Figure 98: Program Memory (Example) ...........................................................177
Figure 99: Data Memory and Function Block Limitation (Example)...................178
Figure 100: Remanent Main Memory (Example) ..............................................179
Figure 101: Flag and Retain Memory (Example) ..............................................179
Figure 102: General Target System Settings ....................................................180
Figure 103: Selecting the Visualization Technique in the Target System Settings
................................................................................................................181
Figure 104: Creating the PLC_VISU Starting Visualization ...............................182
Figure 105: Remanent Main Memory ...............................................................190
Figure 106: CODESYS PLC Configuration - Modbus Settings .........................192
Figure 107: Modbus Process Image .................................................................198
Figure 108: Flag Area.......................................................................................199
Figure 109: State Diagram, STANDARD_WATCHDOG Operation Mode .........209
Figure 110: State Diagram, ALTERNATIVE_WATCHDOG Operation Mode ....210
Figure 111: State Diagram, Switchover Operation Mode ..................................211
Figure 112: Modbus Address Overview ............................................................220
Figure 113: State Diagram, ADVANCED_WATCHDOG Operation Mode.........223
Figure 114: State Diagram, SIMPLE_WATCHDOG Operation Mode ...............224
Figure 115: State Diagram, Switching Operation Modes ..................................224
Figure 116: Correlation Between “IEC 61131-3” Variables and PFC Variables.242
Figure 117: Adding the CANopen Master .........................................................246
Figure 118: Basic Parameters Tab (Master) .....................................................247
Figure 119: CAN Parameters Tab (Master) ......................................................248
Figure 120: Module Parameters Tab (Master) ..................................................249
Figure 121: Adding a CANopen Slave ..............................................................250
Figure 122: Basic Parameters Tab (Slave) .......................................................251
Figure 123: CAN Parameters Tab (Slave) ........................................................252
Figure 124: CAN Module Selection Tab ...........................................................255
Figure 125: PDO Mapping Tab.........................................................................256
Figure 126: PDO Properties Window................................................................257
Figure 127: Service Data Objects Tab..............................................................259
Figure 128: Adapting SDOs..............................................................................260
Figure 129: “Module Parameters” Tab (Slave) .................................................261
Figure 130: Attaching a CANopen Slave ..........................................................262
Figure 131: Configuring a CANopen Slave .......................................................262
Figure 132: Configuration of the CANopen Slave Variables .............................263
Figure 133: Configuration of CANopen Slave Parameters ................................264
Figure 134: “Resources” Tab............................................................................266
Figure 135: “Open” Dialog Window ..................................................................267
Figure 136: Module Icon in the Menu Bar; FUP Programming Language .........267
Figure 137: Instance of the Function Block DiagGetBusState() in FUP ............267
Figure 138: Function Block DiagGetState() in FUP ..........................................268
Figure 139: Off-line View of Variable Window in CODESYS.............................268
Figure 140: Online View of Variable Window (Top Window) in FUP .................270
Figure 141: Example of Diagnostics .................................................................270
Figure 142: DiagGetState() Diagnostic Call ......................................................271
Figure 143: Online View of the EXTENDEDINFO Array in Binary Representation
................................................................................................................273
Manual
WAGO I/O System 750 List of Figures 529
750-8214 PFC200; G2; 2ETH RS CAN
Figure 144: Attaching the CANopen Master .....................................................276
Figure 145: Setting the Baud Rate ...................................................................277
Figure 146: EDS File “Generic CAN Device” ....................................................277
Figure 147: “Module Parameters” Tab..............................................................278
Figure 148: “CAN Parameters“ Tab ..................................................................278
Figure 149: Attaching the CAN Layer2 Device .................................................279
Figure 150: Power Supply Indicating Elements ................................................280
Figure 151: Indicating elements for fieldbus/system .........................................281
Figure 152: Indicating Elements, RJ-45 Jacks ..................................................289
Figure 153: Indicating Elements, Memory Card Slot .........................................290
Figure 154: Flashing Sequence Process Diagram ............................................291
Figure 155: Inserting the Memory Card ............................................................300
Figure 156: Release Tab of Controller (Example).............................................307
Figure 157: Marking Example According to ATEX and IECEx ..........................311
Figure 158: Text Detail – Marking Example According to ATEX and IECEx .....311
Figure 159: Marking Example for Approved I/O Module Ex i According to ATEX
and IECEx ...............................................................................................313
Figure 160: Text Detail – Marking Example for Approved I/O ModuleEx i
According to ATEX and IECEx ................................................................313
Figure 161: Marking Example According to NEC..............................................315
Figure 162: Text Detail – Marking Example According to NEC 500 ..................315
Figure 163: Text Detail – Marking Example for Approved I/O Module Ex i
According to NEC 505.............................................................................316
According to NEC 506.............................................................................316
According to CEC 18 attachment J .........................................................317
Figure 166: Graphical Representation of the “ConfigToolFB” Function Block ...504
Manual
530 List of Tables WAGO I/O System 750
750-8214 PFC200; G2; 2ETH RS CAN
List of Tables
Table 1: Number Notation ..................................................................................20
Table 2: Font Conventions .................................................................................20
Table 3: Legend for Figure “View” ......................................................................33
Table 4: Legend for figure “CAGE CLAMP® connections” ..................................36
Table 5: Service Interface ..................................................................................37
Table 6: Legend for Figure “Network Connections – X1, X2” ..............................38
Table 7: Legend for Figure “CANopen – X4 Fieldbus Connection” .....................39
Table 8: Legend for Figure “RS-232/RS-485 – Communication Interface – X3” .41
Table 9: Function of RS-232 Signals for DTE/DCE ............................................42
Table 10: Legend for Figure “Power Jumper Contacts” ......................................45
Table 11: Legend for Figure “Power Supply Indicating Elements” ......................46
Table 12: Legend for Figure “Fieldbus/System Indicating Elements” ..................47
Table 13: Legend for Figure “Indicating Elements, RJ-45 Jacks” ........................48
Table 14: Legend for Figure “Indicating Elements, Memory Card Slot” ...............49
Table 15: Mode Selector Switch .........................................................................50
Table 16: Mode Selector Switch .........................................................................50
Table 17: Technical Data – Mechanical Data .....................................................54
Table 18: Technical Data – System Data ...........................................................54
Table 19: Technical Data – Power Supply ..........................................................54
Table 20: Technical Data – Clock .......................................................................55
Table 21: Technical Data – Programming ..........................................................55
Table 22: Technical Data – Local Bus ................................................................55
Table 23: Technical Data – ETHERNET.............................................................56
Table 24: Technical Data – CANopen ................................................................56
Table 25: Technical Data – Communication Interface ........................................56
Table 26: Technical Data – Field Wiring .............................................................57
Table 27: Technical Data – Power Jumper Contacts ..........................................57
Table 28: Technical Data – Data Contacts .........................................................57
Table 29: Technical Data – Climatic Environmental Conditions ..........................57
Table 30: MAC ID and IP Address Assignment for One Bridge with Two Ports ..63
Table 31: MAC ID and IP Address Assignment for Two Bridges with One/One
Ports .........................................................................................................63
Table 32: Services and Users ............................................................................64
Table 33: WBM Users ........................................................................................65
Table 34: Linux Users ........................................................................................66
Table 35: List of Parameters Transmitted via DHCP ..........................................75
Table 36: Components of the Cloud Connectivity Software Package .................78
Table 37: Loading a Boot Project .......................................................................86
Table 38: WAGO DIN Rails ................................................................................91
Table 39: Filter Modules for 24 V Supply ............................................................96
Table 40: Default IP Addresses for ETHERNET Interfaces ..............................100
Table 41: Network Mask 255.255.255.0 ...........................................................100
Table 42:User Settings in the Default State ......................................................117
Table 43: Access Rights for WBM Pages .........................................................118
Table 44: CBM Menu Structure ........................................................................125
Table 45: Syntax of Logical Addresses ............................................................148
Table 46: Events ..............................................................................................159
Manual
WAGO I/O System 750 List of Tables 531
750-8214 PFC200; G2; 2ETH RS CAN
Table 47: Access to the Process Images of the Input and Output Data – Local
Bus .........................................................................................................166
Table 48: Access to the Process Images of the Input and Output Data – Modbus
................................................................................................................167
Table 49: Access to the Process Images of the Input and Output Data –
PROFIBUS .............................................................................................167
CANopen ................................................................................................167
PROFIBUS .............................................................................................167
Table 52: Access to the Process Images of the Input and Output Data – Flags168
Table 53: Arrangement of the I/O Modules for the Addressing Example ..........168
Table 54: Addressing Example.........................................................................168
Table 55: Local Bus (KBus) Settings ................................................................175
Table 56: Errors and Remedies ........................................................................185
Table 57: CODESYS V3 Priorities ....................................................................189
Table 58: Modbus Settings ...............................................................................193
Table 59: Modbus TCP Settings .......................................................................194
Table 60: Modbus UDP Settings ......................................................................194
Table 61: Modbus RTU Settings ......................................................................195
Table 62: Modbus Mapping for Read Bit Services FC1, FC2............................200
Table 63: Modbus Mapping for Write Bit Services FC5, FC15 ..........................201
Table 64: Modbus Mapping for Read Register Services FC3, FC4, FC23 ........202
................................................................................................................204
Table 66: WAGO Modbus Registers ................................................................206
Table 67: Watchdog Commands ......................................................................212
Table 68: Watchdog Status ..............................................................................213
Table 69: Watchdog Configuration ...................................................................214
Table 70: Watchdog Operation Modes .............................................................215
Table 71: Diagnostics for the Error Server........................................................217
Table 72: WAGO Modbus Registers ................................................................221
Table 73: Watchdog Commands ......................................................................225
Table 74: Watchdog Status ..............................................................................226
Table 75: Watchdog Configuration ...................................................................227
Table 76: Overview of Addresses in the Object Directory .................................232
Table 77: Indexing of “IEC 61131-3” Variable Data in the Object Directory ......240
Table 78: Fieldbus Access to PFC Output Data ...............................................241
Table 79: Examples for CODESYS Access to PFC Variables ..........................243
Table 80: Maximum Indices and Sub-Indices for “IEC 61131-3” Variables .......244
Table 81: Example of “IEC 61131-3” Output Variables .....................................245
Table 82: Description of Basic Parameters (Master) ........................................247
Table 83: Description of the CAN Parameters (Master) ....................................248
Table 84: Description of the Module Parameters (Master) ................................249
Table 85: Description of Basic Parameters (Slave) ..........................................251
Table 86: Description of the CAN Parameters (Slave) ......................................253
Table 87: Receiving and Sending Description for PDO Mapping ......................257
Table 88: Description of the PDO Properties Window ......................................258
Table 89: Description of the Module Parameters (Slave) ..................................261
Table 90: Description of the CANopen Slave Variables Window ......................263
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 91: Description of CANopen Slave Settings............................................264
Table 92: Diagnostic Information Bits ...............................................................271
Table 93: System Power Supply Diagnistics ....................................................280
Table 94: Field-Side Supply Diagnostics ..........................................................280
Table 95: Diagnostics via SYS LED .................................................................282
Table 96: Diagnostics via SYS LED .................................................................283
Table 97: Diagnostics RUN LED ......................................................................284
Table 98: RUN LED Diagnostics ......................................................................285
Table 99: Diagnostics I/O LED .........................................................................286
Table 100: MS-LED Diagnostics ......................................................................287
Table 101: Diagnostics CAN LED.....................................................................288
Table 102: LNK-LED Diagnostics .....................................................................289
Table 103: ACT-LED Diagnostics .....................................................................289
Table 104: Diagnostics via Memory Card Slot LED ..........................................290
Table 105: Overview of Error Codes, I/O LED ..................................................293
Table 106: Error Code 1, Explanation of Blink Codes and Procedures for
Troubleshooting ......................................................................................294
Table 113: Overview of MS-LED Error Codes ..................................................299
Table 115: Description of Marking Example According to ATEX and IECEx .....312
Table 116: Description of Marking Example for Approved I/O Module Ex I
According to ATEX and IECEx ................................................................314
Table 117: Description of Marking Example According to NEC 500 .................315
Table 118: Description of Marking Example for Approved I/O Module Ex i
According to NEC 505.............................................................................316
According to NEC 506.............................................................................316
According to CEC 18 attachment J .........................................................317
Table 121: WBM “Device Status” Page – “Device Details” Group ....................321
Table 122: WBM “Device Status” Page – “Network TCP/IP Details” Group ......322
Table 123: WBM “PLC Runtime Information” Page – “Runtime” Group ............324
Table 124: WBM “PLC Runtime Information” Page – “Project Details” Group ..325
Table 125: WBM “PLC Runtime Information” Page – “Task n” Group(s)...........325
Table 126: WBM “PLC Runtime Configuration” Page – “General PLC Runtime
Configuration” Group...............................................................................331
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 127: WBM “PLC Runtime Configuration” Page – “Webserver Configuration”
Group ......................................................................................................333
Table 128: WBM “TCP/IP Configuration” Page – “TCP/IP Configuration” Group
................................................................................................................334
Table 129: WBM “TCP/IP Configuration” Page – “DNS Server” Group .............335
Table 130: WBM “Ethernet Configuration” Page – “Bridge Configuration” Group
................................................................................................................336
Table 131: WBM “Ethernet Configuration” Page – “Switch Configuration” Group
................................................................................................................337
Table 132: WBM “Ethernet Configuration” Page – “Ethernet Interface
Table 133: WBM “Configuration of Host and Domain Name” Page – “Hostname”
Group ......................................................................................................339
Table 134: WBM “Configuration of Host and Domain Name” Page – “Domain
Name” Group ..........................................................................................339
Table 135: WBM “Routing” Page – “IP Forwarding through multiple interfaces”
Group ......................................................................................................341
Table 136: WBM “Routing” Page – “Custom Routes“ Group ............................342
Table 137: WBM “Routing” Page – “IP-Masquerading” Group ..........................344
Table 138: WBM “Routing” Page – “Port Forwarding” Group............................345
Table 139: WBM “Clock Settings” Page – “Timezone and Format” Group ........346
Table 140: WBM “Clock Settings” Page – “UTC Time and Date” Group ...........346
Table 141: WBM “Clock Settings” Page – “Local Time and Date” Group ..........347
Table 142: WBM “Configuration of Serial Interface RS232” Page – “Assign
Owner of Serial Interface” Group.............................................................348
Table 143: WBM “Configuration of Service Interface” Page – “Assign Owner of
Service Interface” Group .........................................................................349
Table 144: WBM “Create Bootable Image” Page – “Create bootable image from
active partition” Group .............................................................................350
Table 145: WBM “Firmware Backup” Page – “Firmware Backup” Group ..........351
Table 146: WBM “Firmware Restore” Page – “Firmware Restore” Group .........353
Table 147: WBM “Active System” Page – “Boot Device” Group .......................355
Table 148: WBM “Active System” Page – “System <n> (Internal Flash)” Group
................................................................................................................355
Table 149: WBM “Mass Storage” Page – “Devices” Group ..............................356
Table 150: WBM “Mass Storage” Page – “Create new Filesystem on Memory
Card” Group ............................................................................................356
Table 151: WBM “Software Uploads” Page – “Upload New Software” Group ...357
Table 152: WBM “Configuration of Network Services” Page – “FTP” Group .....358
Table 153: WBM “Configuration of Network Services” Page – “FTPS (explicit
FTPS)” Group .........................................................................................358
Table 154: WBM “Configuration of Network Services” Page – “HTTP” Group ..359
Table 155: WBM “Configuration of Network Services” Page – “HTTPS” Group 359
Table 156: WBM “Configuration of Network Services” Page – “I/O-CHECK“
Group ......................................................................................................359
Table 157: WBM “Configuration of NTP Client” Page – “NTP Client Configuration”
Group ......................................................................................................360
Table 158: WBM “PLC Runtime Services” Page – “CODESYS V2” Group .......361
Table 159: WBM “PLC Runtime Services” Page – “e!RUNTIME” Group ..........362
Table 160: WBM “SSH Server Settings” Page – “SSH Server” Group ..............363
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 161: WBM “DHCP Server Configuration” Page – “DHCP Configuration
Bridge <n>” Group ..................................................................................364
Table 162: WBM “Configuration of DNS Server” Page – “DNS Server” Group .365
Table 163: WBM “Status Overview” Page – “Service” Group ...........................366
Table 164: WBM “Status Overview” Page – “Connection <n>” Group ..............366
Table 165: WBM “Configuration of Connection <n>” Page – “Configuration”
Group ......................................................................................................367
Table 166: Display of the Selection and Input Fields Depending on the Selected
Cloud Platform ........................................................................................369
Table 167: Choice of Data Protocol Depending on the Selected Cloud Platform
................................................................................................................371
Data Protocol ..........................................................................................371
Table 169: Choice of Cache Mode Depending on the Selected Data Protocol .371
Authentication .........................................................................................372
Table 171: WBM “Configuration of General SNMP Parameters” Page – “General
SNMP Configuration” Group ...................................................................373
Table 172: WBM “Configuration of SNMP v1/v2c Parameters” Page – “SNMP
v1/v2c Manager Configuration” Group.....................................................374
Table 173: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Actually
Configured Trap Receivers” Group .........................................................375
Table 174: WBM “Configuration of SNMP v3” Page – “Actually configured v3
Users” Group ..........................................................................................376
Table 175: WBM Page “Docker® Settings” – group “Docker® Status” ...............378
Table 176: WBM “WBM User Configuration” Page – “Change Password” Group
................................................................................................................379
Table 177: WBM “OPC UA Status” Page – “OPC UA Server” Group ...............380
Table 178: WBM “OPC UA Configuration” Page – “General OPC UA Server
Table 179: WBM page “OPC UA Configuration” – group “OPC UA Endpoint URL”
................................................................................................................381
Table 180: WBM “OPC UA Configuration” Page – “OPC UA Endpoints” Group
................................................................................................................382
Table 181: WBM Page “OPC UA Configuration” – “OPC UA Security Settings”
Group ......................................................................................................383
Table 182: WBM “OPC UA Information Model” Page – “OPC UA Server
Information Model” Group .......................................................................384
Table 183: WBM Page “OPC UA Server Certificates” – “OPC UA Server Own
Certificate” Group ....................................................................................385
Table 184: WBM Page “OPC UA Server Certificates” – “OPC UA Server Private
Keys” Group ............................................................................................385
Table 185: WBM Page “OPC UA Server Certificates” – “OPC UA Server Trusted /
Rejected Certificates” Group ...................................................................386
Table 186: WBM Page “OPC UA Client Certificates” – “OPC UA Client Own
Certificate” Group ....................................................................................387
Table 187: WBM Page “OPC UA Client Certificates” – “OPC UA Client Private
Keys” Group ............................................................................................387
Table 188: WBM Page “OPC UA Client Certificates” – “OPC UA Client Trusted /
Rejected Certificates” Group ...................................................................388
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 189: WBM “Modbus Services Configuration” Page – “Modbus TCP” Group
................................................................................................................389
Table 190: WBM “Modbus Services Configuration” Page – “Modbus UDP” Group
................................................................................................................389
Table 191: WBM Page “BACnet Status” – “BACnet Information” Group ...........390
Table 192: WBM Page “BACnet Status” – “BACnet License” Group ................390
Table 193: WBM Page “BACnet Configuration” – “BACnet Settings” Group .....391
Table 194: WBM Page “BACnet Configuration” – “BACnet Settings” Group .....391
Table 195: WBM Page “BACnet Configuration” – “BACnet Data Reset” Group 392
Table 196: WBM Page “BACnet Storage Location” – “BACnet Persistence”
Group ......................................................................................................393
Table 197: WBM Page “BACnet Storage Location” – “BACnet Trendlog” Group
................................................................................................................393
Table 198: WBM Page “BACnet Storage Location” – “BACnet Eventlog” Group
................................................................................................................394
Table 199: WBM Page “BACnet Files” – “BACnet override.xml” Group ............395
Table 200: WBM “OpenVPN / IPsec Configuration” Page – “OpenVPN” Group
................................................................................................................396
Table 201: WBM “OpenVPN / IPsec Configuration” Page – “IPsec” Group ......397
Table 202: WBM “General Firewall Configuration” Page – “Global Firewall
Parameter” Group ...................................................................................398
Table 203: WBM “Interface Configuration” Page – “Firewall Configuration Bridge
<n> / VPN / WAN” Group ........................................................................399
Table 204: WBM “Configuration of MAC Address Filter” Page – “Global MAC
address filter state” Group .......................................................................400
Table 205: WBM “Configuration of MAC Address Filter” Page – “MAC address
filter state Bridge <n>” Group ..................................................................401
Table 206: WBM “Configuration of MAC Address Filter” Page – “MAC address
filter whitelist” Group ...............................................................................401
Table 207: WBM “Configuration of User Filter” Page – “User Filter” Group .....402
Table 208: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate List”
Group ......................................................................................................404
Table 209: WBM “Configuration of OpenVPN and IPsec” Page – “Private Key
List” Group ..............................................................................................404
Table 210: WBM Page “Boot mode configuration” – “Force internal boot” Group
................................................................................................................405
Table 211: “Security Settings” WBM Page – “TLS Configuration” Group ..........406
Table 212: WBM “Advanced Intrusion Detection Environment (AIDE)” Page –
“Run AIDE check at startup” Group .........................................................407
Table 213: WBM “Advanced Intrusion Detection Environment (AIDE)” Page –
“Control AIDE and show log” Group ........................................................407
Table 214: WBM Page “WAGO Device Access” – “Unauthenticated Requests”
Group ......................................................................................................409
Table 215: WBM “Diagnostic Information” Page ...............................................410
Table 216: “Information” Menu .........................................................................411
Table 217: “Information” > “Controller Details” Submenu..................................411
Table 218: “Information” > “Network Details” Submenu ....................................412
Table 219: “PLC Runtime” Menu ......................................................................413
Table 220: “PLC Runtime” > “Information” Submenu ........................................413
Table 221: “PLC Runtime” > “Information” > “Runtime Version” Submenu .......414
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 222: “PLC Runtime” > “Information” > “Webserver Version” Submenu ...414
Table 223: “PLC Runtime” > “Information” > “State” Submenu .........................414
Table 224: “PLC Runtime” > “Information” > “Number of Tasks” Submenu ......415
Table 225: “PLC Runtime” > “Information” > “Project Details” Submenu...........415
Table 226: “PLC Runtime” > “Information” > “Tasks” Submenu ........................415
Table 227: “PLC Runtime” > “Information” > “Tasks” > “Task n” Submenu .......416
Table 228: “PLC Runtime” > “General Configuration” Submenu .......................416
Table 229: “PLC Runtime” > “General Configuration” > “PLC Runtime Version”
Submenu ................................................................................................417
Table 230: “PLC Runtime” > “General Configuration” > “Home Dir On SD Card”
Submenu ................................................................................................417
Table 231: “PLC Runtime” > “WebVisu” Submenu ...........................................418
Table 232: “Networking” Menu .........................................................................419
Table 233: “Networking” > “Host/Domain Name” Submenu ..............................419
Table 234: “Networking” > “Hostname” Submenu ............................................420
Table 235: “Networking” > “Host/Domain Name” > “Domain Name” Submenu .420
Table 236: “Networking” > “TCP/IP” Submenu .................................................420
Table 237: “Networking” > “IP Address” Submenu ...........................................421
Table 238: “Networking” > “TCP/IP” > “IP Address” Submenu > “Xn” ...............421
Table 239: “Networking” > “TCP/IP” > “Default Gateway” Submenu .................422
Table 240: “Networking” > “TCP/IP” > “Default Gateway” > “Default Gateway n”
Submenu ................................................................................................422
Table 241: “Networking” > “TCP/IP” > “DNS Server” Submenu ........................423
Table 242: “Networking” > “Ethernet” Submenu ...............................................423
Table 243: “Networking” > “Ethernet” > “Switch Configuration” Submenu.........424
Table 244: “Networking” > “Ethernet” > “Ethernet Ports” Submenu ..................424
Table 245: “Networking” > “Ethernet” > “Ethernet Ports” > “Interface Xn”
Submenu ................................................................................................425
Table 246: “Firewall” Menu ...............................................................................426
Table 247: “Firewall” > “General Configuration” Submenu................................427
Table 248: “Firewall” > “General Configuration” > “Interface xxx” Submenu .....428
Table 249: “Firewall” > “MAC Address Filter” Submenu ...................................430
Table 250: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist”
Submenu ................................................................................................431
Table 251: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” >
“Add new / No (n)” Submenu ...................................................................431
Table 252: “Firewall” > “User Filter” Submenu ..................................................432
Table 253: “Firewall” > “User Filter” > “Add New / No (n)” Submenu ................433
Table 254: “Clock” Menu ..................................................................................434
Table 255: “Administration” Menu.....................................................................435
Table 256: “Administration” > “Users” Submenu ...............................................436
Table 257: “Administration” > “Create Image” Submenu...................................436
Table 258: “Package Server” Menu ..................................................................437
Table 259: “Package Server” > “Firmware Backup” Menu ................................437
Table 260: “Package Server” > “Firmware Backup” > “Auto Update Feature”
Menu .......................................................................................................438
Table 261: “Package Server” > “Firmware Backup” > “Auto Update Feature”
Menu .......................................................................................................438
Table 262: “Package Server” > “Firmware Restore” Menu ...............................439
Table 263: “Package Server” > “Firmware Restore” > “Select Package” Menu.439
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 264: “Package Server” > “System Partition” Submenu ...........................440
Table 265: “Mass Storage” Menu .....................................................................441
Table 266: “Mass Storage” > “SD Card” Menu .................................................441
Table 267: “Ports and Services” Menu .............................................................443
Table 268: “Ports and Services” > “Telnet” Submenu .......................................444
Table 269: “Ports and Services” > “FTP” Submenu ..........................................444
Table 270: “Ports and Services” > “FTPS” Submenu ........................................445
Table 271: “Ports and Services” > “HTTP” Submenu .......................................445
Table 272: “Ports and Services” > “HTTPS” Submenu .....................................446
Table 273: “Ports and Services” > “NTP” Submenu..........................................446
Table 274: “Ports and Services” > “SSH” Submenu .........................................447
Table 275: “Ports and Services” > “TFTP” Submenu ........................................447
Table 276: “Ports and Services” > “DHCPD” Submenu ....................................448
Table 277: “Ports and Services” > “DHCPD” > “Xn” Submenu .........................448
Table 278: “Ports and Services” > “DNS” Submenu .........................................449
Table 279: “Ports and Services” > “IOCHECK PORT” Submenu ......................450
Table 280: “Ports and Services” > “Modbus TCP” Submenu ............................450
Table 281: “Ports and Services” > “Modbus UDP” Submenu ............................451
Table 282: “Ports and Services” > “OPC UA” Submenu ...................................451
Table 283: “Ports and Services” > “Firewall Status” Submenu..........................452
Table 284: “Ports and Services” > “PLC Runtime Services” Submenu .............453
Table 285: “Ports and Services” > “PLC Runtime Services” > “CODESYS 2”
Submenu ................................................................................................454
Table 286: “Ports and Services” > “PLC Runtime Services” > “e!RUNTIME”
Submenu ................................................................................................455
Table 287: “SNMP” Menu .................................................................................456
Table 288: “SNMP” > “General SNMP Configuration” Submenu ......................456
Table 289: “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu ..........457
Table 290: “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu..457
Table 291: “SNMP” > “SNMP v3 Configuration” Submenu ...............................458
Table 292: “SNMP” > “(Secure )SNMP firewalling” Submenu ...........................459
Table 293: 1 Channel Digital Input Module with Diagnostics ............................461
Table 294: 2 Channel Digital Input Modules .....................................................461
Table 295: 2 Channel Digital Input Module with Diagnostics ............................461
Table 296: 2 Channel Digital Input Module with Diagnostics and Output Process
Data ........................................................................................................462
Table 299: 8 Channel Digital Input Module NAMUR with Diagnostics and Output
Process Data ..........................................................................................463
Table 300: 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data ..........................................................................................464
Table 301: 16 Channel Digital Input Modules ...................................................465
Table 302: 1 Channel Digital Output Module with Input Process Data ..............466
Table 303: 2 Channel Digital Output Modules ..................................................466
Table 304: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data ........................................................................................................467
Table 305: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data 75x-506 ..........................................................................................467
Table 306: 4 Channel Digital Output Modules ..................................................468
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 307: 4 Channel Digital Output Modules with Diagnostics and Input Process
Data ........................................................................................................468
Table 308: 8 Channel Digital Output Module ....................................................468
Table 309: 8 Channel Digital Output Modules with Diagnostics and Input Process
Data ........................................................................................................469
Table 310: 16 Channel Digital Output Modules ................................................469
Table 311: 8 Channel Digital Input/Output Modules .........................................470
Table 312: 1 Channel Analog Input Modules ....................................................471
Table 314: 2-Channel Analog Input Modules HART .........................................473
Table 315:: 2 Channel Analog Input Modules HART + 6 bytes Mailbox ............473
Table 318: 3-Phase Power Measurement Module ............................................475
Table 319: 3-Phase Power Measurement Modules 750-494, -495, (and all
variations) ...............................................................................................476
Table 320: 2 Channel Analog Output Modules .................................................477
Table 321: 4 Channel Analog Output Modules .................................................477
Table 322: Counter Modules 750-404, (and all variations except of /000-005),
753-404, -404/000-003............................................................................478
Table 323: Counter Modules 750-404/000-005, 753-404/000-005 ...................479
Table 324: Counter Modules 750-633 ..............................................................480
Table 325: Counter Modules 750-638, 753-638 ...............................................480
Table 326: Pulse Width Modules 750-511, /xxx-xxx, 753-511 ..........................481
Table 327: Serial Interface Modules with Alternative Data Format....................482
Table 328: Serial Interface Modules with Standard Data Format ......................482
Table 329: Serial Interface Modules 750-652, 753-652 ....................................483
Table 330: Data Exchange Module 750-654, -654/000-001 .............................483
Table 331: SSI Transmitter Interface Modules .................................................484
Table 332: SSI Transmitter Interface I/O Modules with an Alternative Data Format
(/000-004, -005, -007) .............................................................................484
Table 333: Incremental Encoder Interface Modules 750-631/000-004, --010, -
011 ..........................................................................................................484
Table 334: Incremental Encoder Interface Modules 750-634............................485
Table 335: Incremental Encoder Interface Modules 750-637, (and all variations)
................................................................................................................485
Table 336: Digital Pulse Interface Modules 750-635, 753-635..........................486
Table 337: DC-Drive Controller 750-636, -636/000-700, -636/000-800 ............486
Table 338: Stepper Controller 750-670, -671, -672 ..........................................487
Table 339: RTC Module 750-640 .....................................................................488
Table 340: DALI/DSI Master Module 750-641 ..................................................488
Table 341: DALI Multi-Master Module 753-647 in the "Easy" Mode ..................489
Table 342: DALI Multi-Master Module 753-647 in the "Full" Mode ....................491
Table 343: LON® FTT Module 753-648 ............................................................492
Table 344: EnOcean Radio Receiver 750-642 .................................................492
Table 345: MP Bus Master Module 750-643 ....................................................493
Table 346: Bluetooth® RF-Transceiver 750-644 ...............................................494
Table 347: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645 ...494
Table 348: KNX/EIB/TP1 Module 753-646 .......................................................495
Table 349: AS-interface Master Module 750-655, 753-655 ..............................496
Manual
750-8214 PFC200; G2; 2ETH RS CAN
Table 350: System Modules with Diagnostics 750-606, -611............................497
Table 351: System Modules with Diagnostics 750-610, -611............................497
Table 352: Filter Modules 750-624/020-002, 750-626/020-002 ........................497
Table 353: Binary Space Module 750-622 (with Behavior like 2 Channel Digital
Input).......................................................................................................498
Table 354: CODESYS System Libraries ..........................................................499
Table 355: Possible Macros for File Access .....................................................501
Table 356: Possible Macros for File Access .....................................................502
Table 357: Input Variable “DEVICENUMBER”..................................................503
Table 358: Description of the Configuration Scripts for “Information” ................505
Table 359: Description of the Configuration Scripts for “CODESYS” ................506
Table 360: Description of the Configuration Scripts for “Networking - Host/Domain
Name” .....................................................................................................507
Table 361: Description of the Configuration Scripts for “Networking - TCP/IP” .507
Table 362: Description of the Configuration Scripts for “Networking - ETHERNET”
................................................................................................................509
Table 363: Description of the Configuration Scripts for “NTP” ..........................510
Table 364: Description of the Configuration Scripts for “Clock” .........................511
Table 365: Description of the Configuration Scripts for "Administration" ...........511
Table 366: Description of Configuration Scripts for “Package Server” ..............512
Table 367: Description of Configuration Scripts for “Ports and Services” –
“Network Services ...................................................................................513
Table 368: Description of Configuration Scripts for “Ports and Services” – “PLC
Runtime Services” ...................................................................................514
Table 369: Description of Configuration Scripts for “Ports and Services” –
“SSH/TFTP” ............................................................................................517
Table 370: Description of Configuration Scripts for “SNMP” .............................518
Manual
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
Internet: www.wago.com

m07508214-00000000-0en

Uploaded by

Copyright:

Available Formats

m07508214-00000000-0en

Uploaded by

Document Information

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

m07508214-00000000-0en

Uploaded by

Copyright:

Available Formats

Manual

WAGO I/O System 750

Version 1.9.0, valid from FW Version 03.10.08(22)

© 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

This documentation is only applicable from FW Version 03.10.08(22).

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.3.1 Improper Use

• Non-observance of the intended use.

• Use without protective measures in an environment in which moisture, salt

2.1.3.2 Warranty and Liability

• The product is improperly used.

• The deficiency (hardware and software configurations) is due to special

Individual agreements always have priority.

2.1.3.3 Obligations of Installers/Operators

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!

Ensure a standard connection!

Power from SELV/PELV power supply only!