m07508207 XXXXXXXX 0 en

Manual
WAGO-I/O-SYSTEM 750
750-8207(/xxx-xxx)
PFC200 CS 2ETH RS 3G
PLC - Controller PFC200
Version 1.3.0, valid from FW Version 02.08.25(11)

2 WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
© 2018 WAGO Kontakttechnik GmbH & Co. KG

All rights reserved.
WAGO Kontakttechnik 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: http://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-8207 PFC200 CS 2ETH RS 3G
Table of Contents
1 Notes about this Documentation ........................................................... 15
1.1 Validity of this Documentation............................................................... 15
1.2 Copyright ..............................................................................................15
1.3 Symbols ...............................................................................................16
1.4 Number Notation ..................................................................................18
1.5 Font Conventions .................................................................................18
2 Important Notes ......................................................................................19
2.1 Legal Bases..........................................................................................19
2.1.1 Subject to Changes .......................................................................... 19
2.1.2 Personnel Qualifications .................................................................. 19
2.1.3 Use of the WAGO-I/O-SYSTEM 750 in Compliance with Underlying
Provisions ........................................................................................19
2.1.4 Technical Condition of Specified Devices......................................... 20
2.2 Safety Advice (Precautions) ................................................................. 21
2.3 Disclaimer.............................................................................................22
2.4 Licensing Terms of the Software Package Used................................... 23
2.5 Special Use Conditions for ETHERNET Devices .................................. 23
3 Device Description ..................................................................................24
3.1 View .....................................................................................................27
3.2 Labeling ................................................................................................29
3.2.1 Manufacturing Number..................................................................... 29
3.3 Connectors ...........................................................................................30
3.3.1 Data Contacts/Local Bus.................................................................. 30
3.3.2 Power Jumper Contacts/Field Supply .............................................. 31
3.3.3 CAGE CLAMP® Connectors ............................................................. 32
3.3.4 Service Interface ..............................................................................33
3.3.5 Network Connectors......................................................................... 34
3.3.6 Communication Interface ................................................................. 35
3.3.6.1 Operating as an RS-232 Interface ............................................... 36
3.3.6.2 Operating as an RS-485 Interface ............................................... 37
3.3.7 Antenna Connector .......................................................................... 38
3.4 Display Elements ..................................................................................39
3.4.1 Power Supply Indicating Elements ................................................... 39
3.4.2 Fieldbus/System Indicating Elements............................................... 40
3.4.3 Memory Card Indicating Elements ................................................... 41
3.4.4 Network Indicating Elements ............................................................ 42
3.4.5 Mobile Communications Network Status Indicating Elements .......... 43
3.5 Operating Elements .............................................................................. 44
3.5.1 Operating Mode Switch .................................................................... 44
3.5.1.1 CODESYS 2 Runtime System ..................................................... 44
3.5.1.2 e!RUNTIME Runtime System ...................................................... 44
3.5.2 Reset Button ....................................................................................45
3.6 Slot for Memory Card ........................................................................... 46
3.7 SIM Card Slot .......................................................................................47
3.8 Schematic Diagram ..............................................................................48
3.9 Technical Data .....................................................................................49
Manual
4 Table of Contents WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
3.9.1 Mechanical Data ..............................................................................49
3.9.2 System Data ....................................................................................49
3.9.3 Power Supply ...................................................................................49
3.9.4 Clock ................................................................................................50
3.9.5 Programming ...................................................................................50
3.9.6 Local Bus .........................................................................................50
3.9.7 ETHERNET .....................................................................................51
3.9.8 Communication Interface ................................................................. 51
3.9.9 Mobile Radio Modem ....................................................................... 51
3.9.10 Connection Type .............................................................................. 52
3.9.11 Climatic Environmental Conditions ................................................... 52
3.10 Approvals .............................................................................................53
3.11 Standards and Guidelines .................................................................... 54
4 Function Description ..............................................................................55
4.1 Network ................................................................................................55
4.1.1 Interface Configuration ..................................................................... 55
4.1.1.1 Operation in Switch Mode............................................................ 55
4.1.1.2 Operation with Separate Network Interfaces................................ 55
4.1.2 Network Security ..............................................................................56
4.1.2.1 Users and Passwords.................................................................. 56
4.1.2.1.1 Services and Users ................................................................. 56
4.1.2.1.2 WBM User Group.................................................................... 57
4.1.2.1.3 Linux® User Group .................................................................. 57
4.1.2.1.4 SNMP User Group .................................................................. 57
4.1.2.2 Web Protocols for WBM Access .................................................. 58
4.1.2.2.1 TLS Encryption ....................................................................... 58
4.1.3 Network Configuration...................................................................... 60
4.1.3.1 Host Name/Domain Name ........................................................... 60
4.1.4 Routing ............................................................................................60
4.1.5 Network Services .............................................................................64
4.1.5.1 DHCP Client ................................................................................64
4.1.5.2 DHCP Server...............................................................................64
4.1.5.3 DNS Server .................................................................................66
4.1.6 Cloud Connectivity Functionality ...................................................... 67
4.1.6.1 Components of the Cloud Connectivity Software Package .......... 67
4.2 Memory Card Function ......................................................................... 69
4.2.1 Formatting........................................................................................69
4.2.2 Data Backup ....................................................................................71
4.2.2.1 Backup Function.......................................................................... 71
4.2.2.2 Restore Function ......................................................................... 72
4.2.3 Inserting a Memory Card during Operation ...................................... 74
4.2.4 Removing the Memory Card during Operation ................................. 74
4.2.5 Setting the Home Directory for the Runtime System ........................ 75
4.2.6 Load Boot Project ............................................................................ 75
5 Mounting..................................................................................................77
5.1 Installation Position...............................................................................77
5.2 Overall Configuration ............................................................................ 77
5.3 Mounting onto Carrier Rail .................................................................... 79
5.3.1 Carrier Rail Properties...................................................................... 79
Manual
750-8207 PFC200 CS 2ETH RS 3G
5.3.2 WAGO DIN Rails .............................................................................80
5.4 Spacing ................................................................................................80
5.5 Mounting Sequence..............................................................................81
5.6 Inserting Devices ..................................................................................82
5.6.1 Inserting the Controller ..................................................................... 82
6 Connect Devices .....................................................................................83
6.1 Connecting a Conductor to the CAGE CLAMP® ................................... 83
6.2 Power Supply Concept ......................................................................... 84
6.2.1 Overcurrent Protection ..................................................................... 84
6.2.2 Supplementary Power Supply Regulations ...................................... 85
7 Commissioning .......................................................................................86
7.1 Switching On the Controller .................................................................. 86
7.2 Determining the IP Address of the Host PC .......................................... 87
7.3 Setting an IP Address ........................................................................... 88
7.3.1 Assigning an IP Address using DHCP .............................................. 89
7.3.2 Changing an IP Address Using the “CBM” Configuration Tool via the
Serial Interface .................................................................................90
7.3.3 Changing an IP Address using “WAGO Ethernet Settings” .............. 93
7.3.4 Temporarily Setting a Fixed IP Address ........................................... 95
7.4 Testing the Network Connection ........................................................... 96
7.5 Changing Standard Passwords ............................................................ 97
7.6 Shutdown/Restart .................................................................................98
7.7 Initiating Reset Functions ..................................................................... 99
7.7.1 Warm Start Reset ............................................................................ 99
7.7.2 Cold Start Reset...............................................................................99
7.7.3 Software Reset .............................................................................. 100
7.8 Configuration ...................................................................................... 101
7.8.1 Configuration via Web-Based-Management (WBM) ....................... 102
7.8.1.1 WBM User Administration.......................................................... 103
7.8.1.2 General Information about the Page .......................................... 106
7.8.1.3 “Status Information” Page .......................................................... 109
7.8.1.3.1 “Controller Details” Group ..................................................... 109
7.8.1.3.2 “Network Details Xn” Group(s) .............................................. 109
7.8.1.4 “General PLC Runtime Configuration” Page .............................. 110
7.8.1.4.1 “General PLC Runtime Configuration” Group ........................ 110
7.8.1.5 “PLC Runtime Information” Page ............................................... 112
7.8.1.5.1 “PLC Runtime” Group ........................................................... 112
7.8.1.5.2 “Project Details” Group.......................................................... 112
7.8.1.5.3 “Task n” Group(s).................................................................. 113
7.8.1.6 “PLC WebVisu” Page ................................................................ 114
7.8.1.6.1 “Web Server Configuration” Group ........................................ 114
7.8.1.7 “Configuration of Host and Domain Name” Page ....................... 115
7.8.1.7.1 “HostName” Group................................................................ 115
7.8.1.7.2 “Domain Name” Group .......................................................... 115
7.8.1.8 “TCP/IP Configuration” Page ..................................................... 116
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.8.1 “IP Configuration (Xn)” Group(s) ........................................... 116
7.8.1.8.2 “Default Gateway n” Groups ................................................. 117
7.8.1.8.3 “DNS Server” Group ............................................................. 118
7.8.1.9 “Ethernet Configuration” Page ................................................... 119
7.8.1.9.1 “Switch Configuration” Group ................................................ 119
7.8.1.9.2 “Interface Xn” Groups ........................................................... 119
7.8.1.10 “Routing” Page .......................................................................... 121
7.8.1.10.1 “General Routing Configuration” Group................................. 121
7.8.1.10.2 “Static Routes” Group ........................................................... 122
7.8.1.10.3 “Dynamic Routes” Group ...................................................... 123
7.8.1.10.4 “IP Masquerading” Group...................................................... 123
7.8.1.10.5 “Port Forwarding” Group ....................................................... 124
7.8.1.11 “General Firewall Configuration” Page ....................................... 125
7.8.1.11.1 “Global Firewall Parameters” Group ...................................... 125
7.8.1.11.2 “Firewall Parameters Interface xxx” Group ............................ 126
7.8.1.12 “Configuration of MAC Address Filter” Page .............................. 127
7.8.1.12.1 “Global MAC Address Filter State” Group ............................. 127
7.8.1.12.2 “MAC Address Filter State Xn” Group ................................... 128
7.8.1.12.3 “MAC Address Filter Whitelist” Group ................................... 128
7.8.1.13 “Configuration of User Filter” Page ............................................ 129
7.8.1.13.1 “User Filter” Group ................................................................ 129
7.8.1.13.2 “User Filter n” Group ............................................................. 129
7.8.1.13.3 “Add New User Filter” Group ................................................. 130
7.8.1.14 “Configuration of Time and Date” Page ..................................... 131
7.8.1.14.1 “Date on Device” Group ........................................................ 131
7.8.1.14.2 “Time on Device” Group ........................................................ 131
7.8.1.14.3 “Time Zone” Group ............................................................... 132
7.8.1.14.4 “TZ String” Group .................................................................. 133
7.8.1.15 “Configuration of the Users for the Web-based Management” Page134
7.8.1.15.1 “Change Password for Selected User” Group ....................... 134
7.8.1.16 “Create Bootable Image” Page .................................................. 135
7.8.1.16.1 "Create Bootable Image from Active Partition (<Active
Partition>" Group .................................................................. 135
7.8.1.17 “Configuration of Serial Interface RS232” Page ......................... 137
7.8.1.17.1 “Serial Interface Assigned to” Group ..................................... 137
7.8.1.17.2 “Assign Owner of Serial Interface (Active after Next Controller
Reboot)” Group ..................................................................... 137
7.8.1.18 “Configuration of Service Interface” Page .................................. 138
7.8.1.18.1 “Service Interface assigned to” Group ................................... 138
7.8.1.18.2 “Assign Owner of Service Interface (enabled after next
controller reboot)” Group ....................................................... 138
7.8.1.19 “Reboot Controller” Page ........................................................... 139
7.8.1.19.1 “Reboot Controller” Group..................................................... 139
7.8.1.20 “Firmware Backup” Page ........................................................... 140
7.8.1.21 “Firmware Restore” Page .......................................................... 142
7.8.1.22 “System Partition” Page............................................................. 144
7.8.1.22.1 “Current Active Partition” Group ............................................ 144
7.8.1.22.2 “Set Inactive Partition Active” Group ..................................... 144
7.8.1.23 “Mass Storage” Page................................................................. 145
7.8.1.23.1 “<Device Name>” Group(s) ................................................... 145
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.23.2 “<Device Name> - FAT Format” Group(s) ............................. 145
7.8.1.24 “Software Uploads” Page........................................................... 146
7.8.1.24.1 “Upload New Software” Group .............................................. 146
7.8.1.24.2 “Activate New Software” Group ............................................. 146
7.8.1.25 “Configuration of Network Services” Page ................................. 147
7.8.1.25.1 “Telnet” Group ...................................................................... 147
7.8.1.25.2 “FTP” Group.......................................................................... 147
7.8.1.25.3 “FTPS” Group ....................................................................... 147
7.8.1.25.4 “HTTP” Group ....................................................................... 148
7.8.1.25.5 “HTTPS” Group ..................................................................... 148
7.8.1.25.6 “WAGO-I/O-CHECK” Group .................................................. 148
7.8.1.25.7 “OPC UA” Group ................................................................... 149
7.8.1.26 “Configuration of NTP Client” Page ........................................... 150
7.8.1.26.1 “NTP Client Configuration” Group ......................................... 150
7.8.1.26.2 “NTP Single Request” Group ................................................ 150
7.8.1.27 “Configuration of PLC Runtime Services” Page ......................... 151
7.8.1.27.1 “General Configuration” Group .............................................. 151
7.8.1.27.2 “CODESYS 2” Group ............................................................ 151
7.8.1.27.3 “e!RUNTIME” Group ............................................................. 151
7.8.1.28 “SSH Server Settings” Page ...................................................... 153
7.8.1.28.1 “SSH Server” Group.............................................................. 153
7.8.1.29 “TFTP Server” Page .................................................................. 154
7.8.1.29.1 “TFTP Server” Group ............................................................ 154
7.8.1.30 “DHCP Configuration” Page ...................................................... 155
7.8.1.30.1 “DHCP Configuration Xn” Group ........................................... 155
7.8.1.31 “Configuration of DNS Service” Page ........................................ 156
7.8.1.31.1 “DNS Service” Group ............................................................ 156
7.8.1.32 “MODBUS Services Configuration” Page .................................. 157
7.8.1.32.1 “MODBUS TCP” Group ......................................................... 157
7.8.1.32.2 “MODBUS UDP” Group ........................................................ 157
7.8.1.33 “Configuration of Cloud Connectivity” Page ............................... 158
7.8.1.33.1 “Software Version” Group ..................................................... 158
7.8.1.33.2 “Status” Group ...................................................................... 158
7.8.1.33.3 “Settings” Group ................................................................... 159
7.8.1.34 “Configuration of General SNMP Parameters” Page.................. 162
7.8.1.34.1 “General SNMP Configuration” Group................................... 162
7.8.1.35 “Configuration of SNMP v1/v2c Parameters” Page .................... 163
7.8.1.35.1 “SNMP v1/v2c Manager Configuration” Group ...................... 163
7.8.1.35.2 “Actually Configured Trap Receivers” Group(s) ..................... 163
7.8.1.35.3 “Trap Receiver n” Group(s) ................................................... 164
7.8.1.35.4 “Add New Trap Receiver” Group ........................................... 164
7.8.1.36 “Configuration of SNMP v3 Users” Page ................................... 165
7.8.1.36.1 “Actually Configured v3 Users” Group(s) ............................... 165
7.8.1.36.2 “v3 User n” Group(s) ............................................................. 165
7.8.1.36.3 “Add New v3 User” Group ..................................................... 166
7.8.1.37 “Diagnostic Information” Page ................................................... 167
7.8.1.38 “Configuration of internal 3G Modem” Page .............................. 168
7.8.1.38.1 “SIM Authentication” Group ................................................... 168
7.8.1.38.2 “Mobile Network Configuration” Group .................................. 169
7.8.1.38.3 “Provider List” Group............................................................. 170
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.38.4 “Network Package Service” Group ........................................ 170
7.8.1.38.5 “Upload and activate new Modem Software” Group .............. 171
7.8.1.39 “Configuration of OpenVPN and IPsec” Page ............................ 172
7.8.1.39.1 “OpenVPN” Group ................................................................ 172
7.8.1.39.2 “IPsec” Group ....................................................................... 172
7.8.1.39.3 “Certificate Upload” Group .................................................... 173
7.8.1.39.4 “Certificate List” Group .......................................................... 173
7.8.1.39.5 “Private Key List” Group ........................................................ 173
7.8.1.40 “Security Settings” Page ............................................................ 174
7.8.1.40.1 “TLS Configuration” Group .................................................... 174
7.8.1.41 “Open Source Licenses” Page ................................................... 175
7.8.1.42 “WAGO Licenses” Page ............................................................ 176
7.8.2 Configuration using a Terminal Program (CBM) ............................. 177
7.8.2.1 CBM Menu Structure Overview ................................................. 177
7.8.2.2 “Information” Menu .................................................................... 180
7.8.2.2.1 “Information” > “Controller Details” Submenu ........................ 180
7.8.2.2.2 “Information” > “Network Details” Submenu .......................... 181
7.8.2.3 “PLC Runtime” Menu ................................................................. 182
7.8.2.3.1 “PLC Runtime” > “Information” Submenu .............................. 182
7.8.2.3.2 “Information” > “Runtime Version” Submenu ......................... 183
7.8.2.3.3 “Information” > “Webserver Version” Submenu ..................... 183
7.8.2.3.4 “Information” > “State” Submenu ........................................... 183
7.8.2.3.5 “Information” > “Number of Tasks” Submenu ........................ 184
7.8.2.3.6 “Information” > “Project Details” Submenu ............................ 184
7.8.2.3.7 “Information” > “Tasks” Submenu.......................................... 184
7.8.2.3.8 “Tasks” > “Task n” Submenu................................................. 185
7.8.2.3.9 “PLC Runtime” > “General Configuration” Submenu ............. 185
7.8.2.3.10 “General Configuration” > “PLC Runtime Version” Submenu 186
7.8.2.3.11 “General Configuration” > “Home Dir On SD Card” Submenu186
7.8.2.3.12 “PLC Runtime” > “WebVisu” Submenu.................................. 187
7.8.2.4 “Networking” Menu .................................................................... 188
7.8.2.4.1 “Networking” > “Host/Domain Name” Submenu .................... 188
7.8.2.4.2 “Host/Domain Name” > “Hostname” Submenu ...................... 189
7.8.2.4.3 “Host/Domain Name” > “Domain Name” Submenu ............... 189
7.8.2.4.4 “Networking” > “TCP/IP” Submenu........................................ 189
7.8.2.4.5 “TCP/IP” > “IP Address” Submenu ........................................ 190
7.8.2.4.6 “IP Address” > “Xn“ Submenu ............................................... 190
7.8.2.4.7 “TCP/IP” > “Default Gateway” Submenu ............................... 191
7.8.2.4.8 “Default Gateway” > “Default Gateway n” Submenu.............. 191
7.8.2.4.9 “TCP/IP” > “DNS Server” Submenu ...................................... 192
7.8.2.4.10 “Networking” > “Ethernet” Submenu...................................... 192
7.8.2.4.11 “Ethernet” > “Switch Configuration” Submenu ....................... 193
7.8.2.4.12 “Ethernet” > “Ethernet Ports” Submenu ................................. 193
7.8.2.4.13 “Ethernet Ports” > “Interface Xn” Submenu ........................... 194
7.8.2.5 “Firewall” Menu .......................................................................... 195
7.8.2.5.1 “Firewall” > “General Configuration” Submenu ...................... 196
7.8.2.5.2 “General Configuration” > “Interface xxx” Submenu .............. 197
7.8.2.5.3 “Firewall” > “MAC Address Filter” Submenu .......................... 199
7.8.2.5.4 “MAC Address Filter” > “MAC address filter whitelist” Submenu200
7.8.2.5.5 “MAC address filter whitelist” > “Add new / No (n)” Submenu 200
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.6 “Firewall” > “User Filter” Submenu ........................................ 201
7.8.2.5.7 “User Filter” > “Add New / No (n)” Submenu ......................... 202
7.8.2.6 “Clock” Menu ............................................................................. 203
7.8.2.7 “Administration” Menu ............................................................... 204
7.8.2.7.1 “Administration” > “Create Image” Submenu ......................... 205
7.8.2.7.2 “Administration” > “Users” Submenu ..................................... 205
7.8.2.8 “Package Server” Menu ............................................................. 206
7.8.2.8.1 “Package Server” > “Firmware Backup” Submenu ................ 206
7.8.2.8.2 “Firmware Backup” > “Auto Update Feature” Submenu ........ 207
7.8.2.8.3 “Firmware Backup” > “Destination” Submenu........................ 207
7.8.2.8.4 “Package Server” > “Firmware Restore” Submenu ............... 208
7.8.2.8.5 “Firmware Restore” > “Select Package” Submenu ................ 208
7.8.2.8.6 “Package Server” > “System Partition” Submenu .................. 209
7.8.2.9 “Mass Storage” Menu ................................................................ 210
7.8.2.9.1 “Mass Storage” > “SD Card” Submenu ................................. 210
7.8.2.10 “Software Uploads” Menu .......................................................... 211
7.8.2.11 “Ports and Services” Menu ........................................................ 212
7.8.2.11.1 “Ports and Services” > “Telnet” Submenu ............................. 213
7.8.2.11.2 “Ports and Services” > “FTP” Submenu ................................ 213
7.8.2.11.3 “Ports and Services” > “FTPS” Submenu .............................. 214
7.8.2.11.4 “Ports and Services” > “HTTP” Submenu .............................. 214
7.8.2.11.5 “Ports and Services” > “HTTPS” Submenu ........................... 215
7.8.2.11.6 “Ports and Services” > “NTP” Submenu ................................ 215
7.8.2.11.7 “Ports and Services” > “SSH” Submenu ................................ 216
7.8.2.11.8 “Ports and Services” > “TFTP” Submenu .............................. 216
7.8.2.11.9 “Ports and Services” > “DHCPD” Submenu .......................... 217
7.8.2.11.10 “DHCPD” > “Xn” Submenu .................................................... 217
7.8.2.11.11 “Ports and Services” > “DNS” Submenu................................ 218
7.8.2.11.12 “Ports and Services” > “IOCHECK PORT” Submenu ............ 219
7.8.2.11.13 “Ports and Services” > “Modbus TCP” Submenu .................. 219
7.8.2.11.14 “Ports and Services” > “Modbus UDP” Submenu .................. 220
7.8.2.11.15 “Ports and Services” > “PLC Runtime Services” Submenu.... 220
7.8.2.11.16 “PLC Runtime Services” > “CODESYS 2” Submenu ............. 221
7.8.2.11.17 “PLC Runtime Services” > “e!RUNTIME” Submenu .............. 222
7.8.2.11.18 “…” > “Firewall Status” Submenu .......................................... 223
7.8.2.12 “SNMP” Menu............................................................................ 224
7.8.2.12.1 “SNMP” > “General SNMP Configuration” Submenu ............. 224
7.8.2.12.2 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu 225
7.8.2.12.3 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration”
Submenu .............................................................................. 225
7.8.2.12.4 “SNMP” > “SNMP v3 Configuration” Submenu...................... 226
7.8.2.12.5 “SNMP” > “(Secure)SNMP firewalling” Submenu .................. 227
7.8.3 Configuration using “WAGO Ethernet Settings”.............................. 228
7.8.3.1 Identification Tab ....................................................................... 230
7.8.3.2 Network Tab .............................................................................. 231
7.8.3.3 PLC Tab .................................................................................... 233
7.8.3.4 Status Tab ................................................................................. 234
8 Run-time System CODESYS 2.3........................................................... 235
8.1 Installing the CODESYS 2.3 Programming System ............................ 235
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.2 First Program with CODESYS 2.3 ...................................................... 235
8.2.1 Start the CODESYS Programming System .................................... 235
8.2.2 Creating a Project and Selecting the Target System ...................... 235
8.2.3 Creating the PLC Configuration ..................................................... 237
8.2.4 Editing the Program Function Block ............................................... 244
8.2.5 Loading and Running the PLC Program in the Fieldbus Controller
(ETHERNET) ................................................................................. 246
8.2.6 Creating a Boot Project .................................................................. 248
8.3 Syntax of Logical Addresses .............................................................. 248
8.4 Creating Tasks ................................................................................... 249
8.4.1 Cyclic Tasks ................................................................................... 252
8.4.2 Freewheeling Tasks ....................................................................... 253
8.4.3 Debugging an IEC Program ........................................................... 253
8.5 System Events ................................................................................... 257
8.5.1 Creating an Event Handler ............................................................. 260
8.6 Process Images .................................................................................. 262
8.6.1 Process Images for I/O Modules Connected to the Controller ........ 264
8.6.2 Process Image for Slaves Connected to the Fieldbus .................... 265
8.7 Access to Process Images of the Input and Output Data via CODESYS
2.3 ...................................................................................................... 265
8.8 Addressing Example ........................................................................... 267
8.9 Local Bus Synchronization ................................................................. 268
8.9.1 Case 1: CODESYS Task Interval Set Smaller than the Local Bus
Cycle .............................................................................................. 268
8.9.2 Case 2: CODESYS Task Interval Smaller than Twice the Local Bus
Cycle .............................................................................................. 270
8.9.3 Case 3: CODESYS Task Interval Greater than Twice the Local Bus
Cycle .............................................................................................. 271
8.9.4 Case 4: CODESYS Task Interval Greater than 10 ms.................... 272
8.9.5 Local Bus (KBus) Settings ............................................................. 273
8.9.5.1 Effect of Update Mode on CODESYS Tasks ............................. 274
8.9.5.1.1 Asynchronous Update Mode ................................................. 274
8.9.5.1.2 Synchronous Update Mode ................................................... 274
8.10 Memory Settings in CODESYS........................................................... 275
8.10.1 Program Memory ........................................................................... 275
8.10.2 Data Memory and Function Block Limitation .................................. 277
8.10.3 Remanent Memory ........................................................................ 278
8.11 General Target System Settings ......................................................... 279
8.12 CODESYS Visualization ..................................................................... 279
8.12.1 Limits of CODESYS Visualization .................................................. 282
8.12.2 Eliminating Errors in CODESYS Web Visualization ........................ 284
8.12.3 FAQs about CODESYS Web Visualization .................................... 285
9 e!RUNTIME Runtime Environment ....................................................... 287
9.1 General Notes .................................................................................... 287
9.2 CODESYS V3 Priorities ...................................................................... 288
9.3 Memory Spaces under e!RUNTIME.................................................... 289
9.3.1 Program and Data Memory ............................................................ 289
9.3.2 Function Block Limitation ............................................................... 289
9.3.3 Remanent Memory ........................................................................ 289
Manual
750-8207 PFC200 CS 2ETH RS 3G
10 MODBUS – CODESYS 2 ........................................................................ 290
10.1 General .............................................................................................. 290
10.2 Features ............................................................................................. 290
10.3 Configuration ...................................................................................... 291
10.3.1 MODBUS Settings ......................................................................... 292
10.3.2 MODBUS TCP Settings ................................................................. 293
10.3.3 MODBUS UDP Settings ................................................................. 293
10.3.4 MODBUS RTU Settings ................................................................. 293
10.4 Data Exchange ................................................................................... 296
10.4.1 Process Image ............................................................................... 297
10.4.2 Flag Area ....................................................................................... 298
10.4.3 MODBUS Registers ....................................................................... 299
10.4.4 MODBUS Mapping ........................................................................ 299
10.4.4.1 MODBUS Mapping for Write Bit Services FC1, FC2 .................. 299
10.4.4.2 MODBUS Mapping for Write Bit Services FC5, FC15 ................ 300
10.4.4.3 MODBUS Mapping for Read Register Services FC3, FC4, FC23301
10.4.4.4 MODBUS Mapping for Write Register Services FC6, FC16, FC22,
FC23 ......................................................................................... 303
10.5 WAGO MODBUS Registers................................................................ 305
10.5.1 Process Image Properties .............................................................. 306
10.5.1.1 Register 0x1022 – Number of Registers in the MODBUS Input
Process Image .......................................................................... 306
10.5.1.2 Register 0x1023 – Number of Registers in the MODBUS Output
Process Image .......................................................................... 306
10.5.1.3 Register 0x1024 – Number of Bits in the MODBUS Input Process
Image ........................................................................................ 306
10.5.1.4 Register 0x1025 – Number of Bits in the MODBUS Output Process
Image ........................................................................................ 306
10.5.2 Network Configuration.................................................................... 307
10.5.2.1 Register 0x1028 – IP Configuration ........................................... 307
10.5.2.2 Register 0x102A – Number of Established TCP Connections .... 307
10.5.2.3 Register 0x1030 – MODBUS TCP Socket Timeout ................... 307
10.5.2.4 Register 0x1031 – MAC Address for ETHERNET-Interface 1 (eth0)307
10.5.2.5 Register 0x1037 - MODBUS TCP Response Delay ................... 307
10.5.3 PLC Status Register ...................................................................... 308
10.5.4 MODBUS Watchdog ...................................................................... 308
10.5.4.1 Register 0x1100 – Watchdog Command ................................... 310
10.5.4.2 Register 0x1101 – Watchdog Status ......................................... 312
10.5.4.3 Register 0x1102 – Watchdog Timeout ....................................... 312
10.5.4.4 Register 0x1103 – Watchdog Config ......................................... 312
10.5.5 Register 0x1104 – Watchdog Operation Mode ............................... 313
10.5.6 MODBUS Constants Registers ...................................................... 314
10.5.6.1 Electronic Nameplate ................................................................ 314
10.5.6.2 Register 0x2010 – Revision (Firmware Index) ........................... 314
10.5.6.3 Register 0x2011 – Series Designator ........................................ 314
10.5.6.4 Register 0x2012 – Device ID ..................................................... 314
10.5.6.5 Register 0x2013 – Major Firmware Version ............................... 315
10.5.6.6 Register 0x2014 – Minor Firmware Version ............................... 315
10.5.6.7 Register 0x2015 – MBS Version ................................................ 315
10.6 Diagnostics ......................................................................................... 316
Manual
750-8207 PFC200 CS 2ETH RS 3G
10.6.1 Diagnostics for the MODBUS Master ............................................. 316
10.6.2 Diagnostics for the Runtime System .............................................. 316
10.6.3 Diagnostics for the Error Server ..................................................... 316
11 MODBUS – e!RUNTIME ......................................................................... 319
11.1 MODBUS Address Overview .............................................................. 319
11.2 MODBUS Registers............................................................................ 320
11.2.1 MODBUS Watchdog ...................................................................... 322
11.2.1.1 Register 0xFA00 – Watchdog Command................................... 324
11.2.1.2 Register 0xFA01 – Watchdog Timeout ...................................... 325
11.2.1.3 Register 0xFA02 – Watchdog Status ......................................... 325
11.2.1.4 Register 0xFA03 – Watchdog Config ......................................... 326
11.2.1.5 MODBUS TCP Connection Watchdog Register......................... 327
11.2.2 Status Registers............................................................................. 328
11.2.2.1 PLC Status Register .................................................................. 328
11.2.3 Electronic Nameplate ..................................................................... 328
11.2.3.1 Order Number ........................................................................... 328
11.2.3.2 Firmware Version ...................................................................... 328
11.2.3.3 Hardware Version ...................................................................... 328
11.2.3.4 Firmware Loader/Boot Loader ................................................... 328
11.2.4 MODBUS Process Image Version.................................................. 328
11.2.5 MODBUS Process Image Registers............................................... 328
11.2.6 Constant Registers ........................................................................ 329
11.2.7 Live Register .................................................................................. 329
11.3 Estimating the MODBUS Master CPU Load ....................................... 330
12 Diagnostics............................................................................................ 331
12.1 Operating and Status Messages......................................................... 331
12.1.1 Power Supply Indicating Elements ................................................. 331
12.1.2 Mobile Communications Network Status LED ................................ 332
12.1.3 Fieldbus/System Indicating Elements............................................. 333
12.2 Diagnostics Messages via Flashing Sequences ................................. 340
12.2.1 Flashing Sequences ...................................................................... 340
12.2.2 Example of a Diagnostics Message Indicated by a Flashing
Sequence....................................................................................... 342
12.2.3 Meaning of Blink Codes and Procedures for Troubleshooting ........ 343
12.2.4 Meaning of Blink Codes and Procedures for Troubleshooting ........ 348
13 Service ................................................................................................... 349
13.1 Inserting and Removing the Memory Card.......................................... 349
13.1.1 Inserting the Memory Card ............................................................. 349
13.1.2 Removing the Memory Card .......................................................... 349
13.2 Inserting and Removing the SIM Card ................................................ 351
13.2.1 Inserting the SIM Card ................................................................... 351
13.2.2 Removing the SIM Card ................................................................. 351
13.3 Firmware Changes ............................................................................. 352
13.3.1 Perform Firmware Upgrade ............................................................ 352
13.3.2 Perform Firmware Downgrade ....................................................... 353
13.3.3 Factory Reset ................................................................................ 354
14 Removal ................................................................................................. 355
Manual
750-8207 PFC200 CS 2ETH RS 3G
14.1 Removing Devices.............................................................................. 355
14.1.1 Removing the Controller ................................................................ 355
15 Appendix ............................................................................................... 356
15.1 Structure of Process Data for the I/O Modules .................................... 356
15.1.1 Digital Input Modules...................................................................... 357
15.1.1.1 1 Channel Digital Input Module with Diagnostics ....................... 357
15.1.1.2 2 Channel Digital Input Modules ................................................ 357
15.1.1.3 2 Channel Digital Input Module with Diagnostics ....................... 357
15.1.1.4 2 Channel Digital Input Module with Diagnostics and Output
Process Data ............................................................................. 358
15.1.1.7 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data ............................................................................. 359
15.1.1.8 16 Channel Digital Input Modules .............................................. 360
15.1.2 Digital Output Modules ................................................................... 361
15.1.2.1 1 Channel Digital Output Module with Input Process Data ......... 361
15.1.2.2 2 Channel Digital Output Modules ............................................. 361
15.1.2.3 2 Channel Digital Input Modules with Diagnostics and Input
Process Data ............................................................................. 362
15.1.2.4 4 Channel Digital Output Modules ............................................. 363
15.1.2.5 4 Channel Digital Output Modules with Diagnostics and Input
Process Data ............................................................................. 363
15.1.2.6 8 Channel Digital Output Module ............................................... 363
Process Data ............................................................................. 364
15.1.2.8 16 Channel Digital Output Modules ........................................... 364
15.1.2.9 8 Channel Digital Input/Output Modules .................................... 365
15.1.3 Analog Input Modules .................................................................... 366
15.1.3.1 1 Channel Analog Input Modules ............................................... 366
15.1.3.4 3-Phase Power Measurement Module ....................................... 368
15.1.4 Analog Output Modules.................................................................. 369
15.1.4.1 2 Channel Analog Output Modules ............................................ 369
15.1.4.2 4 Channel Analog Output Modules ............................................ 369
15.1.5 Specialty Modules .......................................................................... 370
15.1.5.1 Counter Modules ....................................................................... 370
15.1.5.2 Pulse Width Modules ................................................................. 372
15.1.5.3 Serial Interface Modules with Alternative Data Format .............. 372
15.1.5.4 Serial Interface Modules with Standard Data Format ................. 373
15.1.5.5 Data Exchange Module ............................................................. 373
15.1.5.6 SSI Transmitter Interface Modules ............................................ 373
15.1.5.7 Incremental Encoder Interface Modules .................................... 374
15.1.5.8 DC-Drive Controller ................................................................... 376
15.1.5.9 Stepper Controller ..................................................................... 377
15.1.5.10 RTC Module .............................................................................. 378
15.1.5.11 DALI/DSI Master Module ........................................................... 378
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.12 DALI Multi-Master Module ......................................................... 379
15.1.5.13 LON® FTT Module ..................................................................... 381
15.1.5.14 EnOcean Radio Receiver .......................................................... 381
15.1.5.15 MP Bus Master Module ............................................................. 381
15.1.5.16 Bluetooth® RF-Transceiver ........................................................ 382
15.1.5.17 Vibration Velocity/Bearing Condition Monitoring VIB I/O ............ 383
15.1.5.18 KNX/EIB/TP1 Module ................................................................ 383
15.1.5.19 AS-interface Master Module ...................................................... 384
15.1.6 System Modules ............................................................................ 386
15.1.6.1 System Modules with Diagnostics ............................................. 386
15.1.6.2 Binary Space Module ................................................................ 386
15.2 CODESYS 2 Libraries ........................................................................ 387
15.2.1 General Libraries ........................................................................... 387
15.2.1.1 CODESYS System Libraries ..................................................... 387
15.2.1.2 SysLibCom.lib ........................................................................... 388
15.2.1.3 SysLibFile.lib ............................................................................. 388
15.2.1.4 SysLibFileAsync.lib.................................................................... 389
15.2.1.5 SysLibRtc.lib.............................................................................. 390
15.2.1.6 BusDiag.lib ................................................................................ 391
15.2.1.7 mod_com.lib .............................................................................. 391
15.2.1.8 SerComm.lib.............................................................................. 391
15.2.1.9 WagoConfigToolLIB.lib .............................................................. 392
15.2.1.10 WagoLibCpuUsage.lib ............................................................... 408
15.2.1.11 WagoLibDiagnosticIDs.lib .......................................................... 408
15.2.1.12 WagoLibLed.lib.......................................................................... 409
15.2.1.13 WagoLibNetSnmp.lib ................................................................. 409
15.2.1.14 WagoLibNetSnmpManager.lib ................................................... 409
15.2.1.15 WagoLibSSL.lib ......................................................................... 410
15.2.1.16 WagoLibTerminalDiag.lib........................................................... 410
List of Figures ................................................................................................ 411
List of Tables .................................................................................................. 414
Manual
WAGO-I/O-SYSTEM 750 Notes about this Documentation 15
750-8207 PFC200 CS 2ETH RS 3G
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 CS 2ETH RS 3G”
controller (750-8207) and the variants listed in the table below.
Table 1: Variants
Item Number/Variant Designation
750-8207 PFC200 CS 2ETH RS 3G
750-8207/025-000 PFC200 CS 2ETH RS 3G/T
Documentation Validity for Variants

