in combination with PROFIBUS DP and PROFINET (Step 7 V5.5 / TIA Portal) Application note
A114802, English Version 00.03.03
2 General Application note A114802 Copyright 2010 by WAGO Kontakttechnik GmbH & Co. KG All rights reserved. WAGO Kontakttechnik GmbH & Co. KG Hansastrae 27 D-32423 Minden Phone: +49 (0) 571/8 87 0 Fax: +49 (0) 571/8 87 1 69 E-mail: info@wago.com Web: http://www.wago.com Technical Support Phone: +49 (0) 571/8 87 5 55 Fax: +49 (0) 571/8 87 85 55 E-mail: support@wago.com
Every conceivable measure has been taken to ensure the accuracy and completeness of this documentation. However, as errors can never be fully excluded, we always appreciate any information or suggestions for improving the documentation. We wish to point out that the software and hardware terms, as well as the trademarks of companies used and/or mentioned in the present manual, are generally protected by trademark or patent. Contents 3 Application note A114802
TABLE OF CONTENTS 1 Important Notes .......................................................................................... 9 1.1 Legal Principles ........................................................................................ 9 1.1.1 Copyright ............................................................................................. 9 1.1.2 Personnel Qualification ....................................................................... 9 1.1.3 Intended Use ........................................................................................ 9 1.2 Scope of Validity .................................................................................... 10 1.3 Symbols .................................................................................................. 11 2 General ....................................................................................................... 12 2.1 Terms of Use .......................................................................................... 12 3 WAGO-I/O-SYSTEM Basics ................................................................... 14 3.1 General ................................................................................................... 14 3.2 Using the WAGO-I/O-SYSTEM with PROFIBUS DP ......................... 14 3.2.1 General ............................................................................................... 14 3.2.2 GSD File ............................................................................................ 14 3.2.2.1 Download Internet ......................................................................... 14 3.3 Using the WAGO-I/O-SYSTEM with PROFINET ............................... 17 3.3.1 General ............................................................................................... 17 3.3.2 GSDML file ....................................................................................... 17 3.3.2.1 Download Internet ......................................................................... 17 3.4 Using the WAGO-I/O-SYSTEM with PROFIsafe ................................. 20 3.4.1 General ............................................................................................... 20 3.4.2 Required Software Tools ................................................................... 20 3.4.3 Operating Principles .......................................................................... 20 3.4.3.1 Safety Program .............................................................................. 20 3.4.3.2 "Edit safety program" Function ..................................................... 21 3.4.3.3 Fail-safe I/O DB ............................................................................ 21 3.4.3.3.1 PASS_ON ................................................................................ 22 3.4.3.3.2 ACK_NEC ............................................................................... 22 3.4.3.3.3 ACK_REI ................................................................................. 22 3.4.3.3.4 IPAR_EN ................................................................................. 23 3.4.3.3.5 PASS_OUT .............................................................................. 23 3.4.3.3.6 QBAD ....................................................................................... 23 3.4.3.3.7 ACK_REQ ............................................................................... 23 3.4.3.3.8 IPAR_OK ................................................................................. 23 3.4.3.3.9 DIAG ........................................................................................ 24 3.4.4 Assignment of the Hardware Configuration to F-Periphery-DB ....... 25 3.4.4.1 Using PROFIBUS-DP ................................................................... 25 3.4.4.2 Using PROFINET ......................................................................... 26 3.4.4.3 Note about assigned F-Periphery-DBs .......................................... 27 3.4.5 Data Transfer and Data Access .......................................................... 28 3.4.5.1 Standard Program to the Safety Program ...................................... 28 3.4.5.2 Safety Program to the Standard Program ...................................... 29 3.5 Required WAGO Tools .......................................................................... 30 3.5.1 WAGO-I/O-CHECK ......................................................................... 30 3.5.2 WAGO Safety Editor 75x .................................................................. 30 4 Contents Application note A114802 4 iPar-Server Technology ............................................................................ 31 5 Function Blocks iPar Option WAGO ...................................................... 33 5.1 Motivation iPar Option ........................................................................... 33 5.2 General ................................................................................................... 33 5.3 Overview of Block Functions ................................................................. 34 5.3.1 Setup and Structure of Block Calls .................................................... 34 5.3.2 Implemented Function Blocks ........................................................... 35 5.3.2.1 Input Function Blocks ................................................................... 35 5.3.2.1.1 INIT_FB, Type BOOL ............................................................. 35 5.3.2.1.2 RESET, Type BOOL ................................................................ 35 5.3.2.1.3 CHECK_CFG, Type BOOL ..................................................... 35 5.3.2.1.4 UPLOAD_REQ, Type BOOL .................................................. 36 5.3.2.1.5 DOWNLOAD_REQ, Type BOOL ........................................... 36 5.3.2.1.6 COMPARE_REQ, Type BOOL ............................................... 36 5.3.2.1.7 DIAG_DATA_REQ_REQ, Type BOOL ................................. 36 5.3.2.1.8 SELECT_MODULE, Type DWORD ...................................... 37 5.3.2.1.9 READ_DIAG_DATA, Type BOOL ........................................ 37 5.3.2.1.10 ACT_DATE, Type DATE........................................................ 38 5.3.2.1.11 ACT_TIME, Type TIME_OF_DAY ........................................ 38 5.3.2.1.12 iPar_DB_NB, Type BLOCK_DB ............................................ 38 5.3.2.1.13 MODULES_PLUGGED, Type INT ........................................ 38 5.3.2.1.14 SLAVE_DP_PN, Type BOOL ................................................. 38 5.3.2.1.15 ADR_MOD_x, Type INT ........................................................ 39 5.3.2.1.16 F_PER_DB_MOD_x, Type BLOCK_DB ............................... 39 5.3.2.1.17 TYPE_MOD_x, Type INT ....................................................... 39 5.3.2.2 Output Function Blocks ................................................................ 40 5.3.2.2.1 INIT_OK, Type BOOL ............................................................ 40 5.3.2.2.2 UPLOAD_ALL_MODULES, Type BOOL ............................. 40 5.3.2.2.3 BUSY, Type BOOL ................................................................. 40 5.3.2.2.4 DONE, Type BOOL ................................................................. 40 5.3.2.2.5 DONE_ALL_MODULES, Type BOOL .................................. 40 5.3.2.2.6 ERROR, Type BOOL ............................................................... 40 5.3.2.2.7 ERROR_FB, Type WORD ...................................................... 40 5.3.2.2.8 ERROR_FB_NB, Type INT..................................................... 40 5.3.2.2.9 STATE_FCT_REQ_OK, Type DWORD ................................ 41 5.3.2.2.10 STATE_FCT_REQ_ERROR, Type DWORD ......................... 41 5.3.2.2.11 QBAD_ACTIVE, Type BOOL ................................................ 41 5.3.2.2.12 ACK_REQ_ACTIVE, Type BOOL ......................................... 41 5.4 Defined Data Structures / Data Blocks ................................................... 42 5.4.1 General ............................................................................................... 42 5.4.2 Data Block Template ......................................................................... 43 5.4.2.1 Data Block DB37 (4 PROFIsafe modules) ................................... 43 5.4.2.2 Data Block DB38 Template (8 PROFIsafe modules) ................... 44 5.4.2.3 Data Block DB39 Template (32 PROFIsafe modules) ................. 44 5.4.2.4 Data Block DB41 Template (10 PROFIsafe modules) ................. 45 5.4.2.5 Data Block DB101 Template (diagnosis data) .............................. 46 5.5 Function blocks ...................................................................................... 47 5.5.1 FB37 "WAGO_iPar_UDL_4_Mod" .................................................. 47 Contents 5 Application note A114802
5.5.1.1 Block call command Step 7 .......................................................... 47 5.5.1.2 Parameterization before Use ......................................................... 48 5.5.1.3 Function Activation ...................................................................... 48 5.5.2 FB38 "WAGO_iPar_UDL_8_Mod" .................................................. 50 5.5.2.1 Block call command Step 7 .......................................................... 50 5.5.2.2 Parameterization before Use ......................................................... 51 5.5.2.3 Function Activation ...................................................................... 51 5.5.3 FB41 "WAGO_iPar_UDL_10_Mod" ................................................ 53 5.5.3.1 Block call command Step 7 .......................................................... 53 5.5.3.2 Parameterization before Use ......................................................... 54 5.5.3.3 Function Activation ...................................................................... 54 5.5.4 FB39 "WAGO_iPar_UDL_32Mod" .................................................. 56 5.5.4.1 Block call command Step 7 .......................................................... 56 5.5.4.2 Parameterization before Use ......................................................... 56 5.5.4.3 Function Activation ...................................................................... 57 5.5.5 FB40 "WAGO_iPar_State_32_Mod" ................................................ 59 5.5.5.1 Block call command Step 7 .......................................................... 59 5.5.5.2 Parameterization before Use ......................................................... 59 5.5.5.3 Function Activation ...................................................................... 59 5.5.6 FB101 "DiagPROFIsafe_V2_iPar" .................................................... 60 5.5.6.1 Block call command Step 7 .......................................................... 60 5.5.6.2 Parameterization before Use ......................................................... 61 5.5.6.3 Function Activation ...................................................................... 62 5.6 Terms of Use .......................................................................................... 63 5.6.1 Basics ................................................................................................. 63 5.6.1.1 Differences in Implementation ...................................................... 63 5.6.1.2 CPU Communication Resources ................................................... 65 5.6.1.3 Implementation Steps .................................................................... 65 5.6.1.3.1 Specifying Data Block iParameters .......................................... 65 5.6.1.3.2 Function Block Calls ................................................................ 66 5.6.2 Commissioning .................................................................................. 67 5.6.2.1 Create system configuration .......................................................... 67 5.6.2.2 Configuring PROFIsafe Modules ................................................. 68 5.6.2.3 Update system configuration ......................................................... 69 5.6.2.4 Upload iParameters ....................................................................... 69 5.6.3 Troubleshooting ................................................................................. 70 5.6.3.1 Information about FB37, FB38, FB39, FB40, FB41 Error Numbers72 5.6.3.1.1 Status ERROR_FB 16#8001 .................................................... 72 5.6.3.1.2 Status ERROR_FB 16#8040 .................................................... 72 5.6.3.1.3 Status ERROR_FB 16#8080 .................................................... 73 5.6.3.1.4 Status ERROR_FB 16#9000 .................................................... 73 5.6.3.1.5 Status ERROR_FB 16#A000 ................................................... 73 5.6.3.1.6 Status ERROR_FB 16#C000 ................................................... 74 5.6.3.2 Information about communication Error Numbers ....................... 74 5.6.3.2.1 Status error_Com_x 16#8001 .................................................. 74 5.6.3.2.2 Status error_Com_x 16#8002 .................................................. 75 5.6.3.2.3 Status error_Com_x 16#8004 .................................................. 75 5.6.3.2.4 Status error_Com_x 16#8008 .................................................. 75 5.6.3.2.5 Status error_Com_x 16#8010 .................................................. 76 6 Contents Application note A114802 5.6.3.2.6 Status error_Com_x 16#8020................................................... 76 5.6.3.2.7 Status error_Com_x 16#8100................................................... 76 5.6.3.2.8 Status error_Com_x 16#8200................................................... 77 5.6.3.2.9 Status error_Com_x 16#8400................................................... 77 5.6.3.2.10 Status error_Com_x 16#8800................................................... 77 5.6.3.2.11 Status Status error_Com_x 16#C000 ....................................... 78 5.6.3.3 Advice Diagnosis Data at iParameter-DB ..................................... 78 5.6.3.3.1 Diagnosis Information error_info_mod_x ............................ 79 5.6.3.3.2 Diagnosis Information F_Module_mod_x ............................ 79 5.6.3.3.3 Diagnosis Information F_DI_z_mod_x ................................ 79 5.6.3.3.4 Diagnosis Information F_DO_z_mod_x .............................. 79 5.6.3.3.5 Diagnosis Information Reg_xx_mod_x ................................ 79 6 Example with Safety Controller from Siemens ...................................... 80 6.1 Terms of Use .......................................................................................... 80 6.2 Abstract programs and libraries .............................................................. 81 6.2.1 Step 7 V5.5 SP3 ................................................................................. 81 6.2.2 TIA V11 SP2 UP5 ............................................................................. 81 6.2.3 TIA V12 SP1 ..................................................................................... 81 6.3 System Configuration ............................................................................. 82 6.3.1 Hardware Configuration .................................................................... 82 6.3.2 Safety Control .................................................................................... 82 6.3.3 PROFIBUS DP .................................................................................. 83 6.3.3.1 Slave with PROFIBUS DP address 6............................................ 83 6.3.3.2 Slave with PROFIBUS DP address 9............................................ 85 6.3.3.3 Slave with PROFIBUS DP address 13.......................................... 88 6.3.3.4 Slave with PROFIBUS DP address 17.......................................... 95 6.3.4 PROFINET ........................................................................................ 98 6.3.4.1 "WAGO-750-370" Device ............................................................ 98 6.3.4.2 "WAGO-750-370-1" Device ....................................................... 101 6.3.4.3 "WAGO-750-370-8" Device ....................................................... 105 6.4 Software Structure ................................................................................ 108 6.4.1 Program Structure ............................................................................ 108 6.4.1.1 Cyclic Program Calls OB1 .......................................................... 108 6.4.1.2 Program Calls via Watchdog Alarm OB35 ................................. 108 6.4.1.3 Runtime Group Assignments ...................................................... 109 6.4.2 Defined Interfaces ............................................................................ 110 6.4.2.1 Cyclic Program to the Safety Program ........................................ 110 6.4.2.2 Safety Program to the Cyclic Program ........................................ 110 6.4.2.3 Runtime Group Communication ................................................. 111 6.4.3 Note about Assignment of the Safety Module to Runtime Group ... 112 6.5 Program Functions ................................................................................ 113 6.5.1 Cyclic Application Program ............................................................ 113 6.5.2 Organization Blocks Used ............................................................... 113 6.5.2.1 Watchdog Alarm OB35 .............................................................. 113 6.5.2.2 Watchdog Alarm OB82 .............................................................. 113 6.5.2.3 Watchdog Alarm OB83 .............................................................. 113 6.5.2.4 Watchdog Alarm OB85 .............................................................. 113 6.5.2.5 Watchdog Alarm OB86 .............................................................. 113 Contents 7 Application note A114802
6.5.2.6 Watchdog Alarm OB87 .............................................................. 113 6.5.2.7 Start-up OB100 ........................................................................... 113 6.5.3 Safety Program ................................................................................ 114 6.5.3.1 Function Basis ............................................................................. 114 6.5.3.2 Data Transfer from Standard Program ........................................ 114 6.5.3.3 User Acknowledgement / Reintegration ..................................... 115 6.5.3.4 Evaluation E-Stop Active ........................................................... 116 6.5.3.5 Relay Control .............................................................................. 118 6.5.3.6 Status Displays of the Safety Program ........................................ 119 6.6 Function Activation .............................................................................. 120 6.7 Using iPar Server Option...................................................................... 121 6.7.1 General ............................................................................................. 121 6.7.2 Software Structure iPar Option ........................................................ 121 6.7.2.1 General ........................................................................................ 121 6.7.2.2 Required Block Calls .................................................................. 122 6.7.2.3 Function Calls in FC9 ................................................................. 123 6.7.2.4 Function Calls in FC14 ............................................................... 123 6.7.2.4.1 Call for PROFIBUS-DP Slave 9 ............................................ 123 6.7.2.4.2 Call for PROFINET Device 2 ................................................ 124 6.7.2.4.3 Call for PROFIBUS-DP Slave 13 .......................................... 125 6.7.2.5 Function Calls in FC15 ............................................................... 126 6.7.3 Function Example ............................................................................ 127 6.7.3.1 Check configuration .................................................................... 127 6.7.3.2 iParameter Upload....................................................................... 128 6.7.3.3 iParameter Comparison ............................................................... 130 6.7.3.4 iParameter Download .................................................................. 131 6.7.3.5 Read Diagnosis Data (manual request) ....................................... 133 6.7.3.6 Read Diagnosis Data (automatic read) ........................................ 134 7 References TIA Portal V11 SP2 UP5 ..................................................... 135 7.1 General ................................................................................................. 135 7.1.1 Global library WAGO iPar-Server Option ...................................... 135 7.1.2 Example A114802_TIA_V_11_SP2_UP5_x_x_Bib_5_x .............. 136 7.1.3 Parameterization with TCI interface ................................................ 137 7.1.3.1 TCI CC3 with PROFIBUS-DP ................................................... 137 7.1.3.2 TCI CC2 with PROFINET .......................................................... 139 8 References TIA Portal V12 SP1 ............................................................. 140 8.1 General ................................................................................................. 140 8.1.1 Global library WAGO iPar-Server Option ...................................... 140 8.1.2 Example A114802_TIA_V_V12_SP1_x_x_Bib_5_x .................... 141 8.1.3 Parameterization with TCI interface ................................................ 142 8.1.3.1 TCI CC3 with PROFIBUS-DP ................................................... 142 8.1.3.2 TCI CC2 with PROFINET .......................................................... 144 9 Information about Using Safety Components ...................................... 145 9.1 Safety Light Curtain SOLID 2, Leuze electronic ................................. 145 9.1.1 Electrical connection ....................................................................... 145 9.1.2 Configuring PROFIsafe Module ...................................................... 146 8 Contents Application note A114802 9.2 Safety Position Switch S300, Leuze electronic .................................... 147 9.2.1 Electrical connection........................................................................ 147 9.2.2 Configuring PROFIsafe Module ...................................................... 148 10 Source Directory ...................................................................................... 149 11 Version information ................................................................................ 150 11.1 S7 Library WAGO_iPar_Option .......................................................... 150 11.2 Application Note .................................................................................. 151
Important Notes 9 Application note A114802
1 Important Notes To ensure quick installation and start-up of the units, please carefully read and adhere to the following information and explanations. 1.1 Legal Principles 1.1.1 Copyright This document, including all figures and illustrations contained therein, is subject to copyright protection. Any use of this document that infringes upon the copyright provisions stipulated herein is prohibited. Reproduction, translation, electronic and phototechnical filing/archiving (e.g., photocopying), as well as any amendments require the written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden, Germany. Non-observance will involve the right to assert damage claims. WAGO Kontakttechnik GmbH & Co. KG reserves the right to make any alterations or modifications that serve to increase the efficiency of technical progress. WAGO Kontakttechnik GmbH & Co. KG owns all rights arising from granting patents or from the legal protection of utility patents. Third-party products are always mentioned without any reference to patent rights. Thus, the existence of such rights cannot be excluded. 1.1.2 Personnel Qualification The use of the product detailed in this document is geared exclusively to specialists having qualifications in PLC programming, electrical specialists or persons instructed by electrical specialists who are also familiar with the valid standards. WAGO Kontakttechnik GmbH & Co. KG assumes no liability resulting from improper action and damage to WAGO products and third-party products due to non-observance of the information contained in this document. 1.1.3 Intended Use For each individual application, the components are supplied from the factory with a dedicated hardware and software configuration. Modifications are only admitted within the framework of the possibilities documented in this document. All other changes to the hardware and/or software and the non-conforming use of the components entail the exclusion of liability on part of WAGO Kontakttechnik GmbH & Co. KG. Please send your requests for modified and new hardware or software configurations directly to WAGO Kontakttechnik GmbH & Co. KG. 10 Important Notes Application note A114802 1.2 Scope of Validity This application note is based on the stated hardware and software from the specific manufacturer, as well as the associated documentation. This application note is therefore only valid for the described installation. New hardware and software versions may need to be handled differently. Please note the detailed description in the specific manuals.
Important Notes 11 Application note A114802
1.3 Symbols DANGER
Personal Injury Warning Indicates a high-risk, imminently hazardous situation which, if not avoided, will result in death or serious injury. WARNING
Personal Injury Warning Indicates a moderate-risk, potentially hazardous situation which, if not avoided, could result in death or (serious) injury. CAUTION
Personal Injury Warning Indicates a low-risk, potentially hazardous situation which, if not avoided, could result in slight to moderate injury. NOTICE
Material Damage Warning Indicates a potentially hazardous situation which, if not avoided, may result in damage to property. ESD
Warning of Material Damage Due to Electrostatic Charging Indicates a potentially hazardous situation which, if not avoided, may result in damage to property. Note
Important Note Indicates routines or suggestions for efficient use of equipment and possible software optimizations. The respective device manuals of the components used are to be observed. Information
Note about Additional Information Indicates other information, which is not an integral part of this documentation, such as manual, data sheet, Internet, etc.
12 General Application note A114802 2 General 2.1 Terms of Use DANGER
The examples listed are based exclusively on a test configuration with no reference to any machine or system. To use the PROFIsafe modules in a system, the applicable regulations, standards and safety requirements of the machine are to be observed and implemented.
DANGER
The application note provides additional information about the current manuals of the PROFIsafe modules. In addition, the information contained in the system description for the WAGO IO System is to be observed.
Fig. 1 Screenshot of the WAGO-I/O-SYSTEM design notes General 13 Application note A114802
Fig. 2 Screenshot of the PROFIsafe Module V2 iPar manuals and quickstart guide 14 WAGO-I/O-SYSTEM Basics Application note A114802 3 WAGO-I/O-SYSTEM Basics 3.1 General The modular and fieldbus-independent I/O system WAGO I/O 750/753 supports numerous fieldbus systems. The I/O modules are connected by so-called bus interfaces available in various rating classes depending on the bus system used. To usethe PROFI safe technology, the PROFI BUS DP or PROFI NET industrial bus systems can be used. 3.2 Using the WAGO-I/O-SYSTEM with PROFIBUS DP 3.2.1 General To connect the PROFIBUS DP bus system to the modular WAGO I/O 750/753 I/O system, various bus interfaces are available that differ in their range of performance. To use PROFI safeon the PROFI BUS DP, the 750-333 PROFI BUS DP/V1 bus interface must be used for system implementations. 3.2.2 GSD File 3.2.2.1 Download Internet To configure the modular WAGO-I/O-SYSTEM 750/753, GSD files are used that are available to download from the WAGO homepage in Service area.
Fig. 3 Screenshot of the WAGO homepage Source 1: WAGO homepage as of 12/04/03 WAGO-I/O-SYSTEM Basics 15 Application note A114802
Go to "Quicklinks \ Downloads" to display the following selection:
Fig. 4 Screenshot of the WAGO homepage, Downloads Source 1: WAGO homepage as of 12/04/03 The required GSD file is available under the "WAGO-I/O-SYSTEM 750/753" selection:
Fig. 5 Screenshot of the WAGO homepage, Downloads AUTOMATION Source 1: WAGO homepage as of 12/04/03 16 WAGO-I/O-SYSTEM Basics Application note A114802 0 Fig. 6 Screenshot of the WAGO homepage, WAGO-I/O-SYSTEM 750/753 Source 1: WAGO homepage as of 12/04/03 Note
The GSD files are available from an installation program.
When installing, all Step 7 programs should be closed on the PC to enable trouble free transfer of data.
When using the PROFIsafe Module V2 iPar, the "Professional" installation should be selected. The entries contain the "PRO" extension in the hardware catalogue.
After the "Professional" installation, the GSD files appears as follows within the hardware catalogue of the Step 7 hardware configuration:
Fig. 7 Screenshot of the hardware catalogue, WAGO-GSD PRO selection WAGO-I/O-SYSTEM Basics 17 Application note A114802
3.3 Using the WAGO-I/O-SYSTEM with PROFINET 3.3.1 General To connect the PROFINET bus system to the modular WAGO I/O 750/753 I/O system, various bus interfaces are available that differ in their range of performance. To use PROFI safeon the PROFI NET, the 750-370 PROFI NET I /O bus interface must be used for system implementations. 3.3.2 GSDML file 3.3.2.1 Download Internet To configure the modular WAGO-I/O-SYSTEM 750/753 on the PROFINET, GSDML files are used that are available to download from the WAGO homepage in Service area.
Fig. 8 Screenshot of the WAGO homepage Source 1: WAGO homepage as of 12/04/03
18 WAGO-I/O-SYSTEM Basics Application note A114802 Go to "Quicklinks \ Downloads" to display the following selection:
Fig. 9 Screenshot of the WAGO homepage, Downloads Source 1: WAGO homepage as of 12/04/03 The required GSDML file is available under the "WAGO-I/O-SYSTEM 750/753" selection:
Fig. 10 Screenshot of the WAGO homepage, Downloads AUTOMATION Source 1: WAGO homepage as of 12/04/03 WAGO-I/O-SYSTEM Basics 19 Application note A114802
Fig. 11 Screenshot of the WAGO homepage, WAGO-I/O-SYSTEM 750/753 Source 1: WAGO homepage as of 12/04/03 Note
The GSDML files are "installed" in the hardware configuration of Step 7 "Tools \ Install GSD Files".
To install the GSDM files, please follow the instructions in the Step 7 interface.
20 WAGO-I/O-SYSTEM Basics Application note A114802 3.4 Using the WAGO-I/O-SYSTEM with PROFIsafe
3.4.1 General The PROFIsafe technology is offered as an option for safety controls of the S7 series (Distributed Safety) identified by an "F" in the name of the control. 3.4.2 Required Software Tools The following software tools are required to use the current technologies of PROFIsafe in conjunction with S7 controls: - Basic packet Step 7 V 5.4 SP5 - Extension Distributed Safety V 5.4 SP 5
Information
The software tools specified here represent on the base requirements for using the WAGO PROFIsafe modules. Additional tools may be required based on the control components used. The respective instructions in the device manuals are to be taken into consideration.
3.4.3 Operating Principles Some important information has been compiled to give you a simple introduction to the topic. In addition, you should always read the manual of the safety control used. 3.4.3.1 Safety Program The safety program is created in a safety editor, which is similar to the usual program editor. After creating the safety program, the call path must be implemented based on the CPU requirements. The "Edit safety program" function must be used within the Step 7 interface. WAGO-I/O-SYSTEM Basics 21 Application note A114802
3.4.3.2 "Edit safety program" Function This function must be used in the Step 7 interface to define the system call in conjunction with the F-runtime group and to generate the required collective signature for acceptance and thus operation of the safety program. The following individual steps are required for basic implementation of a safety program: - Add or adapt the F-Runtime group(s) - Add F-CALL in the application program of the CPU (typically in OB35) - Check the fail-safe I/O data block and F-runtime group assignments by "Generate" function - Test and document the implemented functions 3.4.3.3 Fail-safe I/O DB When using PROFIsafe modules in the S7 world, an F periphery DB is created after creating an F module within the hardware configuration. This secure data block contains all required information to execute the required base functions (passivation and depassivation) and to receive diagnostic messages.
:
Fig. 12 Screenshot of the PROFIsafe F-Periphery DB module Source 2 Representation of theF-Periphery DB in Step 7 for PROFIsafe modules (Step 7 V5.4 SP5) 22 WAGO-I/O-SYSTEM Basics Application note A114802 3.4.3.3.1 PASS_ON Manual passivation of the PROFIsafe module by selecting VKE 1 in F-Periphery- DB (e.g. via safety program) Do not forget to reset to VKE 0 via the safety program. As long as PASS_ON = 1, a passivation of the corresponding periphery will be completed. The passivation cannot be disabled using the ACK_NEC and ACK_REI reintegration variables. 3.4.3.3.2 ACK_NEC Using this F-Periphery DB variable, the behaviour of the periphery can be defined after a channel error. ACK_NEC = 0 automatic reintegration after a channel error. ACK_NEC =1 Reintegration is only possible via acknowledgement by the user (ACK_REI must be set to VKE 1) DANGER
The parameterization ACK_NEC = 0 means automatic reintegration of the affected F-Periphery, i.e., automatic error acknowledgement and thus automatic machine start-up.
Information
When starting up the controller, ACK_NEC is automatically set to 1, i.e., the automatic reintegration of the modules must be consciously realized by corresponding programming within the safety program.
3.4.3.3.3 ACK_REI User acknowledgement via positive edge at ACK_REI for reintegration of the F periphery after an error. Note
Acknowledgement is only possible if a reintegration acknowledgement by the user is requested by the affected module via ACK_REQ = 1.
3.4.3.3.4 IPAR_EN Release to accept so-called iParameters from DP standard slaves. This function is not available for the WAGO I/O modules at the moment. For detailed information, see PROFIBUS standard. 3.4.3.3.5 PASS_OUT Indicator that substitute values are sent by the PLC, at least 1 channel was passivated. If passivation is done via PASS_ON = 1, no indication will be made via PASS_OUT (only QBAD is set). 3.4.3.3.6 QBAD Indicator that substitute values are sent by the PLC, at least 1 channel was passivated. Passivation can either be performed independently by the CPU or be activated by the user by setting PASS_ON = 1 in the F-Periphery-DB In any case, indication is done via QBAD. Note
The modules currently work with a module related passivation.
3.4.3.3.7 ACK_REQ System Indicator that the user acknowledgement for the integration of the affected F periphery is required Indication is set by the system as soon as the error has been corrected and acknowledgement by the user is possible. DANGER
By evaluating the information ACK_REQ and QBAD, reintegration can be implemented again by setting the user acknowledgement ACK_REI, i.e., possible automatic machine start-up in case of error.
3.4.3.3.8 IPAR_OK Indicator that new iParameters have been taken over via IPAR_EN = 1. As soon as the IPAR_OK indication is displayed, the IPAR_EN request must be reset so that a reintegration of the affected fail-safe DP normal slave can be performed. This function is not available for the WAGO I/O modules at the moment. 24 WAGO-I/O-SYSTEM Basics Application note A114802 3.4.3.3.9 DIAG Cyclic diagnostic indication of each PROFIsafe module within the F periphery DBs. The information can be used within the normal cyclic application program. Bit Meaning 0 Timeout F periphery is identified 1 F periphery / channel error of F periphery is identified 2 CRC / Sequence number error of F periphery is identified 3 Reserve 4 Timeout of F system is identified 5 Sequence number error of F system is identified 6 CRC error of F system is identified 7 Reserve Fig. 13 Configuration of diagnostic F-Periphery DB
3.4.4 Assignment of the Hardware Configuration to F-Periphery-DB Due to automatic creation of the F-Periphery-DBs for PROFIsafe modules, we have to take a look at the relationship between information within the hardware configuration, naming within the project and symbolic program access to the safety information. 3.4.4.1 Using PROFIBUS-DP The symbol name of the IOs for the safety program is created via the first byte address of the module in the HW Configuration and the DP identification of the device. Example: F00010_196 results from I/O byte 10 and DP ID 196:
Fig. 14 Screenshot showing the hardware configuration of the application note (focus PROFIBUS) Source 3: Screenshot of Step 7 Project V5.4 SP5
Fig. 15 Screenshot of the safety program after creating the HW Configuration Source 3: Screenshot of Step 7 Project V5.4 SP5 When accessing information from the F-Periphery-DBs within the application program, usually the symbolic name is used only, e.g., "F00010_196". QBAD are sent for evaluating substitute values. 26 WAGO-I/O-SYSTEM Basics Application note A114802 3.4.4.2 Using PROFINET The symbol name of the IOs for the safety program is created by the first byte address of the module in the hardware configuration and the symbol name of the device. Example: F00060_753_667_4FDI _4FDO results from I/O byte 60 and module name 753-662 4 FDI / 4 FDO of the hardware configuration:
Fig. 16 Screenshot showing the hardware configuration of the application note (focus PROFINET) Source 3: Screenshot of Step 7 Project V5.4 SP5
Fig. 17 Screenshot of the safety program after creating the HW Configuration Source 3: Screenshot of Step 7 Project V5.4 SP5 Source 3: Screenshot of Step 7 Project V5.4 SP5 When accessing information from the F-Periphery-DBs within the application program, usually the symbolic name is used only, e.g., "F00060_753_667_4FDI_4FDO". QBAD are sent for evaluating substitute values. WAGO-I/O-SYSTEM Basics 27 Application note A114802
3.4.4.3 Note about assigned F-Periphery-DBs In principle, each PROFIsafe module can only be evaluated by one runtime group, i.e., the corresponding F-Periphery-DB of a safety module is assigned fixed to one runtime group. Note
From Distributed Safety V 5.4 SP3, only F-Periphery-DBs are still assigned to a runtime group, whose modules are also used. In other words, at least one read or write access to information of the safety module has to occur.
After creating the safety program, the current assignment of the F-Periphery-DBs to the F-runtime group within the editor can be checked:
Fig. 18 Screenshot of the editor showing "Processing of safety program" Source 3: Screenshot of Step 7 Project V5.4 SP5 Note
All assigned F-Periphery DBs of the safety module of a runtime group can be reintegrated via the FB 219 "F_ACK_GL" centrally for this runtime group.
28 WAGO-I/O-SYSTEM Basics Application note A114802 3.4.5 Data Transfer and Data Access By using common hardware for the standard application and safety program, various data access paths are required to realize a user program. Consequently, the most important information is briefly summarized to provide a certain basis for the following example. 3.4.5.1 Standard Program to the Safety Program
Fig. 19 Excerpt from the online help "Transfer from the Standard User to the Safety Program" Source 4 Online help for Step 7 V5.4 SP 5 and Distributed Safety V 5.4 SP5
3.4.5.2 Safety Program to the Standard Program The following information is available in the online help of Step 7 on this topic:
Fig. 20 Excerpt from the online help "Transfer from the Safety to the Standard User Program" Source 4 Online help for Step 7 V5.4 SP 5 and Distributed Safety V 5.4 SP5 30 WAGO-I/O-SYSTEM Basics Application note A114802 3.5 Required WAGO Tools To create the system configuration and to start up the PROFIsafe modules from WAGO, the tools listed below are required. 3.5.1 WAGO-I/O-CHECK The WAGO-I/O-CHECK V 3.x tool is available from WAGO under the following order numbers: - 759-920 CD with WAGO-I/O-CHECK - 759-302 CD with WAGO-I/O-CHECK and RS232 cable - 759-302/000-923 CD with WAGO-I/O-CHECK and USB cable When installing WAGO-I/O-CHECK, the WAGO Safety Editor 75x V2.0 is installed. 3.5.2 WAGO Safety Editor 75x The WAGO Safety Editor 75x V 2.x is available separately under order number 759-920/000-001 as a CD or for download under "Downloads / Automation / WAGO-I/O System 750/753".
:
Fig. 21 Screenshot of the WAGO homepage, WAGO-I/O-SYSTEM 750/753
4 iPar-Server Technology When using PROFIsafe devices, parameter assignments have to be set within the system configuration of the master, basic GSD / GSDML files (F parameters) and individual device parameters (iParameters) on the device directly.
Fig. 22 Screenshot of the PROFIsafe layer structure Source 5 Homepage of PROFIBUS and PROFINET International (09/09/10) The basic PROFIsafe communication parameters are defined by configuring the F- Parameters. By transferring these parameters to the F-Device each time the F host is started, these definitions are available in each system state and each time an F device is replaced. By assigning the iParameters to the F-Device, the manufacturer is required to provide a corresponding tool to make saving and documenting the iParameters possible. To restore the configuration without an additional tool from the manufacturer, the technology of the iPar-Server has been generally defined.
Fig. 23 Screenshot of the iPar server concept Source 5 Homepage of PROFIBUS and PROFINET International (09/09/10) 32 iPar-Server Technology Application note A114802 A so-called "F_iPar_CRC" of the F-Device is transferred to the engineering tool of the F-Host via the defined sequences when using the technology of the iPar-Server. By transferring this checksum to the F-Host, the configuration of the F-Device can be checked at any system state. In addition, the respective "F_iPar_CRC" of the F-Device is also integrated when creating the total signature of the safety program. When using the WAGO PROFIsafe module V2 iPar, a system configuration appears as follows:
Fig. 24 Screenshot of the system configuration for the WAGO PROFIsafe module V2 iPar To use this technology with safety controls from Siemens, Siemens makes a function block (FB24) available to use the iPar-Server technology. Information
The use of the WAGO PROFIsafe module V2 iPar in conjunction with the iPar-Server (FB24) is described in application note 114801 and is available for general download on the Internet in the Documentation / Application Notes area.
Function Blocks iPar Option WAGO 33 Application note A114802
5 Function Blocks iPar Option WAGO 5.1 Motivation iPar Option The implementation of FB24 from Siemens currently available has to be called up several times in the application program (start-up, diagnostic OB, cyclic program) and therefore, can only be used in a limited manner for small safety controls. Using the defined sequences and functions of the iPar-Server technology, it is possible to provide an application-based solution that only has to be called up in the cyclic application program and that can also be used with small safety controls. Available functions of WAGO iPar-Server option:
Fig. 25 Functions iPar-Server option Co. WAGO
5.2 General With the application solution presented here, it is possible to save the iParameters of the WAGO PROFIsafe module V2 iPar (75x-66x/000-003) via the respective function blocks in the application program. To store data, data blocks are available that can be copied to the offline project during operation after transferring the data. 34 Function Blocks iPar Option WAGO Application note A114802 5.3 Overview of Block Functions To implement the transfer of iParameters for the WAGO PROFIsafe module V2 iPar (75x-66x/000-003), the following function blocks are required. 5.3.1 Setup and Structure of Block Calls The basic structure of the function calls is briefly shown in the following figure:
Fig. 26 Setup and structure of block calls Function Blocks iPar Option WAGO 35 Application note A114802
5.3.2 Implemented Function Blocks 5.3.2.1 Input Function Blocks The function blocks make the following inputs available based on the functions used. 5.3.2.1.1 INIT_FB, Type BOOL This input is used to initialize the function block, which has to be occur under the following conditions: - Reboot or restart of the control - Initialization of the application program - Change to the function block configuration or within the iParameter data block Note
To simplify the application program, a flag should be set in the OB100 start- up that is again reset at the end of the OB1 Use as "Initialization active" on input "INIT_FB".
5.3.2.1.2 RESET, Type BOOL If there is an active error on the function block, the error message is reset on the output of the function block. A reset is only possible if no function request are active via the inputs. A new function request is only possible after a fault condition of a FB is acknowledged via a reset. 5.3.2.1.3 CHECK_CFG, Type BOOL "Check configuration" function request Check of the software parameter settings in terms of the expected PROFIsafe module on the configured I/O address. By activating this function, the following module information is checked: - Module type (661, 662, 666 or 667) - Version (....../000-003) The function is completed without error if the right module is available in the right version with the specified I/O address. 36 Function Blocks iPar Option WAGO Application note A114802 5.3.2.1.4 UPLOAD_REQ, Type BOOL Function request "iParameter UPLOAD" from the module to the control. This function request is used to transfer the iParameters from the PROFIsafe module to the iParameter data block. 5.3.2.1.5 DOWNLOAD_REQ, Type BOOL Function request "iParameter DOWNLOAD" from the control to the module. This function request is used to transfer the iParameters from the iParameter data block to the PROFIsafe module. The function can only be enabled if valid iParameters have been saved in the respective data block. 5.3.2.1.6 COMPARE_REQ, Type BOOL Function request "iParameter compare" between module and control. This function request is used to compare the iParameters saved in the control with the current iParameters in the PROFIsafe module. This function can be used to check whether the content of the data block is still identical to the current iParameter dataset in the respective PROFIsafe module. Note
After transferring the iParameters from the control to the PROFIsafe module, the dataset is checked. If the iParameter data in the control has been manipulated, the module goes into a fault condition and outputs a corresponding diagnostic message.
5.3.2.1.7 DIAG_DATA_REQ_REQ, Type BOOL Function request "read diagnostic data of PROFIsafe module". This function request is used reading the diagnostic data of an PROFIsafe module and transfer the information to the iParameter-DB per module. The diagnostic values are shown at the manual of the PROFIsafe modules at diagnosis of errors.
Function Blocks iPar Option WAGO 37 Application note A114802
5.3.2.1.8 SELECT_MODULE, Type DWORD The respective function request for the available modules is released from this "bit" bar. For this purpose, the following assignment applies:
Fig. 27 Assignment of PROFIsafe modules to SELECT_MODULE From this enable input, more modules can be released than actually available with the block call command. This does not lead to an error message. If a function is requested without selecting a module, the function request is cancelled with a corresponding error message. 5.3.2.1.9 READ_DIAG_DATA, Type BOOL Function request "read diagnostic data of PROFIsafe module automatically". This function request is used reading the diagnostic data of the PROFIsafe modules automatically and transfer the information to the iParameter-DB. The function is activated, if QBAD at the F-Periphery-DB changed from FALSE to TRUE. Note
Only one function request can be made from one input, i.e., if several function requests are made at the same time to one function block, the FB executes none.
To implement external monitoring, the BUSY, DONE and ERROR outputs can be monitored for changes after enabling a function request. To activate a RESET, all function requests must be reset on the respective FB.
38 Function Blocks iPar Option WAGO Application note A114802 5.3.2.1.10 ACT_DATE, Type DATE Current date for use as a time stamp in the iParameter data block e.g., application of the system information in OB1. 5.3.2.1.11 ACT_TIME, Type TIME_OF_DAY Current time for use as a time stamp in the iParameter data block e.g., application of the system information in OB1. 5.3.2.1.12 iPar_DB_NB, Type BLOCK_DB Specification of the data block for storing the iParameters and determination of functions. The required data block structures are defined as follows: - Use of FB37 Data block structure acc. template DB37 - Use of FB38 Data block structure acc. template DB38 - Use of FB39 Data block structure acc. template DB39 - Use of FB41 Data block structure acc. template DB41 Setup and required configurations within the data blocks are listed below. 5.3.2.1.13 MODULES_PLUGGED, Type INT Specification of the actually available modules for the function block call. For the specified number of modules, the corresponding parameters have to be assigned to the inputs ADR_MOD_x, F_PER_DB_MOD_x and TYPE_MOD_x. The input parameter is checked for a value specification > 0 upon activation of a function request, but the currently available system configuration cannot be determined. 5.3.2.1.14 SLAVE_DP_PN, Type BOOL Specification of the bus system used by: - VKE 0 (FALSE) Use with PROFIBUS DP - VKE 1 (TRUE) Use with PROFINET Function block not checked for correct configuration wrong configuration leads to negatively acknowledged function requests. Function Blocks iPar Option WAGO 39 Application note A114802
5.3.2.1.15 ADR_MOD_x, Type INT Specification of the I/O address from the hardware configuration of Step 7 for the respective PROFIsafe module. 5.3.2.1.16 F_PER_DB_MOD_x, Type BLOCK_DB Specification of the F periphery data block for the respective PROFIsafe module. 5.3.2.1.17 TYPE_MOD_x, Type INT Specification of the PROFIsafe module type for the respective module as follows: - 661 75x-661/000-003 - 662 75x-662/000-003 - 666 75x-666/000-003 - 667 75x-667/000-003
Note
For all function requests, the actually available module for configuration within the software (corresponds to the request CHECK_CFG_REQ) is always checked as the first step.
40 Function Blocks iPar Option WAGO Application note A114802 5.3.2.2 Output Function Blocks The function blocks make the following outputs available based on the functions used. 5.3.2.2.1 INIT_OK, Type BOOL Indicator that initialization of the function block successfully performed and read for function requests. 5.3.2.2.2 UPLOAD_ALL_MODULES, Type BOOL Indicator that a valid iParameter dataset has been saved in the control for all specified PROFIsafe modules. 5.3.2.2.3 BUSY, Type BOOL Indicator that function request is being processed, the BUSY output is reset after completion of the function request. 5.3.2.2.4 DONE, Type BOOL Indicator that function request is done without error, reset of the function indicator upon cancellation of the function request. 5.3.2.2.5 DONE_ALL_MODULES, Type BOOL Indicator that function request is done without error for all available PROFIsafe modules of the current configuration, reset of the function indicator upon cancellation of the function request. 5.3.2.2.6 ERROR, Type BOOL Indicator that function request is done with error, reset of the fault condition by resetting the function request and fault acknowledgement via "RESET" input. 5.3.2.2.7 ERROR_FB, Type WORD Indicator of error number in case of error Assignment of the error numbers each within the module documentation in the first network 5.3.2.2.8 ERROR_FB_NB, Type INT Additional indicator for the error number in case of error, support resource for functional problems. Function Blocks iPar Option WAGO 41 Application note A114802
5.3.2.2.9 STATE_FCT_REQ_OK, Type DWORD Indicator of function state via "bit" string consistent with function request via input "SELECT_MODULE", meaning here function request done without error. The following assignment applies:
Fig. 28 Assignment of PROFIsafe modules to output STATE_FCT_REQ_OK If a function request ends without error, the status display is reset after resetting the function request on the FB input. In case of error, the status display is first reset with activation error reset via input "RESET" of the FB. 5.3.2.2.10 STATE_FCT_REQ_ERROR, Type DWORD Indicator of function state via "bit" string consistent with function request via input "SELECT_MODULE", meaning here function request done with error. The following assignment applies:
Fig. 29 Assignment of PROFIsafe modules to output STATE_FCT_REQ_ERROR In case of error, the status display is only cleared after activation error reset via input "RESET" of the FB. 5.3.2.2.11 QBAD_ACTIVE, Type BOOL Indicator that at least one PROFIsafe module outputs substitute values Information by evaluating the respective F-Periphery-DB. 5.3.2.2.12 ACK_REQ_ACTIVE, Type BOOL Indicator that at least one PROFIsafe module requires a user acknowledgement Information by evaluating the respective F-Periphery-DB. 42 Function Blocks iPar Option WAGO Application note A114802 5.4 Defined Data Structures / Data Blocks To store the iParameter datasets within the control and to save current states, corresponding data block structures are defined. 5.4.1 General The defined data blocks are divided into 3 areas: x.x versionInfo_1 memory data block header : : x.x fctReqTimeout : : x.x typ_module_1 configuration data : : x.x system information system information : : x.x data storage module module parameter : iParameter / diagnosis data Fig. 30 Overview of data block structure, general
Note
Data blocks DB37, DB38, DB39 and DB41 are to be used as a "template", i.e., when creating an application, these data blocks are created under a new DB number and the required parameterizations made in data word area 0 and 6.
Note
When installing FB37, FB38, FB39 or FB41, the default settings within the iParameter data block data word 0, 2 and 6 are checked and if a default setting is incorrect, the function block goes into the fault condition "W#16#C000", which cannot be acknowledged.
Function Blocks iPar Option WAGO 43 Application note A114802
5.4.2 Data Block Template 5.4.2.1 Data Block DB37 (4 PROFIsafe modules) When using function block FB37 (or copies thereof), a data block of the format DB37 must be used for data archiving of the iParameters. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 37 using FB37 -> "37" 2.0 versionInfo_2 W#16#500 version DB structure 400 6.0 fctReqTimeout 6000 watchdog timing function request Fig. 31 Data block header DB37 settings Note
A counter is implemented to monitor the internal module functions. The default value for monitoring is saved in data word 6 and is calculated as follows:
DW6 = 30.000ms / average cycle time of the PLC
Ex. DW6 = 30.000ms / 5 ms = 6000
No value less than 30s should be assigned. An extension of the time may be required based on the application size.
Note
Dont change the data block version information at address 2 -> necessary information for function block about structure data block.
44 Function Blocks iPar Option WAGO Application note A114802 5.4.2.2 Data Block DB38 Template (8 PROFIsafe modules) When using function block FB38 (or copies thereof), a data block of the format DB38 must be used for data archiving of the iParameters. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 38 using FB38 -> "38" 2.0 versionInfo_2 W#16#500 version DB structure 400 6.0 fctReqTimeout 6000 watchdog timing function request Fig. 32 Data block header DB38 settings Note
For details about calculating "fctReqTimeout", see DB37.
5.4.2.3 Data Block DB39 Template (32 PROFIsafe modules) When using function block FB39 (or copies thereof), a data block of the format DB39 must be used for data archiving of the iParameters. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 39 using FB39 -> "39" 2.0 versionInfo_2 W#16#500 version DB structure 400 6.0 fctReqTimeout 6000 watchdog timing function request Fig. 33 Data block header DB39 settings Note
For details about calculating "fctReqTimeout", see DB37.
Function Blocks iPar Option WAGO 45 Application note A114802
In contrast to the implementation of FB37 and FB38, all required module data must be entered in DB39 from data word 8 when using FB39: address name value 8.0 maxModules >= 1 number used PROFIsafe Module 10.0 type_module_1 ____ used module type (661 / 662 / 666 / 667) 12.0 adr_module_1 ____ I/O address module from HC-Config (start address I/O field) 14.0 bussystem_mod_1 ____ used bus system (0 = PROFIBUS DP / 1 = PROFINET) : : : : 196.0 type_module_32 ____ used module type (661/662/663/666/667) 198.0 adr_module_32 ____ I/O address module from HC-Config (start address I/O field) 200.0 bussystem_mod_32 ____ used bus system (0 = PROFIBUS DP / 1 = PROFINET) Fig. 34 Configuration data DB39 settings
5.4.2.4 Data Block DB41 Template (10 PROFIsafe modules) When using function block FB41 (or copies thereof), a data block of the format DB41 must be used for data archiving of the iParameters. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 41 using FB41 -> "41" 2.0 versionInfo_2 W#16#500 version DB structure 400 6.0 fctReqTimeout 6000 watchdog timing function request Fig. 35 Data block header DB41 settings Note
For details about calculating "fctReqTimeout", see DB37.
46 Function Blocks iPar Option WAGO Application note A114802 5.4.2.5 Data Block DB101 Template (diagnosis data) When using function block FB101 (or copies thereof), a data block of the format DB101 must be used for data archiving of the diagnosis data. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 101 using FB101 -> "101" 2.0 versionInfo_2 W#16#100 version DB structure 100 6.0 fctReqTimeout 6000 watchdog timing function request 8.0 dsvLength 20 Dataset length of circular storage Fig. 36 Data block header DB101 settings Note
For details about calculating "fctReqTimeout", see DB37.
Function Blocks iPar Option WAGO 47 Application note A114802
5.5 Function blocks 5.5.1 FB37 "WAGO_iPar_UDL_4_Mod" This function block implements storage of the iParameters of maximum 4 PROFIsafe modules in one slave and displays the current status of the QBAD and ACK_REQ signals of the PROFIsafe modules used. 5.5.1.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 37 Screenshot of FB37 "WAGO_iPar_UDL_4_Mod" V5.x 48 Function Blocks iPar Option WAGO Application note A114802 5.5.1.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value ACT_DATE actual system date ACT_TIME actual system time iPar_DB_Number data block used for storage iParameter (template data block DB37) MODULES_PLUGGED 1 4 number used PROFIsafe modules at slave SLAVE_DP_PN FALSE TRUE information used bus system at slave FALSE = PROFIBUS DP / TRUE = PROFINET ADR_MOD_1 I/O address PROFIsafe module 1 F_PER_DB_MOD_1 data block F-Periphery-DB PROFIsafe module 1 TYPE_MOD_1 661/662/663/666/667 module type PROFIsafe module 1 : : : ADR_MOD_4 I/O address PROFIsafe module 4 F_PER_DB_MOD_4 data block F-Periphery-DB PROFIsafe module 4 TYPE_MOD_4 661/662/663/666/667 I/O address PROFIsafe module 4 Fig. 38 Parameterization of inputs FB37 V5.x
Note
Before activating the first function request, please check each required parameterization within the iParameter data blocks (DBW0, DBW2, DBW6). Only iParameter data blocks of version 5.x are suitable for use. Used modules are parameterized from module 1 without spares:
5.5.1.3 Function Activation After configuring and initializing the function block, the function can be activated. Before activating a function request, the respective modules must be selected from the "SELECT_MODULE" input, assignment bit orientation. After activating a function request, the "BUSY" output switches to TRUE and displays the activity of the FB. The current function feedback in terms of the available PROFIsafe modules can be evaluated on the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" outputs during execution and while the function request is pending. Function Blocks iPar Option WAGO 49 Application note A114802
After completing the function request, the following module states can be reached: Output "DONE" = TRUE - Function request done without error - "STATE_FCT_REQ_OK" shows processed function request Output "DONE" and "DONE_ALL_MODULES" = TRUE - Function request done without error - Function request was executed for all available modules - "STATE_FCT_REQ_OK" shows processed function request Output "ERROR" = TRUE - Function request done with error - "STATE_FCT_REQ_OK" / "STATE_FCT_REQ_ERROR" show processed function requests The "STATE_FCT_REQ_OK" status displays are reset by resetting the function request during error-free processing. In case of error, the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" status displays remain active until activation of a "RESET".
50 Function Blocks iPar Option WAGO Application note A114802 5.5.2 FB38 "WAGO_iPar_UDL_8_Mod" This function block implements storage of the iParameters of maximum 8 PROFIsafe modules in one slave and displays the current status of the QBAD and ACK_REQ signals of the PROFIsafe modules used. 5.5.2.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 39 Screenshot of FB38 "WAGO_iPar_UDL_8_Mod" V5.x Function Blocks iPar Option WAGO 51 Application note A114802
5.5.2.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value ACT_DATE actual system date ACT_TIME actual system time iPar_DB_Number data block used for storage iParameter (template data block DB38) MODULES_PLUGGED 1 8 number used PROFIsafe modules at slave SLAVE_DP_PN FALSE TRUE information used bus system at slave FALSE = PROFIBUS DP / TRUE = PROFINET ADR_MOD_1 I/O address PROFIsafe module 1 F_PER_DB_MOD_1 data block F-Periphery-DB PROFIsafe module 1 TYPE_MOD_1 661/662/663/666/667 module type PROFIsafe module 1 : : : ADR_MOD_8 I/O address PROFIsafe module 8 F_PER_DB_MOD_8 data block F-Periphery-DB PROFIsafe module 8 TYPE_MOD_8 661/662/663/666/667 I/O address PROFIsafe module 8 Fig. 40 Parameterization of inputs FB38
Note
Before activating the first function request, please check each required parameterization within the iParameter data blocks (DBW0, DBW2, DBW6). Only iParameter data blocks of version 5.x are suitable for use. Used modules are parameterized from module 1 without spares:
5.5.2.3 Function Activation After configuring and initializing the function block, the function can be activated. Before activating a function request, the respective modules must be selected from the "SELECT_MODULE" input, assignment bit orientation. After activating a function request, the "BUSY" output switches to TRUE and displays the activity of the FB. The current function feedback in terms of the available PROFIsafe modules can be evaluated on the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" outputs during execution and while the function request is pending. 52 Function Blocks iPar Option WAGO Application note A114802 After completing the function request, the following module states can be reached: Output "DONE" = TRUE - Function request done without error - "STATE_FCT_REQ_OK" shows processed function request Output "DONE" and "DONE_ALL_MODULES" = TRUE - Function request done without error - Function request was requested for all available modules - "STATE_FCT_REQ_OK" shows processed function request Output "ERROR" = TRUE - Function request done with error - "STATE_FCT_REQ_OK" / "STATE_FCT_REQ_ERROR" show processed function requests The "STATE_FCT_REQ_OK" status displays are reset by resetting the function request during error-free processing. In case of error, the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" status displays remain active until activation of a "RESET". Function Blocks iPar Option WAGO 53 Application note A114802
5.5.3 FB41 "WAGO_iPar_UDL_10_Mod" This function block implements storage of the iParameters of maximum 10 PROFIsafe modules in one slave and displays the current status of the QBAD and ACK_REQ signals of the PROFIsafe modules used. 5.5.3.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 41 Screenshot of FB41 "WAGO_iPar_UDL_10_Mod" V5.x 54 Function Blocks iPar Option WAGO Application note A114802 5.5.3.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value ACT_DATE actual system date ACT_TIME actual system time iPar_DB_Number data block used for storage iParameter (template data block DB41) MODULES_PLUGGED 1 10 number used PROFIsafe modules at slave SLAVE_DP_PN FALSE TRUE information used bus system at slave FALSE = PROFIBUS DP / TRUE = PROFINET ADR_MOD_1 I/O address PROFIsafe module 1 F_PER_DB_MOD_1 data block F-Periphery-DB PROFIsafe module 1 TYPE_MOD_1 661/662/663/666/667 module type PROFIsafe module 1 : : : ADR_MOD_10 I/O address PROFIsafe module 10 F_PER_DB_MOD_10 data block F-Periphery-DB PROFIsafe module 10 TYPE_MOD_10 661/662/663/666/667 I/O address PROFIsafe module 10 Fig. 42 Parameterization of inputs FB38
Note
Before activating the first function request, please check each required parameterization within the iParameter data blocks (DBW0, DBW2, DBW6). Only iParameter data blocks of version 5.x are suitable for use. Used modules are parameterized from module 1 without spares:
5.5.3.3 Function Activation After configuring and initializing the function block, the function can be activated. Before activating a function request, the respective modules must be selected from the "SELECT_MODULE" input, assignment bit orientation. After activating a function request, the "BUSY" output switches to TRUE and displays the activity of the FB. The current function feedback in terms of the available PROFIsafe modules can be evaluated on the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" outputs during execution and while the function request is pending. Function Blocks iPar Option WAGO 55 Application note A114802
After completing the function request, the following module states can be reached: Output "DONE" = TRUE - Function request done without error - "STATE_FCT_REQ_OK" shows processed function request Output "DONE" and "DONE_ALL_MODULES" = TRUE - Function request done without error - Function request was requested for all available modules - "STATE_FCT_REQ_OK" shows processed function request Output "ERROR" = TRUE - Function request done with error - "STATE_FCT_REQ_OK" / "STATE_FCT_REQ_ERROR" show processed function requests The "STATE_FCT_REQ_OK" status displays are reset by resetting the function request during error-free processing. In case of error, the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" status displays remain active until activation of a "RESET". 56 Function Blocks iPar Option WAGO Application note A114802 5.5.4 FB39 "WAGO_iPar_UDL_32Mod" This function block implements storage of the iParameters of maximum 32 PROFIsafe modules in one application. 5.5.4.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 43 Screenshot of FB39 "WAGO_iPar_UDL_32_Mod"V5.x
5.5.4.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value ACT_DATE actual system date ACT_TIME actual system time iPar_DB_Number data block used for storage iParameter (template data block DB39) Fig. 44 Parameterization of inputs FB39
Function Blocks iPar Option WAGO 57 Application note A114802
In contrast to the use of FB37 and FB38, the module data of the PROFIsafe modules used and the number of modules used must be specified in the iParameter data block when using FB39: address name value 8.0 maxModules >= 1 number used PROFIsafe Module 10.0 type_module_1 ____ used module type (661 / 662 / 666 / 667) 12.0 adr_module_1 ____ I/O address module from HC-Config (start address I/O field) 14.0 bussystem_mod_1 ____ used bus system (0 = PROFIBUS DP / 1 = PROFINET) : : : : 196.0 type_module_32 ____ used module type (661/662/663/666/667) 198.0 adr_module_32 ____ I/O address module from HC-Config (start address I/O field) 200.0 bussystem_mod_32 ____ used bus system (0 = PROFIBUS DP / 1 = PROFINET) Fig. 45 Configuration data DB39 settings V5.x After specifying and checking this configuration data, the function block can be used. Note
Before activating the first function request, please check each required parameterization within the iParameter data blocks (DBW0, DBW2, DBW6). Only iParameter data blocks of version 5.x are suitable for use. Used modules are parameterized from module 1 without spares:
5.5.4.3 Function Activation After configuring and initializing the function block, the function can be activated. Before activating a function request, the respective modules must be selected from the "SELECT_MODULE" input, assignment bit orientation. After activating a function request, the "BUSY" output switches to TRUE and displays the activity of the FB. The current function feedback in terms of the available PROFIsafe modules can be evaluated on the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" outputs during execution and while the function request is pending. 58 Function Blocks iPar Option WAGO Application note A114802 After completing the function request, the following module states can be reached: Output "DONE" = TRUE - Function request done without error - "STATE_FCT_REQ_OK" shows processed function request Output "DONE" and "DONE_ALL_MODULES" = TRUE - Function request done without error - Function request was requested for all available modules - "STATE_FCT_REQ_OK" shows processed function request Output "ERROR" = TRUE - Function request done with error - "STATE_FCT_REQ_OK" / "STATE_FCT_REQ_ERROR" show processed function requests The "STATE_FCT_REQ_OK" status displays are reset by resetting the function request during error-free processing. In case of error, the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" status displays remain active until activation of a "RESET".
Function Blocks iPar Option WAGO 59 Application note A114802
5.5.5 FB40 "WAGO_iPar_State_32_Mod" From this function block, the F-Periphery-DB from 32 modules can be evaluated and the current status of "QBAD" and "ACK_REQ" can be easily determined for all modules. FB40 is used as a possible AddOn when using FB39. 5.5.5.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 46 Screenshot of FB40 "WAGO_iPar_State_32_Mod" V5.x 5.5.5.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value iPar_DB_Number data block used for storage iParameter (template data block DB38) F_PER_DB_MOD_1 data block F-Periphery-DB PROFIsafe module 1 : : : F_PER_DB_MOD_32 data block F-Periphery-DB PROFIsafe module 32 Fig. 47 Parameterization of inputs FB40 5.5.5.3 Function Activation The block starts automatically after initialization is complete and evaluates one PROFIsafe module in each cycle. This information is saved in the iParameter data block and is available for further evaluation. 60 Function Blocks iPar Option WAGO Application note A114802 5.5.6 FB101 "DiagPROFIsafe_V2_iPar" This function block offers the storage of diagnosis data of maximum 12 PROFIsafe modules per function block call. The function block is used for fault tracing, if the diagnosis function disabled at the system configuration. 5.5.6.1 Block call command Step 7 The function block appears as follows when called up within Step 7:
Fig. 48 Screenshot of FB101 "DiagPROFIsafe_V2_iPar V1.x Function Blocks iPar Option WAGO 61 Application note A114802
5.5.6.2 Parameterization before Use Before using the function block, the following input connections must be made based on the existing system configuration: input value ACT_DATE actual system date ACT_TIME actual system time Storage_DB_NB Data block for storage diagnosis data (template DB101) MODULES_PLUGGED 1 12 MODULES_PLUGGED ADR_MOD_1 I/O address PROFIsafe module 1 F_PER_DB_MOD_1 data block F-Periphery-DB PROFIsafe module 1 : : F_PER_DB_MOD_12 data block F-Periphery-DB PROFIsafe module 12 Fig. 49 Parameterization of inputs FB101 When using function block FB101 (or copies thereof), a data block of the format DB101 must be used for data archiving of the diagnosis data. After creating a corresponding data block, the following data settings are to be checked within the data block: address name value 0.0 versionInfo_1 101 using FB101 -> "101" 2.0 versionInfo_2 W#16#100 version DB structure 100 6.0 fctReqTimeout 6000 watchdog timing function request 8.0 dsvLength 20 Dataset length of circular storage Fig. 50 Data block header DB101 settings After specifying and checking this configuration data, the function block can be used. 62 Function Blocks iPar Option WAGO Application note A114802 5.5.6.3 Function Activation After configuring and initializing the function block, the function can be activated. The function request INT_FB, RESET, CHECK_CFG_REQ, DIAG_DATA_REQ and SELECT_MODULE works like FB37, FB38, FB39, FB41. The function request READ_DIAG_DATA_FILL reads the diagnosis data automatically until the circular storage is full -> indication output END_OF_STORAGE. In this case, please reset the circular storage with input RESET_STORAGE. After completing the function request, the following module states can be reached: Output "DONE" = TRUE - Function request done without error - "STATE_FCT_REQ_OK" shows processed function request Output "ERROR" = TRUE - Function request done with error - "STATE_FCT_REQ_OK" / "STATE_FCT_REQ_ERROR" show processed function requests The "STATE_FCT_REQ_OK" status displays are reset by resetting the function request during error-free processing. In case of error, the "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" status displays remain active until activation of a "RESET".
Function Blocks iPar Option WAGO 63 Application note A114802
5.6 Terms of Use 5.6.1 Basics Before using or creating an application on this subject, the following points should be defined: - Maximum number of PROFIsafe modules in the application - Implementation with reference to the PROFIsafe modules for one slave (use FB37 / FB38 / FB41) - Implementation without reference to the PROFIsafe modules for one slave (use FB39) 5.6.1.1 Differences in Implementation Use of FB37, FB38 or FB41 with reference to a slave
Fig. 51 Software structure "with slave reference" - One FB37, FB38 or FB41 call is required per slave - One iParameter data block is required per slave 64 Function Blocks iPar Option WAGO Application note A114802 Use of FB39 without reference to a slave
Fig. 52 Software structure "without slave reference" - One FB39 for maximum 32 PROFIsafe modules - One iParameter data block per FB39 call Use of FB101 read diagnosis data PROFIsafe modules
Fig. 53 Software structure read diagnosis data with FB101" - One FB101 for maximum 12 PROFIsafe modules - One dataset for diagnosis data per FB101 necessary Function Blocks iPar Option WAGO 65 Application note A114802
5.6.1.2 CPU Communication Resources The block functions for communication with the PROFIsafe modules are based on the system function blocks SFB52 "RDREC" and SFB53 "WRREC" of the S7 CPU. With the current implementation of these functions within the CPU, these need one "communication resource" within the CPU for each activation. For each CPU, there is a maximum possible number of simultaneous communication resources that should not be exceeded by the application program and all other communication (online functions, etc.). More information about this topic is available in the current manuals of the respective S7 CPU. Note
The individual function blocks (FB37 / FB38 / FB39 / FB41) should be activated sequentially to avoid exceeding the maximum possible communication resources within the S7 CPU through simultaneous function activations.
5.6.1.3 Implementation Steps
5.6.1.3.1 Specifying Data Block iParameters As the first step before implementation, the required data blocks for storing the iParameters should be specified. To create the data blocks, DB37, DB38, DB39 or DB41 should be copied according to the application requirement and added to the project under a new name. After adding the data blocks, the information in data word 0, 2 and 6 should be immediately checked according to the specifications.
template data block word 0 data block word 2 data block word 6
DB 37 37 W#16#500 6000
DB 38 38 W#16#500 6000
DB 39 39 W#16#500 6000
DB41 41 W#16#500 6000 Fig. 54 Parameterization requirement of the iParameter data block header 66 Function Blocks iPar Option WAGO Application note A114802 5.6.1.3.2 Function Block Calls To use the function blocks, a cyclical call must be implemented in OB1. When adding the function blocks, a separate instance data block must be created for each call. A corresponding flag with the following properties must be attached to the "INIT_FB" input of the function blocks: - Reboot or restart of the control - Initialization of the application program - Change to the function block configuration or within the iParameter data block Note
To simplify the application program, a flag should be set in the OB100 start- up that is again reset at the end of the OB1 Use in the application program as "Initialization active" on input "INIT_FB". .
When using function blocks FB37 and FB38, the "Properties" of the PROFIsafe modules are each specified on the inputs of the FBs. When using FB39, these values are to be stored in the iParameter data block directly.
Function Blocks iPar Option WAGO 67 Application note A114802
5.6.2 Commissioning Note
The following steps and workflows represent only one possible path, which may differ based on the available system configuration.
5.6.2.1 Create system configuration To create the system configuration, GSD files are required that are provided in various version for installation: - Standard installation - Professional installation When using the PROFIsafe module V2 iPar, the professional installation must be selected to maintain the error texts within the online diagnostics of the hardware configuration. After correct and successful installation, the GSD entries have the "PRO" extension as the identifier:
Fig. 55 Screenshot of the hardware catalogue, WAGO-GSD PRO selection To use the parameterization via PROFIBUS DP using TCI CC3, a current system configuration must be created and transferred to the CPU. The following steps are required: - Usage of GSD entry for PROFIsafe module with expansion iPar - Settings per PROFIsafe module within the hardware configuration - Specification of the PROFIsafe address - Specification F_iPar_CRC per PROFIsafe module with 0 68 Function Blocks iPar Option WAGO Application note A114802
Fig. 56 Workflow to create the system configuration After transferring the system configuration and restarting the control, all PROFIsafe modules go into the so-called test mode Display via LED H green 2 Hz flashing. In this state, the PROFIsafe modules are passivated; depassivation only occurs after parameterization of the PROFIsafe modules and application of the valid F_iPar_CRC within the hardware configuration. 5.6.2.2 Configuring PROFIsafe Modules After transferring the system configuration, the PROFIsafe modules are configured using Safety Editor 75x from WAGO. Within the Safety Editor, the F_iPar_CRC is output after saving a valid iParameter dataset in the PROFIsafe module. This checksum must be entered in the hardware configuration for each PROFIsafe module.
Fig. 57 PROFIsafe Module V2 iPar configuration workflow Function Blocks iPar Option WAGO 69 Application note A114802
5.6.2.3 Update system configuration By configurating the PROFIsafe modules and applying the respective F_iPar_CRC to the hardware configuration of the application, an updated system configuration can now be created and transferred to the control:
Fig. 58 Workflow to update the system configuration 5.6.2.4 Upload iParameters When restarting a safety control, whether the F_iPar_CRC of a PROFIsafe device was zero before the system restart and whether it is not equal to zero after the restart is always checked. Should this state be detected on a PROFIsafe device, an upload request is made by the PROFIsafe device to the safety control. If no parameters are uploaded by the iPar server within 4 minutes, a corresponding diagnostic message is activated by the device concerned. To start the iParameter transfer in this application example, the upload is activated from the "UPLOAD_REQ" input on each function block. After the iParameters have been transferred to the safety control, the following steps are to be carried out to apply the parameters to the offline project: - Open block display online - Mark iParameter data blocks - Right-click to activate "Load target system in PG" function - Close online block view 70 Function Blocks iPar Option WAGO Application note A114802 The iParameter data blocks are now available offline in the S7 project and can also be transferred to the control at the next program download. Note
When uploading the iParameters for the first time when first commissioning the control, there must be a power on reset of the entire system to clear the CPU diagnostic messages. Future diagnostic messages on "Upload or download request" can simply be cleared by activating the respective function.
5.6.3 Troubleshooting If an error message occurs after activating a function request, a simple error analysis can be performed as described below. The function blocks FB37, FB38, FB39 and FB40 output a corresponding error message on their error outputs directly The current assignment can be found in the block comments in network 1.
Fig. 59 Screenshot of the error messages for FB39 V5.x Function Blocks iPar Option WAGO 71 Application note A114802
After executing a function request, module-related function feedback occurs via the "STATE_FCT_REQ_OK" and "STATE_FUNCTION_REQ_ERROR" outputs with the following assignment:
Fig. 60 Assignment of "STATE_FCT_REQ_OK" and "STATE_FCT_REQ_ERROR" From the state of the individual modules, the respective error number can now be read in the iParameter data block used:
Fig. 61 Screenshot of the error messages for iParameter DB module 1 The following error states are currently defined for communication:
Fig. 62 Screenshot of the error messages for FB39 V 5.x 72 Function Blocks iPar Option WAGO Application note A114802 5.6.3.1 Information about FB37, FB38, FB39, FB40, FB41 Error Numbers The following information refers to the error messages on the ERROR_FB output of the function blocks FB37, FB38, FB39, FB40, FB41 and FB101. 5.6.3.1.1 Status ERROR_FB 16#8001 "Step counter not in the valid range" The internal step counter for implementing the function requests is not in the expected range. Solution: - Check whether the application program is overwriting the content of the instance data block of the FB call. - Check software structure and block calls Are instance DBs assigned twice - Use the "Edit \ Check block inconsistency" function to check block inconsistency in the project.
5.6.3.1.2 Status ERROR_FB 16#8040 "Function request communication active" With a communication function request, an error occurred Details are available in the iPar DBs for the respective module The module affected can be determined from the STATE_FCT_REQ_ERROR output. Solution: - Read the communication error message for the module affected and check details in the chapter below.
Function Blocks iPar Option WAGO 73 Application note A114802
5.6.3.1.3 Status ERROR_FB 16#8080 "Error function request from SELECT_MODULE input SELECT_MODULE = 0 // Module selection not possible" Whether a module was selected from the SELECT_MODULE input or whether the specified module selection led to a function activation in the FB is checked when activating a function request. Solution: - Before activating the function request, the SELECT_MODULE input should be connected:
Default 16#FFFF_FFFF Default all possible modules Default 16#xxxx_xxxx Default required modules
5.6.3.1.4 Status ERROR_FB 16#9000 "Error synchronisation FB39 FB40 read diagnostic data The synchronization between FB39 and FB40 to provide the function READ_DIAG_DATA and DIAG_DATA_REQ stopped with an error. Solution: - Check the parameterization of FB39 and FB40
- Check structure of iParameter-DB is equal to template DB39 V4.0
5.6.3.1.5 Status ERROR_FB 16#A000 "Input MODULES_PLUGGED = 0 -> incorrect default" When starting the function block, an incorrect default on the MODULES_PLUGGED input was detected. Solution: - Adjust MODULES_PLUGGED input and then execute FB initialization again. 74 Function Blocks iPar Option WAGO Application note A114802 5.6.3.1.6 Status ERROR_FB 16#C000 "wrong configuration / structure iPar DB for applications" Within the iParameter data block, the content DW0, DW2 and DW6 content does not match the required parameterizations in order to execute the function block. Solution: - Check the required default value in the iParameter data block.
5.6.3.2 Information about communication Error Numbers The information listed below refers to the communication error messages each stored in the iPar DB for the respective module.
Fig. 63 Screenshot of the error messages for iParameter DB module 1
5.6.3.2.1 Status error_Com_x 16#8001 "Step counter not in the valid range" The internal step counter for implementing the function requests is not in the expected range. Solution: - Check whether the application program is overwriting the content of the instance data block of the FB call. - Check software structure and block calls Are instance DBs assigned twice - Use the "Edit \ Check block inconsistency" function to check block inconsistency in the project.
Function Blocks iPar Option WAGO 75 Application note A114802
5.6.3.2.2 Status error_Com_x 16#8002 "Configuration error CHECK_CFG" When checking the module type in the application program for the module actually available, an error was identified. Solution: - Check the software specifications for module type and I/O address. - Check the PROFIsafe module used for the correct variant (75x-66x/000- 003) from the module labelling. 5.6.3.2.3 Status error_Com_x 16#8004 "Required module type not implemented" The specified module type for the function request does not match the modules currently possible (661 / 662 / 667). Solution: - Check the parameterization for the module type.
5.6.3.2.4 Status error_Com_x 16#8008 "Error comparison function" A difference was identified when comparing the iParameter data between the selected PROFIsafe module and the data of the iPar DB As additional information, the parameter number is saved in the iPar DB under error_nb_Com_x. Solution: - Activate an upload again to save the current iParameters in the iPar DB of the application program. - Apply the iPar DB with current iParameters of the PROFIsafe modules from the online project to the offline project.
76 Function Blocks iPar Option WAGO Application note A114802 5.6.3.2.5 Status error_Com_x 16#8010 "Function selection Download without valid iParameters in the control" The DOWNLOAD_REQ function request for the PROFIsafe module was requested although still not iParameters are available in the iPar DB of the application. Solution: - Execute UPLOAD_REQ for PROFIsafe module to transfer iParameters to iPar DB. - Apply the iPar DB with current iParameters of the PROFIsafe modules from the online project to the offline project.
5.6.3.2.6 Status error_Com_x 16#8020 "Function selection Compare without valid iParameters in the control" The COMPARE_REQ function request for the PROFIsafe module was requested although still not iParameters are available in the iPar DB of the application. Solution: - Execute UPLOAD_REQ for PROFIsafe module to transfer iParameters to iPar DB. - Apply the iPar DB with current iParameters of the PROFIsafe modules from the online project to the offline project.
5.6.3.2.7 Status error_Com_x 16#8100 "Error SFB53 call" The internal SFB53 call was ended with an error message, the ERROR output of SFB53 is stored in the iPar DB for the respective module under state_SFB53a_x and state_SFB53b_x. Solution: - Read error message SFB53 from iPar DB. - Open online documentation Step 7 SFB53 and determine cause of error. Function Blocks iPar Option WAGO 77 Application note A114802
5.6.3.2.8 Status error_Com_x 16#8200 "Error SFB52 call" The internal SFB52 call was ended with an error message, the ERROR output of SFB52 is stored in the iPar DB for the respective module under state_SFB52a_x and state_SFB52b_x. Solution: - Read error message SFB52 from iPar DB. - Open online documentation Step 7 SFB52 and determine cause of error.
5.6.3.2.9 Status error_Com_x 16#8400 "Timeout SFB53 call" No response of SFB53 after time -> no reaction of system function SFB53 Solution: - Check function of SFB53 - Check communication settings of PLC - Check settings timeout at iPar-DB DW 6
5.6.3.2.10 Status error_Com_x 16#8800 "Timeout SFB52 call" No response of SFB52 after time -> no reaction of system function SFB52 Solution: - Check function of SFB52 - Check communication settings of PLC - Check settings timeout at iPar-DB DW 6
78 Function Blocks iPar Option WAGO Application note A114802 5.6.3.2.11 Status Status error_Com_x 16#C000 "wrong configuration / structure iPar DB for applications" Within the iParameter data block, the content DW0, DW2 and DW6 content does not match the required parameterizations in order to execute the function block. Solution: - Check the required default value in the iParameter data block.
5.6.3.3 Advice Diagnosis Data at iParameter-DB With library version 4.0, the diagnosis data of the PROFIsafe modules are stored at the iParameter-DB. The structure of the iParameter-DB is changed per module to provide the storage of the information per module:
Abb. 64 Screenshot structure diagnosis data iParameter-DB All read functions are stored with an time stamp per module. Function Blocks iPar Option WAGO 79 Application note A114802
5.6.3.3.1 Diagnosis Information error_info_mod_x Detailed information about the state of the values at the iParameter-DB per module: 16#W#0000 Error indication at iParameter_DB based on last read request 16#W#0001 Feedback manual data request no diagnosis values available indication is shown up to next function request
Feedback automatic data request no diagnosis values available module passivated, but no error at PROFIsafe module active indication reset, if QBDA change to FALSE 16#W#8001 Feedback automatic data request diagnosis values available and valid module passivation based on an module error indication reset, if QBAD changed to FALSE 16#W#FFFF Read request not possible error SFB52 call error details available at state_SFB52a_x / state_SFB52b_x indication reset with next function request
5.6.3.3.2 Diagnosis Information F_Module_mod_x The diagnosis information based on an module error. The error values with explanation are shown at the module manual at diagnosis error. 5.6.3.3.3 Diagnosis Information F_DI_z_mod_x The diagnosis information based on an F-DI error. The error values with explanation are shown at the module manual at diagnosis error. 5.6.3.3.4 Diagnosis Information F_DO_z_mod_x The diagnosis information based on an F-DO error. The error values with explanation are shown at the module manual at diagnosis error. 5.6.3.3.5 Diagnosis Information Reg_xx_mod_x Additional diagnosis information for WAGO support. 80 Example with Safety Controller from Siemens Application note A114802 6 Example with Safety Controller from Siemens
6.1 Terms of Use NOTICE
The examples and implementations listed are based exclusively on a test configuration with no reference to any machine or system.
To use the PROFIsafe modules in a system, the applicable regulations, standards and safety requirements of the machine are to be observed and implemented.
The general use of safety components does not automatically lead to a safe machine or system!
Note
This application note does not replace the device descriptions of the individual components used.
In addition, all required boundary conditions in the device manuals and program guidelines from Siemens Safety CPUs are to be observed.
Example with Safety Controller from Siemens 81 Application note A114802
6.2 Abstract programs and libraries 6.2.1 Step 7 V5.5 SP3 All informations available at: A114802_Step7_V_5_5__PRG_LIB__20131018.ZIP with - Step 7 project -> A114802_iPar_Option_WAGO_V53_121030.zip - Library -> WAGO_iPar_Option_Bib_V_5_3.zip
6.2.2 TIA V11 SP2 UP5 All informations available at: A114802_TIA_V11_SP2_UP5__PRG_LIB__20131018.ZIP with - Project
6.2.3 TIA V12 SP1 All informations available at: A114802_TIA_V12_SP1__PRG_LIB__20131018.ZIP with - Project
A114802_TIA_V12_SP1__V_0_0_Bib_5_3__20131018.zip
- External library -> TIA_V12_SP1_Wago_iParOption_V5_3.zip 82 Example with Safety Controller from Siemens Application note A114802 6.3 System Configuration 6.3.1 Hardware Configuration The following hardware configuration is implemented in the Step 7 project:
Fig. 65 Screenshot of the hardware configuration of the Step 7 project 6.3.2 Safety Control A CPU 319F-3 PN/DP was used for the example:
Fig. 66 Screenshot of the properties of the CPU319F hardware configuration for Step 7 Example with Safety Controller from Siemens 83 Application note A114802
6.3.3 PROFIBUS DP 6.3.3.1 Slave with PROFIBUS DP address 6 The PROFIBUS DP slave is configured as follows:
Fig. 67 Configuration of the PROFIBUS DP slave with PROFIsafe modules 750-660 / 750-665
Fig. 68 Screenshot of the hardware configuration of the PROFIBUS DP Slave with PROFIsafe 750-660 / 750-665
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F
750-660/ 000-001 8 FDI 24V DC 5 5 1021 F00005_196 DB 3277
750-665/ 000-001 4 FDI / 4 FDO 24V DC 0.5A 10 10 1022 F00010_196 DB 3278 Fig. 69 Safety definitions for PROFIsafe 750-660 / 750-665 with PROFIBUS DP 84 Example with Safety Controller from Siemens Application note A114802 The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-432 4DI 0.0 Reset button (normally open contact) 0.1 Switch 1 (normally open contact) -> Function Activation 1 0.2 Switch 2 (normally open contact) -> Function Activation 2 0.3 Switch 3 (normally open contact) -> Function Activation 3 75x-530 8DO 0.0 Status: Safety program active 0.1 Status: EStop active 0.2 Status: Output of substitute values active 0.3 Status: User acknowledgment of safety modules expected 0.4 Status: Reserved 0.5 Status: Feedback loop error 0.6 Status: Warning, safety program active 0.7 Status: Error, safety program active 750-660/000-001 8FDI 5.0 Emergency Stop Contact 1 (normally closed contact) 5.1 Emergency Stop Contact 2 (normally closed contact) 5.2 Reserved / no function 5.3 Reserved / no function 5.4 Feedback relay control 1 788-384 (normally open contact) 5.5 Feedback relay control 2 788-384 (normally open contact) 5.6 Feedback relay control 3 788-384 (normally open contact) 5.7 Feedback relay control 4 788-384 (normally open contact) 750-665/000-001 4FDI/4FDO 10.0 Relay control 1 788-384 10.1 Relay control 2 788-384 10.2 Relay control 3 788-384 10.3 Relay control 4 788-384 10.0 Feedback relay control 1 788-384 (normally closed contact) 10.1 Feedback relay control 2 788-384 (normally closed contact) 10.2 Feedback relay control 3 788-384 (normally closed contact) 10.3 Feedback relay control 4 788-384 (normally closed contact) Fig. 70 Hardware wiring for PROFIBUS-DP Slave Add. 6
Example with Safety Controller from Siemens 85 Application note A114802
6.3.3.2 Slave with PROFIBUS DP address 9 The PROFIBUS DP slave is configured as follows:
Fig. 71 Configuration of the PROFIBUS DP slave with PROFIsafe modules 753-662 / 753-667
Fig. 72 Screenshot of the hardware configuration of the PROFIBUS DP Slave with PROFIsafe 753-662 / 753-667
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F
75x-662/ 000-003 8 FDI 24V DC 25 25 206 F00025_196 DB 3279
75x-667/ 000-003 4 FDI / 4 FDO 24V DC 30 30 207 F00030_196 DB 3280 Fig. 73 Safety definitions for PROFIsafe 753-662 / 753-667 with PROFIBUS DP 86 Example with Safety Controller from Siemens Application note A114802 The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-430 8DI 20.0 20.1 20.2 20.3 20.4 20.5 20.6 20.7 75x-530 8DO 20.0 Status: Safety program active 20.1 Status: EStop active 20.2 Status: Output of substitute values active 20.3 Status: User acknowledgment of safety modules expected 20.4 Status: Reserved 20.5 Status: Feedback loop error 20.6 Status: Warning, safety program active 20.7 Status: Error, safety program active 753-662/000-002 8FDI 25..0 Emergency Stop Contact 1 (normally closed contact) 25.1 Emergency Stop Contact 2 (normally open contact) 25.2 25.3 25.4 25.5 25.6 25.7 753-667/000-002 4FDI/4FDO 30.0 Relay control 1 788-384 30.1 Relay control 2 788-384 30.2 Relay control 3 788-384 30.3 Relay control 4 788-384 30.0 Feedback relay control 1 788-384 (normally closed contact) 30.1 Feedback relay control 2 788-384 (normally closed contact) 30.2 Feedback relay control 3 788-384 (normally closed contact) 30.3 Feedback relay control 4 788-384 (normally closed contact) Fig. 74 Hardware wiring for PROFIBUS-DP Slave Add. 9
Example with Safety Controller from Siemens 87 Application note A114802
The following parameter settings are carried out for the PROFIsafe modules: 75x-662/000-003 8 FDI (DP 9, Slot 4)
75x-667/000-003 4 FDI / 4 FDO (DP 9, Slot 5)
88 Example with Safety Controller from Siemens Application note A114802 6.3.3.3 Slave with PROFIBUS DP address 13 The PROFIBUS DP slave is configured as follows:
Safety components, Leuze electronic
Fig. 75 Configuration of the PROFIBUS DP slave 13 with PROFIsafe modules
Fig. 76 Screenshot of the hardware configuration of the PROFIBUS DP Slave 13 with PROFIsafe modules Example with Safety Controller from Siemens 89 Application note A114802
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F
75x-667/ 000-003 4 FDI / 4 FDO 24V DC 500 500 10 F00500_196 DB 3324
75x-667/ 000-003 4 FDI / 4 FDO 24V DC 505 505 11 F00505_196 DB 3325
75x-667/ 000-003 4 FDI / 4 FDO 24V DC 510 510 12 F00510_196 DB 3326
75x-662/ 000-003 8 FDI 24V DC 515 515 13 F00515_196 DB 3327
75x-661/ 000-003 4 FDI 24V DC 520 520 14 F00520_196 DB 3328
75x-661/ 000-003 4 FDI 24V DC 525 525 15 F00525_196 DB 3329
75x-661/ 000-003 4 F DI 24V DC 530 530 16 F00530_196 DB 3330
75x-661/ 000-003 4 FDI 24V DC 535 535 17 F00535_196 DB 3331 Fig. 77 Safety definitions for PROFIsafe modules in the PROFIBUS DP slave 13
The following hardware wiring is implemented for this slave. Module I Address O Address Use 753-667/000-002 4FDI/4FDO 500.0 Relay control 1 288-414 500.1 500.2 500.3 500.0 Feedback relay control 1 288-414 (normally closed contact) 500.1 500.2 500.3 753-667/000-002 4FDI/4FDO 505.0 505.1 505.2 505.3 505.0 505.1 505.2 505.3 90 Example with Safety Controller from Siemens Application note A114802
753-667/000-002 4FDI/4FDO 510.0 510.1 510.2 510.3 Relay control 2 288-414 510.0 510.1 510.2 510.3 Feedback relay control 1 288-414 (normally closed contact) 753-662/000-002 8FDI 515.0 Make contact 288-414 (relay on A 500.0) 515.1 515.2 515.3 515.4 515.5 515.6 515.7 753-661/000-002 4FDI 520.0 Make contact 288-414 (relay on A 500.0) 520.1 520.2 520.3 753-661/000-002 4FDI 525.0 Make contact 288-414 (relay on A 500.0) 525.1 5252 525.3 753-661/000-002 4FDI 530.0 Make contact 288-414 (relay on A 500.0) 530.1 530.2 OSSD 1 Leuze Solid 2 light grid 530.3 OSSD 2 Leuze Solid 2 light grid 750-661/000-002 4FDI 535.0 Leuze limit switch 1 (normally closed contact) 535.1 Leuze limit switch 1 (normally open contact) 535.2 Leuze limit switch 2 (normally closed contact) 5353 Leuze limit switch 2 (normally open contact) Fig. 78 Hardware wiring for PROFIBUS-DP Slave Add. 9
Example with Safety Controller from Siemens 91 Application note A114802
The following parameter settings are carried out for the PROFIsafe modules: 75x-667/000-003 4 FDI / 4 FDO (DP 13, Slot 2)
75x-667/000-003 4 FDI / 4 FDO (DP 13, Slot 3)
92 Example with Safety Controller from Siemens Application note A114802 75x-667/000-003 4 FDI / 4 FDO (DP 13, Slot 4)
75x-662/000-003 8 FDI (DP 13, Slot 5)
Example with Safety Controller from Siemens 93 Application note A114802
75x-661/000-003 4 FDI (DP 13, Slot 6)
75x-661/000-003 4 FDI (DP 13, Slot 7)
94 Example with Safety Controller from Siemens Application note A114802 75x-661/000-003 4 FDI (DP 13, Slot 8)
75x-661/000-003 4 FDI (DP 13, Slot 9)
Example with Safety Controller from Siemens 95 Application note A114802
6.3.3.4 Slave with PROFIBUS DP address 17 The PROFIBUS DP slave is configured as follows:
Fig. 79 Configuration of the PROFIBUS DP slave with PROFIsafe module 75x-666
Fig. 80 Screenshot of the hardware configuration of the PROFIBUS DP Slave with PROFIsafe 753-666
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F
75x-666/ 000-003 4 FDI / 2 FDO 24V DC 350 350 666 F00350_196 DB 3336 Fig. 81 Safety definitions for PROFIsafe 75x-666 with PROFIBUS DP 96 Example with Safety Controller from Siemens Application note A114802 The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-666 4FDI / 2 FDO 24V DC /10A 350.0 350.1 350.2 350.3 350.0 Field power supply DO 750-1504 350.1 350.2 350.3 750-1504 16 DO 360.0 360.1 : 361.7 750-1504 16 DO 362.0 Relay control 2 288-414 362.1 363.0 Relay control 2 288-414 : 363.7 750-1504 16 DO 364.0 364.1 : 365.7 Fig. 82 Hardware wiring for PROFIBUS-DP Slave Add. 17
Example with Safety Controller from Siemens 97 Application note A114802
The following parameter settings are carried out for the PROFIsafe modules: 75x-666/000-003 4 FDI / 2 FDO (DP 17, Slot 2)
98 Example with Safety Controller from Siemens Application note A114802 6.3.4 PROFINET 6.3.4.1 "WAGO-750-370" Device The PROFINET device is configured as follows:
Fig. 83 Configuration of the PROFINET device with PROFIsafe modules 753-662 / 753-667
Fig. 84 Screenshot of the hardware configuration of the PROFINET device with PROFIsafe 753- 662 / 753-667
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F 75x-662/ 000-002 8 F-DI 24V DC 105 105 662 F00105_75x_ 662_8FDI DB 3281 75x-667/ 000-002 4 FDI / 4 FDO 24V DC 110 110 667 F00110_75x_ 667_4FDI_4FDO DB 3282 Fig. 85 Safety definitions for PROFIsafe 753-662 / 753-667 with PROFINET Example with Safety Controller from Siemens 99 Application note A114802
The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-430 8DI 100.0 100.1 100.2 100.3 100.4 100.5 100.6 100.7 75x-530 8DO 100.0 Status: Safety program active 100.1 Status: EStop active 100.2 Status: Output of substitute values active 100.3 Status: User acknowledgment of safety modules expected 100.4 Status: Reserved 100.5 Status: Feedback loop error 100.6 Status: Warning, safety program active 100.7 Status: Error, safety program active 753-662/000-003 8FDI 105.0 105.1 105.2 105.3 105.4 105.5 105.6 105.7 753-667/000-003 4FDI/4FDO 110.0 Relay control 1 788-384 110.1 Relay control 2 788-384 110.2 Relay control 3 2x 788-384 (parallel connection) 110.3 Relay control 4 288-414 110.0 Feedback relay control 1 788-384 (normally closed contact) 110.1 Feedback relay control 2 788-384 (normally closed contact) 110.2 Feedback relay control 3 2x 788-384 (both normally closed contact in series connection) 110.3 Feedback relay control 4 288-414 (normally closed contact) Fig. 86 Hardware wiring for PROFINET device 1
100 Example with Safety Controller from Siemens Application note A114802 The following parameter settings are carried out for the PROFIsafe modules: 753-662/000-002 8 FDI (PN 0, Slot 3)
753-667/000-002 4 FDI/ 4 FDO (PN 1, Slot 4)
Example with Safety Controller from Siemens 101 Application note A114802
6.3.4.2 "WAGO-750-370-1" Device The PROFINET device is configured as follows:
Fig. 87 Configuration of the PROFINET device with PROFIsafe modules 753-662 / 753-667
Fig. 88 Screenshot of the hardware configuration of the PROFINET device with PROFIsafe 753- 662 / 753-667
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F 75x-662/ 000-003 8 FDI 24V DC 52 52 62 F00052_753_ 662_8FDI DB 3322 75x-667/ 000-003 4 FDI / 4 FDO 24V DC 60 60 67 F00060_75x_ 667_4FDI_4FDO DB 3320 75x-661/ 000-003 4 FDI 24V DC 65 65 61 F00065_75x_ 661_4FDI_iPar DB3323 Fig. 89 Safety definitions for PROFIsafe 753-662 / 753-667 with PROFINET 102 Example with Safety Controller from Siemens Application note A114802 The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-430 8DI 50.0 50.1 50.2 50.3 50.4 50.5 50.6 50.7 75x-530 8DO 50.0 Status: Safety program active 50.1 Status: EStop active 50.2 Status: Output of substitute values active 50.3 Status: User acknowledgment of safety modules expected 50.4 Status: Reserved 50.5 Status: Feedback loop error 50.6 Status: Warning, safety program active 50.7 Status: Error, safety program active 753-662/000-003 8FDI 52.0 52.1 52.2 52.3 52.4 52.5 52.6 52.7 753-667/000-003 4FDI/4FDO 60.0 Relay control 1 788-384 60.1 60.2 60.3 60.0 Feedback relay control 1 788-384 (normally closed contact) 60.1 60.2 60.3 753-661/000-003 4FDI 65.0 Limit switch (normally closed contact) 65.1 Limit switch (normally open contact) 65.2 65.3 Fig. 90 Hardware wiring for PROFINET device 1 Example with Safety Controller from Siemens 103 Application note A114802
The following parameter settings are carried out for the PROFIsafe modules: 75x-662/000-003 8 FDI (PN 1, Slot 3)
75x-667/000-003 4 FDI / 4 FDO (PN 1, Slot 4)
104 Example with Safety Controller from Siemens Application note A114802 75x-661/000-003 4 FDI (PN 1, Slot 5)
Example with Safety Controller from Siemens 105 Application note A114802
6.3.4.3 "WAGO-750-370-8" Device The PROFINET device is configured as follows (PROFINET via 758-915):
Fig. 91 Configuration of the PROFINET device with PROFIsafe module 75x-667
Fig. 92 Screenshot of the hardware configuration of the PROFINET device with PROFIsafe 753- 662 / 753-667
Module Type I Add. O Add. PROFIsafe Address Symbol F-Periphery DB CPU 319F 75x-667/ 000-003 4 FDI / 4 FDO 24V DC 210 210 7 F00210_75x_ 667_4FDI_4FDO DB3337 Fig. 93 Safety definitions for PROFIsafe 75x-667 with PROFINET 106 Example with Safety Controller from Siemens Application note A114802 The following hardware wiring is implemented for this slave. Module I Address O Address Use 75x-667/000-003 4FDI / 4 FDO 210.0 Relay control 1 788-384 210.1 210.2 210.3 210.0 Feedback relay control 1 788-384 (normally closed contact) 210.1 210.2 210.3 750-1405 16 DI 215.0 215.1 : 216.7 750-1504 16 DO 215.0 215.1 : 216.7 Fig. 94 Hardware wiring for PROFINET device 8 The following parameter settings are carried out for the PROFIsafe modules: 75x-667/000-003 4 FDI / 4 FDO (PN 8, Slot 1)
Example with Safety Controller from Siemens 107 Application note A114802
Abb. 95 PROFINET communication with Bluetooth Ethernet gateway Note
Please read the manual of the Bluetooth Ethernet gateway about details to communication bandwidth and start up.
Startup with the Bluetooth Ethernet gateway only with button MODE possible, no additional tools required. Settings at Slave-Gateway at first start up:
Settings at Master-Gateway at first start up:
108 Example with Safety Controller from Siemens Application note A114802 6.4 Software Structure The following software structure shows all possible uses of the already created function blocks for this defined system configuration. 6.4.1 Program Structure
6.4.1.1 Cyclic Program Calls OB1
Fig. 96 Graphic of block calls via cyclic program calls OB1 6.4.1.2 Program Calls via Watchdog Alarm OB35
Fig. 97 Graphic of block calls via watchdog alarm OB35 Example with Safety Controller from Siemens 109 Application note A114802
6.4.1.3 Runtime Group Assignments For a better overview of the possibilities, the program example was divided into 2 runtime groups to show all possibilities. For runtime group 1, the PROFIBUS DB slave address 6 and the PROFINET device are assigned "WAGO-750-370".
Fig. 98 Graphic of assignment of PROFIsafe modules to runtime group 1 For runtime group 2, the PROFIBUS DB slave address 9, PROFIBUS DB slave address 13 and the PROFINET device "WAGO-750-370" are assigned.
Fig. 99 Graphic assignment of PROFIsafe modules to runtime group 2 110 Example with Safety Controller from Siemens Application note A114802 6.4.2 Defined Interfaces
6.4.2.1 Cyclic Program to the Safety Program Data transfer between the standard PLC program and the safety program is to be carried out as follows based on the device manual of the safety CPU via flags: Cycle Comment Safety Transfer into MB 2 CPU timing flag MB502 OB35 E 0.0 / M 1.0 Reset safety program M 500.0 OB35 Fig. 100 Overview of defined flag interface to the safety program 6.4.2.2 Safety Program to the Cyclic Program Data transfer between the safety program and the cyclic S7 program has to be realized as a secure data block (F DB) based on the device manual of the S7 CPU. The DBs contain the following information: - Indication of the current status of the safety program - User acknowledgement feedback loop monitoring required - Output of substitute values, PROFIsafe module active
Fig. 101 Screenshot, excerpt structure F-DB499 Communication Safety -> cyclic program
Note
The respective status information in DB499 is created in the associated runtime group and stored in DB499. Within FC10, parts of the status information of DB499 are transferred to digital outputs as a status display.
Example with Safety Controller from Siemens 111 Application note A114802
6.4.2.3 Runtime Group Communication For direct data exchange between both runtime groups within the safety program, so-called F-runtime group communication is available as a system function. To use the interface, call up the "Edit F-runtime groups" sub-function under "Edit safety program" in the Step 7 interface and enter the required data block (designation family "RTG_DB" in the block header).
Fig. 102 Screenshot of the designation F-DB as "Cross-communication DB F program"
Fig. 103 Screenshot of runtime group communication 112 Example with Safety Controller from Siemens Application note A114802 6.4.3 Note about Assignment of the Safety Module to Runtime Group In the S7 tool chain, safety modules are always assigned to a runtime group. A safety module is automatically assigned by a write or read command within the application program to the respective input or output address of the safety module. In principle, only one safety module can be accessed from one runtime group, i.e., so-called runtime group communication has to be used for preparing module information for other runtime groups. The "Edit safety program" function can be used to read the current status of the assignment.
Fig. 104 Screenshot showing the assignment of the safety module to the runtime group Note
If not all PROFIsafe modules of the runtime group do not appear in the F- Periphery-DBs, no access within the safety program to the PROFIsafe module is realized.
In this program status, the missing PROFIsafe modules are also not reintegrated via the function block FB219 "F_ACK_GL". Possible remedy Read access to the information QBAD within the F- Periphery-DBs of the PROFIsafe module in the safety program.
Example with Safety Controller from Siemens 113 Application note A114802
6.5 Program Functions 6.5.1 Cyclic Application Program The standard application program is called up cyclically via the OB1 and processed according to the program calls. The individual function details are apparent from the respective network comments of the program. 6.5.2 Organization Blocks Used 6.5.2.1 Watchdog Alarm OB35 The safety program is called up time-controlled via organization block OB35. 6.5.2.2 Watchdog Alarm OB82 Organization block for diagnostic alarms no evaluation of the diagnostic information provided in this example. 6.5.2.3 Watchdog Alarm OB83 Organization block for "swapping a module" This OB is required to configure the PROFIsafe modules because a "swap" of the modules for the higher level control is carried out for defined access from I/O check to the PROFIsafe modules. 6.5.2.4 Watchdog Alarm OB85 Organization block for updating processing image. 6.5.2.5 Watchdog Alarm OB86 Organization block for module failure Example program should also continue to run as long as a distributed module is not available. 6.5.2.6 Watchdog Alarm OB87 Organization block for communication failure Example program should also continue to run as long as a distributed module is not available. 6.5.2.7 Start-up OB100 Organization block call at the start of the control, the PLC_INIT_ACTIVE flag is set and reset again at the end of OB1 Use of the flag on each INIT input of a FB. 114 Example with Safety Controller from Siemens Application note A114802 6.5.3 Safety Program 6.5.3.1 Function Basis The safety program is activated by a function call in OB35, the call sequence and required relationships were established via the "Edit safety program" function of Step 7. 6.5.3.2 Data Transfer from Standard Program To transfer unsafe signals from the standard program, the Step 7 documentation contains corresponding notes that must be observed.
Fig. 105 Screenshot of the Step 7 online help "Transfer from the Standard to the Safety Program" Source 4 Online help for Step 7 V5.4 SP 5 and Distributed Safety V 5.4 SP5
Example with Safety Controller from Siemens 115 Application note A114802
6.5.3.3 User Acknowledgement / Reintegration In principle, all PROFIsafe slaves go into a safe state when switched on and wait for the release to transition into standard mode by the safety host. The safe (passivated) slave status can be exited within the safety program by calling the FB219 "F_ACK_GL" or by manually selecting the acknowledgement via the F periphery DB signal "ACK_REI". In the example program, the FB219 call is implemented in FB501 for the runtime group FC500 and in FB601 for the runtime group FC600.
Fig. 106 Screenshot of the reintegration runtime group 1 in FB501 call
Fig. 107 Screenshot of the reintegration runtime group 2 in FB601 call
Information
More general information about F periphery DB and signal meanings is available in Chapter3.4.3.3 Fail-safe I/O DB p. 21.
116 Example with Safety Controller from Siemens Application note A114802 6.5.3.4 Evaluation E-Stop Active In the example, 2 E-Stop buttons are evaluated that have the following responses in the example program: - Emergency stop (total) on PROFIsafe module 750-660 (DP add. 6) shuts down the example completely. - Emergency stop (individual) on PROFIsafe module 753-662 (DP add. 9) shuts down a part of the demonstration structure. The fast stop (total) is evaluated or detected by the FB215 "F_ESTOP1" within the 1st runtime group. The FB215 is available via the "F-Application Blocks" library from Distributed Safety.
Fig. 108 Screenshot showing evaluation of EStop (total) in runtime group 1 "No active EStop displayed" appears on output Q of FB215 "F_ESTOP1" via Q = TRUE. This information must be provided due to the available editor functions in the next network for both cyclic processing within runtime group 1 and runtime communication via the DB500:
Fig. 109 Screenshot showing evaluation of EStop active and transfer to the 2nd runtime group Example with Safety Controller from Siemens 117 Application note A114802
The fast stop is also evaluated by the FB215 "F_ESTOP1" within the 2nd runtime group.
Fig. 110 Screenshot showing evaluation of EStop (individual) in runtime group 2 To implement the required fast stop function, it is evaluated in the next network whether the fast stop was activated total or individual to make this information available to the subsequent application and the runtime communication via DB600.
Fig. 111 Screenshot showing evaluation of EStop active and transfer to the 1st runtime group 118 Example with Safety Controller from Siemens Application note A114802 6.5.3.5 Relay Control To control and monitor the relay function, FB216 "F_FDBACK" from the "F- Application Blocks" library is used for each relay.
Fig. 112 Screenshot of the call FB216 "F_FDBACK" in the application program
Fig. 113 Screenshot of the online help FB216 "F_FDBACK" Source 4 Online help for Step 7 V5.4 SP 5 and Distributed Safety V 5.4 SP5
FB input Program variable Use ON Switches ON/OFF the relay FEEDBACK safeIn_665_DP_1 Feedback drawn from relay (normally closed contact) QBAD_FIO F00010_196.QBAD QBAD status F module from F periphery DB ACK resetSafety Application reset for module Fig. 114 Explanations of block wiring of application program for "F_FDBACK" Example with Safety Controller from Siemens 119 Application note A114802
Switch 1 (E 0.1), switch 2 (E 0.2) and switch 3 (E 0.3) are used in the application program to activate or deactivate the relay.
Fig. 115 Screenshot of control relay 1 application program (FB501) The activation or deactivation of the field power supply with the PROFIsafe module 75x-666/000-003 depends on the state of the E-Stop at the safety program:
Abb. 116 Screenshot enable 75x-666/000-003(FB501)
6.5.3.6 Status Displays of the Safety Program At the end of the safety program (FB501 and FB601), the current program and PROFIsafe module status is transferred to DB499, so that this information can be evaluated in the cyclic program. 120 Example with Safety Controller from Siemens Application note A114802 6.6 Function Activation To activate the example, the following steps are required. The current program status is displayed via outputs. After switching on the voltage supply, the system starts to boot, the system configuration is checked by the CPU and the system goes into cyclic mode. The following status displays are shown on the digital outputs: - Indicator safety program active via outputs A0.0, A 20.0, A 50.0 and A 100.0 - Indicator EStop active via outputs A0.1, A20.1, A50.1 and A100.1 - Indicator error safety program active via outputs A 0.7, A20.7, A50.7 and A100.7 By activating the reset from the E0.0 input, all pending messages are reset, the status display on the outputs only display the message "Safety program active" from the outputs A0.0, A20.0, A50.0 and A100.0. For direct control of all outputs, the respective function request can be activated within the safety program from switch 1 (input E0.1). Example with Safety Controller from Siemens 121 Application note A114802
6.7 Using iPar Server Option 6.7.1 General In this example, all available function blocks are used to show an application. A variable table is available for each application variant listed to follow each function individually. 6.7.2 Software Structure iPar Option 6.7.2.1 General The internal iParameters of PROFIsafe module V2 iPar can be transferred to defined data blocks in normal application programs by function blocks from WAGO for S7 safety controls. The following examples are implemented: - Implementation with slave reference via FC14 in OB1
Fig. 117 Software structure of example FC14 with slave reference 122 Example with Safety Controller from Siemens Application note A114802 - Implementation without slave reference via FC15 in OB1
Fig. 118 Software structure of example FC15 without slave reference 6.7.2.2 Required Block Calls Only one call is made in the cyclic application program from OB1 to use the function blocks.
Fig. 119 Graphic of block calls via cyclic program calls OB1 Example with Safety Controller from Siemens 123 Application note A114802
6.7.2.3 Function Calls in FC9 Read active diagnosis data of PROFIsafe modules with FB101. 6.7.2.4 Function Calls in FC14 The iParameter data of the PROFIsafe modules is saved per slave / device in a single data block from the calls in FC14. 6.7.2.4.1 Call for PROFIBUS-DP Slave 9
Fig. 120 Screenshot of call FB37 V4.0 for PROFIBUS DP slave 9 The following parameterizations are implemented for this call. - iParameter data block DB 100 - 2 PROFIsafe modules available in the slave - Bus system PROFIBUS DP
124 Example with Safety Controller from Siemens Application note A114802 6.7.2.4.2 Call for PROFINET Device 2
Fig. 121 Screenshot of call FB37 V4.0 for PROFINET Device 2 The following parameterizations are implemented for this call. - iParameter data block DB 101 - 3 PROFIsafe modules available in the slave - Bus system PROFINET
Example with Safety Controller from Siemens 125 Application note A114802
6.7.2.4.3 Call for PROFIBUS-DP Slave 13
Fig. 122 Screenshot of call FB38 V4.0 for PROFIBUS DP slave 13 The following parameterizations are implemented for this call. - iParameter data block DB 102 - 8 PROFIsafe modules available in the slave - Bus system PROFIBUS DP
126 Example with Safety Controller from Siemens Application note A114802 6.7.2.5 Function Calls in FC15 All iParameter data of the PROFIsafe modules is saved in on data block via the calls in FC15 and evaluation of the QBAD and ACK_REQ module states implemented.
Fig. 123 Screenshot of call FB39 for iParameter upload and download
: :
Fig. 124 Screenshot of call FB40 V4.0 for evaluation QBAD and ACK_REQ The following parameterizations are implemented for this call. - iParameter data block DB 103 - 15 PROFIsafe modules in the application - Bus system PROFIBUS DP and PROFINET Example with Safety Controller from Siemens 127 Application note A114802
6.7.3 Function Example The following examples show the required workflows for activating the individual functions. The examples are implemented for the function call of FB38 [DB52] in FC14 for 8 PROFIsafe modules in PROFIBUS DP slave No. 13, the iParameters are stored in data block DB102. 6.7.3.1 Check configuration The parameterizations in the software and the actually available modules are checked using the "CHECK_CFG_REQ" function request. Before activating the function request, the required modules must be selected in the slave via "SELECT_MODULE":
Fig. 125 Screenshot of function request for modules via VAT_iPar_Option_DP13 After specifying the required modules, the function is activated via "CHECK_CFG_REQ":
Fig. 126 Screenshot of function request "CHECK_CFG_REQ" via VAT_iPar_Option_DP13 After activating the function, the "BUSY" output switches to TRUE and keeps this state until the function request is ended without error "DONE" or with error "ERROR". 128 Example with Safety Controller from Siemens Application note A114802 In this case, the function request was ended without error with the following states:
Fig. 127 Screenshot of state messages after "CHECK_CFG_REQ" - "DONE" shows function request done without error. - "DONE_ALL_MODULES" shows function request was executed by all available. - "STATE_FCT_REQ_OK" displays bit-coded that 8 modules have executed the function request without error. Reset of the function request leads to a reset of the status displays. 6.7.3.2 iParameter Upload Before activating the function request, the required modules must be selected in the slave via "SELECT_MODULE":
Fig. 128 Screenshot of function request for modules via VAT_iPar_Option_DP13 After specifying the required modules, the function is activated via "UPLOAD_REQ":
Fig. 129 Screenshot of function request "UPLOAD_REQ" via VAT_iPar_Option_DP13 After activating the function, the "BUSY" output switches to TRUE and keeps this state until the function request is ended without error "DONE" or with error "ERROR". Example with Safety Controller from Siemens 129 Application note A114802
In this case, the function request was ended without error with the following states:
Fig. 130 Screenshot of state messages after "UPLOAD_REQ" - "DONE" shows function request done without error. - "DONE_ALL_MODULES" shows function request was executed by all available. - "UPLOAD_ALL" displays that there is one iParameter dataset available for each PROFIsafe module of the slave This output remains active without function request to make this status available to the application program. - "STATE_FCT_REQ_OK" displays bit-coded that 8 modules have executed the function request without error. Reset of the function request leads to a reset of the status displays. Check of the data in iParameter data block DB102: - Timestamp of the last "UPLOAD" for module 1
Fig. 131 Screenshot of the content of iParameter DB102 Advice: The Information dsv_info_mod_x shows the actual iPar_CRC of the module dataset -> compare between setting HW-Config and module dataset possible without tooling. - Status messages in the iParameter data block
Fig. 132 Screenshot of the content of iParameter DB102 130 Example with Safety Controller from Siemens Application note A114802 6.7.3.3 iParameter Comparison Before activating the function request, the required modules must be selected in the slave via "SELECT_MODULE", here now only for 4 modules in the slave:
Fig. 133 Screenshot of function request for modules via VAT_iPar_Option_DP13 After specifying the required modules, the function is activated via "COMPARE_REQ":
Fig. 134 Screenshot of function request "COMPARE_REQ" via VAT_iPar_Option_DP13 After activating the function, the "BUSY" output switches to TRUE and keeps this state until the function request is ended without error "DONE" or with error "ERROR". In this case, the function request was ended without error with the following states:
Fig. 135 Screenshot of state messages after "COMPARE_REQ" - "DONE" shows function request done without error. - "STATE_FCT_REQ_OK" displays bit-coded that 4 modules have executed the function request without error. - "DONE_ALL_MODULES" remains in the FALSE state because the comparison was activated for only 4 PROFIsafe modules, but 8 modules are installed in the slave. Example with Safety Controller from Siemens 131 Application note A114802
Reset of the function request leads to a reset of the status displays. Check of the data in iParameter data block DB102: - Timestamp of the last "COMPARE" for module 1
Fig. 136 Screenshot of the content of iParameter DB102 - Status messages in the iParameter data block
Fig. 137 Screenshot of the content of iParameter DB102 6.7.3.4 iParameter Download Before activating the function request, the required modules must be selected in the slave via "SELECT_MODULE":
Fig. 138 Screenshot of function request for modules via VAT_iPar_Option_DP13 After specifying the required modules, the function is activated via "DOWNLOAD_REQ" as long as iParameters have been saved in the control via a corresponding "UPLOAD":
Fig. 139 Screenshot of function request "DOWNLOAD_REQ" via VAT_iPar_Option_DP13 After activating the function, the "BUSY" output switches to TRUE and keeps this state until the function request is ended without error "DONE" or with error "ERROR". 132 Example with Safety Controller from Siemens Application note A114802 In this case, the function request was ended with error and the following states:
Fig. 140 Screenshot of state messages after "DOWNLOAD_REQ" - "ERROR" shows function request done with error. - "ERROR_FB" shows W#16#8040 = "Error function request communication active" - "STATE_FCT_REQ_ERROR" displays "DW#16#0000000F" i.e., error function request for modules 1 to 4 - "STATE_FCT_REQ_OK" displays "W#16#000000F0" i.e., error-free processing of the function request for modules 5 to 8 For errors within the function requests, detailed diagnostics can be read within the iParameter data block for each module:
Fig. 141 Screenshot of the content of iParameter DB102 - "error_Com_1" shows W#16#8010 = Function selection Download without valid iParameters in the control - "error_nb_Com_1" shows W#16#0003 = Additional information for fault location (pure diagnosis) In this system state, the function request now has to be reset to acknowledge the pending error messages with a "RESET" and to make a new function request possible. Example with Safety Controller from Siemens 133 Application note A114802
6.7.3.5 Read Diagnosis Data (manual request) Before activating the function request, the required modules must be selected in the slave via "SELECT_MODULE":
Fig. 142 Screenshot of function request for modules via VAT_iPar_Option_DP13 After specifying the required modules, the function is activated via "DIAG_DATA_REQ:
Fig. 143 Screenshot of function request "DIAG_DATA_REQ" via VAT_iPar_Option_DP13 After activating the function, the "BUSY" output switches to TRUE and keeps this state until the function request is ended without error "DONE" or with error "ERROR". In this case, the function request was ended with error and the following states:
Fig. 144 Screenshot of state messages after "DIAG_DATA_REQ" - "DONE" shows function request done without error. - "DONE_ALL_MODULES" shows function request was executed by all available. - "STATE_FCT_REQ_OK" displays bit-coded that 8 modules have executed the function request without error. Reset of the function request leads to a reset of the status displays. 134 Example with Safety Controller from Siemens Application note A114802 The diagnosis data are stored at the iParameter-DB per PROFIsafe module:
Abb. 145 Screenshot diagnosis information after DIAG_DATA_REG at iParameter-DB The information error_info_mod_x shows the actual state of the diagnosis information, i.e. are the values valid. The error values or diagnosis information are shown at the manual diagnosis of errors. For the example here, the following information is available:
Abb. 146 Screenshot manual PROFIsafe module error 0x202 6.7.3.6 Read Diagnosis Data (automatic read) With the function request READ_DIAG_DATA the automatic read function is activated. If the information QBAD at the F-Periphery-DB changed to TRUE, the diagnosis read function is activated automatically.
Abb. 147 Screenshot function request with VAT_iPar_Option_DP13 If the function request is active, no other function request is possible.
References TIA Portal V11 SP2 UP5 135 Application note A114802
7 References TIA Portal V11 SP2 UP5 7.1 General An own library of WAGO iPar-Server Option is available for TIA Portal V11 from SP4 with all known functions. 7.1.1 Global library WAGO iPar-Server Option The WAGO iPar-Server Option library for TIA Portal should be used as global library at the TIA Portal V11 from UP4. With the library administration of TIA Portal, the WAGO iPar-Server Option is available for all TIA Portal projects:
Abb. 148 Screenshot TIA Portal V11 library TIA_V11_WAGO_iParOption_V5_x
Information
The description of the function blocks is valid for Step 7 V5.5 or TIA V11 library.
136 References TIA Portal V11 SP2 UP5 Application note A114802 7.1.2 Example A114802_TIA_V_11_SP2_UP5_x_x_Bib_5_x The TIA Portal example is the same realization as Step 7 V 5.5, described at chapter 6 (same system configuration, parameterization, ):
Abb. 149 Screenshot TIA Portal V11 configuration example
Information
System configuration and parameterization is shown at chapter 6 system configuration with Step 7 V5.5.
References TIA Portal V11 SP2 UP5 137 Application note A114802
7.1.3 Parameterization with TCI interface The TCI communication interface is present at TIA Portal V11 SP2 Update 4 too. 7.1.3.1 TCI CC3 with PROFIBUS-DP Necessary steps activate TCI interface in combination with PROFIBUS-DP.
Abb. 150 Screenshot TIA Portal V11 activate device tool
Abb. 151 Screenshot TIA Portal V11 select online parameterization 138 References TIA Portal V11 SP2 UP5 Application note A114802
Abb. 152 Screenshot TIA Portal V11 set communication interface to plc
Abb. 153 Screenshot TIA Portal V11 WAGO Safety-Editor-75x active References TIA Portal V11 SP2 UP5 139 Application note A114802
7.1.3.2 TCI CC2 with PROFINET Necessary steps activate TCI interface in combination with PROFINET.
Abb. 154 Screenshot TIA Portal V11 activate WAGO-I/O-Check 3
Abb. 155 Screenshot TIA Portal V11 WAGO Safety-Editor-75x active 140 References TIA Portal V12 SP1 Application note A114802 8 References TIA Portal V12 SP1 8.1 General An own library of WAGO iPar-Server Option is available for TIA Portal V12 from SP1 with all known functions. 8.1.1 Global library WAGO iPar-Server Option The WAGO iPar-Server Option library for TIA Portal should be used as global library at the TIA Portal V12 from SP1. With the library administration of TIA Portal, the WAGO iPar-Server Option is available for all TIA Portal projects:
Abb. 156 Screenshot TIA Portal V12 library TIA_V12_SP1_WAGO_iParOption_V5_x
Information
The description of the function blocks is valid for Step 7 V5.5 or TIA V12 library.
References TIA Portal V12 SP1 141 Application note A114802
8.1.2 Example A114802_TIA_V_V12_SP1_x_x_Bib_5_x The TIA Portal example is the same realization as Step 7 V 5.5, described at chapter 6 (same system configuration, parameterization, ):
Abb. 157 Screenshot TIA Portal V12 SP1 configuration example
Information
System configuration and parameterization is shown at chapter 6 system configuration with Step 7 V5.5.
142 References TIA Portal V12 SP1 Application note A114802 8.1.3 Parameterization with TCI interface The TCI communication interface is present at TIA Portal V11 SP2 Update 4 too. 8.1.3.1 TCI CC3 with PROFIBUS-DP Necessary steps activate TCI interface in combination with PROFIBUS-DP.
Abb. 158 Screenshot TIA Portal V12 SP1 activate device tool
Abb. 159 Screenshot TIA Portal V12 SP1 select online parameterization References TIA Portal V12 SP1 143 Application note A114802
Abb. 160 Screenshot TIA Portal V12 SP1 WAGO Safety-Editor-75x active 144 References TIA Portal V12 SP1 Application note A114802 8.1.3.2 TCI CC2 with PROFINET Necessary steps activate TCI interface in combination with PROFINET.
Abb. 161 Screenshot TIA Portal V12 SP1 activate WAGO-I/O-Check 3
Abb. 162 Screenshot TIA Portal V12 SP1 WAGO Safety-Editor-75x active Information about Using Safety Components 145 Application note A114802
9 Information about Using Safety Components 9.1 Safety Light Curtain SOLID 2, Leuze electronic The following points briefly describe the boundary conditions for using a SOLID 2 light grid in the standard version. 9.1.1 Electrical connection To use the SOLID 2 safety light curtain, the following wiring is implemented on the sender side: - Pin 1 24 V DC and Pin 3 0 V DC - Pin 4 24 V DC Activation of internal test
Fig. 163 SOLID 2 sender pin assignment Source 6 SOLID 2 operating instructions, Leuze electronic The following wiring is implemented on the receiver side: - Pin 1 24V DC and Pin 3 0 V DC - Pin 4 OSSD 1 on safe input n - Pin 2 OSSD 2 on safe input n+1
Fig. 164 SOLID 2 receiver pin assignment Source 6 SOLID 2 operating instructions, Leuze electronic 146 Information about Using Safety Components Application note A114802 9.1.2 Configuring PROFIsafe Module By using the OSSD outputs of the SOLID 2 safety light grid, the following settings are made within the iParameters of the PROFIsafe module: iParameter PROFIsafe module Setting: Input filter 3 ms Short-circuit test input n "not active" Short-circuit test input n+1 "not active"
Signal processing can also be activated in the PROFIsafe module. The following settings are required: iParameter PROFIsafe module Setting: Valence analysis "In & In+1" "equivalent" Discrepancy time "In & In+1" 100 ms Restart barrier "In & In+1" acc. requirement
Note
When using signal processing in the PROFIsafe module, the signal states defined in the manual for inputs are to be observed.
Fig. 165 Signal states equivalent evaluation of PROFIsafe modules Source 7 PROFIsafe module 753-661/000-003 operating instructions
Information about Using Safety Components 147 Application note A114802
9.2 Safety Position Switch S300, Leuze electronic The following points briefly describe the boundary conditions when using the S300 safety position switch for the example described here. 9.2.1 Electrical connection To use both S300 safety position switches, the following wiring is implemented: - PROFIsafe module clock output T1 on connection 21 - PROFIsafe module input I1 on connection 22 - PROFIsafe module clock output T2 on connection 13 - PROFIsafe module input I2 on connection 14 - PROFIsafe module clock output T3 on connection 21 - PROFIsafe module input I3 on connection 22 - PROFIsafe module clock output T4 on connection 13 - PROFIsafe module input I4 on connection 14
148 Information about Using Safety Components Application note A114802 9.2.2 Configuring PROFIsafe Module By using the S300 safety position switch, the following settings are made within the iParameters of the PROFIsafe module: iParameter PROFIsafe module Setting: Input filter 5 ms Short-circuit test input 1 "active" Short-circuit test input 2 "active" Short-circuit test input 3 "active" Short-circuit test input 4 "active"
Signal processing for the first position switch as follows: iParameter PROFIsafe module Setting: Valence analysis "I1& I2" "antivalent" Discrepancy time "I1& I2" 200 ms Restart barrier "I1& I2" "yes"
Note
When using signal processing in the PROFIsafe module, the signal states defined in the manual for inputs are to be observed.
Fig. 167 Signal states antivalent evaluation of PROFIsafe modules Source 7 PROFIsafe module 753-661/000-003 operating instructions Source Directory 149 Application note A114802
10 Source Directory Source 1: WAGO homepage as of 12/04/03 Source 2 Representation of theF-Periphery DB in Step 7 for PROFIsafe modules (Step 7 V5.4 SP5) Source 3: Screenshot of Step 7 Project V5.4 SP5 Source 4 Online help for Step 7 V5.4 SP 5 and Distributed Safety V 5.4 SP5 Source 5 Homepage of PROFIBUS and PROFINET International (09/09/10) Source 6 SOLID 2 operating instructions, Leuze electronic Source 7 PROFIsafe module 753-661/000-003 operating instructions Source 8 S300 safety limit switch operating instructions, Leuze electronic
If library version 5.0 is used, please update to version 5.3.
If the library is changed from version 4.x to 5.x, an update of the iParameter data block to version 5.x is necessary too.
Version information 151 Application note A114802
11.2 Application Note
Version Date Notes: 00.01.00 10.12.02 first release 00.01.01 11.01.24 Add information 00.01.02 11.02.17 Add Library information V 3.8 00.02.00 11.03.09 Update library to V4.0: + change structure iParameter-DB + read diagnosis information PROFIsafe modules + copy state of function request at iParameter-DB + support 75x-666/000-003 + add FB41 using 10 PROFIsafe modules V2 iPar per slave
00.02.01 11.05.27 Update library to 4.1: + change FB37, FB38, FB39, FB41 -> miscalculation offset for error indication at iParameter datablock if timeout function request to FB36 active + no additional function + update existing realization recommended 00.02.02 11.08.15 Add information example: + enhancement with PROFIsafe module 4FDI / 2FDO 24V DC + enhancement Bluetooth Ethernet gateway 759-915 Update description based on module enhancements 00.02.03 10.01.12 Add information about new FB101: + read diagnosis data and store at data block + change demo project -> add FB101 call at FC9 Update description 00.03.00 03.04.12 Remove communication FB36 with SCL code at function block Change FB37, FB38. FB39, FB40, FB41 and change to SCL Change structure of DB37, DB38, DB39, DB41 Update description 00.03.01 29.08.12 Bug fix at FB37, FB38, FB39, FB40 and FB41 read information if F- Periphery Data block based on input parameters FB 00.03.02 12.09.12 Add information, library and example TIA Portal V11 SP2 Update 4 Add global information 00.03.03 21.10.13 Add information, library and example TIA Portal V11 SP2 Update 5 and TIA V12 SP1 Add global information __.__.__ __.__.__
WAGO Kontakttechnik GmbH & Co. KG PO Box 2880 D-32385 Minden Hansastrae 27 D-32423 Minden Phone: +49 (0) 571/8 87 0 Fax: +49 (0) 571/8 87 1 69 E-mail: info@wago.com