SIMATIC ET 200SP Distributed I/O system System Manual 02/2018 A5E03576849-AH ___________________ Preface 1 ___________________ Guide to documentation 2 ___________________ New properties/functions 3 ___________________ System overview 4 ___________________ Application planning 5 ___________________ Installation 6 ___________________ Wiring 7 ___________________ Configuring 8 ___________________ Basics of program execution 9 ___________________ Protection Configuration control (option 10 ___________________ handling) 11 ___________________ Commissioning 12 ___________________ SIMATIC memory card 13 ___________________ Maintenance Test functions and 14 ___________________ eliminating problems 15 Technical specifications ___________________ A Dimension drawings ___________________ B Accessories/spare parts ___________________ Calculating the leakage C resistance ___________________ D Safety-relevant symbols ___________________ Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION indicates that minor personal injury can result if proper precautions are not taken. NOTICE indicates that property damage can result if proper precautions are not taken. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. Trademarks All names identified by (R) are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Division Digital Factory Postfach 48 48 90026 NURNBERG GERMANY A5E03576849-AH 02/2018 Subject to change Copyright (c) Siemens AG 2012 - 2018. All rights reserved Preface Preface Purpose of the documentation This documentation provides important information on configuring, installing, wiring and commissioning the ET 200SP distributed I/O system. Basic knowledge required A basic knowledge of automation technology is required to understand the documentation. Validity of the documentation This documentation applies to the distributed I/O system, ET 200SP. Definition In this document, " motor starter" always refers to all variants of the ET 200SP motor starters. Conventions Please pay particular attention to notes highlighted as follows: Note Notes contain important information on the product, handling the product or on part of the documentation to which you should pay particular attention. Standards You can find a dated reference to the relevant standards or EU declaration of conformity on the Internet (https://support.industry.siemens.com). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 3 Preface Special information WARNING Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Proper use of hardware products This equipment is only allowed to be used for the applications described in the catalog and in the technical description, and only in conjunction with non-Siemens equipment and components recommended by Siemens. Correct transport, storage, installation and assembly, as well as careful operation and maintenance, are required to ensure that the product operates safely and without faults. EU note: Start-up/commissioning is absolutely prohibited until it has been ensured that the machine in which the component described here is to be installed fulfills the regulations/specifications of Directive 2006/42/EC. Note Important note for maintaining operational safety of your plant Plants with safety-related features are subject to special operational safety requirements on the part of the operator. Even suppliers are required to observe special measures during product monitoring. For this reason, we inform you in the form of personal notifications about product developments and features that are (or could be) relevant to operation of systems from a safety perspective. By subscribing to the appropriate notifications, you will ensure that you are always up-to-date and able to make changes to your system, when necessary. Log onto Industry Online Support. Go to the following links and, on the side, right click on "email on update": * SIMATIC S7-300/S7-300F (https://support.industry.siemens.com/cs/ww/en/ps/13751) * SIMATIC S7-400/S7-400H/S7-400F/FH (https://support.industry.siemens.com/cs/ww/en/ps/13828) * SIMATIC WinAC RTX (F) (https://support.industry.siemens.com/cs/ww/en/ps/13915) * SIMATIC S7-1500/SIMATIC S7-1500F (https://support.industry.siemens.com/cs/ww/en/ps/13716) * SIMATIC S7-1200/SIMATIC S7-1200F (https://support.industry.siemens.com/cs/ww/en/ps/13683) * Distributed I/O (https://support.industry.siemens.com/cs/ww/en/ps/14029) * STEP 7 (TIA Portal) (https://support.industry.siemens.com/cs/ww/en/ps/14667) Note When using F-CPUs in safety mode and fail-safe modules, observe the description of the SIMATIC Industrial Software SIMATIC Safety - Configuring and Programming (http://support.automation.siemens.com/WW/view/en/54110126) fail-safe system. Distributed I/O system 4 System Manual, 02/2018, A5E03576849-AH Preface Recycling and disposal For ecologically sustainable recycling and disposal of your old device, contact a certified disposal service for electronic scrap and dispose of the device in accordance with the regulations in your country. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement - and continuously maintain - a holistic, state-of-the-art industrial security concept. Siemens' products and solutions constitute one element of such a concept. Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place. For additional information on industrial security measures that may be implemented, please visit (https://www.siemens.com/industrialsecurity). Siemens' products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customers' exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under (https://www.siemens.com/industrialsecurity). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 5 Preface Siemens Industry Online Support You can find current information on the following topics quickly and easily here: Product support All the information and extensive know-how on your product, technical specifications, FAQs, certificates, downloads, and manuals. Application examples Tools and examples to solve your automation tasks - as well as function blocks, performance information and videos. Services Information about Industry Services, Field Services, Technical Support, spare parts and training offers. Forums For answers and solutions concerning automation technology. mySupport Your personal working area in Industry Online Support for messages, support queries, and configurable documents. This information is provided by the Siemens Industry Online Support in the Internet (http://www.siemens.com/automation/service&support). Industry Mall The Industry Mall is the catalog and order system of Siemens AG for automation and drive solutions on the basis of Totally Integrated Automation (TIA) and Totally Integrated Power (TIP). You can find catalogs for all automation and drive products on the Internet. See also Industry Mall (https://mall.industry.siemens.com) Distributed I/O system 6 System Manual, 02/2018, A5E03576849-AH Table of contents Preface ................................................................................................................................................... 3 1 Guide to documentation ........................................................................................................................ 12 2 New properties/functions ....................................................................................................................... 17 3 System overview ................................................................................................................................... 19 4 3.1 What is the SIMATIC ET 200SP distributed I/O system? .......................................................19 3.2 What are fail-safe automation systems and fail-safe modules? .............................................22 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? ..........................................23 3.4 Components ............................................................................................................................27 Application planning .............................................................................................................................. 36 4.1 4.1.1 5 4.1.2 Selecting the BaseUnit for I/O modules ..................................................................................40 Digital, fail-safe, communication, technology or analog modules without temperature measurement ..........................................................................................................................40 Analog modules with temperature measurement ...................................................................41 4.2 4.2.1 4.2.2 4.2.3 Selecting motor starters with a suitable BaseUnit ..................................................................42 Selecting a BaseUnit for motor starters ..................................................................................42 Selecting the motor starter ......................................................................................................43 Selecting accessories for motor starters.................................................................................44 4.3 4.3.1 4.3.2 Selecting potential distributor modules ...................................................................................45 Selecting a PotDis-BaseUnit ...................................................................................................45 Selecting a PotDis-TerminalBlock ..........................................................................................46 4.4 Hardware configuration ...........................................................................................................48 4.5 4.5.1 4.5.2 4.5.3 4.5.4 Forming potential groups ........................................................................................................50 Basics......................................................................................................................................50 Forming potential groups with BaseUnit type B1 ....................................................................55 Forming potential groups with fail-safe modules ....................................................................56 Forming potential groups with motor starters .........................................................................58 4.6 4.6.1 4.6.2 Configuration examples for potential groups ..........................................................................60 Configuration examples with BaseUnits .................................................................................60 Configuration examples with potential distributor modules ....................................................61 Installation ............................................................................................................................................ 64 5.1 Basics......................................................................................................................................64 5.2 Installation conditions for motor starters .................................................................................68 5.3 Mounting the CPU/interface module .......................................................................................70 5.4 Installing the CM DP communication module .........................................................................72 5.5 Mounting BaseUnits for I/O modules ......................................................................................74 5.6 Mounting and dismantling BaseUnits for motor starters .........................................................77 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 7 Table of contents 6 5.7 Installing potential distributor modules ................................................................................... 79 5.8 Installing the server module ................................................................................................... 80 5.9 5.9.1 5.9.2 5.9.3 Mounting further accessories for motor starters .................................................................... 81 Mounting the cover for the 500 V AC infeed bus ................................................................... 81 Mounting the mechanical bracket for the BaseUnit ............................................................... 83 Mounting the BU cover .......................................................................................................... 86 Wiring ................................................................................................................................................... 87 6.1 Rules and regulations for operation ....................................................................................... 87 6.2 6.2.3 Additional rules and regulations for the operation of the ET 200SP with fail-safe modules .................................................................................................................................. 90 Safety extra-low voltage (SELV, PELV) for failsafe modules and failsafe motor starters ..... 90 Requirements for sensors and actuators for fail-safe modules and fail-safe motor starters ................................................................................................................................... 91 Crosstalk of digital input/output signals ................................................................................. 93 6.3 6.3.1 Additional rules and instructions for operation with motor starters ........................................ 93 Protection against short circuit ............................................................................................... 93 6.4 Operating the ET 200SP on grounded incoming supply ....................................................... 94 6.5 Electrical configuration of the ET 200SP ............................................................................... 97 6.6 Wiring rules ............................................................................................................................ 99 6.7 Wiring BaseUnits for I/O modules ........................................................................................ 102 6.8 Connecting cable shields for I/O modules ........................................................................... 105 6.9 Wiring BaseUnits for motor starters ..................................................................................... 107 6.10 Connecting the 3DI/LC module for the motor starter ........................................................... 111 6.11 Connecting the supply voltage to the CPU/interface module .............................................. 113 6.12 6.12.1 6.12.2 Connecting interfaces for communication ............................................................................ 115 Connecting PROFINET IO (port P3) to the CPU ................................................................. 115 Connecting the PROFIBUS DP interface to the interface module/communications module CM DP ..................................................................................................................... 117 6.13 Inserting I/O modules / motor starters and BU covers ......................................................... 118 6.14 6.14.1 6.14.2 6.14.3 Mounting/disassembly of motor starters .............................................................................. 120 Mounting the fan .................................................................................................................. 120 Mounting/disassembly of motor starters .............................................................................. 121 3DI/LC module ..................................................................................................................... 123 6.15 6.15.1 6.15.2 6.15.3 6.15.4 6.15.5 Labeling ET 200SP .............................................................................................................. 127 Factory markings.................................................................................................................. 127 Optional markings ................................................................................................................ 128 Applying color identification labels ....................................................................................... 130 Applying labeling strips ........................................................................................................ 132 Applying reference identification labels ............................................................................... 133 6.2.1 6.2.2 7 Configuring ..........................................................................................................................................134 7.1 Configuring ET 200SP ......................................................................................................... 134 Distributed I/O system 8 System Manual, 02/2018, A5E03576849-AH Table of contents 8 9 10 11 7.2 7.2.1 7.2.2 7.2.3 7.2.3.1 7.2.3.2 7.2.3.3 Configuring the CPU .............................................................................................................137 Reading out the configuration ...............................................................................................137 Addressing ............................................................................................................................139 Process images and process image partitions .....................................................................142 Process image - overview .....................................................................................................142 Automatically updating process image partitions .................................................................142 Update process image partitions in the user program ..........................................................143 7.3 Configuring the interface module ..........................................................................................145 Basics of program execution ............................................................................................................... 146 8.1 Events and OBs ....................................................................................................................146 8.2 CPU overload behavior .........................................................................................................149 8.3 Asynchronous instructions ....................................................................................................151 Protection ........................................................................................................................................... 161 9.1 Overview of the protective functions of the CPU ..................................................................161 9.2 Configuring access protection for the CPU...........................................................................162 9.3 Using the user program to set additional access protection .................................................165 9.4 Know-how protection ............................................................................................................166 9.5 Copy protection .....................................................................................................................170 Configuration control (option handling) ................................................................................................ 172 10.1 Configuring ............................................................................................................................175 10.2 10.2.1 10.2.2 10.2.3 10.2.4 10.2.5 Creating the control data record ...........................................................................................177 Introduction ...........................................................................................................................177 Control data record for an ET 200SP CPU ...........................................................................179 Control data record for an interface module .........................................................................181 Feedback data record for interface modules ........................................................................185 Data records and functions ...................................................................................................187 10.3 Transferring control data record in the startup program of the CPU ....................................188 10.4 Behavior during operation .....................................................................................................193 10.5 Examples of configuration control .........................................................................................194 Commissioning ................................................................................................................................... 199 11.1 Overview ...............................................................................................................................199 11.2 11.2.1 11.2.2 11.2.3 Commissioning the ET 200SP for PROFINET IO ................................................................200 ET 200SP CPU as an IO controller ......................................................................................201 ET 200SP CPU as an I-device .............................................................................................203 ET 200SP as an IO device ...................................................................................................205 11.3 11.3.1 11.3.2 11.3.3 Commissioning the ET 200SP on PROFIBUS DP ...............................................................207 ET 200SP as a DP master ....................................................................................................207 ET 200SP as I-slave .............................................................................................................209 ET 200SP as a DP slave ......................................................................................................211 11.4 Startup of the ET 200SP with empty slots ............................................................................212 11.5 Removing/inserting a SIMATIC memory card on the CPU...................................................213 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 9 Table of contents 12 13 14 11.6 11.6.1 11.6.2 11.6.3 11.6.4 Operating modes of the CPU ............................................................................................... 214 STARTUP mode .................................................................................................................. 214 STOP mode ......................................................................................................................... 217 RUN mode ........................................................................................................................... 217 Operating mode transitions .................................................................................................. 218 11.7 11.7.1 11.7.2 CPU memory reset .............................................................................................................. 221 Automatic memory reset ...................................................................................................... 222 Manual memory reset .......................................................................................................... 222 11.8 Reassigning parameters during operation ........................................................................... 224 11.9 11.9.1 11.9.2 11.9.3 Identification and maintenance data .................................................................................... 225 Reading out and entering I&M data ..................................................................................... 225 Data record structure for I&M data....................................................................................... 227 Example: Read out firmware version of the CPU with Get_IM_Data ................................... 229 11.10 Shared commissioning of projects ....................................................................................... 231 11.11 11.11.1 Backing up and restoring the CPU configuration ................................................................. 231 Overview .............................................................................................................................. 231 11.12 11.12.1 Time synchronization ........................................................................................................... 234 Example: Configuring and changing NTP server ................................................................. 236 SIMATIC memory card.........................................................................................................................240 12.1 SIMATIC memory card - overview ....................................................................................... 240 12.2 Setting the card type ............................................................................................................ 245 12.3 Data transfer with SIMATIC memory cards ......................................................................... 246 Maintenance ........................................................................................................................................247 13.1 Removing and inserting I/O modules/motor starters (hot swapping) ................................... 247 13.2 Changing the type of an I/O module .................................................................................... 251 13.3 Replacing an I/O module ..................................................................................................... 253 13.4 Replacing a motor starter ..................................................................................................... 254 13.5 Replacing the terminal box on the BaseUnit ........................................................................ 255 13.6 Firmware update .................................................................................................................. 257 13.7 13.7.1 13.7.2 13.7.3 Resetting CPU/interface module (PROFINET) to factory settings ...................................... 264 Resetting the CPU to factory settings .................................................................................. 264 Resetting interface module (PROFINET IO) to factory settings .......................................... 267 Resetting the interface module (PROFINET IO) to factory settings with a RESET button ................................................................................................................................... 268 13.8 Reaction to faults in fail-safe modules and fail-safe motor starters ..................................... 270 13.9 Maintenance and repair ....................................................................................................... 272 13.10 Warranty ............................................................................................................................... 272 Test functions and eliminating problems ...............................................................................................273 14.1 Test functions ....................................................................................................................... 273 14.2 Reading out/saving service data .......................................................................................... 280 Distributed I/O system 10 System Manual, 02/2018, A5E03576849-AH Table of contents 15 A B Technical specifications ...................................................................................................................... 282 15.1 Standards, approvals and safety notes ................................................................................282 15.2 Electromagnetic compatibility ...............................................................................................289 15.3 Electromagnetic compatibility of fail-safe modules ...............................................................292 15.4 Shipping and storage conditions ...........................................................................................295 15.5 Mechanical and climatic environmental conditions ...............................................................296 15.6 Insulation, protection class, degree of protection and rated voltage ....................................298 15.7 Use of the ET 200SP in zone 2 potentially explosive atmospheres .....................................299 Dimension drawings ............................................................................................................................ 300 A.1 Shield connector ...................................................................................................................300 A.2 Labeling strip .........................................................................................................................300 A.3 Reference identification labels ..............................................................................................301 Accessories/spare parts ...................................................................................................................... 302 B.1 Lightning protection and overvoltage protection for fail-safe modules .................................306 C Calculating the leakage resistance ...................................................................................................... 307 D Safety-relevant symbols ...................................................................................................................... 309 D.1 Safety-related symbols for devices without Ex protection ....................................................309 D.2 Safety-related symbols for devices with Ex protection .........................................................310 Glossary ............................................................................................................................................. 312 Index................................................................................................................................................... 328 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 11 Guide to documentation 1 The documentation for the SIMATIC ET 200SP distributed I/O system is arranged into three areas. This arrangement enables you to access the specific content you require. Basic information The system manual describes in detail the configuration, installation, wiring and commissioning of the SIMATIC ET 200SP. distributed I/O system. The STEP 7 online help supports you in the configuration and programming. Device information Product manuals contain a compact description of the module-specific information, such as properties, wiring diagrams, characteristics and technical specifications. Distributed I/O system 12 System Manual, 02/2018, A5E03576849-AH Guide to documentation General information The function manuals contain detailed descriptions on general topics regarding the SIMATIC ET 200SP distributed I/O system, e.g. diagnostics, communication, Web server, motion control and OPC UA. You can download the documentation free of charge from the Internet (https://support.industry.siemens.com/cs/ww/en/view/109742709). Changes and supplements to the manuals are documented in a Product Information. You can download the product information free of charge from the Internet (https://support.industry.siemens.com/cs/us/en/view/73021864). Manual Collection ET 200SP The Manual Collection contains the complete documentation on the SIMATIC ET 200SP distributed I/O system gathered together in one file. You can find the Manual Collection on the Internet (http://support.automation.siemens.com/WW/view/en/84133942). "mySupport" With "mySupport", your personal workspace, you make the most of your Industry Online Support. In "mySupport" you can store filters, favorites and tags, request CAx data and put together your personal library in the Documentation area. Furthermore, your data is automatically filled into support requests and you always have an overview of your current requests. You need to register once to use the full functionality of "mySupport". You can find "mySupport" in the Internet (https://support.industry.siemens.com/My/ww/en). "mySupport" - Documentation In the Documentation area of "mySupport", you have the possibility to combine complete manuals or parts of them to make your own manual. You can export the manual in PDF format or in an editable format. You can find "mySupport" - Documentation in the Internet (http://support.industry.siemens.com/My/ww/en/documentation). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 13 Guide to documentation "mySupport" - CAx Data In the CAx Data area of "mySupport", you can have access the latest product data for your CAx or CAe system. You configure your own download package with a few clicks. In doing so you can select: Product images, 2D dimension drawings, 3D models, internal circuit diagrams, EPLAN macro files Manuals, characteristics, operating manuals, certificates Product master data You can find "mySupport" - CAx Data in the Internet (http://support.industry.siemens.com/my/ww/en/CAxOnline). Application examples The application examples support you with various tools and examples for solving your automation tasks. Solutions are shown in interplay with multiple components in the system separated from the focus in individual products. You can find the application examples on the Internet (https://support.industry.siemens.com/sc/ww/en/sc/2054). TIA Selection Tool With the TIA Selection Tool, you can select, configure and order devices for Totally Integrated Automation (TIA). This tool is the successor of the SIMATIC Selection Tool and combines the known configurators for automation technology into one tool. With the TIA Selection Tool, you can generate a complete order list from your product selection or product configuration. You can find the TIA Selection Tool on the Internet (http://w3.siemens.com/mcms/topics/en/simatic/tia-selection-tool). Distributed I/O system 14 System Manual, 02/2018, A5E03576849-AH Guide to documentation SIMATIC Automation Tool You can use the SIMATIC Automation Tool to run commissioning and maintenance activities simultaneously on various SIMATIC S7 stations as a bulk operation independently of the TIA Portal. The SIMATIC Automation Tool provides a multitude of functions: Scanning of a PROFINET/Ethernet network and identification of all connected CPUs Address assignment (IP, subnet, gateway) and station name (PROFINET device) to a CPU Transfer of the data and the programming device/PC time converted to UTC time to the module Program download to CPU Operating mode switchover RUN/STOP Localization of the CPU by means of LED flashing Reading out CPU error information Reading the CPU diagnostic buffer Reset to factory settings Updating the firmware of the CPU and connected modules You can find the SIMATIC Automation Tool on the Internet (https://support.industry.siemens.com/cs/ww/en/view/98161300). PRONETA With SIEMENS PRONETA (PROFINET network analysis), you analyze the plant network during commissioning. PRONETA features two core functions: The topology overview independently scans PROFINET and all connected components. The IO check is a fast test of the wiring and the module configuration of a system. You can find SIEMENS PRONETA on the Internet (https://support.industry.siemens.com/cs/ww/en/view/67460624). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 15 Guide to documentation SINETPLAN SINETPLAN, the Siemens Network Planner, supports you in planning automation systems and networks based on PROFINET. The tool facilitates professional and predictive dimensioning of your PROFINET installation as early as in the planning stage. In addition, SINETPLAN supports you during network optimization and helps you to exploit network resources optimally and to plan reserves. This helps to prevent problems in commissioning or failures during productive operation even in advance of a planned operation. This increases the availability of the production plant and helps improve operational safety. The advantages at a glance Network optimization thanks to port-specific calculation of the network load Increased production availability thanks to online scan and verification of existing systems Transparency before commissioning through importing and simulation of existing STEP 7 projects Efficiency through securing existing investments in the long term and optimal exploitation of resources You can find SINETPLAN on the Internet (https://www.siemens.com/sinetplan). Distributed I/O system 16 System Manual, 02/2018, A5E03576849-AH 2 New properties/functions What's new in the system manual ET 200SP, edition 02/2018 compared to edition 12/2016 What's new? New contents Potential distributor modules What are the customer benefits? Where can I find information? Potential distributor modules are a spacesaving replacement for standard potential distributors or potential distributor terminals. You can set up potential groups much faster, in a more compact design and with fewer components than with standard potential distributor systems. Starting from section System overview (Page 19) One application is, for example, the design of digital input modules with 16 channels and 3wire connection. By using the potential distributor modules, you are reserving the unused signal lines of antivalent sensors. Another application is the supply of potentials for external components. Password provider GetSMCinfo instruction As an alternative to manual password input you can connect a password provider to STEP 7. A password provider offers the following advantages: * Convenient handling of passwords. STEP 7 reads the password automatically for the blocks. This saves you time. * Optimal block protection because the operators do not know the actual password. With the help of the GetSMCinfo instruction you can respond to information provided by the memory card in the user program and if required, replace the memory card as a precautionary measure. This makes sense in particular if you write to the card often in your application, for example if you use data logs. Section Know-how protection (Page 166) Section SIMATIC memory card - overview (Page 240) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 17 New properties/functions What's new? What are the customer benefits? Testing with breakpoints Changed contents Reading out the identification and maintenance data using the Get_IM_Data instruction Where can I find information? When testing with breakpoints, you execute a Section Test functions (Page 273) program from one breakpoint to another. Testing with breakpoints provides you with the following advantages: * Testing SCL and STL program code with the help of breakpoints * Localization of logic errors step by step * Simple and quick analysis of complex programs prior to actual commissioning * Recording of current values within individual executed loops * Use of breakpoints for program validation also possible in SCL/STL networks within LAD/FBD blocks With the Get_IM_Data instruction you can read out the identification and maintenance data of the modules without much programming work. Section Reading out and entering I&M data (Page 225) With the Get_IM_Data instruction, you can access the identification and maintenance data (I&M) of a module in the user program. I&M data is information saved in a module. This allows you to * check the system configurations * react to hardware changes react to hardware faults in the user program. Finding and elimination of hardware errors is made easier. * Time synchronization For all applications that need the exact time, you update the CPU time using the NTP process. This also automatically sets the CPU time beyond subnet limits. Section Time synchronization (Page 234) Firmware update via accessible devices You are given information on fast firmware updates via accessible devices in the network. Section Firmware update (Page 257) Distributed I/O system 18 System Manual, 02/2018, A5E03576849-AH System overview 3.1 3 What is the SIMATIC ET 200SP distributed I/O system? SIMATIC ET 200SP SIMATIC ET 200SP is a scalable and highly flexible distributed I/O system for connecting process signals to a higher-level controller via a fieldbus. Customer benefits of the system Figure 3-1 SIMATIC ET 200SP distributed I/O system - Customer benefits Distributed I/O system System Manual, 02/2018, A5E03576849-AH 19 System overview 3.1 What is the SIMATIC ET 200SP distributed I/O system? Area of application Thanks to its multifunctionality, the SIMATIC ET 200SP distributed I/O system is suitable for a wide range of applications. Its scalable design allows you to tailor your configuration to local requirements. Different CPUs/interface modules are available for connection to PROFINET IO or PROFIBUS DP. SIMATIC ET 200SP with CPU allows intelligent pre-processing to relieve the higher-level controller. The CPU can also be used as standalone device. By using fail-safe CPUs, you can implement applications for safety engineering. Configuration and programming of your safety program takes place the same way as for standard CPUs. A wide range of I/O modules rounds off the product range. SIMATIC ET 200SP is designed with degree of protection IP20 and is intended for installation in a control cabinet. Configuration The SIMATIC ET 200SP distributed I/O system is installed on a mounting rail. It consists of: CPU/interface module Up to 64 I/O modules, which can be plugged into BaseUnits in any combination Up to 31 motor starters A server module that completes the configuration of the ET 200SP. Distributed I/O system 20 System Manual, 02/2018, A5E03576849-AH System overview 3.1 What is the SIMATIC ET 200SP distributed I/O system? Configuration example CPU/interface module Light-colored BaseUnit BU..D with infeed of supply voltage Dark-colored BaseUnits BU..B for extending the potential group BaseUnit for motor starter Server module (included in the scope of delivery of the CPU/interface module) ET 200SP motor starter I/O module BusAdapter Mounting rail Reference identification label Figure 3-2 Configuration example of the ET 200SP Distributed I/O system System Manual, 02/2018, A5E03576849-AH 21 System overview 3.2 What are fail-safe automation systems and fail-safe modules? 3.2 What are fail-safe automation systems and fail-safe modules? Fail-safe automation systems Fail-safe automation systems (F-systems) are used in systems with higher safety requirements. F-systems control processes and ensure that they are in a safe state immediately after shutdown. In other words, F-systems control processes in which an immediate shutdown does not endanger persons or the environment. Safety Integrated Safety Integrated is the integrated safety concept for automation and drive technology from Siemens. Proven technologies and systems from automation technology are used for safety systems. Safety Integrated includes the complete safety sequence, ranging from sensor, actuator and fail-safe modules right through to the controller, including safety-related communication via standard fieldbuses. Drives and controllers handle safety tasks in addition to their actual functions. Fail-safe modules The key difference between fail-safe modules (F-modules) and standard modules is that they have an internal two-channel design. This means the two integrated processors monitor each other, automatically test the input and output circuits, and switch the fail-safe module to a safe state in the event of a fault. The F-CPU communicates with a fail-safe module via the safety-related PROFIsafe bus profile. Fail-safe motor starters Fail-safe motor starters enable safety-related tripping of motor loads. Fail-safe motor starters are not PROFIsafe nodes. Motor starters operate together with the fail-safe modules of the ET 200SP system. Area of application of ET 200SP with fail-safe I/O modules By using the ET 200SP distributed I/O system with fail-safe I/O modules, you are replacing conventional safety engineering configurations. This includes the replacement of switching devices for emergency STOP, protective door monitors, two-hand operation, etc. Distributed I/O system 22 System Manual, 02/2018, A5E03576849-AH System overview 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? SIMATIC Safety F-system with ET 200SP The figure below shows an example of a configuration for a SIMATIC Safety F-system with ET 200SP distributed I/O system and PROFINET IO. The PROFINET IO lines can be set up with copper cable, fiber-optic cable or WLAN. Fail-safe I/O modules and non-fail-safe I/O modules can be combined in an ET 200SP configuration. The fail-safe IO controller (F-CPU) exchanges safety-related and non-safety-related data with fail-safe and non-fail-safe ET 200SP modules. Figure 3-3 Fail-safe SIMATIC Safety automation system (sample configuration) Fail-safe ET 200SP I/O modules The following fail-safe I/O modules are available for the ET 200SP distributed I/O system: Fail-safe power modules are used to supply the potential group load voltage and for the safety-related tripping of the load voltage for non-fail-safe output modules. Fail-safe digital input modules detect the signal states of safety-related sensors and send the relevant safety frames to the F-CPU. Fail-safe digital output modules are suitable for safety-related shutdown procedures with short circuit and cross-circuit protection up to the actuator. ET 200SP fail-safe motor starters Fail-safe motor starters are suitable for safety-related tripping of motor loads. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 23 System overview 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? Example of a configuration with fail-safe I/O modules Interface module Light-colored BaseUnit BU..D with infeed of supply voltage Dark-colored BaseUnits BU..B for conducting the potential group further I/O module Server module (ships with the interface module) Fail-safe I/O modules BusAdapter Mounting rail Reference identification label Figure 3-4 Example of a configuration of the ET 200SP with fail-safe I/O modules Distributed I/O system 24 System Manual, 02/2018, A5E03576849-AH System overview 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? Hardware and software requirements Fail-safe modules ET 200SP are supported by IM155-6PN ST interface modules as of firmware V1.1.1, IM155-6PN HF as of firmware V2.0, IM155-6PN HS as of firmware V4.0 and IM155-6DP HF as of firmware V1.0. You require the STEP 7 Safety Advanced option package, V12 or higher including HSP 54, for configuration and programming of the ET 200SP fail-safe modules with the SIMATIC Safety fail-safe system. You require the F-Configuration Pack V5.5 SP10 or later for configuring and programming the ET 200SP failsafe modules with the Distributed Safety failsafe system. You require the F-Configuration Pack V5.5 SP12 or later for configuring and programming the ET 200SP failsafe modules with the F/FH Systems failsafe system. ET 200SP fail-safe motor starters are supported by interface modules IM155-6PN BA, firmware V3.2 or higher, IM155-6PN ST, firmware V3.1 or higher, IM155-6PN HF, firmware V3.1 or higher and IM155-6DP HF firmware V3.0 or higher. You require SIMATIC Step 7 V14 or higher for configuration and programming of ET 200SP fail-safe motor starters. The F-Configuration Pack is not needed for configuration and programming of the ET 200SP fail-safe motor starter. Note Configuration of ET 200SP motor starters, SIMATIC Step 7 V13 or higher, is possible with a GSD file (GSDML). Use in safety mode only Safety mode is the F-I/O operating mode that allows safety-related communication using safety frames. Safety mode of motor starters is characterized by the fail-safe digital input (F-DI) and availability of the 24 V power supply. You can only use the ET 200SP fail-safe I/O modules in safety mode. They cannot be used in non-fail-safe mode. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 25 System overview 3.3 How are SIMATIC Safety F-systems structured with ET 200SP? Achievable safety classes The fail-safe modules are equipped with integrated safety functions for safety mode. You can achieve the safety classes of the table below: With the appropriate parameter assignment of the safety functions in STEP 7 With a specific combination of fail-safe and non-fail-safe I/O modules With a special arrangement and wiring of the sensors and actuators Table 3- 1 Safety classes that can be achieved with ET 200SP in safety mode Safety class in safety mode According to IEC 61508 In accordance with ISO 13849-1 SIL2 Category 3 (PL) Performance Level d SIL3 Category 3 (PL) Performance Level e SIL3 Category 4 (PL) Performance Level e Additional information You will find the use cases and wiring for the relevant safety class in the manuals of the fail-safe I/Os and the fail-safe motor starters. Distributed I/O system 26 System Manual, 02/2018, A5E03576849-AH System overview 3.4 Components 3.4 Components Basic components of the ET 200SP distributed I/O system Table 3- 2 Basic components of the ET 200SP Basic component Function Mounting rail in accordance with EN 60715 The mounting rail is the rack of the ET 200SP. The ET 200SP is installed on the mounting rail. The mounting rail is 35 mm high. CPU/Fail-safe CPU The (F) CPU: * Runs the user program. The F-CPU also runs the safety program. * Can be used as an IO controller or I-Device on PROFINET IO or as a standalone CPU * Links the ET 200SP to the IO devices or the IO controller Figure Exchanges data with the I/O modules via the backplane bus. Additional CPU functions: * * Communication via PROFIBUS DP (the CPU can be used as a DP master or DP slave in combination with the CM DP communication module) * Integrated Web server * Integrated technology * Integrated trace functionality * Integrated system diagnostics * Integrated safety * Safety mode (when using fail-safe CPUs) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 27 System overview 3.4 Components Basic component Communication module CM DP Interface module for PROFINET IO Interface module for PROFIBUS DP Function Figure The communication module CM DP * Connects the CPU with PROFIBUS DP * The bus connection is an RS485 interface The interface module: * Can be used as IO device on PROFINET IO * Links the ET 200SP with the IO controller * Exchanges data with the I/O modules via the backplane bus. The interface module: * Can be used as DP slave on PROFIBUS DP * Links the ET 200SP with the DP master * Exchanges data with the I/O modules via the backplane bus. Distributed I/O system 28 System Manual, 02/2018, A5E03576849-AH System overview 3.4 Components Basic component BusAdapter Function Figure The BusAdapters allow free selection of the connection technology for PROFINET IO. The following versions are available for PROFINET CPU/interface modules: * For standard RJ45 connector (BA 2xRJ45) * For direct connection of the bus cable (BA 2xFC) * For POF/PCF fiber-optic cable (BA 2xSCRJ) * As media converter for POF/PCF fiber-optic cable standard RJ45 plug (BA SCRJ/RJ45) * As media converter for POF/PCF fiber-optic cable direct connection of the bus cable (BA SCRJ/FC) * For glass fiber-optic cable (BA 2xLC) * As media converter for glass fiber-optic cable standard RJ45 plug (BA LC/RJ45) * As media converter for glass fiber-optic cable direct connection of the bus cable (BA LC/FC) For mixed ET 200SP/ET 200AL configuration, you require the BusAdapter BA-Send 1xFC (plugged into the BaseUnit BU-Send). Connect the bus cable for ET-Connection to the BusAdapter BA-Send 1xFC. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 29 System overview 3.4 Components Basic component Function BaseUnit The BaseUnits provide the electrical and mechanical connection of the ET 200SP modules. Place the I/O modules or the motor starter onto the BaseUnits. Suitable BaseUnits are available in each case for the different requirements. You can find additional information in section Selecting the BaseUnit for I/O modules (Page 40). PotDis-BaseUnit potential distributor module You use the potential distributor module to distribute a variety of potentials (P1, P2). This allows you to implement a multi-cable connection without external terminals with 16-channel digital modules. Figure The assembly has two parts: * If you need additional potential terminals, plug a PotDis-TerminalBlock in the PotDis-BaseUnit. Alternatively, plug a BU cover (15 mm) on the PotDis-BaseUnit. With potential distributor modules, you may only connect to the PotDis-TB versions BR-W and n.c.-G potential, which exceed the voltage level of SELV/PELV. Other SELV/PELV potential groups should be separated with light-colored PotDis BUs. * Suitable PotDis-BaseUnits are available in each case for the different requirements. You can find additional information in section Selecting a PotDis-BaseUnit (Page 45). PotDis-TerminalBlock If you need additional potential terminals for a PotDis-BaseUnit, plug a PotDis-TerminalBlock in the PotDis-BaseUnit. Voltages greater than SELV/PELV are only permitted for the PO PotDis-TBs BR (bridged) and NC (not connected). The same applies to PE. Voltages at the terminals of the PotDis modules connected to the P1/P2 rails must not be greater than SELV/PELV. Suitable PotDis-TerminalBlocks are available in each case for the different requirements. You can find additional information in section Selecting a PotDis-TerminalBlock (Page 46). Distributed I/O system 30 System Manual, 02/2018, A5E03576849-AH System overview 3.4 Components Basic component Function Fail-safe power module The fail-safe power module allows the safetyrelated shutdown of digital output modules / failsafe digital output modules. I/O module / fail-safe I/O module The I/O module determines the function at the terminals. The controller detects the current process state via the connected sensors and actuators, and triggers the corresponding reactions. I/O modules are divided into the following module types: Motor starter/fail-safe motor starter * Digital input (DI, F-DI) * Digital output (DQ, F-DQ PM, F-DQ PP, F-RQ) * Analog input (AI) * Analog output (AQ) * Technology module (TM) * Communication module (CM) Figure The motor starter is a switching and protection device for 1-phase and 3-phase loads. The motor starter is available as a direct-on-line and reversing starter. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 31 System overview 3.4 Components Basic component Vale terminal AirLINE SP type 8647 (Burkert GmbH & Co. KG) 1) 2) Function Figure Basic component: Valve terminal AirLINE SP type 8647 (Burkert). For more information on the AirLINE SP, type 8647 (e.g. data sheet and operating instructions), please contact Burkert (https://www.burkert.co.uk/en/type/8647) directly. Function: Valve terminals are common in industrial automation and are used as pilot valves for controlling pneumatic actuators, for example in areas of the food, pharmaceutical and water treatment industries. The ET 200SP in combination with the AirLINE SP, type 8647 from Burkert provides a universal interface between process and plant control that enables the flexible, modular configuration of pilot valves and I/O modules. The valve terminal can also be fitted to the base of the control cabinet with the help of the AirLINE Quick Adapter. This further reduces the space required in the control cabinet and considerably simplifies installation of the pneumatic system. 1) 2) BU cover Insert the BU cover on the BaseUnits: * Whose slots are not equipped with I/O modules/ motor starters// PotDis-TerminalBlocks. Whose slots have been reserved for future expansion (as empty slots). You can keep a reference identification label for the planned I/O module inside the BU cover. * There are three versions: * For BaseUnits with a width of 15 mm * For BaseUnits with a width of 20 mm * For BaseUnits of motor starters with a width of 30 mm Distributed I/O system 32 System Manual, 02/2018, A5E03576849-AH System overview 3.4 Components Basic component Server module Function Figure The server module completes the configuration of the ET 200SP. The server module includes holders for 3 spare fuses (5 x 20 mm). The server module ships with the CPU/interface module. Coding element The coding element codes the I/O module with the BaseUnit. There are two versions: * * Mechanical coding element : Ensures the coding Electronic coding element : This version also has an electronic, rewritable memory for module-specific configuration data (such as the F-destination address for fail-safe modules, parameter data for the IO link master). 1) Note: The description contains non-binding information on supplementary products that are manufactured and marketed not by Siemens but by third-parties outside the Siemens group ("third-party firms"). These third parties organize the manufacture, sale and delivery of their products independently and their terms and conditions apply. Responsibility for these supplementary products and for the information relating to them that is provided here thus lies solely with the third parties in question. Unless bound to do so by statutory requirements, Siemens shall not accept any liability or provide any guarantee for the supplementary products of third-party firms. Please also note the information "Disclaimer/Use of hyperlinks". 2) Disclaimer/Use of hyperlinks: Siemens has put together this description with great care. However, Siemens is unable to check whether the data provided by third-party firms is complete, accurate and up to date. Certain items of information may therefore potentially be incorrect, incomplete or no longer up to date. Siemens shall not accept any liability should this be the case, nor shall it accept liability for the usability of the data or of the product for the user unless it has a statutory obligation to do so. This entry contains the addresses of third-party websites. Siemens is not responsible for and shall not be liable for these websites or their content, as Siemens has not checked the information contained therein and is not responsible for the content or information they provide. The use of such websites is at the user's own risk. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 33 System overview 3.4 Components Accessories of the ET 200SP distributed I/O system Table 3- 3 Accessories of the ET 200SP Accessories Function 24 V DC connector Applying the 24 V DC supply at the connector and connection with the CPU/interface module, for example. Shield connection The shield connection allows the low-impedance contacting of cable shields with minimum installation times. Labeling strips Attach the labeling strips to the modules for system-specific labeling of the ET 200SP. The labeling strips can be printed. Figure The labeling strips can be ordered as accessories (Page 302) on a roll for thermal transfer printers or as DIN A4 format sheets for laser printers. Reference identification labels The labels enable the reference identification labeling of the ET 200SP components. The labels can be ordered on a mat for thermal transfer and inkjet printers as accessories (Page 302). Color identification labels The color identification labels are modulespecific and can be ordered for the process terminals, AUX terminals and additional terminals as accessories (Page 302). Distributed I/O system 34 System Manual, 02/2018, A5E03576849-AH System overview 3.4 Components Accessories of the SIMATIC ET 200SP motor starters Table 3- 4 SIMATIC ET 200SP motor starter accessories Accessories 3DI/LC module Function Figure The optional 3DI/LC module has three digital inputs and one LC input. For reasons of operational safety, input LC is permanently set to manual local mode. By parameterizing the inputs DI1 - DI3 with motor CLOCKWISE or motor COUNTERCLOCKWISE, you can control the motor in manual local mode. The functions of the 3DI/LC module are not relevant to functional safety. Detailed information on the functions when using a 3DI/LC module can be found in the Manual (https://support.industry.siemens.com/cs/ww/en/vie w/109479973). Mechanical bracket for BaseUnit Use the mechanical bracket for additional fixing of the motor starter. You can use the mechanical bracket on 7.5 mm and 15 mm mounting rails. Infeed bus cover For finger-safe termination of the infeed bus, use the cover. Fan You can use the motor starter at higher ambient temperatures if a fan is installed. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 35 Application planning 4 Overview The BaseUnits (BU) are classified according to different types. Every BaseUnit type is distinguished by characteristics that match certain I/O modules and motor starters (see the following table and graphics). You recognize the BU type for an I/O module by the last two digits of an I/O module's article number. The BU type onto which you can plug the respective I/O module is printed on the I/O modules. You can therefore read which BU type you need straight from the I/O module (see Factory labels (Page 127) (page 122)). Example: On the output module DQ 16x24VDC/0.5A ST with article number 6ES71326BH01-0BA0 the information "BU: A0" is printed. This means you can plug this I/O module to a BaseUnit of the BU type "A0", which means on any BaseUnit whose article number ends in "A0". I/O modules that are suitable for two BU types are labeled accordingly, for example "BU: A0, A1". Note You will find a complete overview of the possibilities of combining BaseUnits and I/O modules /motor starters in the Product information for documentation of the ET 200SP I/O system (http://support.automation.siemens.com/WW/view/en/73021864). Distributed I/O system 36 System Manual, 02/2018, A5E03576849-AH Application planning Table 4- 1 Selecting a suitable BaseUnit for I/O modules Selecting a BaseUnit BU type A0 See Digital, fail-safe, communication, technology or analog modules without temperature measurement (Page 40) I/O module Examples of suitable I/O modules for BU types (example) I/O module (example) BaseUnit Digital, fail-safe, technology or communication module DI 16x24VDC ST BU15-P16+A0+2D (6ES7131-6BH00-0BA0) (6ES7193-6BP00-0DA0) * 6ES7...A0 * 24 V DC * 15 mm wide Analog module without temperature measurement** BU type A1 See Analog modules with temperature measurement (Page 41) BU type B0 (BU..B, dark-colored BaseUnit) * 6ES7...A1 * 24 V DC * 15 mm wide Analog module with temperature measurement* * 6ES7...A1 * 24 V DC * 15 mm wide Digital output module with relay * 6ES7...B0 * Up to 230 V AC * 20 mm wide BU type B1 Digital modules (BU..B, dark-colored BaseUnit) * 6ES7...B1 * up to 230 V AC * 20 mm wide BU type C0 (BU..D, light-colored BaseUnit) Fail-safe power module * 6ES7...C0 * 24 V DC AI 4xU/I 2-wire ST (6ES7134-6HD00-0BA1) AI 4xRTD/TC 2-/3-/4wire HF (6ES7134-6JD00-0CA1) RQ 4x120VDC230VAC/5A NO ST (6ES7132-6HD00-0BB0) BU15P16+A0+2D/T(6ES71936BP00-0DA1) BU20-P12+A4+0B (6ES7193-6BP20-0BB0) DI 4x120..230VAC ST (6ES7131-6FD00-0BB1) BU20-P12+A0+4B CM AS-i Master ST BU20-P6+A2+4D (3RK7137-6SA00-0BC1) (6ES7193-6BP20-0DC0) (6ES7193-6BP20-0BB1) * 20 mm wide CM ASi Master ST/FCM AS-i Safety ST * 6ES7...C1 * Up to 30 V DC * 20 mm wide Distributed I/O system System Manual, 02/2018, A5E03576849-AH 37 Application planning Selecting a BaseUnit BU type C1 (BU..B, dark-colored BaseUnit) BU type D0 BU type F0 BU type U0 I/O module Examples of suitable I/O modules for BU types (example) I/O module (example) BaseUnit F-CM AS-i Safety ST F-CM AS-i Safety ST (3RK7136-6SC00-0BC1) BU20-P6+A2+4B AI Energy Meter 480VAC ST BU20-P12+A0+0B * 6ES7...C1 * Up to 30 V DC * 20 mm wide AI Energy Meter * 6ES7...D0 * Up to 400 V AC/ 480 V AC * 20 mm wide (6ES7134-6PA20-0BD0) FFRQ 1x24VDC/24..230 RQ 1x24VDC/24..230VA VAC/5A C/5A (6ES7136-6RA00-0BF0) * 6ES7...F0 * Up to 230 V AC * 20 mm wide DQ 4x24...230VAC/2 A HF * 6ES7...U0 * Up to 230 V AC * 20 mm wide (6ES7193-6BP20-0BC1) (6ES7193-6BP00-0BD0) BU20-P8+A4+0B (6E7193-6BP20-0BF0) DQ 4x24...230VAC/2A HF BU20-P16+A0+2D (6ES7132-6FD00-0CU0) (6E7193-6BP00-0BU0) * For compensation of the reference junction temperature for thermocouples. The BU type A1 is required if measuring the reference junction temperature with an internal temperature sensor or if you need the 2x5 additional terminals. ** Analog modules with temperature measurement can be plugged on BU type A0. Distributed I/O system 38 System Manual, 02/2018, A5E03576849-AH Application planning Table 4- 2 BaseUnit for motor starters Selecting the BaseUnit BU-30MS1 24 V infeed x 500 V infeed x BU-30MS2 BU-30MS3 BU-30MS4 BU-30MS5 BU-30MS6 x x x F-DI terminals x x Motor starters DS 0.3 - 1A HF 3RK1308-0AB00-0CP0 x x x x x* x* DS 0.9 - 3A HF 3RK1308-0AC00-0CP0 x x x x x* x* DS 2.8 - 9A HF 3RK1308-0AD00-0CP0 x x x x x* x* DS 4.0 - 12A HF 3RK1308-0AE00-0CP0 x x x x x* x* RS 0.3 - 1A HF 3RK1308-0BB00-0CP0 x x x x x* x* RS 0.9 - 3A HF 3RK1308-0BC00-0CP0 x x x x x* x* RS 2.8 - 9A HF 3RK1308-0BD00-0CP0 x x x x x* x* RS 4.0 - 12A HF 3RK1308-0BE00-0CP0 x x x x x* x* F-DS 0.3 - 1A HF 3RK1308-0CB00-0CP0 x x x x x x F-DS 0.9 - 3A HF 3RK1308-0CC00-0CP0 x x x x x x F-DS 2.8 - 9A HF 3RK1308-0CD00-0CP0 x x x x x x F-DS 4.0 - 12A HF 3RK1308-0CE00-0CP0 x x x x x x F-RS 0.3 - 1A HF 3RK1308-0DB00-0CP0 x x x x x x F-RS 0.9 - 3A HF 3RK1308-0DC00-0CP0 x x x x x x F-RS 2.8 - 9A HF 3RK1308-0DD00-0CP0 x x x x x x F-RS 4.0 - 12A HF 3RK1308-0DE00-0CP0 x x x x x x * The F-DI terminals have no function with this combination. Additional information Additional information on the functional assignment of the terminals and on the associated BaseUnits can be found in one of the following manuals: Manual for the relevant I/O module (http://support.automation.siemens.com/WW/view/en/55679691/133300) Manual BaseUnits (http://support.automation.siemens.com/WW/view/en/59753521) Motor starter (https://support.industry.siemens.com/cs/ww/en/view/109479973) manual Distributed I/O system System Manual, 02/2018, A5E03576849-AH 39 Application planning 4.1 Selecting the BaseUnit for I/O modules 4.1 Selecting the BaseUnit for I/O modules 4.1.1 Digital, fail-safe, communication, technology or analog modules without temperature measurement Selection of a suitable BaseUnit Light-colored BaseUnit: Configuration of a new potential group, electrical isolation from adjacent module on the left. The first BaseUnit of the ET 200SP is usually a light-colored BaseUnit for feeding the supply voltage L+. Exception: If you insert an AC I/O module or an AI Energy Meter as the first I/O module, the first BaseUnit in the ET 200SP configuration can be a dark-colored BaseUnit. The requirement is that you use a CPU or IM 155-6 (as of V3.0). Dark-colored BaseUnit: Conduction of the internal power and AUX buses from the adjacent module on the left. AUX terminal: 10 internally bridged terminals for individual use up to 24 V DC/10 A or as protective conductors. Example: Multiple cable connection for DI 8x24VDC ST Figure 4-1 Digital, fail-safe, communication, technology or analog modules without temperature measurement Distributed I/O system 40 System Manual, 02/2018, A5E03576849-AH Application planning 4.1 Selecting the BaseUnit for I/O modules 4.1.2 Analog modules with temperature measurement Selection of a suitable BaseUnit Light-colored BaseUnit: Configuration of a new potential group, electrical isolation from adjacent module on the left. The first BaseUnit of the ET 200SP is usually a light -colored BaseUnit for feeding the supply voltage L+. Dark-coloredBaseUnit: Continuation of the internal power and AUX buses from the adjacent module on the left. Additional terminals: 2x5 internally bridged terminals for individual use up to 24 V DC/2 A Example: Sensor supply for AI 4xU/I 2-wire ST Figure 4-2 Analog modules with temperature measurement Distributed I/O system System Manual, 02/2018, A5E03576849-AH 41 Application planning 4.2 Selecting motor starters with a suitable BaseUnit 4.2 Selecting motor starters with a suitable BaseUnit 4.2.1 Selecting a BaseUnit for motor starters The motor starter BaseUnits "BU30-MS1", "BU30-MS2", "BU30-MS3" and "BU30-MS4" are compatible with all non-fail-safe motor starters. The motor starter BaseUnits "BU30-MS1", "BU30-MS2", "BU30-MS3", "BU30-MS4", "BU30-MS5" and "BU30-MS6" are compatible with all fail-safe motor starters. You will find an overview of available BaseUnits for motor starters here (Page 36). With the different BaseUnits, you can form different potential groups for the 24 V DC electronics supply (L+/M) and for the AC infeed. Voltage range The voltage range of the AC infeed is between 48 V AC and 500 V AC. Selection criteria for the BaseUnit The figure below shows the criteria you use to select the appropriate BaseUnit: Form separate potential groups on the infeed bus for single-phase (L, N, PE) and threephase (L1, L2, L3, PE) operation. Distributed I/O system 42 System Manual, 02/2018, A5E03576849-AH Application planning 4.2 Selecting motor starters with a suitable BaseUnit 4.2.2 Selecting the motor starter You select the suitable motor starter using the load type according to the following scheme: Distributed I/O system System Manual, 02/2018, A5E03576849-AH 43 Application planning 4.2 Selecting motor starters with a suitable BaseUnit 4.2.3 Selecting accessories for motor starters Observe the installation conditions of the station with ET 200SP motor starters. The figure below shows the criteria the station must meet: Distributed I/O system 44 System Manual, 02/2018, A5E03576849-AH Application planning 4.3 Selecting potential distributor modules 4.3 Selecting potential distributor modules 4.3.1 Selecting a PotDis-BaseUnit Selection of a suitable PotDis-BaseUnit potential distributor module Light-colored PotDis-BaseUnit: Configuration of a new potential group, electrical isolation from adjacent module on the left. The first BaseUnit of the ET 200SP is usually a light-colored BaseUnit for the incoming supply voltage. P1 terminal: 16 internally bridged terminals for individual use up to 48 V DC/10 A Example: Multiple cable connection for DI 16x24VDC ST Figure 4-3 PotDis-BaseUnits Distributed I/O system System Manual, 02/2018, A5E03576849-AH 45 Application planning 4.3 Selecting potential distributor modules Please note: The potential groups opened with a light-colored PotDis-BU must not contain any I/O modules. You can integrate any dark-colored PotDis-BUs into I/O module potential groups provided they are based on an SELV/PELV supply. If you do not need the additional terminals of the PotDis-TB in a potential distributor module, replace the PotDis-TB with a BU cover. You may only connect one potential group within a combination of PotDis-BU and PotDis-TB. Only SELV/PELV potentials are permitted on PotDis-BUs. Separate different SELV/PELV potential groups using light-colored PotDis-BUs. With potential distributor modules, you may only connect to the PotDis-TB versions BR-W and n.c.-G potential, which exceed the voltage level of SELV/PELV. PotDis terminals are not directly configurable as PotDis via GSD/GSDML. When configuring with GSD, always use an dummy module; with GSDML, integrate a free space. Additional information Additional information on the potential distributor modules (PotDis-BaseUnits and PotDisTerminalBlocks) is available in the BaseUnits (http://support.automation.siemens.com/WW/view/en/59753521) manual. 4.3.2 Selecting a PotDis-TerminalBlock Selection of a suitable PotDis-TerminalBlock With a PotDis-TerminalBlock you are expanding a PotDis-BaseUnit potential distributor module by an additional 18 potential terminals. You can freely combine PotDis-TerminalBlocks and PotDis-BaseUnits. The following PotDis-TerminalBlocks are available: Table 4- 3 Selection of TerminalBlock PotDis-TB PotDis-TerminalBlocks TerminalBlock Explanation Application PotDis-TB-P1-R Terminal block with 18 terminals with red spring releases with connection to the supply voltage P1 of the PotDis-BaseUnit with SELV/PELV. Provision of 18 x P1 potential, e.g. for P1 sensor supply with 3-wire connection for 16-channel digital input modules PotDis-TB-P2-B Terminal block with 18 terminals with blue spring releases with connection to ground (P2) of the PotDis-BaseUnit Provision of 18 x P2 potential, e.g. for ground of the sensor supply with 2-wire connection for 16channel digital output modules Distributed I/O system 46 System Manual, 02/2018, A5E03576849-AH Application planning 4.3 Selecting potential distributor modules PotDis-TerminalBlocks PotDis-TB-n.c.-G Terminal block with 18 terminals with gray spring releases without connection to each other or to a voltage bus of the PotDis-BaseUnit Provision of 18 x n.c. (not connected), for reserving ("parking") unused signals/lines, e.g. for antivalent sensors in the same potential group PotDis-TB-BR-W Terminal block with 18 terminals connected to each other with white spring releases without connection to a voltage bus of the PotDis-BaseUnit Provision of 17 terminals with shared potential (the 18th terminal is used for infeed) for supply of external consumers Additional information Additional information on the potential distributor modules (PotDis-BaseUnits and PotDis-TerminalBlocks) is available in the BaseUnits (http://support.automation.siemens.com/WW/view/en/59753521) manual. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 47 Application planning 4.4 Hardware configuration 4.4 Hardware configuration Maximum mechanical configuration As soon as one of the following rules applies, the maximum configuration of the ET 200SP has been reached: Table 4- 4 Maximum mechanical configuration Properties Rule Number of modules Maximum of 12/30/32/64 I/O modules (depending on the CPU used/the interface module used; see CPU (http://support.automation.siemens.com/WW/view/en/9046643 9/133300) and interface module (http://support.automation.siemens.com/WW/view/en/5568331 6/133300) manuals) For every 6 F-modules F-RQ 1x24VDC/24..230VAC/5A (6ES7136-6RA00-0BF0), the maximum configuration is reduced by 1 module. Number of motor starters Maximum of 31 motor starters Backplane bus length of the ET 200SP maximum 1 m mounting width (without CPU/interface module, including server module) Electrical maximum configuration for I/O modules The number of operable I/O modules of a potential group is limited by the following factors: Power consumption of the I/O modules Power consumption of the components supplied via these I/O modules The maximum current carrying capacity of the terminals on the BaseUnit L+/M is 10 A. Current carrying capacity refers to the current load via the power bus and the infeed bus of the ET 200SP station. Consider the current carrying capacity when using a motor starter. Maximum electrical configuration for motor starter power bus (24 V DC) To determine the current requirement of an individual motor starter via the power bus, take account of the following parameters: Current consumption via DC infeed in the ON state Current consumption via DC infeed when switching on (40 ms peak load) Increased power consumption through fan operation Current requirement via encoder supply of the connected DI module The maximum current carrying capacity of the 24 V potential group is 7 A across the entire permissible temperature range. Distributed I/O system 48 System Manual, 02/2018, A5E03576849-AH Application planning 4.4 Hardware configuration Maximum electrical configuration for motor starter infeed bus (500 V AC) To determine the current requirement of an individual motor starter via the infeed bus, proceed as follows: Calculate the current requirement via the main current paths of the individual motor starter. In doing so, take into account the parameter Ie (set rated operational current of the motor starter). The permissible overload characteristics of the motor feeder for motors are determined with the thermal motor model. You calculate the current value (Iinfeed bus) for the infeed bus of the ET 200SP system according to the following formula: Iinfeed bus = n(Ie * 1.125) n = number of motor starters of a potential group on the infeed bus Refer to the Manual (https://support.industry.siemens.com/cs/ww/en/view/109479973) for details of how to assign the basic rated operational current Ie parameter. The following values apply for the potential group of the AC infeed: The maximum current carrying capacity is 32 A at an ambient temperature of up to 50 C. The maximum current carrying capacity is 27 A at an ambient temperature of up to 60 C. The maximum current carrying capacity for applications according to UL requirements is 24 A at an ambient temperature of up to 60 C. Address space The address space depends on the CPU/interface module (see CPU (http://support.automation.siemens.com/WW/view/en/90466439/133300) Manual) and the interface module used (see Interface module (http://support.automation.siemens.com/WW/view/en/55683316/133300) Manual): For PROFINET IO: Dependent on the IO controller/IO device used For PROFIBUS DP: Dependent on the DP master used Distributed I/O system System Manual, 02/2018, A5E03576849-AH 49 Application planning 4.5 Forming potential groups 4.5 Forming potential groups 4.5.1 Basics Introduction Potential groups for the ET 200SP distributed I/O system are formed by systematically arranging the BaseUnits. Requirements For formation of potential groups, the ET 200SP distinguishes between the following BaseUnits: BaseUnits BU...D (recognizable by the light-colored terminal box and the light-colored mounting rail release button): - Opening of a new potential group (power busbar and AUX bus are interrupted to the left) - Infeed of the supply voltage L+ up to an infeed current of 10 A BaseUnits BU...B (recognizable by the dark-colored terminal box and the dark-colored mounting rail release button): - Conduction of the potential group (power busbar and AUX bus continued) - Pick up of the supply voltage L+ for external components or loop-through with a maximum total current of 10 A BaseUnits BU30-MSx (BaseUnit for the motor starter only) Depending on the version, the BaseUnits in the "BU30-MSx" model series possess the following properties: - Opening a new potential group or continuing an existing one - Feeding in the supply voltage L+ up to an infeed current of 7 A DC - Opening a new load group or continuing an existing one by means of 500 V AC infeed bus - Feeding in the line voltage up to an infeed current of 32 A AC Distributed I/O system 50 System Manual, 02/2018, A5E03576849-AH Application planning 4.5 Forming potential groups Placement and grouping of I/O modules Each BaseUnit BU...D that you install in the ET 200SP configuration opens a new potential group and supplies all subsequent I/O modules (on BaseUnits BU...B) with the necessary supply voltage. The first 24 V DC I/O module to the right of the CPU/interface module must be installed on a light-colored BaseUnit BU...D. Exception: If you insert an AC I/O module or an AI Energy Meter as the first I/O module, the first BaseUnit in the ET 200SP configuration can be a dark-colored BaseUnit. The requirement is that you use a CPU or IM 155-6 (as of V3.0). If you want to place another BaseUnit BU...B after a BaseUnit BU...D, disconnect the power and AUX buses and open a new potential group at the same time. This allows individual grouping of the supply voltages. Note All BaseUnits placed in a load group must match the infeed potential of the corresponding light-colored BaseUnits. Do not connect any BaseUnit of the "BU...B" type on the right of a motor starter's BaseUnit (BU30-MSxx). Placing and connecting potential distributor modules Potential distributor modules provide potential distributors integrated into the system that you can use to configure a rapid, space-saving customized replacement for standard potential distribution systems. You can place potential distributor modules at any location within the ET 200SP distributed I/O system. To do so, you must observe the same design rules as for placing and connecting I/O modules. Potential distributor modules are only suitable for SELV/PELV. A potential distributor module consists of a potential distributor BaseUnit (PotDis-BU) and (if necessary) a potential distributor TerminalBlock (PotDis-TB) plugged onto it. If you do not need the additional terminals of the PotDis-TB, install a BU cover (15 mm) on the PotDis-BaseUnit. You must not place a BaseUnit for I/O modules in a PotDis potential group formed with a light-colored PotDis-BaseUnit. Note Identical voltages with potential distributor modules You can only connect identical (supplied) voltages with to the terminals of a potential distributor module or PotDis potential group. Example: You only connect 24 V DC. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 51 Application planning 4.5 Forming potential groups Placement and grouping of I/O modules and motor starters For the potential group (L+/M), the following slot rules apply within the motor starter modules and other I/O modules of the ET 200SP: An unassembled BaseUnit (BaseUnit with BU cover) must be inserted between the CPU, an interface module or an I/O module and the motor starter. This is not necessary between the motor starters. The empty slot can take on the potential (24 V DC) of the potential group on the left of it (L+, M), i.e. I/O modules and motor starters can be operated in the same potential group. If you would like to insert an I/O module on the right of a motor starter, then use only one BaseUnit of the BU...D Typ A0 type (light terminal box). The BaseUnits BU30-MS2, BU30-MS4, BU30-MS5 and BU30-MS6 can take on the potential groups of other BaseUnit types. However, pay attention to the following exceptions: - Only a BaseUnit of type BU30-MS1 or BU30-MS3 may follow an AS-i module (AS-i potential group). - Only BaseUnits with fail-safe motor starters can be connected together in the same potential group of an F-PM-E. WARNING Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Hazardous electrical voltage can cause electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. Distributed I/O system 52 System Manual, 02/2018, A5E03576849-AH Application planning 4.5 Forming potential groups AUX bus (AUX(iliary) bus) BaseUnits with additional AUX terminals (e.g. BU15-P16+A10+2D) enable the additional connection of a potential (up to the maximum supply voltage of the module), which is applied via the AUX bus. In the case of light-colored BaseUnits, the AUX bus is interrupted to the left. In the case of BaseUnits of motor starters, the AUX bus is interrupted to the left. The AUX bus can be used individually: You can plug a maximum of 8 I/O modules into the corresponding potential group as a PE bar. For additionally required voltage NOTICE AUX bus as PE bar If you use an AUX bus as a protective conductor bar, attach the yellow-green color identification labels to the AUX terminals, and establish a functional connection to the central protective conductor connection. If you stop using the AUX bus as a protective conductor bar, make sure you remove the yellow-green color identification labels and remove the connection to the central protective conductor connection again. The AUX bus is designed as follows: Maximum current carrying capacity (at 60 C ambient air temperature): 10 A Permissible voltage: Depending on the BaseUnit type (see BaseUnit manual (http://support.automation.siemens.com/WW/view/en/59753521)) Self-assembling voltage buses You must feed in the supply voltage L+ via the BaseUnit BU...D, BU30-MS1 or BU30-MS3 . Each BaseUnit BU...B allows access to the supply voltage L+ via terminals (red/blue). The motor starter BaseUnits "BU30-MS1", "BU30-MS2", "BU30-MS3", "BU30-MS4", "BU30-MS5" and "BU30-MS6" do not have this access. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 53 Application planning 4.5 Forming potential groups Operating principle 1 CPU/interface module 14 Server module 2 BaseUnit BU...D 15 Self-assembling voltage buses P1/P2 3 BaseUnit BU...B 16 AUX bus 4 Potential group 1 17 Infeed bus 500 V AC (L1, L2(N), L3, PE) 5 Potential group 2 18 Supply voltage L+ 6 Potential group 3 19 Supply voltage L+ (3) 7 BaseUnit BU...B with dummy module 20 Additionally required voltage 8 BaseUnit BU30-MS2 21 Supply voltage L+ (2) 9 BaseUnit BU30-MS4 22 Protective conductor (green/yellow) 10 BaseUnit BU30-MS1 23 Supply voltage L+ (1) 11 Potential group 4 24 Supply voltage 1L+ 12 BaseUnit BU30-MS4 13 Backplane bus Figure 4-4 Placing the BaseUnits Connecting different potentials to the power or AUX bus Note If you apply different potentials to the power or AUX bus within an ET 200SP station, you need to separate the potential groups with a BaseUnit BU...D. Distributed I/O system 54 System Manual, 02/2018, A5E03576849-AH Application planning 4.5 Forming potential groups 4.5.2 Forming potential groups with BaseUnit type B1 Introduction The AC I/O modules of the ET 200SP are required to connect sensors/actuators with alternating voltage 24 to 230 V AC. Requirements BaseUnits BU20-P12+A0+4B (BU type B1) and DI 4x120..230VAC ST digital input module DQ 4x24..230VAC/2A ST digital output module Operating principle Connect the required alternating voltage for the AC I/O modules directly at the BaseUnits BU20-P12+A0+4B (terminals 1L, 2L/1N, 2N). Insert the AC I/O modules on the BaseUnits. Note Placing the BaseUnits for AC I/O modules If you insert an AC I/O module as the first I/O module, a BaseUnit BU20-P12+A0+4B can be the first BaseUnit to the right of the CPU/interface module in the ET 200SP configuration. The requirement is that you use a CPU as of V3.0 or IM 155-6 (as of V3.0). * The BaseUnits BU20-P12+A0+4B do not monitor the connected alternating voltage. Please note the information on limiting the overvoltage and power rating in the AC I/O module manuals. * Remember to take the BaseUnit type into account during configuration. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 55 Application planning 4.5 Forming potential groups 4.5.3 CPU/interface module Figure 4-5 Placing the BaseUnits for the AC I/O modules 24 V DC potential group BaseUnits with DC I/O modules BaseUnits BU 20-P12+A0+4B with AC I/O modules Direct voltage Alternating voltage Forming potential groups with fail-safe modules Introduction ET 200SP distributed I/O systems can be configured using fail-safe and non-fail-safe modules. This chapter provides an example of a mixed configuration comprising fail-safe and non-fail-safe modules. Distributed I/O system 56 System Manual, 02/2018, A5E03576849-AH Application planning 4.5 Forming potential groups Example of an ET 200SP configuration with fail-safe and non-fail-safe modules In principle, it is not necessary to operate fail-safe and non-fail-safe modules in separate potential groups. You can divide the modules into fail-safe and non-fail-safe potential groups and install them. The figure below shows an example of a configuration with fail-safe and non-fail-safe modules within a single ET 200SP distributed I/O system. IM 155-6 PN HF interface module F-module Non-fail-safe module Power module F-PM-E 24VDC/8A PPM ST Mixed fail-safe and non-fail-safe potential group with BaseUnits BU15..D and BU15..B. You achieve SIL3/Cat. 4/PLe for the fail-safe modules. No safety category can be achieved with the non-fail-safe motor starter. Non-fail-safe potential group with BaseUnits BU15..D and BU15..B Fail-safe potential group with BaseUnits BU20..D, BU15..B and BU30-MSx. Up to SIL2/Cat. 3/PLd is possible if you disconnect the self-assembling voltage bus and thus the non-failsafe modules. Server module Self-assembling voltage buses P1/P2 Fail-safe motor starter F-DS HF Figure 4-6 ET 200SP - example of a configuration with fail-safe modules Distributed I/O system System Manual, 02/2018, A5E03576849-AH 57 Application planning 4.5 Forming potential groups 4.5.4 Forming potential groups with motor starters Properties of the 500 V AC infeed bus The infeed bus has the following properties: The infeed bus is assembled by lining up the motor starter BaseUnits "BU30-MSx". The infeed bus distributes the energy to the SIMATIC ET 200SP motor starter within one load group. You can open load groups by inserting a 500 V infeed BaseUnit (BU30-MS1, BU30-MS2 or BU30-MS5). With the BaseUnits BU30-MS3, BU30-MS4 or BU30-MS6, you can take over the infeed bus from the left-hand BaseUnit. Via the infeed bus, you have the option of supplying three-phase load groups via L1, L2 and L3 or with single-phase load groups via L and N. The permissible voltage range is between 48 and 500 V AC. The maximum current carrying capacity is up 32 A (3-phase) at 50 C and 500 V. Pay attention to the derating values depending on the configuration. Properties of the self-assembling voltage bus (L+) Self-assembling voltage buses have the following properties: Maximum current: 7 A Rated voltage: 24 V Pay attention to the derating values depending on the configuration. The AUX1 bus is not supported in the BaseUnits of the SIMATIC ET 200SP motor starters. WARNING Electric shock when operating the infeed bus without touch protection cover There is a risk of electric shock when touching the infeed bus if you have not fitted a touch protection cover on the infeed bus on the right. Always fit a touch protection cover on the infeed bus on the right (article number: 3RK19081DA00-2BP0). WARNING Electric shock when operating a BaseUnit without an inserted motor starter If you fit a BaseUnit for motor starters without cover (e.g. option handling), there is a risk of an electric shock when touching the BaseUnit. Always fit a cover on the BaseUnit (article number: 3RK1908-1CA00-0BP0). Distributed I/O system 58 System Manual, 02/2018, A5E03576849-AH Application planning 4.5 Forming potential groups Requirements Use the following devices to form potential groups with motor starters: BaseUnits BU30-MSx 3RK1308-0xx00-0CP0 motor starters Operating principle Feed in the supply voltage L+ via the BaseUnit BU30-MS1 and BU30-MS3 at the 24V DC and M terminals. You can operate the motor starter on a single-phase (L1, N, PE) or a three-phase (L1, L2, L3, PE) AC voltage system. You connect the required AC voltage directly to the BaseUnits BU30-MSx (terminals L1, L2(N), L3, PE). You plug the motor starter onto the BaseUnits. Note The motor starters' AC power supply is not connected to the AC power supply for the AC I/O modules (see Chapter "Forming potential groups with BaseUnit type B1 (Page 55)"). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 59 Application planning 4.6 Configuration examples for potential groups 4.6 Configuration examples for potential groups 4.6.1 Configuration examples with BaseUnits Table 4- 5 Configuration examples with BaseUnits BaseUnits Configuration BU15-P16+A0+2D BU15-P16+A0+2B BU15-P16+A0+2D BU15-P16+A0+2B BU20-P12+A0+0B Distributed I/O system 60 System Manual, 02/2018, A5E03576849-AH Application planning 4.6 Configuration examples for potential groups BaseUnits Configuration BU15-P16+A10+2D BU15-P16+A10+2B 4.6.2 Configuration examples with potential distributor modules 3-wire connection The potential distributor modules allow for a space-saving design. For a 3-wire connection, you can, for example, replace two digital input modules with 8 channels on a 141 mm long BaseUnit with a digital input module with 16 channels and a potential distributor module, each of which is only 117 mm long. Note You must not place a BaseUnit for I/O modules in a PotDis potential group formed with a light-colored PotDis-BaseUnit. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 61 Application planning 4.6 Configuration examples for potential groups The figure below shows a configuration example with a DI 16x24VDC ST digital input module on a BU15-P16+A0+2B BaseUnit and a PotDis-TerminalBlock PotDis-TB-P1-R on a PotDis-BaseUnit PotDis-BU-P2/B-B. Figure 4-7 Example: 3-wire connection Distributed I/O system 62 System Manual, 02/2018, A5E03576849-AH Application planning 4.6 Configuration examples for potential groups Supply of external components Another application of the potential distributor modules is the supply of potentials for external components. Potential distributor modules enable simple, compact, integrated and clear design. Observe the current carrying capacity of each terminal: max. 10 A. Figure 4-8 Example: Supply of external components Distributed I/O system System Manual, 02/2018, A5E03576849-AH 63 Installation 5.1 5 Basics Introduction All modules of the ET 200SP distributed I/O system are open equipment. This means you may only set up the distributed I/O system ET 200SP in enclosures, cabinets or electrical equipment rooms and in a dry environment (IP20 degree of protection). The housings, cabinets and electrical operating rooms must guarantee protection against electric shock and spread of fire. The requirements regarding mechanical strength must also be observed. The housings, cabinets, and electrical operating rooms must not be accessible without a key or tool. Access must only be possible for personnel instructed or authorized to work with such equipment. Installation location Install the ET 200SP distributed I/O system into a suitable housing/control cabinet with sufficient mechanical strength, fire protection and at least IP54 degree of protection according to EN 60529, and take into consideration the ambient conditions for operating the devices. Installation position You can mount the ET 200SP distributed I/O system in any position. The preferred mounting position is horizontal mounting on a vertical wall. The ambient temperature may be restricted in certain installation positions. You will find more information in the section Mechanical and climatic environmental conditions (Page 296). Pay attention to chapter "Installation conditions for motor starters (Page 68)" when using motor starters. Distributed I/O system 64 System Manual, 02/2018, A5E03576849-AH Installation 5.1 Basics Mounting rail Mount the ET 200SP distributed I/O system on a mounting rail in accordance with EN 60715 (35 x 7.5 mm or 35 x 15 mm). You need to ground the mounting rail separately in the control cabinet. Exception: If you install the rail on grounded, zinc-plated mounting plates, there is no need to ground the rail separately. Note If the ET 200SP distributed I/O system is exposed to vibration and shock loads, both ends of the ET 200SP system assembly must be mechanically fixed to the mounting rail (e.g using 8WA1010-1PH01 ground terminals). This measure prevents the ET 200SP distributed I/O system from shifting to the side. Note If the ET 200SP distributed IO system is exposed to increased vibrations and shock, we recommend that you screw the mounting rail to the mounting surface at intervals of approx. 200 mm. The following are suitable surfaces for the mounting rails: Steel strip in accordance with Appendix A of EN 60715 or Tinned steel strip. We recommend these in conjunction with the mounting rails in the section Accessories/spare parts (Page 302). Note If you use mounting rails from other manufacturers, make sure that they have the required properties for your ambient climatic conditions. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 65 Installation 5.1 Basics Minimum clearances The figure below shows the minimum clearances you must observe when installing or dismantling the ET 200SP distributed I/O system. Figure 5-1 Minimum clearances General rules for installation WARNING Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Hazardous electrical voltage can cause electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. Distributed I/O system 66 System Manual, 02/2018, A5E03576849-AH Installation 5.1 Basics Observe the following rules: Installation starts on the left-hand side with the CPU/interface module. A light-colored BaseUnit BU..D0, BU30-MS1 or BU30-MS3 with infeed of the supply voltage L+ follows the CPU/the interface module or is placed at the start of each potential group. If you fit an AC I/O module or an AI Energy Meter as the first I/O module, then the first BaseUnit in the structure of the distributed I/O system ET 200SP may be a dark-colored BaseUnit. The requirement is that you use a CPU or IM 155-6 (as of V3.0). This is followed by BaseUnits BU..B, BU30-MS2 or BU30-MS4 (with a dark-colored terminal box). The matching I/O modules / motor starters can be plugged onto the BaseUnits. You will find matching combinations of BaseUnits and I/O modules / motor starters in Application planning (Page 36). The server module completes the configuration of the ET 200SP distributed I/O system. Note Mount the ET 200SP distributed I/O system only with disconnected supply voltage. WARNING Protection from conductive contamination Taking into account the environmental conditions, the devices must be protected from conductive contamination. This can be achieved, for example, by installing the devices in a control cabinet with the appropriate degree of protection. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 67 Installation 5.2 Installation conditions for motor starters 5.2 Installation conditions for motor starters Observe the following installation conditions when using an ET 200SP motor starter: Installation position You can fit the motor starter vertically or horizontally. The mounting position refers to the alignment of the mounting rail The maximum permissible ambient temperature range depends on the mounting position: - Up to 60 C: Horizontal mounting position - Up to 50 C: Vertical installation position You also need to consider the current carrying capacity of the ET 200SP components. In the case of a vertical mounting position, use end retainers "8WA1808" at both ends of the ET 200SP station: Mounting rail Use one of the following mounting rails: - 35x15 mm DIN rail in accordance with DIN EN 60715 - 35x7.5 mm DIN rail in accordance with DIN EN 60715 - SIMATIC S7 mounting rail Current carrying capacity of the ET 200SP station Current carrying capacity refers to the current load via the power bus and the infeed bus of the ET 200SP station. Depending on the ambient conditions and mounting position, you have to take account of the fan unit or additional mechanical fixings. Mechanical brackets Use the mechanical brackets in the following situations: When using a 15 mm mounting rail With a vertical mounting position For applications according to shipbuilding standards in all mounting positions with 7.5 mm and 15 mm mounting rails Designing interference-free motor starters For interference-free operation of the ET 200SP station in accordance with standard IEC 60947-4-2, use a dummy module before the first motor starter. No dummy module is required to the right of the motor starter. Note the following mounting rules: Use the following dummy module on the standard mounting rail between the previous module and the SIMATIC ET 200SP motor starter: BU cover 15 mm: 6ES7133-6CV15-1AM0 with BaseUnit 6ES7193-6BP00-0BA0 Distributed I/O system 68 System Manual, 02/2018, A5E03576849-AH Installation 5.2 Installation conditions for motor starters For operation of the ET 200SP station with an unused BaseUnit, a cover must be provided for the open BaseUnit plug contacts (power connector, power bus connector, and backplane bus connector). The cover protects the plug contacts against dirt. The BU cover can be ordered as an accessory. Mount the dummy module The figure below provides a schematic representation of how to implement measures for improving interference immunity. Interface module Digital input module Digital output module Dummy module Motor starter Motor starter Server module Infeed bus cover Motor starter NOTICE Ensure interference immunity You must not plug any other module into the BaseUnit of the dummy module, otherwise interference immunity is no longer ensured. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 69 Installation 5.3 Mounting the CPU/interface module 5.3 Mounting the CPU/interface module Introduction The CPU/the interface module connects the ET 200SP distributed I/O system to the fieldbus and exchanges the data between the higher-level control system and the I/O modules / motor starters. Requirement The mounting rail is fitted. Required tools 3 to 3.5 mm screwdriver (only for mounting and removing the BusAdapter) Mounting the CPU/interface module Watch the video sequence (http://support.automation.siemens.com/WW/view/en/95886218) To install a CPU/interface module, follow these steps: 1. Install the CPU/interface module on the mounting rail. 2. Swivel the CPU/interface module towards the back until you hear the mounting rail release button click into place. Figure 5-2 Mounting the CPU/interface module Distributed I/O system 70 System Manual, 02/2018, A5E03576849-AH Installation 5.3 Mounting the CPU/interface module Dismantling the CPU/interface module The CPU/interface module is wired and BaseUnits are located to its right. To remove the CPU/interface module, follow these steps: 1. Switch off the supply voltage on the CPU/interface module. Remove the 24 V DC connector from the CPU/interface module. 2. Press the mounting rail release button on the first BaseUnit. At the same time, shift the CPU/interface module parallel to the left until it detaches from the rest of the module group. Note: The mounting rail release button is located above the CPU/interface module or BaseUnit. 3. While pressing the mounting rail release button on the CPU/interface module, swivel the CPU/interface module off of the mounting rail. Note It is not necessary to remove the BusAdapter from the CPU/interface module. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 71 Installation 5.4 Installing the CM DP communication module 5.4 Installing the CM DP communication module Introduction You need the CM DP communication module to use the CPU with a DP master or DP slave. Requirements The mounting rail is fitted. The CPU is installed. Installing CM DP To install the CM DP communication module, follow these steps: 1. Install the CM DP to the right of the CPU. 2. Swivel the CM DP towards the back until you hear the mounting rail release button click into place. 3. Slide the CM DP to the left until you hear it click into the CPU. Figure 5-3 Installing CM DP Distributed I/O system 72 System Manual, 02/2018, A5E03576849-AH Installation 5.4 Installing the CM DP communication module Removing a CM DP The CPU and the CM DP are wired and BaseUnits are located to its right. To remove the CM DP communication module, follow these steps: 1. Switch off the supply voltage on the CPU. 2. Press the mounting rail release button on the first BaseUnit and, at the same time, move the CPU and the CM DP parallel to the left until they detach from the rest of the module group (clearance about 16 mm). 3. Press the mounting rail release button on the CM DP and move it to the right until it detaches from the CPU (clearance about 8 mm). 4. While pressing the mounting rail release button on the CM DP, swivel the CM DP off of the mounting rail. Note It is not necessary to remove the bus connector from the CM DP unless you have to replace the CM DP. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 73 Installation 5.5 Mounting BaseUnits for I/O modules 5.5 Mounting BaseUnits for I/O modules Introduction The BaseUnits are used for electromechanical connection between the individual ET 200SP components. They also provide terminals for connecting external sensors, actuators and other devices. Requirements The mounting rail is fitted. Required tools 3 to 3.5 mm screwdriver (only for dismantling the terminal box and the encoding element) Installing a BaseUnit Watch "Install configuration" video sequence (http://support.automation.siemens.com/WW/view/en/95886218) To install a BaseUnit, follow these steps: 1. Install the BaseUnit on the mounting rail. 2. Swivel the BaseUnit backwards until you hear it click into the mounting rail. 3. Slide the BaseUnit parallel to the left until you hear it click into the preceding CPU/interface module or BaseUnit. Figure 5-4 Installing a BaseUnit Distributed I/O system 74 System Manual, 02/2018, A5E03576849-AH Installation 5.5 Mounting BaseUnits for I/O modules Removing a BaseUnit WARNING Hazardous Voltage Hazardous electrical voltage can cause electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. To remove a BaseUnit, follow these steps: The BaseUnit is wired and there are other BaseUnits to its right and left. To remove a specific BaseUnit, move the neighboring modules. As soon as you have created a clearance of about 8 mm from the neighboring BaseUnits, you can remove the BaseUnit. Note The terminal box can be replaced without removing the BaseUnit. Refer to section Replacing the terminal box on the BaseUnit (Page 255). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 75 Installation 5.5 Mounting BaseUnits for I/O modules To remove a BaseUnit, follow these steps: 1. If present, turn off the supply voltage on the BaseUnit. 2. Loosen the wiring on the BaseUnit (with a 3 to 3.5 mm screwdriver). 3. Removing (from the right): Press the mounting rail release button on the corresponding BaseUnit. Move the BaseUnit parallel to the right and swivel the BaseUnit off of the mounting rail while pressing the mounting rail release button. Removing (from the left): Press the mounting rail release button on the corresponding BaseUnit and on the BaseUnit to the right of this. Move the BaseUnit parallel to the left and swivel it out of the mounting rail while pressing the mounting rail release button. Note: The mounting rail release button is located above the BaseUnit. Figure 5-5 Removing the BaseUnit (removing from the right) Distributed I/O system 76 System Manual, 02/2018, A5E03576849-AH Installation 5.6 Mounting and dismantling BaseUnits for motor starters 5.6 Mounting and dismantling BaseUnits for motor starters Requirements The mounting rail is fitted. When using a 15 mm mounting rail, the mechanical bracket (3RK1908-1EA00-1BP0) must be mounted. Note Mechanical bracket for BaseUnit You will find out how to mount the mechanical bracket for the BaseUnit in chapter "Mounting the mechanical bracket for the BaseUnit (Page 83)". CAUTION Protection against electrostatic charge When handling and installing the SIMATIC ET 200SP motor starter, ensure protection against electrostatic charging of the components. Changes to the system configuration and wiring are only permissible after disconnection from the power supply. Mounting a BaseUnit Proceed as follows to mount a BaseUnit for motor starters: 1. Hook the BaseUnit into the DIN rail from above. 2. Swing the BaseUnit to the rear until the BaseUnit audibly engages. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 77 Installation 5.6 Mounting and dismantling BaseUnits for motor starters 3. Slide the individual BaseUnits to the left to the previous BaseUnit until they audibly engage. Assemble the BaseUnits only on the DIN rail. Note The BaseUnits for motor starters can be plugged together with the BaseUnits for I/O modules. Disassembling the BaseUnit WARNING Hazardous Voltage Hazardous electrical voltage can cause electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. To disassemble the BaseUnit, proceed as follows: 1. Disconnect the main power supply and the control current supply of the SIMATIC ET 200SP motor starter. 2. Actuate the DIN rail release on the BaseUnit of the motor starter. 3. Move the BaseUnit to the left. As soon as there is a clearance of approximately 8 mm to the neighboring BaseUnits, you can disassemble the BaseUnit of the motor starter. 4. Swing the BaseUnit away from the DIN rail while pressing the DIN rail release. Distributed I/O system 78 System Manual, 02/2018, A5E03576849-AH Installation 5.7 Installing potential distributor modules 5.7 Installing potential distributor modules Introduction You use the potential distributor module to distribute a variety of potentials (P1, P2). Requirements The mounting rail is installed. Installing and uninstalling PotDis-BaseUnit You install/uninstall PotDis-BaseUnits as you would the BaseUnits for I/O modules. You can find additional information in section Mounting BaseUnits for I/O modules (Page 74). Installing and uninstalling PotDis-TerminalBlock Installing Plug the PotDis-TerminalBlock in die PotDis-BaseUnit. Proceed exactly as described in Section Inserting I/O modules / motor starters and BU covers (Page 118). Uninstalling To remove a PotDis-TerminalBlock, follow these steps: 1. Switch off the supply voltage at the PotDis-BaseUnit. 2. Simultaneously press the top and bottom release buttons of the PotDis-TerminalBlock. 3. Remove the PotDis-TerminalBlock from the front of the PotDis-BaseUnit. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 79 Installation 5.8 Installing the server module 5.8 Installing the server module Introduction The server module on the far right of the assembly/line completes the ET 200SP distributed I/O system. Requirement The last BaseUnit is mounted. Installing the server module Watch "Install configuration" video sequence (http://support.automation.siemens.com/WW/view/en/95886218) Proceed as follows to install a server module: 1. Install the server module on the mounting rail on the right next to the last BaseUnit. 2. Swivel the server module backwards on the mounting rail. 3. Move the server module parallel to the left until you hear it click into the last preceding BaseUnit. Figure 5-6 Installing the server module Removing the server module Proceed as follows to remove a server module: 1. Press the mounting rail release button on the server module. 2. Move the server module parallel to the right. 3. While pressing the mounting rail release button, swivel the server module off the mounting rail. Distributed I/O system 80 System Manual, 02/2018, A5E03576849-AH Installation 5.9 Mounting further accessories for motor starters 5.9 Mounting further accessories for motor starters 5.9.1 Mounting the cover for the 500 V AC infeed bus Introduction The 500 V infeed bus connects all SIMATIC ET 200SP motor starters. For finger-safe termination of the infeed bus, you must use the cover. DANGER Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Hazardous electrical voltage causes electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. DANGER Infeed bus - electric shock You must provide the infeed bus with a touch protection cover on the right (Article No.: 3RK1308-1DA00-2BP0). Failure to do so will result in the danger of electric shock. WARNING Personal injury may occur On the last plugged-in BaseUnit of a motor starter, place a cover on the opening of the contacts of the infeed bus. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 81 Installation 5.9 Mounting further accessories for motor starters Procedure Proceed as follows to mount the infeed bus cover on a SIMATIC ET 200SP motor starter: 1. Press the cover onto the opening of the BaseUnit on the right until it audibly engages. The cover can be removed again using 2 fingers and without tools. Distributed I/O system 82 System Manual, 02/2018, A5E03576849-AH Installation 5.9 Mounting further accessories for motor starters 5.9.2 Mounting the mechanical bracket for the BaseUnit Introduction To achieve higher stability, you can use a mechanical bracket on 7.5 mm and 15 mm mounting rails. You must use the mechanical bracket in the following situations: When using a 15 mm mounting rail With a vertical mounting position For applications according to shipbuilding standards in all mounting positions with 7.5 mm and 15 mm mounting rails You can find further information on the mechanical bracket in chapter "Installation conditions for motor starters (Page 68)". Distributed I/O system System Manual, 02/2018, A5E03576849-AH 83 Installation 5.9 Mounting further accessories for motor starters Procedure To mount the mechanical bracket, proceed as follows: 1. Insert the mechanical bracket into the opening at the bottom of the BaseUnit. You use the same mechanical bracket for both mounting rails, rotated through 180 respectively. 2. Hook the BaseUnit into the mounting rail. 3. Insert the mechanical bracket into the BaseUnit. 4. Screw the mechanical bracket securely onto the mounting panel. Use an M4 screw and a suitable washer. Distributed I/O system 84 System Manual, 02/2018, A5E03576849-AH Installation 5.9 Mounting further accessories for motor starters The figures below show the mechanical bracket after installation on a 7.5 mm or 15 mm mounting rail. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 85 Installation 5.9 Mounting further accessories for motor starters 5.9.3 Mounting the BU cover Introduction BU covers are plugged onto BaseUnits whose slots have been reserved for future expansion (as empty slots). The BU covers for motor starters serve as touch protection covers for unoccupied slots. DANGER Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Hazardous electrical voltage causes electric shock, burns and property damage. Disconnect your system and devices from the power supply before starting any assembly tasks. DANGER BaseUnit without motor starter - electric shock If you install a BaseUnit without motor starter in the ET 200SP system (e.g. options handling), you must provide the BaseUnit with a BU cover (Article No: 3RK1908-1CA000BP0). Failure to do so will result in the danger of electric shock. Procedure To mount the BU cover onto a SIMATIC ET 200SP motor starter, insert the BU cover in the BaseUnit in parallel until both interlocks audibly engage. Distributed I/O system 86 System Manual, 02/2018, A5E03576849-AH 6 Wiring 6.1 Rules and regulations for operation Introduction When installing the ET 200SP distributed I/O system as part of a plant or system, special rules and regulations need to be adhered to depending on the area of application. This section provides an overview of the most important rules that must be observed for the integration of the ET 200SP distributed I/O system in a plant or system. Specific application Adhere to the safety and accident prevention regulations applying to specific applications, for example machine protection guidelines. EMERGENCY STOP devices EMERGENCY STOP devices in accordance with IEC 60204 (corresponds to DIN VDE 0113) must remain effective in all operating modes of the plant or system. Excluding hazardous plant states Hazardous operating states must not occur when the plant restarts after a voltage dip or power failure. Bus communication is reestablished following a fault. If necessary, EMERGENCY STOP must be forced! An uncontrolled or undefined startup must not occur after the EMERGENCY STOP is unlocked. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 87 Wiring 6.1 Rules and regulations for operation Line voltage Below, everything you need to consider in terms of line voltage is described (refer to section Insulation, protection class, degree of protection and rated voltage (Page 298)): For fixed plants or systems without an all-pole mains disconnection switch, a mains disconnection device (all-pole) must be available in the building installation. For load power supplies, the configured rated voltage range must correspond to the local line voltage. For all power circuits of the ET 200SP distributed I/O system, the fluctuation/deviation of the line voltage from the rated value must be within the permitted tolerance. 24 V DC supply Below you will find a description of what you need to pay attention to with 24 V DC supply: For buildings: In the event of danger through overload, you must provide lightning protection measures for external lightning protection (e.g. lightning protection elements). For 24 V DC supply lines and signal lines: If there is a risk of overvoltages, you need to take precautions to ensure internal lightning protection (e.g. lightning protection elements, refer to section Accessories/spare parts (Page 302)). For 24 V DC supply: Make sure there is safe (electrical) isolation and separate cable routing or increased insulation of the low voltage (SELV/PELV) to electric circuits with dangerous potentials in accordance with IEC61131-2 / IEC 61010-2-201. Requirements for power supplies in the event of voltage interruption Note To ensure adherence to IEC 61131-2 and NAMUR Recommendation NE 21, only use power packs/power supply units (230 V AC 24 V DC) with a mains buffering time of at least 20 ms. Observe the relevant requirement in your product standards (e.g. 30 ms for "burners" pursuant to EN 298) as regards possible voltage interruptions. The latest information on PS components is available on the Internet (https://mall.industry.siemens.com). These requirements, of course, also apply to power packs/power supply units not constructed using ET 200SP or S7-300-/400-/1500 technology. Distributed I/O system 88 System Manual, 02/2018, A5E03576849-AH Wiring 6.1 Rules and regulations for operation Protection against outside electrical influences Below is a description of what you must pay attention to in terms of protection against electrical impacts and/or faults: Make sure that the system for discharging electromagnetic interference is connected to a functional earth or to protective conductor with a sufficient cross-section for all plants with an ET 200SP distributed I/O system. For supply, signal and bus lines, you must ensure that the laying of the lines and the installation is correct. For signal and bus lines, you must ensure that a wire/cable break or a cross-circuit does not lead to undefined states of the plant or system. Reference You can find more information in the Designing interference-free controllers (http://support.automation.siemens.com/WW/view/en/59193566) function manual. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 89 Wiring 6.2 Additional rules and regulations for the operation of the ET 200SP with fail-safe modules 6.2 Additional rules and regulations for the operation of the ET 200SP with fail-safe modules 6.2.1 Safety extra-low voltage (SELV, PELV) for failsafe modules and failsafe motor starters WARNING The failsafe modules must be operated with safety extra-low voltage (SELV, PELV). You can find more information on safety extra-low voltage (SELV, PELV) in the data sheets of the applicable power supplies, for example. The fail-safe modules operate with the 24 V DC rated voltage. The tolerance range is 19.2 V DC to 28.8 V DC. The fail-safe motor starters operate with the 24 V DC rated voltage. The tolerance range is 20.4 V DC to 28.8 V DC. Within the overvoltage range from 32 V DC to 36 V DC, the F-modules react in a fail-safe manner and the inputs and outputs are passivated. For overvoltages greater than 36 V DC, the F-modules are permanently de-energized. Use a power supply unit that does not exceed Um = 36 V DC even in the event of a fault. For more on this, refer to the information in the data sheet on overvoltage protection in the case of an internal error. Or implement appropriate measures to limit the voltage, e.g. use of an overvoltage protector. All system components that can supply electrical energy in any form whatsoever must fulfill this condition. Each additional circuit (24 V DC) used in the system must have a safety extra-low voltage (SELV, PELV). Refer to the relevant data sheets or contact the manufacturer. Sensors and actuators with an external power supply can also be connected to F-modules. Make sure that power is supplied to these components from safety extra-low voltage (SELV, PELV) as well. The process signal of a 24 V DC digital module may not exceed a fault voltage Um in the event of a fault. WARNING Even when a fault occurs, the permissible potential difference between the supply of the interface module (bus voltage) and the load voltage must not be exceeded. An external direct electrical connection is one way to meet this requirement. This also prevents potential differences from causing voltage additions at the individual voltage sources, which would cause the fault voltage Um to be exceeded. Distributed I/O system 90 System Manual, 02/2018, A5E03576849-AH Wiring 6.2 Additional rules and regulations for the operation of the ET 200SP with fail-safe modules 6.2.2 Requirements for sensors and actuators for fail-safe modules and fail-safe motor starters General requirements for sensors and actuators Note the following important warning regarding safety-related use of sensors and actuators: WARNING Note that instrumentation with sensors and actuators bears a considerable safety responsibility. Also bear in mind that sensors and actuators generally do not have proof-test intervals of 20 years as defined in IEC 61508:2010 without considerable loss of safety. The probability of hazardous faults and the rate of hazardous faults of safety functions must comply with an SIL-defined high limit. A listing of values achieved by F-modules in the technical specifications of the F-modules is available under "Fail-safe performance characteristics". To achieve the required safety class, suitably qualified sensors and actuators are necessary. Additional sensor requirements General rule: To achieve SIL3/Cat. 3/PLe, a single-channel sensor is adequate. However, to achieve SIL3/Cat. 3/PLe with a single-channel sensor, the sensor itself must be SIL3/Cat. 3/PLe-capable; otherwise the sensor must be connected by two channels to achieve this safety level. To achieve SIL3/Cat. 4/PLe, sensors must be connected by two channels. WARNING In the case of fail-safe input modules, the value "0" is output to the F-CPU after detection of faults. You therefore need to make sure that the sensors are implemented in such a way as to ensure the reliable reaction of the safety program when the sensor is in the "0" state. Example: In its safety program, an EMERGENCY-STOP sensor must achieve the shutdown of the relevant actuator when it is in the "0" state (EMERGENCY-STOP button pressed). Additional requirements for sensors for fail-safe motor starters Only single-channel sensors that fulfill the required safety category themselves may be connected to the fail-safe motor starter's F-DI. Fail-safe laying must be observed in accordance with the required safety category. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 91 Wiring 6.2 Additional rules and regulations for the operation of the ET 200SP with fail-safe modules Duration requirements for sensor signals WARNING Observe the following requirements for sensor signals: * To ensure the correct detection of the sensor signals via fail-safe modules with inputs, you need to make sure that the sensor signals are output for a minimum duration. * For pulses to be detected with certainty, the time between two signal changes (pulse duration) must be greater than the PROFIsafe monitoring time. Reliable detection by F-modules with inputs The minimum duration of sensor signals for F-modules with inputs depends on the configured input delay, the parameters of the short circuit test of the sensor supplies, and the configured discrepancy behavior for 1oo2 evaluation. The signal must be greater than the maximum response time of the configured application. Information on calculating the maximum response time can be found in the section "Response times" of the relevant Fmodule. The maximum permitted switching frequency of the sensor signals results from the minimum duration. Additional requirements for actuators The fail-safe output modules test the outputs at regular intervals. The F-module briefly switches off the activated outputs and, if necessary, switches on the deactivated outputs. You can assign the maximum duration of the test pulses (dark and light period) with parameters. Fast reacting actuators may briefly drop out or be activated during the test. If your process does not tolerate this, set the pulse duration of the light or dark test correspondingly or use actuators that have sufficient lag. WARNING If the actuators switch voltages higher than 24 V DC (e.g. 230 V DC), safe galvanic isolation must be ensured between the outputs of a fail-safe output module and the parts carrying a higher voltage (in compliance with the IEC 60664-1 standard). This is generally the case for relays and contactors. Particular attention must be paid to this with semiconductor switching devices. Technical specifications of sensors and actuators Refer to the manuals of the fail-safe modules for technical specifications to assist you in selecting sensors and actuators. Distributed I/O system 92 System Manual, 02/2018, A5E03576849-AH Wiring 6.3 Additional rules and instructions for operation with motor starters 6.2.3 Crosstalk of digital input/output signals When fail-safe digital output and input signals are in a single cable, F-DQ modules and F-PM-E modules may experience readback errors. Cause: capacitive crosstalk During the bit pattern test of the outputs or the sensor supply of the inputs, the steep switching edge of the output drivers caused by the coupling capacitance of the line may result in crosstalk to other non-activated output or input channels. This may then lead to a response of the readback circuit in these channels. A cross circuit/short-circuit is detected, which leads to safety-related tripping. Remedy: Separate cables for F-DI modules, F-DQ modules, and F-PM-E modules or non-fail-safe DQ modules Separate cables for F-DQ channel and F-DI channels for the F-PM-E module Coupling relay or diodes in the outputs Disable the sensor supply test if safety class requirements allow it. Cause: magnetic crosstalk Note that an inductive load connected to the F-DQ channels can induce coupling of a strong magnetic field. Remedy: Separate the inductive loads spatially or shield against the magnetic field. Configure the readback time to 50 ms or higher. 6.3 Additional rules and instructions for operation with motor starters 6.3.1 Protection against short circuit The motor starter complies with type of coordination 1. Secure the feeder cable for the infeed bus according to current, country-specific rules for conductor protection. WARNING Hazardous Voltage at the Motor Can Cause Death, Serious Injury, or Property Damage. Following a short-circuit, the SIMATIC ET 200SP motor starter is defective. Replace the motor starter following a short-circuit. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 93 Wiring 6.4 Operating the ET 200SP on grounded incoming supply 6.4 Operating the ET 200SP on grounded incoming supply Introduction Below you will find information on the overall configuration of an ET 200SP distributed I/O system on a grounded incoming supply (e.g. TN-S network). The specific subjects discussed are: Disconnecting devices and short-circuit and overload protection according to IEC 60364 (corresponds to DIN VDE 0100) and IEC 60204 (corresponds to DIN VDE 0113) Load power supplies and load circuits. Grounded incoming supply In the case of grounded incoming supplies (TN-S system) the neutral conductor (N) and the protective conductor (PE) are each grounded. Both conductors form a part of the overvoltage concept. When a plant is in operation, the current flows across the neutral conductor. When a fault occurs, for example, a single ground fault between a live conductor and ground, the current flows through the protective conductor. Safe electrical isolation (SELV/PELV in accordance with IEC 61131-2 or 61010-2-201) Load current / power supply modules with safe electrical isolation are required for the operation of the ET 200SP distributed I/O system. In accordance with IEC 61131-2 / 610102-201, this protection is referred to as SELV (Safety Extra Low Voltage)/PELV (Protective Extra Low Voltage). The wiring of SELV/PELV circuits must either be isolated from the wiring of other circuits that are not SELV/PELV or the insulation of all conductors must be dimensioned for the higher voltage. Configuration of ET 200SP with ungrounded reference potential To conduct interference currents, the reference potential of the CPU/interface module and the BaseUnits BU15...D is connected internally via an RC combination (IM/CPU: R = 10 M / C = 100 nF, BU15...D: R = 10 M / C = 4 nF) with the mounting rail (functional grounding). This configuration conducts high-frequency interference currents and prevents static charges. It is always possible to configure an ungrounded setup of the ET 200SP distributed I/O system as the ET 200SP distributed I/O system has no fixed ground connection. The power pack/power supply module for 24 V DC must also be ungrounded and electrically isolated. If you want to configure the ET 200SP distributed I/O system with grounded reference potential, connect the 1M connection of the CPU/interface module electrically with the protective conductor. Distributed I/O system 94 System Manual, 02/2018, A5E03576849-AH Wiring 6.4 Operating the ET 200SP on grounded incoming supply Short-circuit / overload protection Various measures as protection against short-circuits and overloads are required for setting up a full installation. The type of components and the binding protective measures depend on which IEC (DIN VDE) regulation applies to your system configuration. The table refers to the figure below and compares the IEC (DIN VDE) regulations. Table 6- 1 Components and protective measures Refer to figure IEC 60364 (DIN VDE 0100) IEC 60204 (DIN VDE 0113) Disconnecting device for controller, sensors, and actuators Main switch Disconnector Short-circuit / overload protection: Single-pole protection of circuits With grounded secondary circuit: single-pole protection In groups for sensors and actuators otherwise: all-pole protection Load current supply for AC load circuits with more than five items of electromagnetic equipment Galvanic isolation by transformer recommended Galvanic isolation by transformer recommended Cable temperature measurement threshold Note Cable temperature measurement threshold When choosing a cable, remember that the cable temperature in operation can be up to 30 C higher than the ambient temperature of the ET200SP system (example: at an ambient temperature of 60 C, a connection conductor must be dimensioned for a temperature range of at least 90 C). You should specify other connection types and material requirements based on the electrical characteristics of the circuits you use and the installation environment. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 95 Wiring 6.4 Operating the ET 200SP on grounded incoming supply ET 200SP in the overall configuration The figure below shows the overall configuration of the ET 200SP distributed I/O system (load current supply and grounding concept) with supply from a TN-S network. Main switch Short-circuit / overload protection The load current supply (galvanic isolation) Figure 6-1 ET 200SP in the overall configuration Distributed I/O system 96 System Manual, 02/2018, A5E03576849-AH Wiring 6.5 Electrical configuration of the ET 200SP 6.5 Electrical configuration of the ET 200SP Electrical isolation Electrical relationships With the ET 200SP distributed I/O system, there is electrical isolation between: The load circuits/process and all other circuit components of the ET 200SP distributed I/O system. The communication interfaces of the CPU (PROFINET) or of the interface module (PROFINET/PROFIBUS) and all other circuit components. The figures below show the electrical relationships of the ET 200SP distributed I/O system with the CPU and the interface module. Only the most important components are represented in the figures. Figure 6-2 Electrical relationships for ET 200SP with CPU Distributed I/O system System Manual, 02/2018, A5E03576849-AH 97 Wiring 6.5 Electrical configuration of the ET 200SP Figure 6-3 Electrical relationships for ET 200SP with interface module (using IM 155-6 PN ST as an example) Distributed I/O system 98 System Manual, 02/2018, A5E03576849-AH Wiring 6.6 Wiring rules 6.6 Wiring rules Wiring rules for the CPU/interface module and BaseUnits for I/O modules Wiring rules for ... Permitted cable cross-sections of solid cables (Cu) CPU/interface module (supply voltage) BaseUnits (push-in terminal) 0.2 to 2.5 mm2 AWG*: 24 to 13 Permitted cable cross-sections of flexible cables (Cu) Without end sleeve 0.2 to 2.5 mm2 AWG*: 24 to 13 AWG*: 24 to 14 mm2** With end sleeve (with plastic sleeve)*** 0.25 mm to 1.5 AWG*: 24 to 16 AWG*: 26 to 16 With TWIN end sleeve*** 0.5 mm to 1 mm2 0.5 to 0.75 mm2 (see below) AWG*: AWG*: 20 to 18 20 to 17 Stripping length of the wires 8 to 10 mm End sleeves in accordance with DIN 46228 with plastic sleeve*** 8 and 10 mm long 0.14 mm to 1.5 mm2 * AWG: American Wire Gauge ** End sleeves without plastic sleeve: 0.25 to 2.5 mm2/AWG: 24 to 13 *** See note on end sleeves Note End sleeves Optimum results with respect to a high-quality and permanent electrical connection with maximum conductor pull forces at the same time can be achieved by using crimping dies, preferably with smooth surfaces, which are provided, for example, with rectangular and trapezoidal crimp cross-sections. Crimping dies with a pronounced wave profile are unsuitable. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 99 Wiring 6.6 Wiring rules TWIN end sleeves for the cables of the I/O modules' push-in terminals Due to the space required by TWIN end sleeves with 0.75 mm2 cross-section, you must ensure a correct angle for the cable arrangement when crimping the TWIN end sleeve so that the cables are optimally arranged. Cross-section of the terminal compartment Crimping TWIN end sleeves at the correct angle Figure 6-4 TWIN end sleeves Wiring rules for motor starters Wiring rules for ... L1(L), L2(N), L3, PE T1, T2, T3, PE, 24 V DC, F-DI, DI1 ... DI3, LC, M, 24 V M OUT Permitted cable cross-sections of solid cables (Cu) 1 to 6 mm2 0.5 to 2.5 mm2 0.2 to 1.5 mm2 AWG: 18 to 10 AWG: 20 to 12 AWG: 24 to 16 Permitted cable cross-sections of flexible cables (Cu) 1 to 6 mm2 0.5 to 2.5 mm2 0.2 to 1.5 mm2 AWG: 18 to 10 AWG: 20 to 12 AWG: 24 to 16 Without end sleeve With end sleeve 1 to 6 mm2 AWG: 18 to 10 With end sleeve (with plastic sleeve) 1 to 4 mm2 0.5 to 2.5 mm2 AWG: 20 to 12 0.5 to 1.5 mm2 0.25 to 1.5 mm2 AWG: 24 to 16 0.25 to 0.75 mm2 AWG: 18 to 11 AWG: 20 to 16 AWG: 24 to 18 Stripping length of the wires 15 mm 10 mm 8 mm End sleeves according to DIN 46228 with plastic sleeve 15 mm long 10 mm long 8 mm long Distributed I/O system 100 System Manual, 02/2018, A5E03576849-AH Wiring 6.6 Wiring rules Safety standards for fail-safe motor starters Fail-safe motor starters fulfill the following standards under certain conditions: PL e/Cat. 4 according to EN ISO 13849-1 Safety Integrity Level SILCL3 acc. to IEC 62061 To fulfill both standards, lay cross-circuit proof and P-cross-circuit proof control cables from the safe output of a sensor or F-DQ to the safe input of the motor starter, e.g. as a separately sheathed cable or in a separate cable duct. Line protection The line protection of the SIMATIC ET 200SP motor starter is provided for the motor outgoing feeder cable when the following condition is met: The cross-section of the motor outgoing feeder cable must be dimensioned for the load ratios of the motor and for the cable-laying method. Comply with national regulations. The user is responsible for the correct selection and dimensioning of the motor connection cable to DIN VDE 0100 and DIN VDE 0298-4 and/or UL 508. The conductor protection for the incoming feeders must be ensured by the owner of the installation depending on the cross-section. Cable temperature measurement threshold Note Cable temperature measurement threshold When choosing a cable, remember that the cable temperature in operation can be up to 30 C higher than the ambient temperature of the ET200SP system (example: at an ambient temperature of 60 C, a connection conductor must be dimensioned for a temperature range of at least 90 C). You should specify other connection types and material requirements based on the electrical characteristics of the circuits you use and the installation environment. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 101 Wiring 6.7 Wiring BaseUnits for I/O modules 6.7 Wiring BaseUnits for I/O modules Introduction The BaseUnits connect the ET 200SP distributed I/O system to the process. The following versions of the BaseUnits can be used: BaseUnits (with light-colored terminal box) for opening a potential group: BU..D BaseUnits (with dark-colored terminal box) for extending the potential group: BU..B BaseUnits with additional AUX terminals or additional terminals: BU..+10.. BaseUnits with integrated thermal resistor for compensation of the reference junction temperature when connecting thermocouples: BU..T Distributed I/O system 102 System Manual, 02/2018, A5E03576849-AH Wiring 6.7 Wiring BaseUnits for I/O modules PotDis-BaseUnits (with light-colored terminal box) for opening a PotDis potential group: PotDis-BU..D PotDis-BaseUnits (with dark-colored terminal box) for extending the potential group: PotDis-BU..B Push-in terminal Spring release Measuring probe (suitable probes: 1 mm diameter, length 10 mm while observing the permitted voltage category) Holder for shield connection Figure 6-5 View of the BaseUnit Note The pin assignment of the BaseUnit depends on the connected I/O module. Information on the BaseUnits and I/O modules can be found in the associated manuals. Replacement of the terminal box on the BaseUnit is described in the section Replacing the terminal box on the BaseUnit (Page 255). Note Special terminal designations in the wiring and block diagrams of the I/O modules/BaseUnits * RES: Reserve, these terminals must remain unconnected so that they can be used for future expansions * n.c.: Not connected, these terminals have no function. However, they can be connected to potentials specifically defined for a module, for example, for the laying unused wires. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 103 Wiring 6.7 Wiring BaseUnits for I/O modules Requirements The supply voltages are turned off. Follow the wiring rules. Color identification labels (Page 130) (optional) have been applied. Required tools 3 to 3.5 mm screwdriver Tool-free connection of cables: single-wire without wire end ferrule, multi-wire (stranded) with wire end ferrule or ultrasonically sealed Watch the video sequence (http://support.automation.siemens.com/WW/view/en/95886218) To connect a wire without tools, follow these steps: 1. Strip 8 to 10 mm of the wires. 2. Only in the case of stranded conductors (except for 2.5 mm cross-section): Seal or crimp the wire with wire end ferrules. 3. Insert the wire into the push-in terminal as far as it will go. Connection of cables: multi-wire (stranded), without wire end ferrule, unprocessed To connect a wire without a wire end ferrule, follow these steps: 1. Strip 8 to 10 mm of the wires. 2. Push with the screwdriver into the spring release. 3. Insert the wire into the push-in terminal as far as it will go. 4. Pull the screwdriver out of the spring release. Removing wires Using the screwdriver, press the spring release of the terminal as far as it will go and pull out the wire. Note When you press the spring release, you should not pull on the wire/cable at the same time. This prevents you from damaging the terminal. Distributed I/O system 104 System Manual, 02/2018, A5E03576849-AH Wiring 6.8 Connecting cable shields for I/O modules 6.8 Connecting cable shields for I/O modules Introduction You need the shield connector to contact cable shields (e.g. for analog modules). The shield connector conducts interference currents on cable shields to ground via the mounting rail. It is not necessary to contact the shield at where the cable enters the cabinet. Attach the shield connector to the BaseUnit. The shield connector consists of a shield contact and a shield terminal. The shield connector is automatically connected to the functional ground (FG) of the mounting rail after installation. Requirements BaseUnit with a width of 15 mm The shield terminal is suitable for cables with max. 7 mm each. Figure 6-6 Shield terminal Required tools Stripping tool Distributed I/O system System Manual, 02/2018, A5E03576849-AH 105 Wiring 6.8 Connecting cable shields for I/O modules Procedure Watch the "Wiring BaseUnits" video sequence (http://support.automation.siemens.com/WW/view/en/95886218) To connect the cable shield, follow these steps: 1. If necessary, connect the supply voltage L+ and ground to the BaseUnit. 2. Press the shield contact up into the mount until you hear it click into place. 3. Remove the cable insulation material around the shield terminal. Connect the cable to the BaseUnit and place the cable in the shield contact. 4. Insert the shield terminal into the shield contact. 5. Tighten the shield terminal with approximately 0.5 Nm. Mount Supply voltage L+, ground Shield contact Insulation material removed (approx. 20 mm) Cable to the encoder Shield terminal Flat connector for push-on contacts (6.3 x 0.8 mm) Figure 6-7 Mounting the shield contact Distributed I/O system 106 System Manual, 02/2018, A5E03576849-AH Wiring 6.9 Wiring BaseUnits for motor starters 6.9 Wiring BaseUnits for motor starters Introduction The following versions of BaseUnits can be used: BU30-MS1 (with 500 V and 24 V infeed) BU30-MS2 (with 500 V infeed and 24 V forwarding) BU30-MS3 (with 24 V infeed and 500 V forwarding) BU30-MS4 (with 500 V and 24 V forwarding) BU30-MS5 (with 500 V infeed, 24 V and F-DI forwarding) BU30-MS6 (with 500 V, 24 V and F-DI forwarding) The following figure shows an example of a BaseUnit BU30-MS1 (with the maximum number of terminals): Push-in terminal Spring release Figure 6-8 Terminals on a BaseUnit BU30-MS1 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 107 Wiring 6.9 Wiring BaseUnits for motor starters The following figure shows an example of a BaseUnit BU30-MS5 (with the maximum number of terminals): Push-in terminal Spring release Figure 6-9 Terminals on a BaseUnit BU30-MS5 DANGER Hazardous Voltage Can Cause Death, Serious Injury, or Property Damage. Hazardous electrical voltage can cause electric shock, burns and property damage. Turn off and lock out all power supplying this device before working on this device. For wiring finely-stranded or stranded conductors without end sleeves on push-in connections, a screwdriver is required. Distributed I/O system 108 System Manual, 02/2018, A5E03576849-AH Wiring 6.9 Wiring BaseUnits for motor starters Requirements The supply voltages are switched off Observe the wiring rules NOTICE Wire the F-DI inputs of the BaseUnits BU-30-MS5 and BU-30-MS6 to surge filters If your system requires overvoltage protection, you must wire the F-DI inputs of the BaseUnits BU-30-MS5 and BU-30-MS6 to surge filters. Please see "Electromagnetic Compatibility" in the technical specifications. Required tools Use the screwdriver "SZF 1-0.6x3.5" (for finely-stranded cables only). Connecting conductors: Solid without end sleeve, stranded (stranded wire) with end sleeve To connect a cable, proceed as follows: 1. Insulate the cables in accordance with the table in chapter "Electromagnetic compatibility of fail-safe modules (Page 292)". 2. Only in the case of stranded conductors: Crimp the cable with end sleeves. 3. Insert the cable into the push-in terminal as far as it will go. 4. Pull on the cable to ensure it is tight. Connecting conductors: multi-wire (stranded), without end sleeve, unfinished To connect a cable, proceed as follows: 1. Insulate the cables in accordance with the table in chapter "Wiring rules (Page 99)". 2. Press the screwdriver into the spring release. 3. Insert the conductor into the push-in terminal until it engages. 4. Pull the screwdriver out of the spring release. 5. Check whether or not the conductor is firmly connected by pulling on the cable. Video sequence At the following Internet link, you can see a video about connecting conductors: Wire BaseUnits (http://support.automation.siemens.com/WW/view/en/95886218) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 109 Wiring 6.9 Wiring BaseUnits for motor starters Releasing conductors To release a conductor, proceed as follows: 1. Press the screwdriver into the spring release of the terminal until it engages. 2. Pull the conductor out. Note When pressing the spring release, you must not pull on the wire/cable at the same time. In this way, you avoid damaging the terminal. Distributed I/O system 110 System Manual, 02/2018, A5E03576849-AH Wiring 6.10 Connecting the 3DI/LC module for the motor starter 6.10 Connecting the 3DI/LC module for the motor starter You will find further information on the 3DI/LC module in the ET 200SP motor starter (https://support.industry.siemens.com/cs/ww/en/view/109479973) manual. Procedure The figure below shows the connections of the 3DI/LC module. Digital input 3 Digital input 2 Digital input 1 Local control (manual local) Ground 24 V DC/ 100 mA output Note The digital inputs (1 to 4) are not isolated. The reference potential is M (5). Control the digital inputs only via a unit supplied from the 24 V DC output (6). Connect only cables of a width not exceeding 30 m to the 3DI/LC module. The supply (5 and 6) is protected against short-circuits. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 111 Wiring 6.10 Connecting the 3DI/LC module for the motor starter Terminal sketch of the 3DI/LC module The following diagram shows a terminal sketch of the 3DI/LC module: Figure 6-10 Connection example of inputs Distributed I/O system 112 System Manual, 02/2018, A5E03576849-AH Wiring 6.11 Connecting the supply voltage to the CPU/interface module 6.11 Connecting the supply voltage to the CPU/interface module Introduction The supply voltage of the CPU/interface module is supplied by means of a 4-pin connector plug located on the front of the CPU/interface module. Power supply unit Only use power supply units of type SELV/PELV with safe electrically isolated functional extra low voltage ( 28.8 V DC). Connection for supply voltage (X80) The connections have the following meaning: Ground of the supply voltage Ground of the supply voltage for looping through (permitted value 10 A) + 24 V DC of the supply voltage for looping through (permitted value 10 A) Spring release + 24 V DC of the supply voltage 1L+ and 2L+ and 1M and 2M are internally jumpered. Figure 6-11 Supply voltage connection The maximum cross-section of the connection is 2.5 mm2 without wire-end ferrule or 1.5 mm2 with wire-end ferrule. A strain relief is not present. The connector plugs provide you with the option of looping the supply voltage through without interruption, even when it is unplugged. Requirements Only wire up the connector plug when the supply voltage is turned off. Follow the wiring rules (Page 99). Required tools 3 to 3.5 mm screwdriver Distributed I/O system System Manual, 02/2018, A5E03576849-AH 113 Wiring 6.11 Connecting the supply voltage to the CPU/interface module Tool-free connection of cables: single-wire without end sleeve, multi-wire (stranded) with end sleeve or ultrasonically sealed Watch video sequence: "Connect BusAdapter to the interface module" (http://support.automation.siemens.com/WW/view/en/95886218) To connect a wire without tools, follow these steps: 1. Strip 8 to 10 mm of the wires. 2. Only in the case of stranded conductors: Seal or crimp the wire with end sleeves. 3. Insert the cable into the push-in terminal as far as it will go. 4. Push the wired connector plug into the plug socket of the interface module. Connection of cables: multi-wire (stranded), without end sleeve, unfinished To connect a wire without an end sleeve, follow these steps: 1. Strip 8 to 10 mm of the wires. 2. Using a screwdriver, press the spring release and insert the wire into the push-in terminal as far as it will go. 3. Pull the screwdriver out of the spring release. 4. Push the wired connector plug into the socket in the interface module. Removing a wire Using the screwdriver, press the spring release as far as it will go and pull out the wire. Distributed I/O system 114 System Manual, 02/2018, A5E03576849-AH Wiring 6.12 Connecting interfaces for communication 6.12 Connecting interfaces for communication Connect the communication interfaces of the ET 200SP distributed I/O system using the standardized connector or directly. If you want to prepare communication cables yourself, the interface assignment is specified in the manuals of the corresponding modules. Observe the mounting instructions for the connectors. Detailed information on the available BusAdapters and the procedure for connecting PROFINET IO to the CPU/interface module is available in the BusAdapter (https://support.industry.siemens.com/cs/ww/en/view/109751716) manual. 6.12.1 Connecting PROFINET IO (port P3) to the CPU Introduction You use the RJ-45 bus connector to connect PROFINET IO (port P3) directly to the CPU. Required accessories Cable ties with standard width of 2.5 mm or 3.6 mm for strain relief Please observe the specifications in the PROFINET Installation Guide (http://www.profibus.com). Mounting the bus connector Mount the PROFINET connector in accordance with the instructions in the PROFINET Installation Guide (http://www.profibus.com). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 115 Wiring 6.12 Connecting interfaces for communication Procedure Insert the RJ45 bus connector into the PROFINET port (port P3) on the CPU. Note Cable support and strain relief If you are using a FastConnect RJ-45 bus connector with 90 cable outlet (6GK1901-1BB202AA0), we recommend you provide strain relief for the PROFINET connecting cable. To do so, you need a cable tie with a standard width of 2.5 mm or 3.6 mm. Use it to fasten the PROFINET connecting cable directly after it exits the bus connector to the intended cable support on the CPU (on the front directly below the PROFINET interface X1P3). CPU PROFINET connecting cable Strain relief (cable tie) Cable support FastConnect RJ45 bus connector with 90 cable outlet PROFINET connector (port P3) Figure 6-12 Connecting PROFINET IO (port P3) to the CPU Distributed I/O system 116 System Manual, 02/2018, A5E03576849-AH Wiring 6.12 Connecting interfaces for communication 6.12.2 Connecting the PROFIBUS DP interface to the interface module/communications module CM DP Introduction Using the bus connector (RS485), connect the PROFIBUS DP to the interface module/communications module CM DP. Required tools 3 to 3.5 mm screwdriver Procedure To connect the PROFIBUS DP interface to the interface module / DP communication module CM DP, follow these steps: 1. Connect the PROFIBUS cable to the bus connector. 2. Plug the bus connector into the PROFIBUS DP connector. 3. Securely tighten the fixing screws of the bus connector (0.3 Nm). Interface module PROFIBUS FastConnect bus connector PROFIBUS connecting cable Communications module CM DP Figure 6-13 Connect PROFIBUS DP to the interface module/communications module CM DP Reference You can find additional information on the PROFIBUS FastConnect bus connector in the corresponding product information on the Internet (http://support.automation.siemens.com/WW/view/en/58648998). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 117 Wiring 6.13 Inserting I/O modules / motor starters and BU covers 6.13 Inserting I/O modules / motor starters and BU covers Introduction You insert the I/O modules on the BaseUnits. The I/O modules are self-coding and typecoded. You insert the PotDis-TerminalBlocks on the PotDis-BaseUnits. You insert the BU covers on BaseUnits whose slots are not equipped with I/O modules/PotDis-TerminalBlocks. You insert the BU covers on BaseUnits whose slots have been reserved for future expansion (as empty slots). The BU covers for motor starters serve as touch protection covers for unoccupied slots. The BU covers have a holder for the reference identification label on the inside. For future expansion of the ET 200SP, remove the reference identification label from the holder and insert it into the final I/O module. It is not possible to attach a reference identification label to the BU cover itself. There are three versions: - BU cover with a width of 15 mm - BU cover with a width of 20 mm - BU cover with a width of 30 mm (for motor starters) Requirement Refer to chapter "Application planning (Page 36)". Distributed I/O system 118 System Manual, 02/2018, A5E03576849-AH Wiring 6.13 Inserting I/O modules / motor starters and BU covers Plugging in I/O modules and BU covers Watch video sequence: "Insert I/O modules" (http://support.automation.siemens.com/WW/view/en/95886218) Insert the I/O module or BU cover parallel into the BaseUnit until you hear both latches click into place. Figure 6-14 Plugging in I/O modules or BU covers (using an I/O module as example) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 119 Wiring 6.14 Mounting/disassembly of motor starters 6.14 Mounting/disassembly of motor starters 6.14.1 Mounting the fan Procedure Proceed as follows to mount a fan on a SIMATIC ET 200SP motor starter: 1. Slide the fan onto the motor starter until you can hear the fan engage. Observe the blowing direction of the fan when mounting. The air stream must be directed to the inside of the motor starter. The correct blowing direction is indicated by arrows on the bottom of the fan. 2. Insert the connection plug into the opening above the fan. 3. Secure the fan cable to the fixing eyes on the right-hand side of the fan cover. Note Specified ambient temperatures are not reached if the fan is incorrectly installed If you do not observe the blowing direction of the fan when mounting, the specified ambient temperatures will not be reached. The device shuts down prematurely due to excessively high temperature. Distributed I/O system 120 System Manual, 02/2018, A5E03576849-AH Wiring 6.14 Mounting/disassembly of motor starters 6.14.2 Mounting/disassembly of motor starters Procedure CAUTION Protection against electrostatic charge When handling and installing the SIMATIC ET 200SP motor starter, ensure protection against electrostatic charging of the components. Changes to the system configuration and wiring are only permissible after disconnection from the power supply. To assemble a SIMATIC ET 200SP motor starter, proceed as follows: Position the mechanical interlock of the SIMATIC ET 200SP motor starter in the assembly/disassembly position Place the SIMATIC ET 200SP motor starter onto the BaseUnit. Turn the mechanical interlock clockwise to the parking position Turn the mechanical interlock counterclockwise to the operating position (= end position) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 121 Wiring 6.14 Mounting/disassembly of motor starters Operating position/READY The motor starter is firmly locked in the BaseUnit, and all electrical contacts are connected. Assembly/disassembly position All electrical contacts are open, and you can use the SIMATIC ET 200SP motor starter in the BaseUnit, or you can remove it from the BaseUnit. Parking position/OFF In this position, you cannot remove the SIMATIC ET 200SP motor starter from the BaseUnit, but all electrical contacts are open. In addition, you can open the locking lever on the mechanical rotary interlock in this position, and fix the position with a padlock (shackle diameter 3 mm). This ensures the isolating function in accordance with IEC 60947-1. In the parking position, the motor starter counts as a disconnected element for the head module. During operation, the parking position is therefore a hot swapping state. See also Removing and inserting I/O modules/motor starters (hot swapping) (Page 247) Note Parking position/OFF This position is only permissible for maintenance purposes and not for continuous operation. In this position, dust protection and mechanical durability are not ensured. If you do not use the motor starter for an extended period, remove it and attach the BU cover (3RK1908-1CA00-0BP0). Distributed I/O system 122 System Manual, 02/2018, A5E03576849-AH Wiring 6.14 Mounting/disassembly of motor starters Mount the touch protection cover for the infeed bus on the last BaseUnit. Note Touch protection cover for the infeed bus You will find out how to mount the touch protection cover of the infeed bus on a SIMATIC ET 200SP motor starter in chapter "Mounting the cover for the 500 V AC infeed bus (Page 81)". To connect the assembly, mount the server module after the last BaseUnit. Note Server module You can find out how to assemble/disassemble the server module in chapter "Installing the server module (Page 80)". Note Removing the motor starter You will find out how to remove the motor starter in chapter "Replacing a motor starter (Page 254)". 6.14.3 3DI/LC module Introduction The optional 3DI/LC module with three inputs and one further LC input can be connected to the motor starter. The status of the inputs of the 3DI/LC module can be seen via the process image input (PII) of the motor starter. Note The 3DI/LC module can be used for the motor starter and the fail-safe motor starter. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 123 Wiring 6.14 Mounting/disassembly of motor starters The input actions can be parameterized. For reasons of operational safety, the LC input is permanently set to manual local mode. For example, by parameterizing the inputs DI1 - DI3 with motor CLOCKWISE or motor COUNTER-CLOCKWISE, you can control the motor in manual local mode. The figure below shows the 3DI/LC module. Assembly WARNING Risk of injury from automatic restart When you mount the the 3DI/LC module, the motor starter can switch on autonomously if an ON command (DI1 to DI3) is active. This can result in property damage or serious injury caused by connected devices that are automatically started up. Revoke the ON commands at DI1 to DI3 before mounting the 3DI/LC module. Proceed as follows to mount a 3DI/LC module onto a motor starter: 1. Wire the 3DI/LC module according to the connection diagram. Note Connecting the 3DI/LC module You will find out how to connect the 3DI/LC module in chapter "Connecting the 3DI/LC module for the motor starter (Page 111)". Distributed I/O system 124 System Manual, 02/2018, A5E03576849-AH Wiring 6.14 Mounting/disassembly of motor starters 2. Slide the 3DI/LC module into the motor starter until the 3DI/LC module engages. The figure below shows a motor starter with a mounted 3DI/LC module. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 125 Wiring 6.14 Mounting/disassembly of motor starters Disassembly Proceed as follows to remove a 3DI/LC module from a motor starter: 1. Push the release lever on the rear of the 3DI/LC module. Release lever 2. Remove the 3DI/LC module from the motor starter while pressing the release lever. Distributed I/O system 126 System Manual, 02/2018, A5E03576849-AH Wiring 6.15 Labeling ET 200SP 6.15 Labeling ET 200SP 6.15.1 Factory markings Introduction For better orientation, the ET 200SP is equipped with various markings ex factory, which help in the configuration and connection of the modules. Factory markings Module labeling Color coding of the module classes - Digital input modules: white - Digital output modules: black - Analog input modules: light blue - Analog output modules: dark blue - Technology module: turquoise - Communication module: light gray - Special module: mint green Module information - Functional version of the module, e.g. "X/2/3/4" (= functional version 1) - Firmware version of the module at delivery, e.g. "V1.0.0" - Color code for usable color identification label, e.g. "CC0" - Usable BaseUnit type, e.g. "BU: A0" Color coding of the potential group - Opening the potential group: Light-colored terminal box and light-colored mounting rail release button - Further conduction of the potential group: Dark-colored terminal box and dark-colored mounting rail release button Distributed I/O system System Manual, 02/2018, A5E03576849-AH 127 Wiring 6.15 Labeling ET 200SP Color coding of the spring releases - Process terminals: gray, white - AUX terminals: turquoise - Additional terminals: red, blue - Terminals for self-assembling voltage buses P1, P2: red, blue Module labeling Color coding of the module classes Module information Color coding of the potential group Color coding of the spring releases (by group) Figure 6-15 6.15.2 Factory markings Optional markings Introduction In addition to the factory markings, there are also other options for labeling and/or marking terminals, BaseUnits and I/O modules for the ET 200SP distributed I/O system. Distributed I/O system 128 System Manual, 02/2018, A5E03576849-AH Wiring 6.15 Labeling ET 200SP Optional markings Color identification labels The color identification labels are module-specific labels for color coding the potentials of the I/O modules. A color code (e.g. 01) is printed on each color identification label and I/O module. The color code allows you to read which color identification label is required for the terminals of the associated BaseUnit directly from the I/O module. The following versions of color coded labels are available: Module-specific color combinations for the process terminals (see the device manuals I/O modules (http://support.automation.siemens.com/WW/view/en/55679691/133300)). The different colors have the following meaning: Gray = input or output signal, red = potential +, blue = ground. For the AUX terminals in the colors yellow-green, blue or red For the add-on terminals in the colors blue-red For the potential distributor modules (see manual BaseUnits (http://support.automation.siemens.com/WW/view/en/59753521)): - For PotDis-BaseUnit PotDis-BU-P1/x-R: red For PotDis-BaseUnit PotDis-BU-P2/x-B: blue - For PotDis-TB-P1-R: red or gray For PotDis-TB-P2-B: blue or gray For PotDis-TB-BR-W: depending on application, yellow/green, blue, red or gray For PotDis-TB-n.c.-G: gray Reference identification labels The reference identification labels (in accordance with EN 81346) can be inserted onto each CPU/interface module, BusAdapter, BaseUnit, I/O module and PotDis-TerminalBlock. This makes it possible to create a fixed assignment between the reference identification label of the BaseUnit and the I/O module/PotDis-TerminalBlock. With the standard plotter setting, the reference identification label is suitable for automatic labeling with E-CAD systems. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 129 Wiring 6.15 Labeling ET 200SP Labeling strips The labeling strips can be inserted in the CPU/interface module, I/O module and BU cover and allow identification of the ET 200SP distributed I/O system. The labeling strips can be ordered on a roll for thermal transfer printers or as DIN A4 format sheets for laser printers. Reference identification labels Labeling strips Color identification labels Figure 6-16 6.15.3 Optional markings Applying color identification labels Requirements The BaseUnits must not be wired when you apply the color identification labels. Required tools 3 mm screwdriver (only for removing the color identification labels) Distributed I/O system 130 System Manual, 02/2018, A5E03576849-AH Wiring 6.15 Labeling ET 200SP Applying color identification labels Press color identification labels into the terminal box of the BaseUnit. Note To remove the color identification labels, you must first disconnect the wiring on the BaseUnit and then carefully lever the color identification labels out of the holder using a screwdriver. Module-specific color identification labels (15 mm) for the process terminals. You can find additional information in the I/O Module (http://support.automation.siemens.com/WW/view/en/55679691/133300) manual. Color identification labels (15 mm) for the 10 AUX terminals Color identification label (15 mm) for the 10 add-on terminals Color identification labels (20 mm) for the 4 AUX terminals Color identification labels (20 mm) for the 2 AUX terminals Figure 6-17 Applying color identification labels (example) NOTICE AUX bus as PE bar If you use an AUX bus as a protective conductor (PE), attach the yellow-green color identification labels to the AUX terminals. If you stop using the AUX terminals as a protective conductor bar, remove the yellow-green color identification labels and make sure that the system is still protected. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 131 Wiring 6.15 Labeling ET 200SP NOTICE Supply of incorrect potential possible Check that the color-coded labels/wiring is correct before commissioning the plant. 6.15.4 Applying labeling strips Procedure Watch video sequence: "Labeling" (http://support.automation.siemens.com/WW/view/en/95886218) Proceed as follows to install a labeling strip: 1. Label the strips. 2. Insert the labeling strip into the interface module or I/O module. Distributed I/O system 132 System Manual, 02/2018, A5E03576849-AH Wiring 6.15 Labeling ET 200SP 6.15.5 Applying reference identification labels Procedure Watch video sequence: "Labeling" (http://support.automation.siemens.com/WW/view/en/95886218) Proceed as follows to install a reference identification label: 3. Break off the reference identification labels from the sheet. 4. Insert the reference identification labels into the opening on the CPU/interface module, BusAdapter, BaseUnit, I/O module and PotDis-TerminalBlock. The insertion opening is located on top of the BaseUnit or the I/O module/PotDis-TerminalBlock. Note Reference identification label The printable side of the reference identification label must be facing forward. Reference identification labels Opening for label Figure 6-18 Applying reference identification labels Distributed I/O system System Manual, 02/2018, A5E03576849-AH 133 7 Configuring 7.1 Configuring ET 200SP Introduction The ET 200SP distributed I/O system is configured and assigned parameters with STEP 7 (CPU/interface module, I/O modules, motor starter and server module) or using configuration software of a third-party manufacturer (interface module, I/O modules, motor starter and server module). "Configuring" is understood to mean the arranging, setup and networking of devices and modules within the device view or network view. STEP 7 graphically represents modules and racks. Just like "real" module racks, the device view allows the insertion of a defined number of modules. When the modules are inserted, STEP 7 automatically assigns the addresses and a unique hardware identifier (HW identifier). You can change the addresses later. The hardware identifiers cannot be changed. When the automation system is started, the CPU/interface module compares the configured planned configuration with the system's actual configuration. You can make parameter settings to control the response of the CPU/interface module to errors in the hardware configuration. "Parameterizing" the components used signifies setting their properties. During parameter assignment, the hardware parameters are set and the settings for data exchange are made: Properties of the modules to which parameters can be assigned Settings for data exchange between components STEP 7 compiles the hardware configuration (result of "configuring" and "assigning parameters") and downloads it to the CPU/interface module. The CPU/interface module then connects to the configured components and transfers their configuration and parameters. Modules can be replaced very easily because STEP 7 transfers the configuration and parameters when a new module is inserted. Distributed I/O system 134 System Manual, 02/2018, A5E03576849-AH Configuring 7.1 Configuring ET 200SP Requirements for configuration of the CPU Table 7- 1 Requirement for installing the CPU Configuration software Requirements CPU 151xSP-1 PN: * STEP 7 (TIA Portal) as of V13 Update 3 PROFINET IO * PROFIBUS DP (optional): With the communication module CM DP CPU 151xSP F-1 PN: Installation information STEP 7 online help STEP 7 (TIA Portal) as of V13 SP1 CPU 151xSP-1PN (as of FW version V1.8), CPU 151xSP F-1 PN (as of FW version V1.8): STEP 7 (TIA Portal) as of V13 SP1 Update 4 Requirements for configuration of the interface module Table 7- 2 Requirement for installing the interface module Configuration software Requirements STEP 7 (TIA Portal) as of V11 SP2* * PROFINET IO: As of Support Package HSP0024 STEP 7 as of V5.5 SP2 * PROFINET IO: GSD file GSDML-Vx.y-siemenset200sp-"Date in format yyyymmdd".xml (http://support.automation.siemens.com/WW/view/e n/19698639/130000) Software of third-party manufacturer * Installation information STEP 7 online help Manufacturer documentation PROFIBUS DP: GSD file SI0xxxxx.gsx (http://support.automation.siemens.com/WW/view/e n/10805317/14280) * The TIA Portal supports GSDML specification V2.25. The ET 200SP distributed I/O system is delivered with a GSD file based on specification V2.3. The GSD file can be installed in the TIA Portal and used without restrictions. Configuring a motor starter You configure SIMATIC ET 200SP motor starters in exactly the same way as the I/O modules of the ET 200SP distributed I/O system. The GSD files can be used with STEP 7 V5.5 SP4 and higher, and TIA Portal V13 SP1 and higher. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 135 Configuring 7.1 Configuring ET 200SP Configuration of the ET 200SP See the STEP 7 online help or the documentation of the configuration software manufacturer. Note For I/O modules that are installed on a BaseUnit BU..D (light-colored BaseUnit), you always have to set the parameter "Potential group" to "Enable new potential group". If you do not set this parameter correctly, the CPU/interface module goes to STOP and generates a parameter error. Note For PROFIBUS with configuration via GSD file In the configuration software, you must set for the BU covers whether these are on a lightcolored or dark-colored BaseUnit. Distributed I/O system 136 System Manual, 02/2018, A5E03576849-AH Configuring 7.2 Configuring the CPU 7.2 Configuring the CPU 7.2.1 Reading out the configuration Introduction When a connection exists to a physically present CPU, you can load the configuration of this CPU (including centrally present modules) from the device into your project using the "Hardware detection" function. You do not need to manually configure the CPU and the centrally present modules, as the physical configuration is read out automatically. If you have already configured a CPU and the centrally present modules and you want to load the current configuration and parameters in a new project, it is advisable to use the "Upload device as new station" function. For additional information about this function, refer to section Backing up and restoring the CPU configuration (Page 231). Procedure for reading out an existing configuration 5. Create a new project and configure an "Unspecified CPU". Figure 7-1 Unspecified CPU in the device view Distributed I/O system System Manual, 02/2018, A5E03576849-AH 137 Configuring 7.2 Configuring the CPU 6. In the device view (or in the network view), select the "Hardware detection" command in the "Online" menu. Figure 7-2 Hardware detection in the Online menu You can also double-click the CPU and click "Detect" in the message. Figure 7-3 Hardware detection message in the device view 7. In the "Hardware detection for PLC_x" dialog box, click "Refresh". Then, select the CPU and the PG/PC interface and click "Detect". STEP 7 downloads the hardware configuration including the modules from the CPU to your project. Figure 7-4 Result of the hardware detection in the device view Distributed I/O system 138 System Manual, 02/2018, A5E03576849-AH Configuring 7.2 Configuring the CPU STEP 7 assigns a valid default parameter assignment for all modules. You can change the parameter assignment subsequently. Note If you want to go online after the hardware detection, you have to first download the detected configuration to the CPU; otherwise, an error may occur due to inconsistent configurations. Properties of central modules The properties of the CPUs have special significance for system behavior. You can set the following for a CPU using STEP 7: Startup behavior Parameter assignment of the interface(s), for example, IP address, subnet mask Web server, e.g. activation, user administration, and languages OPC UA server Global Security Certificate Manager Cycle times, e.g. maximum cycle time System and clock memory Protection level for access protection with assigned password parameter Time and day settings (daylight saving/standard) The properties that can be set and the corresponding value ranges are specified by STEP 7. Fields that cannot be edited are grayed out. Reference Information about the individual settings can be found in the online help and in the manuals of the relevant CPUs. 7.2.2 Addressing Introduction In order to address the automation components or I/O modules, they have to have unique addresses. The following section explains the various address areas. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 139 Configuring 7.2 Configuring the CPU I/O address I/O addresses (input/output addresses) are required in the user program to read inputs and set outputs. STEP 7 automatically assigns input and output addresses when you connect the modules. Each module uses a continuous area in the input and/or output addresses corresponding to its volume of input and output data. Figure 7-5 Example with input / output addresses from STEP 7 STEP 7 assigns the address areas of the modules by default to the process image partition 0 ("Automatic updating"). This process image partition is updated in the main cycle of the CPU. Device address (e.g. Ethernet address) Device addresses are addresses of programmable modules with interfaces to a subnet (e.g., IP address or PROFIBUS address). They are required to address the various devices on a subnet, for example, to download a user program. Distributed I/O system 140 System Manual, 02/2018, A5E03576849-AH Configuring 7.2 Configuring the CPU Hardware identifier STEP 7 automatically assigns a hardware identifier to identify and address modules and submodules. You use the hardware identifier in the case of diagnostic messages or operations, for example, to identify a defective module or the module addressed. Figure 7-6 Example of a hardware identifier from STEP 7 In the "System constants" tab, you will find all hardware identifiers and their symbolic names (of the hardware identifier) for the selected module. You can also find the hardware identifiers and names for all modules of a device in the default tag table of the "System constants" tab. Figure 7-7 Example of an excerpt from a default tag table in STEP 7 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 141 Configuring 7.2 Configuring the CPU 7.2.3 Process images and process image partitions 7.2.3.1 Process image - overview Process image of the inputs and outputs The process image is a memory area of the CPU and includes an image of the signal states of the input/output modules. At the start of the cyclic program, the CPU transfers the signal states of the input modules to the process image of the inputs. At the end of the cyclic program, the CPU transfers the process image of the outputs as a signal state to the output modules. You access this process image memory area in the user program by addressing the operand areas inputs (I) and outputs (O). Advantages of the process image A process image offers the advantage that you can access a consistent image of the process signals during cyclic program execution. If a signal state at an input module changes during program processing, the signal state is retained in the process image. The CPU does not update the process image until the next cycle. You can only assign the addresses of a module to a single process image partition. 32 process image partitions By means of process image partitions, the CPU synchronizes the updated inputs/outputs of particular modules with defined user program sections. The overall process image is subdivided into up to 32 process image partitions (PIP). The CPU updates PIP 0 in each program cycle (automatic update) and assigns it to OB 1. You can assign the process image partitions PIP 1 to PIP 31 to the other OBs during configuration of the input/output modules in STEP 7. After the OB has been started, the CPU updates the assigned process image partition for inputs and reads in the process signals. At the end of the OB the CPU writes the outputs of the assigned process image partition directly to the peripheral outputs without having to wait for the completion of the cyclic program processing. 7.2.3.2 Automatically updating process image partitions You can assign one process image partition to each organization block. In this case, the user program automatically updates the process image partition. The exceptions are PIP 0 and isochronous OBs. Distributed I/O system 142 System Manual, 02/2018, A5E03576849-AH Configuring 7.2 Configuring the CPU Updating the process image partition The process image partition is divided into two parts: Process image partition of the inputs (PIPI) Process image partition of the outputs (PIPQ) The CPU always updates/reads the process image partition of the inputs (PIPI) before processing of the associated OB. The CPU outputs the process image of the outputs (PIPQ) at the end of the OB. The figure below illustrates the updating of the process image partitions. Figure 7-8 7.2.3.3 Updating process image partitions Update process image partitions in the user program Requirements As an alternative to the automatic updating of process image partitions, you can update process images with the "UPDAT_PI" instruction or the "UPDAT_PO" instruction. In STEP 7, these instructions are available on the "Instructions" task card under "Extended instructions". They can be called from any point in the program. Requirements for updating process image partitions with the "UPDAT_PI" and "UPDAT_PO" instructions: The process image partitions are not allowed to be assigned to any OB, which means they are not allowed to be automatically updated. Note Update of PPI 0 PIP 0 (automatic update) cannot be updated with the "UPDAT_PI" and "UPDAT_PO" instructions. UPDAT_PI: updates the process image partition of the inputs With this instruction you read the signal states from the input modules into the process image partition of the inputs (PIPI). UPDAT_PO: updates the process image partition of the outputs With this instruction you transfer the process image partition of the outputs to the output modules. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 143 Configuring 7.2 Configuring the CPU Synchronous cycle interrupt OB In the synchronous cycle interrupt OBs, you use the "SYNC_PI" and "SYNC_PO" operations to update the process image partitions of the operations. For additional information on the synchronous cycle interrupt OBs, refer to the STEP 7 Online Help. Direct I/O access to the inputs and outputs of the module You also have direct read and write access to the I/O, as an alternative to access via the process image, should direct access be required for programming reasons. This prevents a subsequent output of the process image from again overwriting the value written by direct access. Reference Additional information on process image partitions is available in the function manual, Cycle and response times (http://support.automation.siemens.com/WW/view/en/59193558). Distributed I/O system 144 System Manual, 02/2018, A5E03576849-AH Configuring 7.3 Configuring the interface module 7.3 Configuring the interface module Configuring Read the STEP 7 online help and/or the documentation of the configuration software manufacturer when configuring the interface module. The F-destination address is saved permanently on the coding element of the ET 200SP fail-safe modules. Fail-safe motor starters do not need an F-destination address or a coding element. Note The supply voltage L+ must be applied to the F-module when the F-destination address is assigned. Note Note the following in conjunction with configuration control: Before you can use configuration control together with F-modules, you must assign the F-destination address to the F-modules at the designated slots. For this, each F-module must be inserted in the slot configured for it. The actual configuration can then differ from the specified configuration. For additional information on assigning the F-destination address, refer to the SIMATIC Safety - Configuring and Programming (http://support.automation.siemens.com/WW/view/en/54110126) Programming and Operating Manual and to the online help for the S7 Configuration Pack. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 145 8 Basics of program execution 8.1 Events and OBs Response to triggers The occurrence of a start event results in the following reaction: If the event comes from an event source to which you have assigned an OB, this event triggers the execution of the assigned OB. The event enters the queue according to its priority. If the event comes from an event source to which you have not assigned an OB, the CPU executes the default system reaction. Note Some event sources, such as startup, pull/plug, exist even if you do not configure them. Start events The table below provides an overview of: Possible event sources Possible values for the OB priority Possible OB numbers Default system reaction Number of OBs Table 8- 1 Start events Types of event sources Possible priorities (default priority) Possible OB numbers Default system response 1) Number of OBs Starting 2) 1 100, 123 Ignore 0 to 100 Cyclic program 1 1, 123 Ignore 0 to 100 Time-of-day interrupt 2) 2 to 24 (2) 10 to 17, 123 Not applicable 0 to 20 Time-delay interrupt 2 to 24 (3) 20 to 23, 123 Not applicable 0 to 20 2 to 24 (8 to 17, frequency dependent) 30 to 38, 123 Not applicable 0 to 20 Hardware interrupt 2) 2 to 26 (18) 40 to 47, 123 Ignore 0 to 50 Status interrupt 2 to 24 (4) 55 Ignore 0 or 1 Update interrupt 2 to 24 (4) 56 Ignore 0 or 1 Manufacturer-specific or profile-specific interrupt 2 to 24 (4) 57 Ignore 0 or 1 Cyclic interrupt 2) 2) 2) Distributed I/O system 146 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.1 Events and OBs Types of event sources Possible priorities (default priority) Possible OB numbers Default system response 1) Number of OBs Synchronous cycle interrupt 16 to 26 (21) 61 to 64, 123 Ignore 0 to 2 Time error 22 80 Ignore 0 or 1 3) Cycle monitoring time exceeded once STOP Diagnostics interrupt 2 to 26 (5) 82 Ignore 0 or 1 Pull/plug interrupt for modules 2 to 26 (6) 83 Ignore 0 or 1 Rack error 2 to 26 (6) 86 Ignore 0 or 1 MC-servo 4) 17 to 26 (25) 91 Not applicable 0 or 1 17 to 26 (25) 67 Not applicable 0 or 1 MC-PreServo 4) MC-PostServo 17 to 26 (25) 95 Not applicable 0 or 1 MC-Interpolator 4) 16 to 26 (24) 92 Not applicable 0 or 1 Programming error (only for global error handling) 2 to 26 (7) 121 STOP 0 or 1 I/O access error (only for global error handling) 2 to 26 (7) 122 Ignore 0 or 1 4) 1) If you have not configured the OB. 2) In the case of these event sources, besides the permanently assigned OB numbers (see column: Possible OB numbers) in STEP 7 you can assign OB numbers from the range 123. 3) If the maximum cycle time has been exceeded twice within one cycle, the CPU always assumes the STOP state, regardless of whether you have configured OB 80. 4) You will find more information on these event sources and the starting behavior in the S7-1500 Motion Control function manual. Assignment between event source and OBs The type of OB determines where you make the assignment between OB and event source: With hardware interrupts and isochronous mode interrupts, the assignment is made during the configuration of the hardware or when the OB is created. In the case of the MC-Servo, MC-PreServo, MC-PostServo and MC-Interpolator, STEP 7 automatically assigns the OBs 91/92 as soon as you add a technology object. For all other types of OB, the assignment is made when the OB is created, where applicable after you have configured the event source. For hardware interrupts, you can change an assignment which has already been made during runtime with the instructions ATTACH and DETACH. In this case, only the actually effective assignment changes, and not the configured assignment. The configured assignment takes effect after loading, and at startup. The CPU ignores hardware interrupts to which you did not assign an OB in your configuration or which occur after the DETACH instruction. The CPU does not check whether an OB is assigned to this event when an event arrives, but only prior to the actual processing of the hardware interrupt. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 147 Basics of program execution 8.1 Events and OBs OB priority and runtime behavior If you have assigned an OB to the event, the OB has the priority of the event. The CPU supports the priority classes 1 (lowest priority) to 26 (highest priority). The following items are essential to the processing of an event: Calling and processing of the assigned OB The update of the process image partition of the assigned OB The user program processes the OBs exclusively on a priority basis. This means the program processes the OB with the highest priority first when multiple OB requests occur at the same time. If an event occurs that has a higher priority than the currently active OB, this OB is interrupted. The user program processes events of the same priority in order of occurrence. Note Communication Communication (e.g. test functions with the PG) always works permanently with the priority 15. So as not to unnecessarily prolong program runtime in the case of time-critical applications, these OBs should not be interrupted by communication. Assign a priority >15 for these OBs. Reference You can find more information on organization blocks in the STEP 7 online help. Distributed I/O system 148 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.2 CPU overload behavior 8.2 CPU overload behavior Requirement For the event scenarios considered in the following section, we assume that you have assigned an OB to each event source and that these OBs have the same priority. The second condition, in particular, is only for the sake of a simplified representation. Principle of CPU overload behavior An occurring event triggers the execution of the associated OB. Depending on the OB priority and the current processor load, a time delay may occur before the OB is executed when there is an overload. The same event can therefore occur once or several times before the user program processes the OB belonging to the preceding event. The CPU treats such a situation as follows: The operating system positions the events in the order of their occurrence into the queue for their priority level. To cope with temporary overload situations, you can limit the number of pending events originating from one and the same source. The next event is discarded as soon as the maximum number of pending start events of a specific cyclic interrupt OB, for example, is reached. An overload occurs when events which originate from the same source occur faster than they can be processed by the CPU. More detailed information is available in the following sections. Discarding similar events or handling them later Below, the term "similar events" refers to events from a single source, such as triggers for a specific cyclic interrupt OB. The OB parameter "Events to be queued" is used to specify how many similar events the operating system places in the associated queue and therefore post-processes. If this parameter has the value 1, for example, exactly one event is stored temporarily. Note The post-processing of cyclic events is often undesirable, as this can lead to an overload with OBs of the same or lower priority. Therefore, it is generally advantageous to discard similar events and to react to the overload situation during the next scheduled OB processing. If the value of the "Events to be queued" parameter is low, this ensures that an overload situation is defused rather than aggravated. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 149 Basics of program execution 8.2 CPU overload behavior If the maximum number of start events is reached in the queue for a cyclic interrupt OB (Cyclic interrupt), for example, each additional start event is only counted and subsequently discarded. During the next scheduled execution of the OB, the CPU provides the number of discarded start events in the "Event_Count" input parameter (in the start information). You can then react appropriately to the overload situation. The CPU then sets the counter for lost events to zero. If the CPU discards a start event for a cyclic interrupt OB the first time, its further behavior depends on the OB parameter "Report event overflow into diagnostics buffer": If the check box is selected, the CPU enters the event DW#16#0002:3507 once in the diagnostics buffer for the overload situation at this event source. The CPU suppresses additional diagnostics buffer entries of the event DW#16#0002:3507 that refer to this event source until all events from this source have been post-processed. Threshold mechanism for time error OB request The cyclic interrupt OB parameter "Enable time error" is used to specify whether the time error interrupt should be called when a specific overload level is reached for similar events. You can find the OB parameter "Enable time error" in the properties of the OB in the "Attributes" category. If you enable the time error OB (option box set), you define, with the "Event threshold for time error" OB parameter, the number of similar events in the queue that cause the user program to call the time error OB. If this parameter has the value 1, for example, the CPU enters the event DW#16#0002:3502 once in the diagnostics buffer and requests the time error OB when the second event occurs. The CPU suppresses additional diagnostics buffer entries of the event DW#16#0002:3502 until all events from this source have been postprocessed. In the event of an overload, you therefore have the option of programming a reaction well before the limit is reached for similar events and thus before the events are discarded. The following value range applies to the "Event threshold for time error" parameter: 1 "Event threshold for time error" "Events to be queued". Distributed I/O system 150 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.3 Asynchronous instructions 8.3 Asynchronous instructions Difference between synchronous/asynchronous instructions In program processing, a differentiation is made between synchronous and asynchronous instructions. The "synchronous" and "asynchronous" properties relate to the temporal relationship between the call and execution of the instruction. The following applies to synchronous instructions: When the call of a synchronous instruction is ended, the execution is also ended. This is different in the case of asynchronous instructions: When the call of an asynchronous instruction is ended, the execution of the asynchronous instruction is not necessarily ended yet. This means the execution of an asynchronous instruction can extend over multiple calls. The CPU processes asynchronous instructions in parallel with the cyclic user program. Asynchronous instructions generate jobs in the CPU for their processing. Asynchronous instructions are usually instructions for transferring data (data records for modules, communication data, diagnostics data). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 151 Basics of program execution 8.3 Asynchronous instructions Processing of asynchronous instructions The figure below shows the difference between processing an asynchronous instruction and processing a synchronous instruction. In this figure the asynchronous instruction is called five times before the execution is completed, for example, a data record is completely transferred. First call of the asynchronous instruction, start of processing Intermediate call of asynchronous instruction, continuation of processing Last call of the asynchronous instruction, termination of processing The synchronous instruction is completely processed at each call Duration of the complete processing Figure 8-1 Difference between synchronous and asynchronous instructions Distributed I/O system 152 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.3 Asynchronous instructions Parallel processing of asynchronous instruction jobs A CPU can process several asynchronous instruction jobs in parallel. The CPU processes the jobs in parallel under the following conditions: Several asynchronous instruction jobs are called at the same time. The maximum number of concurrently running jobs for the instruction is not exceeded. The figure below shows the parallel processing of two jobs of the instruction WRREC. The two instructions are processed in parallel for a specific period here. Figure 8-2 Parallel processing of the asynchronous instruction WRREC Assignment of call to job of the instruction To execute an instruction over multiple calls, the CPU must be able to uniquely assign a subsequent call to a running job of the instruction. To assign a call to a job, the CPU uses one of the following two mechanisms, depending on the type of the instruction: Via the instance data block of the instruction (in the case of the "SFB" type) The input parameters of the instruction identifying the job. These input parameters must match in each call during processing of the asynchronous instruction. Example: A "Create_DB" instruction job is identified by the input parameters LOW_LIMIT, UP_LIMIT, COUNT, ATTRIB and SRCBLK. The following table shows which instruction you can identify with which input parameters. Instruction Job is identified by DPSYC_FR LADDR, GROUP, MODE D_ACT_DP LADDR DPNRM_DG LADDR WR_DPARM LADDR, RECNUM WR_REC LADDR, RECNUM RD_REC LADDR, RECNUM CREATE_DB LOW_LIMIT, UP_LIMIT, COUNT, ATTRIB, SRCBLK READ_DBL SRCBLK, DSTBLK WRIT_DBL SRCBLK, DSTBLK RD_DPARA LADDR, RECNUM DP_TOPOL DP_ID Distributed I/O system System Manual, 02/2018, A5E03576849-AH 153 Basics of program execution 8.3 Asynchronous instructions Status of an asynchronous instruction An asynchronous instruction shows its status via the block parameters STATUS/RET_VAL and BUSY. Many asynchronous instructions also use the block parameters DONE and ERROR. The figure below shows the two asynchronous instructions WRREC and CREATE_DB. The input parameter REQ starts the job to execute the asynchronous instruction. The output parameter ERROR indicates that an error has occurred. The output parameter DONE indicates that the job was completed without error. The output parameter BUSY indicates whether the job is currently being processed. When BUSY =1, a resource is assigned for the asynchronous instruction. If BUSY = 0, then the resource is free. The output parameter STATUS/RET_VAL provides information on the status of the job execution. The output parameter STATUS/RET_VAL receives the error information after the occurrence of an error. Figure 8-3 Block parameters of asynchronous instructions using the instructions WRREC and CREATE_DB as examples. Summary The table below provides you with an overview of the relationships described above. It shows in particular the possible values of the output parameters if processing is not completed after a call. Note Following every call, you must evaluate the relevant output parameters in your program. Distributed I/O system 154 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.3 Asynchronous instructions Relationship between REQ, STATUS/RET_VAL, BUSY and DONE during a "running" job. Seq. no. of the call Type of call REQ STATUS/RET_VAL BUSY DONE ERROR 1 First call 1 W#16#7001 1 0 0 Error code (for example, W#16#80C3 for lack of resources) 0 0 1 2 to (n - 1) Intermediate call Not relevant W#16#7002 1 0 0 n Not relevant W#16#0000, if no errors have occurred. 0 1 0 Error code, if errors have occurred 0 0 1 Last call Consumption of resources Asynchronous instructions occupy resources in the CPU while they are being processed. The resources are limited depending on the type of CPU and instruction; the CPU can only process a maximum number of asynchronous instruction jobs simultaneously. The resources are available again after a job has been successfully completed or processed with an error. Example: For the RDREC instruction, a 1512SP-1 PN CPU can process up to 20 jobs in parallel. If the maximum number of simultaneous jobs for an instruction is exceeded, the instruction returns the error code 80C3 (lack of resources) in the block parameter STATUS. The execution of the job is stopped until a resource becomes free again. Note Lower-level asynchronous instructions Several asynchronous instructions use one or more lower-level asynchronous instructions for their processing. This dependence is shown in the tables below. Please note that, if there are several lower-level instructions, typically only one lower-level instruction is occupied at one time. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 155 Basics of program execution 8.3 Asynchronous instructions Extended instructions: maximum number of concurrently running jobs The table below shows the maximum number of concurrently running jobs for asynchronous extended instructions. Extended instructions CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN Distributed I/O RDREC 20 RD_REC 10 WRREC 20 WR_REC 10 D_ACT_DP 8 ReconfigIOSystem uses RDREC, WRREC, D_ACT_DP, DPSYC_FR 2 DPNRM_DG 8 DP_TOPOL ASI_CTRL 1 uses RDREC, WRREC PROFIenergy PE_START_END uses RDREC, WRREC PE_CMD uses RDREC, WRREC PE_DS3_Write_ET200S uses RDREC, WRREC PE_WOL uses RDREC, WRREC, TUSEND, TURCV, TCON, TDISCON Module parameter assignment RD_DPAR 10 RD_DPARA 10 RD_DPARM 10 WR_DPARM 10 Diagnostics Get_IM_Data 10 GetStationInfo 10 Recipes and data logging RecipeExport 10 RecipeImport 10 DataLogCreate 10 DataLogOpen 10 DataLogWrite 10 DataLogClear 10 DataLogClose 10 DataLogDelete 10 DataLogNewFile 10 Data block functions CREATE_DB 10 READ_DBL 10 Distributed I/O system 156 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.3 Asynchronous instructions Extended instructions CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN WRIT_DBL 10 DELETE_DB 10 File handling FileReadC 10 FileWriteC 10 Basic instructions: maximum number of concurrently running jobs The table below shows the maximum number of concurrently running jobs for asynchronous basic instructions. Basic instructions CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN Array DB ReadFromArrayDBL uses READ_DBL (see Extended instructions) WriteToArrayDBL uses READ_DBL, WRIT_DBL (see Extended instructions) Communication: maximum number of concurrently running jobs The following table shows the maximum number of simultaneously running jobs for asynchronous instructions (Open User Communication) for the various CPUs. Open User Communication CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN 64 88 64 88 TCON 64 88 TDISCON 64 88 T_RESET 64 88 T_DIAG 64 88 TSEND TUSEND TRCV TURCV T_CONFIG 1 TSEND_C uses TSEND, TUSEND, TRCV, TCON, TDISCON TRCV_C uses TSEND, TUSEND, TRCV, TURCV, TCON, TDISCON TMAIL_C uses TSEND, TUSEND, TRCV, TURCV, TCON, TDISCON Distributed I/O system System Manual, 02/2018, A5E03576849-AH 157 Basics of program execution 8.3 Asynchronous instructions The following table shows the maximum number of simultaneously running jobs for asynchronous instructions (MODBUS TCP) for the various CPUs. MODBUS TCP CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510P F-1 PN CPU 1512SP F-1 PN MB_CLIENT uses TSEND, TUSEND, TRCV, TURCV, TCON, TDISCON MB_SERVER uses TSEND, TUSEND, TRCV, TURCV, TCON, TDISCON The table below shows the maximum number of simultaneously running jobs for asynchronous instructions (S7 communication) for the various CPUs. The S7 communication instructions use a common pool of resources. S7 communication CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN 192 264 PUT GET USEND URCV BSEND BRCV The following table shows the maximum number of simultaneously running jobs for asynchronous instructions (communication processors) for the various CPUs. Communications processors CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN PtP communication Port_Config uses RDDEC, WRREC Send_Config uses RDDEC, WRREC Receive_Config uses RDDEC, WRREC Send_P2P uses RDDEC, WRREC Receive_P2P uses RDDEC, WRREC Receive_Reset uses RDDEC, WRREC Signal_Get uses RDDEC, WRREC Signal_Set uses RDDEC, WRREC Get_Features uses RDDEC, WRREC Set_Features uses RDDEC, WRREC USS communication USS_Port_Scan uses RDDEC, WRREC MODBUS (RTU) Modbus_Comm_Load uses RDDEC, WRREC ET 200S serial interface S_USSI uses CREATE_DB SIMATIC NET FTP_CMD uses TSEND, TRCV, TCON, TDISCON Distributed I/O system 158 System Manual, 02/2018, A5E03576849-AH Basics of program execution 8.3 Asynchronous instructions The following table shows the maximum number of simultaneously running jobs for asynchronous instructions (OPC UA) for the various CPUs. OPC_UA CPU 1510SP-1 PN CPU 1512SP-1 PN CPU 1510SP F-1 PN CPU 1512SP F-1 PN OPC_UA_Connect 10 OPC_UA_Disconnect 10 OPC_UA_NamespaceGetIndexList 10 OPC_UA_NodeGetHandleList 10 OPC_UA_NodeReleaseHandleList 10 OPC_UA_TranslatePathList 10 OPC_UA_Browse 10 OPC_UA_ReadList 10 OPC_UA_WriteList 10 OPC_UA_MethodGetHandleList 10 OPC_UA_MethodReleaseHandleList 10 OPC_UA_MethodCall 10 OPC_UA_ServerMethodPre 10 OPC_UA_ServerMethodPost 10 OPC_UA_ConnectionGetStatus 10 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 159 Basics of program execution 8.3 Asynchronous instructions Technology: maximum number of concurrently running jobs The following table shows the maximum number of simultaneously running jobs for asynchronous instructions (Technology). Technology CPU 1510SP-1 PN CPU 1510SP F-1 PN CPU 1512SP-1 PN CPU 1512SP F-1 PN Motion Control MC_Power 300 MC_Reset MC_Home MC_Halt MC_MoveAbsolute MC_MoveRelative MC_MoveVelocity MC_MoveJog MC_GearIn MC_MoveSuperimposed MC_MeasuringInput MC_MeasuringInputCyclic MC_AbortMeasuringInput MC_OutputCam MC_CamTrack MC_TorqueLimiting Additional information You can find additional information on block parameter assignment in the STEP 7 online help. Distributed I/O system 160 System Manual, 02/2018, A5E03576849-AH 9 Protection 9.1 Overview of the protective functions of the CPU Introduction This chapter describes the following functions for protecting the ET 200SP against unauthorized access: Access protection Know-how protection Copy protection Further measures for protecting the CPU The following measures additionally increase the protection against unauthorized access to functions and data of the CPU from external sources and via the network: Deactivation of the Web server Deactivation of the OPC UA server (you will find further information on the security mechanisms for OPC UA servers in the Communication (https://support.industry.siemens.com/cs/ww/en/view/59192925) function manual) Deactivation of time synchronization via an NTP server Deactivation of PUT/GET communication When using the Web server, you protect your ET 200SP distributed I/O system against unauthorized access By setting password-protected access rights for certain users in user management. By using the default "Allow access via HTTPS only" option. This option allows access to the Web server with the secure Hypertext transfer protocol HTTPS only. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 161 Protection 9.2 Configuring access protection for the CPU 9.2 Configuring access protection for the CPU Introduction The CPU offers four access levels to limit access to specific functions. By setting up the access levels and the passwords for a CPU, you limit the functions and memory areas that are accessible without entering a password. You specify the individual access levels as well as the entry of their associated passwords in the object properties of the CPU. Access levels of the CPU Table 9- 1 Access levels and access restrictions Access levels Access restrictions Full access (no protection) Any user can read and change the hardware configuration and the blocks. Read access With this access level, read-only access to the hardware configuration and the blocks is possible without entering a password, which means you can download the hardware configuration and blocks to the programming device. In addition, HMI access and access to diagnostics data is possible. Without entering the password, you cannot load any blocks or hardware configuration into the CPU. Additionally, the following are not possible without the password: HMI access * Writing test functions * Firmware update (online) With this access level only HMI access and access to diagnostics data are possible without entering the password. Without entering the password, you can neither load blocks nor the hardware configuration into the CPU, nor load blocks and hardware configuration from the CPU into the programming device. Additionally, the following are not possible without the password: No access (complete protection) * Writing test functions * Changing the mode (RUN/STOP) * Firmware update (online) * Display of the online/offline comparison status When the CPU has complete protection, no read or write access to the hardware configuration and the blocks is possible (without access authorization in the form of a password). HMI access is also not possible. The server function for PUT/GET communication is disabled in this access level (cannot be changed). Authentication with the password will again provide you full access to the CPU. You can find a list of which functions are possible in the various protection levels in the STEP 7 online help under the entry "Setting options for the protection". Distributed I/O system 162 System Manual, 02/2018, A5E03576849-AH Protection 9.2 Configuring access protection for the CPU Properties of the access levels Each access level allows unrestricted access to certain functions without entering a password, for example, identification using the "Accessible devices" function. The CPU's default setting is "No restriction" and "No password protection". In order to protect access to a CPU, you need to edit the properties of the CPU and set up a password. In the default access level "Full access (no protection)" every user can read and change the hardware configuration and the blocks. A password is not set and is also not required for online access. Communication between the CPUs (via the communication functions in the blocks) is not restricted by the access level of the CPU, unless PUT/GET communication is deactivated in the "No access" (complete protection) access level. Entry of the right password allows access to all the functions that are allowed in the corresponding level. Note Configuring an access level does not replace know-how protection Configuring access levels offers a high degree of protection against unauthorized changes to the CPU by restricting the rights to download the hardware and software configuration to the CPU. However, blocks on the SIMATIC memory card are not write- or read-protected. Use know-how protection to protect the code of blocks on the SIMATIC memory card. Behavior of functions with different access levels The STEP 7 online help includes a table which lists the online functions that are available in the different access levels. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 163 Protection 9.2 Configuring access protection for the CPU Selecting the access levels To configure the access levels of a CPU, follow these steps: 1. Open the properties of the CPU in the Inspector window. 2. Open the "Protection" entry in the area navigation. A table with the possible access levels is available in the Inspector window. Figure 9-1 Possible access levels 3. Activate the desired protection level in the first column of the table. The green check marks in the columns to the right of the access level show you which operations are still available without entering the password. In the example (see above), read access and HMI access are still possible without a password. 4. In the "Enter password" column, specify a password for the access level "Full access" in the first row. In the "Confirm password" column, enter the selected password again to guard against incorrect entries. Ensure that the password is sufficiently secure, i.e. does not follow a pattern that can be recognized by a machine. 5. Assign additional passwords as needed to other access levels if the selected access level allows you to do so. 6. Download the hardware configuration for the access level to take effect. The CPU logs the entry of the correct or incorrect password and any changes in the configuration of the access levels by a corresponding entry in the diagnostics buffer. Distributed I/O system 164 System Manual, 02/2018, A5E03576849-AH Protection 9.3 Using the user program to set additional access protection Behavior of a password-protected CPU during operation The CPU protection takes effect after you have downloaded the settings to the CPU. Before an online function is executed, the CPU checks the necessary permission and, if necessary, prompts the user to enter a password. You can only execute password-protected functions from one programming device/PC at any time. Another programming device/PC cannot log on. Access authorization to the protected data is in effect for the duration of the online connection or until you rescind the access authorization manually with "Online > Delete access rights". Access levels for F-CPUs For the fail-safe CPUs, there is an additional access level in addition to the four described access levels. For additional information on this access level, refer to the description of the fail-safe system SIMATIC Safety Programming and Operating Manual SIMATIC Safety Configuring and Programming (http://support.automation.siemens.com/WW/view/en/54110126). 9.3 Using the user program to set additional access protection Access protection via user program You can also restrict access to a password-protected CPU in STEP 7 via the ENDIS_PW operation. You can find a description of this block in the online help under the keyword "ENDIS_PW: Limit and enable password legitimation". Distributed I/O system System Manual, 02/2018, A5E03576849-AH 165 Protection 9.4 Know-how protection 9.4 Know-how protection Application You can use know-how protection to protect one or more OB, FB or FC blocks as well as global data blocks in your program from unauthorized access. Enter a password to restrict access to a block. The password offers high-level protection against unauthorized reading or manipulation of the block. Password provider As an alternative to manual entry of password, you can connect a password provider to STEP 7. When using a password provider, you select a password from a list of available passwords. When a protected block is opened, STEP 7 connects to the password provider and retrieves the corresponding password. To connect a password provider you have to install and activate it. A settings file in which you define the use of a password provider is also required. A password provider offers the following advantages: The password provider defines and manages the passwords. When know-how protected blocks are opened, you work with symbolic names for passwords. A password is marked, for example, with the symbolic name "Machine_1" n the password provider. The actual password behind "Machine1" remains hidden from you. A password provider therefore offers you optimum block protection as the users do not know the password themselves. STEP 7 automatically opens know-how protected blocks without the direct entry of a password. This saves you time. You will find more information on connecting a password provider in the STEP 7 online help. Readable data If a block is know-how protected, only the following data is readable without the correct password: Block title, comments and block properties Block parameters (INPUT, OUTPUT, IN, OUT, RETURN) Call structure of the program Global tags without information on the point of use Distributed I/O system 166 System Manual, 02/2018, A5E03576849-AH Protection 9.4 Know-how protection Further actions Further actions that can be carried out with a know-how protected block: Copying and deleting Calling in a program Online/offline comparison Load Global data blocks and array data blocks You can provide global data blocks (global DBs) with know-how protection. Users who do not possess the valid password can read the global data block but not change it. You cannot provide array data blocks (array DBs) with know-how protection. Setting up block know-how protection To set up block know-how protection, follow these steps: 1. Open the properties of the block in question. 2. Select the "Protection" option under "General". Figure 9-2 Setting up block know-how protection (1) 3. Click the "Protection" button to display the "Know-how protection" dialog. Figure 9-3 Setting up block know-how protection (2) Distributed I/O system System Manual, 02/2018, A5E03576849-AH 167 Protection 9.4 Know-how protection 4. Click the "Define" button to open the "Define Password" dialog. Figure 9-4 Setting up block know-how protection (3) 5. Enter the new password in the "New password" box. Enter the same password in the "Confirm password" box. 6. Click "OK" to confirm your entry. 7. Close the "Know-how protection" dialog by clicking "OK". Result: The selected blocks are now know-how protected. Know-how protected blocks are marked with a lock in the project tree. The password entered applies to all blocks selected. Note Password provider Alternatively, you can set up know-how protection for blocks with a password provider. Opening know-how protected blocks To open a know-how protected block, follow these steps: 1. Double-click the block to open the "Access protection" dialog. 2. Enter the password for the know-how protected block. 3. Click "OK" to confirm your entry. Result: The know-how-protected block is open. Once you have opened the block, you can edit the program code and the block interface of the block for as long as the block or STEP 7 is open. You must enter the password again the next time you open the block. If you close the "Access protection" dialog with "Cancel", you will be able to open the block but you cannot display the block code or edit the block. If you copy the block or add it to a library, for example, this does not cancel the know-how protection of the block. The copies will also be know-how-protected. Distributed I/O system 168 System Manual, 02/2018, A5E03576849-AH Protection 9.4 Know-how protection Removing block know-how protection To remove block know-how protection, follow these steps: 1. Select the block from which you want to remove know-how protection. The protected block must not be open in the program editor. 2. In the "Edit" menu, select the "Know-how protection" command to open the "Know-how protection" dialog. 3. Clear the "Hide code (Know-how protection)" check box. Figure 9-5 Removing block know-how protection (1) 4. Enter the password. Figure 9-6 Removing block know-how protection (2) 5. Click "OK" to confirm your entry. Result: Know-how protection is removed from the selected block. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 169 Protection 9.5 Copy protection 9.5 Copy protection Application The copy protection allows you to protect your program against unauthorized duplication. With copy protection you associate the blocks with a specific SIMATIC memory card or CPU. Through the linking of the serial number of a SIMATIC memory card or of a CPU the use of this program or of this block is only possible in conjunction with a specific SIMATIC memory card or CPU. Copy and know-how protection Recommendation: to prevent unauthorized reset of copy protection, additionally apply know-how protection to a copy-protected block. To do this, first set up copy protection and then apply know-how protection for the block. Setting up copy protection To set up copy protection, follow these steps: 1. Open the properties of the block in question. 2. Select the "Protection" option under "General". Figure 9-7 Setting up copy protection (1) 3. In the "Copy protection" area, select either the "Bind to serial number of the CPU" entry or the "Bind to serial number of the memory card" entry from the drop-down list. Figure 9-8 Setting up copy protection (2) Distributed I/O system 170 System Manual, 02/2018, A5E03576849-AH Protection 9.5 Copy protection 4. Activate the option "Serial number is inserted when downloading to a device or a memory card" if the serial number is to be inserted automatically during the uploading process (dynamic binding). Assign a password using the "Define password" button to link the use of a block additionally to the input of a password. Activate the option "Enter serial number" if you want to manually bind the serial number of the CPU or the SIMATIC memory card to a block (static binding). 5. You can now set up the know-how protection for the block in the "Know-how protection" area. Note If you download a copy-protected block to a device that does not match the specified serial number, the entire download operation will be rejected. This means that blocks without copy protection will also not be downloaded. Removing copy protection To remove copy protection, follow these steps: 1. Remove any existing know-how protection. 2. Open the properties of the block in question. 3. Select the "Protection" option under "General". 4. In the "Copy protection" area, select the "No binding" entry from the drop-down list. Figure 9-9 Removing copy protection Distributed I/O system System Manual, 02/2018, A5E03576849-AH 171 10 Configuration control (option handling) Introduction Configuration control (option handling) is used to operate various standard machine configuration levels in one project without changing the configuration or the user program. Operating principle of configuration control You can use configuration control to operate different standard machine configurations with a single configuration of the ET 200SP distributed I/O system. A station master is configured in a project (maximum configuration). The station master comprises all modules needed for all possible plant parts of a modular standard machine. The project's user program provides for several station options for various standard machine configuration levels as well as selection of a station option. A station option uses, for example, only some of the configured modules of the station master and these modules are inserted in the slots in a different order. The standard machine manufacturer selects a station option for a configuration of the standard machine. To do this, the project need not be modified, and it is not necessary to load a modified configuration. You use a control data record you have programmed to notify the CPU/interface module as to which modules are missing or located on different slots in a station option as compared to the station master. The configuration control does not have an impact on the parameter assignment of the modules. Configuration control allows you to flexibly vary the centralized/distributed configuration. This is only possible if the station option can be derived from the station master. The following figure shows three configurations of a standard machine with the corresponding station options of the ET 200SP distributed I/O system. Distributed I/O system 172 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) Figure 10-1 Various configuration levels of a standard machine with the corresponding station options of the ET 200SP distributed I/O system. Advantages Simple project management and commissioning by using a single STEP 7 project for all station options. Simple handling for maintenance, versioning and upgrade: Hardware savings: Only those I/O modules are installed that are required for the machine's current station option. Savings potential in the creation, commissioning and the documentation for standard machines. Simple station expansion by using pre-wired empty slots. To expand, you simply exchange the BU cover for the new model. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 173 Configuration control (option handling) Procedure To set up the configuration control, follow these steps: Step Procedure See... 1 Enable configuration control in STEP 7 Section Configuring (Page 175) 2 Create control data record Section Creating the control data record (Page 177) 3 Transfer control data record Section Transferring the control data record in the startup program of the CPU (Page 188) Block library "OH_S71x00_Library" The block library OH_S71x00_Library (https://support.industry.siemens.com/cs/#document/29430270?lc=en-WW) is available for download from the Internet. The block library contains data types with the structure of the control data records for the ET 200SP distributed I/O system. You can implement your flexible automation solution inexpensively with the help of these data types. Note Configuration control in the case of motor starters "Manual local" mode is possible in the case of motor starters when configuration control is active. The motor starter works with the last valid parameters. Do not change the parameterization while "manual local" mode is active. Distributed I/O system 174 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.1 Configuring 10.1 Configuring Requirements Configuration control is supported by the ET 200SP distributed I/O system with both an ET 200SP CPU and with interface modules via PROFINET IO and PROFIBUS DP. Centrally for ET 200SP CPU: STEP 7 Professional V13 Update 3 or higher CPU 1510SP-1 PN/CPU 1512SP-1 PN Firmware version V1.6 or higher All modules of the CPU must be able to start up even with different configurations. - The startup parameter "Comparison preset to actual configuration" of the CPU is set to "Startup CPU even if mismatch" (default setting) and the module parameter "Comparison preset to actual module" of the module is set to "From CPU" (default setting). or - The module parameter "Comparison preset to actual module" for the module is set to "Startup CPU even if mismatch". Distributed via PROFINET IO: Engineering Tool (e.g. STEP 7) IM 155-6 PN BA/ST/HF/HS You have assigned the interface module to an IO controller. Distributed via PROFIBUS DP: Engineering Tool (e.g. STEP 7) IM 155-6 DP HF You have assigned the interface module to a DP master. The startup parameter is set to "Operate if preset configuration does not match actual configuration" Distributed I/O system System Manual, 02/2018, A5E03576849-AH 175 Configuration control (option handling) 10.1 Configuring Required steps Enable the "Allow to reconfigure the device via the user program" parameter when configuring the CPU/interface module in STEP 7 (TIA Portal). The "Allow to reconfigure the device via the user program" parameter is located in the "Configuration control" area for an ET 200SP CPU. The "Allow to reconfigure the device via the user program" parameter is located in the "Module parameter" area under "General" for an IM 155-6 PN interface module. Figure 10-2 Enabling configuration control using an IM 155-6 PN HF as an example Distributed I/O system 176 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record 10.2 Creating the control data record 10.2.1 Introduction Required steps To create a control data record for the configuration control, follow these steps: 1. Create a PLC data type which contains the structure of the control data record. The following figure shows a PLC data type "CTR_REC", which contains the structure of the control data record for an ET 200SP interface module. Figure 10-3 Creating control data record 196 using an IM 155-6 PN HF as an example 2. Create a global data block. 3. In the data block, create an array that is based on the created PLC data type. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 177 Configuration control (option handling) 10.2 Creating the control data record 4. In the control data records, enter the slot assignments in the "Start value" column. The figure below shows the global data block "ConfDB". The data block "ConfDB" contains an array [0..5] of the PLC_DataType "CTR_REC". Figure 10-4 Data block for configuration control Rules Observe the following rules: Slot entries in the control data record outside the station master are ignored by the CPU/interface module. The control data record must contain the entries up to the last slot of the station option. Multiple configured slots may not be assigned to the same actual slot. In other words, each station option slot may be present only once in the control data record. Distributed I/O system 178 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record 10.2.2 Control data record for an ET 200SP CPU Slot assignment The following table shows the possible slots for the various modules for an ET 200SP CPU: Table 10- 1 Slot assignment Modules Possible slots Comment CPU 1 Slot 1 is always the CPU I/O modules 2 - 65 Downstream of CPU Server module 2 - 66 The server module completes the configuration of the ET 200SP station after the CPU/the last I/O module. Control data record For the configuration control of an ET 200SP CPU, you define a control data record 196 V2.0, which includes a slot assignment. The maximum slot corresponds to the slot of the server module. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 179 Configuration control (option handling) 10.2 Creating the control data record The table below shows the structure of a control data record with explanations of the individual elements. Table 10- 2 Configuration control: Structure of control data record 196 Byte Element Code Explanation 0 Block length 4 + (number of slots x 2) Header 1 Block ID 196 2 Version 2 3 Version 0 4 Slot 1 of the station master Slot assignment 1 in the station option (always 1, because the CPU is always in slot 1) 5 Additional function for slot 1 6 Slot 2 of the station master 7 Additional function for slot 2 8 Slot 3 of the station master 9 Additional function for slot 3 : : : 4 + ((max. slot 1) x 2) Server module slot Server module slot assignment in the station option* 4 + ((max. slot 1)x 2) + 1 Additional function for server module slot Slot assignment in the station option Slot assignment in the station option Control element Contains the information on which module is inserted in which slot. The value that you need to enter in the corresponding byte depends on the following rule: * If the module exists in the station option, enter the slot number of the module. * If the module exists as empty slot (with BU cover), enter the slot number of the module + 128. (Example: module as empty slot on slot 3: Enter 131 in the control element) If the module does not exist in the station option, enter 0. Additional function * Contains information on whether a new potential group will be opened in the station option - by replacing a darkcolored BaseUnit with a light-colored BaseUnit. * If you replace a dark-colored BaseUnit with a light-colored BaseUnit, enter 1 as additional function. * If you accept the BaseUnit from the station master, enter 0 as additional function. * The server module must be present in the station option and must not be marked as empty slot (BU cover). Distributed I/O system 180 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record 10.2.3 Control data record for an interface module Slot assignment The following table shows the possible slots for the various modules for an ET 200SP interface module: Table 10- 3 Slot assignment Modules Possible slots Comment Interface module 0 The interface module (slot 0) is not an element of the configuration control, but instead controls this. Station extension BA-Send 1 For mixed configuration with ET 200AL modules, BA-Send is always on slot 1. ET 200SP I/O module 1 - 12 for IM 155-6 PN BA 1 - 30 for IM 155-6 PN HS 1 - 32 for IM 155-6 PN ST, IM 155-6 DP HF 1 - 64 for IM 155-5 PN HF 1 - 13 for IM 155-6 PN BA 1 - 31 for IM 155-6 PN HS 1 - 33 for IM 155-6 PN ST, IM 155-6 DP HF 1 - 65 for IM 155-5 PN HF Server module ET 200AL I/O module 34 - 49 for IM 155-6 DP HF Downstream from the interface module The server module completes the configuration of the ET 200SP station after the last I/O module. For mixed configuration with ET 200AL modules 66 - 81 for IM 155-6 PN ST, IM 155-6 PN HF Simplified control data record (V1) For the configuration control of interface modules of the ET 200SP distributed I/O system, you define a control data record 196 V1.0, which includes a slot assignment. The maximum slot of the configuration corresponds to the slot of the server module or ET 200AL I/O module (in a mixed ET 200SP / ET 200AL configuration). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 181 Configuration control (option handling) 10.2 Creating the control data record The table below shows the structure of a control data record with explanations of the individual elements. Table 10- 4 Structure of the simplified control data record V1.0 Byte Element Code Explanation 0 Block length 4 + maximum slot Header 1 Block ID 196 2 Version 1 3 Version 0 4 Slot 1 of the station master Slot assignment in the station option 5 Slot 2 of the station master Slot assignment in the station option : : : 4 + (slot server module - 1) Server module slot Server module slot assignment in the station option* Control element ET 200SP Contains the information on which ET 200SP module is inserted in which slot. The value that you need to enter in the corresponding byte depends on the following rule: * If the module exists in the station option, enter the slot number of the module. * If the module exists as empty slot (with BU cover), enter the slot number of the module + 128. (Example: module as empty slot on slot 3: Enter 131 in the control element) * If the module does not exist in the station option, enter 0. : : : : 4 + (first slot ET 200AL - 1) First slot ET 200AL Slot assignment in the station option Control element ET 200AL : : : 4 + (last slot ET 200AL - 1) Last slot ET 200AL Slot assignment in the station option Contains information on which ET 200AL module is inserted in which slot. The value that you need to enter in the corresponding byte depends on the following rule: * If the module exists in the station option, enter the slot number of the module. * If the module does not exist in the station option, enter 0. * The server module must be present in the station option and must not be marked as empty slot (BU cover). Control data record (V2) If you change the potential groups in the station option compared to the station master, define a control data record 196 V2.0 for the ET 200SP interface module which contains a slot assignment. The maximum slot of the configuration corresponds to the slot of the server module or ET 200AL I/O module (in a mixed ET 200SP / ET 200AL configuration). Distributed I/O system 182 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record The table below shows the structure of a control data record with explanations of the individual elements. Table 10- 5 Structure of control data record 196 V2.0 Byte Element Code Explanation 0 Block length 4 + (maximum slot x 2) Header 1 Block ID 196 2 Version 2 3 Version 0 4 Slot 1 of the station master Slot assignment in the station option 5 Additional function for slot 1 6 Slot 2 of the station master 7 Additional function for slot 2 8 Slot 3 of the station master 9 Additional function for slot 3 : : 4 + ((server module Server module slot slot - 1) x 2) Slot assignment in the station option Slot assignment in the station option : Server module slot assignment in the station option* 4 + ((server module Additional function for server module slot slot - 1) x 2) + 1 Control element ET 200SP Contains the information on which ET 200SP module is inserted in which slot. The value that you need to enter in the corresponding byte depends on the following rule: * If the module exists in the station option, enter the slot number of the module. * If the module exists as empty slot (with BU cover), enter the slot number of the module + 128. (Example: module as empty slot on slot 3: Enter 131 in the control element) If the module does not exist in the station option, enter 0. Additional function * Contains information on whether a new potential group will be opened in the station option - by replacing a darkcolored BaseUnit with a light-colored BaseUnit. * If you replace a dark-colored BaseUnit with a light-colored BaseUnit, enter 1 as additional function. * If you accept the BaseUnit from the station master, enter 0 as additional function. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 183 Configuration control (option handling) 10.2 Creating the control data record Byte Element Code Explanation : : : : 4 + ((first slot ET 200AL - 1) x 2) First slot ET 200AL Slot assignment in the station option Control element ET 200AL 4 + ((first slot ET 200AL - 1) x 2) +1 Reserved Contains information on which ET 200AL module is inserted in which slot. : : : The value that you need to enter in the corresponding byte depends on the following rule: 4 + ((last slot ET 200AL - 1) x 2) Last slot ET 200AL Slot assignment in the station option 4 + ((last slot ET 200AL - 1) x 2) +1 Reserved * If the module exists in the station option, enter the slot number of the module. * If the module does not exist in the station option, enter 0. * The server module must be present in the station option and must not be marked as empty slot (BU cover). Note If a BU cover or no I/O module is plugged on a light-colored BaseUnit, you should enter 1 in the additional function for the slot. The function "Group diagnostics: Missing supply voltage L+" requires proper assignment of the slots to a shared supply voltage L+ (potential group). All light-colored BaseUnits must be known to the interface module. By entering 1 in the additional function, you make a lightcolored BaseUnit known to the interface module, even if an I/O module is not inserted. Combination of configuration control and shared device (for PROFINET) The configuration control function in a shared device is therefore only for the I/O modules of the IO controller to which the interface module has subscribed. I/O modules that are assigned to no controller or a different controller behave like a station without activated configuration control. You cannot make any change to the slot assignment for modules that are assigned to another IO controller or are not assigned to an IO controller (shared device on module level). The CPU assumes a one-to-one assignment for the modules. If additional IO controllers subscribe to a module intended for configuration control (shared device on submodule level), only one-to-one assignment is permitted for this module. It is not possible to deselect such a module using the control data record (code 0 for this slot in the control data record). This means the combination of "Configuration control" and "Shared device on submodule level" is only possible to a limited extent. Please note that all modules affected by the configuration control including all assigned submodules are reset when you change the module assignment. Submodules that are assigned to a second IO controller are affected as well. Distributed I/O system 184 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record 10.2.4 Feedback data record for interface modules Operating principle The feedback data record informs you about the accuracy of the module assignment and gives you the option of detecting assignment errors in the control data record. The feedback data record is mapped via a separate data record 197 V2.0. The feedback data record exists only with configured configuration control. Slot assignment The feedback data record refers to the configured station configuration and always includes the maximum configuration limits. The maximum configuration limits comprise 13/49/81 slots depending on the interface module in use. Partial reading of the feedback data record is possible. The following table shows the slot assignment of the modules: Table 10- 6 Slot assignment Modules Possible slots Comment Station extension BA-Send 1 For mixed configuration with ET 200AL modules, BA-Send is always on slot 1. ET 200SP I/O module 1 - 12 for IM 155-6 PN BA 1 - 30 for IM 155-6 PN HS 1 - 32 for IM 155-6 PN ST, IM 155-6 DP HF 1 - 64 for IM 155-5 PN HF 1 - 13 for IM 155-6 PN BA 1 - 31 for IM 155-6 PN HS 1 - 33 for IM 155-6 PN ST, IM 155-6 DP HF 1 - 65 for IM 155-5 PN HF Server module ET 200AL I/O module 34 - 49 for IM 155-6 DP HF Downstream from the interface module The server module completes the configuration of the ET 200SP station after the last I/O module. For mixed configuration with ET 200AL modules 66 - 81 for IM 155-6 PN ST, IM 155-6 PN HF Distributed I/O system System Manual, 02/2018, A5E03576849-AH 185 Configuration control (option handling) 10.2 Creating the control data record Feedback data record Table 10- 7 Feedback data record Byte Element Code Explanation 0 Block length 4 + (number of slots x 2) Header 1 Block ID 197 2 Version 2 3 0 4 Slot 1 status 0/1 Status = 1: 5 Reserved 0 * 6 Slot 2 status 0/1 7 Reserved 0 : : : 4 + ((max. slot - 1) x 2) Max. slot status 0/1 4 + ((max. slot - 1) x 2) + 1 Reserved 0 Module from station master is inserted in the station option Slot is marked as not available in the control data record Status = 0: * * Module pulled * Incorrect module is inserted in the station option* * Not possible if the slot is marked as not available. Note The data in the feedback data record is always mapped for all modules. In a shared device configuration, it is therefore irrelevant which IO controller the respective modules are assigned to. As long as no control data record has been sent, a one-to-one module assignment is assumed for the compilation of data record 197 (station master station option). Distributed I/O system 186 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.2 Creating the control data record Error messages In case of error, the RDREC instruction returns the following error messages via the STATUS block parameter while reading the feedback data record: Table 10- 8 Error messages Error code Meaning 80B1H Invalid length; the length information in data record 197 is not correct. 80B5H Configuration control not configured 80B8H Parameter error The following events cause a parameter error: * 10.2.5 Incorrect block ID in the header (not equal to 197) * Invalid version identifier in the header * A reserved bit has been set * The same slot in the station option has been assigned to more than one slot in the station master Data records and functions Supported data records and functions The table below shows a comparison of the supported data records and functions depending on the CPU/interface module used. CPU... Supported data records and functions Interface module (IM...) 1510SP-1 PN 1512SP-1 PN 155-6 PN 1510SP F-1 PN 1512SP F-1 PN HS 155-6 PN HF 155-6 PN ST 155-6 PN BA 155-6 DP HF Control data record (V2) Simplified control data record (V1) -- -- -- Read back control data record * Read feedback data record -- -- * You can read back the control data record with the RDREC instruction. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 187 Configuration control (option handling) 10.3 Transferring control data record in the startup program of the CPU 10.3 Transferring control data record in the startup program of the CPU Required steps Transfer the created control data record 196 to the CPU/the interface module using the instruction WRREC (Write data record) instruction. Parameters of the instruction WRREC Below, you will find explanations of individual parameters of the WRREC instruction which you must supply with specific values in the configuration control context. You can find additional information on the WRREC instruction in the STEP 7 online help. ID Hardware identifier * Use the HW identifier of the CPU for the configuration control for centrally arranged modules. If you have selected the CPU in the network view or device view, the HW identifier is available in the System constants tab of the Inspector window. Use the value of the system constant "Local~Configuration". * Use the HW identifier of the interface module for the configuration control for distributed I/O. If you have selected the interface module in the network view or device view, the HW identifier is available in the System constants tab of the Inspector window. Use the value of the system constant "~Head". INDEX Data record number: 196 (decimal) RECORD Control data record to be transferred. See the section Creating the control data record (Page 177) for the structure of the control data record. Distributed I/O system 188 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.3 Transferring control data record in the startup program of the CPU Error messages In case of error, the instruction WRREC returns the following error messages via the STATUS block parameter: Table 10- 9 Error messages Error code Meaning 80B1H Invalid length; the length information in data record 196 is not correct. 80B5H Configuration control parameters not assigned. 80E2H Data record was transferred in the wrong OB context. The data record must be transferred in the startup program. 80B8H Parameter error A parameter error is caused by: * Incorrect block ID in the header (not equal to 196) * Invalid version identifier in the header * A reserved bit was set * A station master slot was assigned an invalid slot in the station option * Multiple slots in the station master are assigned to the same slot in the station option * For shared device on submodule level: Violation of defined restrictions Selection of the station option in the user program In order for the CPU to know which station option you want to operate, you must set up a selection option between the various control data records in the user program. You can implement the selection, for example, via an Int tag which references an array element. Note that the tag for selecting the control data record must be located in the retentive memory area. If the tag is not retentive it will be initialized during the startup of the CPU and thus be unavailable for selection of the station option. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 189 Configuration control (option handling) 10.3 Transferring control data record in the startup program of the CPU Special aspects relating to the transfer of the control data record to the CPU If you have enabled configuration control, the CPU is not ready for operation without a control data record. The CPU returns from startup to STOP if a valid control data record is not transferred in the startup OB. The central I/O is not initialized in this case. The cause for the STOP mode is entered in the diagnostics buffer. Note If an incorrect control data record is transferred to the CPU in the startup OB, the startup of the CPU may be prevented. In this case, perform a reset to factory settings of the CPU and then transfer a correct control data record. The CPU processes the WRREC instruction for transfer of the control data record asynchronously. For this reason, you must call WRREC in the startup OB repeatedly in a loop until the output parameters "BUSY" or "DONE" indicate that the data record has been transferred. - Tip: To program the loop, use the SCL programming language with the REPEAT ... UNTIL instruction. REPEAT "WRREC_DB"(REQ := "start_config_control", ID := "Local~Configuration", INDEX := 196, LEN := "conf_LEN", DONE => "conf_DONE", BUSY => "conf_BUSY", RECORD := "ConfDB".ConfigControl["ConfDB".Option], //Selection of control data record ERROR => "conf_ERROR", STATUS => "conf_STATUS"); UNTIL NOT "conf_BUSY" END_REPEAT; - In the graphical programming languages, you implement the loop using instructions for program control. Distributed I/O system 190 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.3 Transferring control data record in the startup program of the CPU Example in FBD: Use the LABEL (jump label) and JMP (jump at RLO=1) instructions to program a loop. Figure 10-5 WRREC The control data record is stored retentively in the CPU. Note: - The retentivity of the control data record is independent of the retentivity settings in the STEP 7 memory area. This means that the memory area in which the control data record is configured does not have to be configured as retentive for this purpose. - If you write a control data record with modified configuration, the original data record 196 is deleted and the new data record 196 is saved retentively. The CPU will then restart with the modified configuration. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 191 Configuration control (option handling) 10.3 Transferring control data record in the startup program of the CPU Special aspects relating to the transfer of the control data record to the interface module If you have enabled configuration control, the ET 200SP station is not ready for operation without a control data record. As long as no valid control data record has been transferred, the I/O modules are considered as failed by the CPU and exhibit substitute value behavior. The interface module continues to exchange data. The control data record is stored retentively in the interface module. Note: - If there have been no changes to the configuration, you do not need to rewrite the control data record 196 during restart. - If you write a control data record with modified configuration to the interface module, it will result in a station failure in the distributed I/O system. The original data record 196 is deleted and the new data record 196 is saved retentively. The station will then restart with the modified configuration. Distributed I/O system 192 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.4 Behavior during operation 10.4 Behavior during operation Effect of discrepancy between station master and station option For the online display and for the display in the diagnostics buffer (module OK or module faulty), the station master is always used and not the differing station option. Example: A module supplies diagnostic information. This module is configured in slot 4 in the station master, but is inserted in slot 3 in the station option (missing module; see example in the next section). The online view (station master) shows a faulty module in slot 4. In the real configuration, the module in slot 3 indicates an error via an LED display. Response when modules are missing If modules are entered as not present in the control data record, the automation system behaves as follows: Modules designated as not present in the control data record do not supply diagnostics and their status is always OK. The value status is OK. Direct write access to the outputs that are not present or write access to the process image of the outputs that are not present: Remains without effect; no access error is signaled. Direct read access to the inputs that are not present or read access to the process image of the inputs that are not present: Value "0" is supplied; no access error is signaled. Write data record to module that is not present: Remains without effect; no error is signaled. Read data record from module that is not present: An error is signaled because a valid data record cannot be returned. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 193 Configuration control (option handling) 10.5 Examples of configuration control 10.5 Examples of configuration control A station master consisting of an interface module, three I/O modules and the server module is configured in STEP 7 in the following section. Four station options are derived from the station master with the configuration control: Station option 1 with module that is not present Station option 2 with modified order of modules Station option 3 with empty slot Station option 4: Opening a new potential group Distributed I/O system 194 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.5 Examples of configuration control Station option 1 with module that is not present The module that is located in slot 3 in the station master is not present in the station option 1. Slot 3 must be designated in the control data record accordingly with 0 (= not present). The server module is located in slot 3 in the station option. Figure 10-6 Example: Hardware configuration of station option 1 with the associated control data record in STEP 7 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 195 Configuration control (option handling) 10.5 Examples of configuration control Station option 2 with modified order of modules The order of the modules at slots 2 and 3 is interchanged. Figure 10-7 Example: Hardware configuration of station option 2 with the associated control data record in STEP 7 Distributed I/O system 196 System Manual, 02/2018, A5E03576849-AH Configuration control (option handling) 10.5 Examples of configuration control Station option 3 with empty slot The module that is located in slot 3 in the station master occupies an empty slot with BU cover in the station option. Enter the value 130 in slot 3 in the control data record. Figure 10-8 Example: Hardware configuration of station option 3 with the associated control data record in STEP 7 Distributed I/O system System Manual, 02/2018, A5E03576849-AH 197 Configuration control (option handling) 10.5 Examples of configuration control Station option 4: Opening a new potential group A new potential group is opened at slot 3 of station option 4. Compared to the station master, a dark-colored BaseUnit is replaced by a light-colored BaseUnit. Enter the value 1 as additional function. Figure 10-9 Example: Hardware configuration of station option 4 with the associated control data record in STEP 7 Distributed I/O system 198 System Manual, 02/2018, A5E03576849-AH Commissioning 11.1 11 Overview Introduction This section includes information on the following topics: Commissioning the ET 200SP distributed I/O system on the PROFINET IO Commissioning the ET 200SP distributed I/O system on the PROFIBUS DP Startup of the ET 200SP distributed I/O system with empty slots Removing/inserting the SIMATIC memory card Operating modes of the CPU CPU memory reset Reassigning parameters during operation Identification and maintenance data Commissioning requirements Note Performing tests You must ensure the safety of your plant. You therefore need to run a complete functional test and make the necessary safety checks before the final commissioning of a plant. Also allow for any possible foreseeable errors in the tests. This avoids endangering persons or equipment during operation. PRONETA With SIEMENS PRONETA (PROFINET network analysis), you analyze the system network during commissioning. PRONETA features two core functions: The topology overview independently scans PROFINET and all connected components. The IO check is a fast test of the wiring and the module configuration of a system. You can find SIEMENS PRONETA on the Internet (http://support.automation.siemens.com/WW/view/en/67460624). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 199 Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO SIMATIC Automation Tool You can use the SIMATIC Automation Tool to perform commissioning and maintenance activities simultaneously on various SIMATIC S7 stations as a bulk operation independent of the TIA Portal. General function overview: Network browsing and creation of a table showing the accessible devices in the network. Flashing of device LEDs or HMI display to locate a device Loading addresses (IP, subnet, gateway) into a device Loading the PROFINET name (station name) into a device name Placing a CPU in RUN or STOP mode Setting the time in a CPU to the current time of your programming device/PC Downloading a new program to a CPU or an HMI device Downloading from CPU, downloading to CPU or deleting recipe data from a CPU Downloading from CPU or deleting data log data from a CPU Backup/restore of data from/to a backup file for CPUs and HMI devices Downloading service data from a CPU Reading the diagnostics buffer of a CPU General reset of a CPU's memory Resetting devices to factory settings Downloading a firmware update to a device ... You can find the SIMATIC Automation Tool on the Internet (https://support.industry.siemens.com/cs/ww/de/view/98161300). 11.2 Commissioning the ET 200SP for PROFINET IO Requirements The CPU/interface module is in the "Factory settings" status or has been reset to factory settings (see section Interface module (http://support.automation.siemens.com/WW/view/en/55683316/133300)). For CPU: The SIMATIC memory card is as delivered or has been formatted. Distributed I/O system 200 System Manual, 02/2018, A5E03576849-AH Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO 11.2.1 ET 200SP CPU as an IO controller Configuration example To use the ET 200SP distributed I/O system as an IO controller, you require the CPU 151xSP-1 PN. Figure 11-1 ET 200SP CPU as an IO controller Commissioning procedure To commission the ET 200SP distributed I/O system CPU as an IO controller for PROFINET IO, we recommend the following procedure: Table 11- 1 Step Procedure for commissioning the ET 200SP CPU as an IO controller for PROFINET IO Procedure See ... 1 Installing ET 200SP Section Installation (Page 64) 2 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFINET IO * Sensors and actuators 3 Inserting a SIMATIC memory card in the IO controller Section Removing/inserting a SIMATIC memory card on the CPU (Page 213) 4 Configuring the IO controller1 Section Configuring (Page 134) 5 Checking the protective measures - Distributed I/O system System Manual, 02/2018, A5E03576849-AH 201 Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO 1 Step Procedure See ... 6 Switching on supply voltages for the IO controller CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 7 Switching on supply voltages for IO devices Documentation of the IO device 8 Downloading the configuration to the IO controller STEP 7 online help 9 Switching IO controller to RUN mode CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 10 Checking LEDs CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 11 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. See section Test functions and eliminating problems (Page 273) The IO devices are configured with the IO controller. Distributed I/O system 202 System Manual, 02/2018, A5E03576849-AH Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO 11.2.2 ET 200SP CPU as an I-device Configuration example You need the CPU 151xSP-1 PN to use the ET 200SP distributed I/O system as an I-device. Figure 11-2 ET 200SP CPU as an I-device Distributed I/O system System Manual, 02/2018, A5E03576849-AH 203 Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO Commissioning procedure For commissioning of the ET 200SP distributed I/O system as an I-device on the PROFINET IO, we recommend the following procedure: Table 11- 2 Procedure for commissioning the ET 200SP as an I-device on the PROFINET IO Step Procedure 1 Installing ET 200SP Section Installation (Page 64) 2 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFINET IO * Sensors and actuators See ... 3 Inserting a SIMATIC memory card in the I-device Section Removing/inserting a SIMATIC memory card on the CPU (Page 213) 4 Configuring the I-device Section Configuring (Page 134) 5 Checking the protective measures - 6 Switching on supply voltages for the IO controller Documentation of the IO controller 7 Switching on supply voltages for I-device and IO devices CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual and documentation of the IO devices 8 Download configuration to the I-device STEP 7 online help 9 Switching IO controller and I-device to RUN mode Documentation of the IO controller and CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 10 Checking LEDs CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 11 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. See section Test functions and eliminating problems (Page 273) Distributed I/O system 204 System Manual, 02/2018, A5E03576849-AH Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO 11.2.3 ET 200SP as an IO device Configuration example To use the ET 200SP distributed I/O system as an IO device, you need the IM 155-6 PNxx interface module. Figure 11-3 ET 200SP as an IO device Commissioning procedure For commissioning of the ET 200SP distributed I/O system as an IO device on the PROFINET IO, we recommend the following procedure: Table 11- 3 Procedure for commissioning the ET 200SP as an IO device for PROFINET IO Step Procedure See ... 1 Installing ET 200SP Section Installation (Page 64) 2 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFINET IO * Sensors and actuators 4 Configuring IO controller Documentation of the IO controller 5 Checking the protective measures - 6 Switching on supply voltages for the IO controller Documentation of the IO controller 7 Switching on supply voltages for IO devices Interface module (http://support.automation.siemens .com/WW/view/en/55683316/1333 00) Manual 8 Downloading the configuration to the IO controller STEP 7 online help 9 Switching IO controller to RUN mode Documentation of the IO controller Distributed I/O system System Manual, 02/2018, A5E03576849-AH 205 Commissioning 11.2 Commissioning the ET 200SP for PROFINET IO Step Procedure See ... 10 Checking LEDs Interface module (http://support.automation.siemens .com/WW/view/en/55683316/1333 00) Manual 11 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. Refer to section Test functions and eliminating problems (Page 273) Distributed I/O system 206 System Manual, 02/2018, A5E03576849-AH Commissioning 11.3 Commissioning the ET 200SP on PROFIBUS DP 11.3 Commissioning the ET 200SP on PROFIBUS DP Requirements The CPU/interface module is in the "Factory settings" status or has been reset to factory settings (see section Interface module (http://support.automation.siemens.com/WW/view/en/55683316/133300)). For CPU: The SIMATIC memory card is as delivered or has been formatted. 11.3.1 ET 200SP as a DP master Configuration example To use the ET 200SP distributed I/O system as a DP master, you need the CPU 151xSP-1 PN and the CM DP communication module. Figure 11-4 ET 200SP as a DP master Distributed I/O system System Manual, 02/2018, A5E03576849-AH 207 Commissioning 11.3 Commissioning the ET 200SP on PROFIBUS DP Commissioning procedure To commission the ET 200SP distributed I/O system as a DP master on PROFIBUS DP, we recommend the following procedure: Table 11- 4 Procedure for commissioning the ET 200SP as a DP master on the PROFIBUS DP Step Procedure See ... 1 Installing ET 200SP (with CPU and CM DP) Section Installation (Page 64) 2 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFIBUS DP * Sensors and actuators 3 Inserting a SIMATIC memory card in the DP master (CPU) Section Removing/inserting a SIMATIC memory card on the CPU (Page 213) 4 Configuring DP master (including PROFIBUS address) CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) and CM DP manual 5 Switching on supply voltages for DP master CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 6 Switching on supply voltages for DP slaves Documentation of the DP slave 7 Download configuration to the DP master STEP 7 online help 8 Switching DP master to RUN CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 9 Checking LEDs CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 10 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. See section Test functions and eliminating problems (Page 273) Distributed I/O system 208 System Manual, 02/2018, A5E03576849-AH Commissioning 11.3 Commissioning the ET 200SP on PROFIBUS DP 11.3.2 ET 200SP as I-slave Configuration example To use the ET 200SP distributed I/O system as I-slave, you need the CPU 151xSP-1 PN and the CM DP communication module. Figure 11-5 ET 200SP as I-slave Distributed I/O system System Manual, 02/2018, A5E03576849-AH 209 Commissioning 11.3 Commissioning the ET 200SP on PROFIBUS DP Commissioning procedure For commissioning of the ET 200SP distributed I/O system as an I-slave on the PROFIBUS DP, we recommend the following procedure: Table 11- 5 Procedure for commissioning the ET 200SP as an I-slave for PROFIBUS DP Step Procedure See ... 1 Installing ET 200SP (with CPU and CM DP) Section Installation (Page 64) 2 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFIBUS DP * Sensors and actuators 3 Configuring DP master (including PROFIBUS address) Documentation of the DP master 4 Inserting a SIMATIC memory card in the I-slave (CPU) Section Removing/inserting a SIMATIC memory card on the CPU (Page 213) 5 Configuring I-slave (including PROFIBUS address) CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) and CM DP manual 6 Switching on supply voltages for DP master Documentation of the DP master 7 Switching on supply voltages for I-slaves CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 8 Loading configuration in the DP master and I-slaves STEP 7 online help 9 Switching DP master and I-slaves to RUN Documentation of the DP master and CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 10 Checking LEDs CPU 15xxSP-1 PN (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) manual 11 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. See the Test functions and fault resolution (http://support.automation.siemens .com/WW/view/en/90466439/1333 00) section Distributed I/O system 210 System Manual, 02/2018, A5E03576849-AH Commissioning 11.3 Commissioning the ET 200SP on PROFIBUS DP 11.3.3 ET 200SP as a DP slave Configuration example To use the ET 200SP distributed I/O system as a DP slave, you need the IM 155-6 DP HF. Figure 11-6 ET 200SP as a DP slave Commissioning procedure To commission the ET 200SP distributed I/O system as a DP slave on PROFIBUS DP, we recommend the following procedure: Table 11- 6 Procedure for commissioning the ET 200SP as a DP master for PROFIBUS DP Step Procedure See ... 1 Installing ET 200SP (with IM 155-6 DP HF) Section Installation (Page 64) 2 Setting the PROFIBUS address on the interface module Section Interface module (http://support.automation.siemens .com/WW/view/en/55683316/1333 00) 3 Connecting ET 200SP Section Wiring (Page 87) * Supply voltages * PROFIBUS DP * Sensors and actuators 4 Configuring DP master (including PROFIBUS address) Documentation of the DP master 5 Switching on supply voltages for DP master Documentation of the DP master 6 Switching on supply voltages for DP slaves Interface module (http://support.automation.siemens .com/WW/view/en/55683316/1333 00) Manual 7 Download configuration to the DP master STEP 7 online help Distributed I/O system System Manual, 02/2018, A5E03576849-AH 211 Commissioning 11.4 Startup of the ET 200SP with empty slots 11.4 Step Procedure See ... 8 Switching DP master to RUN Documentation of the DP master 9 Checking LEDs Interface module (http://support.automation.siemens .com/WW/view/en/55683316/1333 00) Manual 10 Testing inputs and outputs The following functions are helpful: Monitoring and modifying tags, testing with program status, forcing, controlling the outputs. Refer to section Test functions and eliminating problems (Page 273) Startup of the ET 200SP with empty slots Procedure You can configure the ET 200SP distributed I/O system with any number of empty slots. To build the ET 200SP distributed I/O system with any number of empty slots, follow these steps: 1. Cover all empty slots with BU covers. 2. Finish the configuration with a server module. Special consideration: A "Module missing in slot x" diagnostic message is generated by the CPU/interface module for empty slots in which I/O modules are configured. Distributed I/O system 212 System Manual, 02/2018, A5E03576849-AH Commissioning 11.5 Removing/inserting a SIMATIC memory card on the CPU 11.5 Removing/inserting a SIMATIC memory card on the CPU Requirement The CPU only supports pre-formatted SIMATIC memory cards. If necessary, delete all previously stored data before using the SIMATIC memory card. Additional information about deleting the contents of the SIMATIC memory card can be found in the section, SIMATIC memory card - overview (Page 240). In order to work with the SIMATIC memory card, first ensure that the SIMATIC memory card is not write-protected. If it is, move the slider out of the lock position. Inserting the SIMATIC memory card To insert a SIMATIC memory card, follow these steps: 1. Ensure that the CPU is either switched off or in STOP mode. 2. Insert the SIMATIC memory card, as depicted on the CPU, into the slot for the SIMATIC memory card. Figure 11-7 Slot for the SIMATIC memory card 3. Insert the SIMATIC memory card with light pressure into the CPU, until the SIMATIC memory card latches. Removal of the SIMATIC memory card To remove a SIMATIC memory card, follow these steps: 1. Switch the CPU to STOP mode. 2. Press the SIMATIC memory card into the CPU with light pressure. After audible unlatching of the SIMATIC memory card, remove it. Only remove the SIMATIC memory card in POWER OFF or STOP mode of the CPU. Ensure that no writing functions (online functions with the programming device, e.g. loading/deleting a block, test functions) are active in STOP mode or were active before POWER OFF. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 213 Commissioning 11.6 Operating modes of the CPU Reactions after removing/inserting the SIMATIC memory card Inserting and removing the SIMATIC memory card in STOP, STARTUP or RUN mode triggers a re-evaluation of the SIMATIC memory card. The CPU hereby compares the content of the configuration on the SIMATIC memory card with the backed-up retentive data. If the backed-up retentive data matches the data of the configuration on the SIMATIC memory card, the retentive data is retained. If the data differs, the CPU automatically performs a memory reset (which means the retentive data is deleted) and then goes to STOP. The CPU evaluates the SIMATIC memory card, and this is indicated by the RUN/STOP LED flashing. Reference Additional information on the SIMATIC memory card can be found in the SIMATIC memory card (Page 240) section. 11.6 Operating modes of the CPU Introduction Operating modes describe the status of the CPU. The following operating modes are possible using the mode selector: STARTUP RUN STOP In these operating modes, the CPU can communicate, for example, via the PROFINET interface. The status LEDs on the front of the CPU indicate the current operating mode. 11.6.1 STARTUP mode Function Before the CPU starts to execute the cyclic user program, a startup program is executed. By suitably programming startup OBs, you can specify initialization tags for your cyclic program in the startup program. You have the option of programming no, one or several startup OBs. Distributed I/O system 214 System Manual, 02/2018, A5E03576849-AH Commissioning 11.6 Operating modes of the CPU Special features during startup Note the following points regarding the STARTUP mode: All outputs are disabled or react according to the parameter settings for the particular I/O module: They provide a substitute value as set in the parameters or retain the last value output and bring the controlled process to a safe operational status. The process image is initialized. The process image is not updated. In order to read the current state from inputs during STARTUP, you can access inputs directly via I/O access. In order to initialize outputs during STARTUP, values can be written via the process image or via direct I/O access. The values are output at the outputs during the transition to the RUN mode. The CPU always starts up in warm restart mode. - The non-retentive bit memory, timers and counters are initialized. - The non-retentive tags in data blocks are initialized. During startup, cycle time monitoring is not yet running The startup OBs are executed in the order of the startup OB numbers. All startup OBs that you have programmed are executed, regardless of the selected startup mode. The following OBs can be started during startup, if a corresponding event occurs: - OB 82: Diagnostics interrupt - OB 83: Pull/plug interrupt for modules - OB 86: Rack error - OB 121: Programming error (only for global error handling) - OB 122: I/O access error (only for global error handling) You can find a description of how to use global and local error handling in the STEP 7 online help. No other OBs can be started until after the transition to RUN mode. Response when expected and actual configurations do not match The configuration downloaded to the CPU represents the expected configuration. The actual configuration is the actual configuration of the ET 200SP distributed I/O system. If the expected configuration and the actual configuration do not match, the setting of the "Comparison preset to actual configuration" parameter determines the reaction of the CPU (see section Operating mode transitions (Page 218)). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 215 Commissioning 11.6 Operating modes of the CPU Canceling a startup If errors occur during startup, the CPU cancels the startup and returns to STOP mode. The CPU does not execute a startup or cancels a startup under the following conditions: If no SIMATIC memory card is inserted or an invalid SIMATIC memory card is inserted. If no hardware configuration has been downloaded. Setting the startup behavior To set the startup behavior, follow these steps: 1. In the device view of the STEP 7 hardware network editor, select the CPU. 2. In the properties under "General" select the "Startup" area. Figure 11-8 Setting the startup behavior Sets the startup type after POWER ON Defines the startup behavior when a module in a slot does not correspond to the config- ured module. You can set this parameter centrally, on the CPU or for each module. When you change the setting for a module, the setting made centrally for this module no longer applies. * Startup CPU only if compatible: In this setting a module on a configured slot has to be compatible with the configured module. Compatible means that the module matches in terms of the number of inputs and outputs and with respect to its electrical and functional properties. * Startup CPU even if mismatch: With this setting the CPU starts up regardless of the type of module plugged in. Specifies a maximum period (default: 60000 ms) in which the I/O must be ready for operation. The CPU changes to RUN. If the central and distributed I/O is not ready for operation within the configuration time, the startup characteristics of the CPU depends on the setting of the "Comparison preset to actual configuration" parameter. Distributed I/O system 216 System Manual, 02/2018, A5E03576849-AH Commissioning 11.6 Operating modes of the CPU Example for the "Comparison preset to actual configuration" parameter "Startup CPU only if compatible": The input module DI 16x24VDC ST with 16 digital inputs is a compatible replacement for the input module DI 8x24VDC ST with 8 digital inputs, because the pin assignment and all the electrical and functional properties match. "Startup CPU even if mismatch": Instead of a configured digital input module, you insert an analog output module or no module is present in this slot and thus in all subsequent slots. Although the configured inputs cannot be accessed, the CPU starts up. Note that the user program cannot function correctly in this case and take the appropriate measures. 11.6.2 STOP mode Function The CPU does not execute the user program in STOP mode. All outputs are disabled or react according to the parameter settings for the particular I/O module: They provide a substitute value as set in the parameters or retain the last value output keeping the controlled process in a safe operating status. In STOP mode, the motor starter responds according to how it was parameterized for the CPU STOP state. The CPU STOP state can be circumvented with the manual local control (Local Control) function. If the CPU is switched off, a motor can be switched on in the motor starter's commissioning mode. You will find additional information in the Motor starter (https://support.industry.siemens.com/cs/ww/en/view/109479973) manual. 11.6.3 RUN mode Function In "RUN" mode the cyclic, time-driven, and interrupt-driven program is executed. Addresses that are in the "Automatic Update" process image are automatically updated in each program cycle. See also the section Process images and process image partitions (Page 142). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 217 Commissioning 11.6 Operating modes of the CPU Execution of the user program Once the CPU has read the inputs, the cyclic program is executed from the first instruction to the last instruction. If you have configured a minimum cycle time, the CPU will not end the cycle until this minimum cycle time is finished even if the user program is completed sooner. A cycle monitoring time is set to ensure that the cyclic program is completed within a specified time. You can change the cycle monitoring time to suit your requirements. If the cyclic program has not finished running within this time, the system responds with a time error. Further events such as hardware interrupts and diagnostics interrupts can interrupt the cyclic program flow and prolong the cycle time. Reference Further information about cycle and response times is available in the Function Manual Cycle and response times (http://support.automation.siemens.com/WW/view/en/59193558). 11.6.4 Operating mode transitions Operating modes and operating mode transitions The following figure shows the operating modes and the operating mode transitions: Figure 11-9 Operating modes and operating mode transitions Distributed I/O system 218 System Manual, 02/2018, A5E03576849-AH Commissioning 11.6 Operating modes of the CPU The table below shows the effects of the operating mode transitions: Table 11- 7 Operating mode transitions No. Operating mode transitions POWER ON STARTUP * * The CPU clears the non-retentive memory, and resets the content of non-retentive DBs to the start The hardware configuration and program blocks are values of the load memory. Reconsistent. tentive memory and retentive DB Startup type "Warm restart - RUN" is set. contents are retained. Or * POWER ON STOP Effects After switching on, the CPU switches to "STARTUP" mode if: Startup type "Warm restart mode before POWER OFF" is set and the CPU was in RUN mode before POWER OFF. The 500 newest entries in the diagnostics buffer are retained. The CPU clears the non-retentive memory, and resets the content The hardware configuration and program blocks are of non-retentive DBs to the start inconsistent. values of the load memory. Retentive memory and retentive DB Or contents are retained. The "No restart" startup type is set. The 500 newest entries in the Or diagnostics buffer are retained. After switching on, the CPU goes to "STOP" mode if: * * * Startup type "Warm restart mode before POWER OFF" is set and the CPU was in STOP mode before POWER OFF. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 219 Commissioning 11.6 Operating modes of the CPU No. Operating mode transitions STOP STARTUP * The CPU clears the non-retentive memory, and resets the content The hardware configuration and program blocks are of non-retentive DBs to the start consistent. values of the load memory. ReYou set the CPU to "RUN" mode via the programtentive memory and retentive DB ming device and the mode switch in is RUN contents are retained. position. The 500 newest entries in the diagnostics buffer are retained. Or * You set the mode switch from STOP to RUN. * STARTUP STOP STARTUP RUN RUN STOP Effects The CPU switches to "STARTUP" mode if: The CPU returns to the "STOP" mode in the following cases of "STARTUP": * The CPU detects an error during startup. * You set the CPU to "STOP" via the programming device or mode switch. * The CPU executes a STOP command in the Startup OB. These operating mode transitions have no effect on data. The CPU goes to the "RUN" mode in the following cases of "START-UP": * The CPU has initialized the PLC tags. * The CPU has executed the startup blocks successfully. The CPU returns to the "STOP" mode in the following cases of "RUN": * The CPU detects an error which prevents further work. * The CPU executes a STOP command in the user program. * You set the CPU to "STOP" via the programming device or mode switch. Distributed I/O system 220 System Manual, 02/2018, A5E03576849-AH Commissioning 11.7 CPU memory reset 11.7 CPU memory reset Basics of a memory reset A memory reset on the CPU is possible only in the STOP mode. When memory is reset, the CPU is changed to a so-called "initial status". This means that: An existing online connection between your programming device/PC and the CPU is terminated. The content of the work memory and the retentive and non-retentive data (applies only to manual memory reset by the user) are deleted. The diagnostics buffer, time of day, IP address and the device name are retained. Subsequently the CPU is initialized with the loaded project data (hardware configuration, code and data blocks, force jobs). The CPU copies this data from the load memory to the work memory. Result: - If you set an IP address in the hardware configuration ("Set IP address in the project" option) and a SIMATIC memory card with the project is in the CPU, this IP address is valid after the memory reset. - Data blocks no longer have current values but rather their configured start values. - Force jobs remain active. How can I tell if the CPU is performing a memory reset? The RUN/STOP LED flashes yellow at 2 Hz. After completion the CPU goes into STOP mode, and the RUN/STOP LED is switched on (permanently lit yellow). Result after memory reset The following table provides an overview of the contents of the memory objects after memory reset. Table 11- 8 Result after memory reset Memory object Content Actual values of the data blocks, instance data blocks Initialized Bit memory, timers and counters Initialized Retentive tags from technology objects (for example, adjustment values of absolute encoders)* Retained Diagnostics buffer entries Retained IP address Retained Device name Retained Counter readings of the runtime meters Retained Time of day Retained * The retentive tags from technology objects are retained but the content of specific tags is partly reinitialized. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 221 Commissioning 11.7 CPU memory reset 11.7.1 Automatic memory reset Possible cause of an automatic memory reset The CPU executes an automatic memory reset if an error occurs that prevents normal further processing. Causes for such errors can be: User program is too large, and cannot be completely loaded into work memory. The project data on the SIMATIC memory card is corrupt, for example, because a file was deleted. If you remove or insert the SIMATIC memory card and the backed-up retentive data differs in structure from that of the configuration on the SIMATIC memory card. 11.7.2 Manual memory reset Reason for a manual memory reset CPU memory reset is required to reset the CPU to its "original state". CPU memory reset There are two options for performing a CPU memory reset: Using the mode selector Using STEP 7 Procedure using the mode selector Note Memory reset Reset to factory settings The operation described below also reflects the procedure for resetting to factory settings: * Selector operation with inserted SIMATIC memory card: CPU executes a memory reset * Selector operation without inserted SIMATIC memory card: CPU executes reset to factory settings Distributed I/O system 222 System Manual, 02/2018, A5E03576849-AH Commissioning 11.7 CPU memory reset To reset the CPU memory using the mode selector, proceed as follows: 1. Set the mode selector to the STOP position. Result: The RUN/STOP LED lights up yellow. 2. Set the mode selector to the MRES position. Hold the selector in this position until the RUN/STOP LED lights up for the 2nd time and remains continuously lit (this takes three seconds). After this, release the switch. 3. Within the next three seconds, switch the mode selector back to the MRES position, and then back to STOP again. Result: The CPU executes memory reset. For information on resetting the CPU to factory settings, refer to the section Resetting the CPU to factory settings (Page 264). Procedure using STEP 7 For a memory reset of the CPU using STEP 7 proceed as follows: 1. Open the "Online Tools" task card of the CPU. 2. Click the "MRES" button in the "CPU control panel" pane. 3. Click "OK" in response to the confirmation prompt. Result: The CPU switches to STOP mode and performs a memory reset. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 223 Commissioning 11.8 Reassigning parameters during operation 11.8 Reassigning parameters during operation Introduction You have the option of reassigning the parameters for the ET 200SP I/O modules during operation. Changing parameters during operation You make the parameter settings of the I/O modules using data records. Each I/O module has a separate data record. The instruction "WRREC" applies the changed parameters to the I/O module. If you are using the CPU as an I-device, you reassign the parameters of the I/O modules via the I-device. Note If you write data records from the user program to the modules of the distributed I/O, make sure that these modules actually exist and are available. You can evaluate OB83 for this purpose. After inserting a module, the CPU does not call OB83 until the module has started up and its parameters are assigned. This ensures the execution of the data record operations without errors. Note You need to transfer the new parameters with the "WRREC" instruction after a POWER OFF/POWER ON of the ET 200SP. Instruction for parameter assignment The following instruction is provided for assigning parameters to the I/O module in the user program: Instruction Application "WRREC" Transfer the modifiable parameters to the addressed ET 200SP module. Error message In the event of an error, the following return values are reported: Table 11- 9 Error message Error code Meaning 80E0H Error in header information 80E1H Parameter error Reference You will find the setup of the parameter data record in the manuals of the I/O modules (http://support.automation.siemens.com/WW/view/es/55679691/133300). Distributed I/O system 224 System Manual, 02/2018, A5E03576849-AH Commissioning 11.9 Identification and maintenance data 11.9 Identification and maintenance data 11.9.1 Reading out and entering I&M data I&M data I&M identification data is information which is stored on the module either as read-only data (I-data) or read/write data (M-data). Identification data (I&M0): Manufacturer information about the module that can only be read and is in part also printed on the housing of the module, for example, article number and serial number. Maintenance data (I&M1, 2, 3): Plant-dependent information, e.g. installation location. Maintenance data is created during configuration and written to the module. All modules of the ET 200SP distributed I/O system support identification data (I&M0 to I&M3). The I&M identification data supports you in the following activities: Checking the plant configuration Locating hardware changes in a plant Correcting errors in a plant Modules can be clearly identified online using the I&M identification data. STEP 7 allows you to read the identification I&M data (see STEP 7 online help). Note The BusAdapter and the interface module IM 155-6 PN HF support the identification data I&M0 to I&M4 (signature). Options for reading out I&M data Via the user program Via STEP 7 or HMI devices Via the CPU web server Distributed I/O system System Manual, 02/2018, A5E03576849-AH 225 Commissioning 11.9 Identification and maintenance data Procedure for reading I&M data by means of the user program You have the following options to read the modules' I&M data in the user program: using the RDREC instruction The record structure for distributed modules that are accessible via PROFINET IO/PROFIBUS DP, is described in the chapter Record structure for I&M data (Page 227). using the Get_IM_Data instruction Reference The description of the instructions can be found in the STEP 7 online help. Procedure for reading the I&M data via STEP 7 Requirements: There must be an online connection to the CPU/interface module. To read I&M data using STEP 7, follow these steps: 1. In the project tree, under "Distributed I/O" select the IO device IM 155-6 PN ST (for example). 2. Select > IO device > Online & diagnostics > Identification & Maintenance. Procedure for entering maintenance data via STEP 7 STEP 7 assigns a default module name. You can enter the following information: Plant designation (I&M1) Location identifier (I&M1) Installation date (I&M2) Additional information (I&M3) To enter maintenance data via STEP 7, follow these steps: 1. In the device view of the STEP 7 hardware network editor, select the interface module, for example. 2. In the properties under "General", select the "Identification & Maintenance" area and enter the data. During the loading of the hardware configuration, the I&M data is also loaded. Procedure for reading I&M data via the Web server The procedure is described in detail in the Web server (http://support.automation.siemens.com/WW/view/en/59193560) Function Manual. Distributed I/O system 226 System Manual, 02/2018, A5E03576849-AH Commissioning 11.9 Identification and maintenance data 11.9.2 Data record structure for I&M data Reading I&M data records (distributed via PROFINET IO) You can directly access specific identification data by selecting Read data record (RDREC instruction). You obtain the corresponding part of the identification data under the relevant data record index. The data records are structured as follows: Table 11- 10 Basic structure of data records with I&M identification data Content Length (bytes) Coding (hex) Header information BlockType 2 I&M0: 0020H I&M1: 0021H I&M2: 0022H I&M3: 0023H BlockLength 2 I&M0: 0038H I&M1: 0038H I&M2: 0012H I&M3: 0038H BlockVersionHigh 1 01 BlockVersionLow 1 00 Identification data Identification data (see table below) I&M0/index AFF0H: 54 I&M1/index AFF1H: 54 I&M2/index AFF2H: 16 I&M3/index AFF3H: 54 Table 11- 11 Data record structure for I&M identification data Identification data Access Default Explanation Identification data 0: (data record index AFF0 hex) VendorIDHigh Read (1 byte) 00H This is where the name of the manufacturer is stored (42D = SIEMENS AG). VendorIDLow Read (1 byte) 2 AH Order_ID Read (20 bytes) 6ES7155-6AU00-0BN0 Article number of the module (e.g. of the interface module) IM_SERIAL_NUMBER Read (16 bytes) - Serial number (device-specific) IM_HARDWARE_REVISION Read (2 bytes) 1 Corresponding HW version IM_SOFTWARE_REVISION Read Firmware version Provides information about the firmware version of the module * SWRevisionPrefix (1 byte) V * IM_SWRevision_Functional_ Enhancement (1 byte) 00 - FFH * IM_SWRevision_Bug_Fix (1 byte) 00 - FFH Distributed I/O system System Manual, 02/2018, A5E03576849-AH 227 Commissioning 11.9 Identification and maintenance data Identification data Access Default Explanation (1 byte) 00 - FFH IM_REVISION_COUNTER Read (2 bytes) 0000H Provides information about parameter changes on the module (not used) IM_PROFILE_ID Read (2 bytes) 0000H Generic Device IM_PROFILE_SPECIFIC_TYPE Read (2 bytes) 0005H Interface modules/BusAdapters 0003H I/O modules and motor starters 0001H CPU 0101H Provides information on the version of the identification data (0101H = Version 1.1) 000EH Provides information about the available identification data (I&M1 to I&M3) * IM_SWRevision_Internal_ Change IM_VERSION Read * IM_Version_Major (1 byte) * IM_Version_Minor (1 byte) IM_SUPPORTED Read (2 bytes) Maintenance data 1: (data record index AFF1 hex) IM_TAG_FUNCTION Read/write (32 bytes) - Enter a module identifier here that is unique plant-wide. IM_TAG_LOCATION Read/write (22 bytes) - Enter the installation location of the module here. YYYY-MM-DD HH:MM Enter the installation date of the module here. - Enter a comment describing the module. Maintenance data 2: (data record index AFF2 hex) IM_DATE Read/write (16 bytes) Maintenance data 3: (data record index AFF3 hex) IM_DESCRIPTOR Read/write (54 bytes) Reading I&M data records with data record 255 (distributed via PROFIBUS DP) The modules support standardized access to identification data via DS 255 (index 65000 to 65003). For further information on the DS 255 data structure, refer to the specifications of the Profile Guidelines Part 1: Identification & Maintenance Functions, Order No.: 3.502, Version 2.1, May 2016 Distributed I/O system 228 System Manual, 02/2018, A5E03576849-AH Commissioning 11.9 Identification and maintenance data 11.9.3 Example: Read out firmware version of the CPU with Get_IM_Data Automation task You want to check whether the modules in your automation system have the current firmware. The firmware version of the modules can be found in the I&M 0 data. The IM 0 data are the basic information of a device and contain information such as the manufacturer ID, order number, serial number and the hardware and firmware version. To read out the I&M 0 data, use the "Get_IM_Data" instruction. You read the I&M 0 data of all the modules in the user program of the CPU via "Get_IM_Data" instructions and store them in a data block. Conditions and parameters To read out the I&M data of the CPU, use the following block parameters of the "Get_IM_Data" instruction: LADDR: Enter the HW ID of the module at the block parameter "LADDR". IM_TYPE: Enter the I&M data number (e.g. "0" for I&M 0 data) at the "IM_TYPE" block parameter. DATA: Area for storing the read I&M data (for example. in a global data block). Store the I&M 0 data in an area of the data type "IM0_Data". This example shows you how to read out the I&M 0 data of an ET 200SP CPU. To read out the I&M 0 data of a different module, simply use the HW ID of the module at the parameter LADDR. Solution To read out the I&M 0 data of the CPU, follow these steps: 1. Create a global data block to store the I&M 0 data. 2. Create a structure of the data type "IM0_Data" in the global data block. You can assign any name to the structure ("imData") in this case. Figure 11-10 Example: Data block for I&M data 3. Create the "Get_IM_Data" instruction in the user program, e.g. in OB 1. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 229 Commissioning 11.9 Identification and maintenance data 4. Connect the "Get_IM_Data" instruction as follows: Figure 11-11 Example: Calling the "Get_IM_Data" instruction 5. Call the "Get_IM_Data" instruction in the user program. Result The "Get_IM_Data" instruction has stored the I&M 0 data in the data block. You can view the I&M 0 data online in STEP 7, for example, in the data block with the "Monitor all" button. The CPU in the example is a 1512SP-1 PN (6ES7512-1DK01-0AK0) with the firmware version V2.5. Figure 11-12 Example: I&M 0 data of an ET 200SP CPU Distributed I/O system 230 System Manual, 02/2018, A5E03576849-AH Commissioning 11.10 Shared commissioning of projects 11.10 Shared commissioning of projects Team Engineering In Team Engineering several users from various engineering systems work on a project at the same time and access one ET 200SP CPU. The users can edit separate parts of a master project independently of one another at the same time. The changes of the other editors are displayed in a synchronization dialog during the loading of the configuration in the CPU and synchronized automatically, if possible. Certain online functions can also be executed at the same time from several engineering systems on a shared CPU, such as: Monitoring blocks on the CPU Modifying blocks on the CPU Trace functions You can find detailed information on the topic of Team Engineering in the STEP 7 online help. 11.11 Backing up and restoring the CPU configuration 11.11.1 Overview Backup from online device You will make a number of changes to your plant over time, for example, add new devices, replace existing devices or adapt the user program. If these changes result in undesirable behavior, you can restore the plant to an earlier state. Before you load a changed configuration to the CPU, first use the option "Backup from online device" to create a complete backup of the current device status. Upload from device (software) With the option "Upload from device (software)", you load the software project data from the CPU to an existing CPU in the project. Upload device as new station If you are operating a new programming device/PC in the plant, the STEP 7 project that was used to create the plant configuration might not be available. In this case you can use the option "Upload device as new station" to load the device's data into a project in your PG/PC. Snapshot of the monitor values You can use the option "Snapshot of the monitor values" to backup the current values of the data block, in order to be able to restore the current values if necessary at a later date. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 231 Commissioning 11.11 Backing up and restoring the CPU configuration Overview of backup types The table below shows the backup of CPU data depending on the selected type of backup and its specific characteristics: Backup from online device Upload from device (software) Upload device as new station Snapshot of the monitor values Current values of all DBs (global and instance data blocks) 1) Blocks of the type OB, FC, FB and DB -- PLC tags (tag names and constant names) -- Technology objects -- Hardware configuration -- -- Actual values (bit memories, timers, counters)* -- -- -- Contents of the SIMATIC memory card -- -- -- Archives, recipes -- -- -- Entries in the diagnostics buffer -- -- -- -- -- -- -- -- -- Current time Properties of the type of backup Backup possible for fail-safe CPUs Backup can be edited Backup possible in operating mode 2) -- STOP RUN, STOP RUN, STOP RUN, STOP 1) Only the values of the tags that are set as retentive are saved. 2) Only possible in the STOP operating state and for individual fail-safe blocks. Reference You can find more information on the different backup types in the STEP 7 online help. Distributed I/O system 232 System Manual, 02/2018, A5E03576849-AH Commissioning 11.11 Backing up and restoring the CPU configuration Emergency address (emergency IP) The emergency address (emergency IP address) of a CPU was conceived for diagnostic and downloading functions, e.g. if the CPU can no longer be reached via the IP protocol due to loading of an incorrect project. You can find information on the emergency address in the following FAQ on the Internet (https://support.industry.siemens.com/cs/ww/en/view/97649773). Archiving multilingual project texts When you configure a CPU, different categories of texts come into being, e.g. Object names (names of blocks, modules, tags, etc.) Comments (for blocks, networks, watch tables, etc.) Messages and diagnostic texts Texts are provided by the system (e.g. diagnostic buffer texts) or are created during configuration (e.g. messages). In a project, texts exist in one single language or in several languages after a translation process. You can maintain project texts in all languages, which are at your disposal in the project navigator (Languages & Resources > Project Texts). The texts arising during configuration can be loaded into the CPU. The following texts containing the project data are loaded into the CPU in the chosen languages and are also used by the Web server: Diagnostic buffer texts (not editable) Module status texts (not editable) Message texts with associated text lists Tag comments and step comments for S7 GRAPH and PLC Code Viewer Comments in watch tables The following texts containing the project languages are also loaded into the CPU in the chosen languages, but are not used by the Web server: Comments in tag tables (for tags and constants) Comments in global data blocks Comments of elements in block interfaces of FBs, FCs, DBs and UDTs Network titles in data blocks that are written in ladder logic (LAD), function block diagram (FBD) or statement list (STL) Block comments Network comments Comments of LAD and FBD elements Distributed I/O system System Manual, 02/2018, A5E03576849-AH 233 Commissioning 11.12 Time synchronization The CPUs support archiving of multilingual project texts in up to three different project languages. If the project texts belonging to a specific project language nevertheless exceed the memory space reserved for them, it is not possible to load the project into the CPU. The operation is canceled with a message indicating that not enough free storage space is available. In such a case, take measures to reduce the required storage space, for example by shortening comments. Note Size of the SIMATIC memory card If the storage space needed to load projects exceeds the storage space available on the SIMATIC memory card in use, loading into the CPU is canceled with an error message. Therefore, make sure that there is enough available storage space on your SIMATIC memory card for loading projects. You will find information on reading out the storage space capacity utilization of the CPU and the SIMATIC memory card in the Structure and use of the CPU memory (https://support.industry.siemens.com/cs/de/de/view/59193101/en) function manual. You will find information on parameterization of multilingual project texts in STEP 7 in the STEP 7 online help. 11.12 Time synchronization NTP procedure All CPUs are equipped with an internal clock. The clock always shows the time-of-day with a resolution of 1 millisecond and the date including the day of the week. The time adjustment for daylight saving time is also taken into account. You can synchronize the time of the CPUs with an NTP server in NTP mode (NTP: Network Time Protocol). In NTP mode, the device sends time queries at regular intervals (in client mode) to the NTP server in the subnet (LAN). Based on the replies from the server, the most reliable and most accurate time is calculated and the time on the CPU is synchronized. The advantage of this mode is that it allows the time to be synchronized across subnets. You can configure the IP addresses of up to a maximum of four NTP servers. You address a communications processor or an HMI device, for example, as sources for time synchronization via the IP addresses. The update interval defines the interval between the time queries (in seconds). The value of the interval ranges between 10 seconds and one day. In NTP mode, it is generally UTC (Universal Time Coordinated) that is transferred; this corresponds to GMT (Greenwich Mean Time). Distributed I/O system 234 System Manual, 02/2018, A5E03576849-AH Commissioning 11.12 Time synchronization NTP server for the ET 200SP CPU You can assign an ET 200SP CPU to up to 4 NTP servers. In STEP 7 you enable the time synchronization in NTP mode. You can configure up to four NTP servers for the ET 200SP CPU in STEP 7. If you have enabled time synchronization via NTP for the CPU, then you can enter the IP addresses of up to four NTP servers in the user program. For this, use the "T_CONFIG" instruction. Enabling time synchronization via NTP server To enable the time synchronization for the ET 200SP CPU via NTP servers, follow these steps: 1. In the Inspector window, navigate in the properties of the CPU to "General" > "PROFINET interface" > Time synchronization". 2. Enable the option "Enable time synchronization via NTP server". Configuring NTP server in STEP 7 To configure one or more NTP servers for the ET 200SP CPU, follow these steps: 1. In the Inspector window, navigate in the properties of the CPU to "General" > "PROFINET interface" > Time synchronization". 2. Enter the IP addresses of up to four NTP servers at the parameters "Server 1" to "Server 4". 3. Set the interval of the time queries at the "Update interval" parameter. Set the update interval to between 10 s and 86400 s. Changing the IP addresses of the NTP servers with the "T_CONFIG" instruction Requirements: Before using the instruction you have to specify to the hardware configuration that the IP address is assigned via the user program: 1. For this purpose, open the properties of the PROFINET interface in the device view. 2. Select the following option in the "Time synchronization" dialog: Select "Enable time synchronization via NTP server" and specify the IP address of at least one NTP server. T_CONFIG instruction: You store the IP addresses for the NTP time synchronization at the CONF_DATA parameter in the system data type. Reference For additional information on time synchronization in the automation environment, refer to the following FAQ on the Internet (https://support.industry.siemens.com/cs/de/en/view/86535497). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 235 Commissioning 11.12 Time synchronization 11.12.1 Example: Configuring and changing NTP server Configuring time synchronization with your own NTP server Automation task You use your own server in your network. Your own server provides you with the following advantages: Protection against unauthorized accesses from outside Every device that you synchronize with your own NTP server uses the same time. You want to synchronize the ET 200SP CPU with this NTP server. Conditions and parameters You have your own NTP server in your network with the IP address 192.168.1.15. They are located in STEP 7 in the Inspector window in the properties of the PROFINET interface X1. Solution 1. Navigate to "Properties > General > PROFINET interface > Time synchronization > NTP mode". 2. For "Server 1" enter the IP address of the NTP server: 192.168.1.15. Figure 11-13 Example: Configuring the NTP server 3. Download the hardware configuration to the CPU. Result The ET 200SP CPU synchronizes the time with the NTP server 192.168.1.15. Distributed I/O system 236 System Manual, 02/2018, A5E03576849-AH Commissioning 11.12 Time synchronization Changing the IP address of an NTP server in the user program Automation task You change the NTP server in your network. The new NTP server has the address "192.168.1.10". You want to change the IP address of the NTP server with which your ET 200SP CPU synchronizes via the user program. The example shows how you change the IP address of the NTP server to "192.168.1.10"via the user program with the instruction "T_CONFIG". Conditions and parameters Requirements: You have enabled the option "Enable time synchronization via NTP server" for your CPU in STEP 7. You have configured the following NTP servers in STEP 7: Server 1 "192.168.1.15" To change the IP addressed for NTP servers, use the following block parameter of the "T_CONFIG" instruction: Req: A positive edge at the block parameter "Req" starts a job of the "T_CONFIG" instruction. Interface: Enter the hardware identifier of the PROFINET interface 1 of the CPU at the "Interface" block parameter. In this example, the HW ID is "64". Conf_Data: Area in which you save the IP addresses of the NTP server. Use the data type "IF_CONF_NTP" for this purpose. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 237 Commissioning 11.12 Time synchronization Solution To change the IP address of the NTP server in the user program to "192.168.1.10", follow these steps: 1. Create a global data block in the project tree under "Program blocks > Add new block". Name the global data block "NTP". 2. Create a tag of the data type "IF_CONF_NTP" in the global data block "NTP". Figure 11-14 Example: Data block with IF_CONF_NTP 3. Create a "T_CONFIG" instruction in the user program. 4. Connect the "T_CONFIG" instruction as follows. Figure 11-15 Example T_CONFIG: Changing the NTP server Distributed I/O system 238 System Manual, 02/2018, A5E03576849-AH Commissioning 11.12 Time synchronization 5. In the user program, assign the IP address 192.168.1.10 to the data type "IF_CONF_NTP": "NTP".NTP_Server.NTP_IP[1].ADDR[1] := 192; "NTP".NTP_Server.NTP_IP[1].ADDR[2] := 168; "NTP".NTP_Server.NTP_IP[1].ADDR[3] := 1; "NTP".NTP_Server.NTP_IP[1].ADDR[4] := 10; 6. You change the IP address of the NTP server by generating a positive edge for the tag "change_NTP-Server" in the user program. "NTP"."change_NTP-Server" := true; Result The ET 200SP CPU synchronizes the time with the NTP server 192.168.1.10. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 239 12 SIMATIC memory card 12.1 SIMATIC memory card - overview Introduction The CPU uses a SIMATIC memory card as a memory module. The SIMATIC memory card is a preformatted memory card compatible with the Windows file system. The memory card is available in different memory sizes and can be used for the following purposes: Transportable data carrier Program card Firmware update card Service data card If you transfer the user program to the CPU via an online connection, it is written to the SIMATIC memory card, which must be in the card slot of the CPU for this to work. You can also write the SIMATIC memory card in the PG/PC. A commercially available SD card reader is required to write / read the SIMATIC memory card with the programming device / PC. This is used to copy files directly to the SIMATIC memory card using the Windows Explorer, for example. A SIMATIC memory card is absolutely required in order to operate the CPU. Distributed I/O system 240 System Manual, 02/2018, A5E03576849-AH SIMATIC memory card 12.1 SIMATIC memory card - overview Labeling of the SIMATIC memory card Article number Serial number Production version Memory size Slider for enabling write protection: * Slider up: Not write-protected * Slider down: Write-protected Figure 12-1 Labeling of the SIMATIC memory card Folders and files on the SIMATIC memory card The following folders and files can be found on the SIMATIC memory card: Table 12- 1 Folder structure Folder Description FWUPDATE.S7S Firmware update files for CPU and I/O modules SIMATIC.S7S User program, i.e. all blocks (OBs, FCs, FBs, DBs) and system blocks, project data of the CPU SIMATIC.HMI HMI-relevant data DataLogs DataLog files Recipes Recipe files Backups Files for backing up and restoring via the display Distributed I/O system System Manual, 02/2018, A5E03576849-AH 241 SIMATIC memory card 12.1 SIMATIC memory card - overview Table 12- 2 File structure File type Description S7_JOB.S7S Job file SIMATIC.HMI\Backup\*.psb Panel backup files SIMATICHMI_Backups_DMS. Protected file (required to use panel backup files in STEP 7) bin __LOG__ Protected system file (required in order to use the card) crdinfo.bin Protected system file (required in order to use the card) DUMP.S7S Service data file *.pdf, *.txt, *.csv, etc. Further files with different formats that you can also store in folders of the SIMATIC memory card Use the serial number for copy protection You can set up copy protection for CPUs which binds execution of the block to a specific SIMATIC memory card. Configuration is carried out in STEP 7 in the properties of the block "Bind to serial number of the SIMATIC memory card". You can only execute the block if it is on the SIMATIC memory card with the specified serial number (see section Copy protection (Page 170)). Removing a SIMATIC memory card Only remove the SIMATIC memory card in POWER OFF or STOP mode of the CPU. Make sure that no writing functions (e.g. loading/deleting a block) are active in STOP mode, or were active at POWER OFF. To do this, disconnect the communication connections. If you remove the SIMATIC memory card during a write process, the following problems can occur: The data contents of a file are incomplete. The file is no longer readable, or no longer exists. The entire content of the card is corrupted. Inserting the SIMATIC memory card in the CPU in STOP mode triggers a re-evaluation of the SIMATIC memory card. The CPU hereby compares the content of the configuration on the SIMATIC memory card with the backed-up retentive data. If the backed-up retentive data matches the data of the configuration on the SIMATIC memory card, the retentive data is retained. If the data differs, the CPU automatically performs a memory reset (which means the retentive data is deleted) and then goes to STOP. Also note the following FAQ on the Internet (https://support.industry.siemens.com/cs/ww/en/view/59457183) in connection with the removal of the SIMATIC memory card. Distributed I/O system 242 System Manual, 02/2018, A5E03576849-AH SIMATIC memory card 12.1 SIMATIC memory card - overview Removing a SIMATIC memory card from Windows computers If you are using the card in a commercially available card reader under Windows, use the "Eject" function before you remove the card from the card reader. If you remove the card without using the "Eject" function, you may lose data. Deleting the contents of the SIMATIC memory card You have the following options for deleting the content of the SIMATIC memory card: Delete files using Windows Explorer Format with STEP 7 Note If you format the card with Windows utilities, you will render the SIMATIC memory card unusable as a storage medium for a CPU. Deletion of files and folders is permitted, with the exception of the "__LOG__" and "crdinfo.bin" system files. The CPU needs these system files. If you delete the files, you will no longer be able to use the SIMATIC memory card with the CPU. If you have deleted the "__LOG__" and "crdinfo.bin" system files, format the SIMATIC memory card as described in the following section. Formatting the SIMATIC memory card Note You may only format a SIMATIC memory card in the CPU; otherwise, the SIMATIC memory card cannot be used in the CPU. If you want to format the SIMATIC memory card using STEP 7, an online connection to the relevant CPU must exist. The CPU is in STOP mode. Follow these steps to format a SIMATIC memory card with inserted SIMATIC memory card: 1. Open the Online and Diagnostics view of the CPU (either from the project context or via "Accessible devices"). 2. In the "Functions" folder, select the "Format memory card" group. 3. Click the "Format" button. 4. Click "Yes" in response to the confirmation prompt. Result: The SIMATIC memory card is formatted for use in the CPU. The data on the CPU is deleted with the exception of the IP address. You will find information on how to repair an inconsistently or incorrectly formatted card in the following FAQ on the Internet (https://support.industry.siemens.com/cs/ww/en/view/69063974). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 243 SIMATIC memory card 12.1 SIMATIC memory card - overview Service life of a SIMATIC memory card The service life of a SIMATIC memory card depends essentially on the following factors: Number of delete or write operations per memory block Number of bytes written External influences such as ambient temperature Reference You will find further information on the service life of the SIMATIC memory card and also storage space capacity utilization, and on the memory areas used, in the Structure and use of the CPU memory (https://support.industry.siemens.com/cs/de/de/view/59193101/en) function manual. GetSMCinfo instruction In the TIA Portal, you have the option of reading out the inserted SIMATIC memory card with the GetSMCinfo instruction. The following information can be read via the instruction: Memory size in KB Assigned memory space in KB Maintenance information: Previously used up portion of the service life in % Set proportion of the service life as a percentage after which the CPU creates a diagnostics buffer entry and the maintenance LED switches on. You can find additional information on the GetSMCinfo instruction in the STEP 7 online help. Distributed I/O system 244 System Manual, 02/2018, A5E03576849-AH SIMATIC memory card 12.2 Setting the card type 12.2 Setting the card type Introduction You can use the SIMATIC memory card as a program card or as a firmware update card. Procedure 1. To set the card type, insert the SIMATIC memory card into the card reader of the programming device. 2. Select the "SIMATIC Card Reader" folder in the project navigator. 3. In the properties of the selected SIMATIC memory card, specify the card type: Program card You use a program card as an external load memory for the CPU. It contains the entire user program for the CPU. The CPU transfers the user program from the load memory into the work memory. The user program runs in the work memory. The following folder is created on the SIMATIC memory card: SIMATIC.S7 Firmware update card You can save firmware for CPUs and for I/O modules on a SIMATIC memory card. It is thus possible to perform a firmware update with the help of a specifically prepared SIMATIC memory card. The following folder is created on the SIMATIC memory card: FWUPDATE.S7S Reference You can find more information on this topic in the STEP 7 online help. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 245 SIMATIC memory card 12.3 Data transfer with SIMATIC memory cards 12.3 Data transfer with SIMATIC memory cards Transferring objects from the project to a SIMATIC memory card When the SIMATIC memory card is inserted into the programming device or into an external card reader, you can transfer objects from the project tree (STEP 7) to the SIMATIC memory card as follows: Individual blocks (multiple selection possible) In this case, the transfer is consistent, i.e. the function takes dependencies between blocks due to block calls into account. CPU folder In this case, all runtime-relevant objects including blocks and the hardware configuration are transferred onto the SIMATIC memory card - just as when downloading. Service data In this case, the service data previously saved (see chapter Reading out/saving service data (Page 280)) is transferred to the SIMATIC memory card. To perform a transfer, you can transfer the objects by dragging and dropping, or use the "Card Reader/USB memory > Write to memory card" command in the "Project" menu. Firmware update using a SIMATIC memory card You can find information on how to perform a firmware update using a SIMATIC memory card in the section Firmware update (Page 257). Reference For additional information about the SIMATIC memory card, refer to the STEP 7 online help. Distributed I/O system 246 System Manual, 02/2018, A5E03576849-AH 13 Maintenance 13.1 Removing and inserting I/O modules/motor starters (hot swapping) Introduction The ET 200SP distributed I/O system supports removal and insertion of I/O modules and motor starters (hot swapping) during operation (RUN mode): CPU/interface module HF, HS: You can remove and insert any number of I/O modules/motor starters. ST, BA interface module: You can only remove and insert one I/O module/motor starter. This section provides further information on removing and inserting I/O modules/motor starters. I/O modules/motor starters must not be removed or inserted during operation (RUN operating state) in hazardous areas. Requirements The following table describes which modules you may insert and remove under which conditions: Table 13- 1 Removal and insertion of modules Modules Removal and insertion Conditions CPU No --- BusAdapter No --- CM DP module No --- Interface module No --- I/O modules Yes * Digital output modules: Only when load is switched off * Digital modules: For load voltage above the safe extra-low voltage: Only with switched off load voltage supply * Technology modules: Only with switched off supply voltage L+ * AI Energy Meter ST: - Only when measuring voltage on primary side is switched off, or - Without the special current transformer terminal, measuring voltage and load current must be through the converters, which means the machine or the load must be switched off in the process. With the special terminal, the process can continue because the current transformer is isolated safely. However, the measuring voltage on the module, at connections UL1-UL3, still needs to be isolated. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 247 Maintenance 13.1 Removing and inserting I/O modules/motor starters (hot swapping) Modules Removal and insertion PotDis-TerminalBlock Yes Motor starter Yes 1) Server module No Conditions Only in de-energized state. Only when the load is disconnected; when switched on, the motor starter switches off automatically when the rotary interlock is operated. --- 1) The motor starter also counts as removed in the parking position NOTICE Risk of hazardous system states If you remove and insert digital output modules with the load switched on or technology modules with the supply voltage switched on, this can result in hazardous system states. The ET 200SP distributed I/O system or the connected sensors may be damaged as a result. Therefore, a digital output module may only be inserted and removed when the load is switched off and a technology module may only be inserted and removed when the supply voltage is switched off. NOTICE Risk of hazardous system states If you remove and insert the AI Energy Meter ST with the primary-side voltage switched on at the current transformer, this can result in hazardous system states. The ET 200SP distributed I/O system may be damaged as a result. For this reason, remove and insert the AI Energy Meter ST * Only when measuring voltage on primary side is switched off, or * Only when a special current transformer terminal is used which short-circuits the secondary end of the transformer when a module is removed. Do not remove or insert the AI Energy Meter ST until you have removed this current transformer terminal. With the special terminal, the process can continue because the current transformer is isolated safely. However, the measuring voltage on the module at the connections UL1-UL3 still needs to be isolated. WARNING Risk of injury from automatic restart Inserting a motor starter can result in dangerous system states. The motor starter can restart again autonomously if an ON command is active. This can result in serious injury caused by connected devices that are automatically started up. Withdraw and insert a motor starter only after disconnecting the load. Distributed I/O system 248 System Manual, 02/2018, A5E03576849-AH Maintenance 13.1 Removing and inserting I/O modules/motor starters (hot swapping) Removing and inserting I/O module or motor starter with CPU/interface module HF, HS You can remove and insert any number of I/O modules/motor starters during operation. The CPU/interface module and the inserted I/O modules/motor starters remain in operation. NOTICE Reaction of the CPU to removal and insertion of the ET 200SP server module Please note that the backplane bus is deactivated when you remove the server module, regardless of the CPU operating state. Also note that the outputs do not adopt their configured substitute value behavior when you remove the server module. This means you should not remove the server module in the CPU operating states STARTUP, RUN and STOP. If you have nevertheless removed the server module, perform a POWER OFF/POWER ON after you have inserted the server module again. Removing and inserting BusAdapter or CM DP module Do not remove or insert the BusAdapter or CM DP module when the supply voltage is switched on. If you remove the BusAdapter or CM DP module after CPU startup, the supply voltage of the BusAdapter or CM DP module is switched off automatically. To switch on the supply voltage again, you need to perform a POWER OFF/POWER ON after inserting the BusAdapter/CM DP module. Removing and inserting I/O module or motor starter with interface module ST, BA 1. You can remove one I/O module/one motor starter during operation. If you remove another I/O module/motor starter, this results in a station stop of the ET 200SP distributed I/O system: - All I/O modules/motor starters of the ET 200SP distributed I/O system fail Substitute value behavior. - The interface module continues to exchange data with the IO controller and report diagnostics. Note If you want to replace several I/O modules/motor starters during operation, you must replace them one after the other. 2. If you insert all but one of the I/O modules/motor starters withdrawn during operation, all I/O modules will start up again. Note I/O modules/motor starters inserted in empty slots and then removed are also regarded as withdrawn during operation. 3. After a POWER OFF/POWER ON of the supply voltage 1L+ of the interface module, all available I/O modules/motor starters start up again in line with the configuration. Evaluation of the I/O modules/motor starters removed during operation starts again (see 1). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 249 Maintenance 13.1 Removing and inserting I/O modules/motor starters (hot swapping) Removing I/O modules To remove an I/O module, follow these steps: 1. Simultaneously press the top and bottom release buttons of the I/O module. 2. Pull the I/O module out of the BaseUnit, parallel in a forward direction. Figure 13-1 Removing I/O modules See also Interface modules (http://support.automation.siemens.com/WW/view/en/55683316/133300) Distributed I/O system 250 System Manual, 02/2018, A5E03576849-AH Maintenance 13.2 Changing the type of an I/O module 13.2 Changing the type of an I/O module Introduction The coding element is a two-part element. When shipped from the factory, both parts are in the I/O module. When an I/O module is installed for the first time, a part of the coding element clicks into the BaseUnit. This mechanically prevents the insertion of a different module type. There are two versions of the ET 200SP distributed I/O system: Mechanical coding element: Ensures the mechanical coding described above. Electronic coding element: In addition to the above-mentioned mechanical coding, this version also has an electronic, rewritable memory for module-specific configuration data (such as the F-destination address for fail-safe modules, parameter data for IO link master). Requirement Refer to section Application planning (Page 36). NOTICE Do not manipulate the coding element Making changes to the coding element may cause dangerous conditions in your plant and/or result in damage to the outputs of the ET 200SP distributed I/O system. To avoid physical damage, do not manipulate the coding. Changing the type of an I/O module You have already removed the I/O module. To make a type change for an I/O module, follow these steps: 1. Push the coding element out of the BaseUnit using a screwdriver. 2. Put the coding element back onto the removed I/O module. 3. Insert the new I/O module (other module type) into the BaseUnit until you hear it click into place. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 251 Maintenance 13.2 Changing the type of an I/O module 4. Label the new I/O module. Coding element Figure 13-2 Changing the type of an I/O module Distributed I/O system 252 System Manual, 02/2018, A5E03576849-AH Maintenance 13.3 Replacing an I/O module 13.3 Replacing an I/O module Introduction When an I/O module is installed for the first time, a part of the coding element clicks into the BaseUnit. When you replace an I/O module with the same type of module, the correct coding element is already present in the BaseUnit. Requirement Refer to section Application planning (Page 36). Replacing an I/O module You have already removed the I/O module. To replace an I/O module, follow these steps: 1. Remove the coding element (part) from the underside of the new I/O module. 2. Insert the new I/O module (same module type) into the BaseUnit until you hear it click into place. 3. Mark the new I/O module (labeling strip, equipment labeling plate). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 253 Maintenance 13.4 Replacing a motor starter 13.4 Replacing a motor starter The SIMATIC ET 200SP motor starter is wired. To replace a SIMATIC ET 200SP motor starter, proceed as follows: 1. Turn the mechanical rotary interlock counter-clockwise to the assembly/disassembly position. Note Operating position/READY Turn the mechanical rotary interlock out of the READY position only in the current-free state (motor off). 2. Remove the SIMATIC ET 200SP motor starter from the BaseUnit. 3. Assemble the new motor starter as described. Note Mounting the motor starter You will find out how to mount the motor starter in chapter "Mounting/disassembly of motor starters (Page 120)". WARNING Risk of injury from automatic restart When you replace the motor starter, the motor starter can restart again autonomously if an ON command is active. This can result in property damage or serious injury caused by connected devices that are automatically started up. Revoke the ON commands on the motor starter before replacing the motor starter. CAUTION Protection against electrostatic charge When handling and installing the SIMATIC ET 200SP motor starter, ensure protection against electrostatic charging of the components. Changes to the system configuration and wiring are only permissible after disconnection from the power supply. Distributed I/O system 254 System Manual, 02/2018, A5E03576849-AH Maintenance 13.5 Replacing the terminal box on the BaseUnit 13.5 Replacing the terminal box on the BaseUnit Introduction The terminal box is part of the BaseUnit. You can replace the terminal box if necessary. You do not need to dismantle the BaseUnit to do this. The power and AUX buses of the potential group are not interrupted when you replace the terminal box. Requirements The BaseUnit is mounted, wired and fitted with an I/O module. The terminal may only be replaced when the supply voltage is switched off. Required tools 3 to 3.5 mm screwdriver Procedure Watch the video sequence: "Replace terminal box on BaseUnit" (http://support.automation.siemens.com/WW/view/en/95886218) Proceed as follows to replace the terminal box on a BaseUnit: 1. If present, turn off the supply voltage on the BaseUnit. 2. Simultaneously press the top and bottom release buttons of the I/O module and pull the module out of the BaseUnit. 3. Disconnect the wiring on the BaseUnit. 4. The release button of the terminal box is located on the underside of the BaseUnit. Use a screwdriver to push in the small opening at an angle from above. 5. Swivel the screwdriver slightly upwards to loosen the locking mechanism of the terminal box and lever the terminal box up out of the BaseUnit at the same time. 6. Remove the coding element (part) from the terminal box and press it onto the coding element (part) of the I/O module that you removed in step 2. 7. Insert the new terminal box into the BaseUnit at the top and swivel it downwards until it clips into the BaseUnit. 8. Wire up the BaseUnit. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 255 Maintenance 13.5 Replacing the terminal box on the BaseUnit 9. Insert the I/O module into the BaseUnit. 10.Switch on a supply voltage on the BaseUnit. Figure 13-3 Replacing the terminal box on the BaseUnit Distributed I/O system 256 System Manual, 02/2018, A5E03576849-AH Maintenance 13.6 Firmware update 13.6 Firmware update Introduction During operation it may be necessary to update the firmware (e.g. to extend the available functions). Update the firmware of the CPU/interface module and the I/O modules using firmware files. The retentive data is retained after the firmware has been updated. Requirement You have downloaded the file(s) for the firmware update from the Product Support (https://support.industry.siemens.com/cs/ww/en/ps) web page. On this web page, select: - Automation Technology > Automation Systems > Industrial Automation Systems SIMATIC > SIMATIC ET 200 I/O Systems > ET 200 systems for the cabinet > ET 200SP. Figure 13-4 ET 200SP in the product tree Distributed I/O system System Manual, 02/2018, A5E03576849-AH 257 Maintenance 13.6 Firmware update From there, navigate to the specific type of module that you want to update. To continue, click on the "Software downloads" link under "Support". Save the desired firmware update files. Figure 13-5 Selecting the software downloads Before installing the firmware update, make sure that the modules are not being used. Note Firmware update of I/O modules The L+ supply voltage must be present on the module at the start of and during the firmware update. Additional requirement for fail-safe modules WARNING Check the firmware version When using a new firmware version, always check that the version is approved for use in the module in question. The attachments of the certificate (http://support.automation.siemens.com/WW/view/en/49368678/134200) for SIMATIC Safety specify the firmware version that is approved. Distributed I/O system 258 System Manual, 02/2018, A5E03576849-AH Maintenance 13.6 Firmware update Options for the firmware update The following options are available for updating firmware: Online in STEP 7 via Online & Diagnostics Online in STEP 7 via accessible devices (PROFINET) Using a SIMATIC memory card (possible for CPU and central I/O modules) Via the integrated Web server (possible for CPU as well as centralized and distributed I/O modules) Online via the SIMATIC Automation Tool Note Firmware files of the CPU If you perform a CPU update with STEP 7, you require STEP 7 (TIA Portal as of V13 Update 3). The table below provides an overview of the media that can be used to update the firmware of a specific module. Table 13- 2 Overview of firmware update options Firmware update CPU STEP 7 (TIA Portal) Interface module I/O module STEP 7 (V5.5 SP2 or higher) 2) -- Accessible devices SIMATIC memory card -- Web server of the CPU -- SIMATIC Automation Tool 1) 1) V13 update 3 or higher 2) If the firmware files are only available in this format, you can also install the files using STEP 7 (TIA Portal) but not the SIMATIC memory card or the Web server. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 259 Maintenance 13.6 Firmware update Firmware update for the motor starter The following options are available for updating firmware for the motor starter. Online via PROFINET IO/PROFIBUS DP (with STEP 7) Via the integrated Web server (possible for CPU as well as centralized and distributed I/O modules) With the TIA Portal: - As of SIMATIC STEP 7 V13 SP1 with installed HSP for the ET 200SP motor starter - SIMATIC STEP 7 V14 and higher Over a SIMATIC memory card With SIMATIC STEP 7 version V5.5 SP4 and higher For fail-safe motor starters with the TIA Portal Version V14 SP1 or higher and installed HSP. Note The firmware update for fail-safe motor starters must take place in a separate ET 200SP system in which only the fail-safe motor starter that is to be updated is inserted. Installation of the firmware update WARNING Risk of impermissible system states The CPU switches to STOP mode or the interface module to "station failure" as a result of the firmware update being installed. STOP or station failure can have an adverse effect on the operation of an online process or a machine. Unexpected operation of a process or a machine can lead to fatal or severe injuries and/or to material damages. Make sure that the CPU/interface module is not executing any active process before installing the firmware update. Distributed I/O system 260 System Manual, 02/2018, A5E03576849-AH Maintenance 13.6 Firmware update Procedure online in STEP 7 via Online & Diagnostics Proceed as follows to perform an online firmware update via STEP 7: 1. Select the module in the device view. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. Select the "Firmware update" group in the "Functions" folder. 4. Click the "Browse" button to select the path to the firmware update files in the "Firmware update" area. 5. Select the suitable firmware file. The table in the firmware update area lists all modules for which an update is possible with the selected firmware file. 6. Click the "Run update" button. If the module can interpret the selected file, the file is downloaded to the module. Updating the firmware The "Run firmware after update" check box is always selected. When the loading process is complete, the CPU adopts the firmware and then operates with this new firmware. Note If a firmware update is interrupted, you need to remove and insert the module before starting the firmware update again. Procedure online in STEP 7 via accessible devices To perform a firmware update online via accessible devices, follow these steps: 1. From the "Online" menu, select the "Accessible devices" menu item. 2. In the "Accessible devices" dialog, search for the accessible devices for the selected PROFINET interface. 3. To go to a device in the project tree, select the desired device from the list of accessible devices and click the "Show" button. 4. In the project tree, select the "Online & diagnostics" option of the relevant device and perform the firmware update under the category "Functions/Firmware Update" (CPU, Local modules). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 261 Maintenance 13.6 Firmware update Procedure using the SIMATIC memory card To perform a firmware update using the SIMATIC memory card, follow these steps: 1. Insert a SIMATIC memory card into the SD card reader of your programming device/computer. 2. To store the update file on the SIMATIC memory card, select the SIMATIC memory card in the "Card Reader/USB memory" folder in the project tree. 3. Select the "Card Reader/USB memory > Create firmware update memory card" command in the "Project" menu. 4. Use a file selection dialog to navigate to the firmware update file. In a further step you can decide whether you want to delete the content of the SIMATIC memory card or whether you want to add the firmware update files to the SIMATIC memory card. 5. Insert the SIMATIC memory card with the firmware update files into the CPU. Point to note when updating firmware for analog modules and the IO-Link Master CM 4xIO-Link communication module If you want to update firmware for analog modules or the IO-Link Master CM 4xIO-Link communication module, you must supply a load current of 24 V DC to the modules through the infeed element. Procedure 1. Remove any inserted SIMATIC memory card. 2. Insert the SIMATIC memory card with the firmware update files into the CPU. 3. The firmware update begins shortly after the SIMATIC memory card has been inserted. 4. Remove the SIMATIC memory card after the firmware update has been completed. The RUN LED on the CPU lights up yellow, the MAINT LED flashes yellow. If you want to use the SIMATIC memory card later as a program card, delete the firmware update files manually. Note If your hardware configuration contains several modules, the CPU updates all affected modules in the slot sequence, which means in ascending order of the module position in the STEP 7 device configuration. Distributed I/O system 262 System Manual, 02/2018, A5E03576849-AH Maintenance 13.6 Firmware update Note Memory size of the SIMATIC memory card If you perform a firmware update via the SIMATIC memory card, you must use a large enough card based on the CPU used and the associated I/O modules. Therefore, be sure to note the file size of the update files when downloading them from the Product Support website. The file size information is especially important when you perform the firmware update not only for the CPU but also for the associated I/O modules, communication modules, etc. The total size of the update files must not exceed the available memory size of your SIMATIC memory card. Procedure: via the integrated Web server The procedure is described in the Web server (http://support.automation.siemens.com/WW/view/en/59193560) function manual. Procedure: online via the SIMATIC Automation Tool The procedure is described in the SIMATIC Automation Tool (https://support.industry.siemens.com/cs/ww/en/view/98161300) manual (included in the SIMATIC Automation Tool). Behavior during the firmware update Note the following behavior of the relevant I/O module when carrying out a firmware update: The DIAG LED display flashes red. The I/O module retains its current diagnostic status. Diagnostics alarm: Channel temporarily unavailable (error code 31D/1FH) All outputs are in a current-free/voltage-free state Note the following behavior when carrying out the firmware update of the motor starter: RN flashes green and ER flashes red. ST/OL flashes green and MAN flashes yellow. The motor starter powers up after completion of the firmware update. Diagnoses are reset. The firmware update does not affect the TMM and the cooling time. The sensor supply of the DI module remains active. Behavior after the firmware update After the firmware update, check the firmware version of the updated module. Reference You will find more information on these procedures in the STEP 7 online help. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 263 Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings 13.7 Resetting CPU/interface module (PROFINET) to factory settings 13.7.1 Resetting the CPU to factory settings Function The CPU can be reset to its delivery state using "Reset to factory settings". The function deletes all information saved internally on the CPU. Recommendation: If you want to remove a PROFINET CPU and use it elsewhere with a different program, or put it into storage, we recommend that you reset the CPU to its factory settings. When restoring the factory settings, remember that you also delete the IP address parameters. Options for resetting a CPU to factory settings The following options are available for resetting the CPU to its factory settings: Using the mode selector Using STEP 7 Using the SIMATIC Automation Tool Procedure using the mode selector Make sure that there is no SIMATIC memory card in the CPU and that the CPU is in STOP mode (the RUN/STOP LED is lit yellow). Note Reset to factory settings Memory reset The procedure described below also corresponds to the procedure for a memory reset: * Selector operation with inserted SIMATIC memory card: CPU executes a memory reset * Selector operation without inserted SIMATIC memory card: CPU executes reset to factory settings Distributed I/O system 264 System Manual, 02/2018, A5E03576849-AH Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings Perform a reset to factory settings when there is no SIMATIC memory card inserted as follows: 1. Set the mode selector to the STOP position. Result: The RUN/STOP LED lights up yellow. 2. Set the mode selector to the MRES position. Hold the mode selector in this position until the RUN/STOP LED lights up for the 2nd time and remains continuously lit (after three seconds). After this, release the switch. 3. Within the next three seconds, switch the mode selector back to the MRES position, and then back to STOP again. Result: The CPU executes the "Reset to factory settings", during which time the RUN/STOP LED flashes yellow. When the RUN/STOP LED lights up yellow, the CPU has been reset to factory settings and is in the STOP mode. The "Reset to factory settings" event is entered in the diagnostics buffer. Note The IP address of the CPU is also deleted when the CPU is reset to the factory settings through the mode selector. For information on the memory reset of the CPU, refer to the section CPU memory reset (Page 221). Procedure using STEP 7 Make sure that an online connection to the CPU exists. To reset a CPU to factory settings using STEP 7, follow these steps: 1. Open the Online and Diagnostics view of the CPU. 2. In the "Functions" folder, select the "Reset to factory settings" group. 3. If you want to keep the IP address, select the "Retain IP address" option button. If you want to delete the IP address, select the "Reset IP address" option button. Note The "Delete IP address" option deletes all IP addresses. This applies regardless of how you established the online connection. If a SIMATIC memory card is inserted, the "Delete IP address" option deletes the IP addresses and resets the CPU to factory settings. Then, the configuration (including IP address) that is stored on the SIMATIC memory card is transferred to the CPU (see below). If you formatted the memory card before the reset to factory settings or if the memory card is empty, no IP address is transferred to the CPU. 4. Click the "Reset" button. 5. Click "OK" in response to the confirmation prompts. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 265 Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings Result: The CPU executes the "Reset to factory settings", during which time the RUN/STOP LED flashes yellow. When the RUN/STOP LED lights up yellow, the CPU has been reset to factory settings and is in the STOP mode. The "Reset to factory settings" event is entered in the diagnostics buffer. Procedure using the SIMATIC Automation Tool The procedure is described in the SIMATIC Automation Tool (https://support.industry.siemens.com/cs/ww/en/view/98161300) manual (included in the SIMATIC Automation Tool). Result after resetting to factory settings The following table provides an overview of the contents of the memory objects after the reset to factory settings. Table 13- 3 Result after resetting to factory settings Memory object Content Actual values of the data blocks, instance data blocks Initialized Bit memory, timers and counters Initialized Certain retentive tags from technology objects (e.g. adjustment values of absolute encoders) Initialized Diagnostics buffer entries Initialized IP address Depends on the procedure: * Using mode switch: is deleted * Using STEP 7: Depending on the setting of the "Keep IP address"/"Delete IP address" option buttons Device name Initialized Counter readings of the runtime meters Initialized Time of day Initialized If a SIMATIC memory card was inserted prior to the factory reset, the CPU downloads the configuration contained on the SIMATIC memory card (hardware and software). A configured IP address then becomes valid again. Reference Additional information on the topic "Resetting to factory settings" can be found in the Structure and use of the CPU memory (http://support.automation.siemens.com/WW/view/en/59193101) function manual, section on memory areas and retentivity, and in the STEP 7 online help. Distributed I/O system 266 System Manual, 02/2018, A5E03576849-AH Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings 13.7.2 Resetting interface module (PROFINET IO) to factory settings Function The "Reset to factory settings" function returns the interface module (PROFINET) to its delivery state. Reset options Using STEP 7 (online via PROFINET IO) Using a reset button on the interface module (on rear). Exception: The IM 155-6 PN BA does not possess this reset button. See section Resetting the interface module (PROFINET IO) to factory settings with a RESET button (Page 268). Procedure using STEP 7 To reset an interface module to factory settings using STEP 7, follow these steps: Make sure that an online connection to the interface module exists. 1. Open the online and diagnostics view of the interface module. 2. In the "Functions" folder, select the "Reset to factory settings" group. 3. Click the "Reset" button. 4. Click "OK" in response to the confirmation prompt. Result: The interface module then performs "Reset to factory settings". Distributed I/O system System Manual, 02/2018, A5E03576849-AH 267 Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings Result after resetting to factory settings The following table shows the values of the interface module properties after a factory reset: Table 13- 4 Properties of the interface module as shipped Properties Value Parameters Default setting IP address Not available Device name Not available MAC address Available I&M data Identification data (I&M0) available Maintenance data (I&M1, 2, 3, 4) reset * Firmware version Available * Can be selected with STEP 7 V14 or higher: "Keep I&M data"/"Delete I&M data" Note Failure of downstream stations is possible Downstream stations on a bus segment can fail when the factory settings are restored on an interface module. Note Behavior of the installed I/O modules during reset to factory settings When "Resetting to factory settings", the I/O modules of the ET 200SP distributed I/O system take on the non-configured state, which means input data are not entered and output data are not output. Reference You will find more information on the procedure in the STEP 7 online help. 13.7.3 Resetting the interface module (PROFINET IO) to factory settings with a RESET button Requirement The supply voltage to the interface module is turned on. Required tools 3 to 3.5 mm screwdriver (for resetting with a RESET button) Distributed I/O system 268 System Manual, 02/2018, A5E03576849-AH Maintenance 13.7 Resetting CPU/interface module (PROFINET) to factory settings Procedure Proceed as follows to reset an interface module to factory settings by means of the RESET button: 1. Remove the interface module from the mounting rail (see Mounting the CPU/interface module (Page 70)) and swivel it downwards. 2. The RESET button is located on the rear of the interface module behind a small opening: Press a screwdriver into the small opening for at least 3 seconds to activate the RESET button. 3. Install the interface module back on the mounting rail (see Mounting the CPU/interface module (Page 70)). 4. Assign parameters to the interface module again. Rear of the interface module RESET button Figure 13-6 RESET button Distributed I/O system System Manual, 02/2018, A5E03576849-AH 269 Maintenance 13.8 Reaction to faults in fail-safe modules and fail-safe motor starters 13.8 Reaction to faults in fail-safe modules and fail-safe motor starters Safe state (safety concept) The basic principle behind the safety concept is the existence of a safe state for all process variables. Note For digital F-modules, this safe state is the value "0". This applies to both sensors and actuators. In the case of the fail-safe motor starters, the load is shut down in a fail-safe manner. Fault reactions and startup of the F-system The safety function means that fail-safe modules use substitute values (safe state) instead of process values (passivation of the fail-safe module) in the following situations: When the F-system is started up If errors are detected during safety-related communication between the F-CPU and the F-module via the PROFIsafe safety protocol (communication error) If F-I/O faults or channel faults are detected (e.g. crossover or discrepancy errors) Detected faults are written to the diagnostic buffer of the F-CPU and communicated to the safety program in the F-CPU. F-modules cannot save errors as retentive data. After a POWER OFF / POWER ON, any faults still existing are detected again during startup. However, you have the option of saving faults in your safety program. WARNING For channels that you set to "deactivated" in STEP 7, no diagnostic response or error handling is triggered when a channel fault occurs, not even when such a channel is affected indirectly by a channel group fault ("Channel activated/deactivated" parameter). Remedying faults in the F-system To remedy faults in your F-system, follow the procedure described in IEC 61508-1:2010 section 7.15.2.4 and IEC 61508-2:2010 section 7.6.2.1 e. The following steps must be performed: 1. Diagnosing and repairing the fault 2. Revalidation of the safety function 3. Recording in the service report Distributed I/O system 270 System Manual, 02/2018, A5E03576849-AH Maintenance 13.8 Reaction to faults in fail-safe modules and fail-safe motor starters Substitute value output for fail-safe modules In the case of F-modules with inputs, if there is passivation, the F-system provides substitute values (0) for the safety program instead of the process data pending at the fail-safe inputs. In the case of F-modules with outputs, if there is passivation, the F-system transfers substitute values (0) to the fail-safe outputs instead of the output values provided by the safety program. The output channels are de-energized. This also applies when the F-CPU goes into STOP mode. Assignment of substitute values is not possible. Depending on which F-system you are using and the type of fault that occurred (F-I/O fault, channel fault or communication error), substitute values are used either for the relevant channel only or for all channels of the relevant fail-safe module. Reintegration of a fail-safe module The system changes from fail-safe to process values (reintegration of an F-module) either automatically or only after user acknowledgment in the safety program. If channel faults occur, it may be necessary to remove and reinsert the F-module. A detailed listing of faults requiring removal and insertion of the F-module can be found in the section Diagnostic messages of the respective F-module. After reintegration, the following occurs: In the case of an F-module with inputs, the process data pending at the fail-safe inputs is made available to the safety program again In the case of an F-module with outputs, the output values provided in the safety program are transferred to the fail-safe outputs again Additional information on passivation and reintegration For additional information on passivation and reintegration of F-I/O, refer to the SIMATIC Safety, Configuring and Programming (http://support.automation.siemens.com/WW/view/en/54110126) manual. Behavior of the fail-safe module with inputs in the event of a communication disruption F-modules with inputs respond differently to communication errors compared to other errors. If a communication error is detected, the current process values remain set at the inputs of the F-module. There is no passivation of the channels. The current process values are passivated in the F-CPU. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 271 Maintenance 13.9 Maintenance and repair 13.9 Maintenance and repair The components of the SIMATIC ET 200SP system are maintenance-free. Note Repairs to a SIMATIC ET 200SP system may only be carried out by the manufacturer. 13.10 Warranty To meet the conditions of the warranty, you must observe the safety and commissioning instructions. Distributed I/O system 272 System Manual, 02/2018, A5E03576849-AH Test functions and eliminating problems 14.1 14 Test functions Introduction You have the option of testing the operation of your user program on the CPU. You can then monitor signal states and values of tags and can assign values to tags to simulate specific situations in the running of the program. Note Using test functions The use of test functions can influence the program execution time and thus the cycle and response times of the controller to a slight extent (a few milliseconds). Requirements There is an online connection to the relevant CPU. An executable program is in the CPU. Test options Testing with program status Testing with breakpoints Testing with a watch table Testing with a force table Testing with PLC tag table Testing with data block editor Testing with the LED flash test Testing with trace function Distributed I/O system System Manual, 02/2018, A5E03576849-AH 273 Test functions and eliminating problems 14.1 Test functions Testing with program status The program status allows you to monitor the execution of the program. You can display the values of operands and the results of logic operations (RLO) allowing you to recognize and fix logical errors in your program. Note Restrictions for the "Program status" function Monitoring loops can clearly increase the cycle time, depending on the number of tags monitored and depending on the actual number of loops run through. WARNING Testing with program status A test with the "Program status" function can produce serious property damage and personal injury in the event of malfunctions or program errors. Make sure that you take appropriate measures to exclude the risk of hazardous conditions occurring before running a test with the "Program status" function. Testing with breakpoints With this test option, you set breakpoints in your program, establish an online connection, and enable the breakpoints on the CPU. You then execute a program from one breakpoint to another. Requirements: Setting breakpoints is possible in the programming language SCL or STL. Testing with breakpoints provides you with the following advantages: Localization of logic errors step by step Simple and quick analysis of complex programs prior to actual commissioning Recording of current values within individual executed loops Use of breakpoints for program validation also possible in SCL/STL networks within LAD/FBD blocks Note Restriction during testing with breakpoints When you test with breakpoints, there is a risk of overwriting the cycle time of the CPU. Distributed I/O system 274 System Manual, 02/2018, A5E03576849-AH Test functions and eliminating problems 14.1 Test functions Note F-System SIMATIC Safety Setting breakpoints in the standard user program results in errors in the security program: * Sequence of F cycle time monitoring * Error in communication with the fail-safe I/O * Error during safety-oriented CPU-CPU communication * internal CPU error If you still wish to use breakpoints for testing, you must deactivate the safety mode beforehand. This will result in the following errors: * Error in communication with the fail-safe I/O * Error during safety-oriented CPU-CPU communication Distributed I/O system System Manual, 02/2018, A5E03576849-AH 275 Test functions and eliminating problems 14.1 Test functions Testing with watch tables The following functions are available in the watch table: Monitoring of tags With watch tables, you can monitor the current values of individual tags of a user program or a CPU on the PG/PC and Web server. For the Web server to be able to display the value of tags, you must specify a symbolic name for each tag in the "Name" column of the watch table. You can monitor the following operand areas: - Inputs and outputs (process image) and bit memory - Contents of data blocks - Peripheral inputs and peripheral outputs - Timers and counters Modifying tags Use this function to assign fixed values to the individual tags of a user program or CPU. Modifying is also possible for testing with program status. You can control the following operand areas: - Inputs and outputs (process image) and bit memory - Contents of data blocks - Peripheral inputs and peripheral outputs (for example, %I0.0:P, %Q0.0:P) - Timers and counters "Enable peripheral outputs" and "Control immediately" These two functions enable you to assign fixed values to individual peripheral outputs of a CPU in the STOP mode. You can also use them to check your wiring. Distributed I/O system 276 System Manual, 02/2018, A5E03576849-AH Test functions and eliminating problems 14.1 Test functions Testing with the force table The following functions are available in the force table. Monitoring of tags With force tables, you can display the current values of individual tags of a user program or a CPU on the PG/PC and Web server. You can monitor the table with or without a trigger condition. For the Web server to be able to display the value of tags, you must specify a symbolic name for each tag in the "Name" column of the force table. You can monitor the following tags: - Bit memory - Contents of data blocks - Peripheral inputs (e.g. %I0.0:P) Modifying tags With this function, you assign fixed values to the individual tags of a user program or a CPU on the PG/PC and Web server. Modifying is also possible for testing with program status. You can control the following tags: - Bit memories - Contents of data blocks - Peripheral inputs (e.g. %I0.0:P) Forcing of peripheral inputs and peripheral outputs You can force individual peripheral inputs or peripheral outputs. - Peripheral inputs: Forcing of peripheral inputs (for example %I0.0:P) represents the "bypassing" of sensors/inputs by specifying fixed values to the program. Instead of the actual input value (via process image or via direct access) the program receives the force value. - Peripheral outputs: Forcing of peripheral outputs (for example %Q0.0:P) represents the "bypassing" of the complete program by setting fixed values for the actuators. The force table offers the advantage both of being able to simulate different test environments and also of being able to overwrite tags in the CPU with a fixed value. Thus, you have a possibility of intervening in the ongoing process to regulate it. Distributed I/O system System Manual, 02/2018, A5E03576849-AH 277 Test functions and eliminating problems 14.1 Test functions Difference between modifying and forcing The fundamental difference between the modifying and forcing functions consists in the storage behavior: Modifying: Modifying of tags is an online function and is not stored in the CPU. You can end modifying of tags in the watch table or by disconnecting the online connection. Forcing: A force job is written to the SIMATIC memory card and is retained after a POWER OFF. You can only end the forcing of peripheral inputs and peripheral outputs in the force table. Testing with PLC tag table You can monitor the data values that tags currently assume in the CPU directly in the PLC tag table. To do this, open the PLC tag table and start monitoring. Additionally, you have a possibility of copying PLC tags to a monitoring or force table and of monitoring, controlling or forcing them there. Testing with data block editor Various possibilities of monitoring and controlling tags are at your disposal in the data block editor. These functions directly access the current values of the tags in the online program. Current values are the values that the tags assume at the current time during program execution in the CPU's work memory. The following functions for monitoring and control are possible via the data block editor: Monitoring tags online Controlling individual actual values Creating a snapshot of the actual values Overwriting actual values with a snapshot Note Setting data values during commissioning During commissioning of a system, data values often have to be adjusted to optimally adapt the program to the general conditions prevailing locally. To this end, the declaration table offers a few functions for data blocks. Distributed I/O system 278 System Manual, 02/2018, A5E03576849-AH Test functions and eliminating problems 14.2 Reading out/saving service data Testing with the LED flash test In many online dialogs, you can perform an LED flash test. This function is useful, for example, when you are not sure which device in the hardware configuration corresponds to the device currently selected in the software. When you click the "Flash LED" button, an LED flashes on the currently selected device. In the case of the CPU, the RUN/STOP, ERROR and MAINT LEDs flash. They flash until you cancel the flashing test. Testing with trace function The trace function is used to record the CPU tags, depending on the settable trigger conditions. Tags are, for example, the drive parameters or system and user tags of a CPU. The CPU saves the recordings. You can display and evaluate the recordings with STEP 7, if necessary. The trace function can be called from the CPU's folder in the project tree, under the name "Traces". In connection with trace functions, also pay attention to the following FAQ on the Internet (https://support.industry.siemens.com/cs/ww/en/view/102781176). Simulation With STEP 7 you can run and test the hardware and software of the project in a simulated environment. Start the simulation using the menu command "Online" > "Simulation" > "Start". Reference You can find more information on test functions in the STEP 7 online help. Further information about testing with trace and logic analyzer functions is available in the Function Manual Using the trace and logic analyzer function (http://support.automation.siemens.com/WW/view/en/64897128). Distributed I/O system System Manual, 02/2018, A5E03576849-AH 279 Test functions and eliminating problems 14.2 Reading out/saving service data 14.2 Reading out/saving service data Service data In addition to the contents of the diagnostics buffer, the service data contains a wide range of extra information about the internal status of the CPU. If a problem occurs the CPU that cannot be solved with other methods, send the service data to our Service & Support team. The service data allows Service & Support to run fast analysis of the problems that have occurred. Note You cannot simultaneously execute a download to the device while reading out the service data of the CPU. Methods of reading service data You can read service data with: The Web server STEP 7 the SIMATIC memory card Procedure using the Web server To read service data using the Web server, follow these steps: 1. Open a Web browser that is suitable for communication with the CPU. 2. Enter the following address in the address bar of the web browser: https:///save_service_data, e.g. https://172.23.15.3/save_service_data 3. The service data page will appear on your screen, with a button for saving the service data. Figure 14-1 Reading out service data with the Web server 4. Save the service data locally on your PC/programming device, by clicking "Save ServiceData". Distributed I/O system 280 System Manual, 02/2018, A5E03576849-AH Test functions and eliminating problems 14.2 Reading out/saving service data Result: The CPU stores the data in a .dmp file with the following naming convention: "