Unless otherwise indicated, the information given in this documentation applies
to listed variants.
This documentation is only applicable from FW Version 02.08.25(11).
1.2 Copyright
This Manual, including all figures and illustrations, is copyright-protected. Any
further use of this Manual by third parties that violate pertinent copyright
provisions is prohibited. Reproduction, translation, electronic and phototechnical
filing/archiving (e.g., photocopying) as well as any amendments require the
written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden, Germany.
Non-observance will involve the right to assert damage claims.
Manual
16 Notes about this Documentation WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
1.3 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
WAGO-I/O-SYSTEM 750 Notes about this Documentation 17
750-8207 PFC200 CS 2ETH RS 3G
Additional Information:
Refers to additional information which is not an integral part of this
documentation (e.g., the Internet).
Manual
18 Notes about this Documentation WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
1.4 Number Notation

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

Table 3: Font Conventions
Font Type Indicates
italic Names of paths and data files are marked in italic-type.
e.g.: C:\Program Files\WAGO Software
Menu Menu items are marked in bold letters.
e.g.: Save
> A greater-than sign between two names means the selection of a
menu item from a menu.
e.g.: File > New
Input Designation of input or optional fields are marked in bold letters,
e.g.: Start of measurement range
“Value” Input or selective values are marked in inverted commas.
e.g.: Enter the value “4 mA” under Start of measurement range.
[Button] Pushbuttons in dialog boxes are marked with bold letters in square
brackets.
e.g.: [Input]
[Key] Keys are marked with bold letters in square brackets.
e.g.: [F5]
Manual
WAGO-I/O-SYSTEM 750 Important Notes 19
750-8207 PFC200 CS 2ETH RS 3G
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 Kontakttechnik GmbH & Co. KG reserves the right to provide for any
alterations or modifications. WAGO Kontakttechnik GmbH & Co. KG owns all
rights arising from the granting of patents or from the legal protection of utility
patents. Third-party products are always mentioned without any reference to
patent rights. Thus, the existence of such rights cannot be excluded.
2.1.2 Personnel Qualifications

All sequences implemented on 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 WAGO-I/O-SYSTEM 750 in Compliance with

Underlying Provisions
Fieldbus couplers, fieldbus controllers and I/O modules found in 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 programmable
controllers, the signals can also be (pre-) processed.
The devices have been developed for use in an environment that meets the IP20
protection class criteria. Protection against finger injury and solid impurities up to
12.5 mm diameter is assured; protection against water damage is not ensured.
Unless otherwise specified, operation of the devices in wet and dusty
environments is prohibited.
Operating the WAGO-I/O-SYSTEM 750 devices in home applications without

further measures is only permitted if they meet the emission limits (emissions of
interference) according to EN 61000-6-3. You will find the relevant information in
the section “Device Description” > “Standards and Guidelines” in the manual for
the used fieldbus coupler/controller.
Appropriate housing (per 2014/34/EU) is required when operating the

WAGO-I/O-SYSTEM 750 in hazardous environments. Please note that a
Manual
20 Important Notes WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
prototype test certificate must be obtained that confirms the correct installation of
the system in a housing or switch cabinet.
The implementation of safety functions such as EMERGENCY STOP or safety

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

The devices to be supplied ex works are equipped with hardware and software
configurations, which meet the individual application requirements. These
modules contain no parts that can be serviced or repaired by the user. The
following actions will result in the exclusion of liability on the part of WAGO
Kontakttechnik GmbH & Co. KG:
• Repairs,
• Changes to the hardware or software that are not described in the
operating instructions,
• Improper use of the components.
Further details are given in the contractual agreements. Please send your
request for modified and new hardware or software configurations directly to
WAGO Kontakttechnik GmbH & Co. KG.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 the device only in appropriate housings, cabinets or in electrical

operation rooms!
The WAGO-I/O-SYSTEM 750 and its components are an open system. As such,
install the system and its components exclusively in appropriate housings,
cabinets or in electrical operation rooms. Allow access to such equipment and
fixtures to authorized, qualified staff only by means of specific keys or tools.
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.
Replace defective or damaged devices!

Replace defective or damaged device/module (e.g., in the event of deformed
contacts), since the long-term functionality of device/module involved can no
longer be ensured.
Protect the components against materials having seeping and insulating

properties!
The components are not resistant to materials having seeping and insulating
properties such as: aerosols, silicones and triglycerides (found in some hand
creams). If you cannot exclude that such materials will appear in the component
environment, then install the components in an enclosure being resistant to the
above-mentioned materials. Clean tools and materials are imperative for
handling devices/modules.
Manual
22 Important Notes WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
Clean only with permitted materials!

Clean housing and soiled contacts with propanol.
Do not use any contact spray!

Do not use any contact spray. The spray may impair contact area functionality in
connection with contamination.
Do not reverse the polarity of connection lines!

Avoid reverse polarity of data and power supply lines, as this may damage the
devices involved.
Avoid electrostatic discharge!

The devices are equipped with electronic components that may be destroyed by
electrostatic discharge when touched. Please observe the safety precautions
against electrostatic discharge per DIN EN 61340-5-1/-3. When handling the
devices, please ensure that environmental factors (personnel, work space and
packaging) are properly grounded.
2.3 Disclaimer
The “PFC200 CS 2ETH RS 3G” controller (750-8207) also communicates via the
mobile communications network. Please note that the mobile communications
services used by the controller may be affected by faults in the service provider’s
network. Such faults are beyond the control of WAGO Kontakttechnik GmbH &
Co. KG.
WAGO Kontakttechnik GmbH & Co. KG therefore rejects any guarantee for the
execution of the commands transmitted by/to the controller.
Manual
750-8207 PFC200 CS 2ETH RS 3G
2.4 Licensing Terms of the Software Package Used

The firmware for the “PFC200 CS 2ETH RS 3G” controller (750-8207) 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 Kontakttechnik GmbH & Co. KG on request. Send your request to
[email protected] with the subject “Controller Board Support Package.”
2.5 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 to an open

network such as the Internet or an office network. WAGO recommends
putting control components and control networks behind a firewall.
• Limit physical and electronic access to all automation components to

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

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

to restrict the access to and control of individual products and networks.
Manual
24 Device Description WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
3 Device Description
The controller 750-8207(PFC200 CS 2ETH RS 3G) 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 2 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.
For IEC-61131-3 programming in CODESYS applications, the controller provides

16 MB of program memory (flash) and 64 MB of data memory (RAM) under
CODESYS 2 and 64 MB of program and data memory (dynamically distributed)
under e!RUNTIME as well as 128 kB of retentive memory (retain and flag
variables) in an integrated NVRAM.
</dg_
Two ETHERNET interfaces and an integrated, interruptible switch enable wiring

for:
• In line topology with a common MAC address and IP address for both
interfaces.
• Two separate networks with a common MAC address and an IP address

for each interface.
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
Manual
WAGO-I/O-SYSTEM 750 Device Description 25
750-8207 PFC200 CS 2ETH RS 3G
• MODBUS UDP Master/Slave
• MODBUS RTU Master/Slave (via RS-232 or RS-485)
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!
The fieldbus configuration can be defined with the WAGO-I/O-PRO or

e!COCKPIT controller configuration, depending on the set runtime system
(CODESYS 2 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 an Internet 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 Telnet server
• 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 CODESYS Runtime Environment
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
750-8207 PFC200 CS 2ETH RS 3G
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_
Only use recommended memory card!

Use only the SD memory card available from WAGO (item No. 758-879/000-
001) as it is suitable for industrial applications subjected to environmental
extremes and for use in this device.
Compatibility with other commercially available storage media cannot be
guaranteed.
SIM card not included!

Please note that an SIM card is required to use the mobile communications
function with the controller. The SIM card may be obtained from typical service
providers such as T-Mobile, VODAFONE or O2.
Select a suitable mobile communications tariff for your application, e.g., a flat-
rate deal with reduced data rates when the inclusive volume covered by the flat-
rate tariff is exceeded and/or a tariff with a texting package.
Flat rate recommended!

Data traffic may occur even when no user data is exchanged in order to maintain
the mobile communication network. Some mobile communications providers also
charge for this infrastructure data traffic. Therefore, WAGO recommends using a
mobile communications contract with a flat rate or clarifying the charges for
infrastructure data traffic (e.g., dialup, location etc.) with the mobile
communications provider in advance.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.1 View
Figure 1: View of device
Table 4: Legend for Figure “View”

Item Description See section
1 Marking Options (Mini-WSB) ---
“Indicating elements” >
2 LED Indicators – Power Supply “Indicating element power
supply”
“Connections” > “Data
3 Data contacts
Contacts/Local Bus”
CAGE CLAMP® Connections for Power “Connections” > “CAGE
4
Supply CLAMP® connections”
5 Slot for memory card “Memory card slot”
6 Slot for SIM card “SIM card slot”
“Mounting” > “Inserting
Device”
7 Releasing strap
“Removal” > “Removing
Device”
Power contacts for power supply of “Connections” > “Power
8
down-circuit I/O modules contacts/ Field-side supply”
“Connections” > “Mobile
9 Mobile radio antenna connection radio antenna
communication”
“Connections” > “Service
10 Service Interface (behind the flap)
interface”
Manual
750-8207 PFC200 CS 2ETH RS 3G
“Operating elements” >

11 Mode selector switch
“Mode selector switch”
“Connections” > “Network
12 ETHERNET Connections connections ETHERNET –
X1, X2”
“Mounting” > “Inserting
Device”
13 Safe Locking Feature
“Removal” > “Removing
Device”
“Connections” >
14 Serial interface “Communication port RS-
232/RS-485 – X3”
“Indicating elements” >
15 LED Indicators – System “Indicating elements
Fieldbus/System”
“Operating elements” >
16 Reset button (in hole)
“Reset button”
"Indicating elements" >
LED indicators – Mobile radio network
17 "Indicating elements
status
Fieldbus/System"
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.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
3.2.1 Manufacturing Number

The serial number indicates the delivery status directly after production.
Figure 2: Marking Area for Serial Numbers
There are two serial numbers in two rows in the side marking. They are left of the
release tab. The first 10 positions in the longer row of the serial numbers contain
version and date identifications.
Example structure of the rows: 0114010101…
01 14 01 01 01 (additional positions)
WW YY FW -- HW FL -
Calendar Year Firmware Hardware Firmware Internal information
week version version loader
version
The row order can vary depending on the production year, only the longer row is
relevant. The back part of this and the shorter row contain internal administration
information from the manufacturer.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.3 Connectors
3.3.1 Data Contacts/Local Bus
Do not place the I/O modules on the gold spring contacts!

Do not place the I/O modules on the gold spring contacts in order to avoid soiling
or scratching!
Ensure that the environment is well grounded!

The devices are equipped with electronic components that may be destroyed by
electrostatic discharge. When handling the devices, ensure that the environment
(persons, workplace and packing) is well grounded. Avoid touching conductive
components, e.g. data contacts.
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 3: Data Contacts
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.3.2 Power Jumper Contacts/Field Supply
Risk of injury due to sharp-edged blade contacts!

The blade contacts are sharp-edged. Handle the I/O module carefully to prevent
injury.
The controller 750-8207is 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 4: Power Jumper Contacts
Table 5: 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
Do not exceed maximum current via power jumper contacts!

The maximum current to flow through the power jumper contacts is 10 A.
Greater currents can damage the contacts.
When configuring your system, ensure that this current is not exceeded.
If exceeded, insert an additional supply module.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.3.3 CAGE CLAMP® Connectors
®
Figure 5: CAGE CLAMP connections
®
Table 6: 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-8207 PFC200 CS 2ETH RS 3G
3.3.4 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” and for firmware download.
Figure 6: Service Interface (Closed and Open Flap)
Table 7: 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-8207 PFC200 CS 2ETH RS 3G
3.3.5 Network Connectors
Figure 7: Network Connections – X1, X2
Table 8: 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-8207 PFC200 CS 2ETH RS 3G
3.3.6 Communication Interface

Kommuni kati onsansc hlus s
Figure 8: RS-232/RS-485 – Communication Connection – X3
Table 9: Legend for Figure “RS-232/RS-485 – Communication Connection – X3”

RS-232 RS-485
Contact
Signal Description Signal Description
1 NC Not assigned NC Not assigned
2 RxD Receive Data NC Not assigned
3 TxD Transmit Data RxD/TxD-P Receive/transmit data
+
5 FB_GND Ground FB_GND Ground
6 NC Not assigned FB_5V Power Supply
7 RTS Request to send NC Not assigned
8 CTS Clear to send RxD/TxD-N Receive/transmit data
−
Enclosure Shield Shielding Shield Shielding
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-8207 PFC200 CS 2ETH RS 3G
3.3.6.1 Operating as an RS-232 Interface

Kommuni kati onsansc hlus s
Depending on the device type DTE (e.g., PC) or DCE (e.g., PFC, modem), the
RS-232 signals have different data directions.
Table 10: 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 DTE-to-DTE connection, the signal connections are crossed.
Figure 10: Termination with DTE-DTE Connection (Cross-Over)
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.3.6.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 segment 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!
Operation without proper termination of the RS-485 network may result in
transmission errors.
Figure 11: RS-485 Bus Termination
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.3.7 Antenna Connector

The screw connector (SMA jack) for the mobile radio antenna is located at the
front of the housing.
Figure 12: Mobile Radio Antenna Connection
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.4 Display Elements
3.4.1 Power Supply Indicating Elements
Figure 13: Power Supply Indicating Elements
Table 11: Legend for Figure “Power Supply Indicating Elements”

Description Color Description
A Green/off Status of system power supply voltage
B Green/off Status of field-side power supply voltage
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.4.2 Fieldbus/System Indicating Elements
Figure 14: Indicating elements for fieldbus/system
Table 12: Legend for Figure “Fieldbus/System Indicating Elements”

Designation Color Description
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
User LED, programmable using function
Red/Green/
USR blocks from the WAGO libraries to control the
Orange/Off
LEDs
Red/Green/
▐██ Signal quality (S5)
Orange/Off
Red/Green/
██ Signal quality (S4)
Orange/Off
Red/Green/
▐█ Signal quality (S3)
Orange/Off
Red/Green/
█ Signal quality (S2)
Orange/Off
Red/Green/
▐ Signal quality (S1)
Orange/Off
Red/Green/
NET Network status
Orange/Off
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.4.3 Memory Card Indicating Elements
Figure 15: Indicating Elements, Memory Card Slot
Table 13: Legend for Figure “Indicating Elements, Memory Card Slot”
SD Yellow/Off Memory card status
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.4.4 Network Indicating Elements
Figure 16: Indicating Elements, RJ-45 Jacks
Table 14: Legend for Figure “Indicating Elements, RJ-45 Jacks”

LNK Green/Off ETHERNET connection status
ACT Yellow/Off ETHERNET data exchange
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.4.5 Mobile Communications Network Status Indicating

Elements
Figure 17: Mobile Radio Network Status Indicators
Table 15: Legend for the “Mobile Radio Network Status Indicators” Figure
CON Green/off Mobile radio network status
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.5 Operating Elements
3.5.1 Operating Mode Switch
Figure 18: Mode Selector Switch
The function of the mode selector switch depends on the activated runtime
system (CODESYS 2 or e!RUNTIME).
3.5.1.1 CODESYS 2 Runtime System

</dg_
Table 16: Mode Selector Switch

Item Activation Function
Normal mode
RUN Latching
CODESYS 2 application runs.
Stop
STOP Latching
CODESYS 2 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.
3.5.1.2 e!RUNTIME Runtime System

</dg_
Table 17: 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-8207 PFC200 CS 2ETH RS 3G
3.5.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

- Perform a software reset (restart)
- Restore factory setting (factory reset)
Please refer to the same sections in the back of this manual for information about
the functions.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.6 Slot for Memory Card
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-8207 PFC200 CS 2ETH RS 3G
3.7 SIM Card Slot
Figure 21: SIM Card Slot
Table 18: Legend for Figure “SIM Card Slot”

Position Description
1 Release button for SIM card slot
2 SIM card holder
3 SIM card slot
The SIM card slot is located on the front of the housing. The SIM card is locked in
the housing with a SIM card holder.
Inserting and removing the SIM card is described in the section “Service” >
“Inserting and Removing the SIM Card”!
SIM card not included!

Please note that an SIM card is required to use the mobile communications
function with the controller. The SIM card may be obtained from typical service
providers such as T-Mobile, VODAFONE or O2.
Select a suitable mobile communications tariff for your application, e.g., a flat-
rate deal with reduced data rates when the inclusive volume covered by the flat-
rate tariff is exceeded and/or a tariff with a texting package.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.8 Schematic Diagram
Figure 22: Schematic diagram
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.9 Technical Data
3.9.1 Mechanical Data

Table 19: Technical Data − Mechanical Data
Width 103 mm
Height (from upper edge of DIN 35 rail) 65 mm
Length 100 mm
Weight 288 g
3.9.2 System Data

</dg_
Table 20: Technical Data – System Data

CPU Cortex A8, 600 MHz
Operating System Real-time Linux® 4.9.47-rt37
(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 758-
879/000-001 memory card.)
3.9.3 Power Supply

Table 21: 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) 700 mA
Isolation 500 V system/supply
Buffer for system power supply!

