WAGO Kontakttechnik and KG PFC200 3G PLC Controller User Manual Manual 750 8207
WAGO Kontakttechnik GmbH & Co. KG 3G PLC Controller Manual 750 8207
Users Manual
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 3565964 |
| Application ID | NOI4PjGe5hPQfrcS4mPDtQ== |
| Document Description | Users Manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 409.88kB (5123452 bits) |
| Date Submitted | 2017-09-18 00:00:00 |
| Date Available | 2017-09-18 00:00:00 |
| Creation Date | 2017-09-13 10:25:07 |
| Producing Software | Adobe PDF Library 10.0 |
| Document Lastmod | 2017-09-13 10:57:28 |
| Document Title | Manual 750-8207 |
| Document Creator | Acrobat PDFMaker 10.1 für Word |
| Document Author: | WAGO Kontakttechnik GmbH & Co. KG |
Manual WAGO-I/O-SYSTEM 750 750-8207(/xxx-xxx) PFC200 CS 2ETH RS 3G PLC - Controller PFC200 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G © 2017 WAGO Kontakttechnik GmbH & Co. KG All rights reserved. WAGO Kontakttechnik GmbH & Co. KG Hansastraße 27 D-32423 Minden Phone: Fax: +49 (0) 571/8 87 – 0 +49 (0) 571/8 87 – 1 69 E-Mail: info@wago.com Web: http://www.wago.com Technical Support Phone: Fax: +49 (0) 571/8 87 – 5 55 +49 (0) 571/8 87 – 85 55 E-Mail: support@wago.com Every conceivable measure has been taken to ensure the accuracy and completeness of this documentation. However, as errors can never be fully excluded, we always appreciate any information or suggestions for improving the documentation. E-Mail: documentation@wago.com We wish to point out that the software and hardware terms as well as the trademarks of companies used and/or mentioned in the present manual are generally protected by trademark or patent. WAGO is a registered trademark of WAGO Verwaltungsgesellschaft mbH. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table of Contents Table of Contents Notes about this Documentation ........................................................... 15 1.1 1.2 1.3 1.4 1.5 Validity of this Documentation............................................................... 15 Copyright ..............................................................................................15 Symbols ...............................................................................................16 Number Notation ..................................................................................18 Font Conventions .................................................................................18 Important Notes ......................................................................................19 2.1 2.1.1 2.1.2 2.1.3 Legal Bases..........................................................................................19 Subject to Changes .......................................................................... 19 Personnel Qualifications .................................................................. 19 Use of the WAGO-I/O-SYSTEM 750 in Compliance with Underlying Provisions ........................................................................................19 Technical Condition of Specified Devices......................................... 20 Safety Advice (Precautions) ................................................................. 21 Disclaimer.............................................................................................22 Licensing Terms of the Software Package Used................................... 23 Special Use Conditions for ETHERNET Devices .................................. 23 2.1.4 2.2 2.3 2.4 2.5 Device Description ..................................................................................24 3.1 3.2 3.2.1 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.6.1 3.3.6.2 3.3.7 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.5 3.5.1 3.5.1.1 3.5.1.2 3.5.2 3.6 3.7 3.8 3.9 View .....................................................................................................27 Labeling ................................................................................................29 Manufacturing Number..................................................................... 29 Connectors ...........................................................................................30 Data Contacts/Internal Bus .............................................................. 30 Power Jumper Contacts/Field Supply .............................................. 31 CAGE CLAMP® Connectors ............................................................. 32 Service Interface ..............................................................................33 Network Connections – X1, X2 ........................................................ 34 RS-232/RS-485 – X3 Communication Connection ........................... 35 Operating as an RS-232 Interface ............................................... 36 Operating as an RS-485 Interface ............................................... 37 Mobile Radio Antenna ...................................................................... 38 Display Elements ..................................................................................39 Power Supply Indicating Elements ................................................... 39 Fieldbus/System Indicating Elements............................................... 40 Memory Card Indicating Elements ................................................... 41 Network Indicating Elements ............................................................ 42 Mobile Radio Network Status Indicators ........................................... 43 Operating Elements .............................................................................. 44 Operating Mode Switch .................................................................... 44 CODESYS 2 Runtime System ..................................................... 44 e!RUNTIME Runtime System ...................................................... 44 Reset Button ....................................................................................45 Slot for Memory Card ........................................................................... 46 SIM Card Slot .......................................................................................47 Schematic Diagram ..............................................................................48 Technical Data .....................................................................................49 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 4 Table of Contents 3.9.1 3.9.2 3.9.3 3.9.4 3.9.5 3.9.6 3.9.7 3.9.8 3.9.9 3.9.10 3.9.11 3.10 3.11 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Device Data .....................................................................................49 System Data ....................................................................................49 Power supply ...................................................................................49 Clock ................................................................................................50 Programming ...................................................................................50 Internal data bus .............................................................................. 50 ETHERNET .....................................................................................51 Serial interface .................................................................................51 Mobile Radio Modem ....................................................................... 51 Connection Type .............................................................................. 51 Climatic Environmental Conditions ................................................... 52 Approvals .............................................................................................53 Standards and Guidelines .................................................................... 53 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.3.2 Default Gateways ........................................................................ 60 4.1.4 Network Services ............................................................................. 62 4.1.4.1 DHCP Client ................................................................................ 62 4.1.4.2 DHCP Server...............................................................................62 4.1.4.3 DNS Server .................................................................................64 4.2 Memory Card Function ......................................................................... 65 4.2.1 Formatting........................................................................................65 4.2.2 Data Backup ....................................................................................67 4.2.2.1 Backup Function.......................................................................... 67 4.2.2.2 Restore Function ......................................................................... 68 4.2.3 Inserting a Memory Card during Operation ...................................... 70 4.2.4 Removing the Memory Card during Operation ................................. 70 4.2.5 Setting the Home Directory for the Runtime System ........................ 71 5.1 5.2 5.3 5.3.1 5.3.2 5.4 5.5 Mounting..................................................................................................72 Installation Position...............................................................................72 Overall Configuration ............................................................................ 72 Mounting onto Carrier Rail .................................................................... 74 Carrier Rail Properties...................................................................... 74 WAGO DIN Rails ............................................................................. 75 Spacing ................................................................................................75 Mounting Sequence..............................................................................76 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 5.6 5.6.1 5.6.2 6.1 6.2 6.2.1 6.2.2 Table of Contents Inserting Devices ..................................................................................77 Inserting the Controller ..................................................................... 77 Inserting the I/O Module ................................................................... 78 Connect Devices .....................................................................................79 Connecting a Conductor to the CAGE CLAMP® ................................... 79 Power Supply Concept ......................................................................... 80 Fuse Protection of the Electronic Circuit Power Supply .................... 80 Supplementary Power Supply Regulations ...................................... 81 Commissioning .......................................................................................82 7.1 7.2 7.3 7.3.1 7.3.2 Switching On the Controller .................................................................. 82 Determining the IP Address of the Host PC .......................................... 83 Setting an IP Address ........................................................................... 84 Assigning an IP Address using DHCP .............................................. 85 Changing an IP Address Using the “CBM” Configuration Tool via the Serial Interface .................................................................................86 7.3.3 Changing an IP Address using “WAGO Ethernet Settings” .............. 89 7.3.4 Temporarily Setting a Fixed IP Address ........................................... 91 7.4 Testing the Network Connection ........................................................... 92 7.5 Changing Standard Passwords ............................................................ 93 7.6 Shutdown/Restart ................................................................................. 94 7.7 Initiating Reset Functions ..................................................................... 95 7.7.1 Warm Start Reset ............................................................................ 95 7.7.1.1 CODESYS 2 Runtime System ..................................................... 95 7.7.1.2 e!RUNTIME Runtime System ...................................................... 95 7.7.2 Cold Start Reset...............................................................................95 7.7.2.1 CODESYS 2 Runtime System ..................................................... 95 7.7.2.2 e!RUNTIME Runtime System ...................................................... 95 7.7.3 Software Reset ................................................................................ 96 7.8 Configuration ........................................................................................97 7.8.1 Configuration via Web-Based-Management (WBM) ......................... 98 7.8.1.1 WBM User Administration............................................................ 99 7.8.1.2 General Information about the Page .......................................... 102 7.8.1.3 “Status Information” Page .......................................................... 105 7.8.1.3.1 “Controller Details” Group ..................................................... 105 7.8.1.3.2 “Network Details (Xn)” Group(s) ............................................ 105 7.8.1.4 “General PLC Runtime Configuration” Page .............................. 106 7.8.1.4.1 “General PLC Runtime Configuration” Group ........................ 106 7.8.1.5 “PLC Runtime Information” Page ............................................... 108 7.8.1.5.1 “PLC Runtime” Group ........................................................... 108 7.8.1.5.2 “Project Details” Group.......................................................... 108 7.8.1.5.3 “Task n” Group(s).................................................................. 109 7.8.1.6 “PLC WebVisu” Page ................................................................ 110 7.8.1.6.1 “Web Server Configuration” Group ........................................ 110 7.8.1.7 “Configuration of Host and Domain Name” Page ....................... 111 7.8.1.7.1 “HostName” Group................................................................ 111 7.8.1.7.2 “Domain Name” Group .......................................................... 111 7.8.1.8 “TCP/IP Configuration” Page ..................................................... 112 7.8.1.8.1 “IP Configuration (Xn)” Group(s) ........................................... 112 7.8.1.8.2 “Default Gateway n” Groups ................................................. 113 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 6 Table of Contents 7.8.1.8.3 7.8.1.9 7.8.1.9.1 7.8.1.9.2 7.8.1.10 7.8.1.10.1 7.8.1.10.2 7.8.1.11 7.8.1.11.1 7.8.1.11.2 7.8.1.11.3 7.8.1.12 7.8.1.12.1 7.8.1.12.2 7.8.1.12.3 7.8.1.13 7.8.1.13.1 7.8.1.13.2 7.8.1.13.3 7.8.1.13.4 7.8.1.14 7.8.1.14.1 7.8.1.15 7.8.1.15.1 7.8.1.16 7.8.1.16.1 7.8.1.16.2 7.8.1.17 7.8.1.17.1 7.8.1.17.2 7.8.1.18 7.8.1.18.1 7.8.1.19 7.8.1.20 7.8.1.21 7.8.1.21.1 7.8.1.21.2 7.8.1.22 7.8.1.22.1 7.8.1.22.2 7.8.1.23 7.8.1.23.1 7.8.1.23.2 7.8.1.24 7.8.1.24.1 7.8.1.24.2 7.8.1.24.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “DNS Server” Group ............................................................. 114 “Ethernet Configuration” Page ................................................... 115 “Switch Configuration” Group ................................................ 115 “Interface Xn” Groups ........................................................... 115 “General Firewall Configuration” Page ....................................... 117 “Global Firewall Parameters” Group ...................................... 117 “Firewall Parameters Interface xxx” Group ............................ 118 “Configuration of MAC Address Filter” Page .............................. 119 “Global MAC Address Filter State” Group ............................. 119 “MAC Address Filter State Xn” Group ................................... 120 “MAC Address Filter Whitelist” Group ................................... 120 “Configuration of User Filter” Page ............................................ 121 “User Filter” Group ................................................................ 121 “User Filter n” Group ............................................................. 121 “Add New User Filter” Group ................................................. 122 “Configuration of Time and Date” Page ..................................... 123 “Date on Device” Group ........................................................ 123 “Time on Device” Group ........................................................ 123 “Time Zone” Group ............................................................... 124 “TZ String” Group .................................................................. 125 “Configuration of the Users for the Web-based Management” Page126 “Change Password for Selected User” Group ....................... 126 “Create Bootable Image” Page .................................................. 127 "Create Bootable Image from Active Partition (" Group .................................................................. 127 “Configuration of Serial Interface RS232” Page ......................... 129 “Serial Interface Assigned to” Group ..................................... 129 “Assign Owner of Serial Interface (Active after Next Controller Reboot)” Group ..................................................................... 129 “Configuration of Service Interface” Page .................................. 130 “Service Interface assigned to” Group ................................... 130 “Assign Owner of Service Interface (enabled after next controller reboot)” Group ....................................................... 130 “Reboot Controller” Page ........................................................... 131 “Reboot Controller” Group..................................................... 131 “Firmware Backup” Page ........................................................... 132 “Firmware Restore” Page .......................................................... 134 “System Partition” Page ............................................................. 136 “Current Active Partition” Group ............................................ 136 “Set Inactive Partition Active” Group ..................................... 136 “Mass Storage” Page................................................................. 137 “ ” Group(s) ................................................... 137 “ - FAT Format” Group(s) ............................. 137 “Software Uploads” Page........................................................... 138 “Upload New Software” Group .............................................. 138 “Activate New Software” Group ............................................. 138 “Configuration of Network Services” Page ................................. 139 “Telnet” Group ...................................................................... 139 “FTP” Group.......................................................................... 139 “FTPS” Group ....................................................................... 139 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table of Contents 7.8.1.24.4 “HTTP” Group ....................................................................... 139 7.8.1.24.5 “HTTPS” Group ..................................................................... 140 7.8.1.24.6 “I/O-CHECK” Group .............................................................. 140 7.8.1.25 “Configuration of NTP Client” Page ........................................... 141 7.8.1.25.1 “NTP Client Configuration” Group ......................................... 141 7.8.1.25.2 “NTP Single Request” Group ................................................ 141 7.8.1.26 “Configuration of PLC Runtime Services” Page ......................... 142 7.8.1.26.1 “General Configuration” Group .............................................. 142 7.8.1.26.2 “CODESYS 2” Group ............................................................ 142 7.8.1.26.3 “e!RUNTIME” Group ............................................................. 142 7.8.1.27 “SSH Server Settings” Page ...................................................... 144 7.8.1.27.1 “SSH Server” Group.............................................................. 144 7.8.1.28 “TFTP Server” Page .................................................................. 145 7.8.1.28.1 “TFTP Server” Group ............................................................ 145 7.8.1.29 “DHCP Configuration” Page ...................................................... 146 7.8.1.29.1 “DHCP Configuration Xn” Group ........................................... 146 7.8.1.30 “Configuration of DNS Service” Page ........................................ 147 7.8.1.30.1 “DNS Service” Group ............................................................ 147 7.8.1.31 “MODBUS Services Configuration” Page .................................. 148 7.8.1.31.1 “MODBUS TCP” Group ......................................................... 148 7.8.1.31.2 “MODBUS UDP” Group ........................................................ 148 7.8.1.32 “Configuration of General SNMP Parameters” Page.................. 149 7.8.1.32.1 “General SNMP Configuration” Group................................... 149 7.8.1.33 “Configuration of SNMP v1/v2c Parameters” Page .................... 150 7.8.1.33.1 “SNMP v1/v2c Manager Configuration” Group ...................... 150 7.8.1.33.2 “Actually Configured Trap Receivers” Group(s) ..................... 150 7.8.1.33.3 “Trap Receiver n” Group(s) ................................................... 151 7.8.1.33.4 “Add New Trap Receiver” Group ........................................... 151 7.8.1.34 “Configuration of SNMP v3 Users” Page ................................... 152 7.8.1.34.1 “Actually Configured v3 Users” Group(s) ............................... 152 7.8.1.34.2 “v3 User n” Group(s) ............................................................. 152 7.8.1.34.3 “Add New v3 User” Group ..................................................... 153 7.8.1.35 “Diagnostic Information” Page ................................................... 154 7.8.1.36 “Configuration of internal 3G Modem” Page .............................. 155 7.8.1.36.1 “SIM Authentication” Group ................................................... 155 7.8.1.36.2 “Mobile Network Configuration” Group .................................. 156 7.8.1.36.3 “Provider List” Group............................................................. 157 7.8.1.36.4 “Network Package Service” Group ........................................ 157 7.8.1.36.5 “Upload and activate new Modem Software” Group .............. 158 7.8.1.37 “Configuration of OpenVPN and IPsec” Page ............................ 159 7.8.1.37.1 “OpenVPN” Group ................................................................ 159 7.8.1.37.2 “IPsec” Group ....................................................................... 159 7.8.1.37.3 “Certificate Upload” Group .................................................... 160 7.8.1.37.4 “Certificate List” Group .......................................................... 160 7.8.1.37.5 “Private Key List” Group ........................................................ 160 7.8.1.38 “Security Settings” Page ............................................................ 161 7.8.1.38.1 “TLS Configuration” Group .................................................... 161 7.8.2 “Open Source Licenses” Page ....................................................... 162 7.8.3 “WAGO Licenses” Page ................................................................. 163 7.8.4 Configuration using a Terminal Program (CBM) ............................. 164 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 8 Table of Contents 7.8.4.1 7.8.4.2 7.8.4.2.1 7.8.4.2.2 7.8.4.3 7.8.4.3.1 7.8.4.3.2 7.8.4.3.3 7.8.4.3.4 7.8.4.3.5 7.8.4.3.6 7.8.4.3.7 7.8.4.3.8 7.8.4.3.9 7.8.4.3.10 7.8.4.3.11 7.8.4.3.12 7.8.4.4 7.8.4.4.1 7.8.4.4.2 7.8.4.4.3 7.8.4.4.4 7.8.4.4.5 7.8.4.4.6 7.8.4.4.7 7.8.4.4.8 7.8.4.4.9 7.8.4.4.10 7.8.4.4.11 7.8.4.4.12 7.8.4.4.13 7.8.4.5 7.8.4.5.1 7.8.4.5.2 7.8.4.5.3 7.8.4.5.4 7.8.4.5.5 7.8.4.5.6 7.8.4.5.7 7.8.4.6 7.8.4.7 7.8.4.7.1 7.8.4.7.2 7.8.4.8 7.8.4.8.1 7.8.4.8.2 7.8.4.8.3 7.8.4.8.4 7.8.4.8.5 7.8.4.8.6 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G CBM Menu Structure Overview ................................................. 164 “Information” Menu .................................................................... 167 “Information” > “Controller Details” Submenu ........................ 167 “Information” > “Network Details” Submenu .......................... 168 “PLC Runtime” Menu ................................................................. 169 “PLC Runtime” > “Information” Submenu .............................. 169 “Information” > “Runtime Version” Submenu ......................... 170 “Information” > “Webserver Version” Submenu ..................... 170 “Information” > “State” Submenu ........................................... 170 “Information” > “Number of Tasks” Submenu ........................ 171 “Information” > “Project Details” Submenu ............................ 171 “Information” > “Tasks” Submenu.......................................... 171 “Tasks” > “Task n” Submenu................................................. 172 “PLC Runtime” > “General Configuration” Submenu ............. 172 “General Configuration” > “PLC Runtime Version” Submenu 173 “General Configuration” > “Home Dir On SD Card” Submenu173 “PLC Runtime” > “WebVisu” Submenu.................................. 174 “Networking” Menu .................................................................... 175 “Networking” > “Host/Domain Name” Submenu .................... 175 “Host/Domain Name” > “Hostname” Submenu ...................... 176 “Host/Domain Name” > “Domain Name” Submenu ............... 176 “Networking” > “TCP/IP” Submenu........................................ 176 “TCP/IP” > “IP Address” Submenu ........................................ 177 “IP Address” > “Xn“ Submenu ............................................... 177 “TCP/IP” > “Default Gateway” Submenu ............................... 178 “Default Gateway” > “Default Gateway n” Submenu.............. 178 “TCP/IP” > “DNS Server” Submenu ...................................... 179 “Networking” > “Ethernet” Submenu...................................... 179 “Ethernet” > “Switch Configuration” Submenu ....................... 180 “Ethernet” > “Ethernet Ports” Submenu ................................. 180 “Ethernet Ports” > “Interface Xn” Submenu ........................... 181 “Firewall” Menu .......................................................................... 182 “Firewall” > “General Configuration” Submenu ...................... 183 “General Configuration” > “Interface xxx” Submenu .............. 184 “Firewall” > “MAC Address Filter” Submenu .......................... 186 “MAC Address Filter” > “MAC address filter whitelist” Submenu187 “MAC address filter whitelist” > “Add new / No (n)” Submenu 187 “Firewall” > “User Filter” Submenu ........................................ 188 “User Filter” > “Add New / No (n)” Submenu ......................... 189 “Clock” Menu ............................................................................. 190 “Administration” Menu ............................................................... 191 “Administration” > “Create Image” Submenu ......................... 192 “Administration” > “Users” Submenu ..................................... 192 “Package Server” Menu ............................................................. 193 “Package Server” > “Firmware Backup” Submenu ................ 193 “Firmware Backup” > “Auto Update Feature” Submenu ........ 194 “Firmware Backup” > “Destination” Submenu........................ 194 “Package Server” > “Firmware Restore” Submenu ............... 195 “Firmware Restore” > “Select Package” Submenu ................ 195 “Package Server” > “System Partition” Submenu .................. 196 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table of Contents 7.8.4.9 7.8.4.9.1 7.8.4.10 7.8.4.11 7.8.4.11.1 7.8.4.11.2 7.8.4.11.3 7.8.4.11.4 7.8.4.11.5 7.8.4.11.6 7.8.4.11.7 7.8.4.11.8 7.8.4.11.9 7.8.4.11.10 7.8.4.11.11 7.8.4.11.12 7.8.4.11.13 7.8.4.11.14 7.8.4.11.15 7.8.4.11.16 7.8.4.11.17 7.8.4.11.18 7.8.4.12 7.8.4.12.1 7.8.4.12.2 7.8.4.12.3 “Mass Storage” Menu ................................................................ 197 “Mass Storage” > “SD Card” Submenu ................................. 197 “Software Uploads” Menu .......................................................... 198 “Ports and Services” Menu ........................................................ 199 “Ports and Services” > “Telnet” Submenu ............................. 200 “Ports and Services” > “FTP” Submenu ................................ 200 “Ports and Services” > “FTPS” Submenu .............................. 201 “Ports and Services” > “HTTP” Submenu .............................. 201 “Ports and Services” > “HTTPS” Submenu ........................... 202 “Ports and Services” > “NTP” Submenu ................................ 202 “Ports and Services” > “SSH” Submenu ................................ 203 “Ports and Services” > “TFTP” Submenu .............................. 203 “Ports and Services” > “DHCPD” Submenu .......................... 204 “DHCPD” > “Xn” Submenu .................................................... 204 “Ports and Services” > “DNS” Submenu................................ 205 “Ports and Services” > “IOCHECK PORT” Submenu ............ 206 “Ports and Services” > “Modbus TCP” Submenu .................. 206 “Ports and Services” > “Modbus UDP” Submenu .................. 207 “Ports and Services” > “PLC Runtime Services” Submenu.... 207 “PLC Runtime Services” > “CODESYS 2” Submenu ............. 208 “PLC Runtime Services” > “e!RUNTIME” Submenu .............. 209 “…” > “Firewall Status” Submenu .......................................... 210 “SNMP” Menu............................................................................ 211 “SNMP” > “General SNMP Configuration” Submenu ............. 211 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu 212 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu .............................................................................. 212 7.8.4.12.4 “SNMP” > “SNMP v3 Configuration” Submenu...................... 213 7.8.4.12.5 “SNMP” > “(Secure)SNMP firewalling” Submenu .................. 214 7.8.5 Configuration using “WAGO ETHERNET Settings” ........................ 215 7.8.5.1 Identification Tab ....................................................................... 217 7.8.5.2 Network Tab .............................................................................. 218 7.8.5.3 Protocol Tab .............................................................................. 220 7.8.5.4 Status Tab ................................................................................. 221 8.1 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.3 8.4 8.4.1 8.4.2 8.4.3 Run-time System CODESYS 2.3........................................................... 222 Installing the CODESYS 2.3 Programming System ............................ 222 First Program with CODESYS 2.3 ...................................................... 222 Start the CODESYS Programming System .................................... 222 Creating a Project and Selecting the Target System ...................... 222 Creating the PLC Configuration ..................................................... 224 Editing the Program Function Block ............................................... 231 Loading and Running the PLC Program in the Fieldbus Controller (ETHERNET) ................................................................................. 233 Creating a Boot Project .................................................................. 235 Syntax of Logical Addresses .............................................................. 235 Creating Tasks ................................................................................... 236 Cyclic Tasks ................................................................................... 239 Freewheeling Tasks ....................................................................... 240 Debugging an IEC Program ........................................................... 240 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 10 Table of Contents WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.5 8.5.1 8.6 8.6.1 8.6.2 8.7 System Events ................................................................................... 244 Creating an Event Handler ............................................................. 247 Process Images .................................................................................. 249 Process Images for I/O Modules Connected to the Controller ........ 251 Process Image for Slaves Connected to the Fieldbus .................... 252 Access to Process Images of the Input and Output Data via CODESYS 2.3 ...................................................................................................... 252 8.8 Addressing Example ........................................................................... 254 8.9 Internal Data Bus Synchronization ...................................................... 255 8.9.1 Case 1: CODESYS Task Interval Set Smaller than the I/O Module Cycle .............................................................................................. 255 8.9.2 Case 2: CODESYS Task Interval Smaller than Twice the Internal Data Bus Cycle .............................................................................. 257 8.9.3 Case 3: CODESYS Task Interval Greater than Twice the Internal Data Bus Cycle .............................................................................. 258 8.9.4 Case 4: CODESYS Task Interval Greater than 10 ms.................... 259 8.9.5 Internal Data Bus Configuration ..................................................... 260 8.9.5.1 Effect of Update Mode on CODESYS Tasks ............................. 261 8.9.5.1.1 Asynchronous Update Mode ................................................. 261 8.9.5.1.2 Synchronous Update Mode ................................................... 262 8.10 Memory Settings in CODESYS........................................................... 262 8.10.1 Program Memory ........................................................................... 262 8.10.2 Data Memory and Function Block Limitation .................................. 264 8.10.3 Remanent Memory ........................................................................ 265 8.11 General Target System Settings ......................................................... 266 8.12 CODESYS Visualization ..................................................................... 266 8.12.1 Limits of CODESYS Visualization .................................................. 269 8.12.2 Eliminating Errors in CODESYS Web Visualization ........................ 271 8.12.3 FAQs about CODESYS Web Visualization .................................... 272 e!RUNTIME Runtime Environment ....................................................... 274 9.1 9.2 9.3 9.3.1 9.3.2 9.3.3 10 General Notes .................................................................................... 274 CODESYS V3 Priorities ...................................................................... 275 Memory Spaces under e!RUNTIME.................................................... 276 Program and Data Memory ............................................................ 276 Function Block Limitation ............................................................... 276 Remanent Memory ........................................................................ 276 MODBUS – CODESYS 2 ........................................................................ 277 10.1 10.2 10.3 10.3.1 10.3.2 10.3.3 10.3.4 10.4 10.4.1 10.4.2 10.4.3 10.4.4 General .............................................................................................. 277 Features ............................................................................................. 277 Configuration ...................................................................................... 278 MODBUS Settings ......................................................................... 279 MODBUS TCP Settings ................................................................. 280 MODBUS UDP Settings ................................................................. 280 MODBUS RTU Settings ................................................................. 280 Data Exchange ................................................................................... 283 Process Image ............................................................................... 284 Flag Area ....................................................................................... 285 MODBUS Registers ....................................................................... 286 MODBUS Mapping ........................................................................ 286 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table of Contents 11 10.4.4.1 10.4.4.2 10.4.4.3 10.4.4.4 MODBUS Mapping for Write Bit Services FC1, FC2 .................. 286 MODBUS Mapping for Write Bit Services FC5, FC15 ................ 287 MODBUS Mapping for Read Register Services FC3, FC4, FC23288 MODBUS Mapping for Write Register Services FC6, FC16, FC22, FC23 ......................................................................................... 290 10.5 WAGO MODBUS Registers................................................................ 292 10.5.1 Process Image Properties .............................................................. 293 10.5.1.1 Register 0x1022 – Number of Registers in the MODBUS Input Process Image .......................................................................... 293 10.5.1.2 Register 0x1023 – Number of Registers in the MODBUS Output Process Image .......................................................................... 293 10.5.1.3 Register 0x1024 – Number of Bits in the MODBUS Input Process Image ........................................................................................ 293 10.5.1.4 Register 0x1025 – Number of Bits in the MODBUS Output Process Image ........................................................................................ 293 10.5.2 Network Configuration.................................................................... 294 10.5.2.1 Register 0x1028 – IP Configuration ........................................... 294 10.5.2.2 Register 0x102A – Number of Established TCP Connections .... 294 10.5.2.3 Register 0x1030 – MODBUS TCP Socket Timeout ................... 294 10.5.2.4 Register 0x1031 – MAC Address for ETHERNET-Interface 1 (eth0)294 10.5.2.5 Register 0x1037 - MODBUS TCP Response Delay ................... 294 10.5.3 PLC Status Register ...................................................................... 295 10.5.4 MODBUS Watchdog ...................................................................... 295 10.5.4.1 Register 0x1100 – Watchdog Command ................................... 297 10.5.4.2 Register 0x1101 – Watchdog Status ......................................... 299 10.5.4.3 Register 0x1102 – Watchdog Timeout ....................................... 299 10.5.4.4 Register 0x1103 – Watchdog Config ......................................... 299 10.5.5 Register 0x1104 – Watchdog Operation Mode ............................... 300 10.5.6 MODBUS Constants Registers ...................................................... 301 10.5.6.1 Electronic Nameplate ................................................................ 301 10.5.6.2 Register 0x2010 – Revision (Firmware Index) ........................... 301 10.5.6.3 Register 0x2011 – Series Designator ........................................ 301 10.5.6.4 Register 0x2012 – Device ID ..................................................... 301 10.5.6.5 Register 0x2013 – Major Firmware Version ............................... 302 10.5.6.6 Register 0x2014 – Minor Firmware Version ............................... 302 10.5.6.7 Register 0x2015 – MBS Version ................................................ 302 10.6 Diagnostics ......................................................................................... 303 10.6.1 Diagnostics for the MODBUS Master ............................................. 303 10.6.2 Diagnostics for the Runtime System .............................................. 303 10.6.3 Diagnostics for the Error Server ..................................................... 303 11 MODBUS – e!RUNTIME ......................................................................... 306 11.1 MODBUS Address Overview .............................................................. 306 11.2 MODBUS Registers............................................................................ 307 11.2.1 MODBUS Watchdog ...................................................................... 309 11.2.1.1 Register 0xFA00 – Watchdog Command................................... 311 11.2.1.2 Register 0xFA01 – Watchdog Timeout ...................................... 312 11.2.1.3 Register 0xFA02 – Watchdog Status ......................................... 312 11.2.1.4 Register 0xFA03 – Watchdog Config ......................................... 313 11.2.1.5 MODBUS TCP Connection Watchdog Register ......................... 314 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 12 Table of Contents WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2.2 Status Registers............................................................................. 315 11.2.2.1 PLC Status Register .................................................................. 315 11.2.3 Electronic Nameplate ..................................................................... 315 11.2.3.1 Order Number ........................................................................... 315 11.2.3.2 Firmware Version ...................................................................... 315 11.2.3.3 Hardware Version ...................................................................... 315 11.2.3.4 Firmware Loader/Boot Loader ................................................... 315 11.2.4 MODBUS Process Image Version.................................................. 315 11.2.5 MODBUS Process Image Registers............................................... 315 11.2.6 Constant Registers ........................................................................ 316 11.2.7 Live Register .................................................................................. 316 11.3 Estimating the MODBUS Master CPU Load ....................................... 317 12 Diagnostics............................................................................................ 318 12.1 12.1.1 12.1.2 12.1.3 12.2 12.2.1 12.2.2 12.2.3 12.2.4 13 Service ................................................................................................... 336 13.1 13.1.1 13.1.2 13.2 13.2.1 13.2.2 13.3 13.3.1 13.3.2 13.3.3 14 Inserting and Removing the Memory Card.......................................... 336 Inserting the Memory Card ............................................................. 336 Removing the Memory Card .......................................................... 336 Inserting and Removing the SIM Card ................................................ 338 Inserting the SIM Card ................................................................... 338 Removing the SIM Card ................................................................. 338 Firmware Changes ............................................................................. 339 Perform Firmware Upgrade ............................................................ 339 Perform Firmware Downgrade ....................................................... 340 Factory Reset ................................................................................ 341 Removal ................................................................................................. 342 14.1 14.1.1 14.1.2 15 Operating and Status Messages......................................................... 318 Power Supply Indicating Elements ................................................. 318 Mobile Radio Network Status Indicators ......................................... 319 Fieldbus/System Indicating Elements............................................. 320 Diagnostics Messages via Flashing Sequences ................................. 327 Flashing Sequences ...................................................................... 327 Example of a Diagnostics Message Indicated by a Flashing Sequence....................................................................................... 329 Meaning of Blink Codes and Procedures for Troubleshooting ........ 330 Meaning of Blink Codes and Procedures for Troubleshooting ........ 335 Removing Devices.............................................................................. 342 Removing the Controller ................................................................ 342 Removing the I/O Module .............................................................. 343 Appendix ............................................................................................... 344 15.1 Structure of Process Data for the I/O Modules .................................... 344 15.1.1 Digital Input Modules...................................................................... 345 15.1.1.1 1 Channel Digital Input Module with Diagnostics ....................... 345 15.1.1.2 2 Channel Digital Input Modules ................................................ 345 15.1.1.3 2 Channel Digital Input Module with Diagnostics ....................... 345 15.1.1.4 2 Channel Digital Input Module with Diagnostics and Output Process Data ............................................................................. 346 15.1.1.5 4 Channel Digital Input Modules ................................................ 346 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table of Contents 13 15.1.1.6 15.1.1.7 8 Channel Digital Input Modules ................................................ 346 8 Channel Digital Input Module PTC with Diagnostics and Output Process Data ............................................................................. 347 15.1.1.8 16 Channel Digital Input Modules .............................................. 347 15.1.2 Digital Output Modules ................................................................... 348 15.1.2.1 1 Channel Digital Output Module with Input Process Data ......... 348 15.1.2.2 2 Channel Digital Output Modules ............................................. 348 15.1.2.3 2 Channel Digital Input Modules with Diagnostics and Input Process Data ............................................................................. 349 15.1.2.4 4 Channel Digital Output Modules ............................................. 350 15.1.2.5 4 Channel Digital Output Modules with Diagnostics and Input Process Data ............................................................................. 350 15.1.2.6 8 Channel Digital Output Module ............................................... 350 15.1.2.7 8 Channel Digital Output Modules with Diagnostics and Input Process Data ............................................................................. 351 15.1.2.8 16 Channel Digital Output Modules ........................................... 351 15.1.2.9 8 Channel Digital Input/Output Modules .................................... 352 15.1.3 Analog Input Modules .................................................................... 353 15.1.3.1 1 Channel Analog Input Modules ............................................... 353 15.1.3.2 2 Channel Analog Input Modules ............................................... 353 15.1.3.3 4 Channel Analog Input Modules ............................................... 354 15.1.3.4 3-Phase Power Measurement Module ....................................... 355 15.1.3.5 8 Channel Analog Input Modules ............................................... 355 15.1.4 Analog Output Modules.................................................................. 356 15.1.4.1 2 Channel Analog Output Modules ............................................ 356 15.1.4.2 4 Channel Analog Output Modules ............................................ 356 15.1.5 Specialty Modules .......................................................................... 357 15.1.5.1 Counter Modules ....................................................................... 357 15.1.5.2 Pulse Width Modules ................................................................. 359 15.1.5.3 Serial Interface Modules with alternative Data Format ............... 359 15.1.5.4 Serial Interface Modules with Standard Data Format ................. 360 15.1.5.5 Data Exchange Module ............................................................. 360 15.1.5.6 SSI Transmitter Interface Modules ............................................ 360 15.1.5.7 Incremental Encoder Interface Modules .................................... 361 15.1.5.8 DC-Drive Controller ................................................................... 363 15.1.5.9 Stepper Controller ..................................................................... 364 15.1.5.10 RTC Module .............................................................................. 365 15.1.5.11 DALI/DSI Master Module ........................................................... 365 15.1.5.12 DALI Multi-Master Module ......................................................... 366 15.1.5.13 LON® FTT Module ..................................................................... 368 15.1.5.14 EnOcean Radio Receiver .......................................................... 368 15.1.5.15 MP Bus Master Module ............................................................. 368 15.1.5.16 Bluetooth® RF-Transceiver ........................................................ 369 15.1.5.17 Vibration Velocity/Bearing Condition Monitoring VIB I/O ............ 370 15.1.5.18 KNX/EIB/TP1 Module ................................................................ 370 15.1.5.19 AS-interface Master Module ...................................................... 371 15.1.6 System Modules ............................................................................ 373 15.1.6.1 System Modules with Diagnostics ............................................. 373 15.1.6.2 Binary Space Module ................................................................ 373 15.2 CODESYS 2 Libraries ........................................................................ 374 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 14 Table of Contents WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.2.1 General Libraries ........................................................................... 374 15.2.1.1 CODESYS System Libraries ..................................................... 374 15.2.1.2 SysLibCom.lib ........................................................................... 375 15.2.1.3 SysLibFile.lib ............................................................................. 375 15.2.1.4 SysLibFileAsync.lib.................................................................... 376 15.2.1.5 SysLibRtc.lib.............................................................................. 377 15.2.1.6 BusDiag.lib ................................................................................ 378 15.2.1.7 mod_com.lib .............................................................................. 378 15.2.1.8 SerComm.lib.............................................................................. 378 15.2.1.9 WagoConfigToolLIB.lib .............................................................. 379 15.2.1.10 WagoLibCpuUsage.lib ............................................................... 395 15.2.1.11 WagoLibDiagnosticIDs.lib .......................................................... 395 15.2.1.12 WagoLibLed.lib.......................................................................... 396 15.2.1.13 WagoLibNetSnmp.lib ................................................................. 396 15.2.1.14 WagoLibNetSnmpManager.lib ................................................... 396 15.2.1.15 WagoLibSSL.lib ......................................................................... 397 15.2.1.16 WagoLibTerminalDiag.lib........................................................... 397 List of Figures ................................................................................................ 398 List of Tables .................................................................................................. 401 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Notes about this Documentation 15 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 750-8207 750-8207/025-000 Designation PFC200 CS 2ETH RS 3G 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.06.20(09). 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 16 1.3 Notes about this Documentation WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Notes about this Documentation 17 Additional Information: Refers to additional information which is not an integral part of this documentation (e.g., the Internet). Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 18 1.4 Notes about this Documentation Number Notation Table 2: Number Notation Number Code Decimal Hexadecimal Binary 1.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Example 100 0x64 '100' '0110.0100' Note Normal notation C notation In quotation marks, nibble separated with dots (.) Font Conventions Table 3: Font Conventions Font Type italic Menu Input “Value” [Button] [Key] Indicates Names of paths and data files are marked in italic-type. e.g.: C:\Program Files\WAGO Software Menu items are marked in bold letters. e.g.: Save A greater-than sign between two names means the selection of a menu item from a menu. e.g.: File > New Designation of input or optional fields are marked in bold letters, e.g.: Start of measurement range Input or selective values are marked in inverted commas. e.g.: Enter the value “4 mA” under Start of measurement range. Pushbuttons in dialog boxes are marked with bold letters in square brackets. e.g.: [Input] Keys are marked with bold letters in square brackets. e.g.: [F5] Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Important Notes 19 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 WAGOI/O-SYSTEM 750 in hazardous environments. Please note that a prototype test Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 20 Important Notes WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G certificate must be obtained that confirms the correct installation of the system in a housing or switch cabinet. 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. WAGO Kontakttechnik GmbH & Co. KG will be exempted from any liability in case of changes in hardware or software as well as to non-compliant usage of devices. Please send your request for modified and new hardware or software configurations directly to WAGO Kontakttechnik GmbH & Co. KG. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 2.2 Important Notes 21 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 22 Important Notes WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Clean only with permitted materials! Clean soiled contacts using oil-free compressed air or with ethyl alcohol and leather cloths. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 2.4 Important Notes 23 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 support@wago.com 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 24 Device Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. “Indicating element power supply” Data contacts “Connections” > “Data contacts/Internal data bus” CAGE CLAMP® Connections for Power Supply “Connections” > “CAGE CLAMP® connections” Slot for memory card “Memory card slot” Slot for SIM card “SIM card slot” Releasing strap “Mounting” > “Inserting and Removing Device” Power contacts for power supply of down-circuit I/O modules “Connections” > “Power contacts/ Field-side supply” Mobile radio antenna connection “Connections” > “Mobile radio antenna communication” 10 Service Interface (behind the flap) “Connections” > “Service interface” Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 28 Device Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Mode selector switch “Operating elements” > “Mode selector switch” 12 ETHERNET Connections “Connections” > “Network connections ETHERNET – X1, X2” 13 Safe Locking Feature “Mounting” > “Inserting and Removing Device” 14 Serial interface “Connections” > “Communication port RS232/RS-485 – X3” 15 LED Indicators – System “Indicating elements” > “Indicating elements Fieldbus/System” 16 Reset button (in hole) “Operating elements” > “Reset button” 17 LED indicators – Mobile radio network status "Indicating elements" > "Indicating elements Fieldbus/System" 11 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.2 Device Description 29 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 WW Calendar week 14 YY Year 01 01 01 FW -HW FL Firmware Hardware Firmware version version loader version (additional positions) Internal information 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 30 Device Description 3.3 Connectors 3.3.1 Data Contacts/Internal Bus WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 internal data bus, which consists of 6 data contacts designed as self-cleaning gold spring contacts. Figure 3: Data Contacts Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.3.2 Device Description 31 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 Spring contact Spring contact Spring contact Function Potential transmission (UV) for field supply Potential transmission (0 V) for field supply Potential transmission (ground) 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 32 Device Description 3.3.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G CAGE CLAMP® Connectors ® Figure 5: CAGE CLAMP connections ® Table 6: Legend for figure “CAGE CLAMP connections” Contact Description 24 V Ground 0V Ground Description System power supply voltage +24 V Field-side power supply voltage UV Field-side power supply voltage 0 V Field-side power supply voltage, ground System power supply voltage 0 V Field-side power supply voltage UV Field-side power supply voltage 0 V Field-side power supply voltage, ground … > “Supplementary Power Supply Regulations”! Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.3.4 Device Description 33 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 Open flap 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 34 Device Description 3.3.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Network Connections – X1, X2 Figure 7: Network Connections – X1, X2 Table 8: Legend for Figure “Network Connections – X1, X2” Contact Signal TD + TD − RD + NC NC RD − NC NC Description Transmit Data + Transmit Data − Receive Data + Not assigned Not assigned Receive Data − Not assigned Not assigned Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Device Description 35 Kommuni kati onsansc hlus s 3.3.6 RS-232/RS-485 – X3 Communication Connection Figure 8: RS-232/RS-485 – X3 Communication Connection Table 9: Legend for Figure “RS-232/RS-485 – X3 Communication Connection” Contact Signal NC RxD TxD NC FB_GND NC RTS CTS NC Enclosure Shield RS-232 Description Not assigned Receive Data Transmit Data Signal NC NC RxD/TxD-P Not assigned Ground Not assigned Request to send Clear to send NC FB_GND FB_5V NC RxD/TxD-N Not assigned Shielding NC Shield RS-485 Description Not assigned Not assigned Receive/transmit data Not assigned Ground Power Supply Not assigned Receive/transmit data − Not assigned 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 36 Device Description 3.3.6.1 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Operating as an RS-232 Interface 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 Contact Signal RxD TxD FB_GND RTS CTS Data Direction DTE DCE Input Output Output Input ----Output Input 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.3.6.2 Device Description 37 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 38 Device Description 3.3.7 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Mobile Radio Antenna 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Device Description 3.4 Display Elements 3.4.1 Power Supply Indicating Elements 39 Figure 13: Power Supply Indicating Elements Table 11: Legend for Figure “Power Supply Indicating Elements” Description Color Green/off Green/off Description Status of system power supply voltage Status of field-side power supply voltage Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 40 Device Description 3.4.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Fieldbus/System Indicating Elements Figure 14: Indicating elements for fieldbus/system Table 12: Legend for Figure “Fieldbus/System Indicating Elements” Description Color Description SYS Red/Green/ Orange/Off System status RUN Red/Green/ Orange/Off PLC program status I/O Red/Green/ Orange/Off Internal data bus status MS Red/Green/ Orange/Off Module status NS Red/Green/ Orange/Off Without function USR Red/Green/ Orange/Off User LED, programmable using function blocks from the WAGO libraries to control the LEDs ▐██ Red/Green/ Orange/Off Signal quality (S5) ██ Red/Green/ Orange/Off Signal quality (S4) ▐█ Red/Green/ Orange/Off Signal quality (S3) █ Red/Green/ Orange/Off Signal quality (S2) ▐ Red/Green/ Orange/Off Signal quality (S1) NET Red/Green/ Orange/Off Network status Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.4.3 Device Description 41 Memory Card Indicating Elements Figure 15: Indicating Elements, Memory Card Slot Table 13: Legend for Figure “Indicating Elements, Memory Card Slot” Description SD Color Yellow/Off Description Memory card status Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 42 Device Description 3.4.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Network Indicating Elements Figure 16: Indicating Elements, RJ-45 Jacks Table 14: Legend for Figure “Indicating Elements, RJ-45 Jacks” Description LNK ACT Color Green/Off Yellow/Off Description ETHERNET connection status ETHERNET data exchange Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.4.5 Device Description 43 Mobile Radio Network Status Indicators Figure 17: Mobile Radio Network Status Indicators Table 15: Legend for the “Mobile Radio Network Status Indicators” Figure Description CON Color Green/off Description Mobile radio network status Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 44 Device Description WAGO-I/O-SYSTEM 750 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 “Initiating Reset Functions”) “Initiating Reset Functions”) Other functions can also be initiated using the reset button. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.5.2 Device Description 45 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 46 3.6 Device Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. “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 flatrate deal with reduced data rates when the inclusive volume covered by the flatrate tariff is exceeded and/or a tariff with a texting package. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 48 3.8 Device Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Schematic Diagram Figure 22: Schematic diagram Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.9 Technical Data 3.9.1 Device Data Table 19: Technical Data − Device Data Width Height (from upper edge of DIN 35 rail) Length Weight Device Description 49 103 mm 65 mm 100 mm 288 g … > "Flag Area") 32,000 words 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! 3.9.8 Serial interface Table 26: Technical Data – Serial Interface Interface Protocols 3.9.9 Mobile Radio Modem Table 27: Technical Data – Mobile Radio Modem Technology SIM card type / slot Communication Communication types 3.9.10 1 x serial interface per TIA/EIA 232 and TIA/EIA 485 (switchable), 9-pole D-sub female connector MODBUS RTU GSM / Edge / UMTS / HSPA+ Mini SIM, push-push mechanism Quad band SMS (bidirectional), GPRS connection to the Internet Connection Type Table 28: Technical Data – Field Wiring Wire connection Cross section Stripped lengths CAGE CLAMP® 0.08 mm² … 2.5 mm², AWG 28 … 14 8 mm … 9 mm / 0.33 in Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 52 Device Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 29: Technical Data – Power Jumper Contacts Power jumper contacts Table 30: Technical Data – Data Contacts Data contacts 3.9.11 Spring contact, self-cleaning Slide contact, hard gold plated, selfcleaning Climatic Environmental Conditions Table 31: Technical Data – Climatic Environmental Conditions Operating temperature range Operating temperature range for components with extended temperature range (750-xxx/025-xxx) Storage temperature range Storage temperature range for components with extended temperature range (750-xxx/025-xxx) Relative humidity Resistance to harmful substances 0 °C … 55 °C −20 °C … +60 °C Maximum pollutant concentration at relative humidity < 75 % SO2 ≤ 25 ppm H2S ≤ 10 ppm Ensure that additional measures for components are taken, which are used in an environment involving: – dust, caustic vapors or gases – ionizing radiation Special conditions −25 °C … +85 °C −40 °C … +85 °C Max. 5 % … 95 % without condensation Acc. to IEC 60068-2-42 and IEC 60068-2-43 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3.10 Device Description 53 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. 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 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 54 Device Description EMC CE-Emission of interference WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G EN 61000-6-3 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 55 Function Description …> “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 56 Function Description 4.1.2 Network Security 4.1.2.1 Users and Passwords WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. user admin root Web Based Management (WBM) Linux® console Console Based Management (CBM) CODESYS Telnet FTP FTPS SSH SNMP user Service admin WBM Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) SNMP Users Linux® WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 57 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 admin user guest Permissions All (administrator) Supported to a limited extent Display only Default Password wago user --- 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.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 root admin user Special Feature Super user CODESYS user Normal user Home Directory /root /home/admin /home/user Default Password wago wago user 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.4 SNMP User Group The SNMP service manages its own users. In its initial state, no users are stored in the system. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 58 Function Description 4.1.2.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 59 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 60 Function Description WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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.3.2 Default Gateways In the TCP/IP configuration, the controller allows the setting of two default gateways. A network station transmits to a default 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. The default gateways are assigned a so-called metric which specifies the time delay, sometimes called the cost factor, with which a data packet can be routed via the gateway. If multiple default gateways are configured, the operating system transmits the data packets to the default gateway configured with the lowest metric. If this gateway is not accessible, an attempt is made to access the gateway with the next higher metric. The gateway is determined randomly if multiple gateways have the same metric. If this gateway cannot transmit the data packet, the data packet is sent simultaneously to all other gateways of the same metric. The metric of the configured default gateways can be set for the controller. The default value for the metric is 20. Besides the directly configured gateways, other gateways can be set via DHCP responses so that more than two gateways are possible. All gateways transferred via DHCP are assigned a permanent metric of 10. The DHCP gateways are thus normally given priority on account of their low metric. The entries for Destination Address und Destination Mask make it possible to define a complete route. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 61 There are two possibilities here: 1. Default Route If the “default” value is entered in the Destination Address field, a default route is defined. The Destination Mask field must then have the value “0.0.0.0.” 2. Route If an IP address or an address pool is entered in the Destination Address field, all data is sent to the IP address or the address pool via the entered gateway address. The gateway metric here has an important function. This determines the costs of the connection. For example, if two identical address pools are defined (192.168.1.0/24) [IP:192.168.1.1-192.168.1.254], one with a metric of 20 and the second with 192.168.1.2 and a metric of 10, the gateway with the lowest metric is used. If the address 192.168.1.2 in the above example is no longer available, e.g., due to failure, the alternative route is used automatically. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 62 Function Description 4.1.4 Network Services 4.1.4.1 DHCP Client WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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.4.2 DHCP Server The controller provides the DHCP server service for the automatic configuration of IP addresses of network stations on the same subnet. Generally, only one DHCP server can be active on a subnet at one time. The following can be set for the DHCP server: The service itself (active/not active) The range of dynamically assigned IP addresses The lease time of the dynamically assigned IP addresses A list with static assignments of IP addresses to MAC addresses In “switched” mode, these settings are possible for both interfaces together and in “separated” mode for each interface separately. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 63 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 IP address Subnet mask Broadcast address Lease time Host name Name server Default gateway Explanation 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. 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. IP address with which an IP packet can be sent to all network subscribers on the subnet at the same 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. 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. The DHCP server passes its own IP address as the DNS name server to the network subscriber. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 64 Function Description WAGO-I/O-SYSTEM 750 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.4.3 DNS Server The controller offers the DNS server service for the automatic assignment of hostnames to IP addresses of network stations. The DNS server takes over the names and IP addresses of local network stations from the DHCP server. This DNS server routes requests for non-local names, such as from the Internet, to higher-level DNS servers if configured and accessible. The following settings are possible for the DNS server: The service itself (enabled/disabled) Access type to the assignments The requests are buffered in “Proxy” mode (throughput optimized). In Relay mode the requests are routed directly to higher-level name servers. A list with up to 15 static assignments of IP addresses to hostnames If only the hostname is used, the configured or default domain is added to the hostname automatically to ensure FQDN name resolution. The settings are made, e.g., in the WBM, via the “Configuration of DNS Service” page. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4.2 Function Description 65 Memory Card Function “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4.2.2 Function Description 67 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 68 Function Description WAGO-I/O-SYSTEM 750 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Function Description 69 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 70 Function Description 4.2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4.2.5 Function Description 71 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. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 72 Mounting WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Mounting 73 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 74 Mounting WAGO-I/O-SYSTEM 750 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 electromagnetic disturbances. In order to avoid corrosion, this tin-plated carrier rail contact must not form a galvanic cell with the material of the carrier rail which generates a differential voltage above 0.5 V (saline solution of 0.3 % at 20°C). • The carrier rail must optimally support the EMC measures integrated into the system and the shielding of the 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 5.3.2 Mounting 75 WAGO DIN Rails WAGO carrier rails meet the electrical and mechanical requirements shown in the table below. Table 35: WAGO DIN Rails Item No. 210-112 210-113 210-197 210-114 210-118 210-198 210-196 Description 35 × 7.5; 1 mm; steel; bluish, tinned, chromed; slotted 35 × 7.5; 1 mm; steel; bluish, tinned, chromed; unslotted 35 × 15; 1.5 mm; steel; bluish, tinned, chromed; slotted 35 × 15; 1.5 mm; steel; bluish, tinned, chromed; unslotted 35 × 15; 2.3 mm; steel; bluish, tinned, chromed; unslotted 35 × 15; 2.3 mm; copper; unslotted 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 23: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 76 5.5 Mounting WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. Risk of injury due to sharp-edged blade contacts! The blade contacts are sharp-edged. Handle the I/O module carefully to prevent 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/OSYSTEM 750 fieldbus couplers/controllers to guarantee proper data transfer. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 5.6 Mounting 77 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 24: Release Tab of Controller Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 78 Mounting 5.6.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Inserting the I/O Module 1. Position the I/O module so that the tongue and groove joints to the fieldbus coupler/controller or to the previous or possibly subsequent I/O module are engaged. Figure 25: Insert I/O Module (Example) 2. Press the I/O module into the assembly until the I/O module snaps into the carrier rail. Figure 26: Snap the I/O Module into Place (Example) With the I/O module snapped in place, the electrical connections for the data contacts and power jumper contacts (if any) to the fieldbus coupler/controller or to the previous or possibly subsequent I/O module are established. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Connect Devices Connect Devices 6.1 Connecting a Conductor to the CAGE CLAMP® 79 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 feedthrough 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 27: Connecting a Conductor to a CAGE CLAMP Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 80 Connect Devices WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 6.2 Power Supply Concept 6.2.1 Fuse Protection of the Electronic Circuit Power Supply Only implement the electronic circuit power supply with a suitable fuse! The electronic power supply of the controller must only be connected via a slow blow 2A fuse, as shown in the following figure. The electronics may be damaged with higher currents. Figure 28: Fuse Protection of the Electronic Circuit Power Supply Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 6.2.2 Connect Devices 81 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 36: Filter Modules for 24 V Supply Order No. 750-626 750-624 Name Description 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) Supply Filter Filter module for the 24 V field supply (750-602, 750-601, 750-610) Therefore, the following power supply concept must be absolutely complied with. Figure 29: Power Supply Concept Use a supply module for equipotential bonding! Use an additional 750-601/ 602/ 610 Supply Module behind the 750-626 Filter Module if you want to use the lower power jumper contact for equipotential bonding, e.g., between shielded connections and require an additional tap for this potential. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 82 Commissioning Commissioning 7.1 Switching On the Controller WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.2 Commissioning 83 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 84 7.3 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 37: Default IP Addresses for ETHERNET Interfaces Ethernet interface X1/X2 Default setting 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 38: Network Mask 255.255.255.0 Host PC 192.168.1.2 Subnet address range for the controller 192.168.1.3 … 192.168.1.254 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.3.1 Commissioning 85 Assigning an IP Address using DHCP The Controller can obtain dynamic IP addresses from a server (DHCP/BootP). In contrast to fixed IP addresses, dynamically assigned addresses are not stored permanently. Therefore, a BootP or DHCP server must be available each time the controller is restarted. If an IP address has been assigned by means of DHCP (default setting), it can be determined through the settings and the output of the specific DHCP server. In the example figure shown here, the corresponding output of “Open DHCP” is presented. Figure 30: “Open DHCP”, Example Figure In conjunction with the DNS server associated with DHCP, the device can be reached using its host name. This name consists of the prefix “PFCx00-“ and the last six places of the MAC address (in the example shown here: “00:30:DE:FF:00:5A”). The MAC address of the device can be printed on the label on the side of the device. The host name of the device in the example shown here is thus “PFC200FF005A”. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 86 Commissioning 7.3.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 31: CBM Starting Screen Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4. Commissioning 87 In the Main menu use the keyboard (arrow keys or numeric keypad) to move to and select Networking and then press [Enter]. Figure 32: CBM – Selecting “Networking” 5. In the Networking menu select TCP/IP and press [Enter]. Figure 33: CBM – Selecting “TCP/IP” 6. In the menu TCP/IP select IP Address and press [Enter]. Figure 34: CBM – Selecting “IP address” Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 88 Commissioning 7. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G In the menu TCP/IP Configuration select IP Address and press [Enter]. Figure 35: 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 36: CBM – Entering a New IP Address Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.3.3 Commissioning 89 Changing an IP Address using “WAGO Ethernet Settings” The Microsoft Windows® application “WAGO Ethernet Settings” is a software used to identify the controller and configure network settings. Observe the software version! To configure the controller use at least Version 6.4.1.1 dated 2015-06-29 of “WAGO Ethernet Settings”! You can use WAGO communication cables or WAGO radio adapters or even the IP network for data communication. 1. Switch off the power supply to the controller. 2. Connect the 750-920 communication cable to the Service interface on the controller and to a serial interface of your PC. 3. Switch the power supply to the controller on again. 4. Start the “WAGO Ethernet Settings” program. Figure 37: “WAGO Ethernet Settings” – Starting Screen (Example) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 90 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 5. Click [Identify] to read in and identify the connected controller. 6. Select the “Network” tab: Figure 38: “WAGO Ethernet Settings” – “Network” Tab 7. To assign a fixed address, select “Static configuration” on the “Source” line under “Input”. DHCP is normally activated as the default setting. 8. In the column “Input” enter the required IP address and, if applicable, the address of the subnet mask and of the gateway. 9. Click on [Write] to accept the address in the controller. (If necessary, “WAGO Ethernet Settings” will restart your controller. This action may require about 30 seconds.) 10. You can now close “WAGO Ethernet Settings”, or make other changes directly in the Web-based Management system as required. To do this, click on [WBM] at the right in the window. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 91 Execute… > Open: (Windows® XP) or Start > Search programs/files (Windows® 7) and then click [OK] or press [Enter]. 2. In the MS DOS window, enter the command “ping” and the IP address of the controller (for example, ping 192.168.1.17)and then press [Enter]. Host entries in the ARP table! It may also be useful to delete the current host entries in the ARP table with the command “arp -d *” before executing the “ping” command (as administrator in Windows® 7). This ensures that older entries will not impair the success of the “ping” command. 3. Your PC sends out a query that is answered by the controller. This reply appears in the MS DOS prompt window. If the error message “Timeout” appears, the controller has not responded properly. You then need to check your network settings. Figure 39: Example of a Function Test 4. If the test is completed successfully, close the MS DOS window. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.5 Commissioning 93 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 94 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 95 “WagoConfigToolLIB.lib”) • Access via the PC using “WAGO Ethernet Settings” (“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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 98 Commissioning 7.8.1 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 to the pre-set address “192.168.1.17” using the “Fixed IP address” function (see Section “Initiate Reset Functions” > “Set 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 99 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 40: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 100 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Figure 41: Password Reminder Table 39: User Settings in the Default State Users user admin Password user 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 40: Access Rights for WBM Pages Navigation Information PLC Runtime – Information – General Configuration – WebVisu Networking – Host/Domain Name – TCP/IP – Ethernet Firewall – General Configuration – MAC Address Filter – User Filter Clock Administration – Users – Create Image – Serial Interface – Service Interface WBM page Status Information User guest PLC Runtime Information General PLC Runtime Configuration PLC WebVisu guest user guest Configuration of Host and Domain Name TCP/IP Configuration Ethernet Configuration user user user General Firewall Configuration Configuration of MAC Address Filter Configuration of User Filter Configuration of Time and Date user user user user Configuration of the users for the Webbased Management Create bootable Image Configuration of Serial Interface RS233 Configuration of Service Interface admin Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) admin admin admin WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 101 Table 40: Access Rights for WBM Pages Navigation – Reboot Package Server – Firmware Backup – Firmware Restore – System Partition Mass Storage Software Uploads Ports and Services – Network Services – NTP Client – PLC Runtime Services – SSH – TFTP – DHCP – DNS – MODBUS SNMP – General Configuration WBM page Reboot Controller User admin Firmware Backup Firmware Restore System Partition Mass Storage Software Uploads admin admin admin admin admin Configuration of Network Services Configuration of NTP Client Configuration of PLC Runtime Services SSH Server Settings TFTP Server DHCP Configuration Configuration of DNS Service MODBUS Services Configuration user user user user user user user user Configuration of general SNMP parameters Configuration of SNMP v1/v2c parameters Configuration of SNMP v3 Users Diagnostic Information Configuration of internal 3G Modem Configuration of OpenVPN / IPsec Security Settings admin – SNMP v1/v2c – SNMP v3 Diagnostic Modem OpenVPN / IPsec Security Legal Information – Open Source Licenses Open Source Licenses – WAGO Licenses WAGO Licenses admin admin guest admin admin admin guest guest Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 102 Commissioning 7.8.1.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G General Information about the Page Figure 42: 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. A status area with the following elements is displayed on the right: Figure 43: WBM Status Information (Example) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 103 • 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. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 104 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.1.3 Commissioning 105 “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 41: WBM “Status Information” Page – “Controller Details” Group Parameter Product Description Order Number License Information Firmware Revision Explanation Controller identification Item number of the controller Notification that the CODESYS runtime system is available 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 42: WBM “Status Information Page – “Network Details (Xn)” Group(s) Parameter State Mac Address IP Address Subnet Mask Explanation Status of the ETHERNET interface (enabled/disabled) MAC address identifies and addresses the controller Current IP address of the controller and (in brackets) the reference type (static/bootp/dhcp) Current subnet mask of the controller Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 106 Commissioning 7.8.1.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 43: WBM “General PLC Runtime Configuration” Page – “General PLC Runtime Configuration” Group Parameters Explanation 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 the internal memory. card enabled 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 107 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 108 Commissioning 7.8.1.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 44: WBM “PLC Runtime Information” Page – “PLC Runtime” Group Parameters Version Web Server Version State Number of Tasks Explanation The version of the currently activated runtime system is shown here. 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. 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 system. STOP PLC program is not executed. RUN PLC program is executed. The number of tasks in the PLC program is shown. 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 45: WBM “PLC Runtime Information” Page – “Project Details” Group Parameters Date Title Version Author Description Explanation Display of project information that the programmer entered in the PLC program (in programming software under Project > Project Information...). The information only appears when a PLC program is run. Descriptive texts up to 1024 characters long are given under “Description.” Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 109 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 46: WBM “PLC Runtime Information” Page – “Task n” Group(s) Parameters Cycle count Cycle time (µsec) Cycle time min (µsec) Cycle time max (µsec) Cycle time avg (µsec) Status Mode Priority Interval (msec) Explanation Number of task cycles since the system start Currently measured task cycle time for the task Minimum task cycle time for the task since the system start Maximum task cycle time for the task since the system start Average task cycle time since the system start Task status (e.g., RUN, STOP) Task execution mode (e.g., in cycles) Set task priority Set task interval To hide this information, click [–]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 110 Commissioning 7.8.1.6 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 47: WBM “PLC WebVisu” Page – “Web Server Configuration” Group Parameters CODESYS 2 Webserver State e!RUNTIME Webserver State Default Webserver Explanation This indicates the status (enabled/disabled) of the CODESYS 2 web server. This indicates the status (enabled/disabled) of the 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. 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:// /wbm” and the web visualization with “https:// /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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.1.7 Commissioning 111 “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 48: WBM “Configuration of Host and Domain Name” Page – “Hostname” Group Parameters Currently used Configured Explanation If you have selected dynamic assignment of an IP 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 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 49: WBM “Configuration of Host and Domain Name” Page – “Domain Name” Group Parameters Currently used Configured Explanation The domain name currently used is displayed. It may differ from the configured domain name if you have selected dynamic assignment of an IP address via DHCP or BootP. Enter the domain name. The default entry is “localdomain.lan”. Click [Submit] to apply the change. The change is effective immediately. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 112 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G ?@[\^_`{|}~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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 127 " Group The active partition that boot-up was performed from is displayed in brackets in the heading. Table 68: WBM “Create Bootable Image” page – “Create bootable image from active partition” Group Parameters Destination Size of created image Explanation 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 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. 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. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 128 Commissioning WAGO-I/O-SYSTEM 750 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 129 ” Group(s) Table 73: WBM “Mass Storage” Page – “ ” Group Parameters Device Volume name Explanation The name of the storage volume in the operating system file system is displayed here. The name of the storage volume is displayed here. 7.8.1.22.2 “ - FAT Format” Group(s) Table 74: WBM “Mass Storage” Page – “ ” Group Parameters Volume Name Explanation Specify the name for the storage volume when 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 138 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G | , Explanation All available providers with the respective network, 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.36.4 “Network Package Service” Group Table 105: WBM “Configuration of internal 3G Modem” Page – “Network Package Service” Group Parameters State APN User Password Authentication Type Explanation The registry state of the “Network Package Service” is displayed. Enter the APN access point (Access Point Name) of the SIM card provider. Enter the user name for the access point of the SIM card provider. Enter the password for the access point of the SIM card provider. Select the authentication type: None No authentication Password Authentication PAP Protocol Challenge Handshake CHAP Authentication Protocol When possible, the secure CHAP PAP or CHAP is used, otherwise PAP. Click on [Submit] to accept the changes. The changes will be effective immediately. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 158 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.1.36.5 “Upload and activate new Modem Software” Group Table 106: WBM “Configuration of internal 3G Modem” Page – “Upload and activate new Modem Software” Group Parameters Currently used New Software Explanation The current modem firmware version is displayed. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.1.37 Commissioning 159 “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.37.1 “OpenVPN” Group Table 107: WBM “Configuration of OpenVPN and IPsec” Page – “OpenVPN” Group Parameters Current State OpenVPN enabled openvpn.config Explanation The current status of the OpenVPN service is displayed. stopped The service is disabled. running The service is enabled. Enable or disable the OpenVPN service. Select an OpenVPN configuration file to be 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 the WBM reboot function. Do not shut down the controller too early! 7.8.1.37.2 “IPsec” Group Table 108: WBM “Configuration of OpenVPN and IPsec” Page – “IPsec” Group Parameters Current State IPsec enabled ipsec.config ipsec.secrets Explanation The current status of the IPsec service is displayed. stopped The service is disabled. running The service is enabled. Enable or disable the IPsec service. Select an IPsec configuration file to be transferred from PC to controller or vice versa. Select an IPsec configuration file to be transferred 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 160 Commissioning WAGO-I/O-SYSTEM 750 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 the WBM reboot function. Do not shut down the controller too early! 7.8.1.37.3 “Certificate Upload” Group Table 109: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate Upload” Group Parameters New Certificate New Private Key Explanation Select an certificate for transfer from a PC to the controller. 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.37.4 “Certificate List” Group Table 110: WBM “Configuration of OpenVPN and IPsec” Page – “Certificate List” Group Parameters Explanation The loaded certificates are displayed. If no certificate has been loaded. “No certificates existing” is displayed. Click [Delete] to delete an entry. The changes will be effective immediately. 7.8.1.37.5 “Private Key List” Group Table 111: WBM “Configuration of OpenVPN and IPsec” Page – “Private Key List” Group Parameters Explanation The loaded keys are displayed. If no keys has been loaded. “No keys existing” is displayed. Click [Delete] to delete an entry. The changes will be effective immediately. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.1.38 Commissioning 161 “Security Settings” Page The network security settings are found on the “Security Settings” page. 7.8.1.38.1 “TLS Configuration” Group Table 112: “Security Settings” WBM Page – “TLS Configuration” Group Parameters TLS configuration Explanation 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. The Webserver only allows TLS Version 1.2 and strong algorithms. Strong Older software and older operating systems may not support TLS 1.2. Click on [Submit] to accept the changes. The changes will be effective 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 162 Commissioning 7.8.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.3 Commissioning 163 “WAGO Licenses” Page The licence conditions for the WAGO software used in the controller are listed on the “WAGO Licenses” page. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 164 Commissioning 7.8.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 44: CBM main menu (example) 7.8.4.1 CBM Menu Structure Overview Table 113: CBM Menu Structure Menu Hierarchy 0. Quit 1. Information 0. Back to Main Menu 1. Controller Details 2. Network Details 2. PLC Runtime 0. Back to Main Menu 1. Information 2. General Configuration 3. WebVisu 3. Networking 0. Back to Main Menu Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 165 Table 113: CBM Menu Structure 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 0. Back to Main Menu 1. General Configuration 2. MAC Address Filter 3. User Filter 5. Clock 0. Back to Main Menu 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 0. Back to Main Menu 1. Users 2. Create Image 3. Owner of Serial Interface 4. Reboot Controller 7. Package Server 0. Back to Main Menu 1. Firmware Backup 2. Firmware Restore 3. System Partition 8. Mass Storage 0. Back to Main Menu 1. Internal Flash (active partition) 9. Software Uploads 0. Back to Main Menu Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 166 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 113: CBM Menu Structure Menu Hierarchy 1. Update Script 10. Ports and Services 0. Back to Main Menu 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 0. Back to Main Menu 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 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.2 Commissioning 167 “Information” Menu This menu contains other submenus with information on the controller and network. Table 114: “Information” Menu Menu Item 0. Back to … 1. Controller Details 2. Network Details Explanation Back to the higher-level menu Opens a submenu with controller properties Opens a submenu with controller network and interface properties To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.2.1 “Information” > “Controller Details” Submenu In this submenu, the controller properties are displayed. Table 115: “Information” > “Controller Details” Submenu Parameters Product Description Order Number License Information Firmware Revision Explanation Controller identification Item number of the controller Notification that the CODESYS runtime system is available Firmware status To return to the higher-level menu, press [Q] or [Return]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 168 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.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 116: “Information” > “Network Details” Submenu Parameters State Mac Address IP Address Subnet Mask Explanation Status of the ETHERNET interface (enabled/disabled) MAC address identifies and addresses the controller Current IP address of the controller and (in brackets) the reference type (static/bootp/dhcp) Current subnet mask of the controller To return to the higher-level menu, press [Q] or [Return]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.3 Commissioning 169 “PLC Runtime” Menu This menu contains other submenus with information and settings for the runtime system. Table 117: “PLC Runtime” Menu Menu Item 0. Back to … 1. Information 2. General Configuration 3. WebVisu Explanation Back to the higher-level menu Opens a submenu with information on the runtime system Opens a submenu with settings for the runtime system Opens a submenu with settings for the Web visualization To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.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 118: “PLC Runtime” > “Information” Submenu Menu Item 0. Back to … 1. Runtime Version 2. Webserver Version 3. State 4. Number of Tasks 5. Project Details 6. Tasks Explanation Back to the higher-level menu Opens a submenu to display the runtime version Opens a submenu to display the Webserver version Opens a submenu to display the PLC operating state Opens a submenu to display the number of tasks in the PLC program Opens a submenu to display the PLC program project information Opens a submenu to display the tasks in the PLC program To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 170 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.3.2 “Information” > “Runtime Version” Submenu In this submenu, the runtime version is displayed. Table 119: “PLC Runtime” > “Information” > “Runtime Version” Submenu Parameters Version Explanation The version of the currently enabled runtime system is shown. If the runtime system is disabled, “None” is displayed. To return to the higher-level menu, press [Q] or [Return]. 7.8.4.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 120: “PLC Runtime” > “Information” > “Webserver Version” Submenu Parameters Version Explanation The Webserver version is displayed. To return to the higher-level menu, press [Q] or [Return]. 7.8.4.3.4 “Information” > “State” Submenu In this submenu, the PLC operating state is displayed. The submenu only appears when CODESYS 2 is enabled as the runtime system. Table 121: “PLC Runtime” > “Information” > “State” Submenu Parameters State Explanation The PLC operating state is shown. STOP PLC program is not executed. RUN PLC program is executed. To return to the higher-level menu, press [Q] or [Return]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 171 7.8.4.3.5 “Information” > “Number of Tasks” Submenu In this submenu, the number of tasks in the PLC program are displayed. The submenu only appears when CODESYS 2 is enabled as the runtime system. Table 122: “PLC Runtime” > “Information” > “Number of Tasks” Submenu Parameters Number of Tasks Explanation The number of tasks in the PLC program is shown. To return to the higher-level menu, press [Q] or [Return]. 7.8.4.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 123: “PLC Runtime” > “Information” > “Project Details” Submenu Parameters Date Title Version Author Description Explanation Display of project information that the programmer entered in the PLC program (in the programming software under Project > Project Information ...) Descriptive text with up to 1024 characters is displayed under “Description”. To return to the higher-level menu, press [Q] or [Return]. 7.8.4.3.7 “Information” > “Tasks” Submenu In this submenu, tasks from the PLC program are displayed. An entry is generated for each task. The submenu only appears when CODESYS 2 is enabled as the runtime system. Table 124: “PLC Runtime” > “Information” > “Tasks” Submenu Menu Item 0. Back to … n. Task n Explanation Back to the higher-level menu Opens a submenu with information on the selected task To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 172 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.3.8 “Tasks” > “Task n” Submenu In this submenu, information on the selected task is displayed. The submenu only appears when CODESYS 2 is enabled as the runtime system. Table 125: “PLC Runtime” > “Information” > “Tasks” > “Task n” Submenu Parameters Cycle count Cycle time (µsec) Cycle time min (µsec) Cycle time max (µsec) Cycle time avg (µsec) Status Mode Priority Interval (msec) Explanation Number of task cycles since the system start Currently measured task cycle time for the task Minimum task cycle time for the task since the system start Maximum task cycle time for the task since the system start Average task cycle time since the system start Task status (e.g., RUN, STOP) Task execution mode (e.g., in cycles) Set task priority Set task interval To return to the higher-level menu, press [Q] or [Return]. 7.8.4.3.9 “PLC Runtime” > “General Configuration” Submenu This submenu contains other submenus with general settings for the runtime system. Table 126: “PLC Runtime” > “General Configuration” Submenu Menu Item 0. Back to … 1. PLC Runtime Version 2. Home Dir On SD Card Explanation Back to the higher-level menu Opens a submenu for the CODESYS runtime system settings Opens a submenu for the home directory settings To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 173 7.8.4.3.10 “General Configuration” > “PLC Runtime Version” Submenu In this submenu, select which PLC runtime system is enabled. Table 127: “PLC Runtime” > “General Configuration” > “PLC Runtime Version” Submenu Menu Item 0. Back to … 1. None 2. CODESYS 2 3. e!RUNTIME Explanation Back to the higher-level menu No runtime system is enabled. The CODESYS 2 runtime system is enabled. 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! To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.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 128: “PLC Runtime” > “General Configuration” > “Home Dir On SD Card” Submenu Menu Item 0. Back to … 1. Enable 2. Disable Explanation Back to the higher-level menu The home directory is moved to the memory card. 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. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 174 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.3.12 “PLC Runtime” > “WebVisu” Submenu This submenu contains information and settings for the Web visualization. Table 129: “PLC Runtime” > “WebVisu” Submenu Menu Item 0. Back to … 1. CODESYS 2 Webserver State 2. e!RUNTIME Webserver State 3. Default Webserver Submenu Item / Explanation Back to the higher-level menu The status of the CODESYS 2 Webserver is displayed. The status of the e!RUNTIME Webserver is 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. 0. Back to … Back to the higher-level menu 1. Web-based The Web-based Management is Managem displayed. ent 2. CODESYS The web visualization of the runtime WebVisu system is displayed. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.4 Commissioning 175 “Networking” Menu This menu contains other submenus with settings for the network configuration. Table 130: “Networking” Menu Parameters 0. Back to … 1. Host/Domain Name 2. TCP/IP 3. Ethernet Explanation Back to the higher-level menu Opens a submenu with setting options for the general TCP/IP parameters Opens a submenu with TCP/IP settings for the ETHERNET interfaces Opens a submenu with settings for the ETHERNET configuration To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.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 131: “Networking” > “Host/Domain Name” Submenu Parameters 0. Back to … 1. Hostname 2. Domain Name Explanation Back to the higher-level menu Opens a submenu with the hostname settings In addition to the menu item, the configured and current hostname are displayed. Opens a submenu hostname settings In addition to the menu item, the configured and current domain name are displayed. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 176 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.4.2 “Host/Domain Name” > “Hostname” Submenu In this submenu, you can set the hostname of the controller. Table 132: “Networking” > “Hostname” Submenu Parameters Enter new Hostname Explanation Enter here the hostname of the controller to be used if the network interface is changed to a static IP address or if no hostname is transmitted with a DHCP response. Click [ ] to apply the entry. Click [ ] to discard the entry. 7.8.4.4.3 “Host/Domain Name” > “Domain Name” Submenu In this submenu, you can set the domain name of the controller. Table 133: “Networking” > “Host/Domain Name” > “Domain Name” Submenu Parameters Enter new Domain Name Explanation Enter the domain name. The default entry is “localdomain.lan”. Click [ ] to apply the entry. Click [ ] to discard the entry. 7.8.4.4.4 “Networking” > “TCP/IP” Submenu This submenu contains other submenus with the TCP/IP settings for the ETHERNET interfaces. Table 134: “Networking” > “TCP/IP” Submenu Menu Item 0. Back to … 1. IP Address 2. Default Gateway 3. DNS Server Explanation Back to the higher-level menu Opens a submenu with settings for the IP address(es) Opens a submenu with settings for the default gateway Opens a submenu with settings for the DNS server(s) To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 177 7.8.4.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 135: “Networking” > “IP Address” Submenu Menu Item 0. Back to … 1. X1 2. X2 Explanation Back to the higher-level menu Opens a submenu with settings for the X1 interface Opens a submenu with settings for the X2 interface To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.4.6 “IP Address” > “Xn“ Submenu This submenu contains the settings for the selected interface. Table 136: “Networking” > “TCP/IP” > “IP Address” Submenu > “Xn” Menu Item 0. Back to … 1. Type of IP Address Configuration 2. IP Address 3. Subnet Mask Submenu Item / Explanation Back to the higher-level menu Select a static or dynamic IP address. 0. Back to … Back to the higher-level menu Static IP addressing When selecting static addressing, the 1. Static IP IP address and subnet mask are then retrieved. 2. DHCP Dynamic IP addressing 3. BootP Dynamic IP addressing Enter here a static IP address. Enter the subnet mask. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 178 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.4.7 “TCP/IP” > “Default Gateway” Submenu This submenu contains other submenus with settings for the default gateway. Table 137: “Networking” > “TCP/IP” > “Default Gateway” Submenu Menu Item 0. Back to … 1. Default Gateway 1 2. Default Gateway 2 Explanation Back to the higher-level menu Opens a submenu with settings for default gateway In addition to the menu item, the current status of the gateway is displayed. Opens a submenu with settings for default gateway In addition to the menu item, the current status of the gateway is displayed. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.4.8 “Default Gateway” > “Default Gateway n” Submenu This submenu contains the settings for the selected gateway. Table 138: “Networking” > “TCP/IP” > “Default Gateway” > “Default Gateway n” Submenu Menu Item 0. Back to … 1. State 2. Gateway IP Address 3. Gateway Metric Submenu Item / Explanation Back to the higher-level menu Set here whether the selected default gateway is to be used. 0. Back to … Back to the higher-level menu 1. Disabled The default gateway is not used. 2. Enabled The default gateway is used. Enter the address of the default gateway. Set here a number as the metric. The default value for the metric is 20, the lowest value is 0, the highest value is 4.294.967.295. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 179 7.8.4.4.9 “TCP/IP” > “DNS Server” Submenu This submenu contains the settings for the DNS server. Table 139: “Networking” > “TCP/IP” > “DNS Server” Submenu Menu Item 0. Back to … n. DNS Server n (n+1). Add new DNS Server Submenu Item / Explanation Back to the higher-level menu The addresses of the defined DNS servers are displayed. Other submenus are available for the server entered. 0. Back to … Back to the higher-level menu You can change the selected DNS 1. Edit server address. You can delete the selected DNS 2. Delete server address. Add additional DNS server addresses. You can enter 10 addresses. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. 7.8.4.4.10 “Networking” > “Ethernet” Submenu This submenu contains other submenus with settings for the ETHERNET configuration. Table 140: “Networking” > “Ethernet” Submenu Menu Item 0. Back to … 1. Switch Configuration 2. Ethernet Ports Explanation Back to the higher-level menu Opens a submenu with settings for the IP address(es) Opens a submenu with settings for the ETHERNET interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 180 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.4.11 “Ethernet” > “Switch Configuration” Submenu This submenu contains the settings for the Switch configuration. Table 141: “Networking” > “Ethernet” > “Switch Configuration” Submenu Submenu 0. Back to … 1. Network interfaces Submenu Item / Explanation Back to the higher-level menu Enable or disable the switch. 0. Back to … Back to the higher-level menu Each interface is operated with its 1. Separated own IP address. Both interfaces are operated with one 2. Switched IP address. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.4.12 “Ethernet” > “Ethernet Ports” Submenu This submenu contains other submenus with settings for the ETHERNET interfaces. Table 142: “Networking” > “Ethernet” > “Ethernet Ports” Submenu Menu Item 0. Back to … 1. Interface X1 2. Interface X2 Explanation Back to the higher-level menu Opens a submenu with settings for the X1 interface Opens a submenu with settings for the X2 interface To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 181 7.8.4.4.13 “Ethernet Ports” > “Interface Xn” Submenu This submenu contains the settings for the selected ETHERNET interface. Table 143: “Networking” > “Ethernet” > “Ethernet Ports” > “Interface Xn” Submenu Submenu 0. Back to … 1. Port 2. Autonegotiation Submenu Item / Explanation Back to the higher-level menu Set here whether the selected port is to be used. 0. Back to … Back to the higher-level menu 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. 0. Back to … Back to the higher-level menu 1. Disabled Autonegotiation is disabled. 2. Enabled Autonegotiation is enabled. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 182 Commissioning 7.8.4.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “Firewall” Menu This menu contains other submenus for the firewall functionality settings. Table 144: “Firewall” Menu Menu Item 0. Back to … 1. General Configuration 2. MAC Address Filter 3. User Filter Explanation Back to the higher-level menu Opens a submenu with general firewall settings Opens a submenu with MAC address filter settings Opens a submenu with user filter settings To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 183 7.8.4.5.1 “Firewall” > “General Configuration” Submenu This submenu contains the general settings for the firewall. Table 145: “Firewall” > “General Configuration” Submenu Menu Item 0. Back to … Submenu Item / Explanation Back to the higher-level menu 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. 0. Back to … Back to the higher-level menu 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 “0” = “Disabled” You can specify the maximum number of TCP 4. Max TCP connections connections per second. per second “0” = “Disabled” 5. Interface WAN 6. Interface VPN Opens a submenu with firewall settings on the IP level for the selected interface 7. Interface X1 8. Interface X2 To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 184 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.5.2 “General Configuration” > “Interface xxx” Submenu This submenu contains the firewall settings on the IP level for the selected interface. Table 146: “Firewall” > “General Configuration” > “Interface xxx” Submenu Menu Item 0. Back to … 1. Interface state 2. ICMP Policy 3. ICMP Limit 4. ICMP Burst 5. Telnet 6. FTP 7. FTPS 8. HTTP 9. HTTPS 10. I/O-CHECK 11. PLC Runtime 12. PLC WebVisu – direct link (port 8080) 13. SSH 14. TFTP 15. BootP/DHCP 16. DNS 17. MODBUS TCP 18. MODBUS UDP 19. SNMP Submenu Item / Explanation Back to the higher-level menu Enable or disable the firewall for the selected interface. 0. Back to … Back to the higher-level menu 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. 0. Back to … Back to the higher-level menu The “ICMP echo” protection is 1. Accept disabled. The “ICMP echo” protection is 2. Drop enabled. You can specify the maximum number of “ICMP pings” per second. “0” = “Disabled” You can specify the maximum number of “ICMP echo bursts” per second. “0” = “Disabled” Enable or disable the firewall for the respective service. The services themselves must be enabled or disabled separately on the “Ports and Services” page. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 185 Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 186 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.5.3 “Firewall” > “MAC Address Filter” Submenu This submenu contains the settings for the MAC address filter. Table 147: “Firewall” > “MAC Address Filter” Submenu Menu Item 0. Back to … 1. MAC address filter whitelist 2. MAC address filter state VPN 3. MAC address filter state WAN 4. MAC address filter state X1 5. MAC address filter state X2 Submenu Item / Explanation Back to the higher-level menu Opens a submenu to edit the MAC address filter whitelist Enable or disable the firewall for the VPN interface. 0. Back to … Back to the higher-level menu The firewall for the VPN interface is 1. Open disabled. The firewall for the VPN interface is 2. Filtered enabled. Enable or disable the firewall for the WAN interface. 0. Back to … Back to the higher-level menu The firewall for the WAN interface is 1. Open disabled. The firewall for the WAN interface is 2. Filtered enabled. Enable or disable the firewall for the X1 interface. 0. Back to … Back to the higher-level menu The firewall for the X1 interface is 1. Open disabled. The firewall for the X1 interface is 2. Filtered enabled. Enable or disable the firewall for the X2 interface. 0. Back to … Back to the higher-level menu The firewall for the X2 interface is 1. Open disabled. The firewall for the X2 interface is 2. Filtered enabled. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 187 7.8.4.5.4 “MAC Address Filter” > “MAC address filter whitelist” Submenu This submenu displays all available filter entries. Table 148: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” Submenu Menu Item 0. Back to … 1. Add new 2. Previous page 3. Next Page (n + 3.) No (n): Explanation Back to the higher-level menu Opens a submenu to add a new filter entry You can enter 10 filters. Displays the previous page of the list (if more than one page is filled) Displays the next page of the list (if more than one page is filled) Opens a submenu to edit an existing filter entry To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.5.5 “MAC address filter whitelist” > “Add new / No (n)” Submenu In this submenu, you can create, change or delete filter entries. Table 149: “Firewall” > “MAC Address Filter” > “MAC address filter whitelist” > “Add new / No (n)” Submenu Menu Item 0. Back to … 1. MAC address 2. MAC mask 3. Filter state 4. accept 5. delete Submenu Item / Explanation Back to the higher-level menu Enter the MAC address. Enter the MAC mask. Enable or disable the filter. 0. Back to … Back to the higher-level menu 1. on The filter is enabled. 2. off The filter is disabled. To apply the changes for the selected filter entry, choose this menu item. To delete the selected filter entry, choose this menu item. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 188 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.5.6 “Firewall” > “User Filter” Submenu This submenu displays all available filter entries. Table 150: “Firewall” > “User Filter” Submenu Menu Item 0. Back to … 1. Add new 2. Previous page 3. Next Page (n + 3.) No (n): Explanation Back to the higher-level menu Opens a submenu to add a new filter entry Displays the previous page of the list (if more than one page is filled) Displays the next page of the list (if more than one page is filled) Opens a submenu to edit an existing filter entry To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 189 7.8.4.5.7 “User Filter” > “Add New / No (n)” Submenu In this submenu, you can create, change or delete filter entries. Table 151: “Firewall” > “User Filter” > “Add New / No (n)” Submenu Menu Item 0. Back to … 1. Source IP address 2. Source netmask 3. Source port 4. Destination IP address 5. Destination netmask 6. Destination port 7. protocol 8. interface 9. state 10. accept 11. delete Submenu Item / Explanation Back to the higher-level menu Enter the source IP address. Enter the source network mask. Enter the source port number. Enter the destination IP address. Enter here the destination netmask. Enter the destination port number. Select the permitted protocols. 0. Back to … Back to the higher-level menu 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. 0. Back to … Back to the higher-level menu 1. all All interfaces are permitted. 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. 0. Back to … Back to the higher-level menu 1. on The filter is enabled. 2. off The filter is disabled. To apply the changes for the selected filter entry, choose this menu item. To delete the selected filter entry, choose this menu item. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 190 Commissioning 7.8.4.6 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “Clock” Menu This menu contains other submenus for the date and time settings. Table 152: “Clock” Menu Menu Item 0. Back to … 1. Date on device (local) 2. Time on device (local) 3. Time on device (UTC) 4. Clock Display Mode 5. Timezone 6. TZ String Submenu Item / Explanation Back to the higher-level menu Set date. Set local time. Set GMT time. Select the display format for the time. 0. Back to … Back to the higher-level menu The time is displayed in 24-hour 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: 0. Back to … Back to the higher-level menu 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 “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 town if the time zone is not available for selection using the “Timezone” parameter. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.7 Commissioning 191 “Administration” Menu This menu contains settings for controller administration. Table 153: “Administration” Menu Menu Item 0. Back to … Submenu Item / Explanation Back to the higher-level 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. 0. Back to … Back to the higher-level menu 1. Linux The serial interface is assigned to the 3. Owner of Serial Interface Console Linux® console. The serial interface is not assigned 2. Unand 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 To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 192 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.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 154: “Administration” > “Create Image” Submenu Menu Item 0. Back to … 1. SD Card 2. Internal Flash Explanation Back to the higher-level menu To create an image on the memory card, select this menu item. Enter the reserved memory size in another step. This menu item only appears if the memory card is inserted. To create an image on the internal memory, select this menu item. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. 7.8.4.7.2 “Administration” > “Users” Submenu This submenu contains settings for the user passwords. Table 155: “Administration” > “Users” Submenu Menu Item 0. Back to … 1. user 2. admin Explanation Back to the higher-level menu Enter a new password for the “user” user. Enter a new password for the “admin” user. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.8 Commissioning 193 “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 156: “Package Server” Menu Menu Item 0. Back to … 1. Firmware Backup 2. Firmware Restore 3. System Partition Explanation Back to the higher-level menu Opens a submenu with functions for the firmware backup Opens a submenu with functions for the firmware restore Opens a submenu with information and setting options for the current system partition To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.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 157: “Package Server” > “Firmware Backup” Menu Menu Item 0. Back to … 1. All 2. PLC Runtime project 3. Settings 4. System Explanation Back to the higher-level menu All data is saved. The PLC runtime project is saved. The controller settings are saved. The controller operating system is saved. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. You are taken to the following submenu after making the selection. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 194 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.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 158: “Package Server” > “Firmware Backup” > “Auto Update Feature” Menu Menu Item 0. Back to … 1. No 2. Yes Explanation Back to the higher-level menu The Auto Update function is OFF for the selected data. The Auto Update function is ON for the selected data. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. You are taken to the following submenu after making the selection. 7.8.4.8.3 “Firmware Backup” > “Destination” Submenu This submenu contains a selection option for the backup destination drive. Table 159: “Package Server” > “Firmware Backup” > “Auto Update Feature” Menu Menu Item 0. Back to … 1. SD Card Explanation Back to the higher-level menu The selected data is copied to the memory card. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. The copy progress is displayed during the backup process. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 195 7.8.4.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 160: “Package Server” > “Firmware Restore” Menu Menu Item 0. Back to … 1. SD Card 2. Internal Flash Explanation Back to the higher-level menu The data is copied from the memory card. The data is copied from the internal memory. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. You are taken to the following submenu after making the selection. 7.8.4.8.5 “Firmware Restore” > “Select Package” Submenu This submenu contains a selection option for the data to be restored. Table 161: “Package Server” > “Firmware Restore” > “Select Package” Menu Menu Item 0. Back to … 1. PLC Runtime project 2. Settings 3. System 4. System + Setting 5. All Explanation Back to the higher-level menu The PLC runtime project is loaded. The controller settings are loaded. The controller operating system is loaded. The controller operating system and settings are loaded. All data is loaded. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. The copy progress is displayed during the restore process. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 196 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.8.6 “Package Server” > “System Partition” Submenu This submenu contains information and setting options for the current system partition. Table 162: “Package Server” > “System Partition” Submenu Menu Item 0. Back to … 1. Current active partition 2. Set inactive NAND partition active Explanation Back to the higher-level menu The partition currently in use is displayed. Select this menu item to start the system from a different partition at the next controller reboot. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.9 Commissioning 197 “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 163: “Mass Storage” Menu Parameters 0. Back to … 1. SD Card 2. Internal Flash Explanation Back to the higher-level menu Opens a submenu with information on the memory card and its formatting This menu item only appears if a memory card is inserted in the controller. Opens a submenu with information on the internal flash memory To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.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 164: “Mass Storage” > “SD Card” Menu Parameters 0. Back to … 1. Show information 2. FAT format medium Explanation Back to the higher-level menu Displays information on the memory card To format the memory card in FAT format, select this menu item. Then specify a volume name. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 198 Commissioning 7.8.4.10 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11 Commissioning 199 “Ports and Services” Menu This submenu contains other submenus with settings for the respective services. Table 165: “Ports and Services” Menu Menu Item 0. Back to … 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 Explanation Back to the higher-level menu Opens a submenu with settings for the Telnet service Opens a submenu with settings for the FTP service Opens a submenu with settings for the FTPS service Opens a submenu with settings for the HTTP service Opens a submenu with settings for the HTTPS service Opens a submenu with settings for the NTP service Opens a submenu with settings for the SSH server Opens a submenu with settings for the TFTP server Opens a submenu with settings for the DHCPD service Opens a submenu with settings for the DNS service Opens a submenu with settings for the WAGO-I/OCHECK port Opens a submenu with settings for the MODBUS TCP service Opens a submenu with settings for the MODBUS UDP service Opens a submenu with settings for the PLC runtime system services To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 200 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.1 “Ports and Services” > “Telnet” Submenu This submenu contains the settings for the Telnet service. Table 166: “Ports and Services” > “Telnet” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the Telnet service. 0. Back to … Back to the higher-level menu 1. Enable The Telnet service is enabled. 2. Disable The Telnet service is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.2 “Ports and Services” > “FTP” Submenu This submenu contains the settings for the FTP service. Table 167: “Ports and Services” > “FTP” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the FTP service. 0. Back to … Back to the higher-level menu 1. Enable The FTP service is enabled. 2. Disable The FTP service is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 201 7.8.4.11.3 “Ports and Services” > “FTPS” Submenu This submenu contains the settings for the FTPS service. Table 168: “Ports and Services” > “FTPS” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the FTPS service. 0. Back to … Back to the higher-level menu 1. Enable The FTPS service is enabled. 2. Disable The FTPS service is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.4 “Ports and Services” > “HTTP” Submenu This submenu contains the settings for the HTTP service. Table 169: “Ports and Services” > “HTTP” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the HTTP service. 0. Back to … Back to the higher-level menu 1. Enable The HTTP service is enabled. 2. Disable The HTTP service is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 202 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.5 “Ports and Services” > “HTTPS” Submenu This submenu contains the settings for the HTTPS service. Table 170: “Ports and Services” > “HTTPS” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the HTTPS service. 0. Back to … Back to the higher-level menu 1. Enable The HTTPS service is enabled. 2. Disable The HTTPS service is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.6 “Ports and Services” > “NTP” Submenu This submenu contains the settings for the NTP service. Table 171: “Ports and Services” > “NTP” Submenu Menu Item 0. Back to … 1. State 2. Port 3. Time Server 1 4. Time Server 2 5. Time Server 3 6. Time Server 4 7. Update Time 8. Issue immediate update Submenu Item / Explanation Back to the higher-level menu Enable/disable the NTP service. 0. Back to … Back to the higher-level menu 1. Enable The NTP service is enabled. 2. Disable The NTP service is disabled. Enter the port number of the NTP server. Enter here the IP addresses of up to 4 time servers. Time server No. 1 is requested first of all. If no data can be accessed via time server No. 1, time server No. 2 is requested. Specify here the update interval of the time server. To update the time immediately, irrespective of the update interval, select this menu item. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 203 7.8.4.11.7 “Ports and Services” > “SSH” Submenu This submenu contains the settings for the SSH service. Table 172: “Ports and Services” > “SSH” Submenu Menu Item 0. Back to … 1. State 2. Port 3. Allow root login 4. Allow password login 5. Status of firewalling Submenu Item / Explanation Back to the higher-level menu You can enable/disable the SSH server. 0. Back to … Back to the higher-level menu 1. Enable The SSH server is enabled. 2. Disable The SSH server is disabled. Enter the port number. You can enable or inhibit root access. 0. Back to … Back to the higher-level menu 1. Enable Root access is permitted. 2. Disable Root access is not permitted. Enable or disable the password query function. 0. Back to … Back to the higher-level menu 1. Enable Password query is enabled. 2. Disable Password query is disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.8 “Ports and Services” > “TFTP” Submenu This submenu contains the settings for the TFTP service. Table 173: “Ports and Services” > “TFTP” Submenu Menu Item 0. Back to … 1. State 2. Transfer Directory 3. Status of firewalling Submenu Item / Explanation Back to the higher-level menu Enable or disable the TFTP server. 0. Back to … Back to the higher-level menu 1. Enable The TFTP server is enabled. 2. Disable The TFTP server is disabled. Specify here the path for downloading the server directory. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 204 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.9 “Ports and Services” > “DHCPD” Submenu This submenu contains the settings for the DHCPD service. Table 174: “Ports and Services” > “DHCPD” Submenu Menu Item 0. Back to … 1. DHCPD Firewalling 2. X1 3. X2 Explanation Back to the higher-level menu Opens a submenu with firewall settings for the this service for the interfaces Opens a submenu with the DHCPD settings for the selected interface To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.10 “DHCPD” > “Xn” Submenu This submenu contains the settings for the DHCPD service for the selected interface. Table 175: “Ports and Services” > “DHCPD” > “Xn” Submenu Menu Item 0. Back to … 1. State 2. Range 3. Lease Time (min) 4. Add static hostname (5 + n). Static Host (n) Submenu Item / Explanation Back to the higher-level menu Enable/disable the DHCPD service for the Xn interface. 0. Back to … Back to the higher-level menu 1. Enable The DHCPD service is enabled. 2. Disable The DHCPD service is disabled. Enter a range of available IP addresses. Specify the lease time here in seconds. 120 seconds are entered by default. Enter a new static assignment of MAC ID to IP address, e.g., “01:02:03:04:05:06=192.168.1.20” or “hostname=192.168.1.20”. You can enter 10 assignments. This displays the static assignments. 0. Back to … Back to the higher-level menu Opens a submenu to change the 1. Edit selected assignment 2. Delete Deletes the selected assignment To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 205 7.8.4.11.11 “Ports and Services” > “DNS” Submenu This submenu contains the settings for the DNS service. Table 176: “Ports and Services” > “DNS” Submenu Menu Item 0. Back to … 1. State 2. Mode 3. Firewall status 4. Add static hostname (5 + n). Static Host (n) Submenu Item / Explanation Back to the higher-level menu Enable/disable the DNS service. 0. Back to … Back to the higher-level menu 1. Enable The DNS service is enabled. 2. Disable The DNS service is disabled. Select the operating mode of the DNS server. 0. Back to … Back to the higher-level menu The requests are buffered to optimize 1. Proxy throughput. 2. Relay All requests are routed directly. Opens a submenu with firewall settings for the this service for the interfaces Enter a new static assignment of IP address to hostname, e.g., “192.168.1.20:hostname”. You can enter 10 assignments. This displays the static assignments. 0. Back to … Back to the higher-level menu Opens a submenu to change the 1. Edit selected assignment 2. Delete Deletes the selected assignment To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 206 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.12 “Ports and Services” > “IOCHECK PORT” Submenu This submenu contains settings for the WAGO-I/O-CHECK port. Table 177: “Ports and Services” > “IOCHECK PORT” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Enable/disable the WAGO-I/O-CHECK port. 0. Back to … Back to the higher-level menu The WAGO-I/O-CHECK port is 1. Enable enabled. The WAGO-I/O-CHECK port is 2. Disable disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.13 “Ports and Services” > “Modbus TCP” Submenu This submenu contains the settings for the MODBUS TCP service. Table 178: “Ports and Services” > “Modbus TCP” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Disable or enable the MODBUS/TCP service. 0. Back to … Back to the higher-level menu The MODBUS TCP service is 1. Enable enabled. The MODBUS TCP service is 2. Disable disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 207 7.8.4.11.14 “Ports and Services” > “Modbus UDP” Submenu This submenu contains the settings for the MODBUS UDP service. Table 179: “Ports and Services” > “Modbus UDP” Submenu Menu Item 0. Back to … 1. State 2. Firewall status Submenu Item / Explanation Back to the higher-level menu Disable/enable the MODBUS UDP service. 0. Back to … Back to the higher-level menu The MODBUS UDP service is 1. Enable enabled. The MODBUS UDP service is 2. Disable disabled. Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.11.15 “Ports and Services” > “PLC Runtime Services” Submenu This submenu contains the settings for the PLC runtime system services. Table 180: “Ports and Services” > “PLC Runtime Services” Submenu Menu Item 0. Back to … 1. General Configuration 2. CODESYS 2 3. e!RUNTIME 4. Change CODESYS Runtime firewalling settings 5. Change CODESYS WebVisu firewalling settings Explanation Back to the higher-level menu Enter the password for port authentication. Opens a submenu with service settings for CODESYS 2 Opens a submenu with service settings for e!RUNTIME Opens a submenu with firewall settings for the this service for the interfaces Opens a submenu with firewall settings for the this service for the interfaces To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 208 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.16 “PLC Runtime Services” > “CODESYS 2” Submenu This submenu contains the settings for the CODESYS 2 service. Table 181: “Ports and Services” > “PLC Runtime Services” > “CODESYS 2” Submenu Menu Item 0. Back to … 1. Webserver enable/disable 2. Communication enable/disable 3. Communication Port Number 4. Port Authentication enable/disable Submenu Item / Explanation Back to the higher-level menu Enable or disable the Webserver for the CODESYS web visualization. 0. Back to … Back to the higher-level menu 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 programming system. 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 the CODESYS 2 programming system. The default value is 2455. Enter here whether a login is required for connecting to the device. 0. Back to … Back to the higher-level menu 1. Enable Authentication via login is required. 2. Disable Authentication is not required. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 209 7.8.4.11.17 “PLC Runtime Services” > “e!RUNTIME” Submenu This submenu contains the settings for the e!RUNTIME service. Table 182: “Ports and Services” > “PLC Runtime Services” > “e!RUNTIME” Submenu Menu Item 0. Back to … 1. Webserver enable/disable 2. Port Authentication enable/disable Submenu Item / Explanation Back to the higher-level menu Enable or disable the Webserver for the e!RUNTIME web visualization. 0. Back to … Back to the higher-level menu 1. Enable The Webserver is enabled. 2. Disable The Webserver is disabled. Enter here whether a login is required for connecting to the device. 0. Back to … Back to the higher-level menu 1. Enable Authentication via login is required. 2. Disable Authentication is not required. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 210 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.11.18 “…” > “Firewall Status” Submenu This submenu contains firewall settings for the selected service. Table 183: “Ports and Services” > “Firewall Status” Submenu Menu Item 0. Back to … 1. VPN 2. WAN 3. X1 4. X2 Submenu Item / Explanation Back to the higher-level menu Enable or disable the firewall for the VPN interface and respective service. 0. Back to … Back to the higher-level menu 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 and respective service. 0. Back to … Back to the higher-level menu 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 and respective service. 0. Back to … Back to the higher-level menu Data traffic via the X1 interface is 1. open permitted. Data traffic via the X1 interface is not 2. close permitted. Enable or disable the firewall for the X2 interface and respective service. 0. Back to … Back to the higher-level menu Data traffic via the X2 interface is 1. open permitted. Data traffic via the X2 interface is not 2. close permitted. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.12 Commissioning 211 “SNMP” Menu This menu contains other submenus with the SNMP settings. Table 184: “SNMP” Menu Parameters 0. Back to … 1. General SNMP Configuration 2. SNMP v1/v2c Manager Configuration 3. SNMP v1/v2c Trap Receiver Configuration 4. SNMP v3 Configuration Explanation Back to the higher-level menu Opens a submenu with general SNMP settings Opens a submenu with settings for the SNMP v1/v2c Manager Opens a submenu with settings for the SNMP v1/v2c trap receivers Opens a submenu with settings for the SNMP v3 configuration 5. SNMP firewalling Opens a submenu with firewall settings for SNMP 6. Secure SNMP firewalling To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. 7.8.4.12.1 “SNMP” > “General SNMP Configuration” Submenu This submenu contains the general SNMP settings. Table 185: “SNMP” > “General SNMP Configuration” Submenu Parameters 0. Back to … 1. SNMP status 2. Name of device 3. Description 4. Physical location 5. Contact Submenu Item / Explanation Back to the higher-level menu Enable or disable the SNMP service. 0. Back to … Back to the higher-level menu 1. Enable The SNMP service is enabled. 2. Disable The SNMP service is disabled. Enter here the device name (sysName). Enter here the device description (sysDescription). Enter here the location of the device (sysLocation). Enter here the email contact address (sysContact). To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 212 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.12.2 “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu This submenu contains the SNMP v1/v2c Manager settings. Table 186: “SNMP” > “SNMP v1/v2c Manager Configuration” Submenu Parameters 0. Back to … 1. Protocol state 2. Local community name Submenu Item / Explanation Back to the higher-level menu Enable or disable the SNMP v1/v2c protocol. 0. Back to … Back to the higher-level menu The SNMP v1/v2c protocol is 1. Enable enabled. The SNMP v1/v2c protocol is 2. Disable disabled. Specify here the community name for the SNMP manager configuration (max. 32 characters, no spaces). To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. 7.8.4.12.3 “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu This submenu contains settings for the v1/v2c trap receivers. Table 187: “SNMP” > “SNMP v1/v2c Trap Receiver Configuration” Submenu Parameters 0. Back to … (n). Trap Receiver (n) (n + 1). Add new Trap Receiver Explanation Back to the higher-level menu Opens a submenu with information on the selected 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: • IP address of the new trap 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) To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 213 7.8.4.12.4 “SNMP” > “SNMP v3 Configuration” Submenu This submenu contains settings for SNMP v3. Table 188: “SNMP” > “SNMP v3 Configuration” Submenu Parameters 0. Back to … (n). Username (n + 1). Add new v3 User Explanation Back to the higher-level menu Opens a submenu with information on the selected 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) • 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 To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Click [ ] to apply the entry. Click [ ] to discard the entry. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 214 Commissioning WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 7.8.4.12.5 “SNMP” > “(Secure)SNMP firewalling” Submenu These submenus contain the SNMP firewall settings. Table 189: “SNMP” > “(Secure )SNMP firewalling” Submenu Menu Item 0. Back to … 1. VPN 2. WAN 3. X1 4. X2 Submenu Item / Explanation Back to the higher-level menu Enable or disable the firewall for the VPN interface and respective service. 0. Back to … Back to the higher-level menu 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 and respective service. 0. Back to … Back to the higher-level menu 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 and respective service. 0. Back to … Back to the higher-level menu Data traffic via the X1 interface is 1. open permitted. Data traffic via the X1 interface is not 2. close permitted. Enable or disable the firewall for the X2 interface and respective service. 0. Back to … Back to the higher-level menu Data traffic via the X2 interface is 1. open permitted. Data traffic via the X2 interface is not 2. close permitted. To make a selection, choose the appropriate menu item. To return to the higher-level menu, press [Q]. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Commissioning 215 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3. Run-time System CODESYS 2.3 223 Click on [OK]. The “Target system settings” configuration window then opens. Figure 51: Target System Settings (1) 4. To accept the default configuration for the fieldbus controller click [OK]. The “New component” window opens. Figure 52: Target System Settings (2) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 224 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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 53: Creating a New Function Block Figure 54: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 225 Figure 55: “Resources” Tab 2. In the left window double-click on “PLC configuration”. The PLC configuration for the controller opens. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 226 Run-time System CODESYS 2.3 3. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Right-click on the entry “K-Bus[FIX]” and then select “Edit” in the contextual menu. The “configuration” dialog window then opens. Figure 56: 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 57: “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 5. Run-time System CODESYS 2.3 227 WAGO-I/O-CHECK is started. Figure 58: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 228 Run-time System CODESYS 2.3 8. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 59: 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 60: “Add I/O Modules” Button Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 10. Run-time System CODESYS 2.3 229 You can select a module in the new “Module selection” window that then appears. Figure 61: “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 62: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 230 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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 63: 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 64: Control Configuration: I/O Modules with Their Associated Addresses Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.2.4 Run-time System CODESYS 2.3 231 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 65: 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 66: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 232 Run-time System CODESYS 2.3 4. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Repeat Step 2 for the “Input_1” variable. Figure 67: Example of an Allocation 5. To compile, click on Project > Compile all in the menu bar. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.2.5 Run-time System CODESYS 2.3 233 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 68: Creating a Communication Link – Step 1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 234 Run-time System CODESYS 2.3 3. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G In the “Name” field enter a designation for your fieldbus controller and then click on “Tcp/Ip (Level 2 Route)”. Then click [OK]. Figure 69: Creating a Communication Link – Step 2 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]. Figure 70: Creating a Communication Link – Step 3 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.2.6 Run-time System CODESYS 2.3 235 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 190: Syntax of Logical Addresses Item Prefix Description Starts the absolute address Input Output Flag Single bit BByte (8 bits) Word (16 bits) Double word (32 bits) Address Notes: Data width Two examples: Addressing by word Addressing by bit %QW27 (28th word) %IX1.9 (10th bit in word 2) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 236 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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 71: Task Configuration 2. To create a task right-click on “Task configuration” and in the contextual menu select “Attach task”. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 3. Run-time System CODESYS 2.3 237 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 72: Changing Task Names 1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 238 Run-time System CODESYS 2.3 4. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 73: Call-up to Add to the Program Module 5. Compile the example program by selecting Project > Rebuild all in the context menu. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.4.1 Run-time System CODESYS 2.3 239 Cyclic Tasks You can assign a priority for each task in order to establish the task processing sequence. Figure 74: 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-timerelevant access to ETHERNET and the file system, to fieldbus data and the RS232 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 240 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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 75: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 241 Figure 76: Debugging (Case 1) Figure 77: Debugging (Case 2) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 242 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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). Figure 78: Debugging (Case 3) Figure 79: Debugging (Case 4) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 243 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. Figure 80: Debugging (Case 5) Figure 81: Debugging (Case 6) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 244 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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). Figure 82: Debugging (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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 245 Figure 83: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 246 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G The following events can be activated: Table 191: Events Name start stop before_reset Description The event is called directly after the user program starts. The event is called directly after the user program stops. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.5.1 Run-time System CODESYS 2.3 247 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 84: 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 85: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 248 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Figure 86: 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 87: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 249 Figure 88: CODESYS – Variable Contents Prior to Division by “0” Figure 89: 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 internal bus, Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 250 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G the PFC variables, the bit memory address area and the slaves attached to the fieldbus. Figure 90: Process Image Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 251 Figure 91: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 252 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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. 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! 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 internal data bus. Table 192: Access to the Process Images of the Input and Output Data – Internal Data Bus Memory area Description Access via Logical Address Space PLC Internal data bus Map of the local input modules Read Word input process (internal data bus, I/O module 1 %IW0 to %IW999 image to 1 bis 64 ) in the RAM. Byte %IB0 to %IB1999 Internal data bus Map of local output modules Read/ Word output process (internal data bus, I/O module 1 Write %QW0 to %QW999 image to 64 ) in the RAM. Byte %QB0 to %QB1999 * The use of up to 250 I/O modules is possible with the WAGO internal data bus extension modules. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 253 Table 193: Access to the Process Images of the Input and Output Data – MODBUS Memory area Description Access via Logical Address Space PLC MODBUS input process image MODBUS input variables, addressed by word via MODBUS MODBUS input variables, addressed by bit via MODBUS MODBUS output process image Read Read MODBUS output variables, addressed by word via MODBUS Read/ Write MODBUS output variables, addressed by bit via MODBUS Read/ Write Word %IW1000 to %IW1999 Byte %IB2000 to %IB3999 Bit %IX1000.0 …%IX1000.15 to %IX1384.0 … %IX1384.15 Word %QW1000 to %QW1999 Byte %QB2000 to %QB3999 Bit %QX1000.0 … %QX1000.15 to %QX1384.0 … %QX1384.15 Table 194: Access to the Process Images of the Input and Output Data – CANopen Memory area Description Access via Logical Address Space PLC CANopen input process image CANopen master or CANopen slave input variables Read CANopen output process image CANopen master or CANopen slave output variables Read/ Write Word %IW3000 to %IW4999 Byte %IB6000 to %IB9999 Word %QW3000 to %QW4999 Byte %QB6000 to %QB9999 Table 195: Access to the Process Images of the Input and Output Data – PROFIBUS Memory area Description Access via Logical Address Space PLC PROFIBUS input process image PROFIBUS input variables Read PROFIBUS output process image PROFIBUS output variables Read/ Write Word %IW2000 to %IW2499 Byte %IB4000 to %IB4999 Word %QW2000 to %QW2499 Byte %QB4000 to %QB4999 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 254 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 196: 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 memory (65536 words). 104 kB addressed by word via MODBUS (53248 words) 6.5 kB addressed by bit via MODBUS (3328 words). Read/ Write Read/ Write Read/ Write %MW0 to %MW65535 Word (MODBUS) %MW0 to %MW3327 Bit (MODBUS) %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 internal data 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 197: Arrangement of the I/O Modules for the Addressing Example Fieldbus controller 750400 750554 750402 750504 750454 750650 750468 750600 Table 198: Addressing Example I/O module Input data Output data C* Type %IX8.0 %IX8.1 750-400 750-554 750-402 750-504 %QW0 %QW1 %IX8.2 %IX8.3 %IX8.4 %IX8.5 %QX4.0 %QX4.1 Description 2DI, 24 V, 3 ms: 1. Digital input module with a data width of 2 bits. As the analog input modules already occupy the first 8 words of the input process image, the 2 bits occupy the lowest-value bits of the 8th word. 2AO, 4 – 20 mA: 1. Analog output module with a data width of 2 words. This module occupies the first 2 words in the output process image. 4DI, 24 V: 2. Digital input module with a data width of 4 bits. These are added to the 2 bits of the 750400 module and stored in the 8th word of the input process image. 4DO, 24 V: 1. Digital output module with a data width of 4 bits. As the analog output module already Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 255 Table 198: Addressing Example I/O module Input data Output data C* Type 750-454 %QX4.2 %QX4.3 %IW0 %IW1 %IW3 %QW2 %QW3 750-468 %IW4 %IW5 %IW6 %IW7 occupies the first 4 words of the output process image, the 4 bits occupy the lowestvalue bits of the 4th word. 2AI, 4 – 20 mA: 1. Analog input module with a data width of 2 words. This module occupies the first 2 words in the input process image. %IW2 750-650 1 Description RS-232, C 9600/8/N/1: The serial interface module is an analog input and output module, which displays 2 words both in the input process image and in the output process image. 4AI, 0 – 10 V S.E: 2. Analog input module with a data width of 4 words. As the 750-454 and 750-650 analog input and output modules already occupy the first 4 words of the input process image, the 4 words of this I/O module are added behind the others. End module The passive 750-600 end module does not transmit any data. 750-600 Analog input and output modules Digital input and output modules C: Number of the input/output 8.9 Internal Data Bus Synchronization The internal data 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 chapter, CODESYS task denotes only tasks within CODESYS that contain an access to the internal data bus. Tasks that do not access the internal data 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 I/O Module Cycle Execution of the CODESYS tasks is synchronized with internal data bus cycle time. The CODESYS task is processed in parallel to the internal data bus cycle. The CODESYS task interval is extended to the internal data bus cycle time. This is necessary so that each CODESYS task is started with new input data from the Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 256 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G internal data bus and the output values are also set at the module after each CODESYS task. Figure 92: Internal Data Bus Synchronization 01 CTI: CT: KBZ: CODESYS Task Interval CODESYS Task that accesses the I/O module of the internal data bus Internal Data Bus Cycle Example: CODESYS task interval (CTI): 100 µs I/O module cycle (KBZ): 2000 µs Result: Matching of the CODESYS task interval to the I/O module cycle of 2000 µs. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.9.2 Run-time System CODESYS 2.3 257 Case 2: CODESYS Task Interval Smaller than Twice the Internal Data Bus Cycle Execution of the internal data bus is synchronized with the set CODESYS task interval. At the end of the CODESYS task, the internal 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 internal data bus and the output values of each CODESYS task are also output to the I/O modules. Figure 93: I/O Module Synchronization 02 CTI: CODESYS Task Interval CT: CODESYS Task that accesses the I/O module of the internal data bus KBZ: Internal Data Bus Cycle Example: CODESYS task interval (CTI): 2500 µs Internal data bus cycle (KBZ): 2000 µs Result: Execution of the internal data bus cycle every 2500 µs. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 258 Run-time System CODESYS 2.3 8.9.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Case 3: CODESYS Task Interval Greater than Twice the Internal Data Bus Cycle The I/O data from the internal data bus are refreshed once prior to the CODESYS task and once after the CODESYS task. Prior to processing the CODESYS task, the internal data bus cycle is executed, which provides the current input data for the CODESYS task. After execution of the CODESYS task, an additional internal data 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 internal data bus and the output data from each CODESYS task are quickly output to the I/O modules. This prevents processing of internal data bus cycles that would unnecessarily use a great deal of computing time on the CPU. Figure 94: I/O Module Synchronization 03 CTI: CODESYS Task Interval CT: CODESYS Task that accesses the I/O module of the internal data bus KBZ: Internal Data Bus Cycle Example: CODESYS task interval (CTI): 5000 µs Internal data bus cycle (KBZ): 2000 µs Result: Execution of the internal data bus cycle 2000 µs prior to the CODESYS task and once directly after the CODESYS task. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.9.4 Run-time System CODESYS 2.3 259 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 an internal data bus cycle. This reliably prevents the execution of an internal data bus cycle after at least every 10 ms. The I/O data from the internal data bus are refreshed once before the CODESYS task and once after the CODESYS task and an additional internal data bus cycle is also executed every 10 ms. Figure 95: Internal Data Bus Synchronization 04 CTI: CT: KBZ: CODESYS Task Interval CODESYS task that accesses the I/O module of the internal data bus Internal data bus cycle Example: CODESYS task interval (CTI): 150000 µs Internal data bus cycle (KBZ): 2000 µs Result: Execution of the internal data bus cycle 2000 µs prior to the CODESYS task, once directly after the CODESYS task and 10 ms after the previous internal data bus cycle. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 260 Run-time System CODESYS 2.3 8.9.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Internal Data Bus Configuration Figure 96: Internal Data Bus Settings Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 261 Table 199: Internal Data Bus Settings Parameter Update Mode Internal Data Bus Cycle Time Internal Data Bus Thread Priority PLC stop response 8.9.5.1 Explanation The Update mode is used to configure how the internal data bus process data is to be updated (refreshed). In the asynchronous update mode process data Asynchronous are refreshed in cycles at a definable interval. In the synchronous update mode the process data are synchronized with the most rapid Synchronous* CODESYS task that accesses the internal data bus. The update interval for the internal data bus is set by the cycle time. This setting is effective only in the asynchronous mode. 1000 µs Minimum value 1 millisecond 10000 µs Default value 10 milliseconds 50000 µs Maximum value 50 milliseconds This value indicates the priority for the internal data bus thread. This setting is effective only in the asynchronous mode. This priority is equivalent to the priority of the cyclic CODESYS tasks (see Section “Cyclic Tasks”). This setting is effective only in the asynchronous mode. 0* Highest priority 15 Lowest priority Specifies the response of the internal data bus outputs when the PLC application stops. Hold last value The output states are retained. Set to zero* Outputs are set to zero. Default setting 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. Internal data bus “freeze” on priority conflicts! In the asynchronous update mode there is a risk of the internal data bus “freezing”, as the internal data bus thread operates at the same priority as the IEC tasks. The internal data bus thread must therefore use a priority higher than that of the IEC task to prevent this from occurring. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 262 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.9.5.1.2 Synchronous Update Mode In the synchronous update mode the runtime behavior of CODESYS tasks can be influenced by the internal data bus. The minimum task interval that can then be achieved depends on the duration of an internal data bus cycle. The duration of an internal data 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 internal data bus structure, the shorter the cycle time and digital modules are faster than analog or complex ones. In the event of an internal data bus error, the CODESYS tasks are blocked until the error is rectified, i.e., when an internal data bus cycle has been successfully executed again. No call-up of internal data bus status when internal data bus errors are present! If an internal data bus error has occurred, it is not possible to call up the internal data 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: • • • • • • • 8.10.1 Program memory: Data memory: Input data: Output data: Flags: Retain: Function block limitation: 16 Mbyte (max.) 64 Mbytes 64 kbytes 64 kbytes 24 kbytes 104 kbytes 12 * 4096 bytes = 48 kbytes 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 263 Figure 97: Program Memory (Example) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 264 Run-time System CODESYS 2.3 8.10.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 98: Data Memory and Function Block Limitation (Example) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.10.3 Run-time System CODESYS 2.3 265 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 99: 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 100: Flag and Retain Memory (Example) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 266 Run-time System CODESYS 2.3 8.11 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G General Target System Settings Figure 101: 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. 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:// /webvisu”, preferred method (http can also be used instead of https) “https:// ”, if the default Web server in the WBM has been set to“WebVisu” (http can also be used instead of https) “http:// :8080/webvisu.htm” You can also have Web visualization displayed via the WBM (see Section “`CODESYS - WebVisu´” Page). Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 269 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 highpriority 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 270 Run-time System CODESYS 2.3 WAGO-I/O-SYSTEM 750 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8.12.2 Run-time System CODESYS 2.3 271 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 200: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 272 Run-time System CODESYS 2.3 8.12.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Run-time System CODESYS 2.3 273 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 274 e!RUNTIME Runtime Environment WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 9.2 e!RUNTIME Runtime Environment 275 CODESYS V3 Priorities A list of priorities implemented for the controller is provided below as supplementary information to the CODESYS 3 documentation. Table 201: CODESYS V3 Priorities Scheduler Preemptive scheduling Real-time range Task Linux® Priority Local or fieldbus - HIGH -95 … -86 Mode selector switch monitoring -85 CODESYS watchdog -83 IEC Priority Internal data bus (-88) Cyclic and event-55 … -53 1 … 3 controlled IEC task Local or fieldbus - MID Remark -52 … -43 Cyclic and event-42 … -32 4 … 14 controlled IEC task Task registers changes to the mode selector switch and changes the state of the PLC application. (start, stop, reset warm/cold) Execution of the watchdog functions For real-time tasks which must not be influenced in execution by external interfaces (e.g., fieldbus). CAN (-52 … -51) Profibus (-49 … 45) MODBUS slave/master (-43) For real-time tasks which must not influence fieldbus communication during execution. Local or fieldbus – -13 … -4 LOW Fair scheduling None realtime range CODESYS communication Cyclic, eventcontrolled and freewheeling IEC task Communication with the CODESYS development environment Background (20) 15 Incl. standard priority of the visualization task Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 276 e!RUNTIME Runtime Environment 9.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Memory Spaces under e!RUNTIME The memory spaces in the controller under e!RUNTIME have the following sizes: • • • • • • 9.3.1 Program and data memory: Input data: Output data: Flags: Retain: Function block limitation: 60 Mbytes 64 kbytes 64 kbytes 24 kbytes 104 kbytes 12 * 4096 bytes = 48 kbytes 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 104: Remanent Main Memory Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 10 MODBUS – CODESYS 2 277 MODBUS – CODESYS 2 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 282 MODBUS – CODESYS 2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 205: MODBUS RTU Settings Parameters Flow control Physical interface Explanation Data flow control (Supported only for the setting “RS-232” for the physical interface.) None* No data flow control RTS/CTS Hardware flow control Mode for the physical interface RS-232* RS-232 is used as the physical interface. RS-485 RS-485 is used as the physical interface. Default setting Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G MODBUS – CODESYS 2 283 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G MODBUS – CODESYS 2 297 Figure 110: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 298 MODBUS – CODESYS 2 Table 211: Watchdog Commands Value 0x5555 Name WATCHDOG_ START 0x55AA WATCHDOG_ STOP 0xAAAA WATCHDOG_ RESET WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Explanation Starts the configured watchdog; 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. Stops the running watchdog; 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. Resets the expired watchdog; the watchdog is reset in the WATCHDOG_EXPIRED state and STANDARD_WATCHDOG operation mode. The watchdog is then in the WATCHDOG_STOPPED state. In all other cases the response is an ILLEGAL_ DATA_VALUE (0x03) exception. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 10.5.4.2 MODBUS – CODESYS 2 299 Register 0x1101 – Watchdog Status This register provides the current state of the MODBUS watchdog. The following states are possible: Table 212: Watchdog Status 10.5.4.3 Value 0xFFFF Name WATCHDOG_ UNCONFIGURED 0x0000 WATCHDOG_ STOPPED 0x0001 WATCHDOG_ RUNNING 0x0002 WATCHDOG_ EXPIRED Explanation The MODBUS watchdog is not configured, the “Watchdog Timeout” register (0x1102) contains the value 0. This state can only be closed by setting a timeout > 0. The watchdog is configured, the “Watchdog 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. The MODBUS watchdog is active, i.e. configured and started. The set timeout has not yet expired. The timeout set in register 0x1102 (Watchdog 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. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 300 MODBUS – CODESYS 2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. Table 213: Watchdog Configuration Bit Name/Bit Identifier 0 EXPLICIT_ TRIGGER_ONLY 1 TRIGGER_ON_ STATUS_REG 2 CLOSE_ALL_TCP_ CONNECTIONS Explanation Activates the Explicit Trigger mode 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. Activates the watchdog trigger by (read) access to 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. Activates the closing of all MODBUS TCP 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 214: Watchdog Operation Modes 10.5.6 Value 0x0000 Name STANDARD_ WATCHDOG 0x0001 ALTERNATIVE_ WATCHDOG MODBUS – CODESYS 2 301 Explanation “Standard Watchdog” operation mode; the watchdog must be controlled explicitly via commands (see register 0x1100 Watchdog Command). “Alternative Watchdog” operation mode; 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. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 302 MODBUS – CODESYS 2 10.5.6.5 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G MODBUS – CODESYS 2 303 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 215: Diagnostics for the Error Server Diagnostics ID 0x00090000 0x00090001 0x00090002 0x00090003 0x00090004 0x00090005 Diagnostic text Modbus Slave library loaded Modbus Slave library closed Modbus Slave TCP started Modbus Slave TCP start failed Modbus Slave TCP terminated Modbus Slave UDP started Method of saving Temporary Temporary Temporary Permanent Temporary Temporary Explanation MODBUS slave library has been successfully loaded. MODBUS slave library has been successfully unloaded. MODBUS slave successfully started in TCP mode. Starting the MODBUS slave in the TCP mode failed. MODBUS slave TCP mode successfully terminated. MODBUS slave successfully started in UDP mode. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 304 MODBUS – CODESYS 2 Table 215: Diagnostics for the Error Server Diagnostics ID 0x00090006 0x00090007 0x00090008 0x00090009 0x0009000A 0x0009000B 0x0009000C 0x0009000F 0x00090100 0x00090101 0x00090102 0x00090103 0x00090104 0x00090105 0x00090106 0x00090107 Diagnostic text Modbus Slave UDP start failed Modbus Slave UDP terminated Modbus Slave RTU started Modbus Slave RTU start failed Modbus Slave RTU terminated Modbus Slave data exchange started by PLC Modbus Slave data exchange stopped by PLC Modbus Slave PLC watchdog timer expired Modbus Slave common configuration failed. Modbus Slave TCP configured successfully. Modbus Slave TCP configuration failed. Modbus Slave UDP configured successfully Modbus Slave UDP configuration failed. Modbus Slave RTU configured successfully. Modbus Slave RTU configuration failed Port for Modbus Slave RTU operation not free. WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Method of saving Permanent Temporary Temporary Permanent Temporary Temporary Explanation Starting the MODBUS slave in UDP mode failed. MODBUS slave UDP mode successfully terminated. MODBUS slave successfully started in the RTU mode. Starting the MODBUS slave in RTU mode failed. MODBUS slave RTU mode successfully terminated. MODBUS slave data exchange started. Temporary MODBUS slave data exchange stopped. Permanent Monitoring time for controller (PLC) expired. Permanent MODBUS slave configuration failed. Temporary MODBUS slave TCP configuration completed successfully. MODBUS slave TCP configuration failed. Permanent Temporary Permanent Temporary Permanent Permanent MODBUS slave UDP configuration completed successfully. MODBUS slave UDP configuration failed. MODBUS slave RTU configuration completed successfully. MODBUS slave RTU configuration failed. Serial port for MODBUS slave RTU configuration already occupied. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 215: Diagnostics for the Error Server Diagnostics ID 0x00090108 0x00090200 0x00090201 0x00090202 0x00090203 0x00090300 0x00090301 Diagnostic text Modbus Slave RTU configuration in RS-485 mode failed. Modbus Slave Watchdog activated. Modbus Slave Watchdog deactivated. Modbus Slave Watchdog Timer expired. Modbus Slave has terminated all established TCP connections. Modbus Slave: obtaining system resource failed Modbus Slave: processing system resource failed. MODBUS – CODESYS 2 305 Method of saving Permanent Explanation Temporary MODBUS watchdog activated. Temporary MODBUS watchdog deactivated. Permanent MODBUS watchdog monitoring time expired. Permanent All MODBUS TCP connections terminated due to timeout. Permanent Request for system resources by the MODBUS slave has failed. Access to system resources by the MODBUS slave has failed. Permanent MODBUS slave RTU configuration for the RS-485 mode has failed. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 306 MODBUS – e!RUNTIME 11 MODBUS – e!RUNTIME 11.1 MODBUS Address Overview WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Figure 111: MODBUS Address Overview Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2 MODBUS – e!RUNTIME 307 MODBUS Registers Table 216: WAGO MODBUS Registers MODBUS Address Data Length Access Description in Words Dec. Hex. Watchdog Configuration Registers 64,000 0xFA00 Watchdog command register 64,001 0xFA01 rw Watchdog timeout register 64,002 0xFA02 ro Watchdog status register 64,003 0xFA03 rw Watchdog config register MODBUS TCP connection 64,004 0xFA04 rw watchdog register Status Registers LED flash code I/O-LED 64,010 0xFA0A ro (sequence 1 of 3) LED flash code I/O-LED 64,011 0xFA0B ro (sequence 2 of 3) LED flash code I/O-LED 64,012 0xFA0C ro (sequence 3 of 3) 64,013 0xFA0D ro PLC State : 1 = Stop; 2 = Run Electronic Type Label Order number, e.g., 64,016 0xFA10 ro 0750810100400001 64,020 0xFA14 ro Firmware status 64,021 0xFA15 ro Hardware version 64,022 0xFA16 ro Firmware loader Process Image Version Version of the MODBUS process 64,023 0xFA17 ro image Network Configuration 64,032 0xFA20 ro MAC-ID 1 Process Image Registers Number of input registers, analog 64,064 0xFA40 ro and digital (total size of the MODBUS IN space) 0x7D00 Number of input registers, analog 64,065 0xFA41 ro 0x7D00 Number of input registers, digital 64,066 0xFA42 ro 0x8000 Number of output registers, analog and digital (total size of 64,067 0xFA43 ro the MODBUS OUT space) 0x7D00 Number of output registers, 64,068 0xFA44 ro analog 0x7D00 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 308 MODBUS – e!RUNTIME WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 216: WAGO MODBUS Registers MODBUS Address Dec. Hex. 64,069 0xFA45 Constants Registers 64,160 0xFAA0 64,161 0xFAA1 64,162 0xFAA2 64,250 0xFAFA Data Length Access Description in Words ro Number of output registers, digital 0x8000 ro ro ro ro Constant 0x1234 Constant 0xAAAA Constant 0x5555 Live register The WAGO MODBUS registers are described in more details in the following sections. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2.1 MODBUS – e!RUNTIME 309 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 112: State Diagram, ADVANCED_WATCHDOG Operation Mode Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 310 MODBUS – e!RUNTIME WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Figure 113: 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 114: State Diagram, Switching Operation Modes Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2.1.1 MODBUS – e!RUNTIME 311 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 217: Watchdog Commands Value 0x5555 Name WATCHDOG_ START 0x55AA WATCHDOG_ STOP 0xAAAA WATCHDOG_ RESET Explanation Starts the configured watchdog; 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 WATCHDOG_STOPPED state. In all other cases the watchdog is restarted and the WATCHDOG_RUNNING state is set. Stops the running watchdog; 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. Resets the expired watchdog; 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 312 MODBUS – e!RUNTIME 11.2.1.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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. The register can be read and written in the states 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 218: Watchdog Status Value 0xFFFF Name WATCHDOG_ UNCONFIGURED 0x0000 WATCHDOG_ STOPPED 0x0001 WATCHDOG_ RUNNING 0x0002 WATCHDOG_ EXPIRED Explanation The MODBUS watchdog is not configured, i.e., register 0xFA01 (Watchdog Timeout) contains the value 0. Only the setting of a timeout > 0 s can close this state. The MODBUS watchdog is configured, the 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. The MODBUS watchdog is active, i.e. configured and started. The set timeout has not yet expired. The timeout set in register 0xFA01 (Watchdog 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2.1.4 MODBUS – e!RUNTIME 313 Register 0xFA03 – Watchdog Config This register contains the configuration parameters for the watchdog. The register is organized in bits, see following table. The register can be read and written irrespective of the watchdog state in the SIMPLE_WATCHDOG operation mode. However, in the ADVANCED_WATCHDOG operation mode, the register can only be read and written in the WATCHDOG_UNCONFIGURED and WATCHDOG_STOPPED states. If the watchdog is active (WATCHDOG_RUNNING or WATCHDOG_EXPIRED state), only a read access is permissible. The response to a write request in this case is an ILLEGAL_FUNCTION (0x01) exception. Table 219: Watchdog Configuration Bit Name/Bit Identifier 0 EXPLICIT_ TRIGGER_ONLY 1 TRIGGER_ON_ STATUS_REG 2 CLOSE_ALL_TCP_ CONNECTIONS 7 SELECT_ ADVANCED_ SIMPLE_MODE Explanation Activates the Explicit Trigger mode 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). Activates the watchdog trigger by (read) 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. Activates the closing of all MODBUS TCP 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. Determines the watchdog operation mode 0* Advanced Mode: The watchdog must be 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 314 MODBUS – e!RUNTIME WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 219: Watchdog Configuration Bit Name/Bit Identifier *Default setting Explanation 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.2.2 Status Registers 11.2.2.1 PLC Status Register MODBUS – e!RUNTIME 315 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 316 MODBUS – e!RUNTIME 11.2.6 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 11.3 MODBUS – e!RUNTIME 317 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 318 Diagnostics WAGO-I/O-SYSTEM 750 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 115: Power Supply Indicating Elements Table 220: Legend for Figure “Power Supply Indicating Elements” Description Color Green/off Green/off Description Status of system power supply voltage Status of field-side power supply voltage Table 221: Field-Side Supply Diagnostics Status Green Off Explanation 24V field-side supply voltage present No 24V field-side supply voltage present Table 222: System Power Supply Diagnistics Status Green Off Explanation 24V system power supply voltage present No 24V system power supply voltage present Solution --Switch on the power supply. Check the supply voltage. Solution --Switch on the power supply. Check the supply voltage. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 12.1.2 Diagnostics 319 Mobile Radio Network Status Indicators Figure 116: Mobile Radio Network Status Indicators Table 223: Legend for the “Mobile Radio Network Status Indicators” Figure Description CON Color Green/off Table 224: Diagnostics via CON LED Description Mobile radio network status Status Green flashing 1800 ms ON, 200 ms OFF Green flashing 200 ms ON, 1800 ms OFF Explanation 2G or 3G network Remedy --- No network OFF Modem firmware update 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 radio network locally. Wait until the update process has complete. Do not switch off the device! Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 320 Diagnostics 12.1.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Fieldbus/System Indicating Elements Figure 117: Indicating elements for fieldbus/system Table 225: Diagnostics via SYS LED Status Green Yellow Yellow flashing Green/red flashing Explanation Ready to operate System start completed without errors Device is in startup/boot process and the RST button is not pressed. “Fix IP Address” mode, temporary setting until the next reboot Firmware update mode Remedy --- --- Connect to the device via the standard address (192.168.1.17) or restart the device to restore the original value set. --- Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Diagnostics 321 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 226: Diagnostics RUN LED Status Green Green flashing Green/red flashing Red Explanation PLC program has the status “Run”. PLC program at a debug point. PLC is at a debug point and the Run/Stop switch has been set to “Stop”. No PLC-program loaded or PLC program has the status “Stop”. Solution --Resume the program in the linked IDE (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. Set the Run/Stop switch to “Run” to enable the program to continue. Load the PLC program. Set the Run/Stop switch to “Run” to start the current program. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 322 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G The following indications apply to the e!RUNTIME runtime system: Table 227: RUN LED Diagnostics – e!RUNTIME Status Green Explanation Applications loaded and all in the “RUN” status Green flashing No application and now boot project loaded Red Applications loaded and all in the “STOP” status Green/red At least one 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 application after in the “STOP” status after exception (e.g., memory access error) Orange/green flashing Orange OFF Remedy --- Load an application or boot project. Set the mode selector switch to “RUN” to start the application. Start the stopped application. ----- Start the application with a reset via the mode selector switch or in the connected IDE. If the application cannot be started, restart the controller. Contact WAGO Support if the error occurs again. Load above threshold Try to reduce the load on the system: 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. Runtime system in Resume the application in the connected debug state IDE with single step or start. Remove the breakpoint if necessary. (breakpoint, single 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 No runtime system Enable a runtime system, e.g., via the loaded WBM. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 228: Diagnostics I/O LED Status Green Orange flashing Red Red flashing (2 Hz) Red flashing (flashing sequence) Off Diagnostics 323 Explanation Data cycle on the internal data bus, normal operating status. Startup phase; the internal data bus is being initialized. The startup phase is indicated by rapid flashing for about 1 ... 2 seconds. A hardware fault is present. An error which may be able to be eliminated is present. Solution --- Wait until initialization has been completed. Contact WAGO Support. First, try to eliminate the error by switching the 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. An internal data bus error An explanation of the is present. flashing sequence is given in the section “Diagnostics Messages via Flashing Sequences”. A library was not loaded, Restart the device. or a library function was If you cannot eliminate the error, contact WAGO not called up. Support. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 324 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 229: MS-LED Diagnostics Status Off Red flashing (flashing sequence) Explanation No error A configuration error exists. Remedy --An explanation of the flashing sequence is given in the section “Diagnostics via Flashing Sequences.” Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Diagnostics 325 Table 230: Diagnostics via NET LED Status Green Orange Red Explanation 3G network 2G network No network Red flashing, blink code 1-1 Red flashing, blink code 1-2 Red flashing, blink code 2-1 Red flashing, blink code 2-2 Red flashing, blink code 2-3 Remedy ----- 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. No SIM card inserted - Switch off the device. - Insert a SIM card. - Switch the device on again. Invalid/locked SIM - Switch off the device. card - Insert a different SIM card that is valid. - Switch the device on again. Modem not A hardware fault is present. Contact connected WAGO Support. Modem initialization Load the modem firmware originally error (incompatible included as delivered from the factory firmware version) back onto the device. Timeout for modem Switch the device off and on again. reset Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 326 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 231: Diagnostics via Signal Quality LEDs Status of signal quality LEDs ▐ (S1) █ (S2) ▐█ (S3) ██ (S4) ▐██ (S5) Signal quality OFF Yellow Green Green Green Green Green OFF OFF OFF Green Green Green Green OFF OFF OFF OFF Green Green Green OFF OFF OFF OFF OFF Green Green OFF OFF OFF OFF OFF OFF Green No network Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Table 232: Signal Quality Meaning Signal quality Level 1 Level 2 Level 3 Explanation UMTS Only UMTS, probable connection failure HDSPA possible, instable connection HDSPA possible, no weather reserve Level 4 HDSPA, stabile connection Level 5 HDSPA, maximum data rate 7.2 Mbit/s Level 6 HSPA+ possible (if available) GSM Only GSM, probable connection failure GPRS, very slow data connection GPRS, stabile data connection, maximum data rate (54 kbit/s) EDGE, stabile, very slow data connection possible EDGE, maximum data rate (220 kBit/s) E-EDGE possible (up to 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Diagnostics 327 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 328 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Figure 118: Flashing Sequence Process Diagram Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 12.2.2 Diagnostics 329 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 internal data 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 Internal Data 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 internal data 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 330 Diagnostics 12.2.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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: Fax: E-mail: +49 571 887 555 +49 571 887 8555 support@wago.com Table 233: Overview of Error Codes, I/O LED Error code Explanation Hardware and configuration error Configuration error Internal data bus protocol error Physical error on the internal data bus Internal data bus initialization error Not used Not used Not used CPU exception error Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Diagnostics 331 Table 234: Error Code 1, Explanation of Blink Codes and Procedures for Troubleshooting Error Argument Cause Remedy Invalid parameter checksum for internal data bus interface Internal buffer overflow (max. amount of data exceeded) during inline code generation. Data type of the I/O module(s) is not supported Unknown module type of the flash program memory Error occurred while writing to the flash memory Error occurred while erasing a flash sector The I/O module configuration after an internal data bus reset differs from the one after the last controller startup. Switch off the power to the controller and replace it. Then switch the power back on. Switch off the power to the controller. Reduce the number of I/O modules. Switch the power back on. 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 power supply again and place the end module in the middle of the first 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). Switch the power back on. Repeat this procedure until you establish which I/O module is defective. Then replace that module. Switch off the power to the controller and replace it. Then switch the power back on. Switch off the power to the controller and replace it. Then switch the power back on. Restart the controller by first switching off the power supply and then switching it back on, or by pressing the Reset button on the controller. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 332 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 234: Error Code 1, Explanation of Blink Codes and Procedures for Troubleshooting Error Argument 10 11 12 14 16 Cause Remedy Error occurred while writing to the serial EEPROM Invalid hardware/ firmware combination Invalid checksum in the serial EEPROM Fault when initializing the serial EEPROM. Error occurred while reading from the serial EEPROM Time to access the serial EEPROM exceeded Maximum number of gateway or mailbox modules exceeded. Maximum number of I/O modules exceeded Switch off the power to the controller and replace it. Then switch the power back on. Switch off the power supply to the controller and reduce the number of I/O modules. Then switch the power back on. Switch off the power to the controller and replace it. Then switch the power back on. Switch off the power to the controller. Reduce the number of gateway or mailbox modules. Then switch the power back on. Switch off the power to the controller. Reduce the number of I/O modules. Then switch the power back on. Table 235: Error Code 2, Explanation of Blink Codes and Procedures for Troubleshooting Error Argument Cause Maximum size of the process image exceeded Remedy Switch off the power to the controller. Reduce the number of I/O modules. Switch the power back on. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Diagnostics 333 Table 236: Error Code 3, Explanation of Blink Codes and Procedures for Troubleshooting Error Cause Argument Solution 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: -- Internal data bus communication error; defective I/O module cannot be identified 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 LED continues to flash red switch off the power supply again and place the end module in the middle of the first half of the I/O modules (toward the controller). If only one I/O module is left and the LED continues to flash, either this module or the controller internal data 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). Switch the power back on. Repeat this procedure until you establish which I/O module is defective. Then replace that module. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 334 Diagnostics WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 237: Error Code 4, Explanation of Blink Codes and Procedures for Troubleshooting Error Cause Argument -- n* Maximum permissible number of I/O modules exceeded. Internal data bus disruption after the nth process data module. Solution Switch off the power to the controller. Reduce the number of I/O modules to an acceptable value. Switch the power back on. Switch off the power to the controller. Replace the (n+1)th process data module. Switch the power back on. I/O modules that do not provide any data are ignored (e.g., supply module without diagnostics). Table 238: Error Code 5, Explanation of Blink Codes and Procedures for Troubleshooting Error Cause Argument Solution n* Register communication error during internal data bus initialization Switch off the power to the controller. Replace the (n+1)th process data module. Switch the power back on. I/O modules that do not provide any data are ignored (e.g., supply module without diagnostics). Table 239: Error Code 9, Explanation of Blink Codes and Procedures for Troubleshooting Error Cause Argument Invalid program statement Stack overflow Stack underflow Invalid event (NMI) Solution Malfunction of the program sequence. - Please contact WAGO Support. Malfunction of the program sequence. - Please contact WAGO Support. Malfunction of the program sequence. - Please contact WAGO Support. Malfunction of the program sequence. - Please contact WAGO Support. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 12.2.4 Diagnostics 335 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: Fax: E-mail: +49 571 887 555 +49 571 887 8555 support@wago.com Table 240: Overview of MS-LED Error Codes Error Code Explanation Configuration error Table 241: Error Code 1, Explanation of Blink Codes and Procedures for Troubleshooting Error Argument Cause Remedy Error when synchronizing the controller configuration with the internal data bus Check the information of the connected I/O modules in the CODESYS controller configuration. Adjust this to match the I/O module that is actually inserted. Recompile the project. Reload the project into the controller. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 336 Service WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 13 Service 13.1 Inserting and Removing the Memory Card = 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. 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. 8. Remove the memory card. 9. Switch on the controller. The controller can now be started with the new firmware version. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 13.3.3 Service 341 Factory Reset Do not switch the controller off! The controller can be damaged by interrupting the factory reset process. Do not switch the controller off during the factory reset process and do not disconnect the power supply! All parameters and passwords are overwritten! All controller parameters and passwords are overwritten by a factory reset. Any 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 342 Removal 14 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Removal Risk of injury due to sharp-edged blade contacts! The blade contacts are sharp-edged. Handle the I/O module carefully to prevent 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 121: 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 14.1.2 Removal 343 Removing the I/O Module 1. Remove the I/O module from the assembly by pulling the release tab. Figure 122: Removing the I/O Module (Example) Electrical connections for data or power jumper contacts are disconnected when removing the I/O module. 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 344 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 internal data bus is built up wordby-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. No direct access from fieldbus to the process image for I/O modules! Any data that is required from the I/O module process image must be explicitly mapped in the CODESYS program to the data in the fieldbus process image and vice versa! Direct access is not possible! Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.1 Appendix 345 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 242: 1 Channel Digital Input Module with Diagnostics Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 15.1.1.2 Bit 2 Bit 1 Bit 0 Diagnostic bit S1 Data bit DI 1 2 Channel Digital Input Modules 750-400, -401, -405, -406, -410, -411, -412, -427, -438, (and all variations), 753-400, -401, -405, -406, -410, -411, -412, -427 Table 243: 2 Channel Digital Input Modules Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 15.1.1.3 Bit 3 Bit 2 Bit 1 Bit 0 Data bit DI 2 Channel 2 Data bit DI 1 Channel 1 Table 244: 2 Channel Digital Input Module with Diagnostics Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Diagnostic Diagnostic Data bit bit S 2 bit S 1 DI 2 Channel 2 Channel 1 Channel 2 Bit 0 Data bit DI 1 Channel 1 2 Channel Digital Input Module with Diagnostics 750-419, -421, -424, -425, 753-421, -424, -425 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 346 Appendix 15.1.1.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 245: 2 Channel Digital Input Module with Diagnostics and Output Process Data Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Diagnostic bit Diagnostic bit Data bit Data bit S2 S1 DI 2 DI 1 Channel 2 Channel 1 Channel 2 Channel 1 Output Process Image Bit 7 Bit 6 Bit 5 15.1.1.5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Acknowledgement bit Q 2 Channel 2 Acknowledgement bit Q 1 Channel 1 4 Channel Digital Input Modules 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 Table 246: 4 Channel Digital Input Modules Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 15.1.1.6 Bit 3 Data bit DI 4 Channel 4 Bit 2 Bit 1 Bit 0 Data bit Data bit Data bit DI 3 DI 2 DI 1 Channel 3 Channel 2 Channel 1 8 Channel Digital Input Modules 750-430, -431, -436, -437, -1415, -1416, -1417, -1418 753-430, -431, -434 Table 247: 8 Channel Digital Input Modules Input Process Image Bit 7 Bit 6 Data bit DI Data bit DI 7 Channel 8 Channel 7 Bit 5 Data bit DI 6 Channel 6 Bit 4 Data bit DI 5 Channel 5 Bit 3 Data bit DI 4 Channel 4 Bit 2 Data bit DI 3 Channel 3 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) Bit 1 Data bit DI 2 Channel 2 Bit 0 Data bit DI 1 Channel 1 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.1.7 Appendix 347 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 248: 8 Channel Digital Input Module PTC with Diagnostics and Output Process Data Input Process Image Input Byte D0 Input Byte D1 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Signal status DI 8 Channel 8 Wire Wire Wire Wire Wire Wire Wire Wire break/ break/ break/ break/ break/ break/ break/ break/ Signal short short short short short short short short status circuit circuit circuit circuit circuit circuit circuit circuit DI 1 DB/KS DB/KS DB/KS DB/KS DB/KS DB/KS DB/KS DB/KS Chan8 nel 1 Chan- Chan- Chan- Chan- Chan- Chan- Chan- Channel 8 nel 7 nel 6 nel 5 nel 4 nel 3 nel 2 nel 1 Signal status DI 7 Channel 7 Signal status DI 6 Channel 6 Signal status DI 5 Channel 5 Signal status DI 4 Channel 4 Signal status DI 3 Channel 3 Signal status DI 2 Channel 2 Output Process Image Output Byte D0 Output Byte D1 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 15.1.1.8 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 DI Off 8 Channel 8 0: Channel ON 1: Channel OFF DI Off 7 Channel 7 0: Channel ON 1: Channel OFF DI Off 6 Channel 6 0: Channel ON 1: Channel OFF DI Off 5 Channel 5 0: Channel ON 1: Channel OFF DI Off 4 Channel 4 0: Channel ON 1: Channel OFF DI Off 3 Channel 3 0: Channel ON 1: Channel OFF DI Off 2 Channel 2 0: Channel ON 1: Channel OFF DI Off 1 Channel 1 0: Channel ON 1: Channel OFF Bit 7 Data bit DI Chan nel 8 Bit 6 Data bit DI 7 Chan nel 7 Bit 5 Data bit DI 6 Chan nel 6 Bit 4 Data bit DI 5 Chan nel 5 Bit 3 Data bit DI 4 Chan nel 4 Bit 2 Data bit DI 3 Chan nel 3 Bit 1 Data bit DI 2 Chan nel 2 Bit 0 Data bit DI 1 Chan nel 1 16 Channel Digital Input Modules 750-1400, -1402, -1405, -1406, -1407 Table 249: 16 Channel Digital Input Modules Input Process Image Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Data Data Data Data Data Data Data Data bit bit bit bit bit bit bit bit DI 16 DI 15 DI 14 DI 13 DI 12 DI 11 DI 10 DI 9 Chann Chan Chan Chan Chan Chan Chann Chan el 16 nel 15 nel 14 nel 13 nel 12 nel 11 el 10 nel 9 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 348 Appendix 15.1.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 250: 1 Channel Digital Output Module with Input Process Data Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 not used Bit 0 Status bit “Manual Operation“ Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 not used 15.1.2.2 Bit 0 controls DO 1 Channel 1 2 Channel Digital Output Modules 750-501, -502, -509, -512, -513, -514, -517, -535, (and all variations), 753-501, -502, -509, -512, -513, -514, -517 Table 251: 2 Channel Digital Output Modules Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) Bit 1 controls DO 2 Channel 2 Bit 0 controls DO 1 Channel 1 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.2.3 Appendix 349 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 252: 2 Channel Digital Input Modules with Diagnostics and Input Process Data Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Diagnostic Diagnostic bit bit S 2 S1 Channel 2 Channel 1 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls DO 2 Channel 2 Output Process Image Bit 7 Bit 6 Bit 0 controls DO 1 Channel 1 750-506, 753-506 The digital output module has 2-bits of diagnostic information for each output channel. The 2-bit diagnostic information can then be decoded to determine the exact fault condition of the module (i.e., overload, a short circuit, or a broken wire). The 4-bits of diagnostic data are mapped into the Input Process Image, while the output control bits are in the Output Process Image. Table 253: 2 Channel Digital Input Modules with Diagnostics and Input Process Data 75x-506 Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Diagnostic bits S1/S0, S3/S2: = ‘00’ Diagnostic bits S1/S0, S3/S2: = ‘01’ Diagnostic bits S1/S0, S3/S2: = ‘10’ Bit 3 Bit 2 Bit 1 Bit 0 Diagnostic bit Diagnostic bit Diagnostic Diagnostic bit S3 S2 bit S 1 S0 Channel 2 Channel 2 Channel 1 Channel 1 standard mode no connected load/short circuit against +24 V Short circuit to ground/overload Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 not used not used Bit 1 controls DO 2 Channel 2 Bit 0 controls DO 1 Channel 1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 350 Appendix 15.1.2.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4 Channel Digital Output Modules 750-504, -516, -519, -531, 753-504, -516, -531, -540 Table 254: 4 Channel Digital Output Modules Output Process Image Bit 7 15.1.2.5 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls controls controls DO 4 DO 3 DO 2 Channel 4 Channel 3 Channel 2 Bit 0 controls DO 1 Channel 1 4 Channel Digital Output Modules with Diagnostics and Input Process Data 750-532 The digital output modules have a diagnostic bit for each output channel. When an output fault condition occurs (i.e., overload, short circuit, or broken wire), a diagnostic bit is set. The diagnostic data is mapped into the Input Process Image, while the output control bits are in the Output Process Image. Table 255: 4 Channel Digital Output Modules with Diagnostics and Input Process Data Input Process Image Bit 7 Bit 6 Diagnostic bit S = ‘0’ Diagnostic bit S = ‘1’ Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Diagnostic Diagnostic Diagnostic Diagnostic bit bit bit bit S1 S4 S3 S2 Channel 1 Channel 4 Channel 3 Channel 2 no Error overload, short circuit, or broken wire Output Process Image Bit 7 15.1.2.6 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls controls controls DO 4 DO 3 DO 2 Channel 4 Channel 3 Channel 2 Bit 0 controls DO 1 Channel 1 Table 256: 8 Channel Digital Output Module Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls controls controls controls controls controls controls DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Bit 0 controls DO 1 Channel 1 8 Channel Digital Output Module 750-530, -536, -1515, -1516 753-530, -534 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.2.7 Appendix 351 8 Channel Digital Output Modules with Diagnostics and Input Process Data 750-537 The digital output modules have a diagnostic bit for each output channel. When an output fault condition occurs (i.e., overload, short circuit, or broken wire), a diagnostic bit is set. The diagnostic data is mapped into the Input Process Image, while the output control bits are in the Output Process Image. Table 257: 8 Channel Digital Output Modules with Diagnostics and Input Process Data Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic Diagnostic bit bit bit bit bit bit bit bit S8 S7 S6 S5 S4 S3 S2 S1 Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1 Diagnostic bit S = ‘0’ no Error Diagnostic bit S = ‘1’ overload, short circuit, or broken wire Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls controls controls controls controls controls controls DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 15.1.2.8 Bit 0 controls DO 1 Channel 1 16 Channel Digital Output Modules 750-1500, -1501, -1504, -1505 Table 258: 16 Channel Digital Output Modules Output Process Image Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 controls controls controls controls controls controls controls controls controls controls controls controls controls controls controls controls DO 16 DO 15 DO 14 DO 13 DO 12 DO 11 DO 10 DO 9 DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 DO 1 Channel Channe Channe Channe Channe ChanneChannel Channe Channe Channe Channe Channe Channe Channe Channe Channe 16 l 15 l 14 l 13 l 12 l 11 10 l9 l8 l7 l6 l5 l4 l3 l2 l1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 352 Appendix 15.1.2.9 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 8 Channel Digital Input/Output Modules 750-1502, -1506 Table 259: 8 Channel Digital Input/Output Modules Input Process Image Bit 7 Bit 6 Data bit DI Data bit DI 7 Channel 8 Channel 7 Bit 5 Data bit DI 6 Channel 6 Bit 4 Data bit DI 5 Channel 5 Bit 3 Data bit DI 4 Channel 4 Bit 2 Data bit DI 3 Channel 3 Bit 1 Data bit DI 2 Channel 2 Output Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 controls controls controls controls controls controls controls DO 8 DO 7 DO 6 DO 5 DO 4 DO 3 DO 2 Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) Bit 0 Data bit DI 1 Channel 1 Bit 0 controls DO 1 Channel 1 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.3 Appendix 353 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 260: 1 Channel Analog Input Modules Input Process Image Byte Destination Offset High Byte Low Byte 15.1.3.2 D1 D3 D0 D2 Description Measured Value UD Measured Value Uref 2 Channel Analog Input Modules 750-452, -454, -456, -461, -462, -465, -466, -467, -469, -472, -474, -475, 476, 477, -478, -479, -480, -481, -483, -485, -492, (and all variations), 753-452, -454, -456, -461, -465, -466, -467, -469, -472, -474, -475, 476, -477, 478, -479, -483, -492, (and all variations) Table 261: 2 Channel Analog Input Modules Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 D0 D2 Description Measured Value Channel 1 Measured Value Channel 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 354 Appendix 15.1.3.3 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 4 Channel Analog Input Modules 750-450, -453, -455, -457, -459, -460, -468, (and all variations), 753-453, -455, -457, -459 Table 262: 4 Channel Analog Input Modules Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 D5 D7 D0 D2 D4 D6 Description Measured Value Channel 1 Measured Value Channel 2 Measured Value Channel 3 Measured Value Channel 4 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.3.4 Appendix 355 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 263: 3-Phase Power Measurement Module Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 D5 S0 D0 S1 D2 S2 D4 Description Status byte 0 Input data word 1 Status byte 1 Input data word 2 Status byte 2 Input data word 3 Output Process Image Offset 15.1.3.5 Byte Destination High Byte Low Byte D1 D3 D5 C0 D0 C1 D2 C2 D4 Description Control byte 0 Output data word 1 Control byte 1 Output data word 2 Control byte 2 Output data word 3 8 Channel Analog Input Modules 750-451 Table 264: 8 Channel Analog Input Modules Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 D5 D7 D9 D11 D13 D15 D0 D2 D4 D6 D8 D10 D12 D14 Description Measured Value Channel 1 Measured Value Channel 2 Measured Value Channel 3 Measured Value Channel 4 Measured Value Channel 5 Measured Value Channel 6 Measured Value Channel 7 Measured Value Channel 8 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 356 Appendix 15.1.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 265: 2 Channel Analog Output Modules Output Process Image Byte Destination Offset High Byte Low Byte 15.1.4.2 D1 D3 D0 D2 Description Output Value Channel 1 Output Value Channel 2 4 Channel Analog Output Modules 750-553, -555, -557, -559, 753-553, -555, -557, -559 Table 266: 4 Channel Analog Output Modules Output Process Image Byte Destination Offset High Byte Low Byte D1 D3 D5 D7 D0 D2 D4 D6 Description Output Value Channel 1 Output Value Channel 2 Output Value Channel 3 Output Value Channel 4 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.5 Appendix 357 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 to the structure of the Control/Status byte For detailed information about the structure of a particular module’s control/status byte, please refer to that module’s manual. Manuals for each module can be found on the Internet under: 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 267: 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 D1 D3 D0 D2 Status byte Counter value Output Process Image Offset Byte Destination High Byte Low Byte D1 D3 D0 D2 Description Control byte Counter setting value Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 358 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 750-404/000-005 The above Counter Modules have a total of 5 bytes of user data in both the Input and Output Process Image (4 bytes of counter data and 1 byte of control/ status). The two counter values are supplied as 16 bits. The following tables illustrate the Input and Output Process Image, which has a total of 3 words mapped into each image. Word alignment is applied. Table 268: Counter Modules 750-404/000-005 Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 D0 D2 Description Status byte Counter Value of Counter 1 Counter Value of Counter 2 Output Process Image Offset Byte Destination High Byte Low Byte D1 D3 D0 D2 Description Control byte Counter Setting Value of Counter 1 Counter Setting Value of Counter 2 750-638, 753-638 The above Counter Modules have a total of 6 bytes of user data in both the Input and Output Process Image (4 bytes of counter data and 2 bytes of control/status). The two counter values are supplied as 16 bits. The following tables illustrate the Input and Output Process Image, which has a total of 4 words mapped into each image. Word alignment is applied. Table 269: Counter Modules 750-638, 753-638 Input Process Image Byte Destination Offset High Byte Low Byte D1 D3 S0 D0 S1 D2 Description Status byte von Counter 1 Counter Value von Counter 1 Status byte von Counter 2 Counter Value von Counter 2 Output Process Image Offset Byte Destination High Byte Low Byte D1 D3 C0 D0 C1 D2 Description Control byte von Counter 1 Counter Setting Value von Counter 1 Control byte von Counter 2 Counter Setting Value von Counter 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 15.1.5.2 Appendix 359 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 270: Pulse Width Modules 750-511, /xxx-xxx Input and Output Process Byte Destination Offset High Byte Low Byte 15.1.5.3 D1 D3 C0/S0 D0 C1/S1 D2 Description Control/Status byte of Channel 1 Data Value of Channel 1 Control/Status byte of Channel 2 Data Value of Channel 2 Serial Interface Modules with alternative Data Format 750-650, (and the variations /000-002, -004, -006, -009, -010, -011, -012, -013), 750-651, (and the variations /000-001, -002, -003), 750-653, (and the variations /000-002, -007), 753-650, -653 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. Word alignment is applied. Table 271: Serial Interface Modules with alternative Data Format Input and Output Process Image Byte Destination Offset High Byte Low Byte D0 C/S D2 D1 Description Control/status byte Data bytes Data byte Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 360 Appendix 15.1.5.4 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Serial Interface Modules with Standard Data Format 750-650/000-001, -014, -015, -016 750-653/000-001, -006 The above Serial Interface Modules with Standard Data Format have a total of 6 bytes of user data in both the Input and Output Process Image (5 bytes of serial data and 1 byte of control/status). The following table illustrates the Input and Output Process Image, which have a total of 3 words mapped into each image. Word alignment is applied. Table 272: Serial Interface Modules with Standard Data Format Input and Output Process Image Byte Destination Offset High Byte Low Byte 15.1.5.5 D0 C/S D2 D4 D1 D3 Description Data byte Control/status byte Data bytes Data Exchange Module 750-654, (and the variation /000-001) The Data Exchange modules have a total of 4 bytes of user data in both the Input and Output Process Image. The following tables illustrate the Input and Output Process Image, which has a total of 2 words mapped into each image. Word alignment is applied. Table 273: Data Exchange Module Input and Output Process Image Byte Destination Offset High Byte Low Byte 15.1.5.6 D1 D3 D0 D2 Description Data bytes 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 361 The above SSI Transmitter Interface modules have a total of 4 bytes of user data in the Input Process Image, which has 2 words mapped into the image. Word alignment is applied. Table 274: SSI Transmitter Interface Modules Input Process Image Byte Destination Offset High Byte Low Byte 15.1.5.7 D1 D3 D0 D2 Description Data bytes Incremental Encoder Interface Modules 750-631/000-004, -010, -011 The above Incremental Encoder Interface modules have 5 bytes of input data and 3 bytes of output data. The following tables illustrate the Input and Output Process Image, which have 4 words into each image. Word alignment is applied. Table 275: Incremental Encoder Interface Modules 750-631/000-004, --010, -011 Input Process Image Byte Destination Offset Description High Byte Low Byte D1 D4 D0 D3 not used Status byte Counter word not used Latch word Output Process Image Offset Byte Destination High Byte Low Byte D1 D0 Description not used Control byte Counter setting word not used not used 750-634 The above Incremental Encoder Interface module has 5 bytes of input data (6 bytes in cycle duration measurement mode) and 3 bytes of output data. The following tables illustrate the Input and Output Process Image, which has 4 words mapped into each image. Word alignment is applied. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 362 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 276: Incremental Encoder Interface Modules 750-634 Input Process Image Byte Destination Offset High Byte Low Byte *) Description not used Status byte D1 D0 Counter word (D2) *) not used (Periodic time) D4 D3 Latch word If cycle duration measurement mode is enabled in the control byte, the cycle duration is given as a 24-bit value that is stored in D2 together with D3/D4. Output Process Image Offset Byte Destination High Byte Low Byte D1 D0 Description not used Control byte Counter setting word not used 750-637 The above Incremental Encoder Interface Module has a total of 6 bytes of user data in both the Input and Output Process Image (4 bytes of encoder data and 2 bytes of control/status). The following table illustrates the Input and Output Process Image, which have 4 words mapped into each image. Word alignment is applied. Table 277: Incremental Encoder Interface Modules 750-637 Input and Output Process Image Byte Destination Offset High Byte Low Byte D1 D3 C0/S0 D0 C1/S1 D2 Description Control/Status byte of Channel 1 Data Value of Channel 1 Control/Status byte of Channel 2 Data Value of Channel 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 363 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 278: Digital Pulse Interface Modules 750-635 Input and Output Process Image Byte Destination Offset High Byte Low Byte 15.1.5.8 D0 C0/S0 D2 D1 Description Control/status byte Data bytes Data byte DC-Drive Controller 750-636 The DC-Drive Controller maps 6 bytes into both the input and output process image. The data sent and received are stored in up to 4 input and output bytes (D0 ... D3). Two control bytes (C0, C1) and two status bytes (S0/S1) are used to control the I/O module and the drive. In addition to the position data in the input process image (D0 … D3), it is possible to display extended status information (S2 … S5). Then the three control bytes (C1 … C3) and status bytes (S1 … S3) are used to control the data flow. Bit 3 of control byte C1 (C1.3) is used to switch between the process data and the extended status bytes in the input process image (Extended Info_ON). Bit 3 of status byte S1 (S1.3) is used to acknowledge the switching process. Table 279: DC-Drive Controller 750-636 Input Process Image Byte Destination Offset High Byte Low Byte *) **) S1 S0 D1*) / S3**) D0*) / S2**) D3*) / S5**) D2*) / S4**) Description Status byte S1 Status byte S0 Actual position*) / Actual position Extended status (LSB) / Extended byte S3**) status byte S2**) Actual position Actual position*) / (MSB) / Extended Extended status status byte S3**) byte S4**) ExtendedInfo_ON = ‘0’. ExtendedInfo_ON = ‘1’. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 364 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Output Process Image Offset 15.1.5.9 Byte Destination High Byte Low Byte C1 C0 D1 D0 D3 D2 Description Control byte C1 Control byte C0 Setpoint position Setpoint position (LSB) Setpoint position Setpoint position (MSB) 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 280: Stepper Controller RS 422 / 24 V / 20 mA 750-670 Input Process Image Byte Destination Offset High Byte Low Byte reserved D1 D3 D5 S0 D0 D2 D4 S3 D6 *) **) S1 S2 Cyclic process image (Mailbox disabled) Mailbox process image (Mailbox activated) Description reserved Status byte S0 Process data*) / Mailbox**) Status byte S3 Status byte S1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) Process data*) / reserved**) Status byte S2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 365 Output Process Image Byte Destination Offset Description High Byte Low Byte reserved D1 D3 D5 C0 D0 D2 D4 reserved C3 D6 Control byte C3 C1 C2 Cyclic process image (Mailbox disabled) Mailbox process image (Mailbox activated) Control byte C1 *) **) Control byte C0 Process data*) / Mailbox**) Process data*) / reserved**) Control byte C2 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 281: RTC Module 750-640 Input and Output Process Image Byte Destination Offset High Byte Low Byte ID C/S D1 D3 D0 D2 Description Command byte Control/status byte Data bytes 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 282: DALI/DSI Master Module 750-641 Input Process Image Byte Destination Offset High Byte Low Byte D0 D2 D4 D1 D3 Description DALI Response Message 3 Message 1 Status byte DALI Address Message 2 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 366 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Output Process Image Offset Byte Destination High Byte Low Byte D0 D2 D4 D1 D3 Description DALI command, DSI dimming value Parameter 2 Command extension Control byte DALI Address 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 367 Table 283: Overview of Input Process Image in the "Easy" Mode Input process image Byte designation Offset High byte Low byte Note res. DA4…DA7 DA0…DA3 DA12…DA15 DA8…DA11 DA20…DA23 DA16…DA19 DA28…DA31 DA24…DA27 DA36…DA39 DA32…DA35 DA44…DA47 DA52…DA55 DA60…DA63 DA40…DA43 DA48…DA51 DA56…DA59 GA4…GA7 GA0…GA3 10 GA12…GA15 GA8…GA11 11 Status, activate broadcast Bit 0: 1-/2-button mode Bit 2: Broadcast status ON/OFF Bit 1,3-7: Bitpaar für DALI-Adresse DA0: Bit 1: Bit set = ON Bit not set = OFF Bit 2: Bit set = Error Bit not set = No error Bit pairs DA1 … DA63 similar to DA0. Bit pair for DALI group address GA0: Bit 1: Bit set = ON Bit not set = OFF Bit 2: Bit set = Error Bit not set = No error Bit pairs GA1 … GA15 similar to GA0. Not in use DA = DALI address GA = Group address Table 284: Overview of the Output Process Image in the "Easy" Mode“ Output process image Byte designation Offset High byte Low byte Note res. DA4…DA7 DA0…DA3 DA12…DA15 DA8…DA11 DA20…DA23 DA16…DA19 DA28…DA31 DA24…DA27 DA36…DA39 DA32…DA35 DA44…DA47 DA52…DA55 DA60…DA63 DA40…DA43 DA48…DA51 DA56…DA59 Broadcast ON/OFF and activate: Bit 0: Broadcast ON Bit 1: Broadcast OFF Bit 2: Broadcast ON/OFF/dimming Bit 3: Broadcast short ON/OFF Bits 4 … 7: reserved Bit pair for DALI address DA0: Bit 1: short: DA switch ON long: dimming, brighter Bit 2: short: DA switch OFF long: dimming, darker Bit pairs DA1 … DA63 similar to DA0. Bitpaar für DALI-Gruppenadresse GA0: GA4…GA7 GA0…GA3 10 GA12…GA15 GA8…GA11 Bit 1: short: GA switch ON long: dimming, brighter Bit 2: short: GA switch OFF Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 368 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 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/OPRO 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 words mapped into each image. Word alignment is applied. Table 285: EnOcean Radio Receiver 750-642 Input Process Image Byte Destination Offset High Byte Low Byte D0 D2 D1 Description Data byte Status byte Data bytes Output Process Image Offset Byte Destination High Byte Low Byte Description not used Control byte 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 words mapped into each image. Word alignment is applied. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 369 Table 286: MP Bus Master Module 750-643 Input and Output Process Image Byte Destination Offset High Byte Low Byte C1/S1 C0/S0 D1 D3 D5 D0 D2 D4 Description extended Control/ Status byte Control/status byte Data bytes 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 WAGOI/O-CHECK. ® Table 287: Bluetooth RF-Transceiver 750-644 Input and Output Process Image Byte Destination Offset High Byte Low Byte C0/S0 ... max. 23 D1 D3 D5 ... D0 D2 D4 ... D45 D44 Description not used Control/status byte Mailbox (0, 3, 6 or 9 words) and Process data (2-23 words) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 370 Appendix WAGO-I/O-SYSTEM 750 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. Word alignment is applied. Table 288: Vibration Velocity/Bearing Condition Monitoring VIB I/O 750-645 Input and Output Process Image Byte Destination Offset Description High Byte Low Byte C0/S0 D1 D0 C1/S1 D3 D2 C2/S2 D5 D4 C3/S3 D7 D6 Control/status byte (log. Channel 1, Sensor input 1) Data bytes (log. Channel 1, Sensor input 1) Control/status byte not used (log. Channel 2, Sensor input 2) Data bytes (log. Channel 2, Sensor input 2) Control/status byte not used (log. Channel 3, Sensor input 1) Data bytes (log. Channel 3, Sensor input 3) Control/status byte not used (log. Channel 4, Sensor input 2) Data bytes (log. Channel 4, Sensor input 2) not used 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 371 Table 289: KNX/EIB/TP1 Module 753-646 Input Process Image Byte Destination Offset High Byte Low Byte S0 S1 OP 10 11 D1 D3 D5 D7 D9 D11 D13 D15 D17 D19 D0 D2 D4 D6 D8 D10 D12 D14 D16 D18 Description not used extended Status byte Data byte 1 Data byte 3 Data byte 5 Data byte 7 Data byte 9 Data byte 11 Data byte 13 Data byte 15 Data byte 17 Data byte 19 Status byte Opcode Data byte 0 Data byte 2 Data byte 4 Data byte 6 Data byte 8 Data byte 10 Data byte 12 Data byte 14 Data byte 16 Data byte 18 Output Process Image Offset Byte Destination High Byte Low Byte C0 C1 OP 10 11 D1 D3 D5 D7 D9 D11 D13 D15 D17 D19 D0 D2 D4 D6 D8 D10 D12 D14 D16 D18 Description not used extended Control byte Data byte 1 Data byte 3 Data byte 5 Data byte 7 Data byte 9 Data byte 11 Data byte 13 Data byte 15 Data byte 17 Data byte 19 Control byte Opcode Data byte 0 Data byte 2 Data byte 4 Data byte 6 Data byte 8 Data byte 10 Data byte 12 Data byte 14 Data byte 16 Data byte 18 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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 372 Appendix WAGO-I/O-SYSTEM 750 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 WAGOI/O-CHECK. Table 290: AS-interface Master Module 750-655 Input and Output Process Image Byte Destination Offset High Byte Low Byte C0/S0 ... max. 23 D1 D3 D5 ... D0 D2 D4 ... D45 D44 Description not used Control/status byte Mailbox (0, 3, 5, 6 or 9 words)/ Process data (0-16 words) Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 373 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 291: System Modules with Diagnostics 750-610, -611 Input Process Image Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 15.1.6.2 Bit 2 Bit 1 Bit 0 Diagnostic Diagnostic bit bit S 2 S1 Fuse Fuse Binary Space Module 750-622 The Binary Space Modules behave alternatively like 2 channel digital input modules or output modules and seize depending upon the selected settings 1, 2, 3 or 4 bits per channel. According to this, 2, 4, 6 or 8 bits are occupied then either in the process input or the process output image. Table 292: Binary Space Module 750-622 (with Behavior Like 2 Channel Digital Input) Input and Output Process Image Bit 7 (Data bit DI 8) Bit 6 (Data bit DI 7) Bit 5 (Data bit DI 6) Bit 4 (Data bit DI 5) Bit 3 (Data bit DI 4) Bit 2 (Data bit DI 3) Bit 1 Data bit DI 2 Bit 0 Data bit DI 1 Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 374 Appendix 15.2 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G 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 controller7508207. 15.2.1.1 CODESYS System Libraries All of the functions of the CODESYS system libraries listed below are supported. Table 293: CODESYS System Libraries Library Analyzation.lib AnalyzationNew.lib Iecsfc.lib NetVarUdp_LIB_V23.lib Standard.LIB SysLibAlarmTrend.lib SysLibCallback.lib SysLibDir.lib SysLibDirect.lib SysLibEvent.lib SysLibFileStream.lib SysLibGetAddress.lib SysLibIecTasks.lib SysLibMem.lib SysLibPlcCtrl.lib SysLibProjectInfo.lib SysLibSem.lib SysLibSockets.lib SysLibSocketsAsync.lib SysLibStr.lib SysLibTasks.lib SysLibTime.lib SysLibVisu.lib Function Analysis of boolean expressions Analysis of boolean expressions Provision of implicit variables in the SFC (sequential function chart) Implementation for network variables Offers various standard functions Supports alarm and trend tasks For installing call-back handlers and event handlers For accessing directories Access to variables using indices Handling of events in the system File handling using ANSI-C functions Returns addresses and the size of memory segments Administration of IEC tasks Memory administration Control of the PLC from outside the PLC program Reading out of information about the CODESYS project Handling of semaphores Socket handling Socket handling, asynchronous String functions Administration of tasks Administration of real-time clock Dynamic visualization Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) C/IEC 61131 C and IEC 61131 C and IEC 61131 IEC 61131 IEC 61131 IEC 61131 WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 375 Table 293: CODESYS System Libraries Library SysTaskInfo.lib Util.lib Util_no_Real.lib Function Evaluation of task information in the Online mode Various logical operations Various logical operations C/IEC 61131 IEC 61131 IEC 61131 IEC 61131 Additional information about the libraries is given in the online Help function for CODESYS-IDE. Project > Project Information) Immedia tely Immedia tely Immedia tely Immedia tely Immedia tely Display of the CODESYS status (RUN or STOP) Immedia tely Information CODESYS Webserver read Version Project Details Date read Title read Version read Author read Description read get_coupler_details codesys-Webserverversion get_rts_info project date get_rts_info project title get_rts_info project version get_rts_info project author get_rts_info project description CODESYS State get_rts_info state Home Directory (Boot Project Location) State read read get_runtime_config homedir-on-sdcard write config_runtime homedir-onsdcard= Home Directory (Boot Project Location) Storage logation for the home directory. Possible return values: enabled: The home directory is on the SD card. disabled: The home directory is on the boot medium. After restart Storage logation for the home directory. Possible entries for the value are: enabled: Put the home directory on the SD card. disabled: The home directory is on the boot medium. Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 381 Table 299: Description of the Configuration Scripts for “Networking - Host/Domain Name” Parameters Status Call Output/Input Effecti ve Host Name read get_coupler_details hostname write change_hostname hostname= read get_coupler_details actual-hostname Host Name Actual Hostname Display of the host name. The return value is blank when /etc/hostname is empty. For details see the parameter “Actual Hostname.” Changing the host name. Input a host name for . The actual host name (if /etc/hostname is empty, a unique host name is generated from the MAC address) Immedia tely Immedia tely Immedia tely Domain Name read Domain name write get_coupler_details domain-name change_hostname dnsdomain= Display of domain name Change the domain name. Enter the domain name for . Table 300: Description of the Configuration Scripts for “Networking - TCP/IP” Parameters Status Call Output/Input Immedia tely Effecti 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 Possible return values are: get_eth_config read static (set statically) X1 config-type dhcp (per DHC) Type of IP bootp (per BootP) Immedia address tely Enable process, via which the configuration interface receives its IP address config_interfaces Possible entries for are: interface=X1 write static (set statically) config-type= dhcp (per DHC) state=enabled 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 must have an IP address config_interfaces tely write interface=X1 with the format ip-address= “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. must have tely write interface=X1 an IP address with the format subnet-mask= “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 Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) 382 Appendix WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Table 300: Description of the Configuration Scripts for “Networking - TCP/IP” Parameters Status Call Output/Input Effecti ve Default Gateway 1 read Default Gateway write read Default Gateway get_default_gateway_ config number=1 state config_default_gateway number=1 state= get_default_gateway_ config number=1 value write config_default_gateway number=1 value= read get_default_gateway_ config number=1 metric Default Gateway write config_default_gateway number=1 metric= Current status of the default gateway 1. Possible return values: enabled disabled Possible entries for : enabled disabled Current IP address of the default gateway 1 Enter the IP address of the default gateway 1 here. is an IP address with the format “Number. Number. Number. Number.” Current metric (cost factor) of the default gateway 1 The default value is “20.” Enter the metric of the default gateway 1 here. is a number between “0” and “4.294.967.295.” Immedia tely Immedia tely Immedia tely Default Gateway 2 See “Default Gateway 1.” When calling the gateway number, replace 1 with 2. DNS Server 1 DNS Server 1 read get_dns_server 1 write/ change edit_dns_server dns-server-nr=1 change=change dns-servername= write/ delete edit_dns_server dns-server-nr=1 delete=delete DNS server address with the consecutive number 1 Set the address of the DNS server with 1 as the consecutive number. is an IP address with the Immedia format tely “Number.Number.Number.Numbe r.” Delete the DNS server with the consecutive number 1. DNS Server 2 … n See “DNS Server 1.” When calling, adjust the server number (2 … n). Add DNS Server Add DNS server write edit_dns_server add=add dns-servername= Add additional DNS addresses here. is an IP address with the Immedia tely format “Number.Number.Number.Numbe r.” Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 383 Table 301: Description of the Configuration Scripts for “Networking - ETHERNET” Parameters Status Call-Up Output/Input Effective Query the switch configuration: Possible return values: 0 = „switched“ mode 1 = „separated“ mode Set the switch configuration: Possible entries for : 0 = „switched“ mode 1 = „separated“ mode Immediately Switch Configuration read get_dsa_mode Interface Mode write set_dsa_mode -v read get_eth_config X1 state write config_ethernet port=X1 state=enabled config_ethernet port=X1 state=disabled Interface X1 Port State read get_eth_config X1 autoneg config_ethernet port=X1 autoneg=on Autonegotiation write read read Speed and Duplex Settings write config_ethernet port=X1 autoneg=off speed= duplex= get_eth_config X1 speed get_eth_config X1 duplex config_ethernet port=X1 autoneg=off speed= duplex= Query the port state: Possible return values: enabled disabled Activate port: enabled Immediately Deactivate port: disabled Query the status of the autonegotiation function: Possible return values: on off Activate the autonegotiation function: on Deactivate the autonegotiation function: off Note: You must also indicate Immediately the speed and duplex value when you deactivate the autonegotiation function. Possible entries for speed: 10M 100M Possible entries for duplex: half full Display of ETHERNET speed Display of the Duplex mode Change the ETHERNET speed and the Duplex mode. Possible entries for speed: 10M 100M Possible entries for duplex: half full Immediately Interface X2 See “Interface X1”. When calling these up, replace “X1” with “X2”. State Port read write read get_ntp_config time-server- write config_sntp time-server = read get_ntp_config update-time write config_sntp update-time= Time Server Update Time (seconds) get_ntp_config port config_sntp port= Output/Input Query the status of the NTP server Possible return values are: enabled disabled Possible entries for : enabled disabled Port number of the NTP server Enter the port number for . Query the IP address of the time server: N = 1 … 4 for querying one of 4 time servers. Enter the IP address of 4 time servers can be a value from 1 to 4. is an IP address with the format “Number. Number. Number. Number.” Query the time in seconds between two requests to the time server. Specify the time-server's query cycle (in s) for . Manual Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09) Effecti ve Immedia tely Immedia tely Immedia tely Immedia tely WAGO-I/O-SYSTEM 750 750-8207 PFC200 CS 2ETH RS 3G Appendix 385 Table 303: Description of the Configuration Scripts for “Clock” Parameters Status Call-Up Clock Time and Date read Date on device, local write read Time on device, UTC Time on device, local get_clock_data date-local config_clock type=local date= get_clock_data time-utc Output/Input Effective Local time and date Change date. The format for is: DD.MM.YYYY Immediately Time/UTC write config_clock type=utc time=
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : Yes Author : WAGO Kontakttechnik GmbH & Co. KG Create Date : 2017:09:13 10:25:07+02:00 Modify Date : 2017:09:13 10:57:28+02:00 Tagged PDF : Yes XMP Toolkit : Adobe XMP Core 5.4-c005 78.147326, 2012/08/23-13:03:03 Metadata Date : 2017:09:13 10:57:28+02:00 Creator Tool : Acrobat PDFMaker 10.1 für Word Document ID : uuid:e195c9f3-e19f-4db4-90be-b953da7b85b9 Instance ID : uuid:e42f35f9-c4bd-461f-97ad-0891089ecef5 Subject : 10 Format : application/pdf Title : Manual 750-8207 Creator : WAGO Kontakttechnik GmbH & Co. KG Producer : Adobe PDF Library 10.0 Source Modified : D:20170913081915 Company : WAGO Kontakttechnik GmbH & Co. KG Page Layout : SinglePage Page Mode : UseOutlines Page Count : 410EXIF Metadata provided by EXIF.tools