The system power supply must be buffered to bridge power outages. As the
power demand depends on the respective node configuration, buffering is not
implemented internally.
To achieve power outages of 1 ms to 10 ms according to IEC61131-2, determine
the buffering appropriate for your node configuration and structure it as an
external circuit.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.9.4 Clock
</dg_
Table 22: Technical Data – Clock

Drift - system clock (25 °C) 20 ppm
Drift - RTC (25 °C) 3 ppm
Buffer time RTC (25 °C) 30 days
3.9.5 Programming
Table 23: Technical Data – Programming
Programming CODESYS 2 WAGO-I/O-PRO V2.3
e!RUNTIME e!COCKPIT
IEC 61131-3 LD, FBD, ST, FC
CODESYS 2 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 and data memory 60 MByte (dynamically distributed)
Non-volatile memory (NVRAM, 128 kByte
Retain + Flags)
Retain variables max. CODESYS 2 10,000

e!RUNTIME Not specified
3.9.6 Local Bus

Table 24: Technical Data – Local Bus
Number of I/O modules (per node) 64
with bus extension 250
Input and output process CODESYS 2 1,000 words
image (max.) e!RUNTIME Not specified
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.9.7 ETHERNET
Table 25: 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 2 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
3.9.8 Communication Interface

Table 26: 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 MODBUS RTU
3.9.9 Mobile Radio Modem

Table 27: Technical Data – Mobile Radio Modem
Technology GSM / Edge / UMTS / HSPA+
SIM card type / slot Mini SIM, push-push mechanism
Communication Quad band
Communication types SMS (bidirectional),
GPRS connection to the Internet
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.9.10 Connection Type

Table 28: Technical Data – Field Wiring
Wire connection CAGE CLAMP®
Cross section 0.08 mm² … 2.5 mm², AWG 28 … 14
Stripped lengths 8 mm … 9 mm / 0.33 in
Table 29: Technical Data – Power Jumper Contacts

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

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

Table 31: Technical Data – Climatic Environmental Conditions
Surrounding air temperature (operation) 0 °C … 55 °C
Surrounding air temperature (operation) −20 °C … +60 °C
for components with extended
temperature range (750-xxx/025-xxx)
Surrounding air temperature (storage) −25 °C … +85 °C
Surrounding air temperature (storage) −40 °C … +85 °C
for components with extended
temperature range (750-xxx/025-xxx)
Relative humidity 5 % … 95 % without condensation
Operating altitude 0 … 2000 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.10 Approvals
More information about approvals.

Detailed references to the approvals are listed in the document “Overview
Approvals WAGO-I/O-SYSTEM 750”, which you can find via the internet under:
www.wago.com > SERVICES > DOWNLOADS > Additional documentation and
information on automation products > WAGO-I/O-SYSTEM 750 > System
Description.
The following approvals have been granted to the “PFC200 CS 2ETH RS 3G”
controller (750-8207):
Conformity Marking
FCC Federal Communications Commission

This equipment has been tested and found to comply with the limits
for a Class A digital device, pursuant to Part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be
required to correct the interference at his own expense.
Modifications not expressly approved by this company could void the
user´s authority to operate the equipment.
HF Exposition
This equipment complies with FCC and ISED radiation exposure
limits set forth for an uncontrolled environment. This equipment
should be installed and operated with a minimum distance of 20 cm
between the radiator and your body.
Cet équipement est conforme aux exigences des commissions FCC
et ISED relatives aux limitations de l'exposition à l'irradiation pour un
environnement non contrôlé. Cet équipement doit être installé et
utilisé en respectant une distance minimale de 20 cm entre le
radiateur et le corps humain.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3.11 Standards and Guidelines

The “PFC200 CS 2ETH RS 3G” controller (750-8207) 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 55
750-8207 PFC200 CS 2ETH RS 3G
4 Function Description
</dg_
4.1 Network
4.1.1 Interface Configuration

The ETHERNET X1 and X2 interfaces of the controller are connected with an
internal 3-port switch, in which the third port is connected to the CPU.
Interfaces X1 and X2 can either be operated in Switch mode or as separate
network interfaces. The switching can be performed during the runtime.
The Switch mode is activated by default and during initial startup. The
“Configuration mode” is set to “DHCP.”
For interface X1, a fixed IP address can be set temporarily (“Fix IP Address”).
The setting is carried out with the Reset button (see Section “Commissioning” >
… > “Temporarily Setting a Fixed IP Address”).
Setting a fixed IP address has no effect on the mode previously set.
4.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.
4.1.1.2 Operation with Separate Network Interfaces
When operating with separate network interfaces, both ETHERNET interfaces

can be configured and used separately.
Note that the two interfaces still have the same MAC address. Therefore, they
must not be operated in the same network segment.
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
56 Function Description WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
4.1.2 Network Security
4.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.
4.1.2.1.1 Services and Users
All password-protected services and their associated users are listed in the
following table.
Users
WBM Linux®
SNMP
admin
admin
Service
user
user
root
Web Based Management

X X
(WBM)
Linux® console X X X
Console Based Management
X X
(CBM)
CODESYS X
Telnet X X X
FTP X X X
FTPS X X X
SSH X X X
SNMP X
Manual
750-8207 PFC200 CS 2ETH RS 3G
4.1.2.1.2 WBM User Group
WBM has its own user administration system. The users in this system are
isolated from the other user groups in the system for security reasons.
Detailed information about this is given in the Section “WBM User

Administration”.
Table 32: WBM Users

Users Permissions Default Password
admin All (administrator) wago
user Supported to a limited extent user
guest Display only ---
Change passwords
4.1.2.1.3 Linux® User Group
The Linux® users group include the actual users of the operating system, which is
likewise used by most services.
The passwords for these users must be configured through a terminal connection
via SSH/RS-232.
®
Table 33: 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
Change passwords
4.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-8207 PFC200 CS 2ETH RS 3G
4.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.
4.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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
</dg_
4.1.3 Network Configuration
4.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. If there are multiple
network interfaces with DHCP, the last received host name is valid. 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.
4.1.4 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:
1. Destination address,
2. Destination mask,
3. Gateway address,
4. Gateway metric.
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
Manual
750-8207 PFC200 CS 2ETH RS 3G
no specific routing entry exists for their destination address and destination mask
are sent to this default gateway.
1. Default Gateway
If the value “default” is entered in the “Destination Address” field, a default
gateway, also called a default route, is defined. The value “0.0.0.0” must
then be set in the “Destination Mask” field.
2. 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.
If the IP address of the gateway is outside the IP address space that the
controller can reach, the associated route is not enabled.
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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
The metric value of the configured routing entries can be specified for the
controller. The default value for the metric is 20. Besides the manually
configurable routes, default gateways can also be set via DHCP replies. All
default gateways transferred via DHCP are assigned a permanent metric value of
10.
Metric example:
A controller obtains its IP configuration via a DHCP server and receives both the
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, “Routing
enabled entirely” must be enabled in the “General Routing Configuration” 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
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
Gateway Metric 20 Route priority
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-8207 PFC200 CS 2ETH RS 3G
4.1.5 Network Services
4.1.5.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 (X1, X2).
The Hostname and Domain parameters are stored according to the LIFO
principle (Last In First Out). The settings from the last DHCP offer received are
always used.
The DNS and NTP Server parameters are stored centrally for global use. All
transmitted parameters are saved.
4.1.5.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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
The settings are made, for example, in the WBM via the “DHCP Configuration”
page.
The DHCP server also passes other parameters in addition to the IP address.
The following table shows the complete list.
Table 34: 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
server must be manually configured. For the controller, the DHCP server service
is handled by the program "dnsmasq".
From a Linux® command line, an editor must be used to change the file
“/etc/dnsmasq.d/dnsmasq_default.conf” to set the configuration.
4.1.5.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-8207 PFC200 CS 2ETH RS 3G
4.1.6 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 Bluemix are available.
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.”
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.
Observe the additional documentation!

You can find a detailed description of the cloud connectivity software package
with a PFC100 and information on PLC programming in Application Note
A500920 in the Downloads area: www.wago.com.
4.1.6.1 Components of the Cloud Connectivity Software Package
Table 35: 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
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
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.”
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 23: Connecting the PFC Controller Generation to a Cloud
Manual
750-8207 PFC200 CS 2ETH RS 3G
4.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.
4.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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
4.2.2 Data Backup

The controller has a backup function and a restore function.
The necessary settings can be made and the functions can be executed via the
WBM pages or via the CBM “Backup” and “Restore” menus.
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 (“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.
4.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 via the WBM page “Firmware Backup” or the
CBM menu “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/orange during the save operation.
The device settings and files of the internal drive are then saved on the target
medium.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
4.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 via the WBM page “Firmware Restore” or the
CBM menu “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/orange 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.
The boot project is loaded automatically and the settings automatically activated
after a restart. The “Boot project location” setting on the “General PLC Runtime
Configuration Web” page of the WBM determines whether the boot project of the
internal drive or the memory card is loaded.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
4.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/orange during the access.
The memory card is then ready for operation and available under /media/sd.
4.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/orange during the attempted
access.
The controller then works without a memory card.
Manual
750-8207 PFC200 CS 2ETH RS 3G
4.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.
Some conditions must be met before moving the directory.
• A running IEC-61131 application must be stopped and the device restored

to its initial state using the “Reset” function. Any boot project is deleted.
• 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.
Only when the two conditions are met can the “Home directory on memory card
enabled” checkbox be selected from the WBM on the “PLC Runtime” page.
Press the [Submit] button to apply the settings, which take 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.
4.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-8207 PFC200 CS 2ETH RS 3G
Table 36: 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
WAGO-I/O-SYSTEM 750 Mounting 77
750-8207 PFC200 CS 2ETH RS 3G
5 Mounting
5.1 Installation Position
Along with horizontal and vertical installation, all other installation positions are
allowed.
Use an end stop in the case of vertical mounting!

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

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

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

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

The maximum total length of a fieldbus node without fieldbus coupler/controller
and without using a 750-628 I/O Module (coupler module for internal data bus
extension) may not exceed 780 mm.
Also note the limitations of individual fieldbus couplers/controllers.
Manual
78 Mounting WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
5.3 Mounting onto Carrier Rail

5.3.1 Carrier Rail Properties
All system components can be snapped directly onto a carrier rail in accordance
with the European standard EN 50022 (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-8207 PFC200 CS 2ETH RS 3G
5.3.2 WAGO DIN Rails

WAGO carrier rails meet the electrical and mechanical requirements shown in the
table below.
Table 37: 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.
5.4 Spacing
The spacing between adjacent components, cable conduits, casing and frame
sides must be maintained for the complete fieldbus node.
Figure 24: 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-8207 PFC200 CS 2ETH RS 3G
5.5 Mounting Sequence

Fieldbus couplers/controllers and I/O modules of the WAGO-I/O-SYSTEM 750
are snapped directly on a carrier rail in accordance with the European standard
EN 50022 (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/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.

injury.
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 (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/controllers to guarantee proper data transfer.
Manual
750-8207 PFC200 CS 2ETH RS 3G
5.6 Inserting Devices
Perform work on devices only if they are de-energized!

Working on energized devices can damage them. Therefore, turn off the power
supply before working on the devices.
5.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 25: Release Tab of Controller
Manual
WAGO-I/O-SYSTEM 750 Connect Devices 83
750-8207 PFC200 CS 2ETH RS 3G
6 Connect Devices
6.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 26: Connecting a Conductor to a CAGE CLAMP
Manual
84 Connect Devices WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
6.2 Power Supply Concept
6.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!

Without overcurrent protection, the electronics can be damaged.
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!

Without overcurrent protection, the electronics can be damaged.
If you alternatively implement the overcurrent protection for the field supply with
an external fuse, a 10 A fuse should be used.
Manual
WAGO-I/O-SYSTEM 750 Connect Devices 85
750-8207 PFC200 CS 2ETH RS 3G
6.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 38: 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 27: 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
86 Commissioning WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
7 Commissioning
7.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 (750-600)

(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 green flashing of all LEDs. After a
few seconds the SYS LED will signal 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.
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
WAGO-I/O-SYSTEM 750 Commissioning 87
750-8207 PFC200 CS 2ETH RS 3G
7.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-8207 PFC200 CS 2ETH RS 3G
7.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 39: Default IP Addresses for ETHERNET Interfaces

Ethernet interface Default setting
X1/X2 Dynamic assignment of IP address using “Dynamic Host
Configuration Protocol” (DHCP)
Adapt IP addressing for your specific system structure to ensure that the PC and
the controller can communicate with one another using one of the available
configuration tools (WBM, “WAGO Ethernet Settings”, CBM) (see section
“Configuration”).
Example for incorporating the controller (192.168.2.17) into an existing

network:
If the IP address of your host PC is 192.168.1.2, for example, then the controller
must be on the same subnet. That is, with the net mask 255.255.255.0, the first
three digits of the controller must match those of your PC. This yields the
following address range for the controller:
Table 40: Network Mask 255.255.255.0

Host PC Subnet address range for the controller
192.168.1.2 192.168.1.3 … 192.168.1.254
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.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 28: “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-8207 PFC200 CS 2ETH RS 3G
7.3.2 Changing an IP Address Using the “CBM” Configuration

Tool via the Serial Interface
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. Link a PC to the X3 serial interface using a terminal program.
2. 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.”
3. Start the configuration tool by entering the command “cbm” on the

command line and then press [Enter].
Figure 29: CBM Starting Screen
Manual
750-8207 PFC200 CS 2ETH RS 3G
4. In the Main menu use the keyboard (arrow keys or numeric keypad) to
move to and select Networking and then press [Enter].
Figure 30: CBM – Selecting “Networking”
5. In the Networking menu select TCP/IP and press [Enter].
Figure 31: CBM – Selecting “TCP/IP”
6. In the menu TCP/IP select IP Address and press [Enter].
Figure 32: CBM – Selecting “IP address”
Manual
750-8207 PFC200 CS 2ETH RS 3G
7. In the menu TCP/IP Configuration select IP Address and press [Enter].
Figure 33: CBM – Selecting the IP Address
8. 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 34: CBM – Entering a New IP Address
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.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 35: “WAGO Ethernet Settings” – Starting Screen (Example)
5. Click [Read] to read in and identify the connected controller.
Manual
750-8207 PFC200 CS 2ETH RS 3G
6. Select the “Network” tab:
Figure 36: “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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.3.4 Temporarily Setting a Fixed IP Address

This procedure temporarily sets the IP address for the X1 interface to the fixed
address “192.168.1.17”.
When the switch is enabled, the fixed address is also used for interface X2.
When the switch is disabled, the original address setting for interface X2 is not
changed.
No reset is performed.
To make this setting, set the mode selector switch to STOP and press and hold
the Reset button (RST) for longer than 8 seconds.
Execution of the setting is signaled by the “SYS” LED flashing orange.
To cancel this setting, perform a software reset or switch off the controller and
then switch it back on.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.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 37: Example of a Function Test
4. If the test is completed successfully, close the MS DOS window.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.5 Changing Standard Passwords
Change 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.
Therefore 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.
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 serial interface (X3).
2. Start a terminal program on the PC.
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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.7 Initiating Reset Functions

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

The warm start reset function depends on the activated runtime system

</dg_
The CODESYS 2 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.
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.
7.7.2 Cold Start Reset

The cold start reset function depends on the activated runtime system

</dg_
On a cold start reset the CODESYS 2 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.

</dg_
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
</dg_
7.7.3 Software Reset

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.
All LEDs will light up briefly in green to signal reset completion.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8 Configuration
The following methods are available for configuring the controller:
• Access to the Web-based management system via the PC using an

Internet browser (section “Configuration Using Web-Based Management
[WBM]”)
• Access to the “Console-Based Management” system (CBM) via the PC

using a terminal program (via ETHERNET and/or RS-232 interface; section
“Configuration Using a Terminal Program”)
• Access via the CODESYS PLC program using the CODESYS 2 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-8207 PFC200 CS 2ETH RS 3G
7.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 an Internet browser:
1. Connect the controller to the ETHERNET network via the ETHERNET

interface X1.
2. To access the pages, enter “https://” followed by the controller's IP address

and “/wbm” in the address line of your browser, e.g.,
“https://192.168.1.17/wbm.”
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” using the “Fixed IP address” function (see Section
“Commissioning” > … > “Temporarily Setting a Fixed IP Address”).
If you have installed a DHCP server on your PC and would like to access WBM
through DHCP, use the other interface. You can find detailed information about
this in the section “Assigning an IP Address Using DHCP.”
Displaying the Controller Start Page

If the controller does not display the start page, ensure that your Internet browser
settings permit the bypassing of the proxy server for local addresses. Also check
whether your PC is located in the same subnet as the controller.
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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Some pages of the WBM are accessible only for certain users. They are only
displayed if you have logged into the WBM. You can access the login form via
the “Login” link. Pages which cannot be accessed with your current user name
are already grayed out in the navigation. You can nevertheless select the entries
in the navigation bar and are then routed directly to the login form.
As soon as you have logged in, your current user name is displayed in the
header of the WBM. By clicking the “Logout” link you can log out again and then
log in again with a different user name. When using the WBM without logging in,
you are granted “Guest” access rights.
You must be logged into the WBM in order to have write or read access to (most)
parameters. This is checked with every access to the device.
If you have disabled cookies in your 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 browser is then not able to store
the data of your login session.
Figure 38: Entering Authentication
7.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
The standard passwords are documented in these instructions and thus do not
offer adequate protection. Change the passwords to meet your particular needs.
See Section “Administration - Users Page.”
If you do not change these passwords, a warning will appear each time you call
up a website after logging in.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 39: Password Reminder
Table 41: User Settings in the Default State

Users Password
user user
admin wago
Observe access rights

Users in WBM are authorized exclusively for access to websites. User
administration for controller applications is configured separately.
Access to the WBM pages is as follows:
Table 42: Access Rights for WBM Pages

Navigation WBM page User
Information Status Information guest
PLC Runtime
– Information PLC Runtime Information guest
– General Configuration General PLC Runtime Configuration user
– WebVisu PLC WebVisu guest
Networking
– Host/Domain Name Configuration of Host and Domain Name user
– TCP/IP TCP/IP Configuration user
– Ethernet Ethernet Configuration user
- Routing Routing user
Firewall
– General Configuration General Firewall Configuration user
– MAC Address Filter Configuration of MAC Address Filter user
– User Filter Configuration of User Filter user
Clock Configuration of Time and Date user
Administration
– Users Configuration of the users for the Web- admin
based Management
– Create Image Create bootable Image admin
– Serial Interface Configuration of Serial Interface RS233 admin
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 42: Access Rights for WBM Pages
Navigation WBM page User
– Service Interface Configuration of Service Interface admin
– Reboot Reboot Controller admin
Package Server
– Firmware Backup Firmware Backup admin
– Firmware Restore Firmware Restore admin
– System Partition System Partition admin
Mass Storage Mass Storage admin
Software Uploads Software Uploads admin
Ports and Services
– Network Services Configuration of Network Services user
– NTP Client Configuration of NTP Client user
– PLC Runtime Services Configuration of PLC Runtime Services user
– SSH SSH Server Settings user
– TFTP TFTP Server user
– DHCP DHCP Configuration user
– DNS Configuration of DNS Service user
– MODBUS MODBUS Services Configuration user
Cloud Connectivity Configuration of Cloud Connectivity admin
SNMP
– General Configuration Configuration of general SNMP admin
parameters
– SNMP v1/v2c Configuration of SNMP v1/v2c parameters admin
– SNMP v3 Configuration of SNMP v3 Users admin
Diagnostic Diagnostic Information guest
Modem Configuration of internal 3G Modem admin
OpenVPN / IPsec Configuration of OpenVPN / IPsec admin
Security Security Settings admin
Legal Information
– Open Source Licenses Open Source Licenses guest
– WAGO Licenses WAGO Licenses guest
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.2 General Information about the Page
Figure 40: WBM Browser Window (Example)
The device name is displayed in the header of the browser window. When the
user has logged out, a [Login] button is displayed on the right in the header line,
when logged in a [Logout] button is displayed.
The navigation tree is shown on the left of the browser window. You can use this
navigation tree to go to the individual pages and, where provided, subpages
included in these pages. Some pages can only be called after a successful login.
To log in click the [Login] button and enter the user name and password in the
login window.
Manual
750-8207 PFC200 CS 2ETH RS 3G
A status area with the following elements is displayed on the right:
Figure 41: WBM Status Information (Example)
• WBM status:
This indicates whether the WBM is currently communicating with the device
in the background. In other words, one or more requests have been sent
and the browser is waiting for a response. Movement is then visible in the
graphic. This occurs when data is read on initial call-up of the page, when
the user has sent off a change form or when data is reloaded automatically
in cycles, e.g., the contents of the status area.
• Local Time:
Local time on the device
• Local Date:
Local date on the device
• PLC Switch:
Setting of the mode selector switch
• LEDs:
This indicates the status of the device LEDs. 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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
The contents of the individual pages and sub-pages are explained in the
following sections.

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.3 “Status Information” Page
The following tables explain the parameters listed on this page:
7.8.1.3.1 “Controller Details” Group
This group displays the properties of the controller.
Table 43: WBM “Status Information” Page – “Controller Details” Group

Parameter Explanation
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
7.8.1.3.2 “Network Details Xn” Group(s)
This group displays the network and interface properties of the controller.
If the switch is enabled, one group (“Network Details X1/X2”) is shown for both
connections.
If the switch is disabled, a separate group (“Network Details X1” / “Network
Details X2”) is shown for each connection.
Table 44: WBM “Status Information Page – “Network Details Xn” Group(s)
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-8207 PFC200 CS 2ETH RS 3G
7.8.1.4 “General PLC Runtime Configuration” Page
The settings for the boot project created with the programming software are given
on the “General PLC Runtime Configuration” page.
7.8.1.4.1 “General PLC Runtime Configuration” Group
Table 45: WBM “General PLC Runtime Configuration” Page – “General PLC Runtime Configuration”
Group
Select here the PLC runtime system to be enabled.
None No runtime system is enabled.

PLC runtime version CODESYS 2 runtime system is
CODESYS 2
enabled.
e!RUNTIME runtime system is
e!RUNTIME
enabled.
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!
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.
Click [Submit] to apply the change.
The runtime system change is effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
The home directory change only takes effect after restarting the controller. For
this purpose, use the WBM reboot function. Do not shut down the controller too
early!
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.5 “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.
7.8.1.5.1 “PLC Runtime” Group
Table 46: WBM “PLC Runtime Information” Page – “PLC Runtime” Group
The version of the currently activated runtime
system is shown here.
Version If the runtime system is disabled, “None” is
displayed and the subsequent fields of this group
are disabled.
This shows the version number of the web server.
Web Server Version This field is only visible when CODESYS 2 is
enabled as the runtime system.
The PLC operating state is shown. This field is only
visible when CODESYS 2 is enabled as the runtime
State 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 This field is only visible when CODESYS 2 is
enabled as the runtime system.
7.8.1.5.2 “Project Details” Group
This group is only visible if CODESYS 2 is enabled as the runtime system.
Table 47: WBM “PLC Runtime Information” Page – “Project Details” Group
Date Display of project information that the programmer
entered in the PLC program (in programming
Title
software under Project > Project Information...).
Version The information only appears when a PLC program
Author is run.
Descriptive texts up to 1024 characters long are
Description given under “Description.”
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.5.3 “Task n” Group(s)
This group is only visible if CODESYS 2 is enabled as the runtime system.
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.
Click [+] to expand the group and display the following information.
Table 48: 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
To hide this information, click [–].
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.6 “PLC WebVisu” Page
The settings for the web visualization created in the runtime system are shown
on the “PLC WebVisu” page.
7.8.1.6.1 “Web Server Configuration” Group
Table 49: WBM “PLC WebVisu” Page – “Web Server Configuration” Group
CODESYS 2 Webserver This indicates the status (enabled/disabled) of the
State CODESYS 2 web server.
e!RUNTIME Webserver This indicates the status (enabled/disabled) of the
State e!RUNTIME web server.
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.
Web-Visu The web visualization of the runtime
system is displayed.
Click [Submit] to apply change. The change is effective 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 web server must be enabled (in WBM under
“Ports and Services” -> “PLC Runtime Services”) and there must be a suitably
configured application.
Regardless of the default web server setting, the WBM can be called up at any
time with “https://<IP address>/wbm” and the web visualization with
“https://<IP address>/webvisu.”
You can obtain additional information on CODESYS 2 web visualization in the

section of the same name.
Possible error messages when calling up the web visualization

The “500 − Internal Server Error” message indicates that the web server is not
enabled.
A page with the header “WebVisu not available” means that no application has
been loaded in the controller using web visualization.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.7 “Configuration of Host and Domain Name” Page
The settings for the general TCP/IP parameters are found on the “Configuration
of Host and Domain Name” page.
7.8.1.7.1 “HostName” Group
Table 50: 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 here the hostname of your controller to be
used if the network interface is changed to a static
Configured
IP address or if no hostname is transmitted with a
DHCP response.
Click [Submit] to apply the change. The change is effective immediately.
If a hostname is supplied via a DHCP response, this is enabled in the system. If

there are several network interfaces with DHCP always the last received hostname
is valid.
If only the hostname configured here is to be valid, the configuration of the DHCP
server must be adapted so that no hostnames are transferred in the DHCP
response.
7.8.1.7.2 “Domain Name” Group
Table 51: WBM “Configuration of Host and Domain Name” Page – “Domain Name” Group
The domain name currently used is displayed.
It may differ from the configured domain name if you
Currently used
have selected dynamic assignment of an IP address
via DHCP or BootP.
Enter the domain name.
Configured
The default entry is “localdomain.lan”.
If a domain name is supplied via a DHCP response, this is enabled in the system.
If there are several network interfaces with DHCP, the last received domain name
is always valid.
If only the domain name configured here is to be valid, the configuration of the
DHCP server must be adapted so that no domain names are transferred in the
DHCP response.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.8 “TCP/IP Configuration” Page
The TCP/IP settings for the ETHERNET interfaces are shown on the “TCP/IP
configuration” page.
7.8.1.8.1 “IP Configuration (Xn)” Group(s)
If the switch is enabled, one group (“IP Configuration”) is shown for both
connections.
If the switch is disabled, a separate group (“IP Configuration X1” / “IP
Configuration X2”) is shown for each connection.
Table 52: WBM “TCP/IP Configuration” Page – “IP Configuration (Xn)” Group(s)
Select a static or dynamic IP address.
Static IP Static IP addressing
Configuration Type
DHCP Dynamic IP addressing
BootP Dynamic IP addressing
Enter here a static IP address. This is enabled if
IP Address “Static IP” is enabled in the Configuration Type
field.
Enter the subnet mask. This is enabled if “Static IP”
Subnet Mask
is enabled in the Configuration Type field.
Click [Submit] to apply changes. The changes are effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.8.2 “Default Gateway n” Groups
You can configure two default gateways. The controller transmits all network data
not going to a station on the local network to a default gateway. First the gateway
with the lowest metric is addressed. If this is not reached, the second gateway is
used. The selection is random if the metric is the same.
A default gateway can also be configured via DHCP. These default gateways are
given the metric 10, by which they are normally used before the static gateways.
Table 53: WBM “TCP/IP Configuration” Page – “Default Gateway n” Group

Set here whether the selected default gateway is to
be used.
Gateway enabled
Disabled The default gateway is not used.
Enabled The default gateway is used.
Enter here if any network devices or only a specific
network device or device pool is to be accessed.
“default” Any network devices can be reached.
Destination Address
Only a specific network device or
Network
device from the set address pool can
address
be reached.
Enter the subnet mask of the station.
Destination Mask If “default” is entered at Destination Address, the
value “0.0.0.0” must be entered here.
Gateway Address Enter the address of the default gateway.
Set here a number as the metric. With multiple
default gateways, the metric defines the gateway to
which data packets are first sent. Priority is given to
Gateway Metric the gateway with the lower metric. The default value
for the metric is 20.
The lowest value is 0.
The highest value is 4.294.967.295.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.8.3 “DNS Server” Group
Table 54: WBM “TCP/IP Configuration” Page – “DNS Server” Group

The addresses of the defined DNS servers are
Configured: None/
displayed. If no server has been defined,
DNS Server n
“Configured: None” is displayed.
Add additional DNS addresses.
New Server IP
You can enter 10 addresses.
The DNS servers assigned if necessary by DHCP
Additionally used
(or BootP) are displayed. If no DNS server has been
(assigned by DHCP)
assigned by DHCP (or BootP), “none” is displayed.
Click [Delete] to remove the selected DNS server. The change is effective
immediately.
Click [Add] to add the entered DNS server. The change is effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.9 “Ethernet Configuration” Page
The settings for Ethernet TCP/IP are located on the “Ethernet Configuration”
page.
7.8.1.9.1 “Switch Configuration” Group
Table 55: WBM “Ethernet Configuration” Page – “Switch Configuration” Group

Enable or disable the switch.
Both interfaces are operated with one
Switched
Interfaces IP address.
Each interface is operated with its own
Separated
IP address.
Enable or disable the mirroring of the data traffic
between the ports.
None Both Ethernet ports operating 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.
Set here the aging time of unused entries in the list
of MAC addresses with a port assignment to
external network stations.
Fast Aging enabled An unused address entry becomes
Disabled
obsolete after 200 seconds.
An unused address entry becomes
Enabled
obsolete after 800 microseconds.
Set here the broadcast limit for protection against
overloads.
Disabled No limitation of broadcast packets.
Broadcast Protection Limitation of incoming broadcast
packets to the selected percentage of
1 % ... 5 %
the total possible data throughput
(10/100Mbit).
Set here the basic limitation of the incoming data
traffic.
Rate Limit Disabled No limitation of the incoming data traffic
64 kbps … Limitation of the incoming data traffic to
99 mbps the entered value
7.8.1.9.2 “Interface Xn” Groups
One group (“Interface X1” / “Interface X2”) is displayed for each connection.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 56: WBM “Ethernet Configuration” Page – “Interface Xn” Groups
Enabled You can enable or disable the interface.
When Autonegotiation is enabled, the connection
Autonegotiation on modalities are negotiated automatically with the peer
devices.
Select the transmission speed and the duplex
method:
10 Mbit half-duplex Information can only be
Speed/Duplex sent or received.
100 Mbit half-duplex
10 Mbit full-duplex Information can be sent

and received
100 Mbit full-duplex simultaneously.
Click [Submit] to apply changes. The changes are effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.10 “Routing” Page
On the “Routing” page you can find settings and information on the routing
between the network interfaces.
7.8.1.10.1 “General Routing Configuration” Group
Table 57: WBM “Routing” Page – “General Routing Configuration” Group

Specify here 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 PFC on one network interface to
Routing enabled entirely
leave the PFC 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-8207 PFC200 CS 2ETH RS 3G
7.8.1.10.2 “Static Routes” Group
Each configured static route has its own area in the display.
To maintain compatibility with earlier firmware versions, at least two routing

entries always exist. These can be disabled, but not removed. If a route is either
removed or disabled, it is no longer entered in the system.
Table 58: WBM “Routing” Page – “Static Routes“ Group

Specify here whether the selected route should be
used.
Enabled
Disabled The route is not used.
Enabled The route is used.
Specify here 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 here.
Destination Mask If “default” is entered for Destination Address, the
value “0.0.0.0” must be entered here.
Gateway Address Enter the address of the gateway here.
Set the number used as the metric here.
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 default value for
the metric is 20.
The lowest value is 0.
The highest value is 2³²−1 = 4,294,967,295.
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-8207 PFC200 CS 2ETH RS 3G
7.8.1.10.3 “Dynamic Routes” Group
All default gateways received via DHCP are displayed here.

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.
7.8.1.10.4 “IP Masquerading” Group
Each entry has its own area in the display.
Table 59: WBM “Routing” Page – “IP-Masquerading” Group

Specify here whether IP masquerading should be
used for the selected network interface.
Enabled
Disabled IP masquerading is not used.
Enabled IP masquerading is used.
You can select the specified name of a network
Interface interface here. 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 “Routing enabled entirely” 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-8207 PFC200 CS 2ETH RS 3G
7.8.1.10.5 “Port Forwarding” Group
Each entry has its own area in the display.
Table 60: WBM “Routing” Page – “Port Forwarding” Group

Specify here 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 here. Alternatively, selecting “other” allows
you to specify any network interface name.
Enter the port here on which the controller receives
Port
network data packets that are to be forwarded.
Here you can select the protocol to be used for the
Protocol port forwarding. The options are TCP, UDP or both
protocols.
Specify the network address of the destination
Destination Address device here. This address replaces the original
destination address of the network data packet.
Specify the port number of the destination device
Destination Port here. 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 “Routing enabled entirely” 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-8207 PFC200 CS 2ETH RS 3G
7.8.1.11 “General Firewall Configuration” Page
7.8.1.11.1 “Global Firewall Parameters” Group
Table 61: WBM “General Firewall Configuration” Page – “Global Firewall Parameters” 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
Firewall enabled entirely effect. The configuration of the other parameters is
possible nevertheless so that you can set the
firewall parameters correctly before you enable the
firewall.
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-8207 PFC200 CS 2ETH RS 3G
7.8.1.11.2 “Firewall Parameters Interface xxx” Group
These settings in this group refer to the configuration of the firewall at IP level.
Table 62: WBM “General Firewall Configuration” Page – “Firewall Parameter Interface Xn” Group
Firewall enabled for Enable or disable the firewall for the specific
Interface interface.
Enable or disable the “ICMP echo” protection for the
ICMP echo protection
respective interface.
You can specify the maximum number of “ICMP
ICMP echo limit per second
echo bursts” per second.
ICMP burst limit
echo bursts” per second.
(0 = disabled)
“0” = “Disabled”
Telnet
FTP
FTPS
HTTP
HTTPS
I/O-CHECK Enable or disable the
PLC Runtime firewall for the respective
service.
PLC WebVisu –
Service enabled The services themselves
direct link (port 8080)
must be enabled or
SSH disabled separately on the
TFTP “Ports and Services” page.
BootP/DHCP
DNS
MODBUS TCP
MODBUS UDP
SNMP
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.12 “Configuration of MAC Address Filter” Page
You set the firewall configuration at ETHERNET level on this page.
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 activated 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!
7.8.1.12.1 “Global MAC Address Filter State” Group
Table 63: WBM “Configuration of MAC Address Filter” Page – “Global MAC Address Filter State”
Group
Enable or disable the global MAC address filter
Filter enabled
here.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.12.2 “MAC Address Filter State Xn” Group
Table 64: WBM “Configuration of MAC Address Filter” Page – “MAC Address Filter State Xn” Group
Enable or disable here the MAC address filter for the
Filter enabled
specific interface.
7.8.1.12.3 “MAC Address Filter Whitelist” Group
Table 65: 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.
Enable or disable the filter for the relevant list entry
Filter enabled
here.
…
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 here.
Enable or disable the filter for the new list entry
Filter enabled
here.
Click the appropriate [Delete] button to remove an existing list entry. The change
is effective immediately.
Click [Add] to accept a new list entry. You can enter 10 filters. The change is
effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.13 “Configuration of User Filter” Page
7.8.1.13.1 “User Filter” Group
Table 66: WBM “Configuration of User Filter” Page – “User Filter” Group
Count The number of configured user filters is displayed.
7.8.1.13.2 “User Filter n” Group
Table 67: WBM “Configuration of User Filter” Page – “User Filter n” Group
The source IP address for the respective filter entry
Source IP address
is displayed.
This displays the source network for the
Source netmask
corresponding filter entry.
The source port number for the respective filter entry
Source port
is displayed.
The destination IP address for the respective filter
Destination IP address
entry is displayed.
The destination network mask for the respective
Destination subnet mask
filter entry is displayed.
The designation port number for the respective filter
Destination port
entry is displayed.
The permitted protocols for the respective filter is
Protocol
displayed.
The permitted interfaces for the respective filter are
Input interface
displayed.
Hier wird angezeigt, ob der Netzwerkteilnehmer
Policy durch den Filter zugelassen oder ausgeschlossen
ist.
Click the appropriate [Delete] button to remove a configured filter. The change is
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.13.3 “Add New User Filter” Group

You only have to enter values in the fields that are to be set for the filter. At least
one value must be entered, all other fields can remain empty.
Table 68: WBM “Configuration of User Filter” Page – “Add New User Filter” Group
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.
Enter here the source IP address for the new filter
Source IP address
entry.
Enter here the source network mask for the new
Source netmask
filter entry.
Enter here the source port address for the new filter
Source port
entry.
Enter here the destination IP address for the new
Destination IP address
filter entry.
Enter here the destination network mask for the new
Destination subnet mask
filter entry.
Enter the destination port number for the new filter
Destination port
entry.
Enter here the permitted protocols for the new filter.
Protocol TCP The TCP service is permitted.
UDP The UDP service is permitted.
Enter here the permitted interfaces for the new filter.
X1 The X1 interface is permitted.
Input interface
X2 The X2 interface is permitted.
VPN The VPN interface is permitted.
To accept the new filter click [Add]. The change is effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.14 “Configuration of Time and Date” Page
The settings for date and time are shown on the “Configuration of Time and Date”
page.
7.8.1.14.1 “Date on Device” Group
Table 69: WBM “Configuration of Time and Date” Page – “Date on Device” Group
Local Set date.
Click [Change date] to apply change. The change is effective immediately.
7.8.1.14.2 “Time on Device” Group
Table 70: WBM “Configuration of Time and Date” Page – “Time on Device” Group
Local Set local time.
UTC Set GMT time.
12 h format For switching between 12-hour and 24-hour time
display
Click [Change time] to apply change to the time. The change is effective
immediately.
Click [Change format] to apply change to the time format. The change is
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.14.3 “Time Zone” Group
You can specify the appropriate time zone for your location in this group.
The total number of possible time zones is over 500. A complete listing would
exceed the scope of this documentation.
Due to the large number of time zones, the selection is limited via the “Time
Zone” parameter.
You can select further time zones with the “TZ String” parameter.
Table 71: WBM “Configuration of Time and Date” Page – “Time Zone” Group
Specify the appropriate time zone for your location.
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
“Pacific Standard Time,” Los Angeles,
Time zone 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”
* Default setting
Click [Change] to apply time zone change. The change is effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.14.4 “TZ String” Group
In this group you can enter a time zone that is not contained in the “Time Zone”
selection.
If the controller can associate the TZ string entered with a known time zone that
had been missing from the “Time Zone” selection, this time zone is then also
added to the “Time Zone” list.
You can find information on time zones and the corresponding “TZ strings” on the
Internet.
For example, to indicate the pure UTC time, enter the TZ string “UTC0.”
If no unique association is possible, the text “Unknown” is displayed for the “Time
Zone” selection.
Table 72: WBM “Configuration of Time and Date” Page – “TZ String” Group
TZ string You can enter the name of the time zone or the
country and city here.
Click [Change] to apply the change. The change is effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.15 “Configuration of the Users for the Web-based Management” Page
The settings for user administration are shown on this page.
7.8.1.15.1 “Change Password for Selected User” Group
Change passwords
Table 73: WBM “Configuration of the users for the Web-based Management” Page – “Change
Password for Selected User” Group
Select the user (“user” or “admin”) for new password
Select User
assignment.
Enter the new password for the user selected under
“Select User”.
The following ASCII characters for passwords are
New Password
valid: a … z, A … Z, 0 … 9 and spaces. These
special characters are also valid:
]!"#$%&'()*+,./:;<=>?@[\^_`{|}~-
Confirm password Enter the new password again for confirmation.
Click [Change Password] to apply change. The change is effective immediately.
Observe the valid characters for WBM passwords!

If WBM passwords with invalid characters are set outside the WBM system (e.g.
via CBM), then accessing the WBM pages is no longer possible!
Observe access rights

Authorized WBM users only have access to the Web pages. User administration
for controller applications is configured separately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.16 “Create Bootable Image” Page
You can create a bootable image on the “Create Bootable Image” page.
7.8.1.16.1 "Create Bootable Image from Active Partition (<Active Partition>"

Group
The active partition that boot-up was performed from is displayed in brackets in
the heading.
Table 74: WBM “Create Bootable Image” page – “Create bootable image from active partition” Group
The possible destination partition that an image will
be saved to is displayed. Depending on which
medium has been booted, the following destination
is available for selection after boot-up for the image
Destination to be generated:
System was booted Target partition for
from “bootable image”
Memory Card  Internal Flash
Internal memory  Memory Card
Define the size of the image on the memory card.
This field is only visible when “Memory Card” is set
as the target.
Size of created image Reduced to The storage space of the copied
content image is kept as small as possible.
The image is created so that the
Full card size
entire memory card is filled.
Once the destination has been determined and output, it is then checked and the
results of this check are displayed below the settings:
- 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
definitively 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.
</dg_
Manual
750-8207 PFC200 CS 2ETH RS 3G
Remove the memory card write protection!

Because write access to the memory card is possible during the boot process,
the memory card cannot be write protected when creating the image and during
operation.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.17 “Configuration of Serial Interface RS232” Page
The settings for the serial interface are shown on the “Configuration of Serial
Interface RS232” page.
7.8.1.17.1 “Serial Interface Assigned to” Group
The application that the serial interface is currently assigned to is displayed.
7.8.1.17.2 “Assign Owner of Serial Interface (Active after Next Controller

Reboot)” Group
You can specify the application that the serial interface is assigned to after the
next controller reboot.
Table 75: 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 particular application and is available, so that
applications, libraries,
the CODESYS program, for example, can access it
CODESYS)
via 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 after
restarting the controller. For this purpose, use the WBM reboot function. Do not
shut down the controller too early!
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.18 “Configuration of Service Interface” Page
The settings for the service interface are shown on the “Configuration of the
Service Interface” page.
7.8.1.18.1 “Service Interface assigned to” Group
The application that the service interface is currently assigned to is displayed.
7.8.1.18.2 “Assign Owner of Service Interface (enabled after next controller

reboot)” Group
You can specify the application to which the service interface is assigned after
the next controller reboot.
Table 76: WBM “Configuration of Serial Interface RS-232” 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 [Change Owner] to apply the change. The changes only take effect after
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.19 “Reboot Controller” Page
The settings for the system reboot are shown on the “Reboot Controller” page.
7.8.1.19.1 “Reboot Controller” Group
Click the [Reboot] button to reboot the system.
Account for boot-up time!

The boot process takes time. You cannot access the controller while this is
occurring.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.20 “Firmware Backup” Page
You can find the controller data backup settings on the “Firmware Backup” page.
Table 77: “Firmware-Backup” WBM Page

You can select the data to be backed up here.
To do this, select the corresponding entries.
All data is backed up.
This selection is only enabled if the
All
memory card is selected as the
target.
Packages
PLC runtime The PLC runtime project is backed
project up.
The controller settings are backed
Settings
up.
The controller operating system is
System
backed up.
Select the storage location for the backup here.
The data is written to the memory
card.
Memory card This selection only appears if a
Destination memory card without system data is
inserted.
The data are stored on the file
Network system and can then be
downloaded to the PC.
Activate “auto update To start the automatic update when a memory card
feature” with system data is inserted, select this button.

identical.
beforehand.
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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
To begin the backup procedure, click the [Submit] button.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.21 “Firmware Restore” Page
The settings for restoring the controller data are shown on the “Firmware
Restore” page.
Table 78: “Firmware Restore” WBM Page

Select the data source for the restore here.
The data is read from the memory
card.
Memory card This selection is only enabled if a
Source
memory card without system data is
inserted.
The data is uploaded from the PC
Network
and restored.
Select the data to be restored here.
To do this, select the corresponding entries.
All data is restored.
This selection only appears if the
All
memory card is selected as the data
source.
Packages
PLC runtime
The PLC runtime project is restored.
project
Settings The controller settings are restored.
The controller operating system is
System loaded. The current controller
settings are retained.
Enter the name of the backup file for the CODESYS
project here.
CODESYS backup file
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 backup file
Enter the name of the backup file for the system
data here.
System backup file
Manual
750-8207 PFC200 CS 2ETH RS 3G

identical.
beforehand.
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.
Click the [Browse] button to select the files in Explorer. The buttons only appear
if the network is selected as the data source.
To start the restore procedure, click the [Submit] button.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.22 “System Partition” Page
The settings for specifying the partition that the system will be started from are
shown on the “System Partition” page.
7.8.1.22.1 “Current Active Partition” Group
The partition currently in use is displayed here.
7.8.1.22.2 “Set Inactive Partition Active” Group
Click [Activate Partition] to start the system from a different partition at the next
controller reboot.
Ensure bootable partition!

A functional firmware backup must be present in the boot partition!
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.23 “Mass Storage” Page
A group containing information about the storage volume is displayed for each
storage volume that is found, along with an additional group for formatting (when
this is possible).
The group title contains the designation for the storage volume (“SD card” or
“Internal Flash”) and, if this storage volume is also the active partition, the text
“Active Partition”.
7.8.1.23.1 “<Device Name>” Group(s)
Table 79: WBM “Mass Storage” Page – “<Device Name>” Group

The name of the storage volume in the operating
Device
system file system is displayed here.
Volume name The name of the storage volume is displayed here.
7.8.1.23.2 “<Device Name> - FAT Format” Group(s)
Table 80: WBM “Mass Storage” Page – “<Device Name>” Group

Specify the name for the storage volume when
Volume Name
formatted.
Data are deleted!

Any data stored in the storage volume is deleted during formatting!
To format the specified storage volume, click [Start Formatting].
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.24 “Software Uploads” Page
The settings for a device update are shown on the “Software Uploads” page.
7.8.1.24.1 “Upload New Software” Group
Table 81: WBM “Software Uploads” Page – “Upload New Software” Group
You can select fieldbus software, program licenses
Software Files and update scripts, for example, for transfer from a
PC to the controller.
To select a file on the PC, click the [Browse] button.
To transfer the selected file to the controller, click [Start Upload] button.
7.8.1.24.2 “Activate New Software” Group
Table 82: WBM “Software Uploads” Page – “Activate New Software” Group
This shows the file name of the transferred software
package. If no new uploaded software package is
Software File
present on the controller, the message “No upload
file exists” is displayed.
Select here the action required.
Activate The transferred software package is
activated.
Force Installs a transferred software package
(Manual that cannot be activated with “Activate.”
reboot Required for activating a controller
Action
afterward reboot.
s needed) The software package is activated on
reboot.
Discard The transferred software package is
(delete deleted again by the controller.
upload)
To perform the action, click the [Submit] button. The process starts immediately.
The file with the software package is deleted again after the installation is
completed or when the controller is restarted.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.25 “Configuration of Network Services” Page
The settings for various services are shown on the “Configuration of Network
Services” page.
Besides enabling/disabling the individual services, you can also limit the services
for each particular interface via the firewall on the “General Firewall
Configuration” page.
7.8.1.25.1 “Telnet” Group
Table 83: WBM “Configuration of Network Services” Page – “Telnet” Group

Service active Enable/disable the Telnet service here.
Click the [Submit] button to apply the changes. The change takes effect
immediately.
7.8.1.25.2 “FTP” Group
Table 84: WBM “Configuration of Network Services” Page – “FTP” Group

Service active Enable/disable the FTP service here.
immediately.
7.8.1.25.3 “FTPS” Group
Table 85: WBM “Configuration of Network Services” Page – “FTPS” Group

Service active Enable/disable the FTPS service here.
immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.25.4 “HTTP” Group
Table 86: WBM “Configuration of Network Services” Page – “HTTP” Group

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

If the HTTP service is disabled, the connection to the controller may be
interrupted. Then open the WBM page again.
7.8.1.25.5 “HTTPS” Group
Table 87: WBM “Configuration of Network Services” Page – “HTTPS” Group

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

If the HTTPS service is disabled, the connection to the controller may be
interrupted. Then open the WBM page again.
7.8.1.25.6 “WAGO-I/O-CHECK” Group
Table 88: WBM “Configuration of Network Services” Page – “I/O-CHECK“ Group

Service active Enable/disable the WAGO-I/O-CHECK service here.
immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.25.7 “OPC UA” Group
Table 89: WBM “Configuration of Network Services” Page – “OPC UA” Group
Service active Enable/disable the OPC UA service here.
Click the [Submit] button to apply the changes. 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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.26 “Configuration of NTP Client” Page
The settings for the NTP service are shown on the “Configuration of NTP Client”
page.
7.8.1.26.1 “NTP Client Configuration” Group
Table 90: WBM “Configuration of NTP Client” Page – “NTP Client Configuration” Group
Service enabled Enable/disabled time update.
This displays whether time data was accessible and
updated via NTP.
This field is only displayed with the NTP service
Service Result enabled.
Time server not The time data was not yet
available until now updated.
Time server available The time data was updated.
Enter here the IP addresses of up to 4 time servers.
Time server No. 1 is requested first of all. If no data
Time Server n
is accessible via this server, time server No. 2 is
requested etc.
Update interval (sec) Specify here the update interval of the time server.
The NTP servers assigned if necessary by DHCP
Additionally used
(or BootP) are displayed. If no NTP server has been
(assigned by DHCP)
assigned by DHCP (or BootP), “none” is displayed.
Click the [Submit] button to apply the changes. The changes are effective
immediately.
7.8.1.26.2 “NTP Single Request” Group
To update the time immediately, irrespective of the update interval, click [Update
Time Now].
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.27 “Configuration of PLC Runtime Services” Page
The settings for various services of the activated runtime system are shown on
the “Configuration of PLC Runtime Services” page.
7.8.1.27.1 “General Configuration” Group
Table 91: WBM “Configuration of PLC Runtime Services” Page – “General Configuration” Group
Port Authentication
Specify the new password for port authentication.
Password
Confirm Password Enter the new password again for confirmation.
7.8.1.27.2 “CODESYS 2” Group
Table 92: WBM “Configuration of CODESYS Services” Page – “CODESYS 2 Web Server” Group
This displays the status (enabled/disabled) of the
CODESYS 2 State
CODESYS 2 runtime system.
Enable or disable the CODESYS 2 web server for
Web server enabled
the CODESYS web visualization here.
Enable or disable the communication between the
Communication enabled CODESYS 2 runtime system and the CODESYS 2
programming system.
Enter here the port number for communication with
Communication Port
the CODESYS 2 programming system. 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 2 IDE.
7.8.1.27.3 “e!RUNTIME” Group
Table 93: WBM “Configuration of CODESYS Services” Page – “e!RUNTIME Web Server” Group
This displays the status of the e!RUNTIME system
e!RUNTIME State
(enabled/disabled).
Enable or disable the e!WEBSERVER for the
Web server enabled
e!RUNTIME web visualization here.
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.”
Manual
750-8207 PFC200 CS 2ETH RS 3G
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.28 “SSH Server Settings” Page
The settings for the SSH service are shown on the “SSH Server Settings” page.
7.8.1.28.1 “SSH Server” Group
Table 94: WBM “SSH Server Settings” Page – “SSH Server” Group
Service active You can enable/disable the SSH server here.
Port Number Specify the port number here.
Allow root login You can enable or inhibit root access.
Activate or deactivate the password query function
Allow password login
here.
Click on [Submit] to accept the changes. The changes will be effective

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.29 “TFTP Server” Page
The settings for the TFTP service are shown on the “TFTP Server” page.
7.8.1.29.1 “TFTP Server” Group
Table 95: WBM “TFTP Server” Page – “TFTP Server” Group

Service active Activate or deactivate the TFTP server.
Specify here the path for downloading the server
Download directory
directory.

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.30 “DHCP Configuration” Page
The settings for the DHCP service are shown on the “DHCP Configuration” page.
7.8.1.30.1 “DHCP Configuration Xn” Group
Table 96: WBM “DHCP Configuration” – “DHCP Configuration Xn” Group

Enable or disable the DHCP service for the interface
Service active
Xn.
IP Range Enter here a range of available IP addresses.
Specify the lease time here in seconds. 120
Lease time (sec)
seconds are entered by default.
This displays the static assignments of MAC IDs to
Static hosts/
IP addresses. If no assignment was defined, “No
Static host n
static hosts configured” is displayed.
Enter here a new static assignment, e.g.,
“01:02:03:04:05:06=192.168.1.20” or
New static host
“hostname=192.168.1.20.”
You can enter 10 assignments.

immediately.
Click on [Add] to accept a new assignment. The change is effective immediately.
Click on [Delete] to delete an existing assignment. The change is effective

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.31 “Configuration of DNS Service” Page
The settings for the DNS service are shown on the “Configuration of DNS
Service” page.
7.8.1.31.1 “DNS Service” Group
Table 97: WBM “Configuration of DNS Service” Page – “DNS Service” Group
You can enable/disable the DNS server service
Service active
here.
Select here the operating mode of the DNS server:
Requests are buffered to optimize
Mode Proxy
throughput.
Relay All requests are routed directly.
This displays the static assignments of IP addresses
Static hosts to names. If no assignment was defined, “No static
hosts configured” is displayed.
Enter here a new static assignment, e.g.,
New static host “192.168.1.20:hostname.”

immediately.
Click on [Add] to accept a new assignment. The change is effective immediately.
Click on [Delete] to delete an existing assignment. The change is effective

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.32 “MODBUS Services Configuration” Page
The settings for various MODBUS services are shown on the “MODBUS Services
Configuration” page. The groups are only visible if the e!RUNTIME system is
enabled. Otherwise an information text is displayed.
7.8.1.32.1 “MODBUS TCP” Group
Table 98: WBM “MODBUS Services Configuration” Page – “MODBUS TCP” Group
Service active Disable or enable the MODBUS/TCP service here.
Click the [Submit] button to apply the changes. The change is effective
immediately.
7.8.1.32.2 “MODBUS UDP” Group
Table 99: WBM “MODBUS Configuration Services” Page – “MODBUS UDP” Group
Service active Disable/enable the MODBUS-UDP service here.
Click the [Submit] button to apply the changes. The change is effective
immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.33 “Configuration of Cloud Connectivity” Page
On the page “Configuration of Cloud Connectivity” you can find the settings and
information for cloud access.
Observe the additional documentation!

You can find a detailed description of the “Cloud Connectivity” software package
with a PFC100 and information on PLC programming in Application Note
A500920 in the Downloads area at www.wago.com!
7.8.1.33.1 “Software Version” Group
Table 100: WBM “Configuration of Cloud Connectivity” Page – “Software Version” Group
Version The cloud plug-in version is displayed.
7.8.1.33.2 “Status” Group
Table 101: WBM “Configuration of Cloud Connectivity” Page – “Status” Group

The status of the cloud connectivity application is
Operation
displayed here.
This shows how many data collections have been
Data collections registered on the IEC application side for transfer to
the cloud.
The status of the connection to the cloud service is
Connection
shown here.
This shows the current heartbeat interval setting in
Heartbeat
seconds.
Telemetry data This indicates whether transfer of data is enabled or
transmission disabled.
This shows the fill level of the memory cache for
Cache fill level
outgoing messages as a percentage.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.33.3 “Settings” Group
Table 102: WBM “Configuration of Cloud Connectivity” Page – “Settings” Group

Cloud platform Select the cloud platform here.
Enter the host name or IP address for the selected
Host name
cloud platform here.
Enter the device ID for the selected cloud platform
Device ID
here.
Enter the activation key for the selected cloud
platform here.
Activation Key
This input field is only visible if you have selected
“WAGO Cloud” or “Azure” as the cloud platform.
Here you can specify whether TLS encryption
should be used for the connection to the cloud
platform.
This check box is only visible if you have selected
“MTTQ AnyCloud,” “IBM Bluemix” or “Amazon Web
TLS
Services (AWS)” as the cloud platform.
This check box is only enabled if you have selected
“MTTQ AnyCloud” or “IBM Bluemix” as the cloud
platform. Amazon Web Services (AWS) always uses
TLS.
Enter the port here to which a connection is to be
established.
Typical values are 8883 for encrypted connections
and 1883 for unencrypted connections.
Port
This input field is only enabled if you have selected
platform.
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
value is the CA certificate /etc/ssl/certs/ca-
CA file certificates.crt, which is already installed on the
PFC.
Enter the user name for cloud service authentication
here.
User This input field is only visible if you have selected
platform.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Enter the password for cloud service authentication
here.
Password This input field is only visible if you have selected
platform.
format that is used for cloud service authentication.
Certification file This input field is only visible if you have selected
“MTTQ AnyCloud” or “Amazon Web Services
(AWS)” as the cloud platform.
format that contains the private key for cloud service
authentication.
Key file
“MTTQ AnyCloud” or “Amazon Web Services
(AWS)” as the cloud platform.
Specify here in which memory the cache for the data
telegrams should be created.
This selection field is only enabled if a correctly
Cache mode
formatted SD card is inserted.
(You can find more information in Application Note
A500920.)
Specify here whether a device info message should
be generated that informs the cloud service of the
basic configuration of the PFC.
Device info A500920.)
“Azure,” “MTTQ AnyCloud,” “IBM Bluemix” or
“Amazon Web Services (AWS)” as the cloud
platform.
Specify here whether device state messages should
be generated that inform the cloud service about
changes in the mode selector switch and the LEDs.
Device status A500920.)
“Azure,” “MTTQ AnyCloud,” “IBM Bluemix” or
“Amazon Web Services (AWS)” as the cloud
platform.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Specify here whether the integrated standard
commands should be supported.
(You can find the list of standard commands in
Application Note A500920.)
Standard commands If the check box is disabled, only the commands
defined in the IEC program are supported.
“Azure,” “MTTQ AnyCloud” or “Amazon Web
Click the [Submit] button to apply a change.
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!
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.34 “Configuration of General SNMP Parameters” Page
The general settings for SNMP are given on the “Configuration of General SNMP
Parameters” page.
7.8.1.34.1 “General SNMP Configuration” Group
Table 103: 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).
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-8207 PFC200 CS 2ETH RS 3G
7.8.1.35 “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.
7.8.1.35.1 “SNMP v1/v2c Manager Configuration” Group
Table 104: 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 activated. The local community name is deleted
when the protocol is deactivated.
Specify here 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.”
Click [Change] to apply 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!
7.8.1.35.2 “Actually Configured Trap Receivers” Group(s)
Table 105: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Actually Configured Trap
Receivers” Group
Count This displays number of configured trap receivers.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.35.3 “Trap Receiver n” Group(s)
A dedicated group with the following information is displayed for each trap
receiver:
Table 106: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Trap Receiver n” Group(s)
The IP address for the trap receiver (management
IP Address
station) is displayed here.
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).
Click [Delete] to delete the trap receiver. The changes only take effect after
7.8.1.35.4 “Add New Trap Receiver” Group
You can enter 10 trap receivers.
Table 107: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Add New Trap Receiver”
Group
Specify the IP address for the new trap receiver
IP Address
(management station) here.
Specify here 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 [Add] to add a new trap receiver. The changes only take effect after
Manual
750-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.36 “Configuration of SNMP v3 Users” Page
The general settings for SNMP v3 are shown on the “Configuration of SNMP v3
Users” page.
7.8.1.36.1 “Actually Configured v3 Users” Group(s)
Table 108: WBM “Configuration of SNMP v3” Page – “Actually Configured v3 Users” Group
Count The number of configured v3 users is displayed.
7.8.1.36.2 “v3 User n” Group(s)
A group with the following information is displayed for each user:
Table 109: WBM “Configuration of SNMP v3 Users” Page – “v3 User n” Group(s)
Security Authentication
The user name is displayed.
Name
The authentication type for the SNMP v3 packets is
displayed here.
Authentication Type Possible values:

- Use no authentication (“None”)
- Message Digest 5 (“MD5”)
- Secure Hash Algorithm (“SHA”)
Authentication Key (min.
The authentication key is displayed.
eight char.)
The encryption algorithm for the SNMP message is
displayed here.
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 (min. eight
displayed here. If nothing is displayed here, the
char.)
“authentication key” is automatically used.
The IP address of a trap receiver for v3 traps is
Notification Receiver IP displayed here. If no v3 traps are to be sent for this
user, this field remains blank.
Click [Delete] to delete the user. 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-8207 PFC200 CS 2ETH RS 3G
7.8.1.36.3 “Add New v3 User” Group
You can enter 10 users.
Table 110: WBM “Configuration of SNMP v3 Users” Page – “Add New v3 User” Group
Enter the user name here. This name must be
unique; a pre-existing user name is not accepted
Security Authentication
when entered here. The security authentication
Name
name can have a maximum 32 characters, without
any spaces.
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 here. This
Authentication Key (min.
authentication key must have between eight and 32
eight char.)
characters, without any spaces.
Specify the encryption algorithm for the SNMP
message here.
Privacy Possible values:

- No encryption (“None”)
- Data Encryption Standard (“DES”)
- Advanced Encryption Standard (“AES”)
Enter the key for encryption of the SNMP message
here. If nothing is specified here, the “authentication
Privacy Key (min. eight
key” is automatically used. The privacy key must
char.)
have between eight and 32 characters, without any
spaces.
Specify an IP address for a trap receiver for v3 traps
Notification Receiver IP here. If no v3 traps are to be sent for this user, this
field remains blank.
Click [Add] to add a new user. 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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.8.1.37 “Diagnostic Information” Page
The settings for displaying diagnostic messages are shown on the “Diagnostic
Information” page.
Table 111: WBM “Diagnostic Information” Page

Read all notifications Activate display of all messages.
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 check box to enable cyclic refresh.
Enter the cycle time in seconds in which a cyclic
Automatic refresh cycle
refresh is performed. The label of the button
(sec)
(“Refresh”/“Start“/“Stop”) changes depending on
status.
To refresh the display or to enable cyclic refresh, click the [Refresh] button. This
button is only visible if the cyclic refresh is not enabled or stopped.
To enable cyclic refresh, click the [Start] button. The button is only visible if cyclic
refresh is enabled and has not yet started.
To stop cyclic refresh again, click the [Stop] button. The button is only visible if
cyclic refresh is enabled.
The cyclical update is performed for as long as the “Diagnostic” page is opened.
If you change the WBM page, the update is stopped until you call up the
“Diagnostic” Page again.
The messages are displayed below the settings.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.38 “Configuration of internal 3G Modem” Page
The modem settings are available on the “Configuration of internal 3G Modem”

page.
7.8.1.38.1 “SIM Authentication” Group
Table 112: WBM “Configuration of internal 3G Modem” Page – “SIM Authentication” Group
The status of the SIM authentication is displayed.
Ready Authentication was successful.
The PIN must be entered.
PIN requested The number of remaining
State
attempts is displayed.
The PIN was not entered
PUK requested correctly, the PUK must be
specified along with a new PIN.
Enter the PIN.
PIN
The field is only displayed if PIN entry is required.
Enter the PUK.
PUK
The field is only displayed if PUK try is required.
To apply the entries, click the [Submit] button. The changes will be effective
immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.38.2 “Mobile Network Configuration” Group
Table 113: WBM “Configuration of internal 3G Modem” Page – “Mobile Network Configuration” Group
State The network status is displayed.
Signal Quality (%) The current signal quality is displayed.
The provider and network type currently in use are
Operator
displayed.
Select the mode for selecting the provider used:
The network is selected by the
Automatic modem itself based on the SIM
card settings.
Automatic – Like “Automatic”, but the UMTS
UMTS preferred network is preferred.
Automatic – Like “Automatic”, but the GSM
GSM preferred network is preferred.
Automatic – Like “Automatic”, but restricted to
UMTS only the UMTS network.*
Selection Mode
Automatic – Like “Automatic”, but restricted to
GSM only the GSM network.*
Manual network selection from

the Provider selection list;
if you set the “Manual” mode, the
Manual
provider list is then refreshed.
This may take some time (see
section “‘Provider List’ Group”).
Select the provider.

The field is only visible if Selection Mode is set to
“Manual”.
Provider The selection list contains all providers from the
provider list that are actually available.
The selection list is only available if the provider list
has been refreshed.
* However, the restriction applies only when more than one possible network is
available, e.g., if “Automatic UMTS only” is selected, but only a GSM network is
available from the provider, then the modem still logs into the GSM network.

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.38.3 “Provider List” Group
Table 114: WBM “Configuration of internal 3G Modem” Page – “Provider List” Group
<Provider> | <Network> All available providers with the respective network,
<ID>, <Status> its ID and the current status are displayed.
Refreshing the provider list may take some time (approx. 1 minute), during which
the WBM waits for the modem response. The process is canceled after 2 minutes
or immediately if the modem executes another, non-interruptible action.
The list is therefore refreshed only on request, either by clicking the [Refresh]
button or setting the Selection Mode to “Manual”.
The selection list for the provider (“Mobile Network Configuration” Group) can
only be filled in when the provider list has been refreshed.
In normal operation, the provider list changes only rarely, i.e., continuous
refreshing is not required.
Click [Refresh] to refresh the list.
7.8.1.38.4 “Network Package Service” Group
Table 115: WBM “Configuration of internal 3G Modem” Page – “Network Package Service” Group
The registry state of the “Network Package Service”
State
is displayed.
Enter the APN access point (Access Point Name) of
APN
the SIM card provider.
Enter the user name for the access point of the SIM
User
card provider.
Enter the password for the access point of the SIM
Password
card provider.
Select the authentication type:
None No authentication
Password Authentication
PAP
Protocol
Authentication Type
Challenge Handshake
CHAP
Authentication Protocol
When possible, the secure CHAP
PAP or CHAP
is used, otherwise PAP.

immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.38.5 “Upload and activate new Modem Software” Group
Table 116: WBM “Configuration of internal 3G Modem” Page – “Upload and activate new Modem
Software” Group
Currently used The current modem firmware version is displayed.
New Software Enter the firmware version to be installed.
To select a firmware file in Explorer, click the [Browse] button.
To install and enable the firmware, click the [Start Upload] button. The changes
will be effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.39 “Configuration of OpenVPN and IPsec” Page
The general settings for SNMP v1/v2c are shown on the “Configuration of SNMP
v1/v2c Parameters” page.
7.8.1.39.1 “OpenVPN” Group
Table 117: WBM “Configuration of OpenVPN and IPsec” 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 controller or vice versa.
To apply a status change, click the [Submit] button.
To select a file on the controller or PC, click the [Browse] button.
To transfer the selected file from the PC to the controller, click [Start Upload]
button.
To transfer the selected file from the controller to the PC, click [Start Download]
button.
The changes only take effect after restarting the controller. For this purpose, use
7.8.1.39.2 “IPsec” Group
Table 118: WBM “Configuration of OpenVPN and IPsec” 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.config
from PC to controller or vice versa.
Select an IPsec configuration file to be transferred
ipsec.secrets
from PC to controller.
To apply a status change, click the [Submit] button.
To select a file on the controller or PC, click the [Browse] button.
To transfer the selected file to the controller, click [Start Upload] button.
Manual
750-8207 PFC200 CS 2ETH RS 3G
To transfer the selected file from the controller to the PC, click [Start Download]
button.
The changes only take effect after restarting the controller. For this purpose, use
7.8.1.39.3 “Certificate Upload” Group
Table 119: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate Upload” Group
Select an certificate for transfer from a PC to the
New Certificate
controller.
New Private Key Select a key for transfer from a PC to the controller.
To select a file on the PC, click the [Browse] button.
To transfer the selected file to the controller, click [Start Upload] button. The
changes will be effective immediately.
The certificates are saved in the directory “/etc/certificates/” and the keys in the
directory “/etc/certificates/keys/”.
7.8.1.39.4 “Certificate List” Group
Table 120: 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.
Click [Delete] to delete an entry. The changes will be effective immediately.
7.8.1.39.5 “Private Key List” Group
Table 121: WBM “Configuration of OpenVPN and IPsec” Page – “Private Key List” Group
The loaded keys are displayed. If no keys has been
<key name>
loaded. “No keys existing” is displayed.
Click [Delete] to delete an entry. The changes will be effective immediately.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.40 “Security Settings” Page
The network security settings are found on the “Security Settings” page.
7.8.1.40.1 “TLS Configuration” Group
Table 122: “Security Settings” WBM Page – “TLS Configuration” Group

Here 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 longer considered secure.
TLS configuration
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 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-8207 PFC200 CS 2ETH RS 3G
7.8.1.41 “Open Source Licenses” Page
The licence conditions for the open source software used for the controller are
listed in alphabetical order on the “Open Source Licenses” page.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.1.42 “WAGO Licenses” Page
The licence conditions for the WAGO software used in the controller are listed on
the “WAGO Licenses” page.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2 Configuration using a Terminal Program (CBM)

You can use the Console-Based Management Tool (CBM) to configure the
controller via the ETHERNET interface and SSH, as well as the RS-232 interface
and Linux® console.
To establish a connection via the serial interface, set the baud rate to 115200
baud in the terminal program. The settings for data bits, stop bits and parity do
not need to be adjusted.
To launch the CBM, log in to the Linux® console and enter the command "cbm"
(case sensitive).
Figure 42: CBM main menu (example)
7.8.2.1 CBM Menu Structure Overview
Table 123: 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
Menu Hierarchy
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
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
Manual
750-8207 PFC200 CS 2ETH RS 3G
Menu Hierarchy
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-8207 PFC200 CS 2ETH RS 3G
7.8.2.2 “Information” Menu
This menu contains other submenus with information on the controller and
network.
Table 124: “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].
7.8.2.2.1 “Information” > “Controller Details” Submenu
In this submenu, the controller properties are displayed.
Table 125: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.2.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 126: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.3 “PLC Runtime” Menu
This menu contains other submenus with information and settings for the runtime
system.
Table 127: “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

7.8.2.3.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 2 is set as the runtime system.
Table 128: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.3.2 “Information” > “Runtime Version” Submenu
In this submenu, the runtime version is displayed.
Table 129: “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.
7.8.2.3.3 “Information” > “Webserver Version” Submenu
In this submenu, the Webserver version is displayed.

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

Table 131: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.3.5 “Information” > “Number of Tasks” Submenu
In this submenu, the number of tasks in the PLC program are displayed.
Table 132: “PLC Runtime” > “Information” > “Number of Tasks” Submenu
Number of Tasks The number of tasks in the PLC program is shown.
7.8.2.3.6 “Information” > “Project Details” Submenu
In this submenu, project information from the PLC program is displayed.

The submenu only appears when CODESYS 2 is enabled as the runtime system
and the program is executed.
Table 133: “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
7.8.2.3.7 “Information” > “Tasks” Submenu
In this submenu, tasks from the PLC program are displayed. An entry is
generated for each task.
Table 134: “PLC Runtime” > “Information” > “Tasks” Submenu

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

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.3.8 “Tasks” > “Task n” Submenu
In this submenu, information on the selected task is displayed.

Table 135: “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
7.8.2.3.9 “PLC Runtime” > “General Configuration” Submenu
This submenu contains other submenus with general settings for the runtime
system.
Table 136: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.3.10 “General Configuration” > “PLC Runtime Version” Submenu
In this submenu, select which PLC runtime system is enabled.
Table 137: “PLC Runtime” > “General Configuration” > “PLC Runtime Version” Submenu
1. None No runtime system is enabled.
2. CODESYS 2 The CODESYS 2 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!

7.8.2.3.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 138: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.3.12 “PLC Runtime” > “WebVisu” Submenu
This submenu contains information and settings for the Web visualization.
Table 139: “PLC Runtime” > “WebVisu” Submenu

Menu Item Submenu Item / Explanation
1. CODESYS 2 Webserver The status of the CODESYS 2 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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4 “Networking” Menu
This menu contains other submenus with settings for the network configuration.
Table 140: “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

7.8.2.4.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 141: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.2 “Host/Domain Name” > “Hostname” Submenu
In this submenu, you can set the hostname of the controller.
Table 142: “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.
7.8.2.4.3 “Host/Domain Name” > “Domain Name” Submenu
In this submenu, you can set the domain name of the controller.
Table 143: “Networking” > “Host/Domain Name” > “Domain Name” Submenu
Enter the domain name.
Enter new Domain Name
The default entry is “localdomain.lan”.

7.8.2.4.4 “Networking” > “TCP/IP” Submenu
This submenu contains other submenus with the TCP/IP settings for the
ETHERNET interfaces.
Table 144: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.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 145: “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

7.8.2.4.6 “IP Address” > “Xn“ Submenu
This submenu contains the settings for the selected interface.
Table 146: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.7 “TCP/IP” > “Default Gateway” Submenu
This submenu contains other submenus with settings for the default gateway.
Table 147: “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.

7.8.2.4.8 “Default Gateway” > “Default Gateway n” Submenu
This submenu contains the settings for the selected gateway.
Table 148: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.9 “TCP/IP” > “DNS Server” Submenu
This submenu contains the settings for the DNS server.
Table 149: “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.

7.8.2.4.10 “Networking” > “Ethernet” Submenu
configuration.
Table 150: “Networking” > “Ethernet” Submenu

Opens a submenu with settings for the IP
1. Switch Configuration
address(es)
Opens a submenu with settings for the ETHERNET
2. Ethernet Ports
interfaces

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.11 “Ethernet” > “Switch Configuration” Submenu
This submenu contains the settings for the Switch configuration.
Table 151: “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.

7.8.2.4.12 “Ethernet” > “Ethernet Ports” Submenu
interfaces.
Table 152: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.4.13 “Ethernet Ports” > “Interface Xn” Submenu
This submenu contains the settings for the selected ETHERNET interface.
Table 153: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.5 “Firewall” Menu
This menu contains other submenus for the firewall functionality settings.
Table 154: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.1 “Firewall” > “General Configuration” Submenu
This submenu contains the general settings for the firewall.
Table 155: “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 WAN
6. Interface VPN Opens a submenu with firewall settings on the IP
7. Interface X1 level for the selected interface
8. Interface X2

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.2 “General Configuration” > “Interface xxx” Submenu
This submenu contains the firewall settings on the IP level for the selected
interface.
Table 156: “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-8207 PFC200 CS 2ETH RS 3G
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.3 “Firewall” > “MAC Address Filter” Submenu
This submenu contains the settings for the MAC address filter.
Table 157: “Firewall” > “MAC Address Filter” Submenu

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

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.4 “MAC Address Filter” > “MAC address filter whitelist” Submenu
This submenu displays all available filter entries.
Table 158: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” Submenu
Opens a submenu to add a new filter entry
1. Add new
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

7.8.2.5.5 “MAC address filter whitelist” > “Add new / No (n)” Submenu
In this submenu, you can create, change or delete filter entries.
Table 159: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.6 “Firewall” > “User Filter” Submenu
This submenu displays all available filter entries.
Table 160: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.5.7 “User Filter” > “Add New / No (n)” Submenu
In this submenu, you can create, change or delete filter entries.
Table 161: “Firewall” > “User Filter” > “Add New / No (n)” Submenu
1. Source IP address Enter the source IP address.
2. Source netmask Enter the source network mask.
3. Source port Enter the source port number.
4. Destination IP address Enter the destination IP address.
5. Destination netmask Enter here the destination netmask.
6. Destination port Enter the destination port number.
Select the permitted protocols.
7. 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.
8. 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.
9. state
1. on The filter is enabled.
2. off The filter is disabled.
To apply the changes for the selected filter entry,
10. accept
choose this menu item.
To delete the selected filter entry, choose this menu
11. delete
item.

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.6 “Clock” Menu
This menu contains other submenus for the date and time settings.
Table 162: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.7 “Administration” Menu
This menu contains settings for controller administration.
Table 163: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.7.1 “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 164: “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.

7.8.2.7.2 “Administration” > “Users” Submenu
This submenu contains settings for the user passwords.
Table 165: “Administration” > “Users” Submenu

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

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.8 “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 166: “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

7.8.2.8.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 167: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.8.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 168: “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.

7.8.2.8.3 “Firmware Backup” > “Destination” Submenu
This submenu contains a selection option for the backup destination drive.
Table 169: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.8.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 170: “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.

7.8.2.8.5 “Firmware Restore” > “Select Package” Submenu
This submenu contains a selection option for the data to be restored.
Table 171: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.8.6 “Package Server” > “System Partition” Submenu
This submenu contains information and setting options for the current system
partition.
Table 172: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.9 “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 173: “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

7.8.2.9.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 174: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.10 “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11 “Ports and Services” Menu
This submenu contains other submenus with settings for the respective services.
Table 175: “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
12. Modbus TCP
TCP service
Opens a submenu with settings for the MODBUS
13. Modbus UDP
UDP service
Opens a submenu with settings for the PLC runtime
14. PLC Runtime Services
system services

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.1 “Ports and Services” > “Telnet” Submenu
This submenu contains the settings for the Telnet service.
Table 176: “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

7.8.2.11.2 “Ports and Services” > “FTP” Submenu
This submenu contains the settings for the FTP service.
Table 177: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.3 “Ports and Services” > “FTPS” Submenu
This submenu contains the settings for the FTPS service.
Table 178: “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

7.8.2.11.4 “Ports and Services” > “HTTP” Submenu
This submenu contains the settings for the HTTP service.
Table 179: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.5 “Ports and Services” > “HTTPS” Submenu
This submenu contains the settings for the HTTPS service.
Table 180: “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

7.8.2.11.6 “Ports and Services” > “NTP” Submenu
This submenu contains the settings for the NTP service.
Table 181: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.7 “Ports and Services” > “SSH” Submenu
This submenu contains the settings for the SSH service.
Table 182: “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

7.8.2.11.8 “Ports and Services” > “TFTP” Submenu
This submenu contains the settings for the TFTP service.
Table 183: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.9 “Ports and Services” > “DHCPD” Submenu
This submenu contains the settings for the DHCPD service.
Table 184: “Ports and Services” > “DHCPD” Submenu

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

7.8.2.11.10 “DHCPD” > “Xn” Submenu
This submenu contains the settings for the DHCPD service for the selected
interface.
Table 185: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.11 “Ports and Services” > “DNS” Submenu
This submenu contains the settings for the DNS service.
Table 186: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.12 “Ports and Services” > “IOCHECK PORT” Submenu
This submenu contains settings for the WAGO-I/O-CHECK port.
Table 187: “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

7.8.2.11.13 “Ports and Services” > “Modbus TCP” Submenu
This submenu contains the settings for the MODBUS TCP service.
Table 188: “Ports and Services” > “Modbus TCP” Submenu

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

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.14 “Ports and Services” > “Modbus UDP” Submenu
This submenu contains the settings for the MODBUS UDP service.
Table 189: “Ports and Services” > “Modbus UDP” Submenu

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

7.8.2.11.15 “Ports and Services” > “PLC Runtime Services” Submenu
This submenu contains the settings for the PLC runtime system services.
Table 190: “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 2
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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.16 “PLC Runtime Services” > “CODESYS 2” Submenu
This submenu contains the settings for the CODESYS 2 service.
Table 191: “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 2 runtime system and the CODESYS 2
2. Communication 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 2 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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.17 “PLC Runtime Services” > “e!RUNTIME” Submenu
This submenu contains the settings for the e!RUNTIME service.
Table 192: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.11.18 “…” > “Firewall Status” Submenu
This submenu contains firewall settings for the selected service.
Table 193: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.12 “SNMP” Menu
This menu contains other submenus with the SNMP settings.
Table 194: “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

7.8.2.12.1 “SNMP” > “General SNMP Configuration” Submenu
This submenu contains the general SNMP settings.
Table 195: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.12.2 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu
This submenu contains the SNMP v1/v2c Manager settings.
Table 196: “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).

7.8.2.12.3 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu
This submenu contains settings for the v1/v2c trap receivers.
Table 197: “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-8207 PFC200 CS 2ETH RS 3G
7.8.2.12.4 “SNMP” > “SNMP v3 Configuration” Submenu
This submenu contains settings for SNMP v3.
Table 198: “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 (max. 32 characters, no
spaces)
(n + 1). Add new v3 User • Authentication type (None/MD5/SHA)
• Authentication key (min. 8 characters, max. 32
characters, no spaces)
• Privacy type (None/DES/AES)
• Privacy key (min. 8 characters, max. 32
characters, no spaces)
• IP address for a trap receiver for v3 traps

Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.2.12.5 “SNMP” > “(Secure)SNMP firewalling” Submenu
These submenus contain the SNMP firewall settings.
Table 199: “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-8207 PFC200 CS 2ETH RS 3G
</dg_
7.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 correct COM port after starting “WAGO Ethernet Settings”.
Figure 43: “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-8207 PFC200 CS 2ETH RS 3G
Figure 44: “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-8207 PFC200 CS 2ETH RS 3G
7.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 45: “WAGO Ethernet Settings” – Identification Tab (Example)
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.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 46: “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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
7.8.3.3 PLC Tab
Figure 47: “WAGO Ethernet Settings” – Protocol Tab
Here you can select the runtime system.
Manual
750-8207 PFC200 CS 2ETH RS 3G
7.8.3.4 Status Tab
Figure 48: “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 235
750-8207 PFC200 CS 2ETH RS 3G
8 Run-time System CODESYS 2.3

8.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.
8.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.
8.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.
8.2.2 Creating a Project and Selecting the Target System

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 show here this is the
PFC200 CS 2ETH RS 3G “WAGO_750-8207”.
Manual
236 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
3. Click on [OK]. The “Target system settings” configuration window then
opens.
Figure 49: Target System Settings (1)
4. To accept the default configuration for the fieldbus controller click [OK].
The “New component” window opens.
Figure 50: Target System Settings (2)
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
6. Click on [OK] to create the project. The programming interface opens.
Figure 51: Creating a New Function Block
Figure 52: Programming Interface with the PLC_PRG Program Module
8.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-8207 PFC200 CS 2ETH RS 3G
Figure 53: “Resources” Tab
2. In the left window double-click on “PLC configuration”. The PLC

configuration for the controller opens.
Manual
750-8207 PFC200 CS 2ETH RS 3G
3. Right-click on the entry “K-Bus[FIX]” and then select “Edit” in the contextual
menu. The “configuration” dialog window then opens.
Figure 54: 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 55: “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-8207 PFC200 CS 2ETH RS 3G
5. WAGO-I/O-CHECK is started.
Figure 56: 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-8207 PFC200 CS 2ETH RS 3G
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)
or end module (750-600) will not be shown in the I/O configurator.
Figure 57: 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 58: “Add I/O Modules” Button
Manual
750-8207 PFC200 CS 2ETH RS 3G
10. You can select a module in the new “Module selection” window that then
appears.
Figure 59: “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 60: 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-8207 PFC200 CS 2ETH RS 3G
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 61: 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 62: Control Configuration: I/O Modules with Their Associated Addresses
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.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 63: 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 64: 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-8207 PFC200 CS 2ETH RS 3G
4. Repeat Step 2 for the “Input_1” variable.
Figure 65: Example of an Allocation
5. To compile, click on Project > Compile all in the menu bar.
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.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 66: Creating a Communication Link – Step 1
Manual
750-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
8.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.
8.3 Syntax of Logical Addresses

Access to individual memory elements according to IEC 61131-3 is possible
using only the following special symbols:
Table 200: 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-8207 PFC200 CS 2ETH RS 3G
Enter the character string of the absolute address without empty spaces. The first
bit of a word has an address of 0.
8.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 69: Task Configuration
2. To create a task right-click on “Task configuration” and in the contextual

menu select “Attach task”.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 70: Changing Task Names 1
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 71: Call-up to Add to the Program Module
5. Compile the example program by selecting Project > Rebuild all in the
context menu.
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.4.1 Cyclic Tasks

You can assign a priority for each task in order to establish the task processing
sequence.
Figure 72: 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-8207 PFC200 CS 2ETH RS 3G
… 31. These tasks all receive the same computing time from the operating
system (“Completely Fair Scheduler” procedure).
8.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 73: 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.
8.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).
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 74: Debugging (Case 1)
Manual
750-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
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).
8.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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 81: 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-8207 PFC200 CS 2ETH RS 3G
The following events can be activated:
Table 201: 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-8207 PFC200 CS 2ETH RS 3G
8.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 82: 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 83: 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-8207 PFC200 CS 2ETH RS 3G
Figure 84: 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 85: 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-8207 PFC200 CS 2ETH RS 3G
Figure 86: CODESYS – Variable Contents Prior to Division by “0”
Figure 87: CODESYS – Variable Contents After Division by “0” and Call-up of the Event Handler
8.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
Manual
750-8207 PFC200 CS 2ETH RS 3G
PFC variables, the bit memory address area and the slaves attached to the
fieldbus.
Figure 88: Process Image
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 89: Flag Area
8.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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
I/O Module Data Width

The data width of an I/O module is between 0 and 48 bytes.
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.
8.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.
8.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 202: 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-8207 PFC200 CS 2ETH RS 3G
Table 203: Access to the Process Images of the Input and Output Data – MODBUS
Memory area Description Access via Logical Address Space
PLC
MODBUS input MODBUS input variables, Read Word
process image addressed by word via MODBUS %IW1000 to %IW1999
Byte
%IB2000 to %IB3999
Read Bit
MODBUS input variables,
%IX1000.0 …%IX1000.15 to
addressed by bit via MODBUS
%IX1384.0 … %IX1384.15
MODBUS output MODBUS output variables, Read/ Word
process image addressed by word via MODBUS Write %QW1000 to %QW1999
Byte
%QB2000 to %QB3999
MODBUS output variables, Read/ Bit
addressed by bit via MODBUS Write %QX1000.0 …
%QX1000.15 to %QX1384.0
… %QX1384.15
Table 204: 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 205: 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 206: Access to the Process Images of the Input and Output Data – Flags
Memory Area Description Access via Logical Address Space
PLC
Flag variables 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
6.5 kB addressed by bit via Read/ Bit (MODBUS)
MODBUS (3328 words). Write %MX0.0 … %MX0.15 to
%MX3327.0 …
%MX3327.15
Retain variables Retain memory addressed by Read/ -
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.
8.8 Addressing Example

The following addressing example clarifies the access to the process image:
Table 207: 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 208: 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-8207 PFC200 CS 2ETH RS 3G
Table 208: 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
8.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.”
8.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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 90: Local Bus Synchronization 01
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-8207 PFC200 CS 2ETH RS 3G
8.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-8207 PFC200 CS 2ETH RS 3G
8.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-8207 PFC200 CS 2ETH RS 3G
8.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 150 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-8207 PFC200 CS 2ETH RS 3G
8.9.5 Local Bus (KBus) Settings
Figure 94: Local Bus (KBus) Settings
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 209: Local Bus (KBus) Settings
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
8.9.5.1 Effect of Update Mode on CODESYS Tasks
8.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.
8.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-8207 PFC200 CS 2ETH RS 3G
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.
8.10 Memory Settings in CODESYS

The list below illustrates the standard memory allocation of the PFC200:
• 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
8.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-8207 PFC200 CS 2ETH RS 3G
Figure 95: Program Memory (Example)
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.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 96: Data Memory and Function Block Limitation (Example)
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.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 97: 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 98: Flag and Retain Memory (Example)
Manual
750-8207 PFC200 CS 2ETH RS 3G
8.11 General Target System Settings
Figure 99: 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_
8.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 an Internet browser. An applet is stored in the file system of a Web
server and is accessible to 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 an Internet browser.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 100: Selecting the Visualization Technique in the Target System Settings
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 101: 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-8207 PFC200 CS 2ETH RS 3G
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.
8.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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
8.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 210: 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-8207 PFC200 CS 2ETH RS 3G
8.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-8207 PFC200 CS 2ETH RS 3G
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
WAGO-I/O-SYSTEM 750 e!RUNTIME Runtime Environment 287
750-8207 PFC200 CS 2ETH RS 3G
9 e!RUNTIME Runtime Environment

9.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
288 e!RUNTIME Runtime Environment WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
9.2 CODESYS V3 Priorities

A list of priorities implemented for the controller is provided below as
supplementary information to the CODESYS 3 documentation.
Table 211: 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
WAGO-I/O-SYSTEM 750 e!RUNTIME Runtime Environment 289
750-8207 PFC200 CS 2ETH RS 3G
9.3 Memory Spaces under e!RUNTIME

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

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

The program (also code) and data memory has a size of 60 Mbytes.
This space has already been requested in the system after a successful program
download and can be fully utilized.
The memory space is dynamically divided up into program and data space.
9.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 * 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.
9.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 102: Remanent Main Memory
Manual
290 MODBUS – CODESYS 2 WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
10 MODBUS – CODESYS 2
</dg_
10.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.
10.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
WAGO-I/O-SYSTEM 750 MODBUS – CODESYS 2 291
750-8207 PFC200 CS 2ETH RS 3G
10.3 Configuration
All of the MODBUS operating modes are configured using the CODESYS PLC
configuration.
Figure 103: 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-8207 PFC200 CS 2ETH RS 3G
10.3.1 MODBUS Settings

The “MODBUS settings” group contains the following configuration parameters.
Table 212: 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
exchange will 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
*
value 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.
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-8207 PFC200 CS 2ETH RS 3G
10.3.2 MODBUS TCP Settings

The “MODBUS TCP Settings” contains the following configuration parameters for
the “MODBUS TCP” mode:
Table 213: 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
10.3.3 MODBUS UDP Settings

The “MODBUS UDP Settings” group contains the following configuration
parameters for the “MODBUS UDP” mode:
Table 214: 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
10.3.4 MODBUS RTU Settings

The “MODBUS RTU Settings” group contains the following configuration
parameters for the “MODBUS RTU” mode:
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 215: 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-8207 PFC200 CS 2ETH RS 3G
Table 215: 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-8207 PFC200 CS 2ETH RS 3G
</dg_
10.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-8207 PFC200 CS 2ETH RS 3G
10.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 104: 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-8207 PFC200 CS 2ETH RS 3G
10.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 105: 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-8207 PFC200 CS 2ETH RS 3G
10.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”.
10.4.4 MODBUS Mapping

10.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 216: 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-8207 PFC200 CS 2ETH RS 3G
10.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 217: 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-8207 PFC200 CS 2ETH RS 3G
10.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 218: 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-8207 PFC200 CS 2ETH RS 3G
Table 218: 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-8207 PFC200 CS 2ETH RS 3G
10.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 219: 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
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
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-8207 PFC200 CS 2ETH RS 3G
Table 219: MODBUS Mapping for Write Register Services FC6, FC16, FC22, FC23
in parentheses)
12288 … 65535 %MW0 … Maximum addressable flag area:
(0x3000 … 0xFFFF) %MW53247 53248 register/word flags (104 kB);
Manual
750-8207 PFC200 CS 2ETH RS 3G
10.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 220: 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-8207 PFC200 CS 2ETH RS 3G
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.
10.5.1 Process Image Properties

10.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).
10.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).
10.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).
10.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-8207 PFC200 CS 2ETH RS 3G
10.5.2 Network Configuration

10.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
10.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.
10.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.
10.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.
10.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-8207 PFC200 CS 2ETH RS 3G
10.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.
10.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 106: State Diagram, STANDARD_WATCHDOG Operation Mode
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 107: 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-8207 PFC200 CS 2ETH RS 3G
Figure 108: State Diagram, Switchover Operation Mode
10.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-8207 PFC200 CS 2ETH RS 3G
Table 221: 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-8207 PFC200 CS 2ETH RS 3G
10.5.4.2 Register 0x1101 – Watchdog Status
This register provides the current state of the MODBUS watchdog.

The following states are possible:
Table 222: 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.
RUNNING configured 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.
10.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.
10.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-8207 PFC200 CS 2ETH RS 3G
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 223: 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.
10.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-8207 PFC200 CS 2ETH RS 3G
Table 224: 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.
10.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.
10.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.
10.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.
10.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.
10.5.6.4 Register 0x2012 – Device ID
This register provides the device ID (WAGO Item No.) of the controller.
Example: 8206.
Manual
750-8207 PFC200 CS 2ETH RS 3G
10.5.6.5 Register 0x2013 – Major Firmware Version
This register provides the major part for the firmware version.
10.5.6.6 Register 0x2014 – Minor Firmware Version
This register provides the minor part for the firmware version.
10.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-8207 PFC200 CS 2ETH RS 3G
10.6 Diagnostics
10.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.
10.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.
10.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 225: Diagnostics for the Error Server

Diagnostics Diagnostic text Method of Explanation
ID saving
0x00090000 Modbus Slave Temporary MODBUS slave library has
library loaded been successfully loaded.
0x00090001 Modbus Slave Temporary MODBUS slave library has
library closed been 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-8207 PFC200 CS 2ETH RS 3G
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
data exchange exchange started.
started by PLC
0x0009000C Modbus Slave Temporary MODBUS slave data
data exchange 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-8207 PFC200 CS 2ETH RS 3G
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
Watchdog Timer monitoring time expired.
expired.
0x00090203 Modbus Slave has Permanent All MODBUS TCP
terminated all connections terminated due to
established TCP timeout.
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
WAGO-I/O-SYSTEM 750 MODBUS – e!RUNTIME 319
750-8207 PFC200 CS 2ETH RS 3G
11 MODBUS – e!RUNTIME
11.1 MODBUS Address Overview
Figure 109: MODBUS Address Overview
Manual
320 MODBUS – e!RUNTIME WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
11.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,
analog and digital (total size of
64,067 0xFA43 1 ro
the MODBUS OUT space)
0x7D00
64,068 0xFA44 1 ro
analog 0x7D00
Manual
750-8207 PFC200 CS 2ETH RS 3G
Access Description
Dec. Hex. in Words
64,069 0xFA45 1 ro
digital 0x8000
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-8207 PFC200 CS 2ETH RS 3G
11.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 110: State Diagram, ADVANCED_WATCHDOG Operation Mode
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 111: 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 112: State Diagram, Switching Operation Modes
Manual
750-8207 PFC200 CS 2ETH RS 3G
11.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 227: 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-8207 PFC200 CS 2ETH RS 3G
11.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.
11.2.1.3 Register 0xFA02 – Watchdog Status
This register provides the current state of the MODBUS watchdog.

The following states are possible:
Table 228: 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.
RUNNING configured 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-8207 PFC200 CS 2ETH RS 3G
11.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.

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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
*Default setting
The individual options are activated if the relevant bit or bit combination is set.
11.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-8207 PFC200 CS 2ETH RS 3G
11.2.2 Status Registers

11.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
11.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.
11.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
11.2.3.2 Firmware Version
The register 0xFA14 contains the firmware version of the controller.
11.2.3.3 Hardware Version
The register 0xFA15 contains the hardware version of the controller.
11.2.3.4 Firmware Loader/Boot Loader
The register 0xFA16 contains the firmware loader/boot loader version of the
controller.
11.2.4 MODBUS Process Image Version

The register 0xFA17 contains the MODBUS process image version of the
controller.
11.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-8207 PFC200 CS 2ETH RS 3G
11.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
11.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-8207 PFC200 CS 2ETH RS 3G
11.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
WAGO-I/O-SYSTEM 750 Diagnostics 331
750-8207 PFC200 CS 2ETH RS 3G
12 Diagnostics
12.1 Operating and Status Messages
The following tables contain descriptions of all operating and status messages for
the controller which are indicated by LEDs.
12.1.1 Power Supply Indicating Elements
Figure 113: Power Supply Indicating Elements
The A LED (system power supply) indicates following diagnostics:
Table 230: 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.
The B LED (field-side power supply) indicates following diagnostics:
Table 231: 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
332 Diagnostics WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
12.1.2 Mobile Communications Network Status LED
Figure 114: Mobile Radio Network Status Indicators
The CON LED indicates following diagnostics:
Table 232: Diagnostics via CON LED

Status Explanation Remedy
Green flashing 2G or 3G network ---
1800 ms ON,
200 ms OFF
Green flashing No network - Check the SIM status via WBM.
200 ms ON, - Enter the PIN or PUK if necessary.
1800 ms OFF - If the SIM status is “ready” and the
error persists, check the antenna
and its connection to the device.
- If necessary, connect the antenna
correctly or use another compatible
antenna.
- If possible, use a mobile phone or
comparable device to check the
signal quality of the mobile radio
network locally.
OFF Modem firmware Wait until the update process has
update complete.
Do not switch off the device!
Manual
750-8207 PFC200 CS 2ETH RS 3G
12.1.3 Fieldbus/System Indicating Elements
Figure 115: Indicating elements for fieldbus/system
The SYS LED indicates following diagnostics:
Table 233: Diagnostics via SYS LED

Green Ready to operate - ---
System start
completed without
errors
Yellow Device is in ---
startup/boot process
and the RST button is
not pressed.
Yellow 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
The RUN LED indication depends on the runtime system enabled (CODESYS 2
or e!RUNTIME).
The following indications apply to the CODESYS 2 runtime system:
Table 234: 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-8207 PFC200 CS 2ETH RS 3G
The following indications apply to the e!RUNTIME runtime system:
Table 235: 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.
- Select a longer cycle time for IEC
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-8207 PFC200 CS 2ETH RS 3G
The I/O LED indicates following diagnostics:
Table 236: 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-8207 PFC200 CS 2ETH RS 3G
The MS LED indicates following diagnostics:
Table 237: 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-8207 PFC200 CS 2ETH RS 3G
The NET LED indicates following diagnostics:
Table 238: Diagnostics via NET LED

Green 3G network ---
Orange 2G network ---
Red No network - Check the SIM status via WBM.
- Enter the PIN or PUK if necessary.
- If the SIM status is “ready” and the
error persists, check the antenna
and its connection to the device.
- If necessary, connect the antenna
correctly or use another compatible
antenna.
- If possible, use a mobile phone or
comparable device to check the
signal quality of the mobile network
locally.
Red flashing, No SIM card inserted - Switch off the device.
blink code 1-1 - Insert a SIM card.
- Switch the device on again.
Red flashing, Invalid/locked SIM - Switch off the device.
blink code 1-2 card - Insert a different SIM card that is
valid.
- Switch the device on again.
Red flashing, Modem not A hardware fault is present. Contact
blink code 2-1 connected WAGO Support.
Red flashing, Modem initialization Load the modem firmware originally
blink code 2-2 error (incompatible included as delivered from the factory
firmware version) back onto the device.
Red flashing, Timeout for modem Switch the device off and on again.
blink code 2-3 reset
Manual
750-8207 PFC200 CS 2ETH RS 3G
The LEDs S1 … S5 together indicate following diagnostics:
Table 239: Diagnostics via Signal Quality LEDs

Status of signal quality LEDs
▐ █ ▐█ ██ ▐██ Signal quality
(S1) (S2) (S3) (S4) (S5)
OFF OFF OFF OFF OFF No network
Yellow OFF OFF OFF OFF Level 1
Green OFF OFF OFF OFF Level 2
Green Green OFF OFF OFF Level 3
Green Green Green OFF OFF Level 4
Green Green Green Green OFF Level 5
Green Green Green Green Green Level 6
Table 240: Signal Quality Meaning

Explanation
Signal quality
UMTS GSM
Only UMTS, probable Only GSM, probable
Level 1
connection failure connection failure
HDSPA possible, instable GPRS, very slow data
Level 2
connection connection
HDSPA possible, no weather GPRS, stabile data connection,
Level 3
reserve maximum data rate (54 kbit/s)
EDGE, stabile, very slow data
Level 4 HDSPA, stabile connection
connection possible
HDSPA, maximum data rate EDGE, maximum data rate
Level 5
7.2 Mbit/s (220 kBit/s)
E-EDGE possible (up to
Level 6 HSPA+ possible (if available)
1 Mbit/s)
Depending on the mobile network load and limitations set by the mobile network
service provider, the actual data rate may be slower than the signal quality allows
at the time.
Manual
750-8207 PFC200 CS 2ETH RS 3G
12.2 Diagnostics Messages via Flashing Sequences
12.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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Figure 116: Flashing Sequence Process Diagram
Manual
750-8207 PFC200 CS 2ETH RS 3G
12.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-8207 PFC200 CS 2ETH RS 3G
12.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 555

Fax: +49 571 887 8555
E-mail: [email protected]
Table 241: 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 used
8 Not used
9 CPU exception error
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 242: 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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
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 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 applications:
Local bus watchdog - Contact WAGO Support.
5
has triggered. For C applications:
- Check the time monitoring settings.
Manual
750-8207 PFC200 CS 2ETH RS 3G
12.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 555

Fax: +49 571 887 8555
E-mail: [email protected]
Table 248: 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
WAGO-I/O-SYSTEM 750 Service 349
750-8207 PFC200 CS 2ETH RS 3G
13 Service
13.1 Inserting and Removing the Memory Card
</dg_
13.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 117: Inserting the Memory Card

</dg_
13.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
350 Service WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
6. Close the cover flap by flipping it down and pushing it in until it snaps into
place.
Manual
750-8207 PFC200 CS 2ETH RS 3G
13.2 Inserting and Removing the SIM Card
13.2.1 Inserting the SIM Card

1. Press the release button of the SIM card slot with an appropriate object
(e.g., pen or operating tool 210-719 or 720) until the SIM card holder pops
out of the SIM card slot.
2. Remove the SIM card holder.
3. Hold the SIM card holder with the recess for the SIM card facing you.
4. Insert the SIM card into the SIM card holder in such a way that the shape of
the recess lines up with the shape of the SIM card and the contacts of the
SIM card are visible.
5. Reinsert the SIM card holder into the SIM card slot with the SIM card
(contacts visible) oriented towards the memory card slot until the SIM card
holder latches.
Figure 118: Inserting the SIM Card
13.2.2 Removing the SIM Card

1. Press the release button of the SIM card slot with an appropriate object
(e.g., pen or operating tool 210-719 or 720) until the SIM card holder pops
out of the SIM card slot.
2. Remove the SIM card holder.
3. Remove the SIM card.
4. Reinsert the SIM card holder into the SIM card slot with the recess for the
SIM card oriented towards the memory card slot until the SIM card holder
latches.
Manual
750-8207 PFC200 CS 2ETH RS 3G
13.3 Firmware Changes
Obtain documentation appropriate for the firmware target version!

A firmware upgrade or downgrade 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 an upgrade/downgrade.
If you have any questions, feel free to contact our WAGO Support.
13.3.1 Perform Firmware Upgrade
Do not switch the controller off!

The controller can be damaged by interrupting the upgrade process.
Do not switch the controller off during the upgrade process and do not disconnect
the power supply!
Proceed as follows if you want to upgrade the controller to a later firmware

version:
1. Save your application and the controller settings.
2. Switch off the controller.
3. Insert the memory card with the new firmware image into the memory card
slot.
4. Switch on the controller.
5. After booting the controller, launch the WBM “Create Boot Image” page
(you may have to temporarily change the IP address).
6. Create a new boot image on the internal memory.
7. Switch off the controller after completing the process.
The controller can now be started with the new firmware version.
Manual
750-8207 PFC200 CS 2ETH RS 3G
13.3.2 Perform Firmware Downgrade

The controller can be damaged by interrupting the downgrade process.
Do not switch the controller off during the downgrade process and do not
disconnect the power supply!
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.
Proceed as follows if you want to downgrade the controller to an earlier firmware

version:
1. Save your application and the controller settings.
2. Switch off the controller.
3. Insert the memory card with the new firmware image into the memory card
slot. Use a special downgrade image if necessary.
5. After booting the controller, launch the WBM “Create Boot Image” page
(you may have to temporarily change the IP address).
6. Create a new boot image on the internal memory.
7. Switch off the controller after completing the process.
The controller can now be started with the new firmware version.
Manual
750-8207 PFC200 CS 2ETH RS 3G
13.3.3 Factory Reset

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!
All parameters and passwords are overwritten!

All controller parameters and passwords are overwritten by a factory reset.
Stored boot projects are deleted, including existing web visualization data.
Subsequently installed firmware functions are not overwritten.
If you have any questions, contact WAGO Support.
The controller is restarted after the factory reset.

Proceed as follows to factory 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.
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 factory reset.
Manual
WAGO-I/O-SYSTEM 750 Removal 355
750-8207 PFC200 CS 2ETH RS 3G
14 Removal

injury.
14.1 Removing Devices
Perform work on devices only if they are de-energized!

Working on energized devices can damage them. Therefore, turn off the power
supply before working on the devices.
14.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 119: Release Tab of Controller
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
356 Appendix WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
15 Appendix
15.1 Structure of Process Data for the I/O Modules
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
WAGO-I/O-SYSTEM 750 Appendix 357
750-8207 PFC200 CS 2ETH RS 3G
15.1.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.
15.1.1.1 1 Channel Digital Input Module with Diagnostics
750-435
Table 250: 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
15.1.1.2 2 Channel Digital Input Modules
750-400, -401, -405, -406, -410, -411, -412, -427, -438, (and all variations),
753-400, -401, -405, -406, -410, -411, -412, -427
Table 251: 2 Channel Digital Input Modules

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

753-421, -424, -425
Table 252: 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-8207 PFC200 CS 2ETH RS 3G
15.1.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 253: 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

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-8207 PFC200 CS 2ETH RS 3G
15.1.1.7 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 256: 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
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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
15.1.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.
15.1.2.1 1 Channel Digital Output Module with Input Process Data
750-523
The digital output modules deliver 1 bit via a process value Bit in the output
process image, which is illustrated in the input process image. This status image
shows "manual mode".
Table 258: 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
15.1.2.2 2 Channel Digital Output Modules
750-501, -502, -509, -512, -513, -514, -517, -535, (and all variations),
753-501, -502, -509, -512, -513, -514, -517
Table 259: 2 Channel Digital Output Modules

controls controls
DO 2 DO 1
Channel 2 Channel 1
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.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 260: 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 261: 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-8207 PFC200 CS 2ETH RS 3G
750-504, -516, -519, -531,

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

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

Process Data
750-532
Table 263: 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
15.1.2.6 8 Channel Digital Output Module
750-530, -536, -1515, -1516

753-530, -534
Table 264: 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-8207 PFC200 CS 2ETH RS 3G

Process Data
750-537
Table 265: 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-8207 PFC200 CS 2ETH RS 3G
15.1.2.9 8 Channel Digital Input/Output Modules
750-1502, -1506
Table 267: 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-8207 PFC200 CS 2ETH RS 3G
15.1.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.
15.1.3.1 1 Channel Analog Input Modules
750-491, (and all variations)
Table 268: 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, -465, -466, -467, -469, -472, -474, -475, 476, -
477, -478, -479, -480, -481, -483, -485, -492, (and all variations),
753-452, -454, -456, -461, -465, -466, -467, -469, -472, -474, -475, 476, -477,
478, -479, -483, -492, (and all variations)

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0 Measured Value Channel 1
Manual
750-8207 PFC200 CS 2ETH RS 3G
750-450, -453, -455, -457, -459, -460, -468, (and all variations),
753-453, -455, -457, -459

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.3.4 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 271: 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
750-451

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.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.
15.1.4.1 2 Channel Analog Output Modules
750-550, -552, -554, -556, -560, -562, 563, -585, (and all variations),
753-550, -552, -554, -556
Table 273: 2 Channel Analog Output Modules

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

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

Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.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.
15.1.5.1 Counter Modules
750-404, (and all variations except of /000-005),

753-404, (and variation /000-003)
The above Counter Modules have a total of 5 bytes of user data in both the Input
and Output Process Image (4 bytes of counter data and 1 byte of control/status).
The counter value is supplied as 32 bits. The following tables illustrate the Input
and Output Process Image, which has a total of 3 words mapped into each
image. Word alignment is applied.
Table 275: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003)
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S Status byte
1 D1 D0
Counter value
2 D3 D2

Byte Destination
Offset Description
High Byte Low Byte
0 - C Control byte
1 D1 D0
Counter setting value
2 D3 D2
Manual
750-8207 PFC200 CS 2ETH RS 3G
750-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 16 bits. The following tables illustrate the
Input and Output Process Image, which has a total of 3 words mapped into each
image. Word alignment is applied.
Table 276: Counter Modules 750-404/000-005

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

Byte Destination
Offset Description
High Byte Low Byte
0 - C Control byte
1 D1 D0 Counter Setting Value of Counter 1
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 277: Counter Modules 750-638, 753-638

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S0 Status byte of Counter 1
2 - S1 Status byte of Counter 2

Byte Destination
Offset Description
High Byte Low Byte
0 - C0 Control byte of Counter 1
2 - C1 Control byte of Counter 2
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.2 Pulse Width Modules
750-511, (and all variations /xxx-xxx)
The above Pulse Width modules have a total of 6 bytes of user data in both the
Input and Output Process Image (4 bytes of channel data and 2 bytes of control/
status). The two channel values are supplied as 16 bits. Each channel has its
own control/status byte. The following table illustrates the Input and Output
Process Image, which has a total of 4 words mapped into each image. Word
alignment is applied.
Table 278: Pulse Width Modules 750-511, /xxx-xxx

Input and Output Process
Byte Destination
Offset Description
High Byte Low Byte
0 - C0/S0 Control/Status byte of Channel 1
1 D1 D0 Data Value of Channel 1
15.1.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 operation mode can be set. Dependent on it, the process
image of these modules is then the same, as from the appropriate variation.
The above Serial Interface Modules with alternative data format have a total of 4
bytes of user data in both the Input and Output Process Image (3 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 2 words mapped into each image.
Table 279: Serial Interface Modules with Alternative Data Format

Input and Output Process Image
Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 D0 C/S Data byte
byte
1 D2 D1 Data bytes
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.4 Serial Interface Modules with Standard Data Format
750-650/000-001, -014, -015, -016

750-653/000-001, -006
The above Serial Interface Modules with Standard Data Format have a total of 6
bytes of user data in both the Input and Output Process Image (5 bytes of serial
data and 1 byte of control/status). The following table illustrates the Input and
Output Process Image, which have a total of 3 words mapped into each image.
Table 280: Serial Interface Modules with Standard Data Format

Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 D0 C/S Data byte
byte
1 D2 D1
Data bytes
2 D4 D3
15.1.5.5 Data Exchange Module
750-654, (and the variation /000-001)
The Data Exchange modules have a total of 4 bytes of user data in both the Input
and Output Process Image. The following tables illustrate the Input and Output
Process Image, which has a total of 2 words mapped into each image.
Table 281: Data Exchange Module

Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0
Data bytes
1 D3 D2
15.1.5.6 SSI Transmitter Interface Modules
750-630 (and all variations)
The process image of the / 003-000-variants depends on the parameterized

operating mode!
The operating mode of the configurable /003-000 I/O module versions can be
set. Based on the operating mode, the process image of these I/O modules is
then the same as that of the respective version.
Manual
750-8207 PFC200 CS 2ETH RS 3G
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.
Table 282: SSI Transmitter Interface Modules

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 D1 D0
Data bytes
1 D3 D2
15.1.5.7 Incremental Encoder Interface Modules
750-631/000-004, -010, -011
The above Incremental Encoder Interface modules have 5 bytes of input data
and 3 bytes of output data. The following tables illustrate the Input and Output
Process Image, which have 4 words into each image. Word alignment is applied.
Table 283: Incremental Encoder Interface Modules 750-631/000-004, --010, -011

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S not used Status byte
1 D1 D0 Counter word
2 - - not used
3 D4 D3 Latch word

Byte Destination
Offset Description
High Byte Low Byte
0 - C not used Control byte
1 D1 D0 Counter setting word
2 - - not used
3 - - not used
750-634
The above Incremental Encoder Interface module has 5 bytes of input data (6
bytes in cycle duration measurement mode) and 3 bytes of output data. The
following tables illustrate the Input and Output Process Image, which has 4 words
mapped into each image. Word alignment is applied.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 284: Incremental Encoder Interface Modules 750-634
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S not used Status byte
1 D1 D0 Counter word
2 - (D2) *) not used (Periodic time)
3 D4 D3 Latch word
*) If cycle duration measurement mode is enabled in the control byte, the cycle duration is
given as a 24-bit value that is stored in D2 together with D3/D4.
Byte Destination
Offset Description
High Byte Low Byte
1 D1 D0 Counter setting word
2 - -
not used
3 - -
750-637
The above Incremental Encoder Interface Module has a total of 6 bytes of user
data in both the Input and Output Process Image (4 bytes of encoder data and 2
bytes of control/status). The following table illustrates the Input and Output
Process Image, which have 4 words mapped into each image. Word alignment is
applied.
Table 285: Incremental Encoder Interface Modules 750-637

Byte Destination
Offset Description
High Byte Low Byte
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 286: Digital Pulse Interface Modules 750-635

Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 D0 C0/S0 Data byte
byte
1 D2 D1 Data bytes
15.1.5.8 DC-Drive Controller
750-636
The DC-Drive Controller maps 6 bytes into both the input and output process
image. The data sent and received are stored in up to 4 input and output bytes
(D0 ... D3). Two control bytes (C0, C1) and two status bytes (S0/S1) are used to
control the I/O module and the drive.
In addition to the position data in the input process image (D0 … D3), it is
possible to display extended status information (S2 … S5). Then the three control
bytes (C1 … C3) and status bytes (S1 … S3) are used to control the data flow.
Bit 3 of control byte C1 (C1.3) is used to switch between the process data and
the extended status bytes in the input process image (Extended Info_ON). Bit 3
of status byte S1 (S1.3) is used to acknowledge the switching process.
Table 287: DC-Drive Controller 750-636

Input Process Image
Byte Destination
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-8207 PFC200 CS 2ETH RS 3G
Byte Destination
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)
15.1.5.9 Stepper Controller
750-670
The Stepper controller RS422 / 24 V / 20 mA 750-670 provides the fieldbus

coupler 12 bytes input and output process image via 1 logical channel. The data
to be sent and received are stored in up to 7 output bytes (D0 … D6) and 7 input
bytes (D0 … D6), depending on the operating mode.
Output byte D0 and input byte D0 are reserved and have no function assigned.
One I/O module control and status byte (C0, S0) and 3 application control and
status bytes (C1 ... C3, S1 ... S3) provide the control of the data flow.
Switching between the two process images is conducted through bit 5 in the
control byte (C0 (C0.5). Activation of the mailbox is acknowledged by bit 5 of the
status byte S0 (S0.5).
Table 288: Stepper Controller RS 422 / 24 V / 20 mA 750-670

Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 reserved S0 reserved Status byte S0
1 D1 D0
2 D3 D2 Process data*) / Mailbox**)
3 D5 D4
Status byte S3 Process data*) /
4 S3 D6
reserved**)
5 S1 S2 Status byte S1 Status byte S2
*) Cyclic process image (Mailbox disabled)
**) Mailbox process image (Mailbox activated)
Manual
750-8207 PFC200 CS 2ETH RS 3G
Byte Destination
Offset Description
High Byte Low Byte
0 reserved C0 reserved Control byte C0
1 D1 D0
2 D3 D2 Process data*) / Mailbox**)
3 D5 D4
Process data*) /
4 C3 D6 Control byte C3
reserved**)
5 C1 C2 Control byte C1 Control byte C2
*) Cyclic process image (Mailbox disabled)
**) Mailbox process image (Mailbox activated)
15.1.5.10 RTC Module
750-640
The RTC Module has a total of 6 bytes of user data in both the Input and Output
Process Image (4 bytes of module data and 1 byte of control/status and 1 byte ID
for command). The following table illustrates the Input and Output Process
Image, which have 3 words mapped into each image. Word alignment is applied.
Table 289: RTC Module 750-640

Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 ID C/S Command byte
byte
1 D1 D0
Data bytes
2 D3 D2
15.1.5.11 DALI/DSI Master Module
750-641
The DALI/DSI Master module has a total of 6 bytes of user data in both the Input
and Output Process Image (5 bytes of module data and 1 byte of control/status).
The following tables illustrate the Input and Output Process Image, which have 3
words mapped into each image. Word alignment is applied.
Table 290: DALI/DSI Master Module 750-641

Input Process Image
Byte Destination
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
Manual
750-8207 PFC200 CS 2ETH RS 3G
Byte Destination
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
15.1.5.12 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.
The structure of the process data is described in detail in the following tables.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 291: Overview of Input Process Image 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 in use
DA = DALI address
GA = Group address
Table 292: Overview of the Output Process Image in the "Easy" Mode“
Byte Designation
Offset Note
High Byte Low Byte
res. Broadcast ON/OFF and activate:
Bit 0: Broadcast ON
Bit 1: Broadcast OFF
0 - S
Bit 2: Broadcast ON/OFF/dimming
Bit 3: Broadcast short ON/OFF
Bits 4 … 7: reserved
1 DA4…DA7 DA0…DA3 Bit pair for DALI address DA0:
2 DA12…DA15 DA8…DA11 Bit 1: short: DA switch ON
3 DA20…DA23 DA16…DA19 long: dimming, brighter
4 DA28…DA31 DA24…DA27 Bit 2: short: DA switch OFF
5 DA36…DA39 DA32…DA35 long: dimming, darker
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: short: GA switch ON
long: dimming, brighter
Bit 2: short: GA switch OFF
10 GA12…GA15 GA8…GA11 long: dimming, darker
Bit pairs GA1 … GA15 similar to GA0.
11 Bit 8…15 Bit 0…7 Switch scene 0…15
DA = DALI address
GA = Group address
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.13 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.
15.1.5.14 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 293: 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
15.1.5.15 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 294: MP Bus Master Module 750-643

Byte Destination
Offset Description
High Byte Low Byte
extended Control/ Control/status
0 C1/S1 C0/S0
Status byte byte
1 D1 D0
2 D3 D2 Data bytes
3 D5 D4
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.16 Bluetooth® RF-Transceiver
750-644
The size of the process image for the Bluetooth® module can be adjusted to 12,
24 or 48 bytes.
It consists of a control byte (input) or status byte (output); an empty byte; an
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.
®
Table 295: Bluetooth RF-Transceiver 750-644
Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 - C0/S0 not used
byte
1 D1 D0
2 D3 D2
3 D5 D4 Mailbox (0, 3, 6 or 9 words) and
... ... ... Process data (2-23 words)
max.
D45 D44
23
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.5.17 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 296: 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
15.1.5.18 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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 297: KNX/EIB/TP1 Module 753-646
Input Process Image
Byte Destination
Offset Description
High Byte Low Byte
0 - S0 not used Status byte
extended
1 S1 OP Opcode
Status byte
2 D1 D0 Data byte 1 Data byte 0

Byte Destination
Offset Description
High Byte Low Byte
0 - C0 not used Control byte
extended
1 C1 OP Opcode
Control byte
15.1.5.19 AS-interface Master Module
750-655
The length of the process image of the AS-interface master module can be set to
fixed sizes of 12, 20, 24, 32, 40 or 48 bytes.
It consists of a control or status byte, a mailbox with a size of 0, 6, 10, 12 or 18
bytes and the AS-interface process data, which can range from 0 to 32 bytes.
The AS-interface master module has a total of 6 to maximally 24 words data in

both the Input and Output Process Image. Word alignment is applied.
The first Input and output word, which is assigned to an AS-interface master
module, contains the status / control byte and one empty byte.
Subsequently the mailbox data are mapped, when the mailbox is permanently
superimposed (Mode 1).
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 298: AS-interface Master Module 750-655

Byte Destination
Offset Description
High Byte Low Byte
Control/status
0 - C0/S0 not used
byte
1 D1 D0
2 D3 D2
3 D5 D4 Mailbox (0, 3, 5, 6 or 9 words)/
... ... ... Process data (0-16 words)
max.
D45 D44
23
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.1.6 System Modules
15.1.6.1 System Modules with Diagnostics
750-610, -611
The modules provide 2 bits of diagnostics in the Input Process Image for
monitoring of the internal power supply.
Table 299: System Modules with Diagnostics 750-610, -611

Input Process Image
Diagnostic Diagnostic bit
bit S 2 S1
Fuse Fuse
15.1.6.2 Binary Space Module
750-622
The Binary Space Modules behave alternatively like 2 channel digital input
modules or output modules and seize depending upon the selected settings 1, 2,
3 or 4 bits per channel. According to this, 2, 4, 6 or 8 bits are occupied then either
in the process input or the process output image.
Table 300: 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-8207 PFC200 CS 2ETH RS 3G
15.2 CODESYS 2 Libraries

Additional functions for the controller 750-8207are provided using libraries.
15.2.1 General Libraries

This section contains general CODESYS libraries supported by the controller750-
8207.
15.2.1.1 CODESYS System Libraries
All of the functions of the CODESYS system libraries listed below are supported.
Table 301: 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-8207 PFC200 CS 2ETH RS 3G
Table 301: 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_
15.2.1.2 SysLibCom.lib
The controller 750-8207supports 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-8207.
Additional information about this is given in the online Help function for
CODESYS-IDE.
15.2.1.3 SysLibFile.lib

“SysLibFile.lib” library:
- SysFileClose
- SysFileCopy
- SysFileDelete
- SysFileEOF
- SysFileGetPos
- SysFileGetSize
- SysFileGetTime
- SysFileOpen
- SysFileRead
- SysFileRename
- SysFileSetPos
- SysFileWrite
Manual
750-8207 PFC200 CS 2ETH RS 3G
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 302: 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)
15.2.1.4 SysLibFileAsync.lib

“SysLibFileAsync.lib” library:
- SysFileCloseAsync
- SysFileCopyAsync
- SysFileDeleteAsync
- SysFileEOFAsync
- SysFileGetPosAsync
- SysFileGetSizeAsync
- SysFileGetTimeAsync
- SysFileOpenAsync
- SysFileReadAsync
- SysFileRenameAsync
- SysFileSetPosAsync
Manual
750-8207 PFC200 CS 2ETH RS 3G
- 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 303: 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)
15.2.1.5 SysLibRtc.lib

“SysLibRtc.lib” library:
- SysRtcGetHourMode
- SysRtcGetTime
- SysRtcSetTime
CODESYS-IDE.
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.2.1.6 BusDiag.lib
The controller 750-8207 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 CS 2ETH RS 3G” (750-8207):
Table 304: Input Variable “DEVICENUMBER”

Bus System Value
Local bus 0
MODBUS 1
15.2.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
15.2.1.8 SerComm.lib

“SerComm.lib” library:
- SERCOMM
- SERCOMM_VERSION
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.2.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 120: Graphical Representation of the “ConfigToolFB” Function Block
Table 305: 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 Display of the MAC address Immediately
X1 mac-address
get_actual_eth_config
IP Address read Display of current IP address Immediately
X1 ip-address
get_actual_eth_config Display of the current subnet
Subnet Mask read Immediately
X1 subnet-mask mask
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-8207 PFC200 CS 2ETH RS 3G
Table 306: 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.
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 307: 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 308: 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-8207 PFC200 CS 2ETH RS 3G
Table 308: 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 default
read
config number=1 value 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 number.
write/
change=change <Value> is an IP address with the Immedia
DNS Server 1 change
dns-server- format tely
name=<Value> “Number.Number.Number.Numbe
r.”
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
here.
edit_dns_server
<Value> is an IP address with the Immedia
Add DNS server write add=add dns-server-
format tely
name=<Value>
“Number.Number.Number.Numbe
r.”
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 309: 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
- on
- off
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-8207 PFC200 CS 2ETH RS 3G
Table 310: 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-8207 PFC200 CS 2ETH RS 3G
Table 311: 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 312: 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-8207 PFC200 CS 2ETH RS 3G
Table 312: Description of the Configuration Scripts for "Administration"
ve
Configuration of Service Interface
User of the serial interface.
Possible return values are:
- service (WAGO-I/O-CHECK,
get_service_interface_ WAGO-I/O-PRO,
read
config mode e!COCKPIT)
®
Configuration of - linux (Linux console)
immedia
Service - free (unused, free for
tely
Interface application)
User of the serial interface.
Possible entries for <value>:
config_service_interface
write - service
_config mode=<value>
- linux
- free
Reboot Controller
immedia
- write start_reboot Restart the controller.
tely
</dg_
Table 313: 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-nand).
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-8207 PFC200 CS 2ETH RS 3G
Table 314: 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-8207 PFC200 CS 2ETH RS 3G
Table 315: 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 2 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 CODESYS2
- 3 = enable e!RUNTIME
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 Immedia
location memory card) tely
- HOME:// (saving on internal
config_runtime boot-
write memory)
project=<value>
- CARD:// (saving on the
memory card)
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-8207 PFC200 CS 2ETH RS 3G
ve
CODESYS 2 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 2 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 2 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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
Table 316: 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-8207 PFC200 CS 2ETH RS 3G
Table 317: 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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
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-8207 PFC200 CS 2ETH RS 3G
Creating a new v3 user.
v3-auth-name: User name, string
without spaces, maximum of 32
characters. This must be a new,
unique user name.
Parameters:
User name (<Value1> = string)
Encryption method. (<Value2> =
config_snmp
none, MD5 or SHA).
v3-edit=add
Key string for authentication,
v3-auth-name=<Value1>
(<Value3> = String with at least
v3-auth-type=<Value2>
eight and a maximum of 32
Add new v3- v3-auth-key=<Value3> After
write characters)
User v3-privacy=<Value4> restart
Privacy encryption method
v3-privacy-
(<Value4> = none, DES or AES).
key=<Value5>
Privacy key string (<Value5> =
v3-notification-
String with at least eight and a
receiver=<Value6>
maximum of 32 characters), 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).
15.2.1.10 WagoLibCpuUsage.lib

“WagoLibCpuUsage.lib” library:
- CPU_Usage
The document containing the description of the library and the function block it
15.2.1.11 WagoLibDiagnosticIDs.lib

“WagoLibDiagnosticIDs.lib” library:
- DIAGNOSTIC_SEND_ID
- DIAGNOSTIC_SET_TEXT_FOR_ID
Manual
750-8207 PFC200 CS 2ETH RS 3G
15.2.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
15.2.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
15.2.1.14 WagoLibNetSnmpManager.lib

“WagoLibNetSnmpManager.lib” libraries:
- 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
Manual
750-8207 PFC200 CS 2ETH RS 3G
- SNMPM_SET
- SNMPM_SET_V3
15.2.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
15.2.1.16 WagoLibTerminalDiag.lib

“WagoLibTerminalDiag.lib” library:
- GET_TERMINALDIAG
Manual
WAGO-I/O-SYSTEM 750 List of Figures 411
750-8207 PFC200 CS 2ETH RS 3G
List of Figures
Figure 1: View of device .....................................................................................27
Figure 2: Marking Area for Serial Numbers ........................................................29
Figure 3: Data Contacts .....................................................................................30
Figure 4: Power Jumper Contacts ......................................................................31
Figure 5: CAGE CLAMP® connections ...............................................................32
Figure 6: Service Interface (Closed and Open Flap) ...........................................33
Figure 7: Network Connections – X1, X2 ............................................................34
Figure 8: RS-232/RS-485 – Communication Connection – X3 ...........................35
Figure 9: Termination with DTE-DCE Connection (1:1) ......................................36
Figure 10: Termination with DTE-DTE Connection (Cross-Over) .......................36
Figure 11: RS-485 Bus Termination ...................................................................37
Figure 12: Mobile Radio Antenna Connection ....................................................38
Figure 13: Power Supply Indicating Elements ....................................................39
Figure 14: Indicating elements for fieldbus/system .............................................40
Figure 15: Indicating Elements, Memory Card Slot.............................................41
Figure 16: Indicating Elements, RJ-45 Jacks......................................................42
Figure 17: Mobile Radio Network Status Indicators ............................................43
Figure 18: Mode Selector Switch ........................................................................44
Figure 19: Reset Button .....................................................................................45
Figure 20: Slot for SD Memory Card ..................................................................46
Figure 21: SIM Card Slot ....................................................................................47
Figure 22: Schematic diagram............................................................................48
Figure 23: Connecting the PFC Controller Generation to a Cloud ......................68
Figure 24: Spacing .............................................................................................80
Figure 25: Release Tab of Controller..................................................................82
Figure 26: Connecting a Conductor to a CAGE CLAMP® ...................................83
Figure 27: Power Supply Concept ......................................................................85
Figure 28: “Open DHCP”, Example Figure .........................................................89
Figure 29: CBM Starting Screen .........................................................................90
Figure 30: CBM – Selecting “Networking”...........................................................91
Figure 31: CBM – Selecting “TCP/IP” .................................................................91
Figure 32: CBM – Selecting “IP address” ...........................................................91
Figure 33: CBM – Selecting the IP Address .......................................................92
Figure 34: CBM – Entering a New IP Address ....................................................92
Figure 35: “WAGO Ethernet Settings” – Starting Screen (Example) ...................93
Figure 36: “WAGO Ethernet Settings” – “Network” Tab ......................................94
Figure 37: Example of a Function Test ...............................................................96
Figure 38: Entering Authentication ...................................................................103
Figure 39: Password Reminder ........................................................................104
Figure 40: WBM Browser Window (Example) ...................................................106
Figure 41: WBM Status Information (Example).................................................107
Figure 42: CBM main menu (example) .............................................................177
Figure 43: “WAGO Ethernet Settings” – Start Screen .......................................228
Figure 44: “WAGO Ethernet Settings” – Communication Link ..........................229
Figure 45: “WAGO Ethernet Settings” – Identification Tab (Example) ..............230
Figure 46: “WAGO Ethernet Settings” – Network Tab ......................................231
Figure 47: “WAGO Ethernet Settings” – Protocol Tab ......................................233
Manual
412 List of Figures WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
Figure 48: “WAGO Ethernet Settings” – Status Tab .........................................234
Figure 49: Target System Settings (1) ..............................................................236
Figure 50: Target System Settings (2) ..............................................................236
Figure 51: Creating a New Function Block .......................................................237
Figure 52: Programming Interface with the PLC_PRG Program Module ..........237
Figure 53: “Resources” Tab..............................................................................238
Figure 54: Control Configuration – Edit ............................................................239
Figure 55: “Start WAGO-I/O-CHECK and Scan” Button ...................................239
Figure 56: WAGO-I/O-CHECK – Starting Screen .............................................240
Figure 57: I/O Configurator Empty ....................................................................241
Figure 58: “Add I/O Modules” Button ................................................................241
Figure 59: “Module Selection” Window .............................................................242
Figure 60: I/O Configurator with Defined I/O Modules ......................................242
Figure 61: Variable declaration.........................................................................243
Figure 62: Control Configuration: I/O Modules with Their Associated Addresses
................................................................................................................243
Figure 63: Program Function Block ..................................................................244
Figure 64: Input Assistant for Selecting Variables ............................................244
Figure 65: Example of an Allocation .................................................................245
Figure 66: Creating a Communication Link – Step 1 ........................................246
Figure 69: Task Configuration ..........................................................................249
Figure 70: Changing Task Names 1 .................................................................250
Figure 71: Call-up to Add to the Program Module .............................................251
Figure 72: Cyclic Task ......................................................................................252
Figure 73: Freewheeling Task ..........................................................................253
Figure 74: Debugging (Case 1) ........................................................................254
Figure 81: CODESYS – System Events ...........................................................258
Figure 82: CODESYS Program Provokes Division by “0” .................................260
Figure 83: CODESYS – Creating and Activating an Event Handler ..................260
Figure 84: CODESYS – New Module has been Generated ..............................261
Figure 85: CODESYS – Enter the Event in a Global Variable...........................261
Figure 86: CODESYS – Variable Contents Prior to Division by “0” ...................262
Figure 87: CODESYS – Variable Contents After Division by “0” and Call-up of the
Event Handler .........................................................................................262
Figure 88: Process Image ................................................................................263
Figure 89: Flag Area ........................................................................................264
Figure 90: Local Bus Synchronization 01 .........................................................269
Figure 94: Local Bus (KBus) Settings ...............................................................273
Figure 95: Program Memory (Example) ...........................................................276
Manual
WAGO-I/O-SYSTEM 750 List of Figures 413
750-8207 PFC200 CS 2ETH RS 3G
Figure 96: Data Memory and Function Block Limitation (Example)...................277
Figure 97: Remanent Main Memory (Example) ................................................278
Figure 98: Flag and Retain Memory (Example) ................................................278
Figure 99: General Target System Settings......................................................279
Figure 100: Selecting the Visualization Technique in the Target System Settings
................................................................................................................280
Figure 101: Creating the PLC_VISU Starting Visualization ...............................281
Figure 102: Remanent Main Memory ...............................................................289
Figure 103: CODESYS PLC Configuration - MODBUS Settings ......................291
Figure 104: MODBUS Process Image ..............................................................297
Figure 105: Flag Area.......................................................................................298
Figure 106: State Diagram, STANDARD_WATCHDOG Operation Mode .........308
Figure 107: State Diagram, ALTERNATIVE_WATCHDOG Operation Mode ....309
Figure 108: State Diagram, Switchover Operation Mode ..................................310
Figure 109: MODBUS Address Overview .........................................................319
Figure 110: State Diagram, ADVANCED_WATCHDOG Operation Mode.........322
Figure 111: State Diagram, SIMPLE_WATCHDOG Operation Mode ...............323
Figure 112: State Diagram, Switching Operation Modes ..................................323
Figure 113: Power Supply Indicating Elements ................................................331
Figure 114: Mobile Radio Network Status Indicators ........................................332
Figure 115: Indicating elements for fieldbus/system .........................................333
Figure 116: Flashing Sequence Process Diagram............................................341
Figure 117: Inserting the Memory Card ............................................................349
Figure 118: Inserting the SIM Card...................................................................351
Figure 119: Release Tab of Controller..............................................................355
Figure 120: Graphical Representation of the “ConfigToolFB” Function Block ...392
Manual
414 List of Tables WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
List of Tables
Table 1: Variants ................................................................................................15
Table 2: Number Notation ..................................................................................18
Table 3: Font Conventions .................................................................................18
Table 4: Legend for Figure “View” ......................................................................27
Table 5: Legend for Figure “Power Jumper Contacts” ........................................31
Table 6: Legend for figure “CAGE CLAMP® connections” ..................................32
Table 7: Service Interface ..................................................................................33
Table 8: Legend for Figure “Network Connections – X1, X2” ..............................34
Table 9: Legend for Figure “RS-232/RS-485 – Communication Connection – X3”
..................................................................................................................35
Table 10: Function of RS-232 Signals for DTE/DCE ..........................................36
Table 11: Legend for Figure “Power Supply Indicating Elements” ......................39
Table 12: Legend for Figure “Fieldbus/System Indicating Elements” ..................40
Table 13: Legend for Figure “Indicating Elements, Memory Card Slot” ...............41
Table 14: Legend for Figure “Indicating Elements, RJ-45 Jacks” ........................42
Table 15: Legend for the “Mobile Radio Network Status Indicators” Figure ........43
Table 16: Mode Selector Switch .........................................................................44
Table 17: Mode Selector Switch .........................................................................44
Table 18: Legend for Figure “SIM Card Slot” ......................................................47
Table 19: Technical Data − Mechanical Data .....................................................49
Table 20: Technical Data – System Data ...........................................................49
Table 21: Technical Data – Power Supply ..........................................................49
Table 22: Technical Data – Clock .......................................................................50
Table 23: Technical Data – Programming ..........................................................50
Table 24: Technical Data – Local Bus ................................................................50
Table 25: Technical Data – ETHERNET.............................................................51
Table 26: Technical Data – Communication Interface ........................................51
Table 27: Technical Data – Mobile Radio Modem ..............................................51
Table 28: Technical Data – Field Wiring .............................................................52
Table 29: Technical Data – Power Jumper Contacts ..........................................52
Table 30: Technical Data – Data Contacts .........................................................52
Table 31: Technical Data – Climatic Environmental Conditions ..........................52
Table 32: WBM Users ........................................................................................57
Table 33: Linux® Users .......................................................................................57
Table 34: List of Parameters Transmitted via DHCP ..........................................65
Table 35: Components of the Cloud Connectivity Software Package .................67
Table 36: Loading a Boot Project .......................................................................76
Table 37: WAGO DIN Rails ................................................................................80
Table 38: Filter Modules for 24 V Supply ............................................................85
Table 39: Default IP Addresses for ETHERNET Interfaces ................................88
Table 40: Network Mask 255.255.255.0 .............................................................88
Table 41: User Settings in the Default State .....................................................104
Table 42: Access Rights for WBM Pages .........................................................104
Table 43: WBM “Status Information” Page – “Controller Details” Group ...........109
Table 44: WBM “Status Information Page – “Network Details Xn” Group(s) .....109
Table 45: WBM “General PLC Runtime Configuration” Page – “General PLC
Runtime Configuration” Group ................................................................110
Manual
WAGO-I/O-SYSTEM 750 List of Tables 415
750-8207 PFC200 CS 2ETH RS 3G
Table 46: WBM “PLC Runtime Information” Page – “PLC Runtime” Group ......112
Table 47: WBM “PLC Runtime Information” Page – “Project Details” Group ....112
Table 48: WBM “PLC Runtime Information” Page – “Task n” Group(s) ............113
Table 49: WBM “PLC WebVisu” Page – “Web Server Configuration” Group ....114
Table 50: WBM “Configuration of Host and Domain Name” Page – “Hostname”
Group ......................................................................................................115
Table 51: WBM “Configuration of Host and Domain Name” Page – “Domain
Name” Group ..........................................................................................115
Table 52: WBM “TCP/IP Configuration” Page – “IP Configuration (Xn)” Group(s)
................................................................................................................116
Table 53: WBM “TCP/IP Configuration” Page – “Default Gateway n” Group ....117
Table 54: WBM “TCP/IP Configuration” Page – “DNS Server” Group...............118
Table 55: WBM “Ethernet Configuration” Page – “Switch Configuration” Group
................................................................................................................119
Table 56: WBM “Ethernet Configuration” Page – “Interface Xn” Groups ...........120
Table 57: WBM “Routing” Page – “General Routing Configuration” Group .......121
Table 58: WBM “Routing” Page – “Static Routes“ Group..................................122
Table 59: WBM “Routing” Page – “IP-Masquerading” Group ............................123
Table 60: WBM “Routing” Page – “Port Forwarding” Group .............................124
Table 61: WBM “General Firewall Configuration” Page – “Global Firewall
Parameters” Group .................................................................................125
Table 62: WBM “General Firewall Configuration” Page – “Firewall Parameter
Interface Xn” Group.................................................................................126
Table 63: WBM “Configuration of MAC Address Filter” Page – “Global MAC
Address Filter State” Group.....................................................................127
Table 64: WBM “Configuration of MAC Address Filter” Page – “MAC Address
Filter State Xn” Group .............................................................................128
Table 65: WBM “Configuration of MAC Address Filter” Page – “MAC Address
Filter Whitelist” Group .............................................................................128
Table 66: WBM “Configuration of User Filter” Page – “User Filter” Group .......129
Table 67: WBM “Configuration of User Filter” Page – “User Filter n” Group .....129
Table 68: WBM “Configuration of User Filter” Page – “Add New User Filter”
Group ......................................................................................................130
Table 69: WBM “Configuration of Time and Date” Page – “Date on Device” Group
................................................................................................................131
Table 70: WBM “Configuration of Time and Date” Page – “Time on Device”
Group ......................................................................................................131
Table 71: WBM “Configuration of Time and Date” Page – “Time Zone” Group .132
Table 72: WBM “Configuration of Time and Date” Page – “TZ String” Group ...133
Table 73: WBM “Configuration of the users for the Web-based Management”
Page – “Change Password for Selected User” Group .............................134
Table 74: WBM “Create Bootable Image” page – “Create bootable image from
active partition” Group .............................................................................135
Table 75: WBM “Configuration of Serial Interface RS232” Page – “Assign Owner
of Serial Interface” Group ........................................................................137
Table 76: WBM “Configuration of Serial Interface RS-232” page – “Assign Owner
of Service Interface” Group .....................................................................138
Table 77: “Firmware-Backup” WBM Page ........................................................140
Table 78: “Firmware Restore” WBM Page ........................................................142
Table 79: WBM “Mass Storage” Page – “<Device Name>” Group ....................145
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 80: WBM “Mass Storage” Page – “<Device Name>” Group ....................145
Table 81: WBM “Software Uploads” Page – “Upload New Software” Group .....146
Table 82: WBM “Software Uploads” Page – “Activate New Software” Group ...146
Table 83: WBM “Configuration of Network Services” Page – “Telnet” Group ....147
Table 84: WBM “Configuration of Network Services” Page – “FTP” Group .......147
Table 85: WBM “Configuration of Network Services” Page – “FTPS” Group ....147
Table 86: WBM “Configuration of Network Services” Page – “HTTP” Group ....148
Table 87: WBM “Configuration of Network Services” Page – “HTTPS” Group ..148
Table 88: WBM “Configuration of Network Services” Page – “I/O-CHECK“ Group
................................................................................................................148
Table 89: WBM “Configuration of Network Services” Page – “OPC UA” Group 149
Table 90: WBM “Configuration of NTP Client” Page – “NTP Client Configuration”
Group ......................................................................................................150
Table 91: WBM “Configuration of PLC Runtime Services” Page – “General
Configuration” Group...............................................................................151
Table 92: WBM “Configuration of CODESYS Services” Page – “CODESYS 2
Web Server” Group .................................................................................151
Table 93: WBM “Configuration of CODESYS Services” Page – “e!RUNTIME Web
Server” Group .........................................................................................151
Table 94: WBM “SSH Server Settings” Page – “SSH Server” Group ................153
Table 95: WBM “TFTP Server” Page – “TFTP Server” Group ..........................154
Table 96: WBM “DHCP Configuration” – “DHCP Configuration Xn” Group .......155
Table 97: WBM “Configuration of DNS Service” Page – “DNS Service” Group 156
Table 98: WBM “MODBUS Services Configuration” Page – “MODBUS TCP”
Group ......................................................................................................157
Table 99: WBM “MODBUS Configuration Services” Page – “MODBUS UDP”
Group ......................................................................................................157
Table 100: WBM “Configuration of Cloud Connectivity” Page – “Software Version”
Group ......................................................................................................158
Table 101: WBM “Configuration of Cloud Connectivity” Page – “Status” Group158
................................................................................................................159
Table 103: WBM “Configuration of General SNMP Parameters” Page – “General
SNMP Configuration” Group ...................................................................162
Table 104: WBM “Configuration of SNMP v1/v2c Parameters” Page – “SNMP
v1/v2c Manager Configuration” Group.....................................................163
Table 105: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Actually
Configured Trap Receivers” Group .........................................................163
Table 106: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Trap
Receiver n” Group(s)...............................................................................164
Table 107: WBM “Configuration of SNMP v1/v2c Parameters” Page – “Add New
Trap Receiver” Group .............................................................................164
Table 108: WBM “Configuration of SNMP v3” Page – “Actually Configured v3
Users” Group ..........................................................................................165
Table 109: WBM “Configuration of SNMP v3 Users” Page – “v3 User n” Group(s)
................................................................................................................165
Table 110: WBM “Configuration of SNMP v3 Users” Page – “Add New v3 User”
Group ......................................................................................................166
Table 111: WBM “Diagnostic Information” Page ...............................................167
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 112: WBM “Configuration of internal 3G Modem” Page – “SIM
Authentication” Group .............................................................................168
Table 113: WBM “Configuration of internal 3G Modem” Page – “Mobile Network
Configuration” Group...............................................................................169
Table 114: WBM “Configuration of internal 3G Modem” Page – “Provider List”
Group ......................................................................................................170
Table 115: WBM “Configuration of internal 3G Modem” Page – “Network
Package Service” Group .........................................................................170
Table 116: WBM “Configuration of internal 3G Modem” Page – “Upload and
activate new Modem Software” Group ....................................................171
Table 117: WBM “Configuration of OpenVPN and IPsec” Page – “OpenVPN”
Group ......................................................................................................172
Table 118: WBM “Configuration of OpenVPN and IPsec” Page – “IPsec” Group
................................................................................................................172
Table 119: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate
Upload” Group ........................................................................................173
Table 120: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate List”
Group ......................................................................................................173
Table 121: WBM “Configuration of OpenVPN and IPsec” Page – “Private Key
List” Group ..............................................................................................173
Table 122: “Security Settings” WBM Page – “TLS Configuration” Group ..........174
Table 123: CBM Menu Structure ......................................................................177
Table 124: “Information” Menu .........................................................................180
Table 125: “Information” > “Controller Details” Submenu..................................180
Table 126: “Information” > “Network Details” Submenu ....................................181
Table 127: “PLC Runtime” Menu ......................................................................182
Table 128: “PLC Runtime” > “Information” Submenu........................................182
Table 129: “PLC Runtime” > “Information” > “Runtime Version” Submenu .......183
Table 130: “PLC Runtime” > “Information” > “Webserver Version” Submenu ...183
Table 131: “PLC Runtime” > “Information” > “State” Submenu .........................183
Table 132: “PLC Runtime” > “Information” > “Number of Tasks” Submenu ......184
Table 133: “PLC Runtime” > “Information” > “Project Details” Submenu...........184
Table 134: “PLC Runtime” > “Information” > “Tasks” Submenu ........................184
Table 135: “PLC Runtime” > “Information” > “Tasks” > “Task n” Submenu .......185
Table 136: “PLC Runtime” > “General Configuration” Submenu .......................185
Table 137: “PLC Runtime” > “General Configuration” > “PLC Runtime Version”
Submenu ................................................................................................186
Table 138: “PLC Runtime” > “General Configuration” > “Home Dir On SD Card”
Submenu ................................................................................................186
Table 139: “PLC Runtime” > “WebVisu” Submenu ...........................................187
Table 140: “Networking” Menu .........................................................................188
Table 141: “Networking” > “Host/Domain Name” Submenu ..............................188
Table 142: “Networking” > “Hostname” Submenu ............................................189
Table 143: “Networking” > “Host/Domain Name” > “Domain Name” Submenu .189
Table 144: “Networking” > “TCP/IP” Submenu .................................................189
Table 145: “Networking” > “IP Address” Submenu ...........................................190
Table 146: “Networking” > “TCP/IP” > “IP Address” Submenu > “Xn” ...............190
Table 147: “Networking” > “TCP/IP” > “Default Gateway” Submenu .................191
Table 148: “Networking” > “TCP/IP” > “Default Gateway” > “Default Gateway n”
Submenu ................................................................................................191
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 149: “Networking” > “TCP/IP” > “DNS Server” Submenu ........................192
Table 150: “Networking” > “Ethernet” Submenu ...............................................192
Table 151: “Networking” > “Ethernet” > “Switch Configuration” Submenu.........193
Table 152: “Networking” > “Ethernet” > “Ethernet Ports” Submenu ..................193
Table 153: “Networking” > “Ethernet” > “Ethernet Ports” > “Interface Xn”
Submenu ................................................................................................194
Table 154: “Firewall” Menu ...............................................................................195
Table 155: “Firewall” > “General Configuration” Submenu................................196
Table 156: “Firewall” > “General Configuration” > “Interface xxx” Submenu .....197
Table 157: “Firewall” > “MAC Address Filter” Submenu ...................................199
Table 158: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist”
Submenu ................................................................................................200
Table 159: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” >
“Add new / No (n)” Submenu ...................................................................200
Table 160: “Firewall” > “User Filter” Submenu ..................................................201
Table 161: “Firewall” > “User Filter” > “Add New / No (n)” Submenu ................202
Table 162: “Clock” Menu ..................................................................................203
Table 163: “Administration” Menu.....................................................................204
Table 164: “Administration” > “Create Image” Submenu...................................205
Table 165: “Administration” > “Users” Submenu ...............................................205
Table 166: “Package Server” Menu ..................................................................206
Table 167: “Package Server” > “Firmware Backup” Menu ................................206
Table 168: “Package Server” > “Firmware Backup” > “Auto Update Feature”
Menu .......................................................................................................207
Table 169: “Package Server” > “Firmware Backup” > “Auto Update Feature”
Menu .......................................................................................................207
Table 170: “Package Server” > “Firmware Restore” Menu ...............................208
Table 171: “Package Server” > “Firmware Restore” > “Select Package” Menu.208
Table 172: “Package Server” > “System Partition” Submenu ...........................209
Table 173: “Mass Storage” Menu .....................................................................210
Table 174: “Mass Storage” > “SD Card” Menu .................................................210
Table 175: “Ports and Services” Menu .............................................................212
Table 176: “Ports and Services” > “Telnet” Submenu .......................................213
Table 177: “Ports and Services” > “FTP” Submenu ..........................................213
Table 178: “Ports and Services” > “FTPS” Submenu........................................214
Table 179: “Ports and Services” > “HTTP” Submenu .......................................214
Table 180: “Ports and Services” > “HTTPS” Submenu .....................................215
Table 181: “Ports and Services” > “NTP” Submenu..........................................215
Table 182: “Ports and Services” > “SSH” Submenu .........................................216
Table 183: “Ports and Services” > “TFTP” Submenu ........................................216
Table 184: “Ports and Services” > “DHCPD” Submenu ....................................217
Table 185: “Ports and Services” > “DHCPD” > “Xn” Submenu .........................217
Table 186: “Ports and Services” > “DNS” Submenu .........................................218
Table 187: “Ports and Services” > “IOCHECK PORT” Submenu ......................219
Table 188: “Ports and Services” > “Modbus TCP” Submenu ............................219
Table 189: “Ports and Services” > “Modbus UDP” Submenu ............................220
Table 190: “Ports and Services” > “PLC Runtime Services” Submenu .............220
Table 191: “Ports and Services” > “PLC Runtime Services” > “CODESYS 2”
Submenu ................................................................................................221
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 192: “Ports and Services” > “PLC Runtime Services” > “e!RUNTIME”
Submenu ................................................................................................222
Table 193: “Ports and Services” > “Firewall Status” Submenu..........................223
Table 194: “SNMP” Menu .................................................................................224
Table 195: “SNMP” > “General SNMP Configuration” Submenu ......................224
Table 196: “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu ..........225
Table 197: “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu..225
Table 198: “SNMP” > “SNMP v3 Configuration” Submenu ...............................226
Table 199: “SNMP” > “(Secure )SNMP firewalling” Submenu ...........................227
Table 200: Syntax of Logical Addresses...........................................................248
Table 201: Events ............................................................................................259
Table 202: Access to the Process Images of the Input and Output Data – Local
Bus .........................................................................................................265
Table 203: Access to the Process Images of the Input and Output Data –
MODBUS ................................................................................................266
CANopen ................................................................................................266
PROFIBUS .............................................................................................266
Table 206: Access to the Process Images of the Input and Output Data – Flags
................................................................................................................267
Table 207: Arrangement of the I/O Modules for the Addressing Example.........267
Table 208: Addressing Example .......................................................................267
Table 209: Local Bus (KBus) Settings ..............................................................274
Table 210: Errors and Remedies ......................................................................284
Table 211: CODESYS V3 Priorities ..................................................................288
Table 212: MODBUS Settings ..........................................................................292
Table 213: MODBUS TCP Settings ..................................................................293
Table 214: MODBUS UDP Settings .................................................................293
Table 215: MODBUS RTU Settings..................................................................294
Table 216: MODBUS Mapping for Read Bit Services FC1, FC2 .......................299
Table 217: MODBUS Mapping for Write Bit Services FC5, FC15 .....................300
Table 218: MODBUS Mapping for Read Register Services FC3, FC4, FC23 ...301
Table 219: MODBUS Mapping for Write Register Services FC6, FC16, FC22,
FC23 .......................................................................................................303
Table 220: WAGO MODBUS Registers............................................................305
Table 221: Watchdog Commands ....................................................................311
Table 222: Watchdog Status ............................................................................312
Table 223: Watchdog Configuration .................................................................313
Table 224: Watchdog Operation Modes ...........................................................314
Table 225: Diagnostics for the Error Server......................................................316
Table 226: WAGO MODBUS Registers............................................................320
Table 227: Watchdog Commands ....................................................................324
Table 228: Watchdog Status ............................................................................325
Table 229: Watchdog Configuration .................................................................326
Table 230: System Power Supply Diagnistics ..................................................331
Table 231: Field-Side Supply Diagnostics ........................................................331
Table 232: Diagnostics via CON LED...............................................................332
Table 233: Diagnostics via SYS LED ...............................................................333
Table 234: Diagnostics RUN LED ....................................................................334
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 235: RUN LED Diagnostics ....................................................................335
Table 236: Diagnostics I/O LED .......................................................................336
Table 237: MS-LED Diagnostics ......................................................................337
Table 238: Diagnostics via NET LED ...............................................................338
Table 239: Diagnostics via Signal Quality LEDs ...............................................339
Table 240: Signal Quality Meaning ...................................................................339
Table 241: Overview of Error Codes, I/O LED ..................................................343
Table 242: Error Code 1, Explanation of Blink Codes and Procedures for
Troubleshooting ......................................................................................344
Table 248: Overview of MS-LED Error Codes ..................................................348
Table 250: 1 Channel Digital Input Module with Diagnostics ............................357
Table 251: 2 Channel Digital Input Modules .....................................................357
Table 252: 2 Channel Digital Input Module with Diagnostics ............................357
Table 253: 2 Channel Digital Input Module with Diagnostics and Output Process
Data ........................................................................................................358
Table 256: 8 Channel Digital Input Module PTC with Diagnostics and Output
Process Data ..........................................................................................359
Table 257: 16 Channel Digital Input Modules ...................................................360
Table 258: 1 Channel Digital Output Module with Input Process Data ..............361
Table 259: 2 Channel Digital Output Modules ..................................................361
Table 260: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data ........................................................................................................362
Table 261: 2 Channel Digital Input Modules with Diagnostics and Input Process
Data 75x-506 ..........................................................................................362
Table 262: 4 Channel Digital Output Modules ..................................................363
Table 263: 4 Channel Digital Output Modules with Diagnostics and Input Process
Data ........................................................................................................363
Table 264: 8 Channel Digital Output Module ....................................................363
Table 265: 8 Channel Digital Output Modules with Diagnostics and Input Process
Data ........................................................................................................364
Table 266: 16 Channel Digital Output Modules ................................................364
Table 267: 8 Channel Digital Input/Output Modules .........................................365
Table 268: 1 Channel Analog Input Modules ....................................................366
Table 271: 3-Phase Power Measurement Module ............................................368
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 273: 2 Channel Analog Output Modules .................................................369
Table 274: 4 Channel Analog Output Modules .................................................369
Table 275: Counter Modules 750-404, (and all variations except of /000-005),
753-404, (and variation /000-003) ...........................................................370
Table 276: Counter Modules 750-404/000-005 ................................................371
Table 277: Counter Modules 750-638, 753-638 ...............................................371
Table 278: Pulse Width Modules 750-511, /xxx-xxx .........................................372
Table 279: Serial Interface Modules with Alternative Data Format....................372
Table 280: Serial Interface Modules with Standard Data Format ......................373
Table 281: Data Exchange Module ..................................................................373
Table 282: SSI Transmitter Interface Modules .................................................374
Table 283: Incremental Encoder Interface Modules 750-631/000-004, --010, -
011 ..........................................................................................................374
Table 284: Incremental Encoder Interface Modules 750-634............................375
Table 285: Incremental Encoder Interface Modules 750-637............................375
Table 286: Digital Pulse Interface Modules 750-635 ........................................376
Table 287: DC-Drive Controller 750-636 ..........................................................376
Table 288: Stepper Controller RS 422 / 24 V / 20 mA 750-670 ........................377
Table 289: RTC Module 750-640 .....................................................................378
Table 290: DALI/DSI Master Module 750-641 ..................................................378
Table 291: Overview of Input Process Image in the "Easy" Mode ....................380
Table 292: Overview of the Output Process Image in the "Easy" Mode“...........380
Table 293: EnOcean Radio Receiver 750-642 .................................................381
Table 294: MP Bus Master Module 750-643 ....................................................381
Table 295: Bluetooth® RF-Transceiver 750-644 ...............................................382
Table 296: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645 ...383
Table 297: KNX/EIB/TP1 Module 753-646 .......................................................384
Table 298: AS-interface Master Module 750-655 .............................................385
Table 299: System Modules with Diagnostics 750-610, -611............................386
Table 300: Binary Space Module 750-622 (with Behavior Like 2 Channel Digital
Input).......................................................................................................386
Table 301: CODESYS System Libraries ..........................................................387
Table 302: Possible Macros for File Access .....................................................389
Table 303: Possible Macros for File Access .....................................................390
Table 304: Input Variable “DEVICENUMBER”..................................................391
Table 305: Description of the Configuration Scripts for “Information” ................392
Table 306: Description of the Configuration Scripts for “CODESYS” ................393
Table 307: Description of the Configuration Scripts for “Networking - Host/Domain
Name” .....................................................................................................394
Table 308: Description of the Configuration Scripts for “Networking - TCP/IP” .394
Table 309: Description of the Configuration Scripts for “Networking - ETHERNET”
................................................................................................................396
Table 310: Description of the Configuration Scripts for “NTP” ..........................397
Table 311: Description of the Configuration Scripts for “Clock”.........................398
Table 312: Description of the Configuration Scripts for "Administration" ...........398
Table 313: Description of Configuration Scripts for “Package Server” ..............399
Table 314: Description of Configuration Scripts for “Ports and Services” –
“Network Services ...................................................................................400
Manual
750-8207 PFC200 CS 2ETH RS 3G
Table 315: Description of Configuration Scripts for “Ports and Services” – “PLC
Runtime Services” ...................................................................................401
Table 316: Description of Configuration Scripts for “Ports and Services” –
“SSH/TFTP” ............................................................................................404
Table 317: Description of Configuration Scripts for “SNMP” .............................405
Manual
WAGO-I/O-SYSTEM 750 423
750-8207 PFC200 CS 2ETH RS 3G
Manual
WAGO Kontakttechnik GmbH & Co. KG
Postfach 2880 • 32385 Minden
Hansastraße 27 • 32423 Minden
Phone: 0571/887 – 0
Fax: 0571/887 – 169
Internet: http://www.wago.com

m07508207 XXXXXXXX 0 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

m07508207 XXXXXXXX 0 en

Uploaded by

Copyright:

Available Formats

Manual

Version 1.3.0, valid from FW Version 02.08.25(11)

© 2018 WAGO Kontakttechnik GmbH & Co. KG

WAGO Kontakttechnik 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

Documentation Validity for Variants

This documentation is only applicable from FW Version 02.08.25(11).

Personal Injury Caused by Electric Current!

Damage to Property Caused by Electrostatic Discharge (ESD)!

1.4 Number Notation

1.5 Font Conventions

2.1 Legal Bases

2.1.1 Subject to Changes

2.1.2 Personnel Qualifications

2.1.3 Use of the WAGO-I/O-SYSTEM 750 in Compliance with

Operating the WAGO-I/O-SYSTEM 750 devices in home applications without

Appropriate housing (per 2014/34/EU) is required when operating the

The implementation of safety functions such as EMERGENCY STOP or safety

2.1.4 Technical Condition of Specified Devices

2.2 Safety Advice (Precautions)

Do not work on devices while energized!

Install the device only in appropriate housings, cabinets or in electrical

Do not use in telecommunication circuits!

Replace defective or damaged devices!

Protect the components against materials having seeping and insulating

Clean only with permitted materials!

Do not use any contact spray!

Do not reverse the polarity of connection lines!

Avoid electrostatic discharge!

2.4 Licensing Terms of the Software Package Used

2.5 Special Use Conditions for ETHERNET Devices

• Do not connect control components and control networks to an open

• Limit physical and electronic access to all automation components to

• If remote access to control components and control networks is required,

• Use “defense-in-depth” mechanisms in your system's security configuration

This controller can be used for applications in mechanical and systems

Automation tasks can be executed in all IEC 61131-3-compatible languages with

For IEC-61131-3 programming in CODESYS applications, the controller provides

Two ETHERNET interfaces and an integrated, interruptible switch enable wiring

• Two separate networks with a common MAC address and an IP address

Both of these interfaces support:

• Auto-MDI(X) (automatic uplink and crossover switching)

• MODBUS TCP Master/Slave

• MODBUS RTU Master/Slave (via RS-232 or RS-485)

The fieldbus configuration can be defined with the WAGO-I/O-PRO or

A Web-based management system (WBM) is also available as a configuration

• a FTP server, a FTPS server (explicit connections only)

• a BootP and DHCP client

• a CODESYS Runtime Environment

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

Memory card is not included in the scope of delivery!

Only use recommended memory card!

SIM card not included!

Flat rate recommended!

Figure 1: View of device

Table 4: Legend for Figure “View”

“Operating elements” >

The side labeling includes: